
From nobody Tue Aug  1 00:21:52 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A81F013292A for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 00:21:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, PP_MIME_FAKE_ASCII_TEXT=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AB7s3Q3sZtLL for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 00:21:48 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 06E9A132933 for <ietf@ietf.org>; Tue,  1 Aug 2017 00:21:47 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 1886B34A0F7; Tue,  1 Aug 2017 07:21:43 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id D411A160041; Tue,  1 Aug 2017 07:21:42 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 9F64D16004F; Tue,  1 Aug 2017 07:21:42 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id mt9eI18h6gob; Tue,  1 Aug 2017 07:21:42 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id E10B7160041; Tue,  1 Aug 2017 07:21:41 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 316A7809B357; Tue,  1 Aug 2017 17:21:39 +1000 (AEST)
To: jordi.palet@consulintel.es
Cc: "ietf@ietf.org" <ietf@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es> <787AE7BB302AE849A7480A190F8B93300A0155F5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-reply-to: Your message of "Tue, 01 Aug 2017 08:52:10 +0200." <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es>
Date: Tue, 01 Aug 2017 17:21:39 +1000
Message-Id: <20170801072139.316A7809B357@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uXwHYGFvGxZdyKlrZDIn52yhSVQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 07:21:51 -0000

In message <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es>, JORDI PALET M
ARTINEZ writes:
> Hi Med,
>
> In line …
>
> Saludos,
> Jordi
>
>
> -----Mensaje original-----
> De: ietf <ietf-bounces@ietf.org> en nombre de
> <mohamed.boucadair@orange.com>
> Responder a: <mohamed.boucadair@orange.com>
> Fecha: martes, 1 de agosto de 2017, 8:07
> Para: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>,
> "ietf@ietf.org" <ietf@ietf.org>
> Asunto: RE: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for
> IETF Meetings
>
>     Hi Jordi,
>
>     Please see inline.
>
>     Cheers,
>     Med
>
>     > -----Message d'origine-----
>     > De : ietf [mailto:ietf-bounces@ietf.org] De la part de JORDI PALET
>     > MARTINEZ
>     > Envoyé : lundi 31 juillet 2017 23:18
>     > À : ietf@ietf.org
>     > Objet : Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi
>     > for IETF Meetings
>     >
>     > NAT64 was invented for a specific case (when apps use DNS and the
>     > right APIs).
>
>     [Med] This may be misinterpreted as there is a dependency of NAT64 on
> DNS. This is not technically true. This was clarified in
> https://tools.ietf.org/html/rfc6889
>
> [Jordi] Right, I was not pretending to be technically perfect, but
> introducing when NAT64 fails in our network.
>
>        This approach is pragmatic in the sense that there is no dependency
>        on DNS implementation for the successful NAT handling.  As long as
>        there is a function (e.g., DNS64 [RFC6147] or other means) that can
>        construct an IPv6-embedded IPv4 address with a pre-configured IPv6
>        prefix, an IPv4 address and a suffix (refer to [RFC6052]), NAT64
>	 will work just fine.
>
>     FWIW, there are even NAT64 deployments that do not even rely on
> DNS64.
>
> [Jordi] Agree, we can talk about “DNS64 function” instead of DNS64.
> Again, in our IETF network there is a DNS64, so not the issue here.
>
>     >
>     > We realized then that app/devices vendors are lazy, or just they
>     > are out of the market, so we invented 464XLAT, which uses the same
>     > concept as
>     > NAT64/DNS64, but improves it by using the CLAT, a small daemon code
>     > in the
>     > OS or the CPE to solve the problems of the literal addresses and
>     > non-APIs
>     > apps/devices.
>     >
>     > We don’t need to tell the customers to disable IPv4 in their LANs,
>     > we need
>     > to make sure that we deploy CPEs that support CLAT.
>
>     [Med] Is there any CPE-based 464xlat deployment out there?
>
> [Jordi] I’ve identified 4 vendors up to now, with different products
> each. I’m sure there are more. I also know that other vendors did the
> development for specific customers and I’m also aware of other customers
> that asked for it. We have also the open source implementations, such as
> OpenWRT, supporting thousands of devices. Precisely this is my point. As
> IETF, our work is not just inventing transitions mechanism, but also
> making sure that if we state a set of requirements for CPEs, we include
> the support for those transition mechanisms.

People ask for lots of things and even write code.  That doesn't mean
that the thing they ask for is actually good or there is not something
better.  This IETF should be recommending what is actually best.


>     > This way, users don’t
>     > need to throw away old devices or apps, neither learn anything
>     > about IPv4
>     > or IPv6, and everybody is happy.
>     >
>     > We are trying to solve a problem with NAT64 which we knew
>     > since it was invented that it can’t be solved. We don’t have
>     > the time (unless some magic is discovered) to now tell every
>     > ISP that is deploying IPv6 and NAT64, to instead of NAT64
>     > have something different.
>
>     [Med] These operators (with CPEs) are already doing something
> *different*: DS-Lite and the like. NAT64 is widely deployed in cellular
> networks (host-based model), which is really straightforward.
>
> [Jordi] I agree, but if you have a network with cellular and wireline
> access, you may want to have a single transition mechanisms instead of
> two. If we don’t want to use NAT64 in wireline, then why we are trying to
> push it as the default SSID in our IETF network?

Because that's what everyone TALKS about.  NAT64 was sexy.

If we were being honest with ourselves we would do NAT64, then
DS-Lite, then MAP at consecutive IETFs and release a recommendation
for wireline deployments based off the experience or at least a
report on the issues found.

> It is a matter of
> preference of one or another transition mechanisms. All them have good
> and bad things. I see much simpler the combination of NAT64+CLAT than
> DS-Lite or MAP, in addition to the ONLY support in cellular networks is
> precisely NAT64/464XLAT, which means is the MOST extended transition
> mechanism by millions (billions?) of users. It makes a lot of sense to me
> to go in all the infrastructures to the one that has more deployment
> already.

Not really.  Cellular networks went with anything available, rather
than the best.  We are continuing the pay the price for that.

>     > The solution is
>     > there, if CPE vendors implement it, and we are talking about an
>     > available
>     > open source code (several implementations) that take a few bytes.
>     >
>     > We are already doing this effort in v6ops, I started trying to tell
>     > the RFC7084 about the need to update it, but didn’t succeeded. It
>     > seems that now we may want to have instead of a CPE requirements
>     > including this, an additional document to be a must for CPE vendors
>     > to support it, in case the CPE expects “IPv4 old devices and apps”
>     > in the LANs (which is real world life, and will be for 3-5 years).
>
>     [Med] I'm afraid we don't need it. The IETF already specified tools
> to address that case (DS-Lite, MAP-E).
>
> [Jordi] I guess no need to repeat myself …
>
>
>     >
>     > Regards,
>     > Jordi
>     >
>     >
>     > -----Mensaje original-----
>     > De: ietf <ietf-bounces@ietf.org> en nombre de Ole Jacobsen
>     > <olejacobsen@me.com>
>     > Responder a: Ole Jacobsen <olejacobsen@me.com>
>     > Fecha: lunes, 31 de julio de 2017, 23:01
>     > Para: Ted Lemon <mellon@fugue.com>
>     > CC: <ietf@ietf.org>
>     > Asunto: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi
> for IETF
>     > Meetings
>     >
>     >
>     >     You said:
>     >     >
>     >     > Brian, why on earth would we want to advertise IPv6 to IETF
>     >     > attendees?  We invented IPv6.  If we really can't run a
> v6-only
>     >     > network at IETF, what that says is that we have failed
> utterly and
>     >     > expensively.  I do not believe that this is correct: IPv6
> works very
>     >     > well.
>     >
>     >     Putting on my naive end-user hat:
>     >
>     >     That might be true, but here is the thing: "The mission of the
> IETF is
>     >     to make the INTERNET work better..." (my emphasis)
>     >
>     >     For at least a decade now, I've been told that I should "just
> use
>     >     IPv6" and some conferences have even "forced" me to do so.
>     >
>     >     I always respond with this question: "Does running IPv6 allow
> me to
>     >     connect to the Internet?" (meaning the v4 Internet for the most
> part).
>     >     The answer always seems to be: "Yes, but you have to manually
>     >     configure this and, oh by the way, this won't work at all and
> that app
>     >     might not behave as expected."
>     >
>     >     Demonstrating this to people who are experts seems like a waste
>     >     of time.
>     >
>     >     So it sounds to me like we HAVE indeed failed utterly and
> expensively.
>     >     99% of Internet users do not have any idea what version of IP
> they are
>     >     running just as they have no idea what a MAC address is or
> why/if they
>     >     should care.
>     >
>     >     I'd love to see IPv6 succeed, but it is apparently impossible
> to do so
>     >     without teaching end-users a lot of stuff they really have no
> interest
>     >     in or ability to learn. What a shame.
>     >
>     >     Ole
>     >
>     >
>     >
>     >
>     >
>     > **********************************************
>     > IPv4 is over
>     > Are you ready for the new Internet ?
>     > http://www.consulintel.es
>     > The IPv6 Company
>     >
>     > This electronic message contains information which may be
> privileged or
>     > confidential. The information is intended to be for the use of the
>     > individual(s) named above. If you are not the intended recipient be
> aware
>     > that any disclosure, copying, distribution or use of the contents
> of this
>     > information, including attached files, is prohibited.
>     >
>     >
>
>
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
>
> This electronic message contains information which may be privileged or
> confidential. The information is intended to be for the use of the
> individual(s) named above. If you are not the intended recipient be aware
> that any disclosure, copying, distribution or use of the contents of this
> information, including attached files, is prohibited.
>
>
>

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Aug  1 00:32:23 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3950132A10 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 00:32:21 -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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TlFGprptiU14 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 00:32:20 -0700 (PDT)
Received: from mailhost.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 1D699132A04 for <ietf@ietf.org>; Tue,  1 Aug 2017 00:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v717WCds013304; Tue, 1 Aug 2017 09:32:12 +0200 (CEST)
Received: from client-0037.vpn.uni-bremen.de (client-0037.vpn.uni-bremen.de [134.102.107.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3xM7Lh5tGJzDLwv; Tue,  1 Aug 2017 09:32:12 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: normative references to IANA registries
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <716.1501548333@obiwan.sandelman.ca>
Date: Tue, 1 Aug 2017 09:32:11 +0200
Cc: ietf@ietf.org
X-Mao-Original-Outgoing-Id: 523265531.757938-845eb7f1a0e62fd9b714964eadaf71a9
Content-Transfer-Encoding: quoted-printable
Message-Id: <06672B8B-DDC5-4362-8729-346688F587DD@tzi.org>
References: <523.1501530916@obiwan.sandelman.ca> <E8859A9F-7539-4C6B-962C-56E6F3323C14@tzi.org> <716.1501548333@obiwan.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nLEHBZiOOGI_guNUarFft0aBa14>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 07:32:22 -0000

On Aug 1, 2017, at 02:45, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
>=20
>=20
> Carsten Bormann <cabo@tzi.org> wrote:
>>> So I wonder out loud: shouldn't all of the IANA registries have =
clear
>>> reference files that could be normatively referenced?
>=20
>> Try referencing, say, {{!IANA.cbor-tags}} =E2=80=94 it just works :-)
>=20
> wow. I'm sure it's documented in some place so obvious I can't see it.

https://xml2rfc.tools.ietf.org/ is the place that talks about bibxml8 =
references.
kramdown-rfc is just mapping all the IANA.* references to bibxml8, as in

=
https://xml2rfc.tools.ietf.org/public/rfc/bibxml8/reference.IANA.cbor-tags=
.xml

> Is the "cbor-tags" part the last part of the IANA registry URL?

Apparently.

bibxml8/index.cgi:

    if ($IANAref =3D~ m(^/?reference.IANA[.]([^/]+)[.](xml|kramdown)$)) =
{
	my $IANAref =3D $1;
=E2=80=A6
	    my $a =3D =
get("http://www.iana.org/assignments/$IANAref/=E2=80=9C);

kramdown-rfc is, somewhat ironically maybe, using the xml version then =
:-) (getting the kramdown [really: YAML] version isn't even implemented =
at xml2rfc.ietf.org, but there is no need to).

Gr=C3=BC=C3=9Fe, Carsten


From nobody Tue Aug  1 00:53:21 2017
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7287132ACF for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 00:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.4
X-Spam-Level: 
X-Spam-Status: No, score=-5.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1TT9x6NRsUw4 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 00:53:18 -0700 (PDT)
Received: from relais-inet.orange.com (mta136.mail.business.static.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4E4A132ACD for <ietf@ietf.org>; Tue,  1 Aug 2017 00:53:17 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id 292D4C017F; Tue,  1 Aug 2017 09:53:16 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.33]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id F3A6D4005B; Tue,  1 Aug 2017 09:53:15 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM42.corporate.adroot.infra.ftgroup ([fe80::d5fd:9c7d:2ee3:39d9%19]) with mapi id 14.03.0352.000; Tue, 1 Aug 2017 09:53:15 +0200
From: <mohamed.boucadair@orange.com>
To: Mark Andrews <marka@isc.org>, "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Index: AQHTCpbiJ1JDk1dTa0mNsjcn78Anz6JvG+kw
Date: Tue, 1 Aug 2017 07:53:15 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300A0156BD@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es> <787AE7BB302AE849A7480A190F8B93300A0155F5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es> <20170801072139.316A7809B357@rock.dv.isc.org>
In-Reply-To: <20170801072139.316A7809B357@rock.dv.isc.org>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DWfUFRQBRs2Ll7CBdEoq4166LEc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 07:53:20 -0000

SGkgTWFyaywgDQoNCkFuc3dlcmluZyB0aGlzIHBhcnRpY3VsYXIgcG9pbnQuIA0KDQpQbGVhc2Ug
c2VlIGlubGluZS4gDQoNCkNoZWVycywNCk1lZA0KDQo+IC0tLS0tTWVzc2FnZSBkJ29yaWdpbmUt
LS0tLQ0KPiBEZcKgOiBpZXRmIFttYWlsdG86aWV0Zi1ib3VuY2VzQGlldGYub3JnXSBEZSBsYSBw
YXJ0IGRlIE1hcmsgQW5kcmV3cw0KPiBFbnZvecOpwqA6IG1hcmRpIDEgYW/Du3QgMjAxNyAwOToy
Mg0KPiDDgMKgOiBqb3JkaS5wYWxldEBjb25zdWxpbnRlbC5lcw0KPiBDY8KgOiBpZXRmQGlldGYu
b3JnDQo+IE9iamV0wqA6IFJlOiBSRVNFTkRJTkcgLSBJbmNyZW1lbnRhbCBEZXBsb3ltZW50IG9m
IElQdjYtb25seSBXaS1GaSBmb3IgSUVURg0KPiBNZWV0aW5ncw0KPiANCj4gDQo+IEluIG1lc3Nh
Z2UgPDY1RDc5QUNCLTM3MkEtNDk3OC05MDMwLUZGQUI0OTY3QTJCREBjb25zdWxpbnRlbC5lcz4s
IEpPUkRJDQo+IFBBTEVUIE0NCj4gQVJUSU5FWiB3cml0ZXM6DQo+ID4gSGkgTWVkLA0KPiA+DQo+
ID4gSW4gbGluZSDigKYNCj4gPg0KPiA+IFNhbHVkb3MsDQo+ID4gSm9yZGkNCj4gPg0KPiA+DQo+
IA0KPiA+IEl0IGlzIGEgbWF0dGVyIG9mDQo+ID4gcHJlZmVyZW5jZSBvZiBvbmUgb3IgYW5vdGhl
ciB0cmFuc2l0aW9uIG1lY2hhbmlzbXMuIEFsbCB0aGVtIGhhdmUgZ29vZA0KPiA+IGFuZCBiYWQg
dGhpbmdzLiBJIHNlZSBtdWNoIHNpbXBsZXIgdGhlIGNvbWJpbmF0aW9uIG9mIE5BVDY0K0NMQVQg
dGhhbg0KPiA+IERTLUxpdGUgb3IgTUFQLCBpbiBhZGRpdGlvbiB0byB0aGUgT05MWSBzdXBwb3J0
IGluIGNlbGx1bGFyIG5ldHdvcmtzIGlzDQo+ID4gcHJlY2lzZWx5IE5BVDY0LzQ2NFhMQVQsIHdo
aWNoIG1lYW5zIGlzIHRoZSBNT1NUIGV4dGVuZGVkIHRyYW5zaXRpb24NCj4gPiBtZWNoYW5pc20g
YnkgbWlsbGlvbnMgKGJpbGxpb25zPykgb2YgdXNlcnMuIEl0IG1ha2VzIGEgbG90IG9mIHNlbnNl
IHRvDQo+IG1lDQo+ID4gdG8gZ28gaW4gYWxsIHRoZSBpbmZyYXN0cnVjdHVyZXMgdG8gdGhlIG9u
ZSB0aGF0IGhhcyBtb3JlIGRlcGxveW1lbnQNCj4gPiBhbHJlYWR5Lg0KPiANCj4gTm90IHJlYWxs
eS4gIENlbGx1bGFyIG5ldHdvcmtzIHdlbnQgd2l0aCBhbnl0aGluZyBhdmFpbGFibGUsIHJhdGhl
cg0KPiB0aGFuIHRoZSBiZXN0LiAgV2UgYXJlIGNvbnRpbnVpbmcgdGhlIHBheSB0aGUgcHJpY2Ug
Zm9yIHRoYXQuDQoNCltNZWRdIEFjdHVhbGx5LCBuby4gVGhlcmUgd2FzIGFuIElQdjYgU3R1ZHkg
SXRlbSB3aXRoaW4gM0dQUC4gQm90aCBEUy1MaXRlLCBBK1AsIGFuZCBOQVQ2NCB3ZXJlIHByZXNl
bnRlZCBhbmQgZG9jdW1lbnRlZCBpbiBhIDNHUFAgcmVwb3J0LiBGb3IgZXhhbXBsZSwgdGhpcyBp
cyB3aGF0IHdhcyBkb2N1bWVudGVkIGZvciBBK1A6DQoNCktub3duIGlzc3VlczoNCi0JVGhlIFVF
IG5lZWRzIHRvIGJlIG1vZGlmaWVkIHRvIHN1cHBvcnQgQStQIHNjaGVtZQ0KLQlUaGUgZ2F0ZXdh
eSBuZWVkcyB0byBmb3J3YXJkIG5vdCBvbmx5IGJhc2VkIG9uIElQIGFkZHJlc3MgYnV0IGJhc2Vk
IG9uIGFkZHJlc3MgcGx1cyBwb3J0LiBUaGUgbmV0d29yayBuZWVkcyB0byBpbXBsZW1lbnQgUFJS
IGluIHNpbWlsYXIgcGxhY2VzIGFzIENHTiBpbiB0aGUgRFMtTGl0ZSBhcHByb2FjaA0KLQlUaGUg
YmFja2VuZCBSQURJVVMgc3lzdGVtIG5lZWRzIHRvIGJlIGNoYW5nZWQgYXMgc3Vic2NyaWJlcnMg
Y2FuIG5vIGxvbmdlciBiZSBpZGVudGlmaWVkIGJ5IElQIGFkZHJlc3Mgb25seSwgYnV0IGJ5IElQ
IGFkZHJlc3MgYW5kIHBvcnQNCi0JSW4gdGhlIElQdjYgdHVubmVsbGluZyBhcHByb2FjaCBRb1Mg
ZGlmZmVyZW50aWF0aW9uIGJldHdlZW4gYmVhcmVycyBjYW5ub3QgYmUgcHJvdmlkZWQgZWFzaWx5
DQotCVRoZSBzb2x1dGlvbiB3b3JrcyBvbmx5IHdpdGggYXBwbGljYXRpb25zIHVzaW5nIHRyYW5z
cG9ydCBwcm90b2NvbHMsIHdoaWNoIGhhdmUgY29uY2VwdCBvZiBwb3J0IG51bWJlcnMgKHN1Y2gg
YXMgVURQIGFuZCBUQ1ApLiBUaGVyZSB3aWxsIGJlIGNoYWxsZW5nZXMgd2l0aCBwcm90b2NvbHMg
d2hpY2ggdXNlIHBsYWluIElQLg0KLQlUaGUgc29sdXRpb24gc2V0cyByZXN0cmljdGlvbnMgdG8g
YXBwbGljYXRpb25zIHdpdGhpbiBpbiB0aGUgVUUsIGFzIHRoZSBhbGxvY2F0aW9uIG9mIGZpeGVk
IHBvcnQgbnVtYmVycyBiZWNvbWVzIG1vcmUgY29tcGxpY2F0ZWQuDQotCUZvciBJQ01QIG1lc3Nh
Z2VzLCB0aGUgVUUgbXVzdCB1c2UgYW4gSUNNUCBxdWVyeSBpZGVudGlmaWVyIHdpdGhpbiB0aGUg
YWxsb2NhdGVkIHBvcnQgcmFuZ2UsIG90aGVyd2lzZSB0aGUgcmVzcG9uc2Ugd2lsbCBub3QgYmUg
cmVjZWl2ZWQgYnkgdGhpcyBVRS4NCg0KS25vd24gYmVuZWZpdHM6DQoNCi0JVGhlIFVFIGhhcyBh
Y2Nlc3MgdG8gcHVibGljIElQdjQgYWRkcmVzcywgd2hpY2ggc2ltcGxpZmllcyB0aGUgYmVoYXZp
b3VyIGZvciBQMlAgYXBwbGljYXRpb25zIHN1Y2ggYXMgVm9JUC4NCi0JQWxsb3dzIElQdjQgbGlm
ZXRpbWUgZXh0ZW5zaW9uIGlmIHVzZWQgd2l0aCBHVFAvR1JFLg0KLQlMZWdhbCByZXF1aXJlbWVu
dHMgZm9yIHRyYWNpbmcgd2hpY2ggdHJhZmZpYyBmbG93IHdhcyBvcmlnaW5hdGVkIGZyb20gd2hp
Y2ggVUUgaXMgc2ltcGxlciB0aGFuIGluIENHTiBzb2x1dGlvbnMsIGFzIHRoZSBvcGVyYXRvciBk
b2VzIG5vdCBuZWVkIHRvIHN0b3JlIGVhY2ggZmxvdyBidXQgb25seSBBK1AgYWxsb2NhdGlvbiBp
bmZvcm1hdGlvbi4NCi0JSW4gR1RQL0dSRS9EU01JUDYgYmFzZWQgc29sdXRpb25zIFFvUyBjYW4g
YmUgcHJvdmlkZWQuDQotCUErUCBhbGxvd3MgZm9yIGFuIGluY3JlbWVudGFsIG1pZ3JhdGlvbiB0
byBJUHY2LW9ubHkgbmV0d29yaw0KLQlBK1AgY2FuIGJlIGZ1bGx5IHN0YXRlbGVzcyB3aGVuIHVz
ZWQgdG9nZXRoZXIgd2l0aCBJUHY2DQotCU5vIHBlci1zdGF0ZSBzZXNzaW9ucyBhcmUgbWFpbnRh
aW5lZCBpbiB0aGUgUExNTiByZWFsbQ0KLQlVbmxpa2UgTkFUNDQvTkFUNjQsIG5vIGR5bmFtaWMg
c3RhdGUgc3luY2hyb25pemF0aW9uIGlzIHJlcXVpcmVkIHRvIGVuc3VyZSBzZXJ2aWNlIHJvYnVz
dG5lc3MNCi0JTm8gQUxHIGlzIHJlcXVpcmVkIHRvIGJlIGltcGxlbWVudGVkIGluIHRoZSBzZXJ2
aWNlL1BMTU4gcmVhbG0NCi0JTm8gZXh0cmEtY29zdCBvbiB0aGUgVUUgdG8gc3VwcG9ydCBOQVQg
dHJhdmVyc2FsIHRlY2huaXF1ZXMgaXMgcmVxdWlyZWQNCi0JVW5saWtlIGRvdWJsZSBOQVQgc29s
dXRpb25zLCBwZWVyLXRvLXBlZXIgc2VydmljZXMgY2FuIGJlIGRlbGl2ZXJlZCB3aXRoIG9uZSBl
eGNlcHRpb24gYXMgZG9jdW1lbnRlZCBpbiBbMjNdDQotCU5vIEtlZXAtYWxpdmUgbWVzc2FnZXMg
YXJlIHJlcXVpcmVkIHRvIG1haW50YWluIE5BVCBlbnRyaWVzLiBUaGlzIGNoYXJhY3RlcmlzdGlj
IG1pdGlnYXRlcyBiYXR0ZXJ5IGNvbnN1bXB0aW9uIGlzc3VlcyBpbmR1Y2VkIGJ5ICJBbHdheXMt
b24iIHNlcnZpY2VzLiBFc3BlY2lhbGx5LCB0aGUgdXNlIG9mIHNob3J0IGludGVydmFscyBiZXR3
ZWVuIGtlZXAtYWxpdmUgbWVzc2FnZXMgaGFzIGEgYmlnIGltcGFjdCBvbiB0aGUgYmF0dGVyeSBj
b25zdW1wdGlvbiAoU2VlIFsyNF0gZm9yIG1vcmUgZGV0YWlscyBhYm91dCBjb21wbGljYXRpb25z
IHRvIHR3ZWFrIFVEUCB0aW1lcnMgaW4gTkFUIGRldmljZXMgYW5kIGFsc28ga2VlcC1hbGl2ZSBp
bnRlcnZhbHMgdXNlZCBieSBVRSkuIE1vcmVvdmVyLCB0aGUgbmV0d29yayBsb2FkIGlzIG1vcmUg
b3B0aW1pemVkIHNpbmNlIHRoZSBsb2FkIGluZHVjZWQgYnkga2VlcC1hbGl2ZSBtZXNzYWdlcyBp
biB0aGUgY29udGV4dCBvZiBDR04gc29sdXRpb25zIGlzIGF2b2lkZWQuDQotCUxhdGVuY2llcyBh
bmQgcmVsYXRlZCBwcm9ibGVtcyBvZiBOQVRzIGFyZSBhdm9pZGVkLiANCg0KDQpBbmQgZm9yIE5B
VDY0Og0KDQo9PQ0KS25vd24gaXNzdWVzIG9mIHRoZSBzb2x1dGlvbjoNCg0KLQlUaGUgc2Vzc2lv
biBiaW5kaW5nIGJldHdlZW4gTVMvVUUgSVB2NiBhZGRyZXNzIGFuZCBwdWJsaWMgSVB2NCBhZGRy
ZXNzL3BvcnQgaXMgbm90IGtub3duIHRvIHRoZSBQQ0MgYXJjaGl0ZWN0dXJlLiBUaGVyZWZvcmUs
IGRlcGVuZGluZyBvbiBkZXBsb3ltZW50IGFuZCBpZiB0aGUgYXBwbGljYXRpb24gaXMgTkFUIGF3
YXJlIGFuZCBoYXMgYWNjZXNzIHRvIHRoZSBiaW5kaW5nIChhcyBlLmcuIGluIHRoZSBjYXNlIG9m
IElNUyksIHRoZXJlIG1heSBvciBtYXkgbm90IGJlIGlzc3VlcyB3aXRoIGFwcGx5aW5nIFBDQyB0
byB0aGUgc2Vzc2lvbi4NCi0JR2VuZXJhbCBOQVQgY29uY2VybnMsIG5vdCBzcGVjaWZpYyB0byAz
R1BQIG5ldHdvcmtzLCBhcHBseS4gRm9yIGV4YW1wbGUsIGFwcGxpY2F0aW9ucyB0aGF0IGVtYmVk
IElQIGFkZHJlc3NlcyBpbiB0aGUgcGF5bG9hZCBhbmQgYXJlIG5vdCBOQVQgYXdhcmUgcmVxdWly
ZSBhZGRpdGlvbmFsIGZ1bmN0aW9uYWxpdHkgdG8gd29yayBhY3Jvc3MgTkFUcy4NCi0JSW4gY2Fz
ZSBvZiByb2FtaW5nIHdpdGggTG9jYWwgQnJlYWtvdXQgKFBHVy9HR1NOIGluIFZQTE1OKSwgaWYg
dGhlcmUgaXMgYSBuZWVkIHRvIHJlYWNoIElQdjQtb25seSBzZXJ2aWNlcywgdGhlIFZQTE1OIG9w
ZXJhdG9yIHdvdWxkIGJlIHJlcXVpcmVkIHRvIGRlcGxveSBOQVQ2NC9ETlM2NCBpbiBvcmRlciB0
byBwcm92aWRlIHRoZSBzYW1lIHVzZXIgZXhwZXJpZW5jZSB1c2luZyBJUHY2LW9ubHkgY29ubmVj
dGlvbnMgZm9yIElQdjQtb25seSBzZXJ2aWNlcyBhcyBpbiBub24tcm9hbWluZyBzY2VuYXJpb3Mu
DQotCUl0IGlzIHVuY2xlYXIgaG93IElQdjQgbGl0ZXJhbHMgYXJlIHN1cHBvcnRlZC4NCg0KS25v
d24gYmVuZWZpdHMgb2YgdGhlIHNvbHV0aW9uDQoNCi0JVGhpcyBzb2x1dGlvbiByZXF1aXJlcyBu
byBjaGFuZ2VzIHRvIHRoZSBNUy9VRS4NCi0JVGhlIGV4aXN0aW5nIGJlYXJlciBhbmQgc2Vzc2lv
biBtYW5hZ2VtZW50IHByb2NlZHVyZXMgY2FuIGJlIHVzZWQgd2l0aG91dCBhbnkgY2hhbmdlLg0K
LQlUaGlzIHNvbHV0aW9uIGRvZXMgbm90IGludHJvZHVjZSBhbnkgYWRkaXRpb25hbCB0dW5uZWxs
aW5nIG92ZXJoZWFkIG9uIGFueSBpbnRlcmZhY2VzLg0KLQlUaGlzIHNvbHV0aW9uIGhhcyBubyBp
bXBhY3QgdG8gdGhlIDNHUFAgbmV0d29yayBhcmNoaXRlY3R1cmUsIG5vIG5ldyBpbnRlcmZhY2Ug
b3IgbmV0d29yayBlbGVtZW50IGlzIG5lZWRlZC4gVGhpcyBzb2x1dGlvbiBjYW4gYmUgZGVwbG95
ZWQgd2l0aG91dCBhbnkgYWRkaXRpb25hbCBub3JtYXRpdmUgc3BlY2lmaWNhdGlvbiB3aXRoaW4g
M0dQUC4gTGltaXRhdGlvbnMgZGVzY3JpYmVkIHVuZGVyICJrbm93biBpc3N1ZXMiIGFib3ZlIGFw
cGx5Lg0KLQlObyBjaGFuZ2VzIHRvIHRoZSBJUHY2IGFkZHJlc3MtYXNzaWdubWVudCBwcm9jZWR1
cmVzIHJlcXVpcmVkLg0KLQlObyBiZWFyaW5nIG9uIHRoZSB0eXBlIG9mIHRyYW5zcG9ydCBuZXR3
b3JrOiBUcmFuc3BvcnQgbmV0d29yayBjYW4gYmUgSVB2NCBvciBJUHY2Lg0KLQlOQVQ2NCBjYW4g
YmUgZWl0aGVyIGNvLWxvY2F0ZWQgb3Igc2VwYXJhdGUgZnJvbSBHR1NOL1BETi1HVy4NCi0JU29s
dXRpb24gdG8gdGhlIHB1YmxpYyBJUHY0IGFkZHJlc3MgZXhoYXVzdGlvbiBwcm9ibGVtIHRocm91
Z2ggdGhlIHVzZSBvZiBzdGF0ZWZ1bCBOQVQ2NC4NCi0JTm8gaW1wYWN0IG9uIFFvUy9iZWFyZXIg
cHJvY2VkdXJlcyBiZXR3ZWVuIFVFIGFuZCBQRE4gR1cvUyBHVy4NCj09PQ0KDQoNCg==


From nobody Tue Aug  1 01:18:35 2017
Return-Path: <jonathan.hardwick@metaswitch.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 555DD132B8C; Tue,  1 Aug 2017 01:18:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jonathan Hardwick <jonathan.hardwick@metaswitch.com>
To: <rtg-dir@ietf.org>
Cc: i2rs@ietf.org, ietf@ietf.org, draft-ietf-i2rs-rib-info-model.all@ietf.org
Subject: Rtgdir early review of draft-ietf-i2rs-rib-info-model-11
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150157551332.9546.17310175858783211646@ietfa.amsl.com>
Date: Tue, 01 Aug 2017 01:18:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XJcBVvHKydzdm36qhOZQcCiZKns>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 08:18:33 -0000

Reviewer: Henning Rogge
Review result: Has Nits

Submitting on behalf of Henning Rogge:

Hi,

I was asked to do an early review of the i2rs-rib-info-model...

I liked the comprehensive approach describing the RIB, including tunnels,
multi-topology routing (by using multiple RIBs) and routing reactions (like
drop/icmp-error).

I found a few things in the draft that in my opinion need a bit more work...

First it seems that Section 2.3 (Route) is a bit out of sync with the BNF later
in the document, it should at least mention matching the source-IP address of
the IP headers.

Second (if I read the BNF in Section 6 correctly), the match for a route seems
to be one of the list "ip address, MPLS label, MAC address, interface". I think
it should be possible to combine "interface" or "mac address" with an IP
address to restrict the focus of a route, e.g. "match fe80::1 from interface X".

Last, I wonder if multicast routing needs more different types of matchers,
e.g. a match on the TTL of the IP packet to limit the range of a multicast
group.

There is also problem of multicast routing in MANETs (see RFC 6621) which can
use a hash-based duplicate detection to determine if it forwards or drops a
multicast packet. Would this be out of scope for the draft?

Henning Rogge



From nobody Tue Aug  1 02:15:19 2017
Return-Path: <nick@foobar.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F141F132C7F for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 02:15:17 -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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8NYG1ARuB-KM for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 02:15:16 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B81B132C8D for <ietf@ietf.org>; Tue,  1 Aug 2017 02:15:15 -0700 (PDT)
X-Envelope-To: ietf@ietf.org
Received: from cupcake.local (089-101-195156.ntlworld.ie [89.101.195.156] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id v719F9c9054875 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Aug 2017 10:15:09 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-195156.ntlworld.ie [89.101.195.156] (may be forged) claimed to be cupcake.local
Message-ID: <5980469E.80305@foobar.org>
Date: Tue, 01 Aug 2017 10:15:10 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.16 (Macintosh/20170718)
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
CC: jordi.palet@consulintel.es, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es> <787AE7BB302AE849A7480A190F8B93300A0155F5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es> <20170801072139.316A7809B357@rock.dv.isc.org>
In-Reply-To: <20170801072139.316A7809B357@rock.dv.isc.org>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FRZMirR3sbvRyVhkY0TdJhumsRc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 09:15:18 -0000

Mark Andrews wrote:
> People ask for lots of things and even write code.  That doesn't mean
> that the thing they ask for is actually good or there is not something
> better.  This IETF should be recommending what is actually best.

"actually best"?

What a curious idea.

Nick


From nobody Tue Aug  1 02:56:33 2017
Return-Path: <prvs=13860e1204=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD738131FE8 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 02:56:31 -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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8XTWCIft3J1h for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 02:56:29 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B4B2131F5C for <ietf@ietf.org>; Tue,  1 Aug 2017 02:56:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1501581385; x=1502186185; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=DMq9evHSF6hc4HvyMP50/sOvw 9yFrec9wfHKkckkxxw=; b=uDvczLG3KUY0Auedwo4E7yPzqQiY5dSRnLepFQ2Il 7rNlyjm/4ofALrdTHLtSAsF5zW+6lpwQWyhQFMPgz2vNrnGSVxj/mety9Fqifixf JQlhV406HVnnCYibwNZpSP3UUxlApd01E46U8GOypXxkM3gSxQV+Qjpm3xW2IyiQ ZQ=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=tOo1wB4SFK/r991brgMei1x+AXqnBdjwykFLovx/mZ3Up4nHx8UAh+9CRG0r 5xXOLFktwihcMo5y2lq3D/uwEsuhcOHA01bFNQAkKge9886VSeHAQ1BUu YMr5STnJ3jOxRg7j1UuDBAcTxdjVLtEzibxOq9ZuhslD9NthgmjKyo=;
X-MDAV-Processed: mail.consulintel.es, Tue, 01 Aug 2017 11:56:25 +0200
X-Spam-Processed: mail.consulintel.es, Tue, 01 Aug 2017 11:56:24 +0200
Received: from [10.10.10.133] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005491921.msg for <ietf@ietf.org>; Tue, 01 Aug 2017 11:56:23 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170801:md50005491921::1Wnc1T/ZQdAyuLUX:00001z3O
X-Return-Path: prvs=13860e1204=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.24.1.170721
Date: Tue, 01 Aug 2017 11:56:20 +0200
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <E3AEEAB4-FBFF-4824-8B6C-4FD9B3BA4722@consulintel.es>
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es> <787AE7BB302AE849A7480A190F8B93300A0155F5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es> <20170801072139.316A7809B357@rock.dv.isc.org> <787AE7BB302AE849A7480A190F8B93300A0156BD@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93300A0156BD@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BV40MxhWBl29ipWgYu8ACE8Biz8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 09:56:32 -0000

And in general, many of those considerations from 3GPP are equivalent in wi=
reline networks (except for specific 3G items, of course).

And the NAT64 issue:

- General NAT concerns, not specific to 3GPP networks, apply. For example, =
applications that embed IP addresses in the payload and are not NAT aware r=
equire additional functionality to work across NATs.

Is precisely what CLAT (464XLAT) is resolving.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de <mohamed.boucadair@orange.com=
>
Responder a: <mohamed.boucadair@orange.com>
Fecha: martes, 1 de agosto de 2017, 9:53
Para: Mark Andrews <marka@isc.org>, "jordi.palet@consulintel.es" <jordi.pal=
et@consulintel.es>
CC: "ietf@ietf.org" <ietf@ietf.org>
Asunto: RE: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF =
Meetings

    Hi Mark,=20
   =20
    Answering this particular point.=20
   =20
    Please see inline.=20
   =20
    Cheers,
    Med
   =20
    > -----Message d'origine-----
    > De : ietf [mailto:ietf-bounces@ietf.org] De la part de Mark Andrews
    > Envoy=C3=A9 : mardi 1 ao=C3=BBt 2017 09:22
    > =C3=80 : jordi.palet@consulintel.es
    > Cc : ietf@ietf.org
    > Objet : Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for=
 IETF
    > Meetings
    >=20
    >=20
    > In message <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es>, JOR=
DI
    > PALET M
    > ARTINEZ writes:
    > > Hi Med,
    > >
    > > In line =E2=80=A6
    > >
    > > Saludos,
    > > Jordi
    > >
    > >
    >=20
    > > It is a matter of
    > > preference of one or another transition mechanisms. All them have g=
ood
    > > and bad things. I see much simpler the combination of NAT64+CLAT th=
an
    > > DS-Lite or MAP, in addition to the ONLY support in cellular network=
s is
    > > precisely NAT64/464XLAT, which means is the MOST extended transitio=
n
    > > mechanism by millions (billions?) of users. It makes a lot of sense=
 to
    > me
    > > to go in all the infrastructures to the one that has more deploymen=
t
    > > already.
    >=20
    > Not really.  Cellular networks went with anything available, rather
    > than the best.  We are continuing the pay the price for that.
   =20
    [Med] Actually, no. There was an IPv6 Study Item within 3GPP. Both DS-L=
ite, A+P, and NAT64 were presented and documented in a 3GPP report. For exa=
mple, this is what was documented for A+P:
   =20
    Known issues:
    -	The UE needs to be modified to support A+P scheme
    -	The gateway needs to forward not only based on IP address but based o=
n address plus port. The network needs to implement PRR in similar places a=
s CGN in the DS-Lite approach
    -	The backend RADIUS system needs to be changed as subscribers can no l=
onger be identified by IP address only, but by IP address and port
    -	In the IPv6 tunnelling approach QoS differentiation between bearers c=
annot be provided easily
    -	The solution works only with applications using transport protocols, =
which have concept of port numbers (such as UDP and TCP). There will be cha=
llenges with protocols which use plain IP.
    -	The solution sets restrictions to applications within in the UE, as t=
he allocation of fixed port numbers becomes more complicated.
    -	For ICMP messages, the UE must use an ICMP query identifier within th=
e allocated port range, otherwise the response will not be received by this=
 UE.
   =20
    Known benefits:
   =20
    -	The UE has access to public IPv4 address, which simplifies the behavi=
our for P2P applications such as VoIP.
    -	Allows IPv4 lifetime extension if used with GTP/GRE.
    -	Legal requirements for tracing which traffic flow was originated from=
 which UE is simpler than in CGN solutions, as the operator does not need t=
o store each flow but only A+P allocation information.
    -	In GTP/GRE/DSMIP6 based solutions QoS can be provided.
    -	A+P allows for an incremental migration to IPv6-only network
    -	A+P can be fully stateless when used together with IPv6
    -	No per-state sessions are maintained in the PLMN realm
    -	Unlike NAT44/NAT64, no dynamic state synchronization is required to e=
nsure service robustness
    -	No ALG is required to be implemented in the service/PLMN realm
    -	No extra-cost on the UE to support NAT traversal techniques is requir=
ed
    -	Unlike double NAT solutions, peer-to-peer services can be delivered w=
ith one exception as documented in [23]
    -	No Keep-alive messages are required to maintain NAT entries. This cha=
racteristic mitigates battery consumption issues induced by "Always-on" ser=
vices. Especially, the use of short intervals between keep-alive messages h=
as a big impact on the battery consumption (See [24] for more details about=
 complications to tweak UDP timers in NAT devices and also keep-alive inter=
vals used by UE). Moreover, the network load is more optimized since the lo=
ad induced by keep-alive messages in the context of CGN solutions is avoide=
d.
    -	Latencies and related problems of NATs are avoided.=20
   =20
   =20
    And for NAT64:
   =20
    =3D=3D
    Known issues of the solution:
   =20
    -	The session binding between MS/UE IPv6 address and public IPv4 addres=
s/port is not known to the PCC architecture. Therefore, depending on deploy=
ment and if the application is NAT aware and has access to the binding (as =
e.g. in the case of IMS), there may or may not be issues with applying PCC =
to the session.
    -	General NAT concerns, not specific to 3GPP networks, apply. For examp=
le, applications that embed IP addresses in the payload and are not NAT awa=
re require additional functionality to work across NATs.
    -	In case of roaming with Local Breakout (PGW/GGSN in VPLMN), if there =
is a need to reach IPv4-only services, the VPLMN operator would be required=
 to deploy NAT64/DNS64 in order to provide the same user experience using I=
Pv6-only connections for IPv4-only services as in non-roaming scenarios.
    -	It is unclear how IPv4 literals are supported.
   =20
    Known benefits of the solution
   =20
    -	This solution requires no changes to the MS/UE.
    -	The existing bearer and session management procedures can be used wit=
hout any change.
    -	This solution does not introduce any additional tunnelling overhead o=
n any interfaces.
    -	This solution has no impact to the 3GPP network architecture, no new =
interface or network element is needed. This solution can be deployed witho=
ut any additional normative specification within 3GPP. Limitations describe=
d under "known issues" above apply.
    -	No changes to the IPv6 address-assignment procedures required.
    -	No bearing on the type of transport network: Transport network can be=
 IPv4 or IPv6.
    -	NAT64 can be either co-located or separate from GGSN/PDN-GW.
    -	Solution to the public IPv4 address exhaustion problem through the us=
e of stateful NAT64.
    -	No impact on QoS/bearer procedures between UE and PDN GW/S GW.
    =3D=3D=3D
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Tue Aug  1 03:09:14 2017
Return-Path: <prvs=13860e1204=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F177B132031 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 03:09: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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pEkPp9ABwnOJ for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 03:09:09 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E9F313202C for <ietf@ietf.org>; Tue,  1 Aug 2017 03:09:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1501582147; x=1502186947; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=0K1cShmgfBqSTgVs8I3f7xLRg oaadM/V5zEWR3s5jow=; b=pn+hkqv9foRf8hRtd1pkCRitwyh4pD14MaJ93JHJc BVs8oTZ0puBacTXrZqcSbf2g85uPi2ylv8l/Utn553OqEjk7Tv4mEArunfCdtkgD E+6xPJ/Ysp7zfhyi+ZaqCGgE1yUpAaEGm+sQ3nTQKSt2yi7jBbTaX0nssYoht5Y/ 5A=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=PcXZnhf1Bz3pJKoTzY/CRwTUoNliH1l3O2FrMhhVIsMEem5Wh8tRt6/uhMUL TazURXV2GobFMng2y04IHo62fSEAUnR4LSbYzaVKThviLUqTuH6dAL2Nr CT7yzqD5SHK7aLVZ6VJdVEjenQkhnYrJcZsbLTpecPBkXo9v5FrmJA=;
X-MDAV-Processed: mail.consulintel.es, Tue, 01 Aug 2017 12:09:07 +0200
X-Spam-Processed: mail.consulintel.es, Tue, 01 Aug 2017 12:09:05 +0200
Received: from [10.10.10.133] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005491930.msg for <ietf@ietf.org>; Tue, 01 Aug 2017 12:09:05 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170801:md50005491930::Y3C+CRaRiSmh3rFq:00007uOO
X-Return-Path: prvs=13860e1204=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.24.1.170721
Date: Tue, 01 Aug 2017 12:09:02 +0200
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <57AD9D55-FBFD-4B5E-ABC9-90509B228978@consulintel.es>
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es> <787AE7BB302AE849A7480A190F8B93300A0155F5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es> <20170801072139.316A7809B357@rock.dv.isc.org>
In-Reply-To: <20170801072139.316A7809B357@rock.dv.isc.org>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dRMai9i-mVhg-q2JGetM-1NYPR8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 10:09:12 -0000

Fully agree with you in one specific point:

If we try NAT64, we should also try DS-Lite, MAP-T, MAP-E, lw4o6, 464XLAT, =
and all the others =E2=80=A6

We all agree with that? NOC guys will love us! Irony mode off/

Precisely my point is to use what is =E2=80=9Cbest=E2=80=9D in =E2=80=9Cmos=
t=E2=80=9D of the situations.

CLAT is the ONLY one that works in mobile networks. Works also in wireline.=
 Is no breaking apps and devices that user literals or don't use APIs.

Today hosts (laptops, tablets, smartphones), some times are used in wirelin=
e (or WiFi) networks, sometimes are used in cellular network (either direct=
ly attached if they have a 3G/LTE interface or with tethering). SO, it make=
s a lot of sense that all hosts have CLAT support (and Windows 10 has inclu=
ded it in the last update), it is a very lightweight daemon, is not somethi=
ng complex at all.

If we have it also in CPEs, then we are covering all the possible scenarios=
 also for old devices apps or desktop computers in those LANs.

I think it makes a lot of sense and it is the =E2=80=9Cbest=E2=80=9D balanc=
ed solution, which is what you are suggesting, right?

Regards,
Jordi
=20

-----Mensaje original-----
De: Mark Andrews <marka@isc.org>
Responder a: <marka@isc.org>
Fecha: martes, 1 de agosto de 2017, 9:21
Para: <jordi.palet@consulintel.es>
CC: "ietf@ietf.org" <ietf@ietf.org>
Asunto: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF =
Meetings

   =20
    In message <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es>, JORDI=
 PALET M
    ARTINEZ writes:
    > Hi Med,
    >
    > In line =C3=A2=E2=80=A2=C5=93
    >
    > Saludos,
    > Jordi
    >
    >
    > -----Mensaje original-----
    > De: ietf <ietf-bounces@ietf.org> en nombre de
    > <mohamed.boucadair@orange.com>
    > Responder a: <mohamed.boucadair@orange.com>
    > Fecha: martes, 1 de agosto de 2017, 8:07
    > Para: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>,
    > "ietf@ietf.org" <ietf@ietf.org>
    > Asunto: RE: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for
    > IETF Meetings
    >
    >     Hi Jordi,
    >
    >     Please see inline.
    >
    >     Cheers,
    >     Med
    >
    >     > -----Message d'origine-----
    >     > De : ietf [mailto:ietf-bounces@ietf.org] De la part de JORDI PA=
LET
    >     > MARTINEZ
    >     > Envoy=C3=83=C2=A9 : lundi 31 juillet 2017 23:18
    >     > =C3=83=E2=80=A2 : ietf@ietf.org
    >     > Objet : Re: RESENDING - Incremental Deployment of IPv6-only Wi-=
Fi
    >     > for IETF Meetings
    >     >
    >     > NAT64 was invented for a specific case (when apps use DNS and t=
he
    >     > right APIs).
    >
    >     [Med] This may be misinterpreted as there is a dependency of NAT6=
4 on
    > DNS. This is not technically true. This was clarified in
    > https://tools.ietf.org/html/rfc6889
    >
    > [Jordi] Right, I was not pretending to be technically perfect, but
    > introducing when NAT64 fails in our network.
    >
    >        This approach is pragmatic in the sense that there is no depen=
dency
    >        on DNS implementation for the successful NAT handling.  As lon=
g as
    >        there is a function (e.g., DNS64 [RFC6147] or other means) tha=
t can
    >        construct an IPv6-embedded IPv4 address with a pre-configured =
IPv6
    >        prefix, an IPv4 address and a suffix (refer to [RFC6052]), NAT=
64
    >	 will work just fine.
    >
    >     FWIW, there are even NAT64 deployments that do not even rely on
    > DNS64.
    >
    > [Jordi] Agree, we can talk about =C3=A2=E2=80=A2=CB=9BDNS64 function=
=C3=A2=E2=80=A2=CB=87 instead of DNS64.
    > Again, in our IETF network there is a DNS64, so not the issue here.
    >
    >     >
    >     > We realized then that app/devices vendors are lazy, or just the=
y
    >     > are out of the market, so we invented 464XLAT, which uses the s=
ame
    >     > concept as
    >     > NAT64/DNS64, but improves it by using the CLAT, a small daemon =
code
    >     > in the
    >     > OS or the CPE to solve the problems of the literal addresses an=
d
    >     > non-APIs
    >     > apps/devices.
    >     >
    >     > We don=C3=A2=E2=80=A2=CB=99t need to tell the customers to disa=
ble IPv4 in their LANs,
    >     > we need
    >     > to make sure that we deploy CPEs that support CLAT.
    >
    >     [Med] Is there any CPE-based 464xlat deployment out there?
    >
    > [Jordi] I=C3=A2=E2=80=A2=CB=99ve identified 4 vendors up to now, with=
 different products
    > each. I=C3=A2=E2=80=A2=CB=99m sure there are more. I also know that o=
ther vendors did the
    > development for specific customers and I=C3=A2=E2=80=A2=CB=99m also a=
ware of other customers
    > that asked for it. We have also the open source implementations, such=
 as
    > OpenWRT, supporting thousands of devices. Precisely this is my point.=
 As
    > IETF, our work is not just inventing transitions mechanism, but also
    > making sure that if we state a set of requirements for CPEs, we inclu=
de
    > the support for those transition mechanisms.
   =20
    People ask for lots of things and even write code.  That doesn't mean
    that the thing they ask for is actually good or there is not something
    better.  This IETF should be recommending what is actually best.
   =20
   =20
    >     > This way, users don=C3=A2=E2=80=A2=CB=99t
    >     > need to throw away old devices or apps, neither learn anything
    >     > about IPv4
    >     > or IPv6, and everybody is happy.
    >     >
    >     > We are trying to solve a problem with NAT64 which we knew
    >     > since it was invented that it can=C3=A2=E2=80=A2=CB=99t be solv=
ed. We don=C3=A2=E2=80=A2=CB=99t have
    >     > the time (unless some magic is discovered) to now tell every
    >     > ISP that is deploying IPv6 and NAT64, to instead of NAT64
    >     > have something different.
    >
    >     [Med] These operators (with CPEs) are already doing something
    > *different*: DS-Lite and the like. NAT64 is widely deployed in cellul=
ar
    > networks (host-based model), which is really straightforward.
    >
    > [Jordi] I agree, but if you have a network with cellular and wireline
    > access, you may want to have a single transition mechanisms instead o=
f
    > two. If we don=C3=A2=E2=80=A2=CB=99t want to use NAT64 in wireline, t=
hen why we are trying to
    > push it as the default SSID in our IETF network?
   =20
    Because that's what everyone TALKS about.  NAT64 was sexy.
   =20
    If we were being honest with ourselves we would do NAT64, then
    DS-Lite, then MAP at consecutive IETFs and release a recommendation
    for wireline deployments based off the experience or at least a
    report on the issues found.
   =20
    > It is a matter of
    > preference of one or another transition mechanisms. All them have goo=
d
    > and bad things. I see much simpler the combination of NAT64+CLAT than
    > DS-Lite or MAP, in addition to the ONLY support in cellular networks =
is
    > precisely NAT64/464XLAT, which means is the MOST extended transition
    > mechanism by millions (billions?) of users. It makes a lot of sense t=
o me
    > to go in all the infrastructures to the one that has more deployment
    > already.
   =20
    Not really.  Cellular networks went with anything available, rather
    than the best.  We are continuing the pay the price for that.
   =20
    >     > The solution is
    >     > there, if CPE vendors implement it, and we are talking about an
    >     > available
    >     > open source code (several implementations) that take a few byte=
s.
    >     >
    >     > We are already doing this effort in v6ops, I started trying to =
tell
    >     > the RFC7084 about the need to update it, but didn=C3=A2=E2=80=
=A2=CB=99t succeeded. It
    >     > seems that now we may want to have instead of a CPE requirement=
s
    >     > including this, an additional document to be a must for CPE ven=
dors
    >     > to support it, in case the CPE expects =C3=A2=E2=80=A2=CB=9BIPv=
4 old devices and apps=C3=A2=E2=80=A2=CB=87
    >     > in the LANs (which is real world life, and will be for 3-5 year=
s).
    >
    >     [Med] I'm afraid we don't need it. The IETF already specified too=
ls
    > to address that case (DS-Lite, MAP-E).
    >
    > [Jordi] I guess no need to repeat myself =C3=A2=E2=80=A2=C5=93
    >
    >
    >     >
    >     > Regards,
    >     > Jordi
    >     >
    >     >
    >     > -----Mensaje original-----
    >     > De: ietf <ietf-bounces@ietf.org> en nombre de Ole Jacobsen
    >     > <olejacobsen@me.com>
    >     > Responder a: Ole Jacobsen <olejacobsen@me.com>
    >     > Fecha: lunes, 31 de julio de 2017, 23:01
    >     > Para: Ted Lemon <mellon@fugue.com>
    >     > CC: <ietf@ietf.org>
    >     > Asunto: Re: RESENDING - Incremental Deployment of IPv6-only Wi-=
Fi
    > for IETF
    >     > Meetings
    >     >
    >     >
    >     >     You said:
    >     >     >
    >     >     > Brian, why on earth would we want to advertise IPv6 to IE=
TF
    >     >     > attendees?  We invented IPv6.  If we really can't run a
    > v6-only
    >     >     > network at IETF, what that says is that we have failed
    > utterly and
    >     >     > expensively.  I do not believe that this is correct: IPv6
    > works very
    >     >     > well.
    >     >
    >     >     Putting on my naive end-user hat:
    >     >
    >     >     That might be true, but here is the thing: "The mission of =
the
    > IETF is
    >     >     to make the INTERNET work better..." (my emphasis)
    >     >
    >     >     For at least a decade now, I've been told that I should "ju=
st
    > use
    >     >     IPv6" and some conferences have even "forced" me to do so.
    >     >
    >     >     I always respond with this question: "Does running IPv6 all=
ow
    > me to
    >     >     connect to the Internet?" (meaning the v4 Internet for the =
most
    > part).
    >     >     The answer always seems to be: "Yes, but you have to manual=
ly
    >     >     configure this and, oh by the way, this won't work at all a=
nd
    > that app
    >     >     might not behave as expected."
    >     >
    >     >     Demonstrating this to people who are experts seems like a w=
aste
    >     >     of time.
    >     >
    >     >     So it sounds to me like we HAVE indeed failed utterly and
    > expensively.
    >     >     99% of Internet users do not have any idea what version of =
IP
    > they are
    >     >     running just as they have no idea what a MAC address is or
    > why/if they
    >     >     should care.
    >     >
    >     >     I'd love to see IPv6 succeed, but it is apparently impossib=
le
    > to do so
    >     >     without teaching end-users a lot of stuff they really have =
no
    > interest
    >     >     in or ability to learn. What a shame.
    >     >
    >     >     Ole
    >     >
    >     >
    >     >
    >     >
    >     >
    >     > **********************************************
    >     > IPv4 is over
    >     > Are you ready for the new Internet ?
    >     > http://www.consulintel.es
    >     > The IPv6 Company
    >     >
    >     > This electronic message contains information which may be
    > privileged or
    >     > confidential. The information is intended to be for the use of =
the
    >     > individual(s) named above. If you are not the intended recipien=
t be
    > aware
    >     > that any disclosure, copying, distribution or use of the conten=
ts
    > of this
    >     > information, including attached files, is prohibited.
    >     >
    >     >
    >
    >
    >
    >
    >
    > **********************************************
    > IPv4 is over
    > Are you ready for the new Internet ?
    > http://www.consulintel.es
    > The IPv6 Company
    >
    > This electronic message contains information which may be privileged =
or
    > confidential. The information is intended to be for the use of the
    > individual(s) named above. If you are not the intended recipient be a=
ware
    > that any disclosure, copying, distribution or use of the contents of =
this
    > information, including attached files, is prohibited.
    >
    >
    >
   =20
    --=20
    Mark Andrews, ISC
    1 Seymour St., Dundas Valley, NSW 2117, Australia
    PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Tue Aug  1 03:34:11 2017
Return-Path: <pch-b7900FA3D@u-1.phicoh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02CCA131FFE for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 03:34:10 -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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w9BMa4brfhHI for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 03:34:08 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id E88B3131FFC for <ietf@ietf.org>; Tue,  1 Aug 2017 03:34:07 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #130) id m1dcUV1-0000FGC; Tue, 1 Aug 2017 12:34:03 +0200
Message-Id: <m1dcUV1-0000FGC@stereo.hq.phicoh.net>
To: ietf@ietf.org
Cc: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings 
From: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Sender: pch-b7900FA3D@u-1.phicoh.com
In-reply-to: Your message of "Tue, 01 Aug 2017 11:56:20 +0200 ." <E3AEEAB4-FBFF-4824-8B6C-4FD9B3BA4722@consulintel.es> 
Date: Tue, 01 Aug 2017 12:34:02 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0C0zoTdh2B1DNqhRijhoThWuXpU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 10:34:10 -0000

>Is precisely what CLAT (464XLAT) is resolving.

So we have a standard way of delivering IPv4 over wifi. It actually works.
It is used by billions of people every day without even thinking about it.
By all measures a great success.

We also have a way of delivering IPv6 over wifi. In typical IETF fashion 
we try to break that as much as possible. But it can be made to work.

So obviously this is way too boring. We have both IPv4 and IPv6 that work.
We need to do something, anything.

So NAT64 enters the stage. At first NAT64 was used to solve a problem in
the mobile networks where you cannot have dual stack for reasons only telco's 
understand.

But now we can use that same technology to spice up the wifi landscape a bit
more.

First we confusingly call it 'IPv6-only'. There is nothing IPv6-only about
NAT64. It is a technology specifically designed to provide access to the
IPv4 world.

Then, because of the fancy name 'IPv6-only' we claim it is the future. No
need to justify why modifying all hosts and making the whole system more
complex would be a reasonable future.

We have something that works today. We have plenty of experience delivering
what works today. No need to push overly complex technologies that offer
nothing more than a fancy name. That's not engineering, that's a hobby.




From nobody Tue Aug  1 03:39:48 2017
Return-Path: <prvs=13860e1204=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AA8E13209E for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 03:39: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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b3rSzXW8376E for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 03:39:45 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E7B3132064 for <ietf@ietf.org>; Tue,  1 Aug 2017 03:39:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1501583983; x=1502188783; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=2U+gj3EXqBVadyXnKuL92WKA0 58nFCJN5ebnhkvq5sA=; b=Xz6xRS4QlcJagguSgHKgJhWlBB6CjxFQD5tpN5yki gHRF503VlLE1NbWYRMSaoL3piCa+NMTZWYQaG4zlEFiqCH5rEXci38BHW30Opvb1 5+cRHaN/ihD+ww1ys0OFA2Tk/posbSpha34qa28St3T6kUhX2r5JIY4Ciioy3Z86 g0=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=J6TbUx8fFN/NqQKR+MdCA2ag3zNQjnWMExcefo+Kmhpu3TYK6NNmWPvJiQJX RJlFU0PUeqmNmja3WFNIbAcgma6w7cu4yNfxnzoL1M79wZQRY9FcvUoGE A383LcbxwVTg8VFDhUOrCK/aJixj0RHvsP9pdnzZCMyCpMS6oGQg2o=;
X-MDAV-Processed: mail.consulintel.es, Tue, 01 Aug 2017 12:39:43 +0200
X-Spam-Processed: mail.consulintel.es, Tue, 01 Aug 2017 12:39:42 +0200
Received: from [10.10.10.133] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005491961.msg for <ietf@ietf.org>; Tue, 01 Aug 2017 12:39:42 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170801:md50005491961::GL9QtalyQU+WxBRb:00001fqT
X-Return-Path: prvs=13860e1204=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.24.1.170721
Date: Tue, 01 Aug 2017 12:39:40 +0200
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <2322AE99-0425-4811-93D1-3EAD78488A08@consulintel.es>
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
References: <E3AEEAB4-FBFF-4824-8B6C-4FD9B3BA4722@consulintel.es> <m1dcUV1-0000FGC@stereo.hq.phicoh.net>
In-Reply-To: <m1dcUV1-0000FGC@stereo.hq.phicoh.net>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qJ84Tofwic-c3cH_47CNXykgVqg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 10:39:47 -0000

Just small clarifications in-line.

Saludos,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Philip Homburg <pch-ietf-6@u-=
1.phicoh.com>
Responder a: <pch-ietf-6@u-1.phicoh.com>
Fecha: martes, 1 de agosto de 2017, 12:34
Para: <ietf@ietf.org>
CC: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Asunto: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF =
Meetings

    >Is precisely what CLAT (464XLAT) is resolving.
   =20
    So we have a standard way of delivering IPv4 over wifi. It actually wor=
ks.
    It is used by billions of people every day without even thinking about =
it.
    By all measures a great success.
   =20
    We also have a way of delivering IPv6 over wifi. In typical IETF fashio=
n=20
    we try to break that as much as possible. But it can be made to work.
   =20
    So obviously this is way too boring. We have both IPv4 and IPv6 that wo=
rk.
    We need to do something, anything.
   =20
    So NAT64 enters the stage. At first NAT64 was used to solve a problem i=
n
    the mobile networks where you cannot have dual stack for reasons only t=
elco's=20
    understand.

[Jordi] Because we don=E2=80=99t have any more IPv4 public addresses, and w=
e know that for some time, we will need to access still some old =E2=80=9CI=
Pv6-only=E2=80=9D resources? Sharing IPv4 addresses by means of NAT64 is on=
e solution to that.
   =20
    But now we can use that same technology to spice up the wifi landscape =
a bit
    more.
   =20
    First we confusingly call it 'IPv6-only'. There is nothing IPv6-only ab=
out
    NAT64. It is a technology specifically designed to provide access to th=
e
    IPv4 world.
   =20
    Then, because of the fancy name 'IPv6-only' we claim it is the future. =
No
    need to justify why modifying all hosts and making the whole system mor=
e
    complex would be a reasonable future.

[Jordi] Agree, see: https://tools.ietf.org/html/draft-palet-ietf-v6ops-ipv6=
-only-00
   =20
    We have something that works today. We have plenty of experience delive=
ring
    what works today. No need to push overly complex technologies that offe=
r
    nothing more than a fancy name. That's not engineering, that's a hobby.
   =20
[Jordi] We need to move to IPv6-only =E2=80=9Call=E2=80=9D, there is an int=
ermediate step, for =E2=80=9Csome=E2=80=9D (crystal ball) years, which is I=
Pv6-only-WAN, but dual-stack in the LAN. NAT64+CLAT provides it seamless ac=
ross both wireline, WiFi and cellular networks.
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Tue Aug  1 04:41:18 2017
Return-Path: <logan@hackers.mu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3EC11320DE for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 04:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.2
X-Spam-Level: 
X-Spam-Status: No, score=-1.2 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hackers-mu.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ass5AXMKePvF for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 04:41:15 -0700 (PDT)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 647F5131EBC for <ietf@ietf.org>; Tue,  1 Aug 2017 04:41:15 -0700 (PDT)
Received: by mail-oi0-x235.google.com with SMTP id d71so7599773oih.0 for <ietf@ietf.org>; Tue, 01 Aug 2017 04:41:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hackers-mu.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=dq0ZgQW82qxZjOeoR6cG148CDc09zMINtmALvttf4Ds=; b=rteZwa8dHCgWMopLfD0tHwk/zhfAwEL6RhO7brQMNMn4Zkps5oQj3IyvA0GADnLNy2 NngXgXqfBRozB9WkPFgfSPD1edd6ILa7R46l73Jssv/mNHPDu9TnRQUJSqQuTVsUlHQ2 ODsibhvr5NfMhRod5VM8jgJ852xuIhevS4VeozHlT6tK5kt74srrOXCaYpgYBkyoK2QS 8IQR3hH0Km0Xx6m7ikSHzD8c/sroPqHpSJQvdWbrmb8/RNzYyPS3XFa3SSJXpfcKVVaF m4+AMxGdzUAS7+7teDW9LdRksSzDmCiuncK/rde0xHkh6GWfuvpUbNnfLOSoyAf5KfFa hloA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=dq0ZgQW82qxZjOeoR6cG148CDc09zMINtmALvttf4Ds=; b=GZqzrtjyHJoC/m7MNSE4WTM3vP7TaDePkWCYddgS950ObcjWVMiaHhLJLUwY1UupBp gDRc0/eIzulw4gpT4GnB43XN/nxJYsk2EyFh/WU/FyZm4pl7qtgREgSHWmpLyq8y2TW2 tIPlJPBx8mp5cASqQYgujN9vZbeDKlhG2sZ3vvEFF9H+1TPctjR0YeilwQIY7/HjRhdS 0Eov32+tG265DpHxkV5KFMlOR7pJsY++h1jmC6Nryf9hSuR6rg0H0rC71oOeeqBZSGMQ Xgij+DPj33bQTMlTJzPoagia8JuBbqyR7YhOmc12YF/echKmwUqyPnFFZIJywrhaTkks 4Bqw==
X-Gm-Message-State: AIVw113tHFc4P7flXddls7LPemHchfX5KJ4mVJvpvTUoEojXI5IXO407 rwACqyeP/H+0ZZ0YwMDzeEoJiX64HeEdHPU=
X-Received: by 10.202.214.3 with SMTP id n3mr19263716oig.35.1501587674536; Tue, 01 Aug 2017 04:41:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.139.137 with HTTP; Tue, 1 Aug 2017 04:41:14 -0700 (PDT)
From: Loganaden Velvindron <logan@hackers.mu>
Date: Tue, 1 Aug 2017 15:41:14 +0400
Message-ID: <CAFDEUTciw4Rr5b7jY4iZ4cqPLjdd4h8zS7NVXy59cZXi4HOgWA@mail.gmail.com>
Subject: Remote participation
To: ietf@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qu8EKKTv9AHKt9HoG5iOwfUjZXA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 11:41:17 -0000

Dear IETF folks,

I would like to discuss about one thing:

I am from Mauritius, which is still a emerging country. The average
salary of 50% of the working population is around $430 (USD). In the
IT sector, its slightly higher depending on the job. It's great that
remote participation is now available, and thanks to the team behind
this.

My group was able to participate in both IETF 98 & IETF 99 remotely,
and produce working code for the hackathon & contribute to Internet
Drafts.

For the majority of people in our region, we cannot afford to travel
to the IETF, and most employers would not pay an IETF trip. It's great
that remote participation is free, but I believe that we can
contribute financially, according to our means.

Would such as option be made available to remote participants at the
time of registration ?

Kind regards,
Logan


From nobody Tue Aug  1 06:00:53 2017
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B3EC13213D for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 06:00:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2v3erqWHOOLr for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 06:00:49 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9819613188F for <ietf@ietf.org>; Tue,  1 Aug 2017 06:00:49 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id t201so14020652wmt.1 for <ietf@ietf.org>; Tue, 01 Aug 2017 06:00:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=81avQs5aFavdz9IlE0vE81WtBcb6IDSbOLtyNAv88xo=; b=rlhWjj7A8EQrazfJWfvQ5zyCcOjeYpYoBw2NUI1lWl/4Pi/ejbO3QuFCYRciRy9G/o ixMOjE/ZetG+4GRkFONuD7i3ZTgYuGOK6l63vkYfgUAF2GIJutGdOB+VqW4XwR0uWaUD 4l2KtYA69xbMpNVfce9Ym6vGqb4N3A08K8yyXNHYqkzGQdNtb15Q+sIcEWEtPFt+vqAW di/YkwaYuzv2JJ4hEolRQQKK4bHecUK7vW/rUCQXlUrF7SCn/7aam886YyhHLZYI1NUC w/hYZo55CxBTQuERmUahQeyEOrToknnnEhODyqb86H2Iz5VTRUHcMjzWFzp9ixSOo3cZ CcAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=81avQs5aFavdz9IlE0vE81WtBcb6IDSbOLtyNAv88xo=; b=PmRcInUskIRvjdz8oiIa3Sno579gfgtFEm08mJ477a18WSi7BSUVkubOT74VttFMcP RoxcCUu7HZu490+9XMaSPTzJ5l54J3wy+N0QnkrorH5DNnLqSWptMSAmD6Kx8+U/hgPw vAyYeidLrEUIkrALud3gn26WXVOrVskZWqqD8mdelnMRA6RPrjM4qIf8olES3ki0e8RP 9KlkyHGke4MCwnNpcUbVbQVTyAePuNyYPrG+CvuGCq0v5jeafsStZn/zQ58YR+KvJ0PA d1cMNvgQFi22jgyBpDzkDMmvWUw/qhjw9s6bRXsMVZBpqb+blCJj3OH+8LZ7leK11N68 xnkQ==
X-Gm-Message-State: AIVw111P/cskFY1lew5mB5q7p/h+2VwSDlVjpF1iZp/4SO8GLnHnwhva UiYQRGZEtqHV6fOJVl7MG7pchdM8KQ==
X-Received: by 10.28.161.3 with SMTP id k3mr1442565wme.155.1501592447915; Tue, 01 Aug 2017 06:00:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.183.1 with HTTP; Tue, 1 Aug 2017 06:00:47 -0700 (PDT)
In-Reply-To: <06672B8B-DDC5-4362-8729-346688F587DD@tzi.org>
References: <523.1501530916@obiwan.sandelman.ca> <E8859A9F-7539-4C6B-962C-56E6F3323C14@tzi.org> <716.1501548333@obiwan.sandelman.ca> <06672B8B-DDC5-4362-8729-346688F587DD@tzi.org>
From: Alia Atlas <akatlas@gmail.com>
Date: Tue, 1 Aug 2017 09:00:47 -0400
Message-ID: <CAG4d1re6k-RhavZ7YFYrLD2qYg362fELdan0tN4LpiTW0VEf4w@mail.gmail.com>
Subject: Re: normative references to IANA registries
To: Carsten Bormann <cabo@tzi.org>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a114ed608749df10555b0bc2f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/r-OZfA6kakxMmWyuzx-koA-Az9I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 13:00:52 -0000

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

Carsten,

On Tue, Aug 1, 2017 at 3:32 AM, Carsten Bormann <cabo@tzi.org> wrote:

> On Aug 1, 2017, at 02:45, Michael Richardson <mcr+ietf@sandelman.ca>
> wrote:
> >
> >
> > Carsten Bormann <cabo@tzi.org> wrote:
> >>> So I wonder out loud: shouldn't all of the IANA registries have clear
> >>> reference files that could be normatively referenced?
> >
> >> Try referencing, say, {{!IANA.cbor-tags}} =E2=80=94 it just works :-)
> >
> > wow. I'm sure it's documented in some place so obvious I can't see it.
>
> https://xml2rfc.tools.ietf.org/ is the place that talks about bibxml8
> references.
> kramdown-rfc is just mapping all the IANA.* references to bibxml8, as in
>
> https://xml2rfc.tools.ietf.org/public/rfc/bibxml8/
> reference.IANA.cbor-tags.xml
>
> > Is the "cbor-tags" part the last part of the IANA registry URL?
>
> Apparently.
>
> bibxml8/index.cgi:
>
>     if ($IANAref =3D~ m(^/?reference.IANA[.]([^/]+)[.](xml|kramdown)$)) {
>         my $IANAref =3D $1;
> =E2=80=A6
>             my $a =3D get("http://www.iana.org/assignments/$IANAref/=E2=
=80=9C);
>
> kramdown-rfc is, somewhat ironically maybe, using the xml version then :-=
)
> (getting the kramdown [really: YAML] version isn't even implemented at
> xml2rfc.ietf.org, but there is no need to).
>

It would be very helpful to  have the kramdown version at xml2rfc.ietf.org.
Simply going to github (https://github.com/cabo/kramdown-rfc2629)  to
download and run the kramdown converter to xml doesn't work trivially on a
Windows machine.  I go to
http://xml2rfc.tools.ietf.org/experimental.html#kramdown to run it.

Since this is the only time that I use kramdown (or any markdown language),
it would be quite helpful to
also have a pointer to the syntax to use.  I end up googling and looking at
random kramdown documentation
and hoping.  The error-checking is also a bit frustrating - I had an extra
space in front of a - for separating
the authors and the document failed to convert at all with no error.  Not
being familiar enough with kramdown,
it was completely non-obvious.

Regardless of the above digression, kramdown-rfc is really awesome and
makes it much easier to write drafts!
I've converted over to doing so.  I really think that a bit more visibility
- including on the xml2rfc.ietf.org page - with a pointer or two - would
speed interest and adoption.

Thank you for your work on this!
Alia

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

<div dir=3D"ltr">Carsten,<div class=3D"gmail_extra"><br><div class=3D"gmail=
_quote">On Tue, Aug 1, 2017 at 3:32 AM, Carsten Bormann <span dir=3D"ltr">&=
lt;<a href=3D"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span cla=
ss=3D"gmail-">On Aug 1, 2017, at 02:45, Michael Richardson &lt;<a href=3D"m=
ailto:mcr%2Bietf@sandelman.ca">mcr+ietf@sandelman.ca</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; Carsten Bormann &lt;<a href=3D"mailto:cabo@tzi.org">cabo@tzi.org</a>&g=
t; wrote:<br>
&gt;&gt;&gt; So I wonder out loud: shouldn&#39;t all of the IANA registries=
 have clear<br>
&gt;&gt;&gt; reference files that could be normatively referenced?<br>
&gt;<br>
&gt;&gt; Try referencing, say, {{!IANA.cbor-tags}} =E2=80=94 it just works =
:-)<br>
&gt;<br>
&gt; wow. I&#39;m sure it&#39;s documented in some place so obvious I can&#=
39;t see it.<br>
<br>
</span><a href=3D"https://xml2rfc.tools.ietf.org/" rel=3D"noreferrer" targe=
t=3D"_blank">https://xml2rfc.tools.ietf.<wbr>org/</a> is the place that tal=
ks about bibxml8 references.<br>
kramdown-rfc is just mapping all the IANA.* references to bibxml8, as in<br=
>
<br>
<a href=3D"https://xml2rfc.tools.ietf.org/public/rfc/bibxml8/reference.IANA=
.cbor-tags.xml" rel=3D"noreferrer" target=3D"_blank">https://xml2rfc.tools.=
ietf.<wbr>org/public/rfc/bibxml8/<wbr>reference.IANA.cbor-tags.xml</a><br>
<span class=3D"gmail-"><br>
&gt; Is the &quot;cbor-tags&quot; part the last part of the IANA registry U=
RL?<br>
<br>
</span>Apparently.<br>
<br>
bibxml8/index.cgi:<br>
<br>
=C2=A0 =C2=A0 if ($IANAref =3D~ m(^/?reference.IANA[.]([^/]+)[<wbr>.](xml|k=
ramdown)$)) {<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 my $IANAref =3D $1;<br>
=E2=80=A6<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 my $a =3D get(&quot;<a href=3D"ht=
tp://www.iana.org/assignments/$IANAref/" rel=3D"noreferrer" target=3D"_blan=
k">http://www.iana.org/<wbr>assignments/$IANAref/</a>=E2=80=9C);<br>
<br>
kramdown-rfc is, somewhat ironically maybe, using the xml version then :-) =
(getting the kramdown [really: YAML] version isn&#39;t even implemented at =
<a href=3D"http://xml2rfc.ietf.org" rel=3D"noreferrer" target=3D"_blank">xm=
l2rfc.ietf.org</a>, but there is no need to).<br></blockquote><div><br></di=
v><div>It would be very helpful to =C2=A0have the kramdown version at <a hr=
ef=3D"http://xml2rfc.ietf.org">xml2rfc.ietf.org</a>.</div><div>Simply going=
 to github (<a href=3D"https://github.com/cabo/kramdown-rfc2629">https://gi=
thub.com/cabo/kramdown-rfc2629</a>)=C2=A0 to download and run the kramdown =
converter to xml doesn&#39;t work trivially on a Windows machine.=C2=A0 I g=
o to <a href=3D"http://xml2rfc.tools.ietf.org/experimental.html#kramdown">h=
ttp://xml2rfc.tools.ietf.org/experimental.html#kramdown</a> to run it.</div=
><div><br></div><div>Since this is the only time that I use kramdown (or an=
y markdown language), it would be quite helpful to</div><div>also have a po=
inter to the syntax to use.=C2=A0 I end up googling and looking at random k=
ramdown documentation=C2=A0</div><div>and hoping.=C2=A0 The error-checking =
is also a bit frustrating - I had an extra space in front of a - for separa=
ting</div><div>the authors and the document failed to convert at all with n=
o error.=C2=A0 Not being familiar enough with kramdown,</div><div>it was co=
mpletely non-obvious.=C2=A0</div><div><br></div><div>Regardless of the abov=
e digression, kramdown-rfc is really awesome and makes it much easier to wr=
ite drafts!</div><div>I&#39;ve converted over to doing so.=C2=A0 I really t=
hink that a bit more visibility - including on the <a href=3D"http://xml2rf=
c.ietf.org">xml2rfc.ietf.org</a> page - with a pointer or two - would speed=
 interest and adoption. =C2=A0</div><div><br></div><div>Thank you for your =
work on this!</div><div>Alia</div></div></div></div>

--001a114ed608749df10555b0bc2f--


From nobody Tue Aug  1 06:15:38 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFAE7131FB7 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 06:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TD5HQsn0sLJ4 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 06:15:35 -0700 (PDT)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1063132155 for <ietf@ietf.org>; Tue,  1 Aug 2017 06:15:34 -0700 (PDT)
Received: by mail-qk0-x22f.google.com with SMTP id d136so8612781qkg.3 for <ietf@ietf.org>; Tue, 01 Aug 2017 06:15:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=kcz9dlJfTbNCAPzlqm9HIG1Fjy4yphsMfKJZ73ald4I=; b=jN6BfdhC1SnFl3ng+pvBMTIx81D3AvO0olWLsW9xIpSrXBp1eNG9MCz7K1hFqsUU5/ PIjF2HJsfMVFycXdbIhYvc8U+jD0P7QyG8yEge9M4mMuqyyukVSfChZnuPGdBJk+knMs tv66XqjKjDsndwnBjVBlVAx0DsfxKw3sfYYuaLpnVYCujqPxsaonMEFiNj2kDiDTDBO6 EenfKFNwHDpZpOP2XO82vpT9Uo4cE283pTzmnn4PVvW+85Qsy5xKecyQyePbyqwNXQ9I rrSvIrFwzy6ycxEpm/HuUQOROLxFmFUKOFkLVq6E51NrZQuDbGMZv6gRo1LlcAOota6S 6uvg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=kcz9dlJfTbNCAPzlqm9HIG1Fjy4yphsMfKJZ73ald4I=; b=kZjH4tm0CzVRmrIuimdeHe3FQuHjBMVeoCUYjMxSrlA4K/fnD7f7XZzOfiRVRYoBrO M/Q3XHRRsQt2pd4aFh2dPUZkiozFQlAtRumgn40XYh62AOzpfRf2WB9826tPZbdqj+dP TcZ4/p36oAOSReXQVwiZ4qrJQCa4L6kCE4LCZXLHPccwKAQ5sogcB8JLfjmA3apQp4La 8yWjy9sMQbUnaSnNV0P4xj3hCjodm1FYP/3Hr057oOhW0CwwdEV/SaTmrCeX0ochkEwu BgM/3RRy3ddoJyRX8WcQyzBsq7HPChxu8vBIT8DXAwMN92i495le33HT5Qh+uqU4ezBZ i3qA==
X-Gm-Message-State: AIVw111WRUarFck4cDKzxdW4Dc9rqH0hNAmr1rl4YdMx3JTBtYWAjvXU ta0lSbA3LP/1D909
X-Received: by 10.55.183.65 with SMTP id h62mr26727839qkf.35.1501593333959; Tue, 01 Aug 2017 06:15:33 -0700 (PDT)
Received: from [10.0.30.153] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id y7sm2908356qta.49.2017.08.01.06.15.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Aug 2017 06:15:32 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <7415616E-6D4D-4164-B19D-DD4174599C75@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A5CC0C0D-ED31-46A3-A7FC-0CEE10665989"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Tue, 1 Aug 2017 09:15:31 -0400
In-Reply-To: <m1dcUV1-0000FGC@stereo.hq.phicoh.net>
Cc: ietf@ietf.org, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
References: <m1dcUV1-0000FGC@stereo.hq.phicoh.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UhoW_3sRu4tL5EL_JJt8QDPKVFs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 13:15:37 -0000

--Apple-Mail=_A5CC0C0D-ED31-46A3-A7FC-0CEE10665989
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Aug 1, 2017, at 6:34 AM, Philip Homburg <pch-ietf-6@u-1.phicoh.com> =
wrote:
> We need to do something, anything.

Yes, Philip.   The reason we are having this discussion is that a bunch =
of us were bored and wanted to see if we could get a rise out of the =
IETF by proposing something with no good purpose, just to kill the =
boredom.   None of us have any other work to do.   Hell, that's why we =
invented IPv6 in the first place, and IPv4 too.   POTS was working fine. =
  And remember chaosnet and SNA?   Those kicked ass!   We were just =
bored.

Honestly, though, it's been a blast.   I don't see why you are being =
such a killjoy.   What's wrong with hobbies?

Seriously, my point is that the tone of your message and quite a few =
others here is that people who think this proposal is worthwhile are =
hobbyists, and people who think it's not are Serious People Trying To =
Get Work Done.   I'm sure it's a satisfying narrative, but it's kind of =
absurd.

If there's consensus to do this, we should do it.   If there isn't, we =
shouldn't.   That's how the IETF is supposed to work.   A little less =
contempt would go a long way to preventing conversations like this from =
blooming into the hundreds of messages.


--Apple-Mail=_A5CC0C0D-ED31-46A3-A7FC-0CEE10665989
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;" =
class=3D"">On Aug 1, 2017, at 6:34 AM, Philip Homburg &lt;<a =
href=3D"mailto:pch-ietf-6@u-1.phicoh.com" =
class=3D"">pch-ietf-6@u-1.phicoh.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">We need to do something, =
anything.</span><br style=3D"font-family: Menlo-Regular; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""></div></blockquote></div><br =
class=3D""><div class=3D"">Yes, Philip. &nbsp; The reason we are having =
this discussion is that a bunch of us were bored and wanted to see if we =
could get a rise out of the IETF by proposing something with no good =
purpose, just to kill the boredom. &nbsp; None of us have any other work =
to do. &nbsp; Hell, that's why we invented IPv6 in the first place, and =
IPv4 too. &nbsp; POTS was working fine. &nbsp; And remember chaosnet and =
SNA? &nbsp; Those kicked ass! &nbsp; We were just bored.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Honestly, though, it's =
been a blast. &nbsp; I don't see why you are being such a killjoy. =
&nbsp; What's wrong with hobbies?</div><div class=3D""><br =
class=3D""></div><div class=3D"">Seriously, my point is that the tone of =
your message and quite a few others here is that people who think this =
proposal is worthwhile are hobbyists, and people who think it's not are =
Serious People Trying To Get Work Done. &nbsp; I'm sure it's a =
satisfying narrative, but it's kind of absurd.</div><div class=3D""><br =
class=3D""></div><div class=3D"">If there's consensus to do this, we =
should do it. &nbsp; If there isn't, we shouldn't. &nbsp; That's how the =
IETF is supposed to work. &nbsp; A little less contempt would go a long =
way to preventing conversations like this from blooming into the =
hundreds of messages.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_A5CC0C0D-ED31-46A3-A7FC-0CEE10665989--


From nobody Tue Aug  1 07:17:02 2017
Return-Path: <shares@ndzh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 336D41275F4; Tue,  1 Aug 2017 07:16:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level: 
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TcCR9OPDdo-0; Tue,  1 Aug 2017 07:16:48 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9E1D12711B; Tue,  1 Aug 2017 07:16:44 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=70.194.10.26; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Jonathan Hardwick'" <jonathan.hardwick@metaswitch.com>, <rtg-dir@ietf.org>
Cc: <i2rs@ietf.org>, <ietf@ietf.org>, <draft-ietf-i2rs-rib-info-model.all@ietf.org>
References: <150157551332.9546.17310175858783211646@ietfa.amsl.com>
In-Reply-To: <150157551332.9546.17310175858783211646@ietfa.amsl.com>
Subject: RE: Rtgdir early review of draft-ietf-i2rs-rib-info-model-11
Date: Tue, 1 Aug 2017 10:10:31 -0400
Message-ID: <007801d30acf$f04d9280$d0e8b780$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQE7A5ElB5TCjRQ2QeiC25IY4N7z2KOfmK1A
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LUtieD-DOLQwPBJlguk4sli5S80>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 14:16:49 -0000

Jonathan:=20

Please thank Henning for his review.=20

Sue Hares=20

-----Original Message-----
From: Jonathan Hardwick [mailto:jonathan.hardwick@metaswitch.com]=20
Sent: Tuesday, August 1, 2017 4:19 AM
To: rtg-dir@ietf.org
Cc: i2rs@ietf.org; ietf@ietf.org; =
draft-ietf-i2rs-rib-info-model.all@ietf.org
Subject: Rtgdir early review of draft-ietf-i2rs-rib-info-model-11

Reviewer: Henning Rogge
Review result: Has Nits

Submitting on behalf of Henning Rogge:

Hi,

I was asked to do an early review of the i2rs-rib-info-model...

I liked the comprehensive approach describing the RIB, including =
tunnels, multi-topology routing (by using multiple RIBs) and routing =
reactions (like drop/icmp-error).

I found a few things in the draft that in my opinion need a bit more =
work...

First it seems that Section 2.3 (Route) is a bit out of sync with the =
BNF later in the document, it should at least mention matching the =
source-IP address of the IP headers.

Second (if I read the BNF in Section 6 correctly), the match for a route =
seems to be one of the list "ip address, MPLS label, MAC address, =
interface". I think it should be possible to combine "interface" or "mac =
address" with an IP address to restrict the focus of a route, e.g. =
"match fe80::1 from interface X".

Last, I wonder if multicast routing needs more different types of =
matchers, e.g. a match on the TTL of the IP packet to limit the range of =
a multicast group.

There is also problem of multicast routing in MANETs (see RFC 6621) =
which can use a hash-based duplicate detection to determine if it =
forwards or drops a multicast packet. Would this be out of scope for the =
draft?

Henning Rogge




From nobody Tue Aug  1 07:59:02 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66BD1132195 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 07:59:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0vUsUwPq0eQx for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 07:58:58 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DB09132188 for <ietf@ietf.org>; Tue,  1 Aug 2017 07:58:58 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id B670924AE3B; Tue,  1 Aug 2017 14:58:47 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id CA573160041; Tue,  1 Aug 2017 14:58:52 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id AE4EC16004F; Tue,  1 Aug 2017 14:58:52 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 32extRfbABWr; Tue,  1 Aug 2017 14:58:52 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 24C70160041; Tue,  1 Aug 2017 14:58:52 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 1660780A6174; Wed,  2 Aug 2017 00:58:49 +1000 (AEST)
To: mohamed.boucadair@orange.com
Cc: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>, "ietf@ietf.org" <ietf@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es> <787AE7BB302AE849A7480A190F8B93300A0155F5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es> <20170801072139.316A7809B357@rock.dv.isc.org> <787AE7BB302AE849A7480A190F8B93300A0156BD@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-reply-to: Your message of "Tue, 01 Aug 2017 07:53:15 +0000." <787AE7BB302AE849A7480A190F8B93300A0156BD@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Date: Wed, 02 Aug 2017 00:58:49 +1000
Message-Id: <20170801145849.1660780A6174@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8XBNe0DZkl-VIdOeBdFz7M0dCho>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 14:59:00 -0000

In message <787AE7BB302AE849A7480A190F8B93300A0156BD@OPEXCLILMA3.corporate.adro
ot.infra.ftgroup>, mohamed.boucadair@orange.com writes:
> Hi Mark,
>
> Answering this particular point.
>
> Please see inline.
>
> Cheers,
> Med
>
> > -----Message d'origine-----
> > De: ietf mailto:ietf-bounces@ietf.org De la part de Mark Andrews
> > Envoy: mardi 1 aot 2017 09:22
> > : jordi.palet@consulintel.es
> > Cc: ietf@ietf.org
> > Objet: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for
> IETF
> > Meetings
> >
> >
> > In message <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es>, JORDI
> > PALET M
> > ARTINEZ writes:
> > > Hi Med,
> > >
> > > In line
> > >
> > > Saludos,
> > > Jordi
> > >
> > >
> >
> > > It is a matter of
> > > preference of one or another transition mechanisms. All them have good
> > > and bad things. I see much simpler the combination of NAT64+CLAT than
> > > DS-Lite or MAP, in addition to the ONLY support in cellular networks
> is
> > > precisely NAT64/464XLAT, which means is the MOST extended transition
> > > mechanism by millions (billions?) of users. It makes a lot of sense to
> > me
> > > to go in all the infrastructures to the one that has more deployment
> > > already.
> >
> > Not really.  Cellular networks went with anything available, rather
> > than the best.  We are continuing the pay the price for that.
>
> Med Actually, no. There was an IPv6 Study Item within 3GPP. Both DS-Lite,
> A+P, and NAT64 were presented and documented in a 3GPP report. For
> example, this is what was documented for A+P:
>
> Known issues:
> -	The UE needs to be modified to support A+P scheme
> -	The gateway needs to forward not only based on IP address but
> based on address plus port. The network needs to implement PRR in similar
> places as CGN in the DS-Lite approach
> -	The backend RADIUS system needs to be changed as subscribers can
> no longer be identified by IP address only, but by IP address and port
> -	In the IPv6 tunnelling approach QoS differentiation between
> bearers cannot be provided easily
> -	The solution works only with applications using transport
> protocols, which have concept of port numbers (such as UDP and TCP).
> There will be challenges with protocols which use plain IP.
> -	The solution sets restrictions to applications within in the UE,
> as the allocation of fixed port numbers becomes more complicated.
> -	For ICMP messages, the UE must use an ICMP query identifier
> within the allocated port range, otherwise the response will not be
> received by this UE.
>
> Known benefits:
>
> -	The UE has access to public IPv4 address, which simplifies the
> behaviour for P2P applications such as VoIP.
> -	Allows IPv4 lifetime extension if used with GTP/GRE.
> -	Legal requirements for tracing which traffic flow was originated
> from which UE is simpler than in CGN solutions, as the operator does not
> need to store each flow but only A+P allocation information.
> -	In GTP/GRE/DSMIP6 based solutions QoS can be provided.
> -	A+P allows for an incremental migration to IPv6-only network
> -	A+P can be fully stateless when used together with IPv6
> -	No per-state sessions are maintained in the PLMN realm
> -	Unlike NAT44/NAT64, no dynamic state synchronization is required
> to ensure service robustness
> -	No ALG is required to be implemented in the service/PLMN realm
> -	No extra-cost on the UE to support NAT traversal techniques is
> required
> -	Unlike double NAT solutions, peer-to-peer services can be
> delivered with one exception as documented in 23
> -	No Keep-alive messages are required to maintain NAT entries. This
> characteristic mitigates battery consumption issues induced by
> "Always-on" services. Especially, the use of short intervals between
> keep-alive messages has a big impact on the battery consumption (See 24
> for more details about complications to tweak UDP timers in NAT devices
> and also keep-alive intervals used by UE). Moreover, the network load is
> more optimized since the load induced by keep-alive messages in the
> context of CGN solutions is avoided.
> -	Latencies and related problems of NATs are avoided.
>
>
> And for NAT64:
>
> ==
> Known issues of the solution:
>
> -	The session binding between MS/UE IPv6 address and public IPv4
> address/port is not known to the PCC architecture. Therefore, depending
> on deployment and if the application is NAT aware and has access to the
> binding (as e.g. in the case of IMS), there may or may not be issues with
> applying PCC to the session.
> -	General NAT concerns, not specific to 3GPP networks, apply. For
> example, applications that embed IP addresses in the payload and are not
> NAT aware require additional functionality to work across NATs.
> -	In case of roaming with Local Breakout (PGW/GGSN in VPLMN), if
> there is a need to reach IPv4-only services, the VPLMN operator would be
> required to deploy NAT64/DNS64 in order to provide the same user
> experience using IPv6-only connections for IPv4-only services as in
> non-roaming scenarios.
> -	It is unclear how IPv4 literals are supported.

Requires EVERY DNSSEC validator on the planet to learn about DNS64.

DS-Lite does NOT require every DNSSEC validator on the planet to
be upgraded.

> Known benefits of the solution
>
> -	This solution requires no changes to the MS/UE.
> -	The existing bearer and session management procedures can be used
> without any change.

Since you are sending IPv4 as IPv6 there is no difference between NAT64
and DNS-Lite etc.

> -	This solution does not introduce any additional tunnelling
> overhead on any interfaces.

You have 1480 payloads with NAT64 and 1460 byte playloads with DS-Lite etc.
Incoming 1500 byte IPv4 packets get fragmented either way as they can't
fit in a 1500 byte IPv6 packet.

> -	This solution has no impact to the 3GPP network architecture, no
> new interface or network element is needed. This solution can be deployed
> without any additional normative specification within 3GPP. Limitations
> described under "known issues" above apply.
> -	No changes to the IPv6 address-assignment procedures required.

None required for DS-Lite either.

> -	No bearing on the type of transport network: Transport network
> can be IPv4 or IPv6.
> -	NAT64 can be either co-located or separate from GGSN/PDN-GW.

Same with DS-Lite.

> -	Solution to the public IPv4 address exhaustion problem through
> the use of stateful NAT64.

Same with DS-Lite (stateful NAT again).

> -	No impact on QoS/bearer procedures between UE and PDN GW/S GW.
> ===

DS-Lite does NOT require every node on the planet to aquire a CLAT
only a encapsulating interface to talk to legacy devices.

When you ignore some of the problem space NAT64 looks ok.  When you
look at the entire problem space that is not the case.

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Aug  1 08:08:22 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11D5C131D38 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 08:08:20 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9IeUwGEXieGY for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 08:08:18 -0700 (PDT)
Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 856C9129ABE for <ietf@ietf.org>; Tue,  1 Aug 2017 08:08:18 -0700 (PDT)
Received: by mail-qt0-x230.google.com with SMTP id t37so10705650qtg.5 for <ietf@ietf.org>; Tue, 01 Aug 2017 08:08:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=rBUv8dXMpi6kX7ypWMaUh0l/VmP4WzNhOU+oEGNWXhA=; b=133na1OAKSEsOI4Fz054wGx/UImnlVUy+D4V9ewqzb59XymtKIbhMNhzhhh3sQR6QQ OdN92IMNgLZKQ+vygvgxSXLSOBD9tdj/4SQLZBA9UelmxR89wNDgWOqvvj4YeAdsGodP 5n5ZS7RGlGUv/d0Tw8TEpeYguTFJNQjmMMpmb59LJE+lnXIDfzSz8ZjgHE7nNz66FEhG fu2NwZfAPFgWvhGlVukS3l0YzJVdson59PMcO3PywO0y57XlVfbGb1RlEwcezMfQmq90 BVc4N3ClLIWy3dASxKGpw+sbiRUlZBvzH+6MkdTg4Zf79qlM3RhyiTclF9695xbSPcUy XJBQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=rBUv8dXMpi6kX7ypWMaUh0l/VmP4WzNhOU+oEGNWXhA=; b=JNplyS+19F+aqEXJ5NkBqjSTDo/zCF4/zx1ofvglcJhoGxrwuaNFqKaMCZL1WbRJf9 rzUTWP74tZ6TPGrJUDpFTOEjgCt+9uGfDK7AdrtC/85u8PRnbQbCw6J5AE9q0RyZtfAJ c/9YQOvzlye4oHS2s2Kw4IWXKVQVhg1V2aYpnbZQkJU4WoFbsEKnuuWHucbe0pR1iSO6 CkPw1/8MJpaEFqci0Xd469qDurvhLS/CM3UarHELMjo19SYl6PRo+Q38E2GPB55qt+5y FZtIev87oRWAd2RgLA3MnJPYd6piDowzIOIyuX2XFX6vYm80Bg5SQzFr+m55COYBUb0w oGSA==
X-Gm-Message-State: AIVw111CvQTRiSbnywF1NhrSki9tgvznjF6pTEqSgoj2NP3HV1xWTqgs lLW2HOHJQuIvUH8Z
X-Received: by 10.237.34.39 with SMTP id n36mr27577569qtc.258.1501600097568; Tue, 01 Aug 2017 08:08:17 -0700 (PDT)
Received: from [10.0.30.153] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id g27sm23117830qtg.84.2017.08.01.08.08.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Aug 2017 08:08:16 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <5C3343EF-3724-4155-87BC-E169DFC38342@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5922A275-B091-4C68-8533-D32167B59C76"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Tue, 1 Aug 2017 11:08:15 -0400
In-Reply-To: <20170801145849.1660780A6174@rock.dv.isc.org>
Cc: "mohamed.boucadair@orange.com> <mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "ietf@ietf.org" <ietf@ietf.org>, "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
To: Mark Andrews <marka@isc.org>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es> <787AE7BB302AE849A7480A190F8B93300A0155F5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es> <20170801072139.316A7809B357@rock.dv.isc.org> <787AE7BB302AE849A7480A190F8B93300A0156BD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20170801145849.1660780A6174@rock.dv.isc.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/D9iyZn9-SVZHhC60ue4UGTe0kKI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 15:08:20 -0000

--Apple-Mail=_5922A275-B091-4C68-8533-D32167B59C76
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Aug 1, 2017, at 10:58 AM, Mark Andrews <marka@isc.org> wrote:
> Requires EVERY DNSSEC validator on the planet to learn about DNS64.

Just to be clear, every DNSSEC validator on the planet also had to learn =
about DNSSEC, so it's probably worth explaining why this is a problem: =
the problem is not that we'd have to update every DNSSEC validator, but =
rather that this makes DNSSEC validators more complicated, and that =
potentially comes with problems, and that code will just be extra most =
of the time, perhaps.

Although in practice I suspect that as time goes on and more providers =
adopt IPv6, there will come a time when NAT64 will be very much the most =
economical solution to dealing with the long tail of small IPv4 service =
providers.   And I think if you impose functional separation between =
validation and translation, you don't create a serious risk.

But I think the point you make is valid, and I don't claim to be =
authoritative on the topic of how risky this is.


--Apple-Mail=_5922A275-B091-4C68-8533-D32167B59C76
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;" =
class=3D"">On Aug 1, 2017, at 10:58 AM, Mark Andrews &lt;<a =
href=3D"mailto:marka@isc.org" class=3D"">marka@isc.org</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">Requires EVERY =
DNSSEC validator on the planet to learn about DNS64.</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote></div><br class=3D""><div class=3D"">Just =
to be clear, every DNSSEC validator on the planet also had to learn =
about DNSSEC, so it's probably worth explaining why this is a problem: =
the problem is not that we'd have to update every DNSSEC validator, but =
rather that this makes DNSSEC validators more complicated, and that =
potentially comes with problems, and that code will just be extra most =
of the time, perhaps.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Although in practice I suspect that as time goes on and more =
providers adopt IPv6, there will come a time when NAT64 will be very =
much the most economical solution to dealing with the long tail of small =
IPv4 service providers. &nbsp; And I think if you impose functional =
separation between validation and translation, you don't create a =
serious risk.</div><div class=3D""><br class=3D""></div><div =
class=3D"">But I think the point you make is valid, and I don't claim to =
be authoritative on the topic of how risky this is.</div><div =
class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_5922A275-B091-4C68-8533-D32167B59C76--


From nobody Tue Aug  1 10:29:21 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF4B51321C0 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 10:29:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQ1WdpDQSM_D for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 10:29:13 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1F561321BD for <ietf@ietf.org>; Tue,  1 Aug 2017 10:29:12 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v71HSOh2007273; Tue, 1 Aug 2017 18:28:24 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v71HSOh2007273
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1501608515; bh=FvnCEcNmdNS76yuVEVApOTmznc0=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=hW72dZaooDv5cEJbTHaE3q5kuyVF5X08xH4ZUqdy8pRtkia20m1Op34uzLdpk1rIj VXHYM1yulHx2GG6g9mBGTmxPkSRJ7pS8eklo8a6qxEJRowhKA5e8Zdn3J8cI59RyC5 MIPJ5X1G5eT/HOT+JFEGngypxsog1VSlQnaO2dKY=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y70ISJ0543810918Id ret-id none; Tue, 01 Aug 2017 18:28:34 +0100
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:e54a:ea58:f5f0:7d1e] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v71HSC7p020676 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Aug 2017 18:28:13 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <5C3343EF-3724-4155-87BC-E169DFC38342@fugue.com>
Date: Tue, 1 Aug 2017 18:28:11 +0100
Cc: Mark Andrews <marka@isc.org>, "ietf@ietf.org" <ietf@ietf.org>, "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|c23812222e6467c6d3ed634ad82e65b2y70ISJ03tjc|ecs.soton.ac.uk|FE8011FD-6E26-40EB-9058-A60909CD00D2@ecs.soton.ac.uk>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es> <787AE7BB302AE849A7480A190F8B93300A0155F5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es> <20170801072139.316A7809B357@rock.dv.isc.org> <787AE7BB302AE849A7480A190F8B93300A0156BD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20170801145849.1660780A6174@rock.dv.isc.org> <5C3343EF-3724-4155-87BC-E169DFC38342@fugue.com> <FE8011FD-6E26-40EB-9058-A60909CD00D2@ecs.soton.ac.uk>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y70ISJ054381091800; tid=y70ISJ0543810918Id; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=4:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v71HSOh2007273
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RmyV7Xc0K9XcAMfWZ2NLzl7g3dc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 17:29:20 -0000

> On 1 Aug 2017, at 16:08, Ted Lemon <mellon@fugue.com> wrote:
>=20
> On Aug 1, 2017, at 10:58 AM, Mark Andrews <marka@isc.org> wrote:
>> Requires EVERY DNSSEC validator on the planet to learn about DNS64.
>=20
> Just to be clear, every DNSSEC validator on the planet also had to =
learn about DNSSEC, so it's probably worth explaining why this is a =
problem: the problem is not that we'd have to update every DNSSEC =
validator, but rather that this makes DNSSEC validators more =
complicated, and that potentially comes with problems, and that code =
will just be extra most of the time, perhaps.
>=20
> Although in practice I suspect that as time goes on and more providers =
adopt IPv6, there will come a time when NAT64 will be very much the most =
economical solution to dealing with the long tail of small IPv4 service =
providers.   And I think if you impose functional separation between =
validation and translation, you don't create a serious risk.
>=20
> But I think the point you make is valid, and I don't claim to be =
authoritative on the topic of how risky this is.

Apologies if it was already mentioned, but this was a good read:

https://blog.apnic.net/2016/06/09/lets-talk-ipv6-dns64-dnssec/

Tim


From nobody Tue Aug  1 10:34:50 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7BF51321D9 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 10:34:46 -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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yy5xMFegNhvT for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 10:34:44 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F30F1321D7 for <ietf@ietf.org>; Tue,  1 Aug 2017 10:34:44 -0700 (PDT)
Received: (qmail 46459 invoked from network); 1 Aug 2017 17:34:43 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 1 Aug 2017 17:34:43 -0000
Date: 1 Aug 2017 17:34:21 -0000
Message-ID: <20170801173421.1328.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-Reply-To: <7415616E-6D4D-4164-B19D-DD4174599C75@fugue.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bHqAt3Mwzlxql7nmCD1g2Qe8Zz0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 17:34:47 -0000

In article <7415616E-6D4D-4164-B19D-DD4174599C75@fugue.com> you write:
>Yes, Philip.   The reason we are having this discussion is that a bunch of us were bored and wanted to see if we could get
>a rise out of the IETF by proposing something with no good purpose, just to kill the boredom.

It certainly worked, didn't it?

HTH, HAND,
John


From nobody Tue Aug  1 10:57:19 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86DEB12ECB7 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 10:57:17 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FpIRZNu31lAA for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 10:57:15 -0700 (PDT)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9503B12009C for <ietf@ietf.org>; Tue,  1 Aug 2017 10:57:15 -0700 (PDT)
Received: by mail-qk0-x229.google.com with SMTP id z18so13582306qka.4 for <ietf@ietf.org>; Tue, 01 Aug 2017 10:57:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=3Th9YfKEvfQinVTlfXuj50FxTdTxbJK8fP9d6/A++nc=; b=WJzZO+8/qF3rOqJCBSNwfvZ0rYp+ccd5r+uYLgPvmKEWl/URhYEhZ7QANTcGCN4de9 M86qN/bi2fYBHcM9oveY3hm3vDTCyWXH+DF4YpsTXEO96r9tOrDeYJFLrNP2bDf0Z0kc 8GwqBj8ESDD9wnUilycIlEXLFzf0LmeQrpRzRIFkkC5CQyzNo3nkd54c0sF6DEeK85DB GR6t5axOOQQQu4lGogvUsGCx87HOYERh8io4/jsz4mqKXr8bDmOtAeDhAbL9wjTeafR6 Gjwy2ER+OVXiDK/BDYh0NhXqhDmjZw5u1NInP1jIjOhV9+MjPrLDsM4PnQU1GsyXzFZL etDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=3Th9YfKEvfQinVTlfXuj50FxTdTxbJK8fP9d6/A++nc=; b=fSGLR1brp4D7tRZFk2tEARZU3W/HlW85Gwp0uP5aaWoOcWLN0AjnkXIx0D8Gvc4ucY 7oDG4ghoj4eH0Tp9mPhp8Ws8iJx39C8Am+n3o46GYshdRKvWZeWoM4Ys00SHfiilIhw+ y7nl5rZGdiaZY8Q7WiHr508LyvayEOOKd4dCEalq5Xe608+ogfcrfqc8ShErTopix4rD T15XRw8ohJ+GSMXI4f79uIV5PEqOiYAkNW/SxrCJ3yZfiLYmKX3+Ee2W/nxXMQO9UIf3 Jm5HWAmlFDneY0sfV40c1P7za3q66qv2NmriS7M/XhvJVsXDuBvNFsY+OwxebbhNoRKx G1ow==
X-Gm-Message-State: AIVw113exKtWCaPhepvD2WqXCtUdrTSI8k3viaZ4zO8f38Rmx12hk8ZT TCla8JCt2FC1uAJ+
X-Received: by 10.55.105.135 with SMTP id e129mr25806918qkc.317.1501610234478;  Tue, 01 Aug 2017 10:57:14 -0700 (PDT)
Received: from [10.0.30.153] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id s51sm10861191qtc.9.2017.08.01.10.57.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Aug 2017 10:57:13 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <79B094AE-8D4B-4E30-AC8F-7F74BE8C13D2@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1A62BA56-B366-4734-9E97-69423DDD841F"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Tue, 1 Aug 2017 13:57:11 -0400
In-Reply-To: <EMEW3|c23812222e6467c6d3ed634ad82e65b2y70ISJ03tjc|ecs.soton.ac.uk|FE8011FD-6E26-40EB-9058-A60909CD00D2@ecs.soton.ac.uk>
Cc: Mark Andrews <marka@isc.org>, "ietf@ietf.org" <ietf@ietf.org>, "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
To: Tim Chown <tjc@ecs.soton.ac.uk>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es> <787AE7BB302AE849A7480A190F8B93300A0155F5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es> <20170801072139.316A7809B357@rock.dv.isc.org> <787AE7BB302AE849A7480A190F8B93300A0156BD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20170801145849.1660780A6174@rock.dv.isc.org> <5C3343EF-3724-4155-87BC-E169DFC38342@fugue.com> <FE8011FD-6E26-40EB-9058-A60909CD00D2@ecs.soton.ac.uk> <EMEW3|c23812222e6467c6d3ed634ad82e65b2y70ISJ03tjc|ecs.soton.ac.uk|FE8011FD-6E26-40EB-9058-A60909CD00D2@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HvuehkZ_MeYq3ezOUZXDDCf9lzk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 17:57:17 -0000

--Apple-Mail=_1A62BA56-B366-4734-9E97-69423DDD841F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Aug 1, 2017, at 1:28 PM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
> Apologies if it was already mentioned, but this was a good read:

Yes, she describes the issue nicely.   What she doesn't mention is that =
there is a way to detect DNS64, so in principle a validating stub =
resolver can do DNS64 itself _post validation_.   Of course, there are a =
lot of moving parts in this, particularly if you have multiple stub =
resolvers per host (e.g., a stub resolver in your browser and another =
one in your libc).

But the point is that it is actually possible to have NAT64 and DNSSEC.  =
 And indeed, if you are able to detect the NAT64 prefix (RFC 7050), you =
can treat all IPv4 addresses as IPv6 addresses by prepending the NAT64 =
prefix in the stack, and you don't even need to do DNS64 in the =
resolver, so validation just works (RFC 6535).

You can also do this by doing IPv4-to-v6 translation in the router, =
which is what Jordi is talking about when he mentions CLAT (RFC6877).

The only reason I'm not on board with Jordi's proposal is that I think =
it's more interesting to see what stacks do when you don't give them =
_any_ IPv4 address.   But in principle, with Jordi's solution, even IPv4 =
literals are handled correctly, and the interactions between DNS64 and =
VPNs go away as well.   To me this seems like a pretty reasonable =
compromise position, although it's not the experiment I'd personally =
prefer to run.


--Apple-Mail=_1A62BA56-B366-4734-9E97-69423DDD841F
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;" =
class=3D"">On Aug 1, 2017, at 1:28 PM, Tim Chown &lt;<a =
href=3D"mailto:tjc@ecs.soton.ac.uk" class=3D"">tjc@ecs.soton.ac.uk</a>&gt;=
 wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">Apologies if it was =
already mentioned, but this was a good read:</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote></div><br class=3D""><div class=3D"">Yes, =
she describes the issue nicely. &nbsp; What she doesn't mention is that =
there is a way to detect DNS64, so in principle a validating stub =
resolver can do DNS64 itself _post validation_. &nbsp; Of course, there =
are a lot of moving parts in this, particularly if you have multiple =
stub resolvers per host (e.g., a stub resolver in your browser and =
another one in your libc).</div><div class=3D""><br class=3D""></div><div =
class=3D"">But the point is that it is actually possible to have NAT64 =
and DNSSEC. &nbsp; And indeed, if you are able to detect the NAT64 =
prefix (RFC 7050), you can treat all IPv4 addresses as IPv6 addresses by =
prepending the NAT64 prefix in the stack, and you don't even need to do =
DNS64 in the resolver, so validation just works (RFC 6535).</div><div =
class=3D""><br class=3D""></div><div class=3D"">You can also do this by =
doing IPv4-to-v6 translation in the router, which is what Jordi is =
talking about when he mentions CLAT (RFC6877).</div><div class=3D""><br =
class=3D""></div><div class=3D"">The only reason I'm not on board with =
Jordi's proposal is that I think it's more interesting to see what =
stacks do when you don't give them _any_ IPv4 address. &nbsp; But in =
principle, with Jordi's solution, even IPv4 literals are handled =
correctly, and the interactions between DNS64 and VPNs go away as well. =
&nbsp; To me this seems like a pretty reasonable compromise position, =
although it's not the experiment I'd personally prefer to run.</div><div =
class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_1A62BA56-B366-4734-9E97-69423DDD841F--


From nobody Tue Aug  1 11:07:19 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 47C051321CD; Tue,  1 Aug 2017 11:07:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
Cc: codec@ietf.org, ietf@ietf.org, draft-ietf-codec-opus-update.all@ietf.org
Subject: Genart last call review of draft-ietf-codec-opus-update-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150161082225.9505.16606445945798880852@ietfa.amsl.com>
Date: Tue, 01 Aug 2017 11:07:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1r1QepssV_0keVIJcvl26O3gypQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 18:07:02 -0000

Reviewer: Robert Sparks
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-codec-opus-update-08
Reviewer: Robert Sparks
Review Date: 2017-08-01
IETF LC End Date: 2017-08-09
IESG Telechat date: Not scheduled for a telechat

Summary: Ready for publication as a Standards Track RFC

This document is straightforward in the changes it is making to OPUS.

My only note of sadness is that it continues to use a documentation mechanism
started by RFC6716 of effectively making a normative reference to the
_proceedings_ of previous IETF meetings. (Note that this document does this
twice: once for the patch file, which is a convenience - the information is in
the draft, and once for the updated test vectors. This is _not_ a convenience,
the information is not in the draft. If, for whatever reason, the proceedings
URL could not be retrieved, someone could not verify their implementation with
the updated test vectors).

On the one hand, we've set the precedent, and we could agree to just let this
go (I'm recommending that to the IESG with this review). On the other hand, we
could make things _slightly_ better (or perhaps just different) by putting the
test vectors in the doc as an appendix as a uuencoded compressed tarball.


From nobody Tue Aug  1 11:15:00 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDCE71321DE for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 11:14:57 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iCaYOzOLUcW0 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 11:14:56 -0700 (PDT)
Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 682761321CD for <ietf@ietf.org>; Tue,  1 Aug 2017 11:14:56 -0700 (PDT)
Received: by mail-qt0-x233.google.com with SMTP id s6so14036612qtc.1 for <ietf@ietf.org>; Tue, 01 Aug 2017 11:14:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=zZDlpCajf/0S+Sa0BnGl6frDMJHE85iov+wUpH7NcaM=; b=hn0H9KKmRNKcCKFVKl7hQcO4lpC7m4K1EXyvjqMBASFBt34qlBmxAg4bHEWXManLxR ixKvDW0iHwflpO0KnDRKCHg7pDoXnOaJVXDJGBt/OA8KZiNNUq1Virp8IqdAOcUfWSNW llRFtH2DP2GlcyDjnDqSiY2JqEtCIkqU/XhSPGQpu62Gvjnp1ieQMDNQpLPUl8dh84iH TcBGOmjzkMZ6jB+Wo+cy7yz1PZ/Mle3ZiyrV/YBWAVsQovfmb60vXAtGA9nofd4sr0gO JjQO28xvy2HxFXPDqU7K1BdDIRc5fBfAz8qlQQv2rvgCpoCN6c8mPMGhn6ScdRwYOqSp Dd9g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=zZDlpCajf/0S+Sa0BnGl6frDMJHE85iov+wUpH7NcaM=; b=ihkzwcZNBO61cRG9ysCuq6ssZLMaRsdHCQCvrBiU8OGAGO/+VJghrYrjyHFX26GDxb 0dS+Pevxi3aihCNeRozEQdnYz10fol33RFJwJP0PDkoLn0Tplb9GH21hu1FBx5AXeYLc lf0ID7ccgX1V3CzSc7zm4F9fcxiNJkfIZsBsnYIwNx6f4sy3VXmJcg8n73GkjYSRZgek kU1XzNlFv7vVsho/krhVcZIuaA8nS+K/wbOncfP3+bZO9QuvZwlQqyXgQz5CyRIC+oKl OgvldLsHAtVn6Jd2mYI8jp9OHLvusHDn5aXDYDVMqYUvk8rz/r7GdBVdgqFMC6MXe3qT lwjA==
X-Gm-Message-State: AIVw1119BDtwXPqPqKa4TVReGVZoj2/G5V/eLkjeQqTXjiyWLb9nXiVz Cw3wNJStKnGvuVrk
X-Received: by 10.200.39.115 with SMTP id h48mr28966943qth.294.1501611295502;  Tue, 01 Aug 2017 11:14:55 -0700 (PDT)
Received: from [10.0.30.153] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id j185sm5041857qkf.62.2017.08.01.11.14.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Aug 2017 11:14:54 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <30708801-142F-47C5-A154-15E9D3C5068D@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_41163AA2-9973-48AD-A46C-3036C9A7CA85"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Tue, 1 Aug 2017 14:14:53 -0400
In-Reply-To: <79B094AE-8D4B-4E30-AC8F-7F74BE8C13D2@fugue.com>
Cc: Mark Andrews <marka@isc.org>, "ietf@ietf.org" <ietf@ietf.org>, "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
To: Tim Chown <tjc@ecs.soton.ac.uk>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es> <787AE7BB302AE849A7480A190F8B93300A0155F5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es> <20170801072139.316A7809B357@rock.dv.isc.org> <787AE7BB302AE849A7480A190F8B93300A0156BD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20170801145849.1660780A6174@rock.dv.isc.org> <5C3343EF-3724-4155-87BC-E169DFC38342@fugue.com> <FE8011FD-6E26-40EB-9058-A60909CD00D2@ecs.soton.ac.uk> <EMEW3|c23812222e6467c6d3ed634ad82e65b2y70ISJ03tjc|ecs.soton.ac.uk|FE8011FD-6E26-40EB-9058-A60909CD00D2@ecs.soton.ac.uk> <79B094AE-8D4B-4E30-AC8F-7F74BE8C13D2@fugue.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qtaWmo3XqGBLaMpuzxg67v7tq9E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 18:14:58 -0000

--Apple-Mail=_41163AA2-9973-48AD-A46C-3036C9A7CA85
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Aug 1, 2017, at 1:57 PM, Ted Lemon <mellon@fugue.com> wrote:
> What she doesn't mention is that there is a way to detect DNS64, so in =
principle a validating stub resolver can do DNS64 itself _post =
validation_.

Oops, actually she did mention that in the last paragraph=E2=80=94sorry!


--Apple-Mail=_41163AA2-9973-48AD-A46C-3036C9A7CA85
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Aug 1, 2017, at 1:57 PM, Ted Lemon &lt;<a =
href=3D"mailto:mellon@fugue.com" class=3D"">mellon@fugue.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">What she doesn't mention is that =
there is a way to detect DNS64, so in principle a validating stub =
resolver can do DNS64 itself _post =
validation_.</span></div></blockquote></div><br class=3D""><div =
class=3D"">Oops, actually she did mention that in the last =
paragraph=E2=80=94sorry!</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_41163AA2-9973-48AD-A46C-3036C9A7CA85--


From nobody Tue Aug  1 11:54:22 2017
Return-Path: <vaibhavsinghacads@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A44901322D0 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 11:54:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XJePOGgPY7DH for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 11:54:09 -0700 (PDT)
Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B4EB1322A1 for <ietf@ietf.org>; Tue,  1 Aug 2017 11:54:09 -0700 (PDT)
Received: by mail-io0-x22f.google.com with SMTP id c74so11754323iod.4 for <ietf@ietf.org>; Tue, 01 Aug 2017 11:54:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=OxCWBS+Gkazj56GTaj591D4YTv+ywMhYheTND9zq1V0=; b=M6psWQeuvYSbc/rtz+R6x26a2+xdakClQ/FyEH3rYeMssrrJGUdWR6S7I5uvRek6iJ fJvwgAlyJ0gp3oct0SPVPyjYT9Kitio7gFW5Jeo3Tv/fkde+y3+qAqVmoNkIqYEANJd6 m5Vutp9gWJg2u8EFj0iJD0HrtdoiSUTAd4sk3G/9yw2+JEIg3xdXPieylp34/vEdav2O cBNoiHnZk5VD+/S5r3MwnjmSgf4m0ADNKPMYxYXFvFLOKomk3aKYJgXWK4+hVwfY3Jgc U9swHdw+QAWlrRvCAMmWIANNuLWSmNyICj6zC1y7KZLMv1La28xiAiV3GWyu+sATEi6w FAEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=OxCWBS+Gkazj56GTaj591D4YTv+ywMhYheTND9zq1V0=; b=h/b34jIXgaCtwlf393B1l4gg7t5K4y23hUfxaRAyArfyurXnRvz4dnuUGUbSjehSYv vzwXIBkxEUnFlRt1FZQembMViG927Q/Fp31ZGMsZFNL1yfVAzeMJ3DuDZSHbCBZJAxhR pjbyzjfWIuWfT4Yevp5gN5U65gIQaT3vY0u9v2+o4k92tUc+Q5uUUf4QVWn26Oaei1qH Gq/wRe7ZetopXTR+fz6Ff3jm0dWcKxC1M26n2a1Tr9AK5wDP26HvkDXVLAxT6FBg+D40 07S0i6UP7QDYcZRLWE3Ph6BKgzkFuZIMwZD8CxG1Ggxq5KdYX48Ul+XCZhyelHlK2mYJ 6RNw==
X-Gm-Message-State: AIVw11300Lmlw0ChlAqjogfqbjY2Bb5PrO+la7ey4ygCtsQ1pzFhXv5W 6HR9sYJtIEQ8jRibeiW9WD+nLV8Aiugt
X-Received: by 10.107.151.21 with SMTP id z21mr25542705iod.205.1501613648453;  Tue, 01 Aug 2017 11:54:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.0.208 with HTTP; Tue, 1 Aug 2017 11:54:07 -0700 (PDT)
From: vaibhav singh <vaibhavsinghacads@gmail.com>
Date: Wed, 2 Aug 2017 00:24:07 +0530
Message-ID: <CACZ1GirngAhAjXofFcVOObGsnFCg_bQUwSWmLKPps=zb3u1sfg@mail.gmail.com>
Subject: S/MIME for JMAP
To: ietf@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uj_JHfdBNQ4XrtfZgAhxSeajHvs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 18:54:20 -0000

Hi,

I was catching up on the recording of JMAP's meeting for IETF99, and
this seems really fascinating to me. I have one straight question
though; how is S/MIME going to be supported for JMAP? The JMAP mail
spec seems to be silent on this, and maybe the spec needn't concern
itself with S/MIME, but I would still like to get your views on S/MIME
over JMAP, and the potential issues which could come up with trying to
integrate S/MIME with JMAP.

Thanking you,
Vaibhav Singh


From nobody Tue Aug  1 12:09:09 2017
Return-Path: <jmvalin@jmvalin.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 158E41321C3 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 12:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jmvalin-ca.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TfBVWfbTduzQ for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 12:08:52 -0700 (PDT)
Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B59B1322E3 for <ietf@ietf.org>; Tue,  1 Aug 2017 12:08:51 -0700 (PDT)
Received: by mail-it0-x22c.google.com with SMTP id v127so13337938itd.0 for <ietf@ietf.org>; Tue, 01 Aug 2017 12:08:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jmvalin-ca.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=+lMevIy0v0cRFwHCQhGqtcKpdAqC5HP63DBgibokKDU=; b=kkh7OEnxkPMyg0glbuLiv4+hrWN/y2sPbNXZshwjcHE4/0NeWaqaPf3XQ50DHOfpzX t0su0UNs6MLwXe/nFiVTWAjPWt0G4Ti6mZWV6tQTgXcn1wROohIcWBoyRCj6LDLvqFvF HLOYThVxAp34MRhEWCwjsgtg8WQzbV6dHvt8RCTrOOsbZFxWEWB5LphkPkl/PNVumLiz /kXxWlzn5I43QDTiPHytuImg3LYwyZjugEcdd5ZJ0LVJqvCF+c3pOnbK89ByR+TtbWHQ cR88IqMT1OZseBOCqHVC7XNWO/CGTEc/IfP9q7PaAAlaipOjDrFU2a4OkflHFyz7W5uQ fIMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=+lMevIy0v0cRFwHCQhGqtcKpdAqC5HP63DBgibokKDU=; b=t+di858uXETQm5Bvrr7LTBxaapntwI9W4H7rj0JOrWdJlzYgtafQBwVT5U1Bw4HbcB Fe2kCejyKmKjFP+1bMkiLedw1ZVThPLoXZnPXSSIOot3JCfNIDge5q1wHr8VNSxfF8HF WCQNlDffsjuvoh4un7mecQFlFNXz7EoTR5nP1I/kKpOUVcW37ur0Nw3lu1RwrCKvRQ30 q46lTCGuP4k/fqRyKCV/x59zBZVnYDHPaBLwpXFOo7wg9r/bNjeDseAnaxUernbPSoeo xAXMRNbZqFMg7Zb/jQ+nlIAr/hscymzJe7/K+qmDcidUs/Pa23+o8NN4L4CiWyzKFzuS WsxA==
X-Gm-Message-State: AIVw110GZfA67sYEoN+nFnKYJLwmWlmFW2/Y610RRMKfsiDNYFVgIvcP vfaIGy/Aq2LTl1D8
X-Received: by 10.36.53.141 with SMTP id k135mr2782969ita.176.1501614530546; Tue, 01 Aug 2017 12:08:50 -0700 (PDT)
Received: from panoramix.jmvalin.ca (modemcable067.31-56-74.mc.videotron.ca. [74.56.31.67]) by smtp.gmail.com with ESMTPSA id s204sm1044357itb.13.2017.08.01.12.08.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Aug 2017 12:08:49 -0700 (PDT)
Subject: Re: Genart last call review of draft-ietf-codec-opus-update-08
To: Robert Sparks <rjsparks@nostrum.com>, gen-art@ietf.org
References: <150161082225.9505.16606445945798880852@ietfa.amsl.com>
Cc: codec@ietf.org, ietf@ietf.org, draft-ietf-codec-opus-update.all@ietf.org
From: Jean-Marc Valin <jmvalin@jmvalin.ca>
Message-ID: <7a13a147-5be7-f15b-2d93-88b0922ef543@jmvalin.ca>
Date: Tue, 1 Aug 2017 15:08:48 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <150161082225.9505.16606445945798880852@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hbWu-yYaSrdPpGoZ09HyoI0B8DQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 19:08:54 -0000

Hi Robert,

Thanks for the review. The main issue with including uuencoded
testvectors in the document is that it would cause the RFC to be around
32000 pages long. That's why RFC6716 included the source code, but not
the test vectors. Back then, we were told that the meeting material was
the only place we could put the test vectors. I don't really like doing
that, but it still beats the other options I'm aware of (unless I missed
something).

Cheers,

	Jean-Marc

On 01/08/17 02:07 PM, Robert Sparks wrote:
> Reviewer: Robert Sparks
> Review result: Ready
> 
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
> 
> For more information, please see the FAQ at
> 
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> 
> Document: draft-ietf-codec-opus-update-08
> Reviewer: Robert Sparks
> Review Date: 2017-08-01
> IETF LC End Date: 2017-08-09
> IESG Telechat date: Not scheduled for a telechat
> 
> Summary: Ready for publication as a Standards Track RFC
> 
> This document is straightforward in the changes it is making to OPUS.
> 
> My only note of sadness is that it continues to use a documentation mechanism
> started by RFC6716 of effectively making a normative reference to the
> _proceedings_ of previous IETF meetings. (Note that this document does this
> twice: once for the patch file, which is a convenience - the information is in
> the draft, and once for the updated test vectors. This is _not_ a convenience,
> the information is not in the draft. If, for whatever reason, the proceedings
> URL could not be retrieved, someone could not verify their implementation with
> the updated test vectors).
> 
> On the one hand, we've set the precedent, and we could agree to just let this
> go (I'm recommending that to the IESG with this review). On the other hand, we
> could make things _slightly_ better (or perhaps just different) by putting the
> test vectors in the doc as an appendix as a uuencoded compressed tarball.
> 


From nobody Tue Aug  1 12:28:15 2017
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAB551317CC for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 12:28:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.611
X-Spam-Level: 
X-Spam-Status: No, score=-0.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XNx3RgYHLW6C for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 12:28:10 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 63D4A126C0F for <ietf@ietf.org>; Tue,  1 Aug 2017 12:28:10 -0700 (PDT)
Received: from pps.filterd (m0049287.ppops.net [127.0.0.1]) by m0049287.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v71JPqkD032955; Tue, 1 Aug 2017 15:28:07 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049287.ppops.net-00191d01. with ESMTP id 2c2x5cvj3p-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 01 Aug 2017 15:28:06 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v71JS5KS019979; Tue, 1 Aug 2017 15:28:05 -0400
Received: from mlpi407.sfdc.sbc.com (mlpi407.sfdc.sbc.com [130.9.128.239]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v71JRvVp019842 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 1 Aug 2017 15:28:00 -0400
Received: from MISOUT7MSGHUBAC.ITServices.sbc.com (MISOUT7MSGHUBAC.itservices.sbc.com [130.9.129.147]) by mlpi407.sfdc.sbc.com (RSA Interceptor); Tue, 1 Aug 2017 19:27:38 GMT
Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.78]) by MISOUT7MSGHUBAC.ITServices.sbc.com ([130.9.129.147]) with mapi id 14.03.0319.002; Tue, 1 Aug 2017 15:27:38 -0400
From: "HANSEN, TONY L" <tony@att.com>
To: Alia Atlas <akatlas@gmail.com>
CC: IETF Discussion Mailing List <ietf@ietf.org>, Carsten Bormann <cabo@tzi.org>
Subject: Re: normative references to IANA registries
Thread-Topic: normative references to IANA registries
Thread-Index: AQHTCjb+qEkO9pZ17kChF5NdM5rkHqJuooOAgABLE4CAAHGdgIAAW8+AgAApBoA=
Date: Tue, 1 Aug 2017 19:27:37 +0000
Message-ID: <17CABFD7-19B2-4225-B99D-7718D71E25D7@att.com>
References: <523.1501530916@obiwan.sandelman.ca> <E8859A9F-7539-4C6B-962C-56E6F3323C14@tzi.org> <716.1501548333@obiwan.sandelman.ca> <06672B8B-DDC5-4362-8729-346688F587DD@tzi.org> <CAG4d1re6k-RhavZ7YFYrLD2qYg362fELdan0tN4LpiTW0VEf4w@mail.gmail.com>
In-Reply-To: <CAG4d1re6k-RhavZ7YFYrLD2qYg362fELdan0tN4LpiTW0VEf4w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.210.14.34]
Content-Type: multipart/alternative; boundary="_000_17CABFD719B24225B99D7718D71E25D7attcom_"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-08-01_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1706020000 definitions=main-1708010315
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VTNZLvjxqcnu0i_zV1Z2pl5d6u8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 19:28:13 -0000

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

QWxpYSwNCg0KPiBJIHJlYWxseSB0aGluayB0aGF0IGEgYml0IG1vcmUgdmlzaWJpbGl0eSAtIGlu
Y2x1ZGluZyBvbiB0aGUgeG1sMnJmYy5pZXRmLm9yZzxodHRwczovL3VybGRlZmVuc2UucHJvb2Zw
b2ludC5jb20vdjIvdXJsP3U9aHR0cC0zQV9feG1sMnJmYy5pZXRmLm9yZyZkPUR3TUZhUSZjPUxG
WVotbzlfSFVNZU1UU1FpY3ZqSWcmcj1LejhWZGdQVmN0RE5TTlBKNlBzQmF3Jm09VWFJZmhEQzQ1
NWJpQjg2eFNMbjA5MHJPWWRzdWh1RE54UWJSalRhc2dsMCZzPVY4STVpVmI4dzJiWkhPZUNZVl9D
dnVTbEIycDJfZjRnZ3pfclhwb2Q0VW8mZT0+IHBhZ2UgLSB3aXRoIGEgcG9pbnRlciBvciB0d28g
LSB3b3VsZCBzcGVlZCBpbnRlcmVzdCBhbmQgYWRvcHRpb24uDQoNCkNhcmUgdG8gY29udHJpYnV0
ZSB0ZXh0PyAoR29zaCwgYWxtb3N0IGxpa2Ugd29ya2luZyBvbiBhbiBJLUQuIDotKSApDQoNCiAg
ICAgICAgICAgICAgICBUb255IEhhbnNlbg0KDQpGcm9tOiBpZXRmIDxpZXRmLWJvdW5jZXNAaWV0
Zi5vcmc+IG9uIGJlaGFsZiBvZiBBbGlhIEF0bGFzIDxha2F0bGFzQGdtYWlsLmNvbT4NCkRhdGU6
IFR1ZXNkYXksIEF1Z3VzdCAxLCAyMDE3IGF0IDk6MDEgQU0NClRvOiBDYXJzdGVuIEJvcm1hbm4g
PGNhYm9AdHppLm9yZz4NCkNjOiBNaWNoYWVsIFJpY2hhcmRzb24gPG1jcitpZXRmQHNhbmRlbG1h
bi5jYT4sIElFVEYgRGlzY3Vzc2lvbiBNYWlsaW5nIExpc3QgPGlldGZAaWV0Zi5vcmc+DQpTdWJq
ZWN0OiBSZTogbm9ybWF0aXZlIHJlZmVyZW5jZXMgdG8gSUFOQSByZWdpc3RyaWVzDQoNCkNhcnN0
ZW4sDQoNCk9uIFR1ZSwgQXVnIDEsIDIwMTcgYXQgMzozMiBBTSwgQ2Fyc3RlbiBCb3JtYW5uIDxj
YWJvQHR6aS5vcmc8bWFpbHRvOmNhYm9AdHppLm9yZz4+IHdyb3RlOg0KT24gQXVnIDEsIDIwMTcs
IGF0IDAyOjQ1LCBNaWNoYWVsIFJpY2hhcmRzb24gPG1jcitpZXRmQHNhbmRlbG1hbi5jYTxtYWls
dG86bWNyJTJCaWV0ZkBzYW5kZWxtYW4uY2E+PiB3cm90ZToNCj4NCj4NCj4gQ2Fyc3RlbiBCb3Jt
YW5uIDxjYWJvQHR6aS5vcmc8bWFpbHRvOmNhYm9AdHppLm9yZz4+IHdyb3RlOg0KPj4+IFNvIEkg
d29uZGVyIG91dCBsb3VkOiBzaG91bGRuJ3QgYWxsIG9mIHRoZSBJQU5BIHJlZ2lzdHJpZXMgaGF2
ZSBjbGVhcg0KPj4+IHJlZmVyZW5jZSBmaWxlcyB0aGF0IGNvdWxkIGJlIG5vcm1hdGl2ZWx5IHJl
ZmVyZW5jZWQ/DQo+DQo+PiBUcnkgcmVmZXJlbmNpbmcsIHNheSwge3shSUFOQS5jYm9yLXRhZ3N9
fSDigJQgaXQganVzdCB3b3JrcyA6LSkNCj4NCj4gd293LiBJJ20gc3VyZSBpdCdzIGRvY3VtZW50
ZWQgaW4gc29tZSBwbGFjZSBzbyBvYnZpb3VzIEkgY2FuJ3Qgc2VlIGl0Lg0KDQpodHRwczovL3ht
bDJyZmMudG9vbHMuaWV0Zi5vcmcvPGh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92
Mi91cmw/dT1odHRwcy0zQV9feG1sMnJmYy50b29scy5pZXRmLm9yZ18mZD1Ed01GYVEmYz1MRlla
LW85X0hVTWVNVFNRaWN2aklnJnI9S3o4VmRnUFZjdEROU05QSjZQc0JhdyZtPVVhSWZoREM0NTVi
aUI4NnhTTG4wOTByT1lkc3VodUROeFFiUmpUYXNnbDAmcz10WjJiUUFDZ2tndzFtaG9aTk93TnJ4
Vjd5UXIzZ29QZnBqbmlfWk12YllnJmU9PiBpcyB0aGUgcGxhY2UgdGhhdCB0YWxrcyBhYm91dCBi
aWJ4bWw4IHJlZmVyZW5jZXMuDQprcmFtZG93bi1yZmMgaXMganVzdCBtYXBwaW5nIGFsbCB0aGUg
SUFOQS4qIHJlZmVyZW5jZXMgdG8gYmlieG1sOCwgYXMgaW4NCg0KaHR0cHM6Ly94bWwycmZjLnRv
b2xzLmlldGYub3JnL3B1YmxpYy9yZmMvYmlieG1sOC9yZWZlcmVuY2UuSUFOQS5jYm9yLXRhZ3Mu
eG1sPGh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRwcy0zQV9f
eG1sMnJmYy50b29scy5pZXRmLm9yZ19wdWJsaWNfcmZjX2JpYnhtbDhfcmVmZXJlbmNlLklBTkEu
Y2Jvci0yRHRhZ3MueG1sJmQ9RHdNRmFRJmM9TEZZWi1vOV9IVU1lTVRTUWljdmpJZyZyPUt6OFZk
Z1BWY3RETlNOUEo2UHNCYXcmbT1VYUlmaERDNDU1YmlCODZ4U0xuMDkwck9ZZHN1aHVETnhRYlJq
VGFzZ2wwJnM9UmpTZXVSS1BWT1h1WFBEaGNFUHg3a1pDZnE2YW9PdERBOVQ1bDRDUElwYyZlPT4N
Cg0KPiBJcyB0aGUgImNib3ItdGFncyIgcGFydCB0aGUgbGFzdCBwYXJ0IG9mIHRoZSBJQU5BIHJl
Z2lzdHJ5IFVSTD8NCg0KQXBwYXJlbnRseS4NCg0KYmlieG1sOC9pbmRleC5jZ2k6DQoNCiAgICBp
ZiAoJElBTkFyZWYgPX4gbSheLz9yZWZlcmVuY2UuSUFOQVsuXShbXi9dKylbLl0oeG1sfGtyYW1k
b3duKSQpKSB7DQogICAgICAgIG15ICRJQU5BcmVmID0gJDE7DQrigKYNCiAgICAgICAgICAgIG15
ICRhID0gZ2V0KCJodHRwOi8vd3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRzLyRJQU5BcmVmLzxodHRw
czovL3VybGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cC0zQV9fd3d3LmlhbmEu
b3JnX2Fzc2lnbm1lbnRzXy0yNElBTkFyZWZfJmQ9RHdNRmFRJmM9TEZZWi1vOV9IVU1lTVRTUWlj
dmpJZyZyPUt6OFZkZ1BWY3RETlNOUEo2UHNCYXcmbT1VYUlmaERDNDU1YmlCODZ4U0xuMDkwck9Z
ZHN1aHVETnhRYlJqVGFzZ2wwJnM9eXlySVdZSVM2TzFkQWVhQXZWLU1iUm8yYzBCZUhkazB0U2c1
SlVKNC1zRSZlPT7igJwpOw0KDQprcmFtZG93bi1yZmMgaXMsIHNvbWV3aGF0IGlyb25pY2FsbHkg
bWF5YmUsIHVzaW5nIHRoZSB4bWwgdmVyc2lvbiB0aGVuIDotKSAoZ2V0dGluZyB0aGUga3JhbWRv
d24gW3JlYWxseTogWUFNTF0gdmVyc2lvbiBpc24ndCBldmVuIGltcGxlbWVudGVkIGF0IHhtbDJy
ZmMuaWV0Zi5vcmc8aHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91PWh0
dHAtM0FfX3htbDJyZmMuaWV0Zi5vcmcmZD1Ed01GYVEmYz1MRllaLW85X0hVTWVNVFNRaWN2akln
JnI9S3o4VmRnUFZjdEROU05QSjZQc0JhdyZtPVVhSWZoREM0NTViaUI4NnhTTG4wOTByT1lkc3Vo
dUROeFFiUmpUYXNnbDAmcz1WOEk1aVZiOHcyYlpIT2VDWVZfQ3Z1U2xCMnAyX2Y0Z2d6X3JYcG9k
NFVvJmU9PiwgYnV0IHRoZXJlIGlzIG5vIG5lZWQgdG8pLg0KDQpJdCB3b3VsZCBiZSB2ZXJ5IGhl
bHBmdWwgdG8gIGhhdmUgdGhlIGtyYW1kb3duIHZlcnNpb24gYXQgeG1sMnJmYy5pZXRmLm9yZzxo
dHRwczovL3VybGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cC0zQV9feG1sMnJm
Yy5pZXRmLm9yZyZkPUR3TUZhUSZjPUxGWVotbzlfSFVNZU1UU1FpY3ZqSWcmcj1LejhWZGdQVmN0
RE5TTlBKNlBzQmF3Jm09VWFJZmhEQzQ1NWJpQjg2eFNMbjA5MHJPWWRzdWh1RE54UWJSalRhc2ds
MCZzPVY4STVpVmI4dzJiWkhPZUNZVl9DdnVTbEIycDJfZjRnZ3pfclhwb2Q0VW8mZT0+Lg0KU2lt
cGx5IGdvaW5nIHRvIGdpdGh1YiAoaHR0cHM6Ly9naXRodWIuY29tL2NhYm8va3JhbWRvd24tcmZj
MjYyOTxodHRwczovL3VybGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cHMtM0Ff
X2dpdGh1Yi5jb21fY2Fib19rcmFtZG93bi0yRHJmYzI2MjkmZD1Ed01GYVEmYz1MRllaLW85X0hV
TWVNVFNRaWN2aklnJnI9S3o4VmRnUFZjdEROU05QSjZQc0JhdyZtPVVhSWZoREM0NTViaUI4NnhT
TG4wOTByT1lkc3VodUROeFFiUmpUYXNnbDAmcz1BQVllX3JTU25pbzlUOVQwSGtpTzBYVl9ETDlr
eGpKMnJETHl5dTBialp3JmU9PikgIHRvIGRvd25sb2FkIGFuZCBydW4gdGhlIGtyYW1kb3duIGNv
bnZlcnRlciB0byB4bWwgZG9lc24ndCB3b3JrIHRyaXZpYWxseSBvbiBhIFdpbmRvd3MgbWFjaGlu
ZS4gIEkgZ28gdG8gaHR0cDovL3htbDJyZmMudG9vbHMuaWV0Zi5vcmcvZXhwZXJpbWVudGFsLmh0
bWwja3JhbWRvd248aHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91PWh0
dHAtM0FfX3htbDJyZmMudG9vbHMuaWV0Zi5vcmdfZXhwZXJpbWVudGFsLmh0bWwtMjNrcmFtZG93
biZkPUR3TUZhUSZjPUxGWVotbzlfSFVNZU1UU1FpY3ZqSWcmcj1LejhWZGdQVmN0RE5TTlBKNlBz
QmF3Jm09VWFJZmhEQzQ1NWJpQjg2eFNMbjA5MHJPWWRzdWh1RE54UWJSalRhc2dsMCZzPUs0c0N3
aEdfd3dURjI3SUt2eFJ1YU9MeXdvczR4bVk5eVFaZzd3TFlZNVUmZT0+IHRvIHJ1biBpdC4NCg0K
U2luY2UgdGhpcyBpcyB0aGUgb25seSB0aW1lIHRoYXQgSSB1c2Uga3JhbWRvd24gKG9yIGFueSBt
YXJrZG93biBsYW5ndWFnZSksIGl0IHdvdWxkIGJlIHF1aXRlIGhlbHBmdWwgdG8NCmFsc28gaGF2
ZSBhIHBvaW50ZXIgdG8gdGhlIHN5bnRheCB0byB1c2UuICBJIGVuZCB1cCBnb29nbGluZyBhbmQg
bG9va2luZyBhdCByYW5kb20ga3JhbWRvd24gZG9jdW1lbnRhdGlvbg0KYW5kIGhvcGluZy4gIFRo
ZSBlcnJvci1jaGVja2luZyBpcyBhbHNvIGEgYml0IGZydXN0cmF0aW5nIC0gSSBoYWQgYW4gZXh0
cmEgc3BhY2UgaW4gZnJvbnQgb2YgYSAtIGZvciBzZXBhcmF0aW5nDQp0aGUgYXV0aG9ycyBhbmQg
dGhlIGRvY3VtZW50IGZhaWxlZCB0byBjb252ZXJ0IGF0IGFsbCB3aXRoIG5vIGVycm9yLiAgTm90
IGJlaW5nIGZhbWlsaWFyIGVub3VnaCB3aXRoIGtyYW1kb3duLA0KaXQgd2FzIGNvbXBsZXRlbHkg
bm9uLW9idmlvdXMuDQoNClJlZ2FyZGxlc3Mgb2YgdGhlIGFib3ZlIGRpZ3Jlc3Npb24sIGtyYW1k
b3duLXJmYyBpcyByZWFsbHkgYXdlc29tZSBhbmQgbWFrZXMgaXQgbXVjaCBlYXNpZXIgdG8gd3Jp
dGUgZHJhZnRzIQ0KSSd2ZSBjb252ZXJ0ZWQgb3ZlciB0byBkb2luZyBzby4gIEkgcmVhbGx5IHRo
aW5rIHRoYXQgYSBiaXQgbW9yZSB2aXNpYmlsaXR5IC0gaW5jbHVkaW5nIG9uIHRoZSB4bWwycmZj
LmlldGYub3JnPGh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRw
LTNBX194bWwycmZjLmlldGYub3JnJmQ9RHdNRmFRJmM9TEZZWi1vOV9IVU1lTVRTUWljdmpJZyZy
PUt6OFZkZ1BWY3RETlNOUEo2UHNCYXcmbT1VYUlmaERDNDU1YmlCODZ4U0xuMDkwck9ZZHN1aHVE
TnhRYlJqVGFzZ2wwJnM9VjhJNWlWYjh3MmJaSE9lQ1lWX0N2dVNsQjJwMl9mNGdnel9yWHBvZDRV
byZlPT4gcGFnZSAtIHdpdGggYSBwb2ludGVyIG9yIHR3byAtIHdvdWxkIHNwZWVkIGludGVyZXN0
IGFuZCBhZG9wdGlvbi4NCg0KVGhhbmsgeW91IGZvciB5b3VyIHdvcmsgb24gdGhpcyENCkFsaWEN
Cg==

--_000_17CABFD719B24225B99D7718D71E25D7attcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <044A9130A6056B4099100C69D6127BA6@LOCAL>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iVGl0bGUiIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPSJLZXl3b3JkcyIgY29udGVu
dD0iIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUg
KGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0
IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ
cGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eTpQTWluZ0xpVTsNCglwYW5vc2UtMToyIDIgNSAwIDAgMCAwIDAgMCAwO30NCi8qIFN0eWxlIERl
ZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJ
e21hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7
DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5
cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRl
Y29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dl
ZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3Jh
dGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29MaXN0UGFyYWdyYXBoLCBsaS5Nc29MaXN0UGFyYWdyYXBo
LCBkaXYuTXNvTGlzdFBhcmFncmFwaA0KCXttc28tc3R5bGUtcHJpb3JpdHk6MzQ7DQoJbWFyZ2lu
LXRvcDowaW47DQoJbWFyZ2luLXJpZ2h0OjBpbjsNCgltYXJnaW4tYm90dG9tOjBpbjsNCgltYXJn
aW4tbGVmdDouNWluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNwYW4uZ21haWwtDQoJe21z
by1zdHlsZS1uYW1lOmdtYWlsLTt9DQpzcGFuLkVtYWlsU3R5bGUxOA0KCXttc28tc3R5bGUtdHlw
ZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCglj
b2xvcjp3aW5kb3d0ZXh0O30NCnNwYW4ubXNvSW5zDQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1v
bmx5Ow0KCW1zby1zdHlsZS1uYW1lOiIiOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7DQoJ
Y29sb3I6dGVhbDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25s
eTsNCglmb250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWlu
IDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0
aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPg0KPC9oZWFkPg0KPGJvZHkg
Ymdjb2xvcj0id2hpdGUiIGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4N
CjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BbGlhLCA8
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jmd0OyBJIHJlYWxseSB0aGluayB0aGF0IGEgYml0IG1v
cmUgdmlzaWJpbGl0eSAtIGluY2x1ZGluZyBvbiB0aGUNCjxhIGhyZWY9Imh0dHBzOi8vdXJsZGVm
ZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRwLTNBX194bWwycmZjLmlldGYub3JnJmFt
cDtkPUR3TUZhUSZhbXA7Yz1MRllaLW85X0hVTWVNVFNRaWN2aklnJmFtcDtyPUt6OFZkZ1BWY3RE
TlNOUEo2UHNCYXcmYW1wO209VWFJZmhEQzQ1NWJpQjg2eFNMbjA5MHJPWWRzdWh1RE54UWJSalRh
c2dsMCZhbXA7cz1WOEk1aVZiOHcyYlpIT2VDWVZfQ3Z1U2xCMnAyX2Y0Z2d6X3JYcG9kNFVvJmFt
cDtlPSI+DQp4bWwycmZjLmlldGYub3JnPC9hPiBwYWdlIC0gd2l0aCBhIHBvaW50ZXIgb3IgdHdv
IC0gd291bGQgc3BlZWQgaW50ZXJlc3QgYW5kIGFkb3B0aW9uLiAmbmJzcDs8bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+Q2FyZSB0byBjb250cmlidXRlIHRleHQ/IChHb3NoLCBhbG1vc3QgbGlrZSB3
b3JraW5nIG9uIGFuIEktRC4gOi0pICk8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IFRvbnkgSGFuc2VuPG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRl
cjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAw
aW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTIuMHB0O2NvbG9yOmJsYWNrIj5Gcm9tOiA8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTIuMHB0O2NvbG9yOmJsYWNrIj5pZXRmICZsdDtpZXRmLWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7
IG9uIGJlaGFsZiBvZiBBbGlhIEF0bGFzICZsdDtha2F0bGFzQGdtYWlsLmNvbSZndDs8YnI+DQo8
Yj5EYXRlOiA8L2I+VHVlc2RheSwgQXVndXN0IDEsIDIwMTcgYXQgOTowMSBBTTxicj4NCjxiPlRv
OiA8L2I+Q2Fyc3RlbiBCb3JtYW5uICZsdDtjYWJvQHR6aS5vcmcmZ3Q7PGJyPg0KPGI+Q2M6IDwv
Yj5NaWNoYWVsIFJpY2hhcmRzb24gJmx0O21jciYjNDM7aWV0ZkBzYW5kZWxtYW4uY2EmZ3Q7LCBJ
RVRGIERpc2N1c3Npb24gTWFpbGluZyBMaXN0ICZsdDtpZXRmQGlldGYub3JnJmd0Ozxicj4NCjxi
PlN1YmplY3Q6IDwvYj5SZTogbm9ybWF0aXZlIHJlZmVyZW5jZXMgdG8gSUFOQSByZWdpc3RyaWVz
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5DYXJzdGVuLCA8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBU
dWUsIEF1ZyAxLCAyMDE3IGF0IDM6MzIgQU0sIENhcnN0ZW4gQm9ybWFubiAmbHQ7PGEgaHJlZj0i
bWFpbHRvOmNhYm9AdHppLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPmNhYm9AdHppLm9yZzwvYT4mZ3Q7
IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2Jv
cmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDtt
YXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGNsYXNzPSJnbWFpbC0iPk9uIEF1ZyAxLCAyMDE3LCBhdCAwMjo0NSwgTWljaGFlbCBS
aWNoYXJkc29uICZsdDs8YSBocmVmPSJtYWlsdG86bWNyJTJCaWV0ZkBzYW5kZWxtYW4uY2EiPm1j
ciYjNDM7aWV0ZkBzYW5kZWxtYW4uY2E8L2E+Jmd0OyB3cm90ZTo8L3NwYW4+PGJyPg0KPHNwYW4g
Y2xhc3M9ImdtYWlsLSI+Jmd0Ozwvc3Bhbj48YnI+DQo8c3BhbiBjbGFzcz0iZ21haWwtIj4mZ3Q7
PC9zcGFuPjxicj4NCjxzcGFuIGNsYXNzPSJnbWFpbC0iPiZndDsgQ2Fyc3RlbiBCb3JtYW5uICZs
dDs8YSBocmVmPSJtYWlsdG86Y2Fib0B0emkub3JnIj5jYWJvQHR6aS5vcmc8L2E+Jmd0OyB3cm90
ZTo8L3NwYW4+PGJyPg0KPHNwYW4gY2xhc3M9ImdtYWlsLSI+Jmd0OyZndDsmZ3Q7IFNvIEkgd29u
ZGVyIG91dCBsb3VkOiBzaG91bGRuJ3QgYWxsIG9mIHRoZSBJQU5BIHJlZ2lzdHJpZXMgaGF2ZSBj
bGVhcjwvc3Bhbj48YnI+DQo8c3BhbiBjbGFzcz0iZ21haWwtIj4mZ3Q7Jmd0OyZndDsgcmVmZXJl
bmNlIGZpbGVzIHRoYXQgY291bGQgYmUgbm9ybWF0aXZlbHkgcmVmZXJlbmNlZD88L3NwYW4+PGJy
Pg0KPHNwYW4gY2xhc3M9ImdtYWlsLSI+Jmd0Ozwvc3Bhbj48YnI+DQo8c3BhbiBjbGFzcz0iZ21h
aWwtIj4mZ3Q7Jmd0OyBUcnkgcmVmZXJlbmNpbmcsIHNheSwge3shSUFOQS5jYm9yLXRhZ3N9fSDi
gJQgaXQganVzdCB3b3JrcyA6LSk8L3NwYW4+PGJyPg0KPHNwYW4gY2xhc3M9ImdtYWlsLSI+Jmd0
Ozwvc3Bhbj48YnI+DQo8c3BhbiBjbGFzcz0iZ21haWwtIj4mZ3Q7IHdvdy4gSSdtIHN1cmUgaXQn
cyBkb2N1bWVudGVkIGluIHNvbWUgcGxhY2Ugc28gb2J2aW91cyBJIGNhbid0IHNlZSBpdC48L3Nw
YW4+PGJyPg0KPGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29t
L3YyL3VybD91PWh0dHBzLTNBX194bWwycmZjLnRvb2xzLmlldGYub3JnXyZhbXA7ZD1Ed01GYVEm
YW1wO2M9TEZZWi1vOV9IVU1lTVRTUWljdmpJZyZhbXA7cj1LejhWZGdQVmN0RE5TTlBKNlBzQmF3
JmFtcDttPVVhSWZoREM0NTViaUI4NnhTTG4wOTByT1lkc3VodUROeFFiUmpUYXNnbDAmYW1wO3M9
dFoyYlFBQ2drZ3cxbWhvWk5Pd05yeFY3eVFyM2dvUGZwam5pX1pNdmJZZyZhbXA7ZT0iIHRhcmdl
dD0iX2JsYW5rIj5odHRwczovL3htbDJyZmMudG9vbHMuaWV0Zi5vcmcvPC9hPg0KIGlzIHRoZSBw
bGFjZSB0aGF0IHRhbGtzIGFib3V0IGJpYnhtbDggcmVmZXJlbmNlcy48YnI+DQprcmFtZG93bi1y
ZmMgaXMganVzdCBtYXBwaW5nIGFsbCB0aGUgSUFOQS4qIHJlZmVyZW5jZXMgdG8gYmlieG1sOCwg
YXMgaW48YnI+DQo8YnI+DQo8YSBocmVmPSJodHRwczovL3VybGRlZmVuc2UucHJvb2Zwb2ludC5j
b20vdjIvdXJsP3U9aHR0cHMtM0FfX3htbDJyZmMudG9vbHMuaWV0Zi5vcmdfcHVibGljX3JmY19i
aWJ4bWw4X3JlZmVyZW5jZS5JQU5BLmNib3ItMkR0YWdzLnhtbCZhbXA7ZD1Ed01GYVEmYW1wO2M9
TEZZWi1vOV9IVU1lTVRTUWljdmpJZyZhbXA7cj1LejhWZGdQVmN0RE5TTlBKNlBzQmF3JmFtcDtt
PVVhSWZoREM0NTViaUI4NnhTTG4wOTByT1lkc3VodUROeFFiUmpUYXNnbDAmYW1wO3M9UmpTZXVS
S1BWT1h1WFBEaGNFUHg3a1pDZnE2YW9PdERBOVQ1bDRDUElwYyZhbXA7ZT0iIHRhcmdldD0iX2Js
YW5rIj5odHRwczovL3htbDJyZmMudG9vbHMuaWV0Zi5vcmcvcHVibGljL3JmYy9iaWJ4bWw4L3Jl
ZmVyZW5jZS5JQU5BLmNib3ItdGFncy54bWw8L2E+PGJyPg0KPGJyPg0KPHNwYW4gY2xhc3M9Imdt
YWlsLSI+Jmd0OyBJcyB0aGUgJnF1b3Q7Y2Jvci10YWdzJnF1b3Q7IHBhcnQgdGhlIGxhc3QgcGFy
dCBvZiB0aGUgSUFOQSByZWdpc3RyeSBVUkw/PC9zcGFuPjxicj4NCjxicj4NCkFwcGFyZW50bHku
PGJyPg0KPGJyPg0KYmlieG1sOC9pbmRleC5jZ2k6PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyBp
ZiAoJElBTkFyZWYgPX4gbSheLz9yZWZlcmVuY2UuSUFOQVsuXShbXi9dJiM0MzspWy5dKHhtbHxr
cmFtZG93bikkKSkgezxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBteSAkSUFOQXJl
ZiA9ICQxOzxicj4NCuKApjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtQTWluZ0xpVSZx
dW90OyxzZXJpZiI+PGJyPg0KPC9zcGFuPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7IG15ICRhID0gZ2V0KCZxdW90OzxhIGhyZWY9Imh0dHBzOi8vdXJsZGVmZW5zZS5w
cm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRwLTNBX193d3cuaWFuYS5vcmdfYXNzaWdubWVudHNf
LTI0SUFOQXJlZl8mYW1wO2Q9RHdNRmFRJmFtcDtjPUxGWVotbzlfSFVNZU1UU1FpY3ZqSWcmYW1w
O3I9S3o4VmRnUFZjdEROU05QSjZQc0JhdyZhbXA7bT1VYUlmaERDNDU1YmlCODZ4U0xuMDkwck9Z
ZHN1aHVETnhRYlJqVGFzZ2wwJmFtcDtzPXl5cklXWUlTNk8xZEFlYUF2Vi1NYlJvMmMwQmVIZGsw
dFNnNUpVSjQtc0UmYW1wO2U9IiB0YXJnZXQ9Il9ibGFuayI+aHR0cDovL3d3dy5pYW5hLm9yZy9h
c3NpZ25tZW50cy8kSUFOQXJlZi88L2E+4oCcKTs8c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1
b3Q7UE1pbmdMaVUmcXVvdDssc2VyaWYiPjxicj4NCjxicj4NCjwvc3Bhbj5rcmFtZG93bi1yZmMg
aXMsIHNvbWV3aGF0IGlyb25pY2FsbHkgbWF5YmUsIHVzaW5nIHRoZSB4bWwgdmVyc2lvbiB0aGVu
IDotKSAoZ2V0dGluZyB0aGUga3JhbWRvd24gW3JlYWxseTogWUFNTF0gdmVyc2lvbiBpc24ndCBl
dmVuIGltcGxlbWVudGVkIGF0DQo8YSBocmVmPSJodHRwczovL3VybGRlZmVuc2UucHJvb2Zwb2lu
dC5jb20vdjIvdXJsP3U9aHR0cC0zQV9feG1sMnJmYy5pZXRmLm9yZyZhbXA7ZD1Ed01GYVEmYW1w
O2M9TEZZWi1vOV9IVU1lTVRTUWljdmpJZyZhbXA7cj1LejhWZGdQVmN0RE5TTlBKNlBzQmF3JmFt
cDttPVVhSWZoREM0NTViaUI4NnhTTG4wOTByT1lkc3VodUROeFFiUmpUYXNnbDAmYW1wO3M9VjhJ
NWlWYjh3MmJaSE9lQ1lWX0N2dVNsQjJwMl9mNGdnel9yWHBvZDRVbyZhbXA7ZT0iIHRhcmdldD0i
X2JsYW5rIj4NCnhtbDJyZmMuaWV0Zi5vcmc8L2E+LCBidXQgdGhlcmUgaXMgbm8gbmVlZCB0byku
PG86cD48L286cD48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5JdCB3b3VsZCBiZSB2ZXJ5IGhlbHBmdWwgdG8gJm5ic3A7aGF2ZSB0aGUga3JhbWRvd24g
dmVyc2lvbiBhdCA8YSBocmVmPSJodHRwczovL3VybGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIv
dXJsP3U9aHR0cC0zQV9feG1sMnJmYy5pZXRmLm9yZyZhbXA7ZD1Ed01GYVEmYW1wO2M9TEZZWi1v
OV9IVU1lTVRTUWljdmpJZyZhbXA7cj1LejhWZGdQVmN0RE5TTlBKNlBzQmF3JmFtcDttPVVhSWZo
REM0NTViaUI4NnhTTG4wOTByT1lkc3VodUROeFFiUmpUYXNnbDAmYW1wO3M9VjhJNWlWYjh3MmJa
SE9lQ1lWX0N2dVNsQjJwMl9mNGdnel9yWHBvZDRVbyZhbXA7ZT0iPg0KeG1sMnJmYy5pZXRmLm9y
ZzwvYT4uPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5TaW1wbHkgZ29pbmcgdG8gZ2l0aHViICg8YSBocmVmPSJodHRwczovL3VybGRlZmVuc2UucHJv
b2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cHMtM0FfX2dpdGh1Yi5jb21fY2Fib19rcmFtZG93bi0y
RHJmYzI2MjkmYW1wO2Q9RHdNRmFRJmFtcDtjPUxGWVotbzlfSFVNZU1UU1FpY3ZqSWcmYW1wO3I9
S3o4VmRnUFZjdEROU05QSjZQc0JhdyZhbXA7bT1VYUlmaERDNDU1YmlCODZ4U0xuMDkwck9ZZHN1
aHVETnhRYlJqVGFzZ2wwJmFtcDtzPUFBWWVfclNTbmlvOVQ5VDBIa2lPMFhWX0RMOWt4akoyckRM
eXl1MGJqWncmYW1wO2U9Ij5odHRwczovL2dpdGh1Yi5jb20vY2Fiby9rcmFtZG93bi1yZmMyNjI5
PC9hPikmbmJzcDsNCiB0byBkb3dubG9hZCBhbmQgcnVuIHRoZSBrcmFtZG93biBjb252ZXJ0ZXIg
dG8geG1sIGRvZXNuJ3Qgd29yayB0cml2aWFsbHkgb24gYSBXaW5kb3dzIG1hY2hpbmUuJm5ic3A7
IEkgZ28gdG8NCjxhIGhyZWY9Imh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91
cmw/dT1odHRwLTNBX194bWwycmZjLnRvb2xzLmlldGYub3JnX2V4cGVyaW1lbnRhbC5odG1sLTIz
a3JhbWRvd24mYW1wO2Q9RHdNRmFRJmFtcDtjPUxGWVotbzlfSFVNZU1UU1FpY3ZqSWcmYW1wO3I9
S3o4VmRnUFZjdEROU05QSjZQc0JhdyZhbXA7bT1VYUlmaERDNDU1YmlCODZ4U0xuMDkwck9ZZHN1
aHVETnhRYlJqVGFzZ2wwJmFtcDtzPUs0c0N3aEdfd3dURjI3SUt2eFJ1YU9MeXdvczR4bVk5eVFa
Zzd3TFlZNVUmYW1wO2U9Ij4NCmh0dHA6Ly94bWwycmZjLnRvb2xzLmlldGYub3JnL2V4cGVyaW1l
bnRhbC5odG1sI2tyYW1kb3duPC9hPiB0byBydW4gaXQuPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlNpbmNlIHRoaXMgaXMgdGhlIG9ubHkgdGlt
ZSB0aGF0IEkgdXNlIGtyYW1kb3duIChvciBhbnkgbWFya2Rvd24gbGFuZ3VhZ2UpLCBpdCB3b3Vs
ZCBiZSBxdWl0ZSBoZWxwZnVsIHRvPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5hbHNvIGhhdmUgYSBwb2ludGVyIHRvIHRoZSBzeW50YXggdG8gdXNl
LiZuYnNwOyBJIGVuZCB1cCBnb29nbGluZyBhbmQgbG9va2luZyBhdCByYW5kb20ga3JhbWRvd24g
ZG9jdW1lbnRhdGlvbiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+YW5kIGhvcGluZy4mbmJzcDsgVGhlIGVycm9yLWNoZWNraW5nIGlzIGFs
c28gYSBiaXQgZnJ1c3RyYXRpbmcgLSBJIGhhZCBhbiBleHRyYSBzcGFjZSBpbiBmcm9udCBvZiBh
IC0gZm9yIHNlcGFyYXRpbmc8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPnRoZSBhdXRob3JzIGFuZCB0aGUgZG9jdW1lbnQgZmFpbGVkIHRvIGNvbnZl
cnQgYXQgYWxsIHdpdGggbm8gZXJyb3IuJm5ic3A7IE5vdCBiZWluZyBmYW1pbGlhciBlbm91Z2gg
d2l0aCBrcmFtZG93biw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPml0IHdhcyBjb21wbGV0ZWx5IG5vbi1vYnZpb3VzLiZuYnNwOzxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5SZWdhcmRsZXNzIG9m
IHRoZSBhYm92ZSBkaWdyZXNzaW9uLCBrcmFtZG93bi1yZmMgaXMgcmVhbGx5IGF3ZXNvbWUgYW5k
IG1ha2VzIGl0IG11Y2ggZWFzaWVyIHRvIHdyaXRlIGRyYWZ0cyE8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkndmUgY29udmVydGVkIG92ZXIgdG8g
ZG9pbmcgc28uJm5ic3A7IEkgcmVhbGx5IHRoaW5rIHRoYXQgYSBiaXQgbW9yZSB2aXNpYmlsaXR5
IC0gaW5jbHVkaW5nIG9uIHRoZQ0KPGEgaHJlZj0iaHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9p
bnQuY29tL3YyL3VybD91PWh0dHAtM0FfX3htbDJyZmMuaWV0Zi5vcmcmYW1wO2Q9RHdNRmFRJmFt
cDtjPUxGWVotbzlfSFVNZU1UU1FpY3ZqSWcmYW1wO3I9S3o4VmRnUFZjdEROU05QSjZQc0JhdyZh
bXA7bT1VYUlmaERDNDU1YmlCODZ4U0xuMDkwck9ZZHN1aHVETnhRYlJqVGFzZ2wwJmFtcDtzPVY4
STVpVmI4dzJiWkhPZUNZVl9DdnVTbEIycDJfZjRnZ3pfclhwb2Q0VW8mYW1wO2U9Ij4NCnhtbDJy
ZmMuaWV0Zi5vcmc8L2E+IHBhZ2UgLSB3aXRoIGEgcG9pbnRlciBvciB0d28gLSB3b3VsZCBzcGVl
ZCBpbnRlcmVzdCBhbmQgYWRvcHRpb24uICZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFuayB5b3UgZm9yIHlvdXIgd29yayBvbiB0
aGlzITxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
QWxpYTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rp
dj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_17CABFD719B24225B99D7718D71E25D7attcom_--


From nobody Tue Aug  1 12:31:30 2017
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8751A126C0F for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 12:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.71
X-Spam-Level: 
X-Spam-Status: No, score=-0.71 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, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qOocwgsv1YOQ for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 12:31:25 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60A381322F8 for <ietf@ietf.org>; Tue,  1 Aug 2017 12:31:25 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id t201so23642500wmt.0 for <ietf@ietf.org>; Tue, 01 Aug 2017 12:31:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3Sfz83yKWrGtTEPvh18eIftQSPp+WNgsd6RXqj/8EfA=; b=UT6QRaeaHKpria8xQoIsf9pyYu8f9oZLmpXvCCcv9aj6JJnvKBUBLMnSZJY10KRViB FyZYmYu6GUp2A00kU1KUHIw9Y6c0as30/oqoIhnLillvL7GMKTTIiFEDCWbfjYooZD7A kE18a9watmeCnZQZs2NP7zBypfKERBi7qTsCEN5hAvEvssIfEWtRh+jfsRKvFmn2v/2B xErkSnXcEG/XWi+a1Aik9ppUbfw6+04oxDZvhL40asSFc5Reod+b/vzpCiDRb5Bn8U0Y wZIeoJITjRVfWEOgjSZSCFyX14McxG2yn+OyXgIgs1Qg+YHY4Yqd7VojXzi/xf04ucOT tKCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=3Sfz83yKWrGtTEPvh18eIftQSPp+WNgsd6RXqj/8EfA=; b=tthR9c7IunrmeBzsZzg5kuyUM+9s7QLzF7aWF+pB5l3PuTLrBthq28WVi762gJ8W3N X45mw35XnipOlZgeE+20mHFbyEM7jB4jC4X9OWyDxYRmMjlrhreCNF3RicrnNz5NTYLG 8vL4yNgymRqyHwIgW/+ABKaTZ8twint2XhBpdTwSkwP3wDCZ7Ik4w3egl4kz9uIIC0IY prFrYHcu2+V99boCPPQ6DpplPfLzOYtCCTJ4Hs9QgN6Phlo0sgs/+x2lhVs89Go/TBR+ w0fA+rRuUVnUQgUOsMx6Jpvd5Tmuso6hhb5aJoOiTzsivFMh3nlM0/niMFvzy2PLFGas uGDw==
X-Gm-Message-State: AIVw11074TBYZIT3uUWz1o7BmBzN/9+CxUBXA4MZPBhx/82RUJvrr9dQ 66LVhXuAhUNPs3pLYHQ87NacvgGeJw==
X-Received: by 10.28.131.3 with SMTP id f3mr2258733wmd.181.1501615883658; Tue, 01 Aug 2017 12:31:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.154.108 with HTTP; Tue, 1 Aug 2017 12:31:22 -0700 (PDT)
In-Reply-To: <17CABFD7-19B2-4225-B99D-7718D71E25D7@att.com>
References: <523.1501530916@obiwan.sandelman.ca> <E8859A9F-7539-4C6B-962C-56E6F3323C14@tzi.org> <716.1501548333@obiwan.sandelman.ca> <06672B8B-DDC5-4362-8729-346688F587DD@tzi.org> <CAG4d1re6k-RhavZ7YFYrLD2qYg362fELdan0tN4LpiTW0VEf4w@mail.gmail.com> <17CABFD7-19B2-4225-B99D-7718D71E25D7@att.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Tue, 1 Aug 2017 15:31:22 -0400
Message-ID: <CAG4d1rcSNFqVM5THgaGFyvv=652zM3kfZhSYy31f9-0NGt3p9A@mail.gmail.com>
Subject: Re: normative references to IANA registries
To: "HANSEN, TONY L" <tony@att.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>, Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary="001a1144323655ac6f0555b63103"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-ogFIa6ukpfUeL4e7CUIc-LQ4vg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 19:31:29 -0000

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

Tony,

On Tue, Aug 1, 2017 at 3:27 PM, HANSEN, TONY L <tony@att.com> wrote:

> Alia,
>
>
>
> > I really think that a bit more visibility - including on the
> xml2rfc.ietf.org
> <https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__xml2rfc.ietf.org&d=
=3DDwMFaQ&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DKz8VdgPVctDNSNPJ6PsBaw&m=3DUaIfhDC=
455biB86xSLn090rOYdsuhuDNxQbRjTasgl0&s=3DV8I5iVb8w2bZHOeCYV_CvuSlB2p2_f4ggz=
_rXpod4Uo&e=3D>
> page - with a pointer or two - would speed interest and adoption.
>
>
>
> Care to contribute text? (Gosh, almost like working on an I-D. :-) )
>
>
Sure - but as part of a group.  I can't tell folks - look here for details
on markdown without knowing it is what is implemented.  It'd be nice to be
able to see and retrieve markdown versions of drafts - if available - but
that's a datatracker/tools team effort.
I put some energy into encouraging at least a wiki with best practices,
including for this, a couple years ago but my arm-twisting foo wasn't
strong/good enough then.

Regards,
Alia


>
>                 Tony Hansen
>
>
>
> *From: *ietf <ietf-bounces@ietf.org> on behalf of Alia Atlas <
> akatlas@gmail.com>
> *Date: *Tuesday, August 1, 2017 at 9:01 AM
> *To: *Carsten Bormann <cabo@tzi.org>
> *Cc: *Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion Mailing
> List <ietf@ietf.org>
> *Subject: *Re: normative references to IANA registries
>
>
>
> Carsten,
>
>
>
> On Tue, Aug 1, 2017 at 3:32 AM, Carsten Bormann <cabo@tzi.org> wrote:
>
> On Aug 1, 2017, at 02:45, Michael Richardson <mcr+ietf@sandelman.ca>
> wrote:
> >
> >
> > Carsten Bormann <cabo@tzi.org> wrote:
> >>> So I wonder out loud: shouldn't all of the IANA registries have clear
> >>> reference files that could be normatively referenced?
> >
> >> Try referencing, say, {{!IANA.cbor-tags}} =E2=80=94 it just works :-)
> >
> > wow. I'm sure it's documented in some place so obvious I can't see it.
>
> https://xml2rfc.tools.ietf.org/
> <https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__xml2rfc.tools.iet=
f.org_&d=3DDwMFaQ&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DKz8VdgPVctDNSNPJ6PsBaw&m=
=3DUaIfhDC455biB86xSLn090rOYdsuhuDNxQbRjTasgl0&s=3DtZ2bQACgkgw1mhoZNOwNrxV7=
yQr3goPfpjni_ZMvbYg&e=3D>
> is the place that talks about bibxml8 references.
> kramdown-rfc is just mapping all the IANA.* references to bibxml8, as in
>
> https://xml2rfc.tools.ietf.org/public/rfc/bibxml8/
> reference.IANA.cbor-tags.xml
> <https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__xml2rfc.tools.iet=
f.org_public_rfc_bibxml8_reference.IANA.cbor-2Dtags.xml&d=3DDwMFaQ&c=3DLFYZ=
-o9_HUMeMTSQicvjIg&r=3DKz8VdgPVctDNSNPJ6PsBaw&m=3DUaIfhDC455biB86xSLn090rOY=
dsuhuDNxQbRjTasgl0&s=3DRjSeuRKPVOXuXPDhcEPx7kZCfq6aoOtDA9T5l4CPIpc&e=3D>
>
> > Is the "cbor-tags" part the last part of the IANA registry URL?
>
> Apparently.
>
> bibxml8/index.cgi:
>
>     if ($IANAref =3D~ m(^/?reference.IANA[.]([^/]+)[.](xml|kramdown)$)) {
>         my $IANAref =3D $1;
> =E2=80=A6
>             my $a =3D get("http://www.iana.org/assignments/$IANAref/
> <https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__www.iana.org_assig=
nments_-24IANAref_&d=3DDwMFaQ&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DKz8VdgPVctDNSN=
PJ6PsBaw&m=3DUaIfhDC455biB86xSLn090rOYdsuhuDNxQbRjTasgl0&s=3DyyrIWYIS6O1dAe=
aAvV-MbRo2c0BeHdk0tSg5JUJ4-sE&e=3D>
> =E2=80=9C);
>
> kramdown-rfc is, somewhat ironically maybe, using the xml version then :-=
)
> (getting the kramdown [really: YAML] version isn't even implemented at
> xml2rfc.ietf.org
> <https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__xml2rfc.ietf.org&d=
=3DDwMFaQ&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DKz8VdgPVctDNSNPJ6PsBaw&m=3DUaIfhDC=
455biB86xSLn090rOYdsuhuDNxQbRjTasgl0&s=3DV8I5iVb8w2bZHOeCYV_CvuSlB2p2_f4ggz=
_rXpod4Uo&e=3D>,
> but there is no need to).
>
>
>
> It would be very helpful to  have the kramdown version at xml2rfc.ietf.or=
g
> <https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__xml2rfc.ietf.org&d=
=3DDwMFaQ&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DKz8VdgPVctDNSNPJ6PsBaw&m=3DUaIfhDC=
455biB86xSLn090rOYdsuhuDNxQbRjTasgl0&s=3DV8I5iVb8w2bZHOeCYV_CvuSlB2p2_f4ggz=
_rXpod4Uo&e=3D>
> .
>
> Simply going to github (https://github.com/cabo/kramdown-rfc2629
> <https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_cabo_k=
ramdown-2Drfc2629&d=3DDwMFaQ&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DKz8VdgPVctDNSNP=
J6PsBaw&m=3DUaIfhDC455biB86xSLn090rOYdsuhuDNxQbRjTasgl0&s=3DAAYe_rSSnio9T9T=
0HkiO0XV_DL9kxjJ2rDLyyu0bjZw&e=3D>)
> to download and run the kramdown converter to xml doesn't work trivially =
on
> a Windows machine.  I go to http://xml2rfc.tools.ietf.org/
> experimental.html#kramdown
> <https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__xml2rfc.tools.ietf=
.org_experimental.html-23kramdown&d=3DDwMFaQ&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=
=3DKz8VdgPVctDNSNPJ6PsBaw&m=3DUaIfhDC455biB86xSLn090rOYdsuhuDNxQbRjTasgl0&s=
=3DK4sCwhG_wwTF27IKvxRuaOLywos4xmY9yQZg7wLYY5U&e=3D>
> to run it.
>
>
>
> Since this is the only time that I use kramdown (or any markdown
> language), it would be quite helpful to
>
> also have a pointer to the syntax to use.  I end up googling and looking
> at random kramdown documentation
>
> and hoping.  The error-checking is also a bit frustrating - I had an extr=
a
> space in front of a - for separating
>
> the authors and the document failed to convert at all with no error.  Not
> being familiar enough with kramdown,
>
> it was completely non-obvious.
>
>
>
> Regardless of the above digression, kramdown-rfc is really awesome and
> makes it much easier to write drafts!
>
> I've converted over to doing so.  I really think that a bit more
> visibility - including on the xml2rfc.ietf.org
> <https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__xml2rfc.ietf.org&d=
=3DDwMFaQ&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DKz8VdgPVctDNSNPJ6PsBaw&m=3DUaIfhDC=
455biB86xSLn090rOYdsuhuDNxQbRjTasgl0&s=3DV8I5iVb8w2bZHOeCYV_CvuSlB2p2_f4ggz=
_rXpod4Uo&e=3D>
> page - with a pointer or two - would speed interest and adoption.
>
>
>
> Thank you for your work on this!
>
> Alia
>

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

<div dir=3D"ltr">Tony,<div><br></div><div>On Tue, Aug 1, 2017 at 3:27 PM, H=
ANSEN, TONY L <span dir=3D"ltr">&lt;<a href=3D"mailto:tony@att.com" target=
=3D"_blank">tony@att.com</a>&gt;</span> wrote:<br></div><div class=3D"gmail=
_extra"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">







<div bgcolor=3D"white" lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_2471055081724861076WordSection1">
<p class=3D"MsoNormal">Alia, <u></u><u></u></p><span class=3D"">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">&gt; I really think that a bit more visibility - inc=
luding on the
<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__xml2rfc.ie=
tf.org&amp;d=3DDwMFaQ&amp;c=3DLFYZ-o9_HUMeMTSQicvjIg&amp;r=3DKz8VdgPVctDNSN=
PJ6PsBaw&amp;m=3DUaIfhDC455biB86xSLn090rOYdsuhuDNxQbRjTasgl0&amp;s=3DV8I5iV=
b8w2bZHOeCYV_CvuSlB2p2_f4ggz_rXpod4Uo&amp;e=3D" target=3D"_blank">
xml2rfc.ietf.org</a> page - with a pointer or two - would speed interest an=
d adoption. =C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</span><p class=3D"MsoNormal">Care to contribute text? (Gosh, almost like w=
orking on an I-D. :-) )<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u></p></div></div></blockquote><div><br></div><=
div>Sure - but as part of a group.=C2=A0 I can&#39;t tell folks - look here=
 for details on markdown without knowing it is what is implemented.=C2=A0 I=
t&#39;d be nice to be able to see and retrieve markdown versions of drafts =
- if available - but that&#39;s a datatracker/tools team effort.</div><div>=
I put some energy into encouraging at least a wiki with best practices, inc=
luding for this, a couple years ago but my arm-twisting foo wasn&#39;t stro=
ng/good enough then.</div><div><br></div><div>Regards,</div><div>Alia=C2=A0=
</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor=3D"white" =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"m_2471055081724=
861076WordSection1"><p class=3D"MsoNormal">=C2=A0<u></u></p>
<p class=3D"MsoNormal">=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 Tony Hansen<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:12.0pt;color:black">From=
: </span></b><span style=3D"font-size:12.0pt;color:black">ietf &lt;<a href=
=3D"mailto:ietf-bounces@ietf.org" target=3D"_blank">ietf-bounces@ietf.org</=
a>&gt; on behalf of Alia Atlas &lt;<a href=3D"mailto:akatlas@gmail.com" tar=
get=3D"_blank">akatlas@gmail.com</a>&gt;<br>
<b>Date: </b>Tuesday, August 1, 2017 at 9:01 AM<br>
<b>To: </b>Carsten Bormann &lt;<a href=3D"mailto:cabo@tzi.org" target=3D"_b=
lank">cabo@tzi.org</a>&gt;<br>
<b>Cc: </b>Michael Richardson &lt;<a href=3D"mailto:mcr%2Bietf@sandelman.ca=
" target=3D"_blank">mcr+ietf@sandelman.ca</a>&gt;, IETF Discussion Mailing =
List &lt;<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</=
a>&gt;<br>
<b>Subject: </b>Re: normative references to IANA registries<u></u><u></u></=
span></p>
</div><div><div class=3D"h5">
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Carsten, <u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Tue, Aug 1, 2017 at 3:32 AM, Carsten Bormann &lt;=
<a href=3D"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org</a>&gt; wrot=
e:<u></u><u></u></p>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class=3D"MsoNormal"><span class=3D"m_2471055081724861076gmail-">On Aug 1=
, 2017, at 02:45, Michael Richardson &lt;<a href=3D"mailto:mcr%2Bietf@sande=
lman.ca" target=3D"_blank">mcr+ietf@sandelman.ca</a>&gt; wrote:</span><br>
<span class=3D"m_2471055081724861076gmail-">&gt;</span><br>
<span class=3D"m_2471055081724861076gmail-">&gt;</span><br>
<span class=3D"m_2471055081724861076gmail-">&gt; Carsten Bormann &lt;<a hre=
f=3D"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org</a>&gt; wrote:</sp=
an><br>
<span class=3D"m_2471055081724861076gmail-">&gt;&gt;&gt; So I wonder out lo=
ud: shouldn&#39;t all of the IANA registries have clear</span><br>
<span class=3D"m_2471055081724861076gmail-">&gt;&gt;&gt; reference files th=
at could be normatively referenced?</span><br>
<span class=3D"m_2471055081724861076gmail-">&gt;</span><br>
<span class=3D"m_2471055081724861076gmail-">&gt;&gt; Try referencing, say, =
{{!IANA.cbor-tags}} =E2=80=94 it just works :-)</span><br>
<span class=3D"m_2471055081724861076gmail-">&gt;</span><br>
<span class=3D"m_2471055081724861076gmail-">&gt; wow. I&#39;m sure it&#39;s=
 documented in some place so obvious I can&#39;t see it.</span><br>
<br>
<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__xml2rfc.t=
ools.ietf.org_&amp;d=3DDwMFaQ&amp;c=3DLFYZ-o9_HUMeMTSQicvjIg&amp;r=3DKz8Vdg=
PVctDNSNPJ6PsBaw&amp;m=3DUaIfhDC455biB86xSLn090rOYdsuhuDNxQbRjTasgl0&amp;s=
=3DtZ2bQACgkgw1mhoZNOwNrxV7yQr3goPfpjni_ZMvbYg&amp;e=3D" target=3D"_blank">=
https://xml2rfc.tools.ietf.<wbr>org/</a>
 is the place that talks about bibxml8 references.<br>
kramdown-rfc is just mapping all the IANA.* references to bibxml8, as in<br=
>
<br>
<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__xml2rfc.t=
ools.ietf.org_public_rfc_bibxml8_reference.IANA.cbor-2Dtags.xml&amp;d=3DDwM=
FaQ&amp;c=3DLFYZ-o9_HUMeMTSQicvjIg&amp;r=3DKz8VdgPVctDNSNPJ6PsBaw&amp;m=3DU=
aIfhDC455biB86xSLn090rOYdsuhuDNxQbRjTasgl0&amp;s=3DRjSeuRKPVOXuXPDhcEPx7kZC=
fq6aoOtDA9T5l4CPIpc&amp;e=3D" target=3D"_blank">https://xml2rfc.tools.ietf.=
<wbr>org/public/rfc/bibxml8/<wbr>reference.IANA.cbor-tags.xml</a><br>
<br>
<span class=3D"m_2471055081724861076gmail-">&gt; Is the &quot;cbor-tags&quo=
t; part the last part of the IANA registry URL?</span><br>
<br>
Apparently.<br>
<br>
bibxml8/index.cgi:<br>
<br>
=C2=A0 =C2=A0 if ($IANAref =3D~ m(^/?reference.IANA[.]([^/]+)[<wbr>.](xml|k=
ramdown)$)) {<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 my $IANAref =3D $1;<br>
=E2=80=A6<span style=3D"font-family:&quot;PMingLiU&quot;,serif"><br>
</span>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 my $a =3D get(&quot;<a hre=
f=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__www.iana.org_ass=
ignments_-24IANAref_&amp;d=3DDwMFaQ&amp;c=3DLFYZ-o9_HUMeMTSQicvjIg&amp;r=3D=
Kz8VdgPVctDNSNPJ6PsBaw&amp;m=3DUaIfhDC455biB86xSLn090rOYdsuhuDNxQbRjTasgl0&=
amp;s=3DyyrIWYIS6O1dAeaAvV-MbRo2c0BeHdk0tSg5JUJ4-sE&amp;e=3D" target=3D"_bl=
ank">http://www.iana.org/<wbr>assignments/$IANAref/</a>=E2=80=9C);<span sty=
le=3D"font-family:&quot;PMingLiU&quot;,serif"><br>
<br>
</span>kramdown-rfc is, somewhat ironically maybe, using the xml version th=
en :-) (getting the kramdown [really: YAML] version isn&#39;t even implemen=
ted at
<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__xml2rfc.ie=
tf.org&amp;d=3DDwMFaQ&amp;c=3DLFYZ-o9_HUMeMTSQicvjIg&amp;r=3DKz8VdgPVctDNSN=
PJ6PsBaw&amp;m=3DUaIfhDC455biB86xSLn090rOYdsuhuDNxQbRjTasgl0&amp;s=3DV8I5iV=
b8w2bZHOeCYV_CvuSlB2p2_f4ggz_rXpod4Uo&amp;e=3D" target=3D"_blank">
xml2rfc.ietf.org</a>, but there is no need to).<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">It would be very helpful to =C2=A0have the kramdown =
version at <a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A_=
_xml2rfc.ietf.org&amp;d=3DDwMFaQ&amp;c=3DLFYZ-o9_HUMeMTSQicvjIg&amp;r=3DKz8=
VdgPVctDNSNPJ6PsBaw&amp;m=3DUaIfhDC455biB86xSLn090rOYdsuhuDNxQbRjTasgl0&amp=
;s=3DV8I5iVb8w2bZHOeCYV_CvuSlB2p2_f4ggz_rXpod4Uo&amp;e=3D" target=3D"_blank=
">
xml2rfc.ietf.org</a>.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Simply going to github (<a href=3D"https://urldefens=
e.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_cabo_kramdown-2Drfc2629&am=
p;d=3DDwMFaQ&amp;c=3DLFYZ-o9_HUMeMTSQicvjIg&amp;r=3DKz8VdgPVctDNSNPJ6PsBaw&=
amp;m=3DUaIfhDC455biB86xSLn090rOYdsuhuDNxQbRjTasgl0&amp;s=3DAAYe_rSSnio9T9T=
0HkiO0XV_DL9kxjJ2rDLyyu0bjZw&amp;e=3D" target=3D"_blank">https://github.com=
/cabo/<wbr>kramdown-rfc2629</a>)=C2=A0
 to download and run the kramdown converter to xml doesn&#39;t work trivial=
ly on a Windows machine.=C2=A0 I go to
<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__xml2rfc.to=
ols.ietf.org_experimental.html-23kramdown&amp;d=3DDwMFaQ&amp;c=3DLFYZ-o9_HU=
MeMTSQicvjIg&amp;r=3DKz8VdgPVctDNSNPJ6PsBaw&amp;m=3DUaIfhDC455biB86xSLn090r=
OYdsuhuDNxQbRjTasgl0&amp;s=3DK4sCwhG_wwTF27IKvxRuaOLywos4xmY9yQZg7wLYY5U&am=
p;e=3D" target=3D"_blank">
http://xml2rfc.tools.ietf.org/<wbr>experimental.html#kramdown</a> to run it=
.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Since this is the only time that I use kramdown (or =
any markdown language), it would be quite helpful to<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">also have a pointer to the syntax to use.=C2=A0 I en=
d up googling and looking at random kramdown documentation=C2=A0<u></u><u><=
/u></p>
</div>
<div>
<p class=3D"MsoNormal">and hoping.=C2=A0 The error-checking is also a bit f=
rustrating - I had an extra space in front of a - for separating<u></u><u><=
/u></p>
</div>
<div>
<p class=3D"MsoNormal">the authors and the document failed to convert at al=
l with no error.=C2=A0 Not being familiar enough with kramdown,<u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal">it was completely non-obvious.=C2=A0<u></u><u></u></=
p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Regardless of the above digression, kramdown-rfc is =
really awesome and makes it much easier to write drafts!<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I&#39;ve converted over to doing so.=C2=A0 I really =
think that a bit more visibility - including on the
<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__xml2rfc.ie=
tf.org&amp;d=3DDwMFaQ&amp;c=3DLFYZ-o9_HUMeMTSQicvjIg&amp;r=3DKz8VdgPVctDNSN=
PJ6PsBaw&amp;m=3DUaIfhDC455biB86xSLn090rOYdsuhuDNxQbRjTasgl0&amp;s=3DV8I5iV=
b8w2bZHOeCYV_CvuSlB2p2_f4ggz_rXpod4Uo&amp;e=3D" target=3D"_blank">
xml2rfc.ietf.org</a> page - with a pointer or two - would speed interest an=
d adoption. =C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Thank you for your work on this!<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Alia<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div></div></div>
</div>

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

--001a1144323655ac6f0555b63103--


From nobody Tue Aug  1 12:32:49 2017
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76D9F1322F8 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 12:32:47 -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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ve32ubHTeOqW for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 12:32:46 -0700 (PDT)
Received: from mailhost.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 4ABF9129B34 for <ietf@ietf.org>; Tue,  1 Aug 2017 12:32:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v71JWfa4023360; Tue, 1 Aug 2017 21:32:41 +0200 (CEST)
Received: from client-0048.vpn.uni-bremen.de (client-0048.vpn.uni-bremen.de [134.102.107.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3xMRL06l8FzDMC6; Tue,  1 Aug 2017 21:32:40 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: normative references to IANA registries
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <17CABFD7-19B2-4225-B99D-7718D71E25D7@att.com>
Date: Tue, 1 Aug 2017 21:32:40 +0200
Cc: Alia Atlas <akatlas@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-Mao-Original-Outgoing-Id: 523308760.220246-767e56c877fac041aba009a302ef7e24
Content-Transfer-Encoding: quoted-printable
Message-Id: <563255C0-11AD-4902-9A3F-D403E1A2A363@tzi.org>
References: <523.1501530916@obiwan.sandelman.ca> <E8859A9F-7539-4C6B-962C-56E6F3323C14@tzi.org> <716.1501548333@obiwan.sandelman.ca> <06672B8B-DDC5-4362-8729-346688F587DD@tzi.org> <CAG4d1re6k-RhavZ7YFYrLD2qYg362fELdan0tN4LpiTW0VEf4w@mail.gmail.com> <17CABFD7-19B2-4225-B99D-7718D71E25D7@att.com>
To: "HANSEN, TONY L" <tony@att.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/M_Heo_IG7rqcVZe6525KWysJ8GQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 19:32:47 -0000

On Aug 1, 2017, at 21:27, HANSEN, TONY L <tony@att.com> wrote:
>=20
> Care to contribute text? (Gosh, almost like working on an I-D. :-) )

I have this project of coming up with an I-D describing kramdown-rfc.
I even have a TOC and a collaborator lined up.
Now just for some time to actually do the work...
Somehow the normative stuff always gets precedence.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Tue Aug  1 12:48:35 2017
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 625EA131C80 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 12:48:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=Ni3FI8WM; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=F6SOXRji
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TDp4346Xvprk for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 12:48:32 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE61C131C7D for <ietf@ietf.org>; Tue,  1 Aug 2017 12:48:32 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 4052A20BB7; Tue,  1 Aug 2017 15:48:32 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Tue, 01 Aug 2017 15:48:32 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=0Z8a2/U7orUlKPrfjh z7nCNQqcsLgfeaoSOBU2lqZmk=; b=Ni3FI8WMwxZbM/WOcPsW+bD2j/bmOvPfLH 9EevZJYMjsnA5bk5SNr54yq9jdyA5bRABU8Sfh58jXJkhNE0a8jUwm/YTUXfVtwh pWHHKKVa/G/zbPi98fxYYuGHup82m1NyTQJ7GFt3KAPIgKYqmDF98oHtDRzsphME NnTNecgWeOtU61u9rDTMVZacxyuHfPFhppAx4x4tU5KsQvyIeXyGZnlxfBKgLNO4 E4BdxfqtR5fy6QN+G7l4Yy+g5SjaVWSNYNfeHjXLcLTwhsJ2IP9yx7rmvSpvxeJ3 +EikFG7fPhT65g0nJ90EtTwOYTfpBFOkmcQVU2wiM7M+CQ6Z6AhQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=0Z8a2/U7orUlKPrfjhz7nCNQqcsLgfeaoSOBU2lqZmk=; b=F6SOXRji u0GUkVUfx7VCiwhMmYLjJfgbQjBzR+88uKmQQIrn+UTSjbRYfV+Tv1DDnXnZk89W 57Zh3+YNbeC9up5/fItYnerEXZbZA87cw0nXvg8xC6cHPKK2/TqJcY8eX8HhzGe9 3vxgI5NdIe3XCjIzxNOczXBppifRA4xVKyusO4JvslenvFSWr+Bhmy2WZKRSVVxu SaNFc7dp81XgMlCzk+LddMzTvd0hF+EMy0jWNz+f2WAU5j7dOxBB1lH8686um3/s s6SOZN09CQ/0gRt8hbHc5z1s3YwDmEoShO/X3TG2qeDbpXmk5xahY0zjpWI5XEi5 ammAdoJ088Ip2Q==
X-ME-Sender: <xms:ENuAWZkiCpzL3k4g_C-XWSuDMH5ZXZWMChf8W1XCtRs52PYifwWLCw>
X-Sasl-enc: /H/jDdl42ZlQYyzeX9BK9b3l16GcYgynDf6uXC0xD+Bc 1501616911
Received: from [192.168.1.14] (cpe-124-188-19-231.hdbq1.win.bigpond.net.au [124.188.19.231]) by mail.messagingengine.com (Postfix) with ESMTPA id DBFB07E4AA; Tue,  1 Aug 2017 15:48:30 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: normative references to IANA registries
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <563255C0-11AD-4902-9A3F-D403E1A2A363@tzi.org>
Date: Wed, 2 Aug 2017 05:48:27 +1000
Cc: "HANSEN, TONY L" <tony@att.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <033EE4F9-A9D3-4AD9-BC88-63C6C2CA6DB7@mnot.net>
References: <523.1501530916@obiwan.sandelman.ca> <E8859A9F-7539-4C6B-962C-56E6F3323C14@tzi.org> <716.1501548333@obiwan.sandelman.ca> <06672B8B-DDC5-4362-8729-346688F587DD@tzi.org> <CAG4d1re6k-RhavZ7YFYrLD2qYg362fELdan0tN4LpiTW0VEf4w@mail.gmail.com> <17CABFD7-19B2-4225-B99D-7718D71E25D7@att.com> <563255C0-11AD-4902-9A3F-D403E1A2A363@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qZRDQpJNLand7Chkrg_2tEi_Umw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 19:48:34 -0000

That would be great -- I'd be happy to help review, make pull requests, =
etc.

kramdown-rfc is magical.


> On 2 Aug 2017, at 5:32 am, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> On Aug 1, 2017, at 21:27, HANSEN, TONY L <tony@att.com> wrote:
>>=20
>> Care to contribute text? (Gosh, almost like working on an I-D. :-) )
>=20
> I have this project of coming up with an I-D describing kramdown-rfc.
> I even have a TOC and a collaborator lined up.
> Now just for some time to actually do the work...
> Somehow the normative stuff always gets precedence.
>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20

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



From nobody Tue Aug  1 13:04:07 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABB57131C3B for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 13:04:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.71
X-Spam-Level: 
X-Spam-Status: No, score=-0.71 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, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e3wGH52EOH-y for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 13:04:03 -0700 (PDT)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16841126B71 for <ietf@ietf.org>; Tue,  1 Aug 2017 13:04:03 -0700 (PDT)
Received: by mail-wm0-x22c.google.com with SMTP id t201so24179852wmt.1 for <ietf@ietf.org>; Tue, 01 Aug 2017 13:04:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=hj0hEhFWEoyVmG13f7c5Zz4o42vfOw0pc7yBS0DkYAE=; b=uNKDpQGXddYCt0LFcONXC3Bc+rNTowQX9/ki9er6kdxHD4c92EMJ7KtE7xYhlbYL5G 8dJ6MraPkJ8JncSALM57wVqJ59k4aOG1L46XI7wCaKzT02ieUXsxx3R0X13/OPDt4xQU XYt7Pli+QouKNvzVjdqMmpIctwXxeMgMzHW+taV39vW/WHA0LyLGTCVR9AUkOvMfj7St E11Uc8QodIrxzsfAPF9Eq8ULE0GMm7ugx2aXapSf4h8nj8PsWCI+3TK0JWCJrxd04eLS Z14XmoDn22d3Nk1fJwd45xFtxWvD9KWIAf6sNMjMmpJfBtuPNsFDTykeLdXQst5UgjZs JPKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=hj0hEhFWEoyVmG13f7c5Zz4o42vfOw0pc7yBS0DkYAE=; b=ZYjuLxbSuNNG1SoDZ2Sm3NRvQ3cfbPuPuDrIbK8TD+Vw6rI3JWw8/J1rrUA1SLj2Db m2stDzEVYRsAAxJoVViNbbjLwHKRcIXGstTqRzVO9kLpTjbOBh+BKfcv1oZ3HnYpWexb uQoJuLJNd4fO0gysJ8E6qimZAHsyccVqmq83mJ6qc8crVH77lB0JghKxBJa6FzggkBgT h+pjd8g4SIXgvCnLlwr+f5TVcYMaLHSt5u9GWI7AxZiXY/qNwCBPnOdmajoSnyAYvNj4 nZ/803iV74AmH2wwBrjPO2ZnKlNIIJqH5QPwpEB2KAu1D6AD9jFZovo3w4YOov2y852w 4nVw==
X-Gm-Message-State: AIVw112MFi2l7wUHg8/yGUGM05ZLU82YsspcYnQ+bBA/i8sMhtXGTHMO gSCcVRdOZa/S8ZlZKxc=
X-Received: by 10.80.168.65 with SMTP id j59mr18556320edc.110.1501617841419; Tue, 01 Aug 2017 13:04:01 -0700 (PDT)
Received: from [192.168.1.18] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id j6sm6343351edb.14.2017.08.01.13.03.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Aug 2017 13:03:59 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <F0326876-51CB-4925-BB08-D3471F259BEE@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_2452BB7B-E4CE-4A75-B651-30B336E489F4"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Remote participation
Date: Tue, 1 Aug 2017 23:03:57 +0300
In-Reply-To: <CAFDEUTciw4Rr5b7jY4iZ4cqPLjdd4h8zS7NVXy59cZXi4HOgWA@mail.gmail.com>
Cc: ietf@ietf.org
To: Loganaden Velvindron <logan@hackers.mu>
References: <CAFDEUTciw4Rr5b7jY4iZ4cqPLjdd4h8zS7NVXy59cZXi4HOgWA@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ifn_yvv_XFuZ13ROoJ1j4kEdFiE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 20:04:06 -0000

--Apple-Mail=_2452BB7B-E4CE-4A75-B651-30B336E489F4
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_6659C4E6-E05D-427D-B15E-A6FED429D681"


--Apple-Mail=_6659C4E6-E05D-427D-B15E-A6FED429D681
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On 1 Aug 2017, at 14:41, Loganaden Velvindron <logan@hackers.mu> =
wrote:
>=20
> Dear IETF folks,
>=20
> I would like to discuss about one thing:
>=20
> I am from Mauritius, which is still a emerging country. The average
> salary of 50% of the working population is around $430 (USD). In the
> IT sector, its slightly higher depending on the job. It's great that
> remote participation is now available, and thanks to the team behind
> this.
>=20
> My group was able to participate in both IETF 98 & IETF 99 remotely,
> and produce working code for the hackathon & contribute to Internet
> Drafts.
>=20
> For the majority of people in our region, we cannot afford to travel
> to the IETF, and most employers would not pay an IETF trip. It's great
> that remote participation is free, but I believe that we can
> contribute financially, according to our means.
>=20
> Would such as option be made available to remote participants at the
> time of registration ?

Hi, Logan

Donations to the IETF are possible through ISOC:

https://www.isoc.org/apps/ietf-donation/ =
<https://www.isoc.org/apps/ietf-donation/>
https://www.sustainietf.org =
<https://www.internetsociety.org/form/donate-ietfendowment>

This is available regardless of registration to any particular meeting.

HTH

Yoav


--Apple-Mail=_6659C4E6-E05D-427D-B15E-A6FED429D681
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;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 1 Aug 2017, at 14:41, Loganaden Velvindron &lt;<a =
href=3D"mailto:logan@hackers.mu" class=3D"">logan@hackers.mu</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">Dear IETF folks,<br class=3D""><br class=3D"">I would like to =
discuss about one thing:<br class=3D""><br class=3D"">I am from =
Mauritius, which is still a emerging country. The average<br =
class=3D"">salary of 50% of the working population is around $430 (USD). =
In the<br class=3D"">IT sector, its slightly higher depending on the =
job. It's great that<br class=3D"">remote participation is now =
available, and thanks to the team behind<br class=3D"">this.<br =
class=3D""><br class=3D"">My group was able to participate in both IETF =
98 &amp; IETF 99 remotely,<br class=3D"">and produce working code for =
the hackathon &amp; contribute to Internet<br class=3D"">Drafts.<br =
class=3D""><br class=3D"">For the majority of people in our region, we =
cannot afford to travel<br class=3D"">to the IETF, and most employers =
would not pay an IETF trip. It's great<br class=3D"">that remote =
participation is free, but I believe that we can<br class=3D"">contribute =
financially, according to our means.<br class=3D""><br class=3D"">Would =
such as option be made available to remote participants at the<br =
class=3D"">time of registration ?<br =
class=3D""></div></div></blockquote></div><br class=3D""><div =
class=3D"">Hi, Logan</div><div class=3D""><br class=3D""></div><div =
class=3D"">Donations to the IETF are possible through ISOC:</div><div =
class=3D""><br class=3D""></div><div class=3D""><a =
href=3D"https://www.isoc.org/apps/ietf-donation/" =
class=3D"">https://www.isoc.org/apps/ietf-donation/</a></div><div =
class=3D""><a =
href=3D"https://www.internetsociety.org/form/donate-ietfendowment" =
class=3D"">https://www.sustainietf.org</a></div><div class=3D""><br =
class=3D""></div><div class=3D"">This is available regardless of =
registration to any particular meeting.</div><div class=3D""><br =
class=3D""></div><div class=3D"">HTH</div><div class=3D""><br =
class=3D""></div><div class=3D"">Yoav</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_6659C4E6-E05D-427D-B15E-A6FED429D681--

--Apple-Mail=_2452BB7B-E4CE-4A75-B651-30B336E489F4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQEcBAEBCgAGBQJZgN6uAAoJELhJCxUKWMyZP7QH/0LPf/H708BdS15NAYdeciDi
0i20y+Chk/HxLIVaoruw00T7+6J+M/O1F4Qi5FWG+Z8qaGv5eGrPlewFj/WEclva
vorzN3UcKH1D1eRTi9RmwJB0nxqEby+3SL4qeMLbikN2sJEZdF41DSiIlyAXrTKY
ITmNQUM+H+wc7D3Jdlzi8PBQlXtFVXCduUc7yJEYIpJCqXSNIrtS+BfknVOp6MNz
bhcrdn6BYxrwfYUKCgbwsXqVTwDLdYPTWx6sRa790PQhmhOXznNy2ZK6MisyJ6Xs
GZThSeFzH39Ev6Kf6UMd2UtX0xZ9Mr2o0iTgxkeBTBaa66lIhYn+3KdsPXtzb3Y=
=bBNY
-----END PGP SIGNATURE-----

--Apple-Mail=_2452BB7B-E4CE-4A75-B651-30B336E489F4--


From nobody Tue Aug  1 13:36:48 2017
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E4FF129B40; Tue,  1 Aug 2017 13:36:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Tim Chown <tim.chown@jisc.ac.uk>
To: <ops-dir@ietf.org>
Cc: webpush@ietf.org, ietf@ietf.org, draft-ietf-webpush-encryption.all@ietf.org
Subject: Opsdir last call review of draft-ietf-webpush-encryption-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150161980513.12098.6547423319804689888@ietfa.amsl.com>
Date: Tue, 01 Aug 2017 13:36:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SiG96ftIkL70MihkkBr4WKd2Wf8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 20:36:45 -0000

Reviewer: Tim Chown
Review result: Ready

I have reviewed this document as part of the Operational directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written with the intent of improving the operational aspects of
the IETF drafts. Comments that are not addressed in last call may be included
in AD reviews during the IESG review.  Document editors and WG chairs should
treat these comments just like any other last call comments.

This document specifies a message encryption scheme for the Web Push protocol
described in RFC8030. The scheme provides confidentiality and integrity for
Push messages sent from an Application Server to a User Agent.  The encryption
scheme has also been adopted by W3C.

Note: I have not followed this work, and am not active in the relevant WGs.

The document is well-written, and clear, but noting point 1 below.

Overall I think the document is Ready, though I have some comments below.

1. I looked at RFC8030, the protocol spec for “Generic Event Delivery Using
HTTP Push”, and it includes a useful terminology section. Perhaps this draft
would benefit from a terminology section for the specific language used here?

2. If it is not already planned, I would recommend a review by an independent
reviewer who follows both the IETF and W3C work.  The Web Push API is described
at https://w3c.github.io/push-api/, where this draft is cited as
[WEBPUSH-ENCRYPTION]. Is the W3C spec for the Push API fully consistent with
the spec here?

3. Would the “Security Considerations” section benefit from some DoS text,
given the computations required at both ends of the subscription channel?  The
privacy considerations text is also rather light compared to that in RFC8030 -
perhaps point there, and clarify any additional considerations specific to this
draft here?

4. Are there any considerations for this spec is the load distribution
mechanisms in Section 7.1 of RFC8030 are employed? I assume not, but think it’s
worth asking.

And one nit:

1. In Section 3, “application secret” is used, and only used here. Should this
be “authentication secret” instead?

2. Section 3.1 para 4, should that be “Application Server”?


From nobody Tue Aug  1 16:01:18 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64D34131CE7 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 16:01:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wUFX6hLekM-3 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 16:01:16 -0700 (PDT)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F024F126BF3 for <ietf@ietf.org>; Tue,  1 Aug 2017 16:01:15 -0700 (PDT)
Received: by mail-wm0-x22b.google.com with SMTP id t201so27121596wmt.1 for <ietf@ietf.org>; Tue, 01 Aug 2017 16:01:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=references:in-reply-to:mime-version:content-transfer-encoding :message-id:cc:from:subject:date:to; bh=TlHTkDHazBnXP+8t9F6dMhusVr2qG+JOJOdKZZMAins=; b=bJRKWQeDL+6IdS32Y5apCkImUjHWgiZHPu0Bn42zaGjK1y0FXb806gyPUwkFy4kRfc av4sUzgjGcS2DBfMlZTvdclib9i3EUbS4xCT2yMZpH8zqq5YKGqIkCoV8188XM7gZG2c LdMvCDIvAUZr/qVaq4IpdR/qGiHscQ2FbEBU2DWFyTbCavcisbEm39kSF4OVu/3TFxsV Kl6dQUioXJIQ4bZzRo9YSwSb9faTGq57Y3vKHh5pD/eZ3JDbev/qlcxiOHgKdTS0XZaH YkNzc1HIwbSK1+9RBceFhEsH/cx3IAKNUfXl1mWOvnx7wIE1Twe1g1gonXeU8R1agbsD vgMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:in-reply-to:mime-version :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=TlHTkDHazBnXP+8t9F6dMhusVr2qG+JOJOdKZZMAins=; b=ufqdj1wiWF6yAegchfJ+5u+yE65zPugGeGXcFVgFojzePNGf2ZeF9rlTBiF6b+AyJQ 2xkO1Q6pygjW6M+BD6U8rOhrChvwAlzzSZ6EsFVpmvwvBkWmo4dyBinwaqhGI7J6BErz 1pQaV6jkHYpoZNGRhGNLuuBxPe4NnsaAugieNUyXlpslWDZ7zz/LgB3JAOvYDsXGq1jV rbLnh02t8mPgum/TS9o75AXAP/8Vnc9EfixgoqdWq8CAg1iz8LKnCC0UIVSh0LX8n4vo TIGENJn4n0oEsB6hYsuy5W5EjMVtEKfgItxojXZzzC3L8rZbXWckGRY8b0/v3kIm26uO kJng==
X-Gm-Message-State: AIVw1137srJKSQdgOomu3Wk9gNYakVv63xowzywYD+4X73V/rpAmPijB aaeBh6o5gYyU9w==
X-Received: by 10.28.19.9 with SMTP id 9mr2572948wmt.171.1501628474530; Tue, 01 Aug 2017 16:01:14 -0700 (PDT)
Received: from [192.168.3.102] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id 125sm2480452wmp.37.2017.08.01.16.01.13 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 01 Aug 2017 16:01:13 -0700 (PDT)
References: <523.1501530916@obiwan.sandelman.ca> <E8859A9F-7539-4C6B-962C-56E6F3323C14@tzi.org> <716.1501548333@obiwan.sandelman.ca> <06672B8B-DDC5-4362-8729-346688F587DD@tzi.org> <CAG4d1re6k-RhavZ7YFYrLD2qYg362fELdan0tN4LpiTW0VEf4w@mail.gmail.com> <17CABFD7-19B2-4225-B99D-7718D71E25D7@att.com> <CAG4d1rcSNFqVM5THgaGFyvv=652zM3kfZhSYy31f9-0NGt3p9A@mail.gmail.com>
In-Reply-To: <CAG4d1rcSNFqVM5THgaGFyvv=652zM3kfZhSYy31f9-0NGt3p9A@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <9E9C52C9-A0ED-4CE7-A1A1-22BF327645EC@gmail.com>
Cc: "HANSEN, TONY L" <tony@att.com>, Carsten Bormann <cabo@tzi.org>, IETF Discussion Mailing List <ietf@ietf.org>
X-Mailer: iPad Mail (13G36)
From: Gmail <stewart.bryant@gmail.com>
Subject: Re: normative references to IANA registries
Date: Wed, 2 Aug 2017 00:01:12 +0100
To: Alia Atlas <akatlas@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bHV1YOpGzeZLZgGf3j5ALIJBo7I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 23:01:17 -0000

Sent from my iPad

> On 1 Aug 2017, at 20:31, Alia Atlas <akatlas@gmail.com> wrote:
>=20
>   It'd be nice to be able to see and retrieve markdown versions of drafts -=
 if available - but that's a datatracker/tools team effort.


Yes, please, please, please can we have that, or better an opaque type so th=
at we can save the original in the format of the day.

-Stewart=


From nobody Tue Aug  1 16:28:22 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39D2E131C90 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 16:28:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, PP_MIME_FAKE_ASCII_TEXT=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S3LpCXQycgIz for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 16:28:19 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0EFC1287A5 for <ietf@ietf.org>; Tue,  1 Aug 2017 16:28:18 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id 7A5A524AE29; Tue,  1 Aug 2017 23:26:49 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 975DD160041; Tue,  1 Aug 2017 23:26:54 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 82AAB16004F; Tue,  1 Aug 2017 23:26:54 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id zt4nlRmbRjAq; Tue,  1 Aug 2017 23:26:54 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 2D83F160041; Tue,  1 Aug 2017 23:26:54 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 7E2FF80B1398; Wed,  2 Aug 2017 09:26:51 +1000 (AEST)
To: Ted Lemon <mellon@fugue.com>
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "ietf@ietf.org" <ietf@ietf.org>, "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
From: Mark Andrews <marka@isc.org>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es> <787AE7BB302AE849A7480A190F8B93300A0155F5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es> <20170801072139.316A7809B357@rock.dv.isc.org> <787AE7BB302AE849A7480A190F8B93300A0156BD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20170801145849.1660780A6174@rock.dv.isc.org> <5C3343EF-3724-4155-87BC-E169DFC38342@fugue.com> <FE8011FD-6E26-40EB-9058-A60909CD00D2@ecs.soton.ac.uk> <EMEW3|c23812222e6467c6d3ed634ad82e65b2y70ISJ03tjc|ecs.soton.ac.uk|FE8011FD-6E26-40EB-9058-A60909CD00D2@ecs.soton.ac.uk> <79B094AE-8D4B-4E30-AC8F-7F74BE8C13D2@fugue.com> <30708801-142F-47C5-A154-15E9D3C5068D@fugue.com>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-reply-to: Your message of "Tue, 01 Aug 2017 14:14:53 -0400." <30708801-142F-47C5-A154-15E9D3C5068D@fugue.com>
Date: Wed, 02 Aug 2017 09:26:51 +1000
Message-Id: <20170801232651.7E2FF80B1398@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3XFVEKQa8FhmuepmqFRZRjZqIqk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Aug 2017 23:28:21 -0000

In message <30708801-142F-47C5-A154-15E9D3C5068D@fugue.com>, Ted Lemon writes:
>
> On Aug 1, 2017, at 1:57 PM, Ted Lemon <mellon@fugue.com> wrote:
> > What she doesn't mention is that there is a way to detect DNS64, so in
> principle a validating stub resolver can do DNS64 itself _post
> validation_.
>
> Oops, actually she did mention that in the last paragraph—sorry!

You have to detect it and work around it.

NAT64 start out with the claim "You don't have to touch the node".

Now you have complicated CLAT and DNSSEC changes required in every
node in the internet to support NAT64 with more breakage than simple
tunneling and a NAT44 protocol translation in DS-Lite.  What's the
next workaround that will have to be deployed because NAT64 is being
used instead of NAT44 at the end of the tunnel?

CLAT and DNSSEC changes are required on every node as they will end
up on IPv6-only networks.  DS-Lite also requires changes on every
node on IPv6-only networks but they are much less intrusive.

We have created Frankenstein's monster here with NAT64.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Aug  1 18:06:36 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E868912714F for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 18:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id suPv7pbuYRhV for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 18:06:33 -0700 (PDT)
Received: from mail-pg0-x22a.google.com (mail-pg0-x22a.google.com [IPv6:2607:f8b0:400e:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65C99127058 for <ietf@ietf.org>; Tue,  1 Aug 2017 18:06:33 -0700 (PDT)
Received: by mail-pg0-x22a.google.com with SMTP id u185so14549239pgb.1 for <ietf@ietf.org>; Tue, 01 Aug 2017 18:06:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NK8oTioL7BLzZTmt5iMAnDD7aneI05y+TY/INaW0i5w=; b=W3lQrHPEsvw0VSQcZPPx7aoaFDPyLVxEzj71tPX6EbGMsBSGrWGkfFz6iYGgIB/YHh KnfoCZqNcB4b+uq24MVV5gcLn2guMTnlXe/kCxAvhufs4t8sl0aMy5aU9Q4ZNyErI4R1 imEY63xtaEu37sZXWLVtkzDPC9ptyjeTMtG7tCEO3IpawuKnfdj0Ke9LuTIhs4hHAm+a AyPM2GeBQMNIJeshf+E4QG9esRRMJTN+yhnMIW4LOCoCL1lCe0m/GQ0XmRTYtCPA4wJ+ /elySmViXR6F4xFImsfvp151CmpAPn7ONlEVtXd92hHhcQU9ZVlar78MIVlEPQ0eSZqO DFNg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NK8oTioL7BLzZTmt5iMAnDD7aneI05y+TY/INaW0i5w=; b=Met9YUh5cpaUQIuE2ri35C84lg9B61bTez64Bvnis9DVfXlUZUVSeUYhL6UWAkhhbk touBTTPZSiuAIOmYojnp3J1y8o/JRo1AfSNk0I9Fn6nNfFFvl4U+oDBUpDSOyvqupym5 TFhTMiG7Fk3I/CndfJrIcLt9GAByJjyzD3igWyJv3BrVaH2qVaAvcnaxzGlXDTVJnX9l z8fOeByCH4KemjXVGfQbLUkTSkdkNu8oLfZvGf90AGIdx5dBgiiVpbEb4ZNtnL4HwqbR t6EUIOWHjOrUkUZHIXX9k+Vxo+Kk2KfY55BE55dmNrF0fv106mtZKWCgmw7y8USYJaP0 szcw==
X-Gm-Message-State: AIVw1104izHeP7xhU7YgjCOUi6zmHAUUKm/gYbO+m6yQSltsT9dPBDIX 5d2oKmm4u4nQjxQJ4LcqkkpZSPF0pViP
X-Received: by 10.99.54.201 with SMTP id d192mr8461799pga.310.1501635992908; Tue, 01 Aug 2017 18:06:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.180.131 with HTTP; Tue, 1 Aug 2017 18:05:52 -0700 (PDT)
In-Reply-To: <20170801232651.7E2FF80B1398@rock.dv.isc.org>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es> <787AE7BB302AE849A7480A190F8B93300A0155F5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es> <20170801072139.316A7809B357@rock.dv.isc.org> <787AE7BB302AE849A7480A190F8B93300A0156BD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20170801145849.1660780A6174@rock.dv.isc.org> <5C3343EF-3724-4155-87BC-E169DFC38342@fugue.com> <FE8011FD-6E26-40EB-9058-A60909CD00D2@ecs.soton.ac.uk> <EMEW3|c23812222e6467c6d3ed634ad82e65b2y70ISJ03tjc|ecs.soton.ac.uk|FE8011FD-6E26-40EB-9058-A60909CD00D2@ecs.soton.ac.uk> <79B094AE-8D4B-4E30-AC8F-7F74BE8C13D2@fugue.com> <30708801-142F-47C5-A154-15E9D3C5068D@fugue.com> <20170801232651.7E2FF80B1398@rock.dv.isc.org>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 1 Aug 2017 21:05:52 -0400
Message-ID: <CAPt1N1ksfcjSAf06rVzNFBD-vyLcJUxL7UdRVud9_HKk7Eiysw@mail.gmail.com>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: Mark Andrews <marka@isc.org>
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "ietf@ietf.org" <ietf@ietf.org>,  "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
Content-Type: multipart/alternative; boundary="94eb2c0de54cf091f30555badf94"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/A4jepjPzyUpxb7KWEUh6qSGtZAs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Aug 2017 01:06:35 -0000

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

Actually CLAT+NAT64 doesn't require changes on the node.   I don't disagree
with the rest of what you said (aside from the Frankenstein's monster bit:
Frankenstein's monster was really misunderstood).

On Tue, Aug 1, 2017 at 7:26 PM, Mark Andrews <marka@isc.org> wrote:

>
> In message <30708801-142F-47C5-A154-15E9D3C5068D@fugue.com>, Ted Lemon
> writes:
> >
> > On Aug 1, 2017, at 1:57 PM, Ted Lemon <mellon@fugue.com> wrote:
> > > What she doesn't mention is that there is a way to detect DNS64, so i=
n
> > principle a validating stub resolver can do DNS64 itself _post
> > validation_.
> >
> > Oops, actually she did mention that in the last paragraph=E2=80=94sorry=
!
>
> You have to detect it and work around it.
>
> NAT64 start out with the claim "You don't have to touch the node".
>
> Now you have complicated CLAT and DNSSEC changes required in every
> node in the internet to support NAT64 with more breakage than simple
> tunneling and a NAT44 protocol translation in DS-Lite.  What's the
> next workaround that will have to be deployed because NAT64 is being
> used instead of NAT44 at the end of the tunnel?
>
> CLAT and DNSSEC changes are required on every node as they will end
> up on IPv6-only networks.  DS-Lite also requires changes on every
> node on IPv6-only networks but they are much less intrusive.
>
> We have created Frankenstein's monster here with NAT64.
>
> Mark
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>

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

<div dir=3D"ltr">Actually CLAT+NAT64 doesn&#39;t require changes on the nod=
e. =C2=A0 I don&#39;t disagree with the rest of what you said (aside from t=
he Frankenstein&#39;s monster bit: Frankenstein&#39;s monster was really mi=
sunderstood).</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote=
">On Tue, Aug 1, 2017 at 7:26 PM, Mark Andrews <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:marka@isc.org" target=3D"_blank">marka@isc.org</a>&gt;</span> w=
rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D=
"h5"><br>
In message &lt;<a href=3D"mailto:30708801-142F-47C5-A154-15E9D3C5068D@fugue=
.com">30708801-142F-47C5-A154-<wbr>15E9D3C5068D@fugue.com</a>&gt;, Ted Lemo=
n writes:<br>
&gt;<br>
&gt; On Aug 1, 2017, at 1:57 PM, Ted Lemon &lt;<a href=3D"mailto:mellon@fug=
ue.com">mellon@fugue.com</a>&gt; wrote:<br>
&gt; &gt; What she doesn&#39;t mention is that there is a way to detect DNS=
64, so in<br>
&gt; principle a validating stub resolver can do DNS64 itself _post<br>
&gt; validation_.<br>
&gt;<br>
&gt; Oops, actually she did mention that in the last paragraph=E2=80=94sorr=
y!<br>
<br>
</div></div>You have to detect it and work around it.<br>
<br>
NAT64 start out with the claim &quot;You don&#39;t have to touch the node&q=
uot;.<br>
<br>
Now you have complicated CLAT and DNSSEC changes required in every<br>
node in the internet to support NAT64 with more breakage than simple<br>
tunneling and a NAT44 protocol translation in DS-Lite.=C2=A0 What&#39;s the=
<br>
next workaround that will have to be deployed because NAT64 is being<br>
used instead of NAT44 at the end of the tunnel?<br>
<br>
CLAT and DNSSEC changes are required on every node as they will end<br>
up on IPv6-only networks.=C2=A0 DS-Lite also requires changes on every<br>
node on IPv6-only networks but they are much less intrusive.<br>
<br>
We have created Frankenstein&#39;s monster here with NAT64.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Mark<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5">--<br>
Mark Andrews, ISC<br>
1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
PHONE: <a href=3D"tel:%2B61%202%209871%204742" value=3D"+61298714742">+61 2=
 9871 4742</a>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0INTERNET: <a href=3D"mailto:marka@isc.org">marka@isc.org</a><br>
</div></div></blockquote></div><br></div>

--94eb2c0de54cf091f30555badf94--


From nobody Tue Aug  1 18:13:29 2017
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE0E612714F for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 18:13:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.41
X-Spam-Level: 
X-Spam-Status: No, score=-3.41 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ub9_5QQyJhOW for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 18:13:26 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 EB21D127058 for <ietf@ietf.org>; Tue,  1 Aug 2017 18:13:25 -0700 (PDT)
Received: from pps.filterd (m0049463.ppops.net [127.0.0.1]) by m0049463.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v7215iVU025608; Tue, 1 Aug 2017 21:13:21 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049463.ppops.net-00191d01. with ESMTP id 2c32fjm252-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 01 Aug 2017 21:13:21 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v721DLCP032460; Tue, 1 Aug 2017 21:13:21 -0400
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v721DAwd032394 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 1 Aug 2017 21:13:14 -0400
Received: from MISOUT7MSGHUBAA.ITServices.sbc.com (MISOUT7MSGHUBAA.itservices.sbc.com [130.9.129.145]) by mlpi409.sfdc.sbc.com (RSA Interceptor); Wed, 2 Aug 2017 01:12:59 GMT
Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.78]) by MISOUT7MSGHUBAA.ITServices.sbc.com ([130.9.129.145]) with mapi id 14.03.0319.002; Tue, 1 Aug 2017 21:12:59 -0400
From: "HANSEN, TONY L" <tony@att.com>
To: Alia Atlas <akatlas@gmail.com>
CC: IETF Discussion Mailing List <ietf@ietf.org>, Carsten Bormann <cabo@tzi.org>
Subject: Re: normative references to IANA registries
Thread-Topic: normative references to IANA registries
Thread-Index: AQHTCjb+qEkO9pZ17kChF5NdM5rkHqJuooOAgABLE4CAAHGdgIAAW8+AgAApBoCAAEQbAIAAHGKA
Date: Wed, 2 Aug 2017 01:12:58 +0000
Message-ID: <EA939F44-511A-4EEA-BDF1-D0E2CDBAE30E@att.com>
References: <523.1501530916@obiwan.sandelman.ca> <E8859A9F-7539-4C6B-962C-56E6F3323C14@tzi.org> <716.1501548333@obiwan.sandelman.ca> <06672B8B-DDC5-4362-8729-346688F587DD@tzi.org> <CAG4d1re6k-RhavZ7YFYrLD2qYg362fELdan0tN4LpiTW0VEf4w@mail.gmail.com> <17CABFD7-19B2-4225-B99D-7718D71E25D7@att.com> <CAG4d1rcSNFqVM5THgaGFyvv=652zM3kfZhSYy31f9-0NGt3p9A@mail.gmail.com>
In-Reply-To: <CAG4d1rcSNFqVM5THgaGFyvv=652zM3kfZhSYy31f9-0NGt3p9A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.210.14.178]
Content-Type: multipart/alternative; boundary="_000_EA939F44511A4EEABDF1D0E2CDBAE30Eattcom_"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-08-01_15:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1706020000 definitions=main-1708020017
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2KsXK0IwCq1vOZ_YSteP2GnnUxU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Aug 2017 01:13:28 -0000

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

QWx0ZXJuYXRpdmVseSwgY2FuIHlvdSBiZSBtb3JlIHNwZWNpZmljIG9uIHdoYXQgdHlwZXMgb2Yg
aW5mb3JtYXRpb24geW914oCZcmUgbG9va2luZyBmb3I/DQoNCkZvciBleGFtcGxlLCBnaXZlIG1l
IHRoZSBRIHBhcnQgb2YgYW4gRkFRLg0KDQogICAgICAgICAgICAgICAgVG9ueQ0KDQpGcm9tOiBB
bGlhIEF0bGFzIDxha2F0bGFzQGdtYWlsLmNvbT4NCkRhdGU6IFR1ZXNkYXksIEF1Z3VzdCAxLCAy
MDE3IGF0IDM6MzEgUE0NClRvOiAiSEFOU0VOLCBUT05ZIEwiIDx0b255QGF0dC5jb20+DQpDYzog
SUVURiBEaXNjdXNzaW9uIE1haWxpbmcgTGlzdCA8aWV0ZkBpZXRmLm9yZz4sIENhcnN0ZW4gQm9y
bWFubiA8Y2Fib0B0emkub3JnPg0KU3ViamVjdDogUmU6IG5vcm1hdGl2ZSByZWZlcmVuY2VzIHRv
IElBTkEgcmVnaXN0cmllcw0KDQpUb255LA0KDQpPbiBUdWUsIEF1ZyAxLCAyMDE3IGF0IDM6Mjcg
UE0sIEhBTlNFTiwgVE9OWSBMIDx0b255QGF0dC5jb208bWFpbHRvOnRvbnlAYXR0LmNvbT4+IHdy
b3RlOg0KQWxpYSwNCg0KPiBJIHJlYWxseSB0aGluayB0aGF0IGEgYml0IG1vcmUgdmlzaWJpbGl0
eSAtIGluY2x1ZGluZyBvbiB0aGUgeG1sMnJmYy5pZXRmLm9yZzxodHRwczovL3VybGRlZmVuc2Uu
cHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cC0zQV9feG1sMnJmYy5pZXRmLm9yZyZkPUR3TUZh
USZjPUxGWVotbzlfSFVNZU1UU1FpY3ZqSWcmcj1LejhWZGdQVmN0RE5TTlBKNlBzQmF3Jm09VWFJ
ZmhEQzQ1NWJpQjg2eFNMbjA5MHJPWWRzdWh1RE54UWJSalRhc2dsMCZzPVY4STVpVmI4dzJiWkhP
ZUNZVl9DdnVTbEIycDJfZjRnZ3pfclhwb2Q0VW8mZT0+IHBhZ2UgLSB3aXRoIGEgcG9pbnRlciBv
ciB0d28gLSB3b3VsZCBzcGVlZCBpbnRlcmVzdCBhbmQgYWRvcHRpb24uDQoNCkNhcmUgdG8gY29u
dHJpYnV0ZSB0ZXh0PyAoR29zaCwgYWxtb3N0IGxpa2Ugd29ya2luZyBvbiBhbiBJLUQuIDotKSAp
DQoNClN1cmUgLSBidXQgYXMgcGFydCBvZiBhIGdyb3VwLiAgSSBjYW4ndCB0ZWxsIGZvbGtzIC0g
bG9vayBoZXJlIGZvciBkZXRhaWxzIG9uIG1hcmtkb3duIHdpdGhvdXQga25vd2luZyBpdCBpcyB3
aGF0IGlzIGltcGxlbWVudGVkLiAgSXQnZCBiZSBuaWNlIHRvIGJlIGFibGUgdG8gc2VlIGFuZCBy
ZXRyaWV2ZSBtYXJrZG93biB2ZXJzaW9ucyBvZiBkcmFmdHMgLSBpZiBhdmFpbGFibGUgLSBidXQg
dGhhdCdzIGEgZGF0YXRyYWNrZXIvdG9vbHMgdGVhbSBlZmZvcnQuDQpJIHB1dCBzb21lIGVuZXJn
eSBpbnRvIGVuY291cmFnaW5nIGF0IGxlYXN0IGEgd2lraSB3aXRoIGJlc3QgcHJhY3RpY2VzLCBp
bmNsdWRpbmcgZm9yIHRoaXMsIGEgY291cGxlIHllYXJzIGFnbyBidXQgbXkgYXJtLXR3aXN0aW5n
IGZvbyB3YXNuJ3Qgc3Ryb25nL2dvb2QgZW5vdWdoIHRoZW4uDQoNClJlZ2FyZHMsDQpBbGlhDQoN
Cg0KICAgICAgICAgICAgICAgIFRvbnkgSGFuc2VuDQoNCkZyb206IGlldGYgPGlldGYtYm91bmNl
c0BpZXRmLm9yZzxtYWlsdG86aWV0Zi1ib3VuY2VzQGlldGYub3JnPj4gb24gYmVoYWxmIG9mIEFs
aWEgQXRsYXMgPGFrYXRsYXNAZ21haWwuY29tPG1haWx0bzpha2F0bGFzQGdtYWlsLmNvbT4+DQpE
YXRlOiBUdWVzZGF5LCBBdWd1c3QgMSwgMjAxNyBhdCA5OjAxIEFNDQpUbzogQ2Fyc3RlbiBCb3Jt
YW5uIDxjYWJvQHR6aS5vcmc8bWFpbHRvOmNhYm9AdHppLm9yZz4+DQpDYzogTWljaGFlbCBSaWNo
YXJkc29uIDxtY3IraWV0ZkBzYW5kZWxtYW4uY2E8bWFpbHRvOm1jciUyQmlldGZAc2FuZGVsbWFu
LmNhPj4sIElFVEYgRGlzY3Vzc2lvbiBNYWlsaW5nIExpc3QgPGlldGZAaWV0Zi5vcmc8bWFpbHRv
OmlldGZAaWV0Zi5vcmc+Pg0KU3ViamVjdDogUmU6IG5vcm1hdGl2ZSByZWZlcmVuY2VzIHRvIElB
TkEgcmVnaXN0cmllcw0KDQpDYXJzdGVuLA0KDQpPbiBUdWUsIEF1ZyAxLCAyMDE3IGF0IDM6MzIg
QU0sIENhcnN0ZW4gQm9ybWFubiA8Y2Fib0B0emkub3JnPG1haWx0bzpjYWJvQHR6aS5vcmc+PiB3
cm90ZToNCk9uIEF1ZyAxLCAyMDE3LCBhdCAwMjo0NSwgTWljaGFlbCBSaWNoYXJkc29uIDxtY3Ir
aWV0ZkBzYW5kZWxtYW4uY2E8bWFpbHRvOm1jciUyQmlldGZAc2FuZGVsbWFuLmNhPj4gd3JvdGU6
DQo+DQo+DQo+IENhcnN0ZW4gQm9ybWFubiA8Y2Fib0B0emkub3JnPG1haWx0bzpjYWJvQHR6aS5v
cmc+PiB3cm90ZToNCj4+PiBTbyBJIHdvbmRlciBvdXQgbG91ZDogc2hvdWxkbid0IGFsbCBvZiB0
aGUgSUFOQSByZWdpc3RyaWVzIGhhdmUgY2xlYXINCj4+PiByZWZlcmVuY2UgZmlsZXMgdGhhdCBj
b3VsZCBiZSBub3JtYXRpdmVseSByZWZlcmVuY2VkPw0KPg0KPj4gVHJ5IHJlZmVyZW5jaW5nLCBz
YXksIHt7IUlBTkEuY2Jvci10YWdzfX0g4oCUIGl0IGp1c3Qgd29ya3MgOi0pDQo+DQo+IHdvdy4g
SSdtIHN1cmUgaXQncyBkb2N1bWVudGVkIGluIHNvbWUgcGxhY2Ugc28gb2J2aW91cyBJIGNhbid0
IHNlZSBpdC4NCg0KaHR0cHM6Ly94bWwycmZjLnRvb2xzLmlldGYub3JnLzxodHRwczovL3VybGRl
ZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cHMtM0FfX3htbDJyZmMudG9vbHMuaWV0
Zi5vcmdfJmQ9RHdNRmFRJmM9TEZZWi1vOV9IVU1lTVRTUWljdmpJZyZyPUt6OFZkZ1BWY3RETlNO
UEo2UHNCYXcmbT1VYUlmaERDNDU1YmlCODZ4U0xuMDkwck9ZZHN1aHVETnhRYlJqVGFzZ2wwJnM9
dFoyYlFBQ2drZ3cxbWhvWk5Pd05yeFY3eVFyM2dvUGZwam5pX1pNdmJZZyZlPT4gaXMgdGhlIHBs
YWNlIHRoYXQgdGFsa3MgYWJvdXQgYmlieG1sOCByZWZlcmVuY2VzLg0Ka3JhbWRvd24tcmZjIGlz
IGp1c3QgbWFwcGluZyBhbGwgdGhlIElBTkEuKiByZWZlcmVuY2VzIHRvIGJpYnhtbDgsIGFzIGlu
DQoNCmh0dHBzOi8veG1sMnJmYy50b29scy5pZXRmLm9yZy9wdWJsaWMvcmZjL2JpYnhtbDgvcmVm
ZXJlbmNlLklBTkEuY2Jvci10YWdzLnhtbDxodHRwczovL3VybGRlZmVuc2UucHJvb2Zwb2ludC5j
b20vdjIvdXJsP3U9aHR0cHMtM0FfX3htbDJyZmMudG9vbHMuaWV0Zi5vcmdfcHVibGljX3JmY19i
aWJ4bWw4X3JlZmVyZW5jZS5JQU5BLmNib3ItMkR0YWdzLnhtbCZkPUR3TUZhUSZjPUxGWVotbzlf
SFVNZU1UU1FpY3ZqSWcmcj1LejhWZGdQVmN0RE5TTlBKNlBzQmF3Jm09VWFJZmhEQzQ1NWJpQjg2
eFNMbjA5MHJPWWRzdWh1RE54UWJSalRhc2dsMCZzPVJqU2V1UktQVk9YdVhQRGhjRVB4N2taQ2Zx
NmFvT3REQTlUNWw0Q1BJcGMmZT0+DQoNCj4gSXMgdGhlICJjYm9yLXRhZ3MiIHBhcnQgdGhlIGxh
c3QgcGFydCBvZiB0aGUgSUFOQSByZWdpc3RyeSBVUkw/DQoNCkFwcGFyZW50bHkuDQoNCmJpYnht
bDgvaW5kZXguY2dpOg0KDQogICAgaWYgKCRJQU5BcmVmID1+IG0oXi8/cmVmZXJlbmNlLklBTkFb
Ll0oW14vXSspWy5dKHhtbHxrcmFtZG93bikkKSkgew0KICAgICAgICBteSAkSUFOQXJlZiA9ICQx
Ow0K4oCmDQogICAgICAgICAgICBteSAkYSA9IGdldCgiaHR0cDovL3d3dy5pYW5hLm9yZy9hc3Np
Z25tZW50cy8kSUFOQXJlZi88aHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3Vy
bD91PWh0dHAtM0FfX3d3dy5pYW5hLm9yZ19hc3NpZ25tZW50c18tMjRJQU5BcmVmXyZkPUR3TUZh
USZjPUxGWVotbzlfSFVNZU1UU1FpY3ZqSWcmcj1LejhWZGdQVmN0RE5TTlBKNlBzQmF3Jm09VWFJ
ZmhEQzQ1NWJpQjg2eFNMbjA5MHJPWWRzdWh1RE54UWJSalRhc2dsMCZzPXl5cklXWUlTNk8xZEFl
YUF2Vi1NYlJvMmMwQmVIZGswdFNnNUpVSjQtc0UmZT0+4oCcKTsNCg0Ka3JhbWRvd24tcmZjIGlz
LCBzb21ld2hhdCBpcm9uaWNhbGx5IG1heWJlLCB1c2luZyB0aGUgeG1sIHZlcnNpb24gdGhlbiA6
LSkgKGdldHRpbmcgdGhlIGtyYW1kb3duIFtyZWFsbHk6IFlBTUxdIHZlcnNpb24gaXNuJ3QgZXZl
biBpbXBsZW1lbnRlZCBhdCB4bWwycmZjLmlldGYub3JnPGh0dHBzOi8vdXJsZGVmZW5zZS5wcm9v
ZnBvaW50LmNvbS92Mi91cmw/dT1odHRwLTNBX194bWwycmZjLmlldGYub3JnJmQ9RHdNRmFRJmM9
TEZZWi1vOV9IVU1lTVRTUWljdmpJZyZyPUt6OFZkZ1BWY3RETlNOUEo2UHNCYXcmbT1VYUlmaERD
NDU1YmlCODZ4U0xuMDkwck9ZZHN1aHVETnhRYlJqVGFzZ2wwJnM9VjhJNWlWYjh3MmJaSE9lQ1lW
X0N2dVNsQjJwMl9mNGdnel9yWHBvZDRVbyZlPT4sIGJ1dCB0aGVyZSBpcyBubyBuZWVkIHRvKS4N
Cg0KSXQgd291bGQgYmUgdmVyeSBoZWxwZnVsIHRvICBoYXZlIHRoZSBrcmFtZG93biB2ZXJzaW9u
IGF0IHhtbDJyZmMuaWV0Zi5vcmc8aHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3Yy
L3VybD91PWh0dHAtM0FfX3htbDJyZmMuaWV0Zi5vcmcmZD1Ed01GYVEmYz1MRllaLW85X0hVTWVN
VFNRaWN2aklnJnI9S3o4VmRnUFZjdEROU05QSjZQc0JhdyZtPVVhSWZoREM0NTViaUI4NnhTTG4w
OTByT1lkc3VodUROeFFiUmpUYXNnbDAmcz1WOEk1aVZiOHcyYlpIT2VDWVZfQ3Z1U2xCMnAyX2Y0
Z2d6X3JYcG9kNFVvJmU9Pi4NClNpbXBseSBnb2luZyB0byBnaXRodWIgKGh0dHBzOi8vZ2l0aHVi
LmNvbS9jYWJvL2tyYW1kb3duLXJmYzI2Mjk8aHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQu
Y29tL3YyL3VybD91PWh0dHBzLTNBX19naXRodWIuY29tX2NhYm9fa3JhbWRvd24tMkRyZmMyNjI5
JmQ9RHdNRmFRJmM9TEZZWi1vOV9IVU1lTVRTUWljdmpJZyZyPUt6OFZkZ1BWY3RETlNOUEo2UHNC
YXcmbT1VYUlmaERDNDU1YmlCODZ4U0xuMDkwck9ZZHN1aHVETnhRYlJqVGFzZ2wwJnM9QUFZZV9y
U1NuaW85VDlUMEhraU8wWFZfREw5a3hqSjJyREx5eXUwYmpadyZlPT4pICB0byBkb3dubG9hZCBh
bmQgcnVuIHRoZSBrcmFtZG93biBjb252ZXJ0ZXIgdG8geG1sIGRvZXNuJ3Qgd29yayB0cml2aWFs
bHkgb24gYSBXaW5kb3dzIG1hY2hpbmUuICBJIGdvIHRvIGh0dHA6Ly94bWwycmZjLnRvb2xzLmll
dGYub3JnL2V4cGVyaW1lbnRhbC5odG1sI2tyYW1kb3duPGh0dHBzOi8vdXJsZGVmZW5zZS5wcm9v
ZnBvaW50LmNvbS92Mi91cmw/dT1odHRwLTNBX194bWwycmZjLnRvb2xzLmlldGYub3JnX2V4cGVy
aW1lbnRhbC5odG1sLTIza3JhbWRvd24mZD1Ed01GYVEmYz1MRllaLW85X0hVTWVNVFNRaWN2akln
JnI9S3o4VmRnUFZjdEROU05QSjZQc0JhdyZtPVVhSWZoREM0NTViaUI4NnhTTG4wOTByT1lkc3Vo
dUROeFFiUmpUYXNnbDAmcz1LNHNDd2hHX3d3VEYyN0lLdnhSdWFPTHl3b3M0eG1ZOXlRWmc3d0xZ
WTVVJmU9PiB0byBydW4gaXQuDQoNClNpbmNlIHRoaXMgaXMgdGhlIG9ubHkgdGltZSB0aGF0IEkg
dXNlIGtyYW1kb3duIChvciBhbnkgbWFya2Rvd24gbGFuZ3VhZ2UpLCBpdCB3b3VsZCBiZSBxdWl0
ZSBoZWxwZnVsIHRvDQphbHNvIGhhdmUgYSBwb2ludGVyIHRvIHRoZSBzeW50YXggdG8gdXNlLiAg
SSBlbmQgdXAgZ29vZ2xpbmcgYW5kIGxvb2tpbmcgYXQgcmFuZG9tIGtyYW1kb3duIGRvY3VtZW50
YXRpb24NCmFuZCBob3BpbmcuICBUaGUgZXJyb3ItY2hlY2tpbmcgaXMgYWxzbyBhIGJpdCBmcnVz
dHJhdGluZyAtIEkgaGFkIGFuIGV4dHJhIHNwYWNlIGluIGZyb250IG9mIGEgLSBmb3Igc2VwYXJh
dGluZw0KdGhlIGF1dGhvcnMgYW5kIHRoZSBkb2N1bWVudCBmYWlsZWQgdG8gY29udmVydCBhdCBh
bGwgd2l0aCBubyBlcnJvci4gIE5vdCBiZWluZyBmYW1pbGlhciBlbm91Z2ggd2l0aCBrcmFtZG93
biwNCml0IHdhcyBjb21wbGV0ZWx5IG5vbi1vYnZpb3VzLg0KDQpSZWdhcmRsZXNzIG9mIHRoZSBh
Ym92ZSBkaWdyZXNzaW9uLCBrcmFtZG93bi1yZmMgaXMgcmVhbGx5IGF3ZXNvbWUgYW5kIG1ha2Vz
IGl0IG11Y2ggZWFzaWVyIHRvIHdyaXRlIGRyYWZ0cyENCkkndmUgY29udmVydGVkIG92ZXIgdG8g
ZG9pbmcgc28uICBJIHJlYWxseSB0aGluayB0aGF0IGEgYml0IG1vcmUgdmlzaWJpbGl0eSAtIGlu
Y2x1ZGluZyBvbiB0aGUgeG1sMnJmYy5pZXRmLm9yZzxodHRwczovL3VybGRlZmVuc2UucHJvb2Zw
b2ludC5jb20vdjIvdXJsP3U9aHR0cC0zQV9feG1sMnJmYy5pZXRmLm9yZyZkPUR3TUZhUSZjPUxG
WVotbzlfSFVNZU1UU1FpY3ZqSWcmcj1LejhWZGdQVmN0RE5TTlBKNlBzQmF3Jm09VWFJZmhEQzQ1
NWJpQjg2eFNMbjA5MHJPWWRzdWh1RE54UWJSalRhc2dsMCZzPVY4STVpVmI4dzJiWkhPZUNZVl9D
dnVTbEIycDJfZjRnZ3pfclhwb2Q0VW8mZT0+IHBhZ2UgLSB3aXRoIGEgcG9pbnRlciBvciB0d28g
LSB3b3VsZCBzcGVlZCBpbnRlcmVzdCBhbmQgYWRvcHRpb24uDQoNClRoYW5rIHlvdSBmb3IgeW91
ciB3b3JrIG9uIHRoaXMhDQpBbGlhDQoNCg==

--_000_EA939F44511A4EEABDF1D0E2CDBAE30Eattcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <4095E2513F2FED47909BF2DD20BE624A@LOCAL>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iVGl0bGUiIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPSJLZXl3b3JkcyIgY29udGVu
dD0iIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUg
KGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0
IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ
cGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eTpQTWluZ0xpVTsNCglwYW5vc2UtMToyIDIgNSAwIDAgMCAwIDAgMCAwO30NCi8qIFN0eWxlIERl
ZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJ
e21hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7
DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5
cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRl
Y29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dl
ZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3Jh
dGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5tMjQ3MTA1NTA4MTcyNDg2MTA3NmdtYWlsLQ0KCXttc28t
c3R5bGUtbmFtZTptXzI0NzEwNTUwODE3MjQ4NjEwNzZnbWFpbC07fQ0Kc3Bhbi5FbWFpbFN0eWxl
MTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGli
cmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQpzcGFuLm1zb0lucw0KCXttc28t
c3R5bGUtdHlwZTpleHBvcnQtb25seTsNCgltc28tc3R5bGUtbmFtZToiIjsNCgl0ZXh0LWRlY29y
YXRpb246dW5kZXJsaW5lOw0KCWNvbG9yOnRlYWw7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0
eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2Vj
dGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEu
MGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHls
ZT4NCjwvaGVhZD4NCjxib2R5IGJnY29sb3I9IndoaXRlIiBsYW5nPSJFTi1VUyIgbGluaz0iYmx1
ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+QWx0ZXJuYXRpdmVseSwgY2FuIHlvdSBiZSBtb3JlIHNwZWNpZmljIG9uIHdo
YXQgdHlwZXMgb2YgaW5mb3JtYXRpb24geW914oCZcmUgbG9va2luZyBmb3I/PG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPkZvciBleGFtcGxlLCBnaXZlIG1lIHRoZSBRIHBhcnQgb2YgYW4gRkFRLjxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsg
VG9ueTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYg
MS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtjb2xvcjpibGFjayI+RnJvbTogPC9zcGFu
PjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtjb2xvcjpibGFjayI+QWxpYSBBdGxh
cyAmbHQ7YWthdGxhc0BnbWFpbC5jb20mZ3Q7PGJyPg0KPGI+RGF0ZTogPC9iPlR1ZXNkYXksIEF1
Z3VzdCAxLCAyMDE3IGF0IDM6MzEgUE08YnI+DQo8Yj5UbzogPC9iPiZxdW90O0hBTlNFTiwgVE9O
WSBMJnF1b3Q7ICZsdDt0b255QGF0dC5jb20mZ3Q7PGJyPg0KPGI+Q2M6IDwvYj5JRVRGIERpc2N1
c3Npb24gTWFpbGluZyBMaXN0ICZsdDtpZXRmQGlldGYub3JnJmd0OywgQ2Fyc3RlbiBCb3JtYW5u
ICZsdDtjYWJvQHR6aS5vcmcmZ3Q7PGJyPg0KPGI+U3ViamVjdDogPC9iPlJlOiBub3JtYXRpdmUg
cmVmZXJlbmNlcyB0byBJQU5BIHJlZ2lzdHJpZXM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRvbnksIDxvOnA+PC9vOnA+PC9wPg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gVHVlLCBBdWcgMSwgMjAxNyBhdCAzOjI3
IFBNLCBIQU5TRU4sIFRPTlkgTCAmbHQ7PGEgaHJlZj0ibWFpbHRvOnRvbnlAYXR0LmNvbSIgdGFy
Z2V0PSJfYmxhbmsiPnRvbnlAYXR0LmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFy
Z2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+QWxpYSwNCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph
dXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jmd0OyBJ
IHJlYWxseSB0aGluayB0aGF0IGEgYml0IG1vcmUgdmlzaWJpbGl0eSAtIGluY2x1ZGluZyBvbiB0
aGUNCjxhIGhyZWY9Imh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1o
dHRwLTNBX194bWwycmZjLmlldGYub3JnJmFtcDtkPUR3TUZhUSZhbXA7Yz1MRllaLW85X0hVTWVN
VFNRaWN2aklnJmFtcDtyPUt6OFZkZ1BWY3RETlNOUEo2UHNCYXcmYW1wO209VWFJZmhEQzQ1NWJp
Qjg2eFNMbjA5MHJPWWRzdWh1RE54UWJSalRhc2dsMCZhbXA7cz1WOEk1aVZiOHcyYlpIT2VDWVZf
Q3Z1U2xCMnAyX2Y0Z2d6X3JYcG9kNFVvJmFtcDtlPSIgdGFyZ2V0PSJfYmxhbmsiPg0KeG1sMnJm
Yy5pZXRmLm9yZzwvYT4gcGFnZSAtIHdpdGggYSBwb2ludGVyIG9yIHR3byAtIHdvdWxkIHNwZWVk
IGludGVyZXN0IGFuZCBhZG9wdGlvbi4gJm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0
b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij5DYXJlIHRvIGNvbnRyaWJ1dGUgdGV4dD8gKEdvc2gsIGFsbW9zdCBsaWtlIHdvcmtpbmcgb24g
YW4gSS1ELiA6LSkgKTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90
ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlN1cmUgLSBidXQgYXMgcGFydCBvZiBh
IGdyb3VwLiZuYnNwOyBJIGNhbid0IHRlbGwgZm9sa3MgLSBsb29rIGhlcmUgZm9yIGRldGFpbHMg
b24gbWFya2Rvd24gd2l0aG91dCBrbm93aW5nIGl0IGlzIHdoYXQgaXMgaW1wbGVtZW50ZWQuJm5i
c3A7IEl0J2QgYmUgbmljZSB0byBiZSBhYmxlIHRvIHNlZSBhbmQgcmV0cmlldmUgbWFya2Rvd24g
dmVyc2lvbnMgb2YgZHJhZnRzIC0gaWYgYXZhaWxhYmxlIC0gYnV0IHRoYXQncyBhIGRhdGF0cmFj
a2VyL3Rvb2xzDQogdGVhbSBlZmZvcnQuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5JIHB1dCBzb21lIGVuZXJneSBpbnRvIGVuY291cmFnaW5nIGF0
IGxlYXN0IGEgd2lraSB3aXRoIGJlc3QgcHJhY3RpY2VzLCBpbmNsdWRpbmcgZm9yIHRoaXMsIGEg
Y291cGxlIHllYXJzIGFnbyBidXQgbXkgYXJtLXR3aXN0aW5nIGZvbyB3YXNuJ3Qgc3Ryb25nL2dv
b2QgZW5vdWdoIHRoZW4uPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPlJlZ2FyZHMsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5BbGlhJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJs
b2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4w
cHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmln
aHQ6MGluIj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7IFRvbnkgSGFuc2VuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9y
ZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtj
b2xvcjpibGFjayI+RnJvbToNCjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4w
cHQ7Y29sb3I6YmxhY2siPmlldGYgJmx0OzxhIGhyZWY9Im1haWx0bzppZXRmLWJvdW5jZXNAaWV0
Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5pZXRmLWJvdW5jZXNAaWV0Zi5vcmc8L2E+Jmd0OyBvbiBi
ZWhhbGYgb2YgQWxpYSBBdGxhcyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFrYXRsYXNAZ21haWwuY29t
IiB0YXJnZXQ9Il9ibGFuayI+YWthdGxhc0BnbWFpbC5jb208L2E+Jmd0Ozxicj4NCjxiPkRhdGU6
IDwvYj5UdWVzZGF5LCBBdWd1c3QgMSwgMjAxNyBhdCA5OjAxIEFNPGJyPg0KPGI+VG86IDwvYj5D
YXJzdGVuIEJvcm1hbm4gJmx0OzxhIGhyZWY9Im1haWx0bzpjYWJvQHR6aS5vcmciIHRhcmdldD0i
X2JsYW5rIj5jYWJvQHR6aS5vcmc8L2E+Jmd0Ozxicj4NCjxiPkNjOiA8L2I+TWljaGFlbCBSaWNo
YXJkc29uICZsdDs8YSBocmVmPSJtYWlsdG86bWNyJTJCaWV0ZkBzYW5kZWxtYW4uY2EiIHRhcmdl
dD0iX2JsYW5rIj5tY3ImIzQzO2lldGZAc2FuZGVsbWFuLmNhPC9hPiZndDssIElFVEYgRGlzY3Vz
c2lvbiBNYWlsaW5nIExpc3QgJmx0OzxhIGhyZWY9Im1haWx0bzppZXRmQGlldGYub3JnIiB0YXJn
ZXQ9Il9ibGFuayI+aWV0ZkBpZXRmLm9yZzwvYT4mZ3Q7PGJyPg0KPGI+U3ViamVjdDogPC9iPlJl
OiBub3JtYXRpdmUgcmVmZXJlbmNlcyB0byBJQU5BIHJlZ2lzdHJpZXM8L3NwYW4+PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8iPkNhcnN0ZW4sDQo8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+T24gVHVlLCBBdWcgMSwgMjAxNyBhdCAzOjMyIEFNLCBDYXJzdGVuIEJvcm1hbm4gJmx0Ozxh
IGhyZWY9Im1haWx0bzpjYWJvQHR6aS5vcmciIHRhcmdldD0iX2JsYW5rIj5jYWJvQHR6aS5vcmc8
L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6
bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4g
Ni4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6MGlu
O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBjbGFz
cz0ibTI0NzEwNTUwODE3MjQ4NjEwNzZnbWFpbC0iPk9uIEF1ZyAxLCAyMDE3LCBhdCAwMjo0NSwg
TWljaGFlbCBSaWNoYXJkc29uICZsdDs8YSBocmVmPSJtYWlsdG86bWNyJTJCaWV0ZkBzYW5kZWxt
YW4uY2EiIHRhcmdldD0iX2JsYW5rIj5tY3ImIzQzO2lldGZAc2FuZGVsbWFuLmNhPC9hPiZndDsg
d3JvdGU6PC9zcGFuPjxicj4NCjxzcGFuIGNsYXNzPSJtMjQ3MTA1NTA4MTcyNDg2MTA3NmdtYWls
LSI+Jmd0Ozwvc3Bhbj48YnI+DQo8c3BhbiBjbGFzcz0ibTI0NzEwNTUwODE3MjQ4NjEwNzZnbWFp
bC0iPiZndDs8L3NwYW4+PGJyPg0KPHNwYW4gY2xhc3M9Im0yNDcxMDU1MDgxNzI0ODYxMDc2Z21h
aWwtIj4mZ3Q7IENhcnN0ZW4gQm9ybWFubiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmNhYm9AdHppLm9y
ZyIgdGFyZ2V0PSJfYmxhbmsiPmNhYm9AdHppLm9yZzwvYT4mZ3Q7IHdyb3RlOjwvc3Bhbj48YnI+
DQo8c3BhbiBjbGFzcz0ibTI0NzEwNTUwODE3MjQ4NjEwNzZnbWFpbC0iPiZndDsmZ3Q7Jmd0OyBT
byBJIHdvbmRlciBvdXQgbG91ZDogc2hvdWxkbid0IGFsbCBvZiB0aGUgSUFOQSByZWdpc3RyaWVz
IGhhdmUgY2xlYXI8L3NwYW4+PGJyPg0KPHNwYW4gY2xhc3M9Im0yNDcxMDU1MDgxNzI0ODYxMDc2
Z21haWwtIj4mZ3Q7Jmd0OyZndDsgcmVmZXJlbmNlIGZpbGVzIHRoYXQgY291bGQgYmUgbm9ybWF0
aXZlbHkgcmVmZXJlbmNlZD88L3NwYW4+PGJyPg0KPHNwYW4gY2xhc3M9Im0yNDcxMDU1MDgxNzI0
ODYxMDc2Z21haWwtIj4mZ3Q7PC9zcGFuPjxicj4NCjxzcGFuIGNsYXNzPSJtMjQ3MTA1NTA4MTcy
NDg2MTA3NmdtYWlsLSI+Jmd0OyZndDsgVHJ5IHJlZmVyZW5jaW5nLCBzYXksIHt7IUlBTkEuY2Jv
ci10YWdzfX0g4oCUIGl0IGp1c3Qgd29ya3MgOi0pPC9zcGFuPjxicj4NCjxzcGFuIGNsYXNzPSJt
MjQ3MTA1NTA4MTcyNDg2MTA3NmdtYWlsLSI+Jmd0Ozwvc3Bhbj48YnI+DQo8c3BhbiBjbGFzcz0i
bTI0NzEwNTUwODE3MjQ4NjEwNzZnbWFpbC0iPiZndDsgd293LiBJJ20gc3VyZSBpdCdzIGRvY3Vt
ZW50ZWQgaW4gc29tZSBwbGFjZSBzbyBvYnZpb3VzIEkgY2FuJ3Qgc2VlIGl0Ljwvc3Bhbj48YnI+
DQo8YnI+DQo8YSBocmVmPSJodHRwczovL3VybGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJs
P3U9aHR0cHMtM0FfX3htbDJyZmMudG9vbHMuaWV0Zi5vcmdfJmFtcDtkPUR3TUZhUSZhbXA7Yz1M
RllaLW85X0hVTWVNVFNRaWN2aklnJmFtcDtyPUt6OFZkZ1BWY3RETlNOUEo2UHNCYXcmYW1wO209
VWFJZmhEQzQ1NWJpQjg2eFNMbjA5MHJPWWRzdWh1RE54UWJSalRhc2dsMCZhbXA7cz10WjJiUUFD
Z2tndzFtaG9aTk93TnJ4Vjd5UXIzZ29QZnBqbmlfWk12YllnJmFtcDtlPSIgdGFyZ2V0PSJfYmxh
bmsiPmh0dHBzOi8veG1sMnJmYy50b29scy5pZXRmLm9yZy88L2E+DQogaXMgdGhlIHBsYWNlIHRo
YXQgdGFsa3MgYWJvdXQgYmlieG1sOCByZWZlcmVuY2VzLjxicj4NCmtyYW1kb3duLXJmYyBpcyBq
dXN0IG1hcHBpbmcgYWxsIHRoZSBJQU5BLiogcmVmZXJlbmNlcyB0byBiaWJ4bWw4LCBhcyBpbjxi
cj4NCjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91
cmw/dT1odHRwcy0zQV9feG1sMnJmYy50b29scy5pZXRmLm9yZ19wdWJsaWNfcmZjX2JpYnhtbDhf
cmVmZXJlbmNlLklBTkEuY2Jvci0yRHRhZ3MueG1sJmFtcDtkPUR3TUZhUSZhbXA7Yz1MRllaLW85
X0hVTWVNVFNRaWN2aklnJmFtcDtyPUt6OFZkZ1BWY3RETlNOUEo2UHNCYXcmYW1wO209VWFJZmhE
QzQ1NWJpQjg2eFNMbjA5MHJPWWRzdWh1RE54UWJSalRhc2dsMCZhbXA7cz1SalNldVJLUFZPWHVY
UERoY0VQeDdrWkNmcTZhb090REE5VDVsNENQSXBjJmFtcDtlPSIgdGFyZ2V0PSJfYmxhbmsiPmh0
dHBzOi8veG1sMnJmYy50b29scy5pZXRmLm9yZy9wdWJsaWMvcmZjL2JpYnhtbDgvcmVmZXJlbmNl
LklBTkEuY2Jvci10YWdzLnhtbDwvYT48YnI+DQo8YnI+DQo8c3BhbiBjbGFzcz0ibTI0NzEwNTUw
ODE3MjQ4NjEwNzZnbWFpbC0iPiZndDsgSXMgdGhlICZxdW90O2Nib3ItdGFncyZxdW90OyBwYXJ0
IHRoZSBsYXN0IHBhcnQgb2YgdGhlIElBTkEgcmVnaXN0cnkgVVJMPzwvc3Bhbj48YnI+DQo8YnI+
DQpBcHBhcmVudGx5Ljxicj4NCjxicj4NCmJpYnhtbDgvaW5kZXguY2dpOjxicj4NCjxicj4NCiZu
YnNwOyAmbmJzcDsgaWYgKCRJQU5BcmVmID1+IG0oXi8/cmVmZXJlbmNlLklBTkFbLl0oW14vXSYj
NDM7KVsuXSh4bWx8a3JhbWRvd24pJCkpIHs8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgbXkgJElBTkFyZWYgPSAkMTs8YnI+DQrigKY8c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1
b3Q7UE1pbmdMaVUmcXVvdDssc2VyaWYiPjxicj4NCjwvc3Bhbj4mbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBteSAkYSA9IGdldCgmcXVvdDs8YSBocmVmPSJodHRwczov
L3VybGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cC0zQV9fd3d3LmlhbmEub3Jn
X2Fzc2lnbm1lbnRzXy0yNElBTkFyZWZfJmFtcDtkPUR3TUZhUSZhbXA7Yz1MRllaLW85X0hVTWVN
VFNRaWN2aklnJmFtcDtyPUt6OFZkZ1BWY3RETlNOUEo2UHNCYXcmYW1wO209VWFJZmhEQzQ1NWJp
Qjg2eFNMbjA5MHJPWWRzdWh1RE54UWJSalRhc2dsMCZhbXA7cz15eXJJV1lJUzZPMWRBZWFBdlYt
TWJSbzJjMEJlSGRrMHRTZzVKVUo0LXNFJmFtcDtlPSIgdGFyZ2V0PSJfYmxhbmsiPmh0dHA6Ly93
d3cuaWFuYS5vcmcvYXNzaWdubWVudHMvJElBTkFyZWYvPC9hPuKAnCk7PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OiZxdW90O1BNaW5nTGlVJnF1b3Q7LHNlcmlmIj48YnI+DQo8YnI+DQo8L3NwYW4+
a3JhbWRvd24tcmZjIGlzLCBzb21ld2hhdCBpcm9uaWNhbGx5IG1heWJlLCB1c2luZyB0aGUgeG1s
IHZlcnNpb24gdGhlbiA6LSkgKGdldHRpbmcgdGhlIGtyYW1kb3duIFtyZWFsbHk6IFlBTUxdIHZl
cnNpb24gaXNuJ3QgZXZlbiBpbXBsZW1lbnRlZCBhdA0KPGEgaHJlZj0iaHR0cHM6Ly91cmxkZWZl
bnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91PWh0dHAtM0FfX3htbDJyZmMuaWV0Zi5vcmcmYW1w
O2Q9RHdNRmFRJmFtcDtjPUxGWVotbzlfSFVNZU1UU1FpY3ZqSWcmYW1wO3I9S3o4VmRnUFZjdERO
U05QSjZQc0JhdyZhbXA7bT1VYUlmaERDNDU1YmlCODZ4U0xuMDkwck9ZZHN1aHVETnhRYlJqVGFz
Z2wwJmFtcDtzPVY4STVpVmI4dzJiWkhPZUNZVl9DdnVTbEIycDJfZjRnZ3pfclhwb2Q0VW8mYW1w
O2U9IiB0YXJnZXQ9Il9ibGFuayI+DQp4bWwycmZjLmlldGYub3JnPC9hPiwgYnV0IHRoZXJlIGlz
IG5vIG5lZWQgdG8pLjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPkl0IHdvdWxkIGJlIHZlcnkgaGVscGZ1bCB0byAmbmJzcDto
YXZlIHRoZSBrcmFtZG93biB2ZXJzaW9uIGF0DQo8YSBocmVmPSJodHRwczovL3VybGRlZmVuc2Uu
cHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cC0zQV9feG1sMnJmYy5pZXRmLm9yZyZhbXA7ZD1E
d01GYVEmYW1wO2M9TEZZWi1vOV9IVU1lTVRTUWljdmpJZyZhbXA7cj1LejhWZGdQVmN0RE5TTlBK
NlBzQmF3JmFtcDttPVVhSWZoREM0NTViaUI4NnhTTG4wOTByT1lkc3VodUROeFFiUmpUYXNnbDAm
YW1wO3M9VjhJNWlWYjh3MmJaSE9lQ1lWX0N2dVNsQjJwMl9mNGdnel9yWHBvZDRVbyZhbXA7ZT0i
IHRhcmdldD0iX2JsYW5rIj4NCnhtbDJyZmMuaWV0Zi5vcmc8L2E+LjxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5TaW1wbHkgZ29pbmcgdG8gZ2l0
aHViICg8YSBocmVmPSJodHRwczovL3VybGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9
aHR0cHMtM0FfX2dpdGh1Yi5jb21fY2Fib19rcmFtZG93bi0yRHJmYzI2MjkmYW1wO2Q9RHdNRmFR
JmFtcDtjPUxGWVotbzlfSFVNZU1UU1FpY3ZqSWcmYW1wO3I9S3o4VmRnUFZjdEROU05QSjZQc0Jh
dyZhbXA7bT1VYUlmaERDNDU1YmlCODZ4U0xuMDkwck9ZZHN1aHVETnhRYlJqVGFzZ2wwJmFtcDtz
PUFBWWVfclNTbmlvOVQ5VDBIa2lPMFhWX0RMOWt4akoyckRMeXl1MGJqWncmYW1wO2U9IiB0YXJn
ZXQ9Il9ibGFuayI+aHR0cHM6Ly9naXRodWIuY29tL2NhYm8va3JhbWRvd24tcmZjMjYyOTwvYT4p
Jm5ic3A7DQogdG8gZG93bmxvYWQgYW5kIHJ1biB0aGUga3JhbWRvd24gY29udmVydGVyIHRvIHht
bCBkb2Vzbid0IHdvcmsgdHJpdmlhbGx5IG9uIGEgV2luZG93cyBtYWNoaW5lLiZuYnNwOyBJIGdv
IHRvDQo8YSBocmVmPSJodHRwczovL3VybGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9
aHR0cC0zQV9feG1sMnJmYy50b29scy5pZXRmLm9yZ19leHBlcmltZW50YWwuaHRtbC0yM2tyYW1k
b3duJmFtcDtkPUR3TUZhUSZhbXA7Yz1MRllaLW85X0hVTWVNVFNRaWN2aklnJmFtcDtyPUt6OFZk
Z1BWY3RETlNOUEo2UHNCYXcmYW1wO209VWFJZmhEQzQ1NWJpQjg2eFNMbjA5MHJPWWRzdWh1RE54
UWJSalRhc2dsMCZhbXA7cz1LNHNDd2hHX3d3VEYyN0lLdnhSdWFPTHl3b3M0eG1ZOXlRWmc3d0xZ
WTVVJmFtcDtlPSIgdGFyZ2V0PSJfYmxhbmsiPg0KaHR0cDovL3htbDJyZmMudG9vbHMuaWV0Zi5v
cmcvZXhwZXJpbWVudGFsLmh0bWwja3JhbWRvd248L2E+IHRvIHJ1biBpdC48bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPlNpbmNlIHRoaXMg
aXMgdGhlIG9ubHkgdGltZSB0aGF0IEkgdXNlIGtyYW1kb3duIChvciBhbnkgbWFya2Rvd24gbGFu
Z3VhZ2UpLCBpdCB3b3VsZCBiZSBxdWl0ZSBoZWxwZnVsIHRvPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPmFsc28gaGF2ZSBhIHBvaW50ZXIgdG8g
dGhlIHN5bnRheCB0byB1c2UuJm5ic3A7IEkgZW5kIHVwIGdvb2dsaW5nIGFuZCBsb29raW5nIGF0
IHJhbmRvbSBrcmFtZG93biBkb2N1bWVudGF0aW9uJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPmFuZCBob3BpbmcuJm5ic3A7IFRoZSBl
cnJvci1jaGVja2luZyBpcyBhbHNvIGEgYml0IGZydXN0cmF0aW5nIC0gSSBoYWQgYW4gZXh0cmEg
c3BhY2UgaW4gZnJvbnQgb2YgYSAtIGZvciBzZXBhcmF0aW5nPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPnRoZSBhdXRob3JzIGFuZCB0aGUgZG9j
dW1lbnQgZmFpbGVkIHRvIGNvbnZlcnQgYXQgYWxsIHdpdGggbm8gZXJyb3IuJm5ic3A7IE5vdCBi
ZWluZyBmYW1pbGlhciBlbm91Z2ggd2l0aCBrcmFtZG93biw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+aXQgd2FzIGNvbXBsZXRlbHkgbm9uLW9i
dmlvdXMuJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj5SZWdhcmRsZXNzIG9mIHRoZSBhYm92ZSBkaWdyZXNzaW9uLCBrcmFtZG93
bi1yZmMgaXMgcmVhbGx5IGF3ZXNvbWUgYW5kIG1ha2VzIGl0IG11Y2ggZWFzaWVyIHRvIHdyaXRl
IGRyYWZ0cyE8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+SSd2ZSBjb252ZXJ0ZWQgb3ZlciB0byBkb2luZyBzby4mbmJzcDsgSSByZWFsbHkgdGhp
bmsgdGhhdCBhIGJpdCBtb3JlIHZpc2liaWxpdHkgLSBpbmNsdWRpbmcgb24gdGhlDQo8YSBocmVm
PSJodHRwczovL3VybGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cC0zQV9feG1s
MnJmYy5pZXRmLm9yZyZhbXA7ZD1Ed01GYVEmYW1wO2M9TEZZWi1vOV9IVU1lTVRTUWljdmpJZyZh
bXA7cj1LejhWZGdQVmN0RE5TTlBKNlBzQmF3JmFtcDttPVVhSWZoREM0NTViaUI4NnhTTG4wOTBy
T1lkc3VodUROeFFiUmpUYXNnbDAmYW1wO3M9VjhJNWlWYjh3MmJaSE9lQ1lWX0N2dVNsQjJwMl9m
NGdnel9yWHBvZDRVbyZhbXA7ZT0iIHRhcmdldD0iX2JsYW5rIj4NCnhtbDJyZmMuaWV0Zi5vcmc8
L2E+IHBhZ2UgLSB3aXRoIGEgcG9pbnRlciBvciB0d28gLSB3b3VsZCBzcGVlZCBpbnRlcmVzdCBh
bmQgYWRvcHRpb24uICZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy
Z2luLWJvdHRvbS1hbHQ6YXV0byI+VGhhbmsgeW91IGZvciB5b3VyIHdvcmsgb24gdGhpcyE8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+QWxpYTxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2JvZHk+DQo8L2h0bWw+DQo=

--_000_EA939F44511A4EEABDF1D0E2CDBAE30Eattcom_--


From nobody Tue Aug  1 18:38:18 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85DB9126BF3 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 18:38:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XjIQ0vO4aL1B for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 18:38:15 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 044D112426E for <ietf@ietf.org>; Tue,  1 Aug 2017 18:38:15 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id CD07F24AE87; Wed,  2 Aug 2017 01:38:04 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id E629E160041; Wed,  2 Aug 2017 01:38:09 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id D660816004A; Wed,  2 Aug 2017 01:38:09 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id UiFNdaJTASOt; Wed,  2 Aug 2017 01:38:09 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id E90FF160041; Wed,  2 Aug 2017 01:38:08 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id F222B80BCE0B; Wed,  2 Aug 2017 11:38:06 +1000 (AEST)
To: Ted Lemon <mellon@fugue.com>
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "ietf@ietf.org" <ietf@ietf.org>, "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
From: Mark Andrews <marka@isc.org>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es> <787AE7BB302AE849A7480A190F8B93300A0155F5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es> <20170801072139.316A7809B357@rock.dv.isc.org> <787AE7BB302AE849A7480A190F8B93300A0156BD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20170801145849.1660780A6174@rock.dv.isc.org> <5C3343EF-3724-4155-87BC-E169DFC38342@fugue.com> <FE8011FD-6E26-40EB-9058-A60909CD00D2@ecs.soton.ac.uk> <EMEW3|c23812222e6467c6d3ed634ad82e65b2y70ISJ03tjc|ecs.soton.ac.uk|FE8011FD-6E26-40EB-9058-A60909CD00D2@ecs.soton.ac.uk> <79B094AE-8D4B-4E30-AC8F-7F74BE8C13D2@fugue.com> <30708801-142F-47C5-A154-15E9D3C5068D@fugue.com> <2017 0801232651.7E2FF80B1398@rock.dv.isc.org> <CAPt1N1ksfcjSAf06rVzNFBD-vyLcJUxL7UdRVud9_HKk7Eiysw@mail.gmail.com>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
In-reply-to: Your message of "Tue, 01 Aug 2017 21:05:52 -0400." <CAPt1N1ksfcjSAf06rVzNFBD-vyLcJUxL7UdRVud9_HKk7Eiysw@mail.gmail.com>
Date: Wed, 02 Aug 2017 11:38:06 +1000
Message-Id: <20170802013806.F222B80BCE0B@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AiiQxfOGQMM8z4GJ_YaOF_U_lE0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Aug 2017 01:38:16 -0000

In message <CAPt1N1ksfcjSAf06rVzNFBD-vyLcJUxL7UdRVud9_HKk7Eiysw@mail.gmail.com>, Ted Lemo
n writes:
> 
> Actually CLAT+NAT64 doesn't require changes on the node.   I don't disagree
> with the rest of what you said (aside from the Frankenstein's monster bit:
> Frankenstein's monster was really misunderstood).

It does for IPv6-only if want to talk to IPv4 literals or talk to
IPv4 only services when you are validating DNS answers.  You may
be thinking about DS local + IPv6 only uplink where you have the
CLAT on the router (which is the configuration that is being proposed
for ietf ssid).  Real IPv6 only networks don't have IPv4 traffic
on the wire, just inside the node.

Mark

> On Tue, Aug 1, 2017 at 7:26 PM, Mark Andrews <marka@isc.org> wrote:
> 
> >
> > In message <30708801-142F-47C5-A154-15E9D3C5068D@fugue.com>, Ted Lemon
> > writes:
> > >
> > > On Aug 1, 2017, at 1:57 PM, Ted Lemon <mellon@fugue.com> wrote:
> > > > What she doesn't mention is that there is a way to detect DNS64, so i=
> n
> > > principle a validating stub resolver can do DNS64 itself _post
> > > validation_.
> > >
> > > Oops, actually she did mention that in the last paragraph=E2=80=94sorry=
> !
> >
> > You have to detect it and work around it.
> >
> > NAT64 start out with the claim "You don't have to touch the node".
> >
> > Now you have complicated CLAT and DNSSEC changes required in every
> > node in the internet to support NAT64 with more breakage than simple
> > tunneling and a NAT44 protocol translation in DS-Lite.  What's the
> > next workaround that will have to be deployed because NAT64 is being
> > used instead of NAT44 at the end of the tunnel?
> >
> > CLAT and DNSSEC changes are required on every node as they will end
> > up on IPv6-only networks.  DS-Lite also requires changes on every
> > node on IPv6-only networks but they are much less intrusive.
> >
> > We have created Frankenstein's monster here with NAT64.
> >
> > Mark
> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
> >
> 
> --94eb2c0de54cf091f30555badf94
> Content-Type: text/html; charset="UTF-8"
> Content-Transfer-Encoding: quoted-printable
> 
> <div dir=3D"ltr">Actually CLAT+NAT64 doesn&#39;t require changes on the nod=
> e. =C2=A0 I don&#39;t disagree with the rest of what you said (aside from t=
> he Frankenstein&#39;s monster bit: Frankenstein&#39;s monster was really mi=
> sunderstood).</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote=
> ">On Tue, Aug 1, 2017 at 7:26 PM, Mark Andrews <span dir=3D"ltr">&lt;<a hre=
> f=3D"mailto:marka@isc.org" target=3D"_blank">marka@isc.org</a>&gt;</span> w=
> rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
> r-left:1px #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D=
> "h5"><br>
> In message &lt;<a href=3D"mailto:30708801-142F-47C5-A154-15E9D3C5068D@fugue=
> .com">30708801-142F-47C5-A154-<wbr>15E9D3C5068D@fugue.com</a>&gt;, Ted Lemo=
> n writes:<br>
> &gt;<br>
> &gt; On Aug 1, 2017, at 1:57 PM, Ted Lemon &lt;<a href=3D"mailto:mellon@fug=
> ue.com">mellon@fugue.com</a>&gt; wrote:<br>
> &gt; &gt; What she doesn&#39;t mention is that there is a way to detect DNS=
> 64, so in<br>
> &gt; principle a validating stub resolver can do DNS64 itself _post<br>
> &gt; validation_.<br>
> &gt;<br>
> &gt; Oops, actually she did mention that in the last paragraph=E2=80=94sorr=
> y!<br>
> <br>
> </div></div>You have to detect it and work around it.<br>
> <br>
> NAT64 start out with the claim &quot;You don&#39;t have to touch the node&q=
> uot;.<br>
> <br>
> Now you have complicated CLAT and DNSSEC changes required in every<br>
> node in the internet to support NAT64 with more breakage than simple<br>
> tunneling and a NAT44 protocol translation in DS-Lite.=C2=A0 What&#39;s the=
> <br>
> next workaround that will have to be deployed because NAT64 is being<br>
> used instead of NAT44 at the end of the tunnel?<br>
> <br>
> CLAT and DNSSEC changes are required on every node as they will end<br>
> up on IPv6-only networks.=C2=A0 DS-Lite also requires changes on every<br>
> node on IPv6-only networks but they are much less intrusive.<br>
> <br>
> We have created Frankenstein&#39;s monster here with NAT64.<br>
> <span class=3D"HOEnZb"><font color=3D"#888888"><br>
> Mark<br>
> </font></span><div class=3D"HOEnZb"><div class=3D"h5">--<br>
> Mark Andrews, ISC<br>
> 1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
> PHONE: <a href=3D"tel:%2B61%202%209871%204742" value=3D"+61298714742">+61 2=
>  9871 4742</a>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
> =A0INTERNET: <a href=3D"mailto:marka@isc.org">marka@isc.org</a><br>
> </div></div></blockquote></div><br></div>
> 
> --94eb2c0de54cf091f30555badf94--
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Aug  1 18:43:02 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A71C12EC11 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 18:43:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j5ypVooVDgsk for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 18:43:00 -0700 (PDT)
Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D03312942F for <ietf@ietf.org>; Tue,  1 Aug 2017 18:43:00 -0700 (PDT)
Received: by mail-qt0-x235.google.com with SMTP id 16so19345136qtz.4 for <ietf@ietf.org>; Tue, 01 Aug 2017 18:43:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=gjl8PBpLLjckAkQBGxywiww4Le04iSBx14pthAmmr4U=; b=GQ4H59Jy2KEqOx+hWJkczK1nLiFe0kOGc3LCf3B4yKK/LD8V7sUke8Lm37QhmXEuYm I0NWrJKQe6feGF3WPjQqiGLOLiitflXj2Gt/YGc72ARWKr9e5UHYmt35z+Xyjbm/12oW uiIpodN0idhHFQLRWUxN/ITZpT/HhePLrXc2jvTHoV5tzYfbQmsvT9by7koF96PvuzEk kB+cU4E3dBznqz+S/vsb+bfe7wz3T/uuV29r2c8V7kWOeb1xzzX47NXau1JGtvzC8YyR B2nbL2YI+Q2cZaGav3ZvDsiqeUiWf1XV7+Uw5enBAeFPCIjqy6RA/y2ic7FSRTFcqg13 ypNA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=gjl8PBpLLjckAkQBGxywiww4Le04iSBx14pthAmmr4U=; b=BCL1O2/W+vBDOccVvqRjduhhOQ7EaIJ/BjyVdId/NPwz51Jba7k4X1fZZd0eK3B/Wk xFWBPzJJHRk4hr8f1qBVcNpSXmsVyfTzp8LSsG7ghagWTqrAQE2kjoT+oJOh6CcG/W7L 4Um+mDJI0MmlrcQgr/YfYvp0QOAJIcx7WcM8ZyDWMVG4xf2a5BvG4wIJW8jmqcWwqSOI JFzkMqHPHZtOM77N3CCujw1t5T5Cz72b8PCYPIssNk0tkBTxneljJcSnVUeHPHsqjhpG 49r+QxF2KRo5DI24dS3gQ6mMldwmkRkIJOkmQra/VvCPTMc7SxpBo4JXT1BJCHygXWUm WW8Q==
X-Gm-Message-State: AIVw111FP/SEobU6MtzrPJZkOIUZ69NTM54q+GaYgJZKYC/eDk7sFLiE h6EcAqSDqD4poboS
X-Received: by 10.200.52.56 with SMTP id u53mr30713657qtb.217.1501638179536; Tue, 01 Aug 2017 18:42:59 -0700 (PDT)
Received: from [10.0.30.153] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id w28sm745564qta.33.2017.08.01.18.42.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Aug 2017 18:42:58 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <CFC64369-8C1B-40AF-A414-EDBE75236D20@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3761772D-5A1A-42DD-B3C7-3168CACC2932"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Date: Tue, 1 Aug 2017 21:42:57 -0400
In-Reply-To: <20170802013806.F222B80BCE0B@rock.dv.isc.org>
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "ietf@ietf.org" <ietf@ietf.org>, "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
To: Mark Andrews <marka@isc.org>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es> <787AE7BB302AE849A7480A190F8B93300A0155F5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es> <20170801072139.316A7809B357@rock.dv.isc.org> <787AE7BB302AE849A7480A190F8B93300A0156BD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20170801145849.1660780A6174@rock.dv.isc.org> <5C3343EF-3724-4155-87BC-E169DFC38342@fugue.com> <FE8011FD-6E26-40EB-9058-A60909CD00D2@ecs.soton.ac.uk> <EMEW3|c23812222e6467c6d3ed634ad82e65b2y70ISJ03tjc|ecs.soton.ac.uk|FE8011FD-6E26-40EB-9058-A60909CD00D2@ecs.soton.ac.uk> <79B094AE-8D4B-4E30-AC8F-7F74BE8C13D2@fugue.com> <30708801-142F-47C5-A154-15E9D3C5068D@fugue.com> <2017 0801232651.7E2FF80B1398@rock.dv.isc.org> <CAPt1N1ksfcjSAf06rVzNFBD-vyLcJUxL7UdRVud9_HKk7Eiysw@mail.gmail.com> <20170802013806.F222B80BCE0B@rock.dv.isc.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wuuNx44nDQeJlWaR3kHB7gcTBpw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Aug 2017 01:43:01 -0000

--Apple-Mail=_3761772D-5A1A-42DD-B3C7-3168CACC2932
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Aug 1, 2017, at 9:38 PM, Mark Andrews <marka@isc.org> wrote:
>> Actually CLAT+NAT64 doesn't require changes on the node.   I don't =
disagree
>> with the rest of what you said (aside from the Frankenstein's monster =
bit:
>> Frankenstein's monster was really misunderstood).
>=20
> It does for IPv6-only if want to talk to IPv4 literals or talk to
> IPv4 only services when you are validating DNS answers.

I'm talking about when you have CLAT in the router.


--Apple-Mail=_3761772D-5A1A-42DD-B3C7-3168CACC2932
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;" =
class=3D"">On Aug 1, 2017, at 9:38 PM, Mark Andrews &lt;<a =
href=3D"mailto:marka@isc.org" class=3D"">marka@isc.org</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><blockquote type=3D"cite" style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">Actually CLAT+NAT64 doesn't =
require changes on the node. &nbsp;&nbsp;I don't disagree<br =
class=3D"">with the rest of what you said (aside from the Frankenstein's =
monster bit:<br class=3D"">Frankenstein's monster was really =
misunderstood).<br class=3D""></blockquote><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">It does for =
IPv6-only if want to talk to IPv4 literals or talk to</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">IPv4 only services when you are validating DNS =
answers.</span></div></div></blockquote></div><br class=3D""><div =
class=3D"">I'm talking about when you have CLAT in the router.</div><div =
class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_3761772D-5A1A-42DD-B3C7-3168CACC2932--


From nobody Tue Aug  1 19:40:19 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF690129AA0 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 19:40:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r-GIaPENQIi8 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 19:40:09 -0700 (PDT)
Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (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 971CC127B60 for <ietf@ietf.org>; Tue,  1 Aug 2017 19:40:09 -0700 (PDT)
Received: from resomta-ch2-14v.sys.comcast.net ([69.252.207.110]) by resqmta-ch2-07v.sys.comcast.net with ESMTP id cjZvd0fP6OomtcjZvdbQ6S; Wed, 02 Aug 2017 02:40:07 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-14v.sys.comcast.net with SMTP id cjZtdRbxoyqbQcjZudgSvh; Wed, 02 Aug 2017 02:40:07 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v722e40P008949; Tue, 1 Aug 2017 22:40:04 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v722e4Xj008944; Tue, 1 Aug 2017 22:40:04 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Dhruv Dhody <dhruv.dhody@huawei.com>
Cc: gen-art@ietf.org, draft-ietf-pce-pceps.all@ietf.org, pce@ietf.org, ietf@ietf.org, dhruv.ietf@gmail.com
Subject: Re: [Pce] Genart last call review of draft-ietf-pce-pceps-14
In-Reply-To: <23CE718903A838468A8B325B80962F9B8CB962D9@blreml501-mbb> (dhruv.dhody@huawei.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Tue, 01 Aug 2017 22:40:04 -0400
Message-ID: <87d18ed75n.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfIAcwgM2bU3tXwQQG0wM0ojrG+bGlxzSLlCcTA1RqCzbxW+C/RBkBzeyqQp2/b5vinyqHxLFXLgzbaeYnDL1JANB8AgRy+VkVyQoev3Fw2SDXmCuYplt AcTx1Qh9UmecW0KJmKzayTDnByNQ+ED/OzPN1fOfycniWs1Su4DewnRRQfXZOAPXM0WmNYi/Vc+6PJGv3563YWhHl8ST73uu+Ljkab23e1Ga80d3nniel+Rg Y2pjasIx/entJROnoxUQpXBfAxkMSCQigvwS04cqcmaIT3nraFTw+b/xsnDEuujDj2SOLxeAfTBuw+MwCYoRTg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/i4L3pXaRSv1rh0M8YkWLWD5wXoU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Aug 2017 02:40:11 -0000

Dhruv Dhody <dhruv.dhody@huawei.com> writes:
>> It's more complicated than that:  If a PCE does not like the first message
>> it receives, if it implements PCEPS, it replies TBA2/2.  But if it does
>> not implement PCEPS, it replies 1/1.  Similarly, a PCC may reject an
>> initial message with either of these error codes, depending on the
>> situation.  If the other endpoint does not implement PCEPS, it might be
>> surprised by receiving TBA2/2, which it has no way of understanding in
>> detail (although it will probably simply disconnect, which is what it
>> would do in reaction to a 1/1).
>> 
> [[Dhruv Dhody]] You are right about this case, which I have clarified now -  
>
>    If the PCEP speaker that only supports PCEPS connection (as a local
>    policy), receives an Open message, it MUST treat it as an unexpected
>    message and reply with a PCErr message with Error-Type set to 1 (PCEP
>    session establishment failure) and Error-value set to 1 (reception of
>    an invalid Open message or a non Open message).
>
> In your description you mentioned the error TBA2/2, but the
> description of TBA2/2 is  - 
>
>    A PCEP
>    speaker receiving any other message apart from StartTLS, Open, or
>    PCErr as the first message, MUST treat it as an unexpected message
>    and reply with a PCErr message with Error-Type set to [TBA2 by IANA]
>    (PCEP StartTLS failure) and Error-value set to 2 (reception of any
>    other message apart from StartTLS, Open, or PCErr message), and MUST
>    close the TCP connection.
>
> So receiving of open message would not trigger this error. The new
> text above would take care of that. 

I don't know if the case I'm thinking of is important enough to change
anything for, but I think it should at least be thought about.

I'm considering the situation where the TCP connection is started, and
one endpoint receives a message that it does not understand.  Not the
case where a non-implementing endpoint receives a StartTLS, but where
the message is entirely incorrect, and is neither Open nor StartTLS, or
at least, is sufficiently malformed that the receiver cannot parse it as
one of those message types.

Of course, this situation should never happen, but I expect that it is
occasionally seen, and it would be useful if it was handled in a way
that would make it easier for the humans involved to diagnose the
problem.

If the receiver of the message does not implementing PCEPS, it will send
error 1/1.  The receiver of the error (the sender of the message) will
receive 1/1, and will "understand" it and log it as something requiring
human intervention -- whether or not it implements PCEPS.

OTOH, if the receiver of the message implements PCEPS, it will send
error TBA2/2.  If the receiver of the error (the sender of the message)
implements PCEPS, it will understand it and log it as something
requiring human intervention.  However, if the receiver does not
implement PCEPS, it won't understand the error message, and will have to
log it as "I received an unknown error message".  Of course, human
inquiry will reveal that the error message was a PCEPS error message,
and its meaning is "unknown initial message", getting us back to the
previous situation.  But it seems to me that this is adding a step of
human processing where it could be avoided, and that better performance
(of the humans and the system as a whole) would be achieved in practice
if a PCEPS implementation, when it received an initial message that was
not Open or StartTLS, sent a 1/1 error in the same way as a non-PCEPS
implementation.

Dale


From nobody Tue Aug  1 22:51:47 2017
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D8171288B8 for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 22:51:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ExQ7h2VrJ-6S for <ietf@ietfa.amsl.com>; Tue,  1 Aug 2017 22:51:44 -0700 (PDT)
Received: from relais-inet.orange.com (mta239.mail.business.static.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71CF9126557 for <ietf@ietf.org>; Tue,  1 Aug 2017 22:51:44 -0700 (PDT)
Received: from opfedar03.francetelecom.fr (unknown [xx.xx.xx.5]) by opfedar21.francetelecom.fr (ESMTP service) with ESMTP id D31F41005FE; Wed,  2 Aug 2017 07:51:42 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.10]) by opfedar03.francetelecom.fr (ESMTP service) with ESMTP id B09B5180066; Wed,  2 Aug 2017 07:51:42 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM5C.corporate.adroot.infra.ftgroup ([fe80::4bd:9b2b:3651:6fba%19]) with mapi id 14.03.0352.000; Wed, 2 Aug 2017 07:51:42 +0200
From: <mohamed.boucadair@orange.com>
To: Mark Andrews <marka@isc.org>
CC: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Index: AQHTCtauir91WbwF20idGLo7UkWl3qJwiz3Q
Date: Wed, 2 Aug 2017 05:51:42 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300A015E76@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <62FE7E9A-9CC0-4DE6-93C6-61A08AC95281@consulintel.es> <787AE7BB302AE849A7480A190F8B93300A0155F5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es> <20170801072139.316A7809B357@rock.dv.isc.org> <787AE7BB302AE849A7480A190F8B93300A0156BD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20170801145849.1660780A6174@rock.dv.isc.org>
In-Reply-To: <20170801145849.1660780A6174@rock.dv.isc.org>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1fP3vai5NcNNAH2qlfXy68CPsoQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Aug 2017 05:51:46 -0000

Mark,

It seems that you missed my point (or I wasn't that clear).=20

I was answering to your claim that "Cellular networks went with anything av=
ailable". That claim is not true at all. I provided you with details about =
what was happening since 2010 when all the documents we are talking about, =
are IETF drafts (dome of them are individual drafts such as A+P). Public re=
ports are available. =20

What is important to note is there is some kind of consensus to proceed wit=
h NAT64 if you only assign IPv6 prefix to mobile handsets. That's really im=
portant for the industry instead of fragmenting required features on the ha=
ndsets. =20

Issues are known and documented for NAT64 (e.g., RFC6889, Section 3 of RFC =
7051). Some of the issues are not specific to NAT64, but apply to any IPv4 =
service continuity flavor (RFC6269). Solutions are documented for some of t=
he issues (RFC7050, RFC7225, ...).

You may disagree with the analysis, but all the proposals were on the table=
 and none of them was available in term of "stable" product at that time. W=
e worked with vendors on both Ds-Lite and NAT64 when these technologies are=
 not RFCed yet. =20

I agree that some of the issues do not apply for DS-Lite, and some of the D=
S-Lite implications on the mobile handset are removed if Gi-DS-Lite is enab=
led (RFC6674) but 6674 comes with its own set of issues that were analyzed =
too.=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: Mark Andrews [mailto:marka@isc.org]
> Envoy=E9=A0: mardi 1 ao=FBt 2017 16:59
> =C0=A0: BOUCADAIR Mohamed IMT/OLN
> Cc=A0: jordi.palet@consulintel.es; ietf@ietf.org
> Objet=A0: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for I=
ETF
> Meetings
>=20
>=20
> In message
> <787AE7BB302AE849A7480A190F8B93300A0156BD@OPEXCLILMA3.corporate.adro
> ot.infra.ftgroup>, mohamed.boucadair@orange.com writes:
> > Hi Mark,
> >
> > Answering this particular point.
> >
> > Please see inline.
> >
> > Cheers,
> > Med
> >
> > > -----Message d'origine-----
> > > De: ietf mailto:ietf-bounces@ietf.org De la part de Mark Andrews
> > > Envoy: mardi 1 aot 2017 09:22
> > > : jordi.palet@consulintel.es
> > > Cc: ietf@ietf.org
> > > Objet: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for
> > IETF
> > > Meetings
> > >
> > >
> > > In message <65D79ACB-372A-4978-9030-FFAB4967A2BD@consulintel.es>,
> JORDI
> > > PALET M
> > > ARTINEZ writes:
> > > > Hi Med,
> > > >
> > > > In line
> > > >
> > > > Saludos,
> > > > Jordi
> > > >
> > > >
> > >
> > > > It is a matter of
> > > > preference of one or another transition mechanisms. All them have
> good
> > > > and bad things. I see much simpler the combination of NAT64+CLAT
> than
> > > > DS-Lite or MAP, in addition to the ONLY support in cellular network=
s
> > is
> > > > precisely NAT64/464XLAT, which means is the MOST extended transitio=
n
> > > > mechanism by millions (billions?) of users. It makes a lot of sense
> to
> > > me
> > > > to go in all the infrastructures to the one that has more deploymen=
t
> > > > already.
> > >
> > > Not really.  Cellular networks went with anything available, rather
> > > than the best.  We are continuing the pay the price for that.
> >
> > Med Actually, no. There was an IPv6 Study Item within 3GPP. Both DS-
> Lite,
> > A+P, and NAT64 were presented and documented in a 3GPP report. For
> > example, this is what was documented for A+P:
> >
> > Known issues:
> > -	The UE needs to be modified to support A+P scheme
> > -	The gateway needs to forward not only based on IP address but
> > based on address plus port. The network needs to implement PRR in
> similar
> > places as CGN in the DS-Lite approach
> > -	The backend RADIUS system needs to be changed as subscribers can
> > no longer be identified by IP address only, but by IP address and port
> > -	In the IPv6 tunnelling approach QoS differentiation between
> > bearers cannot be provided easily
> > -	The solution works only with applications using transport
> > protocols, which have concept of port numbers (such as UDP and TCP).
> > There will be challenges with protocols which use plain IP.
> > -	The solution sets restrictions to applications within in the UE,
> > as the allocation of fixed port numbers becomes more complicated.
> > -	For ICMP messages, the UE must use an ICMP query identifier
> > within the allocated port range, otherwise the response will not be
> > received by this UE.
> >
> > Known benefits:
> >
> > -	The UE has access to public IPv4 address, which simplifies the
> > behaviour for P2P applications such as VoIP.
> > -	Allows IPv4 lifetime extension if used with GTP/GRE.
> > -	Legal requirements for tracing which traffic flow was originated
> > from which UE is simpler than in CGN solutions, as the operator does no=
t
> > need to store each flow but only A+P allocation information.
> > -	In GTP/GRE/DSMIP6 based solutions QoS can be provided.
> > -	A+P allows for an incremental migration to IPv6-only network
> > -	A+P can be fully stateless when used together with IPv6
> > -	No per-state sessions are maintained in the PLMN realm
> > -	Unlike NAT44/NAT64, no dynamic state synchronization is required
> > to ensure service robustness
> > -	No ALG is required to be implemented in the service/PLMN realm
> > -	No extra-cost on the UE to support NAT traversal techniques is
> > required
> > -	Unlike double NAT solutions, peer-to-peer services can be
> > delivered with one exception as documented in 23
> > -	No Keep-alive messages are required to maintain NAT entries. This
> > characteristic mitigates battery consumption issues induced by
> > "Always-on" services. Especially, the use of short intervals between
> > keep-alive messages has a big impact on the battery consumption (See 24
> > for more details about complications to tweak UDP timers in NAT devices
> > and also keep-alive intervals used by UE). Moreover, the network load i=
s
> > more optimized since the load induced by keep-alive messages in the
> > context of CGN solutions is avoided.
> > -	Latencies and related problems of NATs are avoided.
> >
> >
> > And for NAT64:
> >
> > =3D=3D
> > Known issues of the solution:
> >
> > -	The session binding between MS/UE IPv6 address and public IPv4
> > address/port is not known to the PCC architecture. Therefore, depending
> > on deployment and if the application is NAT aware and has access to the
> > binding (as e.g. in the case of IMS), there may or may not be issues
> with
> > applying PCC to the session.
> > -	General NAT concerns, not specific to 3GPP networks, apply. For
> > example, applications that embed IP addresses in the payload and are no=
t
> > NAT aware require additional functionality to work across NATs.
> > -	In case of roaming with Local Breakout (PGW/GGSN in VPLMN), if
> > there is a need to reach IPv4-only services, the VPLMN operator would b=
e
> > required to deploy NAT64/DNS64 in order to provide the same user
> > experience using IPv6-only connections for IPv4-only services as in
> > non-roaming scenarios.
> > -	It is unclear how IPv4 literals are supported.
>=20
> Requires EVERY DNSSEC validator on the planet to learn about DNS64.
>=20
> DS-Lite does NOT require every DNSSEC validator on the planet to
> be upgraded.
>=20
> > Known benefits of the solution
> >
> > -	This solution requires no changes to the MS/UE.
> > -	The existing bearer and session management procedures can be used
> > without any change.
>=20
> Since you are sending IPv4 as IPv6 there is no difference between NAT64
> and DNS-Lite etc.
>=20
> > -	This solution does not introduce any additional tunnelling
> > overhead on any interfaces.
>=20
> You have 1480 payloads with NAT64 and 1460 byte playloads with DS-Lite
> etc.
> Incoming 1500 byte IPv4 packets get fragmented either way as they can't
> fit in a 1500 byte IPv6 packet.
>=20
> > -	This solution has no impact to the 3GPP network architecture, no
> > new interface or network element is needed. This solution can be
> deployed
> > without any additional normative specification within 3GPP. Limitations
> > described under "known issues" above apply.
> > -	No changes to the IPv6 address-assignment procedures required.
>=20
> None required for DS-Lite either.
>=20
> > -	No bearing on the type of transport network: Transport network
> > can be IPv4 or IPv6.
> > -	NAT64 can be either co-located or separate from GGSN/PDN-GW.
>=20
> Same with DS-Lite.
>=20
> > -	Solution to the public IPv4 address exhaustion problem through
> > the use of stateful NAT64.
>=20
> Same with DS-Lite (stateful NAT again).
>=20
> > -	No impact on QoS/bearer procedures between UE and PDN GW/S GW.
> > =3D=3D=3D
>=20
> DS-Lite does NOT require every node on the planet to aquire a CLAT
> only a encapsulating interface to talk to legacy devices.
>=20
> When you ignore some of the problem space NAT64 looks ok.  When you
> look at the entire problem space that is not the case.
>=20
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Wed Aug  2 01:45:13 2017
Return-Path: <pch-b7900FA3D@u-1.phicoh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C33F131D2D for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 01:45:12 -0700 (PDT)
X-Quarantine-ID: <ky1aNGobyxNz>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Cc"
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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ky1aNGobyxNz for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 01:45:10 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id 5B1AA131C9D for <ietf@ietf.org>; Wed,  2 Aug 2017 01:45:10 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #130) id m1dcpH8-0000FsC; Wed, 2 Aug 2017 10:45:06 +0200
Message-Id: <m1dcpH8-0000FsC@stereo.hq.phicoh.net>
To: ietf@ietf.org
Cc: Ted Lemon <mellon@fugue.com>
Cc: Mark Andrews <marka@isc.org>, "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
Subject: Incremental Deployment of CLAT on the router for IETF Meetings 
From: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Sender: pch-b7900FA3D@u-1.phicoh.com
In-reply-to: Your message of "Tue, 1 Aug 2017 21:42:57 -0400 ." <CFC64369-8C1B-40AF-A414-EDBE75236D20@fugue.com> 
Date: Wed, 02 Aug 2017 10:45:04 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3n1D8CaT-DoBsHxBRTcS4fH9PSY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Aug 2017 08:45:12 -0000

>I'm talking about when you have CLAT in the router.

Maybe we can have all discussion about CLAT on the router under this 
subject?

Is there any experience with this? Did previous IETF meetings have an
experimental SSID with this setup?

I'm certainly not opposed to having the router do some sort of tunneling.
Whether it is CLAT+NAT64 or MAP-E, MAP-T. DS-Lite or what have you.

As long it provides hosts with the illusion of CGN IPv4-NAT then that's
probably the best you can expect in most places.



From nobody Wed Aug  2 01:48:47 2017
Return-Path: <prvs=138701a393=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 498B4131D36 for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 01:48: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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6QEF6PdZkSat for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 01:48:38 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48475131D34 for <ietf@ietf.org>; Wed,  2 Aug 2017 01:48:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1501663716; x=1502268516; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=uHw1AuP+C1RPfX65YT7A8jOxJ PUfdmHCphMM03Q/JMc=; b=fzESs57uc8KQgTfibFRYbLYJpBnylsIM0RRw+Ec+X 8gq5T94MLZ23YWqpfxqNSmTJbe92a6O6aLX+MKrhELoquoKhW3d910yTE8WBQceR IURZ3gBhHuM28S7TwNmUdKr4izmnQN9EkV36MX0VnWzKqWFjgf7dP9yFMfMqZYIo dI=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=JyolZyxUyE8P/8HVLAHuae4zwMlAudrBVbseuLx4B9k4eUtQMHXK/mzxB3Ll knP9rUZ4tusWXL88mcdiPwuszzoliAfOT4Csa0Au2x5SW6ctwDe6s1N2x seGB6GfigvBHyYwsQibm4URBgjsZ+WKb1fZCQt8HettBT8/mOj/5qA=;
X-MDAV-Processed: mail.consulintel.es, Wed, 02 Aug 2017 10:48:36 +0200
X-Spam-Processed: mail.consulintel.es, Wed, 02 Aug 2017 10:48:36 +0200
Received: from [10.10.10.133] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005492863.msg for <ietf@ietf.org>; Wed, 02 Aug 2017 10:48:36 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170802:md50005492863::2CLqegSd33RVlrHP:00005ckz
X-Return-Path: prvs=138701a393=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.24.1.170721
Date: Wed, 02 Aug 2017 10:48:34 +0200
Subject: Re: Incremental Deployment of CLAT on the router for IETF Meetings
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <550D6EEF-DEF2-4F35-8D66-93AC4093325F@consulintel.es>
Thread-Topic: Incremental Deployment of CLAT on the router for IETF Meetings
References: <CFC64369-8C1B-40AF-A414-EDBE75236D20@fugue.com> <m1dcpH8-0000FsC@stereo.hq.phicoh.net>
In-Reply-To: <m1dcpH8-0000FsC@stereo.hq.phicoh.net>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RUp5PlDk-3RBAZ_FoKbvQGdI8Jc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Aug 2017 08:48:40 -0000

In the Chicago (IETF 98), I=E2=80=99ve been allocated a /64 so I can run my=
 own CLAT in my laptop (I was doing it either by means of a VM with OpenWRT=
 or a VM with Ubuntu and Jool).

It was working perfectly.

Of course, I=E2=80=99ve tried that in other scenarios, including some thous=
ands of CPEs in customer networks.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Philip Homburg <pch-ietf-6@u-=
1.phicoh.com>
Responder a: <pch-ietf-6@u-1.phicoh.com>
Fecha: mi=C3=A9rcoles, 2 de agosto de 2017, 10:45
Para: <ietf@ietf.org>
CC: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
Asunto: Incremental Deployment of CLAT on the router for IETF Meetings

    >I'm talking about when you have CLAT in the router.
   =20
    Maybe we can have all discussion about CLAT on the router under this=20
    subject?
   =20
    Is there any experience with this? Did previous IETF meetings have an
    experimental SSID with this setup?
   =20
    I'm certainly not opposed to having the router do some sort of tunnelin=
g.
    Whether it is CLAT+NAT64 or MAP-E, MAP-T. DS-Lite or what have you.
   =20
    As long it provides hosts with the illusion of CGN IPv4-NAT then that's
    probably the best you can expect in most places.
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Wed Aug  2 06:56:50 2017
Return-Path: <huitema@huitema.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E1A112F280 for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 06:56:48 -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_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zSLnUjaqW3df for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 06:56:47 -0700 (PDT)
Received: from mx1.antispamcloud.com (mx36-42.antispamcloud.com [209.126.121.30]) (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 1509012008A for <ietf@ietf.org>; Wed,  2 Aug 2017 06:56:47 -0700 (PDT)
Received: from xsmtp02.mail2web.com ([168.144.250.215]) by mx1.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1dcu8i-0006jE-ES for ietf@ietf.org; Wed, 02 Aug 2017 15:56:45 +0200
Received: from [10.5.2.13] (helo=xmail03.myhosting.com) by xsmtp02.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1dcu8f-0000vo-CT for ietf@ietf.org; Wed, 02 Aug 2017 09:56:42 -0400
Received: (qmail 23114 invoked from network); 2 Aug 2017 13:56:39 -0000
Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.56.42.66]) (envelope-sender <huitema@huitema.net>) by xmail03.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf@ietf.org>; 2 Aug 2017 13:56:38 -0000
To: ietf@ietf.org
References: <CFC64369-8C1B-40AF-A414-EDBE75236D20@fugue.com> <m1dcpH8-0000FsC@stereo.hq.phicoh.net> <550D6EEF-DEF2-4F35-8D66-93AC4093325F@consulintel.es>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <11cca0e7-08d5-f644-81a5-cf3e9d642606@huitema.net>
Date: Wed, 2 Aug 2017 06:56:36 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <550D6EEF-DEF2-4F35-8D66-93AC4093325F@consulintel.es>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: Incremental Deployment of CLAT on the router for IETF Meetings
X-Originating-IP: 168.144.250.215
X-SpamExperts-Domain: xsmtpout.mail2web.com
X-SpamExperts-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-SpamExperts-Outgoing-Class: ham
X-SpamExperts-Outgoing-Evidence: Combined (0.05)
X-Recommended-Action: accept
X-Filter-ID: PqwsvolAWURa0gwxuN3S5YEa3T7JuZT23fGO2rGt3ZgTCGhDnudOJ80D1c8rffxrus7BTv7Ss8cH d2IQQuvdbtM+m4WpRRDP6YzwkAPgQJYWwktM+UPDyXniaU9ttNgkND46yZLY9QyX+cRXmooQ3hum JwiT+2brWmQlzkLIcXivpIH4ag6BM/+u9ym+BA23gNO8a0DRnNX++fsR3hB4kE5SvzZFcn5J62ab Al4JpFbVk2WImtYbOEz8ROevI2d8YOEkjsX7F8KmpUaZQHV+SZbCEQkE+Ttak7yNVmHZUfi2G5Pj 7iQJEmtNUzH3idZ6uMF2OhyCCCV83x+RZrKIj0QqMGQOSwmEPwP4wBzM77N8GvkYGGDFjg9NrmGY yNnXsSjdYwfRhjHqxQXDsBKLpPLwHqwRykc1ByOUA6hOga/6lO4FGen962xgCFRckncKfg1XSK9P 1z/R6plfrFWGyZCdrcs5Z3q7JGGisMbxE7feNHk15VolAGHS5rCXQKDym+Gab6cuAPzLi/SdAxlO dgkraHgbbAuZgv0Q6mJ3vUcipz1IT62ZEk6+MmovaufbiR3bHfnMCIEU+nrglojKwMr3vOY18GvB wSXAfWcj237p0djsrZ/k7aFJneAV66i3WezJa7xDQcOg5ET5/LmCvfowf2dVtQw0TRxkBmGNERww /+ZimU+N4fvn04Xlox1kmz3NJmJzTE1T6wyg1SHXCw4gSiiwGe0nWoCpGccCSAmgGl1aPxAtivmw 3hSDPS17qAoEr1A/pA8bSBvJitlJki2wErj03uQL9OSP3oAqkbgmxYRXOZgzdAQCjuYKoBVKyLoA 6S28+bT6JBt5hIe9NsT+zJGLhBRfUiVo7tDfe92IvYPtoBVPF/cFj7Q8A7EvMLn6MURQGfriekzS 9Ga3AA==
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lC4opA6ruLZDc9Tt1ZEv3LGZpFk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Aug 2017 13:56:48 -0000

On 8/2/2017 1:48 AM, JORDI PALET MARTINEZ wrote:
> In the Chicago (IETF 98), I=E2=80=99ve been allocated a /64 so I can ru=
n my own CLAT in my laptop (I was doing it either by means of a VM with O=
penWRT or a VM with Ubuntu and Jool).
>
> It was working perfectly.
>
> Of course, I=E2=80=99ve tried that in other scenarios, including some t=
housands of CPEs in customer networks.

I have no doubt that a combination of IPv6 native and network provided
CLAT will work. It effectively provides devices with a dual stack
service, native IPv6 and natted IPv4. We know that dual stack works --
it has been the default service on the main IETF network for years. We
also know that natted IPv4 kind of works -- that's what most customers
have been getting for many years, and most applications have adapted by n=
ow.

But then, why deploy that on the main IETF network? IPv6 plus natted
IPv4 is definitely less cool than IPv6 plus native IPv4, which is what
the network has traditionally provided.

-- Christian Huitema



--=20
Christian Huitema



From nobody Wed Aug  2 07:10:16 2017
Return-Path: <prvs=138701a393=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85630126C83 for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 07:10:15 -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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oj-mihYaZ_YK for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 07:10:13 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71C82126BFD for <ietf@ietf.org>; Wed,  2 Aug 2017 07:10:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1501683009; x=1502287809; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=tJwoEkWuNgEesJN0fs6/QD2qw AdzOTp04vjFJel+i64=; b=h4znFwJkTzfE/y6kBmyRw4Vxml6EkAE3mGigFWugE BZ5S3qVa7pNK7MQ8lhzTXPBaZTMeEjf7tn73AhygT3avveDHz3RjFtpXpCMCfLMs Q+mySs023QdpV28zhzFHwyXIL9hM3F/Qg0Kkq64kWeeJByq3qXmf9XYmSZBQXifT bY=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=ZGDhCWirf1en72EEhigl/JBId1WkM1hcm01j/qjMPlPsxMzWLrD8+A0q0II+ uPeeyPRtMwAz3NPLEOrPIUdLp3vILdlmI9up33m6rfkw9N6lanGc8O9w7 /kB35k4FmkWQvgOfwxnC12PanQiKb0huGBLyxFgGw1UikUtM4lUuCY=;
X-MDAV-Processed: mail.consulintel.es, Wed, 02 Aug 2017 16:10:09 +0200
X-Spam-Processed: mail.consulintel.es, Wed, 02 Aug 2017 16:10:08 +0200
Received: from [10.10.10.133] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005493068.msg for <ietf@ietf.org>; Wed, 02 Aug 2017 16:10:07 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170802:md50005493068::PGtin252U+7jAHvd:00002CEy
X-Return-Path: prvs=138701a393=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.24.1.170721
Date: Wed, 02 Aug 2017 16:10:04 +0200
Subject: Re: Incremental Deployment of CLAT on the router for IETF Meetings
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <4C8B7472-F866-447B-A731-AD6EEC57648D@consulintel.es>
Thread-Topic: Incremental Deployment of CLAT on the router for IETF Meetings
References: <CFC64369-8C1B-40AF-A414-EDBE75236D20@fugue.com> <m1dcpH8-0000FsC@stereo.hq.phicoh.net> <550D6EEF-DEF2-4F35-8D66-93AC4093325F@consulintel.es> <11cca0e7-08d5-f644-81a5-cf3e9d642606@huitema.net>
In-Reply-To: <11cca0e7-08d5-f644-81a5-cf3e9d642606@huitema.net>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/e_5LY508azjwn7EVaoiJfKLZDz0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Aug 2017 14:10:15 -0000

Because that is the =E2=80=9Ccloser=E2=80=9D thing we are going to get in t=
he user and corporate networks in the next few years.

IETF has not used before IPv4-NAT, so yes, is less cool, but is more *real =
world* and if we want to make sure that users don=E2=80=99t get into troubl=
es, we should get that dogfood.

By the way, I=E2=80=99m starting to think that before continuing this discu=
ssion, we should understand (and the NOC folks are probably the right ones =
to confirm) if we still believe that the main SSID should be a stable produ=
ction network or open to trying things =E2=80=A6

I asked a few emails ago, what is our target with any change in the main SS=
ID, for example:
1) Try real world (real world has IPv4 behind NAT), using for example CLAT,=
 so the WAN can be IPv6-only
2) Try IPv6-only in the LAN, which we know many things will fail if they us=
e literal IPv4 addresses
3) Something else?
4) Marketing =E2=80=9Chey we are the IETF, we use IPv6-only, everything wor=
ks=E2=80=9D which can never be true, because if anyone has an IPv4 only dev=
ice or app, will not work =E2=80=A6 It is better marketing to make sure tha=
t CPEs and OS support CLAT so nothing gets broken?

Is the reason to report to app/developers what is broken? Who is going to r=
eport that?

Can we enforce them to sort it out? If the answer is not, then it makes sen=
se to ensure that we have mechanisms such as CLAT to avoid users get broken=
 things, right?

If we want to try broken apps, is the IETF the right network or we should l=
ook for app/developers conferences?

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Christian Huitema <huitema@hu=
itema.net>
Responder a: <huitema@huitema.net>
Fecha: mi=C3=A9rcoles, 2 de agosto de 2017, 15:57
Para: <ietf@ietf.org>
Asunto: Re: Incremental Deployment of CLAT on the router for IETF Meetings

   =20
   =20
    On 8/2/2017 1:48 AM, JORDI PALET MARTINEZ wrote:
    > In the Chicago (IETF 98), I=E2=80=99ve been allocated a /64 so I can =
run my own CLAT in my laptop (I was doing it either by means of a VM with O=
penWRT or a VM with Ubuntu and Jool).
    >
    > It was working perfectly.
    >
    > Of course, I=E2=80=99ve tried that in other scenarios, including some=
 thousands of CPEs in customer networks.
   =20
    I have no doubt that a combination of IPv6 native and network provided
    CLAT will work. It effectively provides devices with a dual stack
    service, native IPv6 and natted IPv4. We know that dual stack works --
    it has been the default service on the main IETF network for years. We
    also know that natted IPv4 kind of works -- that's what most customers
    have been getting for many years, and most applications have adapted by=
 now.
   =20
    But then, why deploy that on the main IETF network? IPv6 plus natted
    IPv4 is definitely less cool than IPv6 plus native IPv4, which is what
    the network has traditionally provided.
   =20
    -- Christian Huitema
   =20
   =20
   =20
    --=20
    Christian Huitema
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Wed Aug  2 07:43:46 2017
Return-Path: <huitema@huitema.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A114132113 for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 07:43:45 -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_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7fwHqZnczbEe for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 07:43:44 -0700 (PDT)
Received: from mx1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 220B9131CA2 for <ietf@ietf.org>; Wed,  2 Aug 2017 07:43:44 -0700 (PDT)
Received: from xsmtp03.mail2web.com ([168.144.250.223]) by mx1.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1dcus9-0007QQ-7m for ietf@ietf.org; Wed, 02 Aug 2017 16:43:42 +0200
Received: from [10.5.2.14] (helo=xmail04.myhosting.com) by xsmtp03.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1dcus6-00025x-Cs for ietf@ietf.org; Wed, 02 Aug 2017 10:43:39 -0400
Received: (qmail 31994 invoked from network); 2 Aug 2017 14:43:36 -0000
Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.56.42.66]) (envelope-sender <huitema@huitema.net>) by xmail04.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf@ietf.org>; 2 Aug 2017 14:43:36 -0000
To: ietf@ietf.org
References: <CFC64369-8C1B-40AF-A414-EDBE75236D20@fugue.com> <m1dcpH8-0000FsC@stereo.hq.phicoh.net> <550D6EEF-DEF2-4F35-8D66-93AC4093325F@consulintel.es> <11cca0e7-08d5-f644-81a5-cf3e9d642606@huitema.net> <4C8B7472-F866-447B-A731-AD6EEC57648D@consulintel.es>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <0ef07ade-29f3-0365-fdb6-6b0f814aed20@huitema.net>
Date: Wed, 2 Aug 2017 07:43:34 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <4C8B7472-F866-447B-A731-AD6EEC57648D@consulintel.es>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: Incremental Deployment of CLAT on the router for IETF Meetings
X-Originating-IP: 168.144.250.223
X-SpamExperts-Domain: xsmtpout.mail2web.com
X-SpamExperts-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-SpamExperts-Outgoing-Class: unsure
X-SpamExperts-Outgoing-Evidence: Combined (0.11)
X-Recommended-Action: accept
X-Filter-ID: PqwsvolAWURa0gwxuN3S5YEa3T7JuZT23fGO2rGt3ZgTCGhDnudOJ80D1c8rffxrus7BTv7Ss8cH d2IQQuvdbtM+m4WpRRDP6YzwkAPgQJbFuHJrd6q7ImwszS9kW0E9ND46yZLY9QyX+cRXmooQ3hum JwiT+2brWmQlzkLIcXivpIH4ag6BM/+u9ym+BA23nydjqbtEt5ZOavNKYegBy+nAK+xr92ZGK1ua sQ+8DmhCGag15OHxxvx1S6pDAO16YOEkjsX7F8KmpUaZQHV+Sf+k51CV8HOoCp+bWB2rXxO2G5Pj 7iQJEmtNUzH3idZ6uMF2OhyCCCV83x+RZrKIj0QqMGQOSwmEPwP4wBzM77N8GvkYGGDFjg9NrmGY yNnXsSjdYwfRhjHqxQXDsBKLpGhWDl86FRLsucalajANCRP6lO4FGen962xgCFRckncKfg1XSK9P 1z/R6plfrFWGybMPXnJfes3Hz31QbO9er5beNHk15VolAGHS5rCXQKDym+Gab6cuAPzLi/SdAxlO dgkraHgbbAuZgv0Q6mJ3vUcipz1IT62ZEk6+MmovaufbiR3bHfnMCIEU+nrglojKwMr3vOY18GvB wSXAfWcj237p0djsrZ/k7aFJneAV66i3WezJa7xDQcOg5ET5/LmCvakjSWDcjZyDseb0cBFM1p7J 0ZI2Cud2W8ULqpclZpX6sJqelmxqtloshGkSoDyZkT9+DGUWcLTBDsB1igut165iLeMY0T0TiosZ tAlQKhSNegoSoST68afndNTe7dXdZHBZ7pmcPPET1gsbqYqsHO2B1AyhUYt13ZFWiMbSDOe6Tsut 9Ntwqm/jmjsUXZwk2AT7Y9cRih4Det7+7EbH8nODKT3aoSO0YRIXZRhTMuREr8hUVhe7ugL65f2h l2QLng==
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Hk48VcRIDurRnxnt4YTd2Qzq7ng>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Aug 2017 14:43:45 -0000

On 8/2/2017 7:10 AM, JORDI PALET MARTINEZ wrote:

> I asked a few emails ago, what is our target with any change in the mai=
n SSID, for example:
> 1) Try real world (real world has IPv4 behind NAT), using for example C=
LAT, so the WAN can be IPv6-only
> 2) Try IPv6-only in the LAN, which we know many things will fail if the=
y use literal IPv4 addresses
> 3) Something else?
> 4) Marketing =E2=80=9Chey we are the IETF, we use IPv6-only, everything=
 works=E2=80=9D which can never be true, because if anyone has an IPv4 on=
ly device or app, will not work =E2=80=A6 It is better marketing to make =
sure that CPEs and OS support CLAT so nothing gets broken?
The actual goal of the main IETF network? From the beginning, it has
been "provide the best possible Internet connectivity to IETF
participants." Which for us today means dual stack, native IPv4 and
IPv6, and high bandwidth. That message was repeated quite loudly on the
list. The rough consensus is that any experiment should be opt-in, on a
separate network.

Would that change some day? Yes, very possibly, because of evolving
infrastructure and costs. We could see a situation where providing
native IPv4 connectivity is becoming too hard, or too expensive. If that
happened today, switching to IPv6 plus CLAT would make sense. I assume
that this is a long way from happening, but I have not seen the break
down of the costs.

As for the marketing statement today, it is simple. We do use IPv6 in a
dual stack configuration. Dual stack has been the official IPv6
transition strategy for years, so there is really nothing wrong in
saying that the IETF uses it.

-- Christian Huitema


From nobody Wed Aug  2 07:51:55 2017
Return-Path: <prvs=138701a393=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A4D51319B4 for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 07:51:53 -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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: 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_xLwEhciCGD for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 07:51:52 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE28B126BFD for <ietf@ietf.org>; Wed,  2 Aug 2017 07:51:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1501685509; x=1502290309; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=5mKsTHndSe4VGRN2bDy93+NPB FG/eo8RIystGy7iONI=; b=rwvpPKn+Ck4fm4Sd3ldgFN5yJxTZ/kWG9VT3m5ouB LaHC7vQ9uambCYYtTsZCuKl5scBtmMRAYedgECR7nf/sDcgScQz/vsmW9WqDgTQW zM4STlE2U9k8XAH5Q8vuW9gYdgv93BhRih487Y7275ylRs2UnhrM/QzN26+kERoB d4=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=WuQ+oIkprJm9q/Px1/UQZzCzwNvsiompGvv0vydVTZsMA4R7IGB+VLQBeeW8 9boVfuaziYAsahdd1f1OOXUxEiQhgFvmANyYBC3zi3rEQD5WyihJkj8dv o3g9e3TbIKBDqxeumxpKfNnPRXVs+DdUekIosfVrAx6+122LC8hmcc=;
X-MDAV-Processed: mail.consulintel.es, Wed, 02 Aug 2017 16:51:49 +0200
X-Spam-Processed: mail.consulintel.es, Wed, 02 Aug 2017 16:51:49 +0200
Received: from [10.10.10.133] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005493086.msg for <ietf@ietf.org>; Wed, 02 Aug 2017 16:51:48 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170802:md50005493086::vvs0zLWSZUt2nPPX:000021Tn
X-Return-Path: prvs=138701a393=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.24.1.170721
Date: Wed, 02 Aug 2017 16:51:45 +0200
Subject: Re: Incremental Deployment of CLAT on the router for IETF Meetings
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <04D8F0A9-18A0-418C-9AB3-9D01CBC06B90@consulintel.es>
Thread-Topic: Incremental Deployment of CLAT on the router for IETF Meetings
References: <CFC64369-8C1B-40AF-A414-EDBE75236D20@fugue.com> <m1dcpH8-0000FsC@stereo.hq.phicoh.net> <550D6EEF-DEF2-4F35-8D66-93AC4093325F@consulintel.es> <11cca0e7-08d5-f644-81a5-cf3e9d642606@huitema.net> <4C8B7472-F866-447B-A731-AD6EEC57648D@consulintel.es> <0ef07ade-29f3-0365-fdb6-6b0f814aed20@huitema.net>
In-Reply-To: <0ef07ade-29f3-0365-fdb6-6b0f814aed20@huitema.net>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WB6SNZA-PIHfU82Lj-n08CamrOs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Aug 2017 14:51:53 -0000

Then I guess we fully agree, and I believe I was the first one reminding th=
at our network is a production one =E2=80=A6

As we already had a NAT64 SSID for some time, the right step for IETF100 wi=
ll be then to have a CLAT SSID, so it can be tested by those folks that wan=
t to test it.

I=E2=80=99m happy to help the NOC team to do that if they need help.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Christian Huitema <huitema@hu=
itema.net>
Responder a: <huitema@huitema.net>
Fecha: mi=C3=A9rcoles, 2 de agosto de 2017, 16:44
Para: <ietf@ietf.org>
Asunto: Re: Incremental Deployment of CLAT on the router for IETF Meetings

    On 8/2/2017 7:10 AM, JORDI PALET MARTINEZ wrote:
   =20
    > I asked a few emails ago, what is our target with any change in the m=
ain SSID, for example:
    > 1) Try real world (real world has IPv4 behind NAT), using for example=
 CLAT, so the WAN can be IPv6-only
    > 2) Try IPv6-only in the LAN, which we know many things will fail if t=
hey use literal IPv4 addresses
    > 3) Something else?
    > 4) Marketing =E2=80=9Chey we are the IETF, we use IPv6-only, everythi=
ng works=E2=80=9D which can never be true, because if anyone has an IPv4 on=
ly device or app, will not work =E2=80=A6 It is better marketing to make su=
re that CPEs and OS support CLAT so nothing gets broken?
    The actual goal of the main IETF network? From the beginning, it has
    been "provide the best possible Internet connectivity to IETF
    participants." Which for us today means dual stack, native IPv4 and
    IPv6, and high bandwidth. That message was repeated quite loudly on the
    list. The rough consensus is that any experiment should be opt-in, on a
    separate network.
   =20
    Would that change some day? Yes, very possibly, because of evolving
    infrastructure and costs. We could see a situation where providing
    native IPv4 connectivity is becoming too hard, or too expensive. If tha=
t
    happened today, switching to IPv6 plus CLAT would make sense. I assume
    that this is a long way from happening, but I have not seen the break
    down of the costs.
   =20
    As for the marketing statement today, it is simple. We do use IPv6 in a
    dual stack configuration. Dual stack has been the official IPv6
    transition strategy for years, so there is really nothing wrong in
    saying that the IETF uses it.
   =20
    -- Christian Huitema
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Wed Aug  2 08:04:16 2017
Return-Path: <huitema@huitema.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AA9F13211D for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 08:04:15 -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_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EGYi4tTslWa3 for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 08:04:14 -0700 (PDT)
Received: from mx3.antispamcloud.com (mx36-42.antispamcloud.com [209.126.121.30]) (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 D9EC2131E96 for <ietf@ietf.org>; Wed,  2 Aug 2017 08:04:13 -0700 (PDT)
Received: from xsmtp01.mail2web.com ([168.144.250.230]) by mx3.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1dcvBu-00040i-CM for ietf@ietf.org; Wed, 02 Aug 2017 17:04:12 +0200
Received: from [10.5.2.49] (helo=xmail11.myhosting.com) by xsmtp01.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1dcvBr-0004sf-Qw for ietf@ietf.org; Wed, 02 Aug 2017 11:04:04 -0400
Received: (qmail 21059 invoked from network); 2 Aug 2017 15:04:02 -0000
Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.56.42.66]) (envelope-sender <huitema@huitema.net>) by xmail11.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf@ietf.org>; 2 Aug 2017 15:04:02 -0000
To: ietf@ietf.org
References: <CFC64369-8C1B-40AF-A414-EDBE75236D20@fugue.com> <m1dcpH8-0000FsC@stereo.hq.phicoh.net> <550D6EEF-DEF2-4F35-8D66-93AC4093325F@consulintel.es> <11cca0e7-08d5-f644-81a5-cf3e9d642606@huitema.net> <4C8B7472-F866-447B-A731-AD6EEC57648D@consulintel.es> <0ef07ade-29f3-0365-fdb6-6b0f814aed20@huitema.net> <04D8F0A9-18A0-418C-9AB3-9D01CBC06B90@consulintel.es>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <f911167e-d6ad-d037-d10e-53c4a9c4adc8@huitema.net>
Date: Wed, 2 Aug 2017 08:04:00 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <04D8F0A9-18A0-418C-9AB3-9D01CBC06B90@consulintel.es>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: Incremental Deployment of CLAT on the router for IETF Meetings
X-Originating-IP: 168.144.250.230
X-SpamExperts-Domain: xsmtpout.mail2web.com
X-SpamExperts-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-SpamExperts-Outgoing-Class: ham
X-SpamExperts-Outgoing-Evidence: Combined (0.09)
X-Recommended-Action: accept
X-Filter-ID: PqwsvolAWURa0gwxuN3S5YEa3T7JuZT23fGO2rGt3ZgTCGhDnudOJ80D1c8rffxrus7BTv7Ss8cH d2IQQuvdbtM+m4WpRRDP6YzwkAPgQJZYP2pkjqshrWYL747BjInHND46yZLY9QyX+cRXmooQ3hum JwiT+2brWmQlzkLIcXivpIH4ag6BM/+u9ym+BA23XjJdPnP9tXp4ahLBExHqHPzLO0shYmHPpSXw 3S8A3Aq8sdvCcJXfTGa++mgl13RpYOEkjsX7F8KmpUaZQHV+SejOO+5k046wqf0SEutzqoO2G5Pj 7iQJEmtNUzH3idZ6uMF2OhyCCCV83x+RZrKIj0QqMGQOSwmEPwP4wBzM77N8GvkYGGDFjg9NrmGY yNnXsSjdYwfRhjHqxQXDsBKLpOWca0Z0beD6jMx95O4U5K/6lO4FGen962xgCFRckncKfg1XSK9P 1z/R6plfrFWGyZfwLq/yk8jU+0+8IkEU8gzeNHk15VolAGHS5rCXQKDym+Gab6cuAPzLi/SdAxlO dgkraHgbbAuZgv0Q6mJ3vUcipz1IT62ZEk6+MmovaufbiR3bHfnMCIEU+nrglojKwMr3vOY18GvB wSXAfWcj237jnExji3pN9ZwHGBHd3j58WezJa7xDQcOg5ET5/LmCvfowf2dVtQw0TRxkBmGNERww /+ZimU+N4fvn04Xlox1kmz3NJmJzTE1T6wyg1SHXC7Li3gtrko6MGyhLLmKXHt8078I0y+3uS4dN KiUgYTBU2xkGFU6AjJ05hwL5FulvHYAbiteDwjw8P7mx/NBHSRWxZaHLvUGmD7PXY2RS8idsz7fr MHsNPRylYAkPvY1HttQOF909qtkcRbvucYBIc/TSiGRBfhCjzofKjrwJNQRY0i13zjCiwPgdt77s k1WBMw==
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2RPiHRb8VYDcpaBMqAQrECLeXwA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Aug 2017 15:04:15 -0000

On 8/2/2017 7:51 AM, JORDI PALET MARTINEZ wrote:
> Then I guess we fully agree, and I believe I was the first one remindin=
g that our network is a production one =E2=80=A6
>
> As we already had a NAT64 SSID for some time, the right step for IETF10=
0 will be then to have a CLAT SSID, so it can be tested by those folks th=
at want to test it.
>
> I=E2=80=99m happy to help the NOC team to do that if they need help.
>
> Regards,
> Jordi

That would be good, especially if the CLAT network did NOT include any
DNS64 function. There is a growing suspicion that hacking the DNS in the
name of IPv6 transition was a really bad idea. we have heard it many
times -- breaking DNSSEC, not working with VPN, or Netflix, or Skype.
Also, we know that a large fraction of DNS query are served by Google
DNS and other global providers, which means that the DNS64 hacking
server will not see them. So, if we could demonstrate that DNS64 is not
needed for transition, that would be great.

-- Christian Huitema


--=20
Christian Huitema



From nobody Wed Aug  2 13:00:17 2017
Return-Path: <michael.breuer@ilsf.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C08B132167 for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 13:00:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GC6QhnGPPMDD for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 13:00:13 -0700 (PDT)
Received: from vwp3261.webpack.hosteurope.de (vwp3261.webpack.hosteurope.de [IPv6:2a01:488:42:1000:57e6:2d0c::]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 502AA13209B for <ietf@ietf.org>; Wed,  2 Aug 2017 13:00:13 -0700 (PDT)
Received: from [2a01:598:8886:61e9:40e2:4795:46e2:b7ff] (helo=boell.ac.ilsf.de); authenticated by vwp3261.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1dczoR-0001O1-00; Wed, 02 Aug 2017 22:00:11 +0200
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
To: ietf@ietf.org
References: <m1dcUV1-0000FGC@stereo.hq.phicoh.net>
From: Michael Breuer <michael.breuer@ilsf.de>
Openpgp: id=93EDD6E843159956FCA31698DB0B3B15EB351B72
Message-ID: <32d2a319-d0ac-078c-e069-9d1a287fd7cc@ilsf.de>
Date: Wed, 2 Aug 2017 22:00:11 +0200
User-Agent: Mozilla/5.0 (X11; OpenBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <m1dcUV1-0000FGC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-bounce-key: webpack.hosteurope.de; michael.breuer@ilsf.de; 1501704013; 9cf0496f; 
X-HE-SMSGID: 1dczoR-0001O1-00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mr0ArV1TiA0VFE76qn8FlhczoIk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Aug 2017 20:00:15 -0000

On 08/01/17 12:34, Philip Homburg wrote:
>> Is precisely what CLAT (464XLAT) is resolving.
> 
> So we have a standard way of delivering IPv4 over wifi. It actually works.
> It is used by billions of people every day without even thinking about it.
> By all measures a great success.
> 
> We also have a way of delivering IPv6 over wifi. In typical IETF fashion 
> we try to break that as much as possible. But it can be made to work.
> 
> So obviously this is way too boring. We have both IPv4 and IPv6 that work.
> We need to do something, anything.
> 
> So NAT64 enters the stage. At first NAT64 was used to solve a problem in
> the mobile networks where you cannot have dual stack for reasons only telco's 
> understand.
> 
> But now we can use that same technology to spice up the wifi landscape a bit
> more.
> 
> First we confusingly call it 'IPv6-only'. There is nothing IPv6-only about
> NAT64. It is a technology specifically designed to provide access to the
> IPv4 world.
> 

To me it seems there is a lot of confusion and mixing up IPv6-only and
NAT64, but at least for the IETF network they are two different
networks. On https://tickets.meeting.ietf.org/wiki/IETF99network the
ssid *ietf-v6ONLY* is described as "v6 only" and the ssid *ietf-nat64*
in contrast as "v6 with NAT64 & DNS64".


> Then, because of the fancy name 'IPv6-only' we claim it is the future. No
> need to justify why modifying all hosts and making the whole system more
> complex would be a reasonable future.
> 
> We have something that works today. We have plenty of experience delivering
> what works today. No need to push overly complex technologies that offer
> nothing more than a fancy name. That's not engineering, that's a hobby.
> 


From nobody Wed Aug  2 13:44:36 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D212313216E for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 13:44:34 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x28qSeRjKA1k for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 13:44:33 -0700 (PDT)
Received: from mail-pg0-x22e.google.com (mail-pg0-x22e.google.com [IPv6:2607:f8b0:400e:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 769A212741D for <ietf@ietf.org>; Wed,  2 Aug 2017 13:44:32 -0700 (PDT)
Received: by mail-pg0-x22e.google.com with SMTP id y129so25599467pgy.4 for <ietf@ietf.org>; Wed, 02 Aug 2017 13:44:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=/ELl8/Cgh5mzJpU9mztMHlhHLdqayZakvjhcLp83MOs=; b=YhALGAbifcS38lJvAuIprAyhuDSk6CRWay8VAXnvN/RO0BAysrJLw3Jr5QtRdFMG7w TWLNsaW4wkGkWUIrnNFb/zUskvozhMWe1sn+MXBp6zgtc9hGgfMp1r38oE1H3CGwGmOn 5A8IcyvPwJ04LvzKc52kk7OTDZutPJbbqtEoFcAynsXdUWzqGzRus6udKCaLMqLhlmNG dyQH+kFlfRiSb73Lc0gXaa+iO0CKKoiBv4f1vD0up5T/v/sH5BMB7sudueZ265P7xLcA gF8yM8zBfmjCFNkOA0dE8PE8jkqNYgZFrmauisFNBC7zfa/Kprr5hnZ0UnvtXqItA2DP p7FA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=/ELl8/Cgh5mzJpU9mztMHlhHLdqayZakvjhcLp83MOs=; b=KQQ16PcNxgLDxH5hOUZyy0tKSKTUOYp0QOJu06Hs/q9Dh0z5vfc9n0RrkpfsLpD3JI dXECBZxwgFDo1Bb2IUX/09+C2h653m4Z7Xk2pM/uA6FAhjT2auS/jU23sx9C65ud1SNu c6XHlEBq8r2ZbEooa38ccQE55iWzUBi2cDQSTDeNqNTas0/nrPyk5mya+U8WV1NcBx+8 dqiNDClgbOqS3u00g7BhF7tF4M8Yy9fJkdpWw3px5zJkjBPgtmzuBbuqsp71rNjzFDR1 kl7w1wLp1lt+cCkLR8kZRgNotA5g82oHZqbbH3tr5mQewdacQG1u02ISdruR3QlYLXTg MzHg==
X-Gm-Message-State: AIVw110H8akbkilXCTe/epq8G2U9n+x8sJzPcz5PmF+7YYaWrKYK//E5 QnhiuiM7EYsxVqUx
X-Received: by 10.99.96.145 with SMTP id u139mr24357056pgb.347.1501706671844;  Wed, 02 Aug 2017 13:44:31 -0700 (PDT)
Received: from ?IPv6:2406:e007:521f:1:28cc:dc4c:9703:6781? ([2406:e007:521f:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id o186sm56961103pfo.155.2017.08.02.13.44.29 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 02 Aug 2017 13:44:30 -0700 (PDT)
Subject: Re: Incremental Deployment of CLAT on the router for IETF Meetings
To: ietf@ietf.org
References: <CFC64369-8C1B-40AF-A414-EDBE75236D20@fugue.com> <m1dcpH8-0000FsC@stereo.hq.phicoh.net> <550D6EEF-DEF2-4F35-8D66-93AC4093325F@consulintel.es> <11cca0e7-08d5-f644-81a5-cf3e9d642606@huitema.net> <4C8B7472-F866-447B-A731-AD6EEC57648D@consulintel.es> <0ef07ade-29f3-0365-fdb6-6b0f814aed20@huitema.net> <04D8F0A9-18A0-418C-9AB3-9D01CBC06B90@consulintel.es> <f911167e-d6ad-d037-d10e-53c4a9c4adc8@huitema.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <0687d4f1-82d9-6a09-6e36-d9738bcef5dd@gmail.com>
Date: Thu, 3 Aug 2017 08:44:33 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <f911167e-d6ad-d037-d10e-53c4a9c4adc8@huitema.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/447T-5G5JlysrleyJOC4jwLfMtQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Aug 2017 20:44:35 -0000

On 03/08/2017 03:04, Christian Huitema wrote:
>=20
>=20
> On 8/2/2017 7:51 AM, JORDI PALET MARTINEZ wrote:
>> Then I guess we fully agree, and I believe I was the first one remindi=
ng that our network is a production one =E2=80=A6
>>
>> As we already had a NAT64 SSID for some time, the right step for IETF1=
00 will be then to have a CLAT SSID, so it can be tested by those folks t=
hat want to test it.
>>
>> I=E2=80=99m happy to help the NOC team to do that if they need help.
>>
>> Regards,
>> Jordi
>=20
> That would be good, especially if the CLAT network did NOT include any
> DNS64 function. There is a growing suspicion that hacking the DNS in th=
e
> name of IPv6 transition was a really bad idea. we have heard it many
> times -- breaking DNSSEC, not working with VPN, or Netflix, or Skype.
> Also, we know that a large fraction of DNS query are served by Google
> DNS and other global providers, which means that the DNS64 hacking
> server will not see them. So, if we could demonstrate that DNS64 is not=

> needed for transition, that would be great.

Yes. The fact of life is that most of us live with NAT44 anyway; I don't
like it, but there is nothing I do regularly that is broken by NAT44.
I'd be mildly disturbed if the IETF SSID offered Net 10, but I'm sure
it would work nicely. If the back end was CLAT, how would I even know?

   Brian


From nobody Wed Aug  2 22:45:35 2017
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D49A51321EC for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 22:45:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.4
X-Spam-Level: 
X-Spam-Status: No, score=-5.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IZVnrYAGkuB9 for <ietf@ietfa.amsl.com>; Wed,  2 Aug 2017 22:45:33 -0700 (PDT)
Received: from relais-inet.orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14A28126B6D for <ietf@ietf.org>; Wed,  2 Aug 2017 22:45:33 -0700 (PDT)
Received: from opfedar05.francetelecom.fr (unknown [xx.xx.xx.7]) by opfedar26.francetelecom.fr (ESMTP service) with ESMTP id 89BED1C077E; Thu,  3 Aug 2017 07:45:31 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.63]) by opfedar05.francetelecom.fr (ESMTP service) with ESMTP id 6FB0C60077; Thu,  3 Aug 2017 07:45:31 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM6E.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0352.000; Thu, 3 Aug 2017 07:45:31 +0200
From: <mohamed.boucadair@orange.com>
To: Christian Huitema <huitema@huitema.net>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Incremental Deployment of CLAT on the router for IETF Meetings
Thread-Topic: Incremental Deployment of CLAT on the router for IETF Meetings
Thread-Index: AQHTC6ClMPaW1MQI4U+Dv9zSBKLxRqJyGnHg
Date: Thu, 3 Aug 2017 05:45:30 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300A016592@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <CFC64369-8C1B-40AF-A414-EDBE75236D20@fugue.com> <m1dcpH8-0000FsC@stereo.hq.phicoh.net> <550D6EEF-DEF2-4F35-8D66-93AC4093325F@consulintel.es> <11cca0e7-08d5-f644-81a5-cf3e9d642606@huitema.net> <4C8B7472-F866-447B-A731-AD6EEC57648D@consulintel.es> <0ef07ade-29f3-0365-fdb6-6b0f814aed20@huitema.net> <04D8F0A9-18A0-418C-9AB3-9D01CBC06B90@consulintel.es> <f911167e-d6ad-d037-d10e-53c4a9c4adc8@huitema.net>
In-Reply-To: <f911167e-d6ad-d037-d10e-53c4a9c4adc8@huitema.net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/V9JsIvvYUrdrCckXk3CvGtrGepA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 03 Aug 2017 05:45:35 -0000

Q2hyaXN0aWFuLCANCg0KSSB3aWxsIGZvY3VzIG9uIHRoaXMgcGFydCBvZiB5b3VyIG1lc3NhZ2U6
DQoNCiJTbywgaWYgd2UgY291bGQgZGVtb25zdHJhdGUgdGhhdCBETlM2NCBpcyBub3QNCm5lZWRl
ZCBmb3IgdHJhbnNpdGlvbiwgdGhhdCB3b3VsZCBiZSBncmVhdC4iDQoNCkFjdHVhbGx5LCB3ZSBk
b24ndCBuZWVkIHRvIGRlbW9uc3RyYXRlIHRoYXQgZ2l2ZW4gdGhhdCBOQVQ2NCBzcGVjaWZpY2F0
aW9uIGRvZXMgbm90IG1ha2UgYW55IGFzc3VtcHRpb24gaG93IElQdjQtY29udmVydGVkIElQdjYg
YWRkcmVzc2VzIGFyZSBmb3JtZWQuIFdlIGhvcGVkIHRoaXMgd2FzIGNsYXJpZmllZCBpbiBSRkM2
ODg5LiANCg0KQnV0IGlmIHlvdSBuZWVkIGEgY29uY3JldGUgZXhhbXBsZSwgdGhlcmUgYXJlIGRl
cGxveW1lbnRzIGluIHdoaWNoIEROUzY0IGlzIG5vdCB1c2VkIHRvIHN5bnRoZXNpemUgYWRkcmVz
c2VzLiBZb3UgY2FuIHJlZmVyIHRvIHRoaXMgcHJlejoNCmh0dHBzOi8vd3d3LnlvdXR1YmUuY29t
L3dhdGNoP3Y9bzJfN0J5MkVnU1kgKDFtbjMwKQ0KDQpDaGVlcnMsDQpNZWQNCg0KPiAtLS0tLU1l
c3NhZ2UgZCdvcmlnaW5lLS0tLS0NCj4gRGXCoDogaWV0ZiBbbWFpbHRvOmlldGYtYm91bmNlc0Bp
ZXRmLm9yZ10gRGUgbGEgcGFydCBkZSBDaHJpc3RpYW4gSHVpdGVtYQ0KPiBFbnZvecOpwqA6IG1l
cmNyZWRpIDIgYW/Du3QgMjAxNyAxNzowNA0KPiDDgMKgOiBpZXRmQGlldGYub3JnDQo+IE9iamV0
wqA6IFJlOiBJbmNyZW1lbnRhbCBEZXBsb3ltZW50IG9mIENMQVQgb24gdGhlIHJvdXRlciBmb3Ig
SUVURiBNZWV0aW5ncw0KPiANCj4gDQo+IA0KPiBPbiA4LzIvMjAxNyA3OjUxIEFNLCBKT1JESSBQ
QUxFVCBNQVJUSU5FWiB3cm90ZToNCj4gPiBUaGVuIEkgZ3Vlc3Mgd2UgZnVsbHkgYWdyZWUsIGFu
ZCBJIGJlbGlldmUgSSB3YXMgdGhlIGZpcnN0IG9uZSByZW1pbmRpbmcNCj4gdGhhdCBvdXIgbmV0
d29yayBpcyBhIHByb2R1Y3Rpb24gb25lIOKApg0KPiA+DQo+ID4gQXMgd2UgYWxyZWFkeSBoYWQg
YSBOQVQ2NCBTU0lEIGZvciBzb21lIHRpbWUsIHRoZSByaWdodCBzdGVwIGZvciBJRVRGMTAwDQo+
IHdpbGwgYmUgdGhlbiB0byBoYXZlIGEgQ0xBVCBTU0lELCBzbyBpdCBjYW4gYmUgdGVzdGVkIGJ5
IHRob3NlIGZvbGtzIHRoYXQNCj4gd2FudCB0byB0ZXN0IGl0Lg0KPiA+DQo+ID4gSeKAmW0gaGFw
cHkgdG8gaGVscCB0aGUgTk9DIHRlYW0gdG8gZG8gdGhhdCBpZiB0aGV5IG5lZWQgaGVscC4NCj4g
Pg0KPiA+IFJlZ2FyZHMsDQo+ID4gSm9yZGkNCj4gDQo+IFRoYXQgd291bGQgYmUgZ29vZCwgZXNw
ZWNpYWxseSBpZiB0aGUgQ0xBVCBuZXR3b3JrIGRpZCBOT1QgaW5jbHVkZSBhbnkNCj4gRE5TNjQg
ZnVuY3Rpb24uIFRoZXJlIGlzIGEgZ3Jvd2luZyBzdXNwaWNpb24gdGhhdCBoYWNraW5nIHRoZSBE
TlMgaW4gdGhlDQo+IG5hbWUgb2YgSVB2NiB0cmFuc2l0aW9uIHdhcyBhIHJlYWxseSBiYWQgaWRl
YS4gd2UgaGF2ZSBoZWFyZCBpdCBtYW55DQo+IHRpbWVzIC0tIGJyZWFraW5nIEROU1NFQywgbm90
IHdvcmtpbmcgd2l0aCBWUE4sIG9yIE5ldGZsaXgsIG9yIFNreXBlLg0KPiBBbHNvLCB3ZSBrbm93
IHRoYXQgYSBsYXJnZSBmcmFjdGlvbiBvZiBETlMgcXVlcnkgYXJlIHNlcnZlZCBieSBHb29nbGUN
Cj4gRE5TIGFuZCBvdGhlciBnbG9iYWwgcHJvdmlkZXJzLCB3aGljaCBtZWFucyB0aGF0IHRoZSBE
TlM2NCBoYWNraW5nDQo+IHNlcnZlciB3aWxsIG5vdCBzZWUgdGhlbS4gU28sIGlmIHdlIGNvdWxk
IGRlbW9uc3RyYXRlIHRoYXQgRE5TNjQgaXMgbm90DQo+IG5lZWRlZCBmb3IgdHJhbnNpdGlvbiwg
dGhhdCB3b3VsZCBiZSBncmVhdC4NCj4gDQo+IC0tIENocmlzdGlhbiBIdWl0ZW1hDQo+IA0KPiAN
Cj4gLS0NCj4gQ2hyaXN0aWFuIEh1aXRlbWENCj4gDQoNCg==


From nobody Thu Aug  3 01:01:45 2017
Return-Path: <prvs=1388390a6d=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C63B8126CB6 for <ietf@ietfa.amsl.com>; Thu,  3 Aug 2017 01:01:43 -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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lNEPw8zTBwEg for <ietf@ietfa.amsl.com>; Thu,  3 Aug 2017 01:01:40 -0700 (PDT)
Received: from mail.consulintel.com (mail.consulintel.com [213.0.69.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8419124234 for <ietf@ietf.org>; Thu,  3 Aug 2017 01:01:35 -0700 (PDT)
X-MDAV-Processed: mail.consulintel.com, Thu, 03 Aug 2017 10:01:32 +0200
Received: from mail.consulintel.es by mail.consulintel.com (Cipher TLSv1:-SHA:128) (MDaemon PRO v11.0.3) with ESMTP id md50000900558.msg for <ietf@ietf.org>; Thu, 03 Aug 2017 10:01:31 +0200
X-Spam-Processed: mail.consulintel.com, Thu, 03 Aug 2017 10:01:31 +0200 (not processed: spam filter heuristic analysis disabled)
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Return-Path: prvs=1388390a6d=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1501747267; x=1502352067; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=9x8vzG4OVOqX5mz+WOWXYMKy+ wutyyaOpQT3TKpevC0=; b=ASl1ONLbDySPsuwqotQZJaa05VBjA5LvU/50bdlT7 MC8z5wv6Wis63rNSJYlRgQUfGfkHugMct/NXuptVvMU72SnYcoLRzR1/oPtKSzup zpD6dR2/W1ZGBgWuCPIv/WNX+0GhrntLJuf1TaSJPaBy3hXjvaISUWG68r3wxOBb Bo=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=WvYSZbQmoX/TBgpoSR7VsD5ebQ1J0CxvwfDcF+lfKu1m0DD/8AyqvzzFe1q3 QiDVGxRDC+fHCo7Pw6mSDBjWiBg56nxPvQBGI+oKigKYsZoUPGzaADnMD Asn3lvduRAZgLaU+C7L55p8Zeo8FmMQ2j5T4alyOG+IldybAOevRP8=;
X-MDAV-Processed: mail.consulintel.es, Thu, 03 Aug 2017 10:01:07 +0200
X-Spam-Processed: mail.consulintel.es, Thu, 03 Aug 2017 10:01:06 +0200
Received: from [10.10.10.133] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005493495.msg for <ietf@ietf.org>; Thu, 03 Aug 2017 10:01:05 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170803:md50005493495::YUqd1/YMSN+nPCQc:00006i7a
User-Agent: Microsoft-MacOutlook/f.24.1.170721
Date: Thu, 03 Aug 2017 10:01:04 +0200
Subject: Re: Incremental Deployment of CLAT on the router for IETF Meetings
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <1D12B31C-31D5-4818-97D5-265906DF41EB@consulintel.es>
Thread-Topic: Incremental Deployment of CLAT on the router for IETF Meetings
References: <CFC64369-8C1B-40AF-A414-EDBE75236D20@fugue.com> <m1dcpH8-0000FsC@stereo.hq.phicoh.net> <550D6EEF-DEF2-4F35-8D66-93AC4093325F@consulintel.es> <11cca0e7-08d5-f644-81a5-cf3e9d642606@huitema.net> <4C8B7472-F866-447B-A731-AD6EEC57648D@consulintel.es> <0ef07ade-29f3-0365-fdb6-6b0f814aed20@huitema.net> <04D8F0A9-18A0-418C-9AB3-9D01CBC06B90@consulintel.es> <f911167e-d6ad-d037-d10e-53c4a9c4adc8@huitema.net> <787AE7BB302AE849A7480A190F8B93300A016592@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93300A016592@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZhY4u_w9XbyuNoeCqRGtekl7Ack>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 03 Aug 2017 08:01:44 -0000

And I can confirm that yesterday I did some testing about this, with the sa=
me VMs that I=E2=80=99ve used in the IETF98, and as expected, it worked.

So yes for NAT64 you need DNS64, but if you have a CLAT in the CPE or in th=
e hosts, even if you don=E2=80=99t use DNS64, everything works fine, so DNS=
SEC is not broken.

The extra overhead of not doing DNS64, is that all the IPv4 traffic is tran=
slated twice (at the CLAT =E2=80=93 stateless NAT46 and at the statefull NA=
T64) vs translating only the IPv4 traffic that uses literals (when you use =
DNS64).

With NAT64 + DNS64 and 464XLAT (CLAT)
1) IPv6 app <-> IPv6 server (no translation)
2) IPv4/IPv6 app (DNS64) <-> IPv4 server (NAT64 translation) ----> breaks D=
NSSEC
3) IPv4 app (NAT46 - CLAT) <-> IPv4 server (NAT64 translation)

Without the DNS64
1) IPv6 app <-> IPv6 server (no translation)
2) IPv4/IPv6 app (NAT46 - CLAT) <-> IPv4 server (NAT64 translation)
3) IPv4 app (NAT46 - CLAT) <-> IPv4 server (NAT64 translation)

Already working in a new ID with operational recommendations about this, wh=
ich can be used in the IETF network as well.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de <mohamed.boucadair@orange.com=
>
Responder a: <mohamed.boucadair@orange.com>
Fecha: jueves, 3 de agosto de 2017, 7:45
Para: Christian Huitema <huitema@huitema.net>, "ietf@ietf.org" <ietf@ietf.o=
rg>
Asunto: RE: Incremental Deployment of CLAT on the router for IETF Meetings

    Christian,=20
   =20
    I will focus on this part of your message:
   =20
    "So, if we could demonstrate that DNS64 is not
    needed for transition, that would be great."
   =20
    Actually, we don't need to demonstrate that given that NAT64 specificat=
ion does not make any assumption how IPv4-converted IPv6 addresses are form=
ed. We hoped this was clarified in RFC6889.=20
   =20
    But if you need a concrete example, there are deployments in which DNS6=
4 is not used to synthesize addresses. You can refer to this prez:
    https://www.youtube.com/watch?v=3Do2_7By2EgSY (1mn30)
   =20
    Cheers,
    Med
   =20
    > -----Message d'origine-----
    > De : ietf [mailto:ietf-bounces@ietf.org] De la part de Christian Huit=
ema
    > Envoy=C3=A9 : mercredi 2 ao=C3=BBt 2017 17:04
    > =C3=80 : ietf@ietf.org
    > Objet : Re: Incremental Deployment of CLAT on the router for IETF Mee=
tings
    >=20
    >=20
    >=20
    > On 8/2/2017 7:51 AM, JORDI PALET MARTINEZ wrote:
    > > Then I guess we fully agree, and I believe I was the first one remi=
nding
    > that our network is a production one =E2=80=A6
    > >
    > > As we already had a NAT64 SSID for some time, the right step for IE=
TF100
    > will be then to have a CLAT SSID, so it can be tested by those folks =
that
    > want to test it.
    > >
    > > I=E2=80=99m happy to help the NOC team to do that if they need help=
.
    > >
    > > Regards,
    > > Jordi
    >=20
    > That would be good, especially if the CLAT network did NOT include an=
y
    > DNS64 function. There is a growing suspicion that hacking the DNS in =
the
    > name of IPv6 transition was a really bad idea. we have heard it many
    > times -- breaking DNSSEC, not working with VPN, or Netflix, or Skype.
    > Also, we know that a large fraction of DNS query are served by Google
    > DNS and other global providers, which means that the DNS64 hacking
    > server will not see them. So, if we could demonstrate that DNS64 is n=
ot
    > needed for transition, that would be great.
    >=20
    > -- Christian Huitema
    >=20
    >=20
    > --
    > Christian Huitema
    >=20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.





From nobody Thu Aug  3 06:37:55 2017
Return-Path: <dhruv.dhody@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65B44131FF3; Thu,  3 Aug 2017 06:37:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level: 
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BMBSO4loo7Nr; Thu,  3 Aug 2017 06:37:35 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C434131EB3; Thu,  3 Aug 2017 06:37:07 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DLW52594; Thu, 03 Aug 2017 13:34:05 +0000 (GMT)
Received: from BLREML703-CAH.china.huawei.com (10.20.4.172) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 3 Aug 2017 14:34:04 +0100
Received: from BLREML501-MBB.china.huawei.com ([10.20.5.200]) by blreml703-cah.china.huawei.com ([::1]) with mapi id 14.03.0301.000; Thu, 3 Aug 2017 19:03:54 +0530
From: Dhruv Dhody <dhruv.dhody@huawei.com>
To: "'Dale R. Worley'" <worley@ariadne.com>
CC: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-pce-pceps.all@ietf.org" <draft-ietf-pce-pceps.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "dhruv.ietf@gmail.com" <dhruv.ietf@gmail.com>
Subject: RE: [Pce] Genart last call review of draft-ietf-pce-pceps-14
Thread-Topic: [Pce] Genart last call review of draft-ietf-pce-pceps-14
Thread-Index: AQHTCzilzqPRSDFqSU+m/UcLVejzmaJyF/3A
Date: Thu, 3 Aug 2017 13:33:54 +0000
Message-ID: <23CE718903A838468A8B325B80962F9B8CB98624@blreml501-mbb>
References: <23CE718903A838468A8B325B80962F9B8CB962D9@blreml501-mbb> (dhruv.dhody@huawei.com) <87d18ed75n.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87d18ed75n.fsf@hobgoblin.ariadne.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.79.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.5983264E.0046, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: b42523666d453e6c31b5be5136449c93
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/v7p7k93Z3bBsH7kDK0cWMC71ZH4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 03 Aug 2017 13:37:36 -0000

Hi Dale,=20
=09
> -----Original Message-----
> From: Dale R. Worley [mailto:worley@ariadne.com]
> Sent: 02 August 2017 08:10
> To: Dhruv Dhody <dhruv.dhody@huawei.com>
> Cc: gen-art@ietf.org; draft-ietf-pce-pceps.all@ietf.org; pce@ietf.org;
> ietf@ietf.org; dhruv.ietf@gmail.com
> Subject: Re: [Pce] Genart last call review of draft-ietf-pce-pceps-14
>=20
> Dhruv Dhody <dhruv.dhody@huawei.com> writes:
> >> It's more complicated than that:  If a PCE does not like the first
> >> message it receives, if it implements PCEPS, it replies TBA2/2.  But
> >> if it does not implement PCEPS, it replies 1/1.  Similarly, a PCC may
> >> reject an initial message with either of these error codes, depending
> >> on the situation.  If the other endpoint does not implement PCEPS, it
> >> might be surprised by receiving TBA2/2, which it has no way of
> >> understanding in detail (although it will probably simply disconnect,
> >> which is what it would do in reaction to a 1/1).
> >>
> > [[Dhruv Dhody]] You are right about this case, which I have clarified
> > now -
> >
> >    If the PCEP speaker that only supports PCEPS connection (as a local
> >    policy), receives an Open message, it MUST treat it as an unexpected
> >    message and reply with a PCErr message with Error-Type set to 1 (PCE=
P
> >    session establishment failure) and Error-value set to 1 (reception o=
f
> >    an invalid Open message or a non Open message).
> >
> > In your description you mentioned the error TBA2/2, but the
> > description of TBA2/2 is  -
> >
> >    A PCEP
> >    speaker receiving any other message apart from StartTLS, Open, or
> >    PCErr as the first message, MUST treat it as an unexpected message
> >    and reply with a PCErr message with Error-Type set to [TBA2 by IANA]
> >    (PCEP StartTLS failure) and Error-value set to 2 (reception of any
> >    other message apart from StartTLS, Open, or PCErr message), and MUST
> >    close the TCP connection.
> >
> > So receiving of open message would not trigger this error. The new
> > text above would take care of that.
>=20
> I don't know if the case I'm thinking of is important enough to change
> anything for, but I think it should at least be thought about.
>=20
> I'm considering the situation where the TCP connection is started, and on=
e
> endpoint receives a message that it does not understand.  Not the case
> where a non-implementing endpoint receives a StartTLS, but where the
> message is entirely incorrect, and is neither Open nor StartTLS, or at
> least, is sufficiently malformed that the receiver cannot parse it as one
> of those message types.
>=20
> Of course, this situation should never happen, but I expect that it is
> occasionally seen, and it would be useful if it was handled in a way that
> would make it easier for the humans involved to diagnose the problem.
>=20
> If the receiver of the message does not implementing PCEPS, it will send
> error 1/1.  The receiver of the error (the sender of the message) will
> receive 1/1, and will "understand" it and log it as something requiring
> human intervention -- whether or not it implements PCEPS.
>=20
> OTOH, if the receiver of the message implements PCEPS, it will send error
> TBA2/2.  If the receiver of the error (the sender of the message)
> implements PCEPS, it will understand it and log it as something requiring
> human intervention.  However, if the receiver does not implement PCEPS, i=
t
> won't understand the error message, and will have to log it as "I receive=
d
> an unknown error message".  Of course, human inquiry will reveal that the
> error message was a PCEPS error message, and its meaning is "unknown
> initial message", getting us back to the previous situation.  But it seem=
s
> to me that this is adding a step of human processing where it could be
> avoided, and that better performance (of the humans and the system as a
> whole) would be achieved in practice if a PCEPS implementation, when it
> received an initial message that was not Open or StartTLS, sent a 1/1
> error in the same way as a non-PCEPS implementation.
>=20
> Dale
[[Dhruv Dhody]] I have added this in the backward compatibility session to =
note this concern -=20

   Note that, a PCEP implementation that support PCEPS would respond
   with PCErr message with Error-Type set to [TBA2 by IANA] (PCEP
   StartTLS failure) and Error-value set to 2 if any other message is
   sent before StartTLS or Open.  If the sender of the invalid message
   is a PCEP implementation that does not support PCEPS, it will not be
   able to understand this error.  A PCEPS implementation could also
   send the PCErr message as per [RFC5440] with Error-Type "PCEP session
   establishment failure" and Error-value "reception of an invalid Open
   message or a non Open message" before closing the session.

Regards,
Dhruv


From nobody Thu Aug  3 15:02:29 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F286D131C32; Thu,  3 Aug 2017 15:02:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
Cc: v6ops@ietf.org, draft-ietf-v6ops-unique-ipv6-prefix-per-host.all@ietf.org,  ietf@ietf.org
Subject: Genart telechat review of draft-ietf-v6ops-unique-ipv6-prefix-per-host-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150179774694.7100.15043779550485158536@ietfa.amsl.com>
Date: Thu, 03 Aug 2017 15:02:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yvvN6CW2plpIpWtE2huaxVu2Tm0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 03 Aug 2017 22:02:27 -0000

Reviewer: Joel Halpern
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-v6ops-unique-ipv6-prefix-per-host-07
Reviewer: Joel Halpern
Review Date: 2017-08-03
IETF LC End Date: 2017-06-06
IESG Telechat date: 2017-08-17

Summary: This document is ready for publication as a Best Common practice RFC<
although there are some issues to be considered.

Major issues:
    N/A

Minor issues:
    The issue of status for the document (BCP vs Informational) is for the IESG
    to conclude.  However, even if it is a BCP, as I understand the purpose,
    this document is intended to describe the practices to be used when a
    provider has decided to deploy a /64 per host.  The wording that is chosen
    throughout the document makes it appear that the underlying decision about
    such a deployment is also a recommended practice.

Nits/editorial comments:
    N/A


From nobody Thu Aug  3 21:53:29 2017
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6730120227 for <ietf@ietfa.amsl.com>; Thu,  3 Aug 2017 21:53:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q556EffMDi_L for <ietf@ietfa.amsl.com>; Thu,  3 Aug 2017 21:53:25 -0700 (PDT)
Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) (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 4C55C128AA1 for <ietf@ietf.org>; Thu,  3 Aug 2017 21:53:25 -0700 (PDT)
Received: from pps.filterd (m0098420.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v744moDn006266 for <ietf@ietf.org>; Fri, 4 Aug 2017 00:53:22 -0400
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by mx0b-001b2d01.pphosted.com with ESMTP id 2c4aeqjxst-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 04 Aug 2017 00:53:21 -0400
Received: from localhost by e32.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, 3 Aug 2017 22:53:21 -0600
Received: from b03cxnp07028.gho.boulder.ibm.com (9.17.130.15) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 3 Aug 2017 22:53:19 -0600
Received: from b03ledav001.gho.boulder.ibm.com (b03ledav001.gho.boulder.ibm.com [9.17.130.232]) by b03cxnp07028.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v744rJqo4784578 for <ietf@ietf.org>; Thu, 3 Aug 2017 21:53:19 -0700
Received: from b03ledav001.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id E18F56E035 for <ietf@ietf.org>; Thu,  3 Aug 2017 22:53:18 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b03ledav001.gho.boulder.ibm.com (Postfix) with ESMTPS id BC1136E0BC for <ietf@ietf.org>; Thu,  3 Aug 2017 22:53:18 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v744rHmC031327 for <ietf@ietf.org>; Fri, 4 Aug 2017 00:53:17 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v744rHrl031309 for ietf@ietf.org; Fri, 4 Aug 2017 00:53:17 -0400
From: narten@us.ibm.com
Date: Fri, 04 Aug 2017 00:53:17 -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-GCONF: 00
x-cbid: 17080404-0004-0000-0000-000012B2DB29
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00007481; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000216; SDB=6.00897281; UDB=6.00448950; IPR=6.00677464;  BA=6.00005509; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00016526; XFM=3.00000015; UTC=2017-08-04 04:53:20
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17080404-0005-0000-0000-00008089ECC7
Message-Id: <201708040453.v744rHrl031309@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-08-04_02:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=13 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1706020000 definitions=main-1708040073
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4mZbWPu7MNRVQjl4WoUg2bvtSRk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Aug 2017 04:53:28 -0000

Total of 162 messages in the last 7 days.
 
script run at: Fri Aug  4 00:53:12 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 17.90% |   29 | 15.87% |   348089 | mellon@fugue.com
  1.85% |    3 | 22.40% |   491448 | dhruv.dhody@huawei.com
  7.41% |   12 |  6.99% |   153274 | jordi.palet@consulintel.es
  7.41% |   12 |  3.93% |    86217 | randy@psg.com
  3.09% |    5 |  2.18% |    47760 | tjc@ecs.soton.ac.uk
  2.47% |    4 |  2.77% |    60756 | fenner@fenron.com
  3.09% |    5 |  2.10% |    46163 | huitema@huitema.net
  3.09% |    5 |  2.08% |    45559 | brian.e.carpenter@gmail.com
  2.47% |    4 |  2.39% |    52419 | marka@isc.org
  3.09% |    5 |  1.73% |    38007 | mcr+ietf@sandelman.ca
  2.47% |    4 |  2.30% |    50388 | mohamed.boucadair@orange.com
  3.09% |    5 |  1.67% |    36564 | paul.hoffman@vpnc.org
  2.47% |    4 |  2.12% |    46412 | stephen.farrell@cs.tcd.ie
  1.23% |    2 |  3.00% |    65781 | tony@att.com
  1.85% |    3 |  2.31% |    50687 | akatlas@gmail.com
  1.85% |    3 |  2.03% |    44545 | ekr@rtfm.com
  1.85% |    3 |  0.97% |    21298 | cabo@tzi.org
  1.85% |    3 |  0.83% |    18110 | johnl@taugh.com
  1.23% |    2 |  1.29% |    28225 | leifj@mnt.se
  1.23% |    2 |  1.15% |    25280 | worley@ariadne.com
  1.23% |    2 |  0.79% |    17318 | adam@nostrum.com
  1.23% |    2 |  0.75% |    16420 | swmike@swm.pp.se
  1.23% |    2 |  0.74% |    16183 | stewart.bryant@gmail.com
  1.23% |    2 |  0.63% |    13782 | heas@shrubbery.net
  1.23% |    2 |  0.59% |    12944 | pch-ietf-6@u-1.phicoh.com
  0.62% |    1 |  1.20% |    26229 | denisbider.ietf@gmail.com
  0.62% |    1 |  0.94% |    20607 | linuxwolf+ietf@outer-planes.net
  0.62% |    1 |  0.69% |    15129 | jefftant.ietf@gmail.com
  0.62% |    1 |  0.67% |    14795 | eric.gray@ericsson.com
  0.62% |    1 |  0.66% |    14550 | rlb@ipv.sx
  0.62% |    1 |  0.58% |    12663 | ynir.ietf@gmail.com
  0.62% |    1 |  0.54% |    11780 | narten@us.ibm.com
  0.62% |    1 |  0.53% |    11558 | john_leddy@comcast.com
  0.62% |    1 |  0.52% |    11431 | lhotka@nic.cz
  0.62% |    1 |  0.45% |     9881 | jmvalin@jmvalin.ca
  0.62% |    1 |  0.45% |     9879 | joelja@bogus.com
  0.62% |    1 |  0.45% |     9825 | warren@kumari.net
  0.62% |    1 |  0.44% |     9718 | j.schoenwaelder@jacobs-university.de
  0.62% |    1 |  0.43% |     9344 | tjw.ietf@gmail.com
  0.62% |    1 |  0.42% |     9319 | spencerdawkins.ietf@gmail.com
  0.62% |    1 |  0.42% |     9166 | agmalis@gmail.com
  0.62% |    1 |  0.40% |     8858 | olejacobsen@me.com
  0.62% |    1 |  0.40% |     8847 | lee@asgard.org
  0.62% |    1 |  0.40% |     8836 | ajs@anvilwalrusden.com
  0.62% |    1 |  0.40% |     8759 | mnot@mnot.net
  0.62% |    1 |  0.40% |     8741 | suzworldwide@gmail.com
  0.62% |    1 |  0.36% |     7823 | logan@hackers.mu
  0.62% |    1 |  0.35% |     7768 | michael.breuer@ilsf.de
  0.62% |    1 |  0.34% |     7565 | shares@ndzh.com
  0.62% |    1 |  0.34% |     7480 | rsk@gsp.org
  0.62% |    1 |  0.34% |     7478 | paf@frobbit.se
  0.62% |    1 |  0.34% |     7445 | vaibhavsinghacads@gmail.com
  0.62% |    1 |  0.32% |     7100 | jared@puck.nether.net
  0.62% |    1 |  0.32% |     6996 | tim.chown@jisc.ac.uk
  0.62% |    1 |  0.31% |     6899 | nick@foobar.org
  0.62% |    1 |  0.31% |     6814 | aallen@blackberry.com
  0.62% |    1 |  0.31% |     6792 | paul@nohats.ca
  0.62% |    1 |  0.29% |     6328 | dorian@blackrose.org
  0.62% |    1 |  0.29% |     6279 | rjsparks@nostrum.com
  0.62% |    1 |  0.27% |     6026 | jonathan.hardwick@metaswitch.com
  0.62% |    1 |  0.27% |     5995 | jmh@joelhalpern.com
  0.62% |    1 |  0.25% |     5404 | oritl@microsoft.com
--------+------+--------+----------+------------------------
100.00% |  162 |100.00% |  2193736 | Total


From nobody Fri Aug  4 08:57:40 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C4411321B9 for <ietf@ietfa.amsl.com>; Fri,  4 Aug 2017 08:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FXMKJsDxq_H1 for <ietf@ietfa.amsl.com>; Fri,  4 Aug 2017 08:57:36 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16ADD132182 for <ietf@ietf.org>; Fri,  4 Aug 2017 08:57:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 55156300579 for <ietf@ietf.org>; Fri,  4 Aug 2017 11:57:35 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id c9Q2FY-3JlHz for <ietf@ietf.org>; Fri,  4 Aug 2017 11:57:33 -0400 (EDT)
Received: from [192.168.1.13] (75-139-107-240.dhcp.mant.nc.charter.com [75.139.107.240]) by mail.smeinc.net (Postfix) with ESMTPSA id 7D766300429; Fri,  4 Aug 2017 11:57:33 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Revamp of the www.ietf.org website - next steps
Message-Id: <9D0E96C9-EC66-4BEF-9726-5956A0787864@vigilsec.com>
Date: Fri, 4 Aug 2017 11:57:32 -0400
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZCmTQeBwgfbvFtFr-mEh7ZMM39c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Aug 2017 15:57:38 -0000

Many thanks to everyone who took time to review  the beta.ietf.org =
website and provide comments. Based on feedback received, there seem to =
be a few items requiring attention before moving the revamped =
public-facing website to production:

A. Provide a landing page dedicated to current IETF participants

That page will include links to:
 - items on the left-side at www.ietf.org (or a subset thereof)
 - information about the next IETF meeting=20
 - links to functions at datatracker.ietf.org=20

Ideally this would also be:
 - viewable in a single screen on a desktop/laptop display
 -  reachable via a short, memorable URL without images

A draft is currently posted at https://beta.ietf.org/links/

This page can be updated further based on input from the community. =
There were also some suggestions received that revisions to =
datatracker.ietf.org might meet this need. While that is out of scope =
for this project, suggestions have been noted by the tools team.  If you =
frequently use something that is missing, please let us know.

B. Ensure WCAG 2.0 compliance

This is a requirement of the SOW =
(https://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf) =
and we are working with the website developer to ensure it is =
implemented. The baseline goal is to improve upon the status of the =
current www.ietf.org site. Furthermore, improving accessibility will =
continue to be an area of focus for the revamped website.

C. Conduct review with other key audiences, especially potential =
participants and non-participants

Based on the project SOW and the results of initial research =
(https://iaoc.ietf.org/documents/Torchbox_ETFUserresearch.pdf), =
additional interviews with members of the key audiences will be =
conducted to gather input. The results of those interviews will be =
incorporated into the project via issues noted at: =
https://github.com/ietf/www.ietf.org/issues =20

D. Improve data use and load times

Load time and data usage was noted as being higher than the current =
www.ietf.org site. The expectation is that load times will improve as =
the beta site moves to production and is deployed on the CDN used by =
www.ietf.org. In addition, content elements such as images will be =
adjusted to improve performance. In particular, some of the potential =
participants and non-participants reviewers will be in locations with =
less robust connectivity and their input on this aspect of the revamped =
site will be sought out. This is an aspect called out in the SOW and =
will have ongoing attention.

Over the next few weeks, the project team will be working through these =
and some other issues, such as filling out content and moving to the the =
most current version of the open source Wagtail Content Management =
System. There will be ongoing efforts to improve the revamped site, so =
your ongoing input is encouraged. Feedback can be sent to =
webmaster@ietf.org or issues can be raised at:

   https://github.com/ietf/www.ietf.org/issues

Thanks again to all those who have provided input. I expect to be in =
touch again as we move the revamped site to production.

Sincerely,
 Russ Housley
 IETF Website Revamp Project Manager



From nobody Fri Aug  4 09:35:56 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E658131E96 for <ietf@ietfa.amsl.com>; Fri,  4 Aug 2017 09:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8XCdOgFbepOB for <ietf@ietfa.amsl.com>; Fri,  4 Aug 2017 09:35:48 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51C6D1323FD for <ietf@ietf.org>; Fri,  4 Aug 2017 09:35:47 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v74GYwbQ007888; Fri, 4 Aug 2017 17:35:03 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v74GYwbQ007888
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1501864509; bh=+b4uM5MdgKUtQJgmkKgCOEnc1V8=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=1cw0cUitsZCAp2ARMkPxhcwZlKNv0LIrdPi9g9gvV0Rp24t0Op2lDRObyRegjsKYG F/tIJxF3H3A8OwhT4OZKhsUAKXfebXkyGX+aAHqjiqku1FngC9tSDNmety08sOkhc7 evcZM5z67iIgSDVFUFYUvjw2V0Yue/DxwAerUHcw=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y73HYr3144707780d6 ret-id none; Fri, 04 Aug 2017 17:35:08 +0100
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:2c19:c7da:71cb:5b8a] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v74GYjID030439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Aug 2017 17:34:46 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Revamp of the www.ietf.org website - next steps
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <9D0E96C9-EC66-4BEF-9726-5956A0787864@vigilsec.com>
Date: Fri, 4 Aug 2017 17:34:45 +0100
Cc: IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|d354b080c6285622a28f63748729b7a5y73HYr03tjc|ecs.soton.ac.uk|0F2B4B79-1D2B-4193-A086-6AAA2314E687@ecs.soton.ac.uk>
References: <9D0E96C9-EC66-4BEF-9726-5956A0787864@vigilsec.com> <0F2B4B79-1D2B-4193-A086-6AAA2314E687@ecs.soton.ac.uk>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-ECS-MailScanner-SpamScore: ss
X-smtpf-Report: sid=y73HYr314470778000; tid=y73HYr3144707780d6; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v74GYwbQ007888
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/A0a7pzeIHTS8Q6nErXOhVTYh9o0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Aug 2017 16:35:54 -0000

Hi,

> On 4 Aug 2017, at 16:57, Russ Housley <housley@vigilsec.com> wrote:
>=20
>=20
> Many thanks to everyone who took time to review  the beta.ietf.org =
website and provide comments. Based on feedback received, there seem to =
be a few items requiring attention before moving the revamped =
public-facing website to production:
>=20
> A. Provide a landing page dedicated to current IETF participants
>=20
> That page will include links to:
> - items on the left-side at www.ietf.org (or a subset thereof)
> - information about the next IETF meeting=20
> - links to functions at datatracker.ietf.org=20
>=20
> Ideally this would also be:
> - viewable in a single screen on a desktop/laptop display
> -  reachable via a short, memorable URL without images
>=20
> A draft is currently posted at https://beta.ietf.org/links/

Having a direct and short URL to the =E2=80=98participants=E2=80=99 =
page=E2=80=99 will be welcome.

But as it stands, the beta links page is difficult to parse. It would be =
easier to parse were it laid out more like this style - =
https://www.ietf.org/wg/chairs-page.html.

> This page can be updated further based on input from the community. =
There were also some suggestions received that revisions to =
datatracker.ietf.org might meet this need. While that is out of scope =
for this project, suggestions have been noted by the tools team.  If you =
frequently use something that is missing, please let us know.

The main site and the datatracker site take different perspective on =
certain (important) areas, such as past and next meeting info. Both are =
useful.  Witness https://www.ietf.org/meeting/100/index.html and =
https://datatracker.ietf.org/meeting/upcoming.

I=E2=80=99m expecting with the revamp that I would rarely visit =
www.ietf.org, rather I would visit the new =E2=80=98links=E2=80=99 URL =
and the datatracker, where now I visit www.ietf.org and the datatracker. =
 I would point people interested in finding out more about the IETF to =
www.ietf.org.

I=E2=80=99m very happy with the datatracker site.  New features like =
support for managing and submitting draft reviews are really nice.

> B. Ensure WCAG 2.0 compliance
>=20
> This is a requirement of the SOW =
(https://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf) =
and we are working with the website developer to ensure it is =
implemented. The baseline goal is to improve upon the status of the =
current www.ietf.org site. Furthermore, improving accessibility will =
continue to be an area of focus for the revamped website.

As someone with contrast issues, I don=E2=80=99t think =
https://beta.ietf.org/links/ would be compliant; it=E2=80=99s light blue =
on light grey.  There=E2=80=99s no need for the text to be that light, =
or there to be a background =E2=80=98colour=E2=80=99.

Thanks,
Tim

> C. Conduct review with other key audiences, especially potential =
participants and non-participants
>=20
> Based on the project SOW and the results of initial research =
(https://iaoc.ietf.org/documents/Torchbox_ETFUserresearch.pdf), =
additional interviews with members of the key audiences will be =
conducted to gather input. The results of those interviews will be =
incorporated into the project via issues noted at: =
https://github.com/ietf/www.ietf.org/issues =20
>=20
> D. Improve data use and load times
>=20
> Load time and data usage was noted as being higher than the current =
www.ietf.org site. The expectation is that load times will improve as =
the beta site moves to production and is deployed on the CDN used by =
www.ietf.org. In addition, content elements such as images will be =
adjusted to improve performance. In particular, some of the potential =
participants and non-participants reviewers will be in locations with =
less robust connectivity and their input on this aspect of the revamped =
site will be sought out. This is an aspect called out in the SOW and =
will have ongoing attention.
>=20
> Over the next few weeks, the project team will be working through =
these and some other issues, such as filling out content and moving to =
the the most current version of the open source Wagtail Content =
Management System. There will be ongoing efforts to improve the revamped =
site, so your ongoing input is encouraged. Feedback can be sent to =
webmaster@ietf.org or issues can be raised at:
>=20
>   https://github.com/ietf/www.ietf.org/issues
>=20
> Thanks again to all those who have provided input. I expect to be in =
touch again as we move the revamped site to production.
>=20
> Sincerely,
> Russ Housley
> IETF Website Revamp Project Manager
>=20
>=20


From nobody Fri Aug  4 13:48:49 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8452B126B6D for <ietf@ietfa.amsl.com>; Fri,  4 Aug 2017 13:48:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wcN8-z4e1-3u for <ietf@ietfa.amsl.com>; Fri,  4 Aug 2017 13:48:45 -0700 (PDT)
Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A42DA124B18 for <ietf@ietf.org>; Fri,  4 Aug 2017 13:48:45 -0700 (PDT)
Received: by mail-pg0-x229.google.com with SMTP id y129so12100431pgy.4 for <ietf@ietf.org>; Fri, 04 Aug 2017 13:48:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:cc:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=cO4NgUtRSifSRoxI35LxXptuy7X5KQOFs/1USnMgyH0=; b=jnRtrJG5EStw+ac8NjhkfEfUyqAcL0YYBOsE5QlS9PUQpCO8biP0Itib60g8gb6g1+ JEEcoz0hAET3LVsDgqlSlmvsFzfhH55S/PEiTXUbIk7ihTYpYHTtAA5TWSYrnkCDDMIJ p9ReWV80QptCiD8MIUs/iEFnZ6vaO6HheAVEdCCXUCCjHsoX3w5C4yBNK0Lb9+p+tTlY FCX/xaKl3N9X+P+NZVUCSMPuESaeWak7DLvpWt71hBxSYnUNmil6IP53NgPVY+NaGWlR SJH7dMxJDLM6QQqTUsGeyapiD1+rewmklZAYGYc/oBn5qFqrbQvu3IzBjyl9zbiUootZ TCPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization:cc :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=cO4NgUtRSifSRoxI35LxXptuy7X5KQOFs/1USnMgyH0=; b=OwzVs0C1Tgf0wjTAZT4YZqs3HIWceZHZ/LoVqyiGLdq9rxnFfBdkV3JXeN2tl8VF+b 3JE2rG9sSg455Zsr7B5NDQRHrphL0IKq50b8FWy2fT0SLiX3D4VsNVKKZjgMpVil/jnt iX9NyhNFeJDYZyLXqHiPBD9zarb4+9zCZVPm+u7e4fLD3W2CXQREWZYJvH7+seJ1TEJx G6YKT3N84E84+/jJdNgcMPOrCHQUTIn53yTkuTfGfVgGbjy06cgDOkrUjTWBqIhA3v8t v+HgQjnoi8M+IoURpBrrhqIW0E7EF41SvuwSQPcXy3TmikPk/we6W8dL7Gc6Qihwq72J hOWw==
X-Gm-Message-State: AIVw112dpUDR3On1BffueIozfnxL28yfw1FZ228hohxEqCWkIMorh6+R kPiUU9ImwTgnbUr+
X-Received: by 10.99.120.9 with SMTP id t9mr3602527pgc.263.1501879725030; Fri, 04 Aug 2017 13:48:45 -0700 (PDT)
Received: from ?IPv6:2406:e007:521f:1:28cc:dc4c:9703:6781? ([2406:e007:521f:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id m65sm4350418pfi.94.2017.08.04.13.48.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 04 Aug 2017 13:48:44 -0700 (PDT)
Subject: Re: Revamp of the www.ietf.org website - next steps
To: Russ Housley <housley@vigilsec.com>
References: <9D0E96C9-EC66-4BEF-9726-5956A0787864@vigilsec.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Cc: IETF <ietf@ietf.org>
Message-ID: <65ae800a-13d9-f8db-ed9b-0622c02a64bd@gmail.com>
Date: Sat, 5 Aug 2017 08:48:51 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <9D0E96C9-EC66-4BEF-9726-5956A0787864@vigilsec.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-jYMhnCHY4Oj4Wm3Zd1dVfSOYo8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Aug 2017 20:48:47 -0000

Russ,
On 05/08/2017 03:57, Russ Housley wrote:
... 
> A draft is currently posted at https://beta.ietf.org/links/

Thanks for this. A few comments:

1. I agree with Tim that the visual style isn't ideal. There isn't really enough
contrast. I hope the current fashion for pale print over a pale background will
soon go away. (This applies to the whole beta site, of course. Needs to be legible
in direct sunlight :-)

2. A few bits of content that I use fairly often are missing:

Under Internet-Drafts: Guidelines | Checklist
Contact the IETF (important things like ietf-action@ietf.org)

3. There's a bar at the bottom with "RFC Editor IANA IAB" etc.
That's fine except it's so far down that I completely missed it
and was most of the way through typing a complaint that it wasn't there
until I happened to find it.

4. The links on that bar to "Secretariat" and "ISOC" seem to be advertising.
I think they need to go first to little "About" pages that explain the
roles of AMS and ISOC w.r.t. the IETF, then the links to AMS and ISOC.

Regards
     Brian


From nobody Fri Aug  4 14:00:28 2017
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 890E61241FC for <ietf@ietfa.amsl.com>; Fri,  4 Aug 2017 14:00:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level: 
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FPiV2F3TPaM6 for <ietf@ietfa.amsl.com>; Fri,  4 Aug 2017 14:00:23 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2141912009C for <ietf@ietf.org>; Fri,  4 Aug 2017 14:00:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 4D4C549DB172; Fri,  4 Aug 2017 17:00:22 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dSVr-K2wPDcx; Fri,  4 Aug 2017 17:00:20 -0400 (EDT)
Received: from [10.0.1.16] (173-166-5-69-newengland.hfc.comcastbusiness.net [173.166.5.69]) by sobco.sobco.com (Postfix) with ESMTPSA id 8239249DB165; Fri,  4 Aug 2017 17:00:20 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Revamp of the www.ietf.org website - next steps
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <9D0E96C9-EC66-4BEF-9726-5956A0787864@vigilsec.com>
Date: Fri, 4 Aug 2017 17:00:20 -0400
Cc: IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DBF68DC2-A743-4DC6-A095-3CCBA3525913@sobco.com>
References: <9D0E96C9-EC66-4BEF-9726-5956A0787864@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RFR7Qz1uwZh-95Qjjn6mjZzYXLo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Aug 2017 21:00:26 -0000

I trust that as many of the existing URLs as possible will continue to =
work
(e.g., https://datatracker.ietf.org/ipr/search/)

on the links page - it would be good to include the contact section

Scott

> On Aug 4, 2017, at 11:57 AM, Russ Housley <housley@vigilsec.com> =
wrote:
>=20
>=20
> Many thanks to everyone who took time to review  the beta.ietf.org =
website and provide comments. Based on feedback received, there seem to =
be a few items requiring attention before moving the revamped =
public-facing website to production:
>=20
> A. Provide a landing page dedicated to current IETF participants
>=20
> That page will include links to:
> - items on the left-side at www.ietf.org (or a subset thereof)
> - information about the next IETF meeting=20
> - links to functions at datatracker.ietf.org=20
>=20
> Ideally this would also be:
> - viewable in a single screen on a desktop/laptop display
> -  reachable via a short, memorable URL without images
>=20
> A draft is currently posted at https://beta.ietf.org/links/
>=20
> This page can be updated further based on input from the community. =
There were also some suggestions received that revisions to =
datatracker.ietf.org might meet this need. While that is out of scope =
for this project, suggestions have been noted by the tools team.  If you =
frequently use something that is missing, please let us know.
>=20
> B. Ensure WCAG 2.0 compliance
>=20
> This is a requirement of the SOW =
(https://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf) =
and we are working with the website developer to ensure it is =
implemented. The baseline goal is to improve upon the status of the =
current www.ietf.org site. Furthermore, improving accessibility will =
continue to be an area of focus for the revamped website.
>=20
> C. Conduct review with other key audiences, especially potential =
participants and non-participants
>=20
> Based on the project SOW and the results of initial research =
(https://iaoc.ietf.org/documents/Torchbox_ETFUserresearch.pdf), =
additional interviews with members of the key audiences will be =
conducted to gather input. The results of those interviews will be =
incorporated into the project via issues noted at: =
https://github.com/ietf/www.ietf.org/issues =20
>=20
> D. Improve data use and load times
>=20
> Load time and data usage was noted as being higher than the current =
www.ietf.org site. The expectation is that load times will improve as =
the beta site moves to production and is deployed on the CDN used by =
www.ietf.org. In addition, content elements such as images will be =
adjusted to improve performance. In particular, some of the potential =
participants and non-participants reviewers will be in locations with =
less robust connectivity and their input on this aspect of the revamped =
site will be sought out. This is an aspect called out in the SOW and =
will have ongoing attention.
>=20
> Over the next few weeks, the project team will be working through =
these and some other issues, such as filling out content and moving to =
the the most current version of the open source Wagtail Content =
Management System. There will be ongoing efforts to improve the revamped =
site, so your ongoing input is encouraged. Feedback can be sent to =
webmaster@ietf.org or issues can be raised at:
>=20
>   https://github.com/ietf/www.ietf.org/issues
>=20
> Thanks again to all those who have provided input. I expect to be in =
touch again as we move the revamped site to production.
>=20
> Sincerely,
> Russ Housley
> IETF Website Revamp Project Manager
>=20
>=20


From nobody Fri Aug  4 14:27:53 2017
Return-Path: <pat.thaler@broadcom.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35422127201 for <ietf@ietfa.amsl.com>; Fri,  4 Aug 2017 14:27:52 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=broadcom.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id euACRPPJiu_k for <ietf@ietfa.amsl.com>; Fri,  4 Aug 2017 14:27:49 -0700 (PDT)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BE5F1241F5 for <ietf@ietf.org>; Fri,  4 Aug 2017 14:27:48 -0700 (PDT)
Received: by mail-qt0-x22d.google.com with SMTP id s6so16202934qtc.1 for <ietf@ietf.org>; Fri, 04 Aug 2017 14:27:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4PLycjV+r+yL/04ZzazUWowctpeOsRAxFMBFPOqD9WM=; b=gm54RFYlFWkJ3KR/r6oxRecTGhhpiOn9a9R92Q3D5QuSjEDLYk/FX5ZN7nB+ZKuZyx +SFhchRlhN4xTpPdGIdWFkAr5yb6LAdI6bZ37bddt/+EUPLB7efYjPSzIQhQ8YVBbtG7 mF5JLRnMPH+ZPzkXThYpXti3wwtHqGwi7Ai4Y=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=4PLycjV+r+yL/04ZzazUWowctpeOsRAxFMBFPOqD9WM=; b=lZ1nLnC0tq9oBl2mskjrmW4QtoC+C+bE010QxLNjK4mE/5kl0ff6m4ZkfIbU3LuK3q ZWeqGy521/DFbvY8rmJ7Xf1H9zc9ULrAcw/FOzjJ1uQawhzZHEtTlA1bjL4fUoTH8DvQ okIPVfYbHKqDFf8ptetg+x02Po6Ll1lHm4kqisza+o6DukrF55rd+Gqez3TmTYprB6ds dO2gfhvgtDM4AS1hd+CohCQuzNkFRIdnOjQHpo78FCO7LyN03Lo8G1fWytlOjuV+DolI Mv+LfjbtOZ5h4jNxUrrvAsY5DTRA82n7n04fES+QGjhH4XHzBP7coFXhjAnJjNzXPdaO +AaQ==
X-Gm-Message-State: AHYfb5g4Hb6cUBjhY/cPUaXu/dPJVWrKyEW3wk5fG+6QOD1JB9e2L7eV MbniARjjFRl4jBxphogesz/kk03v2Q2A
X-Received: by 10.200.39.115 with SMTP id h48mr5292551qth.294.1501882068085; Fri, 04 Aug 2017 14:27:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.29.161 with HTTP; Fri, 4 Aug 2017 14:27:47 -0700 (PDT)
In-Reply-To: <EMEW3|d354b080c6285622a28f63748729b7a5y73HYr03tjc|ecs.soton.ac.uk|0F2B4B79-1D2B-4193-A086-6AAA2314E687@ecs.soton.ac.uk>
References: <0F2B4B79-1D2B-4193-A086-6AAA2314E687@ecs.soton.ac.uk> <9D0E96C9-EC66-4BEF-9726-5956A0787864@vigilsec.com> <EMEW3|d354b080c6285622a28f63748729b7a5y73HYr03tjc|ecs.soton.ac.uk|0F2B4B79-1D2B-4193-A086-6AAA2314E687@ecs.soton.ac.uk>
From: Pat Thaler <pat.thaler@broadcom.com>
Date: Fri, 4 Aug 2017 14:27:47 -0700
Message-ID: <CAJt_5EgTPi0Ts8xDQU2Kw4XWAFNAr7wkjxO2ShBgS0ZaskKmHw@mail.gmail.com>
Subject: Re: Revamp of the www.ietf.org website - next steps
To: Tim Chown <tjc@ecs.soton.ac.uk>
Cc: Russ Housley <housley@vigilsec.com>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a1141ff0629d1ff0555f42b5e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BS4_mvvjrPBzuitiWfZp1GsRu3E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Aug 2017 21:27:52 -0000

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

I also prefer the style on: https://www.ietf.org/wg/chairs-page.html. for a
links page

The low contrast tone-on-tone is hard to read and the two column
arrangement with just one to three links per column line makes it easier to
select the link.

On Fri, Aug 4, 2017 at 9:34 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:

> Hi,
>
> > On 4 Aug 2017, at 16:57, Russ Housley <housley@vigilsec.com> wrote:
> >
> >
> > Many thanks to everyone who took time to review  the beta.ietf.org
> website and provide comments. Based on feedback received, there seem to b=
e
> a few items requiring attention before moving the revamped public-facing
> website to production:
> >
> > A. Provide a landing page dedicated to current IETF participants
> >
> > That page will include links to:
> > - items on the left-side at www.ietf.org (or a subset thereof)
> > - information about the next IETF meeting
> > - links to functions at datatracker.ietf.org
> >
> > Ideally this would also be:
> > - viewable in a single screen on a desktop/laptop display
> > -  reachable via a short, memorable URL without images
> >
> > A draft is currently posted at https://beta.ietf.org/links/
>
> Having a direct and short URL to the =E2=80=98participants=E2=80=99 page=
=E2=80=99 will be welcome.
>
> But as it stands, the beta links page is difficult to parse. It would be
> easier to parse were it laid out more like this style -
> https://www.ietf.org/wg/chairs-page.html.
>
> > This page can be updated further based on input from the community.
> There were also some suggestions received that revisions to
> datatracker.ietf.org might meet this need. While that is out of scope for
> this project, suggestions have been noted by the tools team.  If you
> frequently use something that is missing, please let us know.
>
> The main site and the datatracker site take different perspective on
> certain (important) areas, such as past and next meeting info. Both are
> useful.  Witness https://www.ietf.org/meeting/100/index.html and
> https://datatracker.ietf.org/meeting/upcoming.
>
> I=E2=80=99m expecting with the revamp that I would rarely visit www.ietf.=
org,
> rather I would visit the new =E2=80=98links=E2=80=99 URL and the datatrac=
ker, where now I
> visit www.ietf.org and the datatracker.  I would point people interested
> in finding out more about the IETF to www.ietf.org.
>
> I=E2=80=99m very happy with the datatracker site.  New features like supp=
ort for
> managing and submitting draft reviews are really nice.
>
> > B. Ensure WCAG 2.0 compliance
> >
> > This is a requirement of the SOW (https://iaoc.ietf.org/
> documents/IETF-Website-SOW-20140604-Final.pdf) and we are working with
> the website developer to ensure it is implemented. The baseline goal is t=
o
> improve upon the status of the current www.ietf.org site. Furthermore,
> improving accessibility will continue to be an area of focus for the
> revamped website.
>
> As someone with contrast issues, I don=E2=80=99t think
> https://beta.ietf.org/links/ would be compliant; it=E2=80=99s light blue =
on light
> grey.  There=E2=80=99s no need for the text to be that light, or there to=
 be a
> background =E2=80=98colour=E2=80=99.
>
> Thanks,
> Tim
>
> > C. Conduct review with other key audiences, especially potential
> participants and non-participants
> >
> > Based on the project SOW and the results of initial research (
> https://iaoc.ietf.org/documents/Torchbox_ETFUserresearch.pdf), additional
> interviews with members of the key audiences will be conducted to gather
> input. The results of those interviews will be incorporated into the
> project via issues noted at: https://github.com/ietf/www.ietf.org/issues
> >
> > D. Improve data use and load times
> >
> > Load time and data usage was noted as being higher than the current
> www.ietf.org site. The expectation is that load times will improve as the
> beta site moves to production and is deployed on the CDN used by
> www.ietf.org. In addition, content elements such as images will be
> adjusted to improve performance. In particular, some of the potential
> participants and non-participants reviewers will be in locations with les=
s
> robust connectivity and their input on this aspect of the revamped site
> will be sought out. This is an aspect called out in the SOW and will have
> ongoing attention.
> >
> > Over the next few weeks, the project team will be working through these
> and some other issues, such as filling out content and moving to the the
> most current version of the open source Wagtail Content Management System=
.
> There will be ongoing efforts to improve the revamped site, so your ongoi=
ng
> input is encouraged. Feedback can be sent to webmaster@ietf.org or issues
> can be raised at:
> >
> >   https://github.com/ietf/www.ietf.org/issues
> >
> > Thanks again to all those who have provided input. I expect to be in
> touch again as we move the revamped site to production.
> >
> > Sincerely,
> > Russ Housley
> > IETF Website Revamp Project Manager
> >
> >
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra">I also prefer the style on:=C2=
=A0<a href=3D"https://www.ietf.org/wg/chairs-page.html" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/wg/<wbr>chairs-page.html</a>. for a =
links page</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_ex=
tra">The low contrast tone-on-tone is hard to read and the two column arran=
gement with just one to three links per column line makes it easier to sele=
ct the link.</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"=
>On Fri, Aug 4, 2017 at 9:34 AM, Tim Chown <span dir=3D"ltr">&lt;<a href=3D=
"mailto:tjc@ecs.soton.ac.uk" target=3D"_blank">tjc@ecs.soton.ac.uk</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<span class=3D"gmail-"><br>
&gt; On 4 Aug 2017, at 16:57, Russ Housley &lt;<a href=3D"mailto:housley@vi=
gilsec.com">housley@vigilsec.com</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; Many thanks to everyone who took time to review=C2=A0 the <a href=3D"h=
ttp://beta.ietf.org" rel=3D"noreferrer" target=3D"_blank">beta.ietf.org</a>=
 website and provide comments. Based on feedback received, there seem to be=
 a few items requiring attention before moving the revamped public-facing w=
ebsite to production:<br>
&gt;<br>
&gt; A. Provide a landing page dedicated to current IETF participants<br>
&gt;<br>
&gt; That page will include links to:<br>
&gt; - items on the left-side at <a href=3D"http://www.ietf.org" rel=3D"nor=
eferrer" target=3D"_blank">www.ietf.org</a> (or a subset thereof)<br>
&gt; - information about the next IETF meeting<br>
&gt; - links to functions at <a href=3D"http://datatracker.ietf.org" rel=3D=
"noreferrer" target=3D"_blank">datatracker.ietf.org</a><br>
&gt;<br>
&gt; Ideally this would also be:<br>
&gt; - viewable in a single screen on a desktop/laptop display<br>
&gt; -=C2=A0 reachable via a short, memorable URL without images<br>
&gt;<br>
&gt; A draft is currently posted at <a href=3D"https://beta.ietf.org/links/=
" rel=3D"noreferrer" target=3D"_blank">https://beta.ietf.org/links/</a><br>
<br>
</span>Having a direct and short URL to the =E2=80=98participants=E2=80=99 =
page=E2=80=99 will be welcome.<br>
<br>
But as it stands, the beta links page is difficult to parse. It would be ea=
sier to parse were it laid out more like this style - <a href=3D"https://ww=
w.ietf.org/wg/chairs-page.html" rel=3D"noreferrer" target=3D"_blank">https:=
//www.ietf.org/wg/<wbr>chairs-page.html</a>.<br>
<span class=3D"gmail-"><br>
&gt; This page can be updated further based on input from the community. Th=
ere were also some suggestions received that revisions to <a href=3D"http:/=
/datatracker.ietf.org" rel=3D"noreferrer" target=3D"_blank">datatracker.iet=
f.org</a> might meet this need. While that is out of scope for this project=
, suggestions have been noted by the tools team.=C2=A0 If you frequently us=
e something that is missing, please let us know.<br>
<br>
</span>The main site and the datatracker site take different perspective on=
 certain (important) areas, such as past and next meeting info. Both are us=
eful.=C2=A0 Witness <a href=3D"https://www.ietf.org/meeting/100/index.html"=
 rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/meeting/<wbr>100=
/index.html</a> and <a href=3D"https://datatracker.ietf.org/meeting/upcomin=
g" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<wbr>m=
eeting/upcoming</a>.<br>
<br>
I=E2=80=99m expecting with the revamp that I would rarely visit <a href=3D"=
http://www.ietf.org" rel=3D"noreferrer" target=3D"_blank">www.ietf.org</a>,=
 rather I would visit the new =E2=80=98links=E2=80=99 URL and the datatrack=
er, where now I visit <a href=3D"http://www.ietf.org" rel=3D"noreferrer" ta=
rget=3D"_blank">www.ietf.org</a> and the datatracker.=C2=A0 I would point p=
eople interested in finding out more about the IETF to <a href=3D"http://ww=
w.ietf.org" rel=3D"noreferrer" target=3D"_blank">www.ietf.org</a>.<br>
<br>
I=E2=80=99m very happy with the datatracker site.=C2=A0 New features like s=
upport for managing and submitting draft reviews are really nice.<br>
<span class=3D"gmail-"><br>
&gt; B. Ensure WCAG 2.0 compliance<br>
&gt;<br>
&gt; This is a requirement of the SOW (<a href=3D"https://iaoc.ietf.org/doc=
uments/IETF-Website-SOW-20140604-Final.pdf" rel=3D"noreferrer" target=3D"_b=
lank">https://iaoc.ietf.org/<wbr>documents/IETF-Website-SOW-<wbr>20140604-F=
inal.pdf</a>) and we are working with the website developer to ensure it is=
 implemented. The baseline goal is to improve upon the status of the curren=
t <a href=3D"http://www.ietf.org" rel=3D"noreferrer" target=3D"_blank">www.=
ietf.org</a> site. Furthermore, improving accessibility will continue to be=
 an area of focus for the revamped website.<br>
<br>
</span>As someone with contrast issues, I don=E2=80=99t think <a href=3D"ht=
tps://beta.ietf.org/links/" rel=3D"noreferrer" target=3D"_blank">https://be=
ta.ietf.org/links/</a> would be compliant; it=E2=80=99s light blue on light=
 grey.=C2=A0 There=E2=80=99s no need for the text to be that light, or ther=
e to be a background =E2=80=98colour=E2=80=99.<br>
<br>
Thanks,<br>
Tim<br>
<div class=3D"gmail-HOEnZb"><div class=3D"gmail-h5"><br>
&gt; C. Conduct review with other key audiences, especially potential parti=
cipants and non-participants<br>
&gt;<br>
&gt; Based on the project SOW and the results of initial research (<a href=
=3D"https://iaoc.ietf.org/documents/Torchbox_ETFUserresearch.pdf" rel=3D"no=
referrer" target=3D"_blank">https://iaoc.ietf.org/<wbr>documents/Torchbox_<=
wbr>ETFUserresearch.pdf</a>), additional interviews with members of the key=
 audiences will be conducted to gather input. The results of those intervie=
ws will be incorporated into the project via issues noted at: <a href=3D"ht=
tps://github.com/ietf/www.ietf.org/issues" rel=3D"noreferrer" target=3D"_bl=
ank">https://github.com/ietf/www.<wbr>ietf.org/issues</a><br>
&gt;<br>
&gt; D. Improve data use and load times<br>
&gt;<br>
&gt; Load time and data usage was noted as being higher than the current <a=
 href=3D"http://www.ietf.org" rel=3D"noreferrer" target=3D"_blank">www.ietf=
.org</a> site. The expectation is that load times will improve as the beta =
site moves to production and is deployed on the CDN used by <a href=3D"http=
://www.ietf.org" rel=3D"noreferrer" target=3D"_blank">www.ietf.org</a>. In =
addition, content elements such as images will be adjusted to improve perfo=
rmance. In particular, some of the potential participants and non-participa=
nts reviewers will be in locations with less robust connectivity and their =
input on this aspect of the revamped site will be sought out. This is an as=
pect called out in the SOW and will have ongoing attention.<br>
&gt;<br>
&gt; Over the next few weeks, the project team will be working through thes=
e and some other issues, such as filling out content and moving to the the =
most current version of the open source Wagtail Content Management System. =
There will be ongoing efforts to improve the revamped site, so your ongoing=
 input is encouraged. Feedback can be sent to <a href=3D"mailto:webmaster@i=
etf.org">webmaster@ietf.org</a> or issues can be raised at:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0<a href=3D"https://github.com/ietf/www.ietf.org/issues" re=
l=3D"noreferrer" target=3D"_blank">https://github.com/ietf/www.<wbr>ietf.or=
g/issues</a><br>
&gt;<br>
&gt; Thanks again to all those who have provided input. I expect to be in t=
ouch again as we move the revamped site to production.<br>
&gt;<br>
&gt; Sincerely,<br>
&gt; Russ Housley<br>
&gt; IETF Website Revamp Project Manager<br>
&gt;<br>
&gt;<br>
<br>
</div></div></blockquote></div><br></div></div>

--001a1141ff0629d1ff0555f42b5e--


From nobody Sat Aug  5 03:57:53 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C932312ECB7 for <ietf@ietfa.amsl.com>; Sat,  5 Aug 2017 03:57:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BWynASxcvR_v for <ietf@ietfa.amsl.com>; Sat,  5 Aug 2017 03:57:47 -0700 (PDT)
Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BF32131CDF for <ietf@ietf.org>; Sat,  5 Aug 2017 03:57:16 -0700 (PDT)
Received: by mail-wr0-x232.google.com with SMTP id v105so24379446wrb.0 for <ietf@ietf.org>; Sat, 05 Aug 2017 03:57:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=GI6cstTlAVKICRTmQ9aMsaWPz0l/bw9Ajggt0uOZ8Zk=; b=SsKo4j8SnYIXXAroVz/1/AwBra/wCT8Yto90iPWvk5iGyQ2rev2JwyX8Ror8VBMjen Xpqku+1P31DxNNoYFlGHl3mFjUy8WUHM93eI47qq4nH/ZdJXjLVS//4rEgoko7f6t5FZ y6FerkVsClpiWsQ7LtcLdtKnHT9GteCwzeNW8XR9vVmEeY8CmMbB+4ZJ2XenBNxNOq49 7lEn6R6gejnuEsyoIqrH/XnAVpQ6A0rMj5uiWFtvx/WVGaqrMM81HYJOHp+atmuErtYg iMXfQrawfpGMbCA+ryQyf9CuExUp9khxxTsUTaGcSziMEfKLvlgNkXrAhADf08KTJsAB kHnA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=GI6cstTlAVKICRTmQ9aMsaWPz0l/bw9Ajggt0uOZ8Zk=; b=guNDZIh+ZC3X8GXaHzByGHQzk1lBjzZsJP8s9LgCSOr4UT8+eyvcnWWNE+SWGperBB 7frwUigSCdW8zrvHlTd+U6rYBFSkoU3WrdWfDwpFBlP5Xa3ZaYZfjlyOEy0cUaXxpjD+ mqJtUyLyhJbgtqtrsvBh9060IFnhDdNSROGJdJq/XpdbkLmrJdzYotRTedkdUnOogqLu MX7NCtwMFkulFxg4tdW0wHQMhjdr/4nrB4WeYrYg9g6lnPo/+KNjBhv4XVMhKrUqJdLE 1kqBeM0+9UL+2Ucyn1bsWoJZjUP6fQCBrIyPGZBHP5gWsyEpbakQ5aYueLHtWGXNI0Pv XQ5Q==
X-Gm-Message-State: AIVw111lmfNtLSIGPjbekf1NSt2CIYzh+vFBxzLTHTErGuG/s9mNzAm0 SMnF08AN2vkeWvccmTg=
X-Received: by 10.223.139.154 with SMTP id o26mr4197219wra.178.1501930634586;  Sat, 05 Aug 2017 03:57:14 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id v6sm6995147wmd.42.2017.08.05.03.57.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 05 Aug 2017 03:57:13 -0700 (PDT)
Subject: Re: Revamp of the www.ietf.org website - next steps
To: Pat Thaler <pat.thaler@broadcom.com>, Tim Chown <tjc@ecs.soton.ac.uk>
Cc: IETF <ietf@ietf.org>
References: <0F2B4B79-1D2B-4193-A086-6AAA2314E687@ecs.soton.ac.uk> <9D0E96C9-EC66-4BEF-9726-5956A0787864@vigilsec.com> <EMEW3|d354b080c6285622a28f63748729b7a5y73HYr03tjc|ecs.soton.ac.uk|0F2B4B79-1D2B-4193-A086-6AAA2314E687@ecs.soton.ac.uk> <CAJt_5EgTPi0Ts8xDQU2Kw4XWAFNAr7wkjxO2ShBgS0ZaskKmHw@mail.gmail.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <0f1315d6-f7f1-2245-8b0a-b7c70cf4b607@gmail.com>
Date: Sat, 5 Aug 2017 11:57:10 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CAJt_5EgTPi0Ts8xDQU2Kw4XWAFNAr7wkjxO2ShBgS0ZaskKmHw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------7EAC7297CC1655A4A20AEF66"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5nsCbG7ePL9Z9DVaw5Z56iLYD6Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 05 Aug 2017 10:57:52 -0000

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

+1

Stewart


On 04/08/2017 22:27, Pat Thaler wrote:
> I also prefer the style on: https://www.ietf.org/wg/chairs-page.html 
> <https://www.ietf.org/wg/chairs-page.html>. for a links page
>
> The low contrast tone-on-tone is hard to read and the two column 
> arrangement with just one to three links per column line makes it 
> easier to select the link.
>
> On Fri, Aug 4, 2017 at 9:34 AM, Tim Chown <tjc@ecs.soton.ac.uk 
> <mailto:tjc@ecs.soton.ac.uk>> wrote:
>
>     Hi,
>
>     > On 4 Aug 2017, at 16:57, Russ Housley <housley@vigilsec.com
>     <mailto:housley@vigilsec.com>> wrote:
>     >
>     >
>     > Many thanks to everyone who took time to review the
>     beta.ietf.org <http://beta.ietf.org> website and provide comments.
>     Based on feedback received, there seem to be a few items requiring
>     attention before moving the revamped public-facing website to
>     production:
>     >
>     > A. Provide a landing page dedicated to current IETF participants
>     >
>     > That page will include links to:
>     > - items on the left-side at www.ietf.org <http://www.ietf.org>
>     (or a subset thereof)
>     > - information about the next IETF meeting
>     > - links to functions at datatracker.ietf.org
>     <http://datatracker.ietf.org>
>     >
>     > Ideally this would also be:
>     > - viewable in a single screen on a desktop/laptop display
>     > -  reachable via a short, memorable URL without images
>     >
>     > A draft is currently posted at https://beta.ietf.org/links/
>
>     Having a direct and short URL to the ‘participants’ page’ will be
>     welcome.
>
>     But as it stands, the beta links page is difficult to parse. It
>     would be easier to parse were it laid out more like this style -
>     https://www.ietf.org/wg/chairs-page.html
>     <https://www.ietf.org/wg/chairs-page.html>.
>
>     > This page can be updated further based on input from the
>     community. There were also some suggestions received that
>     revisions to datatracker.ietf.org <http://datatracker.ietf.org>
>     might meet this need. While that is out of scope for this project,
>     suggestions have been noted by the tools team.  If you frequently
>     use something that is missing, please let us know.
>
>     The main site and the datatracker site take different perspective
>     on certain (important) areas, such as past and next meeting info.
>     Both are useful.  Witness
>     https://www.ietf.org/meeting/100/index.html
>     <https://www.ietf.org/meeting/100/index.html> and
>     https://datatracker.ietf.org/meeting/upcoming
>     <https://datatracker.ietf.org/meeting/upcoming>.
>
>     I’m expecting with the revamp that I would rarely visit
>     www.ietf.org <http://www.ietf.org>, rather I would visit the new
>     ‘links’ URL and the datatracker, where now I visit www.ietf.org
>     <http://www.ietf.org> and the datatracker.  I would point people
>     interested in finding out more about the IETF to www.ietf.org
>     <http://www.ietf.org>.
>
>     I’m very happy with the datatracker site.  New features like
>     support for managing and submitting draft reviews are really nice.
>
>     > B. Ensure WCAG 2.0 compliance
>     >
>     > This is a requirement of the SOW
>     (https://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf
>     <https://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf>)
>     and we are working with the website developer to ensure it is
>     implemented. The baseline goal is to improve upon the status of
>     the current www.ietf.org <http://www.ietf.org> site. Furthermore,
>     improving accessibility will continue to be an area of focus for
>     the revamped website.
>
>     As someone with contrast issues, I don’t think
>     https://beta.ietf.org/links/ would be compliant; it’s light blue
>     on light grey. There’s no need for the text to be that light, or
>     there to be a background ‘colour’.
>
>     Thanks,
>     Tim
>
>     > C. Conduct review with other key audiences, especially potential
>     participants and non-participants
>     >
>     > Based on the project SOW and the results of initial research
>     (https://iaoc.ietf.org/documents/Torchbox_ETFUserresearch.pdf
>     <https://iaoc.ietf.org/documents/Torchbox_ETFUserresearch.pdf>),
>     additional interviews with members of the key audiences will be
>     conducted to gather input. The results of those interviews will be
>     incorporated into the project via issues noted at:
>     https://github.com/ietf/www.ietf.org/issues
>     <https://github.com/ietf/www.ietf.org/issues>
>     >
>     > D. Improve data use and load times
>     >
>     > Load time and data usage was noted as being higher than the
>     current www.ietf.org <http://www.ietf.org> site. The expectation
>     is that load times will improve as the beta site moves to
>     production and is deployed on the CDN used by www.ietf.org
>     <http://www.ietf.org>. In addition, content elements such as
>     images will be adjusted to improve performance. In particular,
>     some of the potential participants and non-participants reviewers
>     will be in locations with less robust connectivity and their input
>     on this aspect of the revamped site will be sought out. This is an
>     aspect called out in the SOW and will have ongoing attention.
>     >
>     > Over the next few weeks, the project team will be working
>     through these and some other issues, such as filling out content
>     and moving to the the most current version of the open source
>     Wagtail Content Management System. There will be ongoing efforts
>     to improve the revamped site, so your ongoing input is encouraged.
>     Feedback can be sent to webmaster@ietf.org
>     <mailto:webmaster@ietf.org> or issues can be raised at:
>     >
>     > https://github.com/ietf/www.ietf.org/issues
>     <https://github.com/ietf/www.ietf.org/issues>
>     >
>     > Thanks again to all those who have provided input. I expect to
>     be in touch again as we move the revamped site to production.
>     >
>     > Sincerely,
>     > Russ Housley
>     > IETF Website Revamp Project Manager
>     >
>     >
>
>


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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>+1</p>
    <p>Stewart<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 04/08/2017 22:27, Pat Thaler wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAJt_5EgTPi0Ts8xDQU2Kw4XWAFNAr7wkjxO2ShBgS0ZaskKmHw@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">I also prefer the style on: <a
            href="https://www.ietf.org/wg/chairs-page.html"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.ietf.org/wg/<wbr>chairs-page.html</a>.
          for a links page</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">The low contrast tone-on-tone is hard
          to read and the two column arrangement with just one to three
          links per column line makes it easier to select the link.</div>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Fri, Aug 4, 2017 at 9:34 AM, Tim
            Chown <span dir="ltr">&lt;<a
                href="mailto:tjc@ecs.soton.ac.uk" target="_blank"
                moz-do-not-send="true">tjc@ecs.soton.ac.uk</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">Hi,<br>
              <span class="gmail-"><br>
                &gt; On 4 Aug 2017, at 16:57, Russ Housley &lt;<a
                  href="mailto:housley@vigilsec.com"
                  moz-do-not-send="true">housley@vigilsec.com</a>&gt;
                wrote:<br>
                &gt;<br>
                &gt;<br>
                &gt; Many thanks to everyone who took time to review 
                the <a href="http://beta.ietf.org" rel="noreferrer"
                  target="_blank" moz-do-not-send="true">beta.ietf.org</a>
                website and provide comments. Based on feedback
                received, there seem to be a few items requiring
                attention before moving the revamped public-facing
                website to production:<br>
                &gt;<br>
                &gt; A. Provide a landing page dedicated to current IETF
                participants<br>
                &gt;<br>
                &gt; That page will include links to:<br>
                &gt; - items on the left-side at <a
                  href="http://www.ietf.org" rel="noreferrer"
                  target="_blank" moz-do-not-send="true">www.ietf.org</a>
                (or a subset thereof)<br>
                &gt; - information about the next IETF meeting<br>
                &gt; - links to functions at <a
                  href="http://datatracker.ietf.org" rel="noreferrer"
                  target="_blank" moz-do-not-send="true">datatracker.ietf.org</a><br>
                &gt;<br>
                &gt; Ideally this would also be:<br>
                &gt; - viewable in a single screen on a desktop/laptop
                display<br>
                &gt; -  reachable via a short, memorable URL without
                images<br>
                &gt;<br>
                &gt; A draft is currently posted at <a
                  href="https://beta.ietf.org/links/" rel="noreferrer"
                  target="_blank" moz-do-not-send="true">https://beta.ietf.org/links/</a><br>
                <br>
              </span>Having a direct and short URL to the ‘participants’
              page’ will be welcome.<br>
              <br>
              But as it stands, the beta links page is difficult to
              parse. It would be easier to parse were it laid out more
              like this style - <a
                href="https://www.ietf.org/wg/chairs-page.html"
                rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.ietf.org/wg/<wbr>chairs-page.html</a>.<br>
              <span class="gmail-"><br>
                &gt; This page can be updated further based on input
                from the community. There were also some suggestions
                received that revisions to <a
                  href="http://datatracker.ietf.org" rel="noreferrer"
                  target="_blank" moz-do-not-send="true">datatracker.ietf.org</a>
                might meet this need. While that is out of scope for
                this project, suggestions have been noted by the tools
                team.  If you frequently use something that is missing,
                please let us know.<br>
                <br>
              </span>The main site and the datatracker site take
              different perspective on certain (important) areas, such
              as past and next meeting info. Both are useful.  Witness <a
                href="https://www.ietf.org/meeting/100/index.html"
                rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.ietf.org/meeting/<wbr>100/index.html</a>
              and <a
                href="https://datatracker.ietf.org/meeting/upcoming"
                rel="noreferrer" target="_blank" moz-do-not-send="true">https://datatracker.ietf.org/<wbr>meeting/upcoming</a>.<br>
              <br>
              I’m expecting with the revamp that I would rarely visit <a
                href="http://www.ietf.org" rel="noreferrer"
                target="_blank" moz-do-not-send="true">www.ietf.org</a>,
              rather I would visit the new ‘links’ URL and the
              datatracker, where now I visit <a
                href="http://www.ietf.org" rel="noreferrer"
                target="_blank" moz-do-not-send="true">www.ietf.org</a>
              and the datatracker.  I would point people interested in
              finding out more about the IETF to <a
                href="http://www.ietf.org" rel="noreferrer"
                target="_blank" moz-do-not-send="true">www.ietf.org</a>.<br>
              <br>
              I’m very happy with the datatracker site.  New features
              like support for managing and submitting draft reviews are
              really nice.<br>
              <span class="gmail-"><br>
                &gt; B. Ensure WCAG 2.0 compliance<br>
                &gt;<br>
                &gt; This is a requirement of the SOW (<a
href="https://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">https://iaoc.ietf.org/<wbr>documents/IETF-Website-SOW-<wbr>20140604-Final.pdf</a>)
                and we are working with the website developer to ensure
                it is implemented. The baseline goal is to improve upon
                the status of the current <a href="http://www.ietf.org"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">www.ietf.org</a> site.
                Furthermore, improving accessibility will continue to be
                an area of focus for the revamped website.<br>
                <br>
              </span>As someone with contrast issues, I don’t think <a
                href="https://beta.ietf.org/links/" rel="noreferrer"
                target="_blank" moz-do-not-send="true">https://beta.ietf.org/links/</a>
              would be compliant; it’s light blue on light grey. 
              There’s no need for the text to be that light, or there to
              be a background ‘colour’.<br>
              <br>
              Thanks,<br>
              Tim<br>
              <div class="gmail-HOEnZb">
                <div class="gmail-h5"><br>
                  &gt; C. Conduct review with other key audiences,
                  especially potential participants and non-participants<br>
                  &gt;<br>
                  &gt; Based on the project SOW and the results of
                  initial research (<a
                    href="https://iaoc.ietf.org/documents/Torchbox_ETFUserresearch.pdf"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">https://iaoc.ietf.org/<wbr>documents/Torchbox_<wbr>ETFUserresearch.pdf</a>),
                  additional interviews with members of the key
                  audiences will be conducted to gather input. The
                  results of those interviews will be incorporated into
                  the project via issues noted at: <a
                    href="https://github.com/ietf/www.ietf.org/issues"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">https://github.com/ietf/www.<wbr>ietf.org/issues</a><br>
                  &gt;<br>
                  &gt; D. Improve data use and load times<br>
                  &gt;<br>
                  &gt; Load time and data usage was noted as being
                  higher than the current <a href="http://www.ietf.org"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">www.ietf.org</a> site. The
                  expectation is that load times will improve as the
                  beta site moves to production and is deployed on the
                  CDN used by <a href="http://www.ietf.org"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">www.ietf.org</a>. In
                  addition, content elements such as images will be
                  adjusted to improve performance. In particular, some
                  of the potential participants and non-participants
                  reviewers will be in locations with less robust
                  connectivity and their input on this aspect of the
                  revamped site will be sought out. This is an aspect
                  called out in the SOW and will have ongoing attention.<br>
                  &gt;<br>
                  &gt; Over the next few weeks, the project team will be
                  working through these and some other issues, such as
                  filling out content and moving to the the most current
                  version of the open source Wagtail Content Management
                  System. There will be ongoing efforts to improve the
                  revamped site, so your ongoing input is encouraged.
                  Feedback can be sent to <a
                    href="mailto:webmaster@ietf.org"
                    moz-do-not-send="true">webmaster@ietf.org</a> or
                  issues can be raised at:<br>
                  &gt;<br>
                  &gt;   <a
                    href="https://github.com/ietf/www.ietf.org/issues"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">https://github.com/ietf/www.<wbr>ietf.org/issues</a><br>
                  &gt;<br>
                  &gt; Thanks again to all those who have provided
                  input. I expect to be in touch again as we move the
                  revamped site to production.<br>
                  &gt;<br>
                  &gt; Sincerely,<br>
                  &gt; Russ Housley<br>
                  &gt; IETF Website Revamp Project Manager<br>
                  &gt;<br>
                  &gt;<br>
                  <br>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------7EAC7297CC1655A4A20AEF66--


From nobody Sat Aug  5 08:49:07 2017
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 095C0131D32; Sat,  5 Aug 2017 08:49:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Yaron Sheffer <yaronf.ietf@gmail.com>
To: <secdir@ietf.org>
Cc: draft-weis-gdoi-rekey-ack.all@ietf.org, ietf@ietf.org
Subject: Secdir last call review of draft-weis-gdoi-rekey-ack-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150194814585.18635.3104789196001873381@ietfa.amsl.com>
Date: Sat, 05 Aug 2017 08:49:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Mu1RQf_80FPF33gV0Pl6i7a1x7A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 05 Aug 2017 15:49:06 -0000

Reviewer: Yaron Sheffer
Review result: Has Issues

Summary: this reviewer is not clear about the value of the push-ack (compared
to a pull) and about the strategy that was chosen.

* "For example, a GCKS policy can use the acknowledgements to determine [...]
which members may no longer be members of the group." This sentence is very
confusing: when are members not members?

* The new protocol capability is defined as optional, but really isn't. "A GM
receiving the KEK_ACK_REQUESTED attribute can choose to ignore it, thus
appearing as if it does not support the KEK_ACK_REQUESTED attribute. However,
GCKS policy may consider a non-responsive GM to no longer desire to be a member
of the group." So if you want to play the game, you MUST support the new
attribute.

* I'm puzzled at the overall protocol. Being able to send ACKs is a GM software
capability. Why not have the GM announce this capability when it initially
registers to the GCKS? Then the GCKS would know what to expect, whereas with
the current protocol it is left waiting for an ACK that may never come, either
because the GM is dead or because it just doesn't feel like responding. Add the
long waits (jitter of "a few seconds" and potential retries), and this looks
like a far from optimal management experience.

* 2.2: "This is a private key" - to avoid confusion, I suggest: "This is a
secret symmetric key" (if this is indeed the case). Obviously using the same
key for encryption and for HMAC is not a best practice.

* Sec. 5: ACK messages can also be duplicated in the network. I suggest to add
a sentence describing what the GCKS should do in this case.

* Sec. 6: I am confused about the notion of "jitter" here. If the PUSH messages
are sent as multicast (the recommended alternative AFAICT), I'm not sure about
the benefit of using multicast, given that each recipient responds with a
unicast ACK. And if the PUSH is unicast, there should be no reason for a jitter
as the sender can throttle the PUSH messages as necessary.

* Moreover, everything would be much more predictable if the GCKS could
indicate if a jitter is expected and how much of a jitter (based on size of the
group, network throughput, and queue length). Specifically, this would allow
the GCKS to tell how long it should wait for an ACK.

* Cryptographic agility: this document specifies only one algorithm for the
HASH value, and says that if a new algorithm is needed, there will be a new
KEK_ACK_REQUESTED payload defined. However to make sure that this really
"works", we need to define whether multiple such payloads can be sent
simultaneously (if e.g. some GMs still support the old algorithm) and what's
the expected behavior. I would suggest to define an additional SHA-512 payload
just to make for a concrete example.


From nobody Sat Aug  5 09:49:42 2017
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C066912EAF7 for <ietf@ietfa.amsl.com>; Sat,  5 Aug 2017 09:49:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ewa5HQKqlnSD for <ietf@ietfa.amsl.com>; Sat,  5 Aug 2017 09:49:38 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C837131CDC for <ietf@ietf.org>; Sat,  5 Aug 2017 09:49:38 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id g131so37585180oic.3 for <ietf@ietf.org>; Sat, 05 Aug 2017 09:49:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gl7izQPfyCIC06ifsscmBJJzociXm+5BsrP4L7Zl6a0=; b=N0OVzPDNlfASj9DqFO3YzUK0HB5GG5bI3dJUWCiPHDtr5XZoVAN7spIKb3uUgca5xP CTsBuWvfIhzxAj1coiC+XqykRRsP8PqPxDw8uRekDqg55WSwPfSDecVcg5ORkoQ7VmJQ 4LF/YVy33AAy/HGAMU/alUq6gAHwxgoMOcTEJS8FwcV2trHAOHGeJqtSPqTs9LsaN+P5 8gelH8RYU7NgvXyzsatDsdMvoiovJMUETnbzFhaC3CeYMTqyYDAlXhTALvyhwE8+aOyS SS7hdqjkxjh2saRg/5L8IVtYEdBBr8Cu3nYkS0NPcMyus9TYesBspQFsAzNOu8k7X52d M2Pg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=gl7izQPfyCIC06ifsscmBJJzociXm+5BsrP4L7Zl6a0=; b=KFzpNdGW8YqfkvkCaQVg0WM+n0BstW+fgKIw5WkkFTkEslTCxIE3PSs9gGLWkj0y1s f97qKteNKPZHpqlXkvFPRz7MhzuOsQahYhiENAa0rNYa6bKtZkXE5dfMqOLJUAiUf8k1 crq2DeXS+L1ha1ur4ESedMs+TRKA0vrPgwaOWXB9p+B39H4oc3iqFKQib4GRGDbZQCHQ D3fdJwRFlaa79rVTZ9a5WR5mVwVDEBS8Rv6yhR4RSdqFrMfMm+43F/7hU4RLhF6w4+qn pN1PPWMfBEXcGFKq1v8z6P1bADO4KZ6mDERWMAXVXDmdBylagPFCyvUjquW+k1on4ehq taiw==
X-Gm-Message-State: AHYfb5gS9ClFNA6850pUunpdWmPRaVEw6Xzq1hQnZNSaoHB9XRZebDL/ oNXa+qcMvd0EnAhiRQZK8xTMxE6rwg==
X-Received: by 10.202.173.209 with SMTP id w200mr3625033oie.170.1501951777613;  Sat, 05 Aug 2017 09:49:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.232.34 with HTTP; Sat, 5 Aug 2017 09:49:17 -0700 (PDT)
In-Reply-To: <0f1315d6-f7f1-2245-8b0a-b7c70cf4b607@gmail.com>
References: <0F2B4B79-1D2B-4193-A086-6AAA2314E687@ecs.soton.ac.uk> <9D0E96C9-EC66-4BEF-9726-5956A0787864@vigilsec.com> <EMEW3|d354b080c6285622a28f63748729b7a5y73HYr03tjc|ecs.soton.ac.uk|0F2B4B79-1D2B-4193-A086-6AAA2314E687@ecs.soton.ac.uk> <CAJt_5EgTPi0Ts8xDQU2Kw4XWAFNAr7wkjxO2ShBgS0ZaskKmHw@mail.gmail.com> <0f1315d6-f7f1-2245-8b0a-b7c70cf4b607@gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Sat, 5 Aug 2017 12:49:17 -0400
Message-ID: <CAA=duU1bStM-XEaQE6fdZgMvszApdCRfg=2-Tn8e2Kp66Cv9AQ@mail.gmail.com>
Subject: Re: Revamp of the www.ietf.org website - next steps
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: Pat Thaler <pat.thaler@broadcom.com>, Tim Chown <tjc@ecs.soton.ac.uk>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113cf6822cadc20556046603"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cKxp-99p3DzCRckIlmq_j5vqBgI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 05 Aug 2017 16:49:42 -0000

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

I also agree. Just because you CAN update web pages to make them looks more
=E2=80=9Cmodern=E2=80=9D or =E2=80=9Cstylish=E2=80=9D doesn=E2=80=99t mean =
that you SHOULD =E2=80=A6

Cheers,
Andy


On Sat, Aug 5, 2017 at 6:57 AM, Stewart Bryant <stewart.bryant@gmail.com>
wrote:

> +1
>
> Stewart
>
> On 04/08/2017 22:27, Pat Thaler wrote:
>
> I also prefer the style on: https://www.ietf.org/wg/chairs-page.html. for
> a links page
>
> The low contrast tone-on-tone is hard to read and the two column
> arrangement with just one to three links per column line makes it easier =
to
> select the link.
>
> On Fri, Aug 4, 2017 at 9:34 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
>
>> Hi,
>>
>> > On 4 Aug 2017, at 16:57, Russ Housley <housley@vigilsec.com> wrote:
>> >
>> >
>> > Many thanks to everyone who took time to review  the beta.ietf.org
>> website and provide comments. Based on feedback received, there seem to =
be
>> a few items requiring attention before moving the revamped public-facing
>> website to production:
>> >
>> > A. Provide a landing page dedicated to current IETF participants
>> >
>> > That page will include links to:
>> > - items on the left-side at www.ietf.org (or a subset thereof)
>> > - information about the next IETF meeting
>> > - links to functions at datatracker.ietf.org
>> >
>> > Ideally this would also be:
>> > - viewable in a single screen on a desktop/laptop display
>> > -  reachable via a short, memorable URL without images
>> >
>> > A draft is currently posted at https://beta.ietf.org/links/
>>
>> Having a direct and short URL to the =E2=80=98participants=E2=80=99 page=
=E2=80=99 will be welcome.
>>
>> But as it stands, the beta links page is difficult to parse. It would be
>> easier to parse were it laid out more like this style -
>> https://www.ietf.org/wg/chairs-page.html.
>>
>> > This page can be updated further based on input from the community.
>> There were also some suggestions received that revisions to
>> datatracker.ietf.org might meet this need. While that is out of scope
>> for this project, suggestions have been noted by the tools team.  If you
>> frequently use something that is missing, please let us know.
>>
>> The main site and the datatracker site take different perspective on
>> certain (important) areas, such as past and next meeting info. Both are
>> useful.  Witness https://www.ietf.org/meeting/100/index.html and
>> https://datatracker.ietf.org/meeting/upcoming.
>>
>> I=E2=80=99m expecting with the revamp that I would rarely visit www.ietf=
.org,
>> rather I would visit the new =E2=80=98links=E2=80=99 URL and the datatra=
cker, where now I
>> visit www.ietf.org and the datatracker.  I would point people interested
>> in finding out more about the IETF to www.ietf.org.
>>
>> I=E2=80=99m very happy with the datatracker site.  New features like sup=
port for
>> managing and submitting draft reviews are really nice.
>>
>> > B. Ensure WCAG 2.0 compliance
>> >
>> > This is a requirement of the SOW (https://iaoc.ietf.org/documen
>> ts/IETF-Website-SOW-20140604-Final.pdf) and we are working with the
>> website developer to ensure it is implemented. The baseline goal is to
>> improve upon the status of the current www.ietf.org site. Furthermore,
>> improving accessibility will continue to be an area of focus for the
>> revamped website.
>>
>> As someone with contrast issues, I don=E2=80=99t think
>> https://beta.ietf.org/links/ would be compliant; it=E2=80=99s light blue=
 on
>> light grey.  There=E2=80=99s no need for the text to be that light, or t=
here to be
>> a background =E2=80=98colour=E2=80=99.
>>
>> Thanks,
>> Tim
>>
>> > C. Conduct review with other key audiences, especially potential
>> participants and non-participants
>> >
>> > Based on the project SOW and the results of initial research (
>> https://iaoc.ietf.org/documents/Torchbox_ETFUserresearch.pdf),
>> additional interviews with members of the key audiences will be conducte=
d
>> to gather input. The results of those interviews will be incorporated in=
to
>> the project via issues noted at: https://github.com/ietf/www.ie
>> tf.org/issues
>> >
>> > D. Improve data use and load times
>> >
>> > Load time and data usage was noted as being higher than the current
>> www.ietf.org site. The expectation is that load times will improve as
>> the beta site moves to production and is deployed on the CDN used by
>> www.ietf.org. In addition, content elements such as images will be
>> adjusted to improve performance. In particular, some of the potential
>> participants and non-participants reviewers will be in locations with le=
ss
>> robust connectivity and their input on this aspect of the revamped site
>> will be sought out. This is an aspect called out in the SOW and will hav=
e
>> ongoing attention.
>> >
>> > Over the next few weeks, the project team will be working through thes=
e
>> and some other issues, such as filling out content and moving to the the
>> most current version of the open source Wagtail Content Management Syste=
m.
>> There will be ongoing efforts to improve the revamped site, so your ongo=
ing
>> input is encouraged. Feedback can be sent to webmaster@ietf.org or
>> issues can be raised at:
>> >
>> >   https://github.com/ietf/www.ietf.org/issues
>> >
>> > Thanks again to all those who have provided input. I expect to be in
>> touch again as we move the revamped site to production.
>> >
>> > Sincerely,
>> > Russ Housley
>> > IETF Website Revamp Project Manager
>> >
>> >
>>
>>
>
>

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

<div dir=3D"ltr">I also agree. Just because you CAN update web pages to mak=
e them looks more =E2=80=9Cmodern=E2=80=9D or =E2=80=9Cstylish=E2=80=9D doe=
sn=E2=80=99t mean that you SHOULD =E2=80=A6<div><br></div><div>Cheers,</div=
><div>Andy</div><div><br></div><div class=3D"gmail_extra"><br><div class=3D=
"gmail_quote">On Sat, Aug 5, 2017 at 6:57 AM, Stewart Bryant <span dir=3D"l=
tr">&lt;<a href=3D"mailto:stewart.bryant@gmail.com" target=3D"_blank">stewa=
rt.bryant@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p>+1</p><span class=3D"HOEnZb"><font color=3D"#888888">
    <p>Stewart<br>
    </p></font></span><div><div class=3D"h5">
    <br>
    <div class=3D"m_-7482734826266938422moz-cite-prefix">On 04/08/2017 22:2=
7, Pat Thaler wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_extra">I also prefer the style on:=C2=A0<a href=
=3D"https://www.ietf.org/wg/chairs-page.html" rel=3D"noreferrer" target=3D"=
_blank">https://www.ietf.org/wg/ch<wbr>airs-page.html</a>.
          for a links page</div>
        <div class=3D"gmail_extra"><br>
        </div>
        <div class=3D"gmail_extra">The low contrast tone-on-tone is hard
          to read and the two column arrangement with just one to three
          links per column line makes it easier to select the link.</div>
        <div class=3D"gmail_extra"><br>
          <div class=3D"gmail_quote">On Fri, Aug 4, 2017 at 9:34 AM, Tim
            Chown <span dir=3D"ltr">&lt;<a href=3D"mailto:tjc@ecs.soton.ac.=
uk" target=3D"_blank">tjc@ecs.soton.ac.uk</a>&gt;</span>
            wrote:<br>
            <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
              <span class=3D"m_-7482734826266938422gmail-"><br>
                &gt; On 4 Aug 2017, at 16:57, Russ Housley &lt;<a href=3D"m=
ailto:housley@vigilsec.com" target=3D"_blank">housley@vigilsec.com</a>&gt;
                wrote:<br>
                &gt;<br>
                &gt;<br>
                &gt; Many thanks to everyone who took time to review=C2=A0
                the <a href=3D"http://beta.ietf.org" rel=3D"noreferrer" tar=
get=3D"_blank">beta.ietf.org</a>
                website and provide comments. Based on feedback
                received, there seem to be a few items requiring
                attention before moving the revamped public-facing
                website to production:<br>
                &gt;<br>
                &gt; A. Provide a landing page dedicated to current IETF
                participants<br>
                &gt;<br>
                &gt; That page will include links to:<br>
                &gt; - items on the left-side at <a href=3D"http://www.ietf=
.org" rel=3D"noreferrer" target=3D"_blank">www.ietf.org</a>
                (or a subset thereof)<br>
                &gt; - information about the next IETF meeting<br>
                &gt; - links to functions at <a href=3D"http://datatracker.=
ietf.org" rel=3D"noreferrer" target=3D"_blank">datatracker.ietf.org</a><br>
                &gt;<br>
                &gt; Ideally this would also be:<br>
                &gt; - viewable in a single screen on a desktop/laptop
                display<br>
                &gt; -=C2=A0 reachable via a short, memorable URL without
                images<br>
                &gt;<br>
                &gt; A draft is currently posted at <a href=3D"https://beta=
.ietf.org/links/" rel=3D"noreferrer" target=3D"_blank">https://beta.ietf.or=
g/links/</a><br>
                <br>
              </span>Having a direct and short URL to the =E2=80=98particip=
ants=E2=80=99
              page=E2=80=99 will be welcome.<br>
              <br>
              But as it stands, the beta links page is difficult to
              parse. It would be easier to parse were it laid out more
              like this style - <a href=3D"https://www.ietf.org/wg/chairs-p=
age.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/wg/chai=
rs<wbr>-page.html</a>.<br>
              <span class=3D"m_-7482734826266938422gmail-"><br>
                &gt; This page can be updated further based on input
                from the community. There were also some suggestions
                received that revisions to <a href=3D"http://datatracker.ie=
tf.org" rel=3D"noreferrer" target=3D"_blank">datatracker.ietf.org</a>
                might meet this need. While that is out of scope for
                this project, suggestions have been noted by the tools
                team.=C2=A0 If you frequently use something that is missing=
,
                please let us know.<br>
                <br>
              </span>The main site and the datatracker site take
              different perspective on certain (important) areas, such
              as past and next meeting info. Both are useful.=C2=A0 Witness=
 <a href=3D"https://www.ietf.org/meeting/100/index.html" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/meeting/1<wbr>00/index.html</a>
              and <a href=3D"https://datatracker.ietf.org/meeting/upcoming"=
 rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/m<wbr>ee=
ting/upcoming</a>.<br>
              <br>
              I=E2=80=99m expecting with the revamp that I would rarely vis=
it <a href=3D"http://www.ietf.org" rel=3D"noreferrer" target=3D"_blank">www=
.ietf.org</a>,
              rather I would visit the new =E2=80=98links=E2=80=99 URL and =
the
              datatracker, where now I visit <a href=3D"http://www.ietf.org=
" rel=3D"noreferrer" target=3D"_blank">www.ietf.org</a>
              and the datatracker.=C2=A0 I would point people interested in
              finding out more about the IETF to <a href=3D"http://www.ietf=
.org" rel=3D"noreferrer" target=3D"_blank">www.ietf.org</a>.<br>
              <br>
              I=E2=80=99m very happy with the datatracker site.=C2=A0 New f=
eatures
              like support for managing and submitting draft reviews are
              really nice.<br>
              <span class=3D"m_-7482734826266938422gmail-"><br>
                &gt; B. Ensure WCAG 2.0 compliance<br>
                &gt;<br>
                &gt; This is a requirement of the SOW (<a href=3D"https://i=
aoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf" rel=3D"noreferr=
er" target=3D"_blank">https://iaoc.ietf.org/documen<wbr>ts/IETF-Website-SOW=
-20140604-<wbr>Final.pdf</a>)
                and we are working with the website developer to ensure
                it is implemented. The baseline goal is to improve upon
                the status of the current <a href=3D"http://www.ietf.org" r=
el=3D"noreferrer" target=3D"_blank">www.ietf.org</a> site.
                Furthermore, improving accessibility will continue to be
                an area of focus for the revamped website.<br>
                <br>
              </span>As someone with contrast issues, I don=E2=80=99t think=
 <a href=3D"https://beta.ietf.org/links/" rel=3D"noreferrer" target=3D"_bla=
nk">https://beta.ietf.org/links/</a>
              would be compliant; it=E2=80=99s light blue on light grey.=C2=
=A0
              There=E2=80=99s no need for the text to be that light, or the=
re to
              be a background =E2=80=98colour=E2=80=99.<br>
              <br>
              Thanks,<br>
              Tim<br>
              <div class=3D"m_-7482734826266938422gmail-HOEnZb">
                <div class=3D"m_-7482734826266938422gmail-h5"><br>
                  &gt; C. Conduct review with other key audiences,
                  especially potential participants and non-participants<br=
>
                  &gt;<br>
                  &gt; Based on the project SOW and the results of
                  initial research (<a href=3D"https://iaoc.ietf.org/docume=
nts/Torchbox_ETFUserresearch.pdf" rel=3D"noreferrer" target=3D"_blank">http=
s://iaoc.ietf.org/documen<wbr>ts/Torchbox_ETFUserresearch.<wbr>pdf</a>),
                  additional interviews with members of the key
                  audiences will be conducted to gather input. The
                  results of those interviews will be incorporated into
                  the project via issues noted at: <a href=3D"https://githu=
b.com/ietf/www.ietf.org/issues" rel=3D"noreferrer" target=3D"_blank">https:=
//github.com/ietf/www.ie<wbr>tf.org/issues</a><br>
                  &gt;<br>
                  &gt; D. Improve data use and load times<br>
                  &gt;<br>
                  &gt; Load time and data usage was noted as being
                  higher than the current <a href=3D"http://www.ietf.org" r=
el=3D"noreferrer" target=3D"_blank">www.ietf.org</a> site. The
                  expectation is that load times will improve as the
                  beta site moves to production and is deployed on the
                  CDN used by <a href=3D"http://www.ietf.org" rel=3D"norefe=
rrer" target=3D"_blank">www.ietf.org</a>. In
                  addition, content elements such as images will be
                  adjusted to improve performance. In particular, some
                  of the potential participants and non-participants
                  reviewers will be in locations with less robust
                  connectivity and their input on this aspect of the
                  revamped site will be sought out. This is an aspect
                  called out in the SOW and will have ongoing attention.<br=
>
                  &gt;<br>
                  &gt; Over the next few weeks, the project team will be
                  working through these and some other issues, such as
                  filling out content and moving to the the most current
                  version of the open source Wagtail Content Management
                  System. There will be ongoing efforts to improve the
                  revamped site, so your ongoing input is encouraged.
                  Feedback can be sent to <a href=3D"mailto:webmaster@ietf.=
org" target=3D"_blank">webmaster@ietf.org</a> or
                  issues can be raised at:<br>
                  &gt;<br>
                  &gt;=C2=A0 =C2=A0<a href=3D"https://github.com/ietf/www.i=
etf.org/issues" rel=3D"noreferrer" target=3D"_blank">https://github.com/iet=
f/www.i<wbr>etf.org/issues</a><br>
                  &gt;<br>
                  &gt; Thanks again to all those who have provided
                  input. I expect to be in touch again as we move the
                  revamped site to production.<br>
                  &gt;<br>
                  &gt; Sincerely,<br>
                  &gt; Russ Housley<br>
                  &gt; IETF Website Revamp Project Manager<br>
                  &gt;<br>
                  &gt;<br>
                  <br>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
  </div></div></div>

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

--001a113cf6822cadc20556046603--


From nobody Mon Aug  7 18:15:11 2017
Return-Path: <amy.yemin@huawei.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 942C2131D34; Mon,  7 Aug 2017 18:15:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Min Ye <amy.yemin@huawei.com>
To: <rtg-dir@ietf.org>
Cc: ccamp@ietf.org, draft-ietf-ccamp-dwdm-if-mng-ctrl-fwk.all@ietf.org, ietf@ietf.org
Subject: Rtgdir early review of draft-ietf-ccamp-dwdm-if-mng-ctrl-fwk-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150215490357.12451.8584891205942119809@ietfa.amsl.com>
Date: Mon, 07 Aug 2017 18:15:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LUHqDURVNhHyKY9W9LLoU5H1WUo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 08 Aug 2017 01:15:03 -0000

Reviewer: Keyur Patel
Review result: Has Issues

Document: draft-item-ccamp-dwdm-if-mng-ctrl-fwk
Reviewer: Keyur Patel
Review Date: August 7, 2017
Intended Status: Informational Track

Here are my comments.

Overall, the document is well organized and clear about the problem statement
and requirements for the framework for Management and Control of DWDM optical
interface. This document could simplify early draft sections text and fix few
typos + grammatical errors.

Attached are my comments:

1 - Section 1, Consider replacing: "Carriers deploy their networks today based
on transport und packet" with "Carriers deploy their networks today based on
transport and packet".

2 - Section 1, Last Paragraph, consider replacing: "Optical routing and
wavelength assignment based on WSON is out of scope although can benefit of the
way the optical parameters are exchanged between the Client and the DWDM
Network." with: "Although Optical routing and wavelength assignment based on
WSON is out of scope, they can benefit from the optical parameters that are
exchanged between the Client and the DWDM Network."

3 - Section 2, first Paragraph, consider replacing: "The DWDM interfaces
migration…" with "The DWDM interface migration..."

4 - Section 2, fifth Paragraph: "Administrative domain [G.805]: For the
purposes of this Recommendation"
   Perhaps the authors meant "this document" as oppose to "this Recommendation"?

5 - Section 3.1.2 last Paragraph: "The following documents[DWDM-interface-MIB],
[YANG], [LMP] define such a protocol- FIX-THE-REFERENCE specific information
using SNMP SMI, Yang models and LMP TLV to support the direct exchange of
information between the client and the network management and control plane."

Does this also apply to Section 3.1.1 or it is specific to Section 3.1.2? If
so, it should be moved out of Section 3.1.2.

6 - Section 4.1.2, third Paragraph and 5.1: LMP uses reliable UDP.  For any
Indirect and Direct connections, how does the optical network node recover from
partial network configurations upon LMP based adjacency failures? Does that
need to be a requirement for LMP extensions?

7 - Section 5.2.1: The alarms that can be generated for use cases mentioned in
5.2.1 can be chatty particularly when sending over LMP (or protocol of choice).
Is there a requirement to pace/damp the rate of Alarms (that would be carried
within LMP)?



From nobody Mon Aug  7 19:29:30 2017
Return-Path: <worley@ariadne.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 98882131E08; Mon,  7 Aug 2017 19:29:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dale Worley <worley@ariadne.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-bess-evpn-etree.all@ietf.org, ietf@ietf.org, bess@ietf.org
Subject: Genart last call review of draft-ietf-bess-evpn-etree-12
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150215935959.12343.2397423105077446380@ietfa.amsl.com>
Date: Mon, 07 Aug 2017 19:29:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sNKmHK0zB_j7O3XMJrfJZIRz4pk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 08 Aug 2017 02:29:20 -0000

Reviewer: Dale Worley
Review result: On the Right Track

I am the assigned Gen-ART reviewer for this draft.  The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document:  draft-ietf-bess-evpn-etree-12
Reviewer:  Dale R. Worley
Review Date:  2017-08-07
IETF LC End Date:  2017-08-09
IESG Telechat date:  2017-08-17

Summary:

This draft is on the right track but has open issues, described in the
review.  A few of the issues are directly technical.

Reading this draft, I have the sense that it isn't so much a
specification as the description of an idea, which is that EVPN can be
used to implement E-Tree functionality.  It reads as if someone who is
extremely knowledgeable about EVPN is outlining the idea to someone
similar, given that various details don't seem to be worked out
completely and that in several places there are alternative
implementation methods that are mentioned but do not seem to be
rigorously enumerated.  The document seems to more describe *class* of
ways of implementing E-Trees, and not a rigidly delimited class.

As far as I can tell, the idea works, but I suspect that an
implementor would not just be following the specification but
completing it in many respects.  Given that the document seems to
extend the mechanisms of RFC 7432, I suspect that an implementor would
have to carefully work out the details of all the BGP announcements,
and that not all implementations would interoperate.  E.g., "This Leaf
label is advertised to other PE devices, using the E-TREE Extended
Community" sounds to me like it's very under-specified.

The way forward seems to be clear:  The draft needs to be edited
carefully, filling in the missing details and making more explicit and
rigid the various implementation alternatives.  It might be worth
enumerating all of the mentioned implementation choices in one place,
as successful interoperation requires that all devices in a VPN are
using the same choices.  And I think interoperation needs to be
emphasized -- two devices that implement this draft should
interoperate if they are configured to have the same choices of the
implementation choices enumerated in the draft.  Otherwise, this draft
is just the outline for a dozen vendors' similar-but-not-interoperable
proprietary products.

Abstract

   This document
   discusses how those functional requirements can be easily met with
   Ethernet VPN (EVPN) and how EVPN offers a more efficient
   implementation of these functions.

"More efficient" than what?  The abstract reads as if this document is
an alternative method of implementing E-Tree, but I read well into the
draft before it became clear that this draft is an alternative to RFC
7387, rather than that this draft and RFC 7387 are an alternative to
something else.  The abstract does not specifically state all of the
relationships between the specifications it mentions.

And although this mechanism is described as "more efficient", there
doesn't seem to be any discussion of how it is more efficient.  You
don't need a lot of detail for this, but it would be helpful if there
was at least a brief description of what way it is more efficient and
some indication of the degree.

Also, what is relationship between "EVPN" and this document?  Is EVPN
a widely-known technology whose name need not be footnoted?  Is it
something defined in this document?  Importantly, is the usage in this
document a subset within some defined EVPN specification, or is it a
modification/extension of EVPN?

   This document makes use of the
   most significant bit of the scope governed by the IANA registry
   created by RFC7385, and hence updates RFC7385 accordingly.

The use of "scope" is peculiar here.  Generally, "scope" refers to a
region of some sort of space, so one would say "scope value" or "scope
value field" to refer to a group of bits that designate a scope.  But
checking with RFC 7385 and the IANA registry page for "Border Gateway
Protocol (BGP) Parameters", I am unable to find any occurrence of the
word "scope".  And other than a very similar passage in section 1,
"scope" only appears in this document in the phrase "scope of this
document".  Perhaps "scope" should be "tunnel type"?

Table of Contents

What is the capitalization rule you're using for section titles?
E.g., sections 3.2.{1,2,3,4} are capitalized in a decidedly different
way that other sections.

1  Introduction

   The Metro Ethernet Forum (MEF) has defined a rooted-multipoint
   Ethernet service known as Ethernet Tree (E-Tree) [MEF6.1]. In an E-
   Tree service, Attachment Circuits (ACs) are labeled as either Root or
   Leaf ACs. Root ACs can communicate with all other ACs. Leaf ACs can
   communicate with Root ACs but not with other Leaf ACs. 

Given the use of "rooted-multipoint", it seems that there is to be
exactly one Root AC per virtual Ethernet, as rooted trees have exactly
one root node.  Where or not that is true is very important for the
conceptual model of the service, but is not stated clearly
here. Perhaps there is a terminology problem, as when I see "rooted"
and "tree" in a sentence, I assume that the "tree" is "rooted", i.e.,
it has exactly one root.  (Similarly in Wikipedia, "Rooted-MultiPoint"
[sic] redirects to "Point-to-multipoint", which says "providing
multiple paths from a *single* [my emphasis] location to multiple
locations".)  However, the last sentences of section 2.1 suggest that
an E-Tree might have more than one Root.

Subtle point:  If there are multiple Roots, the text implies that all
Roots can communicate with all other Roots.  It might be worth
mentioning that explicitly, as the naive reader might overlook it.
Indeed, it is possible within this model that all endpoints are Roots,
in which case the VPN is completely connected.

Also, it seems that in scenario 3 of section 2 that a single AC could
have multiple endpoints on it some of which are Root and some are
Leaf, which doesn't fit within the description in this paragraph.

(In general, meticulously editing the Introduction section is
extremely helpful to readers who aren't already thoroughly familiar
with the subject.)

   [RFC7387] proposes the solution framework for supporting E-Tree
   service in MPLS networks.

I think this should be "a solution framework".  If one says "the solution
framework", then there is in some way only one solution framework, and
the RFC would "state" it.  Saying that the RFC "proposes" a framework
shows that there could be others that could be proposed.  Similarly in
the next sentence would be "... of an overall solution ...".

   The document identifies the functional
   components of the overall solution to emulate E-Tree services in
   addition to Ethernet LAN (E-LAN) services on an existing MPLS
   network.

The relationship of E-LAN to E-Tree is not clear, and how the phrase
"on an existing MPLS network" attaches to either is not clear.  I
think you mean at least:

   The document identifies the functional components of the overall
   solution to emulate E-Tree services on an existing MPLS network.

and that the document does the same for E-LAN.  I suspect that there
is some implied relationship between E-Tree and E-LAN, other than that
solution frameworks are described in RFC 7387.

However, the term "E-LAN" does not appear anywhere else in this
document, is it important to include it?  And given that E-Tree gets
its own reference to describe its functional specification, shouldn't
there be a reference giving the functional specification of "E-LAN"?
(As opposed to the implementation specification in RFC 7387.)

   [RFC7432] is a solution for multipoint L2VPN services, with advanced
   multi-homing capabilities, using BGP for distributing customer/client
   MAC address reach-ability information over the MPLS/IP network.
   [RFC7623] combines the functionality of EVPN with [802.1ah] Provider
   Backbone Bridging (PBB) for MAC address scalability.

The structure of this paragraph suggests that "EVPN" is defined by RFC
7432, but I had to look at 7432 to verify that.  Perhaps "[RFC7432]
defines EVPN, a solution for ..."?

"[802.1ah]" appears to be a reference, but there is no entry in
section 9 for it.

   This document discusses how the functional requirements for E-Tree
   service can be met with (PBB-)EVPN and how (PBB-)EVPN offers a more
   efficient implementation of these functions.

This paragraph has some of the same problems as the abstract.  But I
am now starting to suspect that the document is proposing using EVPN
as a way to provide E-Tree service *instead of* using the RFC 7387
proposal.  If that is so, this sentence needs to end "a more efficient
implementation of these functions than RFC7387.", and the third
sentence of the Abstract should start "This document discusses how the
functional requirements for E-Tree can be ..." (making clear that it
logically succeeds the first sentence, not the second), and the use of
"EVPN" in the Abstract needs to reference RFC 7432.

   This document makes use
   of the most significant bit of the scope governed by the IANA
   registry created by RFC7385, and hence updates RFC7385 accordingly.

The "scope" business is still unresolved.

Also, this sentence doesn't say what the new purpose of the bit is.
Perhaps something like, "This document repurposes the most significant
bit of the tunnel type byte governed by the IANA registry created by
RFC7385 to ...".  But that is still opaque, as few people will
immediately know the purpose of a registry referenced only by RFC
number.  Perhaps "... the Tunnel Type byte in the BGP PMSI Tunnel
attribute ...".

   Section 2 discusses E-TREE scenarios.

What the proper capitalization of "E-Tree"?

1.1  Terminology

The text uses many acronyms which may not be widely known by people
not deeply conversant in these technologies.  It may help to put a
define many of them in section 1.1.  (E.g., "EVI" is defined well down
in the second paragraph of section 2.1, whereas it is used in the
first paragraph of that section.)

2  E-Tree Scenarios

The enumeration of cases is unclear.  I think you mean for scenario 1,
"PE is exclusively Leaf or Root site(s)", etc.  But "OR" doesn't carry
that meaning unambiguously.  You could s/OR/XOR/ to make it
unambiguous, but that would be awkward and very geekish.

Also, I think "MAC address" is more correct than "MAC" here.

2.1 Scenario 1: Leaf OR Root site(s) per PE

   In this scenario, a PE may receive traffic from either Root ACs OR
   Leaf ACs for a given MAC-VRF/bridge table, but not both concurrently.

There's a problem with "receive traffic from", because one can say a
PE "receives traffic from" any endpoint in the VPN -- if the traffic
is egressing from the VPN through the PE.  I think you want to phrase
it in terms of "all endpoints attached to the ACs attached to the PE
are Root endpoints or they are all Leaf endpoints".  Or you could
rephrase it in terms of ingressing traffic.  But really, Root and Leaf
are properties of endpoints much more than properties of traffic, and
it's best to use the terms accordingly.

Also, the meaning of "concurrently" is probably not what you want --
strictly, it means that two things cannot happen at the same time, but
it implies that they can happen at different times.  I don't think
that is what you mean.

                   +---------+            +---------+
                   |   PE1   |            |   PE2   |
    +---+          |  +---+  |  +------+  |  +---+  |            +---+
    |CE1+---AC1----+--+   |  |  | MPLS |  |  |   +--+----AC2-----+CE2|
    +---+  (Root)  |  |MAC|  |  |  /IP |  |  |MAC|  |   (Leaf)   +---+
                   |  |VRF|  |  |      |  |  |VRF|  |
                   |  |   |  |  |      |  |  |   |  |            +---+
                   |  |   |  |  |      |  |  |   +--+----AC3-----+CE3|
                   |  +---+  |  +------+  |  +---+  |   (Leaf)   +---+
                   +---------+            +---------+

The figure is useful in showing the relationship of PE, AC, and CE.
(I see now that what I call an "endpoint" is generally known as a
"CE".)  But there is a shortage of connection lines.  I think
something like this would be clearer:

                   +---------+            +---------+
                   |   PE1   |            |   PE2   |
    +---+          |  +---+  |  +------+  |  +---+  |            +---+
    |CE1+---AC1----+--+   |  |  | MPLS |  |  |   +--+----AC2-----+CE2|
    +---+  (Root)  |  |MAC|  |  |  /IP |  |  |MAC|  |   (Leaf)   +---+
                   |  |VRF+------------------+VRF|  |
                   |  |   |  |  |      |  |  |   |  |            +---+
                   |  |   |  |  |      |  |  |   +--+----AC3-----+CE3|
                   |  +---+  |  +------+  |  +---+  |   (Leaf)   +---+
                   +---------+            +---------+


   In such scenario, using tailored BGP Route Target (RT) import/export
   policies among the PEs belonging to the same EVI, can be used to
   restrict the communications among Leaf PEs.

Presumably, "In such a scenario ..." but I prefer "In this scenario
...".  But the grammar has a problem, since if you elide the clause
"using ... the same EVI", it reads "In such [a] scenario ... can be
used to ...".  I think you want "In such a scenario, tailored BGP
... policies ... can be used to ...".

I think you want "prevent" rather than "restrict", since by the
definition of E-Tree service, there is to be no communication between
Leaf ACs at all -- restrict has an implication that the limitation is
not absolute (and indeed, is somehow configurable).

   from one Leaf AC to another Leaf AC on a MAC-VRF for a given E-TREE
   EVI.

Across the whole document, it's clear that the operation of the
proposed E-Tree mechanism is absolutely independent for each EVI.
E.g., here you note that scenario 1 is "for any PE, *for any EVI*, all
CEs connected to that PE are either all Roots or all Leafs".  But you
could simply state this separation of each EVI from every other EVI at
the top of the document and not have to keep repeating it at various
places throughout the document.

That is, I think it's true.  If there are ways in which the
implementation of one EVI interacts the implementation of another EVI,
that needs to be prominently flagged and carefully assessed for
causing subtle problems.  E.g., in section 3.2.1, it seems like the
advertisements of "Ethernet A-D per ES routes" may bundle information
about multiple EVIs.

2.2 Scenario 2: Leaf OR Root site(s) per AC

There is a technical question in that scenario 1 is more restrictive
than scenario 2, so any solution for scenario 2 can be used in
scenario 1.  But only alternative A is presented for scenario 1, even
though alternative B must necessarily work.  Presumably there is a
reason why alternative B is not presented for scenario 1, and I think
it should be stated.

This fact caused me some confusion when I was reading the document:
The mechanism described in 2.1 seems to be satisfactory for fulfilling
the requirements stated in paragraph 2, so but paragraph 2 introduces
"coloring" of MAC addresses.  I think that the expositions of the
three scenarios could better be done if they were all coordinated with
each other.  Perhaps the choice between alternatives A and B for
coloring MAC addresses is actually common across the three scenarios,
and what really changes between the scenarios is the efficiency
tradeoffs between the two alternatives.

   Approach (A) would require the same data plane enhancements as
   approach (B) if MAC-VRF and bridge tables used per VLAN, are to
   remain consistent with [RFC7432] (section 6).

What is the subject of "are"?

   In order to avoid data-
   plane enhancements for approach (A), multiple bridge tables per VLAN
   may be considered; 

It's not clear what the difference is between "MAC-VRF and bridge
tables used per VLAN" and "multiple bridge tables per VLAN".  Can this
be described in a way that is clearer to people who are not highly
familiar with the subject?

   then two RTs (one for Root and another for Leaf)
   can still be used with approach (B)

This seems to be proposing some sort of mixture of alternatives A and
B.  What exactly are the alternatives that are being specified that
the implementor chooses between?

2.3 Scenario 3: Leaf OR Root site(s) per MAC

   This scenario is
   not covered in both [RFC7387] and [MEF6.1]

Literally, this means "It is not true that this scenario is covered in
RFC 7387 and in MEF6.1."  But I think you mean "This scenario is not
covered in either ...".

   the Designated Forwarding (DF)
   filtering per [RFC7432] would not be compatible with the required
   egress filtering

Interestingly, "designated forwarding" is not mentioned anywhere else
in this draft.  Does it appear elsewhere or is it implied in the
mechanics of RFC 7432 that are used throughout this draft?

There seems to be no description of the techniques to be used in this
case.

And given that it seems to be contemplated to support scenario 3,
there are numerous places in the draft where "a Root AC" and "a Leaf
AC" are not correct.  You could use "a Root CE" or "a Root site", etc.

3 Operation for EVPN

   In other words,
   [RFC7432] has inherent capability to support E-TREE services without
   defining any new BGP routes but by just defining a new BGP Extended
   Community for leaf indication as shown later in this document
   (section 5.1).

And by implication, the addition of various processing of that leaf
indication.

But this does show that this draft is not just an application of RFC
7432 but an extension of it.

3.1 Known Unicast Traffic

   sending ... traffic over MPLS/IP core to be filtered at the egress
   PE ...

The implication seems to be that this "sending" that is avoided is
really multicast, from the ingress PE to all egress PEs.  Naively,
describing this as "over MPLS/IP core" doesn't seem to capture the
meaning, since *all* traffic is going to be send "over the MPLS/IP
core".

   To provide such ingress filtering for known unicast traffic, a PE
   MUST indicate to other PEs what kind of sites (root or leaf) its MAC
   addresses are associated with by advertising a leaf indication flag
   (via an Extended Community) along with each of its MAC/IP
   Advertisement routes. The lack of such flag indicates that the MAC
   address is associated with a root site. This scheme applies to all
   scenarios described in section 2. 

Read literally, this paragraph says that a leaf indication flag MUST
be present on each advertisement, but then says the absence of the
flag means that it is a root side (implying that the absence of the
flag is legitimate).  There are two alternatives -- a) the flag is a
1/0 flag, with one value meaning Leaf and one meaning Root or b) the
flag is some optional field whose presence means Leaf and whose
absence means Root -- but this wording isn't quite correct for either.

Also, this paragraph seems to be saying that the extended community is
always used to indicate Leaf/Root status (though perhaps it specifies
status by its absence).  But the descriptions in section 2 seem to be
saying that alternative A doesn't require the extended community,
which contradicts the MUST in this paragraph.

3.2 BUM Traffic

   This specification does not provide support for filtering BUM
   (Broadcast, Unknown, and Multicast) traffic on the ingress PE because
   it is not possible to perform filtering of BUM traffic on the ingress
   PE, as is the case with known unicast described above, due to the
   multi-destination nature of BUM traffic.

This sentence is quite awkward.  I think you can carry all of the
meaning with "This specification does not provide support for
filtering BUM (Broadcast, Unknown, and Multicast) traffic on the
ingress PE because it is not possible to do so, due to the
multi-destination nature of BUM traffic."

But the phrase "does not provide support" is not correct -- the
ingress PE fully *supports* BUM traffic (except in scenario 3), it's
just that the support doesn't include *filtering* by the ingress PE.

   the MPLS-encapsulated frames MUST be tagged with an
   indication that they originated from a Leaf AC - i.e., to be tagged
   with a Leaf label as specified in section 5.1. 

As written, the sentence requires "... tagged with an indication
whether they originated ...".  The use of "that" states that all the
frames originated from a Leaf AC.

Looking ahead to section 5.1, I see that the Leaf label is
considerably longer than the 1 bit that would seem to be necessary for
this function given its description here.  And the next paragraph
suggests that the assignment of Leaf labels is complex.  It would be
helpful if you clarified here all of the functionality of Leaf labels
so the reader has context for following paragraphs.  I suspect the
meaning here is "all MPLS-encapsulated frame are tagged with labels,
and to distinguish Leaf-originated frames, they must be tagged with
labels which are known to be Leaf labels".  Also, is there only one
leaf label (for an EVI), or can there be many, perhaps one for every
Leaf AC?

   The main difference between
   downstream and upstream assigned Leaf label is that in case of
   downstream assigned not all egress PE devices need to receive the
   label just like ESI label for ingress replication procedures defined
   in [RFC7432].

This sentence isn't clear to me.  I suspect that it just needs a few
words adjusted.  Also, I suspect that it would help to move the final
clause, "just like ESI label ..." to a separate sentence.

   On the ingress PE, the PE needs to place all its Leaf ACs for a given
   bridge domain in a single split-horizon group in order to prevent
   intra-PE forwarding among its Leaf ACs.

The phrase "bridge domain" appears only twice in this document.  I
suspect it is synonymous with some other term you are using.

My belief is that a "split-horizon group" means a group of ACs that
are visible to each other.  If that is correct, this sentence needs to
be rephrased to something like "... the PE needs to place each of its
Leaf ACs for a given bridge domain into separate split-horizon groups
...".

   Other mechanisms
   for identifying root or leaf (e.g., on a per MAC address basis) is
   beyond the scope of this document.

Scenario 3 in section 2.3 posits that a single AC may support both
Leaf and Root endpoints.  So there must be a known method of
performing this identification on a per-MAC address basis, or else
scenario 3 cannot be implemented at present.  That doesn't require
that this document specify or describe a method of doing so, but it
seems that at this point, the document should either identify one or
more ways in which it can be done, or admit that there are no known
mechanisms at this time.  (Or perhaps that there are no known *good*
mechanisms at this time.)  Otherwise the inclusion of scenario 3 is
purely hypothetical.

The acronym "ES" us used a lot in this section, meaning "Ethernet
segment".  Is "Ethernet segment" related to "AC"?

3.2.1 BUM traffic originated from a single-homed site on a leaf AC

What is the rule for capitalizing or not the words "leaf" and "root"?

   This Leaf label is
   advertised to other PE devices, using the E-TREE Extended Community
   (section 5.1) along with an Ethernet A-D per ES route with ESI of
   zero and a set of Route Targets (RTs) corresponding to all EVIs on
   the PE with at least one leaf site per EVI.

I'm not sure, but I think you mean s/all EVIs on the PE with at least
one leaf site per EVI/all EVIs which have at least one leaf site on
the PE/.

   The set of Ethernet A-D
   per ES routes may be needed if the number of Route Targets (RTs) that
   need to be sent exceed the limit on a single route per [RFC7432].

I suspect from the text that "Ethernet A-D per ES route" is a single
term, but I have no idea what it is referring to.  And I suspect that
someone has coined a shorter term to use.

I suspect that one or more words in this sentence aren't quite right
and I can't parse it.  For instance "The set of ... routes may be
needed if ..." doesn't make sense -- in what way can a set of routes
be needed only under some conditions?  Perhaps it should be "A set of
... routes", if the meaning is that in some situations only one would
be needed.  Reading this again, I think you mean "Multiple Ethernet
A-D per ES routes will need to be advertised if the number of Route
Targets needed to carry the EVIs exceeds the limit on a single route."

   The
   ESI for the Ethernet A-D per ES route is set to zero to indicate
   single-homed sites.

This sentence seems to be talking about some attribute of a route
(which is an operation in the control plane) while the section is
theoretically talking about BUM traffic (which is in the data plane).
This seems to be a general organizational problem, where the details
of the data plane operations are mixed with general descriptions of
the control plane operations needed to support the data plane
operations.  It would be clearer if the data plane specifications and
the control plane specifications were separated (e.g., into adjacent
paragraphs), making it more explicit what information is passed from
the control plane to the data plane.

3.2.3 BUM traffic originated from a multi-homed site on a leaf AC

The first paragraph introduces various matters that aren't discussed
in the rest of the document, or at least aren't much discussed.  If I
understand it right, these considerations don't introduce anything
unexpected other than that an AC which is multi-homed (i.e., connects
to more than one PE) must, for any single EVI, be consistently a Root
or a Leaf on all of those PEs.  If I'm correct, this paragraph could
be made much easier to understand by stating just that and avoiding
details.

However, there may be more involved than that.  E.g., "there is no
forwarding among subnets" may be an additional requirement.  It's hard
to tell, because there are only two occurrences of "forwarding among
subnets", and it's not at all clear what that term is intended to
cover.

3.2.4 BUM traffic originated from a multi-homed site on a root AC

I think the critical point of this paragraph is omitted: "... but no
Leaf label is added".  Compare with section 3.2.2.

3.3 E-TREE Traffic Flows for EVPN

        - Ethernet known unicast from Root to Roots & Leaf
        - Ethernet known unicast from Leaf to Root
        - Ethernet BUM traffic from Root to Roots & Leafs
        - Ethernet BUM traffic from Leaf to Roots

The grammar of these is not good.  I think you mean "Known unicast
Ethernet from ... to ...", or better "Known unicast traffic from
... to ...".

   In the case where unicast flows need not be supported,
   the L2VPN PEs can avoid performing any MAC learning function. 

I think you want s/unicast/known unicast/ -- there may be situations
where unicast traffic exists, and it could be handled as known unicast
traffic, but the implementation can tolerate handling all of it as
unknown traffic to avoid MAC learning.

OTOH, the choice of supporting scenario 3 requires the choice of MAC
learning, since scenario 3 prevents handling should-be-known unicast
traffic as BUM traffic.  That dependency should be noted somewhere.

3.3.1 E-Tree with MAC Learning

I see here much use of "Ethernet Segments".  It seems that it has the
same functional meaning as "ACs".  If so, only one term should be used
consistently.  If not, does the distinction need to be explained?

   For the scenario
   described in section 2.1 (or possibly section 2.2), these routes are
   imported only by PEs with at least one Root site in the EVI ...

What is the condition on "possibly in section 2.2"?  (Is this a
distinction between alternatives A and B?)

   To support multicast/broadcast from Leaf to Root sites, ingress
   replication should be sufficient for most scenarios where there are
   only a few Roots (typically two).

This is introducing one of a pair of alternatives (the other one being
described in the following paragraphs).  I think the reader should be
warned in advance what the two alternatives are and what it depends on
(viz., the number of Roots).  That is, a top-down structure.

   If the number of Roots is large, P2MP tunnels originated at the PEs
   with Leaf sites may be used and thus there will be no need to use the
   modified PMSI tunnel attribute in section 5.2 for composite tunnel
   type.

The wording here is not quite right; I think it allows some ambiguity.
Perhaps

   If the number of Roots is large, P2MP tunnels originated at the PEs
   with Leaf sites may be used (and thus there will be no need to use
   the composite tunnel type values of the modified PMSI tunnel
   attribute in section 5.2).

3.3.2 E-Tree without MAC Learning

Similarly, I suggest

   Just as in the previous section, if the number of PEs with root
   sites are only a few and thus ingress replication is desired from
   leaf PEs to these root PEs, then the composite tunnel values
   defined in section 5.2 should be used.

4 Operation for PBB-EVPN

   In PBB-EVPN, the PE advertises a Root/Leaf indication along with each
   B-MAC Advertisement route, to indicate whether the associated B-MAC
   address corresponds to a Root or a Leaf site. Just like the EVPN
   case, the new E-TREE Extended Community defined in section [5.1] is
   advertised with each MAC Advertisement route.

I don't understand the distinctions here, but is "MAC Advertisement
route" correct?  There are two uses of "MAC" and 12 uses of "B-MAC" in
this section.

4.1 Known Unicast Traffic

   The ingress PE cross-checks this flag with the status of
   the originating site, and if both are a Leaf, then the packet is not
   forwarded.

I think this can be simplified to

   The ingress PE also checks the status of the originating site, and
   if both are a Leaf, then the packet is not forwarded.

4.2 BUM Traffic

   it updates its egress filtering (based on the
   source B-MAC address), as follows:

The stated algorithm has some important properties.  One is that if a
frame arrives, but its B-MAC address is unknown, then the frame is
forwarded.  That is, traffic not from a known Leaf is assumed to be
from a Root.  This may not be a problem, but it seems like it is an
important property of this specification, and the implementor should
be aware of it.  (OTOH, perhaps this is a generic property of
PBB-EVPN, in which case it need not be stated here.)

Another property is that if a B-MAC changes from being a Leaf to being
a Root (by whatever means that might happen), it seems that the new
advertisements of the B-MAC as a Root will *not* remove it from the
list of blocked B-MACs of any Leaf that has seen that B-MAC advertised
as a Leaf.  Unless there is some consideration that I'm not aware of,
I think you want to revise this algorithm in this regard.

4.3 E-Tree without MAC Learning

   For PBB-EVPN, the handling of such traffic is per
   section 4.2 without C-MAC learning part of it at both ingress and
   egress PEs.  

This could be phrased better.  And is the "non-C-MAC learning" mode of
operation of PBB-EVPN defined in the PBB-EVPN specification?  If not,
I think you might need to describe it in more detail here.

5.1 E-Tree Extended Community

   It is used for leaf indication of known unicast and BUM
   traffic.    

It's probably worth specifying that it indicates that the frame's
*origin* is a Leaf.

   The label value is encoded in the high-order 20 bits of the
   Leaf Label field.

This sentence seems to be in the wrong place, since the case described
in this paragraph doesn't use the Label Value field.  It seems to me
that it would be better to incorporate this information into the value
layout:

        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       | Type=0x06     | Sub-Type=0x05 | Flags(1 Octet)|  Reserved=0   |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |  Reserved=0   |           Leaf Label                  |0 0 0 0|
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

5.2 PMSI Tunnel Attribute

   Composite tunnel type is advertised by the root
   PE to simultaneously indicate a non-ingress replication tunnel ...

There's a certain ambiguity here, as I first read it as "... a
(non-ingress) replication tunnel ..." -- but of course, there is no
"egress replication".  What is meant is "... a non-(ingress
replication) tunnel ...", which I think would be better expressed as
"... a non-ingress-replication tunnel ...".

   When this Composite Tunnel bit is set, the "tunnel identifier" field
   would begin with a three-octet label, followed by the actual tunnel
   identifier for the transmit tunnel.

Probably better s/would begin/begins/.  (The clause of the condition
"Composite Tunnel bit is set" does not use the subjunctive mood, so
you don't use the subjunctive mood in the consequent clause.)

It might help to add a figure

         +---------------------------------+
         |  Flags (1 octet)                |
         +---------------------------------+
         |  Tunnel Type (1 octet)          |
         +---------------------------------+
         |  P2MP MPLS Label (3 octets)     |
         +---------------------------------+
         |  Ingress Replication MPLS Label |
         |  (3 octets)                     |
         +---------------------------------+
         |  Tunnel Identifier (variable)   |
         +---------------------------------+

And s/1 octets/1 octet/ -- even though RFC 6514 makes that mistake!

   PEs that don't understand the
   new meaning of the high-order bit would treat the tunnel type as an
   undefined tunnel type and would treat the PMSI tunnel attribute as a
   malformed attribute [RFC6514].

It might be worth noting that this processing is why the composite
tunnel bit is allocated in the Tunnel Type field rather than the Flags
field.

8.1 Considerations for PMSI Tunnel Types

   The registry is to be updated, by removing the entries for 0xFB-0xFE
   and 0x0F, and replacing them by:

   Value          Meaning                            Reference
   0x0B-0x7A      Unassigned
   0x7B-0x7E      Reserved for Experimental Use      this document
   0x7F           Reserved                           this document
   0x80-0xFF      Reserved for Composite Tunnels     this document

   The allocation policy for values 0x00 to 0x7A is IETF Review
   [RFC5226]. The range for experimental use is now 0x7B-0x7E, and value
   in this range are not to be assigned. The status of 0x7F may only be
   changed through Standards Action [RFC5226].  

This structure allows the high-order bit to modify the interpretation
of the other bits.  However, section 5.2 says, "... the high-order bit
of the tunnel type field (Composite Tunnel bit) is set while the
remaining low-order seven bits indicate the tunnel type as before."

I think what you intended is to change the "P-Multicast Service
Interface Tunnel (PMSI Tunnel) Tunnel Types" registry to only specify
the low-order seven bits of the Tunnel Type field, with the high-order
bit of Tunnel Type being the Composite Tunnel bit.  Conceptualized
that way, the registry changes to:

   Value          Meaning                            Reference
   0x00-0x7A      (as before)
   0x7B-0x7E      Reserved for Experimental Use      this document
   0x7F           Reserved                           this document

This implies that the octet values 0x80 to 0xFF are subdivided into
assigned, unassigned, experimental, and reserved groups in the
parallel way.

9.1  Normative References

   [MEF6.1] Metro Ethernet Forum, "Ethernet Services Definitions - Phase
   2", MEF 6.1, April 2008.

Can we get a URL for this?

[EOF]



From nobody Mon Aug  7 23:15:45 2017
Return-Path: <dromasca@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 47FA412420B; Mon,  7 Aug 2017 23:15:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dan Romascanu <dromasca@gmail.com>
To: <ops-dir@ietf.org>
Cc: slim@ietf.org, draft-ietf-slim-multilangcontent.all@ietf.org, ietf@ietf.org, dromasca@gmail.com
Subject: Opsdir last call review of draft-ietf-slim-multilangcontent-11
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150217294315.12399.13728808737116015156@ietfa.amsl.com>
Date: Mon, 07 Aug 2017 23:15:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QB94Xc4SSYqdJyhnToSV7-hkb60>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 08 Aug 2017 06:15:43 -0000

Reviewer: Dan Romascanu
Review result: Ready

Ready.

This document extends MIME with the capability of supporting sending  one
message that contains multiple language versions of the same information.
Translations are identified by a language tag and selected by the email client
based on a user's language settings.

The document belongs to the application space and there are no direct
implications for the operators of networks. An RFC 5706 review does not apply.
The document is Ready from an operational and manageability point of view. Some
information or references about possible errors and how application debugging
is performed in cases of errors would have been useful - I suppose that such
information may be included in other MIME documents.


From nobody Tue Aug  8 08:26:58 2017
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17856132558 for <ietf@ietfa.amsl.com>; Tue,  8 Aug 2017 08:26:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1_gq6woRXCZu for <ietf@ietfa.amsl.com>; Tue,  8 Aug 2017 08:26:55 -0700 (PDT)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61A0E132554 for <ietf@ietf.org>; Tue,  8 Aug 2017 08:26:55 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id y15so16312477lfd.5 for <ietf@ietf.org>; Tue, 08 Aug 2017 08:26:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=RaOJApmZxkmkt/s75TZo1HbVpN11jlbBbWCOHBo4/jM=; b=CTpxXm75eZuf4iPmfbQZ5qbPFXZl71CtmNAhk6S5gqVWjk8BZGp2RVJk9sLqK2sctK GnBp1Cy0aXlfavjo4GSr9BOyoier19gfTk1V/0IamLeL0zw2MXoROIgNR/1RkeWNVJbJ ZTVJZ4gIXwll0RNukfYHF67wBrLjXgKbHSY9k=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=RaOJApmZxkmkt/s75TZo1HbVpN11jlbBbWCOHBo4/jM=; b=WaI+uKGk38l+ezMGL/Zg3xzPKSRtSCJv9K2+i2g1G7Wv0gF6g2kskEJJER6VNXlik2 IV1SH7OCIySFf5V4kiOkBxjoUUZs3lx3k+Nz/rSa4y2tbII5xsQnaqOUpZfM4E6oBVzi vEuxef9rWqKUK06mzlxEgaL0IhGB3dJSi5X2Py9DmWKiXpNj4HeUxElp7VM5SX+2MeKi 0LAPLLPEBu+dnj0fPc0WdIcTqylnXy26w75nhanuL838m/0/t327+QsERFjOiWQEjCq+ ntXnTIXXunsiVbBfirB7UphNUwH/H84UEkBadHFfvc+5/rm9gY1QU0jniVL0iykcsLvo 31MA==
X-Gm-Message-State: AHYfb5j7w9r1eyJ9JJdV//ePl3LYVMvLNMt7zjfqa003P+wwjb6+wJAj v3GSLM+KIz+E8KDW/G8TrZvvxofeqwnW
X-Received: by 10.46.8.17 with SMTP id 17mr1831550lji.103.1502206013668; Tue, 08 Aug 2017 08:26:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.179.75.130 with HTTP; Tue, 8 Aug 2017 08:26:53 -0700 (PDT)
In-Reply-To: <62FDB3A5-C71A-4B5C-8CD9-94B0EE4DC313@gmail.com>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com> <28827.1499886723@dooku.sandelman.ca> <CACZ1GiqmFTzD346x02_gvvFqfm1n-N=xBC01xb0_mEpUa_JYUA@mail.gmail.com> <62FDB3A5-C71A-4B5C-8CD9-94B0EE4DC313@gmail.com>
From: Dave Cridland <dave@cridland.net>
Date: Tue, 8 Aug 2017 16:26:53 +0100
Message-ID: <CAKHUCzy3rzhAHZ3n3KrrLVC6AYG7+obgMJyVA63NfO2=mMU1Wg@mail.gmail.com>
Subject: Re: Need for secured email delegation workflow
To: Yoav Nir <ynir.ietf@gmail.com>
Cc: vaibhav singh <vaibhavsinghacads@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>,  "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/w6as1SM9hHuj3-vWQqK4Moq0a0U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 08 Aug 2017 15:26:57 -0000

On 14 July 2017 at 15:42, Yoav Nir <ynir.ietf@gmail.com> wrote:
> While it may be OK to share a key with my phone (but too difficult to do
> securely in practice), sharing with a delegate is hairy on many different
> layers. But still it=E2=80=99s the same issue.

I think it's all solvable using Proxy Re[en]cryption, but that seems
to be a little fraught with patents at the moment.

Dave.


From nobody Tue Aug  8 08:39:02 2017
Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E38CA13267C; Tue,  8 Aug 2017 08:38:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: ietf@ietf.org
Subject: Announcement IETF 100 Fairmont and Swissotel Rooms Added
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: agenda@ietf.org
Message-ID: <150220673383.12399.5657189075753272491.idtracker@ietfa.amsl.com>
Date: Tue, 08 Aug 2017 08:38:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ylJKtFwtUYHvKlm3q1dIbbQJVeI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 08 Aug 2017 15:38:54 -0000

Hello IETFers,

Great News! Because of the high demand, more rooms have now been added to both the Fairmont and Swissotel hotels. Please note, these rooms may go quick so please also consider our overflows. For all of our hotels information please reference https://www.ietf.org/meeting/100/hotel.html. If you have any questions or concerns please contact agenda@ietf.org. 


Best Regards,
IETF Secretariat


From nobody Tue Aug  8 10:25:08 2017
Return-Path: <vaibhavsinghacads@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AE071324D9 for <ietf@ietfa.amsl.com>; Tue,  8 Aug 2017 10:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k4ZH8Ez_ntf9 for <ietf@ietfa.amsl.com>; Tue,  8 Aug 2017 10:25:04 -0700 (PDT)
Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A15CD13284E for <ietf@ietf.org>; Tue,  8 Aug 2017 10:25:04 -0700 (PDT)
Received: by mail-it0-x22f.google.com with SMTP id 76so7376680ith.0 for <ietf@ietf.org>; Tue, 08 Aug 2017 10:25:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=OOPI9a9lUX+x7R1ngDS0aJ0Amd9O2bUmJCZxbIQ6+80=; b=ikBMLESK+c6l7ODn0ITc6guGnFSWePr4GTBOVeENvv71vdkiMjZ9RICReE1Kdhjb/j ud7hqEnN60Rz6pn2zA3JVVGLKTTQdEOfGktcxhQm/6E6Tr56NzmoDmeK/9FrKd+Pid6s P2BF7qQr0VyAfKBcFjPr3QMbnyvHlrfOZ1weJw8jZAUJIlODNRdlCYdXOF0ySKO+S/WW ZNx8FEoqhFSjKqJBwwY5iicA4QuBLfv5qSbKhy8CDYUlqdcV1DfVzdbuYnU6CfzXQjbl GMAIz5t97LHQiieWmCWVRg4OERkDJ+FXNj1kP6dh8VEL5B5ry8FqWjHGr4vvZ67nDAcU wazg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=OOPI9a9lUX+x7R1ngDS0aJ0Amd9O2bUmJCZxbIQ6+80=; b=N7Kur7EwgWqCeijRgdc2WYYUMLvuU4XFkv+8zRCUcBfrJrSr+OrG5JfWF+N6fRHy7Q kS7M/igBIq54Kd7feZhzChRoyanD5pE762C4ebOnO8OFgGnxACyFHRaEd71iUA7DIJmd ygrdmGnG2LzAqKEBhNAnPntrIjUOxez2JLecEHR7ObukGyqHi06lN1y4imKbTpxo3GUX 5K0UJo1dFhXtrIHG8UAbirdLZUmIhDF/Sg5Ox67wW/TTprdpfi2BiJEZXqaw9EiH18qi pCMoV2OTJyRicyrSIWPyBLPDDt3t/3vzm9eO34uKIlOUNV/AVVgAxv2t0Ki9NjCtTgss 3Xsw==
X-Gm-Message-State: AIVw111BhEA6jgfo/D0p6LQ7EDKyMxKhkqt/n9TjoFDWv1GyP/PedmIs sn/gsMFKxJRAnqjsvJ8l2EdEpnGnqw==
X-Received: by 10.36.135.140 with SMTP id f134mr5001173ite.156.1502213103925;  Tue, 08 Aug 2017 10:25:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.0.208 with HTTP; Tue, 8 Aug 2017 10:25:03 -0700 (PDT)
In-Reply-To: <CAKHUCzy3rzhAHZ3n3KrrLVC6AYG7+obgMJyVA63NfO2=mMU1Wg@mail.gmail.com>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com> <28827.1499886723@dooku.sandelman.ca> <CACZ1GiqmFTzD346x02_gvvFqfm1n-N=xBC01xb0_mEpUa_JYUA@mail.gmail.com> <62FDB3A5-C71A-4B5C-8CD9-94B0EE4DC313@gmail.com> <CAKHUCzy3rzhAHZ3n3KrrLVC6AYG7+obgMJyVA63NfO2=mMU1Wg@mail.gmail.com>
From: vaibhav singh <vaibhavsinghacads@gmail.com>
Date: Tue, 8 Aug 2017 22:55:03 +0530
Message-ID: <CACZ1GioR14iufKQk_9819ZNc1ewuXG9=EhH3nGBTgmgefy9Xsg@mail.gmail.com>
Subject: Re: Need for secured email delegation workflow
To: Dave Cridland <dave@cridland.net>
Cc: Yoav Nir <ynir.ietf@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>, "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c03bb066fc8290556413e21"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wD5BDOpyOdS2k5RRCdjEJs14-Oo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 08 Aug 2017 17:25:07 -0000

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

On Tue, Aug 8, 2017 at 8:56 PM, Dave Cridland <dave@cridland.net> wrote:

> On 14 July 2017 at 15:42, Yoav Nir <ynir.ietf@gmail.com> wrote:
> > While it may be OK to share a key with my phone (but too difficult to d=
o
> > securely in practice), sharing with a delegate is hairy on many differe=
nt
> > layers. But still it=E2=80=99s the same issue.
>
> I think it's all solvable using Proxy Re[en]cryption, but that seems
> to be a little fraught with patents at the moment.
>

I am not comfortable with sharing my private key with anyone, be it the
proxy user itself. I believe that is a requirement for Proxy Reencryption,
please correct me if I may have interpreted it wrongly.

The root problem:



*How will S/MIME work with delegation? *
For sending emails on behalf of the principal/manager:

The delegate will have access to his private key, plus all the receiver's
public keys. Encryption here is trivial, encrypting the mail can be done
only with the delegates' private key. On the other side, the receivers will
be verifying the delegates' signature, and as the delegate is authorized to
act on behalf of his manager, the receivers may not have issues trusting
the delegate. The only thing that has to be ensured here is that there has
to be a provision for all the receivers to know that this delegate is
acting and signing mails on behalf of his manager, as in,
* the list of *all* delegates and managers has to be openly accessible by
any user within the network.*
For receiving mails on behalf of the principal/manager:

Here lies the main issue of* the delegate not able to decrypt any encrypted
messages coming for the Manager. *Reason: The delegate will not have the
manager's private key.

However, given that the list of every manager and delegate is openly
available in the network, what can happen is while creating a message, the
MUA could use the delegate's public key while encrypting the message, or,
in case of multiple delegates for that manager, could generate a one time
use key which could be used to encrypt the message, copy the key n number
of times(where 'n' is the number of delegates), encrypt all new key copies
with the public key of the delegates and bundle them along with the
encrypted message. This is how key-encryption-key (KEK) works while sending
an encrypted S/MIME message to multiple receivers; we can use the same
logic with multiple delegates here.

The only issue here is that I feel the concept of public-private keys is
getting diluted here; when a person is getting a signed mail, he is not
getting the mail from the manager as such, he is getting the mail signed by
his delegate/PA. Similar is the case when creating the mail on the other
side.

The other issue is the MIME could get really big, but then again, most
people would not have multiple delegates/PA.

Atleast, I am not sharing my private key with anyone here. This would
definitely make me sleep better at night.


Regards,
Vaibhav Singh


> Dave.
>

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Tue, Aug 8, 2017 at 8:56 PM, Dave Cridland <span dir=3D"ltr">&lt;<a =
href=3D"mailto:dave@cridland.net" target=3D"_blank">dave@cridland.net</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span=
 class=3D"gmail-">On 14 July 2017 at 15:42, Yoav Nir &lt;<a href=3D"mailto:=
ynir.ietf@gmail.com">ynir.ietf@gmail.com</a>&gt; wrote:<br>
&gt; While it may be OK to share a key with my phone (but too difficult to =
do<br>
&gt; securely in practice), sharing with a delegate is hairy on many differ=
ent<br>
&gt; layers. But still it=E2=80=99s the same issue.<br>
<br>
</span>I think it&#39;s all solvable using Proxy Re[en]cryption, but that s=
eems<br>
to be a little fraught with patents at the moment.<br></blockquote><div><br=
></div><div>I am not comfortable with sharing my private key with anyone, b=
e it the proxy user itself. I believe that is a requirement for Proxy Reenc=
ryption, please correct me if I may have interpreted it wrongly. <br></div>=
<div><br>The root problem: <br><br><strong>How will S/MIME work with delega=
tion? <br><br></strong></div><div>For sending emails on behalf of the princ=
ipal/manager:<br></div><div><br>The delegate will have access to his privat=
e key, plus all the receiver&#39;s public keys. Encryption here is trivial,=
 encrypting the mail can be done only with the delegates&#39; private key. =
On the other side, the receivers will be verifying the delegates&#39; signa=
ture, and as the delegate is authorized to act on behalf of his manager, th=
e receivers may not have issues trusting the delegate. The only thing that =
has to be ensured here is that there has to be a provision for all the rece=
ivers to know that this delegate is acting and signing mails on behalf of h=
is manager, as in,<b> the list of *all* delegates and managers has to be op=
enly accessible by any user within the network.<br></b><br></div><div>For r=
eceiving mails on behalf of the principal/manager:<br></div><div><br>Here l=
ies the main issue of<strong> the delegate not able to decrypt any encrypte=
d messages coming for the Manager. </strong>Reason: The delegate will not h=
ave the manager&#39;s private key.<br><br></div><div>However, given that th=
e list of every manager and delegate is openly available in the network, wh=
at can happen is while creating a message, the MUA could use the delegate&#=
39;s public key while encrypting the message, or, in case of multiple deleg=
ates for that manager, could generate a one time use key which could be use=
d to encrypt the message, copy the key n number of times(where &#39;n&#39; =
is the number of delegates), encrypt all new key copies with the public key=
 of the delegates and bundle them along with the encrypted message. This is=
 how key-encryption-key (KEK) works while sending an encrypted S/MIME messa=
ge to multiple receivers; we can use the same logic with multiple delegates=
 here.<br><br></div><div>The only issue here is that I feel the concept of =
public-private keys is getting diluted here; when a person is getting a sig=
ned mail, he is not getting the mail from the manager as such, he is gettin=
g the mail signed by his delegate/PA. Similar is the case when creating the=
 mail on the other side.<br><br></div><div>The other issue is the MIME coul=
d get really big, but then again, most people would not have multiple deleg=
ates/PA.<br></div><div><br></div><div>Atleast, I am not sharing my private =
key with anyone here. This would definitely make me sleep better at night.<=
br><br></div><div><div class=3D"gmail_signature"><div dir=3D"ltr"><div><br>=
</div>Regards,<div>Vaibhav Singh</div></div></div></div><div><br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex">
<span class=3D"gmail-HOEnZb"><font color=3D"#888888"><br>
Dave.<br>
</font></span></blockquote></div><br><br clear=3D"all"><br></div></div>

--94eb2c03bb066fc8290556413e21--


From nobody Tue Aug  8 11:15:05 2017
Return-Path: <mjethanandani@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 607E8132A65; Tue,  8 Aug 2017 11:14:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mahesh Jethanandani <mjethanandani@gmail.com>
To: <ops-dir@ietf.org>
Cc: draft-ietf-lamps-rfc5280-i18n-update.all@ietf.org, spasm@ietf.org, ietf@ietf.org
Subject: Opsdir last call review of draft-ietf-lamps-rfc5280-i18n-update-02
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150221609128.12407.7360399856163460147@ietfa.amsl.com>
Date: Tue, 08 Aug 2017 11:14:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GEGxJ0yQaC297E8jf-uZUcFFtWU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 08 Aug 2017 18:14:51 -0000

Reviewer: Mahesh Jethanandani
Review result: Ready

I have reviewed this document as part of the Operational directorate’s ongoing
effort to review all IETF documents being processed by the IESG.
 These comments were written with the intent of improving the
operational aspects of the IETF drafts. Comments that are not addressed in last
call may be included in AD reviews during the IESG review.  Document editors
and WG chairs should treat these comments just like any other last
call comments.

Summary:
The document provides updates to RFC 5280 providing clarity on the handling of
Internationalized Domain Names (IDNs) and Internationalized Email Addresses in
X.509 Certificates.

Comments:
The document provides clarifications on the handling of Internationalized
Domain Names (IDNs) and Internationalized Email Addresses in X.509
Certificates. As such it has no operational or management impact.


From nobody Tue Aug  8 12:31:17 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D8F09132445; Tue,  8 Aug 2017 12:31:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-rtcweb-jsep.all@ietf.org, rtcweb@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-ietf-rtcweb-jsep-21
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150222067484.12279.1715829344429803452@ietfa.amsl.com>
Date: Tue, 08 Aug 2017 12:31:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tXDSTtNqT24equLRXTVawGR1v18>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 08 Aug 2017 19:31:15 -0000

Reviewer: Robert Sparks
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-rtcweb-jsep-21
Reviewer: Robert Sparks
Review Date: 2017-08-08
IETF LC End Date: 2017-08-11
IESG Telechat date: Not scheduled for a telechat

Summary: Almost ready for publication as a Proposed Standard RFC, but with
issues that need to be addressed before publishing

Major issues:

The last paragraph of 5.1 needs more context. Why woudn't you expect the
re-offer to fail, given that you already know the peer is using the older
profile strings? It's not clear from the email list and proceedings how the
document ended up with this particular text.

Minor issues:

Second paragraph of 3.2, last sentence: at "these parameters or reject
them" - "these" and "them" have ambiguous antecedents. It's not clear if you
are trying to point to the parameters that don't follow the earlier stated
rule, or all parameters. The sentence is complex. Splitting it up and
finding a way to avoid the need for the semicolon will likely make it
easier to say what you mean.

Last paragraph on page 5 - first sentence: at "One way to mitigate this" -
"this" has an unclear antecedent. Did you mean "One way to reduce the
complexity of the application's responsibilities"?

Last paragraph of 3.5.2.1 - "all of these fields" is ambiguous. Please
state precisely which fields you mean.

Odd edge: The description createAnswer (in 4.1.7) leaves open the
possibility that the application could call createAnswer twice
(back-to-back with no intervening calls to other APIs) with different
values in the options parameter. Is this ok? If not, should there be
language that says not to do that somewhere?

Slightly more than minor maybe: The first paragraph of 5.1.2 has at least a
reference error. UDP/TLS/RTP/SAVPF is not specified in RFC7850. It's in
RFC5764. Assuming that this is only a reference error, then the last
sentence seems like a stray. It doesn't seem to be in the right context
("this advertisement" doesn't cast back to the discussion of the two
profiles above it, which are both UDP only). Please clarify the sentence,
giving it the right context, or remove it.

The fourth sentence of the second bullet of section 5.2.1 is confusing. (It
starts "It is RECOMMENDED that the <sess-id>".) RFC3265 requires the
initial sess-id high-order bit to be zero. As written, this can be read to
say that setting that bit to zero is only RECOMMENDED, and that it's
possible to have sess-ids that are something other than 64 bits. You mean
to say "Do what 3265 says to do and make the lower 63 bits random". Here's
one possible replacement for the sentence: "RFC 3265 requires that the
high-order bit of the initial <sess-id> be zero. It is RECOMMENDED that the
remaining 63 bits be initially set to a cryptographically random value."

The last paragraph of 5.3.1 prohibits the same attributes from generated
answers that are prohibited in generated offers. Consider adding text for
what to do if an offer shows up from a peer with some of those prohibited
attributes.

The second paragraph of section 5.4 is confusing. A slight restructuring of
the sentences would remove much of the potential confusion, I think. I
suggest replacing the first sentence (which is very complex) with this:
"After calling setLocalDescription, the application MAY modify the SDP to
reduce the capabilities in the offer before sending it to the far side, as
long as it remains a valid SDP offer and specifies a subset of what was in
the original offer. Likewise, an application that has received an offer
from a peer MAY modify the received SDP, subject to those same constraints,
before calling setRemoteDescription."

The first paragraph of section 5.7.1 is simply restating requirements from
RFC4566. Restating normative requirements like that has led to interop
problems through unintended introduced ambiguity and spec maintenance
problems. Please consider rewriting the paragraph to say "RFC4566 says" and
avoid the 2119 keywords.

On page 69, at "If the application attempt to transmit DTMF when using a
media format that does not have a corresponding telephone-event format,
this MUST result in an error". This sentence is out-of-place. The section
is about applying a remote description. If the document needs to retain the
sentence, it belongs off in some "processing media" section. In particular,
the current placement of text is confusing about what and when an error
could be returned, and it could be misread to say that an error should be
returned to the setRemoteDescription call.

Nits:

Section 1.2 second paragraph - "This was rejected based on a feeling". Can
you write something that speaks to consensus here? "Based on a feeling"
isn't quite right. Maybe "using the argument"?

PeerConnection is used first at the next to last paragraph of section 3.
Please add a reference at that point.

"LS" (lipsync) is first used at 4.1.2, with no context for what it is.
Please add a reference.

The concept of a "pending local description" is used in sections 3.5.1,
4.1.6, and 4.1.7  but isn't really explained until much later in the
document. Please provide forward references, or move a description of what
a pending description is earlier in the document.

In 4.1.7 (create Answer) why would calling setLocalDescription cause the
answer to be a _pending_ local description. I think it's the full on local
description at that point, not a pending one?

At 4.1.17's first paragraph: Why is "if parsed successfully" necessary to
call out? I suggest removing the phrase.

4.2.3 talks about setting direction properties, but the values that can be
set aren't called out (and even then only by inference from a list in an
example) in section 4.2.5. Should there be explicit pointers to the api doc
here? (And in section 4.2.6?)

There are two paragraphs on page 50 that start "The next step is to". They
are both referring to the same step. I suggest combining the paragraphs.

The 4th bullet on page 64 is ambiguous at "this m= section". It looks like
this bullet should just be merged with the previous bullet.

The second paragraph of 6.8 starts "Next, ". I think it should start
"First, ".

It's not clear what the "Or," in the first bullet on page 65 is referring
to. Are you trying to say "If the m= section is not new, and the ICE ufrag
and password values have changed" or something else?

In the last paragraph of section 8 at "programmer MUST recognize". That is
not an appropriate use of 2119. I suggest "needs to be aware" instead of
"MUST recognize".

Micro Nits:

Suggested change to the first sentence of 1.1

  OLD:

    The thinking behind WebRTC call setup has been to fully specify and
control the media plane, but to leave the signaling plane up to the
application as much as possible.

  New:

    WebRTC call setup has been designed to focus on controlling the media
plane, leaving signaling plane behavior up to the application as much as
possible.

The first full bullet on page 18 has a sentence that starts "Note that when
considering". Please change that to simply "When considering". As written,
there is an implication that this is a consequence of something specified
somewhere else.

The verb "surfaced" appears three times in the document without support or
definition. Can you replace them with simpler language?

At the second to last sub-bullet at the end of page 66, please remove "note
that". The sentence is stronger without it.

I noted these sections as particularly hard to read when going through the
document linearly. I don't have concrete suggestions for improvement, but
perhaps other eyes (if they agree the sections could use improvement) can
come up with something:
 - First sentence of the first paragraph on page 19.
 - 2nd sentence of the 4th paragraph on page 19.



From nobody Tue Aug  8 13:10:39 2017
Return-Path: <rsalz@akamai.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B39591329AF; Tue,  8 Aug 2017 13:10:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Rich Salz <rsalz@akamai.com>
To: <secdir@ietf.org>
Cc: draft-ietf-mmusic-dtls-sdp.all@ietf.org, ietf@ietf.org, mmusic@ietf.org
Subject: Secdir telechat review of draft-ietf-mmusic-dtls-sdp-28
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150222302662.12343.4196075098931297625@ietfa.amsl.com>
Date: Tue, 08 Aug 2017 13:10:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zc6yXQ9dFnIndxfyOrAsHjGBwXM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 08 Aug 2017 20:10:27 -0000

Reviewer: Rich Salz
Review result: Ready

Issues I raised in the -22 review have been addressed, and a quick read showed
nothing new to complain about :)



From nobody Tue Aug  8 13:55:57 2017
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F140A1321CC for <ietf@ietfa.amsl.com>; Tue,  8 Aug 2017 13:55:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.879
X-Spam-Level: 
X-Spam-Status: No, score=-0.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_PHARMACY=1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yvI4VBC9KhP0 for <ietf@ietfa.amsl.com>; Tue,  8 Aug 2017 13:55:53 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0ABD126DD9 for <ietf@ietf.org>; Tue,  8 Aug 2017 13:55:52 -0700 (PDT)
Received: from [10.0.1.63] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v78KsrAZ074014 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 8 Aug 2017 15:54:54 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.63]
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Visiting Singapore/Customs Clearance
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <CABmDk8kWr_NSh_r2JCeVST929UJVXFwPPkxAf9+k6_PBuQmmsw@mail.gmail.com>
Date: Tue, 8 Aug 2017 15:54:52 -0500
Cc: Mike StJohns <mstjohns@comcast.net>, "Gary E. Miller" <gem@rellim.com>, IETF discussion list <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA3C14A5-34AF-457F-B67B-995C3C7BFC08@nostrum.com>
References: <73ae5759-32a7-38fb-3232-9630a4dd6faa@gmail.com> <20170726222602.72dc27ab@spidey.rellim.com> <CABmDk8m3V7dPi-qNn3sig89_keOaepo29_GAyEr+__MjUrLLHA@mail.gmail.com> <4C169449-D1E2-4F9C-8163-CF3B5A067772@comcast.net> <CABmDk8kWr_NSh_r2JCeVST929UJVXFwPPkxAf9+k6_PBuQmmsw@mail.gmail.com>
To: Mary B <mary.h.barnes@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YAi_x7BBNjpLN2SY7CCCk6Fvr58>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 08 Aug 2017 20:55:55 -0000

> On Jul 27, 2017, at 8:49 AM, Mary B <mary.h.barnes@gmail.com> wrote:

[=E2=80=A6]
>=20
>  That page also mentions that Pseudoephedrine has limitations - lots =
of people take that for allergies, but I guess that amount is similar to =
US restrictions for buying at the pharmacy.

The HSA page on personal medications[1] says you need a license to bring =
more than 21.6g of PSE or ephedrine. That should be several times more =
than one needs for personal use (on label use, at least) unless one =
plans to spend considerably more time there than week of the IETF.

=
[1]http://www.hsa.gov.sg/content/hsa/en/Health_Products_Regulation/Consume=
r_Information/Personal_Import_Regulations/bringing_personal_medication_int=
o_Singapore.html

Ben.=


From nobody Tue Aug  8 13:57:20 2017
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48D511321D1 for <ietf@ietfa.amsl.com>; Tue,  8 Aug 2017 13:57:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U9V0bTWlWIFV for <ietf@ietfa.amsl.com>; Tue,  8 Aug 2017 13:57:16 -0700 (PDT)
Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57F601321B9 for <ietf@ietf.org>; Tue,  8 Aug 2017 13:57:16 -0700 (PDT)
Received: by mail-lf0-x22d.google.com with SMTP id g25so20046698lfh.1 for <ietf@ietf.org>; Tue, 08 Aug 2017 13:57:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=HpatHcCKOdLs5LLEKVl4kQqm3mZFi7VRgjEoxNS0ZE8=; b=JlecgZNwYAX90WJh2fVGGGVOfSzBgIaVKSF5FZ62j97Rr8PDlKlsSDB9szdBbFpdDU NtOerPjad0jUzbDFv5qE8aoGMmneIJZpabgc3Be8QHW0WUXfaR9MT2uRDnepHuvupFYm ++MOZbR42PT88zo6qzTDdzHiubbmNj5E/grWw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=HpatHcCKOdLs5LLEKVl4kQqm3mZFi7VRgjEoxNS0ZE8=; b=ZQZx/jJU4PD8/vVwwTPGHZB72sI0sn1wP+/DvUess/H5tsXKZ2Fx3LAJEs+zWe05E4 fEHQUN9cY4zi5l8ouyupaXoDhZyIrQoWmSkZmQEB4jlMlcWTTiXWx58Py9MfX7UBP69n nOoZXSGjqyYENQxNyClpV1JISZUxfglX5IRIXJsS/3k6E8pRTvAg6d9eMqd8mcTVHa3F pyTqAXPZqUGYMz54nFJ5i4swXV+PbhrnjKwjLonamAtswOBmsEigH7epI0UbNEcWdFp1 TPwFYNeoWg7iJ577C35/z6ECXBIUpYrdfAMt6Qok6n1wpYffPEmb4p3LO3Kzp15eXMoP 2YoA==
X-Gm-Message-State: AHYfb5jzjfEzPhV0sae9JcxBRGwwevW/DaZOj9lIhRUzNfHTLMd7zrjN tEgh1wE6UJeQlVi10X6Cxk7KUm3dAnWVuag=
X-Received: by 10.46.32.80 with SMTP id g77mr2350028ljg.55.1502225834657; Tue, 08 Aug 2017 13:57:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.179.75.130 with HTTP; Tue, 8 Aug 2017 13:57:13 -0700 (PDT)
In-Reply-To: <CACZ1GioR14iufKQk_9819ZNc1ewuXG9=EhH3nGBTgmgefy9Xsg@mail.gmail.com>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com> <28827.1499886723@dooku.sandelman.ca> <CACZ1GiqmFTzD346x02_gvvFqfm1n-N=xBC01xb0_mEpUa_JYUA@mail.gmail.com> <62FDB3A5-C71A-4B5C-8CD9-94B0EE4DC313@gmail.com> <CAKHUCzy3rzhAHZ3n3KrrLVC6AYG7+obgMJyVA63NfO2=mMU1Wg@mail.gmail.com> <CACZ1GioR14iufKQk_9819ZNc1ewuXG9=EhH3nGBTgmgefy9Xsg@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
Date: Tue, 8 Aug 2017 21:57:13 +0100
Message-ID: <CAKHUCzxcnapaKyMDMMSD9iusqX3q1ucEGd99uG30adB7CkbvsA@mail.gmail.com>
Subject: Re: Need for secured email delegation workflow
To: vaibhav singh <vaibhavsinghacads@gmail.com>
Cc: Yoav Nir <ynir.ietf@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>, "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/paGMS_DnnKRZSr1YsUZ5Q1Y59wk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 08 Aug 2017 20:57:18 -0000

On 8 August 2017 at 18:25, vaibhav singh <vaibhavsinghacads@gmail.com> wrot=
e:
>
>
> On Tue, Aug 8, 2017 at 8:56 PM, Dave Cridland <dave@cridland.net> wrote:
>>
>> On 14 July 2017 at 15:42, Yoav Nir <ynir.ietf@gmail.com> wrote:
>> > While it may be OK to share a key with my phone (but too difficult to =
do
>> > securely in practice), sharing with a delegate is hairy on many
>> > different
>> > layers. But still it=E2=80=99s the same issue.
>>
>> I think it's all solvable using Proxy Re[en]cryption, but that seems
>> to be a little fraught with patents at the moment.
>
>
> I am not comfortable with sharing my private key with anyone, be it the
> proxy user itself. I believe that is a requirement for Proxy Reencryption=
,
> please correct me if I may have interpreted it wrongly.
>

You have interpreted it incorrectly.

The proxy holds a key that will change a message encrypted to its
proxy key into a message encrypted for an authorized key. It cannot
decrypt the message to plaintext itself.

All quite bleeding edge, all quite patent-encumbered, but look at
Mathew Green's work for details - he's been researching very heavily
in this field.

Dave.


From nobody Tue Aug  8 14:11:50 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D9661325CD; Tue,  8 Aug 2017 14:11:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ja05cenR89oE; Tue,  8 Aug 2017 14:11:39 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 E36241325EB; Tue,  8 Aug 2017 14:11:38 -0700 (PDT)
X-AuditID: c1b4fb3a-81bff70000001b2f-a1-598a2908b63a
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id A8.A2.06959.8092A895; Tue,  8 Aug 2017 23:11:36 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.91]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0352.000; Tue, 8 Aug 2017 23:11:36 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Rich Salz <rsalz@akamai.com>, "secdir@ietf.org" <secdir@ietf.org>
CC: "draft-ietf-mmusic-dtls-sdp.all@ietf.org" <draft-ietf-mmusic-dtls-sdp.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: RE: Secdir telechat review of draft-ietf-mmusic-dtls-sdp-28
Thread-Topic: Secdir telechat review of draft-ietf-mmusic-dtls-sdp-28
Thread-Index: AQHTEIJhHC/9q3fc0USxdaOFO/icVqJ69OJg
Date: Tue, 8 Aug 2017 21:11:36 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4CCB48D9@ESESSMB109.ericsson.se>
References: <150222302662.12343.4196075098931297625@ietfa.amsl.com>
In-Reply-To: <150222302662.12343.4196075098931297625@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupkkeLIzCtJLcpLzFFi42KZGbHdQ5dDsyvS4EmjvsWOuzvYLJ5tnM9i MXX5YxaL/1s6WSw+LHzI4sDqMfnIAmaPJUt+MgUwRXHZpKTmZJalFunbJXBlnFxdWdDFWjH/ yRLGBsYfLF2MnBwSAiYSD7d/ZOpi5OIQEjjCKLHq1zdWCGcRo8T3XRfZuxg5ONgELCS6/2mD NIgIuEps6/3MDFLDLLAQqObsJ0aQhLCAi8SF22eZYIr+bnvKCGEbSWxYeA3MZhFQkVjwdSHY Zl4BX4lzD1aAxYUEnCXu3t3OCmJzAs15snwRWA2jgJjE91NrwGYyC4hL3HoynwniagGJJXvO M0PYohIvH/9jhbCVJBbd/swEcjOzgKbE+l36EK2KElO6H7JDrBWUODnzCcsERtFZSKbOQuiY haRjFpKOBYwsqxhFi1OLi3PTjYz0Uosyk4uL8/P08lJLNjECI+jglt9WOxgPPnc8xCjAwajE w3tmSWekEGtiWXFl7iFGCQ5mJRFeM42uSCHelMTKqtSi/Pii0pzU4kOM0hwsSuK8DvsuRAgJ pCeWpGanphakFsFkmTg4pRoYtR/M5lqew9SXYXpO2cYzNfOMyneOuua0V/q+ffLqpa/FP7PO vfF7Vv22fPna/GV61/cetD9WcWPvL6tVfs+YCha0MXpdv20vtOkQ94+3obPf7BKborZyr2ut u5CDyppoXkvZO/1Tkhc+X7lazlmv0Pn7u5jrp2bJGM2qLbhq1JNxsFK70FlViaU4I9FQi7mo OBEAdNkJaJwCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_qVx5ihTBEEJyUkRyhBOH2iTw0o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 08 Aug 2017 21:11:41 -0000

VGhhbmtzLCBSaWNoISA6KQ0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQotLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLQ0KRnJvbTogUmljaCBTYWx6IFttYWlsdG86cnNhbHpAYWthbWFpLmNvbV0g
DQpTZW50OiAwOCBBdWd1c3QgMjAxNyAyMjoxMA0KVG86IHNlY2RpckBpZXRmLm9yZw0KQ2M6IGRy
YWZ0LWlldGYtbW11c2ljLWR0bHMtc2RwLmFsbEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzsgbW11
c2ljQGlldGYub3JnDQpTdWJqZWN0OiBTZWNkaXIgdGVsZWNoYXQgcmV2aWV3IG9mIGRyYWZ0LWll
dGYtbW11c2ljLWR0bHMtc2RwLTI4DQoNClJldmlld2VyOiBSaWNoIFNhbHoNClJldmlldyByZXN1
bHQ6IFJlYWR5DQoNCklzc3VlcyBJIHJhaXNlZCBpbiB0aGUgLTIyIHJldmlldyBoYXZlIGJlZW4g
YWRkcmVzc2VkLCBhbmQgYSBxdWljayByZWFkIHNob3dlZCBub3RoaW5nIG5ldyB0byBjb21wbGFp
biBhYm91dCA6KQ0KDQoNCg==


From nobody Tue Aug  8 19:45:12 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73C351320A6; Tue,  8 Aug 2017 19:45:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d73XKo6gJJgw; Tue,  8 Aug 2017 19:45:06 -0700 (PDT)
Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 831B912426E; Tue,  8 Aug 2017 19:44:54 -0700 (PDT)
Received: by mail-yw0-x22d.google.com with SMTP id l82so32434220ywc.2; Tue, 08 Aug 2017 19:44:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to:cc; bh=Syn2gSc1UCMWj7rMNNxYnLVxkYwgM0BbUVkQcA+H6Bk=; b=KldqT52TOM3sATMoz2kVwEsq6P71iW63wjn56NEHDOlsDPbGpbMIxCwOYy0Xz+qJSA /zXpDNSZPxBX7nk2k8ntfOUVUKSz091/21Do9UVBEuflrSje3Z8pjo7RW5prcF8QIiSg Rg8VNmGirionsFzVKWU4Nd2WKOMIRnRjKcdk8DF9ykNSD2aL7tyo2Q+19jWc+MaQpsMr uxV2rRKLa4GGQKb5e0QO0xRmtxTeqSP5mxxGZ9+Ugt4DkR0+dn7K+2+dI9MMS1ZEik3u 8yEZYHW1y8hE6elWRbPT5wxVTcpCJKMnXWMppdHZZs02uVMvZzWBa+qON/KbiQjeN0Jt z8VA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=Syn2gSc1UCMWj7rMNNxYnLVxkYwgM0BbUVkQcA+H6Bk=; b=Lx91DGqeyvUeDrtqDVzAgt1crX/yLUjdSrnj7RFZp3Cj29ow59EBNWu0or15pp3SUR eSWO2R/tVide6Mwov0mG5tX05tZ2mUAcUHXGuxZg0T6x6SRabz9g/xh8HIaG7GOH86Dv XhpKT3aRU/sxwuYMlOi2LYmKVxF/0u4PWbLYh7F8hsYTb1jD2R50E9NnFCkP9lGaGQMY q4VSMgCf5VnNqTzNF1bm9pP4jibeE4ilTXj4Z9JINReAaEaYGtAUOcY7Hq0cL78bW4TX cAgUDwEEOT/5qbUHNGi5PXxNXssjazJdgpwHs31vvG1LR6uNU8G23hkXXcYFXnptQaXc fxDw==
X-Gm-Message-State: AHYfb5gfFphIrSwF1DnzJoTEHyErovfzUo0ME0vXLmdqmIxj6Sl8ss1x EeFN08n0hBU25axTnwksOqKpqzBA42zH
X-Received: by 10.37.105.82 with SMTP id e79mr5272196ybc.39.1502246693538; Tue, 08 Aug 2017 19:44:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.52.79 with HTTP; Tue, 8 Aug 2017 19:44:53 -0700 (PDT)
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 8 Aug 2017 21:44:53 -0500
Message-ID: <CAKKJt-cd2-tS=3QnvRcsDKcZ8=o5Z98wUr-=tp8OeP9J1M0M8g@mail.gmail.com>
Subject: BCP 10 Update, adding an IAOC Advisor to the Nominating Committee
To: "ietf@ietf.org" <ietf@ietf.org>
Cc: "iesg@ietf.org" <iesg@ietf.org>, NomCom-Discussion <ietf-nomcom@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c14e02888976b055649101d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_dEmTDRdQoSOO6MvACztywgk8Kw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 02:45:09 -0000

--94eb2c14e02888976b055649101d
Content-Type: text/plain; charset="UTF-8"

Dear all,

At Alissa Cooper's request, I put together a short draft that updates BCP
10, the Nomcom process, adding a reminder that Nomcoms can ask the IAOC to
provide an advisor, and the IAOC can provide one.

Yeah, I thought that was already in BCP 10, but it's not :-) ...

For your reading pleasure, the draft is available at

URL:            https://www.ietf.org/internet-drafts/draft-dawkins-iesg-
nomcom-advisor-iaoc-01.txt
Status:         https://datatracker.ietf.org/doc/draft-dawkins-iesg-nomcom-
advisor-iaoc/
Htmlized:       https://tools.ietf.org/html/draft-dawkins-iesg-nomcom-
advisor-iaoc-01
Htmlized:       https://datatracker.ietf.org/doc/html/draft-dawkins-iesg-
nomcom-advisor-iaoc-01
Diff:           https://www.ietf.org/rfcdiff?url2=draft-dawkins-iesg-
nomcom-advisor-iaoc-01

BUT please send questions and comments to the (public) IETF-Nomcom mailing
list, which is intended for conversations about BCP 10 updates.

If you're not already subscribed to that mailing list, the URL for it is
https://www.ietf.org/mailman/listinfo/ietf-nomcom.

Alexey Melnikov has graciously agreed to AD-sponsor the draft.

Thanks,

Spencer, as an individual

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

<div dir=3D"ltr">Dear all,<div><br></div><div>At Alissa Cooper&#39;s reques=
t, I put together a short draft that updates BCP 10, the Nomcom process, ad=
ding a reminder that Nomcoms can ask the IAOC to provide an advisor, and th=
e IAOC can provide one.=C2=A0</div><div><br></div><div>Yeah, I thought that=
 was already in BCP 10, but it&#39;s not :-) ...</div><div><br></div><div>F=
or your reading pleasure, the draft is available at=C2=A0</div><div><br></d=
iv><div><span style=3D"font-size:12.8px">URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0=C2=A0</span><a href=3D"https://www.ietf.org/internet-drafts/d=
raft-dawkins-iesg-nomcom-advisor-iaoc-01.txt" rel=3D"noreferrer" target=3D"=
_blank" style=3D"font-size:12.8px">https://www.ietf.org/internet-<wbr>draft=
s/draft-dawkins-iesg-<wbr>nomcom-advisor-iaoc-01.txt</a><br style=3D"font-s=
ize:12.8px"><span style=3D"font-size:12.8px">Status:=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0</span><a href=3D"https://datatracker.ietf.org/doc/draft-dawki=
ns-iesg-nomcom-advisor-iaoc/" rel=3D"noreferrer" target=3D"_blank" style=3D=
"font-size:12.8px">https://datatracker.ietf.org/<wbr>doc/draft-dawkins-iesg=
-nomcom-<wbr>advisor-iaoc/</a><br style=3D"font-size:12.8px"><span style=3D=
"font-size:12.8px">Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0</span><a href=3D"ht=
tps://tools.ietf.org/html/draft-dawkins-iesg-nomcom-advisor-iaoc-01" rel=3D=
"noreferrer" target=3D"_blank" style=3D"font-size:12.8px">https://tools.iet=
f.org/html/<wbr>draft-dawkins-iesg-nomcom-<wbr>advisor-iaoc-01</a><br style=
=3D"font-size:12.8px"><span style=3D"font-size:12.8px">Htmlized:=C2=A0 =C2=
=A0 =C2=A0 =C2=A0</span><a href=3D"https://datatracker.ietf.org/doc/html/dr=
aft-dawkins-iesg-nomcom-advisor-iaoc-01" rel=3D"noreferrer" target=3D"_blan=
k" style=3D"font-size:12.8px">https://datatracker.ietf.org/<wbr>doc/html/dr=
aft-dawkins-iesg-<wbr>nomcom-advisor-iaoc-01</a><br style=3D"font-size:12.8=
px"><span style=3D"font-size:12.8px">Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0</span><a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-dawki=
ns-iesg-nomcom-advisor-iaoc-01" rel=3D"noreferrer" target=3D"_blank" style=
=3D"font-size:12.8px">https://www.ietf.org/rfcdiff?<wbr>url2=3Ddraft-dawkin=
s-iesg-<wbr>nomcom-advisor-iaoc-01</a><br></div><div><br></div><div>BUT ple=
ase send questions and comments to the (public) IETF-Nomcom mailing list, w=
hich is intended for conversations about BCP 10 updates.=C2=A0</div><div><b=
r></div><div>If you&#39;re not already subscribed to that mailing list, the=
 URL for it is=C2=A0<a href=3D"https://www.ietf.org/mailman/listinfo/ietf-n=
omcom">https://www.ietf.org/mailman/listinfo/ietf-nomcom</a>.</div><div><br=
></div><div>Alexey Melnikov has graciously agreed to AD-sponsor the draft.<=
/div><div><br></div><div>Thanks,</div><div><br></div><div>Spencer, as an in=
dividual</div></div>

--94eb2c14e02888976b055649101d--


From nobody Wed Aug  9 01:55:17 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FA48126C7A for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 01:55:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nsjy_u6LxYvx for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 01:55:13 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20134.outbound.protection.outlook.com [40.107.2.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1904127869 for <ietf@ietf.org>; Wed,  9 Aug 2017 01:55:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=svc7Epdqr2Uf2Ms+G3mdBrSTS7Cd/mASE6DOhwLlKZQ=; b=VPlBCkiPlJDBtlbhvrywcGZlOkMRpc0HHLjoYbhfSQWNGCjPzV/sI2euloNqf9dH5TPYR6op6QcWJZPTbJZySPMiuWZplJydKhNU6TOnYO9M48WwhBixMZihFR1/9UTsaSp1aOIc1nNSSDLj8UdcKqdhskznNdtNEnptkum1VcU=
Received: from pc6 (86.176.20.38) by VI1PR07MB1567.eurprd07.prod.outlook.com (2a01:111:e400:7a65::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1341.9; Wed, 9 Aug 2017 08:55:10 +0000
Message-ID: <017c01d310ec$90c78f00$4001a8c0@gateway.2wire.net>
From: "tom p." <daedulus@btconnect.com>
To: "IETF" <ietf@ietf.org>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <c9c759cd-2d56-1367-4e42-644b83f46f13@gmail.com>
Subject: In Search of a Revised Notewell
Date: Wed, 9 Aug 2017 09:33:38 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
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: [86.176.20.38]
X-ClientProxiedBy: VI1P194CA0004.EURP194.PROD.OUTLOOK.COM (2603:10a6:800:be::14) To VI1PR07MB1567.eurprd07.prod.outlook.com (2a01:111:e400:7a65::13)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 44143fcb-097f-48ad-94e5-08d4df04574e
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(300000502095)(300135100095)(22001)(2017030254152)(300000503095)(300135400095)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:VI1PR07MB1567; 
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 3:e+Rm2bwOrfjdFRjfe9yrMDNtjFBG/+iuoKX+GyS0tST+dB0F/d6CUQDNNqO5rjjB7QR5yNSe96/5+eKRd7kn3aJlcDE6K4XmNLfffzPDdpdqFNVGGcIgRqkY8ES/Qq5PEEmfe2AhSNnAp7+rrh00atURhONJ0ZF6rauC2LTomiiRyoLGFfYMaJuHv1W79EgXh3iD41NyG+h0KQb7xBRLoutfRMtNqlcXaMSk2laK8XKF9dfMb2I2QGiQFocmBpwr; 25:15t4/TEt5zVFx2ZAC3fXO7/ODjyxKI4n+DPUap6BUXHqarfZcTbvjGAzNI3wTc+cUYQM7MVMjfudfNVWVqSYU+nT4ROw+/5FsYsx5EJ0Cif/Z1kUNIog6sC2psB5OgzUNCnloNrwBSLJS1vqr9mo0gapEE0Q6bE+BBAzMjW5myGR/lpGAUhDF3o94No6oM4WOTN1dcmGg7cEyBdfmUlPcUu7ZuMGzKB+SHGGQQWQWnlU1hzYMnvD00C+3U8BzCVghZL9tUFjaDGBCYDBl6lIF04iINEpotjelQGMJKjjr/oZrjFUjvd+z/Nj5ohy72KODarMb/IRTDyzreA3Iz0cvg==; 31:WCJMHLkNRL6jmR1JqEboy02zjwX6zLNbFoO7JmR3fc9hKy0BIZXbk6iLo7AvuLHnMuYf2ROK6t6d3hgE+8K+W37rrOvkTSxxnQM4KXuZO3qZpuo0S+fK1Uy4sP3FIB0UFRTyyvk/okXv+Rrr4N64IaTuV5I2VnTkeLoRgqCRujEnpKMiGokxnxGgugpIqjdKDTsO3UFVshsW0yzSb+Ib0Fa5bH5CIKMVdx9E10W/qJo=
X-MS-TrafficTypeDiagnostic: VI1PR07MB1567:
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com; 
X-Exchange-Antispam-Report-Test: UriScan:;
X-Microsoft-Antispam-PRVS: <VI1PR07MB156777BE3E8F37157090C2D0C68B0@VI1PR07MB1567.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(100000703101)(100105400095)(93006095)(93001095)(6041248)(20161123564025)(20161123558100)(20161123555025)(20161123560025)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:VI1PR07MB1567; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:VI1PR07MB1567; 
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 4:eBoZJ7lXYRb0E7USZPrnTI7UNlk1IKhRgjDKmG0Hyrwl975fr8DdDHFVcouBhIQ5XeMcOtfBF92p9A1XOqK/JF1mBPCNmm/ANCiPcflcHNF6CwdGRJSs4hPBYSBmxP8TA+ONZwhto19N/jkHSpfiNE82X9bWLtHT/PbADUMc/nDjvldl6c59565oJru8CoD5B7VAIJxpahZo+YZ1AZ12nXKbi+srvqNhj80W1JqXozKnXZcZLmhAaZEpndc0PLDK
X-Forefront-PRVS: 0394259C80
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(7370300001)(6009001)(39450400003)(39860400002)(39400400002)(39410400002)(39850400002)(39840400002)(189002)(199003)(110136004)(6496005)(105586002)(106356001)(38730400002)(53936002)(4720700003)(305945005)(23676002)(6666003)(68736007)(1556002)(61296003)(14496001)(33646002)(81166006)(2906002)(3846002)(84392002)(6116002)(8676002)(42186005)(50466002)(9686003)(6916009)(50226002)(81156014)(7736002)(478600001)(7350300001)(101416001)(97736004)(6486002)(44716002)(25786009)(62236002)(86362001)(230700001)(47776003)(116806002)(66066001)(81816999)(81686999)(189998001)(5660300001)(1456003)(76176999)(50986999)(44736005)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB1567; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:0; LANG:en; 
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtWSTFQUjA3TUIxNTY3OzIzOko1WmZqVWtjaTRiN1RUd0daOGFFWU9WTGJW?= =?utf-8?B?Qnh0cC9WMXFEQW5HNnVlVVYra2tJalFHWWxNczl3VGV5QzdlSE8ydXJrZmUx?= =?utf-8?B?OEkyVmJZT0plaUtlQjEvalI0RWxPQzM0SmpncDVIc3hrTkdJc1prY3NJaFRT?= =?utf-8?B?SDJvaWpNM2ZqRFhZN2JJRFU1UEl6R3dDUFhnRWwwdnozOVlXYk5razUxc2tT?= =?utf-8?B?SkxlUUVUR2FZai9MYWo1MkJlT0xYNGZiRlUxelE4NnpzL0lWWlpiZFhkeHdI?= =?utf-8?B?SU1JaERWUE1YZHB5NmxjdXdEQjd2dHRxajhJa1JuS0FGZldIS29iYmd4aGd5?= =?utf-8?B?bkl4NzZaRXcxblREeW1Ld0tVQTdmWWVmTmJLZ3FwUE83ZU85WFBoVTJCU2Nm?= =?utf-8?B?VWJkM3RtRjZGWGFxSlkzUTlPV1dyNCt6RFNGTUd0UitDK3JwcXd1Z2JlaEVJ?= =?utf-8?B?N3R4NDBiaG1qaS94S2ZIZWtRTlNQYU5iSEprN1U2NVlMRHlXSi9TTzJ3Y3Qx?= =?utf-8?B?UTUxWWwwdDV5eTdqQTBMMjcwekJhU1poR25VaDd1QkxqYnVaWVRzWUN1aWYw?= =?utf-8?B?Qk9OalZvc1UzOWI3YnR3OERXLzFKN2RUUUt5TCs0RUZEZ0tFNU1XMUhuOXdB?= =?utf-8?B?ODlFQjBCa2FaMndIa3pKa01uL3psZ0dNcGZWekkzQ0VHQzh1TWl0eDd2Y1hk?= =?utf-8?B?NlB4NTVFamZOTGlIdU5ZOW1mSTVrNUJIT1dHc0dpWEc1b20xWk5kcVo5dDBj?= =?utf-8?B?YnJVdEFVV3pMWDZ0YkVFZlFCRGNFSW1hVVBRYkRKeC83Ym9yb1dwc2h1aTE4?= =?utf-8?B?YzdxdVlvSXJhMEU2WUlVRC9BckxaNldBL2ptQ1hudGxZek51d3lTSURiYkUw?= =?utf-8?B?WWNhZ044QWtCc1BSMHNXNW5tanM5NjI3dmRCMU82USt1Rm1tbjJEb3VKUDlM?= =?utf-8?B?S1FUVXZOSUE5by81RkFUM3VvNTFCUUNtVlNxajNDMU9PT3E3Z1dDcG9SU1k0?= =?utf-8?B?bHhjQmJoaFd5RFVtZS9wVUYxN0k2ZTROQlcrQURZZUtialhSaGRjRlpKTkZw?= =?utf-8?B?U0ZzQWxiME1waUpHektQbVNjK2VXUXA5UnRQKzZWZGs1RXR3cURTOVZCcUtS?= =?utf-8?B?R1JVTkdpSzd1c3c1dHZUS1YyNVhJbXdmaGdPRXk4STY1UkVCd3RNU3JuekQ2?= =?utf-8?B?ZHVkWVdQNmNFc2dHYThLTEswWG15L2RPdG5veTdqWXBSK0ljL0hMOTJvSXdy?= =?utf-8?B?RHhuRGNvZXkrY2p0VnpEdGlvcUhkUFpBcWpXVXlqVzQ1SXpaSXhlbEFqQm52?= =?utf-8?B?TjUwOGJ1MEJVN0xkc2ZpQm9jRnU1SDVhVmpOVFNsQlVsV1Z0dnRtYjNaQkl1?= =?utf-8?B?OGUzK2krdEI1NW5wdVNaa1o1S3R0RzF5elJMY3l6dkdDZ082TVRNNkFCRjht?= =?utf-8?B?UnA3dkk5WCt5ZlpjUWxYTjBtWVZ2eEdZd0UraU9rbTVzRzNmTDRPNTlScHhU?= =?utf-8?B?U0VxMEQ3dEFoS2Q1VUFFNGtQMnd3WmZrSkdiRzNPZGJoWEtWK0JNeGxiM0w2?= =?utf-8?B?ZkgxbytFK0gzblA5WW9UZVUzck1LNlIrbDJucFVQVnIxaTNxTUovUDQ1ZmFE?= =?utf-8?B?eWR0cUJWUUx6UUNtelphSHl5angrdjBCaWFSM2c3TkNlcUtUVnFQd3RPRVEr?= =?utf-8?B?dUo2OUdSYXY0dUdjcEpMU2xZMFB6Umc5c0tGSHZsOUFnTWJLUnNZcnJHSkZN?= =?utf-8?B?Sk1OdUU5eHU1dXdGcHhzUVFjOE9YNGlzcUJLcVV6Wm5DVmg2aFBrVjFUcWNU?= =?utf-8?B?VFBPMG5rc2hQbEFMc0VGMUIwUmZuRStqTVZyeVRjVmticG5rb3FoRzZlU0Qv?= =?utf-8?B?QWxSS3ZqdnhtcTY3NU5rSWljUmVJMUZhOHZZQ0tLQ2kycDVqbFNVZFY0NitK?= =?utf-8?B?dnRsWnJveTlRMUJvMkdRZlJEaUpESVhlakFWaElLdTk5L0VQMndWTndBcjZ3?= =?utf-8?B?ZVBuRWhUYXNEYzNaZjhjSG1NaFBtNkMvQTVOdz09?=
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 6:/G1wfo9UGxB5UcHEJA3a2zGIUmyq9PGkClQNfDrMpmyDBxsMoiyzuZ3ycqZuCVjwhY1XwB5PC5JIIYkcaGlQKfj5WH+Oe9Ga/z/+NXR+GfHS1S3H/Yn6efo2hWlRbXAmoiXEdzi5xpDxxL57UaLkyAVZViW1KGSP+lvSI3ppcJIV5cusJhmSYIypL3sucwanO6FzHj4IooQG0yCaygFkXQLyOxanv2LikbWotEjtc6EzsAENHpkze46G2NEe9vE6ORI17VeWQtdvEgkIbgF31CxEesgvDHxsgkjs7OhpEfKC3+w6Jzhm33qqpx7MBILSSOqesqJ+cLohnCENwYhtUg==; 5:QJNPljqeluALpiRxXKhbG8eUCtCjnM0ERwLQcdjJy6WwPzi5Y1LqBr7sh1s3Y40vc7hEMkbiPVPmxPO73Mk9fiXtgsHVW/JyXKZLiyeYEYYmdSwVO/zPMnkMgR48xPsXl6hlOKeGWzeFvsMvDojnlA==; 24:yH2XdweiiBAyXcFk20/6u9TMDmvRTpYm9ECuQ1HBmLTSY+yqP0opgazsubEHGlYuz0k6sH36TCX0tTaJXm2Hcbr4L29A0qBKB+x36CIeqZY=; 7:XLR5S2MCiLqc0zz7EORDzKf8jGspuRkQ1ENLpqRSAR2abEgKFLleDdGdb16V+RGBgKV3g/U6yBF8KcG97JHJkovU7h+Zg4Rq0+b9waqPzSif3UXXtpAyDsOAcBqYmlWNjpA53fju3IA1/Y/MolzvlBiBvYfR0tbizybzHEGS3ra2rfLmHV4S3qWW/QCL2uxvcKwoTHuYBv8JUxBBuAQ5RrttN9EVqaWlaScTUYNO+XA=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 09 Aug 2017 08:55:10.1838 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB1567
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KLCesL5OkjXfIm1ftPrChSPBBEo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 08:55:15 -0000

As the minutes trickle out for IETF99, I see repeated references to a
revised Notewell, one of which asks us to read RFC8127.

Looking at the RFC Editor's FTP site, I find a gap between RFC8126 and
RFC8128.

Looking at the RFCINDEX thereon, I see a similar gap.

Searching the announcement list for RFC 8127, I get no matches.

Clearly the WG Chairs have been given a briefing but is this something
that those of us who only contribute via e-mail should be aware of? If
so, how?  I cannot recall seeing anything on WG lists about this, until
I started reading the minutes, since January 2016.

Tom Petch


From nobody Wed Aug  9 04:45:54 2017
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CB8D132143 for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 04:45:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j5OBZz1JZ4aW for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 04:45:51 -0700 (PDT)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4369E131D32 for <ietf@ietf.org>; Wed,  9 Aug 2017 04:45:51 -0700 (PDT)
Received: by mail-oi0-x230.google.com with SMTP id f11so43730740oic.0 for <ietf@ietf.org>; Wed, 09 Aug 2017 04:45:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=PsV4NJoi63qGgn4nigkrUjfZrfplXqKOSB1UbdUBmoo=; b=d5ZiCJPT5qg8aNqqxv8ERA2BBkq1IbJsQGZTD95YpUD+TGfSJdcC7ig3NeefMMIHii dTaxq/VQxUsM/pgifmcHAQqU/wVIdqLP76VzT+w5rBSQ2UDRbhk1bwuIffEaeCFSuNw2 0DsxW6DC7R4D72zpasMPIec4gCTBxFmADnxLvXNa4Q9DZabAeTld2RTCGGHA/SiZyLwh yztODtNpE38dHPBA8jBzH7XhU3pNdJ2Rge6k79uVmTYh6SS4UZHemS2w4DFBAXenyAgW 99YekCK++ahVgMRW+zjICN8iOftvP55izEg6k+FrqWcaTWQFHaNq5ukVc9oxHew81QhI 8TiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=PsV4NJoi63qGgn4nigkrUjfZrfplXqKOSB1UbdUBmoo=; b=thUkeBdhqnOAtgqQ6P4v3g4SNPCEONx45OypQTx3wzmMpzAzSv7GP+TqqGxgrY0CXe /HZVVgPgXT1pLTEmXDKAEbpqTv73SOZO1TciDX2GyKSEWe9DaNK40Epl7earyOiGcEs9 eUF9IQ0BsQHiWn3T7a5CyfgUkNbhsJwS09q5DhXpc2VPmUpbSu4j2qCGSI/ytaQ0Jm9l 2Qg+dCV/LUHSvx01LxDb91CFONEIJvY61NrdZT2l3hrXSR6+ztX5s58MKpf2VY5Z6T6q eCDqg/kVDW/R/yQ96zmsDhLEu9f46W6J97YSX+SUUwaJOqW7TjtqpAed2B2fTUyy2Fah Erdw==
X-Gm-Message-State: AHYfb5isMNI4qHN/BwZCFJ81PSvd3hbFBqFblVE+Sx0VDYk4bCcd9Fkt ex9dWx6CzPngaIJzJlYWOaQC06KTHg==
X-Received: by 10.202.213.79 with SMTP id m76mr7791782oig.54.1502279150641; Wed, 09 Aug 2017 04:45:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.232.34 with HTTP; Wed, 9 Aug 2017 04:45:30 -0700 (PDT)
In-Reply-To: <017c01d310ec$90c78f00$4001a8c0@gateway.2wire.net>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <c9c759cd-2d56-1367-4e42-644b83f46f13@gmail.com> <017c01d310ec$90c78f00$4001a8c0@gateway.2wire.net>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 9 Aug 2017 07:45:30 -0400
Message-ID: <CAA=duU3nvgfEvmCcXOgNvdfyMg0zC7xXmRtYG9DFZPc_Qt2cCA@mail.gmail.com>
Subject: Re: In Search of a Revised Notewell
To: "tom p." <daedulus@btconnect.com>
Cc: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113acab220a7460556509f3e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/T9Hh7fUb21n3aZEPWk8zkKQjJ4w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 11:45:53 -0000

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

Tom,

The revised Note Well references 8179, not 8127. See
https://www.ietf.org/about/note-well.html , which is where I lifted the
Note Well text for my chairs slides.

Cheers,
Andy


On Wed, Aug 9, 2017 at 4:33 AM, tom p. <daedulus@btconnect.com> wrote:

> As the minutes trickle out for IETF99, I see repeated references to a
> revised Notewell, one of which asks us to read RFC8127.
>
> Looking at the RFC Editor's FTP site, I find a gap between RFC8126 and
> RFC8128.
>
> Looking at the RFCINDEX thereon, I see a similar gap.
>
> Searching the announcement list for RFC 8127, I get no matches.
>
> Clearly the WG Chairs have been given a briefing but is this something
> that those of us who only contribute via e-mail should be aware of? If
> so, how?  I cannot recall seeing anything on WG lists about this, until
> I started reading the minutes, since January 2016.
>
> Tom Petch
>
>

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

<div dir=3D"ltr">Tom,<div><br></div><div>The revised Note Well references 8=
179, not 8127. See=C2=A0<a href=3D"https://www.ietf.org/about/note-well.htm=
l">https://www.ietf.org/about/note-well.html</a> , which is where I lifted =
the Note Well text for my chairs slides.</div><div><br></div><div>Cheers,</=
div><div>Andy</div><div><br></div></div><div class=3D"gmail_extra"><br><div=
 class=3D"gmail_quote">On Wed, Aug 9, 2017 at 4:33 AM, tom p. <span dir=3D"=
ltr">&lt;<a href=3D"mailto:daedulus@btconnect.com" target=3D"_blank">daedul=
us@btconnect.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">As=
 the minutes trickle out for IETF99, I see repeated references to a<br>
revised Notewell, one of which asks us to read RFC8127.<br>
<br>
Looking at the RFC Editor&#39;s FTP site, I find a gap between RFC8126 and<=
br>
RFC8128.<br>
<br>
Looking at the RFCINDEX thereon, I see a similar gap.<br>
<br>
Searching the announcement list for RFC 8127, I get no matches.<br>
<br>
Clearly the WG Chairs have been given a briefing but is this something<br>
that those of us who only contribute via e-mail should be aware of? If<br>
so, how?=C2=A0 I cannot recall seeing anything on WG lists about this, unti=
l<br>
I started reading the minutes, since January 2016.<br>
<br>
Tom Petch<br>
<br>
</blockquote></div><br></div>

--001a113acab220a7460556509f3e--


From nobody Wed Aug  9 04:51:02 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A23D413218E for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 04:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lFH03dnlAB1v for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 04:50:58 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B17AE13218C for <ietf@ietf.org>; Wed,  9 Aug 2017 04:50:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 1436F300546 for <ietf@ietf.org>; Wed,  9 Aug 2017 07:50:58 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 4_TIiJN0KPI0 for <ietf@ietf.org>; Wed,  9 Aug 2017 07:50:56 -0400 (EDT)
Received: from [192.168.1.9] (75-139-107-240.dhcp.mant.nc.charter.com [75.139.107.240]) by mail.smeinc.net (Postfix) with ESMTPSA id B4C5030040B; Wed,  9 Aug 2017 07:50:56 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_7FAE506E-509A-4ABF-A794-B02040E9688A"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: In Search of a Revised Notewell
From: Russ Housley <housley@vigilsec.com>
X-Priority: 3
In-Reply-To: <017c01d310ec$90c78f00$4001a8c0@gateway.2wire.net>
Date: Wed, 9 Aug 2017 07:50:55 -0400
Cc: IETF <ietf@ietf.org>
Message-Id: <6975376A-4D11-41D4-983E-19ABF0D6BA65@vigilsec.com>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <c9c759cd-2d56-1367-4e42-644b83f46f13@gmail.com> <017c01d310ec$90c78f00$4001a8c0@gateway.2wire.net>
To: "tom p." <daedulus@btconnect.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FbxaEaUc92fONuQnNjmdUEHtUCQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 11:51:01 -0000

--Apple-Mail=_7FAE506E-509A-4ABF-A794-B02040E9688A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

https://www.ietf.org/about/note-well.html =
<https://www.ietf.org/about/note-well.html>


> On Aug 9, 2017, at 4:33 AM, tom p. <daedulus@btconnect.com> wrote:
>=20
> As the minutes trickle out for IETF99, I see repeated references to a
> revised Notewell, one of which asks us to read RFC8127.
>=20
> Looking at the RFC Editor's FTP site, I find a gap between RFC8126 and
> RFC8128.
>=20
> Looking at the RFCINDEX thereon, I see a similar gap.
>=20
> Searching the announcement list for RFC 8127, I get no matches.
>=20
> Clearly the WG Chairs have been given a briefing but is this something
> that those of us who only contribute via e-mail should be aware of? If
> so, how?  I cannot recall seeing anything on WG lists about this, =
until
> I started reading the minutes, since January 2016.
>=20
> Tom Petch
>=20


--Apple-Mail=_7FAE506E-509A-4ABF-A794-B02040E9688A
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;" =
class=3D""><a href=3D"https://www.ietf.org/about/note-well.html" =
class=3D"">https://www.ietf.org/about/note-well.html</a><div =
class=3D""><br class=3D""></div><div class=3D""><br class=3D""><div =
style=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Aug =
9, 2017, at 4:33 AM, tom p. &lt;<a href=3D"mailto:daedulus@btconnect.com" =
class=3D"">daedulus@btconnect.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">As =
the minutes trickle out for IETF99, I see repeated references to a<br =
class=3D"">revised Notewell, one of which asks us to read RFC8127.<br =
class=3D""><br class=3D"">Looking at the RFC Editor's FTP site, I find a =
gap between RFC8126 and<br class=3D"">RFC8128.<br class=3D""><br =
class=3D"">Looking at the RFCINDEX thereon, I see a similar gap.<br =
class=3D""><br class=3D"">Searching the announcement list for RFC 8127, =
I get no matches.<br class=3D""><br class=3D"">Clearly the WG Chairs =
have been given a briefing but is this something<br class=3D"">that =
those of us who only contribute via e-mail should be aware of? If<br =
class=3D"">so, how? &nbsp;I cannot recall seeing anything on WG lists =
about this, until<br class=3D"">I started reading the minutes, since =
January 2016.<br class=3D""><br class=3D"">Tom Petch<br class=3D""><br =
class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_7FAE506E-509A-4ABF-A794-B02040E9688A--


From nobody Wed Aug  9 06:00:08 2017
Return-Path: <lee@asgard.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96CC81321B7 for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 06:00:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.399
X-Spam-Level: 
X-Spam-Status: No, score=-5.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L_T-retlC-gH for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 06:00:04 -0700 (PDT)
Received: from atl4mhob14.registeredsite.com (atl4mhob14.registeredsite.com [209.17.115.52]) (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 F3B2E1321D2 for <ietf@ietf.org>; Wed,  9 Aug 2017 06:00:03 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.204]) by atl4mhob14.registeredsite.com (8.14.4/8.14.4) with ESMTP id v79D01up008132 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Wed, 9 Aug 2017 09:00:01 -0400
Received: (qmail 26627 invoked by uid 0); 9 Aug 2017 13:00:01 -0000
X-TCPREMOTEIP: 68.100.68.25
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.1.160?) (lee@asgard.org@68.100.68.25) by 0 with ESMTPA; 9 Aug 2017 13:00:00 -0000
User-Agent: Microsoft-MacOutlook/14.7.2.170228
Date: Wed, 09 Aug 2017 08:59:59 -0400
Subject: Re: In Search of a Revised Notewell
From: Lee Howard <lee@asgard.org>
To: "tom p." <daedulus@btconnect.com>, IETF <ietf@ietf.org>
Message-ID: <D5B07EA1.7F830%lee@asgard.org>
Thread-Topic: In Search of a Revised Notewell
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <c9c759cd-2d56-1367-4e42-644b83f46f13@gmail.com> <017c01d310ec$90c78f00$4001a8c0@gateway.2wire.net>
In-Reply-To: <017c01d310ec$90c78f00$4001a8c0@gateway.2wire.net>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GHtBcKBD7UCl9AAWoleWCX9YRok>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 13:00:06 -0000

On 8/9/17, 4:33 AM, "ietf on behalf of tom p." <ietf-bounces@ietf.org on
behalf of daedulus@btconnect.com> wrote:

>
>
>Clearly the WG Chairs have been given a briefing but is this something
>that those of us who only contribute via e-mail should be aware of? If
>so, how?  I cannot recall seeing anything on WG lists about this, until
>I started reading the minutes, since January 2016.

I recall seeing an announcement from Scott Bradner that certain IPR rules
had been updated. I don=E2=80=99t remember seeing a broad community announcement
with the banner, =E2=80=9CThe Note Well advisory has changed.=E2=80=9D

https://www.ietf.org/about/note-well.html

I presume that the new version was used in meeting registration.

Lee

>
>Tom Petch
>
>



From nobody Wed Aug  9 08:14:38 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2543A132055 for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 08:14:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rsP_xFd5zLtG for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 08:14:30 -0700 (PDT)
Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35451126BF3 for <ietf@ietf.org>; Wed,  9 Aug 2017 08:14:30 -0700 (PDT)
Received: by mail-yw0-x229.google.com with SMTP id l82so41755375ywc.2 for <ietf@ietf.org>; Wed, 09 Aug 2017 08:14:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=n4C/ocZ5ZafgqbEQlCCQs3JIontxFqj1R+XmnIFGs5w=; b=srdviC8Dcv477G6QYjGhfnXCLTNE7W8v2Q9qnqaxXo5r45ZjNGSXeVvQ56e4UvrW3G TbgTgvXlkpFKGBD2mqa+qwtEF/si1lN6c5UnFhdmQzXyygys3/xSPYWEj6Stere+Vk6y t65ayYHIYDlhAscPR+/CMEc6wYfWq26fKVA/W2qbxNIfB/5T6N+Id4lMd/ylXRK2A7xc E3p4QtE3pd6RihSAOpps0of5DPZJfKFAjPkd7zGB7foNMdRPO1pGQX+SblpXq/wPWhdf xbTZT12A1Tk695kP6oBQpVlE1wI3t5fZX0uDaxlEbCGJYRVG9+Ogo2yl0HXY6yxkbAZd GzZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=n4C/ocZ5ZafgqbEQlCCQs3JIontxFqj1R+XmnIFGs5w=; b=MqTDxiebWkueUQ9b7aZ941Bv8rijGEUOvP8KZ8oJ/IR5PRBpK0ptf6O+0ve9Eo5jj+ pGE9K05hmpqcDMRvRmCuGtXDxQmQRs5LnY/cSGhQjIwnkPuHMsDWY0sg6HQnrm7BZSpp +irKF9unvDVFJXySo/XK3i/X9baQVIrNHnLc20xBr3ZyBxdG1MhODXIkKxvwDB+4i+2O QF7Ou3o4nOc0mJ4vUwb61dAoyO48rt10cy3NYY8rar+XWaof2HgVqEQW0vO7KlXyI6+b PMzLjBk3H3KDS76DWL5/oCZn39+PEt21vHsbcpwrfJy4WswiTS286PdJ/o5K554j4kmb YzoQ==
X-Gm-Message-State: AHYfb5h9wNWVvx1lLwpTcK7RGC+OFGWsJ09ZRK2brDmjinH5sOK8Wg1l Esoh1VAOOYVklfNAtwVo4N5L8RY1Rg==
X-Received: by 10.13.213.148 with SMTP id x142mr6830471ywd.311.1502291669375;  Wed, 09 Aug 2017 08:14:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.52.79 with HTTP; Wed, 9 Aug 2017 08:14:28 -0700 (PDT)
In-Reply-To: <D5B07EA1.7F830%lee@asgard.org>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <c9c759cd-2d56-1367-4e42-644b83f46f13@gmail.com> <017c01d310ec$90c78f00$4001a8c0@gateway.2wire.net> <D5B07EA1.7F830%lee@asgard.org>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 9 Aug 2017 10:14:28 -0500
Message-ID: <CAKKJt-cuexnMgnFYxKPX8oRidjCTL5oAZmR+c1UnRT8awG5M5A@mail.gmail.com>
Subject: Re: In Search of a Revised Notewell
To: Lee Howard <lee@asgard.org>
Cc: "tom p." <daedulus@btconnect.com>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a114fa2664d64430556538985"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SZYXG7wdV9yqhqiY__t5Nz6LfQ4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 15:14:37 -0000

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

Under the category of "mistakes were made" ...

On Wed, Aug 9, 2017 at 7:59 AM, Lee Howard <lee@asgard.org> wrote:

>
>
> On 8/9/17, 4:33 AM, "ietf on behalf of tom p." <ietf-bounces@ietf.org on
> behalf of daedulus@btconnect.com> wrote:
>
> >
> >
> >Clearly the WG Chairs have been given a briefing but is this something
> >that those of us who only contribute via e-mail should be aware of? If
> >so, how?  I cannot recall seeing anything on WG lists about this, until
> >I started reading the minutes, since January 2016.
>
> I recall seeing an announcement from Scott Bradner that certain IPR rules
> had been updated. I don=E2=80=99t remember seeing a broad community annou=
ncement
> with the banner, =E2=80=9CThe Note Well advisory has changed.=E2=80=9D
>
> https://www.ietf.org/about/note-well.html
>
> I presume that the new version was used in meeting registration.


I assume so as well, although of course I didn't notice at the time.

True confession - I did the slides for TSVAREA at IETF 99, and didn't think
to change the RFC number on my Note Well slide.

It's not like I didn't know about RFC 8179. According to
https://datatracker.ietf.org/doc/rfc8179/ballot/, I BALLOTED YES WITH
COMMENTS on it. But that didn't translate into me changing my Note Well
slide ... making the change to my IETF 100 slide deck now.

So, Tom, thanks for asking about this, and helping the rest of us catch up.

Spencer, who apparently isn't getting enough caffeine in his diet Pepsi, in
spite of many valiant efforts to do so ...

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

<div dir=3D"ltr">Under the category of &quot;mistakes were made&quot; ...<d=
iv class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Aug 9, 2017=
 at 7:59 AM, Lee Howard <span dir=3D"ltr">&lt;<a href=3D"mailto:lee@asgard.=
org" target=3D"_blank">lee@asgard.org</a>&gt;</span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><br>
<br>
On 8/9/17, 4:33 AM, &quot;ietf on behalf of tom p.&quot; &lt;<a href=3D"mai=
lto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a> on<br>
<span class=3D"gmail-">behalf of <a href=3D"mailto:daedulus@btconnect.com">=
daedulus@btconnect.com</a>&gt; wrote:<br>
<br>
&gt;<br>
&gt;<br>
&gt;Clearly the WG Chairs have been given a briefing but is this something<=
br>
&gt;that those of us who only contribute via e-mail should be aware of? If<=
br>
&gt;so, how?=C2=A0 I cannot recall seeing anything on WG lists about this, =
until<br>
&gt;I started reading the minutes, since January 2016.<br>
<br>
</span>I recall seeing an announcement from Scott Bradner that certain IPR =
rules<br>
had been updated. I don=E2=80=99t remember seeing a broad community announc=
ement<br>
with the banner, =E2=80=9CThe Note Well advisory has changed.=E2=80=9D<br>
<br>
<a href=3D"https://www.ietf.org/about/note-well.html" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/about/<wbr>note-well.html</a><br>
<br>
I presume that the new version was used in meeting registration.</blockquot=
e><div><br></div><div>I assume so as well, although of course I didn&#39;t =
notice at the time.</div><div><br></div><div>True confession - I did the sl=
ides for TSVAREA at IETF 99, and didn&#39;t think to change the RFC number =
on my Note Well slide.=C2=A0</div><div><br></div><div>It&#39;s not like I d=
idn&#39;t know about RFC 8179. According to <a href=3D"https://datatracker.=
ietf.org/doc/rfc8179/ballot/">https://datatracker.ietf.org/doc/rfc8179/ball=
ot/</a>, I BALLOTED YES WITH COMMENTS on it. But that didn&#39;t translate =
into me changing my Note Well slide ...=C2=A0making the change to my IETF 1=
00 slide deck now.</div><div><br></div><div>So, Tom, thanks for asking abou=
t this, and helping the rest of us catch up.</div><div><br></div><div>Spenc=
er, who apparently isn&#39;t getting enough caffeine in his diet Pepsi, in =
spite of many valiant efforts to do so ...</div></div></div></div>

--001a114fa2664d64430556538985--


From nobody Wed Aug  9 08:27:25 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D21E81323C1; Wed,  9 Aug 2017 08:27:08 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id saaDd_M3Y2xH; Wed,  9 Aug 2017 08:27:06 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C69CA1323B3; Wed,  9 Aug 2017 08:27:06 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id EED8920567; Wed,  9 Aug 2017 11:29:20 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 97A8D806BA; Wed,  9 Aug 2017 11:27:05 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "ietf\@ietf.org" <ietf@ietf.org>, NomCom-Discussion <ietf-nomcom@ietf.org>, "iesg\@ietf.org" <iesg@ietf.org>
Subject: Re: BCP 10 Update, adding an IAOC Advisor to the Nominating Committee
In-Reply-To: <CAKKJt-cd2-tS=3QnvRcsDKcZ8=o5Z98wUr-=tp8OeP9J1M0M8g@mail.gmail.com>
References: <CAKKJt-cd2-tS=3QnvRcsDKcZ8=o5Z98wUr-=tp8OeP9J1M0M8g@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.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-sha256; protocol="application/pgp-signature"
Date: Wed, 09 Aug 2017 11:27:05 -0400
Message-ID: <4622.1502292425@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Oh-BOJE7fA8lOnx0kLaNypyA3Dk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 15:27:09 -0000

--=-=-=
Content-Type: text/plain


Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
    > At Alissa Cooper's request, I put together a short draft that updates BCP 10,
    > the Nomcom process, adding a reminder that Nomcoms can ask the IAOC to
    > provide an advisor, and the IAOC can provide one.

The other entities provide liasons, and I see that your document explains why
an advisor is listed.    I understand that the word "advisor" is from BCP10,
and allows the nomcom to add advisors to the nomcom. I'd call this an
"import", because the nomcom pulls someone in.

The other liason are not nomcom decisions, and so there is some subtle distinction.

It's also not clear to be that we want the NOMCOM to ask for an IAOC advisor,
or if we the IAOC appoints someone.  The previous tradition was the IAOC
appointed someone, and they gave us Ole even after he was no longer a seated
IAOC member.

As a voting member and chair, I found the IAOC (liason) very useful in
explaining not only what the IAOC does, but also what the IAB and IESG do not
do, even when sometimes IAOC activities get relayed via IETF Chair or IAB
chair.  Many voting members are ignorant of the IAOC and sometimes look for
characteristics in an IESG or IAB member that would be more appropriate for IAOC.
So I strongly agree with always having an IAOC liason/advisor, even when not
appointing someone directly to the IAOC.

{nomcom: 2002,2012,2013. chair: 2014}

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




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

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

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlmLKckACgkQgItw+93Q
3WWZJQf9Gz/jrxzQ6dQ8R5fdtPkwgSayBM09fqjRKkI0uN+M37xI/uQ+z+g1PPQr
wgi0/X8mtsYm2TjsZZD6Y2QiEFFmUV/bwB+vueetNqo7kiayxYIZqSTs3UjQ4ewe
9nSToM4xUF83Ao5KUXBZgK+LKqVX7ngbOXNm/vspig03S1dM4PPltswmbJPhPiiK
EhTr/XwaCDY9sAWIPwFnfmVCC4iVyq6z3vpSdKDUmwUPsM8EEle6iNI7PU3xQNNb
3RJhPrbp23+LZgEJcLDhGguPGtQGkwRzBy12Pt+9fpN//cv/IdWBHj4kGWfAiG+V
lB630K2ltyxHEz0r4i87XT0BjgdTlQ==
=/SHU
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Aug  9 08:35:57 2017
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B7521323BF for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 08:35:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cX2veEpiCFkz for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 08:35:53 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B561E1323BD for <ietf@ietf.org>; Wed,  9 Aug 2017 08:35:53 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id x3so64884267oia.1 for <ietf@ietf.org>; Wed, 09 Aug 2017 08:35:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=eAvB4DvbWaPAdPhBc6MmUj/bFN0bazFNW+CCkdA3tQ4=; b=bRsGIt5igTCRLh4z8gSGXUFE+HrpEcj5F0tYY+qmUNhSa6guXyk7/6Pg52bUuckfMD VtbaIJd6FIT5J4e8gzWafdJ0FHYyUUZEngGhuwwq7HxxMyQ5B/U+q2U4NKspUtyd5iOb ncNyxQ9i1PjL5s+JsSqCp6QntDzbltuZKSjrHzlr4AWGvs+hZvG86/bAj+qUW7K4T42v IiI0pqSGeiQeIuWwFpbnbRYm06OWnBOrSXLPUkchAGiMD0j5vnrwoiKIhMYy8kpC/X2S ZwcRuGymVlkcu4Hu1FCQgMRbD691czxb1YC9kYydhDpWRx+7av88Yt0WPGhEDSTe4uhu yP4A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=eAvB4DvbWaPAdPhBc6MmUj/bFN0bazFNW+CCkdA3tQ4=; b=iMkZCQUL4aphSlK1yhO6agXiqZGwbVd2gCG93rYfWOMQ2OyR/9Z0P7MIWOvpCaXT7Z ww+l5bn49BAyca3KsipFyZPi3Do1seS+rnxeBO46RH2o4JjL6HaIhEUkEDPC5S4dFvIk Ci21p7zGCedtd8G3Yenm7SIRdV+iuhyMbm1PdNUrevT6oPF4bM9w1x4h2BlJOjR9H9HS 6uz+evk5IcBuhrGobLCLWblpQeJnq42RG5vqGvNVq6R4lQezsqxIe565BlJhV1sVPMOw D0+J82eniyggPMbDUvVBKlr5rkqm6MXrt/2xahuYtrQguzNPJMW7QA1TSV8ReNVQstcL ke8g==
X-Gm-Message-State: AHYfb5jioY67xCVUjmbMaP2R4tINcNoG5/jUJ6GIJuBkWNNZwbW9qMYV /n6H2hDkcA7VycwiBlrv/agR6XlK4Q==
X-Received: by 10.202.8.67 with SMTP id 64mr9250383oii.305.1502292953047; Wed, 09 Aug 2017 08:35:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.232.34 with HTTP; Wed, 9 Aug 2017 08:35:32 -0700 (PDT)
In-Reply-To: <CAKKJt-cuexnMgnFYxKPX8oRidjCTL5oAZmR+c1UnRT8awG5M5A@mail.gmail.com>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <c9c759cd-2d56-1367-4e42-644b83f46f13@gmail.com> <017c01d310ec$90c78f00$4001a8c0@gateway.2wire.net> <D5B07EA1.7F830%lee@asgard.org> <CAKKJt-cuexnMgnFYxKPX8oRidjCTL5oAZmR+c1UnRT8awG5M5A@mail.gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 9 Aug 2017 11:35:32 -0400
Message-ID: <CAA=duU3dGXT50HMGorpzN8Fpyje98DW0A+=s-Pacqk3KfOXaYg@mail.gmail.com>
Subject: Re: In Search of a Revised Notewell
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Lee Howard <lee@asgard.org>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c12e414d0ab50055653d5a0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FUbnm3_YG4clo7-Pqqw5LYK4Y7I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 15:35:56 -0000

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

Spencer,

Before each meeting I always recopy the Note Well text into my chairs
slides, because there just might be a change in the wording, and it=E2=80=
=99s
easier to copy than to check.

Cheers,
Andy

On Wed, Aug 9, 2017 at 11:14 AM, Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:

> Under the category of "mistakes were made" ...
>
> On Wed, Aug 9, 2017 at 7:59 AM, Lee Howard <lee@asgard.org> wrote:
>
>>
>>
>> On 8/9/17, 4:33 AM, "ietf on behalf of tom p." <ietf-bounces@ietf.org on
>> behalf of daedulus@btconnect.com> wrote:
>>
>> >
>> >
>> >Clearly the WG Chairs have been given a briefing but is this something
>> >that those of us who only contribute via e-mail should be aware of? If
>> >so, how?  I cannot recall seeing anything on WG lists about this, until
>> >I started reading the minutes, since January 2016.
>>
>> I recall seeing an announcement from Scott Bradner that certain IPR rule=
s
>> had been updated. I don=E2=80=99t remember seeing a broad community anno=
uncement
>> with the banner, =E2=80=9CThe Note Well advisory has changed.=E2=80=9D
>>
>> https://www.ietf.org/about/note-well.html
>>
>> I presume that the new version was used in meeting registration.
>
>
> I assume so as well, although of course I didn't notice at the time.
>
> True confession - I did the slides for TSVAREA at IETF 99, and didn't
> think to change the RFC number on my Note Well slide.
>
> It's not like I didn't know about RFC 8179. According to
> https://datatracker.ietf.org/doc/rfc8179/ballot/, I BALLOTED YES WITH
> COMMENTS on it. But that didn't translate into me changing my Note Well
> slide ... making the change to my IETF 100 slide deck now.
>
> So, Tom, thanks for asking about this, and helping the rest of us catch u=
p.
>
> Spencer, who apparently isn't getting enough caffeine in his diet Pepsi,
> in spite of many valiant efforts to do so ...
>

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

<div dir=3D"ltr">Spencer,<div><br></div><div>Before each meeting I always r=
ecopy the Note Well text into my chairs slides, because there just might be=
 a change in the wording, and it=E2=80=99s easier to copy than to check.</d=
iv><div><br></div><div>Cheers,</div><div>Andy</div></div><div class=3D"gmai=
l_extra"><br><div class=3D"gmail_quote">On Wed, Aug 9, 2017 at 11:14 AM, Sp=
encer Dawkins at IETF <span dir=3D"ltr">&lt;<a href=3D"mailto:spencerdawkin=
s.ietf@gmail.com" target=3D"_blank">spencerdawkins.ietf@gmail.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"><div dir=3D"ltr">Under the c=
ategory of &quot;mistakes were made&quot; ...<div class=3D"gmail_extra"><br=
><div class=3D"gmail_quote"><span class=3D"">On Wed, Aug 9, 2017 at 7:59 AM=
, Lee Howard <span dir=3D"ltr">&lt;<a href=3D"mailto:lee@asgard.org" target=
=3D"_blank">lee@asgard.org</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><br>
<br>
On 8/9/17, 4:33 AM, &quot;ietf on behalf of tom p.&quot; &lt;<a href=3D"mai=
lto:ietf-bounces@ietf.org" target=3D"_blank">ietf-bounces@ietf.org</a> on<b=
r>
<span class=3D"m_-9161275643101997614gmail-">behalf of <a href=3D"mailto:da=
edulus@btconnect.com" target=3D"_blank">daedulus@btconnect.com</a>&gt; wrot=
e:<br>
<br>
&gt;<br>
&gt;<br>
&gt;Clearly the WG Chairs have been given a briefing but is this something<=
br>
&gt;that those of us who only contribute via e-mail should be aware of? If<=
br>
&gt;so, how?=C2=A0 I cannot recall seeing anything on WG lists about this, =
until<br>
&gt;I started reading the minutes, since January 2016.<br>
<br>
</span>I recall seeing an announcement from Scott Bradner that certain IPR =
rules<br>
had been updated. I don=E2=80=99t remember seeing a broad community announc=
ement<br>
with the banner, =E2=80=9CThe Note Well advisory has changed.=E2=80=9D<br>
<br>
<a href=3D"https://www.ietf.org/about/note-well.html" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/about/not<wbr>e-well.html</a><br>
<br>
I presume that the new version was used in meeting registration.</blockquot=
e><div><br></div></span><div>I assume so as well, although of course I didn=
&#39;t notice at the time.</div><div><br></div><div>True confession - I did=
 the slides for TSVAREA at IETF 99, and didn&#39;t think to change the RFC =
number on my Note Well slide.=C2=A0</div><div><br></div><div>It&#39;s not l=
ike I didn&#39;t know about RFC 8179. According to <a href=3D"https://datat=
racker.ietf.org/doc/rfc8179/ballot/" target=3D"_blank">https://datatracker.=
ietf.org/<wbr>doc/rfc8179/ballot/</a>, I BALLOTED YES WITH COMMENTS on it. =
But that didn&#39;t translate into me changing my Note Well slide ...=C2=A0=
making the change to my IETF 100 slide deck now.</div><div><br></div><div>S=
o, Tom, thanks for asking about this, and helping the rest of us catch up.<=
/div><div><br></div><div>Spencer, who apparently isn&#39;t getting enough c=
affeine in his diet Pepsi, in spite of many valiant efforts to do so ...</d=
iv></div></div></div>
</blockquote></div><br></div>

--94eb2c12e414d0ab50055653d5a0--


From nobody Wed Aug  9 10:01:31 2017
Return-Path: <mersue@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF2A132447 for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 10:01:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EEmNpAQcTC1J for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 10:01:28 -0700 (PDT)
Received: from mail-wr0-x22f.google.com (mail-wr0-x22f.google.com [IPv6:2a00:1450:400c:c0c::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5093E13243B for <ietf@ietf.org>; Wed,  9 Aug 2017 10:01:25 -0700 (PDT)
Received: by mail-wr0-x22f.google.com with SMTP id f21so26207366wrf.5 for <ietf@ietf.org>; Wed, 09 Aug 2017 10:01:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=ITpZUy5v8HBNDYYJcRUpRSm98t7uDVw9zViCGmMYHYc=; b=GqdhrwYjivaPtiYRfuezMuYSoUih3jL7Oj/dPpSnS0U1pCpPJorarEheb5jjPGTBCv N2cZteSRhTr+6UtH5dQPc6wztk/7Lchm3MGO4FpjCU9ndDjMWqc9gpEpz7MsKYESp5IK ANmfyh+QcxsgXFteJ2PN7dbQrVdE1jWPwop8MoxPtQK3NqSEHHhn47YXyh1UN330Fpzj aQt8TBOKZFsPHHCJw67hUZNkl7fcoJiQ3udaUo5yUdwFRkkC3VeO88CzOd2v7PoDx3V0 AyHTbJQZ4aq86M5Ib1bmYQkeKzXuL0G2rQdx93RURjHoj0+OpYjdIuJ/uNkmXwWTKUls OuyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=ITpZUy5v8HBNDYYJcRUpRSm98t7uDVw9zViCGmMYHYc=; b=cwZdw+eC7iVNTvtD2aZxek0D5tCc6DYiLQsyrnG6SpfO7FUil/7NqGivH6olxZwF6Q eh1qBGWMirROY6ss8MC89PyqdpPfZK0idYA1/iI8Jw+2oURbYEuEIXwWyQf9nWozkUgm 1F0N8F1541hMJ88n7WS+Fgi7Ju5VXswdB5Hu0jDcwFl64KpSOnuRAUa8k4FL2bxzWAkd 2HAN8dCMMi8yQqEMnOv8baVn2F8jcU7bT/1xff1REnWXNc5pqUNlPKfl7+Xd2H09lwH/ dwfefm8WWg3Ieo8nyvvwYdttbZnFSJwrcAhaR116GHWKVb1c8DcJf2sd+5drfzqGiDNG Hk+Q==
X-Gm-Message-State: AHYfb5hlGTkf9rKSaQASjI91kzZrq7gIUd8VTwz5aGZQfKguxhwHR5hi 8AffCFi3T8bWrw==
X-Received: by 10.223.164.194 with SMTP id h2mr7706580wrb.137.1502298083706; Wed, 09 Aug 2017 10:01:23 -0700 (PDT)
Received: from DESKTOPFLHJVQJ (p57A773FE.dip0.t-ipconnect.de. [87.167.115.254]) by smtp.gmail.com with ESMTPSA id p68sm17281428wmf.0.2017.08.09.10.01.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Aug 2017 10:01:23 -0700 (PDT)
From: "Mehmet Ersue" <mersue@gmail.com>
To: "'Andrew G. Malis'" <agmalis@gmail.com>, "'Spencer Dawkins at IETF'" <spencerdawkins.ietf@gmail.com>
Cc: "'IETF'" <ietf@ietf.org>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <c9c759cd-2d56-1367-4e42-644b83f46f13@gmail.com> <017c01d310ec$90c78f00$4001a8c0@gateway.2wire.net> <D5B07EA1.7F830%lee@asgard.org> <CAKKJt-cuexnMgnFYxKPX8oRidjCTL5oAZmR+c1UnRT8awG5M5A@mail.gmail.com> <CAA=duU3dGXT50HMGorpzN8Fpyje98DW0A+=s-Pacqk3KfOXaYg@mail.gmail.com>
In-Reply-To: <CAA=duU3dGXT50HMGorpzN8Fpyje98DW0A+=s-Pacqk3KfOXaYg@mail.gmail.com>
Subject: RE: In Search of a Revised Notewell
Date: Wed, 9 Aug 2017 19:01:24 +0200
Message-ID: <00de01d31131$226ec1f0$674c45d0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DF_01D31141.E5FA2A00"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQIWNdbDxqC9a/1J56cKO+MWBeEJUQLLAukzAmrv7S0Bc8T+ggLzeRSMAcqbxSmhmrdPIA==
Content-Language: de
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-c8oCWNq_d3LfmM8jtxzdHW6ERI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 17:01:30 -0000

This is a multipart message in MIME format.

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

Without knowing the URL one can always download the current version of =
Note Well slide from:

WG Chair=E2=80=99s Page / Meeting Tools /  Note Well (PPT =
<https://www.ietf.org/wg/documents/note-well.ppt> )

=20

I agree, copying regularly is easier than checking the content.

=20

Cheers,

Mehmet

=20

From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Andrew G. Malis
Sent: Wednesday, August 9, 2017 5:36 PM
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: IETF <ietf@ietf.org>
Subject: Re: In Search of a Revised Notewell

=20

Spencer,

=20

Before each meeting I always recopy the Note Well text into my chairs =
slides, because there just might be a change in the wording, and =
it=E2=80=99s easier to copy than to check.

=20

Cheers,

Andy

=20

On Wed, Aug 9, 2017 at 11:14 AM, Spencer Dawkins at IETF =
<spencerdawkins.ietf@gmail.com <mailto:spencerdawkins.ietf@gmail.com> > =
wrote:

Under the category of "mistakes were made" ...

=20

On Wed, Aug 9, 2017 at 7:59 AM, Lee Howard <lee@asgard.org =
<mailto:lee@asgard.org> > wrote:



On 8/9/17, 4:33 AM, "ietf on behalf of tom p." <ietf-bounces@ietf.org =
<mailto:ietf-bounces@ietf.org>  on
behalf of daedulus@btconnect.com <mailto:daedulus@btconnect.com> > =
wrote:

>
>
>Clearly the WG Chairs have been given a briefing but is this something
>that those of us who only contribute via e-mail should be aware of? If
>so, how?  I cannot recall seeing anything on WG lists about this, until
>I started reading the minutes, since January 2016.

I recall seeing an announcement from Scott Bradner that certain IPR =
rules
had been updated. I don=E2=80=99t remember seeing a broad community =
announcement
with the banner, =E2=80=9CThe Note Well advisory has changed.=E2=80=9D

https://www.ietf.org/about/note-well.html

I presume that the new version was used in meeting registration.

=20

I assume so as well, although of course I didn't notice at the time.

=20

True confession - I did the slides for TSVAREA at IETF 99, and didn't =
think to change the RFC number on my Note Well slide.=20

=20

It's not like I didn't know about RFC 8179. According to =
https://datatracker.ietf.org/doc/rfc8179/ballot/, I BALLOTED YES WITH =
COMMENTS on it. But that didn't translate into me changing my Note Well =
slide ... making the change to my IETF 100 slide deck now.

=20

So, Tom, thanks for asking about this, and helping the rest of us catch =
up.

=20

Spencer, who apparently isn't getting enough caffeine in his diet Pepsi, =
in spite of many valiant efforts to do so ...

=20


------=_NextPart_000_00DF_01D31141.E5FA2A00
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:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.m-9161275643101997614gmail-
	{mso-style-name:m_-9161275643101997614gmail-;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#0000CC;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
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'color:#0000CC'>Without knowing the URL one can always download =
the current version of Note Well slide from:<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#0000CC'>WG Chair=E2=80=99s =
Page<b> </b>/ Meeting Tools /&nbsp; Note Well (<a =
href=3D"https://www.ietf.org/wg/documents/note-well.ppt">PPT</a>)<o:p></o=
:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#0000CC'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#0000CC'>I agree, copying =
regularly is easier than checking the content.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#0000CC'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#0000CC'>Cheers,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#0000CC'>Mehmet<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#0000CC'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #E1E1E1 =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b>From:</b> ietf =
[mailto:ietf-bounces@ietf.org] <b>On Behalf Of </b>Andrew G. =
Malis<br><b>Sent:</b> Wednesday, August 9, 2017 5:36 PM<br><b>To:</b> =
Spencer Dawkins at IETF =
&lt;spencerdawkins.ietf@gmail.com&gt;<br><b>Cc:</b> IETF =
&lt;ietf@ietf.org&gt;<br><b>Subject:</b> Re: In Search of a Revised =
Notewell<o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>Spencer,<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Before each meeting I always recopy the Note Well text =
into my chairs slides, because there just might be a change in the =
wording, and it=E2=80=99s easier to copy than to =
check.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Cheers,<o:p></o:p></p></div><div><p =
class=3DMsoNormal>Andy<o:p></o:p></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On Wed, =
Aug 9, 2017 at 11:14 AM, Spencer Dawkins at IETF &lt;<a =
href=3D"mailto:spencerdawkins.ietf@gmail.com" =
target=3D"_blank">spencerdawkins.ietf@gmail.com</a>&gt; =
wrote:<o:p></o:p></p><blockquote style=3D'border:none;border-left:solid =
#CCCCCC 1.0pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-right:0cm'><div><p =
class=3DMsoNormal>Under the category of &quot;mistakes were made&quot; =
...<o:p></o:p></p><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>On Wed, Aug 9, 2017 at 7:59 AM, Lee Howard &lt;<a =
href=3D"mailto:lee@asgard.org" target=3D"_blank">lee@asgard.org</a>&gt; =
wrote:<o:p></o:p></p><blockquote style=3D'border:none;border-left:solid =
#CCCCCC 1.0pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-right:0cm'><p =
class=3DMsoNormal><br><br>On 8/9/17, 4:33 AM, &quot;ietf on behalf of =
tom p.&quot; &lt;<a href=3D"mailto:ietf-bounces@ietf.org" =
target=3D"_blank">ietf-bounces@ietf.org</a> on<br><span =
class=3Dm-9161275643101997614gmail->behalf of <a =
href=3D"mailto:daedulus@btconnect.com" =
target=3D"_blank">daedulus@btconnect.com</a>&gt; =
wrote:</span><br><br><span =
class=3Dm-9161275643101997614gmail->&gt;</span><br><span =
class=3Dm-9161275643101997614gmail->&gt;</span><br><span =
class=3Dm-9161275643101997614gmail->&gt;Clearly the WG Chairs have been =
given a briefing but is this something</span><br><span =
class=3Dm-9161275643101997614gmail->&gt;that those of us who only =
contribute via e-mail should be aware of? If</span><br><span =
class=3Dm-9161275643101997614gmail->&gt;so, how?&nbsp; I cannot recall =
seeing anything on WG lists about this, until</span><br><span =
class=3Dm-9161275643101997614gmail->&gt;I started reading the minutes, =
since January 2016.</span><br><br>I recall seeing an announcement from =
Scott Bradner that certain IPR rules<br>had been updated. I =
don=E2=80=99t remember seeing a broad community announcement<br>with the =
banner, =E2=80=9CThe Note Well advisory has changed.=E2=80=9D<br><br><a =
href=3D"https://www.ietf.org/about/note-well.html" =
target=3D"_blank">https://www.ietf.org/about/note-well.html</a><br><br>I =
presume that the new version was used in meeting =
registration.<o:p></o:p></p></blockquote><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
assume so as well, although of course I didn't notice at the =
time.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>True confession - I did the slides for TSVAREA at IETF =
99, and didn't think to change the RFC number on my Note Well =
slide.&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>It's not like I didn't know about RFC 8179. According =
to <a href=3D"https://datatracker.ietf.org/doc/rfc8179/ballot/" =
target=3D"_blank">https://datatracker.ietf.org/doc/rfc8179/ballot/</a>, =
I BALLOTED YES WITH COMMENTS on it. But that didn't translate into me =
changing my Note Well slide ...&nbsp;making the change to my IETF 100 =
slide deck now.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>So, Tom, thanks for asking about this, and helping the =
rest of us catch up.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Spencer, who apparently isn't getting enough caffeine =
in his diet Pepsi, in spite of many valiant efforts to do so =
...<o:p></o:p></p></div></div></div></div></blockquote></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_00DF_01D31141.E5FA2A00--


From nobody Wed Aug  9 10:05:56 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96058132423; Wed,  9 Aug 2017 10:05:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UfAeOgEyPMoW; Wed,  9 Aug 2017 10:05:46 -0700 (PDT)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 738ED132417; Wed,  9 Aug 2017 10:05:46 -0700 (PDT)
Received: by mail-yw0-x22f.google.com with SMTP id s143so43782298ywg.1; Wed, 09 Aug 2017 10:05:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=SK8TW0apcHwTr5i9DWY+777K6aSL8WgwbeDc7KMBWVE=; b=Xck6YL+Z3cJc9AC2FfQ6r59QiIXbu9bwt03KkPs6qvoFlmdb1BuBlTkiKf53nxsjTi jYnrvQSCmdamtd2WzGJi+BH7FGL77W4n25wvnfjTHK+PxJ0rEnr13D2FRbSPZ/ZHaBQO CPeIm8iGlP0/zAF/AitYHSvecFHJKf4FJ4c1QIGQk1LS8qx7wKAm9I0I/KuNGwCzZAoI YfdmSOq/bIUkT06hm4ICXQ5LawjDfkFquIXKmzZwjh1Bd4W47jgNYLOjLPXURRgLI7yL qDNvfNC9vUjQlhsbfDJio5LyazXIrstYXFD5j+7DxWdnBSyI5Syd+vOBbdwpO16M0N/7 WuXg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=SK8TW0apcHwTr5i9DWY+777K6aSL8WgwbeDc7KMBWVE=; b=jwwL8F41fo90zZD8ozD+jblku5H4236c2MnS15reylLPLuANOIIQGR1vCEeePPVw8G 5EgVK9e33kHUpTqoRrdyCjWX+LP5TCQM7ES3Ka7cBgWYCEzmsLJ7FSTXfobAVehz8Odd O45QoWpEAokMYwTp1l4VChCNArIfWTKqhwJ6IML6T91hxLZaFC6/O7GFnqoQ5wMBZJzY LxEN5gEGZfAT0+XyOIs4k9QSqy1Sly8KpSiz/D36LG2/3YpSOeiktkP5r82AsKbPL05K 9Yzqr8D/MwzJlDUl19ujg9HneRO2gH5CIKvSnrGGd8yeh+lHhqdU4ficcx/qzdRmL1sn S6ug==
X-Gm-Message-State: AHYfb5gKhNSl7IlKjIZUlgr6ukaisk09qpM5d7OEz6t4dSoYPUdYn8fM cVKn0dkz1N4VQTmSf3Cbj5g4yiizOPy0
X-Received: by 10.37.38.146 with SMTP id m140mr7080299ybm.66.1502298345408; Wed, 09 Aug 2017 10:05:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.52.79 with HTTP; Wed, 9 Aug 2017 10:05:44 -0700 (PDT)
In-Reply-To: <4622.1502292425@obiwan.sandelman.ca>
References: <CAKKJt-cd2-tS=3QnvRcsDKcZ8=o5Z98wUr-=tp8OeP9J1M0M8g@mail.gmail.com> <4622.1502292425@obiwan.sandelman.ca>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 9 Aug 2017 12:05:44 -0500
Message-ID: <CAKKJt-fxhFnnK3T2nVj2bD=Ve7z6L0oJFjYFqBb59TusJDwFzQ@mail.gmail.com>
Subject: Re: BCP 10 Update, adding an IAOC Advisor to the Nominating Committee
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: "ietf@ietf.org" <ietf@ietf.org>, NomCom-Discussion <ietf-nomcom@ietf.org>,  "iesg@ietf.org" <iesg@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c18f336398f5f055655173b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cHlC0FG2inAJOF22EtPKd6jpzv4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 17:05:49 -0000

--94eb2c18f336398f5f055655173b
Content-Type: text/plain; charset="UTF-8"

Hi, Michael,

On Wed, Aug 9, 2017 at 10:27 AM, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
>     > At Alissa Cooper's request, I put together a short draft that
> updates BCP 10,
>     > the Nomcom process, adding a reminder that Nomcoms can ask the IAOC
> to
>     > provide an advisor, and the IAOC can provide one.
>
> The other entities provide liasons, and I see that your document explains
> why
> an advisor is listed.    I understand that the word "advisor" is from
> BCP10,
> and allows the nomcom to add advisors to the nomcom. I'd call this an
> "import", because the nomcom pulls someone in.
>

Yeah. I'm kind of dancing here, because I'm trying to reuse terminology in
a new and exciting(?) way.

This document could

   - Remind the Nomcom that they will probably need help understanding what
   the IAOC does, so they should ask, OR
   - Tell the IAOC to appoint (let's call it) an Advisor, at the same time
   the IAB and IESG are appointing liaisons.

The first option is where I headed, because I tend to write permissive BCP
text ("BCP text is hard to get right").

The second option would probably appear in a new section that looks a lot
like https://tools.ietf.org/html/rfc7437#section-4.8, except that the
eligibility would be different. I'd be OK doing that, if it makes sense to
others.

For extra credit, https://tools.ietf.org/html/rfc7437#section-4.3 could
actually require that an IAOC advisor be named, at the same level of
"required" that the IAB and IESG liaisons are required. There would be more
text changes going this way (but, see below).

>
> The other liason are not nomcom decisions, and so there is some subtle
> distinction.
>
> It's also not clear to be that we want the NOMCOM to ask for an IAOC
> advisor,
> or if we the IAOC appoints someone.  The previous tradition was the IAOC
> appointed someone, and they gave us Ole even after he was no longer a
> seated
> IAOC member.
>
> As a voting member and chair, I found the IAOC (liason) very useful in
> explaining not only what the IAOC does, but also what the IAB and IESG do
> not
> do, even when sometimes IAOC activities get relayed via IETF Chair or IAB
> chair.  Many voting members are ignorant of the IAOC and sometimes look for
> characteristics in an IESG or IAB member that would be more appropriate
> for IAOC.
> So I strongly agree with always having an IAOC liason/advisor, even when
> not
> appointing someone directly to the IAOC.
>

I'm willing to make this position a requirement, if that's the right
answer. It's optional in the current draft.


> {nomcom: 2002,2012,2013. chair: 2014}


Thanks for your continued review and advice. I'm {nomcom: 2011 liaison}, so
appreciate people with more, and especially more recent, experience telling
me what they're thinking.

Spencer

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

<div dir=3D"ltr">Hi, Michael,<div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Wed, Aug 9, 2017 at 10:27 AM, Michael Richardson <span dir=
=3D"ltr">&lt;<a href=3D"mailto:mcr+ietf@sandelman.ca" target=3D"_blank">mcr=
+ietf@sandelman.ca</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><span class=3D"gmail-"><br>
Spencer Dawkins at IETF &lt;<a href=3D"mailto:spencerdawkins.ietf@gmail.com=
">spencerdawkins.ietf@gmail.com</a><wbr>&gt; wrote:<br>
=C2=A0 =C2=A0 &gt; At Alissa Cooper&#39;s request, I put together a short d=
raft that updates BCP 10,<br>
=C2=A0 =C2=A0 &gt; the Nomcom process, adding a reminder that Nomcoms can a=
sk the IAOC to<br>
=C2=A0 =C2=A0 &gt; provide an advisor, and the IAOC can provide one.<br>
<br>
</span>The other entities provide liasons, and I see that your document exp=
lains why<br>
an advisor is listed.=C2=A0 =C2=A0 I understand that the word &quot;advisor=
&quot; is from BCP10,<br>
and allows the nomcom to add advisors to the nomcom. I&#39;d call this an<b=
r>
&quot;import&quot;, because the nomcom pulls someone in.<br></blockquote><d=
iv><br></div><div>Yeah. I&#39;m kind of dancing here, because I&#39;m tryin=
g to reuse terminology in a new and exciting(?) way.=C2=A0</div><div><br></=
div><div>This document could</div><div><ul><li>Remind the Nomcom that they =
will probably need help understanding what the IAOC does, so they should as=
k, OR</li><li>Tell the IAOC to appoint (let&#39;s call it) an Advisor, at t=
he same time the IAB and IESG are appointing liaisons.<br></li></ul><div>Th=
e first option is where I headed, because I tend to write permissive BCP te=
xt (&quot;BCP text is hard to get right&quot;).</div><div><br></div><div>Th=
e second option would probably appear in a new section that looks a lot lik=
e=C2=A0<a href=3D"https://tools.ietf.org/html/rfc7437#section-4.8">https://=
tools.ietf.org/html/rfc7437#section-4.8</a>, except that the eligibility wo=
uld be different. I&#39;d be OK doing that, if it makes sense to others.</d=
iv></div><div><br></div><div>For extra credit,=C2=A0<a href=3D"https://tool=
s.ietf.org/html/rfc7437#section-4.3">https://tools.ietf.org/html/rfc7437#se=
ction-4.3</a> could actually require that an IAOC advisor be named, at the =
same level of &quot;required&quot; that the IAB and IESG liaisons are requi=
red. There would be more text changes going this way (but, see below).</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
The other liason are not nomcom decisions, and so there is some subtle dist=
inction.<br>
<br>
It&#39;s also not clear to be that we want the NOMCOM to ask for an IAOC ad=
visor,<br>
or if we the IAOC appoints someone.=C2=A0 The previous tradition was the IA=
OC<br>
appointed someone, and they gave us Ole even after he was no longer a seate=
d<br>
IAOC member.<br>
<br>
As a voting member and chair, I found the IAOC (liason) very useful in<br>
explaining not only what the IAOC does, but also what the IAB and IESG do n=
ot<br>
do, even when sometimes IAOC activities get relayed via IETF Chair or IAB<b=
r>
chair.=C2=A0 Many voting members are ignorant of the IAOC and sometimes loo=
k for<br>
characteristics in an IESG or IAB member that would be more appropriate for=
 IAOC.<br>
So I strongly agree with always having an IAOC liason/advisor, even when no=
t<br>
appointing someone directly to the IAOC.<br></blockquote><div><br></div><di=
v>I&#39;m willing to make this position a requirement, if that&#39;s the ri=
ght answer. It&#39;s optional in the current draft.</div><div>=C2=A0</div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex">{nomcom: 2002,2012,2013. c=
hair: 2014}</blockquote><div><br></div><div>Thanks for your continued revie=
w and advice. I&#39;m {nomcom: 2011 liaison}, so appreciate people with mor=
e, and especially more recent, experience telling me what they&#39;re think=
ing.</div><div><br></div><div>Spencer=C2=A0</div></div></div></div>

--94eb2c18f336398f5f055655173b--


From nobody Wed Aug  9 11:48:46 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1331D132474 for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 11:48:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level: 
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wWBAbNIiVZhO for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 11:48:42 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEE0613247E for <ietf@ietf.org>; Wed,  9 Aug 2017 11:48:40 -0700 (PDT)
Received: from unescapeable.local ([47.186.15.50]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v79ImbAw075922 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 9 Aug 2017 13:48:38 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.15.50] claimed to be unescapeable.local
Subject: Re: BCP 10 Update, adding an IAOC Advisor to the Nominating Committee
To: ietf@ietf.org, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
References: <CAKKJt-cd2-tS=3QnvRcsDKcZ8=o5Z98wUr-=tp8OeP9J1M0M8g@mail.gmail.com> <4622.1502292425@obiwan.sandelman.ca> <CAKKJt-fxhFnnK3T2nVj2bD=Ve7z6L0oJFjYFqBb59TusJDwFzQ@mail.gmail.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <1250df52-b5b3-4f71-bab1-790d156af1e9@nostrum.com>
Date: Wed, 9 Aug 2017 13:48:37 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CAKKJt-fxhFnnK3T2nVj2bD=Ve7z6L0oJFjYFqBb59TusJDwFzQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------AAA60747DB790F94CBC16250"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9CJUzxMMw1fEtzcwf5O8Pmp6i1s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 18:48:45 -0000

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

Spencer -

The attempt to avoid the term liaison is not working well for me.

I think the biggest thing making you want to avoid that term are the 
requirements on liaisons to oversee process as you call out in the 
document. Instead of trying to to refashion terms, why don't you just 
change things so that it is explicit that only the IAB, IESG, and ISOC 
liaisons have that duty. Then you won't run into trouble with the "other 
unrepresented organizations" text you quote.

You can make it clear that for the IESG and IAB, seated members are 
required. Any other body can delegate outside its membership.

That _seems_ to me to be a more straightforward adjustment. What am I 
missing?

RjS


On 8/9/17 12:05 PM, Spencer Dawkins at IETF wrote:
> Hi, Michael,
>
> On Wed, Aug 9, 2017 at 10:27 AM, Michael Richardson 
> <mcr+ietf@sandelman.ca <mailto:mcr+ietf@sandelman.ca>> wrote:
>
>
>     Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com
>     <mailto:spencerdawkins.ietf@gmail.com>> wrote:
>         > At Alissa Cooper's request, I put together a short draft
>     that updates BCP 10,
>         > the Nomcom process, adding a reminder that Nomcoms can ask
>     the IAOC to
>         > provide an advisor, and the IAOC can provide one.
>
>     The other entities provide liasons, and I see that your document
>     explains why
>     an advisor is listed.    I understand that the word "advisor" is
>     from BCP10,
>     and allows the nomcom to add advisors to the nomcom. I'd call this an
>     "import", because the nomcom pulls someone in.
>
>
> Yeah. I'm kind of dancing here, because I'm trying to reuse 
> terminology in a new and exciting(?) way.
>
> This document could
>
>   * Remind the Nomcom that they will probably need help understanding
>     what the IAOC does, so they should ask, OR
>   * Tell the IAOC to appoint (let's call it) an Advisor, at the same
>     time the IAB and IESG are appointing liaisons.
>
> The first option is where I headed, because I tend to write permissive 
> BCP text ("BCP text is hard to get right").
>
> The second option would probably appear in a new section that looks a 
> lot like https://tools.ietf.org/html/rfc7437#section-4.8, except that 
> the eligibility would be different. I'd be OK doing that, if it makes 
> sense to others.
>
> For extra credit, https://tools.ietf.org/html/rfc7437#section-4.3 
> could actually require that an IAOC advisor be named, at the same 
> level of "required" that the IAB and IESG liaisons are required. There 
> would be more text changes going this way (but, see below).
>
>
>     The other liason are not nomcom decisions, and so there is some
>     subtle distinction.
>
>     It's also not clear to be that we want the NOMCOM to ask for an
>     IAOC advisor,
>     or if we the IAOC appoints someone.  The previous tradition was
>     the IAOC
>     appointed someone, and they gave us Ole even after he was no
>     longer a seated
>     IAOC member.
>
>     As a voting member and chair, I found the IAOC (liason) very useful in
>     explaining not only what the IAOC does, but also what the IAB and
>     IESG do not
>     do, even when sometimes IAOC activities get relayed via IETF Chair
>     or IAB
>     chair.  Many voting members are ignorant of the IAOC and sometimes
>     look for
>     characteristics in an IESG or IAB member that would be more
>     appropriate for IAOC.
>     So I strongly agree with always having an IAOC liason/advisor,
>     even when not
>     appointing someone directly to the IAOC.
>
>
> I'm willing to make this position a requirement, if that's the right 
> answer. It's optional in the current draft.
>
>     {nomcom: 2002,2012,2013. chair: 2014}
>
>
> Thanks for your continued review and advice. I'm {nomcom: 2011 
> liaison}, so appreciate people with more, and especially more recent, 
> experience telling me what they're thinking.
>
> Spencer


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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Spencer -</p>
    <p>The attempt to avoid the term liaison is not working well for me.</p>
    <p>I think the biggest thing making you want to avoid that term are
      the requirements on liaisons to oversee process as you call out in
      the document. Instead of trying to to refashion terms, why don't
      you just change things so that it is explicit that only the IAB,
      IESG, and ISOC liaisons have that duty. Then you won't run into
      trouble with the "other unrepresented organizations" text you
      quote.</p>
    <p>You can make it clear that for the IESG and IAB, seated members
      are required. Any other body can delegate outside its membership.</p>
    <p>That _seems_ to me to be a more straightforward adjustment. What
      am I missing?</p>
    <p>RjS<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 8/9/17 12:05 PM, Spencer Dawkins at
      IETF wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAKKJt-fxhFnnK3T2nVj2bD=Ve7z6L0oJFjYFqBb59TusJDwFzQ@mail.gmail.com">
      <div dir="ltr">Hi, Michael,
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Wed, Aug 9, 2017 at 10:27 AM,
            Michael Richardson <span dir="ltr">&lt;<a
                href="mailto:mcr+ietf@sandelman.ca" target="_blank"
                moz-do-not-send="true">mcr+ietf@sandelman.ca</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex"><span class="gmail-"><br>
                Spencer Dawkins at IETF &lt;<a
                  href="mailto:spencerdawkins.ietf@gmail.com"
                  moz-do-not-send="true">spencerdawkins.ietf@gmail.com</a><wbr>&gt;
                wrote:<br>
                    &gt; At Alissa Cooper's request, I put together a
                short draft that updates BCP 10,<br>
                    &gt; the Nomcom process, adding a reminder that
                Nomcoms can ask the IAOC to<br>
                    &gt; provide an advisor, and the IAOC can provide
                one.<br>
                <br>
              </span>The other entities provide liasons, and I see that
              your document explains why<br>
              an advisor is listed.    I understand that the word
              "advisor" is from BCP10,<br>
              and allows the nomcom to add advisors to the nomcom. I'd
              call this an<br>
              "import", because the nomcom pulls someone in.<br>
            </blockquote>
            <div><br>
            </div>
            <div>Yeah. I'm kind of dancing here, because I'm trying to
              reuse terminology in a new and exciting(?) way. </div>
            <div><br>
            </div>
            <div>This document could</div>
            <div>
              <ul>
                <li>Remind the Nomcom that they will probably need help
                  understanding what the IAOC does, so they should ask,
                  OR</li>
                <li>Tell the IAOC to appoint (let's call it) an Advisor,
                  at the same time the IAB and IESG are appointing
                  liaisons.<br>
                </li>
              </ul>
              <div>The first option is where I headed, because I tend to
                write permissive BCP text ("BCP text is hard to get
                right").</div>
              <div><br>
              </div>
              <div>The second option would probably appear in a new
                section that looks a lot like <a
                  href="https://tools.ietf.org/html/rfc7437#section-4.8"
                  moz-do-not-send="true">https://tools.ietf.org/html/rfc7437#section-4.8</a>,
                except that the eligibility would be different. I'd be
                OK doing that, if it makes sense to others.</div>
            </div>
            <div><br>
            </div>
            <div>For extra credit, <a
                href="https://tools.ietf.org/html/rfc7437#section-4.3"
                moz-do-not-send="true">https://tools.ietf.org/html/rfc7437#section-4.3</a>
              could actually require that an IAOC advisor be named, at
              the same level of "required" that the IAB and IESG
              liaisons are required. There would be more text changes
              going this way (but, see below).</div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <br>
              The other liason are not nomcom decisions, and so there is
              some subtle distinction.<br>
              <br>
              It's also not clear to be that we want the NOMCOM to ask
              for an IAOC advisor,<br>
              or if we the IAOC appoints someone.  The previous
              tradition was the IAOC<br>
              appointed someone, and they gave us Ole even after he was
              no longer a seated<br>
              IAOC member.<br>
              <br>
              As a voting member and chair, I found the IAOC (liason)
              very useful in<br>
              explaining not only what the IAOC does, but also what the
              IAB and IESG do not<br>
              do, even when sometimes IAOC activities get relayed via
              IETF Chair or IAB<br>
              chair.  Many voting members are ignorant of the IAOC and
              sometimes look for<br>
              characteristics in an IESG or IAB member that would be
              more appropriate for IAOC.<br>
              So I strongly agree with always having an IAOC
              liason/advisor, even when not<br>
              appointing someone directly to the IAOC.<br>
            </blockquote>
            <div><br>
            </div>
            <div>I'm willing to make this position a requirement, if
              that's the right answer. It's optional in the current
              draft.</div>
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">{nomcom:
              2002,2012,2013. chair: 2014}</blockquote>
            <div><br>
            </div>
            <div>Thanks for your continued review and advice. I'm
              {nomcom: 2011 liaison}, so appreciate people with more,
              and especially more recent, experience telling me what
              they're thinking.</div>
            <div><br>
            </div>
            <div>Spencer </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------AAA60747DB790F94CBC16250--


From nobody Wed Aug  9 12:00:29 2017
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A95781324F9 for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 12:00:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ngEMY4sAPDqS for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 12:00:24 -0700 (PDT)
Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6010F1324D8 for <ietf@ietf.org>; Wed,  9 Aug 2017 12:00:21 -0700 (PDT)
Received: by mail-qt0-x229.google.com with SMTP id t37so41763132qtg.5 for <ietf@ietf.org>; Wed, 09 Aug 2017 12:00:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YeaJYwDwl1aeAhuYtYRkKSbH9hfIPsGteHRreL9GNDE=; b=ZXyDK7SUB3qk5+ZFujadXPbyvKg3ILnRDQeaTLmP1uBnHCWF06onWHBa9XED4ILnhi 6FjeB0w9PE4Ht0V1OV4OzaLEswi/Ab2V7/4ylbptXhTKB10x4q+GtGUrumol/jmvtbfl wRWeJZIwwZ12hv5WOXBTegi5QMGxDeY5S9qSraP1UWjv6T4KDcJJpWd2snTW07xVIi3K cmKs2nkqB2zz4hkWB2gpkizyTA3g1Ki5wGYSARLQxEcBF/gCxg4H85Be2sTmdezLIBpZ 8cMZdzAJuHNV2icAU78EzEbWqsE05sWXRHuwuxC+F6CgxZnMXWLyGAT9JsoDLohz2Ymn df/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=YeaJYwDwl1aeAhuYtYRkKSbH9hfIPsGteHRreL9GNDE=; b=PPYKkb9GpLF+ie5gUnYmv/03n9t5vLM/YLnEJ/UJRxSYvuw+/utvGGv+zhFfTXqxa1 sZKbDLgdpNcVwiurLPNp9oM4PVrBuYgC8YftCZvrK0BNC7zc5NIWIBjCrIHhfxYYdydI 243SZCopq/RQrY1ip8RFPIbY1iaDoIpvZlIzeFDwryiyRUlRlEx4wH+KWrYfiphqmx6W jSfLygXOp50KQRqvDBVcuN28x7AuOoZDuzfOZbgO8ftHdEyk5EZqHCXzJ65QZoiB0XVP zU5Q0BgW6CeIugYWHNN0e9WAENjefO7Ow11q44Flmum3CjHTlMws510d7V+ENwyTP0km AW6Q==
X-Gm-Message-State: AHYfb5ioj3/bDeKJEQssS3k1oj7TulJSpLresCkdt+lsKrWrtEMtIMqF hk2iiG79/7pafAslUlEUTqz3UT7lmw==
X-Received: by 10.200.45.164 with SMTP id p33mr12328437qta.208.1502305220189;  Wed, 09 Aug 2017 12:00:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.59.248 with HTTP; Wed, 9 Aug 2017 11:59:49 -0700 (PDT)
In-Reply-To: <1250df52-b5b3-4f71-bab1-790d156af1e9@nostrum.com>
References: <CAKKJt-cd2-tS=3QnvRcsDKcZ8=o5Z98wUr-=tp8OeP9J1M0M8g@mail.gmail.com> <4622.1502292425@obiwan.sandelman.ca> <CAKKJt-fxhFnnK3T2nVj2bD=Ve7z6L0oJFjYFqBb59TusJDwFzQ@mail.gmail.com> <1250df52-b5b3-4f71-bab1-790d156af1e9@nostrum.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 9 Aug 2017 11:59:49 -0700
Message-ID: <CA+9kkMC4yWGptsTxhQgHQp4mRppMfpXdw_ZLz47Sgyyb=przDQ@mail.gmail.com>
Subject: Re: BCP 10 Update, adding an IAOC Advisor to the Nominating Committee
To: Robert Sparks <rjsparks@nostrum.com>
Cc: IETF <ietf@ietf.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="001a11c023fefe6153055656b021"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6Nla-1aOuEaRdmfutJj7nC-59iI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 19:00:28 -0000

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

On Wed, Aug 9, 2017 at 11:48 AM, Robert Sparks <rjsparks@nostrum.com> wrote:

> Spencer -
>
> The attempt to avoid the term liaison is not working well for me.
>
> I think the biggest thing making you want to avoid that term are the
> requirements on liaisons to oversee process as you call out in the
> document. Instead of trying to to refashion terms, why don't you just
> change things so that it is explicit that only the IAB, IESG, and ISOC
> liaisons have that duty. Then you won't run into trouble with the "other
> unrepresented organizations" text you quote.
>
> You can make it clear that for the IESG and IAB, seated members are
> required. Any other body can delegate outside its membership.
>
> That _seems_ to me to be a more straightforward adjustment. What am I
> missing?
>
> There's at least one other potential shift: removing the IAOC liaison from
the list of liaisons who might serve as replacement Nomcom chair.  If you
remove that and the other process duties, it's not clear why it is useful
to call two different sets of responsibilities by the same name.  You can
do it, of course, as long as you've specified it.  But I don't personally
see much of an advantage.

My take is that we want the IAOC job or its successor to eventually by
folks with specific skills in financial oversight, program management, and
community relations.  Having the IAOC rep be able to explain those tasks to
a Nomcom is very valuable, and I support getting this formalized.  I care
about that much more than what we call it.

Ted


> RjS
>
> On 8/9/17 12:05 PM, Spencer Dawkins at IETF wrote:
>
> Hi, Michael,
>
> On Wed, Aug 9, 2017 at 10:27 AM, Michael Richardson <mcr+ietf@sandelman.ca
> > wrote:
>
>>
>> Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
>>     > At Alissa Cooper's request, I put together a short draft that
>> updates BCP 10,
>>     > the Nomcom process, adding a reminder that Nomcoms can ask the IAOC
>> to
>>     > provide an advisor, and the IAOC can provide one.
>>
>> The other entities provide liasons, and I see that your document explains
>> why
>> an advisor is listed.    I understand that the word "advisor" is from
>> BCP10,
>> and allows the nomcom to add advisors to the nomcom. I'd call this an
>> "import", because the nomcom pulls someone in.
>>
>
> Yeah. I'm kind of dancing here, because I'm trying to reuse terminology in
> a new and exciting(?) way.
>
> This document could
>
>    - Remind the Nomcom that they will probably need help understanding
>    what the IAOC does, so they should ask, OR
>    - Tell the IAOC to appoint (let's call it) an Advisor, at the same
>    time the IAB and IESG are appointing liaisons.
>
> The first option is where I headed, because I tend to write permissive BCP
> text ("BCP text is hard to get right").
>
> The second option would probably appear in a new section that looks a lot
> like https://tools.ietf.org/html/rfc7437#section-4.8, except that the
> eligibility would be different. I'd be OK doing that, if it makes sense to
> others.
>
> For extra credit, https://tools.ietf.org/html/rfc7437#section-4.3 could
> actually require that an IAOC advisor be named, at the same level of
> "required" that the IAB and IESG liaisons are required. There would be more
> text changes going this way (but, see below).
>
>>
>> The other liason are not nomcom decisions, and so there is some subtle
>> distinction.
>>
>> It's also not clear to be that we want the NOMCOM to ask for an IAOC
>> advisor,
>> or if we the IAOC appoints someone.  The previous tradition was the IAOC
>> appointed someone, and they gave us Ole even after he was no longer a
>> seated
>> IAOC member.
>>
>> As a voting member and chair, I found the IAOC (liason) very useful in
>> explaining not only what the IAOC does, but also what the IAB and IESG do
>> not
>> do, even when sometimes IAOC activities get relayed via IETF Chair or IAB
>> chair.  Many voting members are ignorant of the IAOC and sometimes look
>> for
>> characteristics in an IESG or IAB member that would be more appropriate
>> for IAOC.
>> So I strongly agree with always having an IAOC liason/advisor, even when
>> not
>> appointing someone directly to the IAOC.
>>
>
> I'm willing to make this position a requirement, if that's the right
> answer. It's optional in the current draft.
>
>
>> {nomcom: 2002,2012,2013. chair: 2014}
>
>
> Thanks for your continued review and advice. I'm {nomcom: 2011 liaison},
> so appreciate people with more, and especially more recent, experience
> telling me what they're thinking.
>
> Spencer
>
>
>

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

<div dir=3D"ltr">On Wed, Aug 9, 2017 at 11:48 AM, Robert Sparks <span dir=
=3D"ltr">&lt;<a href=3D"mailto:rjsparks@nostrum.com" target=3D"_blank">rjsp=
arks@nostrum.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div c=
lass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p>Spencer -</p>
    <p>The attempt to avoid the term liaison is not working well for me.</p=
>
    <p>I think the biggest thing making you want to avoid that term are
      the requirements on liaisons to oversee process as you call out in
      the document. Instead of trying to to refashion terms, why don&#39;t
      you just change things so that it is explicit that only the IAB,
      IESG, and ISOC liaisons have that duty. Then you won&#39;t run into
      trouble with the &quot;other unrepresented organizations&quot; text y=
ou
      quote.</p>
    <p>You can make it clear that for the IESG and IAB, seated members
      are required. Any other body can delegate outside its membership.</p>
    <p>That _seems_ to me to be a more straightforward adjustment. What
      am I missing?</p>
    <p></p></div></blockquote><div>There&#39;s at least one other potential=
 shift: removing the IAOC liaison from the list of liaisons who might serve=
 as replacement Nomcom chair.=C2=A0 If you remove that and the other proces=
s duties, it&#39;s not clear why it is useful to call two different sets of=
 responsibilities by the same name.=C2=A0 You can do it, of course, as long=
 as you&#39;ve specified it.=C2=A0 But I don&#39;t personally see much of a=
n advantage.<br><br></div><div>My take is that we want the IAOC job or its =
successor to eventually by folks with specific skills in financial oversigh=
t, program management, and community relations.=C2=A0 Having the IAOC rep b=
e able to explain those tasks to a Nomcom is very valuable, and I support g=
etting this formalized.=C2=A0 I care about that much more than what we call=
 it.<br><br></div><div>Ted<br></div><div>=C2=A0</div><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex"><div text=3D"#000000" bgcolor=3D"#FFFFFF"><p>RjS<br>
    </p><div><div class=3D"h5">
    <br>
    <div class=3D"m_1069408380790804449moz-cite-prefix">On 8/9/17 12:05 PM,=
 Spencer Dawkins at
      IETF wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">Hi, Michael,
        <div class=3D"gmail_extra"><br>
          <div class=3D"gmail_quote">On Wed, Aug 9, 2017 at 10:27 AM,
            Michael Richardson <span dir=3D"ltr">&lt;<a href=3D"mailto:mcr+=
ietf@sandelman.ca" target=3D"_blank">mcr+ietf@sandelman.ca</a>&gt;</span>
            wrote:<br>
            <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class=
=3D"m_1069408380790804449gmail-"><br>
                Spencer Dawkins at IETF &lt;<a href=3D"mailto:spencerdawkin=
s.ietf@gmail.com" target=3D"_blank">spencerdawkins.ietf@gmail.com</a><wbr>&=
gt;
                wrote:<br>
                =C2=A0 =C2=A0 &gt; At Alissa Cooper&#39;s request, I put to=
gether a
                short draft that updates BCP 10,<br>
                =C2=A0 =C2=A0 &gt; the Nomcom process, adding a reminder th=
at
                Nomcoms can ask the IAOC to<br>
                =C2=A0 =C2=A0 &gt; provide an advisor, and the IAOC can pro=
vide
                one.<br>
                <br>
              </span>The other entities provide liasons, and I see that
              your document explains why<br>
              an advisor is listed.=C2=A0 =C2=A0 I understand that the word
              &quot;advisor&quot; is from BCP10,<br>
              and allows the nomcom to add advisors to the nomcom. I&#39;d
              call this an<br>
              &quot;import&quot;, because the nomcom pulls someone in.<br>
            </blockquote>
            <div><br>
            </div>
            <div>Yeah. I&#39;m kind of dancing here, because I&#39;m trying=
 to
              reuse terminology in a new and exciting(?) way.=C2=A0</div>
            <div><br>
            </div>
            <div>This document could</div>
            <div>
              <ul>
                <li>Remind the Nomcom that they will probably need help
                  understanding what the IAOC does, so they should ask,
                  OR</li>
                <li>Tell the IAOC to appoint (let&#39;s call it) an Advisor=
,
                  at the same time the IAB and IESG are appointing
                  liaisons.<br>
                </li>
              </ul>
              <div>The first option is where I headed, because I tend to
                write permissive BCP text (&quot;BCP text is hard to get
                right&quot;).</div>
              <div><br>
              </div>
              <div>The second option would probably appear in a new
                section that looks a lot like=C2=A0<a href=3D"https://tools=
.ietf.org/html/rfc7437#section-4.8" target=3D"_blank">https://tools.ietf.or=
g/<wbr>html/rfc7437#section-4.8</a>,
                except that the eligibility would be different. I&#39;d be
                OK doing that, if it makes sense to others.</div>
            </div>
            <div><br>
            </div>
            <div>For extra credit,=C2=A0<a href=3D"https://tools.ietf.org/h=
tml/rfc7437#section-4.3" target=3D"_blank">https://tools.ietf.<wbr>org/html=
/rfc7437#section-4.3</a>
              could actually require that an IAOC advisor be named, at
              the same level of &quot;required&quot; that the IAB and IESG
              liaisons are required. There would be more text changes
              going this way (but, see below).</div>
            <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
              <br>
              The other liason are not nomcom decisions, and so there is
              some subtle distinction.<br>
              <br>
              It&#39;s also not clear to be that we want the NOMCOM to ask
              for an IAOC advisor,<br>
              or if we the IAOC appoints someone.=C2=A0 The previous
              tradition was the IAOC<br>
              appointed someone, and they gave us Ole even after he was
              no longer a seated<br>
              IAOC member.<br>
              <br>
              As a voting member and chair, I found the IAOC (liason)
              very useful in<br>
              explaining not only what the IAOC does, but also what the
              IAB and IESG do not<br>
              do, even when sometimes IAOC activities get relayed via
              IETF Chair or IAB<br>
              chair.=C2=A0 Many voting members are ignorant of the IAOC and
              sometimes look for<br>
              characteristics in an IESG or IAB member that would be
              more appropriate for IAOC.<br>
              So I strongly agree with always having an IAOC
              liason/advisor, even when not<br>
              appointing someone directly to the IAOC.<br>
            </blockquote>
            <div><br>
            </div>
            <div>I&#39;m willing to make this position a requirement, if
              that&#39;s the right answer. It&#39;s optional in the current
              draft.</div>
            <div>=C2=A0</div>
            <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">{nomcom:
              2002,2012,2013. chair: 2014}</blockquote>
            <div><br>
            </div>
            <div>Thanks for your continued review and advice. I&#39;m
              {nomcom: 2011 liaison}, so appreciate people with more,
              and especially more recent, experience telling me what
              they&#39;re thinking.</div>
            <div><br>
            </div>
            <div>Spencer=C2=A0</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </div></div></div>

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

--001a11c023fefe6153055656b021--


From nobody Wed Aug  9 12:02:30 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA52213247C; Wed,  9 Aug 2017 12:02:16 -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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pTvhWKNRvjQk; Wed,  9 Aug 2017 12:02: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 F1954132471; Wed,  9 Aug 2017 12:02:14 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 8506C2009E; Wed,  9 Aug 2017 15:04:29 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id A6308806BA; Wed,  9 Aug 2017 15:02:13 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
cc: "ietf\@ietf.org" <ietf@ietf.org>, NomCom-Discussion <ietf-nomcom@ietf.org>, "iesg\@ietf.org" <iesg@ietf.org>
Subject: Re: BCP 10 Update, adding an IAOC Advisor to the Nominating Committee
In-Reply-To: <CAKKJt-fxhFnnK3T2nVj2bD=Ve7z6L0oJFjYFqBb59TusJDwFzQ@mail.gmail.com>
References: <CAKKJt-cd2-tS=3QnvRcsDKcZ8=o5Z98wUr-=tp8OeP9J1M0M8g@mail.gmail.com> <4622.1502292425@obiwan.sandelman.ca> <CAKKJt-fxhFnnK3T2nVj2bD=Ve7z6L0oJFjYFqBb59TusJDwFzQ@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.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-sha256; protocol="application/pgp-signature"
Date: Wed, 09 Aug 2017 15:02:13 -0400
Message-ID: <21862.1502305333@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VvqFOG2RCTxiMfuoM9bPdpyjTTA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 19:02:17 -0000

--=-=-=
Content-Type: text/plain


Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
    > Yeah. I'm kind of dancing here, because I'm trying to reuse terminology in a
    > new and exciting(?) way.

understood.

    > This document could

    > * Remind the Nomcom that they will probably need help understanding what the
    > IAOC does, so they should ask, OR
    > * Tell the IAOC to appoint (let's call it) an Advisor, at the same time the
    > IAB and IESG are appointing liaisons.

    > The first option is where I headed, because I tend to write permissive BCP
    > text ("BCP text is hard to get right").

I think that I'd prefer the IAOC be told to pick someone, but I'm listening
to other opinions.


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




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

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

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlmLXDUACgkQgItw+93Q
3WVv+ggAsX+CK4dS6Y+N1wj/0dAjOUa21v0uV8zD4XtdhsXDGB23G2Lq+MLJrBbt
c4PdW7FGH0otkYhELWq6YRT/zrrW4TiaftBezMckAEt7xAD0K9F+GgSdSDiPfdii
aaiULRp0CKUofyvBec/y1mjhjhP4aG7dB/+kYnO1LX8XtrFmtneNZopo73+Kd+bM
NciXQA1pGSFYve79DtsM+HRuJdY98X4Ok0Z/T8muDPDecx0j7V9xSRPh9PtvGEKz
81kSgI//GUB31A0QWSDN1XBbgk6RZ/T5/3oQwgRlp0TanBSUmlBngZrzU8a/Ii/v
i2OqjmiPlzm8yTWoirFriWlqCc4QWA==
=fuMF
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Aug  9 12:18:29 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2097132489 for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 12:18:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level: 
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xVN6-dm0KwU1 for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 12:18:25 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 233A8132459 for <ietf@ietf.org>; Wed,  9 Aug 2017 12:17:59 -0700 (PDT)
Received: from unescapeable.local ([47.186.15.50]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v79JHu8U081081 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 9 Aug 2017 14:17:57 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.15.50] claimed to be unescapeable.local
Subject: Re: BCP 10 Update, adding an IAOC Advisor to the Nominating Committee
To: Ted Hardie <ted.ietf@gmail.com>
Cc: IETF <ietf@ietf.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
References: <CAKKJt-cd2-tS=3QnvRcsDKcZ8=o5Z98wUr-=tp8OeP9J1M0M8g@mail.gmail.com> <4622.1502292425@obiwan.sandelman.ca> <CAKKJt-fxhFnnK3T2nVj2bD=Ve7z6L0oJFjYFqBb59TusJDwFzQ@mail.gmail.com> <1250df52-b5b3-4f71-bab1-790d156af1e9@nostrum.com> <CA+9kkMC4yWGptsTxhQgHQp4mRppMfpXdw_ZLz47Sgyyb=przDQ@mail.gmail.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <5e20388a-a6dd-691d-feeb-8f5363119c0c@nostrum.com>
Date: Wed, 9 Aug 2017 14:17:56 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CA+9kkMC4yWGptsTxhQgHQp4mRppMfpXdw_ZLz47Sgyyb=przDQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------FC018A08B0EE8F9C58E44AF7"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/z-j3ydV07Cfx7jGsxOasw8d6IBc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 19:18:28 -0000

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



On 8/9/17 1:59 PM, Ted Hardie wrote:
> On Wed, Aug 9, 2017 at 11:48 AM, Robert Sparks <rjsparks@nostrum.com 
> <mailto:rjsparks@nostrum.com>> wrote:
>
>     Spencer -
>
>     The attempt to avoid the term liaison is not working well for me.
>
>     I think the biggest thing making you want to avoid that term are
>     the requirements on liaisons to oversee process as you call out in
>     the document. Instead of trying to to refashion terms, why don't
>     you just change things so that it is explicit that only the IAB,
>     IESG, and ISOC liaisons have that duty. Then you won't run into
>     trouble with the "other unrepresented organizations" text you quote.
>
>     You can make it clear that for the IESG and IAB, seated members
>     are required. Any other body can delegate outside its membership.
>
>     That _seems_ to me to be a more straightforward adjustment. What
>     am I missing?
>
> There's at least one other potential shift: removing the IAOC liaison 
> from the list of liaisons who might serve as replacement Nomcom 
> chair.  If you remove that and the other process duties, it's not 
> clear why it is useful to call two different sets of responsibilities 
> by the same name.  You can do it, of course, as long as you've 
> specified it.  But I don't personally see much of an advantage.
>
> My take is that we want the IAOC job or its successor to eventually by 
> folks with specific skills in financial oversight, program management, 
> and community relations. Having the IAOC rep be able to explain those 
> tasks to a Nomcom is very valuable, and I support getting this 
> formalized.  I care about that much more than what we call it.
I think the thing that's bothering me is that the current proposal still 
leaves the unintended trouble if the "Any committee member may propose 
the addition of a liaison" is exercised.

If you strip away all the rationalization text, the change in Spencer's 
current document reduces to "Hey future nomcoms - it would be a good 
idea if you found an advisor that can talk to you about the IAOC, and 
the current IAOC might be a good body to ask to help you find one". I 
don't object to that. Perhaps the rationalization is a distraction?

But the rationalization part also argues that we want to say "If you 
think you want a liaison from some other body, you might want to look 
closely at asking for an advisor instead."


>
> Ted
>
>     RjS
>
>
>     On 8/9/17 12:05 PM, Spencer Dawkins at IETF wrote:
>>     Hi, Michael,
>>
>>     On Wed, Aug 9, 2017 at 10:27 AM, Michael Richardson
>>     <mcr+ietf@sandelman.ca <mailto:mcr+ietf@sandelman.ca>> wrote:
>>
>>
>>         Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com
>>         <mailto:spencerdawkins.ietf@gmail.com>> wrote:
>>             > At Alissa Cooper's request, I put together a short
>>         draft that updates BCP 10,
>>             > the Nomcom process, adding a reminder that Nomcoms can
>>         ask the IAOC to
>>             > provide an advisor, and the IAOC can provide one.
>>
>>         The other entities provide liasons, and I see that your
>>         document explains why
>>         an advisor is listed.    I understand that the word "advisor"
>>         is from BCP10,
>>         and allows the nomcom to add advisors to the nomcom. I'd call
>>         this an
>>         "import", because the nomcom pulls someone in.
>>
>>
>>     Yeah. I'm kind of dancing here, because I'm trying to reuse
>>     terminology in a new and exciting(?) way.
>>
>>     This document could
>>
>>       * Remind the Nomcom that they will probably need help
>>         understanding what the IAOC does, so they should ask, OR
>>       * Tell the IAOC to appoint (let's call it) an Advisor, at the
>>         same time the IAB and IESG are appointing liaisons.
>>
>>     The first option is where I headed, because I tend to write
>>     permissive BCP text ("BCP text is hard to get right").
>>
>>     The second option would probably appear in a new section that
>>     looks a lot like https://tools.ietf.org/html/rfc7437#section-4.8
>>     <https://tools.ietf.org/html/rfc7437#section-4.8>, except that
>>     the eligibility would be different. I'd be OK doing that, if it
>>     makes sense to others.
>>
>>     For extra credit, https://tools.ietf.org/html/rfc7437#section-4.3
>>     <https://tools.ietf.org/html/rfc7437#section-4.3> could actually
>>     require that an IAOC advisor be named, at the same level of
>>     "required" that the IAB and IESG liaisons are required. There
>>     would be more text changes going this way (but, see below).
>>
>>
>>         The other liason are not nomcom decisions, and so there is
>>         some subtle distinction.
>>
>>         It's also not clear to be that we want the NOMCOM to ask for
>>         an IAOC advisor,
>>         or if we the IAOC appoints someone.  The previous tradition
>>         was the IAOC
>>         appointed someone, and they gave us Ole even after he was no
>>         longer a seated
>>         IAOC member.
>>
>>         As a voting member and chair, I found the IAOC (liason) very
>>         useful in
>>         explaining not only what the IAOC does, but also what the IAB
>>         and IESG do not
>>         do, even when sometimes IAOC activities get relayed via IETF
>>         Chair or IAB
>>         chair.  Many voting members are ignorant of the IAOC and
>>         sometimes look for
>>         characteristics in an IESG or IAB member that would be more
>>         appropriate for IAOC.
>>         So I strongly agree with always having an IAOC
>>         liason/advisor, even when not
>>         appointing someone directly to the IAOC.
>>
>>
>>     I'm willing to make this position a requirement, if that's the
>>     right answer. It's optional in the current draft.
>>
>>         {nomcom: 2002,2012,2013. chair: 2014}
>>
>>
>>     Thanks for your continued review and advice. I'm {nomcom: 2011
>>     liaison}, so appreciate people with more, and especially more
>>     recent, experience telling me what they're thinking.
>>
>>     Spencer
>
>


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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 8/9/17 1:59 PM, Ted Hardie wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CA+9kkMC4yWGptsTxhQgHQp4mRppMfpXdw_ZLz47Sgyyb=przDQ@mail.gmail.com">
      <div dir="ltr">On Wed, Aug 9, 2017 at 11:48 AM, Robert Sparks <span
          dir="ltr">&lt;<a href="mailto:rjsparks@nostrum.com"
            target="_blank" moz-do-not-send="true">rjsparks@nostrum.com</a>&gt;</span>
        wrote:<br>
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF">
                <p>Spencer -</p>
                <p>The attempt to avoid the term liaison is not working
                  well for me.</p>
                <p>I think the biggest thing making you want to avoid
                  that term are the requirements on liaisons to oversee
                  process as you call out in the document. Instead of
                  trying to to refashion terms, why don't you just
                  change things so that it is explicit that only the
                  IAB, IESG, and ISOC liaisons have that duty. Then you
                  won't run into trouble with the "other unrepresented
                  organizations" text you quote.</p>
                <p>You can make it clear that for the IESG and IAB,
                  seated members are required. Any other body can
                  delegate outside its membership.</p>
                <p>That _seems_ to me to be a more straightforward
                  adjustment. What am I missing?</p>
              </div>
            </blockquote>
            <div>There's at least one other potential shift: removing
              the IAOC liaison from the list of liaisons who might serve
              as replacement Nomcom chair.  If you remove that and the
              other process duties, it's not clear why it is useful to
              call two different sets of responsibilities by the same
              name.  You can do it, of course, as long as you've
              specified it.  But I don't personally see much of an
              advantage.<br>
              <br>
            </div>
            <div>My take is that we want the IAOC job or its successor
              to eventually by folks with specific skills in financial
              oversight, program management, and community relations. 
              Having the IAOC rep be able to explain those tasks to a
              Nomcom is very valuable, and I support getting this
              formalized.  I care about that much more than what we call
              it.<br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    I think the thing that's bothering me is that the current proposal
    still leaves the unintended trouble if the "Any committee member may
    propose the addition of a liaison" is exercised.<br>
    <br>
    If you strip away all the rationalization text, the change in
    Spencer's current document reduces to "Hey future nomcoms - it would
    be a good idea if you found an advisor that can talk to you about
    the IAOC, and the current IAOC might be a good body to ask to help
    you find one". I don't object to that. Perhaps the rationalization
    is a distraction? <br>
    <br>
    But the rationalization part also argues that we want to say "If you
    think you want a liaison from some other body, you might want to
    look closely at asking for an advisor instead."<br>
    <br>
    <br>
    <blockquote type="cite"
cite="mid:CA+9kkMC4yWGptsTxhQgHQp4mRppMfpXdw_ZLz47Sgyyb=przDQ@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div>Ted<br>
            </div>
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF">
                <p>RjS<br>
                </p>
                <div>
                  <div class="h5"> <br>
                    <div class="m_1069408380790804449moz-cite-prefix">On
                      8/9/17 12:05 PM, Spencer Dawkins at IETF wrote:<br>
                    </div>
                    <blockquote type="cite">
                      <div dir="ltr">Hi, Michael,
                        <div class="gmail_extra"><br>
                          <div class="gmail_quote">On Wed, Aug 9, 2017
                            at 10:27 AM, Michael Richardson <span
                              dir="ltr">&lt;<a
                                href="mailto:mcr+ietf@sandelman.ca"
                                target="_blank" moz-do-not-send="true">mcr+ietf@sandelman.ca</a>&gt;</span>
                            wrote:<br>
                            <blockquote class="gmail_quote"
                              style="margin:0px 0px 0px
                              0.8ex;border-left:1px solid
                              rgb(204,204,204);padding-left:1ex"><span
                                class="m_1069408380790804449gmail-"><br>
                                Spencer Dawkins at IETF &lt;<a
                                  href="mailto:spencerdawkins.ietf@gmail.com"
                                  target="_blank" moz-do-not-send="true">spencerdawkins.ietf@gmail.com</a><wbr>&gt;
                                wrote:<br>
                                    &gt; At Alissa Cooper's request, I
                                put together a short draft that updates
                                BCP 10,<br>
                                    &gt; the Nomcom process, adding a
                                reminder that Nomcoms can ask the IAOC
                                to<br>
                                    &gt; provide an advisor, and the
                                IAOC can provide one.<br>
                                <br>
                              </span>The other entities provide liasons,
                              and I see that your document explains why<br>
                              an advisor is listed.    I understand that
                              the word "advisor" is from BCP10,<br>
                              and allows the nomcom to add advisors to
                              the nomcom. I'd call this an<br>
                              "import", because the nomcom pulls someone
                              in.<br>
                            </blockquote>
                            <div><br>
                            </div>
                            <div>Yeah. I'm kind of dancing here, because
                              I'm trying to reuse terminology in a new
                              and exciting(?) way. </div>
                            <div><br>
                            </div>
                            <div>This document could</div>
                            <div>
                              <ul>
                                <li>Remind the Nomcom that they will
                                  probably need help understanding what
                                  the IAOC does, so they should ask, OR</li>
                                <li>Tell the IAOC to appoint (let's call
                                  it) an Advisor, at the same time the
                                  IAB and IESG are appointing liaisons.<br>
                                </li>
                              </ul>
                              <div>The first option is where I headed,
                                because I tend to write permissive BCP
                                text ("BCP text is hard to get right").</div>
                              <div><br>
                              </div>
                              <div>The second option would probably
                                appear in a new section that looks a lot
                                like <a
                                  href="https://tools.ietf.org/html/rfc7437#section-4.8"
                                  target="_blank" moz-do-not-send="true">https://tools.ietf.org/<wbr>html/rfc7437#section-4.8</a>,
                                except that the eligibility would be
                                different. I'd be OK doing that, if it
                                makes sense to others.</div>
                            </div>
                            <div><br>
                            </div>
                            <div>For extra credit, <a
                                href="https://tools.ietf.org/html/rfc7437#section-4.3"
                                target="_blank" moz-do-not-send="true">https://tools.ietf.<wbr>org/html/rfc7437#section-4.3</a>
                              could actually require that an IAOC
                              advisor be named, at the same level of
                              "required" that the IAB and IESG liaisons
                              are required. There would be more text
                              changes going this way (but, see below).</div>
                            <blockquote class="gmail_quote"
                              style="margin:0px 0px 0px
                              0.8ex;border-left:1px solid
                              rgb(204,204,204);padding-left:1ex"> <br>
                              The other liason are not nomcom decisions,
                              and so there is some subtle distinction.<br>
                              <br>
                              It's also not clear to be that we want the
                              NOMCOM to ask for an IAOC advisor,<br>
                              or if we the IAOC appoints someone.  The
                              previous tradition was the IAOC<br>
                              appointed someone, and they gave us Ole
                              even after he was no longer a seated<br>
                              IAOC member.<br>
                              <br>
                              As a voting member and chair, I found the
                              IAOC (liason) very useful in<br>
                              explaining not only what the IAOC does,
                              but also what the IAB and IESG do not<br>
                              do, even when sometimes IAOC activities
                              get relayed via IETF Chair or IAB<br>
                              chair.  Many voting members are ignorant
                              of the IAOC and sometimes look for<br>
                              characteristics in an IESG or IAB member
                              that would be more appropriate for IAOC.<br>
                              So I strongly agree with always having an
                              IAOC liason/advisor, even when not<br>
                              appointing someone directly to the IAOC.<br>
                            </blockquote>
                            <div><br>
                            </div>
                            <div>I'm willing to make this position a
                              requirement, if that's the right answer.
                              It's optional in the current draft.</div>
                            <div> </div>
                            <blockquote class="gmail_quote"
                              style="margin:0px 0px 0px
                              0.8ex;border-left:1px solid
                              rgb(204,204,204);padding-left:1ex">{nomcom:
                              2002,2012,2013. chair: 2014}</blockquote>
                            <div><br>
                            </div>
                            <div>Thanks for your continued review and
                              advice. I'm {nomcom: 2011 liaison}, so
                              appreciate people with more, and
                              especially more recent, experience telling
                              me what they're thinking.</div>
                            <div><br>
                            </div>
                            <div>Spencer </div>
                          </div>
                        </div>
                      </div>
                    </blockquote>
                    <br>
                  </div>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------FC018A08B0EE8F9C58E44AF7--


From nobody Wed Aug  9 12:56:25 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0E3E1324B4; Wed,  9 Aug 2017 12:56:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M-btwPnfCFfX; Wed,  9 Aug 2017 12:56:21 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F14D1324B3; Wed,  9 Aug 2017 12:56:21 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id s143so46530250ywg.1; Wed, 09 Aug 2017 12:56:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ggoyIoOhEu5EBjtHOC6k5Vlt6EFWBURvbEhpPpu9zpo=; b=LwmS2fsfL2Sq/TkHBMekm7nZxrxYoO1hwLPnS79kuLjoUUZJVwI6+GMh/qRX+quc7U M+fDmDeAFg9OrGfgO1RaxBo1JCMYRPZtd6yr8S/Mb/UNgwCvG03EM0+adSAC+ZOSxhli XGfkEgpqeV38ccd5MFwjEdGdqpShBLHZiIx0T2vcqfZ1gKIg6jOfdKO/KIkjbGWBD2eT LFMNMlpm4X7U0DVC51SUiBLlxyZEzg4orzmyG4wKpoAnXDYZEc2zbA6Qv8mM0VxCyy0M SX43Oo6ieS8wGHkz0eOHZ4cKqoW180IyKp3Jka2ABHiROFxgMN1pmgOeswQrF5ss1BR0 3D2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ggoyIoOhEu5EBjtHOC6k5Vlt6EFWBURvbEhpPpu9zpo=; b=DPK58gQ3FljeXHdSVpKsGe7pEpBGPgqKXnJNCVe3o9bNzdTBnUyaRmDoX0xci44GMn 8KoaP/hzAPXl+phsXQYy/WBkWvF5E+ZxfwuxdbjgX8MQMUovtxaTrYVAwCXhsd1Q7RLl I9wKBCOOmG69Q08sqPa+nZvG3tpzNh8ZTO3EjPUZPm772afVjYGzzlzGrqd61pqCdoap OIRAS6tnHhq/nuxKtIv+cV7UdmFtP6ZDl+sdcdgLW2KkBDV+y1vOM9R81sx2czC9AScg Z6TiXo5Wlzs96pl2RX5V1c412B0+IE6plsVHW2SeIKAKtqonzZZfgM+DgJvW/+RsMJ0C XPfw==
X-Gm-Message-State: AHYfb5gOWat3z9Rf94eP4Hq0TdpHY493v8Y6xGuLYudJEDtb3unruGrs tBt0NIZ98MtLiEbXeNqua3WS7ZggXA==
X-Received: by 10.37.172.72 with SMTP id r8mr7983960ybd.38.1502308580453; Wed, 09 Aug 2017 12:56:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.52.79 with HTTP; Wed, 9 Aug 2017 12:56:19 -0700 (PDT)
In-Reply-To: <5e20388a-a6dd-691d-feeb-8f5363119c0c@nostrum.com>
References: <CAKKJt-cd2-tS=3QnvRcsDKcZ8=o5Z98wUr-=tp8OeP9J1M0M8g@mail.gmail.com> <4622.1502292425@obiwan.sandelman.ca> <CAKKJt-fxhFnnK3T2nVj2bD=Ve7z6L0oJFjYFqBb59TusJDwFzQ@mail.gmail.com> <1250df52-b5b3-4f71-bab1-790d156af1e9@nostrum.com> <CA+9kkMC4yWGptsTxhQgHQp4mRppMfpXdw_ZLz47Sgyyb=przDQ@mail.gmail.com> <5e20388a-a6dd-691d-feeb-8f5363119c0c@nostrum.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 9 Aug 2017 14:56:19 -0500
Message-ID: <CAKKJt-fuw+KOUxpN0+6B2XiBS3XUFPw9A5gxpekNzQV468kj-A@mail.gmail.com>
Subject: Re: BCP 10 Update, adding an IAOC Advisor to the Nominating Committee
To: Robert Sparks <rjsparks@nostrum.com>
Cc: Ted Hardie <ted.ietf@gmail.com>, IETF <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, NomCom-Discussion <ietf-nomcom@ietf.org>
Content-Type: multipart/alternative; boundary="f403045eb43047fa2205565779f4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/q78lh7TARXjLV4p6FLxCL8-rMzU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 19:56:24 -0000

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

Revectoring to the ietf-nomcom list, which is intended for conversations
like this ...

On Wed, Aug 9, 2017 at 2:17 PM, Robert Sparks <rjsparks@nostrum.com> wrote:

>
>
> On 8/9/17 1:59 PM, Ted Hardie wrote:
>
> On Wed, Aug 9, 2017 at 11:48 AM, Robert Sparks <rjsparks@nostrum.com>
> wrote:
>
>> Spencer -
>>
>> The attempt to avoid the term liaison is not working well for me.
>>
>> I think the biggest thing making you want to avoid that term are the
>> requirements on liaisons to oversee process as you call out in the
>> document. Instead of trying to to refashion terms, why don't you just
>> change things so that it is explicit that only the IAB, IESG, and ISOC
>> liaisons have that duty. Then you won't run into trouble with the "other
>> unrepresented organizations" text you quote.
>>
>> You can make it clear that for the IESG and IAB, seated members are
>> required. Any other body can delegate outside its membership.
>>
>> That _seems_ to me to be a more straightforward adjustment. What am I
>> missing?
>>
> There's at least one other potential shift: removing the IAOC liaison from
> the list of liaisons who might serve as replacement Nomcom chair.  If you
> remove that and the other process duties, it's not clear why it is useful
> to call two different sets of responsibilities by the same name.  You can
> do it, of course, as long as you've specified it.  But I don't personally
> see much of an advantage.
>
> My take is that we want the IAOC job or its successor to eventually by
> folks with specific skills in financial oversight, program management, and
> community relations.  Having the IAOC rep be able to explain those tasks to
> a Nomcom is very valuable, and I support getting this formalized.  I care
> about that much more than what we call it.
>
> I think the thing that's bothering me is that the current proposal still
> leaves the unintended trouble if the "Any committee member may propose the
> addition of a liaison" is exercised.
>

Yes, and that's borked.

I'm a tiny bit loath to turn this draft into a "liaison responsibilities
cleanup" draft, although Robert correctly points out that if we wanted to
clean up the liaison responsibilities, we would have changes to make.

If this draft continues to be about an advisor, I'd be happy to address the
liaison responsibilities in another draft. of course.

<rant>

When we have text in BCPs that is rarely/never executed, we don't look at
it very often. You'd be impressed at the list of people who told me they
didn't realize what all the liaison responsibilities are. I won't embarrass
the ones who told me that, and who have previously served as liaison (so,
subject to those responsibilities) without noticing that, but I can confirm
that *I* didn't notice them, in 2011 as the IAB liaison to the Nomcom :-)

That text doesn't age any better than error-path code that doesn't get
triggered for a very long time, of course.

But I digress.

</rant>


> If you strip away all the rationalization text, the change in Spencer's
> current document reduces to "Hey future nomcoms - it would be a good idea
> if you found an advisor that can talk to you about the IAOC, and the
> current IAOC might be a good body to ask to help you find one". I don't
> object to that. Perhaps the rationalization is a distraction?
>

It's only there to explain why this role isn't a liaison. If the role
becomes a liaison, the rationalization text would, of course, go away.


> But the rationalization part also argues that we want to say "If you think
> you want a liaison from some other body, you might want to look closely at
> asking for an advisor instead."
>

One could make the case that "Any committee member may propose the addition
of a non-voting liaison" is also borked.

Of course, I don't know why that  text is there in the first place. It's
also in RFC 3777, and in RFC 2727, which means it was added after RFC 2282
was published in 1998.  So I wonder if this was intended to prevent a
problem I don't know about?

Thanks again for the feedback. It's helpful.

Spencer

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

<div dir=3D"ltr">Revectoring to the ietf-nomcom list, which is intended for=
 conversations like this ...<div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">On Wed, Aug 9, 2017 at 2:17 PM, Robert Sparks <span dir=3D"ltr">=
&lt;<a href=3D"mailto:rjsparks@nostrum.com" target=3D"_blank">rjsparks@nost=
rum.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF"><span class=3D"gmail-">
    <p><br>
    </p>
    <br>
    <div class=3D"gmail-m_6117404204876653354moz-cite-prefix">On 8/9/17 1:5=
9 PM, Ted Hardie wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">On Wed, Aug 9, 2017 at 11:48 AM, Robert Sparks <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@nostrum.com" target=3D"_blank">=
rjsparks@nostrum.com</a>&gt;</span>
        wrote:<br>
        <div class=3D"gmail_extra">
          <div class=3D"gmail_quote">
            <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
              <div bgcolor=3D"#FFFFFF">
                <p>Spencer -</p>
                <p>The attempt to avoid the term liaison is not working
                  well for me.</p>
                <p>I think the biggest thing making you want to avoid
                  that term are the requirements on liaisons to oversee
                  process as you call out in the document. Instead of
                  trying to to refashion terms, why don&#39;t you just
                  change things so that it is explicit that only the
                  IAB, IESG, and ISOC liaisons have that duty. Then you
                  won&#39;t run into trouble with the &quot;other unreprese=
nted
                  organizations&quot; text you quote.</p>
                <p>You can make it clear that for the IESG and IAB,
                  seated members are required. Any other body can
                  delegate outside its membership.</p>
                <p>That _seems_ to me to be a more straightforward
                  adjustment. What am I missing?</p>
              </div>
            </blockquote>
            <div>There&#39;s at least one other potential shift: removing
              the IAOC liaison from the list of liaisons who might serve
              as replacement Nomcom chair.=C2=A0 If you remove that and the
              other process duties, it&#39;s not clear why it is useful to
              call two different sets of responsibilities by the same
              name.=C2=A0 You can do it, of course, as long as you&#39;ve
              specified it.=C2=A0 But I don&#39;t personally see much of an
              advantage.<br>
              <br>
            </div>
            <div>My take is that we want the IAOC job or its successor
              to eventually by folks with specific skills in financial
              oversight, program management, and community relations.=C2=A0
              Having the IAOC rep be able to explain those tasks to a
              Nomcom is very valuable, and I support getting this
              formalized.=C2=A0 I care about that much more than what we ca=
ll
              it.<br>
            </div>
          </div>
        </div>
      </div>
    </blockquote></span>
    I think the thing that&#39;s bothering me is that the current proposal
    still leaves the unintended trouble if the &quot;Any committee member m=
ay
    propose the addition of a liaison&quot; is exercised.<br></div></blockq=
uote><div><br></div><div>Yes, and that&#39;s borked.=C2=A0</div><div><br></=
div><div>I&#39;m a tiny bit loath to turn this draft into a &quot;liaison r=
esponsibilities cleanup&quot; draft, although Robert correctly points out t=
hat if we wanted to clean up the liaison responsibilities, we would have ch=
anges to make.=C2=A0</div><div><br></div><div>If this draft continues to be=
 about an advisor, I&#39;d be happy to address the liaison responsibilities=
 in another draft. of course.</div><div><br></div><div>&lt;rant&gt;</div><d=
iv><br></div><div>When we have text in BCPs that is rarely/never executed, =
we don&#39;t look at it very often. You&#39;d be impressed at the list of p=
eople who told me they didn&#39;t realize what all the liaison responsibili=
ties are. I won&#39;t embarrass the ones who told me that, and who have pre=
viously served as liaison (so, subject to those responsibilities) without n=
oticing that, but I can confirm that *I* didn&#39;t notice them, in 2011 as=
 the IAB liaison to the Nomcom :-)</div><div><br></div><div>That text doesn=
&#39;t age any better than error-path code that doesn&#39;t get triggered f=
or a very long time, of course.</div><div><br></div><div>But I digress.</di=
v><div><br></div><div>&lt;/rant&gt;</div><div>=C2=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div bgcolor=3D"#FFFFFF">If you strip away=
 all the rationalization text, the change in
    Spencer&#39;s current document reduces to &quot;Hey future nomcoms - it=
 would
    be a good idea if you found an advisor that can talk to you about
    the IAOC, and the current IAOC might be a good body to ask to help
    you find one&quot;. I don&#39;t object to that. Perhaps the rationaliza=
tion
    is a distraction? </div></blockquote><div><br></div><div>It&#39;s only =
there to explain why this role isn&#39;t a liaison. If the role becomes a l=
iaison, the rationalization text would, of course, go away.</div><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor=3D"=
#FFFFFF">But the rationalization part also argues that we want to say &quot=
;If you
    think you want a liaison from some other body, you might want to
    look closely at asking for an advisor instead.&quot;</div></blockquote>=
<div><br></div><div>One could make the case that &quot;<span style=3D"color=
:rgb(0,0,0);font-size:13.3333px">Any committee member may propose the addit=
ion of a non-voting=C2=A0</span><span style=3D"color:rgb(0,0,0);font-size:1=
3.3333px">liaison&quot;</span>=C2=A0is also borked.</div><div><br></div><di=
v>Of course, I don&#39;t know why that=C2=A0 text is there in the first pla=
ce. It&#39;s also in RFC 3777, and in RFC 2727, which means it was added af=
ter RFC 2282 was published in 1998.=C2=A0 So I wonder if this was intended =
to prevent a problem I don&#39;t know about?</div><div><br></div><div>Thank=
s again for the feedback. It&#39;s helpful.</div><div><br></div><div>Spence=
r</div></div></div></div>

--f403045eb43047fa2205565779f4--


From nobody Wed Aug  9 13:09:51 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F83513247E for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 13:09: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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IvxLSKbHOHJt for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 13:09:47 -0700 (PDT)
Received: from mail-pg0-x230.google.com (mail-pg0-x230.google.com [IPv6:2607:f8b0:400e:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50682132476 for <ietf@ietf.org>; Wed,  9 Aug 2017 13:09:47 -0700 (PDT)
Received: by mail-pg0-x230.google.com with SMTP id v77so32151237pgb.3 for <ietf@ietf.org>; Wed, 09 Aug 2017 13:09:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=vR1NSzSJWxZNUDHN/mgLD7A7hqUmLNeHolpg0zLNkKw=; b=MbxfL6fK5wVlfj5ni55HvriIkbyxwBgoOjAJZur41AlDc4TJKmTTjDE6+9MdXg7wk2 edLnc4qxfeHh6XWYcJGuFxSRxMgTt0tfGkv4zcN3588uHw+qF2Cevqesu6AR8gSIEpCL MfqLweS1mhlse/W4zVySDmTSDIil9DNq9OPgaaBUMCW1gouK57mMf8F3lakcOvVCjm42 zJVWZWukzt1znJbwZtpaBy9sKrPCxGqNSkvIkkDqWdZMWXVLIjInT2fGL1whmWEfur8O VWqzeYStm/NIzFiFd+ngGx6btQuBpnBCdy0DuVc7eD1Ht/fJUAX1sUV9OBl1HLnZbF2h XKAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=vR1NSzSJWxZNUDHN/mgLD7A7hqUmLNeHolpg0zLNkKw=; b=V0z7sMlninhcvm/yXDNM/9NKhlfJNsMKgBt3mp6fLDA/fCZwFCk99PxvhZozPwO6Z2 ByQuCClNwwwaAaUr74z8fW4SPEHKqBpoRRYFCnWQtO8MBjKRWa5QKxHy74JEsocH3mWz PlfzVT5P3AcOciRIcemULLKfI4nZYqUkyPWK7GAiB4YJkzHVFA95BF04l4NlS05WasAn C2cSq9cRKVJBulyVr91c2wsHPwjihh7mARZphT9pM5rsk2EQ+EZqW40Ipz9kyoeAbC4f vS/vm0pBKeInbr1WF++Xlr4LrIAa44UPZitL/bitnTmUoRE5IfFwCyDrkhZvsn+AP8ce erkQ==
X-Gm-Message-State: AHYfb5gt2zYiVcQAHx38v0qxmrkY8kgYhyOro6B3aGqTQymJSU44H0pY rnqfkPROvGnjiW7g
X-Received: by 10.98.32.65 with SMTP id g62mr9337412pfg.125.1502309386729; Wed, 09 Aug 2017 13:09:46 -0700 (PDT)
Received: from ?IPv6:2406:e007:521f:1:28cc:dc4c:9703:6781? ([2406:e007:521f:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 78sm8661728pft.123.2017.08.09.13.09.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Aug 2017 13:09:45 -0700 (PDT)
Subject: Re: In Search of a Revised Notewell
To: Mehmet Ersue <mersue@gmail.com>, "'Andrew G. Malis'" <agmalis@gmail.com>,  'Spencer Dawkins at IETF' <spencerdawkins.ietf@gmail.com>
Cc: 'IETF' <ietf@ietf.org>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <c9c759cd-2d56-1367-4e42-644b83f46f13@gmail.com> <017c01d310ec$90c78f00$4001a8c0@gateway.2wire.net> <D5B07EA1.7F830%lee@asgard.org> <CAKKJt-cuexnMgnFYxKPX8oRidjCTL5oAZmR+c1UnRT8awG5M5A@mail.gmail.com> <CAA=duU3dGXT50HMGorpzN8Fpyje98DW0A+=s-Pacqk3KfOXaYg@mail.gmail.com> <00de01d31131$226ec1f0$674c45d0$@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <e150fe3a-cac9-b401-1d57-a26840fb5703@gmail.com>
Date: Thu, 10 Aug 2017 08:09:47 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <00de01d31131$226ec1f0$674c45d0$@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W0RktYcJkA4E-Hl6dSCLyTvCo28>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 20:09:49 -0000

On 10/08/2017 05:01, Mehmet Ersue wrote:
> Without knowing the URL one can always download the current version of =
Note Well slide from:
>=20
> WG Chair=E2=80=99s Page / Meeting Tools /  Note Well (PPT <https://www.=
ietf.org/wg/documents/note-well.ppt> )

But https://www.ietf.org/wg/documents/note-well.odp is 404.

If the Note Well referred to BCP78 and BCP79, we wouldn't have had this c=
onfusion.

    Brian


From nobody Wed Aug  9 13:13:31 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4259413247E for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 13:13:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nIt5_A5nrgv0 for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 13:13:27 -0700 (PDT)
Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8C42132476 for <ietf@ietf.org>; Wed,  9 Aug 2017 13:13:26 -0700 (PDT)
Received: by mail-yw0-x22b.google.com with SMTP id p68so46871716ywg.0 for <ietf@ietf.org>; Wed, 09 Aug 2017 13:13:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CJsFKFsCEnLLfSH4eRm/7gwuZg51sCo+RE4A5DOotRE=; b=hYl1TJrguHQczTEj9yZfZP4e/cdI3Ty4Z8qsmS3dzUl/kycAgz6F3t0KLqZe/TgkUb cSMf83YJjEGs7RW/7tlp6nukMDurOcrD/6nz2kkRDKY90+i+h1pfcBPsCBzuWLo4ad3J 09QN9zI2n83+iJuPO/dg+9D2fMIwhjEYNBUePUaHKSS8aSHeo9ZTjIDTOFVyjs+e/OvR xrbi3FXY7g7h5N3HDFT+w1//J9VGMzUIwsrSmOsWNluerHPFAKH0sSawf7/+9RJsMmX3 QUcGrHrztDMfBdeHPxd5y5h4XPmVilue5PobGVkxVppxP0D2fCV1fCHOmiSlQhoDuhx6 Z99A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CJsFKFsCEnLLfSH4eRm/7gwuZg51sCo+RE4A5DOotRE=; b=YQ/BDgi8LWSZoNLluBd+s0BxClQ2I/Kss1R+EhHrkLeu0rgayj4cDgSkGGkAFQ1qnI I5G+jIvqxYF+gL0kPjKAfS2CsQLo+O2yguNIv01tBVFv82An4oxSIQB66N1kaHMwAv5q etSJ36aKGPgXr2AlVq0vcDI4HmrU9GNXWlkErvYhjYuwek+X0Ar6ec6194fKzmjWZzIx US4jmK6IWYhtd4hF7s1/479wgDUAEU/pzQi3EQGPijtYoYpl5+sfOc8CBStMR4jgmQPq NCZKvMMFkZpy8FCVuIJUVVu6qKFjgUaC9DJ278fJoKL2/LZB+iHtYGv6kQs5MpwbtnS7 eY/w==
X-Gm-Message-State: AHYfb5gpbnxDGmCdTW51LFrVr1l4Ndz9PDsH2WSSPnm/FPRF9MQHuW58 qYdJZDe+N8xYcWPHcwp8ArPqaIuUiTHp
X-Received: by 10.13.210.67 with SMTP id u64mr7743701ywd.218.1502309606109; Wed, 09 Aug 2017 13:13:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.52.79 with HTTP; Wed, 9 Aug 2017 13:13:25 -0700 (PDT)
In-Reply-To: <e150fe3a-cac9-b401-1d57-a26840fb5703@gmail.com>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <c9c759cd-2d56-1367-4e42-644b83f46f13@gmail.com> <017c01d310ec$90c78f00$4001a8c0@gateway.2wire.net> <D5B07EA1.7F830%lee@asgard.org> <CAKKJt-cuexnMgnFYxKPX8oRidjCTL5oAZmR+c1UnRT8awG5M5A@mail.gmail.com> <CAA=duU3dGXT50HMGorpzN8Fpyje98DW0A+=s-Pacqk3KfOXaYg@mail.gmail.com> <00de01d31131$226ec1f0$674c45d0$@gmail.com> <e150fe3a-cac9-b401-1d57-a26840fb5703@gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 9 Aug 2017 15:13:25 -0500
Message-ID: <CAKKJt-ewgkWkPP=QO_Ds9WUDngO8Q9eo7q7Q3Zvk3tv55ygaqw@mail.gmail.com>
Subject: Re: In Search of a Revised Notewell
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Mehmet Ersue <mersue@gmail.com>, "Andrew G. Malis" <agmalis@gmail.com>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a114e7e306a3bcf055657b662"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5QxZb_QVVJ_t9pPR7kzfrtfRhUM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 20:13:29 -0000

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

On Wed, Aug 9, 2017 at 3:09 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 10/08/2017 05:01, Mehmet Ersue wrote:
> > Without knowing the URL one can always download the current version of
> Note Well slide from:
> >
> > WG Chair=E2=80=99s Page / Meeting Tools /  Note Well (PPT <
> https://www.ietf.org/wg/documents/note-well.ppt> )
>
> But https://www.ietf.org/wg/documents/note-well.odp is 404.
>

Harumph ...


> If the Note Well referred to BCP78 and BCP79, we wouldn't have had this
> confusion.


Not one second before Brian's e-mail appeared in my inbox, I sent a private
reply to someone else that said

"I GUESS I get that it's worth specifying exactly what people had available
to note well (so, specific RFCs), but the benefit of knowing what the Note
Well actually said in any meeting seems outweighed by the cost of someone
agreeing to an outdated version of the BCP, because that's what the chairs
put on the slides."

Harumph.

Spencer

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Wed, Aug 9, 2017 at 3:09 PM, Brian E Carpenter <span dir=3D"ltr">&lt;<a =
href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpe=
nter@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex"><span class=3D"gmail-">On 10/08/2017 05:01, Mehmet Ersue wro=
te:<br>
&gt; Without knowing the URL one can always download the current version of=
 Note Well slide from:<br>
&gt;<br>
</span>&gt; WG Chair=E2=80=99s Page / Meeting Tools /=C2=A0 Note Well (PPT =
&lt;<a href=3D"https://www.ietf.org/wg/documents/note-well.ppt" rel=3D"nore=
ferrer" target=3D"_blank">https://www.ietf.org/wg/<wbr>documents/note-well.=
ppt</a>&gt; )<br>
<br>
But <a href=3D"https://www.ietf.org/wg/documents/note-well.odp" rel=3D"nore=
ferrer" target=3D"_blank">https://www.ietf.org/wg/<wbr>documents/note-well.=
odp</a> is 404.<br></blockquote><div><br></div><div>Harumph ...</div><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">If the Note W=
ell referred to BCP78 and BCP79, we wouldn&#39;t have had this confusion.</=
blockquote><div><br></div><div>Not one second before Brian&#39;s e-mail app=
eared in my inbox, I sent a private reply to someone else that said</div><d=
iv><br></div><div>&quot;<span style=3D"font-size:12.8px">I GUESS I get that=
 it&#39;s worth specifying exactly what people had available to note well (=
so, specific RFCs), but the benefit of knowing what the Note Well actually =
said in any meeting seems outweighed by the cost of someone agreeing to an =
outdated version of the BCP, because that&#39;s what the chairs put on the =
slides.&quot;</span></div><div><span style=3D"font-size:12.8px"><br></span>=
</div><div><span style=3D"font-size:12.8px">Harumph.=C2=A0</span></div><div=
><span style=3D"font-size:12.8px"><br></span></div><div><span style=3D"font=
-size:12.8px">Spencer</span></div></div></div></div>

--001a114e7e306a3bcf055657b662--


From nobody Wed Aug  9 14:29:40 2017
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C032132339 for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 14:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HQ4RjHDEORcx for <ietf@ietfa.amsl.com>; Wed,  9 Aug 2017 14:29:37 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04C8D132191 for <ietf@ietf.org>; Wed,  9 Aug 2017 14:29:37 -0700 (PDT)
Received: by mail-oi0-x229.google.com with SMTP id e124so73888848oig.2 for <ietf@ietf.org>; Wed, 09 Aug 2017 14:29:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=MrKriD0A6a8/or/uk10fH7eVn6TjYb+Rk/V7CPZV6/8=; b=Z0vfT4zqb70/QAFxCS6tOjKHv47vc+VshS1kjsAIgMJHZrN09rOenQ+lewdLpZCD6a W9KU524A//b8qwEd9g+pxqO3G0Yfvfkox9sWFopv85En1Eyd/f1GexKUUdYSFiXEgdB1 059IXatJW6jD4+I8DECan0Mk0J8up1ZuwH3q7RMu3mO07+oxLjPDT0glot1Es5K4gdMm RM03xP2jgAxCvxYIuuJFEFN+6PPeBlFtghfO7shMOYfM9ZQeA5bsP66HymkfwJRTFS79 kCsxpCNphR3InTbq1cKYVu9hBjKbNt46vYT827y3Df39SqT3PM0yrgY56XEPizsg0xXT r/CQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=MrKriD0A6a8/or/uk10fH7eVn6TjYb+Rk/V7CPZV6/8=; b=h+1blRRopdUU0KkCpn4UinCAstJ+z2H31qk1bOCredeFcZgjrqa5SLwQkA+MDi+6rg spVWiZoHQggfXheL3mg+UmvO4va4kKqf5NMdkNIfEWfFtwZ802qhd7hdgU8ZnPfYfu8O 2tYqzw1igQCdozu0j+hlINgcxQ/OIiz6wHqrQ42I8gmEsB4EIuP9AExzB42ZtiEkPjMo i7BHn94qL73l4KVs01tQaBu9Ojqlq/hQo0+4/NMXHr6J6GprQ922XNMltGkdzHODj8X3 HrKLhMrfqVayB53GxHqptDJtGIGk1fwtdv7RqBMZPJ6ESdDXWefgWt6KLpo8w9+90AQT YyiQ==
X-Gm-Message-State: AHYfb5j1F7VfBOSfw7+2CWVSfrpydkmnLxZolgowYVieirQ/gSQVl/Jh 8b74rPl4qVNTQE4tx58U1Y9iGvlAeQ==
X-Received: by 10.202.194.139 with SMTP id s133mr10329381oif.222.1502314176353;  Wed, 09 Aug 2017 14:29:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.232.34 with HTTP; Wed, 9 Aug 2017 14:29:15 -0700 (PDT)
In-Reply-To: <e150fe3a-cac9-b401-1d57-a26840fb5703@gmail.com>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <c9c759cd-2d56-1367-4e42-644b83f46f13@gmail.com> <017c01d310ec$90c78f00$4001a8c0@gateway.2wire.net> <D5B07EA1.7F830%lee@asgard.org> <CAKKJt-cuexnMgnFYxKPX8oRidjCTL5oAZmR+c1UnRT8awG5M5A@mail.gmail.com> <CAA=duU3dGXT50HMGorpzN8Fpyje98DW0A+=s-Pacqk3KfOXaYg@mail.gmail.com> <00de01d31131$226ec1f0$674c45d0$@gmail.com> <e150fe3a-cac9-b401-1d57-a26840fb5703@gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 9 Aug 2017 17:29:15 -0400
Message-ID: <CAA=duU0ivyWd+ofu-BM9N-35aN48g03i1UT5b5txxjF7se9v2w@mail.gmail.com>
Subject: Re: In Search of a Revised Notewell
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Mehmet Ersue <mersue@gmail.com>,  Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113d32acd29edb055658c60a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LMUvMgaZWjgwvyBNjZVYTTe2sbI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 21:29:39 -0000

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

Brian,

I don=E2=80=99t use the pre-prepared slide, I prefer to copy and paste the =
text
from the official online Note Well page. That way you don=E2=80=99t have to=
 worry
about the pre-prepared slide accidentally being out of date, slide
formatting issues (font, background, etc.), and such.

I=E2=80=99m happy to leave it to the people who know much more about such i=
ssues
than I to decide whether the BCPs, RFCs, or both should be referenced.

Cheers,
Andy


On Wed, Aug 9, 2017 at 4:09 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 10/08/2017 05:01, Mehmet Ersue wrote:
> > Without knowing the URL one can always download the current version of
> Note Well slide from:
> >
> > WG Chair=E2=80=99s Page / Meeting Tools /  Note Well (PPT <
> https://www.ietf.org/wg/documents/note-well.ppt> )
>
> But https://www.ietf.org/wg/documents/note-well.odp is 404.
>
> If the Note Well referred to BCP78 and BCP79, we wouldn't have had this
> confusion.
>
>     Brian
>
>

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

<div dir=3D"ltr">Brian,<div><br></div><div>I don=E2=80=99t use the pre-prep=
ared slide, I prefer to copy and paste the text from the official online No=
te Well page. That way you don=E2=80=99t have to worry about the pre-prepar=
ed slide accidentally being out of date, slide formatting issues (font, bac=
kground, etc.), and such.</div><div><br></div><div>I=E2=80=99m happy to lea=
ve it to the people who know much more about such issues than I to decide w=
hether the BCPs, RFCs, or both should be referenced.</div><div><br></div><d=
iv>Cheers,</div><div>Andy</div><div><br></div></div><div class=3D"gmail_ext=
ra"><br><div class=3D"gmail_quote">On Wed, Aug 9, 2017 at 4:09 PM, Brian E =
Carpenter <span dir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.c=
om" target=3D"_blank">brian.e.carpenter@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"><span class=3D"">On 10/08/2017 05:01, Mehmet=
 Ersue wrote:<br>
&gt; Without knowing the URL one can always download the current version of=
 Note Well slide from:<br>
&gt;<br>
</span>&gt; WG Chair=E2=80=99s Page / Meeting Tools /=C2=A0 Note Well (PPT =
&lt;<a href=3D"https://www.ietf.org/wg/documents/note-well.ppt" rel=3D"nore=
ferrer" target=3D"_blank">https://www.ietf.org/wg/<wbr>documents/note-well.=
ppt</a>&gt; )<br>
<br>
But <a href=3D"https://www.ietf.org/wg/documents/note-well.odp" rel=3D"nore=
ferrer" target=3D"_blank">https://www.ietf.org/wg/<wbr>documents/note-well.=
odp</a> is 404.<br>
<br>
If the Note Well referred to BCP78 and BCP79, we wouldn&#39;t have had this=
 confusion.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=C2=A0 =C2=A0 Brian<br>
<br>
</font></span></blockquote></div><br></div>

--001a113d32acd29edb055658c60a--


From nobody Thu Aug 10 00:35:30 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C78E13262F for <ietf@ietfa.amsl.com>; Thu, 10 Aug 2017 00:35:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level: 
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DiyAGQNl6DYZ for <ietf@ietfa.amsl.com>; Thu, 10 Aug 2017 00:35:26 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0131.outbound.protection.outlook.com [104.47.1.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C55FC13262E for <ietf@ietf.org>; Thu, 10 Aug 2017 00:35:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=8Gzs3ZXZNnu2r2+u7Qu4WCx+elOFHN2gagREX0nc7Zk=; b=U4y3LKgjlV//WX2/w2akV87gI0nTpxf4poIweOrfD5E/2QeD1y6PNgBhWBmj5bEGP5rc1iPkrNBb3tbTO6CRTckfjgIF8wrDVdxMGymVu8C7wC+A86PTQPJyQ9sRXc4XzZAWMmFwuk8U0QKQ5CH/RpDo29yKac+C7CQxqHtsrvQ=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com; 
Received: from pc6 (86.176.20.38) by HE1PR07MB1561.eurprd07.prod.outlook.com (2a01:111:e400:7a2d::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1341.9; Thu, 10 Aug 2017 07:35:22 +0000
Message-ID: <00e901d311aa$94d25080$4001a8c0@gateway.2wire.net>
From: "tom p." <daedulus@btconnect.com>
To: "Mehmet Ersue" <mersue@gmail.com>, "'Andrew G. Malis'" <agmalis@gmail.com>, "'Spencer Dawkins at IETF'" <spencerdawkins.ietf@gmail.com>
Cc: "'IETF'" <ietf@ietf.org>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <c9c759cd-2d56-1367-4e42-644b83f46f13@gmail.com> <017c01d310ec$90c78f00$4001a8c0@gateway.2wire.net> <D5B07EA1.7F830%lee@asgard.org> <CAKKJt-cuexnMgnFYxKPX8oRidjCTL5oAZmR+c1UnRT8awG5M5A@mail.gmail.com> <CAA=duU3dGXT50HMGorpzN8Fpyje98DW0A+=s-Pacqk3KfOXaYg@mail.gmail.com> <00de01d31131$226ec1f0$674c45d0$@gmail.com>
Subject: Re: In Search of a Revised Notewell
Date: Thu, 10 Aug 2017 08:24:15 +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: [86.176.20.38]
X-ClientProxiedBy: HE1PR0502CA0024.eurprd05.prod.outlook.com (2603:10a6:3:e3::34) To HE1PR07MB1561.eurprd07.prod.outlook.com (2a01:111:e400:7a2d::11)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: d86c2abf-82b7-4340-703c-08d4dfc25bfd
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254152)(300000503095)(300135400095)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:HE1PR07MB1561; 
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1561; 3:dqBEnnTJw03DPA9yge57k1Jp8ZHgglyWfpFksKMQ3GthDNT/OX31I/bcFmLgRVp7K11Wmtoo4MvDUSaWwVvz2aiObucg+Sz0Z9XBl6gPTH8ldvc2k/dXgZ2fvrh/Bly/qVFPkBH1lcJEsMOjYjumLz4sbYfNs/YDXS3wQED7R9y8f4tKzBZ/fkA8MnevunyeMllaBm713AkQgJyY7+IPB//wj0VmhgWAvzRQn84MKIeh/lECLEXjrT/66GT2BROc; 25:55lzX7AbDuWcUHJ1uNwIDTOPoAlTJAY98crMqN0WiH/ZIfnkxp63o5IfhWlRlXdc9I5qzWoaBrp6zeYPb0/4bT3rjEdIrH7s6AHx38MhkcFZsYztcqDdtvWCi+maIz1GtmCB5jvSo0kZyhXJQSQ/IJl1l32OXBut4bRD9ytQvKA5LqvUoYnkNru2alWvfe6C3uGe3EAHC0EWbrV0qYucpSOXd9anjEjEgFLrNRywSlQbujdQr+0WXQ5fd4V5UP9/D75nzze1WPh6/0OtesfJIVJ6dZyFVPNEltxbUaT0KzxCrGb1mWCnTvV/TkR8iQPmW07iDWLbOVLSYWbcCHRRgw==; 31:raVwDDXvWnwS3Dz1cWF8yYf/JgrY7aQVerfAAFoFotDjXCxuBO0VKIFC/4L5fnfDHNKly6ZU8XIxsDIezJbkWt/5kIdbohxek5cdltpWWhnQytyJi9Eaups4vl1DTQieK9SJzcU8qVQFwHYs9cwAhLf7Tj9iIpkO5aQiL9b/7KYZ0mye2RTZwIVNnicOhLK1XY0eidY+H2h9k4xJcpzKhsrpqrXqywtHJKSD97q/G9M=
X-MS-TrafficTypeDiagnostic: HE1PR07MB1561:
X-Exchange-Antispam-Report-Test: UriScan:(178726229863574)(120809045254105);
X-Microsoft-Antispam-PRVS: <HE1PR07MB1561288D0380A7ABD1775B05C6880@HE1PR07MB1561.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(100000703101)(100105400095)(93006095)(93001095)(3002001)(10201501046)(6041248)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123558100)(20161123564025)(20161123560025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:HE1PR07MB1561; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:HE1PR07MB1561; 
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1561; 4:2mhFvX9kaEqmpzmCIDDlHPA4LHPENmlNJXyAyAO6m29wUmp0jZKtszjLDp4vERULGdKbcn86Y0wLDPcTa44IRothWfqMvXfREGRdclOvoKVB3rDyMjy5kU4kReQ2emHO1AzeKslW56urYgKzHZFMxBSkh0sCVHL0WSTpWZeR0E3tfiQ0ajkfuUSuNfoGY++YH9JggJVP+eSPBQMon/2mgQENxq8/A0JoXFQVyDWUJe2p5SY3pV68NmuaUGe1Q+d4YPC8w0H+qKSYH7uSPAL6LO3NaEb6O53lXNqsnDK0HbhNu14wrrV7sNsDfjyO64cW9UbsM7FxbL5XqbuR4YOrzA==
X-Forefront-PRVS: 03950F25EC
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(7370300001)(6009001)(39410400002)(39840400002)(39860400002)(39850400002)(39450400003)(39400400002)(13464003)(199003)(24454002)(189002)(377454003)(305945005)(7736002)(7350300001)(44736005)(6486002)(189998001)(50466002)(81816999)(53546010)(66066001)(14496001)(478600001)(25786009)(2870700001)(81686999)(42186005)(4326008)(1556002)(1456003)(76176999)(81156014)(86362001)(6496005)(9686003)(2906002)(106356001)(61296003)(105586002)(97736004)(50986999)(47776003)(4720700003)(23676002)(53936002)(81166006)(5660300001)(966005)(38730400002)(6116002)(33646002)(68736007)(6246003)(6666003)(62236002)(3846002)(229853002)(50226002)(44716002)(101416001)(6306002)(8676002)(84392002)(93886004)(116806002)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR07MB1561; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtIRTFQUjA3TUIxNTYxOzIzOlR4c3R0bUtYY1ovWUZwTHdKN0dSY3VBaVZW?= =?utf-8?B?bmY4dndKTmlZSVZHb2VLQmRwZnlMbTZ6eHFsR0VDaUV3dForV2IvV2dqa3Np?= =?utf-8?B?dUhOOTBMdXFITnFXbkNHUGJ4Nk1ZcTJDMUI2UGN1WHhvTVV6VVJxOStTc2xv?= =?utf-8?B?T2R1RU1HanZQclNwOUNNMUVnSTZieS9tcVhMeGdxY3VKSTFnUmVqdU5tdVRF?= =?utf-8?B?OGNsUEd3RDNmN0p0L3dyYXkwUjl3cVZSbG81OWVveXI2NFdUcjlaZEphVUpN?= =?utf-8?B?dmp6NlpPNGlSbUtYWGErSFlBMk04T3ErS2paMFdjWExrcWhJOVR4UWcrNkd4?= =?utf-8?B?N0VrcVozZm02SjRxVlpiZWhtRmlLbXZHSEl0MzhsY3FYN2lEYlA1RDY1QTht?= =?utf-8?B?dks0V2IvVEMydUdVWlJJQkRsbDBwSTBSeHdyNDczUlYydURLUVhGQWZWWi9l?= =?utf-8?B?a0E4bnVQU2FvL1ZTSXhJUlorK3ZxeUZQSGZ5VlZCTE9rNnI5S09kMHpIUm41?= =?utf-8?B?RUJyUlVLUDREbk11dGRIcVA5ZlZiaWVSUER2ZmMzNFJPbFdBVTBPK1NzeFRr?= =?utf-8?B?TEVnbENLcStEcnFGcm4vdFFWZDhjWk5rNjR1NVNDZGJaRDdUWW8wZWxQYUdF?= =?utf-8?B?L1pzZjFOM01heUoyTCtHVFhJUWl6WkkzbWZYMWxUdDZ2VGpoZ2c4R3VtZytC?= =?utf-8?B?YktLTFVFUzlFdEJrZERyemVaV0UrR2dLdGE1eEVITWJGVUZQcUJYazZSd05x?= =?utf-8?B?RmhhdTdrSmt1UTlFMGVPN1NwNzBCN1FlMldGOStRLzBQWEpIV3pxVHRaUVJm?= =?utf-8?B?M2VuOVdSaDRlSjVXMnhITitTSjgxRnFRdFZQMGJBQ2FmZi9mQXZuNmVic0w1?= =?utf-8?B?cmVkS053dHB5M1MyZW9JWnZDQjdLRjFLNlBrRkJvMmJrejQvek5HQWhEYmhY?= =?utf-8?B?YXhNTWRjRHJzRUZoNlhQeVNFWDJhdlpvNis1NDI4Ry9wTjk1OVdLU3o2eTA1?= =?utf-8?B?TTkwaEdNa3VtSHVkckt4UWJEUkdGZXZPckpnbmlnb0cwV2R5ZlB0V0NGdk9E?= =?utf-8?B?MG9GenFrMXhoSm5rTWxWSVRsR1hLeHRNNGFEbTZCRWJ0ZEV1YTljcG8wa3R2?= =?utf-8?B?MVFQUjFVbk55ZmdTMXE1TkFIQVdSYjdkemxSUjFuN2k3UnlOa1RwUEJBZG5V?= =?utf-8?B?dGZXRGVJRVhDeWJzbUFxVmd1MEVpd2dUU2FpMm1GdUhrZldHVE1YRkZqUldP?= =?utf-8?B?QVBmcjdTVDFRZjZmcTJiYXBsdEw5OHFZZzdrajJXS0tXK2E2SkhvdVFFcGtn?= =?utf-8?B?MEpXQ2RhK2FESkJCV3UrT1c2OWtLOEhpUUoyNG5LM2lUZTJGVDNIVlUzWFZn?= =?utf-8?B?KzF6Q0ZNRHZqd1IyZlNVbkh0S0phSjVOTDhCbTBEM1ZPSGhzTE1ES2JVSldz?= =?utf-8?B?TjFWc1dxcS8xQzFXRjdIUzNXYXpHeER4dlIvRndwR0NMeVlpd3I4LzZ1QW1v?= =?utf-8?B?dTFCa05nM2dHWnU0MUx6TnpEcndvc3NHcWh6TVFHazkvcHMzNGlMMVNVK3FE?= =?utf-8?B?OE1iTEEzTE9sUUdTZWppMyt1RFozSmUzOURQVXFZQ253QTJDazBjOWd3WWlH?= =?utf-8?B?dUZqU015QUFua3duL1NhMWtnOUE3cUlRMVI5bGlHOHBQakpkVFlraTRtdm5o?= =?utf-8?B?WFFIakx0bGxiM2paM3YwUWs0U2NLVWJBbUZGcjErczQwYng3UHUxMGYvYlhO?= =?utf-8?B?eHlHWUVzMlZHR1J2bElGZnJJR1N6Q3p1WUJBUkk0RzQvdzA1QlRHQ0JzNFM0?= =?utf-8?B?QmlrYlZ2UWt1ZVRMQmUwRlhUbjMvRkZneXhlb0UvcVU0YTFBM0NXZnlHSVZn?= =?utf-8?B?QWI1ZjFOWklSRmxSZlA5SU9SQU1GMHd5QjZOREVlSUZ0U21sL296UEZRWVJ4?= =?utf-8?B?ZHRrSmtYOWdaUHJEekNwNHB6U3JjbGZrM2pySWRBbU5sWWptS3E3R2k4M1BY?= =?utf-8?B?d29YamlxVnN1Z0Q4Vm55ZnVUcEtMdnM3bWFFZkgwdXlwN2tieGZUMzNScHIz?= =?utf-8?B?aE9uSVVoMDRReG1tTzN5dHBtRnFSVnRuSjJQbzUxYjQ5WnhseVliTmxXYnRQ?= =?utf-8?B?S2FFOVQwSEoxb1dvSEpMMWY0Yng3cTdvUUZ0T3dtTlcva1lLOWsxSVlGK29J?= =?utf-8?B?eC9LWUdDTW1XSGt3aFBCTUxUYkxXZHRxeFQvSFRPdkFjTGhBWWMzNW1kZ3Mw?= =?utf-8?Q?tF9vh2Gze0jWy9eqMY?=
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1561; 6:Wg7pdWYkCZHQza+5qr3whEsSt+ZbkHYH996gv7ADOuN+i4HRBZaQix7klI73HXNcQVY+OwP3agd8vEWWFnWlCwfr8g58h14DLtm7Hx+y/QNseMjibct23CUqNWWAB7NsoyqHKq41F5gmY6lviTf4HOmLGDEurSIiuQKwY7Ub/JKnvNgMsLIrrZrpQ51z7GhHz23HoMKNtFxcRPrl3C+a5jQ+si0+0lvyxRJNLKJmjxWeOqcSRi2dLFbiKHaZaEeGGarDHdcH6u2ybRnPI4CvKfrzQTlozX/ghiUafczUE5cfbUA4JvlSdPrV1L6p+fS/ukEeor5p+YP4+xqyV5tYLw==; 5:j/G31NNUK/wVO02/vKf4VqNPxWgjmx0GpHTtRlwYR+gHym1EAo/ClgT2Jr+CXY+DRBymHeOkX1m+1+JmIO/CtCHbRs5MYHEe4YErlRN+xHVM1y8xeKolrX0BDeuoQ4fCTKSXXlTGaZcflFotlnl9Wg==; 24:bbfNRqSXilcv1d3pHVJAdq4A9WKvM/e59940hNDU098N5EUYpZwZFyAhFF57ormJsTDfecsfJC4/+C/tEzAixK9qzBNddlSPPZ6ijWJGAuE=; 7:yQ8Hr1LqOrBlUaDQ87go3ElDuf16N2dCaC1Ii+R2SIAyeYj+BSMCPkNN7OUusz8Y03aWP0QFSrkQYMo8nNRhh5Koa4ZAZrwjVTlODbFRdwvURVgoPFlcXhM+ekENnV7bg5qIHEm0ri8/37P04AkGyJPj/FM27uYGKBAxUBdtmsKTi3KKBK71/WWfg/mtAUuKZNC/5bKihrr4T02q1TFQPLqrqMQ1+uPVpIqO6CX+kOo=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 Aug 2017 07:35:22.1380 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB1561
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ePFHLLGq1fN2BU7bdvwBkMZXhGU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 10 Aug 2017 07:35:29 -0000

----- Original Message -----
From: "Mehmet Ersue" <mersue@gmail.com>
To: "'Andrew G. Malis'" <agmalis@gmail.com>; "'Spencer Dawkins at IETF'"
<spencerdawkins.ietf@gmail.com>
Cc: "'IETF'" <ietf@ietf.org>
Sent: Wednesday, August 09, 2017 6:01 PM

Without knowing the URL one can always download the current version of
Note Well slide from:

WG Chair’s Page / Meeting Tools /  Note Well (PPT
<https://www.ietf.org/wg/documents/note-well.ppt> )

<tp>

Yes, if you are a WG Chair at an IETF Meeting:-)  The e-mail participant
would not know to do this AFAICT (and I am subscribed to the ipr mailing
list!); and even now, the e-mail participant who does not track the IETF
list would still probably not know of a revised Notewell..

Tom Petch

I agree, copying regularly is easier than checking the content.



Cheers,

Mehmet



From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Andrew G. Malis
Sent: Wednesday, August 9, 2017 5:36 PM
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: IETF <ietf@ietf.org>
Subject: Re: In Search of a Revised Notewell



Spencer,



Before each meeting I always recopy the Note Well text into my chairs
slides, because there just might be a change in the wording, and it’s
easier to copy than to check.



Cheers,

Andy



On Wed, Aug 9, 2017 at 11:14 AM, Spencer Dawkins at IETF
<spencerdawkins.ietf@gmail.com <mailto:spencerdawkins.ietf@gmail.com> >
wrote:

Under the category of "mistakes were made" ...



On Wed, Aug 9, 2017 at 7:59 AM, Lee Howard <lee@asgard.org
<mailto:lee@asgard.org> > wrote:



On 8/9/17, 4:33 AM, "ietf on behalf of tom p." <ietf-bounces@ietf.org
<mailto:ietf-bounces@ietf.org>  on
behalf of daedulus@btconnect.com <mailto:daedulus@btconnect.com> >
wrote:

>
>
>Clearly the WG Chairs have been given a briefing but is this something
>that those of us who only contribute via e-mail should be aware of? If
>so, how?  I cannot recall seeing anything on WG lists about this, until
>I started reading the minutes, since January 2016.

I recall seeing an announcement from Scott Bradner that certain IPR
rules
had been updated. I don’t remember seeing a broad community announcement
with the banner, “The Note Well advisory has changed.”

https://www.ietf.org/about/note-well.html

I presume that the new version was used in meeting registration.



I assume so as well, although of course I didn't notice at the time.



True confession - I did the slides for TSVAREA at IETF 99, and didn't
think to change the RFC number on my Note Well slide.



It's not like I didn't know about RFC 8179. According to
https://datatracker.ietf.org/doc/rfc8179/ballot/, I BALLOTED YES WITH
COMMENTS on it. But that didn't translate into me changing my Note Well
slide ... making the change to my IETF 100 slide deck now.



So, Tom, thanks for asking about this, and helping the rest of us catch
up.



Spencer, who apparently isn't getting enough caffeine in his diet Pepsi,
in spite of many valiant efforts to do so ...





From nobody Thu Aug 10 00:42:24 2017
Return-Path: <mahend.negi@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45DE413250B for <ietf@ietfa.amsl.com>; Thu, 10 Aug 2017 00:42:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tJxGDXSivWjr for <ietf@ietfa.amsl.com>; Thu, 10 Aug 2017 00:42:19 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66A5D132632 for <ietf@ietf.org>; Thu, 10 Aug 2017 00:42:19 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id l82so53779455ywc.2 for <ietf@ietf.org>; Thu, 10 Aug 2017 00:42:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to;  bh=MwnUWx7rCsSr7hyVNXj6eX0aKomPbw9wzphkxUkvQac=; b=p220Z5X6kuTT/h67gWTyGiQvhBx1Q17CurPect9j7KcVM0G3M0Hn/iplrzw4Mh+4NR oswmcMTnBtgOYkbGR+PYPvQsn5tymbcZtSvhdYrXoUGTLue1wvlxSUStBJUL6jtSpQg5 9CNAO7dm1fBm86loGA2EhAgWGTJapEV2nR1Dxx7fFA5lsfgTD/gTpqQKaCFVBcOXatBH 3sHy74D4NJ94TAmmFVxzflO9G6zQzmw5frlhIpd8zll6gd3PK/r5wFSCmU9SBUK8+hQp f/fWWTQHu4Sbbr7SBf76ZPWmWZqnIFQVNItiLJEytGRx8ReH07GKobRpaBcKfpPuG+PU aYBg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=MwnUWx7rCsSr7hyVNXj6eX0aKomPbw9wzphkxUkvQac=; b=DvgmDf8020ZW90511NU5Ut2LFaNiAvxgp3HAnbH5JjagLPdksKg2GFkjHJCb7kkgzk 17xjR/DqaTbGT2kbOUMV7c/UP0ife5yp7Dx/LVvdObiaVx2VvtWW0rdiBfv9YTDr0nOi QuNhDyq1sRJNXGdiuMtNpUeD9gb8Jaws5gPUrYZbSGgv4qQltQz6VpcLXrsKs8FygmUA FnUb6yj0TMNZ8JaTApe79D84q3L9nTC0IZ5XuZKSYrmJj4rVID981tyMQmD+EkPwOCr4 CnsqMk45sjSXfBvRbeD+EqyBusZ/aBdcNfuc3Gm5IwFKEKUBu6HefLmRjEygKhcqwfbg Kp4A==
X-Gm-Message-State: AHYfb5j/CAcSSeUPWBcJb7gUSeQ0yGN6vBmHyui4JpoNIsJcs628Asc0 PU6E++XJxmFSzl9JJVwEs2koMftPYg==
X-Received: by 10.37.244.67 with SMTP id p3mr6340284ybe.33.1502350938593; Thu, 10 Aug 2017 00:42:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.177.5 with HTTP; Thu, 10 Aug 2017 00:42:18 -0700 (PDT)
Received: by 10.37.177.5 with HTTP; Thu, 10 Aug 2017 00:42:18 -0700 (PDT)
In-Reply-To: <150230783857.3511.3361008716547750022.idtracker@ietfa.amsl.com>
References: <150230783857.3511.3361008716547750022.idtracker@ietfa.amsl.com>
From: Mahendra Negi <mahend.negi@gmail.com>
Date: Thu, 10 Aug 2017 13:12:18 +0530
Message-ID: <CAHbbxhz01HZ9v_KP=vUVDo59UH+aDEwLoWkPWrTA-K6q6wi_Jg@mail.gmail.com>
Subject: Re: [Pce] Last Call: <draft-ietf-pce-pce-initiated-lsp-10.txt> (PCEP Extensions for PCE-initiated LSP Setup in a Stateful PCE Model) to Proposed Standard
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary="f403045dbe0205e12205566156b1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/coq2IRDwgcGgQu1FB7NtrCyIICU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 10 Aug 2017 07:42:22 -0000

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

Dear Authors,

I have 3 points as below:

1.
Section 4.1:
It doesn't mention about U Bit.

(MN)  I assume U Bit MUST be set to set initiate-capability (I Bit),
suggest to update the same.

2.
(MN) During LSP synchronization LSP Initiate SHOULD be avoided, as this may
lead to other issues, if this can be mentioned in the draft..

3.
Section 5.3:
The only exception to this rule is for LSPs for which the State Timeout
Interval timer is running (see Section 6
<https://tools.ietf.org/html/draft-ietf-pce-pce-initiated-lsp-10#section-6>).

Section 6:
A PCE (either the original or one of its backups) sends a PCInitiate
message, including just the SRP and LSP objects, and carrying the PLSP-ID
of the LSP it wants to take control of. If the PCC receives a PCInitiate
message with a PLSP-ID pointing to an orphaned PCE- initiated LSP, then it
MUST redelegate that LSP to the PCE.

(MN)  Why is this exception required? Why can't PCE just takes control of
this orphan LSP? As the orphan LSP may be used by service, why to interrupt?
Moreover new initiate request may have different destination and different
attributes.
Or please kindly explain if my undestanding is not correct.

Regards,
Mahendra
Huawei Tech.

The IESG has received a request from the Path Computation Element WG (pce)
to
consider the following document: - 'PCEP Extensions for PCE-initiated LSP
Setup in a Stateful PCE Model'
  <draft-ietf-pce-pce-initiated-lsp-10.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 2017-08-23. 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


   The Path Computation Element Communication Protocol (PCEP) provides
   mechanisms for Path Computation Elements (PCEs) to perform path
   computations in response to Path Computation Clients (PCCs) requests.

   The extensions for stateful PCE provide active control of
   Multiprotocol Label Switching (MPLS) Traffic Engineering Label
   Switched Paths (TE LSP) via PCEP, for a model where the PCC delegates
   control over one or more locally configured LSPs to the PCE.  This
   document describes the creation and deletion of PCE-initiated LSPs
   under the stateful PCE model.





The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-pce-pce-initiated-lsp/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-pce-pce-initiated-lsp/ballot/


No IPR declarations have been submitted directly on this I-D.




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

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

<p dir=3D"ltr">Dear Authors,</p>
<p dir=3D"ltr">I have 3 points as below:</p>
<p dir=3D"ltr">1.<br>
Section 4.1:<br>
It doesn&#39;t mention about U Bit.</p>
<p dir=3D"ltr">(MN)=C2=A0 I assume U Bit MUST be set to set initiate-capabi=
lity (I Bit), suggest to update the same.</p>
<p dir=3D"ltr">2.<br>
(MN) During LSP synchronization LSP Initiate SHOULD be avoided, as this may=
 lead to other issues, if this can be mentioned in the draft..</p>
<p dir=3D"ltr">3.<br>
Section 5.3:<br>
The only exception to this rule is for LSPs for which the State Timeout Int=
erval timer is running (see <a href=3D"https://tools.ietf.org/html/draft-ie=
tf-pce-pce-initiated-lsp-10#section-6">Section 6</a>). <br>
Section 6:<br>
A PCE (either the original or one of its backups) sends a PCInitiate messag=
e, including just the SRP and LSP objects, and carrying the PLSP-ID of the =
LSP it wants to take control of. If the PCC receives a PCInitiate message w=
ith a PLSP-ID pointing to an orphaned PCE- initiated LSP, then it MUST rede=
legate that LSP to the PCE. </p>
<p dir=3D"ltr">(MN)=C2=A0 Why is this exception required? Why can&#39;t PCE=
 just takes control of this orphan LSP? As the orphan LSP may be used by se=
rvice, why to interrupt?<br>
Moreover new initiate request may have different destination and different =
attributes. <br>
Or please kindly explain if my undestanding is not correct.</p>
<p dir=3D"ltr">Regards,<br>
Mahendra<br>
Huawei Tech.<br>
</p>
<div class=3D"gmail_quot&lt;blockquote class=3D" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><br>
The IESG has received a request from the Path Computation Element WG (pce) =
to<br>
consider the following document: - &#39;PCEP Extensions for PCE-initiated L=
SP<br>
Setup in a Stateful PCE Model&#39;<br>
=C2=A0 &lt;draft-ietf-pce-pce-initiated-<wbr>lsp-10.txt&gt; as Proposed Sta=
ndard<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits final=
<br>
comments on this action. Please send substantive comments to the<br>
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2017-08=
-23. Exceptionally, comments may be<br>
sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In eith=
er case, please retain the beginning of<br>
the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
<br>
=C2=A0 =C2=A0The Path Computation Element Communication Protocol (PCEP) pro=
vides<br>
=C2=A0 =C2=A0mechanisms for Path Computation Elements (PCEs) to perform pat=
h<br>
=C2=A0 =C2=A0computations in response to Path Computation Clients (PCCs) re=
quests.<br>
<br>
=C2=A0 =C2=A0The extensions for stateful PCE provide active control of<br>
=C2=A0 =C2=A0Multiprotocol Label Switching (MPLS) Traffic Engineering Label=
<br>
=C2=A0 =C2=A0Switched Paths (TE LSP) via PCEP, for a model where the PCC de=
legates<br>
=C2=A0 =C2=A0control over one or more locally configured LSPs to the PCE.=
=C2=A0 This<br>
=C2=A0 =C2=A0document describes the creation and deletion of PCE-initiated =
LSPs<br>
=C2=A0 =C2=A0under the stateful PCE model.<br>
<br>
<br>
<br>
<br>
<br>
The file can be obtained via<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-pce-pce-initiated-ls=
p/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<wbr>=
doc/draft-ietf-pce-pce-<wbr>initiated-lsp/</a><br>
<br>
IESG discussion can be tracked via<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-pce-pce-initiated-ls=
p/ballot/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.or=
g/<wbr>doc/draft-ietf-pce-pce-<wbr>initiated-lsp/ballot/</a><br>
<br>
<br>
No IPR declarations have been submitted directly on this I-D.<br>
<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
Pce mailing list<br>
<a href=3D"mailto:Pce@ietf.org">Pce@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pce" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/pce</a><br>
</div>

--f403045dbe0205e12205566156b1--


From nobody Thu Aug 10 06:13:55 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CF3F1321EC for <ietf@ietfa.amsl.com>; Thu, 10 Aug 2017 06:13:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YETI0g239fbK for <ietf@ietfa.amsl.com>; Thu, 10 Aug 2017 06:13:52 -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 557B61321B0 for <ietf@ietf.org>; Thu, 10 Aug 2017 06:13:52 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dfnHb-000NaD-3W; Thu, 10 Aug 2017 09:13:51 -0400
Date: Thu, 10 Aug 2017 09:13:43 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Mehmet Ersue <mersue@gmail.com>, "'Andrew G. Malis'" <agmalis@gmail.com>, 'Spencer Dawkins at IETF' <spencerdawkins.ietf@gmail.com>
cc: 'IETF' <ietf@ietf.org>
Subject: Re: In Search of a Revised Notewell
Message-ID: <2EE76E9283DA06BF1BC7E833@PSB>
In-Reply-To: <e150fe3a-cac9-b401-1d57-a26840fb5703@gmail.com>
References: <84780978-8FBD-4B8F-9ACF-3AC7D744C2EC@vigilsec.com> <c9c759cd-2d56-1367-4e42-644b83f46f13@gmail.com> <017c01d310ec$90c78f00$4001a8c0@gateway.2wire.net> <D5B07EA1.7F830%lee@asgard.org> <CAKKJt-cuexnMgnFYxKPX8oRidjCTL5oAZmR+c1UnRT8awG5M5A@mail.gmail.com> <CAA=duU3dGXT50HMGorpzN8Fpyje98DW0A+=s-Pacqk3KfOXaYg@mail.gmail.c om> <00de01d31131$226ec1f0$674c45d0$@gmail.com> <e150fe3a-cac9-b401-1d57-a26840fb5703@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/64eqdyzHD_NRlZaE4N4iwB-ExCc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 10 Aug 2017 13:13:54 -0000

--On Thursday, August 10, 2017 08:09 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> On 10/08/2017 05:01, Mehmet Ersue wrote:
>> Without knowing the URL one can always download the current
>> version of Note Well slide from:
>> 
>> WG Chair's Page / Meeting Tools /  Note Well (PPT
>> <https://www.ietf.org/wg/documents/note-well.ppt> )
> 
> But https://www.ietf.org/wg/documents/note-well.odp is 404.
> 
> If the Note Well referred to BCP78 and BCP79, we wouldn't have
> had this confusion.

Maybe, and maybe our "stable" references are not stable enough.
I would certainly prefer to go in that direction.   However, my
guess is that it would need to not only refer to them but to say
explicitly that it is the reader's responsibility to find the
most recent version and then provide a reference for where to
look that up.  But that is, again, a guess -- IANAL, and the
Note Well is not a random piece of general advice.  It is an
attempt to bind people to particular legal restrictions by
virtue of seeing or hearing about it (maybe with a few
exceptions like the registration procedure in which people are
required to read and then sign off before moving further).    I
gather that how effective it might be if challenged is a matter
of disagreement among lawyers and perhaps jurisdictions and I
continue to hope that whatever is there, how we use it, and how
precise it needs to be are subjects on which the IESG and IETF
Trust are getting good enough advice to be willing to bet the
effectiveness of the policies to which it points, even in edge
cases, on that advice.

    john




From nobody Thu Aug 10 16:17:12 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6251D132701; Thu, 10 Aug 2017 16:17:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-pce-pce-initiated-lsp.all@ietf.org, pce@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-ietf-pce-pce-initiated-lsp-10
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150240703036.8476.2109418125181500710@ietfa.amsl.com>
Date: Thu, 10 Aug 2017 16:17:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/K3jS9DewwqVPK0cFhKhLbp_9qVo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 10 Aug 2017 23:17:10 -0000

Reviewer: Joel Halpern
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-pce-pce-initiated-lsp-10
Reviewer: Joel Halpern
Review Date: 2017-08-10
IETF LC End Date: 2017-08-23
IESG Telechat date: 2017-08-31

Summary: This document as a Proposed Standard RFC

Major issues: N/A

Minor issues: N/A

Nits/editorial comments:
    It seems odd to have a message for the creation or deletion of an LSP
    called an LSP Initiate Request.



From nobody Thu Aug 10 21:53:24 2017
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D4A313207A for <ietf@ietfa.amsl.com>; Thu, 10 Aug 2017 21:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level: 
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B8qqXYKUbyGc for <ietf@ietfa.amsl.com>; Thu, 10 Aug 2017 21:53:20 -0700 (PDT)
Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.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 B45DC132031 for <ietf@ietf.org>; Thu, 10 Aug 2017 21:53:20 -0700 (PDT)
Received: from pps.filterd (m0098410.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v7B4mjQJ007940 for <ietf@ietf.org>; Fri, 11 Aug 2017 00:53:19 -0400
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by mx0a-001b2d01.pphosted.com with ESMTP id 2c91w31bbg-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 11 Aug 2017 00:53:18 -0400
Received: from localhost by e32.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, 10 Aug 2017 22:53:18 -0600
Received: from b03cxnp07029.gho.boulder.ibm.com (9.17.130.16) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 10 Aug 2017 22:53:16 -0600
Received: from b03ledav006.gho.boulder.ibm.com (b03ledav006.gho.boulder.ibm.com [9.17.130.237]) by b03cxnp07029.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v7B4rFhG9634276 for <ietf@ietf.org>; Thu, 10 Aug 2017 21:53:15 -0700
Received: from b03ledav006.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 78C8AC6042 for <ietf@ietf.org>; Thu, 10 Aug 2017 22:53:15 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b03ledav006.gho.boulder.ibm.com (Postfix) with ESMTPS id 5B359C603C for <ietf@ietf.org>; Thu, 10 Aug 2017 22:53:15 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v7B4rEF3010343 for <ietf@ietf.org>; Fri, 11 Aug 2017 00:53:14 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v7B4rCuu010315 for ietf@ietf.org; Fri, 11 Aug 2017 00:53:13 -0400
From: narten@us.ibm.com
Date: Fri, 11 Aug 2017 00:53:12 -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-GCONF: 00
x-cbid: 17081104-0004-0000-0000-000012BB2CD5
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00007523; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000219; SDB=6.00900611; UDB=6.00450901; IPR=6.00680812;  BA=6.00005522; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00016640; XFM=3.00000015; UTC=2017-08-11 04:53:17
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17081104-0005-0000-0000-000080A2CC12
Message-Id: <201708110453.v7B4rCuu010315@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-08-11_03:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=13 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1706020000 definitions=main-1708110078
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ACwpBhO4eZBE3TL7C_XXHFKrmGE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 11 Aug 2017 04:53:23 -0000

Total of 43 messages in the last 7 days.
 
script run at: Fri Aug 11 00:53:07 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 11.63% |    5 | 12.42% |    67549 | spencerdawkins.ietf@gmail.com
  9.30% |    4 | 10.70% |    58242 | agmalis@gmail.com
  6.98% |    3 | 10.28% |    55941 | rjsparks@nostrum.com
  4.65% |    2 |  5.95% |    32379 | daedulus@btconnect.com
  2.33% |    1 |  7.51% |    40880 | worley@ariadne.com
  4.65% |    2 |  3.37% |    18321 | housley@vigilsec.com
  4.65% |    2 |  3.23% |    17552 | brian.e.carpenter@gmail.com
  4.65% |    2 |  3.09% |    16786 | dave@cridland.net
  4.65% |    2 |  2.93% |    15928 | mcr+ietf@sandelman.ca
  2.33% |    1 |  4.78% |    26001 | stewart.bryant@gmail.com
  2.33% |    1 |  3.78% |    20580 | ted.ietf@gmail.com
  2.33% |    1 |  3.77% |    20488 | pat.thaler@broadcom.com
  2.33% |    1 |  3.41% |    18558 | mersue@gmail.com
  2.33% |    1 |  2.77% |    15060 | vaibhavsinghacads@gmail.com
  2.33% |    1 |  2.67% |    14541 | mahend.negi@gmail.com
  2.33% |    1 |  2.22% |    12072 | tjc@ecs.soton.ac.uk
  2.33% |    1 |  2.19% |    11917 | narten@us.ibm.com
  2.33% |    1 |  1.80% |     9785 | sob@sobco.com
  2.33% |    1 |  1.47% |     8014 | john-ietf@jck.com
  2.33% |    1 |  1.44% |     7809 | christer.holmberg@ericsson.com
  2.33% |    1 |  1.38% |     7501 | yaronf.ietf@gmail.com
  2.33% |    1 |  1.32% |     7175 | ben@nostrum.com
  2.33% |    1 |  1.32% |     7157 | amy.yemin@huawei.com
  2.33% |    1 |  1.30% |     7088 | lee@asgard.org
  2.33% |    1 |  1.04% |     5672 | mjethanandani@gmail.com
  2.33% |    1 |  1.02% |     5546 | dromasca@gmail.com
  2.33% |    1 |  1.01% |     5491 | jmh@joelhalpern.com
  2.33% |    1 |  0.95% |     5167 | ietf-secretariat@ietf.org
  2.33% |    1 |  0.90% |     4878 | rsalz@akamai.com
--------+------+--------+----------+------------------------
100.00% |   43 |100.00% |   544078 | Total


From nobody Fri Aug 11 09:53:26 2017
Return-Path: <wendellcnicolas.on@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACA05126B6E for <ietf@ietfa.amsl.com>; Fri, 11 Aug 2017 09:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZIbgEZxf6Unc for <ietf@ietfa.amsl.com>; Fri, 11 Aug 2017 09:53:23 -0700 (PDT)
Received: from mail-oi0-x243.google.com (mail-oi0-x243.google.com [IPv6:2607:f8b0:4003:c06::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 093B0131D2F for <ietf@ietf.org>; Fri, 11 Aug 2017 09:53:23 -0700 (PDT)
Received: by mail-oi0-x243.google.com with SMTP id b130so3824464oii.3 for <ietf@ietf.org>; Fri, 11 Aug 2017 09:53:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=2eZdFXdeHDC5OE/4RCwEA0imS+jNRrcHfvaaqu3aHsQ=; b=ZQl5B7ickpCBSb7ZnSOCtVAJ8/5glHbk0UNEc57C0frAYSmYwJQwDTbUmqeHtmCdfm 9VXLgFJr7I1IMzGGpATHvkcx2ozgMaRgVPbchTdFjDYtUYk/pvIpmpwQk1mv7ju3I4w1 sA954pMumCQHZuPnO1F+nLsaNQ5saqOgugqP/tjUBrUoqhSR5QvEXnvL26e6QzPFJ7Ql BfqHT4VfF+5kag0VQ3HhWigjkNJ7WjoM1H+x1u0F4cpY8Axa1PCSZ0+do+tIjqmv/1qk 15tJVf5/ovNUSqXuMWeG0CohiwgLBq8wDslRZfGA77ImVuf9lUxkUurj4SuCYUslPn4q d47w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=2eZdFXdeHDC5OE/4RCwEA0imS+jNRrcHfvaaqu3aHsQ=; b=gGtEDK+BmvOetjbSlMmjenE1HWB6DXcLCAhy3StYxyJUHs/7GB+Qyv0AL8vH6JFE41 w1o3xuWSysfckhIuTNEptRAWYp7yJarFrsIYI+6xM/XEthWxFR9C/not+8mfT9d5AT/R Z8u7PI7mxCd5zTuC4xJj6OjJNvOSrmAEIRGtxtK7GEDzo6FL8P4g8MhIFRPVj5d7F7ZZ WFshyUG2icc6Uecijm7ETh/F2TucYs2AXkHL+U5hUMBWpC7YAoHIw9pUjKEkBCQd03/S 2CzfXmu3pWm1Z5Rlx7nWY519F2GabPBEBnZJNtAVXz0XCP3WF5iQSUi4yDWDgcu9xbut AB0A==
X-Gm-Message-State: AHYfb5itusaFygrRDSK7bmvbbBVMmFbF5kG4D6yo8ZhibYs5DOPsPriE YCHZs62NSOJOTpqiHQu2u23I1CsqYVxD
X-Received: by 10.202.87.129 with SMTP id l123mr19083337oib.119.1502470402066;  Fri, 11 Aug 2017 09:53:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.153.68 with HTTP; Fri, 11 Aug 2017 09:53:21 -0700 (PDT)
From: Wendell Nicolas <wendellcnicolas.on@gmail.com>
Date: Fri, 11 Aug 2017 09:53:21 -0700
Message-ID: <CAA2XyHV5zn-BOA5FwJ91=ps8=aHUhJO7E=dd6K3RTCYD113DDQ@mail.gmail.com>
Subject: Re:
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary="001a113b007499cd3605567d2614"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NJ-iPmmnyUityr25gw6PQ9Y4Z2I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 11 Aug 2017 16:53:25 -0000

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

HELO

--001a113b007499cd3605567d2614
Content-Type: text/html; charset="UTF-8"

<div dir="ltr">HELO</div>

--001a113b007499cd3605567d2614--


From nobody Fri Aug 11 10:41:28 2017
Return-Path: <buhrmi@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA9821324EE for <ietf@ietfa.amsl.com>; Fri, 11 Aug 2017 10:41:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MLzgFEZMJTYp for <ietf@ietfa.amsl.com>; Fri, 11 Aug 2017 10:41:25 -0700 (PDT)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EF071323A8 for <ietf@ietf.org>; Fri, 11 Aug 2017 10:41:25 -0700 (PDT)
Received: by mail-oi0-x236.google.com with SMTP id x3so39734624oia.1 for <ietf@ietf.org>; Fri, 11 Aug 2017 10:41:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=wpGrFZccUzcI0Ls72Mxe2A4PGgQlscA3rv9QKKCwv6o=; b=JCWQ3ftLjNbLqFW47ntb0kFZIY+BbEZxkj4LuOS2KNyK9Q1ydTlJfuYiiqzG2rzqUC CmZfLEaoYQdomCAUSUruw5gBneWc99kWo6AruFx4Pd8aoQZpnkb21TWLOFrxlKwfIn9d vkyqkYeKJvXtqNqQoIRLa6mniAsapjjWIf83sj0UHrLH0W9tbXi98PkVVxUHSMJYG5f7 zTl85IG2OvTum7NrmpzsJFHyBVRplX5X0/I+9JSc12J1JSQQv3h3L8yb5AgpffC2HnS+ GXJU2c72x069nH6gKvoxGXMo4PPMfBztMnJakYMrUpc99Byz179CFAs+ji/xgDTGH7l0 0CYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=wpGrFZccUzcI0Ls72Mxe2A4PGgQlscA3rv9QKKCwv6o=; b=T4datx9kyHAUbrs/9jR19zB70vVwJcKGkzYbSf4MT4uq2Bg4asQjnHSekll8ucx1AT oJ2Ib+oIlmDGF0M44co7tfspR+92OuRJl0IsOyVOonOd6hdFA11ERL6t43AgGgGoSC36 BHe/Vu9hwtJMUoINNIRvJK2eFioVR2n2FlZtkuZOuJ/aTFT75iZTpbAU6HflLGVJ16v1 lEiyZl0S0D+iF8DwrcS+rbA+4ip5lLS6skVTjezp3X7oPRKs0Jb87KJaB7Oliw1++y20 goAbb/PLu9mKmklWbqSYrPCXnkrbE3w4/jGHRR0PJn9hr2jjURVIS853yL1BPdFQlagW 6aqQ==
X-Gm-Message-State: AHYfb5jzN9gHgsprsahKzhnnro/IQq42Pikykd1rlG6WTzLzI1An/lbC fRQeTG+dsjTrRYnt8c5Y2ucPxKciyg==
X-Received: by 10.202.6.195 with SMTP id 186mr19165157oig.263.1502473284581; Fri, 11 Aug 2017 10:41:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.104.17 with HTTP; Fri, 11 Aug 2017 10:41:23 -0700 (PDT)
Received: by 10.74.104.17 with HTTP; Fri, 11 Aug 2017 10:41:23 -0700 (PDT)
In-Reply-To: <CAA2XyHV5zn-BOA5FwJ91=ps8=aHUhJO7E=dd6K3RTCYD113DDQ@mail.gmail.com>
References: <CAA2XyHV5zn-BOA5FwJ91=ps8=aHUhJO7E=dd6K3RTCYD113DDQ@mail.gmail.com>
From: Stefan Buhrmester <buhrmi@gmail.com>
Date: Sat, 12 Aug 2017 02:41:23 +0900
Message-ID: <CANhkrbRhw1Jib-vQtRFdyLhrwsiZx6rc-P28npChUL_141HH9A@mail.gmail.com>
Subject: Re:
To: Wendell Nicolas <wendellcnicolas.on@gmail.com>
Cc: ietf@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c13f9a069833105567dd26d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gFZShlnESxyI3z8XWFPLvxtIpys>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 11 Aug 2017 17:41:27 -0000

--94eb2c13f9a069833105567dd26d
Content-Type: text/plain; charset="UTF-8"

Hi :)

On Aug 12, 2017 01:53, "Wendell Nicolas" <wendellcnicolas.on@gmail.com>
wrote:

> HELO
>

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

<div dir=3D"auto">Hi :)=C2=A0</div><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote">On Aug 12, 2017 01:53, &quot;Wendell Nicolas&quot; &lt;<a=
 href=3D"mailto:wendellcnicolas.on@gmail.com">wendellcnicolas.on@gmail.com<=
/a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
dir=3D"ltr">HELO</div>
</blockquote></div></div>

--94eb2c13f9a069833105567dd26d--


From nobody Fri Aug 11 10:46:01 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCE8B13266B for <ietf@ietfa.amsl.com>; Fri, 11 Aug 2017 10:45: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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cez-e9GkQiaE for <ietf@ietfa.amsl.com>; Fri, 11 Aug 2017 10:45:58 -0700 (PDT)
Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2ACF4132667 for <ietf@ietf.org>; Fri, 11 Aug 2017 10:45:58 -0700 (PDT)
Received: by mail-qt0-x229.google.com with SMTP id 16so25030142qtz.4 for <ietf@ietf.org>; Fri, 11 Aug 2017 10:45:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=JEaLgmrbWThXZQdp1kJXafcpA2QrJ6QSXFZK6FIwjCk=; b=KZ/LhDaADFU9Oyc419hpKs4VLDhevzblwq0fTxNw1XCbH87d0aYYyCniqqciccow3s kZLePD3Lvo2kENNvgLnRUrP39Qu9KXQjXri26pTebet5ByB/p1J7YZLHKW0huVYA9+Q0 KBEyExu3Qdi3pJug0kW9NviB3BNNyf83TrlELca6mr1bySuwST/hT3p50cHRXSfqUDTK Aueo7X3fqD3uF2bNlLjeHrYSXX83c9FEMj7rRu7R2sHlSsUNkfRLA6BSjB0pN6OTXi/3 UuDXNLxO7OWC3D7ldC9OXa6ilTswsODf0pQKI7w2wLqdCx7fgTSYSpqXo/CsZefCgMci XDhA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=JEaLgmrbWThXZQdp1kJXafcpA2QrJ6QSXFZK6FIwjCk=; b=W01ee2xpa4A4CqwrmG7RUeIDEbSMHMlqz7VQCyqytSiHMdmBW+BRBPoo+5P3WEnLO1 r6i0EWUst6433O8HMAz4oBTWctzIetSVpYH8wtp4kFwX/v3aGk/4z1PoHA1eFJDnmdcP THlWeX+Xxctv+zCdLkT/dvT0iBssbNXw6jW0k6PnkzZe/ItVt/ymnYD481aAsRsfyVZa hU18c3S2ZrPZN5qTOiZx/grDvd6uf/wV7haEFB7QuKslBjgISfQha5kjBF7+1OsOLzhn ANdO4O/HvlOqXfel17I22guBWqCi7UcU4EYdwjgh66BabgZLtE3kuqSKy0xgm21jIz/g /WCw==
X-Gm-Message-State: AHYfb5jTIhKycQCQ2zG56q92zYhew1GgKEB2kvcGJtNyHwvAazmkWqPS 2+qiuSns2UKT1F4k
X-Received: by 10.200.56.54 with SMTP id q51mr22551661qtb.338.1502473557333; Fri, 11 Aug 2017 10:45:57 -0700 (PDT)
Received: from cavall.ether.lede.home (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id u16sm914717qtc.81.2017.08.11.10.45.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 Aug 2017 10:45:56 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <29FA842E-E784-412E-9151-ABAA055368B5@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A99808D0-5885-4444-B12D-143DD3410580"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: 
Date: Fri, 11 Aug 2017 13:45:55 -0400
In-Reply-To: <CANhkrbRhw1Jib-vQtRFdyLhrwsiZx6rc-P28npChUL_141HH9A@mail.gmail.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
To: Stefan Buhrmester <buhrmi@gmail.com>
References: <CAA2XyHV5zn-BOA5FwJ91=ps8=aHUhJO7E=dd6K3RTCYD113DDQ@mail.gmail.com> <CANhkrbRhw1Jib-vQtRFdyLhrwsiZx6rc-P28npChUL_141HH9A@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/00Cpv8ax9p1_e2r9YykQxAgXwiA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 11 Aug 2017 17:46:00 -0000

--Apple-Mail=_A99808D0-5885-4444-B12D-143DD3410580
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

On Aug 11, 2017, at 1:41 PM, Stefan Buhrmester <buhrmi@gmail.com> wrote:
> Hi :) 

I think you mean:

501 5.5.4 Empty HELO/EHLO argument not allowed, closing connection.


--Apple-Mail=_A99808D0-5885-4444-B12D-143DD3410580
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;" class="">On Aug 11, 2017, at 1:41 PM, Stefan Buhrmester &lt;<a href="mailto:buhrmi@gmail.com" class="">buhrmi@gmail.com</a>&gt; wrote:<div><blockquote type="cite" class=""><div class=""><div dir="auto" style="font-family: Helvetica; font-size: 18px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Hi :)&nbsp;</div></div></blockquote><br class=""></div><div>I think you mean:</div><div><br class=""></div><div>501 5.5.4 Empty HELO/EHLO argument not allowed, closing connection.<br class=""></div><br class=""></body></html>
--Apple-Mail=_A99808D0-5885-4444-B12D-143DD3410580--


From nobody Fri Aug 11 15:21:20 2017
Return-Path: <huitema@huitema.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0504F1326B1 for <ietf@ietfa.amsl.com>; Fri, 11 Aug 2017 15:21:13 -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_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ke_lXGOKf4n9 for <ietf@ietfa.amsl.com>; Fri, 11 Aug 2017 15:21:11 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 B50161326AC for <ietf@ietf.org>; Fri, 11 Aug 2017 15:21:10 -0700 (PDT)
Received: from xsmtp03.mail2web.com ([168.144.250.223]) by mx18.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1dgIIg-00072o-2C for ietf@ietf.org; Sat, 12 Aug 2017 00:21:08 +0200
Received: from [10.5.2.15] (helo=xmail05.myhosting.com) by xsmtp03.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1dgIId-0000mF-RZ for ietf@ietf.org; Fri, 11 Aug 2017 18:21:00 -0400
Received: (qmail 14990 invoked from network); 11 Aug 2017 22:20:57 -0000
Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.56.42.186]) (envelope-sender <huitema@huitema.net>) by xmail05.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf@ietf.org>; 11 Aug 2017 22:20:57 -0000
From: Christian Huitema <huitema@huitema.net>
To: The IESG <iesg@ietf.org>, secdir@ietf.org, draft-ietf-sfc-nsh.all@ietf.org
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <2ad0274f-3385-136d-794b-082192393ebf@huitema.net>
Date: Fri, 11 Aug 2017 15:20:53 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: SECDIR review of draft-ietf-sfc-nsh-18
X-Originating-IP: 168.144.250.223
X-SpamExperts-Domain: xsmtpout.mail2web.com
X-SpamExperts-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-SpamExperts-Outgoing-Class: unsure
X-SpamExperts-Outgoing-Evidence: Combined (0.19)
X-Recommended-Action: accept
X-Filter-ID: PqwsvolAWURa0gwxuN3S5YEa3T7JuZT23fGO2rGt3ZgTCGhDnudOJ80D1c8rffxrus7BTv7Ss8cH d2IQQuvdbtM+m4WpRRDP6YzwkAPgQJbFuHJrd6q7ImwszS9kW0E9ND46yZLY9QyX+cRXmooQ3hum JwiT+2brWmQlzkLIcXivpIH4ag6BM/+u9ym+BA23Cv81ubRiYxDNJ8r4VI/quIHT3azp2ACbWz9H GkpW4x2miYMFDIGCEmkZ4eVntd8kYOEkjsX7F8KmpUaZQHV+Sf+k51CV8HOoCp+bWB2rXxO2G5Pj 7iQJEmtNUzH3idZ6uMF2OhyCCCV83x+RZrKIj0QqMGQOSwmEPwP4wBzM77N8GvkYGGDFjg9NrmGY yNnXsSjdYwfRhjHqxQXDsBKLpGhWDl86FRLsucalajANCRP6lO4FGen962xgCFRckncKfg1XSK9P 1z/R6plfrFWGyb5pE1hv2y98CU17gG3OzcHeNHk15VolAGHS5rCXQKDym+Gab6cuAPzLi/SdAxlO dgkraHgbbAuZgv0Q6mJ3vUcipz1IT62ZEk6+MmovaufbiR3bHfnMCIEU+nrglojKwMr3vOY18GvB wSXAfWcj236q7PAZDtRV/fbtqwTluR/oNdSMuNhZC3X/nGdDKYyg+1Fotn1TGspRGWfHjmaruO0b XpkevaElTi+sCWwmqxHi+BUHXGjp0J8FpT+J6AFTxj/uBBlDrSTu/iScSDnvxhqkfdoogjfTpZPs zrPFazX6Ic5J+7ODbgBzY3tezkQUvBklgDtVC2Xqa4QCRhTuoCmXPUJkXUk8tGhJsBnmMDbaKcNO SCytRyeT1c4b6jF7f/DKzfOCXnJQjcl9DhaIFtxOL5qi64EWd0pZxWefvs3WRIbZK0lCbLYw/2Y2 Z+15FA==
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yOpivbcHAy-0dGkWpE3tB6OHuJI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 11 Aug 2017 22:21:13 -0000

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the=20
IESG.  These comments were written primarily for the benefit of the=20
security area directors.  Document editors and WG chairs should treat=20
these comments just like any other last call comments.

The summary of this review is a puzzled reviewer. Why was I asked to=20
review this? Why is the IETF even working on such specifications? What
does this have to do with the Internet? And why such disregard
for privacy and security? In any case, this document has significant
issues. It does not explaining where exactly the proposed Network
Service Header would be inserted (MPLS or IPv6?). The security
provisions boil down to lip-service mentions of IPSEC, and that's way
insufficient given the nature of the protocol.

Sometimes you read a document and it gives you a glimpse of an alternate
universe in which the Internet has been replaced by a mad pile-up of
middle boxes. Of course, they will not be called that. Instead, we will
speak of "service functions" providing such essential features as NAT
and deep packet inspection. I suppose that censorship and surveillance
are not desirable key words in marketing brochures, and that metadata
collection and the insertion of adverts are better described in yet to
be published extensions.

As far as I can tell, the so called "Service Function Chaining
Architecture" tries to standardize this pile-up of middleboxes, so that
service providers can procure them from multiple vendors. The draft that
I am reviewing, draft-ietf-sfc-nsh-18, defines a clear-text "network
service header" (NSH) that would inserted between the "transport" used
in the domain and the IPv4 or IPv6 packet itself. Boxes could look at
this header, add metadata to it, and forward it to other boxes along a
"service path". I mentioned IPv4 or IPv6, but there are also provisions
for passing pure NSH information, probably for maintaining the "service
path", or passing Ethernet, MPLS or experimental frames, because why not.=


The specification itself is appropriately baroque, with the header
composed of three components and multiple options, but the basic idea is
to allow different boxes to see the packet so they can read, update and
process the metadata. As far as I can tell, there are no serious attempt
to provide any kind of security or privacy protection except maybe some
basic ingress filtering, which means that the metadata can be observed
by any entity able to tap the path, or can be spoofed by any system
inserted on the path, such as for example a virus infected box. The only
security reference is a short note that deployments "could use IPSEC",
through a token reference to RFC 6071.

When first reading the document, I was under the impression that the
"transport" used in the domain would be some kind of close layer 2
system, MPLS or maybe Ethernet. That would give some assurance that the
collection of middle boxes would be part of a somewhat controlled
domain. It was only the reference to IPSEC that enlightened me. If IPSEC
is plausible, it probably means that the packet would be composed of an
IP header, the SFH, and the original IP payload. So the proposed usage
implies carrying metadata like subscriber information and identification
of content in clear text  over long distance paths. What could possibly
go wrong? And if that was not enough, imagine what an adversary could
achieve by spoofing the service packets.

Of course, the same threats would still apply if the protocol was
strictly carried over layer 2, as several adversaries are quite capable
of snooping and spoofing layer 2 traffic.

Coming at the end of this review, I hesitate between two options. One
would be to just express my disgust, wash my hands, and hope that the
effort will fail under its own weight, maybe after a couple of
catastrophic security failures. The other option is to provide some
advice on how to solve the most blatant issues. In a spirit of
cooperation, I choose the latter, and here is the two steps advice:

The first step to better security and privacy there would be to present
the practical deployment conditions. I could only make guesses, and
that's silly. There should be some kind of diagram explaining how the
SFH is inserted in packets, and where it sits between Ethernet, MPLS and
IP.

The next step is to develop a protection model. Given that the goal of
the architecture is to decorate the packets with sensitive metadata,
there need to be some thinking about who should be able to see it. How
would path encryption like IPSEC be deployed? Should all elements on
path really be able to access all metadata, or should some of it be
further protected?

Please fix that before the document is published.


--=20
Christian Huitema



From nobody Fri Aug 11 17:45:20 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EAE013243E for <ietf@ietfa.amsl.com>; Fri, 11 Aug 2017 17:45:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level: 
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mvFDIbx4BVmu for <ietf@ietfa.amsl.com>; Fri, 11 Aug 2017 17:45:15 -0700 (PDT)
Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19625132412 for <ietf@ietf.org>; Fri, 11 Aug 2017 17:45:15 -0700 (PDT)
Received: by mail-lf0-x232.google.com with SMTP id t128so22170088lff.2 for <ietf@ietf.org>; Fri, 11 Aug 2017 17:45:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=J2mH2wNMmkKCQKoEj2050z/DGRtCaUih5rJ/wOLTXr8=; b=rAvfEFo+ERX/RHuMqGoVOad1aOCdl2VUjaHGJG6guhDdrEc31/hVEykeOpCS5q+mHa IscdHM1xuoK7oYm0h0HvIQfaF6/+mtUcS0uzDnm2aoKWGLFZqtaox153OdSF5HGSzLJw zyRwkDa7nwxbgGda0GRxkiU9ieKML/myNrpMnpxGcxkniDXaotLqRfQWBaWYJbEbtd2w ZRosBhZ2SZldP3YY8ZQw2owcxOVVaSQxep41vjkws1IAnJnRYcx/fBpcIto2x9qZsVpB CuyayHeap6qCX5QunsuUbEqMVv65iZI4pnyg8+owEa2ngAKdl/s4AZqNKOGA4Jmwetef M/ZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=J2mH2wNMmkKCQKoEj2050z/DGRtCaUih5rJ/wOLTXr8=; b=OoK+ugUQ4qxQ6OtKcSecrBY+znXFVCkzwJjA19OD9zcJ5Wu9So875S1YQOfCO/Jxp8 IRUB5Cr70OAZ/q3ycxZc9qkQ8Q+wIvuqkleObbyUoAvabdHn9udyouuZHjT3Pr+Fgp+o GQmzb7tX9ESv3G5iKaQSb/6UMBPQQh1Tm2SQ4BlPlBeDa22xSgraVYRZRQxc7C10rbjZ vjfS3OdLg/tSGkhy3o38IzHWALcw7/OhAgwD3nQmEXsZ8QR4Ba1sSrxNMxOjqGK8/U4U NJGafPvNTE1V+HztudVBDi9dBEwXOuAV/x6lYkRWY9HP4y+QndEYNJheERymjGSjJw40 6bYQ==
X-Gm-Message-State: AHYfb5hn/k13c6hjslIqaKLbnEepBoYGj2LB3F5Y8nzNvThiuIwpLiAP x6BrjQSF1kZeZzsCd8os4NOVRuWfCg==
X-Received: by 10.25.23.212 with SMTP id 81mr5134910lfx.150.1502498713424; Fri, 11 Aug 2017 17:45:13 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.25.142.199 with HTTP; Fri, 11 Aug 2017 17:45:12 -0700 (PDT)
In-Reply-To: <CAKHUCzxcnapaKyMDMMSD9iusqX3q1ucEGd99uG30adB7CkbvsA@mail.gmail.com>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com> <28827.1499886723@dooku.sandelman.ca> <CACZ1GiqmFTzD346x02_gvvFqfm1n-N=xBC01xb0_mEpUa_JYUA@mail.gmail.com> <62FDB3A5-C71A-4B5C-8CD9-94B0EE4DC313@gmail.com> <CAKHUCzy3rzhAHZ3n3KrrLVC6AYG7+obgMJyVA63NfO2=mMU1Wg@mail.gmail.com> <CACZ1GioR14iufKQk_9819ZNc1ewuXG9=EhH3nGBTgmgefy9Xsg@mail.gmail.com> <CAKHUCzxcnapaKyMDMMSD9iusqX3q1ucEGd99uG30adB7CkbvsA@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 11 Aug 2017 20:45:12 -0400
X-Google-Sender-Auth: kpZQwnPCl3Of661zk34Vnvhkj6o
Message-ID: <CAMm+LwgGz6=BzvkH8Q7NSFqxBgkNjZAzn7prYz5jtTqZ3Per=w@mail.gmail.com>
Subject: Re: Need for secured email delegation workflow
To: Dave Cridland <dave@cridland.net>
Cc: vaibhav singh <vaibhavsinghacads@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>,  "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a114102ae16d831055683bebc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VHUT2xJARwo7ca5nBTafJqdZLDg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 12 Aug 2017 00:45:19 -0000

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

On Tue, Aug 8, 2017 at 4:57 PM, Dave Cridland <dave@cridland.net> wrote:

> On 8 August 2017 at 18:25, vaibhav singh <vaibhavsinghacads@gmail.com>
> wrote:
> >
> >
> > On Tue, Aug 8, 2017 at 8:56 PM, Dave Cridland <dave@cridland.net> wrote=
:
> >>
> >> On 14 July 2017 at 15:42, Yoav Nir <ynir.ietf@gmail.com> wrote:
> >> > While it may be OK to share a key with my phone (but too difficult t=
o
> do
> >> > securely in practice), sharing with a delegate is hairy on many
> >> > different
> >> > layers. But still it=E2=80=99s the same issue.
> >>
> >> I think it's all solvable using Proxy Re[en]cryption, but that seems
> >> to be a little fraught with patents at the moment.
> >
> >
> > I am not comfortable with sharing my private key with anyone, be it the
> > proxy user itself. I believe that is a requirement for Proxy
> Reencryption,
> > please correct me if I may have interpreted it wrongly.
> >
>
> You have interpreted it incorrectly.
>
> The proxy holds a key that will change a message encrypted to its
> proxy key into a message encrypted for an authorized key. It cannot
> decrypt the message to plaintext itself.
>
> All quite bleeding edge, all quite patent-encumbered, but look at
> Mathew Green's work for details - he's been researching very heavily
> in this field.


=E2=80=8BProxy re-encryption has been around for 25 years. It is hardly cut=
ting
edge.

There is a patent on the DRM use expiring soon. But the original Blaze
scheme does everything I need. It certainly isn't 'all' encumbered.

It seems to me that the cryptographers got a particular mathematical
property into their head as 'essential' which really isn't if you design
protocols. So I don't need the paired stuff.

I wrote some stuff on this:
http://www.defaultdenysecurity.com/Professional/Patents/Recryption.html

If you know of patent claims on the DH based scheme I describe, please let
me know.

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Au=
g 8, 2017 at 4:57 PM, Dave Cridland <span dir=3D"ltr">&lt;<a href=3D"mailto=
:dave@cridland.net" target=3D"_blank">dave@cridland.net</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><span class=3D"gmai=
l-">On 8 August 2017 at 18:25, vaibhav singh &lt;<a href=3D"mailto:vaibhavs=
inghacads@gmail.com">vaibhavsinghacads@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; On Tue, Aug 8, 2017 at 8:56 PM, Dave Cridland &lt;<a href=3D"mailto:da=
ve@cridland.net">dave@cridland.net</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; On 14 July 2017 at 15:42, Yoav Nir &lt;<a href=3D"mailto:ynir.ietf=
@gmail.com">ynir.ietf@gmail.com</a>&gt; wrote:<br>
&gt;&gt; &gt; While it may be OK to share a key with my phone (but too diff=
icult to do<br>
&gt;&gt; &gt; securely in practice), sharing with a delegate is hairy on ma=
ny<br>
&gt;&gt; &gt; different<br>
&gt;&gt; &gt; layers. But still it=E2=80=99s the same issue.<br>
&gt;&gt;<br>
&gt;&gt; I think it&#39;s all solvable using Proxy Re[en]cryption, but that=
 seems<br>
&gt;&gt; to be a little fraught with patents at the moment.<br>
&gt;<br>
&gt;<br>
&gt; I am not comfortable with sharing my private key with anyone, be it th=
e<br>
&gt; proxy user itself. I believe that is a requirement for Proxy Reencrypt=
ion,<br>
&gt; please correct me if I may have interpreted it wrongly.<br>
&gt;<br>
<br>
</span>You have interpreted it incorrectly.<br>
<br>
The proxy holds a key that will change a message encrypted to its<br>
proxy key into a message encrypted for an authorized key. It cannot<br>
decrypt the message to plaintext itself.<br>
<br>
All quite bleeding edge, all quite patent-encumbered, but look at<br>
Mathew Green&#39;s work for details - he&#39;s been researching very heavil=
y<br>
in this field.</blockquote><div><br></div><div class=3D"gmail_default" styl=
e=3D"font-size:small">=E2=80=8BProxy re-encryption has been around for 25 y=
ears. It is hardly cutting edge.</div><div class=3D"gmail_default" style=3D=
"font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size=
:small">There is a patent on the DRM use expiring soon. But the original Bl=
aze scheme does everything I need. It certainly isn&#39;t &#39;all&#39; enc=
umbered.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></=
div><div class=3D"gmail_default" style=3D"font-size:small">It seems to me t=
hat the cryptographers got a particular mathematical property into their he=
ad as &#39;essential&#39; which really isn&#39;t if you design protocols. S=
o I don&#39;t need the paired stuff.</div><div class=3D"gmail_default" styl=
e=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-=
size:small">I wrote some stuff on this:</div><div class=3D"gmail_default"><=
a href=3D"http://www.defaultdenysecurity.com/Professional/Patents/Recryptio=
n.html">http://www.defaultdenysecurity.com/Professional/Patents/Recryption.=
html</a><br></div><div class=3D"gmail_default"><br></div><div class=3D"gmai=
l_default">If you know of patent claims on the DH based scheme I describe, =
please let me know.</div></div><br></div></div>

--001a114102ae16d831055683bebc--


From nobody Sat Aug 12 03:44:31 2017
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5F8E132638 for <ietf@ietfa.amsl.com>; Sat, 12 Aug 2017 03:44:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LjLfvjQR_Aud for <ietf@ietfa.amsl.com>; Sat, 12 Aug 2017 03:44:27 -0700 (PDT)
Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49D19132586 for <ietf@ietf.org>; Sat, 12 Aug 2017 03:44:27 -0700 (PDT)
Received: by mail-lf0-x230.google.com with SMTP id d17so24726765lfe.0 for <ietf@ietf.org>; Sat, 12 Aug 2017 03:44:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=j3OwfBnBDaOmv8wWHJEdDe5Aw7Su39+00+Gfs0/D2FY=; b=Oby7xdeAsr2edDhqMd/TsCz0mArOh2wAZ7Ma+Oki37DoikNQLKivewawgzSR6YH4BD Oq6TCl4b6FSCabL4qhqGKma/pPJOXsSHOPNiVWCWlNWHxCYNWrW21t3m52+8Hop1VTFM 3aIkIQ8j8F8THyvIdmf2MsbFYTgk6e3uO7Eww=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=j3OwfBnBDaOmv8wWHJEdDe5Aw7Su39+00+Gfs0/D2FY=; b=YXMzH9kDVpIZQOAZ5avrZY6+8rXoSFC440XYQDMaIlRaztIRVhmVXIqmEebvx0+92P ONmCWjrAKcby3EWf+MtIVqh1OwI4Z7ddJgvRWy8qFX45ndGl8ZZE1gpHQyeznuyQzTyo hNsoa0ykpDhsgkK6ipyOcEGoreht52iUZLOwgxsFONd0Rbat2141yQ/oxt6n++n44O3z lDIXPXaXZug5zd0szkJYU8dlboPL1iFoRjm47T1Fn4r/Fl7/WF5gXRIt5W27ZkbuCq8/ C7v7aABajBisDeL8Qmf2/oGnvqjLSAIA+MufscOKX9EtMhamkLWTRss2CfsOkYO3ZU1Z oe2w==
X-Gm-Message-State: AHYfb5h6hW0TacW+zse75cmmRVTrnTBXobKsVwNLWulIlIUqe1ou4ZCr 0HcZWhXpw6ab0p4mk2+G1a0wrxtgqb+c
X-Received: by 10.25.235.200 with SMTP id f69mr5467402lfk.46.1502534665570; Sat, 12 Aug 2017 03:44:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.179.75.130 with HTTP; Sat, 12 Aug 2017 03:44:24 -0700 (PDT)
Received: by 10.179.75.130 with HTTP; Sat, 12 Aug 2017 03:44:24 -0700 (PDT)
In-Reply-To: <CAMm+LwgGz6=BzvkH8Q7NSFqxBgkNjZAzn7prYz5jtTqZ3Per=w@mail.gmail.com>
References: <CACZ1GioM8Oiz5-bkk33MkmxPBwORcoiPGVsBSg3Hn9cti7FHug@mail.gmail.com> <28827.1499886723@dooku.sandelman.ca> <CACZ1GiqmFTzD346x02_gvvFqfm1n-N=xBC01xb0_mEpUa_JYUA@mail.gmail.com> <62FDB3A5-C71A-4B5C-8CD9-94B0EE4DC313@gmail.com> <CAKHUCzy3rzhAHZ3n3KrrLVC6AYG7+obgMJyVA63NfO2=mMU1Wg@mail.gmail.com> <CACZ1GioR14iufKQk_9819ZNc1ewuXG9=EhH3nGBTgmgefy9Xsg@mail.gmail.com> <CAKHUCzxcnapaKyMDMMSD9iusqX3q1ucEGd99uG30adB7CkbvsA@mail.gmail.com> <CAMm+LwgGz6=BzvkH8Q7NSFqxBgkNjZAzn7prYz5jtTqZ3Per=w@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
Date: Sat, 12 Aug 2017 11:44:24 +0100
Message-ID: <CAKHUCzyFLfn1=p+Q+v6q2TRwiahx4ccQMi-v1gwrQDTBJebhMQ@mail.gmail.com>
Subject: Re: Need for secured email delegation workflow
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>, vaibhav singh <vaibhavsinghacads@gmail.com>,  Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary="001a113c58fa01203d05568c1d38"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Cq2GGQ583kUv4r1ve2ZIgZQGBAk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 12 Aug 2017 10:44:30 -0000

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

On 12 Aug 2017 01:45, "Phillip Hallam-Baker" <phill@hallambaker.com> wrote:



On Tue, Aug 8, 2017 at 4:57 PM, Dave Cridland <dave@cridland.net> wrote:

> On 8 August 2017 at 18:25, vaibhav singh <vaibhavsinghacads@gmail.com>
> wrote:
> >
> >
> > On Tue, Aug 8, 2017 at 8:56 PM, Dave Cridland <dave@cridland.net> wrote=
:
> >>
> >> On 14 July 2017 at 15:42, Yoav Nir <ynir.ietf@gmail.com> wrote:
> >> > While it may be OK to share a key with my phone (but too difficult t=
o
> do
> >> > securely in practice), sharing with a delegate is hairy on many
> >> > different
> >> > layers. But still it=E2=80=99s the same issue.
> >>
> >> I think it's all solvable using Proxy Re[en]cryption, but that seems
> >> to be a little fraught with patents at the moment.
> >
> >
> > I am not comfortable with sharing my private key with anyone, be it the
> > proxy user itself. I believe that is a requirement for Proxy
> Reencryption,
> > please correct me if I may have interpreted it wrongly.
> >
>
> You have interpreted it incorrectly.
>
> The proxy holds a key that will change a message encrypted to its
> proxy key into a message encrypted for an authorized key. It cannot
> decrypt the message to plaintext itself.
>
> All quite bleeding edge, all quite patent-encumbered, but look at
> Mathew Green's work for details - he's been researching very heavily
> in this field.


=E2=80=8BProxy re-encryption has been around for 25 years. It is hardly cut=
ting
edge.

There is a patent on the DRM use expiring soon. But the original Blaze
scheme does everything I need. It certainly isn't 'all' encumbered.

It seems to me that the cryptographers got a particular mathematical
property into their head as 'essential' which really isn't if you design
protocols. So I don't need the paired stuff.

I wrote some stuff on this:
http://www.defaultdenysecurity.com/Professional/Patents/Recryption.html

If you know of patent claims on the DH based scheme I describe, please let
me know.

I'm not sure if I have ever been so happy to be proven wrong,  thanks.

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

<div dir=3D"auto"><div><br><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On 12 Aug 2017 01:45, &quot;Phillip Hallam-Baker&quot; &lt;<a hre=
f=3D"mailto:phill@hallambaker.com">phill@hallambaker.com</a>&gt; wrote:<br =
type=3D"attribution"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=
=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_=
extra"><br><div class=3D"gmail_quote"><div class=3D"elided-text">On Tue, Au=
g 8, 2017 at 4:57 PM, Dave Cridland <span dir=3D"ltr">&lt;<a href=3D"mailto=
:dave@cridland.net" target=3D"_blank">dave@cridland.net</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><span class=3D"m_14=
72482265124813916gmail-">On 8 August 2017 at 18:25, vaibhav singh &lt;<a hr=
ef=3D"mailto:vaibhavsinghacads@gmail.com" target=3D"_blank">vaibhavsinghaca=
ds@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; On Tue, Aug 8, 2017 at 8:56 PM, Dave Cridland &lt;<a href=3D"mailto:da=
ve@cridland.net" target=3D"_blank">dave@cridland.net</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; On 14 July 2017 at 15:42, Yoav Nir &lt;<a href=3D"mailto:ynir.ietf=
@gmail.com" target=3D"_blank">ynir.ietf@gmail.com</a>&gt; wrote:<br>
&gt;&gt; &gt; While it may be OK to share a key with my phone (but too diff=
icult to do<br>
&gt;&gt; &gt; securely in practice), sharing with a delegate is hairy on ma=
ny<br>
&gt;&gt; &gt; different<br>
&gt;&gt; &gt; layers. But still it=E2=80=99s the same issue.<br>
&gt;&gt;<br>
&gt;&gt; I think it&#39;s all solvable using Proxy Re[en]cryption, but that=
 seems<br>
&gt;&gt; to be a little fraught with patents at the moment.<br>
&gt;<br>
&gt;<br>
&gt; I am not comfortable with sharing my private key with anyone, be it th=
e<br>
&gt; proxy user itself. I believe that is a requirement for Proxy Reencrypt=
ion,<br>
&gt; please correct me if I may have interpreted it wrongly.<br>
&gt;<br>
<br>
</span>You have interpreted it incorrectly.<br>
<br>
The proxy holds a key that will change a message encrypted to its<br>
proxy key into a message encrypted for an authorized key. It cannot<br>
decrypt the message to plaintext itself.<br>
<br>
All quite bleeding edge, all quite patent-encumbered, but look at<br>
Mathew Green&#39;s work for details - he&#39;s been researching very heavil=
y<br>
in this field.</blockquote><div><br></div></div><div class=3D"gmail_default=
" style=3D"font-size:small">=E2=80=8BProxy re-encryption has been around fo=
r 25 years. It is hardly cutting edge.</div><div class=3D"gmail_default" st=
yle=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"fon=
t-size:small">There is a patent on the DRM use expiring soon. But the origi=
nal Blaze scheme does everything I need. It certainly isn&#39;t &#39;all&#3=
9; encumbered.</div><div class=3D"gmail_default" style=3D"font-size:small">=
<br></div><div class=3D"gmail_default" style=3D"font-size:small">It seems t=
o me that the cryptographers got a particular mathematical property into th=
eir head as &#39;essential&#39; which really isn&#39;t if you design protoc=
ols. So I don&#39;t need the paired stuff.</div><div class=3D"gmail_default=
" style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D=
"font-size:small">I wrote some stuff on this:</div><div class=3D"gmail_defa=
ult"><a href=3D"http://www.defaultdenysecurity.com/Professional/Patents/Rec=
ryption.html" target=3D"_blank">http://www.<wbr>defaultdenysecurity.com/<wb=
r>Professional/Patents/<wbr>Recryption.html</a><br></div><div class=3D"gmai=
l_default"><br></div><div class=3D"gmail_default">If you know of patent cla=
ims on the DH based scheme I describe, please let me know.</div></div><br><=
/div></div>
</blockquote></div>I&#39;m not sure if I have ever been so happy to be prov=
en wrong, =C2=A0thanks.=C2=A0</div></div></div>

--001a113c58fa01203d05568c1d38--


From nobody Sat Aug 12 20:54:24 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF3A213249C for <ietf@ietfa.amsl.com>; Sat, 12 Aug 2017 20:54:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FqzLz28Q74lm for <ietf@ietfa.amsl.com>; Sat, 12 Aug 2017 20:54:20 -0700 (PDT)
Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FFEC132460 for <ietf@ietf.org>; Sat, 12 Aug 2017 20:54:20 -0700 (PDT)
Received: by mail-lf0-x231.google.com with SMTP id d17so28894335lfe.0 for <ietf@ietf.org>; Sat, 12 Aug 2017 20:54:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:from:date:message-id:subject:to; bh=Qk15HY796HNkXH6ps8La/MOdTiWofG56GDUZV67GBvs=; b=SyapoxJAWzT6STdV51YG/CcnoCuxcF5L5WadT3fiOvQLEJVo4xK0OTZxhzYyEU0kcL I3eDkJydmtc0Pqge7+712BKg2EAPYTE0OlOBKmI1uHbZwGsHljzoyUILoSsqdSo7SIFK +ViEP6qdwtq/AaSez7qUzWlyxY7yJiKUxrajQLvpobP+HItV5T4yLmFVp8s2ofLkLILj LbqSFUzvIp2tIIP/CdpcO8+2Y1n+S5HbDyGqDgMEQaKocCRPgzwXIAz8so2mZ4dC2fu/ DgmFwCHyDFbAySoYuAUnUvHcFDBhPmWLo890tuNfiDAM61cHl3raDOEwTdE2CFUxpeKC QDUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=Qk15HY796HNkXH6ps8La/MOdTiWofG56GDUZV67GBvs=; b=NyH9IkD/eNJeemxOtxmWMcBMJv5wv2/4IB++W4JzpyvPpThn0XRus/DB2zyfb1K+LV 1axoE/PNw6qRXzSBq4mbi4zMwkfOj1FjK8hdNZXIsVJtm29nRRLsPQbwmZEHh1mRm9ZH irT93/j6nQTtkMRWA67gQP85dI5heC3YRMNedMJ0R6GXEgGi+SeoPMFdtSbxpgJRPXYt fUKKgDpsE/w2Svn/jaEYuJ58B2tETd+w6lWSq7dEWDyMSzgEDICvVu+Miwq9U6tlXTd3 OHEVoX+NjQCHV1KM6lLgu7qkCSZtmvKNiXrZA9PBkaLMlwDqK/502d8qYMAf/C/VgdOJ ZV0Q==
X-Gm-Message-State: AHYfb5gHcUFzjUKK0K3cWaOhL+fnJpICq4TgzNOcqEoiojPdMl/sCZOB SeXGmUR/CZuU0ZvGiyKDr9e4V611TKDL
X-Received: by 10.25.23.212 with SMTP id 81mr5940837lfx.150.1502596458390; Sat, 12 Aug 2017 20:54:18 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.25.142.199 with HTTP; Sat, 12 Aug 2017 20:54:17 -0700 (PDT)
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sat, 12 Aug 2017 23:54:17 -0400
X-Google-Sender-Auth: WordX6d3v2mTVKCa1cB6O6hpoAQ
Message-ID: <CAMm+Lwiy_G5JvvufRB+DY0efGHeRSoiiB9FaWoCu80=9BqmTOg@mail.gmail.com>
Subject: Someone at Amazon fix this NOW
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a114102ae24ab4a05569a8044"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dlUzNwyKFvI0hvYaQH2O9dng0P8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 13 Aug 2017 03:54:23 -0000

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

https://petapixel.com/2017/08/11/fell-victim-1500-used-camera-lens-scam-amazon/#1502592977366

You have two problems:

1) Your complaints department is not reading the emails sent.

2) Your customers are being defrauded by someone who understands your
system.

Not good.

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

<div dir=3D"ltr"><div class=3D"gmail_default"><a href=3D"https://petapixel.=
com/2017/08/11/fell-victim-1500-used-camera-lens-scam-amazon/#1502592977366=
">https://petapixel.com/2017/08/11/fell-victim-1500-used-camera-lens-scam-a=
mazon/#1502592977366</a><br></div><div class=3D"gmail_default"><br></div><d=
iv class=3D"gmail_default">You have two problems:</div><div class=3D"gmail_=
default"><br></div><div class=3D"gmail_default">1) Your complaints departme=
nt is not reading the emails sent.</div><div class=3D"gmail_default"><br></=
div><div class=3D"gmail_default">2) Your customers are being defrauded by s=
omeone who understands your system.</div><div class=3D"gmail_default"><br><=
/div><div class=3D"gmail_default">Not good.=C2=A0</div><div class=3D"gmail_=
default"><br></div></div>

--001a114102ae24ab4a05569a8044--


From nobody Sun Aug 13 00:27:30 2017
Return-Path: <moritz30@moritz30.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD73E132586 for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 00:27:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xnz8N9hpq5rt for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 00:27:27 -0700 (PDT)
Received: from sender-of-o52.zoho.com (sender-of-o52.zoho.com [135.84.80.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CE1D13245D for <ietf@ietf.org>; Sun, 13 Aug 2017 00:27:26 -0700 (PDT)
Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1502609239573559.6376966478018; Sun, 13 Aug 2017 00:27:19 -0700 (PDT)
Date: Sun, 13 Aug 2017 09:27:19 +0200
From: Matthias Merkel <moritz30@moritz30.de>
To: <phill@hallambaker.com>
Cc: <ietf@ietf.org>
Message-Id: <15dda7d6e12.11e5a2cbe132960.6851532013164375960@moritz30.de>
In-Reply-To: <CAMm+Lwiy_G5JvvufRB+DY0efGHeRSoiiB9FaWoCu80=9BqmTOg@mail.gmail.com>
References: <CAMm+Lwiy_G5JvvufRB+DY0efGHeRSoiiB9FaWoCu80=9BqmTOg@mail.gmail.com>
Subject: Re:Someone at Amazon fix this NOW
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_317196_1780514596.1502609239571"
X-Priority: Normal
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/p01yC9d-Q4LW_icFqmz2bbQbyGI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 13 Aug 2017 07:27:29 -0000

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

Well. This is nothing good but what does the IETF have to do with it?

---- On So, 13 Aug 2017 05:54:17 +0200 phill@hallambaker.com wrote ----

https://petapixel.com/2017/08/11/fell-victim-1500-used-camera-lens-scam-ama=
zon/#1502592977366

You have two problems:

1) Your complaints department is not reading the emails sent.

2) Your customers are being defrauded by someone who understands your syste=
m.

Not good.=C2=A0


------=_Part_317196_1780514596.1502609239571
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>=
<meta content=3D"text/html;charset=3DUTF-8" http-equiv=3D"Content-Type"></h=
ead><body ><div style=3D'font-size:10pt;font-family:Verdana,Arial,Helvetica=
,sans-serif;'>Well. This is nothing good but what does the IETF have to do =
with it?<div id=3D"message"></div><br id=3D"br3"><div id=3D"signature"></di=
v><div id=3D"content"><blockquote><br> ---- On So, 13 Aug 2017 05:54:17 +02=
00 <b> phill@hallambaker.com </b> wrote ----<br><br><div><div dir=3D"ltr"><=
div><a href=3D"https://petapixel.com/2017/08/11/fell-victim-1500-used-camer=
a-lens-scam-amazon/#1502592977366" target=3D"_blank">https://petapixel.com/=
2017/08/11/fell-victim-1500-used-camera-lens-scam-amazon/#1502592977366</a>=
<br></div><div><br></div><div>You have two problems:</div><div><br></div><d=
iv>1) Your complaints department is not reading the emails sent.</div><div>=
<br></div><div>2) Your customers are being defrauded by someone who underst=
ands your system.</div><div><br></div><div>Not good.&nbsp;</div><div><br></=
div></div> </div></blockquote></div></div></body></html>
------=_Part_317196_1780514596.1502609239571--



From nobody Sun Aug 13 04:42:14 2017
Return-Path: <nick@foobar.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CFBB132395 for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 04:42:13 -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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PMWCUxjil3ak for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 04:42:11 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC08F1326A6 for <ietf@ietf.org>; Sun, 13 Aug 2017 04:42:10 -0700 (PDT)
X-Envelope-To: ietf@ietf.org
Received: from crumpet.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id v7DAg6mS041010 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 13 Aug 2017 11:42:06 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.local
Message-ID: <59903B08.2010402@foobar.org>
Date: Sun, 13 Aug 2017 12:42:00 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.16 (Macintosh/20170718)
MIME-Version: 1.0
To: Matthias Merkel <moritz30@moritz30.de>
CC: phill@hallambaker.com, ietf@ietf.org
Subject: Re: Someone at Amazon fix this NOW
References: <CAMm+Lwiy_G5JvvufRB+DY0efGHeRSoiiB9FaWoCu80=9BqmTOg@mail.gmail.com> <15dda7d6e12.11e5a2cbe132960.6851532013164375960@moritz30.de>
In-Reply-To: <15dda7d6e12.11e5a2cbe132960.6851532013164375960@moritz30.de>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2pizpadelb8VyI8TBb7F5tUkVto>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 13 Aug 2017 11:42:13 -0000

Isn't moral outrage on-topic for ietf@?

Nick

Matthias Merkel wrote:
> Well. This is nothing good but what does the IETF have to do with it?
> 
> 
>     ---- On So, 13 Aug 2017 05:54:17 +0200 *phill@hallambaker.com *
>     wrote ----
> 
>     https://petapixel.com/2017/08/11/fell-victim-1500-used-camera-lens-scam-amazon/#1502592977366
> 
>     You have two problems:
> 
>     1) Your complaints department is not reading the emails sent.
> 
>     2) Your customers are being defrauded by someone who understands
>     your system.
> 
>     Not good. 
> 


From nobody Sun Aug 13 05:19:43 2017
Return-Path: <moritz30@moritz30.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69D6B13240C for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 05:19:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.08
X-Spam-Level: *
X-Spam-Status: No, score=1.08 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.723, MISSING_MIMEOLE=1.899, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3u3apezUlD1i for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 05:19:39 -0700 (PDT)
Received: from sender-of-o52.zoho.com (sender-of-o52.zoho.com [135.84.80.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86A2313251B for <ietf@ietf.org>; Sun, 13 Aug 2017 05:19:39 -0700 (PDT)
Received: from [10.58.137.202] (x590fedca.dyn.telefonica.de [89.15.237.202]) by mx.zohomail.com with SMTPS id 1502626771366981.4257667283752; Sun, 13 Aug 2017 05:19:31 -0700 (PDT)
Date: Sun, 13 Aug 2017 14:19:22 +0200
Subject: Re: Someone at Amazon fix this NOW
Message-ID: <f1df6f4f-48d4-4331-abaa-480fa5d459e1@email.android.com>
X-Android-Message-ID: <f1df6f4f-48d4-4331-abaa-480fa5d459e1@email.android.com>
In-Reply-To: <CAMm+Lwiy_G5JvvufRB+DY0efGHeRSoiiB9FaWoCu80=9BqmTOg@mail.gmail.com>
From: Matthias Merkel <moritz30@moritz30.de>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Importance: Normal
X-Priority: 3
X-MSMail-Priority: Normal
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64
X-ZohoMailClient: External
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/spTIz9FVAnBx-gP-COWHgWBSSzM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 13 Aug 2017 12:19:41 -0000

PGRpdiBkaXI9J2F1dG8nPk5vdCBzdXJlLiBCdXQgdGhlIHN1YmplY3QgYW5kIGVtYWlsIGJvZHkg
bW9yZSBzb3VuZCBsaWtlIHRoZXkgYXJlIGRpcmVjdGVkIHRvIEFtYXpvbi48L2Rpdj48ZGl2IGNs
YXNzPSJnbWFpbF9leHRyYSI+PGJyPjxkaXYgY2xhc3M9ImdtYWlsX3F1b3RlIj5PbiBBdWcgMTMs
IDIwMTcgNTo1NCBBTSwgUGhpbGxpcCBIYWxsYW0tQmFrZXIgJmx0O3BoaWxsQGhhbGxhbWJha2Vy
LmNvbSZndDsgd3JvdGU6PGJyIHR5cGU9ImF0dHJpYnV0aW9uIj48YmxvY2txdW90ZSBjbGFzcz0i
cXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3JkZXItbGVmdDoxcHggI2NjYyBzb2xp
ZDtwYWRkaW5nLWxlZnQ6MWV4Ij48ZGl2IGRpcj0ibHRyIj48ZGl2PjxhIGhyZWY9Imh0dHBzOi8v
cGV0YXBpeGVsLmNvbS8yMDE3LzA4LzExL2ZlbGwtdmljdGltLTE1MDAtdXNlZC1jYW1lcmEtbGVu
cy1zY2FtLWFtYXpvbi8jMTUwMjU5Mjk3NzM2NiI+aHR0cHM6Ly9wZXRhcGl4ZWwuY29tLzIwMTcv
MDgvMTEvZmVsbC12aWN0aW0tMTUwMC11c2VkLWNhbWVyYS1sZW5zLXNjYW0tYW1hem9uLyMxNTAy
NTkyOTc3MzY2PC9hPjxiciAvPjwvZGl2PjxkaXY+PGJyIC8+PC9kaXY+PGRpdj5Zb3UgaGF2ZSB0
d28gcHJvYmxlbXM6PC9kaXY+PGRpdj48YnIgLz48L2Rpdj48ZGl2PjEpIFlvdXIgY29tcGxhaW50
cyBkZXBhcnRtZW50IGlzIG5vdCByZWFkaW5nIHRoZSBlbWFpbHMgc2VudC48L2Rpdj48ZGl2Pjxi
ciAvPjwvZGl2PjxkaXY+MikgWW91ciBjdXN0b21lcnMgYXJlIGJlaW5nIGRlZnJhdWRlZCBieSBz
b21lb25lIHdobyB1bmRlcnN0YW5kcyB5b3VyIHN5c3RlbS48L2Rpdj48ZGl2PjxiciAvPjwvZGl2
PjxkaXY+Tm90IGdvb2QuwqA8L2Rpdj48ZGl2PjxiciAvPjwvZGl2PjwvZGl2Pg0KPC9ibG9ja3F1
b3RlPjwvZGl2Pjxicj48L2Rpdj4=



From nobody Sun Aug 13 06:29:50 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FDC013252A for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 06:29:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NSn6n4auHjOi for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 06:29:46 -0700 (PDT)
Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA37A13213D for <ietf@ietf.org>; Sun, 13 Aug 2017 06:29:45 -0700 (PDT)
Received: by mail-lf0-x232.google.com with SMTP id t128so31042632lff.2 for <ietf@ietf.org>; Sun, 13 Aug 2017 06:29:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=aUL0robuLIb0ws1QYs4MI+yYMibxoXzR8+FVf6bz5qc=; b=q6KzYm4EQX9xxvKLW9Om7nLKdV27+ccmsv/jqZ2GD4Hknt1/2nXup/6PB+bNN/0iPf OJAr9rkYGKLtgjf9fb9NebGqkj4mtNh2HShisjcihEDKPTwfrg20hZ8gY9qlnr72uSBy cXeE+8MbZa++B7tM7XjXB0GKKRyQwlwFQEI7o6C5wvjAa7LSwcPO9vfID4/g+RhgViXJ 7ptEEQn+gCa9JZAgXmLKGoOit9k2vCvc3MW7tiZZqZG0/9D+Og+0WAVntphgBEIkWNt8 sm7WryImL1TCfAaYVLBN9+R5fQM+42su0yuVHdeymYa+Kr7o8/H+OxDQxmofRiAQzlD6 eV+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=aUL0robuLIb0ws1QYs4MI+yYMibxoXzR8+FVf6bz5qc=; b=C5r4NZ3wDZiVMgvhBf6sj2eo+oOip04WJuG6Y9SmXxXh0z37Bu3Nu2Iubqof+HWYvk /Fwl+bAKa2iPlyvbbFjrRltWlwtBsGSoP/N+JdaXOWJ0USq8vLvm2hEb2Jo7y1C2Ef6X nmqM2jFBwW4xatGDCoRxU/Ibz/Tw/Wb+2Y37cxtxnUq75EFRnGiQQyJ7b+I6tlzdb3Si ilZt97md9vF0q2wCMDJG46QExWF2ERqSK7rUZYUqDRfPWEzoWl57Zccz4xwzoVhloRJ3 R/p6x1dX8kdp4g7fSFFpYBGEvoXYCDqZKxRHC8y6chigpCraYRivstrYxMnQUXYeGz8w hyZw==
X-Gm-Message-State: AHYfb5gBmiftBLlly+FcyUvR7jY27Ztv2mcZLTRXVzT282z/WoE+ta2G WLqIgZYTnp2HjR5QR36eRiB3V3AY0w==
X-Received: by 10.25.17.218 with SMTP id 87mr7775277lfr.129.1502630983997; Sun, 13 Aug 2017 06:29:43 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.25.142.199 with HTTP; Sun, 13 Aug 2017 06:29:42 -0700 (PDT)
In-Reply-To: <15dda7d6e12.11e5a2cbe132960.6851532013164375960@moritz30.de>
References: <CAMm+Lwiy_G5JvvufRB+DY0efGHeRSoiiB9FaWoCu80=9BqmTOg@mail.gmail.com> <15dda7d6e12.11e5a2cbe132960.6851532013164375960@moritz30.de>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sun, 13 Aug 2017 09:29:42 -0400
X-Google-Sender-Auth: _1gwP2fgwfh8Tq23ci6Sl56STNU
Message-ID: <CAMm+LwieRmX3e02LbANrRjq22fM0Bb7+UiZsWzzONS+D-KdLuw@mail.gmail.com>
Subject: Re: Someone at Amazon fix this NOW
To: Matthias Merkel <moritz30@moritz30.de>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113fb69c079f760556a28a18"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ANEoUAqlYLIEXtZefmuDt83jNeg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 13 Aug 2017 13:29:48 -0000

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

Internet Security is an IETF concern.

Unfortunately, most people in IETF seem to think security is limited to
stopping mass surveillance. Confidentiality is a security concern, of
course. But it is not the only security concern.

The security concern that most Internet users are concerned about
personally is theft. That is the main reason that the WebPKI was designed
and built. The primary motive was to prevent theft of credit card numbers.

I think that everyone working on protocol design should understand the real
security concerns. Integrity attacks are almost always more damaging than
confidentiality. Hijack BGP and you can invade a country without firing a
shot (see the episode in South Ossettia).

The attacks are moving up the stack. But they are still our problem if we
want to remain relevant.

What has happened here is that the lower levels of the corporation in
question have been hollowed out into a set of rigid processes that are
blind to actual facts. It is not the only large corporation that has done
that. When that happens, the only way to reboot is to escalate. Since the
victim of the crime attempted every escalation process the company offered,
it is necessary to go outside those processes.

I also have a process. I begin with a personal contact if I have one. Then
I escalate to a public forum where I know there are employees who will
ensure the issue gets the appropriate attention and so on.

At this point it is one incident of fraud involving $1,500. But left
unaddressed it will be a few thousand within months. The template for the
attack is public now. I read the article and thought, how do we stop this,
the criminals will be reading it and asking how they can apply it. And they
won't just be targeting Amazon.

=E2=80=8B

On Sun, Aug 13, 2017 at 3:27 AM, Matthias Merkel <moritz30@moritz30.de>
wrote:

> Well. This is nothing good but what does the IETF have to do with it?
>
>
> ---- On So, 13 Aug 2017 05:54:17 +0200 * phill@hallambaker.com
> <phill@hallambaker.com> * wrote ----
>
>
> https://petapixel.com/2017/08/11/fell-victim-1500-used-
> camera-lens-scam-amazon/#1502592977366
>
> You have two problems:
>
> 1) Your complaints department is not reading the emails sent.
>
> 2) Your customers are being defrauded by someone who understands your
> system.
>
> Not good.
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">Int=
ernet Security is an IETF concern.</div><div class=3D"gmail_default" style=
=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-s=
ize:small">Unfortunately, most people in IETF seem to think security is lim=
ited to stopping mass surveillance. Confidentiality is a security concern, =
of course. But it is not the only security concern.</div><div class=3D"gmai=
l_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default"=
 style=3D"font-size:small">The security concern that most Internet users ar=
e concerned about personally is theft. That is the main reason that the Web=
PKI was designed and built. The primary motive was to prevent theft of cred=
it card numbers.=C2=A0</div><div class=3D"gmail_default" style=3D"font-size=
:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small">I =
think that everyone working on protocol design should understand the real s=
ecurity concerns. Integrity attacks are almost always more damaging than co=
nfidentiality. Hijack BGP and you can invade a country without firing a sho=
t (see the episode in South Ossettia).</div><div class=3D"gmail_default" st=
yle=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"fon=
t-size:small">The attacks are moving up the stack. But they are still our p=
roblem if we want to remain relevant.</div><div class=3D"gmail_default" sty=
le=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"font=
-size:small">What has happened here is that the lower levels of the corpora=
tion in question have been hollowed out into a set of rigid processes that =
are blind to actual facts. It is not the only large corporation that has do=
ne that. When that happens, the only way to reboot is to escalate. Since th=
e victim of the crime attempted every escalation process the company offere=
d, it is necessary to go outside those processes.</div><div class=3D"gmail_=
default" style=3D"font-size:small"><br></div><div class=3D"gmail_default" s=
tyle=3D"font-size:small">I also have a process. I begin with a personal con=
tact if I have one. Then I escalate to a public forum where I know there ar=
e employees who will ensure the issue gets the appropriate attention and so=
 on.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></div>=
<div class=3D"gmail_default" style=3D"font-size:small">At this point it is =
one incident of fraud involving $1,500. But left unaddressed it will be a f=
ew thousand within months. The template for the attack is public now. I rea=
d the article and thought, how do we stop this, the criminals will be readi=
ng it and asking how they can apply it. And they won&#39;t just be targetin=
g Amazon.</div><div class=3D"gmail_default" style=3D"font-size:small"><br><=
/div><div class=3D"gmail_default" style=3D"font-size:small">=E2=80=8B</div>=
</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sun, Aug=
 13, 2017 at 3:27 AM, Matthias Merkel <span dir=3D"ltr">&lt;<a href=3D"mail=
to:moritz30@moritz30.de" target=3D"_blank">moritz30@moritz30.de</a>&gt;</sp=
an> 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 style=3D"font=
-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif">Well. This is no=
thing good but what does the IETF have to do with it?<div id=3D"m_903584009=
1176709700message"></div><br id=3D"m_9035840091176709700br3"><div id=3D"m_9=
035840091176709700signature"></div><div id=3D"m_9035840091176709700content"=
><blockquote><br> ---- On So, 13 Aug 2017 05:54:17 +0200 <b> <a href=3D"mai=
lto:phill@hallambaker.com" target=3D"_blank">phill@hallambaker.com</a> </b>=
 wrote ----<div><div class=3D"h5"><br><br><div><div dir=3D"ltr"><div><a hre=
f=3D"https://petapixel.com/2017/08/11/fell-victim-1500-used-camera-lens-sca=
m-amazon/#1502592977366" target=3D"_blank">https://petapixel.com/2017/08/<w=
br>11/fell-victim-1500-used-<wbr>camera-lens-scam-amazon/#<wbr>150259297736=
6</a><br></div><div><br></div><div>You have two problems:</div><div><br></d=
iv><div>1) Your complaints department is not reading the emails sent.</div>=
<div><br></div><div>2) Your customers are being defrauded by someone who un=
derstands your system.</div><div><br></div><div>Not good.=C2=A0</div><div><=
br></div></div> </div></div></div></blockquote></div></div></div></blockquo=
te></div><br></div>

--001a113fb69c079f760556a28a18--


From nobody Sun Aug 13 06:35:49 2017
Return-Path: <moritz30@moritz30.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68DAD1324BA for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 06:35:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.08
X-Spam-Level: *
X-Spam-Status: No, score=1.08 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.723, MISSING_MIMEOLE=1.899, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IrRW1JZDTWuj for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 06:35:45 -0700 (PDT)
Received: from sender-of-o52.zoho.com (sender-of-o52.zoho.com [135.84.80.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49223132775 for <ietf@ietf.org>; Sun, 13 Aug 2017 06:35:44 -0700 (PDT)
Received: from [192.168.179.178] (p5DC64A9A.dip0.t-ipconnect.de [93.198.74.154]) by mx.zohomail.com with SMTPS id 1502631337747327.1303475883807; Sun, 13 Aug 2017 06:35:37 -0700 (PDT)
Date: Sun, 13 Aug 2017 15:35:19 +0200
Subject: Re: Someone at Amazon fix this NOW
Message-ID: <86998258-d4d3-4b2a-ab5f-67c1019e1e06@email.android.com>
X-Android-Message-ID: <86998258-d4d3-4b2a-ab5f-67c1019e1e06@email.android.com>
In-Reply-To: <CAMm+LwieRmX3e02LbANrRjq22fM0Bb7+UiZsWzzONS+D-KdLuw@mail.gmail.com>
From: Matthias Merkel <moritz30@moritz30.de>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Importance: Normal
X-Priority: 3
X-MSMail-Priority: Normal
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64
X-ZohoMailClient: External
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QPI8wE8NIHcjCHADwykoCcLRQPQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 13 Aug 2017 13:35:47 -0000

PGRpdiBkaXI9J2F1dG8nPjxkaXY+SSBjYXJlIGFib3V0IHNlY3VyaXR5LiBBY3R1YWxseSBhcyBz
ZWN1cml0eSByZXNlYXJjaGVyIGl0J3MgbXkgam9iIHRvIGNhcmUgYWJvdXQgY3liZXJzZWN1cml0
eS4gSSBhbHNvIGtub3cgdGhhdCBnb2luZyB0b3RvIHRoZSBwdWJsaWMgY2FuIGhlbHAgKGFjdHVh
bGx5IGl0IGhlbHBlZCBtZSB3aXRoIEFtYXpvbiBBV1MgYmVmb3JlKS4gSSB3YXMganVzdCB1bnN1
cmUgaWYgdGhpcyBtYWlsaW5nIGxpc3Qgd2FzIGFwcHJvcHJpYXRlIGZvciBpdC48YnI+PGRpdiBj
bGFzcz0iZ21haWxfZXh0cmEiPjxicj48ZGl2IGNsYXNzPSJnbWFpbF9xdW90ZSI+T24gQXVnIDEz
LCAyMDE3IDM6MjkgUE0sIFBoaWxsaXAgSGFsbGFtLUJha2VyICZsdDtwaGlsbEBoYWxsYW1iYWtl
ci5jb20mZ3Q7IHdyb3RlOjxiciB0eXBlPSJhdHRyaWJ1dGlvbiI+PGJsb2NrcXVvdGUgY2xhc3M9
InF1b3RlIiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29s
aWQ7cGFkZGluZy1sZWZ0OjFleCI+PGRpdiBkaXI9Imx0ciI+PGRpdiBzdHlsZT0iZm9udC1zaXpl
OnNtYWxsIj5JbnRlcm5ldCBTZWN1cml0eSBpcyBhbiBJRVRGIGNvbmNlcm4uPC9kaXY+PGRpdiBz
dHlsZT0iZm9udC1zaXplOnNtYWxsIj48YnI+PC9kaXY+PGRpdiBzdHlsZT0iZm9udC1zaXplOnNt
YWxsIj5VbmZvcnR1bmF0ZWx5LCBtb3N0IHBlb3BsZSBpbiBJRVRGIHNlZW0gdG8gdGhpbmsgc2Vj
dXJpdHkgaXMgbGltaXRlZCB0byBzdG9wcGluZyBtYXNzIHN1cnZlaWxsYW5jZS4gQ29uZmlkZW50
aWFsaXR5IGlzIGEgc2VjdXJpdHkgY29uY2Vybiwgb2YgY291cnNlLiBCdXQgaXQgaXMgbm90IHRo
ZSBvbmx5IHNlY3VyaXR5IGNvbmNlcm4uPC9kaXY+PGRpdiBzdHlsZT0iZm9udC1zaXplOnNtYWxs
Ij48YnI+PC9kaXY+PGRpdiBzdHlsZT0iZm9udC1zaXplOnNtYWxsIj5UaGUgc2VjdXJpdHkgY29u
Y2VybiB0aGF0IG1vc3QgSW50ZXJuZXQgdXNlcnMgYXJlIGNvbmNlcm5lZCBhYm91dCBwZXJzb25h
bGx5IGlzIHRoZWZ0LiBUaGF0IGlzIHRoZSBtYWluIHJlYXNvbiB0aGF0IHRoZSBXZWJQS0kgd2Fz
IGRlc2lnbmVkIGFuZCBidWlsdC4gVGhlIHByaW1hcnkgbW90aXZlIHdhcyB0byBwcmV2ZW50IHRo
ZWZ0IG9mIGNyZWRpdCBjYXJkIG51bWJlcnMuJm5ic3A7PC9kaXY+PGRpdiBzdHlsZT0iZm9udC1z
aXplOnNtYWxsIj48YnI+PC9kaXY+PGRpdiBzdHlsZT0iZm9udC1zaXplOnNtYWxsIj5JIHRoaW5r
IHRoYXQgZXZlcnlvbmUgd29ya2luZyBvbiBwcm90b2NvbCBkZXNpZ24gc2hvdWxkIHVuZGVyc3Rh
bmQgdGhlIHJlYWwgc2VjdXJpdHkgY29uY2VybnMuIEludGVncml0eSBhdHRhY2tzIGFyZSBhbG1v
c3QgYWx3YXlzIG1vcmUgZGFtYWdpbmcgdGhhbiBjb25maWRlbnRpYWxpdHkuIEhpamFjayBCR1Ag
YW5kIHlvdSBjYW4gaW52YWRlIGEgY291bnRyeSB3aXRob3V0IGZpcmluZyBhIHNob3QgKHNlZSB0
aGUgZXBpc29kZSBpbiBTb3V0aCBPc3NldHRpYSkuPC9kaXY+PGRpdiBzdHlsZT0iZm9udC1zaXpl
OnNtYWxsIj48YnI+PC9kaXY+PGRpdiBzdHlsZT0iZm9udC1zaXplOnNtYWxsIj5UaGUgYXR0YWNr
cyBhcmUgbW92aW5nIHVwIHRoZSBzdGFjay4gQnV0IHRoZXkgYXJlIHN0aWxsIG91ciBwcm9ibGVt
IGlmIHdlIHdhbnQgdG8gcmVtYWluIHJlbGV2YW50LjwvZGl2PjxkaXYgc3R5bGU9ImZvbnQtc2l6
ZTpzbWFsbCI+PGJyPjwvZGl2PjxkaXYgc3R5bGU9ImZvbnQtc2l6ZTpzbWFsbCI+V2hhdCBoYXMg
aGFwcGVuZWQgaGVyZSBpcyB0aGF0IHRoZSBsb3dlciBsZXZlbHMgb2YgdGhlIGNvcnBvcmF0aW9u
IGluIHF1ZXN0aW9uIGhhdmUgYmVlbiBob2xsb3dlZCBvdXQgaW50byBhIHNldCBvZiByaWdpZCBw
cm9jZXNzZXMgdGhhdCBhcmUgYmxpbmQgdG8gYWN0dWFsIGZhY3RzLiBJdCBpcyBub3QgdGhlIG9u
bHkgbGFyZ2UgY29ycG9yYXRpb24gdGhhdCBoYXMgZG9uZSB0aGF0LiBXaGVuIHRoYXQgaGFwcGVu
cywgdGhlIG9ubHkgd2F5IHRvIHJlYm9vdCBpcyB0byBlc2NhbGF0ZS4gU2luY2UgdGhlIHZpY3Rp
bSBvZiB0aGUgY3JpbWUgYXR0ZW1wdGVkIGV2ZXJ5IGVzY2FsYXRpb24gcHJvY2VzcyB0aGUgY29t
cGFueSBvZmZlcmVkLCBpdCBpcyBuZWNlc3NhcnkgdG8gZ28gb3V0c2lkZSB0aG9zZSBwcm9jZXNz
ZXMuPC9kaXY+PGRpdiBzdHlsZT0iZm9udC1zaXplOnNtYWxsIj48YnI+PC9kaXY+PGRpdiBzdHls
ZT0iZm9udC1zaXplOnNtYWxsIj5JIGFsc28gaGF2ZSBhIHByb2Nlc3MuIEkgYmVnaW4gd2l0aCBh
IHBlcnNvbmFsIGNvbnRhY3QgaWYgSSBoYXZlIG9uZS4gVGhlbiBJIGVzY2FsYXRlIHRvIGEgcHVi
bGljIGZvcnVtIHdoZXJlIEkga25vdyB0aGVyZSBhcmUgZW1wbG95ZWVzIHdobyB3aWxsIGVuc3Vy
ZSB0aGUgaXNzdWUgZ2V0cyB0aGUgYXBwcm9wcmlhdGUgYXR0ZW50aW9uIGFuZCBzbyBvbi48L2Rp
dj48ZGl2IHN0eWxlPSJmb250LXNpemU6c21hbGwiPjxicj48L2Rpdj48ZGl2IHN0eWxlPSJmb250
LXNpemU6c21hbGwiPkF0IHRoaXMgcG9pbnQgaXQgaXMgb25lIGluY2lkZW50IG9mIGZyYXVkIGlu
dm9sdmluZyAkMSw1MDAuIEJ1dCBsZWZ0IHVuYWRkcmVzc2VkIGl0IHdpbGwgYmUgYSBmZXcgdGhv
dXNhbmQgd2l0aGluIG1vbnRocy4gVGhlIHRlbXBsYXRlIGZvciB0aGUgYXR0YWNrIGlzIHB1Ymxp
YyBub3cuIEkgcmVhZCB0aGUgYXJ0aWNsZSBhbmQgdGhvdWdodCwgaG93IGRvIHdlIHN0b3AgdGhp
cywgdGhlIGNyaW1pbmFscyB3aWxsIGJlIHJlYWRpbmcgaXQgYW5kIGFza2luZyBob3cgdGhleSBj
YW4gYXBwbHkgaXQuIEFuZCB0aGV5IHdvbid0IGp1c3QgYmUgdGFyZ2V0aW5nIEFtYXpvbi48L2Rp
dj48ZGl2IHN0eWxlPSJmb250LXNpemU6c21hbGwiPjxicj48L2Rpdj48ZGl2IHN0eWxlPSJmb250
LXNpemU6c21hbGwiPuKAizwvZGl2PjwvZGl2PjxkaXY+PGJyPjxkaXYgY2xhc3M9ImVsaWRlZC10
ZXh0Ij5PbiBTdW4sIEF1ZyAxMywgMjAxNyBhdCAzOjI3IEFNLCBNYXR0aGlhcyBNZXJrZWwgPHNw
YW4gZGlyPSJsdHIiPiZsdDs8YSBocmVmPSJtYWlsdG86bW9yaXR6MzBAbW9yaXR6MzAuZGUiPm1v
cml0ejMwQG1vcml0ejMwLmRlPC9hPiZndDs8L3NwYW4+IHdyb3RlOjxicj48YmxvY2txdW90ZSBz
dHlsZT0ibWFyZ2luOjAgMCAwIDAuOGV4O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNvbGlkO3BhZGRp
bmctbGVmdDoxZXgiPjx1PjwvdT48ZGl2PjxkaXYgc3R5bGU9ImZvbnQtc2l6ZToxMHB0O2ZvbnQt
ZmFtaWx5Oid2ZXJkYW5hJyAsICdhcmlhbCcgLCAnaGVsdmV0aWNhJyAsIHNhbnMtc2VyaWYiPldl
bGwuIFRoaXMgaXMgbm90aGluZyBnb29kIGJ1dCB3aGF0IGRvZXMgdGhlIElFVEYgaGF2ZSB0byBk
byB3aXRoIGl0PzxkaXY+PC9kaXY+PGJyPjxkaXY+PC9kaXY+PGRpdj48YmxvY2txdW90ZT48YnI+
IC0tLS0gT24gU28sIDEzIEF1ZyAyMDE3IDA1OjU0OjE3ICswMjAwIDxiPiA8YSBocmVmPSJtYWls
dG86cGhpbGxAaGFsbGFtYmFrZXIuY29tIj5waGlsbEBoYWxsYW1iYWtlci5jb208L2E+IDwvYj4g
d3JvdGUgLS0tLTxkaXY+PGRpdj48YnI+PGJyPjxkaXY+PGRpdiBkaXI9Imx0ciI+PGRpdj48YSBo
cmVmPSJodHRwczovL3BldGFwaXhlbC5jb20vMjAxNy8wOC8xMS9mZWxsLXZpY3RpbS0xNTAwLXVz
ZWQtY2FtZXJhLWxlbnMtc2NhbS1hbWF6b24vIzE1MDI1OTI5NzczNjYiPmh0dHBzOi8vcGV0YXBp
eGVsLmNvbS8yMDE3LzA4Lzx3YnI+MTEvZmVsbC12aWN0aW0tMTUwMC11c2VkLTx3YnI+Y2FtZXJh
LWxlbnMtc2NhbS1hbWF6b24vIzx3YnI+MTUwMjU5Mjk3NzM2NjwvYT48YnI+PC9kaXY+PGRpdj48
YnI+PC9kaXY+PGRpdj5Zb3UgaGF2ZSB0d28gcHJvYmxlbXM6PC9kaXY+PGRpdj48YnI+PC9kaXY+
PGRpdj4xKSBZb3VyIGNvbXBsYWludHMgZGVwYXJ0bWVudCBpcyBub3QgcmVhZGluZyB0aGUgZW1h
aWxzIHNlbnQuPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj4yKSBZb3VyIGN1c3RvbWVycyBhcmUg
YmVpbmcgZGVmcmF1ZGVkIGJ5IHNvbWVvbmUgd2hvIHVuZGVyc3RhbmRzIHlvdXIgc3lzdGVtLjwv
ZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+Tm90IGdvb2QuJm5ic3A7PC9kaXY+PGRpdj48YnI+PC9k
aXY+PC9kaXY+IDwvZGl2PjwvZGl2PjwvZGl2PjwvYmxvY2txdW90ZT48L2Rpdj48L2Rpdj48L2Rp
dj48L2Jsb2NrcXVvdGU+PC9kaXY+PGJyPjwvZGl2Pgo8L2Jsb2NrcXVvdGU+PC9kaXY+PGJyPjwv
ZGl2PjwvZGl2PjwvZGl2Pg==



From nobody Sun Aug 13 06:47:54 2017
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B0A8132651; Sun, 13 Aug 2017 06:47:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even <ron.even.tlv@gmail.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-pce-rfc6006bis.all@ietf.org, pce@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-ietf-pce-rfc6006bis-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150263205807.26527.8869013927407425945@ietfa.amsl.com>
Date: Sun, 13 Aug 2017 06:47:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UY8Q5gaFjiMfhz3sWHJ1TN0QTnk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 13 Aug 2017 13:47:38 -0000

Reviewer: Roni Even
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-pce-rfc6006bis-??
Reviewer: Roni Even
Review Date: 2017-08-13
IETF LC End Date: 2017-08-24
IESG Telechat date: 2017-08-31

Summary: The document is ready for publication as standard track RFC

I read all the document and also did a compare with RFC6006 to look at the
changes.

Major issues:

Minor issues:

Nits/editorial comments:

1. In section 4.2 I am not sure why is this sentence there, is it for the
current yang document or for a future one. Why have it at all?-"The PCEP YANG
module [I-D.ietf-pce-pcep-yang] can be extended to also include the P2MP
related parameters."



From nobody Sun Aug 13 07:39:10 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6797513281E for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 07:39:09 -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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RdTmpuPPsPL7 for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 07:39:07 -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 51868132812 for <ietf@ietf.org>; Sun, 13 Aug 2017 07:39:07 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id B915BE20E; Sun, 13 Aug 2017 10:41:34 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 065AA80717; Sun, 13 Aug 2017 10:39:06 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Phillip Hallam-Baker <phill@hallambaker.com>
cc: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Someone at Amazon fix this NOW
In-Reply-To: <CAMm+Lwiy_G5JvvufRB+DY0efGHeRSoiiB9FaWoCu80=9BqmTOg@mail.gmail.com>
References: <CAMm+Lwiy_G5JvvufRB+DY0efGHeRSoiiB9FaWoCu80=9BqmTOg@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.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-sha256; protocol="application/pgp-signature"
Date: Sun, 13 Aug 2017 10:39:06 -0400
Message-ID: <29873.1502635146@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DSvx3iROyUwiWMEDb-RnIdSq5rg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 13 Aug 2017 14:39:09 -0000

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


> The seller knew s system. When I made the order, they shipped a box of
> baking maps s address in Gilberts, Illinois, and then used the tracking
> number for my order.to S

So, to put this into something that IETFers can deal with, this would have
been detectable automatically if USPS had sent a signed artifact to Amazon
(or if such a thing was retrievable via the tracking order) that Amazon cou=
ld
have compared with the correct destination address.

If this IETFs' direct problem?  Not entirely; we have 20yr old protocols for
signing various objects, although PHB knows better than any how unsuccessful
we have been at getting them used.

If anything it outlines the gap between publishing an RFC and getting it
meaningful deployed.  There is a gap in there for motivated early adopters
(such as governments, via procurement) and industry and government to adopt.
I don't understand, for instance, why S/MIME isn't a mandated (by law
societies) standard for emails between lawyers. Instead, we have the silly
disclaimers.

Maybe this is an IASA2 discussion: how could we engage (and collect fees)
From=20a more diverse set of "stakeholders", such that they'd care when/if =
we
actual solved their problems.

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




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

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

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlmQZIkACgkQgItw+93Q
3WX3RAf/Tfm6jINEafGkAURAAdUNYfuimrOetD3xVOM34iX5BCUrk5QL52hW1CKK
2JVAEy0Fju69lOu9Yg0Px4TwK9PP87/idpvNFSFIa32cZIX7mvZ6OQUfcxIEdtJ0
oe06/l9/5bR8O2ejl7/JP2EWoCxma+jFPaSly78nJzF8fePr7Uq0zg1rUB/0q2Js
JhYc1TWDlrMNKZpArZBhXqlyU7lbxSYRgD9a03LafDUgc42UxfV+mwab7+S8ADCk
xcg1VNSwMT2aH5333gz0KKovaGYrBuKLtd4pdqYjT2M/nD1qNAQYUtOYw4JeuGVJ
JjxBU30L/t4S9wbKhOGpaXUZDtGByA==
=a9p+
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Aug 13 07:57:59 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 851241324D6 for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 07:57:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q3UPVa03HMPJ for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 07:57:55 -0700 (PDT)
Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35AEC13239D for <ietf@ietf.org>; Sun, 13 Aug 2017 07:57:55 -0700 (PDT)
Received: by mail-lf0-x22d.google.com with SMTP id o85so31303200lff.3 for <ietf@ietf.org>; Sun, 13 Aug 2017 07:57:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=95n1/lc0/wkVnpdzSjODiiRkqD1Cbhi3N59CLINm9CU=; b=nazYjazHWvQJZbbyQx7Wjw/82BEyzmSaD5shyAMAQR2EQpvrc1u9gLj+jY3Lox5z2n QVwH4lvZhd3BgmoSnth4BYHmTR2ejdo+HvL3Q9U7VAcnDhnFu4jEuk7iM6HjgtfgOD1e T4xBDxWTp3vEijpsRX/zKqmM17+DtcdtNFvWGTI5mfmqoNNCsUELkkUzXWZA1LtCt03N UTyh7aMng7lxoyfQMtxATxaC8popQSt6Npk2MMGOUPvo2EH/vghSl0fBt2BChlURpxCg XfcUEAeaNVaV8hyGIknQRpjA5idTzeVODD0CwYMDLuweTgHTTAG8AnJYGR8ydTrn99ak iKkQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=95n1/lc0/wkVnpdzSjODiiRkqD1Cbhi3N59CLINm9CU=; b=j4HrGClMQHG6WJJS2RmGRZe2b0PDO4ODRsIzcoAOFXEU7lUFM3B1+9hxNzTDxVNsDk cev1WSbrqfuui8iPP536V5/8m43hvZL5tAINBhV72ndCoh+Up7rdNydM5oYsBtvF5gEG oHTwPXqhJDM4c87hWywk0Kz6D7QKNHAUrSfpipOlBFecSC3uqFLz0n9kc+IVmHG6JRIf 8O9Fs9bu8CUgupCsF5e15DkRoHVNxXhmgArSAmw0pVUucPXEf0/ucEGVJ06tAqrbJhGG EhCscyuVJmZrmzKvHXHPGCAmCpSmVnss/DELb7nYAp1D1LIk2JcwFtOttz9yj9C3zI5R Lrhg==
X-Gm-Message-State: AHYfb5gbRT/6AoJEIL4+HEcsejvy316gBfTOTwOfajUg5cOnYRR4ikPk HgnCy8Qj/D2hLsfvWBww3Od2iQeaAQ==
X-Received: by 10.25.168.144 with SMTP id r138mr7686015lfe.15.1502636273288; Sun, 13 Aug 2017 07:57:53 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.25.142.199 with HTTP; Sun, 13 Aug 2017 07:57:52 -0700 (PDT)
In-Reply-To: <29873.1502635146@obiwan.sandelman.ca>
References: <CAMm+Lwiy_G5JvvufRB+DY0efGHeRSoiiB9FaWoCu80=9BqmTOg@mail.gmail.com> <29873.1502635146@obiwan.sandelman.ca>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sun, 13 Aug 2017 10:57:52 -0400
X-Google-Sender-Auth: SToUU99pKQ9yBDYYU3rOGx1PvXc
Message-ID: <CAMm+LwiYU2nQAnWNsjUft-BnZEpTz-0Dy1f_pFgfqeMe9LXe_Q@mail.gmail.com>
Subject: Re: Someone at Amazon fix this NOW
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a114113104bcd020556a3c52c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LCvgKL_Fphx1rVbf9juVMetK7Ag>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 13 Aug 2017 14:57:57 -0000

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

On Sun, Aug 13, 2017 at 10:39 AM, Michael Richardson <mcr+ietf@sandelman.ca=
>
wrote:

>
> > The seller knew s system. When I made the order, they shipped a box of
> > baking maps s address in Gilberts, Illinois, and then used the tracking
> > number for my order.to S
>
> So, to put this into something that IETFers can deal with, this would hav=
e
> been detectable automatically if USPS had sent a signed artifact to Amazo=
n
> (or if such a thing was retrievable via the tracking order) that Amazon
> could
> have compared with the correct destination address.
>
> If this IETFs' direct problem?  Not entirely; we have 20yr old protocols
> for
> signing various objects, although PHB knows better than any how
> unsuccessful
> we have been at getting them used.
>
> If anything it outlines the gap between publishing an RFC and getting it
> meaningful deployed.  There is a gap in there for motivated early adopter=
s
> (such as governments, via procurement) and industry and government to
> adopt.


=E2=80=8BI think we are sleepwalking into a similar disaster with IoT. Righ=
t now,
the message Congress is getting is that the biggest priority in IoT is to
force devices to accept software updates.

Well no it is not. Software updates are only going to make things worse if
you don't do it securely. The update mechanism provides the attacker with a
vector to own the machine entirely unless you authenticate. Do you think
the IoT folk do that right?

I can't use my Sonos device in one room because every time I try, it is
updating. Same with one of the 'smart' TVs.=E2=80=8B

There is a real empathy gap in the industry. Its not just an inability to
see things from the user's point of view, it is a refusal to accept that it
even matters.

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sun, Au=
g 13, 2017 at 10:39 AM, Michael Richardson <span dir=3D"ltr">&lt;<a href=3D=
"mailto:mcr+ietf@sandelman.ca" target=3D"_blank">mcr+ietf@sandelman.ca</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"><br>
&gt; The seller knew s system. When I made the order, they shipped a box of=
<br>
&gt; baking maps s address in Gilberts, Illinois, and then used the trackin=
g<br>
&gt; number for my <a href=3D"http://order.to" rel=3D"noreferrer" target=3D=
"_blank">order.to</a> S<br>
<br>
So, to put this into something that IETFers can deal with, this would have<=
br>
been detectable automatically if USPS had sent a signed artifact to Amazon<=
br>
(or if such a thing was retrievable via the tracking order) that Amazon cou=
ld<br>
have compared with the correct destination address.<br>
<br>
If this IETFs&#39; direct problem?=C2=A0 Not entirely; we have 20yr old pro=
tocols for<br>
signing various objects, although PHB knows better than any how unsuccessfu=
l<br>
we have been at getting them used.<br>
<br>
If anything it outlines the gap between publishing an RFC and getting it<br=
>
meaningful deployed.=C2=A0 There is a gap in there for motivated early adop=
ters<br>
(such as governments, via procurement) and industry and government to adopt=
.</blockquote><div><br></div><div class=3D"gmail_default" style=3D"font-siz=
e:small">=E2=80=8BI think we are sleepwalking into a similar disaster with =
IoT. Right now, the message Congress is getting is that the biggest priorit=
y in IoT is to force devices to accept software updates.</div><div class=3D=
"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_def=
ault" style=3D"font-size:small">Well no it is not. Software updates are onl=
y going to make things worse if you don&#39;t do it securely. The update me=
chanism provides the attacker with a vector to own the machine entirely unl=
ess you authenticate. Do you think the IoT folk do that right?</div><div cl=
ass=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gma=
il_default" style=3D"font-size:small">I can&#39;t use my Sonos device in on=
e room because every time I try, it is updating. Same with one of the &#39;=
smart&#39; TVs.=E2=80=8B</div><div class=3D"gmail_default" style=3D"font-si=
ze:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small">=
There is a real empathy gap in the industry. Its not just an inability to s=
ee things from the user&#39;s point of view, it is a refusal to accept that=
 it even matters.</div></div></div></div>

--001a114113104bcd020556a3c52c--


From nobody Sun Aug 13 11:30:26 2017
Return-Path: <ietf@rozanak.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 141621324CF for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 11:30:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id thCIHy88dkP5 for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 11:30:22 -0700 (PDT)
Received: from mail.rozanak.com (mail.rozanak.com [IPv6:2a01:238:42ad:1500:aa19:4238:e48f:61cf]) (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 4C0621326D3 for <ietf@ietf.org>; Sun, 13 Aug 2017 11:30:22 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mail.rozanak.com (Postfix) with ESMTP id 2B11725CA291; Sun, 13 Aug 2017 18:30:20 +0000 (UTC)
X-Virus-Scanned: amavisd-new at rozanak.com
Received: from mail.rozanak.com ([127.0.0.1]) by localhost (mail.rozanak.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tzcyxZLoWWPv; Sun, 13 Aug 2017 20:30:18 +0200 (CEST)
Received: from localhost.localdomain (unknown [85.195.101.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.rozanak.com (Postfix) with ESMTPSA id 21E3825CA24E; Sun, 13 Aug 2017 20:30:18 +0200 (CEST)
Subject: Re: Someone at Amazon fix this NOW
To: Phillip Hallam-Baker <phill@hallambaker.com>, Michael Richardson <mcr+ietf@sandelman.ca>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
References: <CAMm+Lwiy_G5JvvufRB+DY0efGHeRSoiiB9FaWoCu80=9BqmTOg@mail.gmail.com> <29873.1502635146@obiwan.sandelman.ca> <CAMm+LwiYU2nQAnWNsjUft-BnZEpTz-0Dy1f_pFgfqeMe9LXe_Q@mail.gmail.com>
From: Hosnieh Rafiee <ietf@rozanak.com>
Message-ID: <805781c3-eb11-3ec6-5161-6fef159381ca@rozanak.com>
Date: Sun, 13 Aug 2017 20:30:16 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CAMm+LwiYU2nQAnWNsjUft-BnZEpTz-0Dy1f_pFgfqeMe9LXe_Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------13343AE0C71DFA01C1820A73"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eY4paswSWci2tTRvR0IzaNDFxMc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 13 Aug 2017 18:30:25 -0000

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

IMHO, It is not the problem of IETF or other standards, because
standards can just say what to do but does not enforce it or also does
not say how to do it.

It is the problem of training and knowledge of customers and as a result
industries.

The enforcement cannot happen unless the industries feel the need of
that or there is a kind of competition between industries to have it.
This is not easy as at the moment, the IoT industries just thinking
about adding nice features rather than security or privacy.  One
possibility is that the customer are the one who ask for that. because
if the customer ask for that, then industries will follow the needs of
the customers. For doing that, there need to be a wide understanding and
training for customers to understand the problem. 80% of people just buy
IoT without having a knowledge of security and enjoy its features.

If there are common criterias and customer ask for that, then industries
will follow that goal. Otherwise if security causes additional cost for
industries and customer do not also understand this advantage, then they
prefer to buy what they can have with less price!

Open source or other activities might help but they still cannot enforce
big companies to take care of their security. Otherwise in world there
are whitehat hackers that start activites to show the problems! But
unfortunately based on many countries regulation, even whitehat hackers
can be arrested if the industries did not ask for that....




>
>
> On Sun, Aug 13, 2017 at 10:39 AM, Michael Richardson
> <mcr+ietf@sandelman.ca <mailto:mcr+ietf@sandelman.ca>> wrote:
>
>
>     > The seller knew s system. When I made the order, they shipped a
>     box of
>     > baking maps s address in Gilberts, Illinois, and then used the
>     tracking
>     > number for my order.to <http://order.to> S
>
>     So, to put this into something that IETFers can deal with, this
>     would have
>     been detectable automatically if USPS had sent a signed artifact
>     to Amazon
>     (or if such a thing was retrievable via the tracking order) that
>     Amazon could
>     have compared with the correct destination address.
>
>     If this IETFs' direct problem?  Not entirely; we have 20yr old
>     protocols for
>     signing various objects, although PHB knows better than any how
>     unsuccessful
>     we have been at getting them used.
>
>     If anything it outlines the gap between publishing an RFC and
>     getting it
>     meaningful deployed.  There is a gap in there for motivated early
>     adopters
>     (such as governments, via procurement) and industry and government
>     to adopt.
>
>
> =E2=80=8BI think we are sleepwalking into a similar disaster with IoT. =
Right
> now, the message Congress is getting is that the biggest priority in
> IoT is to force devices to accept software updates.
>
> Well no it is not. Software updates are only going to make things
> worse if you don't do it securely. The update mechanism provides the
> attacker with a vector to own the machine entirely unless you
> authenticate. Do you think the IoT folk do that right?
>
> I can't use my Sonos device in one room because every time I try, it
> is updating. Same with one of the 'smart' TVs.=E2=80=8B
>
> There is a real empathy gap in the industry. Its not just an inability
> to see things from the user's point of view, it is a refusal to accept
> that it even matters.


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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>IMHO, It is not the problem of IETF or other standards, because
      standards can just say what to do but does not enforce it or also
      does not say how to do it.</p>
    <p>It is the problem of training and knowledge of customers and as a
      result industries.<br>
    </p>
    <p>The enforcement cannot happen unless the industries feel the need
      of that or there is a kind of competition between industries to
      have it. This is not easy as at the moment, the IoT industries
      just thinking about adding nice features rather than security or
      privacy.  One possibility is that the customer are the one who ask
      for that. because if the customer ask for that, then industries
      will follow the needs of the customers. For doing that, there need
      to be a wide understanding and training for customers to
      understand the problem. 80% of people just buy IoT without having
      a knowledge of security and enjoy its features.</p>
    <p>If there are common criterias and customer ask for that, then
      industries will follow that goal. Otherwise if security causes
      additional cost for industries and customer do not also understand
      this advantage, then they prefer to buy what they can have with
      less price!<br>
    </p>
    <p>Open source or other activities might help but they still cannot
      enforce big companies to take care of their security. Otherwise in
      world there are whitehat hackers that start activites to show the
      problems! But unfortunately based on many countries regulation,
      even whitehat hackers can be arrested if the industries did not
      ask for that....</p>
    <p><br>
    </p>
    <p><br>
    </p>
    <div class="moz-cite-prefix"><br>
    </div>
    <blockquote type="cite"
cite="mid:CAMm+LwiYU2nQAnWNsjUft-BnZEpTz-0Dy1f_pFgfqeMe9LXe_Q@mail.gmail.com">
      <meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div class="gmail_default"><br>
        </div>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Sun, Aug 13, 2017 at 10:39 AM,
            Michael Richardson <span dir="ltr">&lt;<a
                href="mailto:mcr+ietf@sandelman.ca" target="_blank"
                moz-do-not-send="true">mcr+ietf@sandelman.ca</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote"><br>
              &gt; The seller knew s system. When I made the order, they
              shipped a box of<br>
              &gt; baking maps s address in Gilberts, Illinois, and then
              used the tracking<br>
              &gt; number for my <a href="http://order.to"
                rel="noreferrer" target="_blank" moz-do-not-send="true">order.to</a>
              S<br>
              <br>
              So, to put this into something that IETFers can deal with,
              this would have<br>
              been detectable automatically if USPS had sent a signed
              artifact to Amazon<br>
              (or if such a thing was retrievable via the tracking
              order) that Amazon could<br>
              have compared with the correct destination address.<br>
              <br>
              If this IETFs' direct problem?  Not entirely; we have 20yr
              old protocols for<br>
              signing various objects, although PHB knows better than
              any how unsuccessful<br>
              we have been at getting them used.<br>
              <br>
              If anything it outlines the gap between publishing an RFC
              and getting it<br>
              meaningful deployed.  There is a gap in there for
              motivated early adopters<br>
              (such as governments, via procurement) and industry and
              government to adopt.</blockquote>
            <div><br>
            </div>
            <div class="gmail_default">​I think we are sleepwalking into
              a similar disaster with IoT. Right now, the message
              Congress is getting is that the biggest priority in IoT is
              to force devices to accept software updates.</div>
            <div class="gmail_default"><br>
            </div>
            <div class="gmail_default">Well no it is not. Software
              updates are only going to make things worse if you don't
              do it securely. The update mechanism provides the attacker
              with a vector to own the machine entirely unless you
              authenticate. Do you think the IoT folk do that right?</div>
            <div class="gmail_default"><br>
            </div>
            <div class="gmail_default">I can't use my Sonos device in
              one room because every time I try, it is updating. Same
              with one of the 'smart' TVs.​</div>
            <div class="gmail_default"><br>
            </div>
            <div class="gmail_default">There is a real empathy gap in
              the industry. Its not just an inability to see things from
              the user's point of view, it is a refusal to accept that
              it even matters.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------13343AE0C71DFA01C1820A73--


From nobody Sun Aug 13 20:13:35 2017
Return-Path: <shogunx@sleekfreak.ath.cx>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 603021204DA; Sun, 13 Aug 2017 20:13:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.918
X-Spam-Level: 
X-Spam-Status: No, score=-0.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_DYNAMIC=0.982] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n9UZ-yNSsoE1; Sun, 13 Aug 2017 20:13:32 -0700 (PDT)
Received: from sleekfreak.ath.cx (rrcs-67-79-182-226.se.biz.rr.com [67.79.182.226]) (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 7079D1201F8; Sun, 13 Aug 2017 20:13:32 -0700 (PDT)
Received: from shogunx (helo=localhost) by sleekfreak.ath.cx with local-esmtp (Exim 4.89) (envelope-from <shogunx@sleekfreak.ath.cx>) id 1dh5nm-00019m-R5; Sun, 13 Aug 2017 23:12:26 -0400
Date: Sun, 13 Aug 2017 23:12:26 -0400 (EDT)
From: shogunx@sleekfreak.ath.cx
To: ietf@ietf.org
cc: ietf-announce@ietf.org
Subject: Re: Mailman attack in progress
In-Reply-To: <CABL0ig4UT4Ebfzdf2ce1vu-Q76Ei_A7Yk=q-fkGfDU8o2VWjeA@mail.gmail.com>
Message-ID: <alpine.DEB.2.10.1708132312190.17622@sleekfreak.ath.cx>
References: <CABL0ig7VW_eNC8qEiX0+a71if1L0FnxEJn6usssQu+1Ox5nQOQ@mail.gmail.com> <CABL0ig4UT4Ebfzdf2ce1vu-Q76Ei_A7Yk=q-fkGfDU8o2VWjeA@mail.gmail.com>
User-Agent: Alpine 2.10 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0V1iGyuf3936eO5YCHB2bzKGb4c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 03:13:33 -0000

Kaplah!

On Sun, 13 Aug 2017, Glen wrote:

> A brief update on our Mailman attack.
>
> After analyzing the attack pattern, I've added a new long-term measure
> into Mailman that is preventing these botnet subscription attempts
> from being honored (whilst still allowing humans to subscribe).
>
> I then turned my attention to Cloudflare.   After some experimentation
> (and manual-reading!) I discovered that - with a little custom
> crafting - one can actually use Cloudflare to mitigate this type of
> attack quite nicely.  I inserted some custom rules that have all but
> halted the incoming flood completely.
>
> So Mailman subscription service is back online (for humans only!) and
> we appear to be back to normal.
>
> Thank you for your patience during this interruption.
>
> Glen
> --
> Glen Barney
> IT Director
> AMS (IETF Secretariat)
>
>


From nobody Sun Aug 13 20:22:42 2017
Return-Path: <glen@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 644141204DA for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 20:22:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.701
X-Spam-Level: 
X-Spam-Status: No, score=-3.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RO2x2g2AWNDC for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 20:22:40 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 467941201F8 for <ietf@ietf.org>; Sun, 13 Aug 2017 20:22:40 -0700 (PDT)
Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTPS id B775E1C2B64 for <ietf@ietf.org>; Sun, 13 Aug 2017 20:22:16 -0700 (PDT)
Received: from mail-qk0-f179.google.com (mail-qk0-f179.google.com [209.85.220.179]) by c8a.amsl.com (Postfix) with ESMTPSA id 8A90C1C2BA0 for <ietf@ietf.org>; Sun, 13 Aug 2017 20:22:16 -0700 (PDT)
Received: by mail-qk0-f179.google.com with SMTP id d136so44751694qkg.3 for <ietf@ietf.org>; Sun, 13 Aug 2017 20:22:40 -0700 (PDT)
X-Gm-Message-State: AHYfb5iTHmPnB06dQ9P/lX60b3z6yaCFXQC4CueNGql3uhWt+8jgsLV3 mfipCTdiGJYNbv9gch9YdPbPKMQvyA==
X-Received: by 10.55.157.150 with SMTP id g144mr1865760qke.241.1502680959270;  Sun, 13 Aug 2017 20:22:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.55.103.201 with HTTP; Sun, 13 Aug 2017 20:22:18 -0700 (PDT)
From: Glen <glen@amsl.com>
Date: Sun, 13 Aug 2017 20:22:18 -0700
X-Gmail-Original-Message-ID: <CABL0ig5mRn8w5dYvycfZYqUs46UhYhYneWE0ammxhteTfr2YYw@mail.gmail.com>
Message-ID: <CABL0ig5mRn8w5dYvycfZYqUs46UhYhYneWE0ammxhteTfr2YYw@mail.gmail.com>
Subject: Re: Mailman attack in progress
To: ietf@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zP_AilLaEif_ZXjD43rYs7yyKJI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 03:22:41 -0000

On Sun, 13 Aug 2017, shogunx@sleekfreak.ath.cx wrote:
> Kaplah!

Maj!  Jlyaj!  Tlhlngag mah!

(The original "Kaplah" is of course the Klingon battle cry, loosely
translating as "Success!" or "Victory!"  My response:  "Good!  I
understand!  We are Klingons!")

More truth there than most realize.

Thank you for the support!

Good night, IETF.  May we all have strength, and honor!

Glen


From nobody Sun Aug 13 21:31:01 2017
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 998071241F5 for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 21:30:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.799
X-Spam-Level: 
X-Spam-Status: No, score=0.799 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LMpmJybxzy-5 for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 21:30:57 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id A16D0124217 for <ietf@ietf.org>; Sun, 13 Aug 2017 21:30:57 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 09D1CCC43B for <ietf@ietf.org>; Mon, 14 Aug 2017 00:30:55 -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 sxZ2777tMdSt for <ietf@ietf.org>; Mon, 14 Aug 2017 00:30:51 -0400 (EDT)
Received: from Miless-MacBook-Pro.local (174-17-151-48.phnx.qwest.net [174.17.151.48]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 87C46CC1E6 for <ietf@ietf.org>; Mon, 14 Aug 2017 00:30:41 -0400 (EDT)
Subject: "airborne wireless network" - anybody know anything about these folks?
References: <2ab039d2-713a-f6c7-0c85-5dd1e5e2a010@meetinghouse.net>
To: ietf@ietf.org
From: Miles Fidelman <mfidelman@meetinghouse.net>
X-Forwarded-Message-Id: <2ab039d2-713a-f6c7-0c85-5dd1e5e2a010@meetinghouse.net>
Message-ID: <bc582f7a-9db6-0f38-2d5b-6fcf320dfe20@meetinghouse.net>
Date: Sun, 13 Aug 2017 21:30:40 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <2ab039d2-713a-f6c7-0c85-5dd1e5e2a010@meetinghouse.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FdstZ99tL1l9RWABRFN9RUrZi2A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 04:30:59 -0000

Hi Folks,

Anybody know anything about these folks:
http://www.airbornewirelessnetwork.com/index.asp

I came across an ad from them, in an in-flite magazine - they claim to
be developing a flying mesh network, with nodes hanging off commercial
airliners.  (More like an investment pitch than a technical ad, backed
by a web site that was more sizzle than substance.)

It sure seems like a neat concept, and they seem to have some serious
airline industry connections - but a bit light on the technology side.

They also make a lot of a patent they have - but it seems to be stuff that we've all
seen before in tactical networking and some of the Air Force's airborne
network initiatives.

Anyway... anybody know these folks?  Are they for real?

Miles Fidelman

p.s. Also of possible interest: These folks: https://www.analyticalspace.com - are
about to launch a constellation of LEO cubesats, also with the intent of doing
high bandwidth mesh networking, with laser up/downlinks to customers - no need for
big ground stations.  They seem a lot more substantial - Draper Labs tie in and such.

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


From nobody Sun Aug 13 21:57:19 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75254126BFD for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 21:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TEuFKUPUYOvW for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 21:57:08 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7083D126BF3 for <ietf@ietf.org>; Sun, 13 Aug 2017 21:57:08 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id g25so35109779lfh.1 for <ietf@ietf.org>; Sun, 13 Aug 2017 21:57:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:from:date:message-id:subject:to:cc; bh=7KIjOKFwk1k+Y/cMXtFWck5GaMlidGiQV6cC85b11+k=; b=ed+GxP1Oa2Y2WkKMJQsXoV44douRg10eeqdF8QX+8/T6D6FqhsrmIoOmaBBqDQEzui 3PSvtB2v7aBpW/rnTEEz4R1iubQE5zyHEOJPoGPGHQmTv6THKTs0wgnRikBRO8CrqRkw wia4mTzyRN34rU4tfW584OwVxuSswvJojaKp5tcZ8lkf+urLmR9NaMAd96CrefF+TBtM sotin7q0RQ+/r0obh7PezXzbqM5I5DI96sFtOybr77E+mHm5tPSnTzgazsn2BRs7ilu1 4/ZN2uk/skeCzYBwD72A4IhyF4t84qYRDaeC1gw2rJeKgVtC4etGDhLD7bS/rNyUJ8D8 oyxw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to:cc; bh=7KIjOKFwk1k+Y/cMXtFWck5GaMlidGiQV6cC85b11+k=; b=WdIc9T/p62I02t/vnUvhLKRvdEsyqZBaBZo7kkDOs+5WZMUP6TKppetY09aPiek1tj D8ihOrysM1xf6QFCJTxSGFKTMy6ngDpKoRIcPRQU/Ais7kz3NYGhqj/QEpwvkPFC0W41 u82SDmdjuxaKztx9SXBfUcdQHO8MJ6qEF72T70gixJ0UqsntaaT5PyXjZP/fvTVY8M/5 winHqELsMETWPRAd46iBLoXn3jagOFDoNRzcYEygQYFR4NTf86P4dGMF447QiumgmibN pRoSWugu+z10B3A5qsFTZtUAz6+zwmLZpOEHXSvIT7NrDMYMO+ODlzn5P5234BRac+E9 DKfQ==
X-Gm-Message-State: AHYfb5gh0E9bOFFZ9dQFtxdBhNk6YsRtoloWpUhB7+/7Zf8iqTx/J5Tb HiChN+OiBSP1VsJ2VUVxMouWOUJblQ==
X-Received: by 10.46.21.20 with SMTP id s20mr7509673ljd.172.1502686626751; Sun, 13 Aug 2017 21:57:06 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.25.142.199 with HTTP; Sun, 13 Aug 2017 21:57:05 -0700 (PDT)
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Mon, 14 Aug 2017 00:57:05 -0400
X-Google-Sender-Auth: simDX1mrw0bWM34F5gr4o-CCiEU
Message-ID: <CAMm+LwgyGfcH2Q7M6KsWTT4cPn_QZdHyVt=wj64jeWbDjFANhg@mail.gmail.com>
Subject: IOT Security Bill
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c1cc94698aac30556af7e8b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Rj3eq8x3fLVfCFxkQco2XLrfjnE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 04:57:10 -0000

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

On Sun, Aug 13, 2017 at 10:57 AM, Phillip Hallam-Baker <
phill@hallambaker.com> wrote:

>
> =E2=80=8BI think we are sleepwalking into a similar disaster with IoT. Ri=
ght now,
> the message Congress is getting is that the biggest priority in IoT is to
> force devices to accept software updates.
>
> Well no it is not. Software updates are only going to make things worse i=
f
> you don't do it securely. The update mechanism provides the attacker with=
 a
> vector to own the machine entirely unless you authenticate. Do you think
> the IoT folk do that right?
>
>
=E2=80=8BOK so there is a bill now and it does address authentication.=E2=
=80=8B Which is
good.

=E2=80=8B=E2=80=8B

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">On =
Sun, Aug 13, 2017 at 10:57 AM, Phillip Hallam-Baker <span dir=3D"ltr">&lt;<=
a href=3D"mailto:phill@hallambaker.com" target=3D"_blank">phill@hallambaker=
.com</a>&gt;</span> wrote:<br></div><div class=3D"gmail_extra"><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div style=
=3D"font-size:small"><br></div><div class=3D"gmail_extra"><div class=3D"gma=
il_quote"><div style=3D"font-size:small">=E2=80=8BI think we are sleepwalki=
ng into a similar disaster with IoT. Right now, the message Congress is get=
ting is that the biggest priority in IoT is to force devices to accept soft=
ware updates.</div><div style=3D"font-size:small"><br></div><div style=3D"f=
ont-size:small">Well no it is not. Software updates are only going to make =
things worse if you don&#39;t do it securely. The update mechanism provides=
 the attacker with a vector to own the machine entirely unless you authenti=
cate. Do you think the IoT folk do that right?</div><div style=3D"font-size=
:small"><br></div></div></div></div></blockquote><div><br></div><div class=
=3D"gmail_default" style=3D"font-size:small">=E2=80=8BOK so there is a bill=
 now and it does address authentication.=E2=80=8B Which is good.</div></div=
><br></div><div class=3D"gmail_extra"><div class=3D"gmail_default" style=3D=
"font-size:small">=E2=80=8B=E2=80=8B</div><br></div></div>

--94eb2c1cc94698aac30556af7e8b--


From nobody Sun Aug 13 23:46:22 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42C2B126CB6 for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 23:46:20 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EHwjp0HbXd4h for <ietf@ietfa.amsl.com>; Sun, 13 Aug 2017 23:46:19 -0700 (PDT)
Received: from mail-wr0-x22d.google.com (mail-wr0-x22d.google.com [IPv6:2a00:1450:400c:c0c::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9A54126C2F for <ietf@ietf.org>; Sun, 13 Aug 2017 23:46:18 -0700 (PDT)
Received: by mail-wr0-x22d.google.com with SMTP id l9so8659112wrl.1 for <ietf@ietf.org>; Sun, 13 Aug 2017 23:46:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:content-transfer-encoding:mime-version:date:subject:message-id :references:in-reply-to:to; bh=Ir2ducDYPNz7tT6p8RFPeFRKJgVGOYmgRjf07rhcOUE=; b=HR2UoPjLKYU1UMfknQhHBF+qMNW6mkOIVnfT3PcuLaNsTIcUb955cPp2vRYmZBXZmW wzRwj8QCy49sML+9NOvTfEh537zFs5Pc6ESXg1Vr7zwgL8CLxypV+CaDqDFT3n6JMCb7 F8kIFzFg1PVTecG9wkZ8bQfBx9c/6qrHaoF/YArIfbcanoeVLVZUWG4W673cg3cYEL/l wuWykHkcZ9zhyDqv1H6XGvY5jBJgyU+jq2Va27u2MwhgUKt5xgVuDTc+WJdbiZpFKZTm uFj70XL+TPI7NpZwfyZEO9yLGz5JGyO9T2SB+Zcqn1cHi21sGI3h/i4jbFV26iHBJDfJ AhHQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version:date :subject:message-id:references:in-reply-to:to; bh=Ir2ducDYPNz7tT6p8RFPeFRKJgVGOYmgRjf07rhcOUE=; b=MZnZNBu7jR8VmazCRP044H2rF3rq9wtq2JOat7P+mgAqN/L5qzq5Wk4sCtdEBL/OPI X6vI1sybXlh2UBx+9RdSIRoYS6ZPuyLvRUO0KZ1rOooi3ZbA9OKk/R23QHBAwq+yR2jE V7ktf4rqcrqmHp8llguov+HRnug/lAP9CXIHyuD8AJhMhbt9dmMPKSQoR10hHav9Pjfw OVaIfGtaHI1VZZyxGc6VRWGa98wfsbZr0P/f8QQLKpNlyuU1hExT12aJMMMIbrusOz98 EQbwOHeKs8MWKl7tDiUAa+lKGOqAC3glWEzLMKNdeMPI3+XgOni3qdNgmh/5X5FnKbaj 5PiQ==
X-Gm-Message-State: AHYfb5jX585JmeW11BQnQULoYU9DeaIQBQhZPO4C8vniGR7WTave+jWf PNw9zTi8HpNcuwaFm0E=
X-Received: by 10.223.148.162 with SMTP id 31mr15470401wrr.28.1502693177102; Sun, 13 Aug 2017 23:46:17 -0700 (PDT)
Received: from [192.168.2.173] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id d26sm7903827wra.92.2017.08.13.23.46.16 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 13 Aug 2017 23:46:16 -0700 (PDT)
From: Stewart Bryant <stewart.bryant@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Date: Mon, 14 Aug 2017 07:46:17 +0100
Subject: Re: Mailman attack in progress
Message-Id: <68A3BDCA-C192-4175-A94F-A57529CF7215@gmail.com>
References: <CABL0ig7VW_eNC8qEiX0+a71if1L0FnxEJn6usssQu+1Ox5nQOQ@mail.gmail.com> <CABL0ig4UT4Ebfzdf2ce1vu-Q76Ei_A7Yk=q-fkGfDU8o2VWjeA@mail.gmail.com>
In-Reply-To: <CABL0ig4UT4Ebfzdf2ce1vu-Q76Ei_A7Yk=q-fkGfDU8o2VWjeA@mail.gmail.com>
To: ietf@ietf.org
X-Mailer: iPad Mail (14G60)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PWu75nwMd1NUMJIQD9pUPwrpv9Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 06:46:20 -0000

Do we know why we are being attacked?

-Stewart

Sent from my iPad


From nobody Mon Aug 14 01:57:46 2017
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 472D513207A for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 01:57:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.92
X-Spam-Level: 
X-Spam-Status: No, score=-6.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CKegzP6tLIjH for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 01:57:43 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F15C2132076 for <ietf@ietf.org>; Mon, 14 Aug 2017 01:57:42 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.41,372,1498518000"; d="scan'208";a="18393364"
Received: from unknown (HELO baemasmds016.greenlnk.net) ([10.15.207.101]) by ukmta1.baesystems.com with ESMTP; 14 Aug 2017 09:57:40 +0100
X-IronPort-AV: E=Sophos;i="5.41,372,1498518000"; d="scan'208";a="16429728"
Received: from glkxh0004v.greenlnk.net ([10.109.2.35]) by baemasmds016.greenlnk.net with ESMTP; 14 Aug 2017 09:57:40 +0100
Received: from GLKXM0003V.GREENLNK.net ([169.254.4.199]) by GLKXH0004V.GREENLNK.net ([10.109.2.35]) with mapi id 14.03.0361.001; Mon, 14 Aug 2017 09:57:40 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Miles Fidelman <mfidelman@meetinghouse.net>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: "airborne wireless network" - anybody know anything about these folks?
Thread-Topic: "airborne wireless network" - anybody know anything about these folks?
Thread-Index: AQHTFLY0CFe5eAABsE2Fw1MooD0EVKKDjG/w
Date: Mon, 14 Aug 2017 08:57:39 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE64F3F43@GLKXM0003v.GREENLNK.net>
References: <2ab039d2-713a-f6c7-0c85-5dd1e5e2a010@meetinghouse.net> <bc582f7a-9db6-0f38-2d5b-6fcf320dfe20@meetinghouse.net>
In-Reply-To: <bc582f7a-9db6-0f38-2d5b-6fcf320dfe20@meetinghouse.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NpzcJxe8Y8lPIf02Tp9vwxDvjrA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 08:57:45 -0000

QXMgeW91IHNheSBhYm91dCBzZWVuIGJlZm9yZSAodGhvdWdoIHBhdGVudCB3YXMgMjAwMSwgc28g
aGFkIHNlZW4gbGVzcyB0aGVuKS4gQnV0IGZyb20gdGhlaXIgd2ViIHBhZ2UgIlRvZGF5IG11Y2gg
b2Ygd2hhdCBpcyByZXF1aXJlZCBpcyByZWFkaWx5IGF2YWlsYWJsZS4gVGhlIGVxdWlwbWVudCBq
dXN0IG5lZWRzIHRvIGJlIHBhY2thZ2VkIOKAnHB1cnBvc2Utc3BlY2lmaWPigJ0sIHRvIGNvbXBs
eSB3aXRoIEZBQSBhbmQgRkNDIHJlZ3VsYXRpb25zLiIgRXZlbiB3aXRob3V0IHRoZSAianVzdCIg
dGhhdCByZWFsbHkgdW5kZXJlc3RpbWF0ZXMgdGhlIGFtb3VudCBvZiBjb3N0LCB3b3JrIGFuZCBy
ZXNpc3RhbmNlIHRvIGluc3RhbGxpbmcgZXF1aXBtZW50IG9uIGFlcm9wbGFuZXMuDQoNCi0tIA0K
Q2hyaXN0b3BoZXIgRGVhcmxvdmUNClNlbmlvciBQcmluY2lwYWwgRW5naW5lZXINCkJBRSBTeXN0
ZW1zIEFwcGxpZWQgSW50ZWxsaWdlbmNlIExhYm9yYXRvcmllcw0KX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
Cg0KVDogwqArNDQgMzMwMCA0Njc1MDAgwqB8IMKgRTogY2hyaXMuZGVhcmxvdmVAYmFlc3lzdGVt
cy5jb20NCg0KQkFFIFN5c3RlbXMgQXBwbGllZCBJbnRlbGxpZ2VuY2UsIENoZWxtc2ZvcmQgVGVj
aG5vbG9neSBQYXJrLCBHcmVhdCBCYWRkb3csIENoZWxtc2ZvcmQsIEVzc2V4IENNMiA4SE4uDQp3
d3cuYmFlc3lzdGVtcy5jb20vYWkNCkJBRSBTeXN0ZW1zIEFwcGxpZWQgSW50ZWxsaWdlbmNlIExp
bWl0ZWQNClJlZ2lzdGVyZWQgaW4gRW5nbGFuZCAmIFdhbGVzIE5vOiAwMTMzNzQ1MQ0KUmVnaXN0
ZXJlZCBPZmZpY2U6IFN1cnJleSBSZXNlYXJjaCBQYXJrLCBHdWlsZGZvcmQsIFN1cnJleSwgR1Uy
IDdZUA0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogaWV0ZiBbbWFpbHRvOmll
dGYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIE1pbGVzIEZpZGVsbWFuDQpTZW50OiAx
NCBBdWd1c3QgMjAxNyAwNTozMQ0KVG86IGlldGZAaWV0Zi5vcmcNClN1YmplY3Q6ICJhaXJib3Ju
ZSB3aXJlbGVzcyBuZXR3b3JrIiAtIGFueWJvZHkga25vdyBhbnl0aGluZyBhYm91dCB0aGVzZSBm
b2xrcz8NCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSEgV0FSTklORyAhIC0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0gVGhpcyBtZXNzYWdlIG9yaWdpbmF0ZXMgZnJvbSBvdXRzaWRlIG91ciBvcmdhbmlz
YXRpb24sIGVpdGhlciBmcm9tIGFuIGV4dGVybmFsIHBhcnRuZXIgb3IgZnJvbSB0aGUgaW50ZXJu
ZXQuDQpDb25zaWRlciBjYXJlZnVsbHkgd2hldGhlciB5b3Ugc2hvdWxkIGNsaWNrIG9uIGFueSBs
aW5rcywgb3BlbiBhbnkgYXR0YWNobWVudHMgb3IgcmVwbHkuDQpGb2xsb3cgdGhlICdSZXBvcnQg
U3VzcGljaW91cyBFbWFpbHMnIGxpbmsgb24gSVQgbWF0dGVycyBmb3IgaW5zdHJ1Y3Rpb25zIG9u
IHJlcG9ydGluZyBzdXNwaWNpb3VzIGVtYWlsIG1lc3NhZ2VzLg0KLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KSGkgRm9sa3MsDQoNCkFu
eWJvZHkga25vdyBhbnl0aGluZyBhYm91dCB0aGVzZSBmb2xrczoNCmh0dHA6Ly93d3cuYWlyYm9y
bmV3aXJlbGVzc25ldHdvcmsuY29tL2luZGV4LmFzcA0KDQpJIGNhbWUgYWNyb3NzIGFuIGFkIGZy
b20gdGhlbSwgaW4gYW4gaW4tZmxpdGUgbWFnYXppbmUgLSB0aGV5IGNsYWltIHRvIGJlIGRldmVs
b3BpbmcgYSBmbHlpbmcgbWVzaCBuZXR3b3JrLCB3aXRoIG5vZGVzIGhhbmdpbmcgb2ZmIGNvbW1l
cmNpYWwgYWlybGluZXJzLiAgKE1vcmUgbGlrZSBhbiBpbnZlc3RtZW50IHBpdGNoIHRoYW4gYSB0
ZWNobmljYWwgYWQsIGJhY2tlZCBieSBhIHdlYiBzaXRlIHRoYXQgd2FzIG1vcmUgc2l6emxlIHRo
YW4gc3Vic3RhbmNlLikNCg0KSXQgc3VyZSBzZWVtcyBsaWtlIGEgbmVhdCBjb25jZXB0LCBhbmQg
dGhleSBzZWVtIHRvIGhhdmUgc29tZSBzZXJpb3VzIGFpcmxpbmUgaW5kdXN0cnkgY29ubmVjdGlv
bnMgLSBidXQgYSBiaXQgbGlnaHQgb24gdGhlIHRlY2hub2xvZ3kgc2lkZS4NCg0KVGhleSBhbHNv
IG1ha2UgYSBsb3Qgb2YgYSBwYXRlbnQgdGhleSBoYXZlIC0gYnV0IGl0IHNlZW1zIHRvIGJlIHN0
dWZmIHRoYXQgd2UndmUgYWxsIHNlZW4gYmVmb3JlIGluIHRhY3RpY2FsIG5ldHdvcmtpbmcgYW5k
IHNvbWUgb2YgdGhlIEFpciBGb3JjZSdzIGFpcmJvcm5lIG5ldHdvcmsgaW5pdGlhdGl2ZXMuDQoN
CkFueXdheS4uLiBhbnlib2R5IGtub3cgdGhlc2UgZm9sa3M/ICBBcmUgdGhleSBmb3IgcmVhbD8N
Cg0KTWlsZXMgRmlkZWxtYW4NCg0KcC5zLiBBbHNvIG9mIHBvc3NpYmxlIGludGVyZXN0OiBUaGVz
ZSBmb2xrczogaHR0cHM6Ly93d3cuYW5hbHl0aWNhbHNwYWNlLmNvbSAtIGFyZSBhYm91dCB0byBs
YXVuY2ggYSBjb25zdGVsbGF0aW9uIG9mIExFTyBjdWJlc2F0cywgYWxzbyB3aXRoIHRoZSBpbnRl
bnQgb2YgZG9pbmcgaGlnaCBiYW5kd2lkdGggbWVzaCBuZXR3b3JraW5nLCB3aXRoIGxhc2VyIHVw
L2Rvd25saW5rcyB0byBjdXN0b21lcnMgLSBubyBuZWVkIGZvciBiaWcgZ3JvdW5kIHN0YXRpb25z
LiAgVGhleSBzZWVtIGEgbG90IG1vcmUgc3Vic3RhbnRpYWwgLSBEcmFwZXIgTGFicyB0aWUgaW4g
YW5kIHN1Y2guDQoNCi0tDQpJbiB0aGVvcnksIHRoZXJlIGlzIG5vIGRpZmZlcmVuY2UgYmV0d2Vl
biB0aGVvcnkgYW5kIHByYWN0aWNlLg0KSW4gcHJhY3RpY2UsIHRoZXJlIGlzLiAgLi4uLiBZb2dp
IEJlcnJhDQoNCioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqClRoaXMgZW1haWwgYW5kIGFueSBhdHRhY2htZW50cyBhcmUg
Y29uZmlkZW50aWFsIHRvIHRoZSBpbnRlbmRlZApyZWNpcGllbnQgYW5kIG1heSBhbHNvIGJlIHBy
aXZpbGVnZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZApyZWNpcGllbnQgcGxlYXNlIGRl
bGV0ZSBpdCBmcm9tIHlvdXIgc3lzdGVtIGFuZCBub3RpZnkgdGhlIHNlbmRlci4KWW91IHNob3Vs
ZCBub3QgY29weSBpdCBvciB1c2UgaXQgZm9yIGFueSBwdXJwb3NlIG5vciBkaXNjbG9zZSBvcgpk
aXN0cmlidXRlIGl0cyBjb250ZW50cyB0byBhbnkgb3RoZXIgcGVyc29uLgoqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKgo=


From nobody Mon Aug 14 04:44:43 2017
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88B6B126BFD for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 04:44:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mG-FuJ6b_EdN for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 04:44:40 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35A60120713 for <ietf@ietf.org>; Mon, 14 Aug 2017 04:44:40 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id x3so81551137oia.1 for <ietf@ietf.org>; Mon, 14 Aug 2017 04:44:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Scfu+gu6NTVzxWarKPNNLL3IYpAhf5DB6gEAi+8rtcQ=; b=M14XXLz05StaJm9yvmRxF23r6T2GDIa9nEsw4mky7TTsquxA0XDllgneDDiNqCC8mo tc0D7et9jzn0A8JBLypob8vO6loo0mk/F/Sm9r/C8OkL2AfuwtPDGWIeADbwZ5Guznc4 sVXZl86LqU0YjD9apxCEF8Y45TfGKIeHTsgU2gxFWouHKaIKqqldHroEoEJ8zY/4Mkb0 92TRKXfDp3dwwEUCxldRYSoSWBNLMeTXGju1wGBWfhjlbro2uB0gtd5MC5XowDiwg8kI +FxCHmDTVRwJV440jbvjfhSv8oq1aeKoYGDCOBXmaHbfGmggibw/8HVUbWOoewByzal7 mzDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Scfu+gu6NTVzxWarKPNNLL3IYpAhf5DB6gEAi+8rtcQ=; b=iihLrDk8Js6XiBbEBE15jer22BgRxu2rSwN1OpIrll2v+vhoJMQTumQttJKjOmidC8 kKUXHuzIs8c56bqE3zBV2XAG7Ch75QzWl7m2UyEq1DGNfz/jrcAp21AlxCyGoeghTi+N ulltW/2/otYANoudwITAAnXKiCgAReEMGG5ueFw2qK11XVhMC6vnb+/0GG5cPE48iv8R 7/3uu4joGUlSNeu9aleaXx+eB4mw3CqOILiBvlJuZ4Iwxjuh2UYw+YBPWoB+NGpQF8f6 3tnAsB/j1AlEXMcDbqjppQMGPQcBbTUfnI7jYyrny+QO7HeCqTN5qsp46JBEGsubqFkW +Q4Q==
X-Gm-Message-State: AHYfb5hMYn6SJEQZL/8iSgR8QMDcbUkTTBS8nbfGUV1BqHVr4g7BQpAS Ey2Z7nVcbaovwyN9OAo4IHnKicknvw==
X-Received: by 10.202.173.209 with SMTP id w200mr24959774oie.170.1502711079630;  Mon, 14 Aug 2017 04:44:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.232.34 with HTTP; Mon, 14 Aug 2017 04:44:19 -0700 (PDT)
In-Reply-To: <68A3BDCA-C192-4175-A94F-A57529CF7215@gmail.com>
References: <CABL0ig7VW_eNC8qEiX0+a71if1L0FnxEJn6usssQu+1Ox5nQOQ@mail.gmail.com> <CABL0ig4UT4Ebfzdf2ce1vu-Q76Ei_A7Yk=q-fkGfDU8o2VWjeA@mail.gmail.com> <68A3BDCA-C192-4175-A94F-A57529CF7215@gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Mon, 14 Aug 2017 07:44:19 -0400
Message-ID: <CAA=duU2UhGKDYoVrcGoZBqXhMvNn9PkHj-RUW7Z4pR_ZBPr1xA@mail.gmail.com>
Subject: Re: Mailman attack in progress
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113cf68219fdcf0556b5302e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KB4U72Pnf2gQ-WVl-zUcP2ZnMIY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 11:44:42 -0000

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

Stewart,

I suspect that any organization working on hardening the Internet=E2=80=99s=
 (and
its protocols) security would be an attractive target for such attacks.

Cheers,
Andy


On Mon, Aug 14, 2017 at 2:46 AM, Stewart Bryant <stewart.bryant@gmail.com>
wrote:

> Do we know why we are being attacked?
>
> -Stewart
>
> Sent from my iPad
>
>

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

<div dir=3D"ltr">Stewart,<div><br></div><div>I suspect that any organizatio=
n working on hardening the Internet=E2=80=99s (and its protocols) security =
would be an attractive target for such attacks.</div><div><br></div><div>Ch=
eers,</div><div>Andy</div><div><br></div></div><div class=3D"gmail_extra"><=
br><div class=3D"gmail_quote">On Mon, Aug 14, 2017 at 2:46 AM, Stewart Brya=
nt <span dir=3D"ltr">&lt;<a href=3D"mailto:stewart.bryant@gmail.com" target=
=3D"_blank">stewart.bryant@gmail.com</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">Do we know why we are being attacked?<br>
<br>
-Stewart<br>
<br>
Sent from my iPad<br>
<br>
</blockquote></div><br></div>

--001a113cf68219fdcf0556b5302e--


From nobody Mon Aug 14 07:09:55 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BE621321EF for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 07:09:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sjCI7yeWmat2 for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 07:09:50 -0700 (PDT)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C4A3132055 for <ietf@ietf.org>; Mon, 14 Aug 2017 07:09:50 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id m86so40104027lfi.4 for <ietf@ietf.org>; Mon, 14 Aug 2017 07:09:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=xoy3gUh/nPMJ/57/cs+0Uwdu7cBqCGfQ0hA/V2Lz/38=; b=J+IM/Pxx0+7CgB4LwK2rn3typBMTHZD1hZgFj7W5bErhLXvhd7G3YN45nuMkB/PnD3 c7AyikQUlNRH1tnufWrk81KWyrGX/jGfDcHd8GQcTP5eZ8EfZYr3+cLoRWwaPzgjAdaZ JLW//p+/6cIW2mmnGEXupUwxlnkqFsyGBvKV/7rivlja0G0cLhH3Q+tzTK+6K3UpTFFx AOEeSfj0sShMsIHyOodM4JZJtaBhIXKc1GoM9ZdG/lHmZb3v2ZtELcCDxAqTCp5Qo6rX jq7Q9FSiQf631WTDv94d3K+1MrXtzv+zrxorClGzoRdAMlki+KID7nLjua8O/RooAzzm M0UQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=xoy3gUh/nPMJ/57/cs+0Uwdu7cBqCGfQ0hA/V2Lz/38=; b=GY6L8shYsFl6etM0182OqGF2dSWr40Zgr/f+GsozNtRycX76thBtHWWOMo9CN4BD8a cLqLSpH1cj/0yMss0EpzglK0Kez5qwXBDzrUaui5jASI7fGoTsxm7lJcwm4OWFK+R+yA 9W8v2qT3BtZAZg790AqeJ2cs8wN5UkBd3EdQbXEianXO7Td8oTD64lSma9aD25yd0BDG Z1mC62sDi3Fkt5OFL6fzEXC17p2lABFTnMgo1ecb5X9KfXnFnOJuLX1aLmlcfR0nKx8m 91RGkofCYcTcDSf/Ru1fR4TUTFI5vf3iwM/UYyAUNn37yjzTzxVCZiLixa5OgsxvMle9 uRAA==
X-Gm-Message-State: AHYfb5iEiqfi+OZkGa7iGd1QDmWCaNu5DZHBobrj/j3lcnNL0C3ixq4u Tic0v2EHcqAeu1JxtBdb5LBeEJvZtQ==
X-Received: by 10.46.92.137 with SMTP id q131mr8077526ljb.102.1502719788551; Mon, 14 Aug 2017 07:09:48 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.25.142.199 with HTTP; Mon, 14 Aug 2017 07:09:47 -0700 (PDT)
In-Reply-To: <CAA=duU2UhGKDYoVrcGoZBqXhMvNn9PkHj-RUW7Z4pR_ZBPr1xA@mail.gmail.com>
References: <CABL0ig7VW_eNC8qEiX0+a71if1L0FnxEJn6usssQu+1Ox5nQOQ@mail.gmail.com> <CABL0ig4UT4Ebfzdf2ce1vu-Q76Ei_A7Yk=q-fkGfDU8o2VWjeA@mail.gmail.com> <68A3BDCA-C192-4175-A94F-A57529CF7215@gmail.com> <CAA=duU2UhGKDYoVrcGoZBqXhMvNn9PkHj-RUW7Z4pR_ZBPr1xA@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Mon, 14 Aug 2017 10:09:47 -0400
X-Google-Sender-Auth: woVuzhCZmA92QrlXrDTSGAlTnDI
Message-ID: <CAMm+LwiWcqNAc9DC5yBpeYoNqtPWR6cYYrQ7+XB5_XYvWMEFCw@mail.gmail.com>
Subject: Re: Mailman attack in progress
To: "Andrew G. Malis" <agmalis@gmail.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c1b548a31947b0556b737b9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/belnniVngilc_aBmAjVnuDo6zUc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 14:09:53 -0000

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

On Mon, Aug 14, 2017 at 7:44 AM, Andrew G. Malis <agmalis@gmail.com> wrote:

> Stewart,
>
> I suspect that any organization working on hardening the Internet=E2=80=
=99s (and
> its protocols) security would be an attractive target for such attacks.
>
> Cheers,
> Andy
>

=E2=80=8BWhen =E2=80=8BI started working on spam when the crisis hit, one o=
f the mail
admins told me that I was getting 1/3 of the email sent to VeriSign which
had 2000-3000 employees at the time.

Of course, it wasn't long before the rest of the organization caught up. It
is possible this is IETF only or it might just be someone is hammering
every monarch mailing list front end.

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">On =
Mon, Aug 14, 2017 at 7:44 AM, Andrew G. Malis <span dir=3D"ltr">&lt;<a href=
=3D"mailto:agmalis@gmail.com" target=3D"_blank">agmalis@gmail.com</a>&gt;</=
span> wrote:<br></div><div class=3D"gmail_extra"><div class=3D"gmail_quote"=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Stewart,<div><br></div><di=
v>I suspect that any organization working on hardening the Internet=E2=80=
=99s (and its protocols) security would be an attractive target for such at=
tacks.</div><div><br></div><div>Cheers,</div><div>Andy</div></div></blockqu=
ote><div>=C2=A0</div><div><div class=3D"gmail_default" style=3D"font-size:s=
mall">=E2=80=8BWhen =E2=80=8BI started working on spam when the crisis hit,=
 one of the mail admins told me that I was getting 1/3 of the email sent to=
 VeriSign which had 2000-3000 employees at the time.</div><div class=3D"gma=
il_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default=
" style=3D"font-size:small">Of course, it wasn&#39;t long before the rest o=
f the organization caught up. It is possible this is IETF only or it might =
just be someone is hammering every monarch mailing list front end.</div><br=
></div><div>=C2=A0</div></div></div></div>

--94eb2c1b548a31947b0556b737b9--


From nobody Mon Aug 14 08:09:50 2017
Return-Path: <jcurran@istaff.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADD7213234E for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 08:09: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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xwmkO7AQsfQQ for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 08:09:46 -0700 (PDT)
Received: from outbound1a.ore.mailhop.org (outbound1a.ore.mailhop.org [54.213.22.21]) (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 DC2BE1321AF for <ietf@ietf.org>; Mon, 14 Aug 2017 08:09:46 -0700 (PDT)
X-MHO-User: 9bc38cac-8102-11e7-950d-03a3531dacf2
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 100.36.32.177
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from geode.istaff.org (unknown [100.36.32.177]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 9bc38cac-8102-11e7-950d-03a3531dacf2; Mon, 14 Aug 2017 15:09:46 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by geode.istaff.org (Postfix) with ESMTP id 6FD1E13998C1; Mon, 14 Aug 2017 11:09:44 -0400 (EDT)
X-Virus-Scanned: amavisd-new at istaff.org
Received: from geode.istaff.org ([127.0.0.1]) by localhost (geode.istaff.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 359s48yLkSi3; Mon, 14 Aug 2017 11:09:43 -0400 (EDT)
Received: from [10.1.11.20] (unknown [67.51.226.100]) by geode.istaff.org (Postfix) with ESMTPSA id 4D5FB13998B3; Mon, 14 Aug 2017 11:09:43 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: John Curran <jcurran@istaff.org>
In-Reply-To: <m2r2wwt4vx.wl-randy@psg.com>
Date: Mon, 14 Aug 2017 09:09:42 -0600
Cc: IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F4D3D8A8-D536-4054-838D-320B3A7EA4FD@istaff.org>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <6C3D3B7C-9732-4BD2-97F6-F03A00CB6781@fugue.com> <3A586681-AAEC-4395-B386-450C0AE7950F@vpnc.org> <m2r2wwt4vx.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6XfeLIbBtOxOsGXcXNrUBLKvUp4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 15:09:48 -0000

On 31 Jul 2017, at 8:10 PM, Randy Bush <randy@psg.com> wrote:
> ...
> in our meager experience, pure ipv6 with no hack to get to the ipv4
> internet is not viable from the user perspective, period.  it won't be
> for many years.  yes, this is a tragic failure; and we know where the
> root causes lie.
>=20
> nat64/dns64 is useful in constrained circumstances.  the ietf meeting
> network is not one of them; as there is far too wide a variety of =
users,
> some with laptops they can't even control due to IT departments, many
> use vpns, applications are still incompatible, ...  this is yet =
another
> tragedy.
>=20
> the biggest obstacle to improvement on both these fronts is the denial
> that there are serious problems, and hence far too little serious work
> being done to ameliorate them.
>=20
> but, no matter how hard we work, there is not going to be a magic day
> when it all just works.  ipv6 is on-the-wire incompatible with ipv4;
> so it is gonna be hacks; and hacks are tecnhnical debt.

Randy -

Agreed on all of the above =E2=80=93 it doesn=E2=80=99t appear that =
forced usage of IPv6+nat64=20
is really compatible with an IETF network "where people can get their =
work done=20
with absolutely minimal speedbumps=E2=80=9D

However, the draft proposing same notes that more IPv6/nat64 usage at =
IETF may=20
very well help to identify applications, services, or use cases that are =
not entirely=20
compatible with that setup, and that seems worthwhile - particularly if =
the lessons
learned are published in a I-D afterwards.

To that end, would it be possible for those behind the "IPv6-only Wi-Fi =
for IETF=E2=80=9D
draft to partner with the NOC at the upcoming meeting to help debug =
issues that=20
are reported on =E2=80=9Cietf-nat64* and publish the results?  The IETF =
does have a wide
variety of users, which is really helpful in finding edge cases with =
protocols that
might have issues and otherwise go undiscovered.  If it were may clear =
(e.g. during
the opening) that there is a goal to put the =E2=80=9Cietf-nat64=E2=80=9D =
network through its paces
and that there would be a post-mortem I-D as a result, I suspect quite a =
few folks
would at least give that setup a try for a while, with the goal of =
finding and reporting
breakage.=20

/John



From nobody Mon Aug 14 08:41:33 2017
Return-Path: <derek@ihtfp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EF0B132376; Mon, 14 Aug 2017 08:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.99
X-Spam-Level: 
X-Spam-Status: No, score=-1.99 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ihtfp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hFye6OQpR50D; Mon, 14 Aug 2017 08:41:31 -0700 (PDT)
Received: from mail2.ihtfp.org (MAIL2.IHTFP.ORG [204.107.200.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85131120720; Mon, 14 Aug 2017 08:41:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail2.ihtfp.org (Postfix) with ESMTP id 399D0E2049; Mon, 14 Aug 2017 11:41:27 -0400 (EDT)
Received: from mail2.ihtfp.org ([127.0.0.1]) by localhost (mail2.ihtfp.org [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 17797-01; Mon, 14 Aug 2017 11:41:13 -0400 (EDT)
Received: from securerf.ihtfp.org (unknown [IPv6:fe80::530:248d:f760:bb62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mocana.ihtfp.org", Issuer "IHTFP Consulting Certification Authority" (verified OK)) by mail2.ihtfp.org (Postfix) with ESMTPS id BD5C1E2039; Mon, 14 Aug 2017 11:41:12 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ihtfp.com; s=default; t=1502725273; bh=sXc0t1ENxHcvNgq9W7k/fh+956XBFctOTbtPcIPpehI=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=BinmzsKm1q9e8o6XIQ1icSd+gimJ7eVThNNzwVpZUB6Pep8eSTOhHv4zZOWePT28j jekMcpfgfYeW1z2H0iYHvcYqI5ElluGsx3U6yi5ENULnKyylwnscPQ4J2gfrCzOgBL JeoKswHCJ/eifJKM3rNH3nURou79h7BIaDTY6BaM=
Received: (from warlord@localhost) by securerf.ihtfp.org (8.15.2/8.15.2/Submit) id v7EFfCaF029250; Mon, 14 Aug 2017 11:41:12 -0400
From: Derek Atkins <derek@ihtfp.com>
To: Glen <glen@amsl.com>
Cc: ietf-announce@ietf.org, ietf@ietf.org
Subject: Re: Mailman attack in progress
References: <CABL0ig7VW_eNC8qEiX0+a71if1L0FnxEJn6usssQu+1Ox5nQOQ@mail.gmail.com> <CABL0ig4UT4Ebfzdf2ce1vu-Q76Ei_A7Yk=q-fkGfDU8o2VWjeA@mail.gmail.com>
Date: Mon, 14 Aug 2017 11:41:12 -0400
In-Reply-To: <CABL0ig4UT4Ebfzdf2ce1vu-Q76Ei_A7Yk=q-fkGfDU8o2VWjeA@mail.gmail.com> (glen@amsl.com's message of "Sun, 13 Aug 2017 20:08:38 -0700")
Message-ID: <sjma832f97r.fsf@securerf.ihtfp.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: Maia Mailguard 1.0.2a
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DRuM2NsIpxm5j6Nve4YZws5NbcU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 15:41:32 -0000

Glen,

Glen <glen@amsl.com> writes:

> A brief update on our Mailman attack.
>
> After analyzing the attack pattern, I've added a new long-term measure
> into Mailman that is preventing these botnet subscription attempts
> from being honored (whilst still allowing humans to subscribe).

When you have time, could you elaborate on what long-term countermeasure
you put into place?  Enquiring minds want to know.

> Thank you for your patience during this interruption.

Thank you for your tireless efforts!

> Glen

-derek

-- 
       Derek Atkins                 617-623-3745
       derek@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant


From nobody Mon Aug 14 09:25:29 2017
Return-Path: <glen@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5B5413228D for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 09:25:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.701
X-Spam-Level: 
X-Spam-Status: No, score=-3.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tFxtpr-NQswA for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 09:25:26 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60B991321B9 for <ietf@ietf.org>; Mon, 14 Aug 2017 09:25:26 -0700 (PDT)
Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTPS id 0BBB51C3A5D for <ietf@ietf.org>; Mon, 14 Aug 2017 09:25:02 -0700 (PDT)
Received: from mail-qt0-f178.google.com (mail-qt0-f178.google.com [209.85.216.178]) by c8a.amsl.com (Postfix) with ESMTPSA id D19C01C3437 for <ietf@ietf.org>; Mon, 14 Aug 2017 09:25:01 -0700 (PDT)
Received: by mail-qt0-f178.google.com with SMTP id v29so54375526qtv.3 for <ietf@ietf.org>; Mon, 14 Aug 2017 09:25:26 -0700 (PDT)
X-Gm-Message-State: AHYfb5iKdSpA4R+9yRCtxHVNwhuwTsXMBMep6J0xSWvWlTywr6k5UyQB ajsDkf7WA1qp+H0VRWNFdH6gGWwp9g==
X-Received: by 10.200.42.181 with SMTP id b50mr32231091qta.224.1502727925290;  Mon, 14 Aug 2017 09:25:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.55.31.142 with HTTP; Mon, 14 Aug 2017 09:25:04 -0700 (PDT)
In-Reply-To: <sjma832f97r.fsf@securerf.ihtfp.org>
References: <CABL0ig7VW_eNC8qEiX0+a71if1L0FnxEJn6usssQu+1Ox5nQOQ@mail.gmail.com> <CABL0ig4UT4Ebfzdf2ce1vu-Q76Ei_A7Yk=q-fkGfDU8o2VWjeA@mail.gmail.com> <sjma832f97r.fsf@securerf.ihtfp.org>
From: Glen <glen@amsl.com>
Date: Mon, 14 Aug 2017 09:25:04 -0700
X-Gmail-Original-Message-ID: <CABL0ig7M0F0WDBTA9qqkEDRt9BUBs5uVaCkmtdn3TY8Xv1ik3A@mail.gmail.com>
Message-ID: <CABL0ig7M0F0WDBTA9qqkEDRt9BUBs5uVaCkmtdn3TY8Xv1ik3A@mail.gmail.com>
Subject: Re: Mailman attack in progress
To: ietf@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9nb1cGVeArkJ1diAigGIzbn9XsY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 16:25:28 -0000

On Mon, Aug 14, 2017 at 8:41 AM, Derek Atkins <derek@ihtfp.com> wrote:
>> After analyzing the attack pattern, I've added a new long-term measure
> When you have time, could you elaborate on what long-term countermeasure
> you put into place?  Enquiring minds want to know.

Good morning everyone (adjusted for your local timezone as appropriate)...

I've had several requests of this type this morning.

The attack against Mailman was sophisticated.  It spoke not only to a
good understanding of Mailman, but also, possibly, to a good
understanding of what we have done to block attacks in the past.  It
was automated, yes, and widely distributed... but it was well adapted
to the current state of Mailman today.  The attack pattern suggests to
me that the primary goal was not so much flooding a few (obviously
fake) target addresses with email, but, rather, forcing email
providers to block the IETF (and any other impacted users) to prevent
the flood of mail we were generating as a result of the attack.

Although to my great disappointment I don't have the luxury of
participating in the IETF as a contributor, I do take the IETF's
mission very seriously.  I've learned in my years of associating with
many of you that the IETF faces strong opposition from individuals,
groups and governments who do *not* want global communications and
connectivity to work... and that the IETF takes its ability to reach
out to - and include - individuals around the world who want to
participate - very seriously.  As a result, I personally consider this
attack to be both directed, and serious.

I know that everyone is interested in what I found and what I did, and
I get that.. I would be too!.  On the other hand, *I* (and my small
team) are the ones who get woken up at 3 in the morning local time
(inevitably!) to deal with these types of things.  And I have no
illusions that the botnet authors and users are going to just "go
away" - as with the spammers, it's a constant battle of "us vs
them"... and I really don't feel like enabling their childishness
anymore.

So, needless to say, I am hesitant to just openly describe attack
countermeasures on a public list.  :-)   I'm sorry for that - I truly
am - because as I said *I* would want to know, too.   Although in this
case it's not a big deal, just a tweak or two, but adjustments that,
were they published, would be much easier for the bot authors to
"adjust for".  For all of these reasons, I'm not comfortable just
unilaterally exposing the IETF's defenses here... and I hope that you
will all understand this.  I am preparing a summary report to the TMC
outlining what was done, and I need to leave it to them to determine
if - and how best - to present the information to interested persons.

Thanks for your support as we deal with the ongoing threats to the IETF.

Glen
--
Glen Barney
IT Director
AMS (IETF Secretariat)


From nobody Mon Aug 14 12:01:58 2017
Return-Path: <vaibhavsinghacads@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94DFC1323F9 for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:01:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X66hfmK1FmW1 for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:01:54 -0700 (PDT)
Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D06BF132399 for <ietf@ietf.org>; Mon, 14 Aug 2017 12:01:53 -0700 (PDT)
Received: by mail-it0-x22e.google.com with SMTP id m34so111005iti.1 for <ietf@ietf.org>; Mon, 14 Aug 2017 12:01:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=u3uVuTOZp2F/GwKNTXF2NIe9F9ThEI799mGNQM7L5eA=; b=NFV8a3ZNhjX3C3N01+YQid3g9tzZ5tPrdrbp4QnfSNtnYXrjeev+wSsv8DcFqVQCkr 5zYed3qxG9L5ZhvQ7JbfDTxPzb4tFU7hRdjapwOn9me60K2slQqmWCntMf7pQwlwWsjZ KYhOKNQIEEYkyc8rS6C3i90nRm1AzFswyM0WGYMp+4BSj2KYgTpAe2oQcBL9xyTJIj8h UgCTd2TjyBEQYHOgf8Tltok0RwfGlS4oDb/BqxvjUoFBJcZU7IVLdxJJnpevlP15Of/u nbjMUjnMoaelL9b939uszVbWZFht+3/BGkFgEOtXfOITYZtYN89wTKw/p3luvzzxytgZ qTDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=u3uVuTOZp2F/GwKNTXF2NIe9F9ThEI799mGNQM7L5eA=; b=I9BVGj+5ZANAeTmXiZDcQy7daXJgDhrNSuX6yqhga8j9plWTBB9cVqX4JkHIG66dHn ZBN9Xd6KKK5ypxx5nZxMOuC7ZRJUaRXdGjx3O/oP/Qid4XYP6G1odqCFiAgk3Pr3rZHe z3mGk7iGGWp0dVfjnNyselZ+wliqbGlAdm7BLyYVJ6JysN0MNlIuw9UetNnKKGWYFinK xnGp/l03S+fWmeZmCu+5WZvKHfUjqENRhIiz/yBM29YWL3mhqXh8v5Ik2u5pWTtLcYuU G8c/63nmEcnU4ynBY7iv6k2Ev8RRO+pKpNyez6uSbseNKfRliaZIyARWfyZL3aO5XZtp xZfA==
X-Gm-Message-State: AHYfb5glUCyNbawxuV0Ue6stjjsm++O7bSOFcgb7GsJDZglWc3XiQ8uG nBEcBl/vl0wxlHqJgvW3n1gSj+629zHz
X-Received: by 10.36.243.77 with SMTP id t13mr15794iti.50.1502737312948; Mon, 14 Aug 2017 12:01:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.0.208 with HTTP; Mon, 14 Aug 2017 12:01:52 -0700 (PDT)
From: vaibhav singh <vaibhavsinghacads@gmail.com>
Date: Tue, 15 Aug 2017 00:31:52 +0530
Message-ID: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com>
Subject: Scope for self-destructing email?
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f403045fb318baa61d0556bb4bd4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vDgc5yI8hkkITEC9i_eAiRpWLPQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 19:01:56 -0000

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

Hi,

As some of you may already know, General Data Protection Regulation (GDPR),
about to be enforced in the EU within months, and calls for strict
regulations for Right to rectify communications, Right to be forgotten ,
Pseudonymisation and Data portability.

With regards to this, me and my friends were thinking about the idea of a
self-destructing email, wherein the sender will mark the mail to be
destroyed (expunged from the server) once the receiver(s) have finished
reading it/after a time period chosen by the sender.

Another enhancement to this idea was a notification which will be sent from
some (Exploding email RFC) compliant MUA, in case the receiver refuses to
delete the email from the client. (I know Snapchat is a poor example here,
but they apparently send notifications to the originator of the snap in
case any receiver tries to capture the screenshot of the snap. This is, in
theory, what we are trying to do here).

I would also like to know about things (working groups, internet drafts
etc) which are being done to enforce GDPR to
email and Instant Messaging especially.

-- 

Regards,
Vaibhav Singh

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

<div dir=3D"ltr"><div><div><div>Hi,<br><br></div>As some of you may already=
 know, General Data Protection Regulation (GDPR), about to be enforced in t=
he EU within months, and calls for strict regulations for  Right to rectify=
 communications, Right to be forgotten , Pseudonymisation and Data portabil=
ity.<br><br></div>With regards to this, me and my friends were thinking abo=
ut the idea of a self-destructing email, wherein the sender will mark the m=
ail to be destroyed (expunged from the server) once the receiver(s) have fi=
nished reading it/after a time period chosen by the sender.<br><br></div>An=
other enhancement to this idea was a notification which will be sent from s=
ome (Exploding email RFC) compliant MUA, in case the receiver refuses to de=
lete the email from the client. (I know Snapchat is a poor example here, bu=
t they apparently send notifications to the originator of the snap in case =
any receiver tries to capture the screenshot of the snap. This is, in theor=
y, what we are trying to do here).<br><div><div><div>
<div><div><br></div><div>I would also like to know about things (working gr=
oups, internet drafts etc) which are being done to enforce GDPR to <br></di=
v><div>email and Instant Messaging especially.<br></div><div><br></div><div=
>-- <br><div class=3D"gmail_signature"><div dir=3D"ltr"><div><br></div>Rega=
rds,<div>Vaibhav Singh</div></div></div>
</div></div></div></div></div></div>

--f403045fb318baa61d0556bb4bd4--


From nobody Mon Aug 14 12:14:33 2017
Return-Path: <moritz30@moritz30.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECEE813240D for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:14:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.08
X-Spam-Level: *
X-Spam-Status: No, score=1.08 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.723, MISSING_MIMEOLE=1.899, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KlGI9_lqoGzk for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:14:30 -0700 (PDT)
Received: from sender-of-o52.zoho.com (sender-of-o52.zoho.com [135.84.80.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59364132408 for <ietf@ietf.org>; Mon, 14 Aug 2017 12:14:30 -0700 (PDT)
Received: from [10.53.190.197] (x590feec5.dyn.telefonica.de [89.15.238.197]) by mx.zohomail.com with SMTPS id 1502738063227750.3543644352833; Mon, 14 Aug 2017 12:14:23 -0700 (PDT)
Date: Mon, 14 Aug 2017 21:13:54 +0200
Subject: Re: Scope for self-destructing email?
Message-ID: <b5b27ee1-430f-421d-800b-822e5b6bd45c@email.android.com>
X-Android-Message-ID: <b5b27ee1-430f-421d-800b-822e5b6bd45c@email.android.com>
In-Reply-To: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com>
From: Matthias Merkel <moritz30@moritz30.de>
To: vaibhav singh <vaibhavsinghacads@gmail.com>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
Importance: Normal
X-Priority: 3
X-MSMail-Priority: Normal
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64
X-ZohoMailClient: External
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/41PXcgJgSyHm3TLVvPmtVjurWUU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 19:14:32 -0000

PGRpdiBkaXI9J2F1dG8nPkkgcmVhbGx5IGxpa2UgeW91ciBpZGVhIGFuZCBiYXNpY2FsbHkgSSdt
IGluLiBNeSBjb21wYW55IG93bnMgYW4gZW1haWwgcHJvdmlkZXIgKHdlIHdpbGwgcmVsZWFzZSBz
b29uKSBhbmQgd2UnZCBsb3ZlIHRvIGltcGxlbWVudCB0aGlzIGFuZCBoZWxwIHlvdSB3b3JrIG9u
IGl0LiBJZiB5b3UgbmVlZCBoZWxwIHdyaXRpbmcgc29tZSB0ZWNobmljYWwgc3RhbmRhcmQgZm9y
IGl0IGp1c3QgZW1haWwgbWUhPC9kaXY+PGRpdiBjbGFzcz0iZ21haWxfZXh0cmEiPjxicj48ZGl2
IGNsYXNzPSJnbWFpbF9xdW90ZSI+T24gQXVnIDE0LCAyMDE3IDk6MDEgUE0sIHZhaWJoYXYgc2lu
Z2ggJmx0O3ZhaWJoYXZzaW5naGFjYWRzQGdtYWlsLmNvbSZndDsgd3JvdGU6PGJyIHR5cGU9ImF0
dHJpYnV0aW9uIj48YmxvY2txdW90ZSBjbGFzcz0icXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAg
LjhleDtib3JkZXItbGVmdDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij48ZGl2IGRp
cj0ibHRyIj48ZGl2PjxkaXY+PGRpdj5IaSw8YnIgLz48YnIgLz48L2Rpdj5BcyBzb21lIG9mIHlv
dSBtYXkgYWxyZWFkeSBrbm93LCBHZW5lcmFsIERhdGEgUHJvdGVjdGlvbiBSZWd1bGF0aW9uIChH
RFBSKSwgYWJvdXQgdG8gYmUgZW5mb3JjZWQgaW4gdGhlIEVVIHdpdGhpbiBtb250aHMsIGFuZCBj
YWxscyBmb3Igc3RyaWN0IHJlZ3VsYXRpb25zIGZvciAgUmlnaHQgdG8gcmVjdGlmeSBjb21tdW5p
Y2F0aW9ucywgUmlnaHQgdG8gYmUgZm9yZ290dGVuICwgUHNldWRvbnltaXNhdGlvbiBhbmQgRGF0
YSBwb3J0YWJpbGl0eS48YnIgLz48YnIgLz48L2Rpdj5XaXRoIHJlZ2FyZHMgdG8gdGhpcywgbWUg
YW5kIG15IGZyaWVuZHMgd2VyZSB0aGlua2luZyBhYm91dCB0aGUgaWRlYSBvZiBhIHNlbGYtZGVz
dHJ1Y3RpbmcgZW1haWwsIHdoZXJlaW4gdGhlIHNlbmRlciB3aWxsIG1hcmsgdGhlIG1haWwgdG8g
YmUgZGVzdHJveWVkIChleHB1bmdlZCBmcm9tIHRoZSBzZXJ2ZXIpIG9uY2UgdGhlIHJlY2VpdmVy
KHMpIGhhdmUgZmluaXNoZWQgcmVhZGluZyBpdC9hZnRlciBhIHRpbWUgcGVyaW9kIGNob3NlbiBi
eSB0aGUgc2VuZGVyLjxiciAvPjxiciAvPjwvZGl2PkFub3RoZXIgZW5oYW5jZW1lbnQgdG8gdGhp
cyBpZGVhIHdhcyBhIG5vdGlmaWNhdGlvbiB3aGljaCB3aWxsIGJlIHNlbnQgZnJvbSBzb21lIChF
eHBsb2RpbmcgZW1haWwgUkZDKSBjb21wbGlhbnQgTVVBLCBpbiBjYXNlIHRoZSByZWNlaXZlciBy
ZWZ1c2VzIHRvIGRlbGV0ZSB0aGUgZW1haWwgZnJvbSB0aGUgY2xpZW50LiAoSSBrbm93IFNuYXBj
aGF0IGlzIGEgcG9vciBleGFtcGxlIGhlcmUsIGJ1dCB0aGV5IGFwcGFyZW50bHkgc2VuZCBub3Rp
ZmljYXRpb25zIHRvIHRoZSBvcmlnaW5hdG9yIG9mIHRoZSBzbmFwIGluIGNhc2UgYW55IHJlY2Vp
dmVyIHRyaWVzIHRvIGNhcHR1cmUgdGhlIHNjcmVlbnNob3Qgb2YgdGhlIHNuYXAuIFRoaXMgaXMs
IGluIHRoZW9yeSwgd2hhdCB3ZSBhcmUgdHJ5aW5nIHRvIGRvIGhlcmUpLjxiciAvPjxkaXY+PGRp
dj48ZGl2Pg0KPGRpdj48ZGl2PjxiciAvPjwvZGl2PjxkaXY+SSB3b3VsZCBhbHNvIGxpa2UgdG8g
a25vdyBhYm91dCB0aGluZ3MgKHdvcmtpbmcgZ3JvdXBzLCBpbnRlcm5ldCBkcmFmdHMgZXRjKSB3
aGljaCBhcmUgYmVpbmcgZG9uZSB0byBlbmZvcmNlIEdEUFIgdG8gPGJyIC8+PC9kaXY+PGRpdj5l
bWFpbCBhbmQgSW5zdGFudCBNZXNzYWdpbmcgZXNwZWNpYWxseS48YnIgLz48L2Rpdj48ZGl2Pjxi
ciAvPjwvZGl2PjxkaXY+LS0gPGJyIC8+PGRpdj48ZGl2IGRpcj0ibHRyIj48ZGl2PjxiciAvPjwv
ZGl2PlJlZ2FyZHMsPGRpdj5WYWliaGF2IFNpbmdoPC9kaXY+PC9kaXY+PC9kaXY+DQo8L2Rpdj48
L2Rpdj48L2Rpdj48L2Rpdj48L2Rpdj48L2Rpdj4NCjwvYmxvY2txdW90ZT48L2Rpdj48YnI+PC9k
aXY+



From nobody Mon Aug 14 12:16:21 2017
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A16E113240F for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:16:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1PIAoGz5cnmP for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:16:17 -0700 (PDT)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9815132415 for <ietf@ietf.org>; Mon, 14 Aug 2017 12:16:14 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id g25so43690223lfh.1 for <ietf@ietf.org>; Mon, 14 Aug 2017 12:16:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=rFVo8e9BRZc+PFtKWTkDxR7wgb/Xs9ILVYqjNcor3gI=; b=gntS0aXzgD62pz/Cw5Bjfj/HJ3e0f6WkMIYJNSVxWXPnZ+jSnXOlIp6sAJJcta3V8X FjE4sFSIu26UsyJq7BGllmSK/QVGjBVHxoDRoW5y+bXCX5+I3rOzGyXRGkjHq/k54t1y eISCE4E2cTPBCjm3m5huc2PV3jcGQ4lycsaFQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=rFVo8e9BRZc+PFtKWTkDxR7wgb/Xs9ILVYqjNcor3gI=; b=No0UviP3YYH7kVC6q/Iqv60frdBVtQk1w02B+jif5/4K/uMgv8+QddqkNSMRlwTfwo QU9QGzeztiAsmZjU0fCbg3NaGvHtQvKVzCLJHa7Is86gPnI4vhjY4j2QU7px2bRS5d6B YLAwWX7OPp4aUaQ/gIgbUwKI753MEg2DRr1UvtHoOoGnuiTEPAEROTFfcTp4KpyiNmaj 5CqOS2WfRTm1aHtDl1dyfLb46DAnAWtU3pxG7lho2JNrs9wC3bPL7Us7TxYQX2pSsPWs 62KR2+omZ83N/BXqGRG5oTOPeEnyBTvpQyBtFcSINCGKSJGLzflSVzALgxD6gObmFEuT KMhQ==
X-Gm-Message-State: AHYfb5iaVQ4QhF5+SdIua2GHPz2Q1eF3T3rh98/3JkwL6XMM7I2xOi7/ AX+u9Dm3Nc1r1JUCtms7rZo9b02NeDWk
X-Received: by 10.25.32.205 with SMTP id g196mr6479692lfg.242.1502738172994; Mon, 14 Aug 2017 12:16:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.179.75.130 with HTTP; Mon, 14 Aug 2017 12:16:12 -0700 (PDT)
In-Reply-To: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com>
References: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
Date: Mon, 14 Aug 2017 20:16:12 +0100
Message-ID: <CAKHUCzxja6D8jXz_kR6VaGZ21xNV0aw200956f9ESb-5NkhNEA@mail.gmail.com>
Subject: Re: Scope for self-destructing email?
To: vaibhav singh <vaibhavsinghacads@gmail.com>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lGZijn5fGZJcTKTzhEfHW0yLwrQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 19:16:20 -0000

On 14 August 2017 at 20:01, vaibhav singh <vaibhavsinghacads@gmail.com> wrote:
> With regards to this, me and my friends were thinking about the idea of a
> self-destructing email, wherein the sender will mark the mail to be
> destroyed (expunged from the server) once the receiver(s) have finished
> reading it/after a time period chosen by the sender.
>
> Another enhancement to this idea was a notification which will be sent from
> some (Exploding email RFC) compliant MUA, in case the receiver refuses to
> delete the email from the client. (I know Snapchat is a poor example here,
> but they apparently send notifications to the originator of the snap in case
> any receiver tries to capture the screenshot of the snap. This is, in
> theory, what we are trying to do here).
>

It's pretty much unenforceable. It is, however, theoretically possible
to build a mechanism to request the later deletion of a message using
MSGTRACK (RFC 3885) as a basis - but that's likely to be merely a
means to let others know you made an error rather than a real way to
delete a message.

> I would also like to know about things (working groups, internet drafts etc)
> which are being done to enforce GDPR to
> email and Instant Messaging especially.

In Instant Messaging, things are slightly different.

Because there's an online, synchronous communications path, then
protocols like XMPP can use "Perfect Forward Secrecy" techniques to
limit access to the original message, and protocols such as OTR, "The
Signal Protocol", and OMEMO all deliberately prevent non-repudiation
post-facto.

Therefore after a conversation, it is difficult to decrypt the
messages (you'd need to persistently store ephemeral keys) and
impossible to strictly prove that the message as captured was not
simply a forged log (although since computer logs are usually
admissible evidence, this is of debatable use).

In terms of Pseudonymity, XMPP builds this into chatrooms (XEP-0045)
and is making this slightly better in its replacement, MIX (XEP-0369).

However, all of these still boil down to keeping honest users honest -
the GDPR applies to people and organisations, and not to computer
systems per se. It means we (system and protocol developers) are
required to consider these use-cases to remain relevant, certainly,
but the actual compliance to these laws is a matter for the end user.

Dave.


From nobody Mon Aug 14 12:24:55 2017
Return-Path: <moritz30@moritz30.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D61E132408 for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:24:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.08
X-Spam-Level: *
X-Spam-Status: No, score=1.08 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.723, MISSING_MIMEOLE=1.899, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L-UFJeHl1oFI for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:24:52 -0700 (PDT)
Received: from sender-of-o52.zoho.com (sender-of-o52.zoho.com [135.84.80.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8459F1323D4 for <ietf@ietf.org>; Mon, 14 Aug 2017 12:24:52 -0700 (PDT)
Received: from [10.53.190.197] (x590feec5.dyn.telefonica.de [89.15.238.197]) by mx.zohomail.com with SMTPS id 1502738690395521.0381597778572; Mon, 14 Aug 2017 12:24:50 -0700 (PDT)
Date: Mon, 14 Aug 2017 21:24:42 +0200
Subject: Re: Scope for self-destructing email?
Message-ID: <c734e0d7-e83a-4fb3-8cc2-a24e227b50b9@email.android.com>
X-Android-Message-ID: <c734e0d7-e83a-4fb3-8cc2-a24e227b50b9@email.android.com>
In-Reply-To: <CAKHUCzxja6D8jXz_kR6VaGZ21xNV0aw200956f9ESb-5NkhNEA@mail.gmail.com>
From: Matthias Merkel <moritz30@moritz30.de>
To: Dave Cridland <dave@cridland.net>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>, vaibhav singh <vaibhavsinghacads@gmail.com>
Importance: Normal
X-Priority: 3
X-MSMail-Priority: Normal
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64
X-ZohoMailClient: External
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2M5RukFwrtC-YwnsJhs174AI1BU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 19:24:54 -0000

PGRpdiBkaXI9J2F1dG8nPkhvdyBhYm91dCBhZGRpbmcgYSB3YXkgdG8gdGVsbCBpZiBhIFNNVFAg
c2VydmVyIHN1cHBvcnRzIHNlbGYtZGVzdHJ1Y3RpbmcgZW1haWxzIGFuZCBpZiBpdCBkb2Vzbid0
IHRlbGwgdGhlIHVzZXIgaXQgZG9lc24ndCBhbmQgaWYgdGhleSB3YW50IHRvIHNlbmQgaXQgd2l0
aG91dCBzZWxmIGRlc3RydWN0aW9uPC9kaXY+



From nobody Mon Aug 14 12:41:03 2017
Return-Path: <matt@conundrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AB091323D4 for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:41:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=conundrum-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T8KAhJV6DB4R for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:41:00 -0700 (PDT)
Received: from mail-ua0-x231.google.com (mail-ua0-x231.google.com [IPv6:2607:f8b0:400c:c08::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 144BE1323A6 for <ietf@ietf.org>; Mon, 14 Aug 2017 12:40:59 -0700 (PDT)
Received: by mail-ua0-x231.google.com with SMTP id q25so40615838uah.1 for <ietf@ietf.org>; Mon, 14 Aug 2017 12:40:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=conundrum-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=sbVAt+hoK6dYSofDAqR42C7CzZ2qg/w3Ofi2buSz37U=; b=lsYOrcuIwoigvF7lG5e/SVnWPvB1zzbUnwphR0PMYqrR15a50hk4ARp6blEljOUn2n yodPqylwXmikk/3zSK0b5Y6R0JVWb+ZePHpksueKmut+Sd8uaUPg7mXnjsRm/kS38R7o XZLnagQJT7fANn+30Cic45+ff6J9NnE+ZNeWXJ23BSl+E57E2u/XgwjuLFgeirsexlGv ENjpOxTptPCmOeGPYR3jKH0FBghID9OncWM8IMsEKs+Y26AiGnhCWyr3wXr+QUEbJ3pt VA56lghYzfNmSBTA33fU10dlB81d9sE3kSTfPjBeTfyb02SimEA3mBHXYuaxFFdOVxyF Vn9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=sbVAt+hoK6dYSofDAqR42C7CzZ2qg/w3Ofi2buSz37U=; b=XhZAZeijcWB5+n0pcCl1ROYBONSVQMzRXpFBjCC1yQHLD5kgYOIxpVbFO3N47g1n9Z iQaYnVNmwVrVHXGTBvkME99BIIE1u2+5Pi/awAEmK3W6PPXjHYYTPLlqNgm7oFJ2Gyui Lpkijyo4YLq6+EqPDKF6zL9ztRvwRggc+YxL02FfpQEgmzX9s+8IKhyGoW0627gfNtwv /RRDY50SJ7xugI993wOkjFdAA6VFKy6UfQbMxRcoUvMh9VBbs/3tDX0G/XD72KyValCq YI5+V7c/uCTgJrflsULWBo70w1Axd/wcPFz/+UU6Hq9kTkhdtl8DXiPEZaPND9olbOmk 7slg==
X-Gm-Message-State: AHYfb5hURD/7zo4/IKCCHWvSh4tRCW+S7WKvEqOpOxJ27kvAQY1RmUT+ qxHl08VTNqDPukX+qoeisWJxzH1yWGFD
X-Received: by 10.176.81.34 with SMTP id e31mr18426934uaa.73.1502739658581; Mon, 14 Aug 2017 12:40:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.84.74 with HTTP; Mon, 14 Aug 2017 12:40:58 -0700 (PDT)
In-Reply-To: <c734e0d7-e83a-4fb3-8cc2-a24e227b50b9@email.android.com>
References: <CAKHUCzxja6D8jXz_kR6VaGZ21xNV0aw200956f9ESb-5NkhNEA@mail.gmail.com> <c734e0d7-e83a-4fb3-8cc2-a24e227b50b9@email.android.com>
From: Matthew Pounsett <matt@conundrum.com>
Date: Mon, 14 Aug 2017 15:40:58 -0400
Message-ID: <CAAiTEH9zg2Pk=KZTJ84JP3S5g+t9P8TXBsm3T=s7zOybV6SsJA@mail.gmail.com>
Subject: Re: Scope for self-destructing email?
To: Matthias Merkel <moritz30@moritz30.de>
Cc: Dave Cridland <dave@cridland.net>, vaibhav singh <vaibhavsinghacads@gmail.com>,  "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c1912c68a90d30556bbd799"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2uqzLv4xNMU5cDDaw2lv5lMPhRQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 19:41:02 -0000

--94eb2c1912c68a90d30556bbd799
Content-Type: text/plain; charset="UTF-8"

On 14 August 2017 at 15:24, Matthias Merkel <moritz30@moritz30.de> wrote:

> How about adding a way to tell if a SMTP server supports self-destructing
> emails and if it doesn't tell the user it doesn't and if they want to send
> it without self destruction
>

You have the same enforceability problem.   In the first case the request
is basically, "you MUST delete this message on the date requested, but if
you don't you MUST send a notice saying you didn't do that, but if you
don't... nothing happens."   Just as nothing stops the receiving server
from never deleting the message and never telling you, there's nom way to
force the receiving server to tell you the truth about what features it
implements.

As a simple advisory feature I'd probably ignore it.  Since there's never
any way to know whether the receiving server will live up to its promise,
you can never trust that it will, and so why send the info in the first
place?

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On 14 August 2017 at 15:24, Matthias Merkel <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:moritz30@moritz30.de" target=3D"_blank">moritz30@moritz30.de</=
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"><div dir=3D"auto">Ho=
w about adding a way to tell if a SMTP server supports self-destructing ema=
ils and if it doesn&#39;t tell the user it doesn&#39;t and if they want to =
send it without self destruction</div></blockquote></div><br></div><div cla=
ss=3D"gmail_extra">You have the same enforceability problem. =C2=A0 In the =
first case the request is basically, &quot;you MUST delete this message on =
the date requested, but if you don&#39;t you MUST send a notice saying you =
didn&#39;t do that, but if you don&#39;t... nothing happens.&quot; =C2=A0 J=
ust as nothing stops the receiving server from never deleting the message a=
nd never telling you, there&#39;s nom way to force the receiving server to =
tell you the truth about what features it implements.</div><div class=3D"gm=
ail_extra"><br></div><div class=3D"gmail_extra">As a simple advisory featur=
e I&#39;d probably ignore it.=C2=A0 Since there&#39;s never any way to know=
 whether the receiving server will live up to its promise, you can never tr=
ust that it will, and so why send the info in the first place?</div><div cl=
ass=3D"gmail_extra"><br></div></div>

--94eb2c1912c68a90d30556bbd799--


From nobody Mon Aug 14 12:49:12 2017
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EF9313240F for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:49:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rt5R77YXYEeu for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:49:08 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7350E1323D4 for <ietf@ietf.org>; Mon, 14 Aug 2017 12:49:08 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id t201so963518wmt.1 for <ietf@ietf.org>; Mon, 14 Aug 2017 12:49:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+ntkLBISWjV5ksZZFQ0Yolat97tvdci59FK1KxeFB2k=; b=N9ZGCstCu23mpZ00CIhnX351pcUnfpxGF7eVmO7WINZn2Pa7iEzaNeJ2HyPgipKeTi gqDHsSAPw0kir+UlOgNxOIK1URs8+F0u6uz4n4Xnlvvu+pbnoB2D6QHJvojpMEzrTMrH U1LK3r+xzITYLRW0HFwbNsg4Q494tHx3OX5EX/14HNE/UmERBp9H9ucEtmdwdQ6jVLyQ s4r+YxIwEZDebumtZvURLIDDnx+j08QG7q9RVkelfNqPXnSrXHlhS8o56S1ljTCojujE Pyutw/aDDMPJjfydhSjioaBuf2mRfCFb4opliYJglQKbYj3Hwa8roJL7YX8Mbwxnh1Xy stJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+ntkLBISWjV5ksZZFQ0Yolat97tvdci59FK1KxeFB2k=; b=JJQInyE8uO4V3kfB197yachEDLUPqOz8DV4I58PQ9BGAjpdZKs0lKhg1LCK13ExNj2 T6RmpHHh3uDT7XIe+NsoKX+JNPX4a5Ax8Gtz67UDlEBEfSrvrelzjOCvN3aTHxATTuoV UZUi+3ciKuVnO+fbGPSwx/z4cI36hcjJx0RxIoS5gDZRw3F0+wRNfRsr3S2AEFjlRI4Z 0679LfF163BfFC4UN/RBs/DeVSpqlhwCI+kqqivbUC2OJo1GD5AEhRBl6rIKZK3hNyjA qarZ0oRkRHwlFdfxgjmAweOURK0oZ/cKA/zYw1et9O9ezPNMH0ySluGizGrm2GMQbzws gmJQ==
X-Gm-Message-State: AHYfb5gCb6ywq9XPHsFsQMcSlYyn+1jfx8pcxh4b2ryqtgAwv0MYbImp a4Z7zgwhMDdU1ncyvQuYCjYTp6AxgXl5
X-Received: by 10.28.99.11 with SMTP id x11mr52003wmb.164.1502740146874; Mon, 14 Aug 2017 12:49:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.164.135 with HTTP; Mon, 14 Aug 2017 12:48:26 -0700 (PDT)
In-Reply-To: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com>
References: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
Date: Mon, 14 Aug 2017 15:48:26 -0400
Message-ID: <CAHw9_iJhGz_as7aJbWiJ+Bx+HVAi-ZPoWkMS1scwCtdrjdyc4Q@mail.gmail.com>
Subject: Re: Scope for self-destructing email?
To: vaibhav singh <vaibhavsinghacads@gmail.com>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wxKn4n4MK-1QytekghngRWBfJIQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 19:49:10 -0000

http://www.owl-stretching-time.com/because-you-dont-contol-the-recipient.png

On Mon, Aug 14, 2017 at 3:01 PM, vaibhav singh
<vaibhavsinghacads@gmail.com> wrote:
> Hi,
>
> As some of you may already know, General Data Protection Regulation (GDPR),
> about to be enforced in the EU within months, and calls for strict
> regulations for Right to rectify communications, Right to be forgotten ,
> Pseudonymisation and Data portability.
>
> With regards to this, me and my friends were thinking about the idea of a
> self-destructing email, wherein the sender will mark the mail to be
> destroyed (expunged from the server) once the receiver(s) have finished
> reading it/after a time period chosen by the sender.
>
> Another enhancement to this idea was a notification which will be sent from
> some (Exploding email RFC) compliant MUA, in case the receiver refuses to
> delete the email from the client. (I know Snapchat is a poor example here,
> but they apparently send notifications to the originator of the snap in case
> any receiver tries to capture the screenshot of the snap. This is, in
> theory, what we are trying to do here).
>
> I would also like to know about things (working groups, internet drafts etc)
> which are being done to enforce GDPR to
> email and Instant Messaging especially.
>
> --
>
> Regards,
> Vaibhav Singh



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Mon Aug 14 12:53:34 2017
Return-Path: <moritz30@moritz30.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD70C13241A for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:53:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.08
X-Spam-Level: *
X-Spam-Status: No, score=1.08 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.723, MISSING_MIMEOLE=1.899, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fXYIz5OSIpEw for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:53:32 -0700 (PDT)
Received: from sender-of-o52.zoho.com (sender-of-o52.zoho.com [135.84.80.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B18C0132415 for <ietf@ietf.org>; Mon, 14 Aug 2017 12:53:31 -0700 (PDT)
Received: from [10.53.190.197] (x590feec5.dyn.telefonica.de [89.15.238.197]) by mx.zohomail.com with SMTPS id 1502740404349314.20230736816893; Mon, 14 Aug 2017 12:53:24 -0700 (PDT)
Date: Mon, 14 Aug 2017 21:53:16 +0200
Subject: Re: Scope for self-destructing email?
Message-ID: <bc180881-4562-4b97-a625-51ef29770d9f@email.android.com>
X-Android-Message-ID: <bc180881-4562-4b97-a625-51ef29770d9f@email.android.com>
In-Reply-To: <CAAiTEH9zg2Pk=KZTJ84JP3S5g+t9P8TXBsm3T=s7zOybV6SsJA@mail.gmail.com>
From: Matthias Merkel <moritz30@moritz30.de>
To: Matthew Pounsett <matt@conundrum.com>
Cc: "	ietf@ietf.org Discussion" <ietf@ietf.org>, vaibhav singh <vaibhavsinghacads@gmail.com>, Dave Cridland <dave@cridland.net>
Importance: Normal
X-Priority: 3
X-MSMail-Priority: Normal
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64
X-ZohoMailClient: External
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1yS6eYH1joBUms5r0vHVc7WP_sw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 19:53:34 -0000

PGRpdiBkaXI9J2F1dG8nPkkgdGhpbmsgaG93ZXZlciB0aGF0IHRoaXMgc3lzdGVtIHdvdWxkIG1v
c3RseSBmaW5kIHVzZSBpbiBzeXN0ZW1zIGxpa2UgZ292ZXJubWVudHMgb3IgbWF5YmUgY29tbXVu
aWNhdGlvbiBiZXR3ZWVuIHdoaXN0bGVibG93ZXJzIGFuZCBuZXdzIG91dGxldHMuIEluIHRoZXNl
IGNhc2VzIHlvdSBjYW4gdHJ1c3QgdGhlIHJlY2VpcGllbnQgc2VydmVyIHRvIGRlbGV0ZSB0aGUg
bWVzc2FnZSB3aGVuIGJlaW5nIHRvbGQgdG8gZG8gc28uPC9kaXY+PGRpdiBjbGFzcz0iZ21haWxf
ZXh0cmEiPjxicj48ZGl2IGNsYXNzPSJnbWFpbF9xdW90ZSI+T24gQXVnIDE0LCAyMDE3IDk6NDAg
UE0sIE1hdHRoZXcgUG91bnNldHQgJmx0O21hdHRAY29udW5kcnVtLmNvbSZndDsgd3JvdGU6PGJy
IHR5cGU9ImF0dHJpYnV0aW9uIj48YmxvY2txdW90ZSBjbGFzcz0icXVvdGUiIHN0eWxlPSJtYXJn
aW46MCAwIDAgLjhleDtib3JkZXItbGVmdDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4
Ij48ZGl2IGRpcj0ibHRyIj48YnIgLz48ZGl2PjxiciAvPjxkaXYgY2xhc3M9ImVsaWRlZC10ZXh0
Ij5PbiAxNCBBdWd1c3QgMjAxNyBhdCAxNToyNCwgTWF0dGhpYXMgTWVya2VsIDxzcGFuIGRpcj0i
bHRyIj4mbHQ7PGEgaHJlZj0ibWFpbHRvOm1vcml0ejMwJiM2NDttb3JpdHozMC5kZSI+bW9yaXR6
MzAmIzY0O21vcml0ejMwLmRlPC9hPiZndDs8L3NwYW4+IHdyb3RlOjxiciAvPjxibG9ja3F1b3Rl
IHN0eWxlPSJtYXJnaW46MCAwIDAgMC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFk
ZGluZy1sZWZ0OjFleCI+PGRpdiBkaXI9ImF1dG8iPkhvdyBhYm91dCBhZGRpbmcgYSB3YXkgdG8g
dGVsbCBpZiBhIFNNVFAgc2VydmVyIHN1cHBvcnRzIHNlbGYtZGVzdHJ1Y3RpbmcgZW1haWxzIGFu
ZCBpZiBpdCBkb2VzbiYjMzk7dCB0ZWxsIHRoZSB1c2VyIGl0IGRvZXNuJiMzOTt0IGFuZCBpZiB0
aGV5IHdhbnQgdG8gc2VuZCBpdCB3aXRob3V0IHNlbGYgZGVzdHJ1Y3Rpb248L2Rpdj48L2Jsb2Nr
cXVvdGU+PC9kaXY+PGJyIC8+PC9kaXY+PGRpdj5Zb3UgaGF2ZSB0aGUgc2FtZSBlbmZvcmNlYWJp
bGl0eSBwcm9ibGVtLiDCoCBJbiB0aGUgZmlyc3QgY2FzZSB0aGUgcmVxdWVzdCBpcyBiYXNpY2Fs
bHksICYjMzQ7eW91IE1VU1QgZGVsZXRlIHRoaXMgbWVzc2FnZSBvbiB0aGUgZGF0ZSByZXF1ZXN0
ZWQsIGJ1dCBpZiB5b3UgZG9uJiMzOTt0IHlvdSBNVVNUIHNlbmQgYSBub3RpY2Ugc2F5aW5nIHlv
dSBkaWRuJiMzOTt0IGRvIHRoYXQsIGJ1dCBpZiB5b3UgZG9uJiMzOTt0Li4uIG5vdGhpbmcgaGFw
cGVucy4mIzM0OyDCoCBKdXN0IGFzIG5vdGhpbmcgc3RvcHMgdGhlIHJlY2VpdmluZyBzZXJ2ZXIg
ZnJvbSBuZXZlciBkZWxldGluZyB0aGUgbWVzc2FnZSBhbmQgbmV2ZXIgdGVsbGluZyB5b3UsIHRo
ZXJlJiMzOTtzIG5vbSB3YXkgdG8gZm9yY2UgdGhlIHJlY2VpdmluZyBzZXJ2ZXIgdG8gdGVsbCB5
b3UgdGhlIHRydXRoIGFib3V0IHdoYXQgZmVhdHVyZXMgaXQgaW1wbGVtZW50cy48L2Rpdj48ZGl2
PjxiciAvPjwvZGl2PjxkaXY+QXMgYSBzaW1wbGUgYWR2aXNvcnkgZmVhdHVyZSBJJiMzOTtkIHBy
b2JhYmx5IGlnbm9yZSBpdC7CoCBTaW5jZSB0aGVyZSYjMzk7cyBuZXZlciBhbnkgd2F5IHRvIGtu
b3cgd2hldGhlciB0aGUgcmVjZWl2aW5nIHNlcnZlciB3aWxsIGxpdmUgdXAgdG8gaXRzIHByb21p
c2UsIHlvdSBjYW4gbmV2ZXIgdHJ1c3QgdGhhdCBpdCB3aWxsLCBhbmQgc28gd2h5IHNlbmQgdGhl
IGluZm8gaW4gdGhlIGZpcnN0IHBsYWNlPzwvZGl2PjxkaXY+PGJyIC8+PC9kaXY+PC9kaXY+DQo8
L2Jsb2NrcXVvdGU+PC9kaXY+PGJyPjwvZGl2Pg==



From nobody Mon Aug 14 13:02:24 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3598313240F; Mon, 14 Aug 2017 13:02:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart.bryant@gmail.com>
To: <gen-art@ietf.org>
Cc: tsvwg@ietf.org, ietf@ietf.org, draft-ietf-tsvwg-sctp-ndata.all@ietf.org
Subject: Genart last call review of draft-ietf-tsvwg-sctp-ndata-12
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150274094205.10409.17989486864216331116@ietfa.amsl.com>
Date: Mon, 14 Aug 2017 13:02:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/145859RWytfxciUs0z4CzqUk4Ig>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 20:02:22 -0000

Reviewer: Stewart Bryant
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-tsvwg-sctp-ndata-12
Reviewer: Stewart Bryant
Review Date: 2017-08-14
IETF LC End Date: 2017-08-25
IESG Telechat date: Not scheduled for a telechat

Summary: This is a well written draft and is ready for publication.

Major issues: None

Minor issues: None

Nits/editorial comments:

You repeat the text:

"A message is considered in flight, if at least  on of its I-DATA chunks is not
acknowledged in a non-renegable way"  in two consecutive sections, maybe a
common definition could be used.


From nobody Mon Aug 14 13:05:41 2017
Return-Path: <randy_presuhn@alumni.stanford.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BB75132391 for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 13:05:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U9bqdXIS2lgN for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 13:05:38 -0700 (PDT)
Received: from mail-pg0-f50.google.com (mail-pg0-f50.google.com [74.125.83.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D89D126E64 for <ietf@ietf.org>; Mon, 14 Aug 2017 13:05:38 -0700 (PDT)
Received: by mail-pg0-f50.google.com with SMTP id i12so2809878pgr.3 for <ietf@ietf.org>; Mon, 14 Aug 2017 13:05:38 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Lj0ZU+u5i55v/keIkP6B64YeTQIsMuko+JL+cSSOBXA=; b=rJQyzlCeX+5gTVUbaxI83YSi7ORbdLDl7SNUSxO8dMdKAyGSH2mxbgx7qh/aP5lC8M xLzSMLwx0VabfhphiZcRt6SuBtW4ARZ7vMef3oo0i2SAtMgXyrpsBFOe9Du4LE+lNaqw AzY2grQaHJQPOasGL11F/zhNHoqwxCiBIBxyLuMMtYaui016yC+0Bm2E5JPIExAtlIBI Vvh16/L6qoIKTlRQ9DelnnZ/bMgFx+6tgXpmNQH2oZWAAasJ00Ad4h36nh/BZ+HkbKeD IHfQuI3YBsBML6BfF1iogW1wTGQSsPF8APhq3nbE4VwAMCpPFj0MIEGRgsv+n6Z0k6nn CVdQ==
X-Gm-Message-State: AHYfb5ithtRLjJBv6RE2TFZBAQ5s6pG+a0qdSpoIQATirih9UCh4Hy7y PBwEFnqcyzOxSOgF7HOUkw==
X-Received: by 10.99.97.10 with SMTP id v10mr16492951pgb.199.1502741137730; Mon, 14 Aug 2017 13:05:37 -0700 (PDT)
Received: from [192.168.1.113] (c-24-130-218-233.hsd1.ca.comcast.net. [24.130.218.233]) by smtp.gmail.com with ESMTPSA id 133sm14541638pge.29.2017.08.14.13.05.36 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Aug 2017 13:05:37 -0700 (PDT)
Subject: Re: Scope for self-destructing email?
To: ietf@ietf.org
References: <bc180881-4562-4b97-a625-51ef29770d9f@email.android.com>
From: Randy Presuhn <randy_presuhn@alumni.stanford.edu>
Message-ID: <6ce40fd4-3de7-b016-55f8-68b96df33333@alumni.stanford.edu>
Date: Mon, 14 Aug 2017 13:05:37 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <bc180881-4562-4b97-a625-51ef29770d9f@email.android.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/v4Lnzl-KvGTsVMPWvnckP9e0RR4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 20:05:40 -0000

Hi -

On 8/14/2017 12:53 PM, Matthias Merkel wrote:
> I think however that this system would mostly find use in systems like 
> governments or maybe communication between whistleblowers and news 
> outlets. In these cases you can trust the receipient server to delete 
> the message when being told to do so.

Which governments can actually be trusted to this extent?

More seriously, how could you have any confidence at all that
unauthorized (or even "lawful intercept") copies of the message
would be deleted?

Randy


From nobody Mon Aug 14 13:36:15 2017
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5384D13242C for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 13:36:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level: 
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cw2azlZD1NJr for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 13:36:11 -0700 (PDT)
Received: from smtpde01.smtp.sap-ag.de (smtpde01.smtp.sap-ag.de [155.56.68.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B986132427 for <ietf@ietf.org>; Mon, 14 Aug 2017 13:35:41 -0700 (PDT)
Received: from mail07.wdf.sap.corp (mail04.sap.corp [194.39.131.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtpde01.smtp.sap-ag.de (Postfix) with ESMTPS id 3xWS6g4sCvz1HC8; Mon, 14 Aug 2017 22:35:39 +0200 (CEST)
X-purgate-ID: 152705::1502742939-00000810-C35CF64E/0/0
X-purgate-size: 1336
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate-type: clean
X-SAP-SPAM-Status: clean
Received: from ld9781.wdf.sap.corp (ld9781.wdf.sap.corp [10.21.82.193]) by mail07.wdf.sap.corp (Postfix) with ESMTP id 3xWS6g2dgPzGp7M; Mon, 14 Aug 2017 22:35:38 +0200 (CEST)
Received: by ld9781.wdf.sap.corp (Postfix, from userid 10159) id 4F1DC1A6DF; Mon, 14 Aug 2017 22:35:38 +0200 (CEST)
Subject: Re: Scope for self-destructing email?
In-Reply-To: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com>
To: vaibhav singh <vaibhavsinghacads@gmail.com>
Date: Mon, 14 Aug 2017 22:35:38 +0200 (CEST)
CC: "ietf@ietf.org Discussion" <ietf@ietf.org>
Reply-To: mrex@sap.com
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: <20170814203538.4F1DC1A6DF@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9ic4hPvXDBaR4wNhr8Pb4rMOO2U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 20:36:13 -0000

vaibhav singh wrote:
> 
> As some of you may already know, General Data Protection Regulation (GDPR),
> about to be enforced in the EU within months, and calls for strict
> regulations for Right to rectify communications, Right to be forgotten ,
> Pseudonymisation and Data portability.

I believe you have seriously misunderstood the parts of GDPR about
"the right to be forgotten", because it does regularly not apply to IETF
mailing list posting -- only in very exceptional situations -- and
for those exceptional situations, there is a procedure in place where
you can submit a request to delete an indivdual submission from
the public archives (mailing list archives and I-D repository)
if you have a valid reason why this submission should be deleted.

The "Right to be forgotton" primarily applies to

 - terminated contracts -- so that a seller or service provider
   deletes data about you after termination of contract / subscription

 - that stories in the news (media outlets) about you, which you often
   didn't publish yourself (but some reporter about you) and with little
   public interest, will at some point disappear from online public archives
   (and internet search engines).  The information may remain available
   in offline archives (such as microfiche) as in the past.


-Martin


From nobody Mon Aug 14 13:54:57 2017
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4806813242A for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 13:54:53 -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_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CehK6M6V3aTr for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 13:54:51 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7878E132430 for <ietf@ietf.org>; Mon, 14 Aug 2017 13:54:51 -0700 (PDT)
Received: from [192.168.0.41] (c83-251-104-125.bredband.comhem.se [83.251.104.125]) by mail.frobbit.se (Postfix) with ESMTPSA id 9F0CB24468; Mon, 14 Aug 2017 22:54:47 +0200 (CEST)
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: Glen <glen@amsl.com>
Cc: ietf@ietf.org
Subject: Re: Mailman attack in progress
Date: Mon, 14 Aug 2017 22:54:48 +0200
Message-ID: <0396E8A1-7B7A-4B1F-8B6A-754DE86B6DF8@frobbit.se>
In-Reply-To: <CABL0ig7M0F0WDBTA9qqkEDRt9BUBs5uVaCkmtdn3TY8Xv1ik3A@mail.gmail.com>
References: <CABL0ig7VW_eNC8qEiX0+a71if1L0FnxEJn6usssQu+1Ox5nQOQ@mail.gmail.com> <CABL0ig4UT4Ebfzdf2ce1vu-Q76Ei_A7Yk=q-fkGfDU8o2VWjeA@mail.gmail.com> <sjma832f97r.fsf@securerf.ihtfp.org> <CABL0ig7M0F0WDBTA9qqkEDRt9BUBs5uVaCkmtdn3TY8Xv1ik3A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_4A74A309-6768-4995-8867-22FD6A1623C0_="; micalg=pgp-sha1; protocol="application/pgp-signature"
X-Mailer: MailMate (2.0BETAr6090)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GCHIXpoTsgiXDU3WBLVKcSP7e5s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 14 Aug 2017 20:54:53 -0000

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

--=_MailMate_4A74A309-6768-4995-8867-22FD6A1623C0_=
Content-Type: text/plain

On 14 Aug 2017, at 18:25, Glen wrote:

> So, needless to say, I am hesitant to just openly describe attack
> countermeasures on a public list.  :-)   I'm sorry for that - I truly
> am - because as I said *I* would want to know, too.   Although in this
> case it's not a big deal, just a tweak or two, but adjustments that,
> were they published, would be much easier for the bot authors to
> "adjust for".  For all of these reasons, I'm not comfortable just
> unilaterally exposing the IETF's defenses here... and I hope that you
> will all understand this.  I am preparing a summary report to the TMC
> outlining what was done, and I need to leave it to them to determine
> if - and how best - to present the information to interested persons.

I think this is a very wise decision. Thanks for this.

> Thanks for your support as we deal with the ongoing threats to the IETF.

Thank YOU for your hard work supporting us.

   Patrik

--=_MailMate_4A74A309-6768-4995-8867-22FD6A1623C0_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

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

iEYEARECAAYFAlmSDhgACgkQrMabGguI180NhACgksgLkOrYrhVcGOZGlovsl6q3
D3EAnR8ZtNjBO7k2Mm6pi/vucDmQGbQb
=hTKQ
-----END PGP SIGNATURE-----

--=_MailMate_4A74A309-6768-4995-8867-22FD6A1623C0_=--


From nobody Mon Aug 14 18:33:05 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB5A113247E for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 18:32:46 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9REzdg7XDLH0 for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 18:32:44 -0700 (PDT)
Received: from mail-pg0-x22e.google.com (mail-pg0-x22e.google.com [IPv6:2607:f8b0:400e:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1934E1321B6 for <ietf@ietf.org>; Mon, 14 Aug 2017 18:32:43 -0700 (PDT)
Received: by mail-pg0-x22e.google.com with SMTP id v189so57842315pgd.2 for <ietf@ietf.org>; Mon, 14 Aug 2017 18:32:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=/eLwelNjSMsmANVpsYOOh4eg2sV1i7YgE2WjW1jcqhg=; b=gxXCrcmcKmtGlB5f/hbKsQaZiU5kmkcElXdcUqf7nPQEzN3CPshaZpcDiUY/DM/aPb 5K0muDfJkh0LhT1xKcdYqm3Dc9qIbEEoQm+oOMucWDJipiR9l90H4ePIShB8+9q3EoLD 0pSYFbz64EiLjGc7CLk1rdc8lMYbp2eogoLEwfkTlU/XHqoi1JCUKuUofkTOdRu4GjDo pVQD9QBf5CAw9ThgiOYCSunixuEgijagbZdS2s6f/258YpEIM9X5MOAqb5A4ioOmoOxf NpT8B53/AgPLhptdjxBMzk6lQxuTS3+mc1xe7IiHNfgRaIvUU/BR+njvIkIYXERYZQRb uMsw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=/eLwelNjSMsmANVpsYOOh4eg2sV1i7YgE2WjW1jcqhg=; b=IACP0iiYSx9omvevrycr8B4YK4Ba4bBMXF5oznd1fAlBDbHjA1tG0vtLUrivHh5v8u YheXIDxw9bGEzutpcLwNFXosj38VYT7dPMRHyV3RHOCPEMRCWTtLo9cCse/RDAT+8Dg4 TZZij1nxS/e8EidoXsy0RuPEVrGEHzpYzMmMZjtlPnfoghLVmJFG2Nrz6WjwlQzXTBYw 8TadhGkpvqc9B1m2IsHHcmMKdvKcQk9Cr+HO4VWusmMls77y9Kc1Bciy2LiHFI9kW5Fn x9HZZUC8e1Pmwr/wQ1A4tRwchyMLnMQ7VtB7VlKyF2iSGd1TboToJZB2S7FrpJUvsthI fWKw==
X-Gm-Message-State: AHYfb5jXXyq5c2aEcAR7AODIZwuIfhUYoiDAPKxVtQgxu95IS4X7xHDi hh0oCu7P6r5BpP8A
X-Received: by 10.84.177.67 with SMTP id w61mr30454313plb.112.1502760762453; Mon, 14 Aug 2017 18:32:42 -0700 (PDT)
Received: from ?IPv6:2406:e007:521f:1:28cc:dc4c:9703:6781? ([2406:e007:521f:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id v9sm16379848pgo.39.2017.08.14.18.32.40 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Aug 2017 18:32:41 -0700 (PDT)
Subject: Re: Scope for self-destructing email?
To: ietf@ietf.org
References: <bc180881-4562-4b97-a625-51ef29770d9f@email.android.com> <6ce40fd4-3de7-b016-55f8-68b96df33333@alumni.stanford.edu>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <a12ac1b5-f6a9-679c-23a2-61e715c43016@gmail.com>
Date: Tue, 15 Aug 2017 13:32:40 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <6ce40fd4-3de7-b016-55f8-68b96df33333@alumni.stanford.edu>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rD7MtdiLmc4iV3k2gdebxUmgdmw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 15 Aug 2017 01:32:47 -0000

On 15/08/2017 08:05, Randy Presuhn wrote:
> Hi -
> 
> On 8/14/2017 12:53 PM, Matthias Merkel wrote:
>> I think however that this system would mostly find use in systems like 
>> governments or maybe communication between whistleblowers and news 
>> outlets. In these cases you can trust the receipient server to delete 
>> the message when being told to do so.
> 
> Which governments can actually be trusted to this extent?
> 
> More seriously, how could you have any confidence at all that
> unauthorized (or even "lawful intercept") copies of the message
> would be deleted?

You can't. I have destroyed Message-ID: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com>.
Is that true? How do you know it's true?

    Brian


From nobody Mon Aug 14 18:38:25 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEE66126B7E for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 18:38:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hCJ42WCBEP7G for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 18:38:22 -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 4A0D91321B6 for <ietf@ietf.org>; Mon, 14 Aug 2017 18:38:22 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dhQoH-000Aab-AW; Mon, 14 Aug 2017 21:38:21 -0400
Date: Mon, 14 Aug 2017 21:38:16 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: ietf@ietf.org
Subject: Re: Scope for self-destructing email?
Message-ID: <889C187443C99CC61539528A@PSB>
In-Reply-To: <a12ac1b5-f6a9-679c-23a2-61e715c43016@gmail.com>
References: <bc180881-4562-4b97-a625-51ef29770d9f@email.android.com> <6ce40fd4-3de7-b016-55f8-68b96df33333@alumni.stanford.edu> <a12ac1b5-f6a9-679c-23a2-61e715c43016@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0yNjv3Ial7O5E5MH6BScYFljUYo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 15 Aug 2017 01:38:24 -0000

--On Tuesday, August 15, 2017 13:32 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>> More seriously, how could you have any confidence at all that
>> unauthorized (or even "lawful intercept") copies of the
>> message would be deleted?
> 
> You can't. I have destroyed Message-ID:
> <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmai
> l.com>. Is that true? How do you know it's true?

Even if I had some way to verify that your statement about your
actions were true and that what you meant by "destroyed"
included any backup copies you might have kept as a side-effect
of other operations or procedures, there is no way that you can
guarantee that Google has destroyed it too.   Indeed, prior to
the recent change in Gmail policy, I one could infer that they
had not and would not until whatever information it was
contained were deemed of no relevance.

   john



From nobody Mon Aug 14 19:48:32 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 890D01324AB for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 19:48:30 -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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yLVYs88locxM for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 19:48:29 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F72B1324A1 for <ietf@ietf.org>; Mon, 14 Aug 2017 19:48:28 -0700 (PDT)
Received: (qmail 83576 invoked from network); 15 Aug 2017 02:48:28 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 15 Aug 2017 02:48:28 -0000
Date: 15 Aug 2017 01:44:05 -0000
Message-ID: <20170815014405.1373.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Cc: vaibhavsinghacads@gmail.com
Subject: Re: Scope for self-destructing email?
In-Reply-To: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/v_zTc6peIXlwS8v1AIXmE0gWDCU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 15 Aug 2017 02:48:30 -0000

In article <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com> you write:
>With regards to this, me and my friends were thinking about the idea of a
>self-destructing email, wherein the sender will mark the mail to be
>destroyed (expunged from the server) once the receiver(s) have finished
>reading it/after a time period chosen by the sender.

This can never work, for both technical and policy reasons.

The technical reason, as others have explained, is that recipient
systems can do anything they want with mail they receieve.  If I got
mail with a "must delete" flag I would probably reply that it's been
deleted and then archive it forever.  (I live in the United States,
where that is quite legal.)

The other is that there are organizations that for good policy reasons archive
all of their incoming and outgoing mail, such as banks and other financial
institutions.  Imagine if you sent a message to your broker saying "sell
all of my stocks" with the delete flag.  Whether or not a broker would
act on it, no broker I know would delete it.

R's,
John


From nobody Mon Aug 14 20:12:06 2017
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9F721324A8 for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 20:12:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Si7kJf6ogUK for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 20:12:04 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 78BF21323C4 for <ietf@ietf.org>; Mon, 14 Aug 2017 20:12:04 -0700 (PDT)
Received: from mb.local ([IPv6:2607:fb90:824a:e8e8:80eb:e771:7c35:9cd9]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id v7F3C27v033421 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 15 Aug 2017 03:12:03 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2607:fb90:824a:e8e8:80eb:e771:7c35:9cd9] claimed to be mb.local
Subject: Re: Scope for self-destructing email?
To: vaibhav singh <vaibhavsinghacads@gmail.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
References: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <b1289123-04ac-e62b-879e-614fae9b20b0@bogus.com>
Date: Mon, 14 Aug 2017 20:12:01 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:56.0) Gecko/20100101 Thunderbird/56.0
MIME-Version: 1.0
In-Reply-To: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fIBJW0kL8f4PC7kHwIed1YHtmvE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 15 Aug 2017 03:12:06 -0000

On 8/14/17 12:01, vaibhav singh wrote:
> Hi,
> 
> As some of you may already know, General Data Protection Regulation
> (GDPR), about to be enforced in the EU within months, and calls for
> strict regulations for Right to rectify communications, Right to be
> forgotten , Pseudonymisation and Data portability.
> 
> With regards to this, me and my friends were thinking about the idea of
> a self-destructing email, wherein the sender will mark the mail to be
> destroyed (expunged from the server) once the receiver(s) have finished
> reading it/after a time period chosen by the sender.
> 
> Another enhancement to this idea was a notification which will be sent
> from some (Exploding email RFC) compliant MUA, in case the receiver
> refuses to delete the email from the client. (I know Snapchat is a poor
> example here, but they apparently send notifications to the originator
> of the snap in case any receiver tries to capture the screenshot of the
> snap. This is, in theory, what we are trying to do here).
> 
> I would also like to know about things (working groups, internet drafts
> etc) which are being done to enforce GDPR to
> email and Instant Messaging especially.

In order that you have some assurance that the demands provided at the
input side are honored on the receipt side you need effectively
end-to-end control over the system, that is the sender, receiver, and
any intermediate hops are part of the same administrative domain such
that any control imposed is actually implemented. That might be
practical for an email system but not generally for the email system.

> -- 
> 
> Regards,
> Vaibhav Singh


From nobody Mon Aug 14 20:25:17 2017
Return-Path: <michel@arneill-py.sacramento.ca.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E5101320CF for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 20:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.002
X-Spam-Level: 
X-Spam-Status: No, score=-0.002 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IJ-QiF1TAdQV for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 20:25:15 -0700 (PDT)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [64.113.127.228]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2505513202D for <ietf@ietf.org>; Mon, 14 Aug 2017 20:25:15 -0700 (PDT)
Received: from newserver.arneill-py.local ([fe80::498f:921e:4318:b41]) by newserver.arneill-py.local ([fe80::498f:921e:4318:b41%12]) with mapi id 14.03.0361.001; Mon, 14 Aug 2017 20:25:13 -0700
From: Michel Py <michel@arneill-py.sacramento.ca.us>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Scope for self-destructing email?
Thread-Topic: Scope for self-destructing email?
Thread-Index: AQHTFS/W3P96VIEUGE6Agfu8CbNCyaKFGu2A//+mqVA=
Date: Tue, 15 Aug 2017 03:25:12 +0000
Message-ID: <F04ED1585899D842B482E7ADCA581B846631E036@newserver.arneill-py.local>
References: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com> <20170815014405.1373.qmail@ary.lan>
In-Reply-To: <20170815014405.1373.qmail@ary.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [fe80::498f:921e:4318:b41]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4345af2qGcqd6aYzVKondyiKlUc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 15 Aug 2017 03:25:16 -0000

R29vZCBldmVuaW5nLCBNci4gUGhlbHBzLg0KDQpZb3VyIG1pc3Npb24sIHNob3VsZCB5b3UgY2hv
b3NlL2RlY2lkZSB0byBhY2NlcHQgaXQsIHdvdWxkIGJlIHRvIHNvbHZlIHRoZSByZWN1cnJlbnQg
cHJvYmxlbXMgb2Ygd29ybGQNCmh1bmdlciwgcGVhY2UgaW4gdGhlIE1pZGRsZSBFYXN0LCBVU0Eg
LyBSdXNzaWEgcmVsYXRpb25zaGlwcywgZ2xvYmFsIHdhcm1pbmcsIGFuZCBkZXBsb3ltZW50IG9m
IElQdjYuDQoNCkFzIGFsd2F5cywgc2hvdWxkIHlvdSBvciBhbnkgb2YgeW91ciBJLk0uIEZvcmNl
IGJlIGNhdWdodCBvciBraWxsZWQsIHRoZSBTZWNyZXRhcnkgd2lsbCBkaXNhdm93DQphbnkga25v
d2xlZGdlIG9mIHlvdXIgYWN0aW9ucy4gVGhpcyBlbWFpbCB3aWxsIHNlbGYtZGVzdHJ1Y3QgaW4g
dGVuIHNlY29uZHMuIEdvb2QgbHVjay4NCg0K


From nobody Tue Aug 15 09:47:38 2017
Return-Path: <prvs=393ddb255=theodore.v.faber@aero.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3548E132356 for <ietf@ietfa.amsl.com>; Tue, 15 Aug 2017 09:47:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=aero.org header.b=yDdM6hoR; dkim=pass (1024-bit key) header.d=aerospacecloud.onmicrosoft.com header.b=QwY7YZuk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T9mxncHuHBtj for <ietf@ietfa.amsl.com>; Tue, 15 Aug 2017 09:47:34 -0700 (PDT)
Received: from email3-east.aero.org (email3-east.aero.org [130.221.184.167]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B47121321CB for <ietf@ietf.org>; Tue, 15 Aug 2017 09:47:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=aero.org; i=@aero.org; q=dns/txt; s=mailhub; t=1502815653; x=1534351653; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=SymHmmFrlgpwrrDsdlUH/gFgm4ryQKP/eqNxbbb5HR4=; b=yDdM6hoRmcVrus6wuyJsLZBCWZ9V8O7Byg/85He7Yl4KncuyE/JEvg4A uQYCJm1ueqN/nbQJiXeLk1b8vd3kv70WTBpfxSiCUOzdrvzIAju9WJJOP uTdmNW1usOBt2L1AIBRNgccYYBo9QJ0xIQBiV8z1ia/pMHlX4UCsIYzzZ Y=;
x-SBRS: 3.5
x-SenderGroup: Inbound_Office365
X-IronPort-AV: E=McAfee;i="5900,7806,8622"; a="5554820"
X-IronPort-AV: E=Sophos;i="5.41,378,1498546800";  d="scan'208";a="5554820"
X-IPAS-Result: =?us-ascii?q?A2G4AABjJZNZhzLGZxdbAxoBAQEBAgEBAQEIAQEBAYNXZ18?= =?us-ascii?q?EMgeOfZEMiDeNb4ElA1wkhSMChHkUAQIBAQEBAQEBAxABAQEIDQkIKC+CZXIBA?= =?us-ascii?q?QEBAQEBAQEiKgIILDYBAQEBAgFAAQE3AQ8CAQgVHAITIRElAgQBDQUIig8DDQi?= =?us-ascii?q?gNAKLB4MRgwgBAQWEKg0LhAQBAQEBAQEBAQIBAQEBAQEBAQEBARUIgyiIWIJXg?= =?us-ascii?q?VoPARECAR4CBRoXDw8HgmaCMQGRJTqOJjyPSpdPjDVAh2UBAYE8Nm4zC1MxUYU?= =?us-ascii?q?IH4FzdgFhhxSBMAGBDgEBAQ?=
Received: from mail-dm2gcc01lp0050.outbound.protection.outlook.com (HELO gcc01-dm2-obe.outbound.protection.outlook.com) ([23.103.198.50]) by email3-east.aero.org with ESMTP/TLS/AES256-SHA256; 15 Aug 2017 09:47:15 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aerospacecloud.onmicrosoft.com; s=selector1-aero-org; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=xdvYi/t+p8lpwbl0B1xTGIsz1rCeDrToy5S+AK+AHIc=; b=QwY7YZuk0m+aDMWei3EMD5v11B2I8fabkY7TEu8ym8nxXIwNZgjGK24Eu55xPdy8RU3UWB160DlnvRaFCOLe2t0BE5kX6WYMD4R/+GAMvfFU6lbPCwHoSTcGksohmTePf/nvVZbYAY+h4j3gCOhk+4bqXeBYEg6wfPgyW2GifFg=
Received: from CY1PR09MB0282.namprd09.prod.outlook.com (10.160.140.28) by CY1PR09MB0283.namprd09.prod.outlook.com (10.160.159.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1341.21; Tue, 15 Aug 2017 16:47:13 +0000
Received: from CY1PR09MB0282.namprd09.prod.outlook.com ([10.160.140.28]) by CY1PR09MB0282.namprd09.prod.outlook.com ([10.160.140.28]) with mapi id 15.01.1341.020; Tue, 15 Aug 2017 16:47:13 +0000
From: Theodore V Faber <theodore.v.faber@aero.org>
To: John C Klensin <john-ietf@jck.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Scope for self-destructing email?
Thread-Topic: Scope for self-destructing email?
Thread-Index: AQHTFS/QfhBYmaGKk0OgZCnZTT9DKqKEOTUAgAACYACAAASLAIAAA3AAgAADdICAAFtgAIAAAZEAgAD6INY=
Date: Tue, 15 Aug 2017 16:47:13 +0000
Message-ID: <CY1PR09MB0282CB81D41696253190CDA0B98D0@CY1PR09MB0282.namprd09.prod.outlook.com>
References: <bc180881-4562-4b97-a625-51ef29770d9f@email.android.com> <6ce40fd4-3de7-b016-55f8-68b96df33333@alumni.stanford.edu> <a12ac1b5-f6a9-679c-23a2-61e715c43016@gmail.com>, <889C187443C99CC61539528A@PSB>
In-Reply-To: <889C187443C99CC61539528A@PSB>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=theodore.v.faber@aero.org; 
x-originating-ip: [130.221.224.7]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY1PR09MB0283; 6:GOaHQ+QCcEqUpBQ1LM5iubOfkkzhGV4Or/tFZ0BIhfeYx5iE73uXwds39fL+sscIT+J9pcUB4l4MNeZVM7Dp58yfUttU9/cV8kZfwBRcuSOMc7NVGMB8/QmvxnnPLtdWWoQXpi5B/TEB4d/uCQxAREKIGIoNB/6fX1OU8j2l4rTREYxcAz2JiSNswmJudRJG1VSt2VVqI2UtpTooT0COINDQTxd/5h6kk7H0ikJ1odr/jFAFuq821oqBq+HCQHCIblqfX1tRID8JImimmAXdTh7YVRTYjxXrH5XRZF+4kN4hRq1KRO+MSIE6eITuyDrYivEiJtzBQXc9SKpCfLkPcA==; 5:MdI22Z2WLJKaaEJR0pKqNqZ7xxfJHtuuGiwACe4LsJXDj/JILaQhtj8/U3gcGPfPIoAJGB+iRcTKY1D1KJNpNWYqXhFpHyZVRxvmAsnEMwPdqQXBy0ojk7uxx5ScXLQjQG9Htyvnm8WYeMJZ4gpdVw==; 24:/nKt0FViJjGnYkrqp9CxmsZ174uECFpdZnskdh1mzok09xlBQbl54IMfNgBv3ev7exlDD6MQdeWhoXUA+HhAQB7cO4Hax2w84Sr63mQsTWs=; 7:3Sntyh6rR0AjO4l252zmB6sa7/X+e4SzcfoEtAFWz+uTEUTTkPsf1rCTCt++7TDSBO8hzIFXcoERo5f3boN+0/NPat5dBDUWdNoUTOAjvN9KTb+1JhTnreZFZj0/LWNR1hzMcNGQbzh4fh57Tq5NEEvpKhZON6C4Jm/RuRxJppix71woK/M5sBhjK8DxwZ4aI60nY1tJ8SSB/NM/O6AWXdMq/qdN2vKusuEHMPTNh+I=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: f92df741-45aa-4084-e030-08d4e3fd47b2
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254152)(300000503095)(300135400095)(48565401081)(2017052603031)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:CY1PR09MB0283; 
x-ms-traffictypediagnostic: CY1PR09MB0283:
x-exchange-antispam-report-test: UriScan:;
x-microsoft-antispam-prvs: <CY1PR09MB02838BE57CA4415F23C01F32B98D0@CY1PR09MB0283.namprd09.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(100000703101)(100105400095)(6055026)(6041248)(20161123555025)(20161123558100)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123564025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:CY1PR09MB0283; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CY1PR09MB0283; 
x-forefront-prvs: 04004D94E2
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39860400002)(189002)(199003)(24454002)(51444003)(81166006)(7736002)(86362001)(81156014)(39060400002)(93886004)(5660300001)(14454004)(53936002)(8676002)(68736007)(305945005)(6246003)(33656002)(105586002)(106356001)(76176999)(50986999)(54356999)(66066001)(229853002)(101416001)(77096006)(4326008)(8936002)(55016002)(2906002)(25786009)(97736004)(6436002)(189998001)(3660700001)(6506006)(3480700004)(7696004)(9686003)(74316002)(2950100002)(6116002)(478600001)(99286003)(2900100001)(3846002)(102836003)(3280700002); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR09MB0283; H:CY1PR09MB0282.namprd09.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: aero.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Aug 2017 16:47:13.4749 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: c8294700-c5a4-4ca1-a876-1457d39899fd
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR09MB0283
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TlGy-xjiQSIMx9b8Sbp6CMXivWE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 15 Aug 2017 16:47:36 -0000

________________________________________
> From: ietf <ietf-bounces@ietf.org> on behalf of John C Klensin <john-ietf=
@jck.com>
>--On Tuesday, August 15, 2017 13:32 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>>> More seriously, how could you have any confidence at all that
>>> unauthorized (or even "lawful intercept") copies of the
>>> message would be deleted?
>>
>> You can't. I have destroyed Message-ID:
>> <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=3DJ8oFZ0JZA@mail.gmai
>> l.com>. Is that true? How do you know it's true?

>Even if I had some way to verify that your statement about your
>actions were true and that what you meant by "destroyed"
>included any backup copies you might have kept as a side-effect
>of other operations or procedures, there is no way that you can
>guarantee that Google has destroyed it too.   Indeed, prior to
>the recent change in Gmail policy, I one could infer that they
>had not and would not until whatever information it was
>contained were deemed of no relevance.

As an aside, that passive voice matters, too.  The entity making the judgme=
nt (state agent, intelligence service, advertiser) will evaluate relevance =
differently.

To the main point: I do know lots of people on this list know these issues =
and are channeling Socrates, but to be explicit:  I think that once bits ar=
e out in the net, provably erasing them is impossible.   I'll channel Frank=
lin (or whoever he's quoting): "Three can keep a secret, if two of them are=
 dead."

--
Ted Faber <theodore.v.faber@aero.org>
Engineering Specialist
Computer Systems Research Department
The Aerospace Corporation
310-336-7373
   john



From nobody Tue Aug 15 19:35:54 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4F8813246D for <ietf@ietfa.amsl.com>; Tue, 15 Aug 2017 19:35:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i29D_VeZTI8f for <ietf@ietfa.amsl.com>; Tue, 15 Aug 2017 19:35:40 -0700 (PDT)
Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) (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 7392F13245E for <ietf@ietf.org>; Tue, 15 Aug 2017 19:35:39 -0700 (PDT)
Received: from resomta-ch2-10v.sys.comcast.net ([69.252.207.106]) by resqmta-ch2-03v.sys.comcast.net with ESMTP id ho8mdvdwz61hBhoBGdlnSW; Wed, 16 Aug 2017 02:35:38 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-10v.sys.comcast.net with SMTP id hoBEdg5WI6bpPhoBFdjYAv; Wed, 16 Aug 2017 02:35:38 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v7G2ZZuL019519; Tue, 15 Aug 2017 22:35:35 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v7G2ZZ4l019516; Tue, 15 Aug 2017 22:35:35 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Dhruv Dhody <dhruv.dhody@huawei.com>
Cc: gen-art@ietf.org, draft-ietf-pce-pceps.all@ietf.org, pce@ietf.org, ietf@ietf.org, dhruv.ietf@gmail.com
Subject: Re: [Pce] Genart last call review of draft-ietf-pce-pceps-14
In-Reply-To: <23CE718903A838468A8B325B80962F9B8CB98624@blreml501-mbb> (dhruv.dhody@huawei.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Tue, 15 Aug 2017 22:35:35 -0400
Message-ID: <87mv70utmw.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfODU7UPMr264N0dQW6q4ogRecsmwWpLhcikEfRQjr+e5MUxovo38FhEvu5sdKRlmIW0tyLJExzzPxOvYFUyrYTSmDIfPR/A1QBQQPUzzJoflWKNyKUzq hKuIf5Ws1k3lTXGiTwOzE4Ps3ZAQjxifIQu7E0gHhJx+m+6h/uQtSOuNs5yGUZR0bgwuPl/DUU/asBOJPlcZy4QxR54xk/o6NVOkB1OEy8yne3KyO3/di+ht tznyZh1oegsavet+PmJ65BXBrpfgsuQTJqcgfKjgvi5trAbw8t7tLWClYNYjyWD9U2r2IhTLbCv4Ho2Pt/mO8A==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7AtsEzkyY2drotdIMYr0ADL2SCc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 02:35:42 -0000

Dhruv Dhody <dhruv.dhody@huawei.com> writes:
> [[Dhruv Dhody]] I have added this in the backward compatibility session to note this concern - 
>
>    Note that, a PCEP implementation that support PCEPS would respond
>    with PCErr message with Error-Type set to [TBA2 by IANA] (PCEP
>    StartTLS failure) and Error-value set to 2 if any other message is
>    sent before StartTLS or Open.  If the sender of the invalid message
>    is a PCEP implementation that does not support PCEPS, it will not be
>    able to understand this error.  A PCEPS implementation could also
>    send the PCErr message as per [RFC5440] with Error-Type "PCEP session
>    establishment failure" and Error-value "reception of an invalid Open
>    message or a non Open message" before closing the session.

You are, of course, the author.  But my opinion is that you'd get
cleaner compatibility by sending a 1/1 error in this situation.

Dale


From nobody Tue Aug 15 21:50:57 2017
Return-Path: <vaibhavsinghacads@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1D591321A5 for <ietf@ietfa.amsl.com>; Tue, 15 Aug 2017 21:50:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SGueAJEUuygL for <ietf@ietfa.amsl.com>; Tue, 15 Aug 2017 21:50:52 -0700 (PDT)
Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A420131D19 for <ietf@ietf.org>; Tue, 15 Aug 2017 21:50:52 -0700 (PDT)
Received: by mail-it0-x22f.google.com with SMTP id 76so13037197ith.0 for <ietf@ietf.org>; Tue, 15 Aug 2017 21:50:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cow4/hqjUgzgfjhx1bbuCnTh7JSAohIPAzOlWm2qWRM=; b=KjJVLKWmqAzmG87QMQvkHuFXTTx7qKI+YwKJ72zUGKxEE9C7EJuwZBkddjPEDZXN8H ex8TtlPSBSDk3dHsNKMP8eBqGa2LCAhmDgghkoNwTJHQfXGH66x419Mb/NVojKZ1Dobw +Ur9GbymYS2Zep7MbMs9mdqtOGS6Q56KsgqR/VIONWZdHWSL5tA5FmgbxzI8Q7TG1/Gc T+GtYUmZUZMG11l6d55aW4R7Ac6k3DkJOEVEeUJHaxunpp/L3iV0ECROAuW83faLnONU NXDELGKr+rKhqi+0EwSNS+Vc6mg+e5zua/N7ekgVATHCoHH0fuofICstv4JLKyjJiq7b /neg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=cow4/hqjUgzgfjhx1bbuCnTh7JSAohIPAzOlWm2qWRM=; b=PKtPDFUPlrKRjo1lyF/JyHAL/cfJMBXZ+9VWaWPt3jz1ZocgEobruDigrPnq5hAmRy TFIR2BA23pw8C8GkRgtLMPfSGfuYYmHIW268RHC0EPxke3diG+jUqvLrBtxfRfyPe8hI NXibNdejLIkX9eI1NwUrMC2tnUOCEd5wcOkFJC7lwHoS3nDD2nl7x9rv2wdSS+7gFBLs y0D9VveaP14+XpT6TBBXzUDL2+lTVTW1LMthwNBod4MaxAW3EZioY5jnHyJtZNLqEHx6 da/0VV4sUhB2PkS+r8g7eggd2uy1aAfeqdVMC1vMEyJfiTvXNIXE6K+R76r9D8oN0iu8 4/Cg==
X-Gm-Message-State: AHYfb5ggVmVE5rOTh82YuJQgZl8Rl4WxMlKZVuEKuhOzze4L2CVq9kfs YBs4PT6/3y+7PiqaBfQsqeqRWNHDB1wvaPo=
X-Received: by 10.36.54.77 with SMTP id l74mr767274itl.148.1502859051501; Tue, 15 Aug 2017 21:50:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.0.208 with HTTP; Tue, 15 Aug 2017 21:50:50 -0700 (PDT)
In-Reply-To: <b1289123-04ac-e62b-879e-614fae9b20b0@bogus.com>
References: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com> <b1289123-04ac-e62b-879e-614fae9b20b0@bogus.com>
From: vaibhav singh <vaibhavsinghacads@gmail.com>
Date: Wed, 16 Aug 2017 10:20:50 +0530
Message-ID: <CACZ1GiooBdEZ_YcBZPQNFkbT0DsGf-Cu25fPYzWcLamLUAH+TA@mail.gmail.com>
Subject: Re: Scope for self-destructing email?
To: joel jaeggli <joelja@bogus.com>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a1144d62ce9a5400556d7a33c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SviqyVp5JYzlcG1k1nGfqqXzb5M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 04:50:55 -0000

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

On Tue, Aug 15, 2017 at 8:42 AM, joel jaeggli <joelja@bogus.com> wrote:

> On 8/14/17 12:01, vaibhav singh wrote:
> > Hi,
> >
> > As some of you may already know, General Data Protection Regulation
> > (GDPR), about to be enforced in the EU within months, and calls for
> > strict regulations for Right to rectify communications, Right to be
> > forgotten , Pseudonymisation and Data portability.
> >
> > With regards to this, me and my friends were thinking about the idea of
> > a self-destructing email, wherein the sender will mark the mail to be
> > destroyed (expunged from the server) once the receiver(s) have finished
> > reading it/after a time period chosen by the sender.
> >
> > Another enhancement to this idea was a notification which will be sent
> > from some (Exploding email RFC) compliant MUA, in case the receiver
> > refuses to delete the email from the client. (I know Snapchat is a poor
> > example here, but they apparently send notifications to the originator
> > of the snap in case any receiver tries to capture the screenshot of the
> > snap. This is, in theory, what we are trying to do here).
> >
> > I would also like to know about things (working groups, internet drafts
> > etc) which are being done to enforce GDPR to
> > email and Instant Messaging especially.
>
> In order that you have some assurance that the demands provided at the
> input side are honored on the receipt side you need effectively
> end-to-end control over the system, that is the sender, receiver, and
> any intermediate hops are part of the same administrative domain such
> that any control imposed is actually implemented. That might be
> practical for an email system but not generally for the email system.
>
>
>
>
We found an archived thread of a similar proposal for XMPP being made in
XMPP Standards list as well. There were a couple of neat outcomes from that
discussion, which I would like to present here as well.

There were a couple of improvements/compromises we were thinking:

1.) The popular opinion is that this will be unenforceable on the client;
we can actually drop the idea of clients being forced to clean up those
messages altogether. Our initial plan to propose this was to let the sender
of the email decide whether he wants to store his emails on the server or
not; that would be what we will be focusing on then.

2.) Matthias suggested a way to implement feature discovery for this:

*Have a central list (possibly mentioned in the documentation of this) of
IPs and domains that really support this feature (a central registry that
maintains the list would test if it really works; I'd offer that my company
can do this but that would have to be decided by the public). If a SMTP
server advertises the feature and it is on the list send the mail without
any warnings, if it advertises it but is not on the list warn the user that
the server might potentionally fake the ability to do this. If it does not
advertise the feature but is on the list warn the user that the server may
not have the ability. If it neither is on the list nor advertise the
feature ask the user if they want to send the email without
self-destruction enabled.*

This seems to work for me. Any problems which could come up with having a
central authority for this feature?

3.) We may have to assume that the sender and receiver of the mail are
trusted; this would mean that the mail may have to be encrypted prior to
sending:

*Encryption would allow you to establish a level of trust with the
recipient. I.e. you encrypt the message and mark it for =E2=80=98self destr=
uct=E2=80=99.
You then have to trust the recipient to destroy it (but at least you don=E2=
=80=99t
have to trust every server along the way). This gives you some level of
reassurance that the message will be destroyed, assuming the recipient is
trustworthy (and runs trustworthy clients).*

4.) A really boiled down version of ephemeral mails could just mark the
mail "outdated" if the information provided in the mail is not expected to
hold good after some time, instead of actually expunging the mail.



*why not try to accommodate both realitys and define a feature which is
called "Invalidation of Messages" or similar instead of "Destructible
Messages". The goal of this feature should be to mark messages in a way,
that the client somehow can mark the message as "not being relevant
anymore" or something like that. So it could still be displayed but grayed
out for example telling the receiver that the message can be ignored.
Additionally there could then be added an attribute "deletionrequest" which
can be set for clients which really want to have destructible messages like
Signal does.*

Any thoughts?

--=20

Regards,
Vaibhav Singh

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Tue, Aug 15, 2017 at 8:42 AM, joel jaeggli <span dir=3D"ltr">&lt;<a =
href=3D"mailto:joelja@bogus.com" target=3D"_blank">joelja@bogus.com</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span c=
lass=3D"gmail-">On 8/14/17 12:01, vaibhav singh wrote:<br>
&gt; Hi,<br>
&gt;<br>
&gt; As some of you may already know, General Data Protection Regulation<br=
>
&gt; (GDPR), about to be enforced in the EU within months, and calls for<br=
>
&gt; strict regulations for Right to rectify communications, Right to be<br=
>
&gt; forgotten , Pseudonymisation and Data portability.<br>
&gt;<br>
&gt; With regards to this, me and my friends were thinking about the idea o=
f<br>
&gt; a self-destructing email, wherein the sender will mark the mail to be<=
br>
&gt; destroyed (expunged from the server) once the receiver(s) have finishe=
d<br>
&gt; reading it/after a time period chosen by the sender.<br>
&gt;<br>
&gt; Another enhancement to this idea was a notification which will be sent=
<br>
&gt; from some (Exploding email RFC) compliant MUA, in case the receiver<br=
>
&gt; refuses to delete the email from the client. (I know Snapchat is a poo=
r<br>
&gt; example here, but they apparently send notifications to the originator=
<br>
&gt; of the snap in case any receiver tries to capture the screenshot of th=
e<br>
&gt; snap. This is, in theory, what we are trying to do here).<br>
&gt;<br>
&gt; I would also like to know about things (working groups, internet draft=
s<br>
&gt; etc) which are being done to enforce GDPR to<br>
&gt; email and Instant Messaging especially.<br>
<br>
</span>In order that you have some assurance that the demands provided at t=
he<br>
input side are honored on the receipt side you need effectively<br>
end-to-end control over the system, that is the sender, receiver, and<br>
any intermediate hops are part of the same administrative domain such<br>
that any control imposed is actually implemented. That might be<br>
practical for an email system but not generally for the email system.<br>
<span class=3D"gmail-HOEnZb"><font color=3D"#888888"><br><br>
<br>
</font></span></blockquote></div><br></div><div class=3D"gmail_extra">We fo=
und an archived thread of a similar proposal for XMPP being made in XMPP St=
andards list as well. There were a couple of neat outcomes from that discus=
sion, which I would like to present here as well.<br><br></div><div class=
=3D"gmail_extra">There were a couple of improvements/compromises we were th=
inking:<br></div><div class=3D"gmail_extra"><br>1.) The popular opinion is =
that this will be unenforceable on the client; we can actually drop the ide=
a of clients being forced to clean up those messages altogether. Our initia=
l plan to propose this was to let the sender of the email decide whether he=
 wants to store his emails on the server or not; that would be what we will=
 be focusing on then.<br></div><div class=3D"gmail_extra"><br>2.) Matthias =
suggested a way to implement feature discovery for this:<span class=3D"gmai=
l-im"><br></span><span class=3D"gmail-im"><div dir=3D"auto"><br><i>Have
 a central list (possibly mentioned in the documentation of this) of IPs
 and domains that really support this feature (a central registry that=20
maintains the list would test if it really works; I&#39;d offer that my=20
company can do this but that would have to be decided by the public). If
 a SMTP server advertises the feature and it is on the list send the=20
mail without any warnings, if it advertises it but is not on the list=20
warn the user that the server might potentionally fake the ability to do
 this. If it does not advertise the feature but is on the list warn the=20
user that the server may not have the ability. If it neither is on the=20
list nor advertise the feature ask the user if they want to send the=20
email without self-destruction enabled.</i></div></span></div><div class=3D=
"gmail_extra"><br></div><div class=3D"gmail_extra">This seems to work for m=
e. Any problems which could come up with having a central authority for thi=
s feature?<br><br></div><div class=3D"gmail_extra">3.) We may have to assum=
e that the sender and receiver of the mail are trusted; this would mean tha=
t the mail may have to be encrypted prior to sending:<br><br> <i>Encryption=
 would allow you to establish a level of trust with the recipient. I.e. you=
 encrypt the <span class=3D"gmail-il">message</span> and mark it for =E2=80=
=98<span class=3D"gmail-il">self</span> <span class=3D"gmail-il">destruct</=
span>=E2=80=99.
 You then have to trust the recipient to destroy it (but at least you=20
don=E2=80=99t have to trust every server along the way). This gives you som=
e=20
level of reassurance that the <span class=3D"gmail-il">message</span> will =
be destroyed, assuming the recipient is trustworthy (and runs trustworthy c=
lients).</i></div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_=
extra">4.) A really boiled down version of ephemeral mails could just mark =
the mail &quot;outdated&quot; if the information provided in the mail is no=
t expected to hold good after some time, instead of actually expunging the =
mail.<br><br> <i>why not try to accommodate both realitys and define a feat=
ure which is called &quot;Invalidation of Messages&quot; or similar instead=
 of &quot;Destructible=C2=A0
Messages&quot;. The goal of this feature should be to mark messages in a wa=
y,<br>
that the client somehow can mark the <span class=3D"gmail-il">message</span=
> as &quot;not being relevant anymore&quot; or something like that. So it c=
ould still be displayed but<br>
grayed out for example telling the receiver that the <span class=3D"gmail-i=
l">message</span> can be ignored. Additionally there could then be added an=
 attribute &quot;deletionrequest&quot; which can be set for clients which r=
eally want to have destructible messages like Signal does.</i></div><div cl=
ass=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Any thoughts?<br><=
/div><div class=3D"gmail_extra"><br>-- <br><div class=3D"gmail_signature"><=
div dir=3D"ltr"><div><br></div>Regards,<div>Vaibhav Singh</div></div></div>
</div></div>

--001a1144d62ce9a5400556d7a33c--


From nobody Wed Aug 16 02:24:51 2017
Return-Path: <stefan.winter@restena.lu>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D9F22132025; Wed, 16 Aug 2017 02:24:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stefan Winter <stefan.winter@restena.lu>
To: <ops-dir@ietf.org>
Cc: tsvwg@ietf.org, ietf@ietf.org, draft-ietf-tsvwg-sctp-ndata.all@ietf.org
Subject: Opsdir last call review of draft-ietf-tsvwg-sctp-ndata-12
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150287547583.12471.9085655210334710687@ietfa.amsl.com>
Date: Wed, 16 Aug 2017 02:24:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qDXwA1Gv2T914AZtFbo2Zir9gLY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 09:24:36 -0000

Reviewer: Stefan Winter
Review result: Has Issues

One issue:

The chapter IANA considerations mentions four bits to be registered: E,B,U,I.
In the main body, only three of those are actually defined and used (End of
fragmented message, Beginning of fragmented message, Unordered/Ordered
message). Please add a definition of the I bit or remove the IANA registration
request for that bit.

And the rest are only musings not needing any action if the authors don't want
to action on them:

The introduction presents a good use case, quoting: "e.g., when the
transmission of an urgent
   message is blocked from transmission because the sender has started
   the transmission of another, possibly large, message".

The later queueing example in figure 1 has three SIDs being queued
simultanseously. It is not clear which of those "has already started" and which
are the important ones being delayed. For a better understanding of the reader,
it might be useful to revise the figure so that the head-of-line blocking
happens for SID 1 because transmission of  0 and 2 has already started (and
declare SID 1 to be the "important" message). The ASCII art would just have to
indent SID 1 content a bit (placing 0 and 2 earlier in time), and the resulting
serialisation would then put all the SID 1 messages at the very end, when 0 and
2 have been completely submitted (right?).

In 2.2.3, is there any particular reason why the "protocol violation" error
cause is only a MAY? As it enables debugging on the remote end, a SHOULD seems
useful.


From nobody Wed Aug 16 08:02:17 2017
Return-Path: <lee@asgard.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E62AA1321D9 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 08:02:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Ttx4RTJ9nRQ for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 08:02:13 -0700 (PDT)
Received: from atl4mhob16.registeredsite.com (atl4mhob16.registeredsite.com [209.17.115.109]) (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 D60C2132394 for <ietf@ietf.org>; Wed, 16 Aug 2017 08:02:05 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.206]) by atl4mhob16.registeredsite.com (8.14.4/8.14.4) with ESMTP id v7GF22gh023818 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Wed, 16 Aug 2017 11:02:02 -0400
Received: (qmail 24092 invoked by uid 0); 16 Aug 2017 15:02:02 -0000
X-TCPREMOTEIP: 68.100.68.25
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.1.160?) (lee@asgard.org@68.100.68.25) by 0 with ESMTPA; 16 Aug 2017 15:02:01 -0000
User-Agent: Microsoft-MacOutlook/14.7.2.170228
Date: Wed, 16 Aug 2017 11:01:58 -0400
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: Lee Howard <lee@asgard.org>
To: John Curran <jcurran@istaff.org>, Randy Bush <randy@psg.com>
CC: IETF Rinse Repeat <ietf@ietf.org>
Message-ID: <D5B9D471.8118C%lee@asgard.org>
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <6C3D3B7C-9732-4BD2-97F6-F03A00CB6781@fugue.com> <3A586681-AAEC-4395-B386-450C0AE7950F@vpnc.org> <m2r2wwt4vx.wl-randy@psg.com> <F4D3D8A8-D536-4054-838D-320B3A7EA4FD@istaff.org>
In-Reply-To: <F4D3D8A8-D536-4054-838D-320B3A7EA4FD@istaff.org>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZSyABa6G_AKnL5qjg_crpU3Cl2o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 15:02:16 -0000

On 8/14/17, 11:09 AM, "ietf on behalf of John Curran"
<ietf-bounces@ietf.org on behalf of jcurran@istaff.org> wrote:

>On 31 Jul 2017, at 8:10 PM, Randy Bush <randy@psg.com> wrote:
>> ...
>>
>To that end, would it be possible for those behind the "IPv6-only Wi-Fi
>for IETF=E2=80=9D
>draft to partner with the NOC at the upcoming meeting to help debug
>issues that=20
>are reported on =E2=80=9Cietf-nat64* and publish the results?  The IETF does hav=
e
>a wide
>variety of users, which is really helpful in finding edge cases with
>protocols that
>might have issues and otherwise go undiscovered.  If it were may clear
>(e.g. during
>the opening) that there is a goal to put the =E2=80=9Cietf-nat64=E2=80=9D network thro=
ugh
>its paces
>and that there would be a post-mortem I-D as a result, I suspect quite a
>few folks
>would at least give that setup a try for a while, with the goal of
>finding and reporting
>breakage.


As promised, I have proposed an "IPv4-IPv6 Transition Technology Interop=E2=80=9D
for the IETF100 Hackathon:
Description at:=20
https://www.ietf.org/registration/MeetingWiki/wiki/100hackathon
Discussion/planning list:
http://lists.retevia.net/listinfo.cgi/v6-interop-retevia.net
Hackathon registration and mailing list at
https://www.ietf.org/hackathon/100-hackathon.html

I have two versions of NAT64 planned (A10, VPP). I would like to compare
to at least 464xlat (probably with CLAT on gateway, not device) to address
some of the comments in the thread. I=E2=80=99d also like to compare other
transition technologies, such as DS-Lite and MAP-T/MAP-E, though these are
probably more interesting to the rest of the Internet than to the narrow
question of what the IETF should do. All of that, of course, is subject to
people wanting to do it, and proper planning ahead of time.


Lee



From nobody Wed Aug 16 08:28:29 2017
Return-Path: <julien.meuric@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDE261323C3; Wed, 16 Aug 2017 08:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.534
X-Spam-Level: 
X-Spam-Status: No, score=-3.534 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3rtPdczI2qgn; Wed, 16 Aug 2017 08:28:21 -0700 (PDT)
Received: from r-mail1.rd.orange.com (r-mail1.rd.orange.com [217.108.152.41]) by ietfa.amsl.com (Postfix) with ESMTP id 199821321D9; Wed, 16 Aug 2017 08:28:21 -0700 (PDT)
Received: from r-mail1.rd.orange.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id AFEC3A441FB; Wed, 16 Aug 2017 17:20:04 +0200 (CEST)
Received: from FTRDCH01.rd.francetelecom.fr (unknown [10.194.32.11]) by r-mail1.rd.orange.com (Postfix) with ESMTP id 97AE6A44176; Wed, 16 Aug 2017 17:20:04 +0200 (CEST)
Received: from [10.193.71.121] (10.193.71.121) by FTRDCH01.rd.francetelecom.fr (10.194.32.11) with Microsoft SMTP Server id 14.3.352.0; Wed, 16 Aug 2017 17:20:04 +0200
Subject: Re: Genart last call review of draft-ietf-pce-pce-initiated-lsp-10
To: Joel Halpern <jmh@joelhalpern.com>, <gen-art@ietf.org>
CC: <draft-ietf-pce-pce-initiated-lsp.all@ietf.org>, <pce@ietf.org>, <ietf@ietf.org>
References: <150240703036.8476.2109418125181500710@ietfa.amsl.com>
From: Julien Meuric <julien.meuric@orange.com>
Organization: Orange
Message-ID: <25b0a2c3-0d8b-0e65-15f7-7e4c360032a9@orange.com>
Date: Wed, 16 Aug 2017 17:20:01 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <150240703036.8476.2109418125181500710@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Xs9fpLKm1MGB_nh4Kffr3FRjMek>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 15:28:23 -0000

Hi Joel,

Any issue with a request to initiate an LSP setup/teardown to a device? ;-)

I agree the name reads odd, but it has been there for some time now and
the WG seems to be fine with it. Besides, it does not prevent anyone to
add better wording in a patch to their favorite decoding software...

Thanks a lot for your review,

Julien


Aug. 11, 2017 - jmh@joelhalpern.com:
> Nits/editorial comments:
>     It seems odd to have a message for the creation or deletion of an LSP
>     called an LSP Initiate Request.


From nobody Wed Aug 16 08:48:04 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B3A0132626; Wed, 16 Aug 2017 08:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q6ORbgF922GB; Wed, 16 Aug 2017 08:48:01 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 0ACE2132622; Wed, 16 Aug 2017 08:48:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id E26301C0496; Wed, 16 Aug 2017 08:48:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1502898480; bh=DQONiAweeOy21p7SDspn4wyqS0pI8nxPX6Yhns/Px6g=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=rPg411NGlCGLA5tRJasHr9GBkAUPlgyUJTj7poK0TkbDXwgnRR/b4y2ZXNxOypS// N2XgpXwDbXjI2dDwHBIUy5lKHSPkkc8PuX38HM5qCNNk+88/NK7OSt5ZYNzFQX7iWC 5o5iGFsiBxYRe9pVPUENNVFYKc65D0ub0wgF8f6s=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [50.225.209.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 17C85403133; Wed, 16 Aug 2017 08:47:59 -0700 (PDT)
Subject: Re: Genart last call review of draft-ietf-pce-pce-initiated-lsp-10
To: Julien Meuric <julien.meuric@orange.com>, gen-art@ietf.org
Cc: draft-ietf-pce-pce-initiated-lsp.all@ietf.org, pce@ietf.org, ietf@ietf.org
References: <150240703036.8476.2109418125181500710@ietfa.amsl.com> <25b0a2c3-0d8b-0e65-15f7-7e4c360032a9@orange.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <d1e134b2-a440-a8b2-b15f-8686906c3e38@joelhalpern.com>
Date: Wed, 16 Aug 2017 11:47:59 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <25b0a2c3-0d8b-0e65-15f7-7e4c360032a9@orange.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AsSUwr-zJC1D3NcOWctRFsTms8E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 15:48:02 -0000

That would work for me.  I did conclude that the WG was happy with the 
term, which is why I considered it a nit.

Yours,
Joel

On 8/16/17 11:20 AM, Julien Meuric wrote:
> Hi Joel,
> 
> Any issue with a request to initiate an LSP setup/teardown to a device? ;-)
> 
> I agree the name reads odd, but it has been there for some time now and
> the WG seems to be fine with it. Besides, it does not prevent anyone to
> add better wording in a patch to their favorite decoding software...
> 
> Thanks a lot for your review,
> 
> Julien
> 
> 
> Aug. 11, 2017 - jmh@joelhalpern.com:
>> Nits/editorial comments:
>>      It seems odd to have a message for the creation or deletion of an LSP
>>      called an LSP Initiate Request.


From nobody Wed Aug 16 09:49:45 2017
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7461B132351 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 09:49:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bUxQxA1eHHY6 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 09:49:42 -0700 (PDT)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FC87132339 for <ietf@ietf.org>; Wed, 16 Aug 2017 09:49:42 -0700 (PDT)
Received: by mail-qt0-x22c.google.com with SMTP id 16so24115314qtz.4 for <ietf@ietf.org>; Wed, 16 Aug 2017 09:49:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ME4HYmjIOxrTex4nPylGyiun/l7Oi4tsApR6SXyuOxY=; b=ASnR1pf//avEqIOTHPsiH4gP/xoxceCoNViZ0BhoG132ethzLMaaPa7/+oQp+CNKvs nWuWMc5vD085/KzAKvuWOHvL3EAgb/KozvEXRdht3ESdrdMMR3bD12RK7IfjyzrXZvEF 7/Lo3kLlVDP73TLgZbtzA50cQIut+ZN3FP/P4FQI6M6AQaDS5xdvDIF9pW24Sj2tcjQ5 cu3Xqg+qzK7YHDLpRuZukBdAkB2Z4jmVmc7lJIDf1fRlTtSVqUdGw2hDtAyrTKOi85uf 5KEaEK3XtJidGh6GMriXkkpG5DgBZVhokYINhzj/aTKt6MUr2OnxGgJXUuKKHKv9Ewdh cNKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ME4HYmjIOxrTex4nPylGyiun/l7Oi4tsApR6SXyuOxY=; b=CAsO/Jn9JY2SQ86iMTUfdbUeGejB2I1lAxa4h2NhULG1chZaxT+FC83P4J3x5xCkNa ZGvQ9cwCpOOj7ytqYSYiJQOP79dOo1AucdTxsOxp7VNVItphyY4MAFQ7OusDN8WijBm1 1G31g2TH0YJH0jQe+R6vu245GGIAHHCgUkTzrTE/F6RrNerSfNZfekfMNCj/V567rv6N JapUmRQLW3H2sGmdj8JPvBuhF4lTMi/+nDiQypJJVefZXgctK1TlFoYink9Y+rqMZWDl NF212mTMCVSnMMMSe8tc2OpCaTZUrD3mYKDvE9tzslAYwoYgK8E/1JNshU5WuhhUAEVG EvEQ==
X-Gm-Message-State: AHYfb5g0BRjVrmMUNF2U1EXQEAHHxlcqYGRAkKsEbVA1uiEueKMeKeDk Pd2oXlt+DnHrNMivzFMrpXmOzC3naQ==
X-Received: by 10.200.40.197 with SMTP id j5mr3197092qtj.100.1502902181418; Wed, 16 Aug 2017 09:49:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.59.248 with HTTP; Wed, 16 Aug 2017 09:49:11 -0700 (PDT)
In-Reply-To: <CACZ1GiooBdEZ_YcBZPQNFkbT0DsGf-Cu25fPYzWcLamLUAH+TA@mail.gmail.com>
References: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com> <b1289123-04ac-e62b-879e-614fae9b20b0@bogus.com> <CACZ1GiooBdEZ_YcBZPQNFkbT0DsGf-Cu25fPYzWcLamLUAH+TA@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 16 Aug 2017 09:49:11 -0700
Message-ID: <CA+9kkMAAQh64M59g0Jn=2j0czS6q56-yoOadGMoeVMTZ=4Z72Q@mail.gmail.com>
Subject: Re: Scope for self-destructing email?
To: vaibhav singh <vaibhavsinghacads@gmail.com>
Cc: joel jaeggli <joelja@bogus.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a114069a4a7df060556e1ae90"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gMVhb405XlGjrH4ljT_-p6UsN5A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 16:49:44 -0000

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

On Tue, Aug 15, 2017 at 9:50 PM, vaibhav singh <vaibhavsinghacads@gmail.com>
wrote:

>
> 4.) A really boiled down version of ephemeral mails could just mark the
> mail "outdated" if the information provided in the mail is not expected to
> hold good after some time, instead of actually expunging the mail.
>
>
>
> *why not try to accommodate both realitys and define a feature which is
> called "Invalidation of Messages" or similar instead of "Destructible
> Messages". The goal of this feature should be to mark messages in a way,
> that the client somehow can mark the message as "not being relevant
> anymore" or something like that. So it could still be displayed but grayed
> out for example telling the receiver that the message can be ignored.
> Additionally there could then be added an attribute "deletionrequest" which
> can be set for clients which really want to have destructible messages like
> Signal does.*
>
> Any thoughts?
>
>
I think there are two potential lines of development here, though I confess
I am skeptical of the value of either.

The first is providing a facility that declares a particular message to be
automatically overcome by events at a particular time, leaving it
completely up to the recipient how to process the message based on that
metadata.  There are simple message types (today's weather, lunch
availability, etc.) that could be thus set to be marked OBE when no longer
relevant.  Some clients might choose to auto-delete them or auto-archive
them when the time is reached, but this would be because of their preferred
handling and not a guarantee to the sender that the sender's intent is
being honored.  A message header like OBE-At: could be registered
provisionally without much hassle, and you could see if it saw
implementation and use.

The second is a trickier question:  is it possible to construct a message
such that it is cryptographically non-repudiable within a set time frame
but repudiable thereafter?  I think the answer to this is yes, but it
relies on a carefully crafted interaction among the use of limited validity
certificates, requirements to confirm validity with a CA, and CA behavior.
You could deploy that in a limited environment, in other words, and see if
it was useful enough to make the behavior standard.  It's less clear to me,
though, why it would be useful.  The one scenario I can construct is
financial, as part of the flow for placing a time limited order, but the
flow seems strictly worse that a simpler flow that includes the time limit
for the order within a message which is permanently non-repudiable.

regards,

Ted

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra">On Tue, Aug 15, 2017 at 9:5=
0 PM, vaibhav singh <span dir=3D"ltr">&lt;<a href=3D"mailto:vaibhavsinghaca=
ds@gmail.com" target=3D"_blank">vaibhavsinghacads@gmail.com</a>&gt;</span> =
wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div di=
r=3D"ltr"><div><div class=3D"h5"><span class=3D"m_4794358861034989667gmail-=
"></span></div></div><br><div class=3D"gmail_extra">4.) A really boiled dow=
n version of ephemeral mails could just mark the mail &quot;outdated&quot; =
if the information provided in the mail is not expected to hold good after =
some time, instead of actually expunging the mail.<br><br> <i>why not try t=
o accommodate both realitys and define a feature which is called &quot;Inva=
lidation of Messages&quot; or similar instead of &quot;Destructible=C2=A0
Messages&quot;. The goal of this feature should be to mark messages in a wa=
y,<br>
that the client somehow can mark the <span class=3D"m_4794358861034989667gm=
ail-il">message</span> as &quot;not being relevant anymore&quot; or somethi=
ng like that. So it could still be displayed but<br>
grayed out for example telling the receiver that the <span class=3D"m_47943=
58861034989667gmail-il">message</span> can be ignored. Additionally there c=
ould then be added an attribute &quot;deletionrequest&quot; which can be se=
t for clients which really want to have destructible messages like Signal d=
oes.</i></div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extr=
a">Any thoughts?<span class=3D"HOEnZb"><font color=3D"#888888"><br></font><=
/span></div><span class=3D"HOEnZb"></span><br></div></blockquote></div><br>=
</div><div class=3D"gmail_extra">I think there are two potential lines of d=
evelopment here, though I confess I am skeptical of the value of either.<br=
><br></div><div class=3D"gmail_extra">The first is providing a facility tha=
t declares a particular message to be automatically overcome by events at a=
 particular time, leaving it completely up to the recipient how to process =
the message based on that metadata.=C2=A0 There are simple message types (t=
oday&#39;s weather, lunch availability, etc.) that could be thus set to be =
marked OBE when no longer relevant.=C2=A0 Some clients might choose to auto=
-delete them or auto-archive them when the time is reached, but this would =
be because of their preferred handling and not a guarantee to the sender th=
at the sender&#39;s intent is being honored.=C2=A0 A message header like OB=
E-At: could be registered provisionally without much hassle, and you could =
see if it saw implementation and use. <br></div><div class=3D"gmail_extra">=
<br></div><div class=3D"gmail_extra">The second is a trickier question:=C2=
=A0 is it possible to construct a message such that it is cryptographically=
 non-repudiable within a set time frame but repudiable thereafter?=C2=A0 I =
think the answer to this is yes, but it relies on a carefully crafted inter=
action among the use of limited validity certificates, requirements to conf=
irm validity with a CA, and CA behavior.=C2=A0 You could deploy that in a l=
imited environment, in other words, and see if it was useful enough to make=
 the behavior standard.=C2=A0 It&#39;s less clear to me, though, why it wou=
ld be useful.=C2=A0 The one scenario I can construct is financial, as part =
of the flow for placing a time limited order, but the flow seems strictly w=
orse that a simpler flow that includes the time limit for the order within =
a message which is permanently non-repudiable.<br><br></div><div class=3D"g=
mail_extra">regards,<br><br></div><div class=3D"gmail_extra">Ted<br></div><=
/div>

--001a114069a4a7df060556e1ae90--


From nobody Wed Aug 16 10:22:56 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77B0413235E for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 10:22:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=ya/Xgrs8; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=zcdb+T6U
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aheEGCGezSQB for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 10:22:53 -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 4B11B132344 for <ietf@ietf.org>; Wed, 16 Aug 2017 10:22:53 -0700 (PDT)
Received: from sm-THINK.elandsys.com ([12.217.29.81]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v7GHMU2o025734 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Aug 2017 10:22:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1502904158; x=1502990558; bh=JrsPLtAIecvGRdamXx86AEOluR9t7zM44sWQQi3TqYo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ya/Xgrs8eHiVVNiQJPw95xbonXKCOyZE0EJY0KFIi3iNZa2oqOQRRJPU/HSlhSuUt Gx+fiLVPfA64VNTaSWv+rpffcBhRfSFG6qQX6Hbjm1YG246blax19bAc6NKi89wM9q lepQ6dj+uOu6dMXMi3sXFU05YKpdYYFxcQrESENI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1502904158; x=1502990558; i=@elandsys.com; bh=JrsPLtAIecvGRdamXx86AEOluR9t7zM44sWQQi3TqYo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=zcdb+T6U40yI9i2MBwhxyWAkKRe7mDbc0HUZ5C4Dnk5LyF7Ou7ykntma7NpYqeuYM p839NVyd5INNmK6uPSpO8V8UKDiGw2EHULhGUJ0CV9m/YA5Z0fhlXxxRONb1etWrm8 J0op7lelsDGe5ufYE4xjIUaT/ht+rBxsQmPZ49Ng=
Message-Id: <6.2.5.6.2.20170816081250.05720b30@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 16 Aug 2017 10:10:32 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [homenet] Last Call: <draft-ietf-homenet-dot-12.txt> (Special Use Domain 'home.arpa.') to Proposed Standard
Cc: Pierre Pfister <pierre.pfister@darou.fr>, Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <150246097710.24498.9883419791827623506.idtracker@ietfa.ams l.com>
References: <150246097710.24498.9883419791827623506.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/j3MJnCw48ijODpjxPfnOPEUpKfI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 17:22:54 -0000

Hello,
At 07:16 AM 8/11/2017, The IESG wrote:
>The IESG has received a request from the Home Networking WG (homenet) to
>consider the following document: - 'Special Use Domain 'home.arpa.''
>   <draft-ietf-homenet-dot-12.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 2017-08-25. Exceptionally, comments may be

I took a quick look at draft-ietf-homenet-dot-12.

In Section 4:

   "So for example a query for the NS record for 'home.arpa.'  MUST
    NOT result in that query being forwarded to an upstream cache nor
    to the authoritative DNS server for '.arpa.'."

As the sentence provides an example, the usage of the RFC 2119 
keyword is incorrect.  The "MUST result in whatever queries are 
necessary" seems like specifying by example.

Regards,
S. Moonesamy 


From nobody Wed Aug 16 10:30:44 2017
Return-Path: <moritz30@moritz30.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E46B126CB6 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 10:30:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.08
X-Spam-Level: *
X-Spam-Status: No, score=1.08 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.723, MISSING_MIMEOLE=1.899, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1cT_6664AAkS for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 10:30:41 -0700 (PDT)
Received: from sender-of-o52.zoho.com (sender-of-o52.zoho.com [135.84.80.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 035EC132344 for <ietf@ietf.org>; Wed, 16 Aug 2017 10:30:40 -0700 (PDT)
Received: from [192.168.179.178] (p5DC6529D.dip0.t-ipconnect.de [93.198.82.157]) by mx.zohomail.com with SMTPS id 1502904635181654.2937958497436; Wed, 16 Aug 2017 10:30:35 -0700 (PDT)
Date: Wed, 16 Aug 2017 19:30:23 +0200
Subject: Re: Scope for self-destructing email?
Message-ID: <c661043b-0870-436a-b27e-95f0b7a51923@email.android.com>
X-Android-Message-ID: <c661043b-0870-436a-b27e-95f0b7a51923@email.android.com>
In-Reply-To: <CACZ1GiooBdEZ_YcBZPQNFkbT0DsGf-Cu25fPYzWcLamLUAH+TA@mail.gmail.com>
From: Matthias Merkel <moritz30@moritz30.de>
To: vaibhav singh <vaibhavsinghacads@gmail.com>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>, joel jaeggli <joelja@bogus.com>
Importance: Normal
X-Priority: 3
X-MSMail-Priority: Normal
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64
X-ZohoMailClient: External
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1Hj9rK1b9WgFSEJ3szheQN414k4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 17:30:43 -0000

PGRpdiBkaXI9J2F1dG8nPldlbGwuIFRoZSBwcm9ibGVtIHdpdGggYSBjZW50cmFsIGF1dGhvcml0
eSBpcyB0aGF0IGl0IGhhcyB0byBiZSB0cnVzdGVkLjxkaXYgZGlyPSJhdXRvIj48YnI+PC9kaXY+
PGRpdiBkaXI9ImF1dG8iPkluIGNhc2UgbXkgY29tcGFueSB3aWxsIHNlcnZlIGFzIGNlbnRyYWwg
YXV0aG9yaXR5IHdlIHdvdWxkIHByb3ZpZGUgcHVibGljIGF1ZGl0cyB3aGljaCBldmVyeW9uZSBj
b3VsZCB1c2UgdG8gdmVyaWZ5IHdlIGZvbGxvd2VkIHRoZSBydWxlcy48L2Rpdj48ZGl2IGRpcj0i
YXV0byI+PGJyPjwvZGl2PjxkaXYgZGlyPSJhdXRvIj5JbiBjYXNlIHNvbWUgb3RoZXIgb3JnYW5p
c2F0aW9uIHdvdWxkIHNlcnZlIGFzIGNlbnRyYWwgYXV0aG9yaXR5IEknZCBzdWdnZXN0IHRvIHJl
cXVpcmUgaXQgdG8gcHJvdmlkZSB0aGVzZSBhdWRpdHMgYXMgd2VsbC48L2Rpdj48L2Rpdj48ZGl2
IGNsYXNzPSJnbWFpbF9leHRyYSI+PGJyPjxkaXYgY2xhc3M9ImdtYWlsX3F1b3RlIj5PbiBBdWcg
MTYsIDIwMTcgNjo1MCBBTSwgdmFpYmhhdiBzaW5naCAmbHQ7dmFpYmhhdnNpbmdoYWNhZHNAZ21h
aWwuY29tJmd0OyB3cm90ZTo8YnIgdHlwZT0iYXR0cmlidXRpb24iPjxibG9ja3F1b3RlIGNsYXNz
PSJxdW90ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNv
bGlkO3BhZGRpbmctbGVmdDoxZXgiPjxkaXYgZGlyPSJsdHIiPjxiciAvPjxkaXY+PGJyIC8+PGRp
diBjbGFzcz0iZWxpZGVkLXRleHQiPk9uIFR1ZSwgQXVnIDE1LCAyMDE3IGF0IDg6NDIgQU0sIGpv
ZWwgamFlZ2dsaSA8c3BhbiBkaXI9Imx0ciI+Jmx0OzxhIGhyZWY9Im1haWx0bzpqb2VsamEmIzY0
O2JvZ3VzLmNvbSI+am9lbGphJiM2NDtib2d1cy5jb208L2E+Jmd0Ozwvc3Bhbj4gd3JvdGU6PGJy
IC8+PGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbjowcHggMHB4IDBweCAwLjhleDtib3JkZXItbGVm
dDoxcHggc29saWQgcmdiKCAyMDQgLCAyMDQgLCAyMDQgKTtwYWRkaW5nLWxlZnQ6MWV4Ij5PbiA4
LzE0LzE3IDEyOjAxLCB2YWliaGF2IHNpbmdoIHdyb3RlOjxiciAvPg0KJmd0OyBIaSw8YnIgLz4N
CiZndDs8YnIgLz4NCiZndDsgQXMgc29tZSBvZiB5b3UgbWF5IGFscmVhZHkga25vdywgR2VuZXJh
bCBEYXRhIFByb3RlY3Rpb24gUmVndWxhdGlvbjxiciAvPg0KJmd0OyAoR0RQUiksIGFib3V0IHRv
IGJlIGVuZm9yY2VkIGluIHRoZSBFVSB3aXRoaW4gbW9udGhzLCBhbmQgY2FsbHMgZm9yPGJyIC8+
DQomZ3Q7IHN0cmljdCByZWd1bGF0aW9ucyBmb3IgUmlnaHQgdG8gcmVjdGlmeSBjb21tdW5pY2F0
aW9ucywgUmlnaHQgdG8gYmU8YnIgLz4NCiZndDsgZm9yZ290dGVuICwgUHNldWRvbnltaXNhdGlv
biBhbmQgRGF0YSBwb3J0YWJpbGl0eS48YnIgLz4NCiZndDs8YnIgLz4NCiZndDsgV2l0aCByZWdh
cmRzIHRvIHRoaXMsIG1lIGFuZCBteSBmcmllbmRzIHdlcmUgdGhpbmtpbmcgYWJvdXQgdGhlIGlk
ZWEgb2Y8YnIgLz4NCiZndDsgYSBzZWxmLWRlc3RydWN0aW5nIGVtYWlsLCB3aGVyZWluIHRoZSBz
ZW5kZXIgd2lsbCBtYXJrIHRoZSBtYWlsIHRvIGJlPGJyIC8+DQomZ3Q7IGRlc3Ryb3llZCAoZXhw
dW5nZWQgZnJvbSB0aGUgc2VydmVyKSBvbmNlIHRoZSByZWNlaXZlcihzKSBoYXZlIGZpbmlzaGVk
PGJyIC8+DQomZ3Q7IHJlYWRpbmcgaXQvYWZ0ZXIgYSB0aW1lIHBlcmlvZCBjaG9zZW4gYnkgdGhl
IHNlbmRlci48YnIgLz4NCiZndDs8YnIgLz4NCiZndDsgQW5vdGhlciBlbmhhbmNlbWVudCB0byB0
aGlzIGlkZWEgd2FzIGEgbm90aWZpY2F0aW9uIHdoaWNoIHdpbGwgYmUgc2VudDxiciAvPg0KJmd0
OyBmcm9tIHNvbWUgKEV4cGxvZGluZyBlbWFpbCBSRkMpIGNvbXBsaWFudCBNVUEsIGluIGNhc2Ug
dGhlIHJlY2VpdmVyPGJyIC8+DQomZ3Q7IHJlZnVzZXMgdG8gZGVsZXRlIHRoZSBlbWFpbCBmcm9t
IHRoZSBjbGllbnQuIChJIGtub3cgU25hcGNoYXQgaXMgYSBwb29yPGJyIC8+DQomZ3Q7IGV4YW1w
bGUgaGVyZSwgYnV0IHRoZXkgYXBwYXJlbnRseSBzZW5kIG5vdGlmaWNhdGlvbnMgdG8gdGhlIG9y
aWdpbmF0b3I8YnIgLz4NCiZndDsgb2YgdGhlIHNuYXAgaW4gY2FzZSBhbnkgcmVjZWl2ZXIgdHJp
ZXMgdG8gY2FwdHVyZSB0aGUgc2NyZWVuc2hvdCBvZiB0aGU8YnIgLz4NCiZndDsgc25hcC4gVGhp
cyBpcywgaW4gdGhlb3J5LCB3aGF0IHdlIGFyZSB0cnlpbmcgdG8gZG8gaGVyZSkuPGJyIC8+DQom
Z3Q7PGJyIC8+DQomZ3Q7IEkgd291bGQgYWxzbyBsaWtlIHRvIGtub3cgYWJvdXQgdGhpbmdzICh3
b3JraW5nIGdyb3VwcywgaW50ZXJuZXQgZHJhZnRzPGJyIC8+DQomZ3Q7IGV0Yykgd2hpY2ggYXJl
IGJlaW5nIGRvbmUgdG8gZW5mb3JjZSBHRFBSIHRvPGJyIC8+DQomZ3Q7IGVtYWlsIGFuZCBJbnN0
YW50IE1lc3NhZ2luZyBlc3BlY2lhbGx5LjxiciAvPg0KPGJyIC8+DQpJbiBvcmRlciB0aGF0IHlv
dSBoYXZlIHNvbWUgYXNzdXJhbmNlIHRoYXQgdGhlIGRlbWFuZHMgcHJvdmlkZWQgYXQgdGhlPGJy
IC8+DQppbnB1dCBzaWRlIGFyZSBob25vcmVkIG9uIHRoZSByZWNlaXB0IHNpZGUgeW91IG5lZWQg
ZWZmZWN0aXZlbHk8YnIgLz4NCmVuZC10by1lbmQgY29udHJvbCBvdmVyIHRoZSBzeXN0ZW0sIHRo
YXQgaXMgdGhlIHNlbmRlciwgcmVjZWl2ZXIsIGFuZDxiciAvPg0KYW55IGludGVybWVkaWF0ZSBo
b3BzIGFyZSBwYXJ0IG9mIHRoZSBzYW1lIGFkbWluaXN0cmF0aXZlIGRvbWFpbiBzdWNoPGJyIC8+
DQp0aGF0IGFueSBjb250cm9sIGltcG9zZWQgaXMgYWN0dWFsbHkgaW1wbGVtZW50ZWQuIFRoYXQg
bWlnaHQgYmU8YnIgLz4NCnByYWN0aWNhbCBmb3IgYW4gZW1haWwgc3lzdGVtIGJ1dCBub3QgZ2Vu
ZXJhbGx5IGZvciB0aGUgZW1haWwgc3lzdGVtLjxiciAvPg0KPGZvbnQgY29sb3I9IiM4ODg4ODgi
PjxiciAvPjxiciAvPg0KPGJyIC8+DQo8L2ZvbnQ+PC9ibG9ja3F1b3RlPjwvZGl2PjxiciAvPjwv
ZGl2PjxkaXY+V2UgZm91bmQgYW4gYXJjaGl2ZWQgdGhyZWFkIG9mIGEgc2ltaWxhciBwcm9wb3Nh
bCBmb3IgWE1QUCBiZWluZyBtYWRlIGluIFhNUFAgU3RhbmRhcmRzIGxpc3QgYXMgd2VsbC4gVGhl
cmUgd2VyZSBhIGNvdXBsZSBvZiBuZWF0IG91dGNvbWVzIGZyb20gdGhhdCBkaXNjdXNzaW9uLCB3
aGljaCBJIHdvdWxkIGxpa2UgdG8gcHJlc2VudCBoZXJlIGFzIHdlbGwuPGJyIC8+PGJyIC8+PC9k
aXY+PGRpdj5UaGVyZSB3ZXJlIGEgY291cGxlIG9mIGltcHJvdmVtZW50cy9jb21wcm9taXNlcyB3
ZSB3ZXJlIHRoaW5raW5nOjxiciAvPjwvZGl2PjxkaXY+PGJyIC8+MS4pIFRoZSBwb3B1bGFyIG9w
aW5pb24gaXMgdGhhdCB0aGlzIHdpbGwgYmUgdW5lbmZvcmNlYWJsZSBvbiB0aGUgY2xpZW50OyB3
ZSBjYW4gYWN0dWFsbHkgZHJvcCB0aGUgaWRlYSBvZiBjbGllbnRzIGJlaW5nIGZvcmNlZCB0byBj
bGVhbiB1cCB0aG9zZSBtZXNzYWdlcyBhbHRvZ2V0aGVyLiBPdXIgaW5pdGlhbCBwbGFuIHRvIHBy
b3Bvc2UgdGhpcyB3YXMgdG8gbGV0IHRoZSBzZW5kZXIgb2YgdGhlIGVtYWlsIGRlY2lkZSB3aGV0
aGVyIGhlIHdhbnRzIHRvIHN0b3JlIGhpcyBlbWFpbHMgb24gdGhlIHNlcnZlciBvciBub3Q7IHRo
YXQgd291bGQgYmUgd2hhdCB3ZSB3aWxsIGJlIGZvY3VzaW5nIG9uIHRoZW4uPGJyIC8+PC9kaXY+
PGRpdj48YnIgLz4yLikgTWF0dGhpYXMgc3VnZ2VzdGVkIGEgd2F5IHRvIGltcGxlbWVudCBmZWF0
dXJlIGRpc2NvdmVyeSBmb3IgdGhpczo8YnIgLz48ZGl2IGRpcj0iYXV0byI+PGJyIC8+PGk+SGF2
ZQ0KIGEgY2VudHJhbCBsaXN0IChwb3NzaWJseSBtZW50aW9uZWQgaW4gdGhlIGRvY3VtZW50YXRp
b24gb2YgdGhpcykgb2YgSVBzDQogYW5kIGRvbWFpbnMgdGhhdCByZWFsbHkgc3VwcG9ydCB0aGlz
IGZlYXR1cmUgKGEgY2VudHJhbCByZWdpc3RyeSB0aGF0IA0KbWFpbnRhaW5zIHRoZSBsaXN0IHdv
dWxkIHRlc3QgaWYgaXQgcmVhbGx5IHdvcmtzOyBJJiMzOTtkIG9mZmVyIHRoYXQgbXkgDQpjb21w
YW55IGNhbiBkbyB0aGlzIGJ1dCB0aGF0IHdvdWxkIGhhdmUgdG8gYmUgZGVjaWRlZCBieSB0aGUg
cHVibGljKS4gSWYNCiBhIFNNVFAgc2VydmVyIGFkdmVydGlzZXMgdGhlIGZlYXR1cmUgYW5kIGl0
IGlzIG9uIHRoZSBsaXN0IHNlbmQgdGhlIA0KbWFpbCB3aXRob3V0IGFueSB3YXJuaW5ncywgaWYg
aXQgYWR2ZXJ0aXNlcyBpdCBidXQgaXMgbm90IG9uIHRoZSBsaXN0IA0Kd2FybiB0aGUgdXNlciB0
aGF0IHRoZSBzZXJ2ZXIgbWlnaHQgcG90ZW50aW9uYWxseSBmYWtlIHRoZSBhYmlsaXR5IHRvIGRv
DQogdGhpcy4gSWYgaXQgZG9lcyBub3QgYWR2ZXJ0aXNlIHRoZSBmZWF0dXJlIGJ1dCBpcyBvbiB0
aGUgbGlzdCB3YXJuIHRoZSANCnVzZXIgdGhhdCB0aGUgc2VydmVyIG1heSBub3QgaGF2ZSB0aGUg
YWJpbGl0eS4gSWYgaXQgbmVpdGhlciBpcyBvbiB0aGUgDQpsaXN0IG5vciBhZHZlcnRpc2UgdGhl
IGZlYXR1cmUgYXNrIHRoZSB1c2VyIGlmIHRoZXkgd2FudCB0byBzZW5kIHRoZSANCmVtYWlsIHdp
dGhvdXQgc2VsZi1kZXN0cnVjdGlvbiBlbmFibGVkLjwvaT48L2Rpdj48L2Rpdj48ZGl2PjxiciAv
PjwvZGl2PjxkaXY+VGhpcyBzZWVtcyB0byB3b3JrIGZvciBtZS4gQW55IHByb2JsZW1zIHdoaWNo
IGNvdWxkIGNvbWUgdXAgd2l0aCBoYXZpbmcgYSBjZW50cmFsIGF1dGhvcml0eSBmb3IgdGhpcyBm
ZWF0dXJlPzxiciAvPjxiciAvPjwvZGl2PjxkaXY+My4pIFdlIG1heSBoYXZlIHRvIGFzc3VtZSB0
aGF0IHRoZSBzZW5kZXIgYW5kIHJlY2VpdmVyIG9mIHRoZSBtYWlsIGFyZSB0cnVzdGVkOyB0aGlz
IHdvdWxkIG1lYW4gdGhhdCB0aGUgbWFpbCBtYXkgaGF2ZSB0byBiZSBlbmNyeXB0ZWQgcHJpb3Ig
dG8gc2VuZGluZzo8YnIgLz48YnIgLz4gPGk+RW5jcnlwdGlvbiB3b3VsZCBhbGxvdyB5b3UgdG8g
ZXN0YWJsaXNoIGEgbGV2ZWwgb2YgdHJ1c3Qgd2l0aCB0aGUgcmVjaXBpZW50LiBJLmUuIHlvdSBl
bmNyeXB0IHRoZSBtZXNzYWdlIGFuZCBtYXJrIGl0IGZvciDigJhzZWxmIGRlc3RydWN04oCZLg0K
IFlvdSB0aGVuIGhhdmUgdG8gdHJ1c3QgdGhlIHJlY2lwaWVudCB0byBkZXN0cm95IGl0IChidXQg
YXQgbGVhc3QgeW91IA0KZG9u4oCZdCBoYXZlIHRvIHRydXN0IGV2ZXJ5IHNlcnZlciBhbG9uZyB0
aGUgd2F5KS4gVGhpcyBnaXZlcyB5b3Ugc29tZSANCmxldmVsIG9mIHJlYXNzdXJhbmNlIHRoYXQg
dGhlIG1lc3NhZ2Ugd2lsbCBiZSBkZXN0cm95ZWQsIGFzc3VtaW5nIHRoZSByZWNpcGllbnQgaXMg
dHJ1c3R3b3J0aHkgKGFuZCBydW5zIHRydXN0d29ydGh5IGNsaWVudHMpLjwvaT48L2Rpdj48ZGl2
PjxiciAvPjwvZGl2PjxkaXY+NC4pIEEgcmVhbGx5IGJvaWxlZCBkb3duIHZlcnNpb24gb2YgZXBo
ZW1lcmFsIG1haWxzIGNvdWxkIGp1c3QgbWFyayB0aGUgbWFpbCAmIzM0O291dGRhdGVkJiMzNDsg
aWYgdGhlIGluZm9ybWF0aW9uIHByb3ZpZGVkIGluIHRoZSBtYWlsIGlzIG5vdCBleHBlY3RlZCB0
byBob2xkIGdvb2QgYWZ0ZXIgc29tZSB0aW1lLCBpbnN0ZWFkIG9mIGFjdHVhbGx5IGV4cHVuZ2lu
ZyB0aGUgbWFpbC48YnIgLz48YnIgLz4gPGk+d2h5IG5vdCB0cnkgdG8gYWNjb21tb2RhdGUgYm90
aCByZWFsaXR5cyBhbmQgZGVmaW5lIGEgZmVhdHVyZSB3aGljaCBpcyBjYWxsZWQgJiMzNDtJbnZh
bGlkYXRpb24gb2YgTWVzc2FnZXMmIzM0OyBvciBzaW1pbGFyIGluc3RlYWQgb2YgJiMzNDtEZXN0
cnVjdGlibGXCoA0KTWVzc2FnZXMmIzM0Oy4gVGhlIGdvYWwgb2YgdGhpcyBmZWF0dXJlIHNob3Vs
ZCBiZSB0byBtYXJrIG1lc3NhZ2VzIGluIGEgd2F5LDxiciAvPg0KdGhhdCB0aGUgY2xpZW50IHNv
bWVob3cgY2FuIG1hcmsgdGhlIG1lc3NhZ2UgYXMgJiMzNDtub3QgYmVpbmcgcmVsZXZhbnQgYW55
bW9yZSYjMzQ7IG9yIHNvbWV0aGluZyBsaWtlIHRoYXQuIFNvIGl0IGNvdWxkIHN0aWxsIGJlIGRp
c3BsYXllZCBidXQ8YnIgLz4NCmdyYXllZCBvdXQgZm9yIGV4YW1wbGUgdGVsbGluZyB0aGUgcmVj
ZWl2ZXIgdGhhdCB0aGUgbWVzc2FnZSBjYW4gYmUgaWdub3JlZC4gQWRkaXRpb25hbGx5IHRoZXJl
IGNvdWxkIHRoZW4gYmUgYWRkZWQgYW4gYXR0cmlidXRlICYjMzQ7ZGVsZXRpb25yZXF1ZXN0JiMz
NDsgd2hpY2ggY2FuIGJlIHNldCBmb3IgY2xpZW50cyB3aGljaCByZWFsbHkgd2FudCB0byBoYXZl
IGRlc3RydWN0aWJsZSBtZXNzYWdlcyBsaWtlIFNpZ25hbCBkb2VzLjwvaT48L2Rpdj48ZGl2Pjxi
ciAvPjwvZGl2PjxkaXY+QW55IHRob3VnaHRzPzxiciAvPjwvZGl2PjxkaXY+PGJyIC8+LS0gPGJy
IC8+PGRpdj48ZGl2IGRpcj0ibHRyIj48ZGl2PjxiciAvPjwvZGl2PlJlZ2FyZHMsPGRpdj5WYWli
aGF2IFNpbmdoPC9kaXY+PC9kaXY+PC9kaXY+DQo8L2Rpdj48L2Rpdj4NCjwvYmxvY2txdW90ZT48
L2Rpdj48YnI+PC9kaXY+



From nobody Wed Aug 16 10:48:24 2017
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98AEC126CB6 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 10:48: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, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XY53QawBx8VH for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 10:48:21 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 255EB1200F3 for <ietf@ietf.org>; Wed, 16 Aug 2017 10:48:21 -0700 (PDT)
Received: from webmail.nominum.com (sjc1-exch01.win.nominum.com [64.89.235.83]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 734E67400D9; Wed, 16 Aug 2017 17:47:50 +0000 (UTC)
Received: from cavall.ether.lede.home (73.167.64.188) by SJC1-EXCH01.WIN.NOMINUM.COM (64.89.235.83) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1034.26; Wed, 16 Aug 2017 10:47:47 -0700
From: Ted Lemon <ted.lemon@nominum.com>
Message-ID: <588021C8-31DF-4B02-8661-F9433A1F52D5@nominum.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F3AF2D55-6A98-4596-97C7-27DBED896864"
MIME-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [homenet] Last Call: <draft-ietf-homenet-dot-12.txt> (Special Use Domain 'home.arpa.') to Proposed Standard
Date: Wed, 16 Aug 2017 13:47:48 -0400
In-Reply-To: <6.2.5.6.2.20170816081250.05720b30@elandnews.com>
CC: <ietf@ietf.org>
To: S Moonesamy <sm+ietf@elandsys.com>
References: <150246097710.24498.9883419791827623506.idtracker@ietfa.amsl.com> <6.2.5.6.2.20170816081250.05720b30@elandnews.com>
X-Mailer: Apple Mail (2.3273)
X-Originating-IP: [73.167.64.188]
X-ClientProxiedBy: SJC1-EXCH02.WIN.NOMINUM.COM (64.89.235.69) To SJC1-EXCH01.WIN.NOMINUM.COM (64.89.235.83)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NcvXUNFUVd0pMz03AG5n7AAD5Cs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 17:48:22 -0000

--Apple-Mail=_F3AF2D55-6A98-4596-97C7-27DBED896864
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

El 16 ag 2017, a les 13:10, S Moonesamy <sm+ietf@elandsys.com> va =
escriure:
> In Section 4:
>=20
>  "So for example a query for the NS record for 'home.arpa.'  MUST
>   NOT result in that query being forwarded to an upstream cache nor
>   to the authoritative DNS server for '.arpa.'."
>=20
> As the sentence provides an example, the usage of the RFC 2119 keyword =
is incorrect.  The "MUST result in whatever queries are necessary" seems =
like specifying by example.

I believe the text is correct.   A query for the NS record is required =
not to be forwarded by recursive resolvers.   There is actually a =
mistake in the previous paragraph, though=E2=80=94"caching resolvers" =
should be recursive resolvers.

Anyway, can you explain why you think the text is wrong?   Did it not =
make clear that queries were not to be forwarded, or is there something =
I'm missing where it contradicts itself?


--Apple-Mail=_F3AF2D55-6A98-4596-97C7-27DBED896864
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">El 16 ag 2017, a les 13:10, S Moonesamy &lt;<a =
href=3D"mailto:sm+ietf@elandsys.com" =
class=3D"">sm+ietf@elandsys.com</a>&gt; va escriure:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">In Section 4:</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><br style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">&nbsp;"So for example a query for the NS =
record for 'home.arpa.' &nbsp;MUST</span><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">&nbsp;&nbsp;NOT =
result in that query being forwarded to an upstream cache nor</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">&nbsp;&nbsp;to the authoritative DNS server for =
'.arpa.'."</span><br style=3D"font-family: Menlo-Regular; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">As the sentence =
provides an example, the usage of the RFC 2119 keyword is incorrect. =
&nbsp;The "MUST result in whatever queries are necessary" seems like =
specifying by example.</span></div></blockquote></div><br class=3D""><div =
class=3D"">I believe the text is correct. &nbsp; A query for the NS =
record is required not to be forwarded by recursive resolvers. &nbsp; =
There is actually a mistake in the previous paragraph, though=E2=80=94"cac=
hing resolvers" should be recursive resolvers.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Anyway, can you explain why you think =
the text is wrong? &nbsp; Did it not make clear that queries were not to =
be forwarded, or is there something I'm missing where it contradicts =
itself?</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_F3AF2D55-6A98-4596-97C7-27DBED896864--


From nobody Wed Aug 16 11:05:42 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D72D13235B for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 11:05: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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NlvtyulOASuQ for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 11:05:39 -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 7BC8513237B for <ietf@ietf.org>; Wed, 16 Aug 2017 11:05:39 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1di2hG-000GmG-7p; Wed, 16 Aug 2017 14:05:38 -0400
Date: Wed, 16 Aug 2017 14:05:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Hardie <ted.ietf@gmail.com>, vaibhav singh <vaibhavsinghacads@gmail.com>
cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: Re: Scope for self-destructing email?
Message-ID: <FE2E639B0F0F8D272F1339E2@PSB>
In-Reply-To: <CA+9kkMAAQh64M59g0Jn=2j0czS6q56-yoOadGMoeVMTZ=4Z72Q@mail.gmail.com>
References: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com> <b1289123-04ac-e62b-879e-614fae9b20b0@bogus.com> <CACZ1GiooBdEZ_YcBZPQNFkbT0DsGf-Cu25fPYzWcLamLUAH+TA@mail.gmail.com> <CA+9kkMAAQh64M59g0Jn=2j0czS6q56-yoOadGMoeVMTZ=4Z72Q@mail.gmail.c om>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ItmTeYWC2zmoyAYrFRyIAcIo7pY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 18:05:41 -0000

--On Wednesday, August 16, 2017 09:49 -0700 Ted Hardie
<ted.ietf@gmail.com> wrote:


> On Tue, Aug 15, 2017 at 9:50 PM, vaibhav singh
> <vaibhavsinghacads@gmail.com> wrote:
>...
>> *why not try to accommodate both realitys and define a
>> feature which is called "Invalidation of Messages" or similar
>> instead of "Destructible Messages". The goal of this feature
>> should be to mark messages in a way, that the client somehow
>> can mark the message as "not being relevant anymore" or
>> something like that.
>...

> I think there are two potential lines of development here,
> though I confess I am skeptical of the value of either.

> The first is providing a facility that declares a particular
> message to be automatically overcome by events at a particular
> time, leaving it completely up to the recipient how to process
> the message based on that metadata.  There are simple message
> types (today's weather, lunch availability, etc.) that could
> be thus set to be marked OBE when no longer relevant.  Some
> clients might choose to auto-delete them or auto-archive them
> when the time is reached, but this would be because of their
> preferred handling and not a guarantee to the sender that the
> sender's intent is being honored.  A message header like
> OBE-At: could be registered provisionally without much hassle,
> and you could see if it saw implementation and use.

Ted,

Do you consider the above significantly different from the
X.400-derived Expiry-Date (RFC 1327) or Expires (RFC 2156)?
While both are identified as obsolete in RFC 4021 and the IANA
Message Header registry, they provide a date and leave it up to
the recipient how those metadata are processed.

While RFC 1327 and 2156 primarily define those fields by
reference to X.400 (1988 and 1992), my recollection of the
CCITT/ISO documents is that the expiration date-time is defined
in a way that is quite consistent with "Invalidation of
Messages" as described above, with the receiving system free to
warn about obsolescence or even to discard copies.

While I don't think it has much of a future --for reasons that
many of us have given and that I assume are consistent with your
skepticism -- I'd like to propose what I think would be a far
more constructive approach for Vaibhav and colleagues than
continued iterations on the IETF list:  They could write an I-D
in the form of an Experimental document that would actually pin
down what they are proposing.  That I-D could propose changing
the "obsolete" status for "Expires" in the registry to something
more active if the experiment succeeds, eliminating the need for
any IANA or Expert action at this point and potentially taking
advantage of any MUAs or MTAs that haven't bothered to get rid
of support for those old headers.   Then, with the feature and
any needed protocol bits specified, they see if they can get any
real traction.  Under more usual circumstances, we'd publish an
experimental spec without implementations and demonstration of
usefulness and usability, but, since "Expires" was implemented
and deployed in the past, after which the IETF decided it was
obsolete, it seems to me that pursuing this further should
require proof of utility and/or a clear explanation of why this
time is different.

best,
    john



From nobody Wed Aug 16 11:07:07 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E25213239A for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 11:07: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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=opendkim.org header.b=TmNQ3szB; dkim=pass (1024-bit key) header.d=elandsys.com header.b=1/Qg5j5N
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H290JAIv4_JT for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 11:07:04 -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 24A8F13237B for <ietf@ietf.org>; Wed, 16 Aug 2017 11:07:04 -0700 (PDT)
Received: from sm-THINK.elandsys.com ([12.217.29.81]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v7GI6vun008590 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Aug 2017 11:07:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1502906823; x=1502993223; bh=jV++75uj9hoaQoneyzE82ER0IpBHlJtOHiDgOFXJRnE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=TmNQ3szBIxhSEWF+uoV54zD4vBUW96yEXZRishVjrx+nQPkrHseINGtsuLz1AJiTr ZtDscTuWbvR4q4uKks27j5F83ZUeBQ3C3ivcZ5yqKWcvrAaOWj07aildWlipuipMlK yqxkjiYds0ILCrowfDmq7Sq44qMFMUcj0HjPODLg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1502906823; x=1502993223; i=@elandsys.com; bh=jV++75uj9hoaQoneyzE82ER0IpBHlJtOHiDgOFXJRnE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1/Qg5j5NRfoo2cwYSNzEXsU/lUu8sSDQt0gm5t5NuyhLVsn1tEzojvdPErQE2EgL4 mhJCZStyTOoVi6HjtoM/p7gz+n3MLFxHaXw1jzqXQcFJTLLYdQ3A6eLSuybw+HijDS Btkj30+plxIevQryHXYeZYWuwUMWVU8T9WqJ3L7Y=
Message-Id: <6.2.5.6.2.20170816105747.0d9d6e90@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 16 Aug 2017 11:06:34 -0700
To: Ted Lemon <ted.lemon@nominum.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [homenet] Last Call: <draft-ietf-homenet-dot-12.txt> (Special Use Domain 'home.arpa.') to Proposed Standard
Cc: ietf@ietf.org
In-Reply-To: <588021C8-31DF-4B02-8661-F9433A1F52D5@nominum.com>
References: <150246097710.24498.9883419791827623506.idtracker@ietfa.amsl.com> <6.2.5.6.2.20170816081250.05720b30@elandnews.com> <588021C8-31DF-4B02-8661-F9433A1F52D5@nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/N49ZMsfyxkF3urgiXF33i_0Ea08>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 18:07:06 -0000

Hi Ted,
At 10:47 AM 8/16/2017, Ted Lemon wrote:
>I believe the text is correct.   A query for the=20
>NS record is required not to be forwarded by=20
>recursive resolvers.   There is actually a=20
>mistake in the previous paragraph,=20
>though=97"cacching resolvers" should be recursive resolvers.
>
>Anyway, can you explain why you think the text=20
>is wrong?   Did it not make clear that queries=20
>were not to be forwarded, or is there something=20
>I'm missing where it contradicts itself?

In Section 4, second paragraph in Item 4, there=20
is a requirement not to forward with one=20
exception, "a query for a DS record when the DO=20
bit".  The next paragraph then goes on to provide=20
an example of a query and states the requirement=20
again.  It is not about whether the text does not=20
make it clear or that there is a contradiction;=20
it would be better to drop the "MUST" in that=20
(third) paragraph as it is a restatement of the=20
requirement in the second paragraph.

Regards,
S. Moonesamy=20


From nobody Wed Aug 16 11:11:04 2017
Return-Path: <moritz30@moritz30.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34399132357 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 11:11:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.979
X-Spam-Level: **
X-Spam-Status: No, score=2.979 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.723, MISSING_MIMEOLE=1.899, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pXmo72G7BOtl for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 11:11:01 -0700 (PDT)
Received: from sender-of-o52.zoho.com (sender-of-o52.zoho.com [135.84.80.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7C99132143 for <ietf@ietf.org>; Wed, 16 Aug 2017 11:11:01 -0700 (PDT)
Received: from [192.168.137.101] (p5DC6529D.dip0.t-ipconnect.de [93.198.82.157]) by mx.zohomail.com with SMTPS id 1502907056872835.6257094815678; Wed, 16 Aug 2017 11:10:56 -0700 (PDT)
Date: Wed, 16 Aug 2017 20:10:35 +0200
Subject: Re: Scope for self-destructing email?
Message-ID: <4c4a0d3a-352b-4be0-8163-f581e5d4d549@email.android.com>
X-Android-Message-ID: <4c4a0d3a-352b-4be0-8163-f581e5d4d549@email.android.com>
In-Reply-To: <FE2E639B0F0F8D272F1339E2@PSB>
From: Matthias Merkel <moritz30@moritz30.de>
To: John C Klensin <john-ietf@jck.com>
Cc: Ted Hardie <ted.ietf@gmail.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>, vaibhav singh <vaibhavsinghacads@gmail.com>
Importance: Normal
X-Priority: 3
X-MSMail-Priority: Normal
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64
X-ZohoMailClient: External
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LSiqalrBk0vB8ljAoAx9fODo2uc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 18:11:03 -0000

PGRpdiBkaXI9J2F1dG8nPlRoZSBkaWZmZXJlbmNlIHNlZW1zIHRvIGJlIHRoYXQgRXhwaXJlcyBp
cyBhIHByZS1zZXQgZW1haWwgaGVhZGVyLiBUaGUgY29tbWFuZCBmb3IgdGhpcyBjYW4gYmUgc2Vu
dCBhZnRlciB0aGUgZW1haWwgd2FzIGFscmVhZHkgc2VudC48L2Rpdj4=



From nobody Wed Aug 16 11:20:42 2017
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 362081200F3 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 11:20: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, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yvwKevyk1O90 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 11:20:35 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 B8DC313239A for <ietf@ietf.org>; Wed, 16 Aug 2017 11:20:35 -0700 (PDT)
Received: from webmail.nominum.com (unknown [IPv6:2620:0:b60:fab4:1026:2045:f02a:5f75]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 646897400D9; Wed, 16 Aug 2017 18:20:05 +0000 (UTC)
Received: from cavall.ether.lede.home (73.167.64.188) by SJC1-EXCH01.WIN.NOMINUM.COM (64.89.235.83) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1034.26; Wed, 16 Aug 2017 11:20:02 -0700
From: Ted Lemon <ted.lemon@nominum.com>
Message-ID: <9FAC0BEA-D87A-4987-98DD-0B44E3E02C76@nominum.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_29377A34-D700-4EF3-8AEE-298CDF79FF79"
MIME-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [homenet] Last Call: <draft-ietf-homenet-dot-12.txt> (Special Use Domain 'home.arpa.') to Proposed Standard
Date: Wed, 16 Aug 2017 14:20:03 -0400
In-Reply-To: <6.2.5.6.2.20170816105747.0d9d6e90@elandnews.com>
CC: <ietf@ietf.org>
To: S Moonesamy <sm+ietf@elandsys.com>
References: <150246097710.24498.9883419791827623506.idtracker@ietfa.amsl.com> <6.2.5.6.2.20170816081250.05720b30@elandnews.com> <588021C8-31DF-4B02-8661-F9433A1F52D5@nominum.com> <6.2.5.6.2.20170816105747.0d9d6e90@elandnews.com>
X-Mailer: Apple Mail (2.3273)
X-Originating-IP: [73.167.64.188]
X-ClientProxiedBy: SJC1-EXCH02.WIN.NOMINUM.COM (64.89.235.69) To SJC1-EXCH01.WIN.NOMINUM.COM (64.89.235.83)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kurpVolCR4qwhcNS-YQOgSJlOIo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 18:20:41 -0000

--Apple-Mail=_29377A34-D700-4EF3-8AEE-298CDF79FF79
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"

El 16 ag 2017, a les 14:06, S Moonesamy <sm+ietf@elandsys.com> va =
escriure:
> In Section 4, second paragraph in Item 4, there is a requirement not =
to forward with one exception, "a query for a DS record when the DO =
bit".  The next paragraph then goes on to provide an example of a query =
and states the requirement again.  It is not about whether the text does =
not make it clear or that there is a contradiction; it would be better =
to drop the "MUST" in that (third) paragraph as it is a restatement of =
the requirement in the second paragraph.

Ah.   While I have sympathy for the motivation to be parsimonious with =
normative language, I don't see a clean way to fix this.   If the ADs =
consider it important, perhaps they will suggest text.


--Apple-Mail=_29377A34-D700-4EF3-8AEE-298CDF79FF79
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;" =
class=3D"">El 16 ag 2017, a les 14:06, S Moonesamy &lt;<a =
href=3D"mailto:sm+ietf@elandsys.com" =
class=3D"">sm+ietf@elandsys.com</a>&gt; va escriure:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">In Section 4, second paragraph in Item 4, =
there is a requirement not to forward with one exception, "a query for a =
DS record when the DO bit". &nbsp;The next paragraph then goes on to =
provide an example of a query and states the requirement again. &nbsp;It =
is not about whether the text does not make it clear or that there is a =
contradiction; it would be better to drop the "MUST" in that (third) =
paragraph as it is a restatement of the requirement in the second =
paragraph.</span><br style=3D"font-family: Menlo-Regular; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""></div></blockquote></div><br =
class=3D""><div class=3D"">Ah. &nbsp; While I have sympathy for the =
motivation to be parsimonious with normative language, I don't see a =
clean way to fix this. &nbsp; If the ADs consider it important, perhaps =
they will suggest text.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_29377A34-D700-4EF3-8AEE-298CDF79FF79--


From nobody Wed Aug 16 11:44:14 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61E42132396 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 11:44:12 -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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HdphidI51L8e for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 11:44:09 -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 C5524126B6E for <ietf@ietf.org>; Wed, 16 Aug 2017 11:44:09 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1di3IU-000GpU-I2; Wed, 16 Aug 2017 14:44:06 -0400
Date: Wed, 16 Aug 2017 14:43:59 -0400
From: John C Klensin <john-ietf@jck.com>
To: Matthias Merkel <moritz30@moritz30.de>
cc: Ted Hardie <ted.ietf@gmail.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>, vaibhav singh <vaibhavsinghacads@gmail.com>
Subject: Re: Scope for self-destructing email?
Message-ID: <B51EC6138C87451D02AB6B53@PSB>
In-Reply-To: <4c4a0d3a-352b-4be0-8163-f581e5d4d549@email.android.com>
References: <4c4a0d3a-352b-4be0-8163-f581e5d4d549@email.android.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JT9dNfGssdAm6SbyCCWcyHDeayw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 18:44:12 -0000

--On Wednesday, August 16, 2017 20:10 +0200 Matthias Merkel
<moritz30@moritz30.de> wrote:

> The difference seems to be that Expires is a pre-set email
> header. The command for this can be sent after the email was
> already sent.

But, if an MUA is going to process it, which is implied by
"Invalidation of Messages... mark messages in a way, that the
client somehow can mark the message as "not being relevant
anymore"..., then it needs to make it into the headers of the
message that is seen by the receiving MUA.  Probably we have
enough mechanisms in message management protocols to signal the
delivery MTA or message store to insert that header field.
While I think any of us could devise some new mechanism that
would not require new header fields, such a mechanism would
imply inventing and deploying more machinery and make adoption
of this mechanism even less likely.

But I think the above (both your comment and my response)
demonstrate my main point -- it is time to get to an I-D that
specifies the details rather than continuing an on-list
discussion that is mostly about generalities (as a striking
example, note "...or something like that) and which each of us
is hearing a little differently as to what are, and are not, key
elements of the proposal.

best,
    john





From nobody Wed Aug 16 11:50:41 2017
Return-Path: <vaibhavsinghacads@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 508BF1321CB for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 11:50:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NB7oWpYAdNKl for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 11:50:37 -0700 (PDT)
Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26B0E1321B9 for <ietf@ietf.org>; Wed, 16 Aug 2017 11:50:37 -0700 (PDT)
Received: by mail-it0-x22c.google.com with SMTP id 77so21639041itj.1 for <ietf@ietf.org>; Wed, 16 Aug 2017 11:50:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=X8WYfCV5+FK06WbNYO4uloJ3jHFqZhG9qRs9aMPHCbA=; b=BtxPH8Q3qQ39Kk9LdkBku71OLRv8uhUsSYQ6jPFR7Z0dHlAi/aw/oyujWAqulydDYv 0dTP0Y4nPS/2FgeSHpLEKCfiU2tNoLja+Cqtl1f3OAs298g7qpz9Rp8Fr7L3iqkqHitl /HIcU+TYs9hTd0cI7GF5CUkpE9cc9/muvf09wpgcNjsYnDg+suBSXNbFt1aB04kPSctv UBXIOuY9CtB3/3SAM999d1OKBicN/IyFGtktH+bIZdyibq1rmLJ/n5St7OuQAKmH5hzj QZcIGZudQnFXSCgdZxciZqwyjlAsFqtYXWdWLcFutTkjH1OXsTf4Bz15wm7XNAnjnuIv 1ZVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=X8WYfCV5+FK06WbNYO4uloJ3jHFqZhG9qRs9aMPHCbA=; b=NUL0mUlwZAnkWMjIIKJIDqJEb5roFkud9yjekS8SidSNnsxExduQAYDzNjO49Ed86S /Wx3u9Lkr0KA3ySOSDC8fvBNqmRDYrJstjsoCkwCAp9xoCNFFv4CyMYSFJpEnKmPtNWP BFAhwE9wMTwi7xXsePemFDTMaG1qIs+lstAm87OBQmyxro37KL0p3Qz+mpnIpSBa2HXN gBQr/Srja+THEBoOmPFviGKNZbHLysH64yRFG8vefRv1MUIoMb/xLIvvfqriAknp3ZTI +XYiEbKJHK5iFlv2wJn61AkMjbKXdShBCpEkDFjCyUXypPeXCnD1PJg0Y3zIfYQ/wMfQ tyXw==
X-Gm-Message-State: AHYfb5hwKbZ+dzUlx/Dsq//5nR4Yi0tv1mW/kdvSTuLuvb5CqyPhMG1d GGhT+OhJaJTtjH0I0WZs8qW/Sk6g0Q==
X-Received: by 10.36.196.67 with SMTP id v64mr3049921itf.156.1502909436389; Wed, 16 Aug 2017 11:50:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.0.208 with HTTP; Wed, 16 Aug 2017 11:50:35 -0700 (PDT)
From: vaibhav singh <vaibhavsinghacads@gmail.com>
Date: Thu, 17 Aug 2017 00:20:35 +0530
Message-ID: <CACZ1GiqT6iANkgpDjh-+43pGUY0uEnPdaDnwecBj66S4igTPxA@mail.gmail.com>
Subject: How are S/MIME private keys handled across MUAs?
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c05c64615ed830556e35f6c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iFKEja5aN0ANa6EIUzob2lwRhW0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 18:50:39 -0000

--94eb2c05c64615ed830556e35f6c
Content-Type: text/plain; charset="UTF-8"

Hi,
I was looking at RFCs for S/MIME, and had a question: What if I am logged
into multiple clients(my mobile, a web application, Thunderbird) with an
email account, and I receive an encrypted email?

I can see that the encrypted email would be created with my public key,
and, assuming one public key for one email account, I will have one private
key which I will somehow make use of across all my MUAs. I could not think
of a simple way using which I will be able to sync my private key.

Is there any good way of sharing private keys across clients (maybe some
way of securely syncing files)? How do corporate clients resolve this
issue? Is there an RFC which I may have to refer to?

Another line of thinking; is it possible to create key pairs
(triplets?quadruplets?) wherein there could be multiple private keys
generated for a single public key? And, what about the other way round?

-- 

Regards,
Vaibhav Singh

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

<div dir=3D"ltr"><div><div>Hi,<br></div>I was looking at RFCs for S/MIME, a=
nd had a question: What if I am logged into multiple clients(my mobile, a w=
eb application, Thunderbird) with an email account, and I receive an encryp=
ted email?<br></div><br>I can see that the encrypted email would be created=
 with my public key, and, assuming one public key for one email account, I =
will have one private key which I will somehow make use of across all my MU=
As. I could not think of a simple way using which I will be able to sync my=
 private key.<br><br clear=3D"all"><div><div><div>Is there any good way of =
sharing private keys across clients (maybe some way of securely syncing fil=
es)? How do corporate clients resolve this issue? Is there an RFC which I m=
ay have to refer to?<br><br></div><div>Another line of thinking; is it poss=
ible to create key pairs (triplets?quadruplets?) wherein there could be mul=
tiple private keys generated for a single public key? And, what about the o=
ther way round?<br><br></div><div>-- <br><div class=3D"gmail_signature" dat=
a-smartmail=3D"gmail_signature"><div dir=3D"ltr"><div><br></div>Regards,<di=
v>Vaibhav Singh</div></div></div>
</div></div></div></div>

--94eb2c05c64615ed830556e35f6c--


From nobody Wed Aug 16 12:53:14 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 585961326D7 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 12:53:12 -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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iF1ZbW7VT_G9 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 12:53:10 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8BFC1326D6 for <ietf@ietf.org>; Wed, 16 Aug 2017 12:53:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id DB6383004DD for <ietf@ietf.org>; Wed, 16 Aug 2017 15:53:09 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id IBAefCZjx4LG for <ietf@ietf.org>; Wed, 16 Aug 2017 15:53:08 -0400 (EDT)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 7F3A1300295; Wed, 16 Aug 2017 15:53:08 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: How are S/MIME private keys handled across MUAs?
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <CACZ1GiqT6iANkgpDjh-+43pGUY0uEnPdaDnwecBj66S4igTPxA@mail.gmail.com>
Date: Wed, 16 Aug 2017 15:53:11 -0400
Cc: IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E98400E-4C80-4447-8F3E-79C086BF20E0@vigilsec.com>
References: <CACZ1GiqT6iANkgpDjh-+43pGUY0uEnPdaDnwecBj66S4igTPxA@mail.gmail.com>
To: vaibhav singh <vaibhavsinghacads@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EC4PVPUelnkAy8CgQsbU3GZ2X5w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 19:53:12 -0000

The Asymmetric Key Package (the successor to PKCS#8) as described in RFC =
5958 would be one way to securely move the private key.

Russ


> On Aug 16, 2017, at 2:50 PM, vaibhav singh =
<vaibhavsinghacads@gmail.com> wrote:
>=20
> Hi,
> I was looking at RFCs for S/MIME, and had a question: What if I am =
logged into multiple clients(my mobile, a web application, Thunderbird) =
with an email account, and I receive an encrypted email?
>=20
> I can see that the encrypted email would be created with my public =
key, and, assuming one public key for one email account, I will have one =
private key which I will somehow make use of across all my MUAs. I could =
not think of a simple way using which I will be able to sync my private =
key.
>=20
> Is there any good way of sharing private keys across clients (maybe =
some way of securely syncing files)? How do corporate clients resolve =
this issue? Is there an RFC which I may have to refer to?
>=20
> Another line of thinking; is it possible to create key pairs =
(triplets?quadruplets?) wherein there could be multiple private keys =
generated for a single public key? And, what about the other way round?
>=20
> --=20
>=20
> Regards,
> Vaibhav Singh


From nobody Wed Aug 16 13:03:05 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 278721326D9 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 13:03:04 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jts-8krPX5Es for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 13:03:02 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 949A61326D7 for <ietf@ietf.org>; Wed, 16 Aug 2017 13:03:02 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7DA96E1ED; Wed, 16 Aug 2017 16:05:41 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id DF86880B17; Wed, 16 Aug 2017 16:03:01 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Glen <glen@amsl.com>
cc: ietf@ietf.org
Subject: Re: Mailman attack in progress
In-Reply-To: <CABL0ig7M0F0WDBTA9qqkEDRt9BUBs5uVaCkmtdn3TY8Xv1ik3A@mail.gmail.com>
References: <CABL0ig7VW_eNC8qEiX0+a71if1L0FnxEJn6usssQu+1Ox5nQOQ@mail.gmail.com> <CABL0ig4UT4Ebfzdf2ce1vu-Q76Ei_A7Yk=q-fkGfDU8o2VWjeA@mail.gmail.com> <sjma832f97r.fsf@securerf.ihtfp.org> <CABL0ig7M0F0WDBTA9qqkEDRt9BUBs5uVaCkmtdn3TY8Xv1ik3A@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.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-sha256; protocol="application/pgp-signature"
Date: Wed, 16 Aug 2017 16:03:01 -0400
Message-ID: <15612.1502913781@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/a_0m-Ak6q6tchvWJ_act_IbZDRE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 20:03:04 -0000

--=-=-=
Content-Type: text/plain


Glen <glen@amsl.com> wrote:
    > So, needless to say, I am hesitant to just openly describe attack
    > countermeasures on a public list.  :-)   I'm sorry for that - I truly
    > am - because as I said *I* would want to know, too.   Although in this

Sad, but reasonable.
Perhaps the IAOC would like to organize a by-invitation-only meeting
at which the details might be related, and work to design and/or standardize
counter-measures might be discussed.

    > will all understand this.  I am preparing a summary report to the TMC
    > outlining what was done, and I need to leave it to them to determine
    > if - and how best - to present the information to interested persons.

"TMC" <- I have a cache miss on this.



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




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

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

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlmUpPUACgkQgItw+93Q
3WWuvAf/StzBAl/E6MQ+fGP0EW3AMhxDT6Qcr7SfBCdXLWLd/p9ylCAps/niUFau
X83QzRUhe6DBujxc6GjTnI/3lXOiETORjKthXbIFviPoA1axF7RIANfOrI8P4Fpl
IwNJFfe6xFHDmKLRbnh+Uz7O+aQQZCbFuc9DhHwCFdEpWPSZYWDGJ3hzS6jeNGKE
LZzGf4o/yMMrqRg4Yr/4xEvJ8rMZJQ2rUBm2+4KWIWzEpAuKQOMsS7n5sU9QCzdz
6p7GTg1sElKcZQQmhO/ouMQITEzbcuYTpeYJHkQIVzkhMAOiYYyPG4j4rLsB0UtF
C1ssnzNIbqCWN9iEYRwWenSZcvZf7w==
=E27j
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Aug 16 13:05:51 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A42571326DB for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 13:05:50 -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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id skqilJPhkXbV for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 13:05:49 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 326FA126BF3 for <ietf@ietf.org>; Wed, 16 Aug 2017 13:05:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 8F644300541 for <ietf@ietf.org>; Wed, 16 Aug 2017 16:05:48 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id rRuiRYog0o0X for <ietf@ietf.org>; Wed, 16 Aug 2017 16:05:47 -0400 (EDT)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 3E16F3002C7; Wed, 16 Aug 2017 16:05:47 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Mailman attack in progress
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <15612.1502913781@obiwan.sandelman.ca>
Date: Wed, 16 Aug 2017 16:05:46 -0400
Cc: Glen Barney <glen@amsl.com>, IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <24A4CD65-F5D5-4C7D-B9A5-68FD29CE1D90@vigilsec.com>
References: <CABL0ig7VW_eNC8qEiX0+a71if1L0FnxEJn6usssQu+1Ox5nQOQ@mail.gmail.com> <CABL0ig4UT4Ebfzdf2ce1vu-Q76Ei_A7Yk=q-fkGfDU8o2VWjeA@mail.gmail.com> <sjma832f97r.fsf@securerf.ihtfp.org> <CABL0ig7M0F0WDBTA9qqkEDRt9BUBs5uVaCkmtdn3TY8Xv1ik3A@mail.gmail.com> <15612.1502913781@obiwan.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YO1Zn5apyOWL7S77q5ii5uAtjFE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 20:05:50 -0000

Michael:

> Glen <glen@amsl.com> wrote:
>> So, needless to say, I am hesitant to just openly describe attack
>> countermeasures on a public list.  :-)   I'm sorry for that - I truly
>> am - because as I said *I* would want to know, too.   Although in =
this
>=20
> Sad, but reasonable.
> Perhaps the IAOC would like to organize a by-invitation-only meeting
> at which the details might be related, and work to design and/or =
standardize
> counter-measures might be discussed.
>=20
>> will all understand this.  I am preparing a summary report to the TMC
>> outlining what was done, and I need to leave it to them to determine
>> if - and how best - to present the information to interested persons.
>=20
> "TMC" <- I have a cache miss on this.

The TMC is the Technology Management Committee of the IAOC.
See https://iaoc.ietf.org/committees.html#TMC

Russ


From nobody Wed Aug 16 15:57:05 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A4C01323A4 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 15:57:03 -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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hCVDfqN1yxey for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 15:57:01 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3220613235C for <ietf@ietf.org>; Wed, 16 Aug 2017 15:57:00 -0700 (PDT)
Received: (qmail 34124 invoked from network); 16 Aug 2017 22:56:59 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 16 Aug 2017 22:56:59 -0000
Date: 16 Aug 2017 22:56:37 -0000
Message-ID: <20170816225637.4431.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Cc: vaibhavsinghacads@gmail.com
Subject: Re: Scope for self-destructing email?
In-Reply-To: <CACZ1GiooBdEZ_YcBZPQNFkbT0DsGf-Cu25fPYzWcLamLUAH+TA@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ROsgf6KDSeDytaNjpL-L50N_Jcw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Aug 2017 22:57:03 -0000

In article <CACZ1GiooBdEZ_YcBZPQNFkbT0DsGf-Cu25fPYzWcLamLUAH+TA@mail.gmail.com> you write:
>This seems to work for me. Any problems which could come up with having a
>central authority for this feature?

Many.  What if I tell the central authority that I implement
self-destructive e-mail but I'm lying?  How could the central
authority tell?  I'm pretty sure I can pass whatever audits they make
since they have no way to tell what data I'm hiding in places they
can't see.

>4.) A really boiled down version of ephemeral mails could just mark the
>mail "outdated" if the information provided in the mail is not expected to
>hold good after some time, instead of actually expunging the mail.

As others have said, that feature has come and gone many times in the past.  In
netnews, which is similar in some ways to mail, there's an Expires: header which
works reasonably well, typically used to mark messages that stop being interesting
after some point like weather forecasts or event reminders.  There's no guarantee
that anyone will follow the advice, and you certainly can't use it to force stuff
to disappear, but it's been occasionally useful.

R's,
John


From nobody Wed Aug 16 17:44:19 2017
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB3871323B8 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 17:44:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AxYqzNqI-k8m for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 17:44:12 -0700 (PDT)
Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28CA1132386 for <ietf@ietf.org>; Wed, 16 Aug 2017 17:44:12 -0700 (PDT)
Received: by mail-wr0-x233.google.com with SMTP id z91so20430374wrc.4 for <ietf@ietf.org>; Wed, 16 Aug 2017 17:44:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=F6b1ncl0/sRbFlWxJy5+VJZr6KSc96GQbfw5eXfVJ5Y=; b=NLL5hZsk7Kdu7vTB1i5sZ355sZO8saz55J/J0ubg4/1lMLvlT74OHhsoaOIllVMCGe CaKSLmsfgDRvxla5ZXu8yoU0AxfCYVNcTE614daTPYa4uyGY4QJdxZmJNXjSAD14XP70 GZAOf6Y2PZEF0GUr12UkTvMrvLGSIBkC82Axd2hsX8t61DsqMPjVZ7n5FIPIIYT6KyQZ 3JSTkyLAfGzRHacAk0DX48qFo7rjcjMWO5LGN9RE56NbpSoX4rl/ZcjfdqSHaXSbQOOu 7fnn/hVnxQHcXgnkfnTSsj9+FD4LM1nnlXOpYzdmW60Jp5wiCPmsjFQN0aGwTSCYIfnF 6hgw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=F6b1ncl0/sRbFlWxJy5+VJZr6KSc96GQbfw5eXfVJ5Y=; b=Zn4yWabdYjW8Qks9SdwT8qyrYXzrrnptbModHICNakoSHaiAF3TQKdgnc1Y8rglPG4 VMxJXNKGiyxdgbCzN9LmmBTbAGtFoPnpRI/3DoQt1Gux6aAWkVIq2yktY18BhRnx97SM V/Gk6av7EytLykOLSm5vs3+5Xcf1O2NiAwDVlP/gkb88WvLbZcv1j4UKyS9xcNV+izgy enU0TRbXFRc/E7WjH8Jfa1umgQ1Tc2/qYInhVk/fSM3cQ3wJx2ob1Aqca5XERvfcd7S1 jMN7vDuC3FEZpP51HVsZNKNgGodUZNrvPeiH7hEjXod/pxua5QsPvJPHPtd1rEfjly7o mEGg==
X-Gm-Message-State: AHYfb5h4f1HL2ro2P8U4q3vGCkWNFleLAsZr4UAveY46YwYuKei29t61 tBx4VyIUjJ8M1uK6cqvRFrCm5S0X/FYN
X-Received: by 10.223.184.50 with SMTP id h47mr2234080wrf.163.1502930650630; Wed, 16 Aug 2017 17:44:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.164.135 with HTTP; Wed, 16 Aug 2017 17:43:29 -0700 (PDT)
In-Reply-To: <20170816225637.4431.qmail@ary.lan>
References: <CACZ1GiooBdEZ_YcBZPQNFkbT0DsGf-Cu25fPYzWcLamLUAH+TA@mail.gmail.com> <20170816225637.4431.qmail@ary.lan>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 16 Aug 2017 20:43:29 -0400
Message-ID: <CAHw9_iJdp2OCM8Otmj+bqZLp6QMGep6K+0+TnudSsmUCEfW1_Q@mail.gmail.com>
Subject: Re: Scope for self-destructing email?
To: John Levine <johnl@taugh.com>
Cc: IETF Discuss <ietf@ietf.org>, vaibhav singh <vaibhavsinghacads@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VMgGFPacJbIOwm6wBMyoij4FDDA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Aug 2017 00:44:15 -0000

On Wed, Aug 16, 2017 at 6:56 PM, John Levine <johnl@taugh.com> wrote:
> In article <CACZ1GiooBdEZ_YcBZPQNFkbT0DsGf-Cu25fPYzWcLamLUAH+TA@mail.gmail.com> you write:
>>This seems to work for me. Any problems which could come up with having a
>>central authority for this feature?
>
> Many.  What if I tell the central authority that I implement
> self-destructive e-mail but I'm lying?  How could the central
> authority tell?  I'm pretty sure I can pass whatever audits they make
> since they have no way to tell what data I'm hiding in places they
> can't see.
>

I suspect that one of my previous responses here might have been both
too subtle, and also quite likely to have been ignored as spam.
All of these sorts of solutions will always be subject to the issue
that you don't control the recipient system -- there is noting (well,
very little) that stops the recipient from taking a screen capture of
the message as it is displayed, or even whipping out their smartphone
and taking a picture of the screen.
See: http://www.owl-stretching-time.com/because-you-dont-contol-the-recipient.png
There is nothing that the sender can include which will make a image
of the message go "Boom" later.


>>4.) A really boiled down version of ephemeral mails could just mark the
>>mail "outdated" if the information provided in the mail is not expected to
>>hold good after some time, instead of actually expunging the mail.
>
> As others have said, that feature has come and gone many times in the past.  In
> netnews, which is similar in some ways to mail, there's an Expires: header which
> works reasonably well, typically used to mark messages that stop being interesting
> after some point like weather forecasts or event reminders.  There's no guarantee
> that anyone will follow the advice, and you certainly can't use it to force stuff
> to disappear, but it's been occasionally useful.

Yup - I think that an advisory note (Expire:) saying "This mail might
not be relevant anymore (it was an invitation to a party last week)"
has some (limited) value, but a: relying on something like this to
actually expunge information is unworkable and b: rude. I might want
to search my mail to see what the weather forecast said last Thursday,
or search event reminders to know where I was last Tuesday. Once
you've sent me the mail, it's mine!

W

>
> R's,
> John
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Wed Aug 16 17:58:47 2017
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 972A91323C0 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 17:58:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VZZvOit4gxQt for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 17:58:43 -0700 (PDT)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D70B712EC06 for <ietf@ietf.org>; Wed, 16 Aug 2017 17:58:42 -0700 (PDT)
Received: by mail-qt0-x236.google.com with SMTP id s6so30256211qtc.1 for <ietf@ietf.org>; Wed, 16 Aug 2017 17:58:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=dZoFNPGRplgttetF3FpK2T9cgyRPe55GfqxWaxqErig=; b=L/SBA3zKba8EqqlgUwl3N3NWEEm2itZkfHhdgKvlhApF7hGVbpG0sP6dqqPmKGJ4/e iFrngMDuv14XMtGX/hUeudScv+/m3T4Bo/iFUdiT7xTlrwwtwHdgthfI7gyro4+DodAL YdyvdOtz1B85go/b7yDMZLYT5FVgsi2JQQW4iyLx1uxKZy4ZsPPgCUznfJtuHvAR+bnw TAIv50R8isys2da+byZPbJEnismP7JL5RzvMVEasKuY4BfncRrl/mqZKFjcb3wAQvSy9 FjKudFTL0wlL5zJiQD5h2g3EbbirM3G2+yT6pTLO6b0gDhJrS+isrzEaUUjWq4v2KKah 16/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=dZoFNPGRplgttetF3FpK2T9cgyRPe55GfqxWaxqErig=; b=NFatsxwINQygmZGVli+dW9SUWIcDKQtNQZa7vhbC7OXW1BUGPBHr89v6g3X+0sSk7O EoKjyq44bwwtQx1F12/Q7GLtfldJkmvdrnLOtkUlT3czh7uP+wXTCMBIf0Nv/2dsBZd4 Q9FXVIxmzBWoZPpq+ceis1PPLRvNKFKvRLI5sGMQVXtaYCw/zlvFK37ZQ9t//gmQVp+v nyyqemSNW+6I1kmgbp+799t5KMptxKuiUhb8DOHDVHwLJVHXu/DxJ1RIV3X/8ovM00rf 5sQ5v2gE/MKrSJqJMKdvMGki7IN5b3HJb/MrWoYJy3YVw1IkV5riqmMnKTpKnzeELCNR zJ0Q==
X-Gm-Message-State: AHYfb5gylEEY789YKzQIb1bj2fpjyzScEt/+B+uDr33+T6FcZQF4XYFx 7VLlVNMyqCwFvP5qi0Ix2PIzh8fv6g==
X-Received: by 10.237.53.172 with SMTP id c41mr5284273qte.33.1502931521880; Wed, 16 Aug 2017 17:58:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.59.248 with HTTP; Wed, 16 Aug 2017 17:58:40 -0700 (PDT)
Received: by 10.237.59.248 with HTTP; Wed, 16 Aug 2017 17:58:40 -0700 (PDT)
In-Reply-To: <FE2E639B0F0F8D272F1339E2@PSB>
References: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com> <b1289123-04ac-e62b-879e-614fae9b20b0@bogus.com> <CACZ1GiooBdEZ_YcBZPQNFkbT0DsGf-Cu25fPYzWcLamLUAH+TA@mail.gmail.com> <CA+9kkMAAQh64M59g0Jn=2j0czS6q56-yoOadGMoeVMTZ=4Z72Q@mail.gmail.com> <FE2E639B0F0F8D272F1339E2@PSB>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 16 Aug 2017 17:58:40 -0700
Message-ID: <CA+9kkMAt3fchTHJKg8zd3PqUdvJMauFyLe0sEK6mHxUricCc+w@mail.gmail.com>
Subject: Re: Scope for self-destructing email?
To: John C Klensin <john-ietf@jck.com>
Cc: IETF <ietf@ietf.org>, vaibhav singh <vaibhavsinghacads@gmail.com>
Content-Type: multipart/alternative; boundary="001a1130c1027bc76f0556e883f2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RG9Qs8sKeXUvznTyH4fEHIaACys>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Aug 2017 00:58:46 -0000

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

On Aug 16, 2017 11:05 AM, "John C Klensin" <john-ietf@jck.com> wrote:



--On Wednesday, August 16, 2017 09:49 -0700 Ted Hardie
<ted.ietf@gmail.com> wrote:


> On Tue, Aug 15, 2017 at 9:50 PM, vaibhav singh
> <vaibhavsinghacads@gmail.com> wrote:
>...
>> *why not try to accommodate both realitys and define a
>> feature which is called "Invalidation of Messages" or similar
>> instead of "Destructible Messages". The goal of this feature
>> should be to mark messages in a way, that the client somehow
>> can mark the message as "not being relevant anymore" or
>> something like that.
>...

> I think there are two potential lines of development here,
> though I confess I am skeptical of the value of either.

> The first is providing a facility that declares a particular
> message to be automatically overcome by events at a particular
> time, leaving it completely up to the recipient how to process
> the message based on that metadata.  There are simple message
> types (today's weather, lunch availability, etc.) that could
> be thus set to be marked OBE when no longer relevant.  Some
> clients might choose to auto-delete them or auto-archive them
> when the time is reached, but this would be because of their
> preferred handling and not a guarantee to the sender that the
> sender's intent is being honored.  A message header like
> OBE-At: could be registered provisionally without much hassle,
> and you could see if it saw implementation and use.

Ted,

Do you consider the above significantly different from the
X.400-derived Expiry-Date (RFC 1327) or Expires (RFC 2156)?
While both are identified as obsolete in RFC 4021 and the IANA
Message Header registry, they provide a date and leave it up to
the recipient how those metadata are processed.

While RFC 1327 and 2156 primarily define those fields by
reference to X.400 (1988 and 1992), my recollection of the
CCITT/ISO documents is that the expiration date-time is defined
in a way that is quite consistent with "Invalidation of
Messages" as described above, with the receiving system free to
warn about obsolescence or even to discard copies.


Honestly, I had forgotten about both, so it is entirely possible that they
match the meta data semantics of much of this.

Ted

While I don't think it has much of a future --for reasons that
many of us have given and that I assume are consistent with your
skepticism -- I'd like to propose what I think would be a far
more constructive approach for Vaibhav and colleagues than
continued iterations on the IETF list:  They could write an I-D
in the form of an Experimental document that would actually pin
down what they are proposing.  That I-D could propose changing
the "obsolete" status for "Expires" in the registry to something
more active if the experiment succeeds, eliminating the need for
any IANA or Expert action at this point and potentially taking
advantage of any MUAs or MTAs that haven't bothered to get rid
of support for those old headers.   Then, with the feature and
any needed protocol bits specified, they see if they can get any
real traction.  Under more usual circumstances, we'd publish an
experimental spec without implementations and demonstration of
usefulness and usability, but, since "Expires" was implemented
and deployed in the past, after which the IETF decided it was
obsolete, it seems to me that pursuing this further should
require proof of utility and/or a clear explanation of why this
time is different.

best,
    john

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

<div dir=3D"auto"><div><div class=3D"gmail_extra"><div class=3D"gmail_quote=
">On Aug 16, 2017 11:05 AM, &quot;John C Klensin&quot; &lt;<a href=3D"mailt=
o:john-ietf@jck.com">john-ietf@jck.com</a>&gt; wrote:<br type=3D"attributio=
n"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex"><br>
<br>
--On Wednesday, August 16, 2017 09:49 -0700 Ted Hardie<br>
<div class=3D"quoted-text">&lt;<a href=3D"mailto:ted.ietf@gmail.com">ted.ie=
tf@gmail.com</a>&gt; wrote:<br>
<br>
<br>
&gt; On Tue, Aug 15, 2017 at 9:50 PM, vaibhav singh<br>
&gt; &lt;<a href=3D"mailto:vaibhavsinghacads@gmail.com">vaibhavsinghacads@g=
mail.com</a>&gt; wrote:<br>
</div>&gt;...<br>
&gt;&gt; *why not try to accommodate both realitys and define a<br>
<div class=3D"quoted-text">&gt;&gt; feature which is called &quot;Invalidat=
ion of Messages&quot; or similar<br>
&gt;&gt; instead of &quot;Destructible Messages&quot;. The goal of this fea=
ture<br>
&gt;&gt; should be to mark messages in a way, that the client somehow<br>
&gt;&gt; can mark the message as &quot;not being relevant anymore&quot; or<=
br>
&gt;&gt; something like that.<br>
</div>&gt;...<br>
<div class=3D"quoted-text"><br>
&gt; I think there are two potential lines of development here,<br>
&gt; though I confess I am skeptical of the value of either.<br>
<br>
&gt; The first is providing a facility that declares a particular<br>
&gt; message to be automatically overcome by events at a particular<br>
&gt; time, leaving it completely up to the recipient how to process<br>
&gt; the message based on that metadata.=C2=A0 There are simple message<br>
&gt; types (today&#39;s weather, lunch availability, etc.) that could<br>
&gt; be thus set to be marked OBE when no longer relevant.=C2=A0 Some<br>
&gt; clients might choose to auto-delete them or auto-archive them<br>
&gt; when the time is reached, but this would be because of their<br>
&gt; preferred handling and not a guarantee to the sender that the<br>
&gt; sender&#39;s intent is being honored.=C2=A0 A message header like<br>
&gt; OBE-At: could be registered provisionally without much hassle,<br>
&gt; and you could see if it saw implementation and use.<br>
<br>
</div>Ted,<br>
<br>
Do you consider the above significantly different from the<br>
X.400-derived Expiry-Date (RFC 1327) or Expires (RFC 2156)?<br>
While both are identified as obsolete in RFC 4021 and the IANA<br>
Message Header registry, they provide a date and leave it up to<br>
the recipient how those metadata are processed.<br>
<br>
While RFC 1327 and 2156 primarily define those fields by<br>
reference to X.400 (1988 and 1992), my recollection of the<br>
CCITT/ISO documents is that the expiration date-time is defined<br>
in a way that is quite consistent with &quot;Invalidation of<br>
Messages&quot; as described above, with the receiving system free to<br>
warn about obsolescence or even to discard copies.<br></blockquote></div></=
div></div><div dir=3D"auto"><br></div><div dir=3D"auto">Honestly, I had for=
gotten about both, so it is entirely possible that they match the meta data=
 semantics of much of this.</div><div dir=3D"auto"><br></div><div dir=3D"au=
to">Ted</div><div dir=3D"auto"><br></div><div dir=3D"auto"><div class=3D"gm=
ail_extra"><div class=3D"gmail_quote"><blockquote class=3D"quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
While I don&#39;t think it has much of a future --for reasons that<br>
many of us have given and that I assume are consistent with your<br>
skepticism -- I&#39;d like to propose what I think would be a far<br>
more constructive approach for Vaibhav and colleagues than<br>
continued iterations on the IETF list:=C2=A0 They could write an I-D<br>
in the form of an Experimental document that would actually pin<br>
down what they are proposing.=C2=A0 That I-D could propose changing<br>
the &quot;obsolete&quot; status for &quot;Expires&quot; in the registry to =
something<br>
more active if the experiment succeeds, eliminating the need for<br>
any IANA or Expert action at this point and potentially taking<br>
advantage of any MUAs or MTAs that haven&#39;t bothered to get rid<br>
of support for those old headers.=C2=A0 =C2=A0Then, with the feature and<br=
>
any needed protocol bits specified, they see if they can get any<br>
real traction.=C2=A0 Under more usual circumstances, we&#39;d publish an<br=
>
experimental spec without implementations and demonstration of<br>
usefulness and usability, but, since &quot;Expires&quot; was implemented<br=
>
and deployed in the past, after which the IETF decided it was<br>
obsolete, it seems to me that pursuing this further should<br>
require proof of utility and/or a clear explanation of why this<br>
time is different.<br>
<br>
best,<br>
=C2=A0 =C2=A0 john<br>
<br>
<br>
</blockquote></div><br></div></div></div>

--001a1130c1027bc76f0556e883f2--


From nobody Wed Aug 16 18:21:44 2017
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 05C1313239D; Wed, 16 Aug 2017 18:21:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Carlos Martinez <carlosm3011@gmail.com>
To: <ops-dir@ietf.org>
Cc: draft-ietf-rtcweb-jsep.all@ietf.org, rtcweb@ietf.org, ietf@ietf.org
Subject: Opsdir last call review of draft-ietf-rtcweb-jsep-21
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150293290297.12432.15822575176336895893@ietfa.amsl.com>
Date: Wed, 16 Aug 2017 18:21:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sYA1pT9mnhLdxlhdjg3A2_RD7VM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Aug 2017 01:21:43 -0000

Reviewer: Carlos Martinez
Review result: Ready

I have reviewed this document as part of the Operational directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written with the intent of improving the operational aspects of
the IETF drafts. Comments that are not addressed in last call may be included
in AD reviews during the IESG review.  Document editors and WG chairs should
treat these comments just like any other last call comments.

Noting that I'm certainly not an expert on the subject matter, I've found this
document to be READY. I found it well-written, it contains plenty of detailed
examples (which I believe are really important for API and programming-heavy
documents), and includes plenty of references as well.

Please do not forget to remove "Appendix B.  Change log".

A minor observation, not even a nit, is that the text in the Security
Considerations "While formally the JSEP interface is an API, it is better to
think of it is an Internet protocol, with the JS being untrustworthy from the
perspective of the endpoint. " could be more clear.

thanks!

/Carlos


From nobody Wed Aug 16 18:24:31 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 061BA132391 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 18:24:31 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KCJiW_qQzwsW for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 18:24:28 -0700 (PDT)
Received: from mail-pg0-x22b.google.com (mail-pg0-x22b.google.com [IPv6:2607:f8b0:400e:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3C5A126BF0 for <ietf@ietf.org>; Wed, 16 Aug 2017 18:24:28 -0700 (PDT)
Received: by mail-pg0-x22b.google.com with SMTP id t80so4451233pgb.5 for <ietf@ietf.org>; Wed, 16 Aug 2017 18:24:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ObVYgHMPz3WR8VTFtfo7oxuFReLd4DSW0GIkGvYRaX8=; b=mVmht3zh/zjjB1SsRMIYem/9sTuK13F1Wypztr5rpvkgB+AjY148GZP4fFdUkPEY4i xD/GAtecoHoJwsaplCUXdSNOuNJxK061t7+2b611H+LrL4KLrikAK+TF7/H0Klb9f3xh aDtolyqeJZSL9nudq9Yz989bAGwlK2cXF71XVZVsd19gJQCb0wO+fj6CuGcV4i31/DzK 9Vo1FmFQQCgvX4EPoJm/GDBjheyg4RkXb5gDelbxKIBd3if7uQCd0rgQ6pAVQApCft9y JsnCv4+eQpsA27r6QqIij90rV/0/zoBGFnegE5XHLWeu+bUdzcQyYMsKozpHnltb2tjx QHiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=ObVYgHMPz3WR8VTFtfo7oxuFReLd4DSW0GIkGvYRaX8=; b=odYrKG9GNL//OZ6hSLd6Pv7Ip9cPq4SiPKX/wcE/6RIuJ1Cm6djhQLNOTq3k/Lxuxm f+PScnJOO0fVCo1LygFV6fuOrrq/02d3QDFLl1Ef0fTtOUooOxBGGU1U2wfGMqeivArz fEVx70yHVOxtQVO7NJfD2AzSYtEI2jiaE/u/LrpiI6JCndTewyAJiZWaOSbS7rsgvAEG CXbPkVfnvVaraOOI44QLSPo7zq/ygcKjg2LuHnPkNanf0yEEP2D99BIKy8tj3LJJZmlQ ikIzoTYuUgpqWLlCinJXumBIsSJQlHlLCNaiFawxbO+Pajqc2+jHFKhUZ4YCLoidL0E5 BV2A==
X-Gm-Message-State: AHYfb5i2bt5qTMpqKtN65JjNxBAJw+ISMTp9QCxtyCkRjNp2ygrz83uG i6JGjXvZt5UgBA==
X-Received: by 10.84.231.9 with SMTP id f9mr3816523plk.257.1502933068215; Wed, 16 Aug 2017 18:24:28 -0700 (PDT)
Received: from ?IPv6:2406:e007:521f:1:28cc:dc4c:9703:6781? ([2406:e007:521f:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id u12sm3566719pgq.24.2017.08.16.18.24.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 Aug 2017 18:24:27 -0700 (PDT)
Subject: Re: Scope for self-destructing email?
To: John Levine <johnl@taugh.com>, ietf@ietf.org
Cc: vaibhavsinghacads@gmail.com
References: <20170816225637.4431.qmail@ary.lan>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <7352544b-8626-fb30-b74f-48b62110b7cf@gmail.com>
Date: Thu, 17 Aug 2017 13:24:30 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <20170816225637.4431.qmail@ary.lan>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/L5u8U7wLdBxs4_Wbf5Vx16EF1yw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Aug 2017 01:24:31 -0000

On 17/08/2017 10:56, John Levine wrote:
> In article <CACZ1GiooBdEZ_YcBZPQNFkbT0DsGf-Cu25fPYzWcLamLUAH+TA@mail.gmail.com> you write:
>> This seems to work for me. Any problems which could come up with having a
>> central authority for this feature?
> 
> Many.  What if I tell the central authority that I implement
> self-destructive e-mail but I'm lying?  How could the central
> authority tell?  I'm pretty sure I can pass whatever audits they make
> since they have no way to tell what data I'm hiding in places they
> can't see.
> 
>> 4.) A really boiled down version of ephemeral mails could just mark the
>> mail "outdated" if the information provided in the mail is not expected to
>> hold good after some time, instead of actually expunging the mail.
> 
> As others have said, that feature has come and gone many times in the past.  In
> netnews, which is similar in some ways to mail, there's an Expires: header which
> works reasonably well, typically used to mark messages that stop being interesting
> after some point like weather forecasts or event reminders.  There's no guarantee
> that anyone will follow the advice, and you certainly can't use it to force stuff
> to disappear, but it's been occasionally useful.

I thought of changing the title to "Scope for self-destructing web pages?"

After I heard an early internal presentation of the design of the World-Wide Web
from my CERN colleague Tim Berners-Lee, probably in 1993, I asked him why he didn't
make an expiry date a mandatory feature of every HTML document. Being a man of some
foresight, he explained exactly why it wouldn't work in practice, despite being
a wonderful idea in theory.

And yes, according to RFC 1866 (and for all I know, more recent definitions
of HTML) you can include things like
    <META HTTP-EQUIV="Expires" CONTENT="Tue, 04 Dec 1993 21:29:02 GMT">
and the server may then include "Expires: Tue, 04 Dec 1993 21:29:02 GMT"
in the reply to an HTTP GET.

Only, have you noticed any web pages expiring recently? Maybe there are
browsers that annoy their users by not displaying expired pages?

Bits don't expire.

    Brian


From nobody Wed Aug 16 18:47:51 2017
Return-Path: <lyndon@orthanc.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02FF8132400 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 18:47:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GG9DhC2d1aJl for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 18:47:49 -0700 (PDT)
Received: from orthanc.ca (orthanc.ca [IPv6:2607:f2f8:abf8::2]) (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 A890013226B for <ietf@ietf.org>; Wed, 16 Aug 2017 18:47:49 -0700 (PDT)
Received: from minnie.hitronhub.home (S0106a84e3f81a003.vc.shawcable.net [24.80.126.119]) (authenticated bits=0) by orthanc.ca (8.15.2/8.15.2) with ESMTPSA id v7H1llaL066599 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 16 Aug 2017 18:47:47 -0700 (PDT) (envelope-from lyndon@orthanc.ca)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Scope for self-destructing email?
From: Lyndon Nerenberg <lyndon@orthanc.ca>
In-Reply-To: <7352544b-8626-fb30-b74f-48b62110b7cf@gmail.com>
Date: Wed, 16 Aug 2017 18:47:41 -0700
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org, vaibhavsinghacads@gmail.com
Content-Transfer-Encoding: quoted-printable
Message-Id: <39610B4F-8DE6-4E19-A6C8-5FAB882DD524@orthanc.ca>
References: <20170816225637.4431.qmail@ary.lan> <7352544b-8626-fb30-b74f-48b62110b7cf@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HjUHVTCP_MAp6_E8QlULx47cysM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Aug 2017 01:47:51 -0000

> On Aug 16, 2017, at 6:24 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> Only, have you noticed any web pages expiring recently? Maybe there =
are
> browsers that annoy their users by not displaying expired pages?
>=20
> Bits don't expire.

They do.  Is there a single web site on the planet these days that =
*doesn't* set the page cache time to 0?=20

Then again, my Customer Experience is Enhanced by waiting for that 20 =
second reload, every time I press the "back" button in my phone's web =
browser.  It gives me time to flip to another tab and buy something for =
Instant Delivery from Amazon.  The package usually arrives before the =
other tab finishes reloading.

--lyndon


From nobody Wed Aug 16 20:21:59 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AF3413245C for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 20:21:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level: 
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nyd0vMTOR1Uk for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 20:21:55 -0700 (PDT)
Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47E4213208E for <ietf@ietf.org>; Wed, 16 Aug 2017 20:21:55 -0700 (PDT)
Received: by mail-lf0-x22d.google.com with SMTP id d17so24211341lfe.0 for <ietf@ietf.org>; Wed, 16 Aug 2017 20:21:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=GlhtzllWNVntDbEi3v+88GgDhgyqsYLKGA1joGsagSo=; b=PybQSYKP7YaAs5Q3qpAt54xhHlsaNKWFbhcw5UKkCAEmdgxHZLqBYM6Py1ORBlkYw5 eSdIKeWpoYQJ/KO0IkZrtxSh3KClldmejz1Kg/HxF6dd/skikZ8xr2KKQeziCZO+7kaq +WFVz/7CnLHJhaCDlqmEXSmVpXgcj2ZgsAiUK49xd12/qV7nQbsZYU5JxpjRVWMU37z3 7k7ZSTdhmyasCowsVL2y3MeAxIx33uub+Y1XTeF+HQcUmVRBtcEoWbHr6cmEYBqf6NsV 0UaPbTJQuRI9SKPkyOkteWRrP6/OgAmeqwLYxveKTYnU9Gkk6UqYFR9tXzt98S9ElWz5 ZqNA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=GlhtzllWNVntDbEi3v+88GgDhgyqsYLKGA1joGsagSo=; b=UHALn5voXSPe85SKPnSKeuAEx1fqoJGMXQGlNyVNDKuuodLsn5TQp6wXSSZpHaTWxY w5yxYDGp9U23sBzs32Sa/cfCa7JL74BMWI61uMGZxpWLlTO768/sgNjEulz+Erfri1j1 0drHCdiGVVumP6ouYdTjUmHZhiHxL2NaVslr4kMfNoJbgRyyCETniSACqws9o9Jssn0S str/vZZVdNdNCTYcxanL9ulhJKA3qZybnhyeyuwHMYherANgb4IrhR38y8whmGzctQIp G/zsSChMy6TN5cOiNkQW0scRR+CRosywls2N6FQBmVmFdeGpu+ex5SAc03oEQz9IcFVE 22Zw==
X-Gm-Message-State: AHYfb5gB3Xq8bQvkvbiLQdhMl6iZA4HlWj6SUVWSTIIxvzQaoWYxA7pw wgHKYHrusVgGhv7aPrvYfcF5j03zfHlG
X-Received: by 10.25.150.130 with SMTP id y124mr1450199lfd.202.1502940113289;  Wed, 16 Aug 2017 20:21:53 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.25.142.199 with HTTP; Wed, 16 Aug 2017 20:21:52 -0700 (PDT)
In-Reply-To: <39610B4F-8DE6-4E19-A6C8-5FAB882DD524@orthanc.ca>
References: <20170816225637.4431.qmail@ary.lan> <7352544b-8626-fb30-b74f-48b62110b7cf@gmail.com> <39610B4F-8DE6-4E19-A6C8-5FAB882DD524@orthanc.ca>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 16 Aug 2017 23:21:52 -0400
X-Google-Sender-Auth: DagK_cQsxmjN1N_CiCvS3FmcFqY
Message-ID: <CAMm+LwgqnPx2VBaoaWuU_YW547oRhQDTo48t4BokcwKqRSO+bw@mail.gmail.com>
Subject: Re: Scope for self-destructing email?
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a114025a69247280556ea8348"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Lx0vJ_nWGm-OiUqweNgtCc-30pk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Aug 2017 03:21:58 -0000

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

This is a problem I have been considering for some time. And everyone in
this thread is right. Right on the facts at least. Most are wrong on the
implications.

When the Web was launched in 1992, it was dismissed by the network
hypertext crowd because it did not solve the problem of referential
transparency that Ted Nelson insisted was really really important. It was
not, the Web worked fine with 404 not found. In fact it didn't work fine,
it worked *better*.

It was this insight that led me to propose Confidential Document Control
(CDC) as a subset of the Digital Rights Management (DRM) Problem. I have a
draft if you are interested in the math or just like looking at the pretty
SVG pictures we can use in HTML:

http://prismproof.org/Documents/draft-hallambaker-mesh-recrypt.html


=E2=80=8BWhat I realized was that there are two difficult problems in the D=
RM
problem:

1) Restricting initial distribution of confidential data =E2=80=8Bto the se=
t of
authorized parties.

2) Preventing disclosure by authorized parties to others.

These are both challenging technical problems that cannot be solved with
the cryptographic toolset used in OpenPGP and S/MIME. Mesh/Recrypt
addresses the first. It uses cryptography that can be understood by high
school students but it is cryptography that nobody had worked out how to
apply in practice that way until now[1].

=E2=80=8BSolving the first problem really wasn't impossible. I am pretty su=
re that
many others could have done what I have. But I rather suspect the reason
they did not is that the whole field of DRM has been poisoned by two facts:

1) =E2=80=8B Preventing disclosure by authorized parties to others requires=
 the use
of trustworthy hardware and no hardware is 100% trustworthy.

2) The whole field of DRM has been poisoned by anti-copyright enforcement
ideology.

=E2=80=8BThe problem that began this thread, 'burn after 24 hours' is simpl=
y
another type of attribute =E2=80=8Bdescribing a restriction we wish to enfo=
rce on
the use of the document.

=E2=80=8BAt the moment, Mesh/Recrypt is deliberately limited to solving onl=
y the
first part of the CRM problem. It only addresses the initial distribution
of the documents. This is the subset I call Confidential Document Control.
One reason for this limitation is that authorization policy languages is a
whole different patent minefield to navigate. But the other is that I get
95% of the =E2=80=8Bvalue of a full DRM system with just my CDC component.

Consider recent US government breaches:

* Did Snowden need to read any of the Powerpoint files?
* Did Chelsea Manning need to have access to 250,000 cables?
* Did everyone working in the CIA need access to the website with the
malware tools?
* Should the Secretary of State have reasonably considered the GSA mail
services secure when it is likely thousands of personnel and contractors
had access to them?

=E2=80=8BWhen we drill down, the number of leaks by a person with a need to=
 know
the material in question is a tiny =E2=80=8Bfraction of the people who have=
 access
today. Without a practical, standards based means of performing data level
encryption, the leaks are going to continue.

It is the same in the enterprise. While it is possible that the criminal
gangs that attacked HBO to leak Game of Thrones did so by suborning an
insider, it is vastly more likely that they compromised a machine on the
corporate network and leveraged it. CDC rather than full DRM would almost
certainly have been sufficient.


So what then of DRM? Am I saying it has absolutely no use? Absolutely not.
Because security is risk control, not risk elimination. It is not necessary
to provide an absolute guarantee that the data will not leak in any
possible circumstance to provide value. Trustworthy hardware does not need
to be 100% trustworthy to provide useful risk control in the enterprise.

In fact, there is only one area in which DRM has to be 100% and that is
copyright enforcement and that is because it is break once run anywhere. So
I can certainly help HBO stop their shows leaking before show date but I am
not going to promise anything after they have shared their secret with ten
million of their closest friends.

For early adopter purposes, the hardware used to distribute material need
not be any more trustworthy than an iPad Pro. Of course you or I or any
number of folk could probably work out how to bypass that level of security
given physical access to the device. But the fact is that what most people
want is for the machine to help them not leak stuff accidentally. They have
absolutely no intention of jailbreaking their corporate phone or tablet.


So here is what I propose. Let us start this journey by working on a
solution to the CDC part of the problem. Which will take us some time.
Solving the CDC problem is a subset of the enterprise DRM problem.

And if we win, then its like pinball - you win, you get to play again.
Adding a security policy language to describe permitted uses is a trivial
engineering task. The hard part would be the prior art search.

=E2=80=8BPHB=E2=80=8B


=E2=80=8B[1] Well I hope this is the case as I am going to be doing just th=
at later
this year.=E2=80=8B

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

<div dir=3D"ltr"><div class=3D"gmail_default">This is a problem I have been=
 considering for some time. And everyone in this thread is right. Right on =
the facts at least. Most are wrong on the implications.</div><div class=3D"=
gmail_default"><br></div><div class=3D"gmail_default">When the Web was laun=
ched in 1992, it was dismissed by the network hypertext crowd because it di=
d not solve the problem of referential transparency that Ted Nelson insiste=
d was really really important. It was not, the Web worked fine with 404 not=
 found. In fact it didn&#39;t work fine, it worked <i>better</i>.</div><div=
 class=3D"gmail_default"><br></div><div class=3D"gmail_default">It was this=
 insight that led me to propose Confidential Document Control (CDC) as a su=
bset of the Digital Rights Management (DRM) Problem. I have a draft if you =
are interested in the math or just like looking at the pretty SVG pictures =
we can use in HTML:</div><div class=3D"gmail_default"><br></div><div class=
=3D"gmail_default"><a href=3D"http://prismproof.org/Documents/draft-hallamb=
aker-mesh-recrypt.html">http://prismproof.org/Documents/draft-hallambaker-m=
esh-recrypt.html</a><br></div><div class=3D"gmail_extra"><br></div><div cla=
ss=3D"gmail_extra"><br><div class=3D"gmail_quote"><div class=3D"gmail_defau=
lt" style=3D"font-size:small">=E2=80=8BWhat I realized was that there are t=
wo difficult problems in the DRM problem:</div><div class=3D"gmail_default"=
 style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"=
font-size:small">1) Restricting initial distribution of confidential data =
=E2=80=8Bto the set of authorized parties.</div><div class=3D"gmail_default=
" style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D=
"font-size:small">2) Preventing disclosure by authorized parties to others.=
</div><br></div><div class=3D"gmail_quote"><div class=3D"gmail_default" sty=
le=3D"font-size:small">These are both challenging technical problems that c=
annot be solved with the cryptographic toolset used in OpenPGP and S/MIME. =
Mesh/Recrypt addresses the first. It uses cryptography that can be understo=
od by high school students but it is cryptography that nobody had worked ou=
t how to apply in practice that way until now[1].</div><br></div><div class=
=3D"gmail_quote"><div class=3D"gmail_default" style=3D"font-size:small">=E2=
=80=8BSolving the first problem really wasn&#39;t impossible. I am pretty s=
ure that many others could have done what I have. But I rather suspect the =
reason they did not is that the whole field of DRM has been poisoned by two=
 facts:</div><div class=3D"gmail_default" style=3D"font-size:small"><br></d=
iv><div class=3D"gmail_default" style=3D"font-size:small">1) =E2=80=8B Prev=
enting disclosure by authorized parties to others requires the use of trust=
worthy hardware and no hardware is 100% trustworthy.</div><div class=3D"gma=
il_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default=
" style=3D"font-size:small">2) The whole field of DRM has been poisoned by =
anti-copyright enforcement ideology.</div><br></div><div class=3D"gmail_quo=
te"><div class=3D"gmail_default" style=3D"font-size:small">=E2=80=8BThe pro=
blem that began this thread, &#39;burn after 24 hours&#39; is simply anothe=
r type of attribute =E2=80=8Bdescribing a restriction we wish to enforce on=
 the use of the document.</div><br></div><div class=3D"gmail_quote"><div cl=
ass=3D"gmail_default" style=3D"font-size:small">=E2=80=8BAt the moment, Mes=
h/Recrypt is deliberately limited to solving only the first part of the CRM=
 problem. It only addresses the initial distribution of the documents. This=
 is the subset I call Confidential Document Control. One reason for this li=
mitation is that authorization policy languages is a whole different patent=
 minefield to navigate. But the other is that I get 95% of the =E2=80=8Bval=
ue of a full DRM system with just my CDC component.</div><div class=3D"gmai=
l_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default"=
 style=3D"font-size:small">Consider recent US government breaches:</div><di=
v class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D=
"gmail_default" style=3D"font-size:small">* Did Snowden need to read any of=
 the Powerpoint files?</div><div class=3D"gmail_default" style=3D"font-size=
:small">* Did Chelsea Manning need to have access to 250,000 cables?</div><=
div class=3D"gmail_default" style=3D"font-size:small">* Did everyone workin=
g in the CIA need access to the website with the malware tools?</div><div c=
lass=3D"gmail_default" style=3D"font-size:small">* Should the Secretary of =
State have reasonably considered the GSA mail services secure when it is li=
kely thousands of personnel and contractors had access to them?</div><div c=
lass=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gm=
ail_default" style=3D"font-size:small">=E2=80=8BWhen we drill down, the num=
ber of leaks by a person with a need to know the material in question is a =
tiny =E2=80=8Bfraction of the people who have access today. Without a pract=
ical, standards based means of performing data level encryption, the leaks =
are going to continue.=C2=A0</div><div class=3D"gmail_default" style=3D"fon=
t-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:sma=
ll">It is the same in the enterprise. While it is possible that the crimina=
l gangs that attacked HBO to leak Game of Thrones did so by suborning an in=
sider, it is vastly more likely that they compromised a machine on the corp=
orate network and leveraged it. CDC rather than full DRM would almost certa=
inly have been sufficient.</div><div class=3D"gmail_default" style=3D"font-=
size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small=
"><br></div><div class=3D"gmail_default" style=3D"font-size:small">So what =
then of DRM? Am I saying it has absolutely no use? Absolutely not. Because =
security is risk control, not risk elimination. It is not necessary to prov=
ide an absolute guarantee that the data will not leak in any possible circu=
mstance to provide value. Trustworthy hardware does not need to be 100% tru=
stworthy to provide useful risk control in the enterprise.=C2=A0</div><div =
class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"g=
mail_default" style=3D"font-size:small">In fact, there is only one area in =
which DRM has to be 100% and that is copyright enforcement and that is beca=
use it is break once run anywhere. So I can certainly help HBO stop their s=
hows leaking before show date but I am not going to promise anything after =
they have shared their secret with ten million of their closest friends.=C2=
=A0</div><div class=3D"gmail_default" style=3D"font-size:small"><br></div><=
div class=3D"gmail_default" style=3D"font-size:small">For early adopter pur=
poses, the hardware used to distribute material need not be any more trustw=
orthy than an iPad Pro. Of course you or I or any number of folk could prob=
ably work out how to bypass that level of security given physical access to=
 the device. But the fact is that what most people want is for the machine =
to help them not leak stuff accidentally. They have absolutely no intention=
 of jailbreaking their corporate phone or tablet.<br></div><div class=3D"gm=
ail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_defaul=
t" style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=
=3D"font-size:small">So here is what I propose. Let us start this journey b=
y working on a solution to the CDC part of the problem. Which will take us =
some time. Solving the CDC problem is a subset of the enterprise DRM proble=
m.=C2=A0</div><div class=3D"gmail_default" style=3D"font-size:small"><br></=
div><div class=3D"gmail_default" style=3D"font-size:small">And if we win, t=
hen its like pinball - you win, you get to play again. Adding a security po=
licy language to describe permitted uses is a trivial engineering task. The=
 hard part would be the prior art search.</div><br></div><div class=3D"gmai=
l_quote"><div class=3D"gmail_default" style=3D"font-size:small">=E2=80=8BPH=
B=E2=80=8B</div><br></div><div class=3D"gmail_quote"><br></div><div class=
=3D"gmail_quote"><div class=3D"gmail_default" style=3D"font-size:small">=E2=
=80=8B[1] Well I hope this is the case as I am going to be doing just that =
later this year.=E2=80=8B</div><br></div></div></div>

--001a114025a69247280556ea8348--


From nobody Wed Aug 16 20:47:51 2017
Return-Path: <Glenn.Deen@nbcuni.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02994132489 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 20:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Rwq1enZmh-X for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 20:47:48 -0700 (PDT)
Received: from mx0a-00176a04.pphosted.com (mx0b-00176a04.pphosted.com [67.231.157.49]) (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 3F53713247A for <ietf@ietf.org>; Wed, 16 Aug 2017 20:47:40 -0700 (PDT)
Received: from pps.filterd (m0049465.ppops.net [127.0.0.1]) by mx0b-00176a04.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v7H3gmDD027824 for <ietf@ietf.org>; Wed, 16 Aug 2017 23:47:38 -0400
Received: from usushmgip002.mail.tfayd.com ([216.178.109.236]) by mx0b-00176a04.pphosted.com with ESMTP id 2ccum6ed9w-1 (version=TLSv1.2 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Wed, 16 Aug 2017 23:47:38 -0400
Received: from unknown (HELO USUSHECWP007.mail.tfayd.com) ([10.40.33.204]) by usushmgip002.mail.tfayd.com with ESMTP; 16 Aug 2017 20:47:36 -0700
Received: from potemwp00025.mail.tfayd.com (100.124.56.49) by USUSHECWP007.mail.tfayd.com (3.156.41.61) with Microsoft SMTP Server (TLS) id 14.3.266.1; Wed, 16 Aug 2017 20:47:36 -0700
Received: from potemwp00029.mail.tfayd.com (100.124.56.53) by potemwp00025.mail.tfayd.com (100.124.56.49) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.32; Wed, 16 Aug 2017 21:47:35 -0600
Received: from potemwp00029.mail.tfayd.com ([100.124.56.53]) by potemwp00029.mail.tfayd.com ([100.124.56.53]) with mapi id 15.01.0669.032; Wed, 16 Aug 2017 21:47:35 -0600
From: "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Scope for self-destructing email?
Thread-Topic: Scope for self-destructing email?
Thread-Index: AQHTFS/Xd4h4ca7zTUS2C6rywoqwoqKFIruAgAGt8QCAAS9dgIAAKVIAgAAGeoCAABpQAP//opsm
Date: Thu, 17 Aug 2017 03:47:35 +0000
Message-ID: <F0EECBF6-F48E-425B-A6E8-65E5183FD36E@nbcuni.com>
References: <20170816225637.4431.qmail@ary.lan> <7352544b-8626-fb30-b74f-48b62110b7cf@gmail.com> <39610B4F-8DE6-4E19-A6C8-5FAB882DD524@orthanc.ca>, <CAMm+LwgqnPx2VBaoaWuU_YW547oRhQDTo48t4BokcwKqRSO+bw@mail.gmail.com>
In-Reply-To: <CAMm+LwgqnPx2VBaoaWuU_YW547oRhQDTo48t4BokcwKqRSO+bw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-exclaimer-md-config: 47edc00f-f2d6-45ef-be83-8a353bd47e45
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-08-17_02:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1708170061
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/G4ZjtvCZOZ40Li6v3wq5QHcNHPg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Aug 2017 03:47:50 -0000

The key issue is that no method currently in existence can defeat a camera =
taking a picture of the screen.  That will always let an authorized receive=
r make a permanent copy of the email and do what they want with it.  Yes, y=
ou may be throwing away repudiation and signature information, but they wil=
l have the contents of the mail.

-glenn =


From nobody Wed Aug 16 21:43:22 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F17911323CA for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 21:43:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level: 
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M2J2ciUjtse4 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 21:43:19 -0700 (PDT)
Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00A6E13235C for <ietf@ietf.org>; Wed, 16 Aug 2017 21:43:18 -0700 (PDT)
Received: by mail-lf0-x22c.google.com with SMTP id t128so24848863lff.2 for <ietf@ietf.org>; Wed, 16 Aug 2017 21:43:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=CPI1l0Rw53u85nLBZi7lwskFu7ODv4fC1kt9CdWevx4=; b=qV7ssE7jpY3jSWsMv35LZkSJ2T2GFGyFXsBvCfEuiTZA9A2DC0RLSVa7EvkzDR79bA zPp76K5NV2VwbPrpDWxb0Lq0snMeGPKROwEVwGMUQigfDobEuBPVzOsHv321dbTsi4qc e3rjLfztAX5xfPRe5S/MkXTdKqdiurt0gyHAReIpFVqfcfbPOLCDIy8PziCA6NwXD3Dg l1FXsmafmERwq112M0wo0fADEfZGz6YP1YmAG6OGI94vY9iRWLxs3Xprz63CSHgYMna5 tLQbLWsAzYelV1LMmMLoOqwnJzTc3DjZKB1etfr/k6Q/8C0SPrR5Q00MvomrHtN1WHO7 MmcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=CPI1l0Rw53u85nLBZi7lwskFu7ODv4fC1kt9CdWevx4=; b=O91/Sb+/mV7OP5AqRITmUPEvUBXECdcP46ymsyy8QqPbuN6lBPDjsZPC0L3G3vFiDW tj96g2wiHILafkFS+HQhpVX3PsmRoeEZWqkw+0D0BO7ElCO7qVajLpm7d77fL6OMgHxa yiTx5yTue2sSzOu8if4tTonNNmjVtMstf27aLfb6f/qDEQM4qkL6pARvXxRHe2hZHT0V 30jNuOXgiJc9C525ZnxBAtGC8b7Dw7roUU5w4b8+cQO3PQThoKPfEEsgimXn1LZD/cn+ 3irrPrNVccWYsmEgtAgxkgxHpUK9ZI/de1t4bXq0bWv1JLfaHB8Zf4R07pdwBwlAZ+HC TCuQ==
X-Gm-Message-State: AHYfb5gsB8ciJ9UA9yztjc62ljRawg1lA0tyudJRC5M3XJR30twFgTeI xMXVQFWhFXnlNWRe0yWi4IXrADXWWQ==
X-Received: by 10.25.153.69 with SMTP id b66mr1724540lfe.75.1502944997324; Wed, 16 Aug 2017 21:43:17 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.25.142.199 with HTTP; Wed, 16 Aug 2017 21:43:16 -0700 (PDT)
In-Reply-To: <F0EECBF6-F48E-425B-A6E8-65E5183FD36E@nbcuni.com>
References: <20170816225637.4431.qmail@ary.lan> <7352544b-8626-fb30-b74f-48b62110b7cf@gmail.com> <39610B4F-8DE6-4E19-A6C8-5FAB882DD524@orthanc.ca> <CAMm+LwgqnPx2VBaoaWuU_YW547oRhQDTo48t4BokcwKqRSO+bw@mail.gmail.com> <F0EECBF6-F48E-425B-A6E8-65E5183FD36E@nbcuni.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 17 Aug 2017 00:43:16 -0400
X-Google-Sender-Auth: BFdjgo9u6so8rceykH41LGvg1vA
Message-ID: <CAMm+LwiT8+oiLwSX_9bekiDY6_3njbW9W_jKnP9FJkRYqwqRcQ@mail.gmail.com>
Subject: Re: Scope for self-destructing email?
To: "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a114029fcaebf110556eba686"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Freq7DU_Wcea1wqZufDvdw4AGnk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Aug 2017 04:43:21 -0000

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

On Wed, Aug 16, 2017 at 11:47 PM, Deen, Glenn (NBCUniversal) <
Glenn.Deen@nbcuni.com> wrote:

> The key issue is that no method currently in existence can defeat a camer=
a
> taking a picture of the screen.  That will always let an authorized
> receiver make a permanent copy of the email and do what they want with it=
.
> Yes, you may be throwing away repudiation and signature information, but
> they will have the contents of the mail.
>

=E2=80=8BAbsolutely true. And really serious for some applications. But con=
sider
the Game of Thrones hack, a screen capture would be serious, yes. But
nowhere near as serious as having the final cut leak in HD.

=E2=80=8BThe kids are using snapchat because their principle security conce=
rn is
that the receiver will forget to delete the pics they send and they will
end up with the parents. They understand full well that they can photograph
the screen of one phone with another.

The perfect is the enemy of the good.

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">On =
Wed, Aug 16, 2017 at 11:47 PM, Deen, Glenn (NBCUniversal) <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:Glenn.Deen@nbcuni.com" target=3D"_blank">Glenn.Deen@=
nbcuni.com</a>&gt;</span> wrote:<br></div><div class=3D"gmail_extra"><div c=
lass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The key issue is that n=
o method currently in existence can defeat a camera taking a picture of the=
 screen.=C2=A0 That will always let an authorized receiver make a permanent=
 copy of the email and do what they want with it.=C2=A0 Yes, you may be thr=
owing away repudiation and signature information, but they will have the co=
ntents of the mail.<br></blockquote><div><br></div><div><div class=3D"gmail=
_default" style=3D"font-size:small">=E2=80=8BAbsolutely true. And really se=
rious for some applications. But consider the Game of Thrones hack, a scree=
n capture would be serious, yes. But nowhere near as serious as having the =
final cut leak in HD.</div><div class=3D"gmail_default" style=3D"font-size:=
small"><br></div><div class=3D"gmail_default" style=3D"font-size:small">=E2=
=80=8BThe kids are using snapchat because their principle security concern =
is that the receiver will forget to delete the pics they send and they will=
 end up with the parents. They understand full well that they can photograp=
h the screen of one phone with another.</div></div><div class=3D"gmail_defa=
ult" style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=
=3D"font-size:small">The perfect is the enemy of the good.=C2=A0</div><div>=
=C2=A0</div></div></div></div>

--001a114029fcaebf110556eba686--


From nobody Wed Aug 16 23:28:47 2017
Return-Path: <huitema@huitema.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54B6D13219E for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 23:28:45 -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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H0D2xaFEBu_x for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 23:28:42 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 9A8CF126C2F for <ietf@ietf.org>; Wed, 16 Aug 2017 23:28:42 -0700 (PDT)
Received: from xsmtp31.mail2web.com ([168.144.250.234] helo=xsmtp11.mail2web.com) by mx19.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1diEIE-0003hQ-80 for ietf@ietf.org; Thu, 17 Aug 2017 08:28:40 +0200
Received: from [10.5.2.18] (helo=xmail08.myhosting.com) by xsmtp11.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1diEI9-0005Z7-Aw for ietf@ietf.org; Thu, 17 Aug 2017 02:28:33 -0400
Received: (qmail 14162 invoked from network); 17 Aug 2017 06:28:26 -0000
Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.56.42.132]) (envelope-sender <huitema@huitema.net>) by xmail08.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf@ietf.org>; 17 Aug 2017 06:28:26 -0000
To: ietf@ietf.org
References: <20170816225637.4431.qmail@ary.lan> <7352544b-8626-fb30-b74f-48b62110b7cf@gmail.com> <39610B4F-8DE6-4E19-A6C8-5FAB882DD524@orthanc.ca> <CAMm+LwgqnPx2VBaoaWuU_YW547oRhQDTo48t4BokcwKqRSO+bw@mail.gmail.com> <F0EECBF6-F48E-425B-A6E8-65E5183FD36E@nbcuni.com> <CAMm+LwiT8+oiLwSX_9bekiDY6_3njbW9W_jKnP9FJkRYqwqRcQ@mail.gmail.com>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <a6492c82-2b16-b087-c554-8ca38c8f5e84@huitema.net>
Date: Wed, 16 Aug 2017 23:28:25 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAMm+LwiT8+oiLwSX_9bekiDY6_3njbW9W_jKnP9FJkRYqwqRcQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------4CFB2EBEC99B2B438352FD8F"
Subject: Re: Scope for self-destructing email?
X-Originating-IP: 168.144.250.234
X-SpamExperts-Domain: xsmtpout.mail2web.com
X-SpamExperts-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-SpamExperts-Outgoing-Class: unsure
X-SpamExperts-Outgoing-Evidence: Combined (0.21)
X-Recommended-Action: accept
X-Filter-ID: PqwsvolAWURa0gwxuN3S5YEa3T7JuZT23fGO2rGt3ZgTCGhDnudOJ80D1c8rffxrus7BTv7Ss8cH d2IQQuvdbtM+m4WpRRDP6YzwkAPgQJY8hyefn/FOeAH6Zsqubs62ND46yZLY9QyX+cRXmooQ3hum JwiT+2brWmQlzkLIcXivpIH4ag6BM/+u9ym+BA23zTdcqT02f+vocg6pOUeZvjRN6JmsfZVbaHnz h7m8mZTu1/LFrfSKlBcXEO+Bnz6OYOEkjsX7F8KmpUaZQHV+SWsC1ltxhvDAAiytf1zpGXO2G5Pj 7iQJEmtNUzH3idZ6uMF2OhyCCCV83x+RZrKIj0QqMGQOSwmEPwP4wBzM77N8GvkYGGDFjg9NrmGY yNnXsSjdYwfRhjHqxQXDsBKLpKOHi0RYvlOYvJoUtCbvS/b6lO4FGen962xgCFRckncKfg1XSK9P 1z/R6plfrFWGydPOISCknCUaMSIT6AczNEveNHk15VolAGHS5rCXQKDym+Gab6cuAPzLi/SdAxlO dgkraHgbbAuZgv0Q6mJ3vUcipz1IT62ZEk6+MmovaufbiR3bHfnMCIEU+nrglojKwMr3vOY18GvB wSXAfWcj237lbbxdoi07KbLoeZB/AeCPNdSMuNhZC3X/nGdDKYyg+1Fotn1TGspRGWfHjmaruO0b XpkevaElTi+sCWwmqxHi+BUHXGjp0J8FpT+J6AFTxuD+VwmBZ+w9Rx50ybtFDGs078I0y+3uS4dN KiUgYTBU2GOrYDdWXqXFPJChI1ipI4AbiteDwjw8P7mx/NBHSRWxZaHLvUGmD7PXY2RS8idsz7fr MHsNPRylYAkPvY1HttQOF909qtkcRbvucYBIc/TSiGRBfhCjzofKjrwJNQRY0i13zjCiwPgdt77s k1WBMw==
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6l-UV6bU5x1qsK1Te5HC0yvZuII>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Aug 2017 06:28:45 -0000

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

On 8/16/2017 9:43 PM, Phillip Hallam-Baker wrote:

> On Wed, Aug 16, 2017 at 11:47 PM, Deen, Glenn (NBCUniversal)
> <Glenn.Deen@nbcuni.com <mailto:Glenn.Deen@nbcuni.com>> wrote:
>
>     The key issue is that no method currently in existence can defeat
>     a camera taking a picture of the screen.  That will always let an
>     authorized receiver make a permanent copy of the email and do what
>     they want with it.  Yes, you may be throwing away repudiation and
>     signature information, but they will have the contents of the mail.=

>
>
> =E2=80=8B Absolutely true. And really serious for some applications. Bu=
t
> consider the Game of Thrones hack, a screen capture would be serious,
> yes. But nowhere near as serious as having the final cut leak in HD.
>
> =E2=80=8B The kids are using snapchat because their principle security =
concern
> is that the receiver will forget to delete the pics they send and they
> will end up with the parents. They understand full well that they can
> photograph the screen of one phone with another.
>
> The perfect is the enemy of the good.=20
> =20
Yes. The threat model here is not that the recipient will somehow
divulge the message. Of course they can. The problem is that copies of
the message are kept in multiple places.

If the recipient is cooperating, that is not an unsolvable problem.
Suppose that the recipient's copy is encrypted with a short lived public
key, and that the recipient voluntarily discards the corresponding
private key after some time. There may well be copies of the bits around
in many places, but nobody would be able to decrypt them. Of course,
this requires that the sender acquires an ephemeral key from the
recipient before sending the message. That may be hard to do in
practice. But it is certainly doable.

--=20
Christian Huitema


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

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>On 8/16/2017 9:43 PM, Phillip Hallam-Baker wrote:<br>
    </p>
    <blockquote
cite="mid:CAMm+LwiT8+oiLwSX_9bekiDY6_3njbW9W_jKnP9FJkRYqwqRcQ@mail.gmail.com"
      type="cite">
      <div class="moz-text-html" lang="x-unicode">
        <div dir="ltr">
          <div class="gmail_default" style="font-size:small">On Wed, Aug
            16, 2017 at 11:47 PM, Deen, Glenn (NBCUniversal) <span
              dir="ltr">&lt;<a moz-do-not-send="true"
                href="mailto:Glenn.Deen@nbcuni.com" target="_blank">Glenn.Deen@nbcuni.com</a>&gt;</span>
            wrote:<br>
          </div>
          <div class="gmail_extra">
            <div class="gmail_quote">
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">The
                key issue is that no method currently in existence can
                defeat a camera taking a picture of the screen.  That
                will always let an authorized receiver make a permanent
                copy of the email and do what they want with it.  Yes,
                you may be throwing away repudiation and signature
                information, but they will have the contents of the
                mail.<br>
              </blockquote>
              <div><br>
              </div>
              <div>
                <div class="gmail_default" style="font-size:small">​
                  Absolutely true. And really serious for some
                  applications. But consider the Game of Thrones hack, a
                  screen capture would be serious, yes. But nowhere near
                  as serious as having the final cut leak in HD.</div>
                <div class="gmail_default" style="font-size:small"><br>
                </div>
                <div class="gmail_default" style="font-size:small">​
                  The kids are using snapchat because their principle
                  security concern is that the receiver will forget to
                  delete the pics they send and they will end up with
                  the parents. They understand full well that they can
                  photograph the screen of one phone with another.</div>
              </div>
              <div class="gmail_default" style="font-size:small"><br>
              </div>
              <div class="gmail_default" style="font-size:small">The
                perfect is the enemy of the good. </div>
              <div> </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    Yes. The threat model here is not that the recipient will somehow
    divulge the message. Of course they can. The problem is that copies
    of the message are kept in multiple places. <br>
    <br>
    If the recipient is cooperating, that is not an unsolvable problem.
    Suppose that the recipient's copy is encrypted with a short lived
    public key, and that the recipient voluntarily discards the
    corresponding private key after some time. There may well be copies
    of the bits around in many places, but nobody would be able to
    decrypt them. Of course, this requires that the sender acquires an
    ephemeral key from the recipient before sending the message. That
    may be hard to do in practice. But it is certainly doable.<br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Christian Huitema</pre>
  </body>
</html>

--------------4CFB2EBEC99B2B438352FD8F--


From nobody Wed Aug 16 23:56:46 2017
Return-Path: <gem@rellim.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95A2C1326D8 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 23:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.207
X-Spam-Level: 
X-Spam-Status: No, score=-1.207 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RDNS_NONE=0.793, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=rellim.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PRU8YlJ7teEw for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 23:56:43 -0700 (PDT)
Received: from spidey.rellim.com (unknown [IPv6:2001:470:e815::19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B1E01326AA for <ietf@ietf.org>; Wed, 16 Aug 2017 23:56:43 -0700 (PDT)
Received: from spidey.rellim.com (rellim.com [IPv6:2001:470:e815:0:0:0:0:19]) (authenticated bits=0) by spidey.rellim.com (8.15.2/8.15.2) with ESMTPSA id v7H6ucM2006283 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <ietf@ietf.org>; Wed, 16 Aug 2017 23:56:43 -0700
DKIM-Filter: OpenDKIM Filter v2.10.3 spidey.rellim.com v7H6ucM2006283
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=rellim.com; s=kong; t=1502953003; bh=skrxMiBOEouRDk69ZeHdAWARmqTitNmOXwsMZtklNx8=; h=Date:From:To:Subject:In-Reply-To:References; b=sxfWUr1WLqujoDcJm8VR4FGYrxp0ZaVoNNytI+LNRUEAvhb3NDmsMZZZCj0dpYTgh YhcWdTbeurgS2FZXg7mWOZmbLIw6Moit8+voTpj25Zsqn80H3BrL0mhWTQ6aPYX0/+ rjGrM6pUJoODjGPflp805GlIWgcr/SlWud2qfa/E=
Date: Wed, 16 Aug 2017 23:56:37 -0700
From: "Gary E. Miller" <gem@rellim.com>
To: ietf@ietf.org
Subject: Re: Scope for self-destructing email?
Message-ID: <20170816235637.02377dad@spidey.rellim.com>
In-Reply-To: <a6492c82-2b16-b087-c554-8ca38c8f5e84@huitema.net>
References: <20170816225637.4431.qmail@ary.lan> <7352544b-8626-fb30-b74f-48b62110b7cf@gmail.com> <39610B4F-8DE6-4E19-A6C8-5FAB882DD524@orthanc.ca> <CAMm+LwgqnPx2VBaoaWuU_YW547oRhQDTo48t4BokcwKqRSO+bw@mail.gmail.com> <F0EECBF6-F48E-425B-A6E8-65E5183FD36E@nbcuni.com> <CAMm+LwiT8+oiLwSX_9bekiDY6_3njbW9W_jKnP9FJkRYqwqRcQ@mail.gmail.com> <a6492c82-2b16-b087-c554-8ca38c8f5e84@huitema.net>
Organization: Rellim
X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/guIk0_mylu7fWAm9+0Imp7D"; protocol="application/pgp-signature"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (spidey.rellim.com [IPv6:2001:470:e815:0:0:0:0:19]); Wed, 16 Aug 2017 23:56:43 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eccR1B7RqhPRx3PvuddzQieXhBA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Aug 2017 06:56:44 -0000

--Sig_/guIk0_mylu7fWAm9+0Imp7D
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Yo Christian!

On Wed, 16 Aug 2017 23:28:25 -0700
Christian Huitema <huitema@huitema.net> wrote:

> If the recipient is cooperating, that is not an unsolvable problem.

It is unsolvable.  Nothing to prevent anyone from taking a screen shot,
cut/pasting, or taking a photo of the email.

Robert Redford had it right: No More Secrets

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem@rellim.com  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can=E2=80=99t measure it, you can=E2=80=99t improve it." - Lord=
 Kelvin

--Sig_/guIk0_mylu7fWAm9+0Imp7D
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

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

iQEzBAEBCAAdFiEENqCjEoytAEAuFCk8DQ7ZSUHRedgFAlmVPiUACgkQDQ7ZSUHR
edhcwwf9F8BzHwdBIjCJqF7zHfstBh7cfNmoLgVLa49u9+DqYb4iEwfYgki5yeoR
QQh1tnyfpFpaBXiXWtQV/7kjSpIzlu80+x68YeNU1dRN9oNwh4xzjEJfRcCy2dCP
1aovs6jOJW8lswxJDUwnwQNX3TJk+gGq9h0p242RMsD1u7ZXL+7Oxh6VUryHQxmK
VqK2lwUR1KUsXJFAUcZiscOGe9xv8MgOBXHNsG2ahXeo/GO3QV5vEdDlk9PR937y
cdmirnTwi7socHKazYumKQUKCbgYl//cRB2xde6Fu65xcKqkdq8mrDCWU1tsLPXa
FedcoCc6VJ3VSdKoxlAQM9S5hbmKIQ==
=ImJM
-----END PGP SIGNATURE-----

--Sig_/guIk0_mylu7fWAm9+0Imp7D--


From nobody Thu Aug 17 00:46:10 2017
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E744132814 for <ietf@ietfa.amsl.com>; Thu, 17 Aug 2017 00:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OS2tyaPvRrbx for <ietf@ietfa.amsl.com>; Thu, 17 Aug 2017 00:46:06 -0700 (PDT)
Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FFCC132813 for <ietf@ietf.org>; Thu, 17 Aug 2017 00:46:06 -0700 (PDT)
Received: by mail-lf0-x22e.google.com with SMTP id t128so26264926lff.2 for <ietf@ietf.org>; Thu, 17 Aug 2017 00:46: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:from:date:message-id:subject:to :cc; bh=Lvsh7CvfqVNjxMuJGCUxcYxkXvasc8mf/pcGLndHxuE=; b=bq4aq3AakTK6pzWgJD72LGmum3I7f3kPTWrHYN/1zUFoOXbbtBSYeDiJiNiiKWp7Th jEpWYMrYgN6BM8favIhyfIgDHE2OLiAp0IhWC1QJwAqybrFCvVTpMNNv/AHP1GLWb3H3 9UIXCCnLjprwFI7lcefghhuqwF6nAe4UlqZaM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Lvsh7CvfqVNjxMuJGCUxcYxkXvasc8mf/pcGLndHxuE=; b=NNNEVXY2pyuwoNFQSsXUU9ZmqnL2tkMGRqd1k+lLeOol2zx3LbAi9KH5QwdsfCokju EFQJEOg31DWcNvyHA/ONvPD93dwsscnp6ejD+ghP995kQI62dwnjwJThlstGvoltJ6wk JkOZ1FB/Xb/brO4Of3S0mzqvX2rXwLJSFV+V5cZZ+lVRcsuzcHHhT4PX3mcQ8toSOfNL SZ/00UIXHej+Z66a2B/ciGBVwMgDWNsEaouZEluibyaY8R4z6yEot9c7aS3PN1ZkjPGJ S3QzGUXn7HSmvyCBu7/m7DGoZy7X5V86UDBKeaRWm2OW3d4ZUoE3QFRrnkj4kexjzebC t+RA==
X-Gm-Message-State: AHYfb5gP8Wr1qoEVNTpQM7XbIOiy85uRXmGIiMg9K3hY+Z1M++m2n863 OQohqJTfAlcjnBQkUjN5WwDZLATMkH30
X-Received: by 10.46.82.1 with SMTP id g1mr1775465ljb.145.1502955964587; Thu, 17 Aug 2017 00:46:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.179.75.130 with HTTP; Thu, 17 Aug 2017 00:46:03 -0700 (PDT)
Received: by 10.179.75.130 with HTTP; Thu, 17 Aug 2017 00:46:03 -0700 (PDT)
In-Reply-To: <CACZ1GiqT6iANkgpDjh-+43pGUY0uEnPdaDnwecBj66S4igTPxA@mail.gmail.com>
References: <CACZ1GiqT6iANkgpDjh-+43pGUY0uEnPdaDnwecBj66S4igTPxA@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
Date: Thu, 17 Aug 2017 08:46:03 +0100
Message-ID: <CAKHUCzyT_ObRPzgTMFpChtvLE+vzBbkWqt7iMqHGL77C2nYxBQ@mail.gmail.com>
Subject: Re: How are S/MIME private keys handled across MUAs?
To: vaibhav singh <vaibhavsinghacads@gmail.com>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113c30ea61f60c0556ee34a5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RPTQ6kMy1chqEdwwFhCxAh7OOTw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Aug 2017 07:46:09 -0000

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

On 16 Aug 2017 19:50, "vaibhav singh" <vaibhavsinghacads@gmail.com> wrote:

Hi,
I was looking at RFCs for S/MIME, and had a question: What if I am logged
into multiple clients(my mobile, a web application, Thunderbird) with an
email account, and I receive an encrypted email?

I can see that the encrypted email would be created with my public key,
and, assuming one public key for one email account, I will have one private
key which I will somehow make use of across all my MUAs. I could not think
of a simple way using which I will be able to sync my private key.

Is there any good way of sharing private keys across clients (maybe some
way of securely syncing files)? How do corporate clients resolve this
issue? Is there an RFC which I may have to refer to?

Another line of thinking; is it possible to create key pairs
(triplets?quadruplets?) wherein there could be multiple private keys
generated for a single public key? And, what about the other way round?


As Russ says, the traditional way of handling this is to encrypt the
private key and send it around each client.

Another way would be to use PRE here (see Phillip Hallam-Baker's link sent
in the other thread), so that the key other people actually get is a Proxy
key, and each client has a proxy-decryptor key of its own - one special
client, with a stronger security stance, would be acting as the Proxy
Admin. There's little practical advantage in this, except that should one
client be compromised, you could revoke just that decryptor key. You do
need the re-encryption key to be held somewhere other than the clients,
though, since otherwise you can obtain the Proxy's private key through a
client compromise.

One thing that really doesn't work well here is if you want to use
hardware-backed cryptography (HSM, smartcards, etc). Here, you'd ideally
use a PRE mechanism again, but one in which the proxy re-encrypted to a
specific key (Phillip Hallam-Baker's scheme will not do this). The closest
I can get here in practical terms is to keep the decryptor keys encrypted
using a HSM-backed private key, which isn't - quite - the same.

Of course, without PRE involved, if you want to use an HSM then you can
only decrypt your email in the one client you have the HSM at, which makes
things logistically frustrating.

Dave.



-- 

Regards,
Vaibhav Singh

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

<div dir=3D"auto"><div><br><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On 16 Aug 2017 19:50, &quot;vaibhav singh&quot; &lt;<a href=3D"ma=
ilto:vaibhavsinghacads@gmail.com">vaibhavsinghacads@gmail.com</a>&gt; wrote=
:<br type=3D"attribution"><blockquote class=3D"quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><d=
iv>Hi,<br></div>I was looking at RFCs for S/MIME, and had a question: What =
if I am logged into multiple clients(my mobile, a web application, Thunderb=
ird) with an email account, and I receive an encrypted email?<br></div><br>=
I can see that the encrypted email would be created with my public key, and=
, assuming one public key for one email account, I will have one private ke=
y which I will somehow make use of across all my MUAs. I could not think of=
 a simple way using which I will be able to sync my private key.<br><br cle=
ar=3D"all"><div><div><div>Is there any good way of sharing private keys acr=
oss clients (maybe some way of securely syncing files)? How do corporate cl=
ients resolve this issue? Is there an RFC which I may have to refer to?<br>=
<br></div><div>Another line of thinking; is it possible to create key pairs=
 (triplets?quadruplets?) wherein there could be multiple private keys gener=
ated for a single public key? And, what about the other way round?</div></d=
iv></div></div></blockquote></div></div></div><div dir=3D"auto"><br></div><=
div dir=3D"auto">As Russ says, the traditional way of handling this is to e=
ncrypt the private key and send it around each client.</div><div dir=3D"aut=
o"><br></div><div dir=3D"auto">Another way would be to use PRE here (see Ph=
illip Hallam-Baker&#39;s link sent in the other thread), so that the key ot=
her people actually get is a Proxy key, and each client has a proxy-decrypt=
or key of its own - one special client, with a stronger security stance, wo=
uld be acting as the Proxy Admin. There&#39;s little practical advantage in=
 this, except that should one client be compromised, you could revoke just =
that decryptor key. You do need the re-encryption key to be held somewhere =
other than the clients, though, since otherwise you can obtain the Proxy&#3=
9;s private key through a client compromise.</div><div dir=3D"auto"><br></d=
iv><div dir=3D"auto">One thing that really doesn&#39;t work well here is if=
 you want to use hardware-backed cryptography (HSM, smartcards, etc). Here,=
 you&#39;d ideally use a PRE mechanism again, but one in which the proxy re=
-encrypted to a specific key (Phillip Hallam-Baker&#39;s scheme will not do=
 this). The closest I can get here in practical terms is to keep the decryp=
tor keys encrypted using a HSM-backed private key, which isn&#39;t - quite =
- the same.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Of course, w=
ithout PRE involved, if you want to use an HSM then you can only decrypt yo=
ur email in the one client you have the HSM at, which makes things logistic=
ally frustrating.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Dave.<=
/div><div dir=3D"auto"><br></div><div dir=3D"auto"><div class=3D"gmail_extr=
a"><div class=3D"gmail_quote"><blockquote class=3D"quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><di=
v><div><div><font color=3D"#888888"><br><br></font></div><font color=3D"#88=
8888"><div>-- <br><div class=3D"m_-813699844928931585gmail_signature" data-=
smartmail=3D"gmail_signature"><div dir=3D"ltr"><div><br></div>Regards,<div>=
Vaibhav Singh</div></div></div>
</div></font></div></div></div>
</blockquote></div><br></div></div></div>

--001a113c30ea61f60c0556ee34a5--


From nobody Thu Aug 17 02:06:46 2017
Return-Path: <dhruv.dhody@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1748E13269C; Thu, 17 Aug 2017 02:06:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vfJK_xvPb-9I; Thu, 17 Aug 2017 02:06:30 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DF54132386; Thu, 17 Aug 2017 02:06:29 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML710-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DMU53567; Thu, 17 Aug 2017 09:06:27 +0000 (GMT)
Received: from BLREML406-HUB.china.huawei.com (10.20.4.43) by LHREML710-CAH.china.huawei.com (10.201.108.33) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 17 Aug 2017 10:06:25 +0100
Received: from BLREML501-MBX.china.huawei.com ([10.20.5.198]) by BLREML406-HUB.china.huawei.com ([10.20.4.43]) with mapi id 14.03.0301.000; Thu, 17 Aug 2017 14:36:12 +0530
From: Dhruv Dhody <dhruv.dhody@huawei.com>
To: Roni Even <ron.even.tlv@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-pce-rfc6006bis.all@ietf.org" <draft-ietf-pce-rfc6006bis.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [Pce] Genart last call review of draft-ietf-pce-rfc6006bis-03
Thread-Topic: [Pce] Genart last call review of draft-ietf-pce-rfc6006bis-03
Thread-Index: AQHTFDrKXuNsUXmJ/0aASYriy6cC9KKIDkRA
Date: Thu, 17 Aug 2017 09:06:12 +0000
Message-ID: <23CE718903A838468A8B325B80962F9B8CBB37A0@blreml501-mbx>
References: <150263205807.26527.8869013927407425945@ietfa.amsl.com>
In-Reply-To: <150263205807.26527.8869013927407425945@ietfa.amsl.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.149.39]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.59955C93.00CB, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: af1ef5618c163fe384c012dbf9167f12
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/biUqd0TdbjQ_vbLVfL9sfzvSLl4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Aug 2017 09:06:32 -0000

Hi Roni,=20

Thanks for your comments. See inline...

> -----Original Message-----
> From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Roni Even
> Sent: 13 August 2017 19:18
> To: gen-art@ietf.org
> Cc: draft-ietf-pce-rfc6006bis.all@ietf.org; pce@ietf.org; ietf@ietf.org
> Subject: [Pce] Genart last call review of draft-ietf-pce-rfc6006bis-03
>=20
> Reviewer: Roni Even
> Review result: Ready with Nits
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area Revie=
w
> Team (Gen-ART) reviews all IETF documents being processed by the IESG for
> the IETF Chair.  Please treat these comments just like any other last cal=
l
> comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-pce-rfc6006bis-??
> Reviewer: Roni Even
> Review Date: 2017-08-13
> IETF LC End Date: 2017-08-24
> IESG Telechat date: 2017-08-31
>=20
> Summary: The document is ready for publication as standard track RFC
>=20
> I read all the document and also did a compare with RFC6006 to look at th=
e
> changes.
>=20
> Major issues:
>=20
> Minor issues:
>=20
> Nits/editorial comments:
>=20
> 1. In section 4.2 I am not sure why is this sentence there, is it for the
> current yang document or for a future one. Why have it at all?-"The PCEP
> YANG module [I-D.ietf-pce-pcep-yang] can be extended to also include the
> P2MP related parameters."
>=20
[[Dhruv Dhody]] The text around MIB existed from RFC6006. Since then the fo=
cus has shifted to Yang.=20
We wanted to keep this text about Yang to reflect that. =20

How about we reword to -=20

   The PCEP YANG model is specified in [I-D.ietf-pce-pcep-yang]. The
   YANG models can be augmented to also include the P2MP related
   parameters.

Thanks again for your review.=20

Regards,
Dhruv

Working Copy - https://github.com/dhruvdhody-huawei/ietf/blob/master/draft-=
ietf-pce-rfc6006bis-04.txt



>=20
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce


From nobody Thu Aug 17 05:25:37 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9404C1323BE for <ietf@ietfa.amsl.com>; Thu, 17 Aug 2017 05:25:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JsFB89ZKZVch for <ietf@ietfa.amsl.com>; Thu, 17 Aug 2017 05:25:33 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 998B113213D for <ietf@ietf.org>; Thu, 17 Aug 2017 05:25:33 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 6DAA0E1FF; Thu, 17 Aug 2017 08:28:14 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 7FE78806D2; Thu, 17 Aug 2017 08:25:32 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "ietf\@ietf.org Discussion" <ietf@ietf.org>, Ted Hardie <ted.ietf@gmail.com>
cc: vaibhav singh <vaibhavsinghacads@gmail.com>
Subject: Re: Scope for self-destructing email?
In-Reply-To: <CA+9kkMAAQh64M59g0Jn=2j0czS6q56-yoOadGMoeVMTZ=4Z72Q@mail.gmail.com>
References: <CACZ1GipivEf31iHchaM1OPFQF4QkfVRGVNsY_vVx=J8oFZ0JZA@mail.gmail.com> <b1289123-04ac-e62b-879e-614fae9b20b0@bogus.com> <CACZ1GiooBdEZ_YcBZPQNFkbT0DsGf-Cu25fPYzWcLamLUAH+TA@mail.gmail.com> <CA+9kkMAAQh64M59g0Jn=2j0czS6q56-yoOadGMoeVMTZ=4Z72Q@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.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-sha256; protocol="application/pgp-signature"
Date: Thu, 17 Aug 2017 08:25:32 -0400
Message-ID: <7877.1502972732@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/l4jtoic51_t1JImvIH-etCtoW5o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Aug 2017 12:25:36 -0000

--=-=-=
Content-Type: text/plain


Ted Hardie <ted.ietf@gmail.com> wrote:
    > The first is providing a facility that declares a particular message to be
    > automatically overcome by events at a particular time, leaving it completely
    > up to the recipient how to process the message based on that metadata. There
    > are simple message types (today's weather, lunch availability, etc.) that
    > could be thus set to be marked OBE when no longer relevant. Some
    > clients

This is an interesting idea.  For those of us who deal with many emails,
(particularly upon return from vacation), not having to deal with lunch plans
that have expired would in fact be nice.

Some of us still deal with cron job output.  An hourly job that fails all
weekend generates a lot of email, and often only the most recent failure is
at all useful to know about.  That's a job for good-old-Usenet Supercedes:,
but that's one email overcoming another, and the whole thing needs
some cryptographic support.  Note that a merkle hash (a la s/key) would
probably suffice.

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




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

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

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlmVizwACgkQgItw+93Q
3WX4aggAmCPXmIMKOC8PcSW+DciU/MgqojXm+NK118YOAd3CsfgFYty2o3P4Rx01
7VtUiC0kyq5PVgCWcUWpDPGjW0QbxqvDIDF4+nPpIcF8K0rLmlPRkC8RSIdhOMRw
/GyrvjQp2rhdHCpG9BgcGfuztIJsIVki0lU0PcALDhpv5dSQTkCPslAJm4S3mbwY
s43fxVeWG779Lr5U2vEhqNpeIBigpysdXoLmxJ2JrbUv1MsqUsaXqFORy80G1GQW
WoZadSQw7GVip8KZ0yIqhg6kf+ej36Ouvo/ILL/p5UhfU4UCM62tCw9FOQpC1MLM
eBu88xiN1pK7dMDpBu1RVHUW0jZIxg==
=IIB2
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Aug 17 06:23:19 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64E3613242A for <ietf@ietfa.amsl.com>; Thu, 17 Aug 2017 06:23:17 -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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jQ-j5orIiRI8 for <ietf@ietfa.amsl.com>; Thu, 17 Aug 2017 06:23:15 -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 9A968132427 for <ietf@ietf.org>; Thu, 17 Aug 2017 06:23:15 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1diKlW-000Ir1-Cm; Thu, 17 Aug 2017 09:23:14 -0400
Date: Thu, 17 Aug 2017 09:23:06 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org, vaibhav singh <vaibhavsinghacads@gmail.com>
Subject: Re: Scope for self-destructing email?
Message-ID: <BA30F5B5AFA6760F140209A3@PSB>
In-Reply-To: <a6492c82-2b16-b087-c554-8ca38c8f5e84@huitema.net>
References: <20170816225637.4431.qmail@ary.lan> <7352544b-8626-fb30-b74f-48b62110b7cf@gmail.com> <39610B4F-8DE6-4E19-A6C8-5FAB882DD524@orthanc.ca> <CAMm+LwgqnPx2VBaoaWuU_YW547oRhQDTo48t4BokcwKqRSO+bw@mail.gmail.com> <F0EECBF6-F48E-425B-A6E8-65E5183FD36E@nbcuni.com> <CAMm+LwiT8+oiLwSX_9bekiDY6_3njbW9W_jKnP9FJkRYqwqRcQ@mail.gmail.com> <a6492c82-2b16-b087-c554-8ca38c8f5e84@huitema.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.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fYk8DCtAPeVoIwlDekIIlLSZDEM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Aug 2017 13:23:17 -0000

Folks,

It seems to me that three things are emerging on this thread.

(1) The original proposal and problem to be solved, at least as
most of us understood it, was to allow a sender to send some
sort of notification that would cause all copies of a message to
be  automagically destroyed.  We appear to have unanimity that
problem is unsolvable, at least in the general case and/or in
the absence of universal trust.

(2) We have considerable experience (in both email and netnew)
with putting out messages with expiry dates as information for
the recipient (whether expected to be acted on automatically or
not).  While there are important exceptions, they have never
been as useful as was apparently assumed when they were
adopted... to the point that the IANA registry entries for the
relevant email header fields identify them as obsolete.  We have
less experience with the originator of an already-sent message
as expired or obsolete, but no evidence has been offered so far
that such a facility would be appreciably more useful than the
"Expires:" header field.

(3) We have now reached the stage in which people seem to be
discussing alternate problems that can be solved.  That isn't
very hard, but those alternate problems are not the original one
and little or no case is being made that the new problems are
worth solving or that solutions would be useful, even if they
are feasible.

It seems to me that, if people believe there is a problem worth
solving and if they think they have a feasible solution, we need
to see an I-D that explains both, rather than continuing to
circle around an ever-expanding collection of possible issues on
the IETF list in the absence of such a draft.

     john


From nobody Thu Aug 17 11:13:26 2017
Return-Path: <fluffy@iii.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 803EF1324D2 for <ietf@ietfa.amsl.com>; Thu, 17 Aug 2017 11:13:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j3pXLvnPqMpU for <ietf@ietfa.amsl.com>; Thu, 17 Aug 2017 11:13:24 -0700 (PDT)
Received: from smtp78.ord1d.emailsrvr.com (smtp78.ord1d.emailsrvr.com [184.106.54.78]) (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 DAA651324C6 for <ietf@ietf.org>; Thu, 17 Aug 2017 11:13:23 -0700 (PDT)
Received: from smtp2.relay.ord1d.emailsrvr.com (localhost [127.0.0.1]) by smtp2.relay.ord1d.emailsrvr.com (SMTP Server) with ESMTP id 2CB7340060; Thu, 17 Aug 2017 14:13:23 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp2.relay.ord1d.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 52D8340079;  Thu, 17 Aug 2017 14:13:22 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [172.20.10.2] ([UNAVAILABLE]. [209.52.88.252]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:25 (trex/5.7.12); Thu, 17 Aug 2017 14:13:23 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_23BD1A4B-47A4-4F53-B179-843B5C9BAAE3"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Opsdir last call review of draft-ietf-rtcweb-jsep-21
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <150293290297.12432.15822575176336895893@ietfa.amsl.com>
Date: Thu, 17 Aug 2017 11:13:20 -0700
Cc: ops-dir@ietf.org, draft-ietf-rtcweb-jsep.all@ietf.org, RTCWeb IETF <rtcweb@ietf.org>, ietf@ietf.org
Message-Id: <65A7933F-39BC-4E21-B5D2-9F9BB61B7ED7@iii.ca>
References: <150293290297.12432.15822575176336895893@ietfa.amsl.com>
To: Carlos Martinez <carlosm3011@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/A4Z8gBxvudeP6jKErU7b9U225Is>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Aug 2017 18:13:25 -0000

--Apple-Mail=_23BD1A4B-47A4-4F53-B179-843B5C9BAAE3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Aug 16, 2017, at 6:21 PM, Carlos Martinez <carlosm3011@gmail.com> =
wrote:
>=20
> Reviewer: Carlos Martinez
> Review result: Ready
>=20
> I have reviewed this document as part of the Operational directorate's =
ongoing
> effort to review all IETF documents being processed by the IESG.  =
These
> comments were written with the intent of improving the operational =
aspects of
> the IETF drafts. Comments that are not addressed in last call may be =
included
> in AD reviews during the IESG review.  Document editors and WG chairs =
should
> treat these comments just like any other last call comments.
>=20
> Noting that I'm certainly not an expert on the subject matter, I've =
found this
> document to be READY. I found it well-written, it contains plenty of =
detailed
> examples (which I believe are really important for API and =
programming-heavy
> documents), and includes plenty of references as well.
>=20
> Please do not forget to remove "Appendix B.  Change log".
>=20
> A minor observation, not even a nit, is that the text in the Security
> Considerations "While formally the JSEP interface is an API, it is =
better to
> think of it is an Internet protocol, with the JS being untrustworthy =
from the
> perspective of the endpoint. " could be more clear.
>=20
> thanks!
>=20
> /Carlos
>=20


Thanks Carlos, I'll have a look at the things you mention ( =
https://github.com/rtcweb-wg/jsep/issues/791 =
<https://github.com/rtcweb-wg/jsep/issues/791> and =
https://github.com/rtcweb-wg/jsep/issues/792 =
<https://github.com/rtcweb-wg/jsep/issues/792> for tracking )


--Apple-Mail=_23BD1A4B-47A4-4F53-B179-843B5C9BAAE3
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;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Aug 16, 2017, at 6:21 PM, Carlos Martinez &lt;<a =
href=3D"mailto:carlosm3011@gmail.com" =
class=3D"">carlosm3011@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">Reviewer: Carlos Martinez<br class=3D"">Review result: =
Ready<br class=3D""><br class=3D"">I have reviewed this document as part =
of the Operational directorate's ongoing<br class=3D"">effort to review =
all IETF documents being processed by the IESG. &nbsp;These<br =
class=3D"">comments were written with the intent of improving the =
operational aspects of<br class=3D"">the IETF drafts. Comments that are =
not addressed in last call may be included<br class=3D"">in AD reviews =
during the IESG review. &nbsp;Document editors and WG chairs should<br =
class=3D"">treat these comments just like any other last call =
comments.<br class=3D""><br class=3D"">Noting that I'm certainly not an =
expert on the subject matter, I've found this<br class=3D"">document to =
be READY. I found it well-written, it contains plenty of detailed<br =
class=3D"">examples (which I believe are really important for API and =
programming-heavy<br class=3D"">documents), and includes plenty of =
references as well.<br class=3D""><br class=3D"">Please do not forget to =
remove "Appendix B. &nbsp;Change log".<br class=3D""><br class=3D"">A =
minor observation, not even a nit, is that the text in the Security<br =
class=3D"">Considerations "While formally the JSEP interface is an API, =
it is better to<br class=3D"">think of it is an Internet protocol, with =
the JS being untrustworthy from the<br class=3D"">perspective of the =
endpoint. " could be more clear.<br class=3D""><br class=3D"">thanks!<br =
class=3D""><br class=3D"">/Carlos<br class=3D""><br =
class=3D""></div></div></blockquote></div><br class=3D""><div =
class=3D""><br class=3D""></div><div class=3D"">Thanks Carlos, I'll have =
a look at the things you mention (&nbsp;<a =
href=3D"https://github.com/rtcweb-wg/jsep/issues/791" =
class=3D"">https://github.com/rtcweb-wg/jsep/issues/791</a>&nbsp;and&nbsp;=
<a href=3D"https://github.com/rtcweb-wg/jsep/issues/792" =
class=3D"">https://github.com/rtcweb-wg/jsep/issues/792</a>&nbsp;for =
tracking )</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_23BD1A4B-47A4-4F53-B179-843B5C9BAAE3--


From nobody Thu Aug 17 12:15:30 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1B0413236E for <ietf@ietfa.amsl.com>; Thu, 17 Aug 2017 12:15:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level: 
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tw-QnuGJXLIS for <ietf@ietfa.amsl.com>; Thu, 17 Aug 2017 12:15:26 -0700 (PDT)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FCD313214D for <ietf@ietf.org>; Thu, 17 Aug 2017 12:15:25 -0700 (PDT)
Received: by mail-lf0-x22b.google.com with SMTP id f7so14048849lfg.4 for <ietf@ietf.org>; Thu, 17 Aug 2017 12:15:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=5V567kDbFL55isFXx/7H6NZu8qifeBojNPjEKGLTFjk=; b=eD0WeHXRv5Kko8fmUBlOSj360ciECNPpjyeZolOR32XSb16XyExdu1oH54xzvKGyv6 FW7rER/8geJXPMxNplZGldp7cBzHfCDNX0m1nVWUyujYvKLlkU+6RV6Tw8FQ87Tov107 2lzQiwi7qmrYiAJIyW7cHl6B4el4hGuNvLIhHBD0HcK7a6vg/b5UkIoapjYPCi3nYHZr Tng0yEVvSWWnET7xD62+r07HToN3SrhJ8Kfug4pRB6uYjb2oa9aPbE08Mc3J8X8tuGDL ZFzwtbFaM8VezwCnswNMjgXjtRwiUBOF5z54cSJtyGSGTMwcnKX0wMxk1lexy5Cpj0ub MNAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=5V567kDbFL55isFXx/7H6NZu8qifeBojNPjEKGLTFjk=; b=azrYQ4Y+uDX/tL2qDUORR5LZZUYw3amA+fjrlKgIxuVQ9llKsIUNRLoSrrl4b+UrSx 7jhs3/welxEmOlJE7iFpBXYzlB/QaGdg6WklYXu7mZfm8WyKSlqo72RIl67WckUQEpKb 1BMZYJ0cprNKyWEadDEYonbFuWTeBO4ERE3tU3fAW0K9+PAxQuF0Y2Knz4zEahzUDtYC fuu/6gyvr+bYLvuRgUwRI0caWJqTAyBccyUj4jgjTlalWKEmroeVmVTWDGb3oc41v9L8 MZv1VnRO0ZdFCujt7GXsOrjCLeCPYJls4w3/IXMZzwd2qBQ73XNhC3ZFsK+QCPOkiTo5 vL9w==
X-Gm-Message-State: AHYfb5hkoF3ySCfeimqwFPArKVQF7Xl75CoYVX8uL2c9veT20rvwk034 RX9vA5sXYcxln4jylbIiF4LsKFgvHQ==
X-Received: by 10.25.79.5 with SMTP id d5mr2053892lfb.160.1502997323899; Thu, 17 Aug 2017 12:15:23 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.25.142.199 with HTTP; Thu, 17 Aug 2017 12:15:22 -0700 (PDT)
In-Reply-To: <BA30F5B5AFA6760F140209A3@PSB>
References: <20170816225637.4431.qmail@ary.lan> <7352544b-8626-fb30-b74f-48b62110b7cf@gmail.com> <39610B4F-8DE6-4E19-A6C8-5FAB882DD524@orthanc.ca> <CAMm+LwgqnPx2VBaoaWuU_YW547oRhQDTo48t4BokcwKqRSO+bw@mail.gmail.com> <F0EECBF6-F48E-425B-A6E8-65E5183FD36E@nbcuni.com> <CAMm+LwiT8+oiLwSX_9bekiDY6_3njbW9W_jKnP9FJkRYqwqRcQ@mail.gmail.com> <a6492c82-2b16-b087-c554-8ca38c8f5e84@huitema.net> <BA30F5B5AFA6760F140209A3@PSB>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 17 Aug 2017 15:15:22 -0400
X-Google-Sender-Auth: duOEAEV6V3vHhubxwQ_akw9nvbo
Message-ID: <CAMm+Lwh8HEgWCzgWieM09FsuBhHc+v1K-n4TKqyR6UvS17ha5Q@mail.gmail.com>
Subject: Re: Scope for self-destructing email?
To: John C Klensin <john-ietf@jck.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>, vaibhav singh <vaibhavsinghacads@gmail.com>
Content-Type: multipart/alternative; boundary="94eb2c1cdafe96e91a0556f7d5d1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WSnmKyvpPILXtKODurwupK80OKk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Aug 2017 19:15:29 -0000

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

On Thu, Aug 17, 2017 at 9:23 AM, John C Klensin <john-ietf@jck.com> wrote:

> Folks,
>
> It seems to me that three things are emerging on this thread.
>
> (1) The original proposal and problem to be solved, at least as
> most of us understood it, was to allow a sender to send some
> sort of notification that would cause all copies of a message to
> be  automagically destroyed.  We appear to have unanimity that
> problem is unsolvable, at least in the general case and/or in
> the absence of universal trust.
>

=E2=80=8BIt is agreed that it is impossible to solve without trustworthy ha=
rdware.

The only thing that has stopped me adding such a feature to Mesh/Message
has been that there is a dense thicket of IPR covering such techniques and
I have not read it.

If the next President of the US was to come to me and ask if I could
provide a mechanism that would allow her to send an email message to
members of her cabinet and that supported a 'recall' feature, I would have
no hesitation in saying yes, conditional on some technical support which
Microsoft and Apple and some others are both capable of providing.

If she then said, 'What about adding the UK Prime Minister', I would answer
no.
=E2=80=8B


> (2) We have considerable experience (in both email and netnew)
> with putting out messages with expiry dates as information for
> the recipient (whether expected to be acted on automatically or
> not).  While there are important exceptions, they have never
> been as useful as was apparently assumed when they were
> adopted... to the point that the IANA registry entries for the
> relevant email header fields identify them as obsolete.


=E2=80=8BThat might be because they were never implemented sufficiently wid=
ely. I
can turn off send receipts for example.

Another issue is that SMTP is a push service, not a pull service. For
Mesh/Message, I want to provide a superset of the capabilities of dropbox
like mail and SMTP like mail. So my basic scheme is:

When the mail is sent: Store the message on the sending server, send a
notification to the receiving server.

If the message is less than the receiving server size limit (varies by
sender), forward the body of the message after x minutes.

The reason for this is that most of the times I want to recall a message,
it is because I want to add the #Q$%%* attachment or correct the spelling
mistake.


(3) We have now reached the stage in which people seem to be
> discussing alternate problems that can be solved.  That isn't
> very hard, but those alternate problems are not the original one
> and little or no case is being made that the new problems are
> worth solving or that solutions would be useful, even if they
> are feasible.
>
> It seems to me that, if people believe there is a problem worth
> solving and if they think they have a feasible solution, we need
> to see an I-D that explains both, rather than continuing to
> circle around an ever-expanding collection of possible issues on
> the IETF list in the absence of such a draft.


=E2=80=8BWell I have released 6 drafts this week and I am currently working=
 on
another 3...

I don't think it is a problem that is solvable within the framework of
SMTP. It is a problem that can only be solved in the context of a new
messaging infrastructure in which every user supports the capability by
default. Such infrastructures have been successful in the recent past, see
Snapchat. Sure, they are wobbling a little now. But they have more users
than S/MIME, OpenPGP, IPSEC and SSH combined.
=E2=80=8B

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">On =
Thu, Aug 17, 2017 at 9:23 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></div><div class=3D"gmail_extra"><div class=3D"gmail_quote"=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">Folks,<br>
<br>
It seems to me that three things are emerging on this thread.<br>
<br>
(1) The original proposal and problem to be solved, at least as<br>
most of us understood it, was to allow a sender to send some<br>
sort of notification that would cause all copies of a message to<br>
be=C2=A0 automagically destroyed.=C2=A0 We appear to have unanimity that<br=
>
problem is unsolvable, at least in the general case and/or in<br>
the absence of universal trust.<br></blockquote><div><br></div><div><div cl=
ass=3D"gmail_default" style=3D"font-size:small">=E2=80=8BIt is agreed that =
it is impossible to solve without trustworthy hardware.</div><div class=3D"=
gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_defa=
ult" style=3D"font-size:small">The only thing that has stopped me adding su=
ch a feature to Mesh/Message has been that there is a dense thicket of IPR =
covering such techniques and I have not read it.</div><div class=3D"gmail_d=
efault" style=3D"font-size:small"><br></div><div class=3D"gmail_default" st=
yle=3D"font-size:small">If the next President of the US was to come to me a=
nd ask if I could provide a mechanism that would allow her to send an email=
 message to members of her cabinet and that supported a &#39;recall&#39; fe=
ature, I would have no hesitation in saying yes, conditional on some techni=
cal support which Microsoft and Apple and some others are both capable of p=
roviding.</div><div class=3D"gmail_default" style=3D"font-size:small"><br><=
/div><div class=3D"gmail_default" style=3D"font-size:small">If she then sai=
d, &#39;What about adding the UK Prime Minister&#39;, I would answer no.</d=
iv><div class=3D"gmail_default" style=3D"font-size:small">=E2=80=8B</div></=
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">
(2) We have considerable experience (in both email and netnew)<br>
with putting out messages with expiry dates as information for<br>
the recipient (whether expected to be acted on automatically or<br>
not).=C2=A0 While there are important exceptions, they have never<br>
been as useful as was apparently assumed when they were<br>
adopted... to the point that the IANA registry entries for the<br>
relevant email header fields identify them as obsolete.=C2=A0 </blockquote>=
<div><br></div><div><div class=3D"gmail_default" style=3D"font-size:small">=
=E2=80=8BThat might be because they were never implemented sufficiently wid=
ely. I can turn off send receipts for example.</div><div class=3D"gmail_def=
ault" style=3D"font-size:small"><br></div><div class=3D"gmail_default" styl=
e=3D"font-size:small">Another issue is that SMTP is a push service, not a p=
ull service. For Mesh/Message, I want to provide a superset of the capabili=
ties of dropbox like mail and SMTP like mail. So my basic scheme is:</div><=
div class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=
=3D"gmail_default" style=3D"font-size:small">When the mail is sent: Store t=
he message on the sending server, send a notification to the receiving serv=
er.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></div><=
div class=3D"gmail_default" style=3D"font-size:small">If the message is les=
s than the receiving server size limit (varies by sender), forward the body=
 of the message after x minutes.</div><div class=3D"gmail_default" style=3D=
"font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size=
:small">The reason for this is that most of the times I want to recall a me=
ssage, it is because I want to add the #Q$%%* attachment or correct the spe=
lling mistake.=C2=A0<br></div><div class=3D"gmail_default" style=3D"font-si=
ze:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small">=
<br></div></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
(3) We have now reached the stage in which people seem to be<br>
discussing alternate problems that can be solved.=C2=A0 That isn&#39;t<br>
very hard, but those alternate problems are not the original one<br>
and little or no case is being made that the new problems are<br>
worth solving or that solutions would be useful, even if they<br>
are feasible.<br>
<br>
It seems to me that, if people believe there is a problem worth<br>
solving and if they think they have a feasible solution, we need<br>
to see an I-D that explains both, rather than continuing to<br>
circle around an ever-expanding collection of possible issues on<br>
the IETF list in the absence of such a draft.</blockquote><div><br></div><d=
iv class=3D"gmail_default" style=3D"font-size:small">=E2=80=8BWell I have r=
eleased 6 drafts this week and I am currently working on another 3...</div>=
<div class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=
=3D"gmail_default" style=3D"font-size:small">I don&#39;t think it is a prob=
lem that is solvable within the framework of SMTP. It is a problem that can=
 only be solved in the context of a new messaging infrastructure in which e=
very user supports the capability by default. Such infrastructures have bee=
n successful in the recent past, see Snapchat. Sure, they are wobbling a li=
ttle now. But they have more users than S/MIME, OpenPGP, IPSEC and SSH comb=
ined.</div><div class=3D"gmail_default" style=3D"font-size:small">=E2=80=8B=
</div></div><br></div></div>

--94eb2c1cdafe96e91a0556f7d5d1--


From nobody Thu Aug 17 13:02:34 2017
Return-Path: <a.arsenault.81@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBDBB132063 for <ietf@ietfa.amsl.com>; Thu, 17 Aug 2017 06:59:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T_JCpGH5NYt1 for <ietf@ietfa.amsl.com>; Thu, 17 Aug 2017 06:59:35 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45C7C126BFD for <ietf@ietf.org>; Thu, 17 Aug 2017 06:59:35 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id m88so23145098iod.2 for <ietf@ietf.org>; Thu, 17 Aug 2017 06:59:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NQKKS4ChuPfXmaeA8sRg7ADA7IlgT4PpKO5yXiki5CM=; b=XfPTbHqJJCdz+7rDu4MZbns8Tzv9imv0SqJGsbMNwffuA7ZhTZO/GQ72Xzk/LFkojQ 2Xfehdf89vdT4WC1HhE+00oEtloLVpPiyTgtFhXIN/IN5jEUqaUhgWxL4I+kMdgqEq+p ExaJCFTayhvZYtsY3QrWtt7a70+gRoN58ztm9rpOZJQTUPeJrg0GjKALiAL2THzKKS8O g0wwvaF5YlqsjVjFS4cyLzlj5hYYoK3zPsCBaiUg3w5YxQAwopT/d69e5Y59pTZ9LBwJ WFE6SraUZOeu4P0NMCri5bE0N87/2e5qEeO6ArQO7Kd54+VCHUvYE3ddFuqTqhkW8av9 lyVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NQKKS4ChuPfXmaeA8sRg7ADA7IlgT4PpKO5yXiki5CM=; b=q9XgRZ3DqHCBFS1Dd8MC3NQDAn0U1EGDQO7BPziEg2thwgrbKk2PvziJs6lTmcz2cL 0NiQuH5UikPNBg+zq9Xjg72QzQVf1Wkhvru/g+pr8oeqViClB+WuirYt/YvWXR/TVCR6 VqYsHM8gbb8LWlib8FCLz0o/xFYGabIdIGMPZzo0sWsrNXH6neVk+M4G0K/47C6KI3y0 3dwDGDiKw1zaHn8JheLWZMv6eJfjJ4NX7+cYx40j+hECxLkKbi9VlWUDlACtzEjRz761 8HKbMemDJwbZQPmh7z6tU3Q4QmnpBeLNU0xCTsoX7y2hdIgPOV1rUdR0yd/MJ/5dHIHx zCyA==
X-Gm-Message-State: AHYfb5gsqNTL+T07YIuItCi4njcopihxZxjQ5pIiAbFradfFKnlDtCVI zNDaRc5RlCArJwU9qnlISePsVWCNHA==
X-Received: by 10.107.132.148 with SMTP id o20mr5276048ioi.296.1502978374721;  Thu, 17 Aug 2017 06:59:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.8.67 with HTTP; Thu, 17 Aug 2017 06:59:33 -0700 (PDT)
In-Reply-To: <CAKHUCzyT_ObRPzgTMFpChtvLE+vzBbkWqt7iMqHGL77C2nYxBQ@mail.gmail.com>
References: <CACZ1GiqT6iANkgpDjh-+43pGUY0uEnPdaDnwecBj66S4igTPxA@mail.gmail.com> <CAKHUCzyT_ObRPzgTMFpChtvLE+vzBbkWqt7iMqHGL77C2nYxBQ@mail.gmail.com>
From: Al Arsenault <a.arsenault.81@gmail.com>
Date: Thu, 17 Aug 2017 09:59:33 -0400
Message-ID: <CAEC7viCi6LBi4FU08M_n4x6bt7sp5E9Mdyi8L1u2GkKzbdLzMw@mail.gmail.com>
Subject: Re: How are S/MIME private keys handled across MUAs?
To: Dave Cridland <dave@cridland.net>
Cc: vaibhav singh <vaibhavsinghacads@gmail.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113f396a2165950556f36c08"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FiMxEgmdoSXSJFFsY_noLgd3AJ0>
X-Mailman-Approved-At: Thu, 17 Aug 2017 13:02:33 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Aug 2017 13:59:38 -0000

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

It's a decade in the past, but the entire SACRED working group was
established to address this exact problem.  See e.g. RFC 3767.
https://www.rfc-editor.org/rfc/rfc3767.txt

On Thu, Aug 17, 2017 at 3:46 AM, Dave Cridland <dave@cridland.net> wrote:

>
>
> On 16 Aug 2017 19:50, "vaibhav singh" <vaibhavsinghacads@gmail.com> wrote:
>
> Hi,
> I was looking at RFCs for S/MIME, and had a question: What if I am logged
> into multiple clients(my mobile, a web application, Thunderbird) with an
> email account, and I receive an encrypted email?
>
> I can see that the encrypted email would be created with my public key,
> and, assuming one public key for one email account, I will have one private
> key which I will somehow make use of across all my MUAs. I could not think
> of a simple way using which I will be able to sync my private key.
>
> Is there any good way of sharing private keys across clients (maybe some
> way of securely syncing files)? How do corporate clients resolve this
> issue? Is there an RFC which I may have to refer to?
>
> Another line of thinking; is it possible to create key pairs
> (triplets?quadruplets?) wherein there could be multiple private keys
> generated for a single public key? And, what about the other way round?
>
>
> As Russ says, the traditional way of handling this is to encrypt the
> private key and send it around each client.
>
> Another way would be to use PRE here (see Phillip Hallam-Baker's link sent
> in the other thread), so that the key other people actually get is a Proxy
> key, and each client has a proxy-decryptor key of its own - one special
> client, with a stronger security stance, would be acting as the Proxy
> Admin. There's little practical advantage in this, except that should one
> client be compromised, you could revoke just that decryptor key. You do
> need the re-encryption key to be held somewhere other than the clients,
> though, since otherwise you can obtain the Proxy's private key through a
> client compromise.
>
> One thing that really doesn't work well here is if you want to use
> hardware-backed cryptography (HSM, smartcards, etc). Here, you'd ideally
> use a PRE mechanism again, but one in which the proxy re-encrypted to a
> specific key (Phillip Hallam-Baker's scheme will not do this). The closest
> I can get here in practical terms is to keep the decryptor keys encrypted
> using a HSM-backed private key, which isn't - quite - the same.
>
> Of course, without PRE involved, if you want to use an HSM then you can
> only decrypt your email in the one client you have the HSM at, which makes
> things logistically frustrating.
>
> Dave.
>
>
>
> --
>
> Regards,
> Vaibhav Singh
>
>
>

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

<div dir=3D"ltr">It&#39;s a decade in the past, but the entire SACRED worki=
ng group was established to address this exact problem.=C2=A0 See e.g. RFC =
3767. <a href=3D"https://www.rfc-editor.org/rfc/rfc3767.txt">https://www.rf=
c-editor.org/rfc/rfc3767.txt</a><span></span></div><div class=3D"gmail_extr=
a"><br><div class=3D"gmail_quote">On Thu, Aug 17, 2017 at 3:46 AM, Dave Cri=
dland <span dir=3D"ltr">&lt;<a href=3D"mailto:dave@cridland.net" target=3D"=
_blank">dave@cridland.net</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex"><div dir=3D"auto"><span><div><br><div class=3D"gmail_extra"><br><div=
 class=3D"gmail_quote">On 16 Aug 2017 19:50, &quot;vaibhav singh&quot; &lt;=
<a href=3D"mailto:vaibhavsinghacads@gmail.com" target=3D"_blank">vaibhavsin=
ghacads@gmail.com</a>&gt; wrote:<br type=3D"attribution"><blockquote class=
=3D"m_659269433367224101quote" style=3D"margin:0px 0px 0px 0.8ex;padding-le=
ft:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left=
-style:solid"><div dir=3D"ltr"><div><div>Hi,<br></div>I was looking at RFCs=
 for S/MIME, and had a question: What if I am logged into multiple clients(=
my mobile, a web application, Thunderbird) with an email account, and I rec=
eive an encrypted email?<br></div><br>I can see that the encrypted email wo=
uld be created with my public key, and, assuming one public key for one ema=
il account, I will have one private key which I will somehow make use of ac=
ross all my MUAs. I could not think of a simple way using which I will be a=
ble to sync my private key.<br><br clear=3D"all"><div><div><div>Is there an=
y good way of sharing private keys across clients (maybe some way of secure=
ly syncing files)? How do corporate clients resolve this issue? Is there an=
 RFC which I may have to refer to?<br><br></div><div>Another line of thinki=
ng; is it possible to create key pairs (triplets?quadruplets?) wherein ther=
e could be multiple private keys generated for a single public key? And, wh=
at about the other way round?</div></div></div></div></blockquote></div></d=
iv></div><div dir=3D"auto"><br></div></span><div dir=3D"auto">As Russ says,=
 the traditional way of handling this is to encrypt the private key and sen=
d it around each client.</div><div dir=3D"auto"><br></div><div dir=3D"auto"=
>Another way would be to use PRE here (see Phillip Hallam-Baker&#39;s link =
sent in the other thread), so that the key other people actually get is a P=
roxy key, and each client has a proxy-decryptor key of its own - one specia=
l client, with a stronger security stance, would be acting as the Proxy Adm=
in. There&#39;s little practical advantage in this, except that should one =
client be compromised, you could revoke just that decryptor key. You do nee=
d the re-encryption key to be held somewhere other than the clients, though=
, since otherwise you can obtain the Proxy&#39;s private key through a clie=
nt compromise.</div><div dir=3D"auto"><br></div><div dir=3D"auto">One thing=
 that really doesn&#39;t work well here is if you want to use hardware-back=
ed cryptography (HSM, smartcards, etc). Here, you&#39;d ideally use a PRE m=
echanism again, but one in which the proxy re-encrypted to a specific key (=
Phillip Hallam-Baker&#39;s scheme will not do this). The closest I can get =
here in practical terms is to keep the decryptor keys encrypted using a HSM=
-backed private key, which isn&#39;t - quite - the same.</div><div dir=3D"a=
uto"><br></div><div dir=3D"auto">Of course, without PRE involved, if you wa=
nt to use an HSM then you can only decrypt your email in the one client you=
 have the HSM at, which makes things logistically frustrating.</div><div di=
r=3D"auto"><br></div><div dir=3D"auto">Dave.</div><div dir=3D"auto"><br></d=
iv><div dir=3D"auto"><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
<blockquote class=3D"m_659269433367224101quote" style=3D"margin:0px 0px 0px=
 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-widt=
h:1px;border-left-style:solid"><div dir=3D"ltr"><div><div><div><font color=
=3D"#888888"><br><span class=3D"HOEnZb"><font color=3D"#888888"><br></font>=
</span></font></div><span class=3D"HOEnZb"><font color=3D"#888888"><font co=
lor=3D"#888888"><div>-- <br><div class=3D"m_659269433367224101m_-8136998449=
28931585gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr=
"><div><br></div>Regards,<div>Vaibhav Singh</div></div></div>
</div></font></font></span></div></div></div>
</blockquote></div><br></div></div></div>
</blockquote></div><br></div>

--001a113f396a2165950556f36c08--


From nobody Thu Aug 17 18:31:04 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CB6813270D for <ietf@ietfa.amsl.com>; Thu, 17 Aug 2017 18:31:02 -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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18eVXezq6dBs for <ietf@ietfa.amsl.com>; Thu, 17 Aug 2017 18:31:00 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67C9E1326E1 for <ietf@ietf.org>; Thu, 17 Aug 2017 18:31:00 -0700 (PDT)
Received: (qmail 11823 invoked from network); 18 Aug 2017 01:30:59 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 18 Aug 2017 01:30:59 -0000
Date: 18 Aug 2017 01:30:37 -0000
Message-ID: <20170818013037.6784.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Cc: mcr+ietf@sandelman.ca
Subject: Re: Scope for self-destructing email?
In-Reply-To: <7877.1502972732@obiwan.sandelman.ca>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pBHlP4nMWxrj2z56hb_PCEDEljA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 18 Aug 2017 01:31:02 -0000

In article <7877.1502972732@obiwan.sandelman.ca> you write:
>This is an interesting idea.  For those of us who deal with many emails,
>(particularly upon return from vacation), not having to deal with lunch plans
>that have expired would in fact be nice.

See RFC 2156 and RFC 4021, section 2.1.50.  To me the interesting
question is why, since we've had Expires: for 20 years, nobody uses it
outside of netnews.

> That's a job for good-old-Usenet Supersedes:,
>but that's one email overcoming another, and the whole thing needs
>some cryptographic support.  Note that a merkle hash (a la s/key) would
>probably suffice.

Seems like overkill.  How about you pay attention to the Supersedes:
(see RFC 2156 and RFC 4021, section 2.1.46) if old and new messages
both have DKIM signatures from the same domain?  Same question about
why after 20 years nobody uses it outside of netnews.

R's,
John


From nobody Fri Aug 18 07:02:35 2017
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B1AF132410 for <ietf@ietfa.amsl.com>; Fri, 18 Aug 2017 07:02:33 -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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PA_ei2WEIioX for <ietf@ietfa.amsl.com>; Fri, 18 Aug 2017 07:02:31 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (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 AE8831323FB for <ietf@ietf.org>; Fri, 18 Aug 2017 07:02:31 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QI1PWH54LC00JG4A@mauve.mrochek.com> for ietf@ietf.org; Fri, 18 Aug 2017 06:57:27 -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 <01QHZD17PFNK0000D4@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 18 Aug 2017 06:57:23 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Cc: ietf@ietf.org, mcr+ietf@sandelman.ca
Message-id: <01QI1PWF7K8S0000D4@mauve.mrochek.com>
Date: Fri, 18 Aug 2017 06:53:17 -0700 (PDT)
Subject: Re: Scope for self-destructing email?
In-reply-to: "Your message dated Fri, 18 Aug 2017 01:30:37 +0000" <20170818013037.6784.qmail@ary.lan>
References: <7877.1502972732@obiwan.sandelman.ca> <20170818013037.6784.qmail@ary.lan>
To: John Levine <johnl@taugh.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wBmHi2mhMa2hY690GCljK6v-bkY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 18 Aug 2017 14:02:33 -0000

> In article <7877.1502972732@obiwan.sandelman.ca> you write:
> >This is an interesting idea.  For those of us who deal with many emails,
> >(particularly upon return from vacation), not having to deal with lunch plans
> >that have expired would in fact be nice.

> See RFC 2156 and RFC 4021, section 2.1.50.  To me the interesting
> question is why, since we've had Expires: for 20 years, nobody uses it
> outside of netnews.

More like 30+ years. See RFC 841, section 3.2.5, also X.400-1984.

> > That's a job for good-old-Usenet Supersedes:,
> >but that's one email overcoming another, and the whole thing needs
> >some cryptographic support.  Note that a merkle hash (a la s/key) would
> >probably suffice.

> Seems like overkill.  How about you pay attention to the Supersedes:
> (see RFC 2156 and RFC 4021, section 2.1.46) if old and new messages
> both have DKIM signatures from the same domain?  Same question about
> why after 20 years nobody uses it outside of netnews.

And if you want to explore the cryprographic side of this, there's an
extensive literature. A good place to start is Radia Perlman's "The Ephemerizer
- Making Data Disappear".

				Ned


From nobody Fri Aug 18 09:44:18 2017
Return-Path: <daniel.migault@ericsson.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CB1CB132A13; Fri, 18 Aug 2017 09:43:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Daniel Migault <daniel.migault@ericsson.com>
To: <secdir@ietf.org>
Cc: draft-ietf-homenet-dot.all@ietf.org, homenet@ietf.org, ietf@ietf.org
Subject: Secdir last call review of draft-ietf-homenet-dot-12
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150307463977.14156.2178189421671973906@ietfa.amsl.com>
Date: Fri, 18 Aug 2017 09:43:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2yQp6J10XosNbWdmNvmkbcc3f7Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 18 Aug 2017 16:44:00 -0000

Reviewer: Daniel Migault
Review result: Has Nits

Thank you for writing the draft. Please find my comments. I hope there are helpful. 

Yours, 
Daniel  

                    Special Use Domain 'home.arpa.'
                       draft-ietf-homenet-dot-12

Abstract

   This document specifies the behavior that is expected from the Domain
   Name System with regard to DNS queries for names ending with
   '.home.arpa.', and designates this domain as a special-use domain
   name. 'home.arpa.' is designated for non-unique use in residential
   home networks.  Home Networking Control Protocol (HNCP) is updated to
   use the 'home.arpa.' domain instead of '.home'.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%      
MGLT: I would personally start by saying the document defines a
 special-use domain name and then defines the behavior. 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%      


   
Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 11, 2018.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of



Pfister & Lemon         Expires February 11, 2018               [Page 1]

Internet-Draft                 dot homenet                   August 2017


   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  General Guidance  . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Domain Name Reservation Considerations  . . . . . . . . . . .   3
   5.  Updates to Home Networking Control Protocol . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  Delegation of 'home.arpa.'  . . . . . . . . . . . . . . . . .   7
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   7
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     10.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Users and devices within a home network (hereafter "homenet") require
   devices and services to be identified by names that are unique within
   the boundaries of the homenet [RFC7368].  The naming mechanism needs
   to function without configuration from the user.  While it may be
   possible for a name to be delegated by an ISP, homenets must also
   function in the absence of such a delegation.  A default name with a
   scope limited to each individual homenet needs to be used.

   This document corrects an error in [RFC7788], replacing '.home' with
   'home.arpa.' as the default domain-name for homenets. '.home' had
   been selected as the most user-friendly option.  However, there are
   existing uses of '.home' that may be in conflict with this use:
   evidence indicates that '.home' queries frequently leak out and reach
   the root name servers [ICANN1] [ICANN2].

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   
 MGLT: I believe that more important than the leak is that the 
 introduction of .home in the root zone has been identified as
 highly risky. Another reason for not adopting it are also some
 uncertainty about its introduction into the root zone.    
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   

   In addition, it's necessary, for compatibility with DNSSEC
   (Section 6), that an insecure delegation ([RFC4035] section 4.3) be
   present for the name.  There is an existing process for allocating
   names under '.arpa' [RFC3172].  No such process is available for
   requesting a similar delegation in the root at the request of the
   IETF, which does not administer that zone.  As a result, the use of
   '.home' is deprecated.

   This document registers the domain '.home.arpa.' as a special-use
   domain name [RFC6761] and specifies the behavior that is expected
   from the Domain Name System with regard to DNS queries for names
   whose rightmost non-terminal labels are 'home.arpa.'.  Queries for



Pfister & Lemon         Expires February 11, 2018               [Page 2]

Internet-Draft                 dot homenet                   August 2017


   names ending with '.home.arpa.' are of local significance within the
   scope of a homenet, meaning that identical queries will result in
   different results from one homenet to another.  In other words, a
   name ending in 'home.arpa.' is not globally unique.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   
MGLT: I think the text mentioned in the beginning of the paragraph 
above should be in the abstract. That was the sense of my previous
comment. 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%      

   Although this document makes specific reference to RFC7788, it is not
   intended that the use of 'home.arpa.' be restricted solely to
   networks where HNCP is deployed; it is rather the case that
   'home.arpa.' is the correct domain for uses like the one described
   for '.home' in RFC7788: local name service in residential homenets.

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

3.  General Guidance

   The domain name '.home.arpa.' is to be used for naming within
   residential homenets.  Names ending with '.home.arpa.' reference a
   locally-served zone, the contents of which are unique only to a
   particular homenet, and are not globally unique.  Such names refer to
   nodes and/or services that are located within a homenet (e.g., a
   printer, or a toaster).

   DNS queries for names ending with '.home.arpa.' are resolved using
   local resolvers on the homenet.  Such queries MUST NOT be recursively
   forwarded to servers outside the logical boundaries of the homenet.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   
MGLT: "local resolvers" seems to me mis-leading. Your resolver may
be local but still forward the query to the Global Internet. I do
not see better ways to say it other than inside the boundaries of
the homenet. Maybe we could say:   
   
   DNS queries for names ending with '.home.arpa.' are resolved using
   homenet specific resolution mechanisms. 

Eventually an informational reference to the simple naming 
architecture may be added so the reader can refer to the doc
for further information. For full disclosure Ted and I are
co-authors.  
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   
   
   Some service discovery user interfaces that are expected to be used
   on homenets conceal information such as domain names from end users.
   However, it is still expected that in some cases, users will need to
   see, remember, and even type, names ending with 'home.arpa.'.  It is
   therefore desirable that users identify the domain and understand
   that using it expresses the intention to connect to a service that is
   specific to the homenet to which they are connected.  Enforcing the
   fulfillment of this intention is out of scope for this document.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   
MGLT: I have difficulties understanding the paragraph above. If 
the idea is to say home.arpa has special meaning that should be
considered by GUIs I would propose the following ordering.

It is
   therefore desirable that users identify the domain and understand
   that using it expresses the intention to connect to a service that is
   specific to the homenet to which they are connected. 
 Some service discovery user interfaces that are expected to be used
   on homenets conceal information such as domain names from end users.
   However, it is still expected that in some cases, users will need to
   see, remember, and even type, names ending with 'home.arpa.'.  
 Enforcing the
   fulfillment of this intention is out of scope for this document.   
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   

   
4.  Domain Name Reservation Considerations

   This section defines the behavior of systems involved in domain name
   resolution when resolving queries for names ending with '.home.arpa.'
   (as per [RFC6761]).





Pfister & Lemon         Expires February 11, 2018               [Page 3]

Internet-Draft                 dot homenet                   August 2017


   1.  Users can use names ending with '.home.arpa.' just as they would
       use any other domain name.  The 'home.arpa.' name is chosen to be
       readily recognized by users as signifying that the name is
       addressing a service on the homenet to which the user's device is
       connected.

   2.  Application software SHOULD NOT treat names ending in
       'home.arpa.' differently than other names.  In particular, there
       is no basis for trusting names that are subdomains of
       'home.arpa.' (see Section 6).

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   
MGLT: a domain name ending in home.arpa may be resolved differently
that a regular domain name. As a result a different treatment is 
applied. I think that "treat" means that no special meaning - other
that the domain name is inside the homenet boundaries - should be 
associated to a home.arpa. If I am correct I would limit the 
consideration to the name rather then the application. 
I would suggest the text below:
	
names ending in home.arpa SHOULD NOT be associated any other 
properties than the affiliation to the homenet. In particular, there
       is no basis for trusting names that are subdomains of
       'home.arpa.' (see Section 6).
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   
	
	   
   3.  Name resolution APIs and libraries MUST NOT recognize names that
       end in '.home.arpa.' as special and MUST NOT treat them
       differently.  Name resolution APIs MUST send queries for such
       names to a recursive DNS server that is configured to be
       authoritative for the 'home.arpa.' zone appropriate to the
       homenet.  

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   
MGLT: I believe the text below does not concern the library but 
the resolver. It is different to say libraries MUST NOT have 
specific considerations for home.arpa than a resolution service 
that may use different libraries MUST NOT consider the home.arpa
differently. 
My understanding of the text below is that the resolver and the
authoritative server for the home.arpa MUST be co-located. The
reasons I think this is not exact is that resolution for 
home.arpa can also be provided by other mechanisms than an 
authoritative server. Typically, resolution can be done by 
requesting Authoritative Servers, Advertising Proxies, Hybrid 
Proxies (now called Discovery Proxies)....
The other reason is do not see the text below accurate is that
you may have a DNS Proxy that transparently to the end user split
the resolution between homenet specific resolutions when home.arpa
is encountered while other names are sent to the ISP resolver.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   

  
	   
	   One or more IP addresses for recursive DNS servers will
       usually be supplied to the client through router advertisements
       or DHCP.  If a host is configured to use a resolver other than
       one that is authoritative for the appropriate 'home.arpa.' zone,
       the client may be unable to resolve, or may receive incorrect
       results for, names in sub domains of 'home.arpa.'.

   4.  Caching resolvers conforming to this specification MUST support
       DNSSEC queries.  While validation is not required, it is strongly
       encouraged; a caching resolver that does not validate answers
       that can be validated may cache invalid data; this will prevent
       validating stub resolvers from successfully validating answers.
	   
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   
MGLT: I see the text above as a recommendation for caching resolvers
in the homenet, but the relation to the home.arpa is unclear to me. 
Was the intention to say that names under the home.arpa zone SHOULD 
be secured with DNSSEC so caching resolvers MUST support DNSSEC 
validation. In addition, these caching resolvers MUST also be able 
to be configured with a Trust Anchor for the home.arpa.	   
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   

       Unless configured otherwise, recursive resolvers and DNS proxies
       MUST behave as described in Locally Served Zones ([RFC6303]
       Section 3).  That is, queries for domains that are subdomains of
       'home.arpa.'  MUST NOT be forwarded, with one important
       exception: a query for a DS record when the DO bit ([RFC4035]
       section 3.2.1) set MUST return the correct answer for that
       question, including correct information in the authority section
       that proves that the record is nonexistent.

       So for example a query for the NS record for 'home.arpa.'  MUST
       NOT result in that query being forwarded to an upstream cache nor
       to the authoritative DNS server for '.arpa.'.  However, as
       necessary to provide accurate authority information, a query for
       the DS record MUST result in whatever queries are necessary being
       forwarded; typically, this will just be a query for the DS
       record, since the necessary authority information will be
       included in the authority section of the response if the DO bit
       is set.




Pfister & Lemon         Expires February 11, 2018               [Page 4]

Internet-Draft                 dot homenet                   August 2017


       In addition to the behavior specified above, recursive resolvers
       that can be used in a homenet MUST be configurable with a
       delegation to an authoritative server for that particular
       homenet's instance of the domain 'home.arpa.'.

       It is permissible to combine the recursive resolver function for
       general DNS lookups with an authoritative resolver for
       'home.arpa.'; in this case, rather than forwarding queries for
       subdomains of 'home.arpa.' to an authoritative server, the
       caching resolver answers them authoritatively.  The behavior with
       respect to forwarding queries specifically for 'home.arpa.'
       remains the same.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   
MGLT: The full consideration seems to me to be conformance to RFC6303.
In particular the recommendations for DNSSEC in RFC 6303 seems to me
accurated and are not specifically mentioned here. Maybe that should 
be clearly stated that all considerations of RFC6303 should be 
considered as home.arpa is of local scope. 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   
	   
   5.  No special processing of 'home.arpa.' is required for
       authoritative DNS server implementations.  It is possible that an
       authoritative DNS server might attempt to check the authoritative
       servers for 'home.arpa.' for a delegation beneath that name
       before answering authoritatively for such a delegated name.  In
       such a case, because the name always has only local significance
       there will be no such delegation in the 'home.arpa.' zone, and so
       the server would refuse to answer authoritatively for such a
       zone.  A server that implements this sort of check MUST be
       configurable so that either it does not do this check for the
       'home.arpa.' domain, or it ignores the results of the check.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   
MGLT: I understand this as being incorrect. The resolver can also be configured 
with a trust anchor. I would refer to the RFC6303:

 As DNSSEC is deployed within the IN-ADDR.ARPA and IP6.ARPA
   namespaces, the zones listed above will need to be delegated as
   insecure delegations, or be within insecure zones.  This will allow
   DNSSEC validation to succeed for queries in these spaces despite not
   being answered from the delegated servers.

   It is recommended that sites actively using these namespaces secure
   them using DNSSEC [RFC4035] by publishing and using DNSSEC trust
   anchors.  This will protect the clients from accidental import of
   unsigned responses from the Internet.	   
	   
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   
	   
	   
   6.  DNS server operators MAY configure an authoritative server for
       'home.arpa.' for use in homenets and other home networks.  The
       operator for the DNS servers authoritative for 'home.arpa.' in
       the global DNS will configure any such servers as described in
       Section 7.
	   

   7.  'home.arpa.' is a subdomain of the 'arpa' top-level domain, which
       is operated by IANA under the authority of the Internet
       Architecture Board according to the rules established in
       [RFC3172].  There are no other registrars for .arpa.

5.  Updates to Home Networking Control Protocol

   The final paragraph of Home Networking Control Protocol [RFC7788],
   section 8, is updated as follows:

   OLD:

      Names and unqualified zones are used in an HNCP network to provide
      naming and service discovery with local significance.  A network-
      wide zone is appended to all single labels or unqualified zones in
      order to qualify them. ".home" is the default; however, an
      administrator MAY configure the announcement of a Domain-Name TLV



Pfister & Lemon         Expires February 11, 2018               [Page 5]

Internet-Draft                 dot homenet                   August 2017


      (Section 10.6) for the network to use a different one.  In case
      multiple are announced, the domain of the node with the greatest
      node identifier takes precedence.

   NEW:

      Names and unqualified zones are used in an HNCP network to provide
      naming and service discovery with local significance.  A network-
      wide zone is appended to all single labels or unqualified zones in
      order to qualify them. 'home.arpa.' is the default; however, an
      administrator MAY configure the announcement of a Domain-Name TLV
      (Section 10.6) for the network to use a different one.  In case
      multiple are announced, the domain of the node with the greatest
      node identifier takes precedence.

      The 'home.arpa.' special-use name does not require a special
      resolution protocol.  Names for which the rightmost two labels are
      'home.arpa.' are resolved using the DNS protocol [RFC1035].

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   
MGLT: If home.arpa are no different than other resolutions and we 
start from the root zone responses are likely to be NXDOMAIN. I 
think we should clarify that DNS is used as a transport protocol, 
but that resolution may be handled differently.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   
	  
	  
6.  Security Considerations

   A DNS record that is returned as a response to a query for an FQDN in
   the domain '.home.arpa.' is expected to have local significance.  It
   is expected to be returned by a server involved in name resolution
   for the homenet the device is connected in.  However, such response
   MUST NOT be considered more trustworthy than would be a similar
   response for any other DNS query.

   Because 'home.arpa.' is not globally scoped and cannot be secured
   using DNSSEC based on the root domain's trust anchor, there is no way
   to tell, using a standard DNS query, in which homenet scope an answer
   belongs.  Consequently, users may experience surprising results with
   such names when roaming to different homenets.  To prevent this from
   happening, it may be useful for the resolver to identify different
   homenets on which it has resolved names, but this is out of scope for
   this document.

   It is not possible to install a trust anchor for this zone in the
   '.arpa' zone.  The reason for this is that in order to do so, it
   would be necessary to have the key-signing key for the zone
   ([RFC4034] Section 5).  Since the zone is not globally unique, no one
   key would work.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%      
MGLT: I think that DS is meant rather than trust anchor.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   
 
   An alternative would be to install a authenticated denial of
   existence ([RFC4033] Section 3.2).  

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%      
MGLT: This is unclear where the denial of existence is set. Is 
that in the home.arpa zone or the arpa zone. 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   
  
   However, this assumes that
   validation is being done on a caching resolver that is aware of the
   special local meaning of 'home.arpa.'.  If a host stub resolver
   attempts to validate a name in 'home.arpa.', an authenticated denial



Pfister & Lemon         Expires February 11, 2018               [Page 6]

Internet-Draft                 dot homenet                   August 2017


   of existence of 'home' as a subdomain of 'arpa.' would cause the
   validation to fail.  Therefore, the only delegation that will allow
   names under 'home.arpa.' to be resolved is an insecure delegation, as
   in [RFC6303] section 7.

   Consequently, unless a trust anchor for the particular instance of
   the 'home.arpa.' zone being validated is manually configured on the
   validating resolver, DNSSEC signing of names within the 'home.arpa.'
   zone is not possible.

   Although in principle it might be useful to install a trust anchor
   for a particular instance of 'home.arpa.', it's reasonable to expect
   that a host with such a trust anchor might from time to time connect
   to more than one network with its own instance of 'home.arpa.'.  Such
   a host would be unable to access services on any instance of
   'home.arpa.' other than the one for which a trust anchor was
   configured.

   It is in principle possible to attach an identifier to an instance of
   'home.arpa.' that could be used to identify which trust anchor to
   rely on for validating names in that particular instance.  However,
   the security implications of this are complicated, and such a
   mechanism, as well as a discussion of those implications, is out of
   scope for this document.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%      
MGLT: There are also some privacy issues associated to leaking names
outside the homenet boundaries. For example daniel_smith.home.arpa
reveal the identity of the member of the homenet, my_ipad.home.arpa
reveals the devices you own, the application. 

home.arpa may also used in larger environment such as corporate / 
private. going from one to the other may also leak such information. 

The leak can be from the homenet to the outside world in which case
one neeed to control the queries sent. But in intruder (or guest) 
may also access the homenet and proceed to discovery of the names. 
As a result even though homenet is believe to be a trusted environment, 
care should be considered while publishing under the home.arpa. as
well as whose the information is accessible to.   

They might be collision as well. myprinter.home.arpa may be found
in various environments, and upon discovery you may also - 
in this example - print confidential information to that printer. 
In some case you may not even be aware, for example, if your 
printing information failed home, and is re-activated once you 
are in another environment.  

As information may be sensitive it may be encrypted using IPsec 
DTLS as described by dprive for both authentication and confidentiality. 

When the trust anchor is configured in the resolver, these must be
able to roll-over the key and should follows the requirements for DNSSEC
validators. if it is impossible for a resolver to see the difference 
between an attack and a re-key we are in trouble. 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   

   
   
   
7.  Delegation of 'home.arpa.'

   In order to be fully functional, there must be a delegation of
   'home.arpa.' in the '.arpa.' zone [RFC3172].  This delegation MUST
   NOT include a DS record, and MUST point to one or more black hole
   servers, for example 'blackhole-1.iana.org.' and 'blackhole-
   2.iana.org.'.  The reason that this delegation must not be signed is
   that not signing the delegation breaks the DNSSEC chain of trust,
   which prevents a validating stub resolver from rejecting names
   published under 'home.arpa.' on a homenet name server.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%      
MGLT: The zone home.arpa MUST NOT be seen as belonging to the 
homenet. As a result, NS and DS records for home.arpa does not 
have meanings outside a specific domain. A Public server outside 
the boundaries of the homenet MUST consider this traffic as 
irrelevant and sink.    

Redirection to as112 without coordination with as112 operator 
may rather be performed using DNAME. I believe more text should 
document the two alternative. With the proposed configuration, 
the query will be directed to a server that is not authoritative for 
the zone. The response is likely to be REFUSED, while in the other 
case it is likely to be NXDOMAIN.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%      
 
   
8.  IANA Considerations

   IANA is requested to record the domain name 'home.arpa.' in the
   Special-Use Domain Names registry [SUDN].  IANA is requested, with
   the approval of IAB, to implement the delegation requested in
   Section 7.
   
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%      
 MGLT: OK if IANA may make the direct way work. In that case is 
there any need to update a registry for zone served by as112? 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%      



From nobody Fri Aug 18 09:52:17 2017
Return-Path: <daniel.migault@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50DFD132A0A; Fri, 18 Aug 2017 09:52:15 -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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id twuFlkV1sb21; Fri, 18 Aug 2017 09:52:11 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (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 5CAFD13219F; Fri, 18 Aug 2017 09:52:08 -0700 (PDT)
X-AuditID: c618062d-b7bff70000004f0a-ed-5997323043f0
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usplmg20.ericsson.net (Symantec Mail Security) with SMTP id 94.E8.20234.03237995; Fri, 18 Aug 2017 20:30:08 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0352.000; Fri, 18 Aug 2017 12:52:06 -0400
From: Daniel Migault <daniel.migault@ericsson.com>
To: Daniel Migault <daniel.migault@ericsson.com>, "secdir@ietf.org" <secdir@ietf.org>
CC: "draft-ietf-homenet-dot.all@ietf.org" <draft-ietf-homenet-dot.all@ietf.org>, "homenet@ietf.org" <homenet@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [secdir] Secdir last call review of draft-ietf-homenet-dot-12
Thread-Topic: [secdir] Secdir last call review of draft-ietf-homenet-dot-12
Thread-Index: AQHTGEFPNcIi2xMGa0+hL4jWilNTs6KKUyPA
Date: Fri, 18 Aug 2017 16:52:06 +0000
Message-ID: <2DD56D786E600F45AC6BDE7DA4E8A8C118CD0C08@eusaamb107.ericsson.se>
References: <150307463977.14156.2178189421671973906@ietfa.amsl.com>
In-Reply-To: <150307463977.14156.2178189421671973906@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrOLMWRmVeSWpSXmKPExsUyuXRPuK6B0fRIg2nrtCwef5zCZvF+0SEW i2cb57NYfFj4kMWBxWPJkp9MAYxRXDYpqTmZZalF+nYJXBk3f2xmL7j2krHiX5NhA+O5LYxd jJwcEgImEvff7mTrYuTiEBI4yihxcskXVghnOaNE69J2NpAqNgEjibZD/ewgtohAuMSjHWcZ QYqYBWYzSizuWMYCkhAW8JJYuGgWG0SRt0RHz3co20ji9oE/YOtYBFQljny5xwRi8wr4Shzf eQusV0jAWWLa0adgcU4BF4lZO7czg9iMAmIS30+tAYszC4hL3HoynwnibAGJJXvOM0PYohIv H/9jhbCVJD7+ns8OUa8jsWD3JzYIW1ti2cLXzBB7BSVOznzCMoFRdBaSsbOQtMxC0jILScsC RpZVjBylxQU5uelGBpsYgdFxTIJNdwfj/emehxgFOBiVeHgT1aZHCrEmlhVX5h5ilOBgVhLh FXg2LVKINyWxsiq1KD++qDQntfgQozQHi5I474TzFyKEBNITS1KzU1MLUotgskwcnFINjF39 ayqWb4ybJPt3pnhCcPv9m9LyatcXbLjq++D6jKv2UhsfrzqfvjFhoaWs0e095hMk5NrnZJZt f3mjUds7ucnK9f0P8Sfdy/OSzT4++CXzdpnyq27Jtp0P7u5hFGY0Tn0q+NExlPGsbcu1zU1v HvP831pygV2RZ+sBlWcxxxecdNDacS3VM0uJpTgj0VCLuag4EQDRky9wigIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8PmfDHUFcYGILKYtuxoNTK6q6Xg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 18 Aug 2017 16:52:15 -0000

Hi,=20

I used the web form and expected that the boilerplate would automatically b=
e added. This explains why the introduction may look a bit directive or dry=
. To clarify the scope of my reviews, I am adding the boilerplate below.

I have reviewed this document as part of the security directorate's=20
ongoing effort to review all IETF documents being processed by the=20
IESG.  These comments were written primarily for the benefit of the=20
security area directors.  Document editors and WG chairs should treat=20
these comments just like any other last call comments.

Yours,=20
Daniel
-----Original Message-----
From: secdir [mailto:secdir-bounces@ietf.org] On Behalf Of Daniel Migault
Sent: Friday, August 18, 2017 12:44 PM
To: secdir@ietf.org
Cc: draft-ietf-homenet-dot.all@ietf.org; homenet@ietf.org; ietf@ietf.org
Subject: [secdir] Secdir last call review of draft-ietf-homenet-dot-12

Reviewer: Daniel Migault
Review result: Has Nits

Thank you for writing the draft. Please find my comments. I hope they are h=
elpful.=20

Yours,
Daniel =20

                    Special Use Domain 'home.arpa.'
                       draft-ietf-homenet-dot-12

Abstract

   This document specifies the behavior that is expected from the Domain
   Name System with regard to DNS queries for names ending with
   '.home.arpa.', and designates this domain as a special-use domain
   name. 'home.arpa.' is designated for non-unique use in residential
   home networks.  Home Networking Control Protocol (HNCP) is updated to
   use the 'home.arpa.' domain instead of '.home'.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%    =
 =20
MGLT: I would personally start by saying the document defines a  special-us=
e domain name and then defines the behavior.=20
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%    =
 =20


  =20
Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 11, 2018.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of



Pfister & Lemon         Expires February 11, 2018               [Page 1]


Internet-Draft                 dot homenet                   August 2017


   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  General Guidance  . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Domain Name Reservation Considerations  . . . . . . . . . . .   3
   5.  Updates to Home Networking Control Protocol . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  Delegation of 'home.arpa.'  . . . . . . . . . . . . . . . . .   7
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   7
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     10.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Users and devices within a home network (hereafter "homenet") require
   devices and services to be identified by names that are unique within
   the boundaries of the homenet [RFC7368].  The naming mechanism needs
   to function without configuration from the user.  While it may be
   possible for a name to be delegated by an ISP, homenets must also
   function in the absence of such a delegation.  A default name with a
   scope limited to each individual homenet needs to be used.

   This document corrects an error in [RFC7788], replacing '.home' with
   'home.arpa.' as the default domain-name for homenets. '.home' had
   been selected as the most user-friendly option.  However, there are
   existing uses of '.home' that may be in conflict with this use:
   evidence indicates that '.home' queries frequently leak out and reach
   the root name servers [ICANN1] [ICANN2].

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20
 MGLT: I believe that more important than the leak is that the  introductio=
n of .home in the root zone has been identified as  highly risky. Another r=
eason for not adopting it are also some
 uncertainty about its introduction into the root zone.   =20
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20

   In addition, it's necessary, for compatibility with DNSSEC
   (Section 6), that an insecure delegation ([RFC4035] section 4.3) be
   present for the name.  There is an existing process for allocating
   names under '.arpa' [RFC3172].  No such process is available for
   requesting a similar delegation in the root at the request of the
   IETF, which does not administer that zone.  As a result, the use of
   '.home' is deprecated.

   This document registers the domain '.home.arpa.' as a special-use
   domain name [RFC6761] and specifies the behavior that is expected
   from the Domain Name System with regard to DNS queries for names
   whose rightmost non-terminal labels are 'home.arpa.'.  Queries for



Pfister & Lemon         Expires February 11, 2018               [Page 2]


Internet-Draft                 dot homenet                   August 2017


   names ending with '.home.arpa.' are of local significance within the
   scope of a homenet, meaning that identical queries will result in
   different results from one homenet to another.  In other words, a
   name ending in 'home.arpa.' is not globally unique.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20
MGLT: I think the text mentioned in the beginning of the paragraph above sh=
ould be in the abstract. That was the sense of my previous comment.=20
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%    =
 =20

   Although this document makes specific reference to RFC7788, it is not
   intended that the use of 'home.arpa.' be restricted solely to
   networks where HNCP is deployed; it is rather the case that
   'home.arpa.' is the correct domain for uses like the one described
   for '.home' in RFC7788: local name service in residential homenets.

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

3.  General Guidance

   The domain name '.home.arpa.' is to be used for naming within
   residential homenets.  Names ending with '.home.arpa.' reference a
   locally-served zone, the contents of which are unique only to a
   particular homenet, and are not globally unique.  Such names refer to
   nodes and/or services that are located within a homenet (e.g., a
   printer, or a toaster).

   DNS queries for names ending with '.home.arpa.' are resolved using
   local resolvers on the homenet.  Such queries MUST NOT be recursively
   forwarded to servers outside the logical boundaries of the homenet.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20
MGLT: "local resolvers" seems to me mis-leading. Your resolver may be local=
 but still forward the query to the Global Internet. I do not see better wa=
ys to say it other than inside the boundaries of
the homenet. Maybe we could say:  =20
  =20
   DNS queries for names ending with '.home.arpa.' are resolved using
   homenet specific resolution mechanisms.=20

Eventually an informational reference to the simple naming architecture may=
 be added so the reader can refer to the doc for further information. For f=
ull disclosure Ted and I are co-authors. =20
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20
  =20
   Some service discovery user interfaces that are expected to be used
   on homenets conceal information such as domain names from end users.
   However, it is still expected that in some cases, users will need to
   see, remember, and even type, names ending with 'home.arpa.'.  It is
   therefore desirable that users identify the domain and understand
   that using it expresses the intention to connect to a service that is
   specific to the homenet to which they are connected.  Enforcing the
   fulfillment of this intention is out of scope for this document.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20
MGLT: I have difficulties understanding the paragraph above. If the idea is=
 to say home.arpa has special meaning that should be considered by GUIs I w=
ould propose the following ordering.

It is
   therefore desirable that users identify the domain and understand
   that using it expresses the intention to connect to a service that is
   specific to the homenet to which they are connected.=20
 Some service discovery user interfaces that are expected to be used
   on homenets conceal information such as domain names from end users.
   However, it is still expected that in some cases, users will need to
   see, remember, and even type, names ending with 'home.arpa.'. =20
 Enforcing the
   fulfillment of this intention is out of scope for this document.  =20
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20

  =20
4.  Domain Name Reservation Considerations

   This section defines the behavior of systems involved in domain name
   resolution when resolving queries for names ending with '.home.arpa.'
   (as per [RFC6761]).





Pfister & Lemon         Expires February 11, 2018               [Page 3]


Internet-Draft                 dot homenet                   August 2017


   1.  Users can use names ending with '.home.arpa.' just as they would
       use any other domain name.  The 'home.arpa.' name is chosen to be
       readily recognized by users as signifying that the name is
       addressing a service on the homenet to which the user's device is
       connected.

   2.  Application software SHOULD NOT treat names ending in
       'home.arpa.' differently than other names.  In particular, there
       is no basis for trusting names that are subdomains of
       'home.arpa.' (see Section 6).

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20
MGLT: a domain name ending in home.arpa may be resolved differently that a =
regular domain name. As a result a different treatment is applied. I think =
that "treat" means that no special meaning - other that the domain name is =
inside the homenet boundaries - should be associated to a home.arpa. If I a=
m correct I would limit the consideration to the name rather then the appli=
cation.=20
I would suggest the text below:
=09
names ending in home.arpa SHOULD NOT be associated any other properties tha=
n the affiliation to the homenet. In particular, there
       is no basis for trusting names that are subdomains of
       'home.arpa.' (see Section 6).
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20
=09
	  =20
   3.  Name resolution APIs and libraries MUST NOT recognize names that
       end in '.home.arpa.' as special and MUST NOT treat them
       differently.  Name resolution APIs MUST send queries for such
       names to a recursive DNS server that is configured to be
       authoritative for the 'home.arpa.' zone appropriate to the
       homenet. =20

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20
MGLT: I believe the text below does not concern the library but the resolve=
r. It is different to say libraries MUST NOT have specific considerations f=
or home.arpa than a resolution service that may use different libraries MUS=
T NOT consider the home.arpa differently.=20
My understanding of the text below is that the resolver and the authoritati=
ve server for the home.arpa MUST be co-located. The reasons I think this is=
 not exact is that resolution for home.arpa can also be provided by other m=
echanisms than an authoritative server. Typically, resolution can be done b=
y requesting Authoritative Servers, Advertising Proxies, Hybrid Proxies (no=
w called Discovery Proxies)....
The other reason is do not see the text below accurate is that you may have=
 a DNS Proxy that transparently to the end user split the resolution betwee=
n homenet specific resolutions when home.arpa is encountered while other na=
mes are sent to the ISP resolver.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20

 =20
	  =20
	   One or more IP addresses for recursive DNS servers will
       usually be supplied to the client through router advertisements
       or DHCP.  If a host is configured to use a resolver other than
       one that is authoritative for the appropriate 'home.arpa.' zone,
       the client may be unable to resolve, or may receive incorrect
       results for, names in sub domains of 'home.arpa.'.

   4.  Caching resolvers conforming to this specification MUST support
       DNSSEC queries.  While validation is not required, it is strongly
       encouraged; a caching resolver that does not validate answers
       that can be validated may cache invalid data; this will prevent
       validating stub resolvers from successfully validating answers.
	  =20
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20
MGLT: I see the text above as a recommendation for caching resolvers in the=
 homenet, but the relation to the home.arpa is unclear to me.=20
Was the intention to say that names under the home.arpa zone SHOULD be secu=
red with DNSSEC so caching resolvers MUST support DNSSEC validation. In add=
ition, these caching resolvers MUST also be able=20
to be configured with a Trust Anchor for the home.arpa.	  =20
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20

       Unless configured otherwise, recursive resolvers and DNS proxies
       MUST behave as described in Locally Served Zones ([RFC6303]
       Section 3).  That is, queries for domains that are subdomains of
       'home.arpa.'  MUST NOT be forwarded, with one important
       exception: a query for a DS record when the DO bit ([RFC4035]
       section 3.2.1) set MUST return the correct answer for that
       question, including correct information in the authority section
       that proves that the record is nonexistent.

       So for example a query for the NS record for 'home.arpa.'  MUST
       NOT result in that query being forwarded to an upstream cache nor
       to the authoritative DNS server for '.arpa.'.  However, as
       necessary to provide accurate authority information, a query for
       the DS record MUST result in whatever queries are necessary being
       forwarded; typically, this will just be a query for the DS
       record, since the necessary authority information will be
       included in the authority section of the response if the DO bit
       is set.




Pfister & Lemon         Expires February 11, 2018               [Page 4]


Internet-Draft                 dot homenet                   August 2017


       In addition to the behavior specified above, recursive resolvers
       that can be used in a homenet MUST be configurable with a
       delegation to an authoritative server for that particular
       homenet's instance of the domain 'home.arpa.'.

       It is permissible to combine the recursive resolver function for
       general DNS lookups with an authoritative resolver for
       'home.arpa.'; in this case, rather than forwarding queries for
       subdomains of 'home.arpa.' to an authoritative server, the
       caching resolver answers them authoritatively.  The behavior with
       respect to forwarding queries specifically for 'home.arpa.'
       remains the same.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20
MGLT: The full consideration seems to me to be conformance to RFC6303.
In particular the recommendations for DNSSEC in RFC 6303 seems to me accura=
ted and are not specifically mentioned here. Maybe that should be clearly s=
tated that all considerations of RFC6303 should be considered as home.arpa =
is of local scope.=20
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20
	  =20
   5.  No special processing of 'home.arpa.' is required for
       authoritative DNS server implementations.  It is possible that an
       authoritative DNS server might attempt to check the authoritative
       servers for 'home.arpa.' for a delegation beneath that name
       before answering authoritatively for such a delegated name.  In
       such a case, because the name always has only local significance
       there will be no such delegation in the 'home.arpa.' zone, and so
       the server would refuse to answer authoritatively for such a
       zone.  A server that implements this sort of check MUST be
       configurable so that either it does not do this check for the
       'home.arpa.' domain, or it ignores the results of the check.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20
MGLT: I understand this as being incorrect. The resolver can also be config=
ured with a trust anchor. I would refer to the RFC6303:

 As DNSSEC is deployed within the IN-ADDR.ARPA and IP6.ARPA
   namespaces, the zones listed above will need to be delegated as
   insecure delegations, or be within insecure zones.  This will allow
   DNSSEC validation to succeed for queries in these spaces despite not
   being answered from the delegated servers.

   It is recommended that sites actively using these namespaces secure
   them using DNSSEC [RFC4035] by publishing and using DNSSEC trust
   anchors.  This will protect the clients from accidental import of
   unsigned responses from the Internet.	  =20
	  =20
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20
	  =20
	  =20
   6.  DNS server operators MAY configure an authoritative server for
       'home.arpa.' for use in homenets and other home networks.  The
       operator for the DNS servers authoritative for 'home.arpa.' in
       the global DNS will configure any such servers as described in
       Section 7.
	  =20

   7.  'home.arpa.' is a subdomain of the 'arpa' top-level domain, which
       is operated by IANA under the authority of the Internet
       Architecture Board according to the rules established in
       [RFC3172].  There are no other registrars for .arpa.

5.  Updates to Home Networking Control Protocol

   The final paragraph of Home Networking Control Protocol [RFC7788],
   section 8, is updated as follows:

   OLD:

      Names and unqualified zones are used in an HNCP network to provide
      naming and service discovery with local significance.  A network-
      wide zone is appended to all single labels or unqualified zones in
      order to qualify them. ".home" is the default; however, an
      administrator MAY configure the announcement of a Domain-Name TLV



Pfister & Lemon         Expires February 11, 2018               [Page 5]


Internet-Draft                 dot homenet                   August 2017


      (Section 10.6) for the network to use a different one.  In case
      multiple are announced, the domain of the node with the greatest
      node identifier takes precedence.

   NEW:

      Names and unqualified zones are used in an HNCP network to provide
      naming and service discovery with local significance.  A network-
      wide zone is appended to all single labels or unqualified zones in
      order to qualify them. 'home.arpa.' is the default; however, an
      administrator MAY configure the announcement of a Domain-Name TLV
      (Section 10.6) for the network to use a different one.  In case
      multiple are announced, the domain of the node with the greatest
      node identifier takes precedence.

      The 'home.arpa.' special-use name does not require a special
      resolution protocol.  Names for which the rightmost two labels are
      'home.arpa.' are resolved using the DNS protocol [RFC1035].

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20
MGLT: If home.arpa are no different than other resolutions and we start fro=
m the root zone responses are likely to be NXDOMAIN. I think we should clar=
ify that DNS is used as a transport protocol, but that resolution may be ha=
ndled differently.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20
	 =20
	 =20
6.  Security Considerations

   A DNS record that is returned as a response to a query for an FQDN in
   the domain '.home.arpa.' is expected to have local significance.  It
   is expected to be returned by a server involved in name resolution
   for the homenet the device is connected in.  However, such response
   MUST NOT be considered more trustworthy than would be a similar
   response for any other DNS query.

   Because 'home.arpa.' is not globally scoped and cannot be secured
   using DNSSEC based on the root domain's trust anchor, there is no way
   to tell, using a standard DNS query, in which homenet scope an answer
   belongs.  Consequently, users may experience surprising results with
   such names when roaming to different homenets.  To prevent this from
   happening, it may be useful for the resolver to identify different
   homenets on which it has resolved names, but this is out of scope for
   this document.

   It is not possible to install a trust anchor for this zone in the
   '.arpa' zone.  The reason for this is that in order to do so, it
   would be necessary to have the key-signing key for the zone
   ([RFC4034] Section 5).  Since the zone is not globally unique, no one
   key would work.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%    =
 =20
MGLT: I think that DS is meant rather than trust anchor.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20
=20
   An alternative would be to install a authenticated denial of
   existence ([RFC4033] Section 3.2). =20

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%    =
 =20
MGLT: This is unclear where the denial of existence is set. Is that in the =
home.arpa zone or the arpa zone.=20
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20
 =20
   However, this assumes that
   validation is being done on a caching resolver that is aware of the
   special local meaning of 'home.arpa.'.  If a host stub resolver
   attempts to validate a name in 'home.arpa.', an authenticated denial



Pfister & Lemon         Expires February 11, 2018               [Page 6]


Internet-Draft                 dot homenet                   August 2017


   of existence of 'home' as a subdomain of 'arpa.' would cause the
   validation to fail.  Therefore, the only delegation that will allow
   names under 'home.arpa.' to be resolved is an insecure delegation, as
   in [RFC6303] section 7.

   Consequently, unless a trust anchor for the particular instance of
   the 'home.arpa.' zone being validated is manually configured on the
   validating resolver, DNSSEC signing of names within the 'home.arpa.'
   zone is not possible.

   Although in principle it might be useful to install a trust anchor
   for a particular instance of 'home.arpa.', it's reasonable to expect
   that a host with such a trust anchor might from time to time connect
   to more than one network with its own instance of 'home.arpa.'.  Such
   a host would be unable to access services on any instance of
   'home.arpa.' other than the one for which a trust anchor was
   configured.

   It is in principle possible to attach an identifier to an instance of
   'home.arpa.' that could be used to identify which trust anchor to
   rely on for validating names in that particular instance.  However,
   the security implications of this are complicated, and such a
   mechanism, as well as a discussion of those implications, is out of
   scope for this document.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%    =
 =20
MGLT: There are also some privacy issues associated to leaking names outsid=
e the homenet boundaries. For example daniel_smith.home.arpa reveal the ide=
ntity of the member of the homenet, my_ipad.home.arpa reveals the devices y=
ou own, the application.=20

home.arpa may also used in larger environment such as corporate / private. =
going from one to the other may also leak such information.=20

The leak can be from the homenet to the outside world in which case one nee=
ed to control the queries sent. But in intruder (or guest) may also access =
the homenet and proceed to discovery of the names.=20
As a result even though homenet is believe to be a trusted environment, car=
e should be considered while publishing under the home.arpa. as
well as whose the information is accessible to.  =20

They might be collision as well. myprinter.home.arpa may be found in variou=
s environments, and upon discovery you may also - in this example - print c=
onfidential information to that printer.=20
In some case you may not even be aware, for example, if your printing infor=
mation failed home, and is re-activated once you are in another environment=
. =20

As information may be sensitive it may be encrypted using IPsec DTLS as des=
cribed by dprive for both authentication and confidentiality.=20

When the trust anchor is configured in the resolver, these must be able to =
roll-over the key and should follows the requirements for DNSSEC validators=
. if it is impossible for a resolver to see the difference between an attac=
k and a re-key we are in trouble.=20
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  =20

  =20
  =20
  =20
7.  Delegation of 'home.arpa.'

   In order to be fully functional, there must be a delegation of
   'home.arpa.' in the '.arpa.' zone [RFC3172].  This delegation MUST
   NOT include a DS record, and MUST point to one or more black hole
   servers, for example 'blackhole-1.iana.org.' and 'blackhole-
   2.iana.org.'.  The reason that this delegation must not be signed is
   that not signing the delegation breaks the DNSSEC chain of trust,
   which prevents a validating stub resolver from rejecting names
   published under 'home.arpa.' on a homenet name server.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%    =
 =20
MGLT: The zone home.arpa MUST NOT be seen as belonging to the homenet. As a=
 result, NS and DS records for home.arpa does not have meanings outside a s=
pecific domain. A Public server outside the boundaries of the homenet MUST =
consider this traffic as=20
irrelevant and sink.   =20

Redirection to as112 without coordination with as112 operator may rather be=
 performed using DNAME. I believe more text should document the two alterna=
tive. With the proposed configuration, the query will be directed to a serv=
er that is not authoritative for the zone. The response is likely to be REF=
USED, while in the other case it is likely to be NXDOMAIN.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%    =
 =20
=20
  =20
8.  IANA Considerations

   IANA is requested to record the domain name 'home.arpa.' in the
   Special-Use Domain Names registry [SUDN].  IANA is requested, with
   the approval of IAB, to implement the delegation requested in
   Section 7.
  =20
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%    =
 =20
 MGLT: OK if IANA may make the direct way work. In that case is there any n=
eed to update a registry for zone served by as112?=20
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%    =
 =20


_______________________________________________
secdir mailing list
secdir@ietf.org
https://www.ietf.org/mailman/listinfo/secdir
wiki: http://tools.ietf.org/area/sec/trac/wiki/SecDirReview


From nobody Fri Aug 18 16:42:08 2017
Return-Path: <adam@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF295132380 for <ietf@ietfa.amsl.com>; Fri, 18 Aug 2017 16:42:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level: 
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oohi0iRMnYn4 for <ietf@ietfa.amsl.com>; Fri, 18 Aug 2017 16:42:05 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46EBD126BF3 for <ietf@ietf.org>; Fri, 18 Aug 2017 16:42:05 -0700 (PDT)
Received: from Svantevit.roach.at (cpe-70-122-154-80.tx.res.rr.com [70.122.154.80]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v7INfusK064520 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 18 Aug 2017 18:41:58 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-154-80.tx.res.rr.com [70.122.154.80] claimed to be Svantevit.roach.at
Subject: Re: Scope for self-destructing email?
To: Phillip Hallam-Baker <phill@hallambaker.com>, John C Klensin <john-ietf@jck.com>
Cc: vaibhav singh <vaibhavsinghacads@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
References: <20170816225637.4431.qmail@ary.lan> <7352544b-8626-fb30-b74f-48b62110b7cf@gmail.com> <39610B4F-8DE6-4E19-A6C8-5FAB882DD524@orthanc.ca> <CAMm+LwgqnPx2VBaoaWuU_YW547oRhQDTo48t4BokcwKqRSO+bw@mail.gmail.com> <F0EECBF6-F48E-425B-A6E8-65E5183FD36E@nbcuni.com> <CAMm+LwiT8+oiLwSX_9bekiDY6_3njbW9W_jKnP9FJkRYqwqRcQ@mail.gmail.com> <a6492c82-2b16-b087-c554-8ca38c8f5e84@huitema.net> <BA30F5B5AFA6760F140209A3@PSB> <CAMm+Lwh8HEgWCzgWieM09FsuBhHc+v1K-n4TKqyR6UvS17ha5Q@mail.gmail.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <4f0c6d9e-7447-6268-11cd-8ba7ea9f7d06@nostrum.com>
Date: Fri, 18 Aug 2017 18:41:56 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CAMm+Lwh8HEgWCzgWieM09FsuBhHc+v1K-n4TKqyR6UvS17ha5Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------1452759B78BF8B597D1001AF"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uJ4nN7NSGNDYd2rPdjKE1ZliqW0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 18 Aug 2017 23:42:07 -0000

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

On 8/17/17 2:15 PM, Phillip Hallam-Baker wrote:
> If the next President of the US was to come to me and ask if I could 
> provide a mechanism that would allow her to send an email message to 
> members of her cabinet and that supported a 'recall' feature, I would 
> have no hesitation in saying yes, conditional on some technical 
> support which Microsoft and Apple and some others are both capable of 
> providing.


https://www.google.com/search?q=%22hdcp+stripper%22

https://www.atomos.com/ninja/


/a


--------------1452759B78BF8B597D1001AF
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 8/17/17 2:15 PM, Phillip
      Hallam-Baker wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAMm+Lwh8HEgWCzgWieM09FsuBhHc+v1K-n4TKqyR6UvS17ha5Q@mail.gmail.com">
      <div class="gmail_default" style="font-size:small">If the next
        President of the US was to come to me and ask if I could provide
        a mechanism that would allow her to send an email message to
        members of her cabinet and that supported a 'recall' feature, I
        would have no hesitation in saying yes, conditional on some
        technical support which Microsoft and Apple and some others are
        both capable of providing.</div>
    </blockquote>
    <p><br>
    </p>
    <p><a class="moz-txt-link-freetext" href="https://www.google.com/search?q=%22hdcp+stripper%22">https://www.google.com/search?q=%22hdcp+stripper%22</a></p>
    <p><a class="moz-txt-link-freetext" href="https://www.atomos.com/ninja/">https://www.atomos.com/ninja/</a></p>
    <p><br>
    </p>
    <p>/a<br>
    </p>
  </body>
</html>

--------------1452759B78BF8B597D1001AF--


From nobody Fri Aug 18 17:52:38 2017
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E153D132412 for <ietf@ietfa.amsl.com>; Fri, 18 Aug 2017 17:52:28 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YsIaK0zE6ufQ for <ietf@ietfa.amsl.com>; Fri, 18 Aug 2017 17:52:26 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E479132407 for <ietf@ietf.org>; Fri, 18 Aug 2017 17:52:21 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id l19so10750149wmi.1 for <ietf@ietf.org>; Fri, 18 Aug 2017 17:52:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=mMNa8fqvu6fwc4r0pAveFo6dTsD69LrEdE6X9UJ3JXU=; b=rZ+V+dbl3Y18QNH1On8/XXrsKgVS6gqz6kNeQtlJ1sCz5HPnC4ISg6pzPF9+J24sAr DWSuP0FApcJcWbk7MAcHfDNsiRAj7ZqD/UtZl/5R8CC3a/0nJx1KsQmn85yryKPBKCfN vpeB6tN4riUPAvovNo2j1MwfvR9p2MeBLloBGMmWC+ekU/ruW89W74qgOeu/6AVjFwLP 3nadWNwvW/db42H65dUGuCMsxngEWZzmex6d75E/mtnt41v3JQuz1h3trnPWiyzjpe3s IAWr5/q5aVhGs4PZaZS6xR161b2v2si62H4n+dbTGd9OxFJMXvc2Bjxp5PrMpxt04evu mwCA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=mMNa8fqvu6fwc4r0pAveFo6dTsD69LrEdE6X9UJ3JXU=; b=uPABhf++wutU3E3qulaEJqecNr+pbmyezmBqacD1qP6LxZ0RR7llTebEiwuvyyYnw1 7b4f21aW49QwUuiuDxgcf//CkJFuf3VtpIWKqs8IWAulQVHL5AMcRSkHPP3UwKljrY3T FYpxt7gufuGmcvHu3Yg3edQamJcS6859S6PhX8FcannJ+LMTd3F58Asb/IHKaEhKBv31 ReeJARSMgsNpO7BgPcX0AEi+SvfJLeOklPv+RxYyy+9acYbYrXZ7uLs+KCFVh7kozfsg eXqo23EJTCHC0vq7A3I94k6nWx3c75/CvtXggJZyJbXKw9oq4URcSPZ80opw9faGeS3X XsAw==
X-Gm-Message-State: AHYfb5iGiVrKXwubGMCtWr0cVujqEYtRsv6D0deyo2qW+4r+CPudT0CN ssujrfviEd7h+hCQdUiGnK993UNj8vUlpuno2Q==
X-Received: by 10.28.12.201 with SMTP id 192mr2288672wmm.45.1503103938736; Fri, 18 Aug 2017 17:52:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.164.135 with HTTP; Fri, 18 Aug 2017 17:51:37 -0700 (PDT)
In-Reply-To: <150249274009.24438.5552125434164888108.idtracker@ietfa.amsl.com>
References: <150249274009.24438.5552125434164888108.idtracker@ietfa.amsl.com>
From: Warren Kumari <warren@kumari.net>
Date: Fri, 18 Aug 2017 20:51:37 -0400
Message-ID: <CAHw9_iJWhJxJGngi6yv2Di3XsF-cMZv-mxKV=NNGruEDJcM+eg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-sfc-nsh-18.txt> (Network Service Header (NSH)) to Proposed Standard
To: IETF Discuss <ietf@ietf.org>
Cc: IETF-Announce <ietf-announce@ietf.org>, draft-ietf-sfc-nsh@ietf.org,  "Joel M. Halpern" <jmh@joelhalpern.com>, sfc-chairs@ietf.org, sfc@ietf.org,  Alia Atlas <akatlas@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fwCULgG1g0JmnpRsfa3PrJll6-4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 19 Aug 2017 00:52:29 -0000

On Fri, Aug 11, 2017 at 7:05 PM, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Service Function Chaining WG (sf=
c)
> to consider the following document: - 'Network Service Header (NSH)'
>   <draft-ietf-sfc-nsh-18.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits fin=
al
> comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-08-25. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the beginnin=
g of
> the Subject line to allow automated sorting.
>
> Abstract
>
>
>    This document describes a Network Service Header (NSH) inserted onto
>    packets or frames to realize service function paths.  NSH also
>    provides a mechanism for metadata exchange along the instantiated
>    service paths.  NSH is the SFC encapsulation required to support the
>    Service Function Chaining (SFC) architecture (defined in RFC7665).
>

<no hats>

In my opinion this document still needs significant work. Christian's
great SecDir review lists many issues which need to be addressed;
since he has already raised concerns, I am not focusing on the
security and privacy stuff in my but review. Instead, I'll discuss
some of the other issues.

I only skimmed sections 6.1 - Section 8.

As this is output of the SFC WG, which is chartered to, amongst other
thing, create a "Generic SFC Encapsulation" (with some more details)
I'll take it as given that this is desired / needed.

Issues:

Issue 1: I find the entire document to be confusing about what an NSH
actually is, and after spending much time reading, am still fairly
confused.
A clear model at the beginning of the document which explains how
these bits fit together would be very helpful. I am familiar with
RFC7665 (the architecture document); my confusion stems from this
draft.

For example the Abstract says:
"This document describes a Network Service Header (NSH) inserted onto
packets or frames to realize service function paths. NSH also provides
a mechanism for metadata exchange along the instantiated service
paths.  NSH is the SFC encapsulation required to support the Service
Function Chaining (SFC) architecture ".

Oh, ok, so it is something inserted onto packets or frames...
*inserted onto* sounds like a shim, however,  "NSH is the SFC
encapsulation...".  indicates that I had the wrong mental model and
this is actually an encapsulation, kinda like GRE. (This is reinforced
with (end of Section 1) "NSH is the SFC encapsulation referenced in
[RFC7665].") Ok, so this encapsulates the packet, got it...
I read some more, and then find (in section 2) that "An outer
transport header is imposed, on NSH and the original packet/frame, for
network forwarding.". Oh, so this is *actually* a shim / header which
goes before the packet, and then the whole thing gets encapsulated? It
shouldn't have been this hard to figure out, but Ok, now I get it...Or
do I? Oh, hang on, what transport header do I use?!
It is only much much later, in Section 4 (page 15) that I find "Once
NSH is added to a packet, an outer encapsulation is used to forward
the original packet and the associated metadata to the start of a
service chain. ... The service header is independent of the
encapsulation used and is encapsulated in existing transports.  The
presence of NSH is indicated via protocol type or other indicator in
the outer encapsulation." - I'm now really confused - first I thought
it was a shim / header, then I thought it was an encapsulation, now I
(finally) see that it is a header which goes before the packet
(encapsulating it) before it gets encapsulated again into something
else. It would be much better if the document was clearer at the
beginning about how all this fits together / what the NSH actually
*is* -- an analogy to layering, or as a shim which goes between a
tunneling header and the original packet would make this much clearer
(and the reader much less annoyed!).

Issue 2: Section 1.2.  Definition of Terms
"Metadata:  Defined in [RFC7665]." - The definition of metadata in
RFC7665 says: "Metadata: Provides the ability to exchange context
information between classifiers and SFs, and among SFs.". This is not
an adequate definition for use in this document - the document defines
a context header which carries metadata, and it need to be better
defined than something which provides an ability.
Apart from RFC7665 actually *defining* metadata, it doesn't really
describe what you do with it. As this document discusses metadata much
more (and how to carry it), I think that it needs to much better
define what it is, what its purpose is, and how to use it.

Issue 3: Section 2.  Network Service Header
"An outer transport header is imposed, on NSH and the original
packet/frame, for network forwarding." - this is very poorly worded,
and I don't really know what I'm supposed to do here. I'm assuming
that I'm supposed to concatenate the NSH and the packet, and then
encapsulate this in some transport of my choosing, but this needs more
precision.

Issue 4: The document talks about using the TTL to avoid loops, and
also the Service Index (SI). "The Service Index MUST be decremented by
a value of 1 by Service Functions or by SFC Proxy nodes after
performing required services  and the new decremented SI value MUST be
used in the egress packet=E2=80=99s NSH. ... Additionally, while the TTL fi=
eld
is the main mechanism for service plane loop detection, the SI can
also be used for detecting service plane loops.". Much better text is
needed here to discuss how these interact. Lets say the TTL is 14, and
the SI is 1. The packet is now handed to the next SF, which decrements
it to 0. Now what? It this the same as the TTL hitting 0? If it an
error? Do I wrap and go back to 255? What are there 2 mechanisms for
this? Much further down, in Section 6.1, we have: "SI serves as a
mechanism for detecting invalid service function paths.  In
particular, an SI value of zero indicates that forwarding is incorrect
and the packet must be discarded." This answers many of the above, but
having the text better organized would simplify the document.

Issue 5: Section 6. Service Path Forwarding with NSH Subsection 6.1.
SFFs and Overlay Selection
I'm assuming that there is much more detail in other documents which
cover how to use the SPI / SI to do the forwarding -- can you please
insert a reference? I'm somewhat confused by the level of detail
between this document and <whatever the other one is>. This doesn't
contain enough to implement, but seem to include more than I'd expect
to clarify how to interface with some other doc.





Questions / concerns:
Section 2.2.  NSH Base Header
"TTL: Indicates the maximum SFF hops for an SFP.  This field is used
for service plane loop detection. ...  Each SFF involved in forwarding
an NSH packet MUST decrement the TTL value by 1 prior to NSH
forwarding lookup.  Decrementing by 1 from an incoming value of 0
shall result in a TTL value of 63.  The packet MUST NOT be forwarded
if TTL is, after decrement, 0."
Why does decrementing by 1 from 0 result in 63? Under what (valid)
conditions will I receive a packet with an incoming value of 0? (why
is this not an error?)

Section 2.4.  NSH MD Type 1
"When the Base Header specifies MD Type =3D 0x1, a Fixed Length Context
Header (16-bytes) MUST be present immediately following the Service
Path Header, as per Figure 4.  The value of a Fixed Length Context
Header that carries no metadata MUST be set to zero.". "This
specification does not make any assumptions about the content of the
16 byte Context Header that must be present when the MD Type field is
set to 1, and does not describe the structure or meaning of the
included metadata.". So, the specification doesn't make any
assumptions about the Fixed Length Context Header (I guess it is an
opaque blob), but if it has no metadata is must be 0? And if there is
no metadata, why  would I need to waste 16 bytes? And this document
defines 2 MD types -- why would I use this one instead of a Type 2?
(which seems cleaner, and shorter). Kind of related to Issue 2, I
think that there needs to be more discussions (perhaps in some other
document, which needs a reference) what the purpose of the metadata
is, why it is sometimes metadata and sometimes Context Header, what a
receiver is supposed to do with this, etc.

Section 2.4:
"An SFC-aware SF MUST receive the data semantics first in order to
process the data placed in the mandatory context field.  The data
semantics include both the allocation schema and the meaning of the
included data.  How an SFC-aware SF gets the data semantics is outside
the scope of this specification."  -- related to the above, I still
don't get this. Is "the data placed in the mandatory context field" =3D=3D
"metadata"?  And there is no type information associated, so receiver
cannot look at it and know what it is, other than "I expected a blob,
this is a blob, blobs I receive should be of type X, let me try
decoded it as one?" -- shouldn't there be some sort of hint in the NSH
as to what the context field is carrying (like Type 2 has)? I've
looked at  I-D.guichard-sfc-nsh-dc-allocation and
I-D.napper-sfc-nsh-broadband-allocation which discuss how bits in the
context header can be allocated, but would a receiver differentiate
which type is in use (other than being configured to know that blobs
are always of type X). Again, I'm hoping that there is an SFC document
which explains the architecture in more detail then RFC7665.

Section  2.5.1.  Optional Variable Length Metadata
Optional variable length Context Headers have a Class (scope of the
Type), a Type (explicit type of metadata, defined by the Class owner),
and a Length.
A length of 0 means that the context header has no data. It would be
useful to explain what this actually means -- it sounds like a message
with no content, but perhaps receivers are supposed to use the Type in
this case to do something?

Section 3.  NSH Actions
"NSH-aware nodes are the only nodes that may alter the content of NSH
headers." -- this sentence is nonsensical. If a node doesn't know
something is an NSH (is it not NSH-aware), telling it not to touch NSH
headers is basically "Devices on the Internet shouldn't poke at things
that they don't understand".

Section 3:
"At the end of a service function path, an SFF, MUST be the last node
operating on the service header and MUST remove NSH before forwarding
or delivering the un-encapsulated packet." - I'm somewhat confused
what this is trying to say, and assume that it is simply superfluous
commas. But, with those removed the sentence is still confusing to me
-- a SFF is the thing that does the forwarding, and so, by definition
it has to be the last thing operating on the service header (unless
the packet is dropped) -- so, what does the first MUST mean?

Section 4.  NSH Transport Encapsulation
"The presence of NSH is indicated via protocol type or other indicator
in the outer encapsulation." -- just for my interest, what all
encapsulations already have this defined / allocated?

Section 5.  Fragmentation Considerations
"As discussed in [I-D.ietf-rtgwg-dt-encap], within an administrative
domain, an operator can ensure that the underlay MTU is sufficient to
carry SFC traffic without requiring fragmentation." -- I think that
that is stretching what I-D.ietf-rtgwg-dt-encap says a bit far. NSH
Type 1 adds 24 octets (4 octet Base Header, 4 octet Service Path
Header, 16 octet Context Header), plus the gets wrapped in a new
transport, so let's say 24 octets for GRE. This means that, for a
1500byte packet I need an MTU of 1548 (I'm not sure all operators can
support that everywhere). The Type 2 header is of variable length (and
I don't think I saw a limit).
" For example, when NSH is encapsulated in IP, IP-level fragmentation
coupled with Path MTU Discovery (PMTUD) is used. When, on the other
hand, the underlay does not support fragmentation procedures, an error
message SHOULD be logged when dropping a packet too big." -- I think
that more guidance / text is needed here, e.g for v6. Just dropping
the packet and logging an error doesn't solve the base issue causing
the problem. If this protocol wasn't an "encapsulation" I wouldn't
feel so strongly, but if the protocol says that it providing an
encapsulation it needs to handle things that encapsulation protocols
do.




Nits:

Section 1. Introduction
... current service function deployment models have been relatively
static, and bound to topology
[O] static, and bound
[P] static and bound
[R] grammar

...
Specifically, the following functions are necessary:

      The movement of service functions and application workloads in the
      network.

      The ability to easily bind service policy to granular information,
      such as per-subscriber state.

[R]: Numbers or bullets would make the much easier to read.


Section 1.2 - Definition of Terms
"Byte:  All references to "bytes" in this document refer to 8-bit
bytes, or octets." -- this is a circular definition (the section is
Definition of Terms, not Terminology) - suggest dropping the 8-bit
bytes, octets covers it.

Throughout the document:
The document says "A Service Classifier adds NSH.  NSH is removed by
...", and "NSH offers a common and standards-based header" -- is NSH a
technology (as implied by the second phrase), or a thing added to a
packet (like the first implies). Whatever the case, for the first, "A
Service Classifier adds *the* NSH.  *The* NSH is removed by ..." (or,
"an").


Section 1.4. NSH-based Service Chaining
   NSH creates a dedicated service plane, more specifically, NSH
[O] plane, more
[P] plane; more
[R] grammar

 1.  Topological Independence: Service forwarding occurs within the
       service plane, the underlying network topology does not require

[O] plane, the
[P] plane; the    (or "plane, so the")
[R] grammar


Section  2.2.  NSH Base Header
"MD Type: Indicates the format of NSH beyond the mandatory Base Header
and the Service Path Header.  MD Type defines the format of the
metadata being carried." -- please expand MD here. I wasted much time
before guessing that this was MetaData Type.


Given the
   widespread implementation of existing hardware that uses the first
   nibble after an MPLS label stack for ECMP decision processing, this
   document reserves version 01b and this value MUST NOT be used in
[O] 01b and this value
[P] 01b. This value
[R] grammar -- run on sentence, and it reads awkwardly with a
semicolon before the "and" (but that would be grammatically correct,
if preferred.)


Forwarding OAM
   packets unmodified by SFC elements that do not support SFC OAM
   procedures may be acceptable for a subset of OAM functions, but can
   result in unexpected outcomes for others, thus it is recommended to
[
O] others, thus
[P] others; thus
[R] grammar

This specification does not disallow the MD Type value from changing
   along an SFP; however, the specification of the necessary mechanism
   to allow the MD Type to change along an SFP are outside the scope of
   this document, and would need to be defined for that functionality to
[
O] document, and
[P] document and
[R] grammar



Section 2.4:
As SF or SFC Proxy -> A SF or SFC Proxy

Section 2.5.1:
"the SFC-aware SF MUST NOT process the packet and MUST log at least
once per the SPI for which the mandatory metadata is missing." --
feels like you are missing some words after "log" -- presumably "must
log an error", or "this event", or something.


Section 6.1. SFFs and Overlay Selection
This indirection -- SPI to overlay -- creates a true service plane.
   That is, the SFF/SF topology is constructed without impacting the
   network topology but more importantly, service plane only

[O] topology but more importantly,
[P] topology; but more importantly,
[R] grammar

This can be via the overlay or
   underlay and in some case require additional configuration on the SF.

[O] some case
[P] some cases
[R] I think this is what was intended

Section 6.4. Service Graphs
These classifiers may also of course

[O] may also of course
[P] may, of course, also
[R] readability

   modify the metadata associated with the packet.

Section 7.1. NSH Metadata and Policy Enforcement

   As described in Section 2, NSH provides the ability to carry metadata
   along a service path.  This metadata may be derived from several
   sources, common examples include:

[O] sources, common
[P] sources. Common
[R] grammar

      Network nodes/devices: Information provided by network nodes can
      indicate network-centric information (such as VRF or tenant) that
      may be used by service functions, or conveyed to another network

[O] functions, or conveyed
[P] functions or conveyed
[R] grammar

 The granularity of classification may vary.  For
   example, a network switch, acting as a classifier, might only be able
   to classify based on a 5-tuple, whereas, a service function may be

[O] whereas, a service
[P] while a service
[R] readability

In both of the examples above, the service functions perform policy
   decisions based on the result of the initial classification: the SFs
   did not need to perform re-classification, rather they rely on a

[O] re-classification, rather
[P] re-classification; instead,
[R] grammar/readability

   antecedent classification for local policy enforcement.

   Depending on the information carried in the metadata, data privacy
   considerations may need to be considered.  For example, if the

This feels like its punting on the problem more than it should, but
I'm avoiding privacy and security in this particular review.

   metadata conveys tenant information, that information may need to be
   authenticated and/or encrypted between the originator and the
   intended recipients (which may include intended SFs only) .  NSH

[O] ) .
[P] ).
[R] punctuation

   itself does not provide privacy functions, rather it relies on the
   transport/overlay layer.  An operator can select the appropriate
   transport to ensure confidentially (and other security)

[O] confidentially
[P] confidentiality
[R] word choice


Section 8. Security Considerations

 NSH is always encapsulated in a transport protocol (as detailed in
   Section 4 of this specification) and therefore, when required,

[O] ) and therefore,
[P] ); and, therefore,
[R] grammar




W




--=20
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Fri Aug 18 18:59:27 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 238DF1243F6 for <ietf@ietfa.amsl.com>; Fri, 18 Aug 2017 18:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level: 
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28b8iXPNhDP9 for <ietf@ietfa.amsl.com>; Fri, 18 Aug 2017 18:59:24 -0700 (PDT)
Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B008F132196 for <ietf@ietf.org>; Fri, 18 Aug 2017 18:59:23 -0700 (PDT)
Received: by mail-lf0-x231.google.com with SMTP id t128so49197263lff.2 for <ietf@ietf.org>; Fri, 18 Aug 2017 18:59:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=4QfrQWorImFbhwCJrBunZt7aRwD61Tht8PnoqtSltdw=; b=lsCK7oGf9LZeooVwNVUlPC8proc5MY6/5x+wDc5RAaLKKvVKSikR1m2eHJKsjIpeAr VdbwLhl8dt0bTogzY2kqAX93/NHf1qiUyK3TFtyJwu+PrupUUYAnSwdoqdjM8l7nvgw0 B9muBTbDo5A5ZVQ35iY/rwZC+vrNQIK5DvuNWy6VbgyXVb/Vr2YKZDGasFu3QOTm7vQN 5NsvKzsXIfP4FAI3v1OIb9NxZx+iboANFEUiHo97/7t3ZHeVgQ2jOFlfFxHot/b3fHCk htGY1Vpce9cTr7xwxt1bvq+dtH7J64jAi6XpATrDVsnYkII1UdoaiG+9SKhVufe2smPb fTjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=4QfrQWorImFbhwCJrBunZt7aRwD61Tht8PnoqtSltdw=; b=tkIrKQgFcEJMuFC19Nkn5efkIUVquFTztB+zOI+zG6ToaP0x2betPgQIc3wFW9BKFB lPjVmFAbCN0jTmL/0zmcxgMsng6VashpUuoOFGWoryhpEFYFvuVt+KzxrX+B/f8li+sN gYokT1Z3SlkuKkFqEAeAiU3Ahm96BOHI9MHnM7vTKMJbC3iWNJvu515doHI56g/+m2tB HCv8P/gCryZ+JszU1s+OwVGt/bgLpzn0VmyH/eygE15W7cN5p5n/eod3QwCMB7JDK7SE a9ysBq7brp/ZCL4eSsYyVoD3ccfwqDQov0N5TUcb9fLqCn2XeA+mKrZ8ieGXDVWO11th HUxw==
X-Gm-Message-State: AHYfb5gvZKNlbeha1crIUxmNiZZvf4oKxr1rB+SbHGNVciRbjB7IxUm0 9qdeLSt8VAl/YBOAr9QYQQqB50TsEg==
X-Received: by 10.46.92.137 with SMTP id q131mr3974959ljb.102.1503107962009; Fri, 18 Aug 2017 18:59:22 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.25.142.199 with HTTP; Fri, 18 Aug 2017 18:59:20 -0700 (PDT)
In-Reply-To: <4f0c6d9e-7447-6268-11cd-8ba7ea9f7d06@nostrum.com>
References: <20170816225637.4431.qmail@ary.lan> <7352544b-8626-fb30-b74f-48b62110b7cf@gmail.com> <39610B4F-8DE6-4E19-A6C8-5FAB882DD524@orthanc.ca> <CAMm+LwgqnPx2VBaoaWuU_YW547oRhQDTo48t4BokcwKqRSO+bw@mail.gmail.com> <F0EECBF6-F48E-425B-A6E8-65E5183FD36E@nbcuni.com> <CAMm+LwiT8+oiLwSX_9bekiDY6_3njbW9W_jKnP9FJkRYqwqRcQ@mail.gmail.com> <a6492c82-2b16-b087-c554-8ca38c8f5e84@huitema.net> <BA30F5B5AFA6760F140209A3@PSB> <CAMm+Lwh8HEgWCzgWieM09FsuBhHc+v1K-n4TKqyR6UvS17ha5Q@mail.gmail.com> <4f0c6d9e-7447-6268-11cd-8ba7ea9f7d06@nostrum.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 18 Aug 2017 21:59:20 -0400
X-Google-Sender-Auth: 0JCmWSmFk5VVEymwMiret8RK-TE
Message-ID: <CAMm+LwgaVNiJodMT=fCme2d_KY9tnhZ0vuJ1jUXi29t7MFqMvg@mail.gmail.com>
Subject: Re: Scope for self-destructing email?
To: Adam Roach <adam@nostrum.com>
Cc: John C Klensin <john-ietf@jck.com>, vaibhav singh <vaibhavsinghacads@gmail.com>,  IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c1b548a22816c05571198c0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MatCQSddgDcHMXcZ9YzGZapUl_I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 19 Aug 2017 01:59:26 -0000

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

On Fri, Aug 18, 2017 at 7:41 PM, Adam Roach <adam@nostrum.com> wrote:

> On 8/17/17 2:15 PM, Phillip Hallam-Baker wrote:
>
> If the next President of the US was to come to me and ask if I could
> provide a mechanism that would allow her to send an email message to
> members of her cabinet and that supported a 'recall' feature, I would hav=
e
> no hesitation in saying yes, conditional on some technical support which
> Microsoft and Apple and some others are both capable of providing.
>
>
> https://www.google.com/search?q=3D%22hdcp+stripper%22
>
> https://www.atomos.com/ninja/
>

=E2=80=8BThe point is that the President has already decided to extend an
extraordinary degree of trust to the cabinet by appointing them. They can
certainly be trusted not to make use of devices of that sort (and in any
case, their use can probably be disabled on the tablet class devices, which
is what I wanted assistance from Apple and Microsoft for).

That is precisely why the same consideration would not apply even to allies
as close as the UK.

We are all very much aware of the techniques that can be used to strip out
commodity DRM for copyright enforcement. They do not apply to applications
where the data is being shared between a few dozen or a few hundred users
to anything like the same degree as sharing the data with a quarter billion
folk round the world.

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Au=
g 18, 2017 at 7:41 PM, Adam Roach <span dir=3D"ltr">&lt;<a href=3D"mailto:a=
dam@nostrum.com" target=3D"_blank">adam@nostrum.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF"><span class=3D"">
    <div class=3D"m_4194459991482609493moz-cite-prefix">On 8/17/17 2:15 PM,=
 Phillip
      Hallam-Baker wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div style=3D"font-size:small">If the next
        President of the US was to come to me and ask if I could provide
        a mechanism that would allow her to send an email message to
        members of her cabinet and that supported a &#39;recall&#39; featur=
e, I
        would have no hesitation in saying yes, conditional on some
        technical support which Microsoft and Apple and some others are
        both capable of providing.</div>
    </blockquote>
    <p><br>
    </p>
    </span><p><a class=3D"m_4194459991482609493moz-txt-link-freetext" href=
=3D"https://www.google.com/search?q=3D%22hdcp+stripper%22" target=3D"_blank=
">https://www.google.com/search?<wbr>q=3D%22hdcp+stripper%22</a></p>
    <p><a class=3D"m_4194459991482609493moz-txt-link-freetext" href=3D"http=
s://www.atomos.com/ninja/" target=3D"_blank">https://www.atomos.com/ninja/<=
/a></p></div></blockquote><div><br></div><div class=3D"gmail_default" style=
=3D"font-size:small">=E2=80=8BThe point is that the President has already d=
ecided to extend an extraordinary degree of trust to the cabinet by appoint=
ing them. They can certainly be trusted not to make use of devices of that =
sort (and in any case, their use can probably be disabled on the tablet cla=
ss devices, which is what I wanted assistance from Apple and Microsoft for)=
.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></div><di=
v class=3D"gmail_default" style=3D"font-size:small">That is precisely why t=
he same consideration would not apply even to allies as close as the UK.</d=
iv><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div cl=
ass=3D"gmail_default" style=3D"font-size:small">We are all very much aware =
of the techniques that can be used to strip out commodity DRM for copyright=
 enforcement. They do not apply to applications where the data is being sha=
red between a few dozen or a few hundred users to anything like the same de=
gree as sharing the data with a quarter billion folk round the world.</div>=
<div class=3D"gmail_default" style=3D"font-size:small"><br></div></div></di=
v></div>

--94eb2c1b548a22816c05571198c0--


From nobody Fri Aug 18 19:01:39 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E518D1243F6 for <ietf@ietfa.amsl.com>; Fri, 18 Aug 2017 19:01:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level: 
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OZAFz_sqiqYy for <ietf@ietfa.amsl.com>; Fri, 18 Aug 2017 19:01:37 -0700 (PDT)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEA61132196 for <ietf@ietf.org>; Fri, 18 Aug 2017 19:01:36 -0700 (PDT)
Received: by mail-lf0-x22f.google.com with SMTP id y15so48814944lfd.5 for <ietf@ietf.org>; Fri, 18 Aug 2017 19:01:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=9ddoIuvwmnX647oeCRD3xQOmaeKBm4wGjWjp2Sl1Jek=; b=FfGUBdE9O6vNH7R+KiI14wvN+RUfkfIZ4AAPu0s2Z4UO2q/r59zxJ85PTjQ5TR47Z+ Hi407sdDRYqoa2zbwY/Ogsr7j7rmMIS28if9swuFe28EjqZ6jV70GTy/f6pkdaeRPVGq GK0IftK7lRCyAoy8Zpsug2Q3w5nX1rz+ksjJYbGSpRytfUQUG5MnEJRovl6x/E/9C5lF ++9thIZZjof1xQJAclHl64gz1WsNrCafVwIk+p/1BiTTG19PWh4AcabNIADqqzQHlB9G FqCEe+8p+L4tRv7OM2b1o8KAHGltPuGRPWKK91vlfe3/qESEi+/vu2CQLiM/2K/e0xRU 1feA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=9ddoIuvwmnX647oeCRD3xQOmaeKBm4wGjWjp2Sl1Jek=; b=uA1LjLbu0eK+x1b7dILez+7JM4ltJf52sGmtKD4GijdICmf9jp2cL5Hl3sU6hqeN1K 9Ip3R1MPFlKKoLECBKrBfVSylC19VoH/r3Rk7k59UprqLJdmZOcOYLNXic1Xn1d+Iylf 2lpHkjTTsqTqrXjGfe2Do1FljvZfi1u44A/ONMqFRJ2p0xQyQ66Nhcnepbjy8U1CNn6m QZ+FAjV5/oColMKlBA5s7zbmeovbEgrc6heniaaeIROsvuVqzi/K+nxetCG8Tgj0g8Us vktMpqJuwxp70GZ9vijw34LWZ6SKMzFEO28TTUUwBHeJY5635muEg+eOwkcQHHqW0vgx gMQQ==
X-Gm-Message-State: AHYfb5hqmIsvhC3q9KbC9O8OeERUuF2VVPsILgdKhNqCDJ8HZ45c1CXZ Qd1SVHNOSebkA/hgTB3YxJwXRwNqxg==
X-Received: by 10.46.2.197 with SMTP id y66mr3852600lje.54.1503108094985; Fri, 18 Aug 2017 19:01:34 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.25.142.199 with HTTP; Fri, 18 Aug 2017 19:01:33 -0700 (PDT)
In-Reply-To: <20170818013037.6784.qmail@ary.lan>
References: <7877.1502972732@obiwan.sandelman.ca> <20170818013037.6784.qmail@ary.lan>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 18 Aug 2017 22:01:33 -0400
X-Google-Sender-Auth: nrUEBfjkvTqFc23qRMrKKz5MIyY
Message-ID: <CAMm+Lwh=wO-LSY46F9+s_V0AhNVGA18LNQb1m4j_hsuV5uUVng@mail.gmail.com>
Subject: Re: Scope for self-destructing email?
To: John Levine <johnl@taugh.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary="94eb2c1cddea0f89c4055711a090"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/a2obzm9vqyA2Ug0QgGuaoZHU-JU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 19 Aug 2017 02:01:39 -0000

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

On Thu, Aug 17, 2017 at 9:30 PM, John Levine <johnl@taugh.com> wrote:

> In article <7877.1502972732@obiwan.sandelman.ca> you write:
> >This is an interesting idea.  For those of us who deal with many emails,
> >(particularly upon return from vacation), not having to deal with lunch
> plans
> >that have expired would in fact be nice.
>
> See RFC 2156 and RFC 4021, section 2.1.50.  To me the interesting
> question is why, since we've had Expires: for 20 years, nobody uses it
> outside of netnews.
>
> > That's a job for good-old-Usenet Supersedes:,
> >but that's one email overcoming another, and the whole thing needs
> >some cryptographic support.  Note that a merkle hash (a la s/key) would
> >probably suffice.
>
> Seems like overkill.  How about you pay attention to the Supersedes:
> (see RFC 2156 and RFC 4021, section 2.1.46) if old and new messages
> both have DKIM signatures from the same domain?  Same question about
> why after 20 years nobody uses it outside of netnews.
>

=E2=80=8BDKIM almost helps but this is a data level feature and it really d=
oes not
work well with a presentation layer authentication scheme like DKIM.

And to make it work well, you have to start from a messaging infrastructure
where every message and sender can authenticate themselves
cryptographically from the beginning...=E2=80=8B

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Au=
g 17, 2017 at 9:30 PM, John Levine <span dir=3D"ltr">&lt;<a href=3D"mailto:=
johnl@taugh.com" target=3D"_blank">johnl@taugh.com</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><span class=3D"">In article &lt;<a href=3D"=
mailto:7877.1502972732@obiwan.sandelman.ca">7877.1502972732@obiwan.<wbr>san=
delman.ca</a>&gt; you write:<br>
&gt;This is an interesting idea.=C2=A0 For those of us who deal with many e=
mails,<br>
&gt;(particularly upon return from vacation), not having to deal with lunch=
 plans<br>
&gt;that have expired would in fact be nice.<br>
<br>
</span>See RFC 2156 and RFC 4021, section 2.1.50.=C2=A0 To me the interesti=
ng<br>
question is why, since we&#39;ve had Expires: for 20 years, nobody uses it<=
br>
outside of netnews.<br>
<br>
&gt; That&#39;s a job for good-old-Usenet Supersedes:,<br>
<span class=3D"">&gt;but that&#39;s one email overcoming another, and the w=
hole thing needs<br>
&gt;some cryptographic support.=C2=A0 Note that a merkle hash (a la s/key) =
would<br>
&gt;probably suffice.<br>
<br>
</span>Seems like overkill.=C2=A0 How about you pay attention to the Supers=
edes:<br>
(see RFC 2156 and RFC 4021, section 2.1.46) if old and new messages<br>
both have DKIM signatures from the same domain?=C2=A0 Same question about<b=
r>
why after 20 years nobody uses it outside of netnews.<br></blockquote><div>=
<br></div><div class=3D"gmail_default" style=3D"font-size:small">=E2=80=8BD=
KIM almost helps but this is a data level feature and it really does not wo=
rk well with a presentation layer authentication scheme like DKIM.</div><di=
v class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D=
"gmail_default" style=3D"font-size:small">And to make it work well, you hav=
e to start from a messaging infrastructure where every message and sender c=
an authenticate themselves cryptographically from the beginning...=E2=80=8B=
</div></div></div></div>

--94eb2c1cddea0f89c4055711a090--


From nobody Sat Aug 19 07:21:15 2017
Return-Path: <roni.even@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8405E13282D; Sat, 19 Aug 2017 07:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nH-hJkiKAHNW; Sat, 19 Aug 2017 07:21:12 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 856E7132825; Sat, 19 Aug 2017 07:21:11 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML713-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DMX99228; Sat, 19 Aug 2017 14:21:09 +0000 (GMT)
Received: from DGGEMM404-HUB.china.huawei.com (10.3.20.212) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.301.0; Sat, 19 Aug 2017 15:21:08 +0100
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.138]) by DGGEMM404-HUB.china.huawei.com ([10.3.20.212]) with mapi id 14.03.0301.000; Sat, 19 Aug 2017 22:20:56 +0800
From: Roni Even <roni.even@huawei.com>
To: Dhruv Dhody <dhruv.dhody@huawei.com>, Roni Even <ron.even.tlv@gmail.com>,  "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-pce-rfc6006bis.all@ietf.org" <draft-ietf-pce-rfc6006bis.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [Pce] Genart last call review of draft-ietf-pce-rfc6006bis-03
Thread-Topic: [Pce] Genart last call review of draft-ietf-pce-rfc6006bis-03
Thread-Index: AQHTFDrKXuNsUXmJ/0aASYriy6cC9KKIDkRAgAO04uA=
Date: Sat, 19 Aug 2017 14:20:56 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD7FED7B@DGGEMM506-MBX.china.huawei.com>
References: <150263205807.26527.8869013927407425945@ietfa.amsl.com> <23CE718903A838468A8B325B80962F9B8CBB37A0@blreml501-mbx>
In-Reply-To: <23CE718903A838468A8B325B80962F9B8CBB37A0@blreml501-mbx>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.210.165.147]
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A010203.59984955.0048, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.3.138, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: af1ef5618c163fe384c012dbf9167f12
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UVNuiNgazh5xbeOJCYkzykA9uJw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 19 Aug 2017 14:21:14 -0000

Hi,
I did not see the text in RFC6006bis but this current text does not say muc=
h. If there is some work to reference in PCE  like pce-pcep-yang then add i=
t otherwise I suggest to delete this sentence
Roni

> -----Original Message-----
> From: Gen-art [mailto:gen-art-bounces@ietf.org] On Behalf Of Dhruv Dhody
> Sent: =E9=E5=ED=A0=E4 17 =E0=E5=E2=E5=F1=E8 2017 12:06
> To: Roni Even; gen-art@ietf.org
> Cc: draft-ietf-pce-rfc6006bis.all@ietf.org; pce@ietf.org; ietf@ietf.org
> Subject: Re: [Gen-art] [Pce] Genart last call review of draft-ietf-pce-
> rfc6006bis-03
>=20
> Hi Roni,
>=20
> Thanks for your comments. See inline...
>=20
> > -----Original Message-----
> > From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Roni Even
> > Sent: 13 August 2017 19:18
> > To: gen-art@ietf.org
> > Cc: draft-ietf-pce-rfc6006bis.all@ietf.org; pce@ietf.org;
> > ietf@ietf.org
> > Subject: [Pce] Genart last call review of draft-ietf-pce-rfc6006bis-03
> >
> > Reviewer: Roni Even
> > Review result: Ready with Nits
> >
> > I am the assigned Gen-ART reviewer for this draft. The General Area
> > Review Team (Gen-ART) reviews all IETF documents being processed by
> > the IESG for the IETF Chair.  Please treat these comments just like
> > any other last call comments.
> >
> > For more information, please see the FAQ at
> >
> > <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> >
> > Document: draft-ietf-pce-rfc6006bis-??
> > Reviewer: Roni Even
> > Review Date: 2017-08-13
> > IETF LC End Date: 2017-08-24
> > IESG Telechat date: 2017-08-31
> >
> > Summary: The document is ready for publication as standard track RFC
> >
> > I read all the document and also did a compare with RFC6006 to look at
> > the changes.
> >
> > Major issues:
> >
> > Minor issues:
> >
> > Nits/editorial comments:
> >
> > 1. In section 4.2 I am not sure why is this sentence there, is it for
> > the current yang document or for a future one. Why have it at
> > all?-"The PCEP YANG module [I-D.ietf-pce-pcep-yang] can be extended to
> > also include the P2MP related parameters."
> >
> [[Dhruv Dhody]] The text around MIB existed from RFC6006. Since then the
> focus has shifted to Yang.
> We wanted to keep this text about Yang to reflect that.
>=20
> How about we reword to -
>=20
>    The PCEP YANG model is specified in [I-D.ietf-pce-pcep-yang]. The
>    YANG models can be augmented to also include the P2MP related
>    parameters.
>=20
> Thanks again for your review.
>=20
> Regards,
> Dhruv
>=20
> Working Copy - https://github.com/dhruvdhody-
> huawei/ietf/blob/master/draft-ietf-pce-rfc6006bis-04.txt
>=20
>=20
>=20
> >
> > _______________________________________________
> > Pce mailing list
> > Pce@ietf.org
> > https://www.ietf.org/mailman/listinfo/pce
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Sat Aug 19 07:27:30 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B29E41323B8 for <ietf@ietfa.amsl.com>; Sat, 19 Aug 2017 07:27:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level: 
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=iecc.com header.b=jrpQHNW0; dkim=neutral reason="invalid (public key: not available)" header.d=taugh.com header.b=Ek3FkL5x
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GVXzPcCnJdVA for <ietf@ietfa.amsl.com>; Sat, 19 Aug 2017 07:27:26 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A2971321A2 for <ietf@ietf.org>; Sat, 19 Aug 2017 07:27:26 -0700 (PDT)
Received: (qmail 73599 invoked from network); 19 Aug 2017 14:27:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=11f7d.59984acd.k1707; bh=tZuv2JrJarpN9Zsb5+Dt9ybjy0K06yHBqZRSAvPCrbQ=; b=jrpQHNW05hUxZ0xmcuvtYqSxt2iAwU/f/YngBeujDQVwi2mLUj9VfhSANx9Efuoijz10zTJ2MHZYWlgQdg3kXRobUSxQ0V4vVIF9mPrsgEeLMvWuPSDYhYMNdkKJZO8w7TGCvS2TIpJGibpqNtVmeCjX86icIqOuVnt+mhVZQgMedjiOeW7BmHyb4Exm5VAuYWqHEoTTqr+BgqnhvncM5Jv/6IxgdoQpvS+knIj9z+2i1dS2Y04GQEXcGD3Ji6ZT
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=11f7d.59984acd.k1707; bh=tZuv2JrJarpN9Zsb5+Dt9ybjy0K06yHBqZRSAvPCrbQ=; b=Ek3FkL5x081AkSN11H29ifA7LGXxTmQ/Ns0+nACfxfFeeflNvXwHhCm6K2YqPgymtSsDyKR+LzkGit3Gsix2km97vPHjkaYkEPSXxUhR8b/xVJt7Eb95fyWykzj6dFir7YZzPieFu5GuCexQdtCe3HuPZLwioGg+/4eHJKcg0zw+mBOD50YAPX2s1Njqz5pp6HZhum3UPVqiENgCVnWz0hYm69cA8iVmFIUskjL4pS9Z5IoXdWsw2vJQC7kiA4zK
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 19 Aug 2017 14:27:24 -0000
Date: 19 Aug 2017 10:27:24 -0400
Message-ID: <alpine.OSX.2.21.1708191024470.65721@ary.local>
From: "John R Levine" <johnl@taugh.com>
To: "Phillip Hallam-Baker" <phill@hallambaker.com>
Cc: "IETF Discussion Mailing List" <ietf@ietf.org>, "Michael Richardson" <mcr+ietf@sandelman.ca>
Subject: Re: Scope for self-destructing email?
In-Reply-To: <CAMm+Lwh=wO-LSY46F9+s_V0AhNVGA18LNQb1m4j_hsuV5uUVng@mail.gmail.com>
References: <7877.1502972732@obiwan.sandelman.ca> <20170818013037.6784.qmail@ary.lan> <CAMm+Lwh=wO-LSY46F9+s_V0AhNVGA18LNQb1m4j_hsuV5uUVng@mail.gmail.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-288079867-1503152844=:65721"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CZU-4yCMh9G_Wdpg85ueAc_5T4Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 19 Aug 2017 14:27:28 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-288079867-1503152844=:65721
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Fri, 18 Aug 2017, Phillip Hallam-Baker wrote:
>> Seems like overkill.  How about you pay attention to the Supersedes:
>> (see RFC 2156 and RFC 4021, section 2.1.46) if old and new messages
>> both have DKIM signatures from the same domain?  Same question about
>> why after 20 years nobody uses it outside of netnews.
>
> ​DKIM almost helps but this is a data level feature and it really does not
> work well with a presentation layer authentication scheme like DKIM.

I suppose, but you'd need something like DKIM if you want to prevent 
attacks where the bad guy splices his headers onto your message, and it 
has the advantage that it exists and is widely deployed.

It's certainly not perfect, e.g., any gmail user could supersede anyone 
else's unless gmail limited what headers they sign, but that doesn't seem 
like a high value attack.

> And to make it work well, you have to start from a messaging infrastructure
> where every message and sender can authenticate themselves
> cryptographically from the beginning...​

  ... with a pony?

R's,
John
--0-288079867-1503152844=:65721--


From nobody Sun Aug 20 13:54:38 2017
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A24E132359; Sun, 20 Aug 2017 13:54:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Elwyn Davies <elwynd@dial.pipex.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-teas-pce-central-control.all@ietf.org, ietf@ietf.org, teas@ietf.org
Subject: Genart last call review of draft-ietf-teas-pce-central-control-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150326246998.3553.16986401070448324505@ietfa.amsl.com>
Date: Sun, 20 Aug 2017 13:54:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xmy4WPSwq0BehWcfYLYEmOo6YKk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 20 Aug 2017 20:54:30 -0000

Reviewer: Elwyn Davies
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-teas-pce-central-control-03
Reviewer: Elwyn Davies
Review Date: 2017-08-20
IETF LC End Date: 2017-08-24
IESG Telechat date: 2017-08-31

Summary:
Amost ready.  I found this a well-written and mostly readily comprehensible
document although it contains a couple of instances of unexplained SDN/PCE
jargon (notably 'southbound').  My main concern is that the archtecture
suggests that extensions to PCEP will a.s. be needed and implies that
mechanisms will be needed to provide multiple extensions but neither specifies
detailed guidance as to how this might be done or points to work in progress
that would provide this guidance.  The implication of the statements in this
document are that an implementation or deployment might need to check if
particlar extensions are implemented in communication partners and also how to
behave if an unreconixed extension is received especially to avoid possible
DoS.   The other minor issues are only just abve the level of nits.

Major issues:
None

Minor issues:

Abstract:  The abstract is probably overlong.

s1:  RFC 4655 is itself an architecture that introduces the PCE.  It would be
helpful to explain that this document is an extension of the basic PCE
arcitecture except that it relies on the specific use f the PCEP for
intercommunication between architectural elements providing traffic control and
routing whereas RFC 4655 does not assume any particular protocol.

s3.2: It would be desirable to reiterate the problem of synchronization
mentioned in s2.1.2 which is relevant to all the high level functions.

s4: Since this document effectively gurantees that extensions to PCEP will be
created and since RFC 5440 contains no extensibility procedures/guidelines, it
seems to me that either this document should indicate how PCEP extensions and
profiles are added to the base protocol or should point  to a (normative and
currently non-existent) document that updates RFC 5440 and defines how
extensions shoould be structured and provides ways for implementations to
determine what is supported, if necessary.

s5, para 2:  The second part of this paragraph;
   However, debate will rage over overall system security and the opportunity
   for attacks in an architecture with a central controller since the network
   can be vulnerable to denial of service attacks on the controller, and the
   forwarding system may be harmed by attacks on the messages sent to
   individual NEs. In short, while the interactions with a PCE-based controller
   are not substantially different from those in any other SDN architecture,
   the security implications of SDN are still open for discussion. The IRTF's
   SDN Research Group (SDNRG) discussed this topic.
This text needs to be rewritten to be suitable for inclusion in an RFC that is
a document of record.

s6:  The PCE, depending on which of the aspects mentioned in s3 and the
technology being managed (LSPs, transport paths, etc.) are involved in a
particular imlemetation/deployment, will need to access the relevant state
information in NEs and possibly other PCEs using relevant managent protcol(s)
and MIBs or similar.  Integrating this state information with the PCEP
management information wil be key to effective operation of the centralized PCE
system.

s10:  It is arguable, IMO, that RFC 5440 and I-D.ietf-pce-pce-initiated-lsp are
normative references.  The architecture implies their usage and someone
implementing the architecture would need to be familiar with the details of the
extended PCEP, particularly in respect of the manageability and security
aspects of the protocol.

Nits/editorial comments:

Abstract, para 1: Statements of implied omnipotence by mortals a.s. lead to
hubristic consequences...  s/any definition of "optimal"/virtually any
definition of "optimal"/

Abstract (and subseqently):  The term 'southbound' is SDN specific jargon and
should be explained.  Given that the abstract is already (IMO) too long, it
would be wise to remove it from the abstract (I don't think it is essential)
and provide the explation in s1.

s1, para 4: See comment above... s/any form of routed or switched
network./virtually any form of routed or switched network./

s2, para 2 and Figures 1-7:  It would be useful to add a note in s2 to indicate
that the TED box in all the figures should imply that other databases may also
be accessed.

s2, last para (just before Fig.3): s/use case- specific/use case-specific [or
use case specific]/

s2.1, para 1: The text at the beginning of the para doesn't read very easily -
the 'or' disguises the fact that the two problems are on either sideof the
'or'.  Suggest someting like: OLD: Systems with central controllers are
vulnerable to two problems: failure or overload of the single controller. NEW:
Systems with a single central controllers are vulnerable to two problems:
  - controller failure, and
  - controller overload.
ENDS

s3.1.4, last para:
     new protocol extensions may be needed, and some are already being worked on
     in [I-D.ietf-pce-wson-rwa-ext].
 The second clause of this is not future proof:   Suggest
s/and some are already being worked on in [I-D.ietf-pce-wson-rwa-ext]./as, for
example, described  in [I-D.ietf-pce-wson-rwa-ext]./

s3.1.5, para 1: s/the header or a packet/the header of a packet/ (I think -
certainly for IPv6 use case)

s3.2.2, last para:  The final sentence is probably superfluous - and, if it
remains, probably needs a reference to explain what a FEC is.



From nobody Mon Aug 21 08:40:47 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F6E013235A; Mon, 21 Aug 2017 08:40:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Pete Resnick <presnick@qti.qualcomm.com>
To: <gen-art@ietf.org>
Cc: ospf@ietf.org, draft-ietf-ospf-encapsulation-cap.all@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-ietf-ospf-encapsulation-cap-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150333004648.6756.16820249680656378919@ietfa.amsl.com>
Date: Mon, 21 Aug 2017 08:40:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iPRkwr6PzQUVyyhwfiEz5c-HrR8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 21 Aug 2017 15:40:47 -0000

Reviewer: Pete Resnick
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-ospf-encapsulation-cap-06
Reviewer: Pete Resnick
Review Date: 2017-08-21
IETF LC End Date: 2017-08-28
IESG Telechat date: 2017-08-31

Summary: Almost Ready

The content of this document is fine. However, I think the IANA registry stuff
is not ready.

Major issues:

I think the registrations other than for Endpoint and Color are incorrect and
should not be in this document. Certainly the "Reference" field for 1, 2, 5, 6,
and 7 should not be "This document", given that the syntax and semantics for
these values are defined in other documents. I also think that having things in
this registry which are also used by the BGP registry is asking for trouble:
You wouldn't want the references for the two registries to get out of sync.
This seems like a mess to me. Would it be possible for IANA to simply rename
the "BGP Tunnel Encapsulation Attribute Sub-TLVs" registry to "BGP and OSPF
Tunnel Encapsulation Attribute Sub-TLVs", and share the registry between the
two protocols? Then have this (and other) document(s) add values to that
registry. That way, the documents that actually define the codepoints can be
put into the registry.

Minor issues:

None.

Nits/editorial comments:

In section 7.1, please add:

   [RFC Editor: Please replace "TBD1" in section 3 with the registry value
   allocated by IANA, and remove this note].

That will save them from hunting.


From nobody Mon Aug 21 08:58:22 2017
Return-Path: <acee@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 060B3132A67; Mon, 21 Aug 2017 08:58:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level: 
X-Spam-Status: No, score=-14.521 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cgDIHrLfHOm5; Mon, 21 Aug 2017 08:58:04 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D8AD132026; Mon, 21 Aug 2017 08:58:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3064; q=dns/txt; s=iport; t=1503331083; x=1504540683; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=No6ajkc5S4oiXBoZQKX/Rso2HVW9HUEaFM05JmBKDOA=; b=RANbbanpKpC47TI6OWgVrihdHsEJuk4F15WXBJj0RiVY5Czv6oL6Lv7j BS+jidPgOSsdE9mysL7j1qskA9j7ZDliQ3ZYDFKwZ1DA5vkkhuprzAK8R 1Njr7HpvvU5EJaCEnVqeZyK/cqp3AAnrkDjSLe5xnw/eBPriYOrGYhDHf Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DQAADeAZtZ/4MNJK1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1pkgRUHg3CKG5AWgW6WHoISLIUbAhqDdT8YAQIBAQEBAQEBayi?= =?us-ascii?q?FGQEEASMRRQULAgEIDgYGAiYCAgIwFRACBAENBYopCBCvN4Imi10BAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEYBYELgh2CAoMvgyeEc4MTgmEFmB2IMgKHUoxughCFYYp?= =?us-ascii?q?tlh8BHziBCncVh2N2iVKBDwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.41,409,1498521600"; d="scan'208";a="283321334"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 21 Aug 2017 15:58:02 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v7LFw2Gs028335 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 21 Aug 2017 15:58:02 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 21 Aug 2017 11:58:01 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Mon, 21 Aug 2017 11:58:01 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "ospf@ietf.org" <ospf@ietf.org>, "draft-ietf-ospf-encapsulation-cap.all@ietf.org" <draft-ietf-ospf-encapsulation-cap.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Genart last call review of draft-ietf-ospf-encapsulation-cap-06
Thread-Topic: Genart last call review of draft-ietf-ospf-encapsulation-cap-06
Thread-Index: AQHTGpPf4Ro7Zv5kzUulT2W0ZGd6S6KO90qA
Date: Mon, 21 Aug 2017 15:58:01 +0000
Message-ID: <D5C07A8A.C26DE%acee@cisco.com>
References: <150333004648.6756.16820249680656378919@ietfa.amsl.com>
In-Reply-To: <150333004648.6756.16820249680656378919@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.201]
Content-Type: text/plain; charset="utf-8"
Content-ID: <CB6E2D895E7B23498A34CEACF9E45ED6@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rJ2AGnVvpfqUPBbD_PA4IRDD1EU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 21 Aug 2017 15:58:06 -0000

SGkgUGV0ZSwNCg0KT24gOC8yMS8xNywgMTE6NDAgQU0sICJQZXRlIFJlc25pY2siIDxwcmVzbmlj
a0BxdGkucXVhbGNvbW0uY29tPiB3cm90ZToNCg0KPlJldmlld2VyOiBQZXRlIFJlc25pY2sNCj5S
ZXZpZXcgcmVzdWx0OiBBbG1vc3QgUmVhZHkNCj4NCj5JIGFtIHRoZSBhc3NpZ25lZCBHZW4tQVJU
IHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBUaGUgR2VuZXJhbCBBcmVhDQo+UmV2aWV3IFRlYW0g
KEdlbi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3NlZA0KPmJ5
IHRoZSBJRVNHIGZvciB0aGUgSUVURiBDaGFpci4gIFBsZWFzZSB0cmVhdCB0aGVzZSBjb21tZW50
cyBqdXN0DQo+bGlrZSBhbnkgb3RoZXIgbGFzdCBjYWxsIGNvbW1lbnRzLg0KPg0KPkZvciBtb3Jl
IGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQNCj4NCj48aHR0cHM6Ly90cmFjLmll
dGYub3JnL3RyYWMvZ2VuL3dpa2kvR2VuQXJ0ZmFxPi4NCj4NCj5Eb2N1bWVudDogZHJhZnQtaWV0
Zi1vc3BmLWVuY2Fwc3VsYXRpb24tY2FwLTA2DQo+UmV2aWV3ZXI6IFBldGUgUmVzbmljaw0KPlJl
dmlldyBEYXRlOiAyMDE3LTA4LTIxDQo+SUVURiBMQyBFbmQgRGF0ZTogMjAxNy0wOC0yOA0KPklF
U0cgVGVsZWNoYXQgZGF0ZTogMjAxNy0wOC0zMQ0KPg0KPlN1bW1hcnk6IEFsbW9zdCBSZWFkeQ0K
Pg0KPlRoZSBjb250ZW50IG9mIHRoaXMgZG9jdW1lbnQgaXMgZmluZS4gSG93ZXZlciwgSSB0aGlu
ayB0aGUgSUFOQSByZWdpc3RyeQ0KPnN0dWZmDQo+aXMgbm90IHJlYWR5Lg0KPg0KPk1ham9yIGlz
c3VlczoNCj4NCj5JIHRoaW5rIHRoZSByZWdpc3RyYXRpb25zIG90aGVyIHRoYW4gZm9yIEVuZHBv
aW50IGFuZCBDb2xvciBhcmUgaW5jb3JyZWN0DQo+YW5kDQo+c2hvdWxkIG5vdCBiZSBpbiB0aGlz
IGRvY3VtZW50LiBDZXJ0YWlubHkgdGhlICJSZWZlcmVuY2UiIGZpZWxkIGZvciAxLCAyLA0KPjUs
IDYsDQo+YW5kIDcgc2hvdWxkIG5vdCBiZSAiVGhpcyBkb2N1bWVudCIsIGdpdmVuIHRoYXQgdGhl
IHN5bnRheCBhbmQgc2VtYW50aWNzDQo+Zm9yDQo+dGhlc2UgdmFsdWVzIGFyZSBkZWZpbmVkIGlu
IG90aGVyIGRvY3VtZW50cy4NCg0KVGhlIGF1dGhvcnMgY2FuIGZpeCB0aGVzZS4NCg0KPiBJIGFs
c28gdGhpbmsgdGhhdCBoYXZpbmcgdGhpbmdzIGluDQo+dGhpcyByZWdpc3RyeSB3aGljaCBhcmUg
YWxzbyB1c2VkIGJ5IHRoZSBCR1AgcmVnaXN0cnkgaXMgYXNraW5nIGZvcg0KPnRyb3VibGU6DQo+
WW91IHdvdWxkbid0IHdhbnQgdGhlIHJlZmVyZW5jZXMgZm9yIHRoZSB0d28gcmVnaXN0cmllcyB0
byBnZXQgb3V0IG9mDQo+c3luYy4NCj5UaGlzIHNlZW1zIGxpa2UgYSBtZXNzIHRvIG1lLiBXb3Vs
ZCBpdCBiZSBwb3NzaWJsZSBmb3IgSUFOQSB0byBzaW1wbHkNCj5yZW5hbWUNCj50aGUgIkJHUCBU
dW5uZWwgRW5jYXBzdWxhdGlvbiBBdHRyaWJ1dGUgU3ViLVRMVnMiIHJlZ2lzdHJ5IHRvICJCR1Ag
YW5kDQo+T1NQRg0KPlR1bm5lbCBFbmNhcHN1bGF0aW9uIEF0dHJpYnV0ZSBTdWItVExWcyIsIGFu
ZCBzaGFyZSB0aGUgcmVnaXN0cnkgYmV0d2Vlbg0KPnRoZQ0KPnR3byBwcm90b2NvbHM/IFRoZW4g
aGF2ZSB0aGlzIChhbmQgb3RoZXIpIGRvY3VtZW50KHMpIGFkZCB2YWx1ZXMgdG8gdGhhdA0KPnJl
Z2lzdHJ5LiBUaGF0IHdheSwgdGhlIGRvY3VtZW50cyB0aGF0IGFjdHVhbGx5IGRlZmluZSB0aGUg
Y29kZXBvaW50cyBjYW4NCj5iZQ0KPnB1dCBpbnRvIHRoZSByZWdpc3RyeS4NCg0KV2XigJl2ZSBh
bHJlYWR5IGhhZCBhIHByb3RyYWN0ZWQgZGlzY3Vzc2lvbiBvbiB0aGUgSUFOQSByZWdpc3RyaWVz
LiBJdCBpcw0Kbm90IHBvc3NpYmxlIGFzIEJHUCBhZHZlcnRpc2VzIHNvbWUgb2YgdGhlIGF0dHJp
YnV0ZXMgaW4gQkdQIGNvbW11bml0aWVzDQpyYXRoZXIgdGhhbiB0dW5uZWwgYXR0cmlidXRlcyAo
ZS5nLiwgY29sb3IpLg0KDQpUaGFua3MsDQpBY2VlIA0KDQo+DQo+TWlub3IgaXNzdWVzOg0KPg0K
Pk5vbmUuDQo+DQo+Tml0cy9lZGl0b3JpYWwgY29tbWVudHM6DQo+DQo+SW4gc2VjdGlvbiA3LjEs
IHBsZWFzZSBhZGQ6DQo+DQo+ICAgW1JGQyBFZGl0b3I6IFBsZWFzZSByZXBsYWNlICJUQkQxIiBp
biBzZWN0aW9uIDMgd2l0aCB0aGUgcmVnaXN0cnkgdmFsdWUNCj4gICBhbGxvY2F0ZWQgYnkgSUFO
QSwgYW5kIHJlbW92ZSB0aGlzIG5vdGVdLg0KPg0KPlRoYXQgd2lsbCBzYXZlIHRoZW0gZnJvbSBo
dW50aW5nLg0KPg0KDQo=


From nobody Mon Aug 21 09:13:25 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB6F0132A6D; Mon, 21 Aug 2017 09:13:12 -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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MvNLrFYzJB5U; Mon, 21 Aug 2017 09:13:06 -0700 (PDT)
Received: from alexa-out-lv-01.qualcomm.com (alexa-out.qualcomm.com [129.46.98.28]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B60413234C; Mon, 21 Aug 2017 09:13:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1503331986; x=1534867986; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=6cZCzHTqsE0VQqGGk1MG4Myrxt7oU8L8ejrQfpCGP58=; b=r+r+2FzvbGMrp5Dd+w0AlR5ufdUWdZgMaYfTM0E6Pblgd/Hps/8yK8Rw JKw3lNVWpJqpNxzyOUVRYBrvnWYAoUgS9dS58DLDuBOTxyMGCH+SSLz2n /PpzlY/73hgoFppTxHITl/96oWUJLMF7X4OM7rfaBHXHPDEq2SEAOhWgI k=;
X-IronPort-AV: E=Sophos;i="5.41,409,1498546800";  d="scan'208";a="3580394"
Received: from ironmsg02-l-new.qualcomm.com (HELO ironmsg02-L.qualcomm.com) ([10.53.140.109]) by alexa-out-lv-01.qualcomm.com with ESMTP; 21 Aug 2017 09:12:57 -0700
X-IronPort-AV: E=McAfee;i="5900,7806,8630"; a="985733146"
X-MGA-submission: =?us-ascii?q?MDFPHnA1tzoUNcez7ngCQzPKpMAIjB4ooNxMfW?= =?us-ascii?q?IeUY/YsXmtCe+tP4i+hOVvuoFKmRk0gczmJOAju5FzhYl5FfjBNLLQ6n?= =?us-ascii?q?YcXMZYQYOxket/V9eIO+6OMeZuNb+kwkGS2+5NH07618VHHrcunqaQz1?= =?us-ascii?q?ef?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 21 Aug 2017 09:12:56 -0700
Received: from [10.110.56.223] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 21 Aug 2017 09:12:55 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Acee Lindem <acee@cisco.com>
CC: "gen-art@ietf.org" <gen-art@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, "draft-ietf-ospf-encapsulation-cap.all@ietf.org" <draft-ietf-ospf-encapsulation-cap.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Genart last call review of draft-ietf-ospf-encapsulation-cap-06
Date: Mon, 21 Aug 2017 11:12:54 -0500
Message-ID: <5B41B581-74F4-4F57-B811-F535044350F4@qti.qualcomm.com>
In-Reply-To: <D5C07A8A.C26DE%acee@cisco.com>
References: <150333004648.6756.16820249680656378919@ietfa.amsl.com> <D5C07A8A.C26DE%acee@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01G.na.qualcomm.com (10.85.0.33) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ztr8jOBs5SgI6mnspgz7FV1CPs0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 21 Aug 2017 16:13:13 -0000

On 21 Aug 2017, at 10:58, Acee Lindem (acee) wrote:

> Hi Pete,
>
> On 8/21/17, 11:40 AM, "Pete Resnick" <presnick@qti.qualcomm.com> 
> wrote:
>
>> Reviewer: Pete Resnick
>> Review result: Almost Ready
>>
>> I am the assigned Gen-ART reviewer for this draft. The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair.  Please treat these comments just
>> like any other last call comments.
>>
>> For more information, please see the FAQ at
>>
>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>
>> Document: draft-ietf-ospf-encapsulation-cap-06
>> Reviewer: Pete Resnick
>> Review Date: 2017-08-21
>> IETF LC End Date: 2017-08-28
>> IESG Telechat date: 2017-08-31
>>
>> Summary: Almost Ready
>>
>> The content of this document is fine. However, I think the IANA 
>> registry
>> stuff
>> is not ready.
>>
>> Major issues:
>>
>> I think the registrations other than for Endpoint and Color are 
>> incorrect
>> and
>> should not be in this document. Certainly the "Reference" field for 
>> 1, 2,
>> 5, 6,
>> and 7 should not be "This document", given that the syntax and 
>> semantics
>> for
>> these values are defined in other documents.
>
> The authors can fix these.

For 1, 2, 6, and 7, that's easy; the drafts defining the values can do 
the registrations. For 5, the reference would be to an existing RFC that 
doesn't do the registration. I'm not sure what to do about that; perhaps 
register it here and make the reference both 5640 and this document. 
However, when someone goes to update 5640 some day, they're going to 
have to put into the IANA considerations to update both the OSPF and BGP 
registries. I'm not sure how to keep track of that. Perhaps saying that 
this document "Updates: 5640"? That doesn't seem great either.

>> I also think that having things in
>> this registry which are also used by the BGP registry is asking for
>> trouble:
>> You wouldn't want the references for the two registries to get out of
>> sync.
>> This seems like a mess to me. Would it be possible for IANA to simply
>> rename
>> the "BGP Tunnel Encapsulation Attribute Sub-TLVs" registry to "BGP 
>> and
>> OSPF
>> Tunnel Encapsulation Attribute Sub-TLVs", and share the registry 
>> between
>> the
>> two protocols? Then have this (and other) document(s) add values to 
>> that
>> registry. That way, the documents that actually define the codepoints 
>> can
>> be
>> put into the registry.
>
> We’ve already had a protracted discussion on the IANA registries. It 
> is
> not possible as BGP advertises some of the attributes in BGP 
> communities
> rather than tunnel attributes (e.g., color).

Yuck. I'll try not to prolong the discussion much further, but did you 
consider the possibility of having some of the attributes appear twice, 
with one saying "For BGP communities only" and the other saying, "For 
OSPF tunnels only"? What a lovely mess. :-(

> Thanks,
> Acee

Cheers,

pr

>> Minor issues:
>>
>> None.
>>
>> Nits/editorial comments:
>>
>> In section 7.1, please add:
>>
>>   [RFC Editor: Please replace "TBD1" in section 3 with the registry 
>> value
>>   allocated by IANA, and remove this note].
>>
>> That will save them from hunting.
>>


-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Mon Aug 21 10:03:07 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3D1C13232C for <ietf@ietfa.amsl.com>; Mon, 21 Aug 2017 10:03:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.713
X-Spam-Level: 
X-Spam-Status: No, score=-2.713 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7BIEm3_0Fqyk for <ietf@ietfa.amsl.com>; Mon, 21 Aug 2017 10:03:03 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52CF2132A80 for <ietf@ietf.org>; Mon, 21 Aug 2017 10:03:03 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 1BB3058C4BD; Mon, 21 Aug 2017 19:02:59 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 0653BB0C964; Mon, 21 Aug 2017 19:02:58 +0200 (CEST)
Date: Mon, 21 Aug 2017 19:02:58 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: John C Klensin <john-ietf@jck.com>
Cc: ietf@ietf.org, vaibhav singh <vaibhavsinghacads@gmail.com>
Subject: Re: Scope for self-destructing email?
Message-ID: <20170821170258.GA21915@faui40p.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qhGnrBQprEs1OxOjeSzE4ccHWdI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 21 Aug 2017 17:03:06 -0000

John,

I did like to use a couple of those nice email functions driven
by special headers. IMHO the main reason why those never catched on
is the absence of easy ways for users to figure out how much their
software (MTU/MUA) sucks. 

One thing IMHO that would help are mechanisms to provide users with
an easy ability to learn what their software is claiming to support,
and what's missing. User experience should be some web-page that
explains this to the user in easy terms and ideally even suggests
to create RFE emails to the vendors. The question would then be what
standards APIs one would need to enable interested third parties
to generate such web pages (including IETF).

Eg: Have some yang model/API into MTU/MUA that declares the features
supported, maybe also some options to exercise probes/tests and provide
authentication to do this (eg: via the usual "i am foo@bar.example.com
because i can show some token received in email to that address").

Admittedly, i've been annoyed for 25 years that IETF unlike ISO is not
doing PICS, so maybe this is a more pragmatic approach to tackle
that gap. And one that would be more user friendly, dynamic and maybe
even more reliable (depending on how much actual probing instead of
just declaration you would be able to do via the API).

Toerless

On Thu, Aug 17, 2017 at 09:23:06AM -0400, John C Klensin wrote:
> Folks,
> 
> It seems to me that three things are emerging on this thread.
> 
> (1) The original proposal and problem to be solved, at least as
> most of us understood it, was to allow a sender to send some
> sort of notification that would cause all copies of a message to
> be  automagically destroyed.  We appear to have unanimity that
> problem is unsolvable, at least in the general case and/or in
> the absence of universal trust.
> 
> (2) We have considerable experience (in both email and netnew)
> with putting out messages with expiry dates as information for
> the recipient (whether expected to be acted on automatically or
> not).  While there are important exceptions, they have never
> been as useful as was apparently assumed when they were
> adopted... to the point that the IANA registry entries for the
> relevant email header fields identify them as obsolete.  We have
> less experience with the originator of an already-sent message
> as expired or obsolete, but no evidence has been offered so far
> that such a facility would be appreciably more useful than the
> "Expires:" header field.
> 
> (3) We have now reached the stage in which people seem to be
> discussing alternate problems that can be solved.  That isn't
> very hard, but those alternate problems are not the original one
> and little or no case is being made that the new problems are
> worth solving or that solutions would be useful, even if they
> are feasible.
> 
> It seems to me that, if people believe there is a problem worth
> solving and if they think they have a feasible solution, we need
> to see an I-D that explains both, rather than continuing to
> circle around an ever-expanding collection of possible issues on
> the IETF list in the absence of such a draft.
> 
>      john

-- 
---
tte@cs.fau.de


From nobody Mon Aug 21 11:44:53 2017
Return-Path: <acee@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DB57132709; Mon, 21 Aug 2017 11:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 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, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fc3vdYTdojAn; Mon, 21 Aug 2017 11:44:43 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB9E3132A9A; Mon, 21 Aug 2017 11:44:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5226; q=dns/txt; s=iport; t=1503341073; x=1504550673; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=hZmZetzPMYsGR1KjbHzHr1ADt75i/vs9H5ICe3+u4fg=; b=XK/pqZnsEA8HBiGa1RhHrTXL5HtxIbooL7W9g6BuVfgxsAOOnswqiWvF XQncvpz/KnC7mWNSnnksw3e2trFOTVTU4D37l6LR24jxHlgrja2kdd+B4 OF/0uflvX8JeG9UoNzfFU6tusvxAvE92+Imx4engOdt1TmSGym2ppDZFb E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DeAACmKZtZ/5BdJa1bAxYDAQEBAQEBA?= =?us-ascii?q?QEBAQEHAQEBAQGDWmSBFQeDcIobkBeBbpYeghIshRsCGoN2PxgBAgEBAQEBAQF?= =?us-ascii?q?rKIUYAQEBAQIBIxFFEAIBCA4GBAICJgICAjAVEAIEDgUbig4IEK8ygiaLXwEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAR2BC4IdggKDL4MnhHMXCiaCTIJhBaBPAodSjG6?= =?us-ascii?q?CEIVhim2JaYw2AR84gQp3FYVgHIFndokPgQ8BAQE?=
X-IronPort-AV: E=Sophos;i="5.41,409,1498521600"; d="scan'208";a="446388575"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Aug 2017 18:44:33 +0000
Received: from XCH-RTP-011.cisco.com (xch-rtp-011.cisco.com [64.101.220.151]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id v7LIiW6M007490 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 21 Aug 2017 18:44:33 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-011.cisco.com (64.101.220.151) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 21 Aug 2017 14:44:32 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Mon, 21 Aug 2017 14:44:32 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
CC: "gen-art@ietf.org" <gen-art@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, "draft-ietf-ospf-encapsulation-cap.all@ietf.org" <draft-ietf-ospf-encapsulation-cap.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Genart last call review of draft-ietf-ospf-encapsulation-cap-06
Thread-Topic: Genart last call review of draft-ietf-ospf-encapsulation-cap-06
Thread-Index: AQHTGpPf4Ro7Zv5kzUulT2W0ZGd6S6KO90qAgABHTAD//+dBAA==
Date: Mon, 21 Aug 2017 18:44:32 +0000
Message-ID: <D5C0A175.C277A%acee@cisco.com>
References: <150333004648.6756.16820249680656378919@ietfa.amsl.com> <D5C07A8A.C26DE%acee@cisco.com> <5B41B581-74F4-4F57-B811-F535044350F4@qti.qualcomm.com>
In-Reply-To: <5B41B581-74F4-4F57-B811-F535044350F4@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.201]
Content-Type: text/plain; charset="utf-8"
Content-ID: <167EE52B6ABAC6448E0EF99B087A9DBD@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2jfui5v9y6bRYN8w_kqwzR04bBs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 21 Aug 2017 18:44:52 -0000

DQoNCk9uIDgvMjEvMTcsIDEyOjEyIFBNLCAiUGV0ZSBSZXNuaWNrIiA8cHJlc25pY2tAcXRpLnF1
YWxjb21tLmNvbT4gd3JvdGU6DQoNCj5PbiAyMSBBdWcgMjAxNywgYXQgMTA6NTgsIEFjZWUgTGlu
ZGVtIChhY2VlKSB3cm90ZToNCj4NCj4+IEhpIFBldGUsDQo+Pg0KPj4gT24gOC8yMS8xNywgMTE6
NDAgQU0sICJQZXRlIFJlc25pY2siIDxwcmVzbmlja0BxdGkucXVhbGNvbW0uY29tPg0KPj4gd3Jv
dGU6DQo+Pg0KPj4+IFJldmlld2VyOiBQZXRlIFJlc25pY2sNCj4+PiBSZXZpZXcgcmVzdWx0OiBB
bG1vc3QgUmVhZHkNCj4+Pg0KPj4+IEkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIg
Zm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsIEFyZWENCj4+PiBSZXZpZXcgVGVhbSAoR2VuLUFS
VCkgcmV2aWV3cyBhbGwgSUVURiBkb2N1bWVudHMgYmVpbmcgcHJvY2Vzc2VkDQo+Pj4gYnkgdGhl
IElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLiAgUGxlYXNlIHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1
c3QNCj4+PiBsaWtlIGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQo+Pj4NCj4+PiBGb3Ig
bW9yZSBpbmZvcm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0DQo+Pj4NCj4+PiA8aHR0cHM6
Ly90cmFjLmlldGYub3JnL3RyYWMvZ2VuL3dpa2kvR2VuQXJ0ZmFxPi4NCj4+Pg0KPj4+IERvY3Vt
ZW50OiBkcmFmdC1pZXRmLW9zcGYtZW5jYXBzdWxhdGlvbi1jYXAtMDYNCj4+PiBSZXZpZXdlcjog
UGV0ZSBSZXNuaWNrDQo+Pj4gUmV2aWV3IERhdGU6IDIwMTctMDgtMjENCj4+PiBJRVRGIExDIEVu
ZCBEYXRlOiAyMDE3LTA4LTI4DQo+Pj4gSUVTRyBUZWxlY2hhdCBkYXRlOiAyMDE3LTA4LTMxDQo+
Pj4NCj4+PiBTdW1tYXJ5OiBBbG1vc3QgUmVhZHkNCj4+Pg0KPj4+IFRoZSBjb250ZW50IG9mIHRo
aXMgZG9jdW1lbnQgaXMgZmluZS4gSG93ZXZlciwgSSB0aGluayB0aGUgSUFOQQ0KPj4+IHJlZ2lz
dHJ5DQo+Pj4gc3R1ZmYNCj4+PiBpcyBub3QgcmVhZHkuDQo+Pj4NCj4+PiBNYWpvciBpc3N1ZXM6
DQo+Pj4NCj4+PiBJIHRoaW5rIHRoZSByZWdpc3RyYXRpb25zIG90aGVyIHRoYW4gZm9yIEVuZHBv
aW50IGFuZCBDb2xvciBhcmUNCj4+PiBpbmNvcnJlY3QNCj4+PiBhbmQNCj4+PiBzaG91bGQgbm90
IGJlIGluIHRoaXMgZG9jdW1lbnQuIENlcnRhaW5seSB0aGUgIlJlZmVyZW5jZSIgZmllbGQgZm9y
DQo+Pj4gMSwgMiwNCj4+PiA1LCA2LA0KPj4+IGFuZCA3IHNob3VsZCBub3QgYmUgIlRoaXMgZG9j
dW1lbnQiLCBnaXZlbiB0aGF0IHRoZSBzeW50YXggYW5kDQo+Pj4gc2VtYW50aWNzDQo+Pj4gZm9y
DQo+Pj4gdGhlc2UgdmFsdWVzIGFyZSBkZWZpbmVkIGluIG90aGVyIGRvY3VtZW50cy4NCj4+DQo+
PiBUaGUgYXV0aG9ycyBjYW4gZml4IHRoZXNlLg0KPg0KPkZvciAxLCAyLCA2LCBhbmQgNywgdGhh
dCdzIGVhc3k7IHRoZSBkcmFmdHMgZGVmaW5pbmcgdGhlIHZhbHVlcyBjYW4gZG8NCj50aGUgcmVn
aXN0cmF0aW9ucy4gRm9yIDUsIHRoZSByZWZlcmVuY2Ugd291bGQgYmUgdG8gYW4gZXhpc3Rpbmcg
UkZDIHRoYXQNCj5kb2Vzbid0IGRvIHRoZSByZWdpc3RyYXRpb24uIEknbSBub3Qgc3VyZSB3aGF0
IHRvIGRvIGFib3V0IHRoYXQ7IHBlcmhhcHMNCj5yZWdpc3RlciBpdCBoZXJlIGFuZCBtYWtlIHRo
ZSByZWZlcmVuY2UgYm90aCA1NjQwIGFuZCB0aGlzIGRvY3VtZW50Lg0KPkhvd2V2ZXIsIHdoZW4g
c29tZW9uZSBnb2VzIHRvIHVwZGF0ZSA1NjQwIHNvbWUgZGF5LCB0aGV5J3JlIGdvaW5nIHRvDQo+
aGF2ZSB0byBwdXQgaW50byB0aGUgSUFOQSBjb25zaWRlcmF0aW9ucyB0byB1cGRhdGUgYm90aCB0
aGUgT1NQRiBhbmQgQkdQDQo+cmVnaXN0cmllcy4gSSdtIG5vdCBzdXJlIGhvdyB0byBrZWVwIHRy
YWNrIG9mIHRoYXQuIFBlcmhhcHMgc2F5aW5nIHRoYXQNCj50aGlzIGRvY3VtZW50ICJVcGRhdGVz
OiA1NjQwIj8gVGhhdCBkb2Vzbid0IHNlZW0gZ3JlYXQgZWl0aGVyLg0KPg0KPj4+IEkgYWxzbyB0
aGluayB0aGF0IGhhdmluZyB0aGluZ3MgaW4NCj4+PiB0aGlzIHJlZ2lzdHJ5IHdoaWNoIGFyZSBh
bHNvIHVzZWQgYnkgdGhlIEJHUCByZWdpc3RyeSBpcyBhc2tpbmcgZm9yDQo+Pj4gdHJvdWJsZToN
Cj4+PiBZb3Ugd291bGRuJ3Qgd2FudCB0aGUgcmVmZXJlbmNlcyBmb3IgdGhlIHR3byByZWdpc3Ry
aWVzIHRvIGdldCBvdXQgb2YNCj4+PiBzeW5jLg0KPj4+IFRoaXMgc2VlbXMgbGlrZSBhIG1lc3Mg
dG8gbWUuIFdvdWxkIGl0IGJlIHBvc3NpYmxlIGZvciBJQU5BIHRvIHNpbXBseQ0KPj4+IHJlbmFt
ZQ0KPj4+IHRoZSAiQkdQIFR1bm5lbCBFbmNhcHN1bGF0aW9uIEF0dHJpYnV0ZSBTdWItVExWcyIg
cmVnaXN0cnkgdG8gIkJHUA0KPj4+IGFuZA0KPj4+IE9TUEYNCj4+PiBUdW5uZWwgRW5jYXBzdWxh
dGlvbiBBdHRyaWJ1dGUgU3ViLVRMVnMiLCBhbmQgc2hhcmUgdGhlIHJlZ2lzdHJ5DQo+Pj4gYmV0
d2Vlbg0KPj4+IHRoZQ0KPj4+IHR3byBwcm90b2NvbHM/IFRoZW4gaGF2ZSB0aGlzIChhbmQgb3Ro
ZXIpIGRvY3VtZW50KHMpIGFkZCB2YWx1ZXMgdG8NCj4+PiB0aGF0DQo+Pj4gcmVnaXN0cnkuIFRo
YXQgd2F5LCB0aGUgZG9jdW1lbnRzIHRoYXQgYWN0dWFsbHkgZGVmaW5lIHRoZSBjb2RlcG9pbnRz
DQo+Pj4gY2FuDQo+Pj4gYmUNCj4+PiBwdXQgaW50byB0aGUgcmVnaXN0cnkuDQo+Pg0KPj4gV2Xi
gJl2ZSBhbHJlYWR5IGhhZCBhIHByb3RyYWN0ZWQgZGlzY3Vzc2lvbiBvbiB0aGUgSUFOQSByZWdp
c3RyaWVzLiBJdA0KPj4gaXMNCj4+IG5vdCBwb3NzaWJsZSBhcyBCR1AgYWR2ZXJ0aXNlcyBzb21l
IG9mIHRoZSBhdHRyaWJ1dGVzIGluIEJHUA0KPj4gY29tbXVuaXRpZXMNCj4+IHJhdGhlciB0aGFu
IHR1bm5lbCBhdHRyaWJ1dGVzIChlLmcuLCBjb2xvcikuDQo+DQo+WXVjay4gSSdsbCB0cnkgbm90
IHRvIHByb2xvbmcgdGhlIGRpc2N1c3Npb24gbXVjaCBmdXJ0aGVyLCBidXQgZGlkIHlvdQ0KPmNv
bnNpZGVyIHRoZSBwb3NzaWJpbGl0eSBvZiBoYXZpbmcgc29tZSBvZiB0aGUgYXR0cmlidXRlcyBh
cHBlYXIgdHdpY2UsDQo+d2l0aCBvbmUgc2F5aW5nICJGb3IgQkdQIGNvbW11bml0aWVzIG9ubHki
IGFuZCB0aGUgb3RoZXIgc2F5aW5nLCAiRm9yDQo+T1NQRiB0dW5uZWxzIG9ubHkiPyBXaGF0IGEg
bG92ZWx5IG1lc3MuIDotKA0KDQpUaGUgY2xlYW5lc3Qgc29sdXRpb24gaXMgZm9yIEJHUCBhbmQg
T1NQRiB0byBoYXZlIHRoZWlyIG93biByZWdpc3RyaWVzLg0KVHJ5aW5nIHRvIHJldHJvZml0IHRo
ZSBleGlzdGluZyBCR1AgcmVnaXN0cnkgdG8gc2F0aXNmeSBPU1BGIGFkdmVydGlzZW1lbnQNCnJl
cXVpcmVtZW50cyBpcyBub3QgZmVhc2libGUuDQoNClRoYW5rcywNCkFjZWUgDQoNCg0KDQo+DQo+
PiBUaGFua3MsDQo+PiBBY2VlDQo+DQo+Q2hlZXJzLA0KPg0KPnByDQo+DQo+Pj4gTWlub3IgaXNz
dWVzOg0KPj4+DQo+Pj4gTm9uZS4NCj4+Pg0KPj4+IE5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOg0K
Pj4+DQo+Pj4gSW4gc2VjdGlvbiA3LjEsIHBsZWFzZSBhZGQ6DQo+Pj4NCj4+PiAgIFtSRkMgRWRp
dG9yOiBQbGVhc2UgcmVwbGFjZSAiVEJEMSIgaW4gc2VjdGlvbiAzIHdpdGggdGhlIHJlZ2lzdHJ5
DQo+Pj4gdmFsdWUNCj4+PiAgIGFsbG9jYXRlZCBieSBJQU5BLCBhbmQgcmVtb3ZlIHRoaXMgbm90
ZV0uDQo+Pj4NCj4+PiBUaGF0IHdpbGwgc2F2ZSB0aGVtIGZyb20gaHVudGluZy4NCj4+Pg0KPg0K
Pg0KPi0tIA0KPlBldGUgUmVzbmljayA8aHR0cDovL3d3dy5xdWFsY29tbS5jb20vfnByZXNuaWNr
Lz4NCj5RdWFsY29tbSBUZWNobm9sb2dpZXMsIEluYy4gLSArMSAoODU4KTY1MS00NDc4DQoNCg==


From nobody Mon Aug 21 23:48:58 2017
Return-Path: <lloyd.wood@yahoo.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B03CF132063 for <ietf@ietfa.amsl.com>; Mon, 21 Aug 2017 23:48:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.21
X-Spam-Level: 
X-Spam-Status: No, score=0.21 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_MUA_MOZILLA=2.309, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.co.uk
Received: 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_LhckPrKieK for <ietf@ietfa.amsl.com>; Mon, 21 Aug 2017 23:48:55 -0700 (PDT)
Received: from sonic307-33.consmr.mail.ir2.yahoo.com (sonic307-33.consmr.mail.ir2.yahoo.com [87.248.110.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBDAC132195 for <ietf@ietf.org>; Mon, 21 Aug 2017 23:48:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048;  t=1503384532; bh=1L6embApcRrMAiaJI/nCHHg4UKcqTAJtE5P28HGPo4Y=;  h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject;  b=E7p92iv1YdeAKy1ZrEIHEVj/9ta/ysykiS8wj/Sp01cLrQqugYryvrZG67srM3atox7Rjfq1Ylk1IhodV/JdS1lGqDCgBzlSwffkhkPRYmvJyHExj8JDkl9m/AYCarMJnyUNXrZd4H7BCxjDS/SnS8oOUUndX4Bua55/2mQ1iLF1wwJU2Ar3k8Rc5ze4nHD4kGpatqvYl0fMQn9k6d5KwtYitijos7AvsCtbhtvWJNpxB9doyweTm7oqGXInU2VY5lj7Q5pQcRpkygPNylshSExtj6oVwuEvGrHaE8KMPSkRM3/bM66bfXrlsJWsL+haCnrNrV7B4qk7hPWuBZwTUw==
X-YMail-OSG: pa2vBRoVRDs3m.Jm5uSdrEVVJ06o31y4PFDFaff0wyAOcHtheYCrQlWa
Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.ir2.yahoo.com with HTTP; Tue, 22 Aug 2017 06:48:52 +0000
Date: Tue, 22 Aug 2017 06:44:51 +0000 (UTC)
From: Lloyd Wood <lloyd.wood@yahoo.co.uk>
Reply-To: Lloyd Wood <lloyd.wood@yahoo.co.uk>
To: Toerless Eckert <tte@cs.fau.de>, John C Klensin <john-ietf@jck.com>
Cc: vaibhav singh <vaibhavsinghacads@gmail.com>,  "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <703648523.3317803.1503384291981@mail.yahoo.com>
In-Reply-To: <20170821170258.GA21915@faui40p.informatik.uni-erlangen.de>
References: <20170821170258.GA21915@faui40p.informatik.uni-erlangen.de>
Subject: Re: Scope for self-destructing email?
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailer: WebService/1.1.10391 YahooMailNeo Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qgsPFGs8kI6t7f5SmL6P03ms4IA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 22 Aug 2017 06:48:57 -0000

I have begun to hope that this email thread will self-destruct.
 
Lloyd Wood lloyd.wood@yahoo.co.uk http://about.me/lloydwood 


From nobody Mon Aug 21 23:51:15 2017
Return-Path: <dhruv.dhody@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34D81132195; Mon, 21 Aug 2017 23:51:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t6pEwiajlHYR; Mon, 21 Aug 2017 23:51:11 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A88AF132063; Mon, 21 Aug 2017 23:51:10 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml702-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DTX18266; Tue, 22 Aug 2017 06:51:08 +0000 (GMT)
Received: from BLREML408-HUB.china.huawei.com (10.20.4.47) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 22 Aug 2017 07:51:06 +0100
Received: from BLREML501-MBX.china.huawei.com ([10.20.5.198]) by BLREML408-HUB.china.huawei.com ([10.20.4.47]) with mapi id 14.03.0301.000; Tue, 22 Aug 2017 12:20:58 +0530
From: Dhruv Dhody <dhruv.dhody@huawei.com>
To: Roni Even <roni.even@huawei.com>, Roni Even <ron.even.tlv@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-pce-rfc6006bis.all@ietf.org" <draft-ietf-pce-rfc6006bis.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [Pce] Genart last call review of draft-ietf-pce-rfc6006bis-03
Thread-Topic: [Pce] Genart last call review of draft-ietf-pce-rfc6006bis-03
Thread-Index: AQHTFDrKXuNsUXmJ/0aASYriy6cC9KKIDkRAgAO04uCABDL68A==
Date: Tue, 22 Aug 2017 06:50:57 +0000
Message-ID: <23CE718903A838468A8B325B80962F9B8CBB55DD@blreml501-mbx>
References: <150263205807.26527.8869013927407425945@ietfa.amsl.com> <23CE718903A838468A8B325B80962F9B8CBB37A0@blreml501-mbx> <6E58094ECC8D8344914996DAD28F1CCD7FED7B@DGGEMM506-MBX.china.huawei.com>
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD7FED7B@DGGEMM506-MBX.china.huawei.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.149.39]
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.599BD45C.0129, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: ed929434a3772e0913d9d5947688f56b
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/j27QV5dTRnt4n_s87BY9uceXB7o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 22 Aug 2017 06:51:14 -0000

Hi Roni,=20

I would like to keep the text, thus I have added more description regarding=
 yang.=20

   The PCEP YANG model "ietf-pcep" is specified in [I-D.ietf-pce-pcep-
   yang]. The P2MP capability of a PCEP entity or a configured peer, can
   be set using this YANG model. Also the support for P2MP path
   computation can be learned using this model. The statistics are
   maintained in the model "ietf-pcep-stats" as specified in [I-D.ietf-
   pce-pcep-yang]. This YANG model will be required to be augmented to
   also include the P2MP related statistics.

Hope this works?=20

Regards,
Dhruv

Working copy: https://github.com/dhruvdhody-huawei/ietf/blob/master/draft-i=
etf-pce-rfc6006bis-04.txt


> -----Original Message-----
> From: Roni Even
> Sent: 19 August 2017 19:51
> To: Dhruv Dhody <dhruv.dhody@huawei.com>; Roni Even
> <ron.even.tlv@gmail.com>; gen-art@ietf.org
> Cc: draft-ietf-pce-rfc6006bis.all@ietf.org; pce@ietf.org; ietf@ietf.org
> Subject: RE: [Pce] Genart last call review of draft-ietf-pce-rfc6006bis-0=
3
>=20
> Hi,
> I did not see the text in RFC6006bis but this current text does not say
> much. If there is some work to reference in PCE  like pce-pcep-yang then
> add it otherwise I suggest to delete this sentence Roni
>=20
> > -----Original Message-----
> > From: Gen-art [mailto:gen-art-bounces@ietf.org] On Behalf Of Dhruv
> > Dhody
> > Sent: =E9=E5=ED=A0=E4 17 =E0=E5=E2=E5=F1=E8 2017 12:06
> > To: Roni Even; gen-art@ietf.org
> > Cc: draft-ietf-pce-rfc6006bis.all@ietf.org; pce@ietf.org;
> > ietf@ietf.org
> > Subject: Re: [Gen-art] [Pce] Genart last call review of
> > draft-ietf-pce-
> > rfc6006bis-03
> >
> > Hi Roni,
> >
> > Thanks for your comments. See inline...
> >
> > > -----Original Message-----
> > > From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Roni Even
> > > Sent: 13 August 2017 19:18
> > > To: gen-art@ietf.org
> > > Cc: draft-ietf-pce-rfc6006bis.all@ietf.org; pce@ietf.org;
> > > ietf@ietf.org
> > > Subject: [Pce] Genart last call review of
> > > draft-ietf-pce-rfc6006bis-03
> > >
> > > Reviewer: Roni Even
> > > Review result: Ready with Nits
> > >
> > > I am the assigned Gen-ART reviewer for this draft. The General Area
> > > Review Team (Gen-ART) reviews all IETF documents being processed by
> > > the IESG for the IETF Chair.  Please treat these comments just like
> > > any other last call comments.
> > >
> > > For more information, please see the FAQ at
> > >
> > > <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> > >
> > > Document: draft-ietf-pce-rfc6006bis-??
> > > Reviewer: Roni Even
> > > Review Date: 2017-08-13
> > > IETF LC End Date: 2017-08-24
> > > IESG Telechat date: 2017-08-31
> > >
> > > Summary: The document is ready for publication as standard track RFC
> > >
> > > I read all the document and also did a compare with RFC6006 to look
> > > at the changes.
> > >
> > > Major issues:
> > >
> > > Minor issues:
> > >
> > > Nits/editorial comments:
> > >
> > > 1. In section 4.2 I am not sure why is this sentence there, is it
> > > for the current yang document or for a future one. Why have it at
> > > all?-"The PCEP YANG module [I-D.ietf-pce-pcep-yang] can be extended
> > > to also include the P2MP related parameters."
> > >
> > [[Dhruv Dhody]] The text around MIB existed from RFC6006. Since then
> > the focus has shifted to Yang.
> > We wanted to keep this text about Yang to reflect that.
> >
> > How about we reword to -
> >
> >    The PCEP YANG model is specified in [I-D.ietf-pce-pcep-yang]. The
> >    YANG models can be augmented to also include the P2MP related
> >    parameters.
> >
> > Thanks again for your review.
> >
> > Regards,
> > Dhruv
> >
> > Working Copy - https://github.com/dhruvdhody-
> > huawei/ietf/blob/master/draft-ietf-pce-rfc6006bis-04.txt
> >
> >
> >
> > >
> > > _______________________________________________
> > > Pce mailing list
> > > Pce@ietf.org
> > > https://www.ietf.org/mailman/listinfo/pce
> >
> > _______________________________________________
> > Gen-art mailing list
> > Gen-art@ietf.org
> > https://www.ietf.org/mailman/listinfo/gen-art


From nobody Tue Aug 22 07:10:30 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DBAE132936 for <ietf@ietfa.amsl.com>; Tue, 22 Aug 2017 07:10:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5aXuEolG55-V for <ietf@ietfa.amsl.com>; Tue, 22 Aug 2017 07:10:25 -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 7FB2413239C for <ietf@ietf.org>; Tue, 22 Aug 2017 07:10:23 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dk9ss-0008fg-8k; Tue, 22 Aug 2017 10:10:22 -0400
Date: Tue, 22 Aug 2017 10:10:15 -0400
From: John C Klensin <john-ietf@jck.com>
To: Toerless Eckert <tte@cs.fau.de>
cc: ietf@ietf.org, vaibhav singh <vaibhavsinghacads@gmail.com>
Subject: Email client APIs. features. amd siupport (was: Re: Scope for self-destructing email?)
Message-ID: <E472D28FF44BD58F88258ACC@PSB>
In-Reply-To: <20170821170258.GA21915@faui40p.informatik.uni-erlangen.de>
References: <20170821170258.GA21915@faui40p.informatik.uni-erlangen.de>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sI8Ug09nqzhZgXbu6FU0DYVcdfA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 22 Aug 2017 14:10:28 -0000

--On Monday, August 21, 2017 19:02 +0200 Toerless Eckert
<tte@cs.fau.de> wrote:

> John,
> 
> I did like to use a couple of those nice email functions driven
> by special headers. IMHO the main reason why those never
> catched on is the absence of easy ways for users to figure out
> how much their software (MTU/MUA) sucks. 
> 
> One thing IMHO that would help are mechanisms to provide users
> with an easy ability to learn what their software is claiming
> to support, and what's missing. User experience should be some
> web-page that explains this to the user in easy terms and
> ideally even suggests to create RFE emails to the vendors. The
> question would then be what standards APIs one would need to
> enable interested third parties to generate such web pages
> (including IETF).
>...

Interesting idea, but a very different discussion (hence the
change of subject lines).   As you know, the IETF has tended to
avoid API specifications, largely because we have preferred
performance standards (i.e., "this is what you need to do and
support") to implementation ones ("this is the API, probably
expressed on code or pseudocode, all you need to do is call
it").  We've also tended to focus on what happens or is
transmitted on the wire between machines rather than how and
what things are dong or implemented before the bits leave a
source system or after they get to a destination one.    In
addition, many people have argued strongly that we should,
insofar as possible, stay out of the UI business, in part
because the IETF, as a community, demonstrably has no skill in
the area.

Personally, I think it is desirable to review those constraints
and assumptions from time to time and to do so explicitly.   It
concerns me a bit when we charter WGs to make major excursions
into the interface between mail delivery servers or IMAP servers
and mail stores without explicitly having that review and
discussion. 

All of that said, I think the MTA situation is fairly good,
especially if one is willing to let MTAs be MTAs rather than
expecting different, or even contradictory, functions (message
recall or destruction among them).   The MUA situation sucks,
but, I think, more because of two reasons the IETF probably
can't solve, certainly not by more standards or APIs.  First,
the providers of free MUAs as part of larger packages or
software or services have little or no incentive to strive for
high quality, especially if quality improvements would make it
easier for users to switch to other packages or mail services.
They have little incentive to carefully conform to standards
either, especially if those standards would interfere with the
lock-in to their packages or other pieces of their systems for
which they have a business model.  Second, in an environment in
which most of the users in the world are using either Webmail
interfaces to mailstores and submission systems that are
proprietary to the same providers or "free" mail clients that
are bundled with office or similar packages, it is hard to think
about where major investment in new, improved, and updated MUAs
is likely to come from, especially when one remembers that these
things need to be maintained to be and stay effective and
useful, not just developed once and put out there.   I note that
development stopped on Mulberry and Eudora years ago and that
Pegasus Mail has never really caught up with current feature
expectations and development has progressed very slowly if at
all.

There are two additional challenges to MUA development today.
HTML-format email is becoming increasingly common, sometimes
with advanced and clever (and arguably dangerous) features.
MUAs that do not use browsers (or APIs to browsers) to read that
mail but, instead, display either plain text only or that use
HTML interpreters that are very restrictive about, e.g.,
automatic processing of external links have large advantages in
terms of reduced risk from attacks but are attractive only to
specialists and others with the knowledge to care or require
significant resources to develop and maintain, especially in the
age of HTML 5.x.   As far as I know, no one has made the effort.
In addition, significant parts of the email community decided a
few years ago that support for email addresses with non-ASCII
characters in both the local and domain parts was important.
The features needed to provide and use those addresses have been
deployed very slowly, partially because of a chicken and egg
problem and, perhaps more important, because the development of
high-quality multilingual (not just multiple script, one or a
few languages other than English, or crudely translated) email
clients is a hard (and expensive, whether measured in time,
money, or both) problem.  Any work done by the IETF that would
make the task of getting those more internationalized capability
deployed more difficult would be, long-term, a serious
disservice to the community.


> Admittedly, i've been annoyed for 25 years that IETF unlike
> ISO is not doing PICS, so maybe this is a more pragmatic
> approach to tackle that gap. And one that would be more user
> friendly, dynamic and maybe even more reliable (depending on
> how much actual probing instead of just declaration you would
> be able to do via the API).

FWIW, there is a point of view that suggests that what made the
PICS [1] approach important was the proliferation of options
that make protocols useful only when profiled.  The IETF, at
least in the best of our work IMO, has tended to focus on
interoperability rather than conformance to lists of features
and on keeping protocols simple enough and free of "settle
arguments but putting everything in" designs to avoid the need.
Some of us think those preferences are high on the list of
reasons why we are not all running X.400 mail today.   YMMD, but
be careful what you wish for.

      john

[1] for those who don't know, a "protocol implementation
conformance statement" that explains exactly what features of a
protocol a particular implementation, or set of implementations,
supports.




From nobody Tue Aug 22 07:47:46 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41B4D1329CB for <ietf@ietfa.amsl.com>; Tue, 22 Aug 2017 07:47:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.232
X-Spam-Level: 
X-Spam-Status: No, score=-1.232 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cMWskPw88heS for <ietf@ietfa.amsl.com>; Tue, 22 Aug 2017 07:47:39 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 4D8181321E6 for <ietf@ietf.org>; Tue, 22 Aug 2017 07:47:39 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v7MElbwb029703 for <ietf@ietf.org>; Tue, 22 Aug 2017 16:47:37 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 7193C202502 for <ietf@ietf.org>; Tue, 22 Aug 2017 16:47:37 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 68336200D24 for <ietf@ietf.org>; Tue, 22 Aug 2017 16:47:37 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v7MElb8e018331 for <ietf@ietf.org>; Tue, 22 Aug 2017 16:47:37 +0200
Subject: Re: "airborne wireless network" - anybody know anything about these folks?
To: ietf@ietf.org
References: <2ab039d2-713a-f6c7-0c85-5dd1e5e2a010@meetinghouse.net> <bc582f7a-9db6-0f38-2d5b-6fcf320dfe20@meetinghouse.net>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <e49f14d5-d17d-ea6a-0e5f-1ab8f6b46d4d@gmail.com>
Date: Tue, 22 Aug 2017 16:47:37 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <bc582f7a-9db6-0f38-2d5b-6fcf320dfe20@meetinghouse.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/l-dlc0e5R7PYxhYoY9A11PoqSuY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 22 Aug 2017 14:47:42 -0000

Le 14/08/2017 à 06:30, Miles Fidelman a écrit :
> Hi Folks,
> 
> Anybody know anything about these folks: 
> http://www.airbornewirelessnetwork.com/index.asp
> 
> I came across an ad from them, in an in-flite magazine - they claim
> to be developing a flying mesh network, with nodes hanging off
> commercial airliners.  (More like an investment pitch than a
> technical ad, backed by a web site that was more sizzle than
> substance.)
> 
> It sure seems like a neat concept, and they seem to have some
> serious airline industry connections - but a bit light on the
> technology side.
> 
> They also make a lot of a patent they have - but it seems to be stuff
>  that we've all seen before in tactical networking and some of the
> Air Force's airborne network initiatives.
> 
> Anyway... anybody know these folks?  Are they for real?

Mesh, and on flight, is a complex and at times unclear concept.

While at the gate, I would invite passengers the thrill to access the 
WiFi of the nearby plane.  Some planes have WiFi on board.

 From there, plane-to-plane communications are easy to establish on cheap
WiFi.  Unpatented IP protocols exist for 1-hop network-to-network
communication establishment.

 From there, same IP tech could be applied to laser and other media.

Alex

> 
> Miles Fidelman
> 
> p.s. Also of possible interest: These folks: 
> https://www.analyticalspace.com - are about to launch a constellation
> of LEO cubesats, also with the intent of doing high bandwidth mesh
> networking, with laser up/downlinks to customers - no need for big
> ground stations.  They seem a lot more substantial - Draper Labs tie
>  in and such.
> 


From nobody Tue Aug 22 08:34:08 2017
Return-Path: <dromasca@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D6421329D9; Tue, 22 Aug 2017 08:34:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dan Romascanu <dromasca@gmail.com>
To: <gen-art@ietf.org>
Cc: ietf@ietf.org, sfc@ietf.org, draft-ietf-sfc-nsh.all@ietf.org, dromasca@gmail.com
Subject: Genart last call review of draft-ietf-sfc-nsh-19
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150341604132.6021.14134855950693780483@ietfa.amsl.com>
Date: Tue, 22 Aug 2017 08:34:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z7BGgLIKpc1RJMQRUQIkxczX5XI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 22 Aug 2017 15:34:01 -0000

Reviewer: Dan Romascanu
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-sfc-nsh-19
Reviewer: Dan Romascanu
Review Date: 2017-08-22
IETF LC End Date: 2017-08-25
IESG Telechat date: 2017-09-14

Summary:

This document describes the header (called Network Service Header - NSH) to be
inserted in packets and frames in order to create packets and frames that
realize service functions described by other SFC documents. It needs to be read
in conjunction with RFC 7665 and other documents as the SFC control plane I-D
in order to make sense of the required functionality. This part of the SFC
solution seems almost ready, but a few issues mentioned below need in my
opinion clarification before the document is approved.

Major issues:

1. Section 11.1 claims: 'An IEEE EtherType, 0x894F, has been allocated for
NSH'. I could not find this value in the tables displayed by the IEEE
Registration Authority (RAC) - for example at
http://standards-oui.ieee.org/ethertype/eth.txt. Neither does IANA at
https://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xhtml (which
would not be in any case the authoritative source). Can you please indicate the
source that this is indeed a confirmed IEEE EtherType registration.

2. Section 5 refers to ietf-rtgwg-dt-encap which is expired. If I understand
correctly the status of this work, there is a design team in place in the
Routing Area created to look at common issues for the different data plane
encapsulations being discussed in various WGs including SFC. This leaves the
issue unsettled at this stage and this may be a problem for a standards track
document. I suggest that first the reference to the expired document is
removed, second that the issue is marked as 'open' and subject for future work.

Minor issues:

1.  Two values 'Experiment 1' and 'Experiment 2' are defined in section 2.2 and
11.2.5 for the Next Protocol. This seems a little odd. Why 2? Why are they
defined at the end of the range? Maybe there is an explanation for those who
know the history but for an un-initiated reader or a future implementer this
seems odd.

2. In Section 2.2 I see:

> All other flag fields, marked U, are unassigned and available for
   future use, see Section 11.2.1.  Unassigned bits MUST be set to zero
   upon origination, and MUST be ignored and preserved unmodified by
   other NSH supporting elements.  Elements which do not understand the
   meaning of any of these bits MUST NOT modify their actions based on
   those unknown bits.

The way the last sentence is written it seems to open the path for elements
that claim to 'understand' the meaning of some Unassigned bit to modify its
behavior based upon it. This does not seem good, as at transmission all
Unassigned bits MUST be set to zero. I would suggest to make the statement
simpler and just say that at reception all elements MUST NOT modify their
actions based on these bits.

3. In Section 2.2 I see:

> 0xF - This value is reserved for experimentation and testing, as per
   [RFC3692].  Implementations not explicitly configured to be part of
   an experiment SHOULD silently discard packets with MD Type 0xF.

Why is this a SHOULD and not a MUST?

4. I believe that  [I-D.ietf-sfc-control-plane] needs to be a Normative
Reference. There are several places in the document (e.g. in Section 2.3) where
this document is referred to describe behavior or actions related to the fields
of the header.

5. The version number has only two bits assigned. Moreover, this document
reserves already two values without any explanation why (only 00 is mandatory
to use, as far as I understand). This needs to be explained (maybe 'historical'
reasons - but unclear for future readers and users) and may be a limitation as
the protocol develops.

Nits/editorial comments:

1. Please make sure that acronyms are expanded at first occurrence (e.g. ECMP)
and if necessary appropriate references are being provided.



From nobody Tue Aug 22 11:42:05 2017
Return-Path: <wes@mti-systems.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 38BF2132A12; Tue, 22 Aug 2017 11:41:57 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Wesley Eddy <wes@mti-systems.com>
To: <tsv-art@ietf.org>
Cc: ietf@ietf.org, sfc@ietf.org, draft-ietf-sfc-nsh.all@ietf.org
Subject: Tsvart last call review of draft-ietf-sfc-nsh-19
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150342731718.6066.9872092086965343963@ietfa.amsl.com>
Date: Tue, 22 Aug 2017 11:41:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/J17nzHaoJvP_pMMnsnW58QUeYFM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 22 Aug 2017 18:41:57 -0000

Reviewer: Wesley Eddy
Review result: Not Ready

In general, the document describes the NSH structure and some loose examples of
how it might be used, but this isn't a very clear protocol specification.  It's
mostly just about NSH format and less on the expected behaviors of NSH
speakers, how to maintain state of the NSH peers or other data structures, etc.
 It seems like there could easily be problems in interoperations between
vendors coding solely based on the document.

Section 5 on fragmentation considerations is nebulous and has technical issues.
 Specifically, it says that PMTUD should be used when NSH is encapsulated in
IP.  PMTUD requires ICMP to work, and has known issues when ICMP is blocked in
the path.  Is there a requirement is SFC networks running NSH that ICMP needs
to be carried by the network?  Further, there is no discussion here on PLPMTUD
versus PMTUD, nor reference to the specific RFCs, algorithms, and options or
configuration parameters suggested to do this properly in SFC systems.

In Section 6, the assumptions, expectations, or hard requirements for mapping
NSH onto an underlying "transport" are not very clear.  Only examples are
given, and some of these (e.g. Ethernet) are not capable of doing things like
detecting fragmentation issues.  Other examples (e.g. GRE) are tunnels where
there may be more state.  There is no discussion about whether there are
assumptions about packet ordering/reordering, duplication, losses, corruption,
etc.

It isn't clear why the particular encapsulations discussed have been chosen
rather than UDP or TCP-based options.

There should probably be more discussion about what types of network paths NSH
is suitable for and that the choice of an encapsulation for NSH needs to be
appropriate to the underlying path between service entities.  Some
encapsulations will need to be tuned for the combination of path and offered
load of traffic.  Some can provide much more feedback to the NSH "layer" than
others that are mainly open-loop.

Propagation of errors through a service function chain or signaling of errors
backwards on a chain seems like it bears further discussion.



From nobody Tue Aug 22 16:39:26 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC918132B7B for <ietf@ietfa.amsl.com>; Tue, 22 Aug 2017 16:39:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n00DHSgjkHnu for <ietf@ietfa.amsl.com>; Tue, 22 Aug 2017 16:39:22 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEEED132B81 for <ietf@ietf.org>; Tue, 22 Aug 2017 16:39:16 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 4CC9458C4AF; Wed, 23 Aug 2017 01:39:12 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 35A99B0C985; Wed, 23 Aug 2017 01:39:12 +0200 (CEST)
Date: Wed, 23 Aug 2017 01:39:12 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: John C Klensin <john-ietf@jck.com>
Cc: ietf@ietf.org, vaibhav singh <vaibhavsinghacads@gmail.com>
Subject: Re: Email client APIs. features. amd siupport (was: Re: Scope for self-destructing email?)
Message-ID: <20170822233911.GA27032@faui40p.informatik.uni-erlangen.de>
References: <20170821170258.GA21915@faui40p.informatik.uni-erlangen.de> <E472D28FF44BD58F88258ACC@PSB>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E472D28FF44BD58F88258ACC@PSB>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1p5oj9sUv3B6LRd3F6CO1Qn84ks>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 22 Aug 2017 23:39:25 -0000

Thanks, John for the elaborations. Fully agree.

Some thoughts:

The principle of the IETF to focus on interfaces that require
interoperability is IMHO good, and it has taken certainly a lot of
time to recognize when and how this requirement applies to
north/south interfaces, "abstract APIs", or however you want to 
call them. 

IMHO, the desire to be able to compose software on single systems
from multiple suppliers should evolve to be an ever more important reason
for the IETF to consider those north/south interfaces. As you said
of course there are conflicting market interests to continue building
"platform monopolies". I just hope that some market segments will easier
see the need for such vendor freedom than eg: the consumer market. 
I continue to be grateful we had the opportunity to deploy  rfc822
ubiquitously before the silicon valleys business model of vertical
monopolies took over.

Wrt to PICS: How about we eliminate all SHOULD/MAY fromIETF 
standards and see whats left ;-). There is also the line of
thought that a separate RFC per optional feature is a much better
way to comply with work metrics in certain companies sponsoring
IETF work ;-) IMHO i agree that options should be minimized, but
we also should find a better way for products to allow declaring
how they do implement standards because options are a fact of life
Even in the best IETF work.

Cheers
    Toerless

P.S.: I just can't let go: Self destructing emails exist for a long
time. They are called mails with programs. And they have shown for
decades now how they can destroy themselves and a lot more. So why
do we need a standard. And how do we get all those malware developers to
come to the IETF ? ;-P

On Tue, Aug 22, 2017 at 10:10:15AM -0400, John C Klensin wrote:
> 
> 
> --On Monday, August 21, 2017 19:02 +0200 Toerless Eckert
> <tte@cs.fau.de> wrote:
> 
> > John,
> > 
> > I did like to use a couple of those nice email functions driven
> > by special headers. IMHO the main reason why those never
> > catched on is the absence of easy ways for users to figure out
> > how much their software (MTU/MUA) sucks. 
> > 
> > One thing IMHO that would help are mechanisms to provide users
> > with an easy ability to learn what their software is claiming
> > to support, and what's missing. User experience should be some
> > web-page that explains this to the user in easy terms and
> > ideally even suggests to create RFE emails to the vendors. The
> > question would then be what standards APIs one would need to
> > enable interested third parties to generate such web pages
> > (including IETF).
> >...
> 
> Interesting idea, but a very different discussion (hence the
> change of subject lines).   As you know, the IETF has tended to
> avoid API specifications, largely because we have preferred
> performance standards (i.e., "this is what you need to do and
> support") to implementation ones ("this is the API, probably
> expressed on code or pseudocode, all you need to do is call
> it").  We've also tended to focus on what happens or is
> transmitted on the wire between machines rather than how and
> what things are dong or implemented before the bits leave a
> source system or after they get to a destination one.    In
> addition, many people have argued strongly that we should,
> insofar as possible, stay out of the UI business, in part
> because the IETF, as a community, demonstrably has no skill in
> the area.
> 
> Personally, I think it is desirable to review those constraints
> and assumptions from time to time and to do so explicitly.   It
> concerns me a bit when we charter WGs to make major excursions
> into the interface between mail delivery servers or IMAP servers
> and mail stores without explicitly having that review and
> discussion. 
> 
> All of that said, I think the MTA situation is fairly good,
> especially if one is willing to let MTAs be MTAs rather than
> expecting different, or even contradictory, functions (message
> recall or destruction among them).   The MUA situation sucks,
> but, I think, more because of two reasons the IETF probably
> can't solve, certainly not by more standards or APIs.  First,
> the providers of free MUAs as part of larger packages or
> software or services have little or no incentive to strive for
> high quality, especially if quality improvements would make it
> easier for users to switch to other packages or mail services.
> They have little incentive to carefully conform to standards
> either, especially if those standards would interfere with the
> lock-in to their packages or other pieces of their systems for
> which they have a business model.  Second, in an environment in
> which most of the users in the world are using either Webmail
> interfaces to mailstores and submission systems that are
> proprietary to the same providers or "free" mail clients that
> are bundled with office or similar packages, it is hard to think
> about where major investment in new, improved, and updated MUAs
> is likely to come from, especially when one remembers that these
> things need to be maintained to be and stay effective and
> useful, not just developed once and put out there.   I note that
> development stopped on Mulberry and Eudora years ago and that
> Pegasus Mail has never really caught up with current feature
> expectations and development has progressed very slowly if at
> all.
> 
> There are two additional challenges to MUA development today.
> HTML-format email is becoming increasingly common, sometimes
> with advanced and clever (and arguably dangerous) features.
> MUAs that do not use browsers (or APIs to browsers) to read that
> mail but, instead, display either plain text only or that use
> HTML interpreters that are very restrictive about, e.g.,
> automatic processing of external links have large advantages in
> terms of reduced risk from attacks but are attractive only to
> specialists and others with the knowledge to care or require
> significant resources to develop and maintain, especially in the
> age of HTML 5.x.   As far as I know, no one has made the effort.
> In addition, significant parts of the email community decided a
> few years ago that support for email addresses with non-ASCII
> characters in both the local and domain parts was important.
> The features needed to provide and use those addresses have been
> deployed very slowly, partially because of a chicken and egg
> problem and, perhaps more important, because the development of
> high-quality multilingual (not just multiple script, one or a
> few languages other than English, or crudely translated) email
> clients is a hard (and expensive, whether measured in time,
> money, or both) problem.  Any work done by the IETF that would
> make the task of getting those more internationalized capability
> deployed more difficult would be, long-term, a serious
> disservice to the community.
> 
> 
> > Admittedly, i've been annoyed for 25 years that IETF unlike
> > ISO is not doing PICS, so maybe this is a more pragmatic
> > approach to tackle that gap. And one that would be more user
> > friendly, dynamic and maybe even more reliable (depending on
> > how much actual probing instead of just declaration you would
> > be able to do via the API).
> 
> FWIW, there is a point of view that suggests that what made the
> PICS [1] approach important was the proliferation of options
> that make protocols useful only when profiled.  The IETF, at
> least in the best of our work IMO, has tended to focus on
> interoperability rather than conformance to lists of features
> and on keeping protocols simple enough and free of "settle
> arguments but putting everything in" designs to avoid the need.
> Some of us think those preferences are high on the list of
> reasons why we are not all running X.400 mail today.   YMMD, but
> be careful what you wish for.
> 
>       john
> 
> [1] for those who don't know, a "protocol implementation
> conformance statement" that explains exactly what features of a
> protocol a particular implementation, or set of implementations,
> supports.
> 
> 

-- 
---
tte@cs.fau.de


From nobody Tue Aug 22 20:27:44 2017
Return-Path: <touch@strayalpha.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25767132376; Tue, 22 Aug 2017 20:27:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.99
X-Spam-Level: 
X-Spam-Status: No, score=-1.99 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MqMWJDnJKJVy; Tue, 22 Aug 2017 20:27:34 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 14AB71328D9; Tue, 22 Aug 2017 20:27:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=a505qSeO/ciUDkKwwEI3RFOrhbVekcBHLK4gMuQsqsU=; b=Ir0JMIE8xyj6nlKe8tUthlp83m Hkmul9UZdF5YeBTGIAjHrRb8eSjayd1jnajseRYBYIFwo0dTSkywFyXkHZi/LWCW0cggzchCkScHp LMZ6g8Q/CGrgKe0jm+QIFgnE8lSJzHXzH+F/pby+WZjvITHud0cxvuk652OuosMXr3pXeWt0dKCCo 6NeGns7OZDV2J4F0mfQmbiwO5dKNp2WozoHuYcJdMmgK+fNfFQVQPeUefHGFZX2CxYS0+jiS5zxQ9 iHT8W3XcGxPtmxpQ2aZPmykAYQA1wSR/lYMkCLWZ6k9KszdtfdCkfwbVYkKEctHb5XVib0G5bNztK PUoX/usg==;
Received: from cpe-172-250-240-132.socal.res.rr.com ([172.250.240.132]:58380 helo=[192.168.1.189]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <touch@strayalpha.com>) id 1dkMKI-003wY3-4k; Tue, 22 Aug 2017 23:27:33 -0400
Subject: Re: Tsvart last call review of draft-ietf-sfc-nsh-19
To: Wesley Eddy <wes@mti-systems.com>, tsv-art@ietf.org
Cc: ietf@ietf.org, sfc@ietf.org, draft-ietf-sfc-nsh.all@ietf.org
References: <150342731718.6066.9872092086965343963@ietfa.amsl.com>
From: Joe Touch <touch@strayalpha.com>
Message-ID: <59162f72-fc2a-8303-e0d4-cf88f92704a1@strayalpha.com>
Date: Tue, 22 Aug 2017 20:27:28 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <150342731718.6066.9872092086965343963@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KSQ6OXGGIB0gN6jZZUqD-RY8N2Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 23 Aug 2017 03:27:36 -0000

FWIW, this doc would benefit from consideration of the terminology
developed for draft-ietf-intarea-tunnels

In particular, the issue of the differences between the MTU of a hop,
path, and edge-to-edge (e.g., the last including receiver reassembly).

Joe


On 8/22/2017 11:41 AM, Wesley Eddy wrote:
> Reviewer: Wesley Eddy
> Review result: Not Ready
>
> In general, the document describes the NSH structure and some loose examples of
> how it might be used, but this isn't a very clear protocol specification.  It's
> mostly just about NSH format and less on the expected behaviors of NSH
> speakers, how to maintain state of the NSH peers or other data structures, etc.
>  It seems like there could easily be problems in interoperations between
> vendors coding solely based on the document.
>
> Section 5 on fragmentation considerations is nebulous and has technical issues.
>  Specifically, it says that PMTUD should be used when NSH is encapsulated in
> IP.  PMTUD requires ICMP to work, and has known issues when ICMP is blocked in
> the path.  Is there a requirement is SFC networks running NSH that ICMP needs
> to be carried by the network?  Further, there is no discussion here on PLPMTUD
> versus PMTUD, nor reference to the specific RFCs, algorithms, and options or
> configuration parameters suggested to do this properly in SFC systems.
>
> In Section 6, the assumptions, expectations, or hard requirements for mapping
> NSH onto an underlying "transport" are not very clear.  Only examples are
> given, and some of these (e.g. Ethernet) are not capable of doing things like
> detecting fragmentation issues.  Other examples (e.g. GRE) are tunnels where
> there may be more state.  There is no discussion about whether there are
> assumptions about packet ordering/reordering, duplication, losses, corruption,
> etc.
>
> It isn't clear why the particular encapsulations discussed have been chosen
> rather than UDP or TCP-based options.
>
> There should probably be more discussion about what types of network paths NSH
> is suitable for and that the choice of an encapsulation for NSH needs to be
> appropriate to the underlying path between service entities.  Some
> encapsulations will need to be tuned for the combination of path and offered
> load of traffic.  Some can provide much more feedback to the NSH "layer" than
> others that are mainly open-loop.
>
> Propagation of errors through a service function chain or signaling of errors
> backwards on a chain seems like it bears further discussion.
>
>


From nobody Tue Aug 22 21:06:52 2017
Return-Path: <sammia.rauf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 660D213214D for <ietf@ietfa.amsl.com>; Tue, 22 Aug 2017 21:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7k0k82NaT-L1 for <ietf@ietfa.amsl.com>; Tue, 22 Aug 2017 21:06:49 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF07B126E64 for <ietf@ietf.org>; Tue, 22 Aug 2017 21:06:48 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id b189so6786053wmd.0 for <ietf@ietf.org>; Tue, 22 Aug 2017 21:06:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to;  bh=tySuU5jkl0KrJPu0n0f/T9LdN/FZUYmkXrjzfRMTwNw=; b=LQflPclnzQlI7NQlbzHlO8d6gbT9D3AAyJ1AWjxh8kXrTvz3OXx5oKgQ1I6S5y784x BtcsLI/PWXa9gLUc8tMkpVEz1kPWROgOpNa7hHzKrqfkLJQQQejSvXI2KcX9fuJnICos nYBQvj3Hkr4JB4ONFEATxmgJyEvOoqJw8dHUno8FvfEkKUjMSlJg3m8TLYHfiMBPpYHN NARfI8pQ4gNkFKOIK/CV/FsiiVoOEn7t+XJ8k+vedi3HYSjUGJs7QBxcy2z1FJCFAUep ljl2/6Qu/vDlzVt8BIpu9GqOocumix5QWJmjSbkFLvkCKWxENH+cAQhFsnC+vSELHO8U yeNg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=tySuU5jkl0KrJPu0n0f/T9LdN/FZUYmkXrjzfRMTwNw=; b=F+OZ9uSZu3EGK4Qrf5Yz86pljcc3Z386jRNd6OWM4diIqMARQ/6XXV4oV++EuJsVIP QeQ+5KOD6TQ+2gXRJj2eL465n2zdn/gKVi/9gbudLBqKEm3ePwilEs6uI4RI8h0loq/6 eFkrFmDq6QA47ndcsTCrm4g0P8FUdp1Ix2kCaPJFFZn9rrMzd0/1WStsyY4a1xGosy7+ 9Wk7tg5dBQjRu5pIRz2f0ijRGO7IqrrsTKbZrjbWzBWqot9Sr10z2xjAd0hvFUCXcAiM nS+NizqoJI9pSVQEJwSBv7/M2t5aDF1Hh0D+mnPRVp4NJz5hL9HJntrAJZJc0bG6j6ZV PPvQ==
X-Gm-Message-State: AHYfb5g2EGkrGPSXL6P6MgQeLyP0gdzNxGUGFRg5NJKsSsY8S29W2oIR ogQCSuJ7zkIhbY1V2dAiWakz9J+OxA==
X-Received: by 10.28.150.142 with SMTP id y136mr1066559wmd.51.1503461207139; Tue, 22 Aug 2017 21:06:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.164.129 with HTTP; Tue, 22 Aug 2017 21:06:46 -0700 (PDT)
In-Reply-To: <150333249451.6815.16917284124201077654@ietfa.amsl.com>
References: <150333249451.6815.16917284124201077654@ietfa.amsl.com>
From: Sammia Rauf <sammia.rauf@gmail.com>
Date: Wed, 23 Aug 2017 09:06:46 +0500
Message-ID: <CAEFdpLP2U=jYULOE0gZfOjm8xw25nkaNH5Jk02q5BOnuGdPSAQ@mail.gmail.com>
Subject: Re: IPv6 over Low Power Wide-Area Networks (lpwan) WG Virtual Meeting: 2017-09-12
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary="001a114b3f6a2f6dcb055763d779"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/i5ky7NFrkKmltx6XaKQULYhXNkE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 23 Aug 2017 04:06:50 -0000

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

hi dear

I'm very new to this venue. I want to attend this virtual meeting. Can you
please help me? I'm from Pakistan. How can i remotely participate in this
virtual meeting? Is there any registration procedure?

Best,


Sammia Rauf

On Mon, Aug 21, 2017 at 9:21 PM, IESG Secretary <iesg-secretary@ietf.org>
wrote:

> The IPv6 over Low Power Wide-Area Networks (lpwan) Working Group will hold
> a virtual interim meeting on 2017-09-12 from 17:00 to 18:00 Europe/Paris.
>
> Agenda:
> The agenda will be announced one week before the meeting.
>
> The general items would be:
> - Advancement of WG items: SCHC-IP/UDP, SCHC-CoAP, LPWAN-overview
> - New items to be discussed: SCHC-ICMP, SCHC-over-FOO, more
>
> Information about remote participation:
> Remote participation information will be obtained at the time of approval
>
>

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

<div dir=3D"ltr">hi dear<br><br><div>I&#39;m very new to this venue. I want=
 to attend this virtual meeting. Can you please help me? I&#39;m from Pakis=
tan. How can i remotely participate in this virtual meeting? Is there any r=
egistration procedure?<br><br>Best,<br><br><br>Sammia Rauf</div></div><div =
class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Aug 21, 2017 a=
t 9:21 PM, IESG Secretary <span dir=3D"ltr">&lt;<a href=3D"mailto:iesg-secr=
etary@ietf.org" target=3D"_blank">iesg-secretary@ietf.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">The IPv6 over Low Power Wide-Area Ne=
tworks (lpwan) Working Group will hold<br>
a virtual interim meeting on 2017-09-12 from 17:00 to 18:00 Europe/Paris.<b=
r>
<br>
Agenda:<br>
The agenda will be announced one week before the meeting.<br>
<br>
The general items would be:<br>
- Advancement of WG items: SCHC-IP/UDP, SCHC-CoAP, LPWAN-overview<br>
- New items to be discussed: SCHC-ICMP, SCHC-over-FOO, more<br>
<br>
Information about remote participation:<br>
Remote participation information will be obtained at the time of approval<b=
r>
<br>
</blockquote></div><br></div>

--001a114b3f6a2f6dcb055763d779--


From nobody Tue Aug 22 21:47:32 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 152A713203D for <ietf@ietfa.amsl.com>; Tue, 22 Aug 2017 21:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R25pIPPUNCM1 for <ietf@ietfa.amsl.com>; Tue, 22 Aug 2017 21:47:28 -0700 (PDT)
Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA39F126E64 for <ietf@ietf.org>; Tue, 22 Aug 2017 21:47:27 -0700 (PDT)
Received: by mail-wm0-x241.google.com with SMTP id r77so1075412wmd.2 for <ietf@ietf.org>; Tue, 22 Aug 2017 21:47:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=I6sr1cJrOW+iRMV4wGJKeXdz4R8YaH/ysqBFBl3U5MA=; b=Z80KeT5GE1QXT3AkSzZY2kM8cRjfRBE91hG+E7oNQfoCrpNeguHgb7slvIxU3KFIMX 9mzYmtHJSopM1Zq0NnQucN1fozjYcYo7JVdqiRIKdYQ2bLKJpT2owMCptVLhwARh8Slg oHilwm5d8THNnm00tI8jfGbifxXyWkhfvYYwtYOU17Lpa+fg6sn8e/HfKvqVeutxHlHw tOQ/TdT9loKFkvkeQvVIoD9v+wuC81xZDjoWQtRNPb+GaTu5VPAtO+9y23uQEn6kJOjj 5crfmlj/qwYUxe3xj5rddzwNw+tzI5vDp3O1n1Xg7Z80WepGS8rvlf3kcnBkaXCW5ehp 09XQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=I6sr1cJrOW+iRMV4wGJKeXdz4R8YaH/ysqBFBl3U5MA=; b=kMm0bPtczRXneNHwjkcKn00k4DcrygL7UCFjCFYolNCAaUun0pi9RbLG/yBaEbqkDT Ps0SJr3Jsrb6Ijz3OliV7+H4UKWph9S+JwvE1L1ygo5+4Y0FAWbNOmMnI3QTIKkcsxOF VaqzFi+ALsDiH5QedbK+HhJFJwRtKEhNMuehvjT9QL73AHH88tYf/fOmHj987rs9Jo0o ZyjryrjplmqORAYGhXk9nbptlcZy9tu6CwppIrdT8CuT7b+nCGdyspXe5Ulv42o4Gf1K EXJwahnVKAQjmC+YPCB0cPhEEyTU+8lh9yc0v9GGPjQoRosqqSoerO4n28o5/uT5ed9/ UTrA==
X-Gm-Message-State: AHYfb5ivFtz9KF9ysN2eEyeCzS+ylLKFIVZG6bvyUeS8pitEgtKycCZe gjtTutyK9zqqzA==
X-Received: by 10.80.151.25 with SMTP id c25mr1980688edb.153.1503463646274; Tue, 22 Aug 2017 21:47:26 -0700 (PDT)
Received: from [192.168.1.18] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id j32sm409561edd.50.2017.08.22.21.47.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 22 Aug 2017 21:47:25 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <6E3A4659-E1BA-42DA-97DB-A031332695BA@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_8B0467C1-EB47-4886-BFA0-9956880CDDAD"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IPv6 over Low Power Wide-Area Networks (lpwan) WG Virtual Meeting: 2017-09-12
Date: Wed, 23 Aug 2017 07:47:22 +0300
In-Reply-To: <CAEFdpLP2U=jYULOE0gZfOjm8xw25nkaNH5Jk02q5BOnuGdPSAQ@mail.gmail.com>
Cc: ietf@ietf.org
To: Sammia Rauf <sammia.rauf@gmail.com>
References: <150333249451.6815.16917284124201077654@ietfa.amsl.com> <CAEFdpLP2U=jYULOE0gZfOjm8xw25nkaNH5Jk02q5BOnuGdPSAQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/s-m_LYRMU8yKmEZTICBBnz8adNc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 23 Aug 2017 04:47:30 -0000

--Apple-Mail=_8B0467C1-EB47-4886-BFA0-9956880CDDAD
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_C100DBA9-9E05-4FA9-9474-5C0D411FFC1D"


--Apple-Mail=_C100DBA9-9E05-4FA9-9474-5C0D411FFC1D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi, Sammia.

First, if you haven=E2=80=99t done so already, join the working group =
mailing list (usually something like lpwan@ietf.org =
<mailto:lpwan@ietf.org>).

On that list they will publish the connection details (usually at IETF =
they use Webex, but other technologies are sometimes used instead, like =
jit.si <http://jit.si/>)

Anyway, they=E2=80=99ll give the details on the list a few days before =
the meeting.

HTH

Yoav

> On 23 Aug 2017, at 7:06, Sammia Rauf <sammia.rauf@gmail.com> wrote:
>=20
> hi dear
>=20
> I'm very new to this venue. I want to attend this virtual meeting. Can =
you please help me? I'm from Pakistan. How can i remotely participate in =
this virtual meeting? Is there any registration procedure?
>=20
> Best,
>=20
>=20
> Sammia Rauf
>=20
> On Mon, Aug 21, 2017 at 9:21 PM, IESG Secretary =
<iesg-secretary@ietf.org <mailto:iesg-secretary@ietf.org>> wrote:
> The IPv6 over Low Power Wide-Area Networks (lpwan) Working Group will =
hold
> a virtual interim meeting on 2017-09-12 from 17:00 to 18:00 =
Europe/Paris.
>=20
> Agenda:
> The agenda will be announced one week before the meeting.
>=20
> The general items would be:
> - Advancement of WG items: SCHC-IP/UDP, SCHC-CoAP, LPWAN-overview
> - New items to be discussed: SCHC-ICMP, SCHC-over-FOO, more
>=20
> Information about remote participation:
> Remote participation information will be obtained at the time of =
approval
>=20
>=20


--Apple-Mail=_C100DBA9-9E05-4FA9-9474-5C0D411FFC1D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi, Sammia.<div class=3D""><br class=3D""></div><div =
class=3D"">First, if you haven=E2=80=99t done so already, join the =
working group mailing list (usually something like <a =
href=3D"mailto:lpwan@ietf.org" class=3D"">lpwan@ietf.org</a>).</div><div =
class=3D""><br class=3D""></div><div class=3D"">On that list they will =
publish the connection details (usually at IETF they use Webex, but =
other technologies are sometimes used instead, like <a =
href=3D"http://jit.si" class=3D"">jit.si</a>)</div><div class=3D""><br =
class=3D""></div><div class=3D"">Anyway, they=E2=80=99ll give the =
details on the list a few days before the meeting.</div><div =
class=3D""><br class=3D""></div><div class=3D"">HTH</div><div =
class=3D""><br class=3D""></div><div class=3D"">Yoav</div><div =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 23 Aug 2017, at 7:06, Sammia Rauf &lt;<a =
href=3D"mailto:sammia.rauf@gmail.com" =
class=3D"">sammia.rauf@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D"">hi dear<br class=3D""><br class=3D""><div class=3D"">I'm very =
new to this venue. I want to attend this virtual meeting. Can you please =
help me? I'm from Pakistan. How can i remotely participate in this =
virtual meeting? Is there any registration procedure?<br class=3D""><br =
class=3D"">Best,<br class=3D""><br class=3D""><br class=3D"">Sammia =
Rauf</div></div><div class=3D"gmail_extra"><br class=3D""><div =
class=3D"gmail_quote">On Mon, Aug 21, 2017 at 9:21 PM, IESG Secretary =
<span dir=3D"ltr" class=3D"">&lt;<a =
href=3D"mailto:iesg-secretary@ietf.org" target=3D"_blank" =
class=3D"">iesg-secretary@ietf.org</a>&gt;</span> wrote:<br =
class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">The IPv6 over Low =
Power Wide-Area Networks (lpwan) Working Group will hold<br class=3D"">
a virtual interim meeting on 2017-09-12 from 17:00 to 18:00 =
Europe/Paris.<br class=3D"">
<br class=3D"">
Agenda:<br class=3D"">
The agenda will be announced one week before the meeting.<br class=3D"">
<br class=3D"">
The general items would be:<br class=3D"">
- Advancement of WG items: SCHC-IP/UDP, SCHC-CoAP, LPWAN-overview<br =
class=3D"">
- New items to be discussed: SCHC-ICMP, SCHC-over-FOO, more<br class=3D"">=

<br class=3D"">
Information about remote participation:<br class=3D"">
Remote participation information will be obtained at the time of =
approval<br class=3D"">
<br class=3D"">
</blockquote></div><br class=3D""></div>
</div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_C100DBA9-9E05-4FA9-9474-5C0D411FFC1D--

--Apple-Mail=_8B0467C1-EB47-4886-BFA0-9956880CDDAD
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQEcBAEBCgAGBQJZnQjbAAoJELhJCxUKWMyZ4IYH/R5NHoyQeFlLsSq9yDIHBW5X
cL2yq8r+U3QGNgmy7VM//BENa4vzy3VKa3E37YzM8HTBHLE0l8CNc/HdMAKA2zd1
PScZHtGLx8XTy+hygcJBZCLQ5QjTBPZsDpZyKDuKa3opk3cEoRKhk/zQAVeLVPrO
M2Sr3l8LJfCfLefT+en+MASTMkiHNWFii5w7rxyn/Q1Q0n30ad8j26FB240qDJvV
lxGQS9j7Xn9BGJ8Xte4JE5biOkdhLPz2Rg+NVR//gR+hf456pf5mCIR2e1Alx7UA
EmE6X6/C6fadHWzHqrHv1grLCjQwzkh3i4lIhJIcfb0RLbEAWI778Pj0mjm7jzo=
=I15S
-----END PGP SIGNATURE-----

--Apple-Mail=_8B0467C1-EB47-4886-BFA0-9956880CDDAD--


From nobody Wed Aug 23 00:51:10 2017
Return-Path: <cloos@jhcloos.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32CBC1321C9 for <ietf@ietfa.amsl.com>; Wed, 23 Aug 2017 00:51: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, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jhcloos.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y3_teVLSBPdW for <ietf@ietfa.amsl.com>; Wed, 23 Aug 2017 00:51:06 -0700 (PDT)
Received: from ore.jhcloos.com (ore.jhcloos.com [IPv6:2604:2880::b24d:a297]) (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 27F38132196 for <ietf@ietf.org>; Wed, 23 Aug 2017 00:51:06 -0700 (PDT)
Received: by ore.jhcloos.com (Postfix, from userid 10) id 74EF71E018; Wed, 23 Aug 2017 07:51:04 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jhcloos.com; s=ore17; t=1503474664; bh=vDS6wxDq5zktNzC3kRpY/Et+7Idr16+bGETbWQq3+XM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=f4mEtqNLEGb4/xgnuw105WiP6qzL9M7aTg7F30B3OqooaHpVFSMKi5drCyBT96ys6 tMkRW4yCY8Wf1XuCtbNCIriv7Z7uXccueaycGAx8PAsOMVMEOj/2RCj9Gj2Y3zyOo+ 5sT1EXqR+8b9QIgxd5rExr2l6/eDSEvlD0pECisy3WAv3VKc/4BazM0pF79t9lvU0t /NPCPG5L7aPsvSfQW6f5+a/O84m3EgSv2+y7BzLv/D9TER9ysYyu8Usi7+i3BKPTgJ SvPdmTnqUL5DhF43tcbYzbl6QpUY/nK6L3Z+NYXYs0r1l9XK/6pHaPyWsTL+OXAQ7B UlIEDqHr0GfbA==
Received: by carbon.jhcloos.org (Postfix, from userid 500) id 30A7B107AC442; Wed, 23 Aug 2017 07:49:42 +0000 (UTC)
From: James Cloos <cloos@jhcloos.com>
To: ietf@ietf.org
Cc: Rich Kulawiec <rsk@gsp.org>
Subject: Re: Next steps in IETF list email archiving
In-Reply-To: <20170731132508.GA22575@gsp.org> (Rich Kulawiec's message of "Mon, 31 Jul 2017 09:25:08 -0400")
References: <fe950cd9-bea8-7831-046d-2f48eaaeafb9@nostrum.com> <20170731132508.GA22575@gsp.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)
Face: iVBORw0KGgoAAAANSUhEUgAAABAAAAAQAgMAAABinRfyAAAACVBMVEX///8ZGXBQKKnCrDQ3 AAAAJElEQVQImWNgQAAXzwQg4SKASgAlXIEEiwsSIYBEcLaAtMEAADJnB+kKcKioAAAAAElFTkSu QmCC
Copyright: Copyright 2017 James Cloos
OpenPGP: 0x997A9F17ED7DAEA6; url=https://jhcloos.com/public_key/0x997A9F17ED7DAEA6.asc
OpenPGP-Fingerprint: E9E9 F828 61A4 6EA9 0F2B  63E7 997A 9F17 ED7D AEA6
Date: Wed, 23 Aug 2017 03:49:42 -0400
Message-ID: <m3efs2wwo9.fsf@carbon.jhcloos.org>
Lines: 14
MIME-Version: 1.0
Content-Type: text/plain
X-Hashcash: 1:28:170823:ietf@ietf.org::BMB7U40ZwvCM9EAO:0006UkIc
X-Hashcash: 1:28:170823:rsk@gsp.org::6WW15OuEAK/4P1th:00000IxYb1
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ppY5WQOpErwAmjVXPKItx-STjho>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 23 Aug 2017 07:51:08 -0000

>>>>> "RK" == Rich Kulawiec <rsk@gsp.org> writes:

RK> One of the best approaches to ensure the long-term preservation of these
RK> archives is to (1) keep them in an open, standard, widely-supported
RK> format -- "mbox" is clearly the best choice and (2) make them trivially
RK> easy to mirror.

rsync://rsync.ietf.org/everything-ftp/ietf-mail-archive/

It is currently 23G.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 0x997A9F17ED7DAEA6


From nobody Wed Aug 23 01:03:22 2017
Return-Path: <a@ackl.io>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE6B81321C9 for <ietf@ietfa.amsl.com>; Wed, 23 Aug 2017 01:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z6tKF_ZhHtAo for <ietf@ietfa.amsl.com>; Wed, 23 Aug 2017 01:03:16 -0700 (PDT)
Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [IPv6:2001:4b98:c:538::194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1CDF132196 for <ietf@ietf.org>; Wed, 23 Aug 2017 01:03:16 -0700 (PDT)
Received: from [IPv6:2001:660:7301:3728:40e1:8c33:d89e:762d] (unknown [IPv6:2001:660:7301:3728:40e1:8c33:d89e:762d]) (Authenticated sender: alex@ackl.io) by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id 91C79C5A70; Wed, 23 Aug 2017 10:03:14 +0200 (CEST)
From: Alexander Pelov <a@ackl.io>
Message-Id: <65E627F5-B929-4967-A015-A5FC65EFB58A@ackl.io>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F2827B87-20D1-4B19-94DA-4E41A880C504"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IPv6 over Low Power Wide-Area Networks (lpwan) WG Virtual Meeting: 2017-09-12
Date: Wed, 23 Aug 2017 10:03:18 +0200
In-Reply-To: <6E3A4659-E1BA-42DA-97DB-A031332695BA@gmail.com>
Cc: Sammia Rauf <sammia.rauf@gmail.com>, ietf@ietf.org
To: Yoav Nir <ynir.ietf@gmail.com>
References: <150333249451.6815.16917284124201077654@ietfa.amsl.com> <CAEFdpLP2U=jYULOE0gZfOjm8xw25nkaNH5Jk02q5BOnuGdPSAQ@mail.gmail.com> <6E3A4659-E1BA-42DA-97DB-A031332695BA@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fvqQxEZ3_T-EBJqQdUHxEY9TCzo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 23 Aug 2017 08:03:21 -0000

--Apple-Mail=_F2827B87-20D1-4B19-94DA-4E41A880C504
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Thanks, Yoav, for the detailed explanation!

Hi Sammia, you are very welcome to this call. We are using Webex for our =
meetings - and the connection details will be announced one week before =
the call. (Personally, I love http://jit.si - we may try it in the =
future calls)

Just a small note - the mailing list is lp-wan@ietf.org . To subscribe =
going to the following link: =
https://www.ietf.org/mailman/listinfo/lp-wan

Some more information on the LPWAN Working Group (WG):
- The relevant documents may be found on the WG page on the Datatracker =
(Datatracker is your friend): =
https://datatracker.ietf.org/wg/lpwan/documents/
- I=E2=80=99d recommend you start with the LPWAN Overview document =
before diving in the IP/UDP SCHC draft.=20

If you have any questions, ideas or remarks, don=E2=80=99t hesitate to =
write to lp-wan@ietf.org.=20

Welcome and nice to see you join, Sammia!
Alexander


> Le 23 ao=C3=BBt 2017 =C3=A0 06:47, Yoav Nir <ynir.ietf@gmail.com> a =
=C3=A9crit :
>=20
> Hi, Sammia.
>=20
> First, if you haven=E2=80=99t done so already, join the working group =
mailing list (usually something like lpwan@ietf.org =
<mailto:lpwan@ietf.org>).
>=20
> On that list they will publish the connection details (usually at IETF =
they use Webex, but other technologies are sometimes used instead, like =
jit.si <http://jit.si/>)
>=20
> Anyway, they=E2=80=99ll give the details on the list a few days before =
the meeting.
>=20
> HTH
>=20
> Yoav
>=20
>> On 23 Aug 2017, at 7:06, Sammia Rauf <sammia.rauf@gmail.com =
<mailto:sammia.rauf@gmail.com>> wrote:
>>=20
>> hi dear
>>=20
>> I'm very new to this venue. I want to attend this virtual meeting. =
Can you please help me? I'm from Pakistan. How can i remotely =
participate in this virtual meeting? Is there any registration =
procedure?
>>=20
>> Best,
>>=20
>>=20
>> Sammia Rauf
>>=20
>> On Mon, Aug 21, 2017 at 9:21 PM, IESG Secretary =
<iesg-secretary@ietf.org <mailto:iesg-secretary@ietf.org>> wrote:
>> The IPv6 over Low Power Wide-Area Networks (lpwan) Working Group will =
hold
>> a virtual interim meeting on 2017-09-12 from 17:00 to 18:00 =
Europe/Paris.
>>=20
>> Agenda:
>> The agenda will be announced one week before the meeting.
>>=20
>> The general items would be:
>> - Advancement of WG items: SCHC-IP/UDP, SCHC-CoAP, LPWAN-overview
>> - New items to be discussed: SCHC-ICMP, SCHC-over-FOO, more
>>=20
>> Information about remote participation:
>> Remote participation information will be obtained at the time of =
approval
>>=20
>>=20
>=20


--Apple-Mail=_F2827B87-20D1-4B19-94DA-4E41A880C504
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D"">Thanks, Yoav, for the detailed =
explanation!</div><div class=3D""><br class=3D""></div><div class=3D"">Hi =
Sammia, you are very welcome to this call. We are using Webex for our =
meetings - and the connection details will be announced one week before =
the call. (Personally, I love <a href=3D"http://jit.si" =
class=3D"">http://jit.si</a> - we may try it in the future =
calls)</div><div class=3D""><br class=3D""></div><div class=3D"">Just a =
small note - the mailing list is <a href=3D"mailto:lp-wan@ietf.org" =
class=3D"">lp-wan@ietf.org</a> . To subscribe going to the following =
link:&nbsp;<a href=3D"https://www.ietf.org/mailman/listinfo/lp-wan" =
class=3D"">https://www.ietf.org/mailman/listinfo/lp-wan</a></div><div =
class=3D""><br class=3D""></div><div class=3D"">Some more information on =
the LPWAN Working Group (WG):</div><div class=3D"">- The relevant =
documents may be found on the WG page on the Datatracker (Datatracker is =
your friend):&nbsp;<a =
href=3D"https://datatracker.ietf.org/wg/lpwan/documents/" =
class=3D"">https://datatracker.ietf.org/wg/lpwan/documents/</a></div><div =
class=3D"">- I=E2=80=99d recommend you start with the&nbsp;LPWAN =
Overview document before diving in the IP/UDP SCHC =
draft.&nbsp;</div><div class=3D""><br class=3D""></div><div class=3D"">If =
you have any questions, ideas or remarks, don=E2=80=99t hesitate to =
write to <a href=3D"mailto:lp-wan@ietf.org" =
class=3D"">lp-wan@ietf.org</a>.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Welcome and nice to see you join, =
Sammia!</div><div class=3D"">Alexander</div><div class=3D""><br =
class=3D""></div><br class=3D""><div><blockquote type=3D"cite" =
class=3D""><div class=3D"">Le 23 ao=C3=BBt 2017 =C3=A0 06:47, Yoav Nir =
&lt;<a href=3D"mailto:ynir.ietf@gmail.com" =
class=3D"">ynir.ietf@gmail.com</a>&gt; a =C3=A9crit :</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
http-equiv=3D"Content-Type" content=3D"text/html charset=3Dutf-8" =
class=3D""><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;" class=3D"">Hi, =
Sammia.<div class=3D""><br class=3D""></div><div class=3D"">First, if =
you haven=E2=80=99t done so already, join the working group mailing list =
(usually something like <a href=3D"mailto:lpwan@ietf.org" =
class=3D"">lpwan@ietf.org</a>).</div><div class=3D""><br =
class=3D""></div><div class=3D"">On that list they will publish the =
connection details (usually at IETF they use Webex, but other =
technologies are sometimes used instead, like <a href=3D"http://jit.si/" =
class=3D"">jit.si</a>)</div><div class=3D""><br class=3D""></div><div =
class=3D"">Anyway, they=E2=80=99ll give the details on the list a few =
days before the meeting.</div><div class=3D""><br class=3D""></div><div =
class=3D"">HTH</div><div class=3D""><br class=3D""></div><div =
class=3D"">Yoav</div><div class=3D""><br class=3D""><div =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On 23 =
Aug 2017, at 7:06, Sammia Rauf &lt;<a =
href=3D"mailto:sammia.rauf@gmail.com" =
class=3D"">sammia.rauf@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D"">hi dear<br class=3D""><br class=3D""><div class=3D"">I'm very =
new to this venue. I want to attend this virtual meeting. Can you please =
help me? I'm from Pakistan. How can i remotely participate in this =
virtual meeting? Is there any registration procedure?<br class=3D""><br =
class=3D"">Best,<br class=3D""><br class=3D""><br class=3D"">Sammia =
Rauf</div></div><div class=3D"gmail_extra"><br class=3D""><div =
class=3D"gmail_quote">On Mon, Aug 21, 2017 at 9:21 PM, IESG Secretary =
<span dir=3D"ltr" class=3D"">&lt;<a =
href=3D"mailto:iesg-secretary@ietf.org" target=3D"_blank" =
class=3D"">iesg-secretary@ietf.org</a>&gt;</span> wrote:<br =
class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">The IPv6 over Low =
Power Wide-Area Networks (lpwan) Working Group will hold<br class=3D"">
a virtual interim meeting on 2017-09-12 from 17:00 to 18:00 =
Europe/Paris.<br class=3D"">
<br class=3D"">
Agenda:<br class=3D"">
The agenda will be announced one week before the meeting.<br class=3D"">
<br class=3D"">
The general items would be:<br class=3D"">
- Advancement of WG items: SCHC-IP/UDP, SCHC-CoAP, LPWAN-overview<br =
class=3D"">
- New items to be discussed: SCHC-ICMP, SCHC-over-FOO, more<br class=3D"">=

<br class=3D"">
Information about remote participation:<br class=3D"">
Remote participation information will be obtained at the time of =
approval<br class=3D"">
<br class=3D"">
</blockquote></div><br class=3D""></div>
</div></blockquote></div><br =
class=3D""></div></div></div></blockquote></div><br =
class=3D""></body></html>=

--Apple-Mail=_F2827B87-20D1-4B19-94DA-4E41A880C504--


From nobody Wed Aug 23 07:05:25 2017
Return-Path: <ietf@lmcontreras.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88211132C21 for <ietf@ietfa.amsl.com>; Wed, 23 Aug 2017 07:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level: 
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sZHsgOFwDVgl for <ietf@ietfa.amsl.com>; Wed, 23 Aug 2017 07:05:21 -0700 (PDT)
Received: from 2.mo173.mail-out.ovh.net (2.mo173.mail-out.ovh.net [178.33.251.49]) (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 B8E34132C26 for <ietf@ietf.org>; Wed, 23 Aug 2017 07:05:20 -0700 (PDT)
Received: from player778.ha.ovh.net (b6.ovh.net [213.186.33.56]) by mo173.mail-out.ovh.net (Postfix) with ESMTP id 2C6EF6A576 for <ietf@ietf.org>; Wed, 23 Aug 2017 16:05:17 +0200 (CEST)
Received: from RCM-ns3033854.ip-51-255-71.eu (publico1.tid.es [195.235.92.36]) (Authenticated sender: ietf@lmcontreras.com) by player778.ha.ovh.net (Postfix) with ESMTPSA id ADF581800C8; Wed, 23 Aug 2017 16:05:13 +0200 (CEST)
Received: from publico1.tid.es ([195.235.92.36]) by mail.ovh.net with HTTP (HTTP/1.1 POST); Wed, 23 Aug 2017 16:05:13 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Date: Wed, 23 Aug 2017 16:05:13 +0200
From: ietf@lmcontreras.com
To: ietf@ietf.org
Cc: mboned@ietf.org, draft-ietf-mboned-interdomain-peering-bcp@ietf.org, mboned-chairs@ietf.org, luismiguel.contrerasmurillo@telefonica.com
Subject: Re: [MBONED] Last Call: <draft-ietf-mboned-interdomain-peering-bcp-10.txt> (Use of Multicast Across Inter-Domain Peering Points) to Best Current Practice
In-Reply-To: <150230622113.3494.9085716932582954594.idtracker@ietfa.amsl.com>
References: <150230622113.3494.9085716932582954594.idtracker@ietfa.amsl.com>
Message-ID: <9160f7fd4aef47c66383019dcc820e3d@lmcontreras.com>
X-Sender: ietf@lmcontreras.com
User-Agent: Roundcube Webmail/1.3.0 
X-Originating-IP: 195.235.92.36
X-Webmail-UserID: ietf@lmcontreras.com
X-Ovh-Tracer-Id: 10060197144081219462
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: 0
X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeelledrtddvgdejgecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemuceftddtnecu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Lzw-bNZc1LH0G0KG1FK_w4nQ-SU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 23 Aug 2017 14:05:23 -0000

Dear all,

I have a specific comment regarding to this document. It states (third 
bullet in page 5) that the multicast traffic to be inter-exchanged via 
the peering point is the one generated locally, in this case by AD-1 ("a 
service provider controls one or more application sources in AD-1 ..."). 
So it does not consider the situation where one carrier may act as 
(multicast) transit provider. In other words, a scenario where AD-3 
could obtain via AD-2 the multicast traffic generated by AD-1.

Maybe I’m wrong, but in my understanding the scenarios and methods 
described in the draft could permit such transit scenario, but no 
statement is done to clarify if it is feasible or not. It can be 
interesting to clarify this point in the final version of the document.

Thanks

Luis M. Contreras



El 2017-08-09 21:17, The IESG escribió:
> The IESG has received a request from the MBONE Deployment WG (mboned) 
> to
> consider the following document: - 'Use of Multicast Across 
> Inter-Domain
> Peering Points'
>   <draft-ietf-mboned-interdomain-peering-bcp-10.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 2017-08-23. 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 examines the use of Source Specific Multicast (SSM)
>    across inter-domain peering points for a specified set of deployment
>    scenarios. The objective is to describe the setup process for
>    multicast-based delivery across administrative domains for these
>    scenarios and document supporting functionality to enable this
>    process.
> 
> 
> 
> 
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> The document contains these normative downward references.
> See RFC 3967 for additional information:
>     rfc2784: Generic Routing Encapsulation (GRE) (Proposed Standard -
> Legacy stream)
>     rfc3810: Multicast Listener Discovery Version 2 (MLDv2) for IPv6
> (Proposed Standard - IETF stream)
>     rfc7450: Automatic Multicast Tunneling (Proposed Standard - IETF 
> stream)
>     rfc4609: Protocol Independent Multicast - Sparse Mode (PIM-SM)
> Multicast Routing Security Issues and Enhancements (Informational -
> IETF stream)
>     rfc4271: A Border Gateway Protocol 4 (BGP-4) (Draft Standard - IETF 
> stream)
>     rfc4604: Using Internet Group Management Protocol Version 3
> (IGMPv3) and Multicast Listener Discovery Protocol Version 2 (MLDv2)
> for Source-Specific Multicast (Proposed Standard - IETF stream)
>     rfc3376: Internet Group Management Protocol, Version 3 (Proposed
> Standard - IETF stream)
> 
> 
> 
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

-- 
___________________________________________

Luis M. Contreras
ietf@lmcontreras.com
luismiguel.contrerasmurillo@telefonica.com


From nobody Wed Aug 23 09:37:47 2017
Return-Path: <barryleiba@computer.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7781B132025; Wed, 23 Aug 2017 09:37:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Barry Leiba <barryleiba@computer.org>
To: <secdir@ietf.org>
Cc: mboned@ietf.org, draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org, ietf@ietf.org
Subject: Secdir last call review of draft-ietf-mboned-interdomain-peering-bcp-10
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150350625436.19506.508612463163381728@ietfa.amsl.com>
Date: Wed, 23 Aug 2017 09:37:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/j0l1MOCUI_TiXtNMkGEEU7I55WA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 23 Aug 2017 16:37:35 -0000

Reviewer: Barry Leiba
Review result: Ready

This document seems ready, and seems to cover security concerns adequately.  Carry on...


From nobody Wed Aug 23 12:41:25 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35090132026 for <ietf@ietfa.amsl.com>; Wed, 23 Aug 2017 12:41: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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T_CQMbKEzoad for <ietf@ietfa.amsl.com>; Wed, 23 Aug 2017 12:41:21 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1922132192 for <ietf@ietf.org>; Wed, 23 Aug 2017 12:41:21 -0700 (PDT)
Received: (qmail 80236 invoked from network); 23 Aug 2017 19:41:20 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 23 Aug 2017 19:41:20 -0000
Date: 23 Aug 2017 19:40:58 -0000
Message-ID: <20170823194058.18709.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Cc: rsk@gsp.org
Subject: Re: Next steps in IETF list email archiving
In-Reply-To: <20170731132508.GA22575@gsp.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XLhXKSzplQoDgTZNwN47ltRM6cQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 23 Aug 2017 19:41:23 -0000

In article <20170731132508.GA22575@gsp.org> you write:
>One of the best approaches to ensure the long-term preservation of these
>archives is to (1) keep them in an open, standard, widely-supported
>format -- "mbox" is clearly the best choice

Er, not really.  See RFC 4155.  There are way too many not quite
compatible versions of mbox.  If I wanted a file format for a
multi-file archive, I'd probably use POSIX ustar which is an actual
standard.

On the other hand, I see that there are rsync-able archives in some
mbox variant, so that horse left the barn ages ago.  The archives are
kind of funky, e.g., the file dnsop/2001-01.mail contains messages
from March 1999 through January 2001, and there are empty files
1999-06.mail through 2000-12.mail.

R's,
John



From nobody Wed Aug 23 14:51:19 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E479132A04 for <ietf@ietfa.amsl.com>; Wed, 23 Aug 2017 14:51:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M5Pu0SKt6oij for <ietf@ietfa.amsl.com>; Wed, 23 Aug 2017 14:51:16 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D617E132A1D for <ietf@ietf.org>; Wed, 23 Aug 2017 14:51:15 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id C96CD58C4AF; Wed, 23 Aug 2017 23:51:11 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id B4072B0C99B; Wed, 23 Aug 2017 23:51:11 +0200 (CEST)
Date: Wed, 23 Aug 2017 23:51:11 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: John Levine <johnl@taugh.com>
Cc: ietf@ietf.org, rsk@gsp.org
Subject: Re: Next steps in IETF list email archiving
Message-ID: <20170823215111.GA28827@faui40p.informatik.uni-erlangen.de>
References: <20170731132508.GA22575@gsp.org> <20170823194058.18709.qmail@ary.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170823194058.18709.qmail@ary.lan>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/V6pWc39gXjgTFRNl8P40BfYJ1K4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 23 Aug 2017 21:51:18 -0000

On Wed, Aug 23, 2017 at 07:40:58PM -0000, John Levine wrote:
> In article <20170731132508.GA22575@gsp.org> you write:
> >One of the best approaches to ensure the long-term preservation of these
> >archives is to (1) keep them in an open, standard, widely-supported
> >format -- "mbox" is clearly the best choice
> 
> Er, not really.  See RFC 4155.  There are way too many not quite
> compatible versions of mbox.  If I wanted a file format for a
> multi-file archive, I'd probably use POSIX ustar which is an actual
> standard.

Sure, but that would not be a complete spec because it does not cover
the format of individual messages nor any semantics of file names.

Whats the least restrictive sufficiently well specified generic mail encoding ?
Anything that would also pass via rfc822+mime ?

Might also be nice to have some well-known-filename with metadata
about the archive content, eg: self-URL, previous, next URL, contact
URL (if any), archive owner signed checksums of files. Template
spec of filenames (%YYYY-%MM.mail),...

> On the other hand, I see that there are rsync-able archives in some
> mbox variant, so that horse left the barn ages ago.  The archives are
> kind of funky, e.g., the file dnsop/2001-01.mail contains messages
> from March 1999 through January 2001, and there are empty files
> 1999-06.mail through 2000-12.mail.

See above: metadata that would help you figure out if you have a
complete set of archive files.

Cheers
    Toerless

> R's,
> John
> 

-- 
---
tte@cs.fau.de


From nobody Wed Aug 23 18:21:50 2017
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 377C513219F; Wed, 23 Aug 2017 18:21:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sALpQ3p_4CY9; Wed, 23 Aug 2017 18:21:47 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D35C5126B7E; Wed, 23 Aug 2017 18:21:45 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml708-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DNF27927; Thu, 24 Aug 2017 01:21:44 +0000 (GMT)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 24 Aug 2017 02:21:43 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0235.001; Thu, 24 Aug 2017 09:21:38 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, Pete Resnick <presnick@qti.qualcomm.com>
CC: "gen-art@ietf.org" <gen-art@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, "draft-ietf-ospf-encapsulation-cap.all@ietf.org" <draft-ietf-ospf-encapsulation-cap.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: =?utf-8?B?562U5aSNOiBHZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRm?= =?utf-8?Q?-ospf-encapsulation-cap-06?=
Thread-Topic: Genart last call review of draft-ietf-ospf-encapsulation-cap-06
Thread-Index: AQHTGpPg65n9FtvJ8ESocUdJe7ZtvKKOcUOAgAAEKQCAACpdAIAEGYBg
Date: Thu, 24 Aug 2017 01:21:33 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BC0A506@NKGEML515-MBX.china.huawei.com>
References: <150333004648.6756.16820249680656378919@ietfa.amsl.com> <D5C07A8A.C26DE%acee@cisco.com> <5B41B581-74F4-4F57-B811-F535044350F4@qti.qualcomm.com> <D5C0A175.C277A%acee@cisco.com>
In-Reply-To: <D5C0A175.C277A%acee@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.184.181]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090204.599E2A28.0052, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 4d317ccca1bc7328d02f9f9594f03125
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6YFAnpRCKXmV_l435xtx5uH5uek>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Aug 2017 01:21:49 -0000

DQoNCj4gLS0tLS3pgq7ku7bljp/ku7YtLS0tLQ0KPiDlj5Hku7bkuro6IEFjZWUgTGluZGVtIChh
Y2VlKSBbbWFpbHRvOmFjZWVAY2lzY28uY29tXQ0KPiDlj5HpgIHml7bpl7Q6IDIwMTflubQ45pyI
MjLml6UgMjo0NQ0KPiDmlLbku7bkuro6IFBldGUgUmVzbmljaw0KPiDmioTpgIE6IGdlbi1hcnRA
aWV0Zi5vcmc7IG9zcGZAaWV0Zi5vcmc7DQo+IGRyYWZ0LWlldGYtb3NwZi1lbmNhcHN1bGF0aW9u
LWNhcC5hbGxAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcNCj4g5Li76aKYOiBSZTogR2VuYXJ0IGxh
c3QgY2FsbCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1vc3BmLWVuY2Fwc3VsYXRpb24tY2FwLTA2DQo+
IA0KPiANCj4gDQo+IE9uIDgvMjEvMTcsIDEyOjEyIFBNLCAiUGV0ZSBSZXNuaWNrIiA8cHJlc25p
Y2tAcXRpLnF1YWxjb21tLmNvbT4gd3JvdGU6DQo+IA0KPiA+T24gMjEgQXVnIDIwMTcsIGF0IDEw
OjU4LCBBY2VlIExpbmRlbSAoYWNlZSkgd3JvdGU6DQo+ID4NCj4gPj4gSGkgUGV0ZSwNCj4gPj4N
Cj4gPj4gT24gOC8yMS8xNywgMTE6NDAgQU0sICJQZXRlIFJlc25pY2siIDxwcmVzbmlja0BxdGku
cXVhbGNvbW0uY29tPg0KPiA+PiB3cm90ZToNCj4gPj4NCj4gPj4+IFJldmlld2VyOiBQZXRlIFJl
c25pY2sNCj4gPj4+IFJldmlldyByZXN1bHQ6IEFsbW9zdCBSZWFkeQ0KPiA+Pj4NCj4gPj4+IEkg
YW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5l
cmFsIEFyZWENCj4gPj4+IFJldmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRv
Y3VtZW50cyBiZWluZyBwcm9jZXNzZWQgYnkNCj4gPj4+IHRoZSBJRVNHIGZvciB0aGUgSUVURiBD
aGFpci4gIFBsZWFzZSB0cmVhdCB0aGVzZSBjb21tZW50cyBqdXN0IGxpa2UNCj4gPj4+IGFueSBv
dGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQo+ID4+Pg0KPiA+Pj4gRm9yIG1vcmUgaW5mb3JtYXRp
b24sIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPiA+Pj4NCj4gPj4+IDxodHRwczovL3RyYWMuaWV0
Zi5vcmcvdHJhYy9nZW4vd2lraS9HZW5BcnRmYXE+Lg0KPiA+Pj4NCj4gPj4+IERvY3VtZW50OiBk
cmFmdC1pZXRmLW9zcGYtZW5jYXBzdWxhdGlvbi1jYXAtMDYNCj4gPj4+IFJldmlld2VyOiBQZXRl
IFJlc25pY2sNCj4gPj4+IFJldmlldyBEYXRlOiAyMDE3LTA4LTIxDQo+ID4+PiBJRVRGIExDIEVu
ZCBEYXRlOiAyMDE3LTA4LTI4DQo+ID4+PiBJRVNHIFRlbGVjaGF0IGRhdGU6IDIwMTctMDgtMzEN
Cj4gPj4+DQo+ID4+PiBTdW1tYXJ5OiBBbG1vc3QgUmVhZHkNCj4gPj4+DQo+ID4+PiBUaGUgY29u
dGVudCBvZiB0aGlzIGRvY3VtZW50IGlzIGZpbmUuIEhvd2V2ZXIsIEkgdGhpbmsgdGhlIElBTkEN
Cj4gPj4+IHJlZ2lzdHJ5IHN0dWZmIGlzIG5vdCByZWFkeS4NCj4gPj4+DQo+ID4+PiBNYWpvciBp
c3N1ZXM6DQo+ID4+Pg0KPiA+Pj4gSSB0aGluayB0aGUgcmVnaXN0cmF0aW9ucyBvdGhlciB0aGFu
IGZvciBFbmRwb2ludCBhbmQgQ29sb3IgYXJlDQo+ID4+PiBpbmNvcnJlY3QgYW5kIHNob3VsZCBu
b3QgYmUgaW4gdGhpcyBkb2N1bWVudC4gQ2VydGFpbmx5IHRoZQ0KPiA+Pj4gIlJlZmVyZW5jZSIg
ZmllbGQgZm9yIDEsIDIsIDUsIDYsIGFuZCA3IHNob3VsZCBub3QgYmUgIlRoaXMNCj4gPj4+IGRv
Y3VtZW50IiwgZ2l2ZW4gdGhhdCB0aGUgc3ludGF4IGFuZCBzZW1hbnRpY3MgZm9yIHRoZXNlIHZh
bHVlcyBhcmUNCj4gPj4+IGRlZmluZWQgaW4gb3RoZXIgZG9jdW1lbnRzLg0KPiA+Pg0KPiA+PiBU
aGUgYXV0aG9ycyBjYW4gZml4IHRoZXNlLg0KPiA+DQo+ID5Gb3IgMSwgMiwgNiwgYW5kIDcsIHRo
YXQncyBlYXN5OyB0aGUgZHJhZnRzIGRlZmluaW5nIHRoZSB2YWx1ZXMgY2FuIGRvDQo+ID50aGUg
cmVnaXN0cmF0aW9ucy4gRm9yIDUsIHRoZSByZWZlcmVuY2Ugd291bGQgYmUgdG8gYW4gZXhpc3Rp
bmcgUkZDDQo+ID50aGF0IGRvZXNuJ3QgZG8gdGhlIHJlZ2lzdHJhdGlvbi4gSSdtIG5vdCBzdXJl
IHdoYXQgdG8gZG8gYWJvdXQgdGhhdDsNCj4gPnBlcmhhcHMgcmVnaXN0ZXIgaXQgaGVyZSBhbmQg
bWFrZSB0aGUgcmVmZXJlbmNlIGJvdGggNTY0MCBhbmQgdGhpcyBkb2N1bWVudC4NCj4gPkhvd2V2
ZXIsIHdoZW4gc29tZW9uZSBnb2VzIHRvIHVwZGF0ZSA1NjQwIHNvbWUgZGF5LCB0aGV5J3JlIGdv
aW5nIHRvDQo+ID5oYXZlIHRvIHB1dCBpbnRvIHRoZSBJQU5BIGNvbnNpZGVyYXRpb25zIHRvIHVw
ZGF0ZSBib3RoIHRoZSBPU1BGIGFuZA0KPiA+QkdQIHJlZ2lzdHJpZXMuIEknbSBub3Qgc3VyZSBo
b3cgdG8ga2VlcCB0cmFjayBvZiB0aGF0LiBQZXJoYXBzIHNheWluZw0KPiA+dGhhdCB0aGlzIGRv
Y3VtZW50ICJVcGRhdGVzOiA1NjQwIj8gVGhhdCBkb2Vzbid0IHNlZW0gZ3JlYXQgZWl0aGVyLg0K
PiA+DQo+ID4+PiBJIGFsc28gdGhpbmsgdGhhdCBoYXZpbmcgdGhpbmdzIGluDQo+ID4+PiB0aGlz
IHJlZ2lzdHJ5IHdoaWNoIGFyZSBhbHNvIHVzZWQgYnkgdGhlIEJHUCByZWdpc3RyeSBpcyBhc2tp
bmcgZm9yDQo+ID4+PiB0cm91YmxlOg0KPiA+Pj4gWW91IHdvdWxkbid0IHdhbnQgdGhlIHJlZmVy
ZW5jZXMgZm9yIHRoZSB0d28gcmVnaXN0cmllcyB0byBnZXQgb3V0DQo+ID4+PiBvZiBzeW5jLg0K
PiA+Pj4gVGhpcyBzZWVtcyBsaWtlIGEgbWVzcyB0byBtZS4gV291bGQgaXQgYmUgcG9zc2libGUg
Zm9yIElBTkEgdG8NCj4gPj4+IHNpbXBseSByZW5hbWUgdGhlICJCR1AgVHVubmVsIEVuY2Fwc3Vs
YXRpb24gQXR0cmlidXRlIFN1Yi1UTFZzIg0KPiA+Pj4gcmVnaXN0cnkgdG8gIkJHUCBhbmQgT1NQ
RiBUdW5uZWwgRW5jYXBzdWxhdGlvbiBBdHRyaWJ1dGUgU3ViLVRMVnMiLA0KPiA+Pj4gYW5kIHNo
YXJlIHRoZSByZWdpc3RyeSBiZXR3ZWVuIHRoZSB0d28gcHJvdG9jb2xzPyBUaGVuIGhhdmUgdGhp
cw0KPiA+Pj4gKGFuZCBvdGhlcikgZG9jdW1lbnQocykgYWRkIHZhbHVlcyB0byB0aGF0IHJlZ2lz
dHJ5LiBUaGF0IHdheSwgdGhlDQo+ID4+PiBkb2N1bWVudHMgdGhhdCBhY3R1YWxseSBkZWZpbmUg
dGhlIGNvZGVwb2ludHMgY2FuIGJlIHB1dCBpbnRvIHRoZQ0KPiA+Pj4gcmVnaXN0cnkuDQo+ID4+
DQo+ID4+IFdl4oCZdmUgYWxyZWFkeSBoYWQgYSBwcm90cmFjdGVkIGRpc2N1c3Npb24gb24gdGhl
IElBTkEgcmVnaXN0cmllcy4gSXQNCj4gPj4gaXMgbm90IHBvc3NpYmxlIGFzIEJHUCBhZHZlcnRp
c2VzIHNvbWUgb2YgdGhlIGF0dHJpYnV0ZXMgaW4gQkdQDQo+ID4+IGNvbW11bml0aWVzIHJhdGhl
ciB0aGFuIHR1bm5lbCBhdHRyaWJ1dGVzIChlLmcuLCBjb2xvcikuDQo+ID4NCj4gPll1Y2suIEkn
bGwgdHJ5IG5vdCB0byBwcm9sb25nIHRoZSBkaXNjdXNzaW9uIG11Y2ggZnVydGhlciwgYnV0IGRp
ZCB5b3UNCj4gPmNvbnNpZGVyIHRoZSBwb3NzaWJpbGl0eSBvZiBoYXZpbmcgc29tZSBvZiB0aGUg
YXR0cmlidXRlcyBhcHBlYXIgdHdpY2UsDQo+ID53aXRoIG9uZSBzYXlpbmcgIkZvciBCR1AgY29t
bXVuaXRpZXMgb25seSIgYW5kIHRoZSBvdGhlciBzYXlpbmcsICJGb3INCj4gPk9TUEYgdHVubmVs
cyBvbmx5Ij8gV2hhdCBhIGxvdmVseSBtZXNzLiA6LSgNCj4gDQo+IFRoZSBjbGVhbmVzdCBzb2x1
dGlvbiBpcyBmb3IgQkdQIGFuZCBPU1BGIHRvIGhhdmUgdGhlaXIgb3duIHJlZ2lzdHJpZXMuDQo+
IFRyeWluZyB0byByZXRyb2ZpdCB0aGUgZXhpc3RpbmcgQkdQIHJlZ2lzdHJ5IHRvIHNhdGlzZnkg
T1NQRiBhZHZlcnRpc2VtZW50DQo+IHJlcXVpcmVtZW50cyBpcyBub3QgZmVhc2libGUuDQoNCkZ1
bGx5IGFncmVlLg0KDQpCZXN0IHJlZ2FyZHMsDQpYaWFvaHUNCg0KPiBUaGFua3MsDQo+IEFjZWUN
Cj4gDQo+IA0KPiANCj4gPg0KPiA+PiBUaGFua3MsDQo+ID4+IEFjZWUNCj4gPg0KPiA+Q2hlZXJz
LA0KPiA+DQo+ID5wcg0KPiA+DQo+ID4+PiBNaW5vciBpc3N1ZXM6DQo+ID4+Pg0KPiA+Pj4gTm9u
ZS4NCj4gPj4+DQo+ID4+PiBOaXRzL2VkaXRvcmlhbCBjb21tZW50czoNCj4gPj4+DQo+ID4+PiBJ
biBzZWN0aW9uIDcuMSwgcGxlYXNlIGFkZDoNCj4gPj4+DQo+ID4+PiAgIFtSRkMgRWRpdG9yOiBQ
bGVhc2UgcmVwbGFjZSAiVEJEMSIgaW4gc2VjdGlvbiAzIHdpdGggdGhlIHJlZ2lzdHJ5DQo+ID4+
PiB2YWx1ZQ0KPiA+Pj4gICBhbGxvY2F0ZWQgYnkgSUFOQSwgYW5kIHJlbW92ZSB0aGlzIG5vdGVd
Lg0KPiA+Pj4NCj4gPj4+IFRoYXQgd2lsbCBzYXZlIHRoZW0gZnJvbSBodW50aW5nLg0KPiA+Pj4N
Cj4gPg0KPiA+DQo+ID4tLQ0KPiA+UGV0ZSBSZXNuaWNrIDxodHRwOi8vd3d3LnF1YWxjb21tLmNv
bS9+cHJlc25pY2svPg0KPiA+UXVhbGNvbW0gVGVjaG5vbG9naWVzLCBJbmMuIC0gKzEgKDg1OCk2
NTEtNDQ3OA0KDQo=


From nobody Wed Aug 23 18:32:27 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF90A1321EF for <ietf@ietfa.amsl.com>; Wed, 23 Aug 2017 18:32:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level: 
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=iecc.com header.b=Od09BYpD; dkim=neutral reason="invalid (public key: not available)" header.d=taugh.com header.b=S1D6J3DM
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mgTTx2M04MZA for <ietf@ietfa.amsl.com>; Wed, 23 Aug 2017 18:32:24 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56B1413219F for <ietf@ietf.org>; Wed, 23 Aug 2017 18:32:24 -0700 (PDT)
Received: (qmail 9899 invoked from network); 24 Aug 2017 01:32:23 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=26a9.599e2ca7.k1707; bh=AC4lv2/HZJkfcUVnAWAJGyTeiVECurIwLHntn9N3dDw=; b=Od09BYpDqRcJsnepiW8NXwRlz0wOT30SuZClXwsZ3InnJDMMd4be1ey2gTczCeiRS+AYgSipB2rdDI4HsoF2879bm3JBwU0ytqTJ2CqOfpKL3LsrtPkHwf3CHyGhOnLXmFVzvzMmbkvCx3myL4XWxhfyWmud+tkdfkM3duazmyhbtTJLBIg/UKXyqqGMqT+qOy9SZFVZ8J0QcTQT+ycTzl+eDt9Qb8j19balT5KIL7UpaVnHBx+vPE2CMdsg60fK
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=26a9.599e2ca7.k1707; bh=AC4lv2/HZJkfcUVnAWAJGyTeiVECurIwLHntn9N3dDw=; b=S1D6J3DMb0aOeB8g2xCL18BRO35wB14A75tP6MfyfdXcKuierSynJurzIxO5d19wB5R5wjLU/8elXjJMt3rnPP00z7RCXeM9rXRnyiY8iUhwA7fYDiz+Y0Vwvv9pxFp5am0AwvrvhD8iPiulDyK+DGrqQjb1NWXOgmnh1MHumkdZo5WO854t05r2HlVgcKuKpRzdA5py5zppS16JCPOVdeQDL1zA6FVFfGToc/fsGW0uNxeQZdNuZWvrpC7YSekX
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 24 Aug 2017 01:32:22 -0000
Date: 23 Aug 2017 21:32:22 -0400
Message-ID: <alpine.OSX.2.21.1708232125030.81381@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "Toerless Eckert" <tte@cs.fau.de>
Cc: "IETF general list" <ietf@ietf.org>
Subject: Re: Next steps in IETF list email archiving
In-Reply-To: <20170823215111.GA28827@faui40p.informatik.uni-erlangen.de>
References: <20170731132508.GA22575@gsp.org> <20170823194058.18709.qmail@ary.lan> <20170823215111.GA28827@faui40p.informatik.uni-erlangen.de>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Nqqa1plkgtFqaVE9ZGeeSNs4m3c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Aug 2017 01:32:26 -0000

On Wed, 23 Aug 2017, Toerless Eckert wrote:
>> Er, not really.  See RFC 4155.  There are way too many not quite
>> compatible versions of mbox.  If I wanted a file format for a
>> multi-file archive, I'd probably use POSIX ustar which is an actual
>> standard.
>
> Sure, but that would not be a complete spec because it does not cover
> the format of individual messages nor any semantics of file names.
>
> Whats the least restrictive sufficiently well specified generic mail encoding ?
> Anything that would also pass via rfc822+mime ?

We already have a perfectly good mail encoding, the one defined in RFC 
5322 and its predecessors.  (Recall that MIME is entirely hidden inside 
the 5322 message structure.)  I suppose you could come up with a 
convention for filenames, but it hardly matters since anything interesting 
about the message is within the message itself.

As I noted, the current filenames are based on months, but the mail in the 
files only approximantely was sent during the months the names suggest. 
Doesn't matter.

> Might also be nice to have some well-known-filename with metadata
> about the archive content, eg: self-URL, previous, next URL, contact
> URL (if any), archive owner signed checksums of files. Template
> spec of filenames (%YYYY-%MM.mail),...

URL?  This is mail, not a web site.  In any event, if you want to make 
indexes and such on top of an archive, go ahead but it's not part of the 
archive.

> See above: metadata that would help you figure out if you have a
> complete set of archive files.

A file listing the other files with hashes or checksums is all you need 
for that.

R's,
John


From nobody Wed Aug 23 19:45:03 2017
Return-Path: <sammia.rauf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86B3B12008A for <ietf@ietfa.amsl.com>; Wed, 23 Aug 2017 19:45:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KZwzQAsMqk1E for <ietf@ietfa.amsl.com>; Wed, 23 Aug 2017 19:44:59 -0700 (PDT)
Received: from mail-wr0-x243.google.com (mail-wr0-x243.google.com [IPv6:2a00:1450:400c:c0c::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7ABD01327FF for <ietf@ietf.org>; Wed, 23 Aug 2017 19:44:58 -0700 (PDT)
Received: by mail-wr0-x243.google.com with SMTP id n53so728854wrb.2 for <ietf@ietf.org>; Wed, 23 Aug 2017 19:44:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Ol3tKpjy8rdmx9txpJcDqxoMnat7H1CnXy38G9q+/CE=; b=EvAZh3eCs/yFJ3+S/AC2JOfdcDo+T5COfzdjXXBKgILxq99b37fNVnm0TY/1QcdEGq KJJzGNY4uG+lLbEM6Hln3XR8pzYv8wejq2wBV7B6ytl+Fmvk53mj6iS7evoJkdfcuupg 22w1PsKOxb1xWxlSY2ZN0xKv7gJwgr67qsjXhmKpj5z0BYNjLPq3pn3n8nDUkVmhwEns gupemxNBD4y6WtWM9bJSXlZVPbjnii9pH7Z6B+XlNoeCSPx3FpwFgqVdh4kkcEvfkfNl aABKH6nNF73qUmVnSOjOM5s6whefxGKcWxXLSQqvSIew7yBa0mtMbq9O5iVZb/BkmX4m yBAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Ol3tKpjy8rdmx9txpJcDqxoMnat7H1CnXy38G9q+/CE=; b=sRJ+UuSJcR/LKxJ2oiF72WonQ1aD6VLubkhhLL+A2SILRyoH4fLGBae6l3z1Pv/2UT q3I8DkYvWnKXoWyNjO7x8uJfA+gfa5Xuue/mi2NaBg/zdOatxyfV3yy/pTPjEoC4juHG zHMirsNS4wUQhfHskkhAVLLjZ1uSG9jFdhdEqepRpuQkcBuWjw/5MCL8CjjfxfpqzBto 4wl00wqqlDqD7RKkka9i7S6v/0vvewyKds6dbCQSFyKGSjSE6InYs63AcQAkdKmOrZxq 19nOQjrBll+aytrcUh5tW9kOXSnaZDcA6LRlRWnolAgRgD+hqPz84glxCXTh3TnECtYZ ciwQ==
X-Gm-Message-State: AHYfb5i3/gqJq8kf6cie0+NTUCdcH43vXHW2pfooBlrsaY9l521Y1prj SpStxwtMdXxn8/4bVrZ/hWI9PzXfGA==
X-Received: by 10.223.133.140 with SMTP id 12mr2523302wrt.102.1503542696993; Wed, 23 Aug 2017 19:44:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.164.129 with HTTP; Wed, 23 Aug 2017 19:44:56 -0700 (PDT)
In-Reply-To: <65E627F5-B929-4967-A015-A5FC65EFB58A@ackl.io>
References: <150333249451.6815.16917284124201077654@ietfa.amsl.com> <CAEFdpLP2U=jYULOE0gZfOjm8xw25nkaNH5Jk02q5BOnuGdPSAQ@mail.gmail.com> <6E3A4659-E1BA-42DA-97DB-A031332695BA@gmail.com> <65E627F5-B929-4967-A015-A5FC65EFB58A@ackl.io>
From: Sammia Rauf <sammia.rauf@gmail.com>
Date: Thu, 24 Aug 2017 07:44:56 +0500
Message-ID: <CAEFdpLMQy__9=ufH8ea5PBbSm2uyg74DBkkaf=y0PCpUp5JaKA@mail.gmail.com>
Subject: Re: IPv6 over Low Power Wide-Area Networks (lpwan) WG Virtual Meeting: 2017-09-12
To: Alexander Pelov <a@ackl.io>
Cc: Yoav Nir <ynir.ietf@gmail.com>, ietf@ietf.org
Content-Type: multipart/alternative; boundary="001a11491c0c5be9c7055776d072"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ttiTBfeUR5DhhZzxRwq402huGJ8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Aug 2017 02:45:02 -0000

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

Thank you Yove and Alexander for help.

--
Best
Sammia


On Wed, Aug 23, 2017 at 1:03 PM, Alexander Pelov <a@ackl.io> wrote:

> Thanks, Yoav, for the detailed explanation!
>
> Hi Sammia, you are very welcome to this call. We are using Webex for our
> meetings - and the connection details will be announced one week before t=
he
> call. (Personally, I love http://jit.si - we may try it in the future
> calls)
>
> Just a small note - the mailing list is lp-wan@ietf.org . To subscribe
> going to the following link: https://www.ietf.org/mailman/listinfo/lp-wan
>
> Some more information on the LPWAN Working Group (WG):
> - The relevant documents may be found on the WG page on the Datatracker
> (Datatracker is your friend): https://datatracker.
> ietf.org/wg/lpwan/documents/
> - I=E2=80=99d recommend you start with the LPWAN Overview document before=
 diving
> in the IP/UDP SCHC draft.
>
> If you have any questions, ideas or remarks, don=E2=80=99t hesitate to wr=
ite to
> lp-wan@ietf.org.
>
> Welcome and nice to see you join, Sammia!
> Alexander
>
>
> Le 23 ao=C3=BBt 2017 =C3=A0 06:47, Yoav Nir <ynir.ietf@gmail.com> a =C3=
=A9crit :
>
> Hi, Sammia.
>
> First, if you haven=E2=80=99t done so already, join the working group mai=
ling list
> (usually something like lpwan@ietf.org).
>
> On that list they will publish the connection details (usually at IETF
> they use Webex, but other technologies are sometimes used instead, like
> jit.si)
>
> Anyway, they=E2=80=99ll give the details on the list a few days before th=
e meeting.
>
> HTH
>
> Yoav
>
> On 23 Aug 2017, at 7:06, Sammia Rauf <sammia.rauf@gmail.com> wrote:
>
> hi dear
>
> I'm very new to this venue. I want to attend this virtual meeting. Can yo=
u
> please help me? I'm from Pakistan. How can i remotely participate in this
> virtual meeting? Is there any registration procedure?
>
> Best,
>
>
> Sammia Rauf
>
> On Mon, Aug 21, 2017 at 9:21 PM, IESG Secretary <iesg-secretary@ietf.org>
> wrote:
>
>> The IPv6 over Low Power Wide-Area Networks (lpwan) Working Group will ho=
ld
>> a virtual interim meeting on 2017-09-12 from 17:00 to 18:00 Europe/Paris=
.
>>
>> Agenda:
>> The agenda will be announced one week before the meeting.
>>
>> The general items would be:
>> - Advancement of WG items: SCHC-IP/UDP, SCHC-CoAP, LPWAN-overview
>> - New items to be discussed: SCHC-ICMP, SCHC-over-FOO, more
>>
>> Information about remote participation:
>> Remote participation information will be obtained at the time of approva=
l
>>
>>
>
>
>

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

<div dir=3D"ltr">Thank you Yove and Alexander for help.<br><span style=3D"c=
olor:rgb(119,119,119);font-size:12.8px;white-space:nowrap"><br>--<br>Best<b=
r>Sammia<br><br></span></div><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Wed, Aug 23, 2017 at 1:03 PM, Alexander Pelov <span dir=3D"l=
tr">&lt;<a href=3D"mailto:a@ackl.io" target=3D"_blank">a@ackl.io</a>&gt;</s=
pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break=
-word"><div>Thanks, Yoav, for the detailed explanation!</div><div><br></div=
><div>Hi Sammia, you are very welcome to this call. We are using Webex for =
our meetings - and the connection details will be announced one week before=
 the call. (Personally, I love <a href=3D"http://jit.si" target=3D"_blank">=
http://jit.si</a> - we may try it in the future calls)</div><div><br></div>=
<div>Just a small note - the mailing list is <a href=3D"mailto:lp-wan@ietf.=
org" target=3D"_blank">lp-wan@ietf.org</a> . To subscribe going to the foll=
owing link:=C2=A0<a href=3D"https://www.ietf.org/mailman/listinfo/lp-wan" t=
arget=3D"_blank">https://www.ietf.org/<wbr>mailman/listinfo/lp-wan</a></div=
><div><br></div><div>Some more information on the LPWAN Working Group (WG):=
</div><div>- The relevant documents may be found on the WG page on the Data=
tracker (Datatracker is your friend):=C2=A0<a href=3D"https://datatracker.i=
etf.org/wg/lpwan/documents/" target=3D"_blank">https://datatracker.<wbr>iet=
f.org/wg/lpwan/documents/</a></div><div>- I=E2=80=99d recommend you start w=
ith the=C2=A0LPWAN Overview document before diving in the IP/UDP SCHC draft=
.=C2=A0</div><div><br></div><div>If you have any questions, ideas or remark=
s, don=E2=80=99t hesitate to write to <a href=3D"mailto:lp-wan@ietf.org" ta=
rget=3D"_blank">lp-wan@ietf.org</a>.=C2=A0</div><div><br></div><div>Welcome=
 and nice to see you join, Sammia!</div><span class=3D"HOEnZb"><font color=
=3D"#888888"><div>Alexander</div></font></span><div><div class=3D"h5"><div>=
<br></div><br><div><blockquote type=3D"cite"><div>Le 23 ao=C3=BBt 2017 =C3=
=A0 06:47, Yoav Nir &lt;<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_b=
lank">ynir.ietf@gmail.com</a>&gt; a =C3=A9crit :</div><br class=3D"m_-91756=
40700944173476Apple-interchange-newline"><div><div style=3D"word-wrap:break=
-word">Hi, Sammia.<div><br></div><div>First, if you haven=E2=80=99t done so=
 already, join the working group mailing list (usually something like <a hr=
ef=3D"mailto:lpwan@ietf.org" target=3D"_blank">lpwan@ietf.org</a>).</div><d=
iv><br></div><div>On that list they will publish the connection details (us=
ually at IETF they use Webex, but other technologies are sometimes used ins=
tead, like <a href=3D"http://jit.si/" target=3D"_blank">jit.si</a>)</div><d=
iv><br></div><div>Anyway, they=E2=80=99ll give the details on the list a fe=
w days before the meeting.</div><div><br></div><div>HTH</div><div><br></div=
><div>Yoav</div><div><br><div><blockquote type=3D"cite"><div>On 23 Aug 2017=
, at 7:06, Sammia Rauf &lt;<a href=3D"mailto:sammia.rauf@gmail.com" target=
=3D"_blank">sammia.rauf@gmail.com</a>&gt; wrote:</div><br class=3D"m_-91756=
40700944173476Apple-interchange-newline"><div><div dir=3D"ltr">hi dear<br><=
br><div>I&#39;m very new to this venue. I want to attend this virtual meeti=
ng. Can you please help me? I&#39;m from Pakistan. How can i remotely parti=
cipate in this virtual meeting? Is there any registration procedure?<br><br=
>Best,<br><br><br>Sammia Rauf</div></div><div class=3D"gmail_extra"><br><di=
v class=3D"gmail_quote">On Mon, Aug 21, 2017 at 9:21 PM, IESG Secretary <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:iesg-secretary@ietf.org" target=3D"_bl=
ank">iesg-secretary@ietf.org</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">The IPv6 over Low Power Wide-Area Networks (lpwan) Working Group =
will hold<br>
a virtual interim meeting on 2017-09-12 from 17:00 to 18:00 Europe/Paris.<b=
r>
<br>
Agenda:<br>
The agenda will be announced one week before the meeting.<br>
<br>
The general items would be:<br>
- Advancement of WG items: SCHC-IP/UDP, SCHC-CoAP, LPWAN-overview<br>
- New items to be discussed: SCHC-ICMP, SCHC-over-FOO, more<br>
<br>
Information about remote participation:<br>
Remote participation information will be obtained at the time of approval<b=
r>
<br>
</blockquote></div><br></div>
</div></blockquote></div><br></div></div></div></blockquote></div><br></div=
></div></div></blockquote></div><br></div>

--001a11491c0c5be9c7055776d072--


From nobody Wed Aug 23 20:47:06 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 381D01329FF for <ietf@ietfa.amsl.com>; Wed, 23 Aug 2017 20:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AqCWbD_qjWX0 for <ietf@ietfa.amsl.com>; Wed, 23 Aug 2017 20:47:02 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8C8D1323A2 for <ietf@ietf.org>; Wed, 23 Aug 2017 20:47:01 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 32F8258C4AF; Thu, 24 Aug 2017 05:46:58 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 1DB55B0C9A3; Thu, 24 Aug 2017 05:46:58 +0200 (CEST)
Date: Thu, 24 Aug 2017 05:46:57 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: John R Levine <johnl@taugh.com>
Cc: IETF general list <ietf@ietf.org>
Subject: Re: Next steps in IETF list email archiving
Message-ID: <20170824034657.GB28827@faui40p.informatik.uni-erlangen.de>
References: <20170731132508.GA22575@gsp.org> <20170823194058.18709.qmail@ary.lan> <20170823215111.GA28827@faui40p.informatik.uni-erlangen.de> <alpine.OSX.2.21.1708232125030.81381@ary.qy>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.OSX.2.21.1708232125030.81381@ary.qy>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mCqKC5Y9ot0OUgdQFlZYCQ6TMw8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Aug 2017 03:47:04 -0000

On Wed, Aug 23, 2017 at 09:32:22PM -0400, John R Levine wrote:
> We already have a perfectly good mail encoding, the one defined in
> RFC 5322 and its predecessors.  (Recall that MIME is entirely hidden
> inside the 5322 message structure.)  I suppose you could come up
> with a convention for filenames, but it hardly matters since
> anything interesting about the message is within the message itself.

Great.

> >Might also be nice to have some well-known-filename with metadata
> >about the archive content, eg: self-URL, previous, next URL, contact
> >URL (if any), archive owner signed checksums of files. Template
> >spec of filenames (%YYYY-%MM.mail),...
> 
> URL?  This is mail, not a web site.  In any event, if you want to
> make indexes and such on top of an archive, go ahead but it's not
> part of the archive.
> 
> >See above: metadata that would help you figure out if you have a
> >complete set of archive files.
> 
> A file listing the other files with hashes or checksums is all you
> need for that.

Are there any RFCs specifying how mirrors can point to each others so
folks retrieving the information can load-balance/failover etc.. That ws
pretty much the level i was suggesting, and its certainly an orthogonal
problem.

Cheers
    Toerless

> R's,
> John

-- 
---
tte@cs.fau.de


From nobody Wed Aug 23 21:10:36 2017
Return-Path: <lyndon@orthanc.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E768712700F for <ietf@ietfa.amsl.com>; Wed, 23 Aug 2017 21:10:35 -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 autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5ac4yybTa7cz for <ietf@ietfa.amsl.com>; Wed, 23 Aug 2017 21:10:34 -0700 (PDT)
Received: from orthanc.ca (orthanc.ca [IPv6:2607:f2f8:abf8::2]) (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 3A708132143 for <ietf@ietf.org>; Wed, 23 Aug 2017 21:10:33 -0700 (PDT)
Received: from minnie.hitronhub.home (S0106a84e3f81a003.vc.shawcable.net [24.80.126.119]) (authenticated bits=0) by orthanc.ca (8.15.2/8.15.2) with ESMTPSA id v7O4AP62062326 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 23 Aug 2017 21:10:26 -0700 (PDT) (envelope-from lyndon@orthanc.ca)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Next steps in IETF list email archiving
From: Lyndon Nerenberg <lyndon@orthanc.ca>
In-Reply-To: <20170824034657.GB28827@faui40p.informatik.uni-erlangen.de>
Date: Wed, 23 Aug 2017 21:10:20 -0700
Cc: John R Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <EE74ED30-5D94-4D16-9439-35B54ADE9450@orthanc.ca>
References: <20170731132508.GA22575@gsp.org> <20170823194058.18709.qmail@ary.lan> <20170823215111.GA28827@faui40p.informatik.uni-erlangen.de> <alpine.OSX.2.21.1708232125030.81381@ary.qy> <20170824034657.GB28827@faui40p.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8XMsbkwmLu4fuQw6Y-OeRvGx5GY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Aug 2017 04:10:36 -0000

>> We already have a perfectly good mail encoding, the one defined in
>> RFC 5322 and its predecessors.  (Recall that MIME is entirely hidden
>> inside the 5322 message structure.)  I suppose you could come up
>> with a convention for filenames, [...]

MH nailed down that standard decades ago.  One message per file, in a =
suitable directory hierarchy. E.g.

  ietf/<listname>/<year>/<nn>

This avoids the ambiguity of mbox message separator escapes (the '>From' =
problem), but creates a lot of overhead for things like rsync.

But for a public archive interface, why aren't/can't we use anonymous =
IMAP, with a folder structure as above?  This hides the underlying =
storage format.  It provides search capabilities to na=C3=AFve clients, =
and it's easy to write mirroring tools.  It's trivial to make mirroring =
decisions based on UIDVALIDITY and UIDNEXT; the mirroring tool is =
essentially an offline IMAP client.

> Are there any RFCs specifying how mirrors can point to each others so
> folks retrieving the information can load-balance/failover etc.. That =
ws
> pretty much the level i was suggesting, and its certainly an =
orthogonal
> problem.

For the IMAP case, the fanout happens behind the scenes, with the list =
exploder feeding the IMAP archive servers by Submission is almost every =
case.  This doesn't guarantee complete synchronization between all the =
public IMAP servers, but they will be close enough in daily operation to =
be useful.  Certainly this is no different from load balancing across =
public anonymous FTP servers.

If people want local mirrors, there are already tools out there for =
remote-syncing IMAP accounts that could be easily adapted to the task.  =
But I'm sure lots of people would cook up dedicated tools in short =
order.

--lyndon=


From nobody Wed Aug 23 21:39:11 2017
Return-Path: <touch@strayalpha.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F2981329CF; Wed, 23 Aug 2017 21:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.99
X-Spam-Level: 
X-Spam-Status: No, score=-1.99 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7U6AOxg6q_cV; Wed, 23 Aug 2017 21:39:08 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 41D211323F7; Wed, 23 Aug 2017 21:39:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=tQbvlt+1F6NizoNJeuxKQv2ZPtahYYRAD1aOs1U0h1A=; b=wZtU7XaUNC+g789dFLyiBKcN72 EIOmmQCp+3dWT85s2Yv/Q2ixqWp2cVnfXDhdr7Wk4fSuQ58PvOJFR5qqBUUJX0InOGBqNoome/xsd l+kcpayTT76T3wpreHfPsnDYWjl0VmNyTFxVJouvYh046PqZm6kEwa18XTzinufBsX4HRjHfJAs7f p7qUmSsArFBfMQjIog4gAH7FZZhpcO0j/hVVkWhEWrl6QWxyk9Hf0XjUc4DkkPGz2/CIsPpk/ar45 TBC06CJKo4OVgUPXWcCHMCUUwbpxsdu0rSQQhyMuOrBOJx1+BmBqziSoHeGm63uRbt6Yn2S9A7msN ybcVRVaA==;
Received: from cpe-172-250-240-132.socal.res.rr.com ([172.250.240.132]:52647 helo=[192.168.1.189]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <touch@strayalpha.com>) id 1dkjv8-001aJr-Lr; Thu, 24 Aug 2017 00:39:07 -0400
Subject: tsv-dir review of draft-ietf-ospf-encapsulation-cap-06
To: IETF discussion list <ietf@ietf.org>, ospf@ietf.org
References: <150280426212.21081.15543071828535131713.idtracker@ietfa.amsl.com>
Cc: TSV Dir <tsv-dir@ietf.org>
From: Joe Touch <touch@strayalpha.com>
Message-ID: <7ca66dbe-1437-482d-a785-d5e48a558ccb@strayalpha.com>
Date: Wed, 23 Aug 2017 21:39:04 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <150280426212.21081.15543071828535131713.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rp5GIbDtuwxQBG-XSDqptALM1so>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Aug 2017 04:39:10 -0000

Hi, all,

I am the assigned TSV-ART reviewer for draft-ietf-ospf-encapsulation-cap

For background on TSV-ART, please see the FAQ at
<https://trac.ietf.org/trac/tsv/wiki/TSV-Directorate>.

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

Joe

------

I've reviewed this document as part of the transport area directorate's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the
document's authors for their information and to allow them to address
any issues raised. When done at the time of IETF Last Call, the authors
should consider this review together with any other last-call comments
they receive. Please always CC tsv-dir@ietf.org if you reply to or
forward this review.

"This draft has serious issues, described in the review, and needs to be
rethought."

Although I found no transport issues, there are many fundamental
problems that need to be corrected before this document should proceed.
These are summarized below.

Sec1: The introduction jumps too quickly into a list of situations in
which tunnels are used, two of which are emerging (currently only
drafts). There are many better and more established examples (going back
to the M-Bone, the 6-Bone, etc., to VPNs, network virtualization, etc.).
Terms are used before defined (what is an ingress? are you referring to
the router or host at which a tunnel is attached, or the input to the
tunnel itself?). The last two sentences should begin the intro, which
should expand and explain what is meant (e.g., by "egress tunneling" and
the reason for wanting to encode tunnels as LSAs.

Sec2: The terminology section is incomplete. The terms tunnel, ingress,
egress, egress tunneling, etc. are not defined in RFC7770. Only the LSA
terminology is relevant from that RFC. Other terms need to be defined in
this doc or used from others.

Sec3: This section is written as if the "Encapsulation Capability TLV"
is already defined (in RFC7770), rather than being defined herein. The
section title doesn't match this name, which is confusing. The term TLV
is itself confusing, as this is really a single TLV of the RI Opaque LSA
set of types, which itself is represented as a (sub)TLV list. I
appreciate that this terminology was made confusing in previous,
established documents, but a bit of explanation would go a long way - as
would showing the top-level OSPF RI Opaque LSA and where the new TBD1
value would appear - before diving into the structure inside this new "TLV".

Sec 4: the discussion should clarify what happens if the length field is
longer than the fields indicated by the sub-TLVs (is this an error or
padding to be ignored; does the latter present a covert channel).
additionally, this section refers to RFC5512 - which is being obsoleted
by ietf-idr-tunnel-encaps - and this pending ID is used as the primary
reference in Secs 5.1 and 5.2. References to RFC5512 should be replaced
with that ID (which I'll assume will be published concurrently).

Sec 5: this section refers to the concept of an "invalid" sub-TLV; given
the previous sentence explains that unknown sub-TLVs are silently
ignored, then what exactly is an invalid sub-TLV? It further isn't clear
why 2 octets of type and 2 octets of length are needed (granted it
provides alignment, but is that really important for this sort of
application-layer protocol?)

Sec 5.1 and 5.2: it is unclear why the two fundamental sub-TLVs of this
TLV are defined elsewhere; in specific, the example of the sub-TLV
should appear here (actually for each of the sub-TLVs).

Sec 5.3 infers IP address version from length, when the version could
(should) easily encoded either as different types (you have 65K of
them!) or using an additional few bits (e.g., carved out of the excesses
noted in Sec 5).

Sec 5.4 - I had to thread through several different sections of the IDR
ID to figure out what Color meant and how it is used. Granted that is a
different problem in a different doc, IMO this doc should include enough
of a summary that this sort of 'traceback' should not be needed to
understand what is being described. Further, the other doc doesn't even
explain Color sufficiently, IMO.

Secs 5.6 and 5.7 - There are many rules for how the outer encapsulation
header is composed, and many fields it may affect beyond QoS and UDP
destination port. This section is incomplete in describing values for
the outer header(s) or relationships to the inner header(s).

Sec 6 - I would encourage moving this section earlier, before the
details of how the LSA is composed.

Sec 7 - the document should describe where experimental values
can/should be safely used and how collisions are handled; it should also
explain what happens when a reserved value is seen in an LSA.

----



From nobody Thu Aug 24 04:20:17 2017
Return-Path: <worley@ariadne.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BC7A713293C; Thu, 24 Aug 2017 04:20:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dale Worley <worley@ariadne.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-homenet-dot.all@ietf.org, homenet@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-ietf-homenet-dot-12
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150357360963.24287.5193275103043411365@ietfa.amsl.com>
Date: Thu, 24 Aug 2017 04:20:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fmQILabmTkqoXVMA8bUY4CSAXbU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Aug 2017 11:20:10 -0000

Reviewer: Dale Worley
Review result: Ready

I am the assigned Gen-ART reviewer for this draft.  The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at
<https://wiki.tools.ietf.org/area/gen/wiki/GenArtfaq>.

Document:  draft-ietf-homenet-dot-12
Reviewer:  Dale R. Worley
Review Date:  2017-08-24
IETF LC End Date:  2017-08-25
IESG Telechat date:  2017-08-31

Summary:

This draft is ready for publication as a Standards Track RFC.  It has
some nits that should be considered before publication.

4.  Domain Name Reservation Considerations

   3.  Name resolution APIs MUST send queries for such
       names to a recursive DNS server that is configured to be
       authoritative for the 'home.arpa.' zone appropriate to the
       homenet.

If I understand the terminology correctly, this rules out sending the
query to a DNS server that recursively sends the query to a server
that is authoritative for home.arpa.  If that is intended and there
are technical reasons for making this prescription, that's OK, but I
want to check that that is intended, as this rule is stricter than the
similar rule in the second paragraph of item 4, which is qualified
"Unless configured otherwise".

4.  Domain Name Reservation Considerations

There are 5 paragraphs under item 4.  It might be worth giving them
separate numbers, or if they truly form a unified topic, giving them
sub-numbers 4a, 4b, etc.

6.  Security Considerations

   Therefore, the only delegation that will allow
   names under 'home.arpa.' to be resolved is an insecure delegation, as
   in [RFC6303] section 7.

In context what this means is clear, but its literal meaning is
sufficiently incorrect that I think it could be clarified, perhaps to

   Therefore, the only delegation that will allow names under
   'home.arpa.' to be resolved by a validating resolver that is not
   aware of the local meaning is an insecure delegation, as in
   [RFC6303] section 7.

[EOF]



From nobody Thu Aug 24 08:22:52 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D69B132BCE for <ietf@ietfa.amsl.com>; Thu, 24 Aug 2017 08:22:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X1697pOAdZ-A for <ietf@ietfa.amsl.com>; Thu, 24 Aug 2017 08:22:49 -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 D01FE13237B for <ietf@ietf.org>; Thu, 24 Aug 2017 08:22:49 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id D1102E20B for <ietf@ietf.org>; Thu, 24 Aug 2017 11:25:54 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id F0221842A4 for <ietf@ietf.org>; Thu, 24 Aug 2017 11:22:48 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF general list <ietf@ietf.org>
Subject: Re: Next steps in IETF list email archiving
In-Reply-To: <EE74ED30-5D94-4D16-9439-35B54ADE9450@orthanc.ca>
References: <20170731132508.GA22575@gsp.org> <20170823194058.18709.qmail@ary.lan> <20170823215111.GA28827@faui40p.informatik.uni-erlangen.de> <alpine.OSX.2.21.1708232125030.81381@ary.qy> <20170824034657.GB28827@faui40p.informatik.uni-erlangen.de> <EE74ED30-5D94-4D16-9439-35B54ADE9450@orthanc.ca>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.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-sha256; protocol="application/pgp-signature"
Date: Thu, 24 Aug 2017 11:22:48 -0400
Message-ID: <27860.1503588168@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mDQQv7FgEDOiDbPkmNMMIZAXmxc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Aug 2017 15:22:51 -0000

--=-=-=
Content-Type: text/plain


Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
    > But for a public archive interface, why aren't/can't we use anonymous
    > IMAP, with a folder structure as above?  This hides the underlying

We can, and we already do.

I think the problem is that many people would like to suck the archives back
in bulk, and they see IMAP as too chatty.


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




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

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

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlme70gACgkQgItw+93Q
3WVBDQgAu53C6BCgcZu2sreOTJ4hApj4Vr93ubxDyKc82eO4Fo+Wn5/qqt8Qj7ae
bGCL7T8a6vQ93wa5k3nKobEn3GoxIqhxPzNcxcM/gKEboQNbCa6qcCg/HudWLBSe
pm/TwBge2ss+DwAvyILR65YNNVJUPV9VLICwzXiIY9Got3ID1V7WpSdmWMEdy6oX
epVEfVWl1mfR1V6u6U3WreQtrnlxcaaefVAoTcjk7CxW+Ay0gB9J8esyt5CZrGwS
VExNzgRZGRIH7/W5VGsjvKcRL+RLd96czrTy3znqiJE3+H4/M7VKdDXsImChwwCP
XjVVRBfMc2NnjLX4o77zdlTDY+J5XA==
=juQW
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Aug 24 09:06:44 2017
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79F9F132BCD; Thu, 24 Aug 2017 09:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yVYFoHgXdhFj; Thu, 24 Aug 2017 09:06:38 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E062E1329AF; Thu, 24 Aug 2017 09:06:37 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id v7OG6ZDg003905; Thu, 24 Aug 2017 17:06:35 +0100
Received: from 950129200 (196.252.114.87.dyn.plus.net [87.114.252.196]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id v7OG6UP8003863 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Aug 2017 17:06:34 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Elwyn Davies'" <elwynd@dial.pipex.com>, <gen-art@ietf.org>
Cc: <draft-ietf-teas-pce-central-control.all@ietf.org>, <ietf@ietf.org>, <teas@ietf.org>
References: <150326246998.3553.16986401070448324505@ietfa.amsl.com>
In-Reply-To: <150326246998.3553.16986401070448324505@ietfa.amsl.com>
Subject: RE: [Teas] Genart last call review of draft-ietf-teas-pce-central-control-03
Date: Thu, 24 Aug 2017 17:06:24 +0100
Message-ID: <065c01d31cf2$f203e040$d60ba0c0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKiBtCv3C99t92nP+D+64XFU4lwwKD1Yexw
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23280.000
X-TM-AS-Result: No--18.487-10.0-31-10
X-imss-scan-details: No--18.487-10.0-31-10
X-TMASE-MatchedRID: yebcs53SkkCnykMun0J1wvHkpkyUphL9MhomkrNJ+uzNQVzhfYY5ss3M E4JSKf6jwO0XmKlkN6h37jIEiVeZu9Sq6q0CYrH3t1AhvyEKdj4ZKp0SZ4P+dfkUT+PL07ed07z aVZEg+DPE51KUDhTqFI2Pte01jMa1F/Pivu+18V0ER9Ta+6BEXcMdI0UcXEHziJ71fA8tGWgc5Z b9Gn+Kyi9hoxU2ysWvwW0HcKZdPoK0S/LholNXqfzu9Lw9C7fAgHzgwy8qV5qdwU/qXYxHvI1Tb KWhjfzBVguChDYYg16S30HCTNLdYHFXLIFQlX/F+cKX6yCQ13vHeXKrbMIpAOouc5Rcf1B0wJLY AybWdAJoGq134T2nlFUtXMzbYTKJUJc+88wC0T5/n3z4qeww6ILLh2/Jcc7edEG7y+D7o5ARGoG JcaPeD0JXZnlGyrNBJJDVrEv2PB32fv0LTPfvM31UZSPvDstZ0i/hFXziUdOXcnNUa+aFRfcgZS +tipLVlZaHSIhaFDgBmvTbn2Br79a/jIZoZyKFSEQN/D/3cG4fXzVgO0hVqg2G3vz8l/IE8UfEo 6khbdimeRbQwHAp670jL1dNSkkWwQh6YUqfT5IwiJTf3kjwfX2/mTu5B5RIh6BE/IXc9Sjp6M2T fc1dC9itRFsTmvHsye0+js2lbAZ0VhcRz+glNvt3QgyOPXbLtmsMcVX5NwfHiAsZELoUA1J1Vsw qK55IVZOEYEsHFBv2RJd2bEUo1LcH1nZMbpOp9w4QVIZvk2J3T8gwfPR6+Zy1Yc8tPkV9R0u6by ldJV1QTSFNt6LQtapfKHXwH61nx94l9TkMZwueAiCmPx4NwFkMvWAuahr8+gD2vYtOFhgqtq5d3 cxkNQP90fJP9eHt
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mfmG7-I-Iv8gJn-5VCisakmFT4k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Aug 2017 16:06:42 -0000

Elwyn,

Thanks for the review.

> Summary:
> Almost ready.  I found this a well-written and mostly readily =
comprehensible
> document although it contains a couple of instances of unexplained =
SDN/PCE
> jargon (notably 'southbound').  My main concern is that the =
archtecture
> suggests that extensions to PCEP will a.s. be needed and implies that
> mechanisms will be needed to provide multiple extensions but neither =
specifies
> detailed guidance as to how this might be done or points to work in =
progress
> that would provide this guidance. =20

I'm pretty sure that this architecture should not tell the protocol =
designers how to do their jobs. So "detailed guidance" may be too much, =
but Section 4 does give "Guidance for Solution Developers".

Perhaps the simplest thing is to point at =
draft-zhao-pce-pcep-extension-for-pce-controller which is where early =
work on protocol extensions lives. It's not a working group document =
(yet?) and it still has some issues, but I've changed
OLD
   It is anticipated that new documents will be produced for each use
   case dependent on support and demand.  Such documents will explain
   the use case and define the necessary protocol extensions.
NEW
   It is anticipated that new documents (such as=20
   [I-D.zhao-pce-pcep-extension-for-pce-controller]) will be produced
   for each use case dependent on support and demand.  Such documents
   will explain the use case and define the necessary protocol =
extensions.
END

> The implication of the statements in this
> document are that an implementation or deployment might need to check =
if
> particlar extensions are implemented in communication partners and =
also how to
> behave if an unreconixed extension is received especially to avoid =
possible
> DoS.

RFC 5440 already describes how to handle unknown protocol elements. =
Additionally, the PCEP Open message allows for exchange of capabilities =
information. We can make these points as:

OLD
   The only work expected to be needed is extensions to
   existing PCEP messages to carry additional or specific information
   elements for the individual use cases, which maintain backward
   compatibility and do not impact existing PCEP deployments.  Where
   possible, consistent with the general principles of how protocols are
   extended, any additions to the protocol should be made in a generic
   way such that they are open to use in a range of applications.
NEW
   The only work expected to be needed is extensions to
   existing PCEP messages to carry additional or specific information
   elements for the individual use cases, which maintain backward
   compatibility and do not impact existing PCEP deployments.  [RFC5440]
   already describes how legacy implementations handle unknown=20
   PCEP extensions and how to use the PCEP Open message to indicate
   support for PCEP features.  Where possible, consistent with the =
general
   principles of how protocols are extended, any additions to the
   protocol should be made in a generic way such that they are open
   to use in a range of applications.
END

>  The other minor issues are only just abve the level of nits.
>=20
> Major issues:
> None
>=20
> Minor issues:
>=20
> Abstract:  The abstract is probably overlong.

Ah, why use 3 words when 10 will do?

RFC Ed suggests that up to 20 lines is OK. We have 21. I couldn't =
immediately see anything gratuitously superfluous, so I'm leaving it as =
is.

> s1:  RFC 4655 is itself an architecture that introduces the PCE.  It =
would be
> helpful to explain that this document is an extension of the basic PCE
> arcitecture except that it relies on the specific use of the PCEP for
> intercommunication between architectural elements providing traffic =
control and
> routing whereas RFC 4655 does not assume any particular protocol.

Hmmm. You're right. 4655 doesn't make protocol assumptions. In fact it =
pre-dated the WG's choice of a protocol.
Of course, since then PCEP has been adopted and is the de facto protocol =
for PCE.=20

How about...

OLD
   This document introduces the architecture for PCE as a central
   controller, examines the motivations and applicability for PCEP as a
   southbound interface, and introduces the implications for the
   protocol.  A PCE-based central controller can simplify the processing
   of distributed control plane by blending it with elements of SDN and
   without necessarily completely replacing it.
NEW
   This document introduces the architecture for PCE as a central
   controller as an extension of the architecture described in [RFC4655]
   and assumes the continued use of PCEP as the protocol used between
   PCE and PCC.  The document also examines the motivations and=20
   applicability for PCEP as a southbound interface and introduces the=20
   implications for the protocol used in this way.  A PCE-based central=20
   controller can simplify the processing of distributed control plane =
by
   blending it with elements of SDN and without necessarily completely
   replacing it.
END

> s3.2: It would be desirable to reiterate the problem of =
synchronization
> mentioned in s2.1.2 which is relevant to all the high level functions.

I agree that synchronization of "parallel" stateful PCEs is a very real =
(and potentially hard) problem. I agree that this issue needs to be =
exposed wherever  the concept of parallel controllers is present.

But how is this relevant to Section 3.2?

I have added a paragraph to the bottom of Section 4 as...

   Note that protocol mechanisms to handle synchronization of state
   in parallel PCE-based controllers will also be required if parallel =
controllers
   are used as described in Section 2.1.2.  There is a discussion of =
mechanisms
   to achieve PCE state synchronization in [I-D.ietf-pce-stateful-pce].

> s4: Since this document effectively gurantees that extensions to PCEP =
will be
> created and since RFC 5440 contains no extensibility =
procedures/guidelines, it
> seems to me that either this document should indicate how PCEP =
extensions and
> profiles are added to the base protocol or should point  to a =
(normative and
> currently non-existent) document that updates RFC 5440 and defines how
> extensions shoould be structured and provides ways for implementations =
to
> determine what is supported, if necessary.

Actually (as above) I think 5440 does contain adequate procedures.

Section 6.2 describes the exchange of capabilities.
Section 6.9 handles receipt of unknown messages.
Section 7.2 shows how objects are marked as mandatory to process of not =
and goes on to describe processing of unknown objects.
Section 7.1 describes how to handle unknown TLVs.

> s5, para 2:  The second part of this paragraph;
>    However, debate will rage over overall system security and the =
opportunity
>    for attacks in an architecture with a central controller since the =
network
>    can be vulnerable to denial of service attacks on the controller, =
and the
>    forwarding system may be harmed by attacks on the messages sent to
>    individual NEs. In short, while the interactions with a PCE-based =
controller
>    are not substantially different from those in any other SDN =
architecture,
>    the security implications of SDN are still open for discussion. The =
IRTF's
>    SDN Research Group (SDNRG) discussed this topic.
> This text needs to be rewritten to be suitable for inclusion in an RFC =
that is
> a document of record.

Oh. :-)

We could (of course?) not hope to reach consensus one a number of issues =
related to SDN. So we tried some weasel words. Apparently your BS =
detector is functioning perfectly.

How about something a little more definitive...

However, an architecture with a central controller has a central point =
of failure and
this is also a security weakness since the network can be vulnerable to
denial of service attacks on the controller. Similarly, the central =
controller
provides a focus for interception and modification of messages sent to
individual NEs. In short, while the interactions with a PCE-based =
controller
are not substantially different to those in any other SDN architecture,
the security implications of SDN have not been fully discussed or =
described.
Therefore, protocol and applicability work around solutions for this
architecture must take proper account of these concerns.

> s6:  The PCE, depending on which of the aspects mentioned in s3 and =
the
> technology being managed (LSPs, transport paths, etc.) are involved in =
a
> particular imlemetation/deployment, will need to access the relevant =
state
> information in NEs and possibly other PCEs using relevant managent =
protcol(s)
> and MIBs or similar.  Integrating this state information with the PCEP
> management information wil be key to effective operation of the =
centralized PCE
> system.

Is this any different from any other use of PCE, and especially stateful =
PCE?

I have added a note to highlight it.

   An implementation of a PCE-based controller will require access to =
information about the state of
   the network, its nodes, and its links.  Some of this will be the TED =
as is normal for a PCE and can be
   collected using the mechanisms already in place (such as listening to =
the IGPs, using BGP-LS
   [RFC7752], or northbound export of YANG-encoded data =
[I-D.ietf-teas-yang-te-topo].  More
   information may be collected in the LSP database as described for =
stateful PCEs as described=20
   in [RFC7399] and [I-D.ietf-pce-stateful-pce].  Additional information =
may be needed for other
   specific use cases and will need to be collected and passed to the =
controller.

> s10:  It is arguable, IMO, that RFC 5440 and =
I-D.ietf-pce-pce-initiated-lsp are
> normative references.  The architecture implies their usage and =
someone
> implementing the architecture would need to be familiar with the =
details of the
> extended PCEP, particularly in respect of the manageability and =
security
> aspects of the protocol.

Sure.

> Nits/editorial comments:
>=20
> Abstract, para 1: Statements of implied omnipotence by mortals a.s. =
lead to
> hubristic consequences...  s/any definition of "optimal"/virtually any
> definition of "optimal"/

Hubris is in the eye of the whichever one of the gods is beholding us =
today.

s/any definition/most definitions/

> Abstract (and subseqently):  The term 'southbound' is SDN specific =
jargon and
> should be explained.  Given that the abstract is already (IMO) too =
long, it
> would be wise to remove it from the abstract (I don't think it is =
essential)
> and provide the explation in s1.

Removed from Abstract.
Added "(i.e.,  a control protocol for communicating from the central =
controller to network elements)" to s1.

> s1, para 4: See comment above... s/any form of routed or switched
> network./virtually any form of routed or switched network./

Ditto above.

> s2, para 2 and Figures 1-7:  It would be useful to add a note in s2 to =
indicate
> that the TED box in all the figures should imply that other databases =
may also
> be accessed.

OK. Added a note

> s2, last para (just before Fig.3): s/use case- specific/use =
case-specific [or
> use case specific]/

Hmmm. An xml2rfc bug. Bypassed.

> s2.1, para 1: The text at the beginning of the para doesn't read very =
easily -
> the 'or' disguises the fact that the two problems are on either sideof =
the
> 'or'.  Suggest someting like:=20
>OLD:
> Systems with central controllers are
> vulnerable to two problems: failure or overload of the single =
controller.=20
> NEW:
> Systems with a single central controllers are vulnerable to two =
problems:
>   - controller failure, and
>   - controller overload.
> ENDS

OK

> s3.1.4, last para:
>      new protocol extensions may be needed, and some are already being =
worked
>      on in [I-D.ietf-pce-wson-rwa-ext].
> The second clause of this is not future proof:   Suggest
> s/and some are already being worked on in =
[I-D.ietf-pce-wson-rwa-ext]./as, for
> example, described  in [I-D.ietf-pce-wson-rwa-ext]./

OK

> s3.1.5, para 1: s/the header or a packet/the header of a packet/ (I =
think -
> certainly for IPv6 use case)

Ack

> s3.2.2, last para:  The final sentence is probably superfluous - and, =
if it
> remains, probably needs a reference to explain what a FEC is.

What the FEC?
Removed.

Thanks again,
Adrian


From nobody Thu Aug 24 09:25:16 2017
Return-Path: <acee@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCDE713243E; Thu, 24 Aug 2017 09:25:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level: 
X-Spam-Status: No, score=-14.521 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l7GRgIblsZ9D; Thu, 24 Aug 2017 09:25:12 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2D181321E6; Thu, 24 Aug 2017 09:25:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6652; q=dns/txt; s=iport; t=1503591911; x=1504801511; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=5wowc4KxY1Uj90TSejYiNN1gBVXGsseka9Ai9YlArME=; b=Fu8sj9vER5NEcOeRGxGgEMUVpvVU77adkyO225CJ/Aqtn0ck8QU5xZN+ 99U9ZnUK0gsd8VQrHaoDAoufMmAdMummGF/7dY4JMeRizCUxLNOXiqtP1 7ImTbGWQVR37UeZmKnnziyzabFpMrdZJ5B2OMYhMpjgXlwh5jgeCvVm6A s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DzAAB6/Z5Z/5ldJa1aAxYDAQEBAQEBA?= =?us-ascii?q?QEBAQEHAQEBAQGDWmSBFQeDcIodkBaBcJE5hGyCEiyFGxyENj8YAQIBAQEBAQE?= =?us-ascii?q?BayiFGQEFIxFFEgEGAhQEAgIjAwIEMBQBBQ0EAQ0FG4oWEJEOnWaCJ4tWAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEegQ2CHYICgy+CG4EMhQoKJoJMgmEFoFkCh1SMb4I?= =?us-ascii?q?ShWOKb4lwjD8BHziBCncVhWAcMoE1dooTgQ8BAQE?=
X-IronPort-AV: E=Sophos;i="5.41,422,1498521600"; d="scan'208";a="276511978"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Aug 2017 16:24:51 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v7OGOogN007661 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 24 Aug 2017 16:24:51 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 24 Aug 2017 12:24:50 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Thu, 24 Aug 2017 12:24:50 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Xuxiaohu <xuxiaohu@huawei.com>, Pete Resnick <presnick@qti.qualcomm.com>
CC: "gen-art@ietf.org" <gen-art@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, "draft-ietf-ospf-encapsulation-cap.all@ietf.org" <draft-ietf-ospf-encapsulation-cap.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: =?utf-8?B?UmU6IOetlOWkjTogR2VuYXJ0IGxhc3QgY2FsbCByZXZpZXcgb2YgZHJhZnQt?= =?utf-8?Q?ietf-ospf-encapsulation-cap-06?=
Thread-Topic: =?utf-8?B?562U5aSNOiBHZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRm?= =?utf-8?Q?-ospf-encapsulation-cap-06?=
Thread-Index: AQHTHPWC2ul1ZKCGrUqeBeF5Dh6CYw==
Date: Thu, 24 Aug 2017 16:24:50 +0000
Message-ID: <D5C474D6.C37C9%acee@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.201]
Content-Type: text/plain; charset="utf-8"
Content-ID: <5A217C8693157A4BA5ECEE1B6D961160@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pmZD2BGKP__H4otNUy9oICc9voQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Aug 2017 16:25:15 -0000

SGkgUGV0ZSwgDQoNCk9uZSBtb3JlIGlubGluZSBzaW5jZSBYaWFvaHUgbXVzdCBoYXZlIG1pc3Nl
ZCB5b3VyIG90aGVyIGNvbW1lbnQuDQoNCk9uIDgvMjMvMTcsIDk6MjEgUE0sICJYdXhpYW9odSIg
PHh1eGlhb2h1QGh1YXdlaS5jb20+IHdyb3RlOg0KDQo+DQo+DQo+PiAtLS0tLemCruS7tuWOn+S7
ti0tLS0tDQo+PiDlj5Hku7bkuro6IEFjZWUgTGluZGVtIChhY2VlKSBbbWFpbHRvOmFjZWVAY2lz
Y28uY29tXQ0KPj4g5Y+R6YCB5pe26Ze0OiAyMDE35bm0OOaciDIy5pelIDI6NDUNCj4+IOaUtuS7
tuS6ujogUGV0ZSBSZXNuaWNrDQo+PiDmioTpgIE6IGdlbi1hcnRAaWV0Zi5vcmc7IG9zcGZAaWV0
Zi5vcmc7DQo+PiBkcmFmdC1pZXRmLW9zcGYtZW5jYXBzdWxhdGlvbi1jYXAuYWxsQGlldGYub3Jn
OyBpZXRmQGlldGYub3JnDQo+PiDkuLvpopg6IFJlOiBHZW5hcnQgbGFzdCBjYWxsIHJldmlldyBv
ZiBkcmFmdC1pZXRmLW9zcGYtZW5jYXBzdWxhdGlvbi1jYXAtMDYNCj4+IA0KPj4gDQo+PiANCj4+
IE9uIDgvMjEvMTcsIDEyOjEyIFBNLCAiUGV0ZSBSZXNuaWNrIiA8cHJlc25pY2tAcXRpLnF1YWxj
b21tLmNvbT4gd3JvdGU6DQo+PiANCj4+ID5PbiAyMSBBdWcgMjAxNywgYXQgMTA6NTgsIEFjZWUg
TGluZGVtIChhY2VlKSB3cm90ZToNCj4+ID4NCj4+ID4+IEhpIFBldGUsDQo+PiA+Pg0KPj4gPj4g
T24gOC8yMS8xNywgMTE6NDAgQU0sICJQZXRlIFJlc25pY2siIDxwcmVzbmlja0BxdGkucXVhbGNv
bW0uY29tPg0KPj4gPj4gd3JvdGU6DQo+PiA+Pg0KPj4gPj4+IFJldmlld2VyOiBQZXRlIFJlc25p
Y2sNCj4+ID4+PiBSZXZpZXcgcmVzdWx0OiBBbG1vc3QgUmVhZHkNCj4+ID4+Pg0KPj4gPj4+IEkg
YW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5l
cmFsIEFyZWENCj4+ID4+PiBSZXZpZXcgVGVhbSAoR2VuLUFSVCkgcmV2aWV3cyBhbGwgSUVURiBk
b2N1bWVudHMgYmVpbmcgcHJvY2Vzc2VkIGJ5DQo+PiA+Pj4gdGhlIElFU0cgZm9yIHRoZSBJRVRG
IENoYWlyLiAgUGxlYXNlIHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1c3QgbGlrZQ0KPj4gPj4+IGFu
eSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQo+PiA+Pj4NCj4+ID4+PiBGb3IgbW9yZSBpbmZv
cm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0DQo+PiA+Pj4NCj4+ID4+PiA8aHR0cHM6Ly90
cmFjLmlldGYub3JnL3RyYWMvZ2VuL3dpa2kvR2VuQXJ0ZmFxPi4NCj4+ID4+Pg0KPj4gPj4+IERv
Y3VtZW50OiBkcmFmdC1pZXRmLW9zcGYtZW5jYXBzdWxhdGlvbi1jYXAtMDYNCj4+ID4+PiBSZXZp
ZXdlcjogUGV0ZSBSZXNuaWNrDQo+PiA+Pj4gUmV2aWV3IERhdGU6IDIwMTctMDgtMjENCj4+ID4+
PiBJRVRGIExDIEVuZCBEYXRlOiAyMDE3LTA4LTI4DQo+PiA+Pj4gSUVTRyBUZWxlY2hhdCBkYXRl
OiAyMDE3LTA4LTMxDQo+PiA+Pj4NCj4+ID4+PiBTdW1tYXJ5OiBBbG1vc3QgUmVhZHkNCj4+ID4+
Pg0KPj4gPj4+IFRoZSBjb250ZW50IG9mIHRoaXMgZG9jdW1lbnQgaXMgZmluZS4gSG93ZXZlciwg
SSB0aGluayB0aGUgSUFOQQ0KPj4gPj4+IHJlZ2lzdHJ5IHN0dWZmIGlzIG5vdCByZWFkeS4NCj4+
ID4+Pg0KPj4gPj4+IE1ham9yIGlzc3VlczoNCj4+ID4+Pg0KPj4gPj4+IEkgdGhpbmsgdGhlIHJl
Z2lzdHJhdGlvbnMgb3RoZXIgdGhhbiBmb3IgRW5kcG9pbnQgYW5kIENvbG9yIGFyZQ0KPj4gPj4+
IGluY29ycmVjdCBhbmQgc2hvdWxkIG5vdCBiZSBpbiB0aGlzIGRvY3VtZW50LiBDZXJ0YWlubHkg
dGhlDQo+PiA+Pj4gIlJlZmVyZW5jZSIgZmllbGQgZm9yIDEsIDIsIDUsIDYsIGFuZCA3IHNob3Vs
ZCBub3QgYmUgIlRoaXMNCj4+ID4+PiBkb2N1bWVudCIsIGdpdmVuIHRoYXQgdGhlIHN5bnRheCBh
bmQgc2VtYW50aWNzIGZvciB0aGVzZSB2YWx1ZXMgYXJlDQo+PiA+Pj4gZGVmaW5lZCBpbiBvdGhl
ciBkb2N1bWVudHMuDQo+PiA+Pg0KPj4gPj4gVGhlIGF1dGhvcnMgY2FuIGZpeCB0aGVzZS4NCj4+
ID4NCj4+ID5Gb3IgMSwgMiwgNiwgYW5kIDcsIHRoYXQncyBlYXN5OyB0aGUgZHJhZnRzIGRlZmlu
aW5nIHRoZSB2YWx1ZXMgY2FuIGRvDQo+PiA+dGhlIHJlZ2lzdHJhdGlvbnMuIEZvciA1LCB0aGUg
cmVmZXJlbmNlIHdvdWxkIGJlIHRvIGFuIGV4aXN0aW5nIFJGQw0KPj4gPnRoYXQgZG9lc24ndCBk
byB0aGUgcmVnaXN0cmF0aW9uLiBJJ20gbm90IHN1cmUgd2hhdCB0byBkbyBhYm91dCB0aGF0Ow0K
Pj4gPnBlcmhhcHMgcmVnaXN0ZXIgaXQgaGVyZSBhbmQgbWFrZSB0aGUgcmVmZXJlbmNlIGJvdGgg
NTY0MCBhbmQgdGhpcw0KPj5kb2N1bWVudC4NCj4+ID5Ib3dldmVyLCB3aGVuIHNvbWVvbmUgZ29l
cyB0byB1cGRhdGUgNTY0MCBzb21lIGRheSwgdGhleSdyZSBnb2luZyB0bw0KPj4gPmhhdmUgdG8g
cHV0IGludG8gdGhlIElBTkEgY29uc2lkZXJhdGlvbnMgdG8gdXBkYXRlIGJvdGggdGhlIE9TUEYg
YW5kDQo+PiA+QkdQIHJlZ2lzdHJpZXMuIEknbSBub3Qgc3VyZSBob3cgdG8ga2VlcCB0cmFjayBv
ZiB0aGF0LiBQZXJoYXBzIHNheWluZw0KPj4gPnRoYXQgdGhpcyBkb2N1bWVudCAiVXBkYXRlczog
NTY0MCI/IFRoYXQgZG9lc24ndCBzZWVtIGdyZWF0IGVpdGhlci4NCg0KQWN0dWFsbHksIHRoaXMg
ZG9jdW1lbnQgZG9lcyBhc3NpZ24gdGhlc2UgY29kZSBwb2ludHMgaW4gdGhlIHJlZ2lzdHJ5IHNv
DQrigJxUaGlzIGRvY3VtZW504oCdIGlzIGFwcHJvcHJpYXRlLiBUaGUgdmFsdWUgcG9ydGlvbiBv
ZiB0aGVzZSBUTFZzIGp1c3QNCmhhcHBlbmVkIHRvIGJlIGRlc2NyaWJlZCB2aWEgYSByZWZlcmVu
Y2UgcmF0aGVyIHRoYW4gdGV4dC4NCg0KVGhhbmtzLA0KQWNlZSANCg0KDQoNCg0KPj4gPg0KPj4g
Pj4+IEkgYWxzbyB0aGluayB0aGF0IGhhdmluZyB0aGluZ3MgaW4NCj4+ID4+PiB0aGlzIHJlZ2lz
dHJ5IHdoaWNoIGFyZSBhbHNvIHVzZWQgYnkgdGhlIEJHUCByZWdpc3RyeSBpcyBhc2tpbmcgZm9y
DQo+PiA+Pj4gdHJvdWJsZToNCj4+ID4+PiBZb3Ugd291bGRuJ3Qgd2FudCB0aGUgcmVmZXJlbmNl
cyBmb3IgdGhlIHR3byByZWdpc3RyaWVzIHRvIGdldCBvdXQNCj4+ID4+PiBvZiBzeW5jLg0KPj4g
Pj4+IFRoaXMgc2VlbXMgbGlrZSBhIG1lc3MgdG8gbWUuIFdvdWxkIGl0IGJlIHBvc3NpYmxlIGZv
ciBJQU5BIHRvDQo+PiA+Pj4gc2ltcGx5IHJlbmFtZSB0aGUgIkJHUCBUdW5uZWwgRW5jYXBzdWxh
dGlvbiBBdHRyaWJ1dGUgU3ViLVRMVnMiDQo+PiA+Pj4gcmVnaXN0cnkgdG8gIkJHUCBhbmQgT1NQ
RiBUdW5uZWwgRW5jYXBzdWxhdGlvbiBBdHRyaWJ1dGUgU3ViLVRMVnMiLA0KPj4gPj4+IGFuZCBz
aGFyZSB0aGUgcmVnaXN0cnkgYmV0d2VlbiB0aGUgdHdvIHByb3RvY29scz8gVGhlbiBoYXZlIHRo
aXMNCj4+ID4+PiAoYW5kIG90aGVyKSBkb2N1bWVudChzKSBhZGQgdmFsdWVzIHRvIHRoYXQgcmVn
aXN0cnkuIFRoYXQgd2F5LCB0aGUNCj4+ID4+PiBkb2N1bWVudHMgdGhhdCBhY3R1YWxseSBkZWZp
bmUgdGhlIGNvZGVwb2ludHMgY2FuIGJlIHB1dCBpbnRvIHRoZQ0KPj4gPj4+IHJlZ2lzdHJ5Lg0K
Pj4gPj4NCj4+ID4+IFdl4oCZdmUgYWxyZWFkeSBoYWQgYSBwcm90cmFjdGVkIGRpc2N1c3Npb24g
b24gdGhlIElBTkEgcmVnaXN0cmllcy4gSXQNCj4+ID4+IGlzIG5vdCBwb3NzaWJsZSBhcyBCR1Ag
YWR2ZXJ0aXNlcyBzb21lIG9mIHRoZSBhdHRyaWJ1dGVzIGluIEJHUA0KPj4gPj4gY29tbXVuaXRp
ZXMgcmF0aGVyIHRoYW4gdHVubmVsIGF0dHJpYnV0ZXMgKGUuZy4sIGNvbG9yKS4NCj4+ID4NCj4+
ID5ZdWNrLiBJJ2xsIHRyeSBub3QgdG8gcHJvbG9uZyB0aGUgZGlzY3Vzc2lvbiBtdWNoIGZ1cnRo
ZXIsIGJ1dCBkaWQgeW91DQo+PiA+Y29uc2lkZXIgdGhlIHBvc3NpYmlsaXR5IG9mIGhhdmluZyBz
b21lIG9mIHRoZSBhdHRyaWJ1dGVzIGFwcGVhciB0d2ljZSwNCj4+ID53aXRoIG9uZSBzYXlpbmcg
IkZvciBCR1AgY29tbXVuaXRpZXMgb25seSIgYW5kIHRoZSBvdGhlciBzYXlpbmcsICJGb3INCj4+
ID5PU1BGIHR1bm5lbHMgb25seSI/IFdoYXQgYSBsb3ZlbHkgbWVzcy4gOi0oDQo+PiANCj4+IFRo
ZSBjbGVhbmVzdCBzb2x1dGlvbiBpcyBmb3IgQkdQIGFuZCBPU1BGIHRvIGhhdmUgdGhlaXIgb3du
IHJlZ2lzdHJpZXMuDQo+PiBUcnlpbmcgdG8gcmV0cm9maXQgdGhlIGV4aXN0aW5nIEJHUCByZWdp
c3RyeSB0byBzYXRpc2Z5IE9TUEYNCj4+YWR2ZXJ0aXNlbWVudA0KPj4gcmVxdWlyZW1lbnRzIGlz
IG5vdCBmZWFzaWJsZS4NCj4NCj5GdWxseSBhZ3JlZS4NCj4NCj5CZXN0IHJlZ2FyZHMsDQo+WGlh
b2h1DQo+DQo+PiBUaGFua3MsDQo+PiBBY2VlDQo+PiANCj4+IA0KPj4gDQo+PiA+DQo+PiA+PiBU
aGFua3MsDQo+PiA+PiBBY2VlDQo+PiA+DQo+PiA+Q2hlZXJzLA0KPj4gPg0KPj4gPnByDQo+PiA+
DQo+PiA+Pj4gTWlub3IgaXNzdWVzOg0KPj4gPj4+DQo+PiA+Pj4gTm9uZS4NCj4+ID4+Pg0KPj4g
Pj4+IE5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOg0KPj4gPj4+DQo+PiA+Pj4gSW4gc2VjdGlvbiA3
LjEsIHBsZWFzZSBhZGQ6DQo+PiA+Pj4NCj4+ID4+PiAgIFtSRkMgRWRpdG9yOiBQbGVhc2UgcmVw
bGFjZSAiVEJEMSIgaW4gc2VjdGlvbiAzIHdpdGggdGhlIHJlZ2lzdHJ5DQo+PiA+Pj4gdmFsdWUN
Cj4+ID4+PiAgIGFsbG9jYXRlZCBieSBJQU5BLCBhbmQgcmVtb3ZlIHRoaXMgbm90ZV0uDQo+PiA+
Pj4NCj4+ID4+PiBUaGF0IHdpbGwgc2F2ZSB0aGVtIGZyb20gaHVudGluZy4NCj4+ID4+Pg0KPj4g
Pg0KPj4gPg0KPj4gPi0tDQo+PiA+UGV0ZSBSZXNuaWNrIDxodHRwOi8vd3d3LnF1YWxjb21tLmNv
bS9+cHJlc25pY2svPg0KPj4gPlF1YWxjb21tIFRlY2hub2xvZ2llcywgSW5jLiAtICsxICg4NTgp
NjUxLTQ0NzgNCj4NCg0K


From nobody Thu Aug 24 09:48:54 2017
Return-Path: <bew@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 528FE1321E6; Thu, 24 Aug 2017 09:48:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level: 
X-Spam-Status: No, score=-14.52 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id snEwJxGAH0UH; Thu, 24 Aug 2017 09:48:49 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F1511320DC; Thu, 24 Aug 2017 09:48:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=23668; q=dns/txt; s=iport; t=1503593329; x=1504802929; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=BERowRZUQNpkCHnjy9j3ZLnmRKUygJmU5eJ59Bj8LTY=; b=VYpqSA2QB2meyqaZay+c4daSgYh1mQF179WjkKHsymOPT758A2aRZAuM ou7vedVDtEdcrP5g35QVzLbEWRaMIUrPgb0EGR1re8mLM10FDX9S1XGTx UOZnNrragDBAk0AloNZNO5tKqAAlOIE+KFtDsipjQY0P4C5yc3ioI62Lw 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BjAQDlAZ9Z/4UNJK1TBwMaAQEBAQIBA?= =?us-ascii?q?QEBCAEBAQGCb2tkgRUHgy1Dih2QFoFOiFuIL4U9DoIELIFggzsCGoQ2PxgBAgE?= =?us-ascii?q?BAQEBAQFrKIUZBgwXVhACAQYCPwMCAgIfERQRAgQOBYlNTAMVEJEenWaCJ4c4D?= =?us-ascii?q?YQRAQEBAQEBAQEBAQEBAQEBAQEBAQEBGAWDKoICgy8rC4FlgQyCV4FpAQcLAQk?= =?us-ascii?q?tChURgkwwgjEFoB08AodUh3mEdgyCBoVjim+JcIJRiW4BHzh/C3cVWwGFAwEcg?= =?us-ascii?q?Wd2iGEGAQgXgQyBDwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.41,422,1498521600";  d="scan'208,217";a="286941280"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 24 Aug 2017 16:48:48 +0000
Received: from XCH-RTP-003.cisco.com (xch-rtp-003.cisco.com [64.101.220.143]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id v7OGmlqC005783 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 24 Aug 2017 16:48:47 GMT
Received: from xch-rtp-001.cisco.com (64.101.220.141) by XCH-RTP-003.cisco.com (64.101.220.143) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 24 Aug 2017 12:48:46 -0400
Received: from xch-rtp-001.cisco.com ([64.101.220.141]) by XCH-RTP-001.cisco.com ([64.101.220.141]) with mapi id 15.00.1210.000; Thu, 24 Aug 2017 12:48:46 -0400
From: "Brian Weis (bew)" <bew@cisco.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
CC: "secdir@ietf.org" <secdir@ietf.org>, "draft-weis-gdoi-rekey-ack.all@ietf.org" <draft-weis-gdoi-rekey-ack.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Secdir last call review of draft-weis-gdoi-rekey-ack-05
Thread-Topic: Secdir last call review of draft-weis-gdoi-rekey-ack-05
Thread-Index: AQHTDgJglUgJl63bZkSkx0TnTx/5x6KUGN4A
Date: Thu, 24 Aug 2017 16:48:46 +0000
Message-ID: <E61F05DB-EEB0-4140-A2D4-DB11163C4E13@cisco.com>
References: <150194814585.18635.3104789196001873381@ietfa.amsl.com>
In-Reply-To: <150194814585.18635.3104789196001873381@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.19.191.173]
Content-Type: multipart/alternative; boundary="_000_E61F05DBEEB04140A2D4DB11163C4E13ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/20yEjOXH5J1A-dpzEnJDLuMgl7s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Aug 2017 16:48:52 -0000

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

SGkgWWFyb24sDQoNClRoYW5rcyBmb3IgdGhlIHJldmlldy4gV2XigJl2ZSBhZGRlZCBzb21lIGNs
YXJpZmljYXRpb24gYmVsb3csIGFuZCBtYWRlIHNvbWUgY2hhbmdlcyBpbiAtMDYgdG8gYWRkcmVz
cyB5b3VyIGNvbW1lbnRzLiBQbGVhc2UgbGV0IHVzIGtub3cgaWYgd2UgZGlkIG5vdCBhZGRyZXNz
IHRoZW0gc2F0aXNmYWN0b3JpbHkuDQoNCk9uIEF1ZyA1LCAyMDE3LCBhdCA4OjQ5IEFNLCBZYXJv
biBTaGVmZmVyIDx5YXJvbmYuaWV0ZkBnbWFpbC5jb208bWFpbHRvOnlhcm9uZi5pZXRmQGdtYWls
LmNvbT4+IHdyb3RlOg0KDQpSZXZpZXdlcjogWWFyb24gU2hlZmZlcg0KUmV2aWV3IHJlc3VsdDog
SGFzIElzc3Vlcw0KDQpTdW1tYXJ5OiB0aGlzIHJldmlld2VyIGlzIG5vdCBjbGVhciBhYm91dCB0
aGUgdmFsdWUgb2YgdGhlIHB1c2gtYWNrIChjb21wYXJlZA0KdG8gYSBwdWxsKSBhbmQgYWJvdXQg
dGhlIHN0cmF0ZWd5IHRoYXQgd2FzIGNob3Nlbi4NCg0KSW4gYSBncm91cCBrZXkgbWFuYWdlbWVu
dCBzeXN0ZW0gZWl0aGVyIGEg4oCccHVsbOKAnSAodHJpZ2dlcmVkIGJ5IGEgZ3JvdXAgbWVtYmVy
KSBvciBhIOKAnHB1c2jigJ0gKGJ5IHRoZSBrZXkgc2VydmVyKSIgY291bGQgYmUgdXNlZCB0byBw
cm92aWRlIHVwZGF0ZXMgdG8gdGhlIGdyb3VwLiBIb3dldmVyLCBhIOKAnHB1bGzigJ0gYnkgdGhl
IGdyb3VwIG1lbWJlciBpbXBsaWVzIGEgcG9sbGluZyBtZXRob2QsIHdoaWNoIGhhcyB0aGUgZGVm
aWNpZW5jeSB0aGF0IHRoZSBrZXkgc2VydmVyIGNhbm5vdCBjYXVzZSBhIHBvbGljeSByZXBsYWNl
bWVudCBhbnkgc29vbmVyIHRoYW4gdGhlIHBvbGxpbmcgbWV0aG9kIGJ5IHRoZSBncm91cCBtZW1i
ZXJzLiBBbHNvIOKAnHBvbGxpbmfigJ0gY2FuIGNhdXNlIGFkZGl0aW9uYWwgdW5uZWNlc3Nhcnkg
dHJhZmZpYy4gU28gaXMgaXMgYmV0dGVyIGZvciBhbnkgdXBkYXRlIG9uIHRoZSBncm91cCBwb2xp
Y3kgb3IgcmVuZXdhbCBvZiBncm91cCBrZXlzIHRvIGJlIGRpc3RyaWJ1dGVkIGJ5IHRoZSBHQ0tT
IHVzaW5nIGEgUFVTSCBtZXNzYWdlLiBUaGUgQUNLLW1lc3NhZ2UgaXMgdXNlZCB0byBvZmZlciBh
IGZlZWRiYWNrIG1lY2hhbmlzbSB0byBhIHBvbGljeSB1cGRhdGUgZm9yIHRoZSBQVVNIIGV4Y2hh
bmdlLg0KKiAiRm9yIGV4YW1wbGUsIGEgR0NLUyBwb2xpY3kgY2FuIHVzZSB0aGUgYWNrbm93bGVk
Z2VtZW50cyB0byBkZXRlcm1pbmUgWy4uLl0NCndoaWNoIG1lbWJlcnMgbWF5IG5vIGxvbmdlciBi
ZSBtZW1iZXJzIG9mIHRoZSBncm91cC4iIFRoaXMgc2VudGVuY2UgaXMgdmVyeQ0KY29uZnVzaW5n
OiB3aGVuIGFyZSBtZW1iZXJzIG5vdCBtZW1iZXJzPw0KDQpXZeKAmXZlIHJld29yZGVkIHRoaXMg
dGV4dC4gSXTigJlzIHRyeWluZyB0byBjb252ZXkgdGhhdCBhIG1pc3NpbmcgQUNLIG1lc3NhZ2Ug
KG9yIGEgY2VydGFpbiBudW1iZXIgb2YgaXQpIGNhbiBiZSB1c2VkIHRvIGlkZW50aWZ5IHRoYXQg
YSBncm91cCBtZW1iZXIgaXMgbm8gbG9uZ2VyIHJlY2VpdmluZyBncm91cCB0cmFmZmljLCBhbmQg
aXMgbm93IG1heSBiZSBjb25zaWRlcmVkIGFuIGV4LWdyb3VwIG1lbWJlci4gRm9yIGV4YW1wbGUs
IGl0IGNvdWxkIGJlIGEgbXVsdGljYXN0IHJlY2VpdmVyIHRoYXQgaXMgbm8gbG9uZ2VyIGludGVy
ZXN0ZWQgaW4gYmVpbmcgYSByZWNlaXZlciBmb3IgdGhlIGdyb3VwLiBCdXQgaXQgY291bGQgYWxz
byBiZSB0aGF0IGEgbmV0d29yayBldmVudCBoYXMgY2F1c2VkIGl0IHRvIGJlIHVuYXZhaWxhYmxl
IGZvciBhIHN1ZmZpY2llbnQgbGVuZ3RoIG9mIHRpbWUgc3VjaCB0aGF0IGl0IGRvZXNu4oCZdCBo
YXZlIGN1cnJlbnQga2V5aW5nIG1hdGVyaWFsIGFuZCB0aGVyZWZvcmUgY2Fu4oCZdCBiZSBjb25z
aWRlcmVkIGEgY3VycmVudCBncm91cCBtZW1iZXIuIFRoZXJlIGlzIG5vIHJlbGlhYmxlIOKAnEni
gJltIGxlYXZpbmcgdGhlIGdyb3Vw4oCdIG1lc3NhZ2UgZmxvdywgYW5kIG9mIGNvdXJzZSBpbiBt
eSBzZWNvbmQgZXhhbXBsZSBubyBzdWNoIG1lc3NhZ2VzIHdvdWxkIGhhdmUgYmVlbiBpbnRlbmRl
ZCBieSB0aGUgZ3JvdXAgbWVtYmVyLg0KDQoqIFRoZSBuZXcgcHJvdG9jb2wgY2FwYWJpbGl0eSBp
cyBkZWZpbmVkIGFzIG9wdGlvbmFsLCBidXQgcmVhbGx5IGlzbid0LiAiQSBHTQ0KcmVjZWl2aW5n
IHRoZSBLRUtfQUNLX1JFUVVFU1RFRCBhdHRyaWJ1dGUgY2FuIGNob29zZSB0byBpZ25vcmUgaXQs
IHRodXMNCmFwcGVhcmluZyBhcyBpZiBpdCBkb2VzIG5vdCBzdXBwb3J0IHRoZSBLRUtfQUNLX1JF
UVVFU1RFRCBhdHRyaWJ1dGUuIEhvd2V2ZXIsDQpHQ0tTIHBvbGljeSBtYXkgY29uc2lkZXIgYSBu
b24tcmVzcG9uc2l2ZSBHTSB0byBubyBsb25nZXIgZGVzaXJlIHRvIGJlIGEgbWVtYmVyDQpvZiB0
aGUgZ3JvdXAuIiBTbyBpZiB5b3Ugd2FudCB0byBwbGF5IHRoZSBnYW1lLCB5b3UgTVVTVCBzdXBw
b3J0IHRoZSBuZXcNCmF0dHJpYnV0ZS4NCg0KUG9pbnQgdGFrZW4uIFdl4oCZdmUgY2hhbmdlZCB0
aGUgdGV4dCB0byByZWZsZWN0IHRoaXMuDQoNCiogSSdtIHB1enpsZWQgYXQgdGhlIG92ZXJhbGwg
cHJvdG9jb2wuIEJlaW5nIGFibGUgdG8gc2VuZCBBQ0tzIGlzIGEgR00gc29mdHdhcmUNCmNhcGFi
aWxpdHkuIFdoeSBub3QgaGF2ZSB0aGUgR00gYW5ub3VuY2UgdGhpcyBjYXBhYmlsaXR5IHdoZW4g
aXQgaW5pdGlhbGx5DQpyZWdpc3RlcnMgdG8gdGhlIEdDS1M/IFRoZW4gdGhlIEdDS1Mgd291bGQg
a25vdyB3aGF0IHRvIGV4cGVjdCwgd2hlcmVhcyB3aXRoDQp0aGUgY3VycmVudCBwcm90b2NvbCBp
dCBpcyBsZWZ0IHdhaXRpbmcgZm9yIGFuIEFDSyB0aGF0IG1heSBuZXZlciBjb21lLCBlaXRoZXIN
CmJlY2F1c2UgdGhlIEdNIGlzIGRlYWQgb3IgYmVjYXVzZSBpdCBqdXN0IGRvZXNuJ3QgZmVlbCBs
aWtlIHJlc3BvbmRpbmcuIEFkZCB0aGUNCmxvbmcgd2FpdHMgKGppdHRlciBvZiAiYSBmZXcgc2Vj
b25kcyIgYW5kIHBvdGVudGlhbCByZXRyaWVzKSwgYW5kIHRoaXMgbG9va3MNCmxpa2UgYSBmYXIg
ZnJvbSBvcHRpbWFsIG1hbmFnZW1lbnQgZXhwZXJpZW5jZS4NCg0KSW5kZWVkIGEgR00gY291bGQg
YW5ub3VuY2UgaXRzIGNhcGFiaWxpdHksIGJ1dCB3aGV0aGVyIG9yIG5vdCBBQ0tzIGFyZSBkZXNp
cmVkIGlzIGEgY29tcG9uZW50IG9mIHRoZSBncm91cCBwb2xpY3kuIEluIHRoZSBjb250ZXh0IG9m
IEdET0kgdGhlIEdDS1MgaXMgdGhlIGVudGl0eSB0aGF0IGRlZmluZXMgdGhlIGdyb3VwIHBvbGlj
eS4gVGhlcmUgY2FuIGJlIGdyb3VwcyB3aGVyZSB0aGUgQUNLIGlzIHVzZWQsIHdoZXJlYXMgb3Ro
ZXJzIGRvIG5vdC4gIFRoZSBjYXBhYmlsaXRpZXMgYW5ub3VuY2VtZW50IHlvdSBzdWdnZXN0IGNv
dWxkIGNlcnRhaW5seSBoZWxwIHRoZSBLUyB0byBrbm93IHdoZXRoZXIgb3Igbm90IHRvIGV4cGVj
dCB0aGUgQUNLIGZyb20gYSBwYXJ0aWN1bGFyIEdNLCBidXQgdGhlIGZvY3VzIG9mIHRoaXMgSS1E
IGlzIG9uIHRoZSB0aGUgZGVjbGFyYXRpb24gb2YgdGhlIHJlcXVlc3QgZm9yIEFDS3MgYnkgdGhl
IEdDS1MgYW5kIHRoZSBmb3JtYXQgb2YgdGhlIEFDSy4NCg0KKiAyLjI6ICJUaGlzIGlzIGEgcHJp
dmF0ZSBrZXkiIC0gdG8gYXZvaWQgY29uZnVzaW9uLCBJIHN1Z2dlc3Q6ICJUaGlzIGlzIGENCnNl
Y3JldCBzeW1tZXRyaWMga2V5IiAoaWYgdGhpcyBpcyBpbmRlZWQgdGhlIGNhc2UpLiBPYnZpb3Vz
bHkgdXNpbmcgdGhlIHNhbWUNCmtleSBmb3IgZW5jcnlwdGlvbiBhbmQgZm9yIEhNQUMgaXMgbm90
IGEgYmVzdCBwcmFjdGljZS4NCg0KV2XigJl2ZSBtYWRlIHRoaXMgY2hhbmdlLg0KDQoqIFNlYy4g
NTogQUNLIG1lc3NhZ2VzIGNhbiBhbHNvIGJlIGR1cGxpY2F0ZWQgaW4gdGhlIG5ldHdvcmsuIEkg
c3VnZ2VzdCB0byBhZGQNCmEgc2VudGVuY2UgZGVzY3JpYmluZyB3aGF0IHRoZSBHQ0tTIHNob3Vs
ZCBkbyBpbiB0aGlzIGNhc2UuDQoNClRoZSBTZWN1cml0eSBDb25zaWRlcmF0aW9ucyAoc2VjdGlv
biA3LjMpIGRlc2NyaWJlcyBhIG1ldGhvZCBmb3IgdGhlIEdDS1MgdG8gZGV0ZWN0IHJlcGxheXMu
IFRoaXMgaXMgYXJndWFibHkgYmV0dGVyIHBsYWNlZCBpbiB0aGlzIHNlY3Rpb24sIHNvIHdl4oCZ
dmUgbW92ZWQgaXQgaGVyZS4uDQoNCiogU2VjLiA2OiBJIGFtIGNvbmZ1c2VkIGFib3V0IHRoZSBu
b3Rpb24gb2YgImppdHRlciIgaGVyZS4gSWYgdGhlIFBVU0ggbWVzc2FnZXMNCmFyZSBzZW50IGFz
IG11bHRpY2FzdCAodGhlIHJlY29tbWVuZGVkIGFsdGVybmF0aXZlIEFGQUlDVCksIEknbSBub3Qg
c3VyZSBhYm91dA0KdGhlIGJlbmVmaXQgb2YgdXNpbmcgbXVsdGljYXN0LCBnaXZlbiB0aGF0IGVh
Y2ggcmVjaXBpZW50IHJlc3BvbmRzIHdpdGggYQ0KdW5pY2FzdCBBQ0suIEFuZCBpZiB0aGUgUFVT
SCBpcyB1bmljYXN0LCB0aGVyZSBzaG91bGQgYmUgbm8gcmVhc29uIGZvciBhIGppdHRlcg0KYXMg
dGhlIHNlbmRlciBjYW4gdGhyb3R0bGUgdGhlIFBVU0ggbWVzc2FnZXMgYXMgbmVjZXNzYXJ5Lg0K
DQpUaGUgY29uY2VwdCBvZiDigJxqaXR0ZXLigJ0gaXMgbW9zdCB2YWx1YWJsZSBmb3IgcmVzcG9u
c2VzIHRvIGEgbXVsdGljYXN0IFBVU0ggbWVzc2FnZS4gVGhlIHVzZSBvZiBhIG11bHRpY2FzdCBQ
VVNIIG1lc3NhZ2UgbG93ZXIgcHJvY2Vzc2luZyBvbiB0aGUgR0NLUy4gU2luY2UgZWFjaCBHTSBj
YW4gZSBnaXZlbiB0aGUgZXhhY3Qgc2FtZSBwb2xpY3ksIHRoZXJl4oCZcyBubyBjYWxsIHRvIHNl
bmQgaXQgb3V0IGFzIGEgdW5pY2FzdCBtZXNzYWdlLiBUaGUgaml0dGVyIGhlbHBzIHNwcmVhZCBv
dXQgdGhlIHJlcGxpZXMgYSBiaXQgdG8gYXZvaWQgaW51bmRhdGluZyB0aGUgR0NLUy4NCg0KKiBN
b3Jlb3ZlciwgZXZlcnl0aGluZyB3b3VsZCBiZSBtdWNoIG1vcmUgcHJlZGljdGFibGUgaWYgdGhl
IEdDS1MgY291bGQNCmluZGljYXRlIGlmIGEgaml0dGVyIGlzIGV4cGVjdGVkIGFuZCBob3cgbXVj
aCBvZiBhIGppdHRlciAoYmFzZWQgb24gc2l6ZSBvZiB0aGUNCmdyb3VwLCBuZXR3b3JrIHRocm91
Z2hwdXQsIGFuZCBxdWV1ZSBsZW5ndGgpLiBTcGVjaWZpY2FsbHksIHRoaXMgd291bGQgYWxsb3cN
CnRoZSBHQ0tTIHRvIHRlbGwgaG93IGxvbmcgaXQgc2hvdWxkIHdhaXQgZm9yIGFuIEFDSy4NCg0K
VGhpcyB3b3VsZCBiZSBzb21ld2hhdCB1c2VmdWwsIGJ1dCBpbiBwcmFjdGljZSBtaWdodCBub3Qg
aGVscCB0aGUgR0NLUyBhcyBtdWNoIGFzIGl0IHNlZW1zLiBUaGUgaml0dGVyIHZhbHVlIHByb3Zp
ZGVkIHdvdWxkIGFsc28gYmUgZGVwZW5kZW50IG9uIHNldmVyYWwgbmV0d29yayBwYXJhbWV0ZXJz
IHRoYXQgYXJlbuKAmXQgdW5kZXIgdGhlIGNvbnRyb2wgb2YgdGhlIEdDS1Mgb3IgdGhlIEdNLiBF
dmVuIHdoZW4gdGhlIEdNIGRvZXMgbm90IGFkZCBhbnkgaml0dGVyIHRvIHRoZSBBQ0ssIHRoZSB1
bmRlcmx5aW5nIG5ldHdvcmsgbWF5IGRlbGF5IHRoZSBQVVNIIGFuZC9vciBmb3IgdGhlIEFDSy4g
QW5kIGFzIHN0YXRlZCBpbiBTZWN0aW9uIDYsIHRoZSBHQ0tTIG1heSBiZSBjb25maWd1cmVkIHdp
dGggYWRkaXRpb25hbCBwb2xpY3kgYWN0aW9ucyBsaWtlIHJldHJhbnNtaXNzaW9ucyB0byBvdmVy
Y29tZSBsb3N0IEFDS3MuIEFsdG9nZXRoZXIgdG8gYWRkIGppdHRlciB0byB0aGUgQUNLIGlzIG5v
dCBhIG11c3QsIGl0IGlzIGEgd2F5IHRvIGhlbHAgdGhlIEdDS1MgZGVhbCB3aXRoIGEgaHVnZSBu
dW1iZXIgb2YgR01zLiBJbiBwcmFjdGljZSwgd2XigJl2ZSBmb3VuZCB0aGF0IGhhdmluZyB0aGUg
R01zIGNob29zZSB0aGUgaml0dGVyIGhhcyB3b3JrZWQgd2VsbCwgZXZlbiB3aGVuIHRoZSBHTXMg
YXJlIGRpZmZlcmVudCBpbXBsZW1lbnRhdGlvbnMuDQoNCiogQ3J5cHRvZ3JhcGhpYyBhZ2lsaXR5
OiB0aGlzIGRvY3VtZW50IHNwZWNpZmllcyBvbmx5IG9uZSBhbGdvcml0aG0gZm9yIHRoZQ0KSEFT
SCB2YWx1ZSwgYW5kIHNheXMgdGhhdCBpZiBhIG5ldyBhbGdvcml0aG0gaXMgbmVlZGVkLCB0aGVy
ZSB3aWxsIGJlIGEgbmV3DQpLRUtfQUNLX1JFUVVFU1RFRCBwYXlsb2FkIGRlZmluZWQuIEhvd2V2
ZXIgdG8gbWFrZSBzdXJlIHRoYXQgdGhpcyByZWFsbHkNCiJ3b3JrcyIsIHdlIG5lZWQgdG8gZGVm
aW5lIHdoZXRoZXIgbXVsdGlwbGUgc3VjaCBwYXlsb2FkcyBjYW4gYmUgc2VudA0Kc2ltdWx0YW5l
b3VzbHkgKGlmIGUuZy4gc29tZSBHTXMgc3RpbGwgc3VwcG9ydCB0aGUgb2xkIGFsZ29yaXRobSkg
YW5kIHdoYXQncw0KdGhlIGV4cGVjdGVkIGJlaGF2aW9yLiBJIHdvdWxkIHN1Z2dlc3QgdG8gZGVm
aW5lIGFuIGFkZGl0aW9uYWwgU0hBLTUxMiBwYXlsb2FkDQpqdXN0IHRvIG1ha2UgZm9yIGEgY29u
Y3JldGUgZXhhbXBsZS4NCg0KVGhpcyBpcyBhIGdvb2Qgc3VnZ2VzdGlvbi4gV2XigJl2ZSBhZGRl
ZCBTSEEtNTEyIHZlcnNpb25zIG9mIHRoZSBleGlzdGluZyBLRUtfQUNLX1JFUVVFU1RFRCB2YWx1
ZXMuDQoNClNlZSA8aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXdlaXMtZ2RvaS1y
ZWtleS1hY2stMDY+DQoNClRoYW5rcywNCkJyaWFuDQoNCi0tDQpCcmlhbiBXZWlzDQpTZWN1cml0
eSwgQ1NHLCBDaXNjbyBTeXN0ZW1zDQpUZWxlcGhvbmU6ICsxIDQwOCA1MjYgNDc5Ng0KRW1haWw6
IGJld0BjaXNjby5jb208bWFpbHRvOmJld0BjaXNjby5jb20+DQoNCg==

--_000_E61F05DBEEB04140A2D4DB11163C4E13ciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <AC7FDC1453578443847FD81FD536344E@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KSGkgWWFyb24sDQo8ZGl2IGNsYXNz
PSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5UaGFua3MgZm9yIHRoZSBy
ZXZpZXcuIFdl4oCZdmUgYWRkZWQgc29tZSBjbGFyaWZpY2F0aW9uIGJlbG93LCBhbmQgbWFkZSBz
b21lIGNoYW5nZXMgaW4gLTA2IHRvIGFkZHJlc3MgeW91ciBjb21tZW50cy4gUGxlYXNlIGxldCB1
cyBrbm93IGlmIHdlIGRpZCBub3QgYWRkcmVzcyB0aGVtIHNhdGlzZmFjdG9yaWx5LjwvZGl2Pg0K
PGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0i
Ij4NCjxkaXY+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9
IiI+T24gQXVnIDUsIDIwMTcsIGF0IDg6NDkgQU0sIFlhcm9uIFNoZWZmZXIgJmx0OzxhIGhyZWY9
Im1haWx0bzp5YXJvbmYuaWV0ZkBnbWFpbC5jb20iIGNsYXNzPSIiPnlhcm9uZi5pZXRmQGdtYWls
LmNvbTwvYT4mZ3Q7IHdyb3RlOjwvZGl2Pg0KPGJyIGNsYXNzPSJBcHBsZS1pbnRlcmNoYW5nZS1u
ZXdsaW5lIj4NCjxkaXYgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPlJldmlld2VyOiBZYXJvbiBT
aGVmZmVyPGJyIGNsYXNzPSIiPg0KUmV2aWV3IHJlc3VsdDogSGFzIElzc3VlczxiciBjbGFzcz0i
Ij4NCjxiciBjbGFzcz0iIj4NClN1bW1hcnk6IHRoaXMgcmV2aWV3ZXIgaXMgbm90IGNsZWFyIGFi
b3V0IHRoZSB2YWx1ZSBvZiB0aGUgcHVzaC1hY2sgKGNvbXBhcmVkPGJyIGNsYXNzPSIiPg0KdG8g
YSBwdWxsKSBhbmQgYWJvdXQgdGhlIHN0cmF0ZWd5IHRoYXQgd2FzIGNob3Nlbi48YnIgY2xhc3M9
IiI+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj48YnIgY2xhc3M9IiI+DQo8
L2Rpdj4NCkluIGEgZ3JvdXAga2V5IG1hbmFnZW1lbnQgc3lzdGVtIGVpdGhlciBhIOKAnHB1bGzi
gJ0gKHRyaWdnZXJlZCBieSBhIGdyb3VwIG1lbWJlcikgb3IgYSDigJxwdXNo4oCdIChieSB0aGUg
a2V5IHNlcnZlcikmcXVvdDsgY291bGQgYmUgdXNlZCB0byBwcm92aWRlIHVwZGF0ZXMgdG8gdGhl
IGdyb3VwLiBIb3dldmVyLCBhIOKAnHB1bGzigJ0gYnkgdGhlIGdyb3VwIG1lbWJlciBpbXBsaWVz
IGEgcG9sbGluZyBtZXRob2QsIHdoaWNoIGhhcyB0aGUgZGVmaWNpZW5jeSB0aGF0IHRoZQ0KIGtl
eSBzZXJ2ZXIgY2Fubm90IGNhdXNlIGEgcG9saWN5IHJlcGxhY2VtZW50IGFueSBzb29uZXIgdGhh
biB0aGUgcG9sbGluZyBtZXRob2QgYnkgdGhlIGdyb3VwIG1lbWJlcnMuIEFsc28g4oCccG9sbGlu
Z+KAnSBjYW4gY2F1c2UgYWRkaXRpb25hbCB1bm5lY2Vzc2FyeSB0cmFmZmljLiBTbyBpcyBpcyBi
ZXR0ZXIgZm9yIGFueSB1cGRhdGUgb24gdGhlIGdyb3VwIHBvbGljeSBvciByZW5ld2FsIG9mIGdy
b3VwIGtleXMgdG8gYmUgZGlzdHJpYnV0ZWQgYnkNCiB0aGUgR0NLUyB1c2luZyBhIFBVU0ggbWVz
c2FnZS4mbmJzcDtUaGUgQUNLLW1lc3NhZ2UgaXMgdXNlZCB0byBvZmZlciBhIGZlZWRiYWNrIG1l
Y2hhbmlzbSB0byBhIHBvbGljeSB1cGRhdGUgZm9yIHRoZSBQVVNIIGV4Y2hhbmdlLjxiciBjbGFz
cz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4N
CjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSIgc3R5bGU9InBhZ2U6IFdvcmRTZWN0aW9uMTsiPg0K
PGRpdiBjbGFzcz0iIiBzdHlsZT0iYm9yZGVyLXN0eWxlOiBub25lIG5vbmUgbm9uZSBzb2xpZDsg
Ym9yZGVyLWxlZnQtd2lkdGg6IDEuNXB0OyBib3JkZXItbGVmdC1jb2xvcjogYmx1ZTsgcGFkZGlu
ZzogMGNtIDBjbSAwY20gNHB0OyI+DQo8ZGl2IGNsYXNzPSIiIHN0eWxlPSJib3JkZXItc3R5bGU6
IG5vbmUgbm9uZSBub25lIHNvbGlkOyBib3JkZXItbGVmdC13aWR0aDogMS41cHQ7IGJvcmRlci1s
ZWZ0LWNvbG9yOiBibHVlOyBwYWRkaW5nOiAwY20gMGNtIDBjbSA0cHQ7Ij4NCjxkaXYgY2xhc3M9
IiI+DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOiAwY20gMGNtIDEycHQ7IGZvbnQtc2l6ZTog
MTJwdDsgZm9udC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nLCBzZXJpZjsiPg0KPGIgY2xhc3M9
IiI+PGkgY2xhc3M9IiI+PHNwYW4gbGFuZz0iRU4tVVMiIGNsYXNzPSIiIHN0eWxlPSJmb250LXNp
emU6IDExcHQ7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBjb2xvcjogcmdiKDMx
LCA3MywgMTI1KTsiPjxvOnAgY2xhc3M9IiI+PC9vOnA+PC9zcGFuPjwvaT48L2I+PC9wPg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rp
dj4NCjwvYmxvY2txdW90ZT4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGRp
diBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+KiAmcXVvdDtGb3IgZXhhbXBsZSwgYSBHQ0tTIHBv
bGljeSBjYW4gdXNlIHRoZSBhY2tub3dsZWRnZW1lbnRzIHRvIGRldGVybWluZSBbLi4uXTxiciBj
bGFzcz0iIj4NCndoaWNoIG1lbWJlcnMgbWF5IG5vIGxvbmdlciBiZSBtZW1iZXJzIG9mIHRoZSBn
cm91cC4mcXVvdDsgVGhpcyBzZW50ZW5jZSBpcyB2ZXJ5PGJyIGNsYXNzPSIiPg0KY29uZnVzaW5n
OiB3aGVuIGFyZSBtZW1iZXJzIG5vdCBtZW1iZXJzPzxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2PjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdj4NCjxk
aXYgY2xhc3M9IiI+V2XigJl2ZSByZXdvcmRlZCB0aGlzIHRleHQuIEl04oCZcyB0cnlpbmcgdG8g
Y29udmV5IHRoYXQgYSBtaXNzaW5nIEFDSyBtZXNzYWdlIChvciBhIGNlcnRhaW4gbnVtYmVyIG9m
IGl0KSBjYW4gYmUgdXNlZCB0byBpZGVudGlmeSB0aGF0IGEgZ3JvdXAgbWVtYmVyIGlzIG5vIGxv
bmdlciByZWNlaXZpbmcgZ3JvdXAgdHJhZmZpYywgYW5kIGlzIG5vdyBtYXkgYmUgY29uc2lkZXJl
ZCBhbiBleC1ncm91cCBtZW1iZXIuIEZvciBleGFtcGxlLA0KIGl0IGNvdWxkIGJlIGEgbXVsdGlj
YXN0IHJlY2VpdmVyIHRoYXQgaXMgbm8gbG9uZ2VyIGludGVyZXN0ZWQgaW4gYmVpbmcgYSByZWNl
aXZlciBmb3IgdGhlIGdyb3VwLiBCdXQgaXQgY291bGQgYWxzbyBiZSB0aGF0IGEgbmV0d29yayBl
dmVudCBoYXMgY2F1c2VkIGl0IHRvIGJlIHVuYXZhaWxhYmxlIGZvciBhIHN1ZmZpY2llbnQgbGVu
Z3RoIG9mIHRpbWUgc3VjaCB0aGF0IGl0IGRvZXNu4oCZdCBoYXZlIGN1cnJlbnQga2V5aW5nIG1h
dGVyaWFsIGFuZA0KIHRoZXJlZm9yZSBjYW7igJl0IGJlIGNvbnNpZGVyZWQgYSBjdXJyZW50IGdy
b3VwIG1lbWJlci4gVGhlcmUgaXMgbm8gcmVsaWFibGUg4oCcSeKAmW0gbGVhdmluZyB0aGUgZ3Jv
dXDigJ0gbWVzc2FnZSBmbG93LCBhbmQgb2YgY291cnNlIGluIG15IHNlY29uZCBleGFtcGxlIG5v
IHN1Y2ggbWVzc2FnZXMgd291bGQgaGF2ZSBiZWVuIGludGVuZGVkIGJ5IHRoZSBncm91cCBtZW1i
ZXIuPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPC9kaXY+DQo8
YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+DQo8ZGl2IGNs
YXNzPSIiPiogVGhlIG5ldyBwcm90b2NvbCBjYXBhYmlsaXR5IGlzIGRlZmluZWQgYXMgb3B0aW9u
YWwsIGJ1dCByZWFsbHkgaXNuJ3QuICZxdW90O0EgR008YnIgY2xhc3M9IiI+DQpyZWNlaXZpbmcg
dGhlIEtFS19BQ0tfUkVRVUVTVEVEIGF0dHJpYnV0ZSBjYW4gY2hvb3NlIHRvIGlnbm9yZSBpdCwg
dGh1czxiciBjbGFzcz0iIj4NCmFwcGVhcmluZyBhcyBpZiBpdCBkb2VzIG5vdCBzdXBwb3J0IHRo
ZSBLRUtfQUNLX1JFUVVFU1RFRCBhdHRyaWJ1dGUuIEhvd2V2ZXIsPGJyIGNsYXNzPSIiPg0KR0NL
UyBwb2xpY3kgbWF5IGNvbnNpZGVyIGEgbm9uLXJlc3BvbnNpdmUgR00gdG8gbm8gbG9uZ2VyIGRl
c2lyZSB0byBiZSBhIG1lbWJlcjxiciBjbGFzcz0iIj4NCm9mIHRoZSBncm91cC4mcXVvdDsgU28g
aWYgeW91IHdhbnQgdG8gcGxheSB0aGUgZ2FtZSwgeW91IE1VU1Qgc3VwcG9ydCB0aGUgbmV3PGJy
IGNsYXNzPSIiPg0KYXR0cmlidXRlLjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Js
b2NrcXVvdGU+DQo8ZGl2PjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdj5Qb2ludCB0YWtlbi4g
V2XigJl2ZSBjaGFuZ2VkIHRoZSB0ZXh0IHRvIHJlZmxlY3QgdGhpcy48L2Rpdj4NCjxkaXY+PGJy
IGNsYXNzPSIiPg0KPC9kaXY+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj4NCjxk
aXYgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPiogSSdtIHB1enpsZWQgYXQgdGhlIG92ZXJhbGwg
cHJvdG9jb2wuIEJlaW5nIGFibGUgdG8gc2VuZCBBQ0tzIGlzIGEgR00gc29mdHdhcmU8YnIgY2xh
c3M9IiI+DQpjYXBhYmlsaXR5LiBXaHkgbm90IGhhdmUgdGhlIEdNIGFubm91bmNlIHRoaXMgY2Fw
YWJpbGl0eSB3aGVuIGl0IGluaXRpYWxseTxiciBjbGFzcz0iIj4NCnJlZ2lzdGVycyB0byB0aGUg
R0NLUz8gVGhlbiB0aGUgR0NLUyB3b3VsZCBrbm93IHdoYXQgdG8gZXhwZWN0LCB3aGVyZWFzIHdp
dGg8YnIgY2xhc3M9IiI+DQp0aGUgY3VycmVudCBwcm90b2NvbCBpdCBpcyBsZWZ0IHdhaXRpbmcg
Zm9yIGFuIEFDSyB0aGF0IG1heSBuZXZlciBjb21lLCBlaXRoZXI8YnIgY2xhc3M9IiI+DQpiZWNh
dXNlIHRoZSBHTSBpcyBkZWFkIG9yIGJlY2F1c2UgaXQganVzdCBkb2Vzbid0IGZlZWwgbGlrZSBy
ZXNwb25kaW5nLiBBZGQgdGhlPGJyIGNsYXNzPSIiPg0KbG9uZyB3YWl0cyAoaml0dGVyIG9mICZx
dW90O2EgZmV3IHNlY29uZHMmcXVvdDsgYW5kIHBvdGVudGlhbCByZXRyaWVzKSwgYW5kIHRoaXMg
bG9va3M8YnIgY2xhc3M9IiI+DQpsaWtlIGEgZmFyIGZyb20gb3B0aW1hbCBtYW5hZ2VtZW50IGV4
cGVyaWVuY2UuPGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxk
aXY+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPkluZGVlZCBhIEdNIGNvdWxk
IGFubm91bmNlIGl0cyBjYXBhYmlsaXR5LCBidXQgd2hldGhlciBvciBub3QgQUNLcyBhcmUgZGVz
aXJlZCBpcyBhIGNvbXBvbmVudCBvZiB0aGUgZ3JvdXAgcG9saWN5LiBJbiB0aGUgY29udGV4dCBv
ZiBHRE9JIHRoZSBHQ0tTIGlzIHRoZSBlbnRpdHkgdGhhdCBkZWZpbmVzIHRoZSBncm91cCBwb2xp
Y3kuIFRoZXJlIGNhbiBiZSBncm91cHMgd2hlcmUgdGhlIEFDSyBpcyB1c2VkLCB3aGVyZWFzDQog
b3RoZXJzIGRvIG5vdC4gJm5ic3A7VGhlIGNhcGFiaWxpdGllcyBhbm5vdW5jZW1lbnQgeW91IHN1
Z2dlc3QgY291bGQgY2VydGFpbmx5IGhlbHAgdGhlIEtTIHRvIGtub3cgd2hldGhlciBvciBub3Qg
dG8gZXhwZWN0IHRoZSBBQ0sgZnJvbSBhIHBhcnRpY3VsYXIgR00sIGJ1dCB0aGUgZm9jdXMgb2Yg
dGhpcyBJLUQgaXMgb24gdGhlIHRoZSBkZWNsYXJhdGlvbiBvZiB0aGUgcmVxdWVzdCBmb3IgQUNL
cyBieSB0aGUgR0NLUyBhbmQgdGhlIGZvcm1hdCBvZiB0aGUNCiBBQ0suPC9kaXY+DQo8ZGl2IGNs
YXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xh
c3M9IiI+DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4qIDIuMjogJnF1b3Q7VGhpcyBp
cyBhIHByaXZhdGUga2V5JnF1b3Q7IC0gdG8gYXZvaWQgY29uZnVzaW9uLCBJIHN1Z2dlc3Q6ICZx
dW90O1RoaXMgaXMgYTxiciBjbGFzcz0iIj4NCnNlY3JldCBzeW1tZXRyaWMga2V5JnF1b3Q7IChp
ZiB0aGlzIGlzIGluZGVlZCB0aGUgY2FzZSkuIE9idmlvdXNseSB1c2luZyB0aGUgc2FtZTxiciBj
bGFzcz0iIj4NCmtleSBmb3IgZW5jcnlwdGlvbiBhbmQgZm9yIEhNQUMgaXMgbm90IGEgYmVzdCBw
cmFjdGljZS48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRp
dj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2IGNsYXNzPSIiPldl4oCZdmUgbWFk
ZSB0aGlzIGNoYW5nZS48L2Rpdj4NCjwvZGl2Pg0KPGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUg
dHlwZT0iY2l0ZSIgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4qIFNl
Yy4gNTogQUNLIG1lc3NhZ2VzIGNhbiBhbHNvIGJlIGR1cGxpY2F0ZWQgaW4gdGhlIG5ldHdvcmsu
IEkgc3VnZ2VzdCB0byBhZGQ8YnIgY2xhc3M9IiI+DQphIHNlbnRlbmNlIGRlc2NyaWJpbmcgd2hh
dCB0aGUgR0NLUyBzaG91bGQgZG8gaW4gdGhpcyBjYXNlLjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2PjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdj5U
aGUgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMgKHNlY3Rpb24gNy4zKSBkZXNjcmliZXMgYSBtZXRo
b2QgZm9yIHRoZSBHQ0tTIHRvIGRldGVjdCByZXBsYXlzLiBUaGlzIGlzIGFyZ3VhYmx5IGJldHRl
ciBwbGFjZWQgaW4gdGhpcyBzZWN0aW9uLCBzbyB3ZeKAmXZlIG1vdmVkIGl0IGhlcmUuLjwvZGl2
Pg0KPGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+DQo8ZGl2
IGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4qIFNlYy4gNjogSSBhbSBjb25mdXNlZCBhYm91dCB0
aGUgbm90aW9uIG9mICZxdW90O2ppdHRlciZxdW90OyBoZXJlLiBJZiB0aGUgUFVTSCBtZXNzYWdl
czxiciBjbGFzcz0iIj4NCmFyZSBzZW50IGFzIG11bHRpY2FzdCAodGhlIHJlY29tbWVuZGVkIGFs
dGVybmF0aXZlIEFGQUlDVCksIEknbSBub3Qgc3VyZSBhYm91dDxiciBjbGFzcz0iIj4NCnRoZSBi
ZW5lZml0IG9mIHVzaW5nIG11bHRpY2FzdCwgZ2l2ZW4gdGhhdCBlYWNoIHJlY2lwaWVudCByZXNw
b25kcyB3aXRoIGE8YnIgY2xhc3M9IiI+DQp1bmljYXN0IEFDSy4gQW5kIGlmIHRoZSBQVVNIIGlz
IHVuaWNhc3QsIHRoZXJlIHNob3VsZCBiZSBubyByZWFzb24gZm9yIGEgaml0dGVyPGJyIGNsYXNz
PSIiPg0KYXMgdGhlIHNlbmRlciBjYW4gdGhyb3R0bGUgdGhlIFBVU0ggbWVzc2FnZXMgYXMgbmVj
ZXNzYXJ5LjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2
PjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdj5UaGUgY29uY2VwdCBvZiDigJxqaXR0ZXLigJ0g
aXMgbW9zdCB2YWx1YWJsZSBmb3IgcmVzcG9uc2VzIHRvIGEgbXVsdGljYXN0IFBVU0ggbWVzc2Fn
ZS4gVGhlIHVzZSBvZiBhIG11bHRpY2FzdCBQVVNIIG1lc3NhZ2UgbG93ZXIgcHJvY2Vzc2luZyBv
biB0aGUgR0NLUy4gU2luY2UgZWFjaCBHTSBjYW4gZSBnaXZlbiB0aGUgZXhhY3Qgc2FtZSBwb2xp
Y3ksIHRoZXJl4oCZcyBubyBjYWxsIHRvIHNlbmQgaXQgb3V0IGFzIGEgdW5pY2FzdCBtZXNzYWdl
Lg0KIFRoZSBqaXR0ZXIgaGVscHMgc3ByZWFkIG91dCB0aGUgcmVwbGllcyBhIGJpdCB0byBhdm9p
ZCBpbnVuZGF0aW5nIHRoZSBHQ0tTLjwvZGl2Pg0KPGRpdj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4N
CjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4NCjxkaXYg
Y2xhc3M9IiI+KiBNb3Jlb3ZlciwgZXZlcnl0aGluZyB3b3VsZCBiZSBtdWNoIG1vcmUgcHJlZGlj
dGFibGUgaWYgdGhlIEdDS1MgY291bGQ8YnIgY2xhc3M9IiI+DQppbmRpY2F0ZSBpZiBhIGppdHRl
ciBpcyBleHBlY3RlZCBhbmQgaG93IG11Y2ggb2YgYSBqaXR0ZXIgKGJhc2VkIG9uIHNpemUgb2Yg
dGhlPGJyIGNsYXNzPSIiPg0KZ3JvdXAsIG5ldHdvcmsgdGhyb3VnaHB1dCwgYW5kIHF1ZXVlIGxl
bmd0aCkuIFNwZWNpZmljYWxseSwgdGhpcyB3b3VsZCBhbGxvdzxiciBjbGFzcz0iIj4NCnRoZSBH
Q0tTIHRvIHRlbGwgaG93IGxvbmcgaXQgc2hvdWxkIHdhaXQgZm9yIGFuIEFDSy48YnIgY2xhc3M9
IiI+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj48YnIgY2xhc3M9IiI+DQo8
L2Rpdj4NCjxkaXY+VGhpcyB3b3VsZCBiZSBzb21ld2hhdCB1c2VmdWwsIGJ1dCBpbiBwcmFjdGlj
ZSBtaWdodCBub3QgaGVscCB0aGUgR0NLUyBhcyBtdWNoIGFzIGl0IHNlZW1zLiBUaGUgaml0dGVy
IHZhbHVlIHByb3ZpZGVkIHdvdWxkIGFsc28gYmUgZGVwZW5kZW50IG9uIHNldmVyYWwmbmJzcDtu
ZXR3b3JrIHBhcmFtZXRlcnMgdGhhdCBhcmVu4oCZdCB1bmRlciB0aGUgY29udHJvbCBvZiB0aGUg
R0NLUyBvciB0aGUgR00uIEV2ZW4gd2hlbiB0aGUgR00gZG9lcyBub3QgYWRkDQogYW55IGppdHRl
ciB0byB0aGUgQUNLLCB0aGUgdW5kZXJseWluZyBuZXR3b3JrIG1heSZuYnNwO2RlbGF5IHRoZSBQ
VVNIIGFuZC9vciBmb3IgdGhlIEFDSy4gQW5kIGFzIHN0YXRlZCBpbiBTZWN0aW9uIDYsIHRoZSBH
Q0tTIG1heSBiZSBjb25maWd1cmVkIHdpdGggYWRkaXRpb25hbCBwb2xpY3kgYWN0aW9ucyBsaWtl
IHJldHJhbnNtaXNzaW9ucyB0byBvdmVyY29tZSZuYnNwO2xvc3QgQUNLcy4gQWx0b2dldGhlciB0
byBhZGQgaml0dGVyIHRvIHRoZSBBQ0sgaXMgbm90DQogYSBtdXN0LCBpdCBpcyBhIHdheSB0byBo
ZWxwIHRoZSBHQ0tTIGRlYWwgd2l0aCBhIGh1Z2UgbnVtYmVyIG9mIEdNcy4gSW4gcHJhY3RpY2Us
IHdl4oCZdmUgZm91bmQgdGhhdCBoYXZpbmcgdGhlIEdNcyBjaG9vc2UgdGhlIGppdHRlciBoYXMg
d29ya2VkIHdlbGwsIGV2ZW4gd2hlbiB0aGUgR01zIGFyZSBkaWZmZXJlbnQgaW1wbGVtZW50YXRp
b25zLjwvZGl2Pg0KPGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9
IiI+DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4qIENyeXB0b2dyYXBoaWMgYWdpbGl0
eTogdGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgb25seSBvbmUgYWxnb3JpdGhtIGZvciB0aGU8YnIg
Y2xhc3M9IiI+DQpIQVNIIHZhbHVlLCBhbmQgc2F5cyB0aGF0IGlmIGEgbmV3IGFsZ29yaXRobSBp
cyBuZWVkZWQsIHRoZXJlIHdpbGwgYmUgYSBuZXc8YnIgY2xhc3M9IiI+DQpLRUtfQUNLX1JFUVVF
U1RFRCBwYXlsb2FkIGRlZmluZWQuIEhvd2V2ZXIgdG8gbWFrZSBzdXJlIHRoYXQgdGhpcyByZWFs
bHk8YnIgY2xhc3M9IiI+DQomcXVvdDt3b3JrcyZxdW90Oywgd2UgbmVlZCB0byBkZWZpbmUgd2hl
dGhlciBtdWx0aXBsZSBzdWNoIHBheWxvYWRzIGNhbiBiZSBzZW50PGJyIGNsYXNzPSIiPg0Kc2lt
dWx0YW5lb3VzbHkgKGlmIGUuZy4gc29tZSBHTXMgc3RpbGwgc3VwcG9ydCB0aGUgb2xkIGFsZ29y
aXRobSkgYW5kIHdoYXQnczxiciBjbGFzcz0iIj4NCnRoZSBleHBlY3RlZCBiZWhhdmlvci4gSSB3
b3VsZCBzdWdnZXN0IHRvIGRlZmluZSBhbiBhZGRpdGlvbmFsIFNIQS01MTIgcGF5bG9hZDxiciBj
bGFzcz0iIj4NCmp1c3QgdG8gbWFrZSBmb3IgYSBjb25jcmV0ZSBleGFtcGxlLjxiciBjbGFzcz0i
Ij4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8YnIgY2xhc3M9IiI+DQo8L2Rpdj4N
CjxkaXY+DQo8ZGl2IGNsYXNzPSIiPlRoaXMgaXMgYSBnb29kIHN1Z2dlc3Rpb24uIFdl4oCZdmUg
YWRkZWQgU0hBLTUxMiB2ZXJzaW9ucyBvZiB0aGUgZXhpc3RpbmcgS0VLX0FDS19SRVFVRVNURUQg
dmFsdWVzLjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYg
Y2xhc3M9IiI+U2VlICZsdDs8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJh
ZnQtd2Vpcy1nZG9pLXJla2V5LWFjay0wNiIgY2xhc3M9IiI+aHR0cHM6Ly90b29scy5pZXRmLm9y
Zy9odG1sL2RyYWZ0LXdlaXMtZ2RvaS1yZWtleS1hY2stMDY8L2E+Jmd0OzwvZGl2Pg0KPGRpdiBj
bGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+VGhhbmtzLDwvZGl2
Pg0KPGRpdiBjbGFzcz0iIj5CcmlhbjwvZGl2Pg0KPC9kaXY+DQo8YnIgY2xhc3M9IiI+DQo8ZGl2
IGNsYXNzPSIiPi0tJm5ic3A7PGJyIGNsYXNzPSIiPg0KQnJpYW4gV2VpczxiciBjbGFzcz0iIj4N
ClNlY3VyaXR5LCBDU0csIENpc2NvIFN5c3RlbXM8YnIgY2xhc3M9IiI+DQpUZWxlcGhvbmU6ICYj
NDM7MSA0MDggNTI2IDQ3OTY8YnIgY2xhc3M9IiI+DQpFbWFpbDogPGEgaHJlZj0ibWFpbHRvOmJl
d0BjaXNjby5jb20iIGNsYXNzPSIiPmJld0BjaXNjby5jb208L2E+IDwvZGl2Pg0KPGJyIGNsYXNz
PSIiPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_E61F05DBEEB04140A2D4DB11163C4E13ciscocom_--


From nobody Thu Aug 24 12:59:55 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E78E3132139; Thu, 24 Aug 2017 12:59:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level: 
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ho0TVXxO46pO; Thu, 24 Aug 2017 12:59:41 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B12B132113; Thu, 24 Aug 2017 12:59:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1503604781; x=1535140781; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=41aNnkWn+WRaU8WXKuKboglJOey8kwAuT8szHJsJF2Q=; b=PffKMUVfJdYVeeGJNGygxSIJOoFzEBP5yjJR6X2h4E2Cb0HP+Hp9IxR0 LObt+Lm4C60R5HPywqH+oRbbN3MrdrqsjiCnuG0bUfyU2z+GvlutyyHGQ m4yZTj9LNFroCeWD4jVlOdLh2JPaUZR/PzkefptsJ3Se5D3fku49HVYEw M=;
X-IronPort-AV: E=Sophos;i="5.41,422,1498546800";  d="scan'208,217";a="113511021"
Received: from unknown (HELO Ironmsg04-R.qualcomm.com) ([10.53.140.108]) by sabertooth01.qualcomm.com with ESMTP; 24 Aug 2017 12:59:40 -0700
X-IronPort-AV: E=McAfee;i="5900,7806,8633"; a="1479877812"
X-MGA-submission: =?us-ascii?q?MDHBa1FrrHdawzqzBv7m7wycZz+RNWpflx2q/M?= =?us-ascii?q?Pr9k/chlZxWTMWZXqDMeIkOhG6/9Jp9p60jSBl71lUdGi+n/ikEnoADl?= =?us-ascii?q?1Xi4PZrpFK2qYGY+/jFxW1aJJhSzJ64auZicGiL7J9Ke62zxjQeteLrV?= =?us-ascii?q?HW?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 24 Aug 2017 12:59:39 -0700
Received: from [10.110.41.50] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Thu, 24 Aug 2017 12:59:39 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Acee Lindem <acee@cisco.com>
CC: Xuxiaohu <xuxiaohu@huawei.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, "draft-ietf-ospf-encapsulation-cap.all@ietf.org" <draft-ietf-ospf-encapsulation-cap.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: =?utf-8?b?562U5aSNOg==?= Genart last call review of draft-ietf-ospf-encapsulation-cap-06
Date: Thu, 24 Aug 2017 14:59:37 -0500
Message-ID: <FD0F68BB-E3AE-42CE-BA08-CF4F9827953F@qti.qualcomm.com>
In-Reply-To: <D5C474D6.C37C9%acee@cisco.com>
References: <D5C474D6.C37C9%acee@cisco.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_601E3A86-581B-4610-AD51-3F633A67ABF6_="
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01E.na.qualcomm.com (10.85.0.31) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PhIVR3Ttr5i4zXp2l2gfczHDR60>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Aug 2017 19:59:43 -0000

--=_MailMate_601E3A86-581B-4610-AD51-3F633A67ABF6_=
Content-Type: text/plain; charset="utf-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit

On 24 Aug 2017, at 11:24, Acee Lindem (acee) wrote:

>>>> For 1, 2, 6, and 7, that's easy; the drafts defining the values can 
>>>> do
>>>> the registrations. For 5, the reference would be to an existing RFC
>>>> that doesn't do the registration. I'm not sure what to do about 
>>>> that;
>>>> perhaps register it here and make the reference both 5640 and this
>>> document.
>
> Actually, this document does assign these code points in the registry 
> so
> “This document” is appropriate. The value portion of these TLVs 
> just
> happened to be described via a reference rather than text.

There is nothing preventing the IANA registry from having useful 
information. :-) Yes, this document registers it, but really what the 
implementer is going to need is this document *and* 5640, so I see no 
particular harm in putting both references in the registry, and it's 
probably useful.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478

--=_MailMate_601E3A86-581B-4610-AD51-3F633A67ABF6_=
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">On 24 Aug 2017, at 11:24, Acee Lindem (acee) wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999">
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB">
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB">
<p dir=3D"auto">For 1, 2, 6, and 7, that's easy; the drafts defining the =
values can do<br>
the registrations. For 5, the reference would be to an existing RFC<br>
that doesn't do the registration. I'm not sure what to do about that;<br>=

perhaps register it here and make the reference both 5640 and this</p>
</blockquote>

<p dir=3D"auto">document.</p>
</blockquote>
</blockquote>

<p dir=3D"auto">Actually, this document does assign these code points in =
the registry so<br>
=E2=80=9CThis document=E2=80=9D is appropriate. The value portion of thes=
e TLVs just<br>
happened to be described via a reference rather than text.</p>
</blockquote>

<p dir=3D"auto">There is nothing preventing the IANA registry from having=
 useful information. :-) Yes, this document registers it, but really what=
 the implementer is going to need is this document <em>and</em> 5640, so =
I see no particular harm in putting both references in the registry, and =
it's probably useful.</p>

<p dir=3D"auto">pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" style=3D"co=
lor:#3983C4">http://www.qualcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>
</div>
</div>
</body>
</html>

--=_MailMate_601E3A86-581B-4610-AD51-3F633A67ABF6_=--


From nobody Thu Aug 24 13:47:35 2017
Return-Path: <acee@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6E591321A3; Thu, 24 Aug 2017 13:47:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level: 
X-Spam-Status: No, score=-14.521 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MTuRbmVgEiMn; Thu, 24 Aug 2017 13:47:31 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 459131323A3; Thu, 24 Aug 2017 13:47:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7566; q=dns/txt; s=iport; t=1503607651; x=1504817251; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ZA+rlP6W4614rigPXNYhEUQwD/P7rzc239ziTrOXLyY=; b=WPQTsFWI+jSTeqN1GcZ20KmAEnd9NBqXCUSA+Cn3Fu5UBY76dL86za5T MIWIu1HZc6k0tzSaHDLrBJpQcijXjLc4OSB2JzIuws+JfF+wwSJ3fe8mg BUNaT9Qigr8Y/e++VGYEbNKS8L5AXOMPjexoYP3wHeKKeNsWzP2H7IUoX M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DzAAABOp9Z/51dJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1pkgRUHg3CKHZAXmBWCEiELhRsCGoQ3PxgBAgEBAQEBAQFrKIU?= =?us-ascii?q?ZAgEDAQEhEToEBxACAQgaAiYCAgIlCxUQAgQBDQWKMRCuVoIni1cBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEYBYENgh2CAoZWhHODE4JhBZEbjz4Ch1SMb4IShWOKb5Y?= =?us-ascii?q?vAR84gQp3FR8qhxp2ihOBDwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.41,422,1498521600"; d="scan'208";a="475841519"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Aug 2017 20:47:30 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id v7OKlTnl000425 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 24 Aug 2017 20:47:30 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 24 Aug 2017 16:47:29 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Thu, 24 Aug 2017 16:47:28 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Joe Touch <touch@strayalpha.com>, IETF discussion list <ietf@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, "draft-ietf-ospf-encapsulation-cap@ietf.org" <draft-ietf-ospf-encapsulation-cap@ietf.org>
CC: TSV Dir <tsv-dir@ietf.org>
Subject: Re: [OSPF] tsv-dir review of draft-ietf-ospf-encapsulation-cap-06
Thread-Topic: [OSPF] tsv-dir review of draft-ietf-ospf-encapsulation-cap-06
Thread-Index: AQHTHJMJGfh8krRpK0CtEqEa8CMOEqKT+zaA
Date: Thu, 24 Aug 2017 20:47:28 +0000
Message-ID: <D5C4B293.C38FA%acee@cisco.com>
References: <150280426212.21081.15543071828535131713.idtracker@ietfa.amsl.com> <7ca66dbe-1437-482d-a785-d5e48a558ccb@strayalpha.com>
In-Reply-To: <7ca66dbe-1437-482d-a785-d5e48a558ccb@strayalpha.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.201]
Content-Type: text/plain; charset="utf-8"
Content-ID: <DC848A4F5E74624C9E65F302EAB8EE2B@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Jad7SwMIqGuAenH7ZB6aQRGQRb0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Aug 2017 20:47:34 -0000

WGlhb2h1IGFuZCBvdGhlciBDby1hdXRob3JzLA0KDQpQbGVhc2UgcmVzcG9uZCB0byBKb2XigJlz
IGNvbW1lbnRzLiBZb3UgZG9u4oCZdCBuZWNlc3NhcmlseSBoYXZlIHRvIGFkZHJlc3MNCnRoZW0g
YWxsIGFzIGhlIGFzIHN1Z2dlc3RlZCBidXQgcGxlYXNlIHJlc3BvbmQuDQoNCkpvZSwgDQoNCkZv
ciB5b3VyIGNvbW1lbnQgb24gdGhlIGludHJvZHVjdGlvbiwgY2FuIHlvdSBwcm92aWRlIHRleHQ/
DQoNClRoYW5rcywgDQpBY2VlIA0KDQpPbiA4LzI0LzE3LCAxMjozOSBBTSwgIk9TUEYgb24gYmVo
YWxmIG9mIEpvZSBUb3VjaCIgPG9zcGYtYm91bmNlc0BpZXRmLm9yZw0Kb24gYmVoYWxmIG9mIHRv
dWNoQHN0cmF5YWxwaGEuY29tPiB3cm90ZToNCg0KPkhpLCBhbGwsDQo+DQo+SSBhbSB0aGUgYXNz
aWduZWQgVFNWLUFSVCByZXZpZXdlciBmb3IgZHJhZnQtaWV0Zi1vc3BmLWVuY2Fwc3VsYXRpb24t
Y2FwDQo+DQo+Rm9yIGJhY2tncm91bmQgb24gVFNWLUFSVCwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0
DQo+PGh0dHBzOi8vdHJhYy5pZXRmLm9yZy90cmFjL3Rzdi93aWtpL1RTVi1EaXJlY3RvcmF0ZT4u
DQo+DQo+UGxlYXNlIHJlc29sdmUgdGhlc2UgY29tbWVudHMgYWxvbmcgd2l0aCBhbnkgb3RoZXIg
TGFzdCBDYWxsIGNvbW1lbnRzDQo+eW91IG1heSByZWNlaXZlLg0KPg0KPkpvZQ0KPg0KPi0tLS0t
LQ0KPg0KPkkndmUgcmV2aWV3ZWQgdGhpcyBkb2N1bWVudCBhcyBwYXJ0IG9mIHRoZSB0cmFuc3Bv
cnQgYXJlYSBkaXJlY3RvcmF0ZSdzDQo+b25nb2luZyBlZmZvcnQgdG8gcmV2aWV3IGtleSBJRVRG
IGRvY3VtZW50cy4gVGhlc2UgY29tbWVudHMgd2VyZSB3cml0dGVuDQo+cHJpbWFyaWx5IGZvciB0
aGUgdHJhbnNwb3J0IGFyZWEgZGlyZWN0b3JzLCBidXQgYXJlIGNvcGllZCB0byB0aGUNCj5kb2N1
bWVudCdzIGF1dGhvcnMgZm9yIHRoZWlyIGluZm9ybWF0aW9uIGFuZCB0byBhbGxvdyB0aGVtIHRv
IGFkZHJlc3MNCj5hbnkgaXNzdWVzIHJhaXNlZC4gV2hlbiBkb25lIGF0IHRoZSB0aW1lIG9mIElF
VEYgTGFzdCBDYWxsLCB0aGUgYXV0aG9ycw0KPnNob3VsZCBjb25zaWRlciB0aGlzIHJldmlldyB0
b2dldGhlciB3aXRoIGFueSBvdGhlciBsYXN0LWNhbGwgY29tbWVudHMNCj50aGV5IHJlY2VpdmUu
IFBsZWFzZSBhbHdheXMgQ0MgdHN2LWRpckBpZXRmLm9yZyBpZiB5b3UgcmVwbHkgdG8gb3INCj5m
b3J3YXJkIHRoaXMgcmV2aWV3Lg0KPg0KPiJUaGlzIGRyYWZ0IGhhcyBzZXJpb3VzIGlzc3Vlcywg
ZGVzY3JpYmVkIGluIHRoZSByZXZpZXcsIGFuZCBuZWVkcyB0byBiZQ0KPnJldGhvdWdodC4iDQo+
DQo+QWx0aG91Z2ggSSBmb3VuZCBubyB0cmFuc3BvcnQgaXNzdWVzLCB0aGVyZSBhcmUgbWFueSBm
dW5kYW1lbnRhbA0KPnByb2JsZW1zIHRoYXQgbmVlZCB0byBiZSBjb3JyZWN0ZWQgYmVmb3JlIHRo
aXMgZG9jdW1lbnQgc2hvdWxkIHByb2NlZWQuDQo+VGhlc2UgYXJlIHN1bW1hcml6ZWQgYmVsb3cu
DQo+DQo+U2VjMTogVGhlIGludHJvZHVjdGlvbiBqdW1wcyB0b28gcXVpY2tseSBpbnRvIGEgbGlz
dCBvZiBzaXR1YXRpb25zIGluDQo+d2hpY2ggdHVubmVscyBhcmUgdXNlZCwgdHdvIG9mIHdoaWNo
IGFyZSBlbWVyZ2luZyAoY3VycmVudGx5IG9ubHkNCj5kcmFmdHMpLiBUaGVyZSBhcmUgbWFueSBi
ZXR0ZXIgYW5kIG1vcmUgZXN0YWJsaXNoZWQgZXhhbXBsZXMgKGdvaW5nIGJhY2sNCj50byB0aGUg
TS1Cb25lLCB0aGUgNi1Cb25lLCBldGMuLCB0byBWUE5zLCBuZXR3b3JrIHZpcnR1YWxpemF0aW9u
LCBldGMuKS4NCj5UZXJtcyBhcmUgdXNlZCBiZWZvcmUgZGVmaW5lZCAod2hhdCBpcyBhbiBpbmdy
ZXNzPyBhcmUgeW91IHJlZmVycmluZyB0bw0KPnRoZSByb3V0ZXIgb3IgaG9zdCBhdCB3aGljaCBh
IHR1bm5lbCBpcyBhdHRhY2hlZCwgb3IgdGhlIGlucHV0IHRvIHRoZQ0KPnR1bm5lbCBpdHNlbGY/
KS4gVGhlIGxhc3QgdHdvIHNlbnRlbmNlcyBzaG91bGQgYmVnaW4gdGhlIGludHJvLCB3aGljaA0K
PnNob3VsZCBleHBhbmQgYW5kIGV4cGxhaW4gd2hhdCBpcyBtZWFudCAoZS5nLiwgYnkgImVncmVz
cyB0dW5uZWxpbmciIGFuZA0KPnRoZSByZWFzb24gZm9yIHdhbnRpbmcgdG8gZW5jb2RlIHR1bm5l
bHMgYXMgTFNBcy4NCj4NCj5TZWMyOiBUaGUgdGVybWlub2xvZ3kgc2VjdGlvbiBpcyBpbmNvbXBs
ZXRlLiBUaGUgdGVybXMgdHVubmVsLCBpbmdyZXNzLA0KPmVncmVzcywgZWdyZXNzIHR1bm5lbGlu
ZywgZXRjLiBhcmUgbm90IGRlZmluZWQgaW4gUkZDNzc3MC4gT25seSB0aGUgTFNBDQo+dGVybWlu
b2xvZ3kgaXMgcmVsZXZhbnQgZnJvbSB0aGF0IFJGQy4gT3RoZXIgdGVybXMgbmVlZCB0byBiZSBk
ZWZpbmVkIGluDQo+dGhpcyBkb2Mgb3IgdXNlZCBmcm9tIG90aGVycy4NCj4NCj5TZWMzOiBUaGlz
IHNlY3Rpb24gaXMgd3JpdHRlbiBhcyBpZiB0aGUgIkVuY2Fwc3VsYXRpb24gQ2FwYWJpbGl0eSBU
TFYiDQo+aXMgYWxyZWFkeSBkZWZpbmVkIChpbiBSRkM3NzcwKSwgcmF0aGVyIHRoYW4gYmVpbmcg
ZGVmaW5lZCBoZXJlaW4uIFRoZQ0KPnNlY3Rpb24gdGl0bGUgZG9lc24ndCBtYXRjaCB0aGlzIG5h
bWUsIHdoaWNoIGlzIGNvbmZ1c2luZy4gVGhlIHRlcm0gVExWDQo+aXMgaXRzZWxmIGNvbmZ1c2lu
ZywgYXMgdGhpcyBpcyByZWFsbHkgYSBzaW5nbGUgVExWIG9mIHRoZSBSSSBPcGFxdWUgTFNBDQo+
c2V0IG9mIHR5cGVzLCB3aGljaCBpdHNlbGYgaXMgcmVwcmVzZW50ZWQgYXMgYSAoc3ViKVRMViBs
aXN0LiBJDQo+YXBwcmVjaWF0ZSB0aGF0IHRoaXMgdGVybWlub2xvZ3kgd2FzIG1hZGUgY29uZnVz
aW5nIGluIHByZXZpb3VzLA0KPmVzdGFibGlzaGVkIGRvY3VtZW50cywgYnV0IGEgYml0IG9mIGV4
cGxhbmF0aW9uIHdvdWxkIGdvIGEgbG9uZyB3YXkgLSBhcw0KPndvdWxkIHNob3dpbmcgdGhlIHRv
cC1sZXZlbCBPU1BGIFJJIE9wYXF1ZSBMU0EgYW5kIHdoZXJlIHRoZSBuZXcgVEJEMQ0KPnZhbHVl
IHdvdWxkIGFwcGVhciAtIGJlZm9yZSBkaXZpbmcgaW50byB0aGUgc3RydWN0dXJlIGluc2lkZSB0
aGlzIG5ldw0KPiJUTFYiLg0KPg0KPlNlYyA0OiB0aGUgZGlzY3Vzc2lvbiBzaG91bGQgY2xhcmlm
eSB3aGF0IGhhcHBlbnMgaWYgdGhlIGxlbmd0aCBmaWVsZCBpcw0KPmxvbmdlciB0aGFuIHRoZSBm
aWVsZHMgaW5kaWNhdGVkIGJ5IHRoZSBzdWItVExWcyAoaXMgdGhpcyBhbiBlcnJvciBvcg0KPnBh
ZGRpbmcgdG8gYmUgaWdub3JlZDsgZG9lcyB0aGUgbGF0dGVyIHByZXNlbnQgYSBjb3ZlcnQgY2hh
bm5lbCkuDQo+YWRkaXRpb25hbGx5LCB0aGlzIHNlY3Rpb24gcmVmZXJzIHRvIFJGQzU1MTIgLSB3
aGljaCBpcyBiZWluZyBvYnNvbGV0ZWQNCj5ieSBpZXRmLWlkci10dW5uZWwtZW5jYXBzIC0gYW5k
IHRoaXMgcGVuZGluZyBJRCBpcyB1c2VkIGFzIHRoZSBwcmltYXJ5DQo+cmVmZXJlbmNlIGluIFNl
Y3MgNS4xIGFuZCA1LjIuIFJlZmVyZW5jZXMgdG8gUkZDNTUxMiBzaG91bGQgYmUgcmVwbGFjZWQN
Cj53aXRoIHRoYXQgSUQgKHdoaWNoIEknbGwgYXNzdW1lIHdpbGwgYmUgcHVibGlzaGVkIGNvbmN1
cnJlbnRseSkuDQo+DQo+U2VjIDU6IHRoaXMgc2VjdGlvbiByZWZlcnMgdG8gdGhlIGNvbmNlcHQg
b2YgYW4gImludmFsaWQiIHN1Yi1UTFY7IGdpdmVuDQo+dGhlIHByZXZpb3VzIHNlbnRlbmNlIGV4
cGxhaW5zIHRoYXQgdW5rbm93biBzdWItVExWcyBhcmUgc2lsZW50bHkNCj5pZ25vcmVkLCB0aGVu
IHdoYXQgZXhhY3RseSBpcyBhbiBpbnZhbGlkIHN1Yi1UTFY/IEl0IGZ1cnRoZXIgaXNuJ3QgY2xl
YXINCj53aHkgMiBvY3RldHMgb2YgdHlwZSBhbmQgMiBvY3RldHMgb2YgbGVuZ3RoIGFyZSBuZWVk
ZWQgKGdyYW50ZWQgaXQNCj5wcm92aWRlcyBhbGlnbm1lbnQsIGJ1dCBpcyB0aGF0IHJlYWxseSBp
bXBvcnRhbnQgZm9yIHRoaXMgc29ydCBvZg0KPmFwcGxpY2F0aW9uLWxheWVyIHByb3RvY29sPykN
Cj4NCj5TZWMgNS4xIGFuZCA1LjI6IGl0IGlzIHVuY2xlYXIgd2h5IHRoZSB0d28gZnVuZGFtZW50
YWwgc3ViLVRMVnMgb2YgdGhpcw0KPlRMViBhcmUgZGVmaW5lZCBlbHNld2hlcmU7IGluIHNwZWNp
ZmljLCB0aGUgZXhhbXBsZSBvZiB0aGUgc3ViLVRMVg0KPnNob3VsZCBhcHBlYXIgaGVyZSAoYWN0
dWFsbHkgZm9yIGVhY2ggb2YgdGhlIHN1Yi1UTFZzKS4NCj4NCj5TZWMgNS4zIGluZmVycyBJUCBh
ZGRyZXNzIHZlcnNpb24gZnJvbSBsZW5ndGgsIHdoZW4gdGhlIHZlcnNpb24gY291bGQNCj4oc2hv
dWxkKSBlYXNpbHkgZW5jb2RlZCBlaXRoZXIgYXMgZGlmZmVyZW50IHR5cGVzICh5b3UgaGF2ZSA2
NUsgb2YNCj50aGVtISkgb3IgdXNpbmcgYW4gYWRkaXRpb25hbCBmZXcgYml0cyAoZS5nLiwgY2Fy
dmVkIG91dCBvZiB0aGUgZXhjZXNzZXMNCj5ub3RlZCBpbiBTZWMgNSkuDQo+DQo+U2VjIDUuNCAt
IEkgaGFkIHRvIHRocmVhZCB0aHJvdWdoIHNldmVyYWwgZGlmZmVyZW50IHNlY3Rpb25zIG9mIHRo
ZSBJRFINCj5JRCB0byBmaWd1cmUgb3V0IHdoYXQgQ29sb3IgbWVhbnQgYW5kIGhvdyBpdCBpcyB1
c2VkLiBHcmFudGVkIHRoYXQgaXMgYQ0KPmRpZmZlcmVudCBwcm9ibGVtIGluIGEgZGlmZmVyZW50
IGRvYywgSU1PIHRoaXMgZG9jIHNob3VsZCBpbmNsdWRlIGVub3VnaA0KPm9mIGEgc3VtbWFyeSB0
aGF0IHRoaXMgc29ydCBvZiAndHJhY2ViYWNrJyBzaG91bGQgbm90IGJlIG5lZWRlZCB0bw0KPnVu
ZGVyc3RhbmQgd2hhdCBpcyBiZWluZyBkZXNjcmliZWQuIEZ1cnRoZXIsIHRoZSBvdGhlciBkb2Mg
ZG9lc24ndCBldmVuDQo+ZXhwbGFpbiBDb2xvciBzdWZmaWNpZW50bHksIElNTy4NCj4NCj5TZWNz
IDUuNiBhbmQgNS43IC0gVGhlcmUgYXJlIG1hbnkgcnVsZXMgZm9yIGhvdyB0aGUgb3V0ZXIgZW5j
YXBzdWxhdGlvbg0KPmhlYWRlciBpcyBjb21wb3NlZCwgYW5kIG1hbnkgZmllbGRzIGl0IG1heSBh
ZmZlY3QgYmV5b25kIFFvUyBhbmQgVURQDQo+ZGVzdGluYXRpb24gcG9ydC4gVGhpcyBzZWN0aW9u
IGlzIGluY29tcGxldGUgaW4gZGVzY3JpYmluZyB2YWx1ZXMgZm9yDQo+dGhlIG91dGVyIGhlYWRl
cihzKSBvciByZWxhdGlvbnNoaXBzIHRvIHRoZSBpbm5lciBoZWFkZXIocykuDQo+DQo+U2VjIDYg
LSBJIHdvdWxkIGVuY291cmFnZSBtb3ZpbmcgdGhpcyBzZWN0aW9uIGVhcmxpZXIsIGJlZm9yZSB0
aGUNCj5kZXRhaWxzIG9mIGhvdyB0aGUgTFNBIGlzIGNvbXBvc2VkLg0KPg0KPlNlYyA3IC0gdGhl
IGRvY3VtZW50IHNob3VsZCBkZXNjcmliZSB3aGVyZSBleHBlcmltZW50YWwgdmFsdWVzDQo+Y2Fu
L3Nob3VsZCBiZSBzYWZlbHkgdXNlZCBhbmQgaG93IGNvbGxpc2lvbnMgYXJlIGhhbmRsZWQ7IGl0
IHNob3VsZCBhbHNvDQo+ZXhwbGFpbiB3aGF0IGhhcHBlbnMgd2hlbiBhIHJlc2VydmVkIHZhbHVl
IGlzIHNlZW4gaW4gYW4gTFNBLg0KPg0KPi0tLS0NCj4NCj4NCj5fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPk9TUEYgbWFpbGluZyBsaXN0DQo+T1NQRkBp
ZXRmLm9yZw0KPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vb3NwZg0KDQo=


From nobody Thu Aug 24 13:55:34 2017
Return-Path: <lyndon@orthanc.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A78CA1321A7 for <ietf@ietfa.amsl.com>; Thu, 24 Aug 2017 13:55:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 49Y8fs29B8Uw for <ietf@ietfa.amsl.com>; Thu, 24 Aug 2017 13:55:31 -0700 (PDT)
Received: from orthanc.ca (orthanc.ca [IPv6:2607:f2f8:abf8::2]) (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 4417C1321A3 for <ietf@ietf.org>; Thu, 24 Aug 2017 13:55:31 -0700 (PDT)
Received: from minnie.hitronhub.home (S0106a84e3f81a003.vc.shawcable.net [24.80.126.119]) (authenticated bits=0) by orthanc.ca (8.15.2/8.15.2) with ESMTPSA id v7OKtTdR071254 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Thu, 24 Aug 2017 13:55:30 -0700 (PDT) (envelope-from lyndon@orthanc.ca)
From: Lyndon Nerenberg <lyndon@orthanc.ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Next steps in IETF list email archiving
Date: Thu, 24 Aug 2017 13:55:24 -0700
References: <20170731132508.GA22575@gsp.org> <20170823194058.18709.qmail@ary.lan> <20170823215111.GA28827@faui40p.informatik.uni-erlangen.de> <alpine.OSX.2.21.1708232125030.81381@ary.qy> <20170824034657.GB28827@faui40p.informatik.uni-erlangen.de> <EE74ED30-5D94-4D16-9439-35B54ADE9450@orthanc.ca> <27860.1503588168@obiwan.sandelman.ca>
To: IETF general list <ietf@ietf.org>
In-Reply-To: <27860.1503588168@obiwan.sandelman.ca>
Message-Id: <67C32DB4-E5CF-4042-9F10-50C3AF072919@orthanc.ca>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7cI_F0DKWZp5qXrXlaAFxKTf8Ys>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Aug 2017 20:55:33 -0000

> On Aug 24, 2017, at 8:22 AM, Michael Richardson =
<mcr+ietf@sandelman.ca> wrote:
>=20
> I think the problem is that many people would like to suck the =
archives back
> in bulk, and they see IMAP as too chatty.

I don't think that's a valid argument.  Once you authenticate and select =
your mailbox of interest, you're issuing a single FETCH command for each =
message you want, so it's no more overhead than FTP in that regard.  To =
mitigate the lock-step command RTTs, just run a few FETCH streams in =
parallel.

If I can find some spare time this weekend I'll see about putting =
together a simple downloader and run some timing tests.

--lyndon=


From nobody Thu Aug 24 14:00:03 2017
Return-Path: <acee@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA8971323A3; Thu, 24 Aug 2017 13:59:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level: 
X-Spam-Status: No, score=-14.52 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aL6vPSoiYaiZ; Thu, 24 Aug 2017 13:59:53 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1A5A13238E; Thu, 24 Aug 2017 13:59:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12651; q=dns/txt; s=iport; t=1503608392; x=1504817992; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=giWdu6WBjPe5iGrQf5PlYFaeAkG56n99XeQq4KSFhso=; b=QYgAKcKq0J434zaV53scG0NuLCHjQUUOB8o6NW3x4vWst41SRPuKU6zj QAPf8V6D7NIGibgXsqcgc1N5dPHrLHfkYmkUx8xa9Wcxz8qPV18q8DKN5 GjdyQ+s6IAxfxZLzvGZ4scOse5Z7ZwnE1gls/iYecQOfwClvolh3vgq5l M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CAAgAGPp9Z/5ldJa1aAxYDAQEBAQEBA?= =?us-ascii?q?QEBAQEHAQEBAQGCb2tkgRUHg3CaNIFwiDmIL1GGfieFIAIahDdDFAECAQEBAQE?= =?us-ascii?q?BAWsohRgBAQEBAyNWEAIBBgIOAwMBAigDAgICHxEUBgMIAgQOBYlNTAMVEJBTn?= =?us-ascii?q?WaCJ4c5DYQRAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYMqggKDLgGDJ4JXgjMJAQU?= =?us-ascii?q?hgkyCYQWYI4d6PAKPTYR2kmSMQYluATYhgQp3FUmEXoEHgTV2AYkGgQ8BAQE?=
X-IronPort-AV: E=Sophos;i="5.41,422,1498521600";  d="scan'208,217";a="284841727"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Aug 2017 20:59:22 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v7OKxLcD027648 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 24 Aug 2017 20:59:22 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 24 Aug 2017 16:59:21 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Thu, 24 Aug 2017 16:59:21 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
CC: Xuxiaohu <xuxiaohu@huawei.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, "draft-ietf-ospf-encapsulation-cap.all@ietf.org" <draft-ietf-ospf-encapsulation-cap.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: =?utf-8?B?UmU6IOetlOWkjTogR2VuYXJ0IGxhc3QgY2FsbCByZXZpZXcgb2YgZHJhZnQt?= =?utf-8?Q?ietf-ospf-encapsulation-cap-06?=
Thread-Topic: =?utf-8?B?562U5aSNOiBHZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRm?= =?utf-8?Q?-ospf-encapsulation-cap-06?=
Thread-Index: AQHTHPWC2ul1ZKCGrUqeBeF5Dh6CY6KUMCmA///NmgA=
Date: Thu, 24 Aug 2017 20:59:21 +0000
Message-ID: <D5C4B41B.C3926%acee@cisco.com>
References: <D5C474D6.C37C9%acee@cisco.com> <FD0F68BB-E3AE-42CE-BA08-CF4F9827953F@qti.qualcomm.com>
In-Reply-To: <FD0F68BB-E3AE-42CE-BA08-CF4F9827953F@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.201]
Content-Type: multipart/alternative; boundary="_000_D5C4B41BC3926aceeciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RD61BWpx6YALM5tYkPWjP6fjAGI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Aug 2017 20:59:56 -0000

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

DQoNCkZyb206IFBldGUgUmVzbmljayA8cHJlc25pY2tAcXRpLnF1YWxjb21tLmNvbTxtYWlsdG86
cHJlc25pY2tAcXRpLnF1YWxjb21tLmNvbT4+DQpEYXRlOiBUaHVyc2RheSwgQXVndXN0IDI0LCAy
MDE3IGF0IDM6NTkgUE0NClRvOiBBY2VlIExpbmRlbSA8YWNlZUBjaXNjby5jb208bWFpbHRvOmFj
ZWVAY2lzY28uY29tPj4NCkNjOiBYaWFvaHUgWHUgPHh1eGlhb2h1QGh1YXdlaS5jb208bWFpbHRv
Onh1eGlhb2h1QGh1YXdlaS5jb20+PiwgImdlbi1hcnRAaWV0Zi5vcmc8bWFpbHRvOmdlbi1hcnRA
aWV0Zi5vcmc+IiA8Z2VuLWFydEBpZXRmLm9yZzxtYWlsdG86Z2VuLWFydEBpZXRmLm9yZz4+LCBP
U1BGIFdHIExpc3QgPG9zcGZAaWV0Zi5vcmc8bWFpbHRvOm9zcGZAaWV0Zi5vcmc+PiwgImRyYWZ0
LWlldGYtb3NwZi1lbmNhcHN1bGF0aW9uLWNhcC5hbGxAaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0LWll
dGYtb3NwZi1lbmNhcHN1bGF0aW9uLWNhcC5hbGxAaWV0Zi5vcmc+IiA8ZHJhZnQtaWV0Zi1vc3Bm
LWVuY2Fwc3VsYXRpb24tY2FwLmFsbEBpZXRmLm9yZzxtYWlsdG86ZHJhZnQtaWV0Zi1vc3BmLWVu
Y2Fwc3VsYXRpb24tY2FwLmFsbEBpZXRmLm9yZz4+LCAiaWV0ZkBpZXRmLm9yZzxtYWlsdG86aWV0
ZkBpZXRmLm9yZz4iIDxpZXRmQGlldGYub3JnPG1haWx0bzppZXRmQGlldGYub3JnPj4NClN1Ympl
Y3Q6IFJlOiDnrZTlpI06IEdlbmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtb3Nw
Zi1lbmNhcHN1bGF0aW9uLWNhcC0wNg0KUmVzZW50LUZyb206IDxhbGlhcy1ib3VuY2VzQGlldGYu
b3JnPG1haWx0bzphbGlhcy1ib3VuY2VzQGlldGYub3JnPj4NClJlc2VudC1UbzogWGlhb2h1IFh1
IDx4dXhpYW9odUBodWF3ZWkuY29tPG1haWx0bzp4dXhpYW9odUBodWF3ZWkuY29tPj4sIEJydW5v
IERlY3JhZW5lIDxicnVuby5kZWNyYWVuZUBvcmFuZ2UuY29tPG1haWx0bzpicnVuby5kZWNyYWVu
ZUBvcmFuZ2UuY29tPj4sIFJvYmVydCBSYXN6dWsgPHJvYmVydEByYXN6dWsubmV0PG1haWx0bzpy
b2JlcnRAcmFzenVrLm5ldD4+LCBMdWlzIENvbnRyZXJhcyA8bHVpc21pZ3VlbC5jb250cmVyYXNt
dXJpbGxvQHRlbGVmb25pY2EuY29tPG1haWx0bzpsdWlzbWlndWVsLmNvbnRyZXJhc211cmlsbG9A
dGVsZWZvbmljYS5jb20+PiwgTHVheSBKYWxpbCA8bHVheS5qYWxpbEB2ZXJpem9uLmNvbTxtYWls
dG86bHVheS5qYWxpbEB2ZXJpem9uLmNvbT4+LCBBY2VlIExpbmRlbSA8YWNlZUBjaXNjby5jb208
bWFpbHRvOmFjZWVAY2lzY28uY29tPj4sIDxha3JAY2lzY28uY29tPG1haWx0bzpha3JAY2lzY28u
Y29tPj4sIDxhcmV0YW5hQGNpc2NvLmNvbTxtYWlsdG86YXJldGFuYUBjaXNjby5jb20+PiwgRGVi
b3JhaCBCcnVuZ2FyZCA8ZGIzNTQ2QGF0dC5jb208bWFpbHRvOmRiMzU0NkBhdHQuY29tPj4sIEFs
aWEgQXRsYXMgPGFrYXRsYXNAZ21haWwuY29tPG1haWx0bzpha2F0bGFzQGdtYWlsLmNvbT4+LCBB
Y2VlIExpbmRlbSA8YWNlZUBjaXNjby5jb208bWFpbHRvOmFjZWVAY2lzY28uY29tPj4NClJlc2Vu
dC1EYXRlOiBUaHVyc2RheSwgQXVndXN0IDI0LCAyMDE3IGF0IDM6NTkgUE0NCg0KDQpPbiAyNCBB
dWcgMjAxNywgYXQgMTE6MjQsIEFjZWUgTGluZGVtIChhY2VlKSB3cm90ZToNCg0KRm9yIDEsIDIs
IDYsIGFuZCA3LCB0aGF0J3MgZWFzeTsgdGhlIGRyYWZ0cyBkZWZpbmluZyB0aGUgdmFsdWVzIGNh
biBkbw0KdGhlIHJlZ2lzdHJhdGlvbnMuIEZvciA1LCB0aGUgcmVmZXJlbmNlIHdvdWxkIGJlIHRv
IGFuIGV4aXN0aW5nIFJGQw0KdGhhdCBkb2Vzbid0IGRvIHRoZSByZWdpc3RyYXRpb24uIEknbSBu
b3Qgc3VyZSB3aGF0IHRvIGRvIGFib3V0IHRoYXQ7DQpwZXJoYXBzIHJlZ2lzdGVyIGl0IGhlcmUg
YW5kIG1ha2UgdGhlIHJlZmVyZW5jZSBib3RoIDU2NDAgYW5kIHRoaXMNCg0KZG9jdW1lbnQuDQoN
CkFjdHVhbGx5LCB0aGlzIGRvY3VtZW50IGRvZXMgYXNzaWduIHRoZXNlIGNvZGUgcG9pbnRzIGlu
IHRoZSByZWdpc3RyeSBzbw0K4oCcVGhpcyBkb2N1bWVudOKAnSBpcyBhcHByb3ByaWF0ZS4gVGhl
IHZhbHVlIHBvcnRpb24gb2YgdGhlc2UgVExWcyBqdXN0DQpoYXBwZW5lZCB0byBiZSBkZXNjcmli
ZWQgdmlhIGEgcmVmZXJlbmNlIHJhdGhlciB0aGFuIHRleHQuDQoNClRoZXJlIGlzIG5vdGhpbmcg
cHJldmVudGluZyB0aGUgSUFOQSByZWdpc3RyeSBmcm9tIGhhdmluZyB1c2VmdWwgaW5mb3JtYXRp
b24uIDotKSBZZXMsIHRoaXMgZG9jdW1lbnQgcmVnaXN0ZXJzIGl0LCBidXQgcmVhbGx5IHdoYXQg
dGhlIGltcGxlbWVudGVyIGlzIGdvaW5nIHRvIG5lZWQgaXMgdGhpcyBkb2N1bWVudCBhbmQgNTY0
MCwgc28gSSBzZWUgbm8gcGFydGljdWxhciBoYXJtIGluIHB1dHRpbmcgYm90aCByZWZlcmVuY2Vz
IGluIHRoZSByZWdpc3RyeSwgYW5kIGl0J3MgcHJvYmFibHkgdXNlZnVsLg0KDQpPayDigJMgSSB0
aGluayBJIGZvdW5kIGFuIGV4YW1wbGUgb2Ygd2hlcmUgc29tZXRoaW5nIGxpa2UgdGhpcyB3YXMg
ZG9uZSAoYWx0aG91Z2ggb25seSBmb3IgSVMtSVMgVExWcyA7XikuDQoNCmh0dHBzOi8vd3d3Lmlh
bmEub3JnL2Fzc2lnbm1lbnRzL2JncC1scy1wYXJhbWV0ZXJzL2JncC1scy1wYXJhbWV0ZXJzLnho
dG1sI25vZGUtZGVzY3JpcHRvci1saW5rLWRlc2NyaXB0b3ItcHJlZml4LWRlc2NyaXB0b3ItYXR0
cmlidXRlLXRsdg0KDQpBdXRob3JzIOKAkyBjYW4geW91IGNyb3NzLXJlZmVyZW5jZSB0aGUgZG9j
dW1lbnQgZGVmaW5pbmcgdGhlIHZhbHVlIGluIHRoZSB0YWJsZT8gV2XigJlyZSBub3QgZ29pbmcg
dG8gbW92ZSBhbnkgSUFOQSBhbGxvY2F0aW9ucy4NCg0KVGhhbmtzLA0KQWNlZQ0KDQoNCg0KDQpw
cg0KLS0NClBldGUgUmVzbmljayBodHRwOi8vd3d3LnF1YWxjb21tLmNvbS9+cHJlc25pY2svPGh0
dHA6Ly93d3cucXVhbGNvbW0uY29tLyU3RXByZXNuaWNrLz4NClF1YWxjb21tIFRlY2hub2xvZ2ll
cywgSW5jLiAtICsxICg4NTgpNjUxLTQ0NzgNCg==

--_000_D5C4B41BC3926aceeciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <0CC2C4A131ECE1438AB307F88506BC68@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj48YnI+DQo8L2Rp
dj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8c3BhbiBpZD0iT0xLX1NSQ19CT0RZX1NFQ1RJT04iPg0K
PGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6Q2FsaWJyaTsgZm9udC1zaXplOjExcHQ7IHRleHQtYWxp
Z246bGVmdDsgY29sb3I6YmxhY2s7IEJPUkRFUi1CT1RUT006IG1lZGl1bSBub25lOyBCT1JERVIt
TEVGVDogbWVkaXVtIG5vbmU7IFBBRERJTkctQk9UVE9NOiAwaW47IFBBRERJTkctTEVGVDogMGlu
OyBQQURESU5HLVJJR0hUOiAwaW47IEJPUkRFUi1UT1A6ICNiNWM0ZGYgMXB0IHNvbGlkOyBCT1JE
RVItUklHSFQ6IG1lZGl1bSBub25lOyBQQURESU5HLVRPUDogM3B0Ij4NCjxzcGFuIHN0eWxlPSJm
b250LXdlaWdodDpib2xkIj5Gcm9tOiA8L3NwYW4+UGV0ZSBSZXNuaWNrICZsdDs8YSBocmVmPSJt
YWlsdG86cHJlc25pY2tAcXRpLnF1YWxjb21tLmNvbSI+cHJlc25pY2tAcXRpLnF1YWxjb21tLmNv
bTwvYT4mZ3Q7PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPkRhdGU6IDwvc3Bh
bj5UaHVyc2RheSwgQXVndXN0IDI0LCAyMDE3IGF0IDM6NTkgUE08YnI+DQo8c3BhbiBzdHlsZT0i
Zm9udC13ZWlnaHQ6Ym9sZCI+VG86IDwvc3Bhbj5BY2VlIExpbmRlbSAmbHQ7PGEgaHJlZj0ibWFp
bHRvOmFjZWVAY2lzY28uY29tIj5hY2VlQGNpc2NvLmNvbTwvYT4mZ3Q7PGJyPg0KPHNwYW4gc3R5
bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPkNjOiA8L3NwYW4+WGlhb2h1IFh1ICZsdDs8YSBocmVmPSJt
YWlsdG86eHV4aWFvaHVAaHVhd2VpLmNvbSI+eHV4aWFvaHVAaHVhd2VpLmNvbTwvYT4mZ3Q7LCAm
cXVvdDs8YSBocmVmPSJtYWlsdG86Z2VuLWFydEBpZXRmLm9yZyI+Z2VuLWFydEBpZXRmLm9yZzwv
YT4mcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpnZW4tYXJ0QGlldGYub3JnIj5nZW4tYXJ0QGll
dGYub3JnPC9hPiZndDssIE9TUEYgV0cgTGlzdCAmbHQ7PGEgaHJlZj0ibWFpbHRvOm9zcGZAaWV0
Zi5vcmciPm9zcGZAaWV0Zi5vcmc8L2E+Jmd0OywNCiAmcXVvdDs8YSBocmVmPSJtYWlsdG86ZHJh
ZnQtaWV0Zi1vc3BmLWVuY2Fwc3VsYXRpb24tY2FwLmFsbEBpZXRmLm9yZyI+ZHJhZnQtaWV0Zi1v
c3BmLWVuY2Fwc3VsYXRpb24tY2FwLmFsbEBpZXRmLm9yZzwvYT4mcXVvdDsgJmx0OzxhIGhyZWY9
Im1haWx0bzpkcmFmdC1pZXRmLW9zcGYtZW5jYXBzdWxhdGlvbi1jYXAuYWxsQGlldGYub3JnIj5k
cmFmdC1pZXRmLW9zcGYtZW5jYXBzdWxhdGlvbi1jYXAuYWxsQGlldGYub3JnPC9hPiZndDssICZx
dW90OzxhIGhyZWY9Im1haWx0bzppZXRmQGlldGYub3JnIj5pZXRmQGlldGYub3JnPC9hPiZxdW90
Ow0KICZsdDs8YSBocmVmPSJtYWlsdG86aWV0ZkBpZXRmLm9yZyI+aWV0ZkBpZXRmLm9yZzwvYT4m
Z3Q7PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPlN1YmplY3Q6IDwvc3Bhbj5S
ZTog562U5aSNOiBHZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLW9zcGYtZW5j
YXBzdWxhdGlvbi1jYXAtMDY8YnI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+UmVz
ZW50LUZyb206IDwvc3Bhbj4mbHQ7PGEgaHJlZj0ibWFpbHRvOmFsaWFzLWJvdW5jZXNAaWV0Zi5v
cmciPmFsaWFzLWJvdW5jZXNAaWV0Zi5vcmc8L2E+Jmd0Ozxicj4NCjxzcGFuIHN0eWxlPSJmb250
LXdlaWdodDpib2xkIj5SZXNlbnQtVG86IDwvc3Bhbj5YaWFvaHUgWHUgJmx0OzxhIGhyZWY9Im1h
aWx0bzp4dXhpYW9odUBodWF3ZWkuY29tIj54dXhpYW9odUBodWF3ZWkuY29tPC9hPiZndDssIEJy
dW5vIERlY3JhZW5lICZsdDs8YSBocmVmPSJtYWlsdG86YnJ1bm8uZGVjcmFlbmVAb3JhbmdlLmNv
bSI+YnJ1bm8uZGVjcmFlbmVAb3JhbmdlLmNvbTwvYT4mZ3Q7LCBSb2JlcnQgUmFzenVrICZsdDs8
YSBocmVmPSJtYWlsdG86cm9iZXJ0QHJhc3p1ay5uZXQiPnJvYmVydEByYXN6dWsubmV0PC9hPiZn
dDssDQogTHVpcyBDb250cmVyYXMgJmx0OzxhIGhyZWY9Im1haWx0bzpsdWlzbWlndWVsLmNvbnRy
ZXJhc211cmlsbG9AdGVsZWZvbmljYS5jb20iPmx1aXNtaWd1ZWwuY29udHJlcmFzbXVyaWxsb0B0
ZWxlZm9uaWNhLmNvbTwvYT4mZ3Q7LCBMdWF5IEphbGlsICZsdDs8YSBocmVmPSJtYWlsdG86bHVh
eS5qYWxpbEB2ZXJpem9uLmNvbSI+bHVheS5qYWxpbEB2ZXJpem9uLmNvbTwvYT4mZ3Q7LCBBY2Vl
IExpbmRlbSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFjZWVAY2lzY28uY29tIj5hY2VlQGNpc2NvLmNv
bTwvYT4mZ3Q7LA0KICZsdDs8YSBocmVmPSJtYWlsdG86YWtyQGNpc2NvLmNvbSI+YWtyQGNpc2Nv
LmNvbTwvYT4mZ3Q7LCAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFyZXRhbmFAY2lzY28uY29tIj5hcmV0
YW5hQGNpc2NvLmNvbTwvYT4mZ3Q7LCBEZWJvcmFoIEJydW5nYXJkICZsdDs8YSBocmVmPSJtYWls
dG86ZGIzNTQ2QGF0dC5jb20iPmRiMzU0NkBhdHQuY29tPC9hPiZndDssIEFsaWEgQXRsYXMgJmx0
OzxhIGhyZWY9Im1haWx0bzpha2F0bGFzQGdtYWlsLmNvbSI+YWthdGxhc0BnbWFpbC5jb208L2E+
Jmd0OywgQWNlZQ0KIExpbmRlbSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFjZWVAY2lzY28uY29tIj5h
Y2VlQGNpc2NvLmNvbTwvYT4mZ3Q7PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQi
PlJlc2VudC1EYXRlOiA8L3NwYW4+VGh1cnNkYXksIEF1Z3VzdCAyNCwgMjAxNyBhdCAzOjU5IFBN
PGJyPg0KPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgaWQ9Ik1BQ19PVVRM
T09LX0FUVFJJQlVUSU9OX0JMT0NLUVVPVEUiIHN0eWxlPSJCT1JERVItTEVGVDogI2I1YzRkZiA1
IHNvbGlkOyBQQURESU5HOjAgMCAwIDU7IE1BUkdJTjowIDAgMCA1OyI+DQo8ZGl2Pg0KPGRpdj4N
CjxkaXYgc3R5bGU9ImZvbnQtZmFtaWx5OnNhbnMtc2VyaWYiPg0KPGRpdiBzdHlsZT0id2hpdGUt
c3BhY2U6bm9ybWFsIj4NCjxwIGRpcj0iYXV0byI+T24gMjQgQXVnIDIwMTcsIGF0IDExOjI0LCBB
Y2VlIExpbmRlbSAoYWNlZSkgd3JvdGU6PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlci1s
ZWZ0OjJweCBzb2xpZCAjNzc3OyBjb2xvcjojNzc3OyBtYXJnaW46MCAwIDVweDsgcGFkZGluZy1s
ZWZ0OjVweCI+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyLWxlZnQ6MnB4IHNvbGlkICM3Nzc7
IGNvbG9yOiM5OTk7IG1hcmdpbjowIDAgNXB4OyBwYWRkaW5nLWxlZnQ6NXB4OyBib3JkZXItbGVm
dC1jb2xvcjojOTk5Ij4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXItbGVmdDoycHggc29saWQg
Izc3NzsgY29sb3I6I0JCQjsgbWFyZ2luOjAgMCA1cHg7IHBhZGRpbmctbGVmdDo1cHg7IGJvcmRl
ci1sZWZ0LWNvbG9yOiNCQkIiPg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlci1sZWZ0OjJweCBz
b2xpZCAjNzc3OyBjb2xvcjojQkJCOyBtYXJnaW46MCAwIDVweDsgcGFkZGluZy1sZWZ0OjVweDsg
Ym9yZGVyLWxlZnQtY29sb3I6I0JCQiI+DQo8cCBkaXI9ImF1dG8iPkZvciAxLCAyLCA2LCBhbmQg
NywgdGhhdCdzIGVhc3k7IHRoZSBkcmFmdHMgZGVmaW5pbmcgdGhlIHZhbHVlcyBjYW4gZG88YnI+
DQp0aGUgcmVnaXN0cmF0aW9ucy4gRm9yIDUsIHRoZSByZWZlcmVuY2Ugd291bGQgYmUgdG8gYW4g
ZXhpc3RpbmcgUkZDPGJyPg0KdGhhdCBkb2Vzbid0IGRvIHRoZSByZWdpc3RyYXRpb24uIEknbSBu
b3Qgc3VyZSB3aGF0IHRvIGRvIGFib3V0IHRoYXQ7PGJyPg0KcGVyaGFwcyByZWdpc3RlciBpdCBo
ZXJlIGFuZCBtYWtlIHRoZSByZWZlcmVuY2UgYm90aCA1NjQwIGFuZCB0aGlzPC9wPg0KPC9ibG9j
a3F1b3RlPg0KPHAgZGlyPSJhdXRvIj5kb2N1bWVudC48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Js
b2NrcXVvdGU+DQo8cCBkaXI9ImF1dG8iPkFjdHVhbGx5LCB0aGlzIGRvY3VtZW50IGRvZXMgYXNz
aWduIHRoZXNlIGNvZGUgcG9pbnRzIGluIHRoZSByZWdpc3RyeSBzbzxicj4NCuKAnFRoaXMgZG9j
dW1lbnTigJ0gaXMgYXBwcm9wcmlhdGUuIFRoZSB2YWx1ZSBwb3J0aW9uIG9mIHRoZXNlIFRMVnMg
anVzdDxicj4NCmhhcHBlbmVkIHRvIGJlIGRlc2NyaWJlZCB2aWEgYSByZWZlcmVuY2UgcmF0aGVy
IHRoYW4gdGV4dC48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8cCBkaXI9ImF1dG8iPlRoZXJlIGlzIG5v
dGhpbmcgcHJldmVudGluZyB0aGUgSUFOQSByZWdpc3RyeSBmcm9tIGhhdmluZyB1c2VmdWwgaW5m
b3JtYXRpb24uIDotKSBZZXMsIHRoaXMgZG9jdW1lbnQgcmVnaXN0ZXJzIGl0LCBidXQgcmVhbGx5
IHdoYXQgdGhlIGltcGxlbWVudGVyIGlzIGdvaW5nIHRvIG5lZWQgaXMgdGhpcyBkb2N1bWVudA0K
PGVtPmFuZDwvZW0+IDU2NDAsIHNvIEkgc2VlIG5vIHBhcnRpY3VsYXIgaGFybSBpbiBwdXR0aW5n
IGJvdGggcmVmZXJlbmNlcyBpbiB0aGUgcmVnaXN0cnksIGFuZCBpdCdzIHByb2JhYmx5IHVzZWZ1
bC48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwv
c3Bhbj4NCjxkaXY+T2sg4oCTIEkgdGhpbmsgSSBmb3VuZCBhbiBleGFtcGxlIG9mIHdoZXJlIHNv
bWV0aGluZyBsaWtlIHRoaXMgd2FzIGRvbmUgKGFsdGhvdWdoIG9ubHkgZm9yIElTLUlTIFRMVnMg
O14pLiZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PGEgaHJlZj0iaHR0cHM6
Ly93d3cuaWFuYS5vcmcvYXNzaWdubWVudHMvYmdwLWxzLXBhcmFtZXRlcnMvYmdwLWxzLXBhcmFt
ZXRlcnMueGh0bWwjbm9kZS1kZXNjcmlwdG9yLWxpbmstZGVzY3JpcHRvci1wcmVmaXgtZGVzY3Jp
cHRvci1hdHRyaWJ1dGUtdGx2Ij5odHRwczovL3d3dy5pYW5hLm9yZy9hc3NpZ25tZW50cy9iZ3At
bHMtcGFyYW1ldGVycy9iZ3AtbHMtcGFyYW1ldGVycy54aHRtbCNub2RlLWRlc2NyaXB0b3ItbGlu
ay1kZXNjcmlwdG9yLXByZWZpeC1kZXNjcmlwdG9yLWF0dHJpYnV0ZS10bHY8L2E+PC9kaXY+DQo8
ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5BdXRob3JzIOKAkyBjYW4geW91IGNyb3NzLXJlZmVyZW5j
ZSB0aGUgZG9jdW1lbnQgZGVmaW5pbmcgdGhlIHZhbHVlIGluIHRoZSB0YWJsZT8gV2XigJlyZSBu
b3QgZ29pbmcgdG8gbW92ZSBhbnkgSUFOQSBhbGxvY2F0aW9ucy4mbmJzcDs8L2Rpdj4NCjxkaXY+
PGJyPg0KPC9kaXY+DQo8ZGl2PlRoYW5rcyw8L2Rpdj4NCjxkaXY+QWNlZSZuYnNwOzwvZGl2Pg0K
PGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0K
PHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9TRUNUSU9OIj4NCjxibG9ja3F1b3RlIGlkPSJNQUNfT1VU
TE9PS19BVFRSSUJVVElPTl9CTE9DS1FVT1RFIiBzdHlsZT0iQk9SREVSLUxFRlQ6ICNiNWM0ZGYg
NSBzb2xpZDsgUEFERElORzowIDAgMCA1OyBNQVJHSU46MCAwIDAgNTsiPg0KPGRpdj4NCjxkaXY+
DQo8ZGl2IHN0eWxlPSJmb250LWZhbWlseTpzYW5zLXNlcmlmIj4NCjxkaXYgc3R5bGU9IndoaXRl
LXNwYWNlOm5vcm1hbCI+DQo8cCBkaXI9ImF1dG8iPnByPGJyPg0KLS0gPGJyPg0KUGV0ZSBSZXNu
aWNrIDxhIGhyZWY9Imh0dHA6Ly93d3cucXVhbGNvbW0uY29tLyU3RXByZXNuaWNrLyIgc3R5bGU9
ImNvbG9yOiMzOTgzQzQiPg0KaHR0cDovL3d3dy5xdWFsY29tbS5jb20vfnByZXNuaWNrLzwvYT48
YnI+DQpRdWFsY29tbSBUZWNobm9sb2dpZXMsIEluYy4gLSAmIzQzOzEgKDg1OCk2NTEtNDQ3ODwv
cD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9zcGFu
Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_D5C4B41BC3926aceeciscocom_--


From nobody Thu Aug 24 15:04:24 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73839132441 for <ietf@ietfa.amsl.com>; Thu, 24 Aug 2017 15:04:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e8yNBK7DqwZ7 for <ietf@ietfa.amsl.com>; Thu, 24 Aug 2017 15:04:19 -0700 (PDT)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5108913235C for <ietf@ietf.org>; Thu, 24 Aug 2017 15:04:19 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id y15so3245568lfd.0 for <ietf@ietf.org>; Thu, 24 Aug 2017 15:04:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=qmdJozAoWxlDQ9c94DlrhM54lsY6IQzNwyLNo5dMbTo=; b=m3kM5Upz6Nvb2FT8iP7JGFT3QfvVS3FXfKDiE/nUZyp8/oIxCJWFTRAvLfOAfp4KVg N6lWW/K3AYiH6SKKZ5UkrwC5FoYHAuhLYPlbUb3VfWS6ep0DEzcSt5Sz2YYXfkBzzMq+ 571KsC/PXS6PrD7Is3yeo92Hy+TDYKSWnRKF7XU0/TIJXIchR8mejtx+bEBMf/A4QCK4 FM1ozWgBaqJL3hIaigBFqH9cNMYQiIBcgLyuTIMMHzcxsUV1fhflZZFs4sPk4k7seEIP GVDXtuhapmCPwoz6747FXOJa02cLspZS25O3Yqs5sF6vivZWoQzm0UMouU+znMLpqc0H jxog==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=qmdJozAoWxlDQ9c94DlrhM54lsY6IQzNwyLNo5dMbTo=; b=QlRYge5gKZJB0Q2S909wwsD/r3OsRqgwteJVK4xHmPzbN7JsL12vbCShdUo6knCllY pLd/PNKbltngBQK2IHTutwXM8pDQqmW3AKAVj7ZDvkGOa7kZewsO4tJBTsEc0SQGfEkm H4Zdrv/3LPF3xFXJE1JHdyM2OGrohws8qU/BgkjNRMi61sOeQ/tzhbaEb7mna+hDf87o doOAPk+Ymy814QhXTlOIlxco8XLvS4mkQuvs5zGyw8kssK5iogXpknE/NBXpG8AsSG0g zkjjjtYTXzSjfOYeRI+QdCuKoG+WNgX0gbAlYuNLusl3y4h/pz5U9NAYGaxmkfPiNRO+ P0mw==
X-Gm-Message-State: AHYfb5gy9MwigW5YVxXnOrtg5czFx8yQdFeqjOe0wzzL3rmRLT6ZWW1e baWUywEfgUl+VUGS3XVrb8pz9gi6qQ==
X-Received: by 10.25.168.144 with SMTP id r138mr3049623lfe.15.1503612257526; Thu, 24 Aug 2017 15:04:17 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.25.142.199 with HTTP; Thu, 24 Aug 2017 15:04:16 -0700 (PDT)
In-Reply-To: <E472D28FF44BD58F88258ACC@PSB>
References: <20170821170258.GA21915@faui40p.informatik.uni-erlangen.de> <E472D28FF44BD58F88258ACC@PSB>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 24 Aug 2017 18:04:16 -0400
X-Google-Sender-Auth: ZR1zONijfT3QxuH5vX4Cr2fHsZ0
Message-ID: <CAMm+LwjNy4YS=cuW93zcy6Snp_jiTZ3jYLPAPqdUvyeVEreARw@mail.gmail.com>
Subject: Re: Email client APIs. features. amd siupport (was: Re: Scope for self-destructing email?)
To: John C Klensin <john-ietf@jck.com>
Cc: Toerless Eckert <tte@cs.fau.de>, vaibhav singh <vaibhavsinghacads@gmail.com>,  IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a114113107d69ed05578702b4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dfVY5z69pd21E2pTIUcy-EuMLjU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Aug 2017 22:04:22 -0000

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

On Tue, Aug 22, 2017 at 10:10 AM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Monday, August 21, 2017 19:02 +0200 Toerless Eckert
> <tte@cs.fau.de> wrote:
>
> > John,
> >
> > I did like to use a couple of those nice email functions driven
> > by special headers. IMHO the main reason why those never
> > catched on is the absence of easy ways for users to figure out
> > how much their software (MTU/MUA) sucks.
> >
> > One thing IMHO that would help are mechanisms to provide users
> > with an easy ability to learn what their software is claiming
> > to support, and what's missing. User experience should be some
> > web-page that explains this to the user in easy terms and
> > ideally even suggests to create RFE emails to the vendors. The
> > question would then be what standards APIs one would need to
> > enable interested third parties to generate such web pages
> > (including IETF).
> >...
>
> Interesting idea, but a very different discussion (hence the
> change of subject lines).   As you know, the IETF has tended to
> avoid API specifications, largely because we have preferred
> performance standards (i.e., "this is what you need to do and
> support") to implementation ones ("this is the API, probably
> expressed on code or pseudocode, all you need to do is call
> it").  We've also tended to focus on what happens or is
> transmitted on the wire between machines rather than how and
> what things are dong or implemented before the bits leave a
> source system or after they get to a destination one.    In
> addition, many people have argued strongly that we should,
> insofar as possible, stay out of the UI business, in part
> because the IETF, as a community, demonstrably has no skill in
> the area.
>

=E2=80=8BAs you say later, this sort of thing needs regular review. As we g=
o up the
stack, the difference between an API and a protocol quickly blurs and
eventually vanishes. =E2=80=8B

=E2=80=8BProtogen is a tool I use to generate protocol specifications and r=
eference
code from a common schema. It is similar in concept to YANG except being
designed to be used at a much higher level. Here is an example of a
specification written using it:

http://prismproof.org/Documents/draft-hallambaker-mesh-confirm.html=E2=80=
=8B

=E2=80=8BThe API for the client library and server dispatch methods is =E2=
=80=8Bgenerated
from the same schema that generated the documentation. So a protocol
specification is an API.

This is not the case for most IETF specs, of course, not even application
specs. The 'cost' of doing that is that many of the choices that protocol
designers often make are fixed:

* Encoding, is JSON
=E2=80=8B* Discovery is SRV
* =E2=80=8BPresentation is HTTP

=E2=80=8BI believe that making these choices consistent improves the spec. =
=E2=80=8B


=E2=80=8BThe API is not the same as the user experience of course. But the =
design
of an application protocol is =E2=80=8Bmostly a choice of

* Which information to store at the client vs the server
* The ways the information is to be indexed at the server

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Au=
g 22, 2017 at 10:10 AM, John C Klensin <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:john-ietf@jck.com" target=3D"_blank">john-ietf@jck.com</a>&gt;</span> w=
rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
--On Monday, August 21, 2017 19:02 +0200 Toerless Eckert<br>
&lt;<a href=3D"mailto:tte@cs.fau.de">tte@cs.fau.de</a>&gt; wrote:<br>
<br>
&gt; John,<br>
&gt;<br>
&gt; I did like to use a couple of those nice email functions driven<br>
&gt; by special headers. IMHO the main reason why those never<br>
&gt; catched on is the absence of easy ways for users to figure out<br>
&gt; how much their software (MTU/MUA) sucks.<br>
&gt;<br>
&gt; One thing IMHO that would help are mechanisms to provide users<br>
&gt; with an easy ability to learn what their software is claiming<br>
&gt; to support, and what&#39;s missing. User experience should be some<br>
&gt; web-page that explains this to the user in easy terms and<br>
&gt; ideally even suggests to create RFE emails to the vendors. The<br>
&gt; question would then be what standards APIs one would need to<br>
&gt; enable interested third parties to generate such web pages<br>
&gt; (including IETF).<br>
&gt;...<br>
<br>
Interesting idea, but a very different discussion (hence the<br>
change of subject lines).=C2=A0 =C2=A0As you know, the IETF has tended to<b=
r>
avoid API specifications, largely because we have preferred<br>
performance standards (i.e., &quot;this is what you need to do and<br>
support&quot;) to implementation ones (&quot;this is the API, probably<br>
expressed on code or pseudocode, all you need to do is call<br>
it&quot;).=C2=A0 We&#39;ve also tended to focus on what happens or is<br>
transmitted on the wire between machines rather than how and<br>
what things are dong or implemented before the bits leave a<br>
source system or after they get to a destination one.=C2=A0 =C2=A0 In<br>
addition, many people have argued strongly that we should,<br>
insofar as possible, stay out of the UI business, in part<br>
because the IETF, as a community, demonstrably has no skill in<br>
the area.<br></blockquote><div><br></div><div><div class=3D"gmail_default" =
style=3D"font-size:small">=E2=80=8BAs you say later, this sort of thing nee=
ds regular review. As we go up the stack, the difference between an API and=
 a protocol quickly blurs and eventually vanishes. =E2=80=8B</div><br></div=
><div><div class=3D"gmail_default" style=3D"font-size:small">=E2=80=8BProto=
gen is a tool I use to generate protocol specifications and reference code =
from a common schema. It is similar in concept to YANG except being designe=
d to be used at a much higher level. Here is an example of a specification =
written using it:</div><div class=3D"gmail_default" style=3D"font-size:smal=
l"><br></div><div class=3D"gmail_default" style=3D"font-size:small"><a href=
=3D"http://prismproof.org/Documents/draft-hallambaker-mesh-confirm.html">ht=
tp://prismproof.org/Documents/draft-hallambaker-mesh-confirm.html</a>=E2=80=
=8B</div><br></div><div><div class=3D"gmail_default" style=3D"font-size:sma=
ll">=E2=80=8BThe API for the client library and server dispatch methods is =
=E2=80=8Bgenerated from the same schema that generated the documentation. S=
o a protocol specification is an API.</div><div class=3D"gmail_default" sty=
le=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"font=
-size:small">This is not the case for most IETF specs, of course, not even =
application specs. The &#39;cost&#39; of doing that is that many of the cho=
ices that protocol designers often make are fixed:</div><div class=3D"gmail=
_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default" =
style=3D"font-size:small">* Encoding, is JSON</div><div class=3D"gmail_defa=
ult" style=3D"font-size:small">=E2=80=8B* Discovery is SRV</div><div class=
=3D"gmail_default" style=3D"font-size:small">* =E2=80=8BPresentation is HTT=
P</div><br></div><div><div class=3D"gmail_default" style=3D"font-size:small=
">=E2=80=8BI believe that making these choices consistent improves the spec=
. =E2=80=8B</div><br></div><div><br></div><div class=3D"gmail_default" styl=
e=3D"font-size:small">=E2=80=8BThe API is not the same as the user experien=
ce of course. But the design of an application protocol is =E2=80=8Bmostly =
a choice of</div><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_default" style=3D"font-size:small">* Which infor=
mation to store at the client vs the server</div><div class=3D"gmail_defaul=
t" style=3D"font-size:small">* The ways the information is to be indexed at=
 the server</div><div><br></div><div><br></div><div>=C2=A0</div></div></div=
></div>

--001a114113107d69ed05578702b4--


From nobody Thu Aug 24 19:11:16 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 785121329FB for <ietf@ietfa.amsl.com>; Thu, 24 Aug 2017 19:11:14 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LdhHb6E0pHTS for <ietf@ietfa.amsl.com>; Thu, 24 Aug 2017 19:11:13 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04C551329F9 for <ietf@ietf.org>; Thu, 24 Aug 2017 19:11:12 -0700 (PDT)
Received: (qmail 62849 invoked from network); 25 Aug 2017 02:11:12 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 25 Aug 2017 02:11:12 -0000
Date: 25 Aug 2017 02:10:50 -0000
Message-ID: <20170825021050.23850.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: big files of mail, was Next steps in IETF list email archiving
In-Reply-To: <67C32DB4-E5CF-4042-9F10-50C3AF072919@orthanc.ca>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nV1rtuKecPAD0zdSsYUIKlvKzDU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Aug 2017 02:11:14 -0000

In article <67C32DB4-E5CF-4042-9F10-50C3AF072919@orthanc.ca> you write:
>
>> On Aug 24, 2017, at 8:22 AM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
>> 
>> I think the problem is that many people would like to suck the archives back
>> in bulk, and they see IMAP as too chatty.
>
>I don't think that's a valid argument.

We have mbox-ish archives available via wget and rsync, and have for
many years.  It is my impression that they are maintained
automatically and are not going away.  So if you want to do bulk
fetches via IMAP, that's fine, but anyone who wants to do it with
rsync will continue to do so.

I did, took a while but I got lots and lots of files of messages, and it
had the advantage of being a one-line command, no new programming needed.

R's,
John


From nobody Thu Aug 24 19:38:55 2017
Return-Path: <lyndon@orthanc.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EB07132A02 for <ietf@ietfa.amsl.com>; Thu, 24 Aug 2017 19:38:54 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VMXOd2G3--kG for <ietf@ietfa.amsl.com>; Thu, 24 Aug 2017 19:38:52 -0700 (PDT)
Received: from orthanc.ca (orthanc.ca [IPv6:2607:f2f8:abf8::2]) (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 9D0781329F7 for <ietf@ietf.org>; Thu, 24 Aug 2017 19:38:52 -0700 (PDT)
Received: from minnie.hitronhub.home (S0106a84e3f81a003.vc.shawcable.net [24.80.126.119]) (authenticated bits=0) by orthanc.ca (8.15.2/8.15.2) with ESMTPSA id v7P2cp31076974 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Thu, 24 Aug 2017 19:38:52 -0700 (PDT) (envelope-from lyndon@orthanc.ca)
From: Lyndon Nerenberg <lyndon@orthanc.ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: big files of mail, was Next steps in IETF list email archiving
Date: Thu, 24 Aug 2017 19:38:45 -0700
References: <20170825021050.23850.qmail@ary.lan>
To: IETF general list <ietf@ietf.org>
In-Reply-To: <20170825021050.23850.qmail@ary.lan>
Message-Id: <54ED5403-ECBF-40B7-84CB-459BF348EF20@orthanc.ca>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KYhFvihNC6M48BA_xZt1HI41MwE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Aug 2017 02:38:54 -0000

> On Aug 24, 2017, at 7:10 PM, John Levine <johnl@taugh.com> wrote:
>=20
> We have mbox-ish archives available via wget and rsync, and have for
> many years.  It is my impression that they are maintained
> automatically and are not going away.  So if you want to do bulk
> fetches via IMAP, that's fine, but anyone who wants to do it with
> rsync will continue to do so.

I agree completely.  I'm just pointing out that there's no standard for =
the various "mailbox archive" formats.  E.g. mbox, MH, maildir.  IMAP =
provides a(n IETF) standard interface.  Maybe not the most efficient in =
this specific case, but beware of micro-optimization.

--lyndon



From nobody Thu Aug 24 21:53:27 2017
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AB2E1321DE for <ietf@ietfa.amsl.com>; Thu, 24 Aug 2017 21:53:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hMNxH72_V8C5 for <ietf@ietfa.amsl.com>; Thu, 24 Aug 2017 21:53:24 -0700 (PDT)
Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) (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 07D35131D27 for <ietf@ietf.org>; Thu, 24 Aug 2017 21:53:23 -0700 (PDT)
Received: from pps.filterd (m0098416.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v7P4n7Vp082169 for <ietf@ietf.org>; Fri, 25 Aug 2017 00:53:21 -0400
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by mx0b-001b2d01.pphosted.com with ESMTP id 2cj7qvk0ya-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 25 Aug 2017 00:53:13 -0400
Received: from localhost by e32.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, 24 Aug 2017 22:53:13 -0600
Received: from b03cxnp07029.gho.boulder.ibm.com (9.17.130.16) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 24 Aug 2017 22:53:10 -0600
Received: from b03ledav005.gho.boulder.ibm.com (b03ledav005.gho.boulder.ibm.com [9.17.130.236]) by b03cxnp07029.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v7P4rA608192412 for <ietf@ietf.org>; Thu, 24 Aug 2017 21:53:10 -0700
Received: from b03ledav005.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 33D31BE03A for <ietf@ietf.org>; Thu, 24 Aug 2017 22:53:10 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b03ledav005.gho.boulder.ibm.com (Postfix) with ESMTPS id 16CF0BE039 for <ietf@ietf.org>; Thu, 24 Aug 2017 22:53:10 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v7P4r8io020331 for <ietf@ietf.org>; Fri, 25 Aug 2017 00:53:09 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v7P4r8nB020313 for ietf@ietf.org; Fri, 25 Aug 2017 00:53:08 -0400
From: narten@us.ibm.com
Date: Fri, 25 Aug 2017 00:53:08 -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-GCONF: 00
x-cbid: 17082504-0004-0000-0000-000012D2B783
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00007607; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000225; SDB=6.00907281; UDB=6.00454820; IPR=6.00687478;  BA=6.00005552; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00016857; XFM=3.00000015; UTC=2017-08-25 04:53:11
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17082504-0005-0000-0000-000080D995D8
Message-Id: <201708250453.v7P4r8nB020313@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-08-25_02:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=2 spamscore=2 suspectscore=13 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1708250071
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6a0V-8ERvhKhwQXdMNNuWuhxnYM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Aug 2017 04:53:26 -0000

Total of 42 messages in the last 7 days.
 
script run at: Fri Aug 25 00:53:08 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 11.90% |    5 | 15.22% |    69679 | acee@cisco.com
  9.52% |    4 |  8.36% |    38302 | tte@cs.fau.de
  9.52% |    4 |  6.57% |    30071 | johnl@taugh.com
  7.14% |    3 |  6.41% |    29346 | presnick@qti.qualcomm.com
  7.14% |    3 |  4.70% |    21507 | lyndon@orthanc.ca
  4.76% |    2 |  5.74% |    26269 | sammia.rauf@gmail.com
  4.76% |    2 |  4.95% |    22657 | touch@strayalpha.com
  2.38% |    1 |  5.95% |    27266 | bew@cisco.com
  2.38% |    1 |  4.27% |    19543 | adrian@olddog.co.uk
  2.38% |    1 |  3.58% |    16401 | phill@hallambaker.com
  2.38% |    1 |  3.46% |    15833 | a@ackl.io
  2.38% |    1 |  2.90% |    13261 | ynir.ietf@gmail.com
  2.38% |    1 |  2.70% |    12365 | dhruv.dhody@huawei.com
  2.38% |    1 |  2.64% |    12073 | john-ietf@jck.com
  2.38% |    1 |  2.62% |    12008 | xuxiaohu@huawei.com
  2.38% |    1 |  2.39% |    10957 | ietf@lmcontreras.com
  2.38% |    1 |  2.33% |    10662 | elwynd@dial.pipex.com
  2.38% |    1 |  2.17% |     9915 | roni.even@huawei.com
  2.38% |    1 |  2.14% |     9819 | dromasca@gmail.com
  2.38% |    1 |  1.94% |     8879 | alexandre.petrescu@gmail.com
  2.38% |    1 |  1.63% |     7462 | cloos@jhcloos.com
  2.38% |    1 |  1.61% |     7395 | mcr+ietf@sandelman.ca
  2.38% |    1 |  1.61% |     7356 | lloyd.wood@yahoo.co.uk
  2.38% |    1 |  1.57% |     7167 | worley@ariadne.com
  2.38% |    1 |  1.50% |     6854 | wes@mti-systems.com
  2.38% |    1 |  1.07% |     4907 | barryleiba@computer.org
--------+------+--------+----------+------------------------
100.00% |   42 |100.00% |   457954 | Total


From nobody Fri Aug 25 03:54:19 2017
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F18B013291F; Fri, 25 Aug 2017 03:53:59 -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, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MQ80H4hBWlpN; Fri, 25 Aug 2017 03:53:57 -0700 (PDT)
Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7623B132BC2; Fri, 25 Aug 2017 03:53:57 -0700 (PDT)
Received: from [192.168.1.204] (p57BB53DA.dip0.t-ipconnect.de [87.187.83.218]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 10711721E281A; Fri, 25 Aug 2017 12:53:53 +0200 (CEST)
From: Michael Tuexen <tuexen@fh-muenster.de>
Message-Id: <2B0B5E2A-0B15-4B86-9226-3129A101EE24@fh-muenster.de>
Content-Type: multipart/signed; boundary="Apple-Mail=_A9D8225C-80BA-41CE-A1C7-811AF7BC68CA"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Genart last call review of draft-ietf-tsvwg-sctp-ndata-12
Date: Fri, 25 Aug 2017 12:53:52 +0200
In-Reply-To: <150274094205.10409.17989486864216331116@ietfa.amsl.com>
Cc: gen-art@ietf.org, tsvwg@ietf.org, ietf@ietf.org, draft-ietf-tsvwg-sctp-ndata.all@ietf.org
To: Stewart Bryant <stewart.bryant@gmail.com>
References: <150274094205.10409.17989486864216331116@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/12AydOBnKVtGXSPJ8KBeqVP5Uec>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Aug 2017 10:54:00 -0000
X-List-Received-Date: Fri, 25 Aug 2017 10:54:00 -0000

--Apple-Mail=_A9D8225C-80BA-41CE-A1C7-811AF7BC68CA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> On 14. Aug 2017, at 22:02, Stewart Bryant <stewart.bryant@gmail.com> =
wrote:
>=20
> Reviewer: Stewart Bryant
> Review result: Ready
>=20
Hi Stewart,

thanks for your review. See my comment in-line.

Best regards
Michael
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-tsvwg-sctp-ndata-12
> Reviewer: Stewart Bryant
> Review Date: 2017-08-14
> IETF LC End Date: 2017-08-25
> IESG Telechat date: Not scheduled for a telechat
>=20
> Summary: This is a well written draft and is ready for publication.
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments:
>=20
> You repeat the text:
>=20
> "A message is considered in flight, if at least  on of its I-DATA =
chunks is not
> acknowledged in a non-renegable way"  in two consecutive sections, =
maybe a
> common definition could be used.
The first text covers "Message in flight", the second covers "Fragment =
in flight".
What is duplicated is the text (i.e. acknowledged by the cumulative TSN =
Ack) for
explaining "acknowledged in a non-renegable way". Giving the explanation =
only once
improves readability, I guess.

Best regards
Michael
>=20


--Apple-Mail=_A9D8225C-80BA-41CE-A1C7-811AF7BC68CA
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIQkDCCBNUw
ggO9oAMCAQICCFBOxvU9EbRkMA0GCSqGSIb3DQEBCwUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQK
ExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMw
IQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0xNDA3MjIxMjA4MjZaFw0xOTA3
MDkyMzU5MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdE
Rk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAx
BAuZgeKmFNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84Ik
Q4wcOItqaACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVg
Te3RCSMqljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sW
VlZDz+HVEz2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjggGG
MIIBgjAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1Ud
IwQYMBaAFDHDeRu69VPXF+CJei0XbAqzK50zMBIGA1UdEwEB/wQIMAYBAf8CAQIwYgYDVR0gBFsw
WTARBg8rBgEEAYGtIYIsAQEEAgIwEQYPKwYBBAGBrSGCLAEBBAMAMBEGDysGAQQBga0hgiwBAQQD
ATAPBg0rBgEEAYGtIYIsAQEEMA0GCysGAQQBga0hgiweMD4GA1UdHwQ3MDUwM6AxoC+GLWh0dHA6
Ly9wa2kwMzM2LnRlbGVzZWMuZGUvcmwvRFRfUk9PVF9DQV8yLmNybDB4BggrBgEFBQcBAQRsMGow
LAYIKwYBBQUHMAGGIGh0dHA6Ly9vY3NwMDMzNi50ZWxlc2VjLmRlL29jc3ByMDoGCCsGAQUFBzAC
hi5odHRwOi8vcGtpMDMzNi50ZWxlc2VjLmRlL2NydC9EVF9ST09UX0NBXzIuY2VyMA0GCSqGSIb3
DQEBCwUAA4IBAQBjICj9nCGGcr45Rlk5MiW8qQGbDczKfUGchm0KbiyzE1l1sTOSG2EnFv/DstU1
gvuEKgFJvWa7Zi+ywgZdbj9u4wFaW8pDY1yVtuExpx/VB19N5mWCTjL5w3x6S81NXHTuIfJ1AuxS
PtLJatOQI25JZzW+f01WpOzML8+3oZeocj7JvEDWWqQIPda8gsO3tzKOsSyOam23NQIZz/U5RFhj
pyQAELC7/E6vbi84u6VXST/YblBvLJeW3B1GmmWJz67M8uXZn1OzPqEvkqnYC8aEHwTG6x7on321
e6UC8STFJGMRNMxakyAqeYg6JUKQqWU7fIbTEhUjKfws2sw5W1QXMIIFojCCBIqgAwIBAgIHF6Qk
oQlIMzANBgkqhkiG9w0BAQsFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQ
MA4GA1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4X
DTE0MDUyNzE0NTQwOVoXDTE5MDcwOTIzNTkwMFowgcYxCzAJBgNVBAYTAkRFMRwwGgYDVQQIExNO
b3JkcmhlaW4tV2VzdGZhbGVuMREwDwYDVQQHEwhNdWVuc3RlcjEgMB4GA1UEChMXRmFjaGhvY2hz
Y2h1bGUgTXVlbnN0ZXIxIzAhBgNVBAsTGkRhdGVudmVyYXJiZWl0dW5nc3plbnRyYWxlMR0wGwYD
VQQDExRGSCBNdWVuc3RlciBDQSAtIEcwMTEgMB4GCSqGSIb3DQEJARYRY2FAZmgtbXVlbnN0ZXIu
ZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4eWyu8GzsIv0iowf2v/9BT0SmCFNX
/eyQe5BncOk1j6XIlY5bnNu1S5uBe3uVgekgTh3gJyVNlaoIfCgAjqCrNJIaNQq5fr/S6L8uFeaU
O8IF/C4RH5P7f9Hn2GUueEjmJhg9CI3LBAhrfAmEEtNmuVfDycN2MjngwDNxUNRfuXbWxuhkgDqJ
0ztJeayHGhFDrGx88eyStx40xy+0c0OFWdWxzBFQlBRHnl+zRftj3c9qy6BY+/fGaA2vV1oKr3h5
X6eyU1T8YlpP1NDe4bylqAteX01sM2Qciu8UAPnNc7Sb93TQjhCFRVDIS3CdN6AOpwz5YWEld6ey
CdmFZ7pvAgMBAAGjggH+MIIB+jASBgNVHRMBAf8ECDAGAQH/AgEBMA4GA1UdDwEB/wQEAwIBBjAR
BgNVHSAECjAIMAYGBFUdIAAwHQYDVR0OBBYEFArzW7zkMYDWNUKJptPDzzfe0d/XMB8GA1UdIwQY
MBaAFEm3xs/oPR9/6kR7Eyn38QpwPt5kMBwGA1UdEQQVMBOBEWNhQGZoLW11ZW5zdGVyLmRlMIGI
BgNVHR8EgYAwfjA9oDugOYY3aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9w
dWIvY3JsL2NhY3JsLmNybDA9oDugOYY3aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9v
dC1jYS9wdWIvY3JsL2NhY3JsLmNybDCB1wYIKwYBBQUHAQEEgcowgccwMwYIKwYBBQUHMAGGJ2h0
dHA6Ly9vY3NwLnBjYS5kZm4uZGUvT0NTUC1TZXJ2ZXIvT0NTUDBHBggrBgEFBQcwAoY7aHR0cDov
L2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRwYI
KwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2Vy
dC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBCwUAA4IBAQDeRwM11kpvuRIPuzWXLapr/ZBtB76V3cuF
l45x/Kx0u03yjB4GaBPcxihn4P1z5KhRYkDBMo8HXkOgbL59aF6VdOlCurEgZvghKvUkKOCyWeYx
S9rTGPBkbGiNn2ATVuLXzF8rDf50ynAIu3otstOOv+3Ifqi1pzCva1nO64khQA5Gd5/BNyu+YHbW
f8ERAf9leu5a7yVI7cv1gCZAHpWJpkUKmfawyY4sAJ2hbGZRBvdACOxrfbuMdSOzPneT2rlmvH+D
7M6DmzVabLYk6UtAxQhldd/T/qsHkWvaWXHt0Eb9STs2Fl03Ls7M3NyLQLhaeR3ysNURYcaEfaB+
lxN+MIIGDTCCBPWgAwIBAgIHG5mIdDexozANBgkqhkiG9w0BAQsFADCBxjELMAkGA1UEBhMCREUx
HDAaBgNVBAgTE05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQK
ExdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVu
dHJhbGUxHTAbBgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBm
aC1tdWVuc3Rlci5kZTAeFw0xNjA3MDQwNzA2MTNaFw0xOTA3MDQwNzA2MTNaMHwxCzAJBgNVBAYT
AkRFMSAwHgYDVQQKDBdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEyMDAGA1UECwwpRmFjaGJlcmVp
Y2ggRWxla3Ryb3RlY2huaWsgdW5kIEluZm9ybWF0aWsxFzAVBgNVBAMMDk1pY2hhZWwgVHVleGVu
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzJoaUG3Zm24XxA/zNg2sbFcL56w8xqMg
+X6G7UsYec3YEncnlkw3jgE5nDefos7UVoCA7wPjFTj8AQt5xfpXElnbM45IPy5Ng7g6dS7biGSM
VRACPXe1PrjgApRAwwGmCPvALnZXkmKP6Zlf+3VLfz9YWIIaeKu3jFM2Lk6Y3gr5U1l8bjHSawOo
WMlfvSsXXLT38zKW7Uz9jS278j0OqHANBPgsE6/LJoCWFInwlvybxhO3nGU7OteUGaPikqzvjLsL
YgpHDi0WjMZfVx/UtUSzZ4EJvmJTBeuVwyKnCbrawnfwYPTQQ6VE1OkAzmsMByBbEwJ996RtG//T
XCG06QIDAQABo4ICRzCCAkMwQAYDVR0gBDkwNzARBg8rBgEEAYGtIYIsAQEEAwUwEQYPKwYBBAGB
rSGCLAIBBAMBMA8GDSsGAQQBga0hgiwBAQQwCQYDVR0TBAIwADAOBgNVHQ8BAf8EBAMCBeAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBTQHa9qhKgSZgCCAPThZkXaEaJ/
dTAfBgNVHSMEGDAWgBQK81u85DGA1jVCiabTw8833tHf1zAgBgNVHREEGTAXgRV0dWV4ZW5AZmgt
bXVlbnN0ZXIuZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2Zo
LW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZu
LmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIHXBggrBgEFBQcBAQSByjCBxzAz
BggrBgEFBQcwAYYnaHR0cDovL29jc3AucGNhLmRmbi5kZS9PQ1NQLVNlcnZlci9PQ1NQMEcGCCsG
AQUFBzAChjtodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jYWNlcnQv
Y2FjZXJ0LmNydDBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDIucGNhLmRmbi5kZS9maC1tdWVuc3Rl
ci1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQELBQADggEBAEj2/6x4kzoCVIiu
aaminPrOHxACyoYsmSRjYPQpgW5xRj/FlolO1nG+ZZ11sqTb3TdCGD69ko5/zs8eGKnv/i0VLCHF
g1JLfpaxElN5RrR/cqRJrbzKshF9aUkBODF8vlf9BCeimMK3fifjbbWRyxHssfEECffujD7/Yvta
NYMO46Roz39lIK2s37IVFq3V5RWzUeTuwpP9t8lOxirOi9eK2OYI/dh0HjR2S5Dr9nMR1dNulrhz
jlFxGc+opefGScrRR9Ec0eqTXlbt1Q9UzNIYVS+OGZY8/bBbprwXVTmwSp8dygEULkIaMbLsaTaW
6TehuL8ousPJkL52SOENgSkxggQpMIIEJQIBATCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozAJBgUrDgMCGgUAoIICKzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0xNzA4MjUxMDUzNTNaMCMGCSqGSIb3DQEJBDEWBBSTAd8v90Povog1uT5r
/4uPRN7nKDCB4wYJKwYBBAGCNxAEMYHVMIHSMIHGMQswCQYDVQQGEwJERTEcMBoGA1UECBMTTm9y
ZHJoZWluLVdlc3RmYWxlbjERMA8GA1UEBxMITXVlbnN0ZXIxIDAeBgNVBAoTF0ZhY2hob2Noc2No
dWxlIE11ZW5zdGVyMSMwIQYDVQQLExpEYXRlbnZlcmFyYmVpdHVuZ3N6ZW50cmFsZTEdMBsGA1UE
AxMURkggTXVlbnN0ZXIgQ0EgLSBHMDExIDAeBgkqhkiG9w0BCQEWEWNhQGZoLW11ZW5zdGVyLmRl
AgcbmYh0N7GjMIHlBgsqhkiG9w0BCRACCzGB1aCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozANBgkqhkiG9w0BAQEFAASCAQCPaDD6Mo/lCEk82iMc4gPjDuGX2WcJFGMt
F70w9revy0GejckcrjRgQEbcTMdvvBStNz4qOGAdzmnv0NeLkmKLRomJ4Gj9PWRTaeaXQnkV3Q5x
W/ODLFCf6sBusPI5pcW5syQPrCQTPloSF72jyB94cPz4+IfKN2ht3Q6O1E/ErSpRnpPus59QyVxC
o6MfxM3RGEX1GqWvnKc7X4zS9DE5pyCsUUvkfrY6XIkdIAyXioUFMp1Gnjpx9QR3UBEnSHPOg7iO
sit5hIKLwkU7wNFP1JQYWsyRDDPvGnXqXomjOJ1Wx2xWlNQVshxpzRuQFAcpO4/9c8MZEZetmxOg
sbLvAAAAAAAA
--Apple-Mail=_A9D8225C-80BA-41CE-A1C7-811AF7BC68CA--


From nobody Fri Aug 25 04:28:39 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 174F81321A1; Fri, 25 Aug 2017 04:28:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id er3Dz8qP_1Uf; Fri, 25 Aug 2017 04:28:29 -0700 (PDT)
Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 743D9132B9F; Fri, 25 Aug 2017 04:28:28 -0700 (PDT)
Received: by mail-wr0-x233.google.com with SMTP id a47so6451027wra.4; Fri, 25 Aug 2017 04:28:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=YHyGruDpP2hv76A84vBLPrM5pzmvi07akeqBeS0aBJA=; b=Fs2dwCoc9DkufOZgYbYUBVQK4G8qxdJTI8ElvsT9dRVnTtEVC/8fpoKss9HIOBs42J xxsMkXcvy0SMEnWrLeK8bg4ysb5BgoiVmtRr0kaKWQXQecO2SLZZNq4UXfXVhxcYbaiK d+XSZxTd6Nm127Gi8bjdeSgfzLX+04vZsiTHHfAnFwk4BNE4PjJedy/AuDOhUZsI2Nd3 3vrSGBmmni4Fk2Rl18k/PUYarxTcaWsT6yRECGAvE05Qv0QvZ8AI3/D1GUxJrlHIefUm QmfA1yvc4Qy3OXoItRSxOQWoMrzFnjon62H6YvXNs8V3N0F+nOs4o4F7i3fJ9YisgR4G u+bQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=YHyGruDpP2hv76A84vBLPrM5pzmvi07akeqBeS0aBJA=; b=dnZeXjvgpq/6Mba9jetLBlLWMmbu1LfETN999K2Fox8ZmO70Odwvqw7TOtJIP8YYTi BbBWsCD9IRaEKataHut+wNp8EJGZIXgP7iv0ySLQRbhCuWQJmBNMJ11o11IhYxBBlQ6b wW5qpquw8zpqBLoeJzbeI6a7JZ2eBajVhq0JWM7ZoyWpWeoJWU0xoI7eD/3LIi1xLIM6 AEkKRuraryTTr9aTQrT7JqsBsnQSrNp4YpZjq6PC8ERpj6BEoyXTbDgKicgWGZ5YA3H3 7kx9xfylapMY/8YnGHz+dhI/5sKAJBe1LgC4SKJ6m4syEPRcbpQ59pKS0NLX67Ao2uGx Z7Hw==
X-Gm-Message-State: AHYfb5hHrrP0NaEZQjaVctbpj1hs8u92Dj7w7gW8Yq1Jk+l9Rfdo7tMC zFU4c97KLNYFw31PfiU=
X-Received: by 10.223.167.138 with SMTP id j10mr5081636wrc.97.1503660506634; Fri, 25 Aug 2017 04:28:26 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id u83sm999934wmu.40.2017.08.25.04.28.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 25 Aug 2017 04:28:26 -0700 (PDT)
Subject: Re: Genart last call review of draft-ietf-tsvwg-sctp-ndata-12
To: Michael Tuexen <tuexen@fh-muenster.de>
Cc: gen-art@ietf.org, tsvwg@ietf.org, ietf@ietf.org, draft-ietf-tsvwg-sctp-ndata.all@ietf.org
References: <150274094205.10409.17989486864216331116@ietfa.amsl.com> <2B0B5E2A-0B15-4B86-9226-3129A101EE24@fh-muenster.de>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <3c58ac17-179c-6e2a-2ba6-589e83cb6dd1@gmail.com>
Date: Fri, 25 Aug 2017 12:28:24 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <2B0B5E2A-0B15-4B86-9226-3129A101EE24@fh-muenster.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TqLpVCZ_f9zbNVOZ6FnvbwsWt4g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Aug 2017 11:28:32 -0000

Hi Michael

Sorry I misread the text.

The text is fine as it is, and I leave it to you to see if there is an 
improvement with a common definition.

I am correcting the review.

- Stewart


On 25/08/2017 11:53, Michael Tuexen wrote:
>> On 14. Aug 2017, at 22:02, Stewart Bryant <stewart.bryant@gmail.com> wrote:
>>
>> Reviewer: Stewart Bryant
>> Review result: Ready
>>
> Hi Stewart,
>
> thanks for your review. See my comment in-line.
>
> Best regards
> Michael
>> I am the assigned Gen-ART reviewer for this draft. The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair.  Please treat these comments just
>> like any other last call comments.
>>
>> For more information, please see the FAQ at
>>
>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>
>> Document: draft-ietf-tsvwg-sctp-ndata-12
>> Reviewer: Stewart Bryant
>> Review Date: 2017-08-14
>> IETF LC End Date: 2017-08-25
>> IESG Telechat date: Not scheduled for a telechat
>>
>> Summary: This is a well written draft and is ready for publication.
>>
>> Major issues: None
>>
>> Minor issues: None
>>
>> Nits/editorial comments:
>>
>> You repeat the text:
>>
>> "A message is considered in flight, if at least  on of its I-DATA chunks is not
>> acknowledged in a non-renegable way"  in two consecutive sections, maybe a
>> common definition could be used.
> The first text covers "Message in flight", the second covers "Fragment in flight".
> What is duplicated is the text (i.e. acknowledged by the cumulative TSN Ack) for
> explaining "acknowledged in a non-renegable way". Giving the explanation only once
> improves readability, I guess.
>
> Best regards
> Michael


From nobody Fri Aug 25 04:50:45 2017
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C3C11243F6; Fri, 25 Aug 2017 04:50:38 -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, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AeTgZ9qyj0E1; Fri, 25 Aug 2017 04:50:36 -0700 (PDT)
Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38F5613292C; Fri, 25 Aug 2017 04:50:36 -0700 (PDT)
Received: from [192.168.1.204] (p57BB53DA.dip0.t-ipconnect.de [87.187.83.218]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 1D803721E281A; Fri, 25 Aug 2017 13:50:33 +0200 (CEST)
From: Michael Tuexen <tuexen@fh-muenster.de>
Message-Id: <0D2E38FA-03E3-4C0F-A1DF-08C4F20F50D4@fh-muenster.de>
Content-Type: multipart/signed; boundary="Apple-Mail=_FB0AC65D-AEDB-4EC8-A28F-9817F50F682E"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Genart last call review of draft-ietf-tsvwg-sctp-ndata-12
Date: Fri, 25 Aug 2017 13:50:31 +0200
In-Reply-To: <3c58ac17-179c-6e2a-2ba6-589e83cb6dd1@gmail.com>
Cc: gen-art@ietf.org, tsvwg@ietf.org, ietf@ietf.org, draft-ietf-tsvwg-sctp-ndata.all@ietf.org
To: Stewart Bryant <stewart.bryant@gmail.com>
References: <150274094205.10409.17989486864216331116@ietfa.amsl.com> <2B0B5E2A-0B15-4B86-9226-3129A101EE24@fh-muenster.de> <3c58ac17-179c-6e2a-2ba6-589e83cb6dd1@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jD_jlDCDbRSriDkPNYYSoLMXgYo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Aug 2017 11:50:38 -0000

--Apple-Mail=_FB0AC65D-AEDB-4EC8-A28F-9817F50F682E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> On 25. Aug 2017, at 13:28, Stewart Bryant <stewart.bryant@gmail.com> =
wrote:
>=20
> Hi Michael
>=20
> Sorry I misread the text.
>=20
> The text is fine as it is, and I leave it to you to see if there is an =
improvement with a common definition.
I think the change
=
https://github.com/sctplab/sctp-idata/commit/768dac9acbeff654ecea782bf6823=
92fad4d4709
makes the text more readable.
>=20
> I am correcting the review.
Thanks for the quick feedback!

Best regards
Michael
>=20
> - Stewart
>=20
>=20
> On 25/08/2017 11:53, Michael Tuexen wrote:
>>> On 14. Aug 2017, at 22:02, Stewart Bryant <stewart.bryant@gmail.com> =
wrote:
>>>=20
>>> Reviewer: Stewart Bryant
>>> Review result: Ready
>>>=20
>> Hi Stewart,
>>=20
>> thanks for your review. See my comment in-line.
>>=20
>> Best regards
>> Michael
>>> I am the assigned Gen-ART reviewer for this draft. The General Area
>>> Review Team (Gen-ART) reviews all IETF documents being processed
>>> by the IESG for the IETF Chair.  Please treat these comments just
>>> like any other last call comments.
>>>=20
>>> For more information, please see the FAQ at
>>>=20
>>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>>=20
>>> Document: draft-ietf-tsvwg-sctp-ndata-12
>>> Reviewer: Stewart Bryant
>>> Review Date: 2017-08-14
>>> IETF LC End Date: 2017-08-25
>>> IESG Telechat date: Not scheduled for a telechat
>>>=20
>>> Summary: This is a well written draft and is ready for publication.
>>>=20
>>> Major issues: None
>>>=20
>>> Minor issues: None
>>>=20
>>> Nits/editorial comments:
>>>=20
>>> You repeat the text:
>>>=20
>>> "A message is considered in flight, if at least  on of its I-DATA =
chunks is not
>>> acknowledged in a non-renegable way"  in two consecutive sections, =
maybe a
>>> common definition could be used.
>> The first text covers "Message in flight", the second covers =
"Fragment in flight".
>> What is duplicated is the text (i.e. acknowledged by the cumulative =
TSN Ack) for
>> explaining "acknowledged in a non-renegable way". Giving the =
explanation only once
>> improves readability, I guess.
>>=20
>> Best regards
>> Michael
>=20


--Apple-Mail=_FB0AC65D-AEDB-4EC8-A28F-9817F50F682E
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIQkDCCBNUw
ggO9oAMCAQICCFBOxvU9EbRkMA0GCSqGSIb3DQEBCwUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQK
ExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMw
IQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0xNDA3MjIxMjA4MjZaFw0xOTA3
MDkyMzU5MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdE
Rk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAx
BAuZgeKmFNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84Ik
Q4wcOItqaACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVg
Te3RCSMqljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sW
VlZDz+HVEz2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjggGG
MIIBgjAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1Ud
IwQYMBaAFDHDeRu69VPXF+CJei0XbAqzK50zMBIGA1UdEwEB/wQIMAYBAf8CAQIwYgYDVR0gBFsw
WTARBg8rBgEEAYGtIYIsAQEEAgIwEQYPKwYBBAGBrSGCLAEBBAMAMBEGDysGAQQBga0hgiwBAQQD
ATAPBg0rBgEEAYGtIYIsAQEEMA0GCysGAQQBga0hgiweMD4GA1UdHwQ3MDUwM6AxoC+GLWh0dHA6
Ly9wa2kwMzM2LnRlbGVzZWMuZGUvcmwvRFRfUk9PVF9DQV8yLmNybDB4BggrBgEFBQcBAQRsMGow
LAYIKwYBBQUHMAGGIGh0dHA6Ly9vY3NwMDMzNi50ZWxlc2VjLmRlL29jc3ByMDoGCCsGAQUFBzAC
hi5odHRwOi8vcGtpMDMzNi50ZWxlc2VjLmRlL2NydC9EVF9ST09UX0NBXzIuY2VyMA0GCSqGSIb3
DQEBCwUAA4IBAQBjICj9nCGGcr45Rlk5MiW8qQGbDczKfUGchm0KbiyzE1l1sTOSG2EnFv/DstU1
gvuEKgFJvWa7Zi+ywgZdbj9u4wFaW8pDY1yVtuExpx/VB19N5mWCTjL5w3x6S81NXHTuIfJ1AuxS
PtLJatOQI25JZzW+f01WpOzML8+3oZeocj7JvEDWWqQIPda8gsO3tzKOsSyOam23NQIZz/U5RFhj
pyQAELC7/E6vbi84u6VXST/YblBvLJeW3B1GmmWJz67M8uXZn1OzPqEvkqnYC8aEHwTG6x7on321
e6UC8STFJGMRNMxakyAqeYg6JUKQqWU7fIbTEhUjKfws2sw5W1QXMIIFojCCBIqgAwIBAgIHF6Qk
oQlIMzANBgkqhkiG9w0BAQsFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQ
MA4GA1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4X
DTE0MDUyNzE0NTQwOVoXDTE5MDcwOTIzNTkwMFowgcYxCzAJBgNVBAYTAkRFMRwwGgYDVQQIExNO
b3JkcmhlaW4tV2VzdGZhbGVuMREwDwYDVQQHEwhNdWVuc3RlcjEgMB4GA1UEChMXRmFjaGhvY2hz
Y2h1bGUgTXVlbnN0ZXIxIzAhBgNVBAsTGkRhdGVudmVyYXJiZWl0dW5nc3plbnRyYWxlMR0wGwYD
VQQDExRGSCBNdWVuc3RlciBDQSAtIEcwMTEgMB4GCSqGSIb3DQEJARYRY2FAZmgtbXVlbnN0ZXIu
ZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4eWyu8GzsIv0iowf2v/9BT0SmCFNX
/eyQe5BncOk1j6XIlY5bnNu1S5uBe3uVgekgTh3gJyVNlaoIfCgAjqCrNJIaNQq5fr/S6L8uFeaU
O8IF/C4RH5P7f9Hn2GUueEjmJhg9CI3LBAhrfAmEEtNmuVfDycN2MjngwDNxUNRfuXbWxuhkgDqJ
0ztJeayHGhFDrGx88eyStx40xy+0c0OFWdWxzBFQlBRHnl+zRftj3c9qy6BY+/fGaA2vV1oKr3h5
X6eyU1T8YlpP1NDe4bylqAteX01sM2Qciu8UAPnNc7Sb93TQjhCFRVDIS3CdN6AOpwz5YWEld6ey
CdmFZ7pvAgMBAAGjggH+MIIB+jASBgNVHRMBAf8ECDAGAQH/AgEBMA4GA1UdDwEB/wQEAwIBBjAR
BgNVHSAECjAIMAYGBFUdIAAwHQYDVR0OBBYEFArzW7zkMYDWNUKJptPDzzfe0d/XMB8GA1UdIwQY
MBaAFEm3xs/oPR9/6kR7Eyn38QpwPt5kMBwGA1UdEQQVMBOBEWNhQGZoLW11ZW5zdGVyLmRlMIGI
BgNVHR8EgYAwfjA9oDugOYY3aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9w
dWIvY3JsL2NhY3JsLmNybDA9oDugOYY3aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9v
dC1jYS9wdWIvY3JsL2NhY3JsLmNybDCB1wYIKwYBBQUHAQEEgcowgccwMwYIKwYBBQUHMAGGJ2h0
dHA6Ly9vY3NwLnBjYS5kZm4uZGUvT0NTUC1TZXJ2ZXIvT0NTUDBHBggrBgEFBQcwAoY7aHR0cDov
L2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRwYI
KwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2Vy
dC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBCwUAA4IBAQDeRwM11kpvuRIPuzWXLapr/ZBtB76V3cuF
l45x/Kx0u03yjB4GaBPcxihn4P1z5KhRYkDBMo8HXkOgbL59aF6VdOlCurEgZvghKvUkKOCyWeYx
S9rTGPBkbGiNn2ATVuLXzF8rDf50ynAIu3otstOOv+3Ifqi1pzCva1nO64khQA5Gd5/BNyu+YHbW
f8ERAf9leu5a7yVI7cv1gCZAHpWJpkUKmfawyY4sAJ2hbGZRBvdACOxrfbuMdSOzPneT2rlmvH+D
7M6DmzVabLYk6UtAxQhldd/T/qsHkWvaWXHt0Eb9STs2Fl03Ls7M3NyLQLhaeR3ysNURYcaEfaB+
lxN+MIIGDTCCBPWgAwIBAgIHG5mIdDexozANBgkqhkiG9w0BAQsFADCBxjELMAkGA1UEBhMCREUx
HDAaBgNVBAgTE05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQK
ExdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVu
dHJhbGUxHTAbBgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBm
aC1tdWVuc3Rlci5kZTAeFw0xNjA3MDQwNzA2MTNaFw0xOTA3MDQwNzA2MTNaMHwxCzAJBgNVBAYT
AkRFMSAwHgYDVQQKDBdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEyMDAGA1UECwwpRmFjaGJlcmVp
Y2ggRWxla3Ryb3RlY2huaWsgdW5kIEluZm9ybWF0aWsxFzAVBgNVBAMMDk1pY2hhZWwgVHVleGVu
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzJoaUG3Zm24XxA/zNg2sbFcL56w8xqMg
+X6G7UsYec3YEncnlkw3jgE5nDefos7UVoCA7wPjFTj8AQt5xfpXElnbM45IPy5Ng7g6dS7biGSM
VRACPXe1PrjgApRAwwGmCPvALnZXkmKP6Zlf+3VLfz9YWIIaeKu3jFM2Lk6Y3gr5U1l8bjHSawOo
WMlfvSsXXLT38zKW7Uz9jS278j0OqHANBPgsE6/LJoCWFInwlvybxhO3nGU7OteUGaPikqzvjLsL
YgpHDi0WjMZfVx/UtUSzZ4EJvmJTBeuVwyKnCbrawnfwYPTQQ6VE1OkAzmsMByBbEwJ996RtG//T
XCG06QIDAQABo4ICRzCCAkMwQAYDVR0gBDkwNzARBg8rBgEEAYGtIYIsAQEEAwUwEQYPKwYBBAGB
rSGCLAIBBAMBMA8GDSsGAQQBga0hgiwBAQQwCQYDVR0TBAIwADAOBgNVHQ8BAf8EBAMCBeAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBTQHa9qhKgSZgCCAPThZkXaEaJ/
dTAfBgNVHSMEGDAWgBQK81u85DGA1jVCiabTw8833tHf1zAgBgNVHREEGTAXgRV0dWV4ZW5AZmgt
bXVlbnN0ZXIuZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2Zo
LW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZu
LmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIHXBggrBgEFBQcBAQSByjCBxzAz
BggrBgEFBQcwAYYnaHR0cDovL29jc3AucGNhLmRmbi5kZS9PQ1NQLVNlcnZlci9PQ1NQMEcGCCsG
AQUFBzAChjtodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jYWNlcnQv
Y2FjZXJ0LmNydDBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDIucGNhLmRmbi5kZS9maC1tdWVuc3Rl
ci1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQELBQADggEBAEj2/6x4kzoCVIiu
aaminPrOHxACyoYsmSRjYPQpgW5xRj/FlolO1nG+ZZ11sqTb3TdCGD69ko5/zs8eGKnv/i0VLCHF
g1JLfpaxElN5RrR/cqRJrbzKshF9aUkBODF8vlf9BCeimMK3fifjbbWRyxHssfEECffujD7/Yvta
NYMO46Roz39lIK2s37IVFq3V5RWzUeTuwpP9t8lOxirOi9eK2OYI/dh0HjR2S5Dr9nMR1dNulrhz
jlFxGc+opefGScrRR9Ec0eqTXlbt1Q9UzNIYVS+OGZY8/bBbprwXVTmwSp8dygEULkIaMbLsaTaW
6TehuL8ousPJkL52SOENgSkxggQpMIIEJQIBATCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozAJBgUrDgMCGgUAoIICKzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0xNzA4MjUxMTUwMzJaMCMGCSqGSIb3DQEJBDEWBBTxsbtGH9BB+gS3DQJE
bOerEzMphDCB4wYJKwYBBAGCNxAEMYHVMIHSMIHGMQswCQYDVQQGEwJERTEcMBoGA1UECBMTTm9y
ZHJoZWluLVdlc3RmYWxlbjERMA8GA1UEBxMITXVlbnN0ZXIxIDAeBgNVBAoTF0ZhY2hob2Noc2No
dWxlIE11ZW5zdGVyMSMwIQYDVQQLExpEYXRlbnZlcmFyYmVpdHVuZ3N6ZW50cmFsZTEdMBsGA1UE
AxMURkggTXVlbnN0ZXIgQ0EgLSBHMDExIDAeBgkqhkiG9w0BCQEWEWNhQGZoLW11ZW5zdGVyLmRl
AgcbmYh0N7GjMIHlBgsqhkiG9w0BCRACCzGB1aCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozANBgkqhkiG9w0BAQEFAASCAQApoJ6L1yt1mr6ekfHM7S/XG/Ju2hJ91g9I
l+ONJjO8livJKoLi7IwdMlKfhqQAfpfiqsTEHf/FPj6YIhDPuU4DVg1dubC4SKeRqCycRsYexCu4
T7UQaCRY0WWhQ8VCakSCrPMS50Vlc7utx6cLz1NItO2jdEYKinF6cnYfnM762ow3+L/1rmSen/C5
c7ZApNWCwT/26w0PQEL3c3HnIHBe2uspQybF1Ht47qZEz2ZT79kbYxuC7fQMfKMWtOmwalYwFfSe
lC4KBJgDofzgD9CJD3hP6A75M4TJ/kJyWRqAIqUXahZfI3R4g2wmvtJfqDaayXVuTRb7pw7mmGRd
fnlDAAAAAAAA
--Apple-Mail=_FB0AC65D-AEDB-4EC8-A28F-9817F50F682E--


From nobody Fri Aug 25 07:32:57 2017
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71C34132BF1; Fri, 25 Aug 2017 07:32:39 -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, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZRq1XaSpudv8; Fri, 25 Aug 2017 07:32:37 -0700 (PDT)
Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C69D4132944; Fri, 25 Aug 2017 07:32:36 -0700 (PDT)
Received: from [192.168.1.204] (p57BB598B.dip0.t-ipconnect.de [87.187.89.139]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 4C21D721E2822; Fri, 25 Aug 2017 16:32:33 +0200 (CEST)
From: Michael Tuexen <tuexen@fh-muenster.de>
Message-Id: <FDCFFA8C-8828-4578-A66E-A1AD7FF9BDC9@fh-muenster.de>
Content-Type: multipart/signed; boundary="Apple-Mail=_A9615269-0F8E-4323-B807-63A8FB6EE3D6"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Opsdir last call review of draft-ietf-tsvwg-sctp-ndata-12
Date: Fri, 25 Aug 2017 16:32:31 +0200
In-Reply-To: <150287547583.12471.9085655210334710687@ietfa.amsl.com>
Cc: ops-dir@ietf.org, tsvwg@ietf.org, ietf@ietf.org, draft-ietf-tsvwg-sctp-ndata.all@ietf.org
To: Stefan Winter <stefan.winter@restena.lu>
References: <150287547583.12471.9085655210334710687@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NOssQGMK2m4kIw8dSucAHUAmBo0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Aug 2017 14:32:39 -0000

--Apple-Mail=_A9615269-0F8E-4323-B807-63A8FB6EE3D6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> On 16. Aug 2017, at 11:24, Stefan Winter <stefan.winter@restena.lu> =
wrote:
>=20
> Reviewer: Stefan Winter
> Review result: Has Issues
>=20
Hi Stefan,

thanks for your review. See my comments in-line.

Best regards
Michael
> One issue:
>=20
> The chapter IANA considerations mentions four bits to be registered: =
E,B,U,I.
> In the main body, only three of those are actually defined and used =
(End of
> fragmented message, Beginning of fragmented message, Unordered/Ordered
> message). Please add a definition of the I bit or remove the IANA =
registration
> request for that bit.
The I bit is defined in RFC 7053 and that is the reason why we state
"DATA chunk defined in [RFC4960]and [RFC7053]". In addition to that it =
is
not mentioned (in contrast to the U, B and E bit), since the delaying of =
the
SACK is not specific to the I-DATA chunk.

I have added the following text to the body of Section 2.2:

<t>The handling of the I bit for the I-DATA chunk corresponds to the =
handling
of the I bit for the DATA chunk described in <xref =
target=3D'RFC7053'/>.</t>

to improve the description of the I bit. See
=
https://github.com/sctplab/sctp-idata/commit/f16308ffe0e67ce5deb957bd40c25=
c5a0e691b82
Does that address your issue?
>=20
> And the rest are only musings not needing any action if the authors =
don't want
> to action on them:
>=20
> The introduction presents a good use case, quoting: "e.g., when the
> transmission of an urgent
>   message is blocked from transmission because the sender has started
>   the transmission of another, possibly large, message".
>=20
> The later queueing example in figure 1 has three SIDs being queued
> simultanseously. It is not clear which of those "has already started" =
and which
There is actually one message queued for stream 0, three messages for =
stream 1,
and one message for stream 2.
> are the important ones being delayed. For a better understanding of =
the reader,
The figure is about in which sequence they are put on the wire. So no
transmission has startet. This examples also does not deal with the case
of one stream having a higher priority than another. That would be an
example using a priority scheduler. This examples illustrates the round
robin scheduler.
The point here is that a single scheduler (the round robin scheduler, =
for
example) behaves differently when user message interleaving is used or =
not.
That is an important point: You can even use the schedulers with regular
DATA chunk, i.e. with user message interleaving being negotiated.
> it might be useful to revise the figure so that the head-of-line =
blocking
> happens for SID 1 because transmission of  0 and 2 has already started =
(and
> declare SID 1 to be the "important" message). The ASCII art would just =
have to
> indent SID 1 content a bit (placing 0 and 2 earlier in time), and the =
resulting
> serialisation would then put all the SID 1 messages at the very end, =
when 0 and
> 2 have been completely submitted (right?).
One could think about adding another example based on the priority =
scheduler
and giving stream 1 a higher priority. But for illustrating the point of
schedulers behaving differently depending on the negotiation of user =
message
interleaving this seems not necessary.
>=20
> In 2.2.3, is there any particular reason why the "protocol violation" =
error
> cause is only a MAY? As it enables debugging on the remote end, a =
SHOULD seems
> useful.
This is for consistency with other SCTP specifications. There is always =
the balance
between providing more information to help diagnosing the problem and =
providing more
information to an attacker. This allows implementers to do what they =
prefer.
For interoperability it is not important if the error cause is included =
or not.
>=20


--Apple-Mail=_A9615269-0F8E-4323-B807-63A8FB6EE3D6
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIQkDCCBNUw
ggO9oAMCAQICCFBOxvU9EbRkMA0GCSqGSIb3DQEBCwUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQK
ExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMw
IQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0xNDA3MjIxMjA4MjZaFw0xOTA3
MDkyMzU5MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdE
Rk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAx
BAuZgeKmFNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84Ik
Q4wcOItqaACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVg
Te3RCSMqljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sW
VlZDz+HVEz2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjggGG
MIIBgjAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1Ud
IwQYMBaAFDHDeRu69VPXF+CJei0XbAqzK50zMBIGA1UdEwEB/wQIMAYBAf8CAQIwYgYDVR0gBFsw
WTARBg8rBgEEAYGtIYIsAQEEAgIwEQYPKwYBBAGBrSGCLAEBBAMAMBEGDysGAQQBga0hgiwBAQQD
ATAPBg0rBgEEAYGtIYIsAQEEMA0GCysGAQQBga0hgiweMD4GA1UdHwQ3MDUwM6AxoC+GLWh0dHA6
Ly9wa2kwMzM2LnRlbGVzZWMuZGUvcmwvRFRfUk9PVF9DQV8yLmNybDB4BggrBgEFBQcBAQRsMGow
LAYIKwYBBQUHMAGGIGh0dHA6Ly9vY3NwMDMzNi50ZWxlc2VjLmRlL29jc3ByMDoGCCsGAQUFBzAC
hi5odHRwOi8vcGtpMDMzNi50ZWxlc2VjLmRlL2NydC9EVF9ST09UX0NBXzIuY2VyMA0GCSqGSIb3
DQEBCwUAA4IBAQBjICj9nCGGcr45Rlk5MiW8qQGbDczKfUGchm0KbiyzE1l1sTOSG2EnFv/DstU1
gvuEKgFJvWa7Zi+ywgZdbj9u4wFaW8pDY1yVtuExpx/VB19N5mWCTjL5w3x6S81NXHTuIfJ1AuxS
PtLJatOQI25JZzW+f01WpOzML8+3oZeocj7JvEDWWqQIPda8gsO3tzKOsSyOam23NQIZz/U5RFhj
pyQAELC7/E6vbi84u6VXST/YblBvLJeW3B1GmmWJz67M8uXZn1OzPqEvkqnYC8aEHwTG6x7on321
e6UC8STFJGMRNMxakyAqeYg6JUKQqWU7fIbTEhUjKfws2sw5W1QXMIIFojCCBIqgAwIBAgIHF6Qk
oQlIMzANBgkqhkiG9w0BAQsFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQ
MA4GA1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4X
DTE0MDUyNzE0NTQwOVoXDTE5MDcwOTIzNTkwMFowgcYxCzAJBgNVBAYTAkRFMRwwGgYDVQQIExNO
b3JkcmhlaW4tV2VzdGZhbGVuMREwDwYDVQQHEwhNdWVuc3RlcjEgMB4GA1UEChMXRmFjaGhvY2hz
Y2h1bGUgTXVlbnN0ZXIxIzAhBgNVBAsTGkRhdGVudmVyYXJiZWl0dW5nc3plbnRyYWxlMR0wGwYD
VQQDExRGSCBNdWVuc3RlciBDQSAtIEcwMTEgMB4GCSqGSIb3DQEJARYRY2FAZmgtbXVlbnN0ZXIu
ZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4eWyu8GzsIv0iowf2v/9BT0SmCFNX
/eyQe5BncOk1j6XIlY5bnNu1S5uBe3uVgekgTh3gJyVNlaoIfCgAjqCrNJIaNQq5fr/S6L8uFeaU
O8IF/C4RH5P7f9Hn2GUueEjmJhg9CI3LBAhrfAmEEtNmuVfDycN2MjngwDNxUNRfuXbWxuhkgDqJ
0ztJeayHGhFDrGx88eyStx40xy+0c0OFWdWxzBFQlBRHnl+zRftj3c9qy6BY+/fGaA2vV1oKr3h5
X6eyU1T8YlpP1NDe4bylqAteX01sM2Qciu8UAPnNc7Sb93TQjhCFRVDIS3CdN6AOpwz5YWEld6ey
CdmFZ7pvAgMBAAGjggH+MIIB+jASBgNVHRMBAf8ECDAGAQH/AgEBMA4GA1UdDwEB/wQEAwIBBjAR
BgNVHSAECjAIMAYGBFUdIAAwHQYDVR0OBBYEFArzW7zkMYDWNUKJptPDzzfe0d/XMB8GA1UdIwQY
MBaAFEm3xs/oPR9/6kR7Eyn38QpwPt5kMBwGA1UdEQQVMBOBEWNhQGZoLW11ZW5zdGVyLmRlMIGI
BgNVHR8EgYAwfjA9oDugOYY3aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9w
dWIvY3JsL2NhY3JsLmNybDA9oDugOYY3aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9v
dC1jYS9wdWIvY3JsL2NhY3JsLmNybDCB1wYIKwYBBQUHAQEEgcowgccwMwYIKwYBBQUHMAGGJ2h0
dHA6Ly9vY3NwLnBjYS5kZm4uZGUvT0NTUC1TZXJ2ZXIvT0NTUDBHBggrBgEFBQcwAoY7aHR0cDov
L2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRwYI
KwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2Vy
dC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBCwUAA4IBAQDeRwM11kpvuRIPuzWXLapr/ZBtB76V3cuF
l45x/Kx0u03yjB4GaBPcxihn4P1z5KhRYkDBMo8HXkOgbL59aF6VdOlCurEgZvghKvUkKOCyWeYx
S9rTGPBkbGiNn2ATVuLXzF8rDf50ynAIu3otstOOv+3Ifqi1pzCva1nO64khQA5Gd5/BNyu+YHbW
f8ERAf9leu5a7yVI7cv1gCZAHpWJpkUKmfawyY4sAJ2hbGZRBvdACOxrfbuMdSOzPneT2rlmvH+D
7M6DmzVabLYk6UtAxQhldd/T/qsHkWvaWXHt0Eb9STs2Fl03Ls7M3NyLQLhaeR3ysNURYcaEfaB+
lxN+MIIGDTCCBPWgAwIBAgIHG5mIdDexozANBgkqhkiG9w0BAQsFADCBxjELMAkGA1UEBhMCREUx
HDAaBgNVBAgTE05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQK
ExdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVu
dHJhbGUxHTAbBgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBm
aC1tdWVuc3Rlci5kZTAeFw0xNjA3MDQwNzA2MTNaFw0xOTA3MDQwNzA2MTNaMHwxCzAJBgNVBAYT
AkRFMSAwHgYDVQQKDBdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEyMDAGA1UECwwpRmFjaGJlcmVp
Y2ggRWxla3Ryb3RlY2huaWsgdW5kIEluZm9ybWF0aWsxFzAVBgNVBAMMDk1pY2hhZWwgVHVleGVu
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzJoaUG3Zm24XxA/zNg2sbFcL56w8xqMg
+X6G7UsYec3YEncnlkw3jgE5nDefos7UVoCA7wPjFTj8AQt5xfpXElnbM45IPy5Ng7g6dS7biGSM
VRACPXe1PrjgApRAwwGmCPvALnZXkmKP6Zlf+3VLfz9YWIIaeKu3jFM2Lk6Y3gr5U1l8bjHSawOo
WMlfvSsXXLT38zKW7Uz9jS278j0OqHANBPgsE6/LJoCWFInwlvybxhO3nGU7OteUGaPikqzvjLsL
YgpHDi0WjMZfVx/UtUSzZ4EJvmJTBeuVwyKnCbrawnfwYPTQQ6VE1OkAzmsMByBbEwJ996RtG//T
XCG06QIDAQABo4ICRzCCAkMwQAYDVR0gBDkwNzARBg8rBgEEAYGtIYIsAQEEAwUwEQYPKwYBBAGB
rSGCLAIBBAMBMA8GDSsGAQQBga0hgiwBAQQwCQYDVR0TBAIwADAOBgNVHQ8BAf8EBAMCBeAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBTQHa9qhKgSZgCCAPThZkXaEaJ/
dTAfBgNVHSMEGDAWgBQK81u85DGA1jVCiabTw8833tHf1zAgBgNVHREEGTAXgRV0dWV4ZW5AZmgt
bXVlbnN0ZXIuZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2Zo
LW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZu
LmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIHXBggrBgEFBQcBAQSByjCBxzAz
BggrBgEFBQcwAYYnaHR0cDovL29jc3AucGNhLmRmbi5kZS9PQ1NQLVNlcnZlci9PQ1NQMEcGCCsG
AQUFBzAChjtodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jYWNlcnQv
Y2FjZXJ0LmNydDBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDIucGNhLmRmbi5kZS9maC1tdWVuc3Rl
ci1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQELBQADggEBAEj2/6x4kzoCVIiu
aaminPrOHxACyoYsmSRjYPQpgW5xRj/FlolO1nG+ZZ11sqTb3TdCGD69ko5/zs8eGKnv/i0VLCHF
g1JLfpaxElN5RrR/cqRJrbzKshF9aUkBODF8vlf9BCeimMK3fifjbbWRyxHssfEECffujD7/Yvta
NYMO46Roz39lIK2s37IVFq3V5RWzUeTuwpP9t8lOxirOi9eK2OYI/dh0HjR2S5Dr9nMR1dNulrhz
jlFxGc+opefGScrRR9Ec0eqTXlbt1Q9UzNIYVS+OGZY8/bBbprwXVTmwSp8dygEULkIaMbLsaTaW
6TehuL8ousPJkL52SOENgSkxggQpMIIEJQIBATCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozAJBgUrDgMCGgUAoIICKzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0xNzA4MjUxNDMyMzJaMCMGCSqGSIb3DQEJBDEWBBQtxLPq0Yqy8f5dn3vr
sFA/0vJNtTCB4wYJKwYBBAGCNxAEMYHVMIHSMIHGMQswCQYDVQQGEwJERTEcMBoGA1UECBMTTm9y
ZHJoZWluLVdlc3RmYWxlbjERMA8GA1UEBxMITXVlbnN0ZXIxIDAeBgNVBAoTF0ZhY2hob2Noc2No
dWxlIE11ZW5zdGVyMSMwIQYDVQQLExpEYXRlbnZlcmFyYmVpdHVuZ3N6ZW50cmFsZTEdMBsGA1UE
AxMURkggTXVlbnN0ZXIgQ0EgLSBHMDExIDAeBgkqhkiG9w0BCQEWEWNhQGZoLW11ZW5zdGVyLmRl
AgcbmYh0N7GjMIHlBgsqhkiG9w0BCRACCzGB1aCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozANBgkqhkiG9w0BAQEFAASCAQAM5IlD09mTsIoNg4tynHJbbnsIHx+lDPsw
Lidj+w5usOved0RUkub6qdZifNQXZ9J8ndG5IME9O4oUFy1VZdFP4wc7sIyue+i5GFTxEwGmvrIR
DCMqIxmeG2nOI+vVaN57P5xgcSiAcfRgkrv/3ch3Ht36J12HLRdBXZyINoICkFpI+ISYwT6xrN9K
C3v/oXwMgSdfbgi3ka07V1/X0ifqiRpeP7xZGgkSEgjZXuq+mRp8HDH9XH8iKb4MK6akSkpPzLhB
qKQ9p0iGTQVHticX41gOJGzBicOjhNE+mx9Dfjz4nmzEx9W6eU82/rF4I8se+XfejVGPEQqsBw1M
RFpdAAAAAAAA
--Apple-Mail=_A9615269-0F8E-4323-B807-63A8FB6EE3D6--


From nobody Fri Aug 25 08:36:25 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29FCE132C2E for <ietf@ietfa.amsl.com>; Fri, 25 Aug 2017 08:36:24 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3frOcl4b9kZE for <ietf@ietfa.amsl.com>; Fri, 25 Aug 2017 08:36:22 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C84B132C2B for <ietf@ietf.org>; Fri, 25 Aug 2017 08:36:22 -0700 (PDT)
Received: (qmail 49008 invoked from network); 25 Aug 2017 15:36:20 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 25 Aug 2017 15:36:20 -0000
Date: 25 Aug 2017 15:35:58 -0000
Message-ID: <20170825153558.27008.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: big files of mail, was Next steps in IETF list email archiving
In-Reply-To: <54ED5403-ECBF-40B7-84CB-459BF348EF20@orthanc.ca>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6WQzJpvW3vx5wMU1JZozciHnhaY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Aug 2017 15:36:24 -0000

In article <54ED5403-ECBF-40B7-84CB-459BF348EF20@orthanc.ca> you write:
>I agree completely.  I'm just pointing out that there's no standard for the various "mailbox archive" formats.  E.g. mbox, MH, maildir.  IMAP
>provides a(n IETF) standard interface.  Maybe not the most efficient in this specific case, but beware of micro-optimization.

I agree about not micro-optimizing but it leads me to a different answer.

Having been schlepping mbox files for 40 years, I can report that even
though there are a lot of variations, they are minor enough that it is
easy to handle them all.  There have for decades been libraries and
applications that do so, such as mhonarc which turns mbox files into
pretty archive web pages.  Similarly, although the file naming conventions
in mh and maildor are different, the messages in the files are the same
and again it is easy to handle the naming differences.

IMAP is fine for what it's good for, but the question of how you
store archives of mail messages was answered a long time ago.

R's,
John


From nobody Sat Aug 26 08:35:02 2017
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E952613234B; Sat, 26 Aug 2017 08:34:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WU83E-tSM5k0; Sat, 26 Aug 2017 08:34:53 -0700 (PDT)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE74C132328; Sat, 26 Aug 2017 08:34:49 -0700 (PDT)
Received: by mail-wm0-x22b.google.com with SMTP id z132so10828225wmg.1; Sat, 26 Aug 2017 08:34:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=+1ycyli6gJov2aWsTXJ/uYpEg5xLm1LJk9PHltLjdqE=; b=MbZ70t8FomQOYBo45BZoAAMb3wHlQsGlutlUfwNhbHewrSOrX3gq5Ck5Eh4VtbkP88 ArJcobV2szxGaGhfBR5IUzWBIUew1qp3Q3/y4sOjDy8xJ8aIW8Hf49FOMgraFzyMBRas vXHF5cX/Jn7C2IdfRPScbU2xaeoZjywo0hV0uD5iMoR8y4jDU3pNKlDgZWafBdOTs3SW 5Bnu+rbFXNSWExOOGPW07X1T3mCln90Fk0cHsQJnu+YADFEU+gIv7leXoczHkBndQkw4 M4X9q5l8WIdYSHCNeyNIpX0Ji9I3xwnWA/gW4lPb+JOYiakNG7n0elZ9uaKeq9vRZNbT JoWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=+1ycyli6gJov2aWsTXJ/uYpEg5xLm1LJk9PHltLjdqE=; b=giCKZYFe6E/2DBgXqtzTB9Wrl1za3rU7AlEU9C7Ad+TQvhvTEw7TViqUCchBbpNNOG 6gAE3ys0LeMEfTgTTQ2weoGN3NObip7qdBwPit4ENBg9oksNLVR/krNH9Xc+DnCIHsM/ BLq6P8EXksifemPzzCkt0g5vIetyr3p9P96Mk2Aedd0TuWk+Y4mJy4XlCpeSqpxaL9e/ 9BOff9E9Mn3fp6Z/hF4GINkVzKBlwZLjiEWyr3UXAD/ItmLLyjT1RyIyCI4uWLxyjxC/ q6na4dqwjFRML8v4MasDgs5lfcOBMr+fXw9lrZlF/WQR5IPYSpSakx09qjxhuot7PIxR kAfg==
X-Gm-Message-State: AHYfb5jz6ohzPBBg97YZjGge7pc5VznETHOVOHQAVPfj31oCX7mtWuD4 CXZhPFN29VQkPS41tbA=
X-Received: by 10.28.67.1 with SMTP id q1mr970670wma.162.1503761687829; Sat, 26 Aug 2017 08:34:47 -0700 (PDT)
Received: from [10.0.0.10] (bzq-109-67-55-26.red.bezeqint.net. [109.67.55.26]) by smtp.gmail.com with ESMTPSA id h190sm2955727wmd.4.2017.08.26.08.34.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 26 Aug 2017 08:34:46 -0700 (PDT)
Subject: Re: Secdir last call review of draft-weis-gdoi-rekey-ack-05
To: "Brian Weis (bew)" <bew@cisco.com>
Cc: "secdir@ietf.org" <secdir@ietf.org>, "draft-weis-gdoi-rekey-ack.all@ietf.org" <draft-weis-gdoi-rekey-ack.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
References: <150194814585.18635.3104789196001873381@ietfa.amsl.com> <E61F05DB-EEB0-4140-A2D4-DB11163C4E13@cisco.com>
From: Yaron Sheffer <yaronf.ietf@gmail.com>
Message-ID: <e2b32453-8c4f-9707-0e1f-dab29540fe54@gmail.com>
Date: Sat, 26 Aug 2017 18:34:44 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <E61F05DB-EEB0-4140-A2D4-DB11163C4E13@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TUw_hJwxga5wn-D8KZ3C4zImZ8Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 26 Aug 2017 15:34:56 -0000

Hi Brian,

Thank you for addressing most of my comments in the new version, and for 
clarifying points where I was off the mark.

The only remaining comment that's only partly addressed is the one on 
crypto agility. Quoting myself:

we need to define whether multiple such payloads can be sent 
simultaneously (if e.g. some GMs still support the old algorithm) and 
what's the expected behavior.

In other words, supporting more algorithms in not sufficient. The 
question is whether we support incremental deployment of a new algorithm 
to a large group of GMs.

Thanks,
	Yaron

On 24/08/17 19:48, Brian Weis (bew) wrote:
> Hi Yaron,
> 
> Thanks for the review. We’ve added some clarification below, and made 
> some changes in -06 to address your comments. Please let us know if we 
> did not address them satisfactorily.
> 
>> On Aug 5, 2017, at 8:49 AM, Yaron Sheffer <yaronf.ietf@gmail.com 
>> <mailto:yaronf.ietf@gmail.com>> wrote:
>>
>> Reviewer: Yaron Sheffer
>> Review result: Has Issues
>>
>> Summary: this reviewer is not clear about the value of the push-ack 
>> (compared
>> to a pull) and about the strategy that was chosen.
> 
> In a group key management system either a “pull” (triggered by a group 
> member) or a “push” (by the key server)" could be used to provide 
> updates to the group. However, a “pull” by the group member implies a 
> polling method, which has the deficiency that the key server cannot 
> cause a policy replacement any sooner than the polling method by the 
> group members. Also “polling” can cause additional unnecessary traffic. 
> So is is better for any update on the group policy or renewal of group 
> keys to be distributed by the GCKS using a PUSH message. The ACK-message 
> is used to offer a feedback mechanism to a policy update for the PUSH 
> exchange.
>>
>> *//*
>>
>> * "For example, a GCKS policy can use the acknowledgements to 
>> determine [...]
>> which members may no longer be members of the group." This sentence is 
>> very
>> confusing: when are members not members?
> 
> We’ve reworded this text. It’s trying to convey that a missing ACK 
> message (or a certain number of it) can be used to identify that a group 
> member is no longer receiving group traffic, and is now may be 
> considered an ex-group member. For example, it could be a multicast 
> receiver that is no longer interested in being a receiver for the group. 
> But it could also be that a network event has caused it to be 
> unavailable for a sufficient length of time such that it doesn’t have 
> current keying material and therefore can’t be considered a current 
> group member. There is no reliable “I’m leaving the group” message flow, 
> and of course in my second example no such messages would have been 
> intended by the group member.
> 
>> * The new protocol capability is defined as optional, but really 
>> isn't. "A GM
>> receiving the KEK_ACK_REQUESTED attribute can choose to ignore it, thus
>> appearing as if it does not support the KEK_ACK_REQUESTED attribute. 
>> However,
>> GCKS policy may consider a non-responsive GM to no longer desire to be 
>> a member
>> of the group." So if you want to play the game, you MUST support the new
>> attribute.
> 
> Point taken. We’ve changed the text to reflect this.
> 
>> * I'm puzzled at the overall protocol. Being able to send ACKs is a GM 
>> software
>> capability. Why not have the GM announce this capability when it initially
>> registers to the GCKS? Then the GCKS would know what to expect, 
>> whereas with
>> the current protocol it is left waiting for an ACK that may never 
>> come, either
>> because the GM is dead or because it just doesn't feel like 
>> responding. Add the
>> long waits (jitter of "a few seconds" and potential retries), and this 
>> looks
>> like a far from optimal management experience.
> 
> Indeed a GM could announce its capability, but whether or not ACKs are 
> desired is a component of the group policy. In the context of GDOI the 
> GCKS is the entity that defines the group policy. There can be groups 
> where the ACK is used, whereas others do not.  The capabilities 
> announcement you suggest could certainly help the KS to know whether or 
> not to expect the ACK from a particular GM, but the focus of this I-D is 
> on the the declaration of the request for ACKs by the GCKS and the 
> format of the ACK.
> 
>> * 2.2: "This is a private key" - to avoid confusion, I suggest: "This is a
>> secret symmetric key" (if this is indeed the case). Obviously using 
>> the same
>> key for encryption and for HMAC is not a best practice.
> 
> We’ve made this change.
> 
>> * Sec. 5: ACK messages can also be duplicated in the network. I 
>> suggest to add
>> a sentence describing what the GCKS should do in this case.
> 
> The Security Considerations (section 7.3) describes a method for the 
> GCKS to detect replays. This is arguably better placed in this section, 
> so we’ve moved it here..
> 
>> * Sec. 6: I am confused about the notion of "jitter" here. If the PUSH 
>> messages
>> are sent as multicast (the recommended alternative AFAICT), I'm not 
>> sure about
>> the benefit of using multicast, given that each recipient responds with a
>> unicast ACK. And if the PUSH is unicast, there should be no reason for 
>> a jitter
>> as the sender can throttle the PUSH messages as necessary.
> 
> The concept of “jitter” is most valuable for responses to a multicast 
> PUSH message. The use of a multicast PUSH message lower processing on 
> the GCKS. Since each GM can e given the exact same policy, there’s no 
> call to send it out as a unicast message. The jitter helps spread out 
> the replies a bit to avoid inundating the GCKS.
> 
>> * Moreover, everything would be much more predictable if the GCKS could
>> indicate if a jitter is expected and how much of a jitter (based on 
>> size of the
>> group, network throughput, and queue length). Specifically, this would 
>> allow
>> the GCKS to tell how long it should wait for an ACK.
> 
> This would be somewhat useful, but in practice might not help the GCKS 
> as much as it seems. The jitter value provided would also be dependent 
> on several network parameters that aren’t under the control of the GCKS 
> or the GM. Even when the GM does not add any jitter to the ACK, the 
> underlying network may delay the PUSH and/or for the ACK. And as stated 
> in Section 6, the GCKS may be configured with additional policy actions 
> like retransmissions to overcome lost ACKs. Altogether to add jitter to 
> the ACK is not a must, it is a way to help the GCKS deal with a huge 
> number of GMs. In practice, we’ve found that having the GMs choose the 
> jitter has worked well, even when the GMs are different implementations.
> 
>> * Cryptographic agility: this document specifies only one algorithm 
>> for the
>> HASH value, and says that if a new algorithm is needed, there will be 
>> a new
>> KEK_ACK_REQUESTED payload defined. However to make sure that this really
>> "works", we need to define whether multiple such payloads can be sent
>> simultaneously (if e.g. some GMs still support the old algorithm) and 
>> what's
>> the expected behavior. I would suggest to define an additional SHA-512 
>> payload
>> just to make for a concrete example.
> 
> This is a good suggestion. We’ve added SHA-512 versions of the existing 
> KEK_ACK_REQUESTED values.
> 
> See <https://tools.ietf.org/html/draft-weis-gdoi-rekey-ack-06>
> 
> Thanks,
> Brian
> 
> -- 
> Brian Weis
> Security, CSG, Cisco Systems
> Telephone: +1 408 526 4796
> Email: bew@cisco.com <mailto:bew@cisco.com>
> 


From nobody Sat Aug 26 11:10:41 2017
Return-Path: <juberti@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05D23132BD4 for <ietf@ietfa.amsl.com>; Sat, 26 Aug 2017 11:10:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rx_MQwUwzqTR for <ietf@ietfa.amsl.com>; Sat, 26 Aug 2017 11:10:37 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DE5A132BCD for <ietf@ietf.org>; Sat, 26 Aug 2017 11:10:36 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id g33so6044610ioj.3 for <ietf@ietf.org>; Sat, 26 Aug 2017 11:10:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8WSkQTXnpgM2agkV1fR9FVD087EiMcU7/ktnfNZOFJQ=; b=aCF1H2EEDrcsn5sH651wH2elDGCTmdJAvpnibCrfJb4k7sdN8zxzcIGupH9rsbkolm h57XHQhQqSR2LZlsmWdCTrtooFmslLuwwvR9mH6Z4CCSlHnFrD/D9mFD5Ix+vjfL4sIQ 9gnflYIttNBGLJgHr9kNg+2jCTuld48spLHmzhhP49KaJphD6CGuxSpY/HKTHG/p0NF3 Eq4PHjUb0YMdDBWqZ+KYXgFmDK3mVsHpABmeRnMC6x0c9w00hbgDm9ygCDpYYGu/lbyD 1atLNqYv3O9DY9HuSburFd0jKe3N3r8ZGdSLj489tiIrrj2UYxRlXICzWcXC8QFlBvyq zfuw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8WSkQTXnpgM2agkV1fR9FVD087EiMcU7/ktnfNZOFJQ=; b=Q/oDamTBSAkq57vsOfOulOC/3OEuSHWCL1LURgs5q7/nPspOi8xugiUPM+vB5hsDFr LFsJcl+f/wGWqyIuVcB558guTEMQlk8k2YpSmyLDs6Xf5RXm7QGHmFXDJg+llZfz9fBb U+UgzRIYt2kMboNqYg2XZRfgkXq/N7heE28QxDDPp2xN3Qse7Ybg3j+6hMCD2A6e4Cbi qONaEmK9mYBM8WzzZy2p1YhMIaJHhSglje918EccBsYbr42qQGEkRn2Jcrzb4BdtD3M1 b15VNlWqnJOwq1Og+hCX41/CAMupiKc23Q17emfK88gyuY7byhAxAyNqS17SHTtzQvly EAow==
X-Gm-Message-State: AHYfb5i34mrANd/wg+OpjkvJXmXY0/6snPBX5xR6OiTOReb3CgV11rlw 1XzfEx5ndVoBV3Nj+8GN53b1xgb7IuF8
X-Google-Smtp-Source: ADKCNb6rT3EXvRVPkw64bA0TVL87d8232qOVDRcRFhry5uWtkaMXjPOiWhqrAw+a7kPna9uaHApUL6aaWngG9j2FdjA=
X-Received: by 10.107.11.217 with SMTP id 86mr1751759iol.303.1503771034989; Sat, 26 Aug 2017 11:10:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.148.209 with HTTP; Sat, 26 Aug 2017 11:10:14 -0700 (PDT)
In-Reply-To: <150222067484.12279.1715829344429803452@ietfa.amsl.com>
References: <150222067484.12279.1715829344429803452@ietfa.amsl.com>
From: Justin Uberti <juberti@google.com>
Date: Sat, 26 Aug 2017 11:10:14 -0700
Message-ID: <CAOJ7v-1ZM-6EvY6LYY1txvv9Ub6UfPxw7OaFVd=Fq4kiYYusvw@mail.gmail.com>
Subject: Re: [rtcweb] Genart last call review of draft-ietf-rtcweb-jsep-21
To: Robert Sparks <rjsparks@nostrum.com>
Cc: gen-art@ietf.org, draft-ietf-rtcweb-jsep.all@ietf.org,  "rtcweb@ietf.org" <rtcweb@ietf.org>, ietf@ietf.org
Content-Type: multipart/alternative; boundary="001a113f7dba5de4320557abfa73"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/90EuJ3B-vFr8cjT3uZ7BfW3DM18>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 26 Aug 2017 18:10:39 -0000

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

Thanks for this careful review. A new version of the document (-22) has
been posted which addresses almost all of these comments, with a few
exceptions noted below.

Diff:
https://www.ietf.org/rfcdiff?url1=draft-ietf-rtcweb-jsep-21&url2=draft-ietf-rtcweb-jsep-22&difftype=--html

On Tue, Aug 8, 2017 at 12:31 PM, Robert Sparks <rjsparks@nostrum.com> wrote:

> Reviewer: Robert Sparks
> Review result: Almost Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-rtcweb-jsep-21
> Reviewer: Robert Sparks
> Review Date: 2017-08-08
> IETF LC End Date: 2017-08-11
> IESG Telechat date: Not scheduled for a telechat
>
> Summary: Almost ready for publication as a Proposed Standard RFC, but with
> issues that need to be addressed before publishing
>
> Major issues:
>
> The last paragraph of 5.1 needs more context. Why woudn't you expect the
> re-offer to fail, given that you already know the peer is using the older
> profile strings? It's not clear from the email list and proceedings how the
> document ended up with this particular text.
>
> Minor issues:
>
> Second paragraph of 3.2, last sentence: at "these parameters or reject
> them" - "these" and "them" have ambiguous antecedents. It's not clear if
> you
> are trying to point to the parameters that don't follow the earlier stated
> rule, or all parameters. The sentence is complex. Splitting it up and
> finding a way to avoid the need for the semicolon will likely make it
> easier to say what you mean.
>
> Last paragraph on page 5 - first sentence: at "One way to mitigate this" -
> "this" has an unclear antecedent. Did you mean "One way to reduce the
> complexity of the application's responsibilities"?
>
> Last paragraph of 3.5.2.1 - "all of these fields" is ambiguous. Please
> state precisely which fields you mean.
>
> Odd edge: The description createAnswer (in 4.1.7) leaves open the
> possibility that the application could call createAnswer twice
> (back-to-back with no intervening calls to other APIs) with different
> values in the options parameter. Is this ok? If not, should there be
> language that says not to do that somewhere?
>
> Slightly more than minor maybe: The first paragraph of 5.1.2 has at least a
> reference error. UDP/TLS/RTP/SAVPF is not specified in RFC7850. It's in
> RFC5764. Assuming that this is only a reference error, then the last
> sentence seems like a stray. It doesn't seem to be in the right context
> ("this advertisement" doesn't cast back to the discussion of the two
> profiles above it, which are both UDP only). Please clarify the sentence,
> giving it the right context, or remove it.
>
> The fourth sentence of the second bullet of section 5.2.1 is confusing. (It
> starts "It is RECOMMENDED that the <sess-id>".) RFC3265 requires the
> initial sess-id high-order bit to be zero. As written, this can be read to
> say that setting that bit to zero is only RECOMMENDED, and that it's
> possible to have sess-ids that are something other than 64 bits. You mean
> to say "Do what 3265 says to do and make the lower 63 bits random". Here's
> one possible replacement for the sentence: "RFC 3265 requires that the
> high-order bit of the initial <sess-id> be zero. It is RECOMMENDED that the
> remaining 63 bits be initially set to a cryptographically random value."
>
> The last paragraph of 5.3.1 prohibits the same attributes from generated
> answers that are prohibited in generated offers. Consider adding text for
> what to do if an offer shows up from a peer with some of those prohibited
> attributes.
>

This is covered by the last paragraph on page 43:

   Note that these requirements are in some cases stricter than those of
   SDP.  Implementations MUST be prepared to accept compliant SDP even
   if it would not conform to the requirements for generating SDP in

   this specification.



> The second paragraph of section 5.4 is confusing. A slight restructuring of
> the sentences would remove much of the potential confusion, I think. I
> suggest replacing the first sentence (which is very complex) with this:
> "After calling setLocalDescription, the application MAY modify the SDP to
> reduce the capabilities in the offer before sending it to the far side, as
> long as it remains a valid SDP offer and specifies a subset of what was in
> the original offer. Likewise, an application that has received an offer
> from a peer MAY modify the received SDP, subject to those same constraints,
> before calling setRemoteDescription."
>
> The first paragraph of section 5.7.1 is simply restating requirements from
> RFC4566. Restating normative requirements like that has led to interop
> problems through unintended introduced ambiguity and spec maintenance
> problems. Please consider rewriting the paragraph to say "RFC4566 says" and
> avoid the 2119 keywords.
>

We considered this, but found that a) RFC4566 is clearly cited, and b) the
actual restatement was very minor, really just affecting the discussion of
the v= and o= lines. As a result we concluded that pointing the reader
elsewhere just for those two lines did not seem like an improvement.


>
> On page 69, at "If the application attempt to transmit DTMF when using a
> media format that does not have a corresponding telephone-event format,
> this MUST result in an error". This sentence is out-of-place. The section
> is about applying a remote description. If the document needs to retain the
> sentence, it belongs off in some "processing media" section. In particular,
> the current placement of text is confusing about what and when an error
> could be returned, and it could be misread to say that an error should be
> returned to the setRemoteDescription call.
>
> Nits:
>
> Section 1.2 second paragraph - "This was rejected based on a feeling". Can
> you write something that speaks to consensus here? "Based on a feeling"
> isn't quite right. Maybe "using the argument"?
>
> PeerConnection is used first at the next to last paragraph of section 3.
> Please add a reference at that point.
>
> "LS" (lipsync) is first used at 4.1.2, with no context for what it is.
> Please add a reference.
>
> The concept of a "pending local description" is used in sections 3.5.1,
> 4.1.6, and 4.1.7  but isn't really explained until much later in the
> document. Please provide forward references, or move a description of what
> a pending description is earlier in the document.
>
> In 4.1.7 (create Answer) why would calling setLocalDescription cause the
> answer to be a _pending_ local description. I think it's the full on local
> description at that point, not a pending one?
>
> At 4.1.17's first paragraph: Why is "if parsed successfully" necessary to
> call out? I suggest removing the phrase.
>
> 4.2.3 talks about setting direction properties, but the values that can be
> set aren't called out (and even then only by inference from a list in an
> example) in section 4.2.5. Should there be explicit pointers to the api doc
> here? (And in section 4.2.6?)
>
> There are two paragraphs on page 50 that start "The next step is to". They
> are both referring to the same step. I suggest combining the paragraphs.
>
> The 4th bullet on page 64 is ambiguous at "this m= section". It looks like
> this bullet should just be merged with the previous bullet.
>
> The second paragraph of 6.8 starts "Next, ". I think it should start
> "First, ".
>
> It's not clear what the "Or," in the first bullet on page 65 is referring
> to. Are you trying to say "If the m= section is not new, and the ICE ufrag
> and password values have changed" or something else?
>

The intent here is as stated, "if the m= section is not new and the values
have changed". We discussed this but concluded that the meaning of the
current text was clear.


>
> In the last paragraph of section 8 at "programmer MUST recognize". That is
> not an appropriate use of 2119. I suggest "needs to be aware" instead of
> "MUST recognize".
>
> Micro Nits:
>
> Suggested change to the first sentence of 1.1
>
>   OLD:
>
>     The thinking behind WebRTC call setup has been to fully specify and
> control the media plane, but to leave the signaling plane up to the
> application as much as possible.
>
>   New:
>
>     WebRTC call setup has been designed to focus on controlling the media
> plane, leaving signaling plane behavior up to the application as much as
> possible.
>
> The first full bullet on page 18 has a sentence that starts "Note that when
> considering". Please change that to simply "When considering". As written,
> there is an implication that this is a consequence of something specified
> somewhere else.
>
> The verb "surfaced" appears three times in the document without support or
> definition. Can you replace them with simpler language?
>
> At the second to last sub-bullet at the end of page 66, please remove "note
> that". The sentence is stronger without it.
>
> I noted these sections as particularly hard to read when going through the
> document linearly. I don't have concrete suggestions for improvement, but
> perhaps other eyes (if they agree the sections could use improvement) can
> come up with something:
>  - First sentence of the first paragraph on page 19.
>  - 2nd sentence of the 4th paragraph on page 19.
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

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

<div dir=3D"ltr">Thanks for this careful review. A new version of the docum=
ent (-22) has been posted which addresses almost all of these comments, wit=
h a few exceptions noted below.<div><br></div><div>Diff:=C2=A0<a href=3D"ht=
tps://www.ietf.org/rfcdiff?url1=3Ddraft-ietf-rtcweb-jsep-21&amp;url2=3Ddraf=
t-ietf-rtcweb-jsep-22&amp;difftype=3D--html">https://www.ietf.org/rfcdiff?u=
rl1=3Ddraft-ietf-rtcweb-jsep-21&amp;url2=3Ddraft-ietf-rtcweb-jsep-22&amp;di=
fftype=3D--html</a></div><div class=3D"gmail_extra"><br><div class=3D"gmail=
_quote">On Tue, Aug 8, 2017 at 12:31 PM, Robert Sparks <span dir=3D"ltr">&l=
t;<a href=3D"mailto:rjsparks@nostrum.com" target=3D"_blank">rjsparks@nostru=
m.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex">Reviewer: Robert Sparks<br>
Review result: Almost Ready<br>
<br>
I am the assigned Gen-ART reviewer for this draft. The General Area<br>
Review Team (Gen-ART) reviews all IETF documents being processed<br>
by the IESG for the IETF Chair.=C2=A0 Please treat these comments just<br>
like any other last call comments.<br>
<br>
For more information, please see the FAQ at<br>
<br>
&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" rel=3D"norefe=
rrer" target=3D"_blank">https://trac.ietf.org/trac/<wbr>gen/wiki/GenArtfaq<=
/a>&gt;.<br>
<br>
Document: draft-ietf-rtcweb-jsep-21<br>
Reviewer: Robert Sparks<br>
Review Date: 2017-08-08<br>
IETF LC End Date: 2017-08-11<br>
IESG Telechat date: Not scheduled for a telechat<br>
<br>
Summary: Almost ready for publication as a Proposed Standard RFC, but with<=
br>
issues that need to be addressed before publishing<br>
<br>
Major issues:<br>
<br>
The last paragraph of 5.1 needs more context. Why woudn&#39;t you expect th=
e<br>
re-offer to fail, given that you already know the peer is using the older<b=
r>
profile strings? It&#39;s not clear from the email list and proceedings how=
 the<br>
document ended up with this particular text.<br>
<br>
Minor issues:<br>
<br>
Second paragraph of 3.2, last sentence: at &quot;these parameters or reject=
<br>
them&quot; - &quot;these&quot; and &quot;them&quot; have ambiguous antecede=
nts. It&#39;s not clear if you<br>
are trying to point to the parameters that don&#39;t follow the earlier sta=
ted<br>
rule, or all parameters. The sentence is complex. Splitting it up and<br>
finding a way to avoid the need for the semicolon will likely make it<br>
easier to say what you mean.<br>
<br>
Last paragraph on page 5 - first sentence: at &quot;One way to mitigate thi=
s&quot; -<br>
&quot;this&quot; has an unclear antecedent. Did you mean &quot;One way to r=
educe the<br>
complexity of the application&#39;s responsibilities&quot;?<br>
<br>
Last paragraph of 3.5.2.1 - &quot;all of these fields&quot; is ambiguous. P=
lease<br>
state precisely which fields you mean.<br>
<br>
Odd edge: The description createAnswer (in 4.1.7) leaves open the<br>
possibility that the application could call createAnswer twice<br>
(back-to-back with no intervening calls to other APIs) with different<br>
values in the options parameter. Is this ok? If not, should there be<br>
language that says not to do that somewhere?<br>
<br>
Slightly more than minor maybe: The first paragraph of 5.1.2 has at least a=
<br>
reference error. UDP/TLS/RTP/SAVPF is not specified in RFC7850. It&#39;s in=
<br>
RFC5764. Assuming that this is only a reference error, then the last<br>
sentence seems like a stray. It doesn&#39;t seem to be in the right context=
<br>
(&quot;this advertisement&quot; doesn&#39;t cast back to the discussion of =
the two<br>
profiles above it, which are both UDP only). Please clarify the sentence,<b=
r>
giving it the right context, or remove it.<br>
<br>
The fourth sentence of the second bullet of section 5.2.1 is confusing. (It=
<br>
starts &quot;It is RECOMMENDED that the &lt;sess-id&gt;&quot;.) RFC3265 req=
uires the<br>
initial sess-id high-order bit to be zero. As written, this can be read to<=
br>
say that setting that bit to zero is only RECOMMENDED, and that it&#39;s<br=
>
possible to have sess-ids that are something other than 64 bits. You mean<b=
r>
to say &quot;Do what 3265 says to do and make the lower 63 bits random&quot=
;. Here&#39;s<br>
one possible replacement for the sentence: &quot;RFC 3265 requires that the=
<br>
high-order bit of the initial &lt;sess-id&gt; be zero. It is RECOMMENDED th=
at the<br>
remaining 63 bits be initially set to a cryptographically random value.&quo=
t;<br>
<br>
The last paragraph of 5.3.1 prohibits the same attributes from generated<br=
>
answers that are prohibited in generated offers. Consider adding text for<b=
r>
what to do if an offer shows up from a peer with some of those prohibited<b=
r>
attributes.<br></blockquote><div><br></div><div>This is covered by the last=
 paragraph on page 43:</div><div><br></div><pre class=3D"gmail-newpage" sty=
le=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)=
">   Note that these requirements are in some cases stricter than those of
   SDP.  Implementations MUST be prepared to accept compliant SDP even
   if it would not conform to the requirements for generating SDP in=C2=A0<=
/pre><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0=
px;margin-bottom:0px;color:rgb(0,0,0)">   this specification.<span style=3D=
"font-family:arial,sans-serif;font-size:small;color:rgb(34,34,34)">=C2=A0</=
span></pre><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin=
-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span style=3D"font-family:ari=
al,sans-serif;font-size:small;color:rgb(34,34,34)"><br></span></pre><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex">
<br>
The second paragraph of section 5.4 is confusing. A slight restructuring of=
<br>
the sentences would remove much of the potential confusion, I think. I<br>
suggest replacing the first sentence (which is very complex) with this:<br>
&quot;After calling setLocalDescription, the application MAY modify the SDP=
 to<br>
reduce the capabilities in the offer before sending it to the far side, as<=
br>
long as it remains a valid SDP offer and specifies a subset of what was in<=
br>
the original offer. Likewise, an application that has received an offer<br>
from a peer MAY modify the received SDP, subject to those same constraints,=
<br>
before calling setRemoteDescription.&quot;<br>
<br>
The first paragraph of section 5.7.1 is simply restating requirements from<=
br>
RFC4566. Restating normative requirements like that has led to interop<br>
problems through unintended introduced ambiguity and spec maintenance<br>
problems. Please consider rewriting the paragraph to say &quot;RFC4566 says=
&quot; and<br>
avoid the 2119 keywords.<br></blockquote><div><br></div><div>We considered =
this, but found that a) RFC4566 is clearly cited, and b) the actual restate=
ment was very minor, really just affecting the discussion of the v=3D and o=
=3D lines. As a result we concluded that pointing the reader elsewhere just=
 for those two lines did not seem like an improvement.</div><div>=C2=A0</di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
On page 69, at &quot;If the application attempt to transmit DTMF when using=
 a<br>
media format that does not have a corresponding telephone-event format,<br>
this MUST result in an error&quot;. This sentence is out-of-place. The sect=
ion<br>
is about applying a remote description. If the document needs to retain the=
<br>
sentence, it belongs off in some &quot;processing media&quot; section. In p=
articular,<br>
the current placement of text is confusing about what and when an error<br>
could be returned, and it could be misread to say that an error should be<b=
r>
returned to the setRemoteDescription call.<br>
<br>
Nits:<br>
<br>
Section 1.2 second paragraph - &quot;This was rejected based on a feeling&q=
uot;. Can<br>
you write something that speaks to consensus here? &quot;Based on a feeling=
&quot;<br>
isn&#39;t quite right. Maybe &quot;using the argument&quot;?<br>
<br>
PeerConnection is used first at the next to last paragraph of section 3.<br=
>
Please add a reference at that point.<br>
<br>
&quot;LS&quot; (lipsync) is first used at 4.1.2, with no context for what i=
t is.<br>
Please add a reference.<br>
<br>
The concept of a &quot;pending local description&quot; is used in sections =
3.5.1,<br>
4.1.6, and 4.1.7=C2=A0 but isn&#39;t really explained until much later in t=
he<br>
document. Please provide forward references, or move a description of what<=
br>
a pending description is earlier in the document.<br>
<br>
In 4.1.7 (create Answer) why would calling setLocalDescription cause the<br=
>
answer to be a _pending_ local description. I think it&#39;s the full on lo=
cal<br>
description at that point, not a pending one?<br>
<br>
At 4.1.17&#39;s first paragraph: Why is &quot;if parsed successfully&quot; =
necessary to<br>
call out? I suggest removing the phrase.<br>
<br>
4.2.3 talks about setting direction properties, but the values that can be<=
br>
set aren&#39;t called out (and even then only by inference from a list in a=
n<br>
example) in section 4.2.5. Should there be explicit pointers to the api doc=
<br>
here? (And in section 4.2.6?)<br>
<br>
There are two paragraphs on page 50 that start &quot;The next step is to&qu=
ot;. They<br>
are both referring to the same step. I suggest combining the paragraphs.<br=
>
<br>
The 4th bullet on page 64 is ambiguous at &quot;this m=3D section&quot;. It=
 looks like<br>
this bullet should just be merged with the previous bullet.<br>
<br>
The second paragraph of 6.8 starts &quot;Next, &quot;. I think it should st=
art<br>
&quot;First, &quot;.<br>
<br>
It&#39;s not clear what the &quot;Or,&quot; in the first bullet on page 65 =
is referring<br>
to. Are you trying to say &quot;If the m=3D section is not new, and the ICE=
 ufrag<br>
and password values have changed&quot; or something else?<br></blockquote><=
div><br></div><div>The intent here is as stated, &quot;if the m=3D section =
is not new and the values have changed&quot;. We discussed this but conclud=
ed that the meaning of the current text was clear.</div><div>=C2=A0</div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex">
<br>
In the last paragraph of section 8 at &quot;programmer MUST recognize&quot;=
. That is<br>
not an appropriate use of 2119. I suggest &quot;needs to be aware&quot; ins=
tead of<br>
&quot;MUST recognize&quot;.<br>
<br>
Micro Nits:<br>
<br>
Suggested change to the first sentence of 1.1<br>
<br>
=C2=A0 OLD:<br>
<br>
=C2=A0 =C2=A0 The thinking behind WebRTC call setup has been to fully speci=
fy and<br>
control the media plane, but to leave the signaling plane up to the<br>
application as much as possible.<br>
<br>
=C2=A0 New:<br>
<br>
=C2=A0 =C2=A0 WebRTC call setup has been designed to focus on controlling t=
he media<br>
plane, leaving signaling plane behavior up to the application as much as<br=
>
possible.<br>
<br>
The first full bullet on page 18 has a sentence that starts &quot;Note that=
 when<br>
considering&quot;. Please change that to simply &quot;When considering&quot=
;. As written,<br>
there is an implication that this is a consequence of something specified<b=
r>
somewhere else.<br>
<br>
The verb &quot;surfaced&quot; appears three times in the document without s=
upport or<br>
definition. Can you replace them with simpler language?<br>
<br>
At the second to last sub-bullet at the end of page 66, please remove &quot=
;note<br>
that&quot;. The sentence is stronger without it.<br>
<br>
I noted these sections as particularly hard to read when going through the<=
br>
document linearly. I don&#39;t have concrete suggestions for improvement, b=
ut<br>
perhaps other eyes (if they agree the sections could use improvement) can<b=
r>
come up with something:<br>
=C2=A0- First sentence of the first paragraph on page 19.<br>
=C2=A0- 2nd sentence of the 4th paragraph on page 19.<br>
<br>
<br>
______________________________<wbr>_________________<br>
rtcweb mailing list<br>
<a href=3D"mailto:rtcweb@ietf.org">rtcweb@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/rtcweb" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/rtcweb</a><br=
>
</blockquote></div><br></div></div>

--001a113f7dba5de4320557abfa73--


From nobody Sat Aug 26 23:41:22 2017
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CC8491326BB; Sat, 26 Aug 2017 23:41:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even <ron.even.tlv@gmail.com>
To: <gen-art@ietf.org>
Cc: draft-weis-gdoi-rekey-ack.all@ietf.org, ietf@ietf.org
Subject: Genart telechat review of draft-weis-gdoi-rekey-ack-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150381607469.940.14767657724848101158@ietfa.amsl.com>
Date: Sat, 26 Aug 2017 23:41:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X8RG9fW8E1imP0H0ozKEjsgen28>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 27 Aug 2017 06:41:15 -0000

Reviewer: Roni Even
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-weis-gdoi-rekey-ack-??
Reviewer: Roni Even
Review Date: 2017-08-26
IETF LC End Date: 2017-07-17
IESG Telechat date: 2017-08-31

Summary:
The document is ready for publication as a standard track RFC.

Major issues:

Minor issues:

Nits/editorial comments: 



From nobody Sun Aug 27 03:17:57 2017
Return-Path: <roni.even@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D438F1320D8; Sun, 27 Aug 2017 03:17:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jyQkwZ6oFCYA; Sun, 27 Aug 2017 03:17:48 -0700 (PDT)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 900CC1321ED; Sun, 27 Aug 2017 03:17:45 -0700 (PDT)
Received: from 172.30.72.56 (EHLO lhreml709-cah.china.huawei.com) ([172.30.72.56]) by dggrg02-dlp.huawei.com (MOS 4.4.6-GA FastPath queued) with ESMTP id AUG93414; Sun, 27 Aug 2017 18:17:41 +0800 (CST)
Received: from DGGEMM406-HUB.china.huawei.com (10.3.20.214) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.301.0; Sun, 27 Aug 2017 07:33:24 +0100
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.138]) by DGGEMM406-HUB.china.huawei.com ([10.3.20.214]) with mapi id 14.03.0301.000; Sun, 27 Aug 2017 14:33:17 +0800
From: Roni Even <roni.even@huawei.com>
To: "Brian Weis (bew)" <bew@cisco.com>, Roni Even <ron.even.tlv@gmail.com>
CC: "draft-weis-gdoi-rekey-ack.all@ietf.org" <draft-weis-gdoi-rekey-ack.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Genart last call review of draft-weis-gdoi-rekey-ack-05
Thread-Topic: Genart last call review of draft-weis-gdoi-rekey-ack-05
Thread-Index: AQHS7lLEWzV9+32PME2mgt0Y86IjKaJjlp+AgDSJS9A=
Date: Sun, 27 Aug 2017 06:33:16 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD7FFDBC@DGGEMM506-MBX.china.huawei.com>
References: <149846423732.31797.4914828028458689510@ietfa.amsl.com> <E925AA3C-78E8-4081-9FC7-D2C46725A8F3@cisco.com>
In-Reply-To: <E925AA3C-78E8-4081-9FC7-D2C46725A8F3@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.202.75]
Content-Type: multipart/alternative; boundary="_000_6E58094ECC8D8344914996DAD28F1CCD7FFDBCDGGEMM506MBXchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090203.59A29C46.0048, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.3.138, so=2014-11-16 11:51:01, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 4598f911dd54b928e4f3521013307ce3
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yUhdrWlWIQpZeiSS-HP6tOq1ip4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 27 Aug 2017 10:17:50 -0000

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

SGkgQnJpYW4sDQpUaGFua3MNCk9LIG5vdw0KUm9uaQ0KDQpGcm9tOiBHZW4tYXJ0IFttYWlsdG86
Z2VuLWFydC1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQnJpYW4gV2VpcyAoYmV3KQ0K
U2VudDog15nXldedINeRIDI0INeZ15XXnNeZIDIwMTcgMTk6MTgNClRvOiBSb25pIEV2ZW4NCkNj
OiBkcmFmdC13ZWlzLWdkb2ktcmVrZXktYWNrLmFsbEBpZXRmLm9yZzsgZ2VuLWFydEBpZXRmLm9y
ZzsgaWV0ZkBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtHZW4tYXJ0XSBHZW5hcnQgbGFzdCBjYWxs
IHJldmlldyBvZiBkcmFmdC13ZWlzLWdkb2ktcmVrZXktYWNrLTA1DQoNCkhpIFJvbmksDQoNClRo
YW5rcyBmb3IgeW91ciBoZWxwZnVsIHJldmlldy4NCg0KT24gSnVuIDI2LCAyMDE3LCBhdCAxOjAz
IEFNLCBSb25pIEV2ZW4gPHJvbi5ldmVuLnRsdkBnbWFpbC5jb208bWFpbHRvOnJvbi5ldmVuLnRs
dkBnbWFpbC5jb20+PiB3cm90ZToNCg0KUmV2aWV3ZXI6IFJvbmkgRXZlbg0KUmV2aWV3IHJlc3Vs
dDogQWxtb3N0IFJlYWR5DQoNCkkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9y
IHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsIEFyZWENClJldmlldyBUZWFtIChHZW4tQVJUKSByZXZp
ZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQNCmJ5IHRoZSBJRVNHIGZvciB0
aGUgSUVURiBDaGFpci4gIFBsZWFzZSB0cmVhdCB0aGVzZSBjb21tZW50cyBqdXN0DQpsaWtlIGFu
eSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQoNCkZvciBtb3JlIGluZm9ybWF0aW9uLCBwbGVh
c2Ugc2VlIHRoZSBGQVEgYXQNCg0KPGh0dHBzOi8vdHJhYy5pZXRmLm9yZy90cmFjL2dlbi93aWtp
L0dlbkFydGZhcT4uDQoNCkRvY3VtZW50OiBkcmFmdC13ZWlzLWdkb2ktcmVrZXktYWNrLT8/DQpS
ZXZpZXdlcjogUm9uaSBFdmVuDQpSZXZpZXcgRGF0ZTogMjAxNy0wNi0yNg0KSUVURiBMQyBFbmQg
RGF0ZTogMjAxNy0wNy0xNw0KSUVTRyBUZWxlY2hhdCBkYXRlOiBOb3Qgc2NoZWR1bGVkIGZvciBh
IHRlbGVjaGF0DQoNClN1bW1hcnk6DQpUaGUgZG9jdW1lbnQgaXMgYWxtb3N0IHJlYWR5IGZvciBw
dWJsaWNhdGlvbiBhcyBzdGFuZGFyZCB0cmFjayBkb2N1bWVudA0KTWFqb3IgaXNzdWVzOg0KDQpN
aW5vciBpc3N1ZXM6DQoNCjEuIEluIHNlY3Rpb24gMiBpdCBzYXlzICJBIEdNICByZWNlaXZpbmcg
dGhlIEtFS19BQ0tfUkVRVUVTVEVEIGF0dHJpYnV0ZSBjYW4NCmNob29zZSB0byBpZ25vcmUgaXQs
IHRodXMgYXBwZWFyaW5nIGFzIGlmIGl0IGRvZXMgbm90IHN1cHBvcnQgdGhlDQpLRUtfQUNLX1JF
UVVFU1RFRCAgYXR0cmlidXRlLiIuIEFueSByZWFzb24gZm9yIHRoZSBHTSB0byBpZ25vcmUgdGhl
IG1lc3NhZ2U/IDIuDQpJbiBzZWN0aW9uIDQgYW5kIHNlY3Rpb24gNiBpdCBzYXlzIHRoZSB0aGUg
R00gU0hPVUxEIHNlbmQgYW4gYWNrbm93bGVkZ2VtZW50DQptZXNzYWdlLiBJcyB0aGVyZSBhIGNh
c2Ugd2hlbiB0aGUgR00gc2hvdWxkIG5vdCBzZW5kIGFuZCBpZiBub3Qgd2h5IGlzIHRoaXMgYQ0K
U0hPVUxEIGFuZCBub3QgYSBNVVNUPw0KDQpBZnRlciBjb25mZXJyaW5nLCB0aGUgYXV0aG9ycyBi
ZWxpZXZlIHRoYXQgdGhlIHJlYWwgcmVhc29uIGZvciBhIEdNIHRvIGlnbm9yZSBLRUtfQUNLX1JF
UVVFU1RFRA0KaXMgYmVjYXVzZSB0aGV5IGRvIG5vdCBzdXBwb3J0IGl0LiBBcyBzdWNoLCB3ZeKA
mXZlIGFkanVzdGVkIHRoZSB3b3JkaW5nIGluIHNldmVyYWwgcGxhY2VzIHRvIHNheSB0aGlzLg0K
QW5kIHdpdGggdGhhdCB3b3JkaW5nICBpdCBtYWtlcyBzZW5zZSBmb3IgdGhlIFNIT1VMRCB0byBi
ZWNvbWUgYSBNVVNULg0KDQozLiAgSW4gc2VjdGlvbiA2ICJBIG5vbi1yZWNlaXB0IG9mIGFuIEFj
a25vd2xlZGdlbWVudCBpcw0KYW4gaW5kaWNhdGlvbiB0aGF0IGEgR00gaXMgIGVpdGhlciB1bmFi
bGUgb3IgdW53aWxsaW5nICB0byByZXNwb25kIi4gIFdoYXQNCmFib3V0IGlmIHRoZSBBY2tub3ds
ZWRnZW1lbnQgbWVzc2FnZSB3YXMgbG9zdD8gQW55IHJlbGlhYmlsaXR5IHByb2NlZHVyZT8NCg0K
V2XigJl2ZSBjbGFyaWZpZWQgdGhhdCByZWxpYWJpbGl0eSBpcyBtb3N0IGxpa2VseSB0byBjb21l
IGZyb20gdHJhbnNtaXR0aW5nIHRoZSBHUk9VUEtFWS1QVVNIIG1lc3NhZ2UNCnNldmVyYWwgdGlt
ZXMuIFRoaXMgY29tZXMgZnJvbSBhIHJlY29tbWVuZGF0aW9uIGluIFJGQyA0MDQ2LCBhbmQgd2Xi
gJl2ZSBtYWRlIHRoaXMgbW9yZSBleHBsaWNpdC4NCg0KICAgICAgVGhlIEdDS1MgTUFZIGJlIGNv
bmZpZ3VyZWQgd2l0aCBhZGRpdGlvbmFsIHBvbGljeSBhY3Rpb25zIHN1Y2ggYXMNCiAgICAgIHRy
YW5zbWl0dGluZyB0aGUgR1JPVVBLRVktUFVTSCBtZXNzYWdlIHNldmVyYWwgdGltZXMgaW4gYSBz
aG9ydA0KICAgICAgcGVyaW9kIG9mIHRpbWUgKGFzIHN1Z2dlc3RlZCBpbiBbUkZDNDA0Nl0pLCB3
aGljaCBtaXRpZ2F0ZXMgYQ0KICAgICAgcGFja2V0IGxvc3Mgb2YgZWl0aGVyIHRoZSBHUk9VUEtF
WS1QVVNIIG1lc3NhZ2Ugb3IgYW4NCiAgICAgIEFja25vd2xlZGdlbWVudCBtZXNzYWdlLg0KDQoN
Ck5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOg0KDQoxLiBJbiBzZWN0aW9uIDYgIkFsc28gYSBHTSBt
YXkgYmUgIHdpbGxpbmcgb3IgYWJsZSB0byByZXNwb25kIHdpdGggYW4NCkdST1VQS0VZLVBVU0gg
QUNLICIgLiBJIGNhbm5vdCBwYXJzZSB0aGlzIHNlbnRlbmNlIGluIHRoZSBjb250ZXh0IG9mIHRo
ZSBzZWN0aW9uDQoNClRoZXJlIHdhcyBhIOKAnG5vdOKAnSBtaXNzaW5nLiBUaGUgc2VudGVuY2Ug
bm93IHJlYWRzDQoNCiAgIEFsc28gYSBHTSBtYXkgbm90IGJlIGFibGUgdG8gcmVzcG9uZCB3aXRo
IGFuIEdST1VQS0VZLVBVU0ggQUNLLg0KDQpMZXQgdXMga25vdyBpZiB0aGVzZSBkb27igJl0IHN1
ZmZpY2llbnRseSBhZGRyZXNzIHlvdXIgcG9pbnRzLg0KDQpUaGFua3MsDQpCcmlhbg0KLS0NCkJy
aWFuIFdlaXMNClNlY3VyaXR5LCBDU0csIENpc2NvIFN5c3RlbXMNClRlbGVwaG9uZTogKzEgNDA4
IDUyNiA0Nzk2DQpFbWFpbDogYmV3QGNpc2NvLmNvbTxtYWlsdG86YmV3QGNpc2NvLmNvbT4NCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5Ok1lbmxvOw0KCXBhbm9zZS0xOjAgMCAwIDAgMCAwIDAg
MCAwIDA7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3Jt
YWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7
DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2Vy
aWYiO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5
Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQs
IHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNv
bG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnNwYW4uRW1haWxTdHls
ZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxp
YnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXtt
c28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdv
cmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzIuMHB0IDcyLjBw
dCA3Mi4wcHQgNzIuMHB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7
fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMg
djpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lm
IGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFw
IHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlm
XS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJw
bGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5IaSBCcmlhbiw8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2Vy
aWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+VGhhbmtzPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5
N0QiPk9LIG5vdzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5Sb25pPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5
bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20g
MGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRv
cDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZyb206PC9zcGFu
PjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhv
bWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IEdlbi1hcnQgW21haWx0bzpnZW4tYXJ0
LWJvdW5jZXNAaWV0Zi5vcmddDQo8Yj5PbiBCZWhhbGYgT2YgPC9iPkJyaWFuIFdlaXMgKGJldyk8
YnI+DQo8Yj5TZW50OjwvYj4gPHNwYW4gbGFuZz0iSEUiIGRpcj0iUlRMIj7XmdeV150mbmJzcDvX
kSAyNCDXmdeV15zXmSAyMDE3IDE5OjE4PC9zcGFuPjxicj4NCjxiPlRvOjwvYj4gUm9uaSBFdmVu
PGJyPg0KPGI+Q2M6PC9iPiBkcmFmdC13ZWlzLWdkb2ktcmVrZXktYWNrLmFsbEBpZXRmLm9yZzsg
Z2VuLWFydEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTog
W0dlbi1hcnRdIEdlbmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LXdlaXMtZ2RvaS1yZWtl
eS1hY2stMDU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5I
aSBSb25pLCA8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRo
YW5rcyBmb3IgeW91ciBoZWxwZnVsIHJldmlldy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxi
bG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIEp1biAyNiwgMjAxNywgYXQgMTowMyBBTSwg
Um9uaSBFdmVuICZsdDs8YSBocmVmPSJtYWlsdG86cm9uLmV2ZW4udGx2QGdtYWlsLmNvbSI+cm9u
LmV2ZW4udGx2QGdtYWlsLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+UmV2aWV3ZXI6IFJvbmkgRXZlbjxicj4NClJldmlldyBy
ZXN1bHQ6IEFsbW9zdCBSZWFkeTxicj4NCjxicj4NCkkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQg
cmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsIEFyZWE8YnI+DQpSZXZpZXcgVGVh
bSAoR2VuLUFSVCkgcmV2aWV3cyBhbGwgSUVURiBkb2N1bWVudHMgYmVpbmcgcHJvY2Vzc2VkPGJy
Pg0KYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLiAmbmJzcDtQbGVhc2UgdHJlYXQgdGhl
c2UgY29tbWVudHMganVzdDxicj4NCmxpa2UgYW55IG90aGVyIGxhc3QgY2FsbCBjb21tZW50cy48
YnI+DQo8YnI+DQpGb3IgbW9yZSBpbmZvcm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0PGJy
Pg0KPGJyPg0KJmx0OzxhIGhyZWY9Imh0dHBzOi8vdHJhYy5pZXRmLm9yZy90cmFjL2dlbi93aWtp
L0dlbkFydGZhcSI+aHR0cHM6Ly90cmFjLmlldGYub3JnL3RyYWMvZ2VuL3dpa2kvR2VuQXJ0ZmFx
PC9hPiZndDsuPGJyPg0KPGJyPg0KRG9jdW1lbnQ6IGRyYWZ0LXdlaXMtZ2RvaS1yZWtleS1hY2st
Pz88YnI+DQpSZXZpZXdlcjogUm9uaSBFdmVuPGJyPg0KUmV2aWV3IERhdGU6IDIwMTctMDYtMjY8
YnI+DQpJRVRGIExDIEVuZCBEYXRlOiAyMDE3LTA3LTE3PGJyPg0KSUVTRyBUZWxlY2hhdCBkYXRl
OiBOb3Qgc2NoZWR1bGVkIGZvciBhIHRlbGVjaGF0PGJyPg0KPGJyPg0KU3VtbWFyeTo8YnI+DQpU
aGUgZG9jdW1lbnQgaXMgYWxtb3N0IHJlYWR5IGZvciBwdWJsaWNhdGlvbiBhcyBzdGFuZGFyZCB0
cmFjayBkb2N1bWVudDxicj4NCk1ham9yIGlzc3Vlczo8YnI+DQo8YnI+DQpNaW5vciBpc3N1ZXM6
PGJyPg0KPGJyPg0KMS4gSW4gc2VjdGlvbiAyIGl0IHNheXMgJnF1b3Q7QSBHTSAmbmJzcDtyZWNl
aXZpbmcgdGhlIEtFS19BQ0tfUkVRVUVTVEVEIGF0dHJpYnV0ZSBjYW48YnI+DQpjaG9vc2UgdG8g
aWdub3JlIGl0LCB0aHVzIGFwcGVhcmluZyBhcyBpZiBpdCBkb2VzIG5vdCBzdXBwb3J0IHRoZTxi
cj4NCktFS19BQ0tfUkVRVUVTVEVEICZuYnNwO2F0dHJpYnV0ZS4mcXVvdDsuIEFueSByZWFzb24g
Zm9yIHRoZSBHTSB0byBpZ25vcmUgdGhlIG1lc3NhZ2U/IDIuPGJyPg0KSW4gc2VjdGlvbiA0IGFu
ZCBzZWN0aW9uIDYgaXQgc2F5cyB0aGUgdGhlIEdNIFNIT1VMRCBzZW5kIGFuIGFja25vd2xlZGdl
bWVudDxicj4NCm1lc3NhZ2UuIElzIHRoZXJlIGEgY2FzZSB3aGVuIHRoZSBHTSBzaG91bGQgbm90
IHNlbmQgYW5kIGlmIG5vdCB3aHkgaXMgdGhpcyBhPGJyPg0KU0hPVUxEIGFuZCBub3QgYSBNVVNU
PyA8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QWZ0ZXIgY29uZmVycmluZywgdGhlIGF1dGhv
cnMgYmVsaWV2ZSB0aGF0IHRoZSByZWFsIHJlYXNvbiBmb3IgYSBHTSB0byBpZ25vcmUgS0VLX0FD
S19SRVFVRVNURUQ8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPmlzIGJlY2F1c2UgdGhleSBkbyBub3Qgc3VwcG9ydCBpdC4gQXMgc3VjaCwgd2XigJl2
ZSBhZGp1c3RlZCB0aGUgd29yZGluZyBpbiBzZXZlcmFsIHBsYWNlcyB0byBzYXkgdGhpcy4mbmJz
cDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFu
ZCB3aXRoIHRoYXQgd29yZGluZyAmbmJzcDtpdCBtYWtlcyBzZW5zZSBmb3IgdGhlIFNIT1VMRCB0
byBiZWNvbWUgYSBNVVNULjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGJsb2Nr
cXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjMuICZuYnNwO0luIHNlY3Rpb24gNiAmcXVv
dDtBIG5vbi1yZWNlaXB0IG9mIGFuIEFja25vd2xlZGdlbWVudCBpczxicj4NCmFuIGluZGljYXRp
b24gdGhhdCBhIEdNIGlzICZuYnNwO2VpdGhlciB1bmFibGUgb3IgdW53aWxsaW5nICZuYnNwO3Rv
IHJlc3BvbmQmcXVvdDsuICZuYnNwO1doYXQ8YnI+DQphYm91dCBpZiB0aGUgQWNrbm93bGVkZ2Vt
ZW50IG1lc3NhZ2Ugd2FzIGxvc3Q/IEFueSByZWxpYWJpbGl0eSBwcm9jZWR1cmU/PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+V2XigJl2ZSBjbGFyaWZpZWQgdGhhdCByZWxpYWJpbGl0eSBpcyBtb3N0IGxp
a2VseSB0byBjb21lIGZyb20gdHJhbnNtaXR0aW5nIHRoZSBHUk9VUEtFWS1QVVNIIG1lc3NhZ2U8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPnNldmVy
YWwgdGltZXMuIFRoaXMgY29tZXMgZnJvbSBhIHJlY29tbWVuZGF0aW9uIGluIFJGQyA0MDQ2LCBh
bmQgd2XigJl2ZSBtYWRlIHRoaXMgbW9yZSBleHBsaWNpdC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5k
OndoaXRlIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjguNXB0O2ZvbnQtZmFtaWx5OiZxdW90O01l
bmxvJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7Ij4mbmJzcDsgJm5ic3A7ICZuYnNwOyBUaGUmbmJz
cDtHQ0tTIE1BWSBiZSBjb25maWd1cmVkIHdpdGggYWRkaXRpb25hbCBwb2xpY3kgYWN0aW9ucyBz
dWNoIGFzPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
OC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7TWVubG8mcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDsiPiZu
YnNwOyAmbmJzcDsgJm5ic3A7IHRyYW5zbWl0dGluZyB0aGUgR1JPVVBLRVktUFVTSCBtZXNzYWdl
IHNldmVyYWwgdGltZXMgaW4gYSBzaG9ydDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjguNXB0O2ZvbnQtZmFtaWx5OiZxdW90O01lbmxvJnF1b3Q7LCZx
dW90O3NlcmlmJnF1b3Q7Ij4mbmJzcDsgJm5ic3A7ICZuYnNwOyBwZXJpb2Qgb2YgdGltZSAoYXMg
c3VnZ2VzdGVkIGluIFtSRkM0MDQ2XSksIHdoaWNoIG1pdGlnYXRlcyBhPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImJhY2tn
cm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OC41cHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7TWVubG8mcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDsiPiZuYnNwOyAmbmJzcDsgJm5ic3A7IHBh
Y2tldCBsb3NzIG9mIGVpdGhlciB0aGUgR1JPVVBLRVktUFVTSCBtZXNzYWdlIG9yIGFuPG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9ImJhY2tncm91bmQ6d2hpdGUiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OC41cHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7TWVubG8mcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDsiPiZuYnNwOyAmbmJzcDsg
Jm5ic3A7IEFja25vd2xlZGdlbWVudCBtZXNzYWdlLiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0
O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48YnI+DQpOaXRzL2VkaXRvcmlhbCBjb21tZW50czo8YnI+DQo8YnI+DQoxLiBJbiBzZWN0aW9u
IDYgJnF1b3Q7QWxzbyBhIEdNIG1heSBiZSAmbmJzcDt3aWxsaW5nIG9yIGFibGUgdG8gcmVzcG9u
ZCB3aXRoIGFuPGJyPg0KR1JPVVBLRVktUFVTSCBBQ0sgJnF1b3Q7IC4gSSBjYW5ub3QgcGFyc2Ug
dGhpcyBzZW50ZW5jZSBpbiB0aGUgY29udGV4dCBvZiB0aGUgc2VjdGlvbjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
VGhlcmUgd2FzIGEg4oCcbm904oCdIG1pc3NpbmcuIFRoZSBzZW50ZW5jZSBub3cgcmVhZHM8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJiYWNrZ3JvdW5kOndoaXRlIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjguNXB0O2Zv
bnQtZmFtaWx5OiZxdW90O01lbmxvJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7Ij4mbmJzcDsgJm5i
c3A7QWxzbyBhIEdNIG1heSBub3QgYmUmbmJzcDthYmxlIHRvIHJlc3BvbmQgd2l0aCBhbiBHUk9V
UEtFWS1QVVNIIEFDSy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+TGV0IHVzIGtub3cgaWYgdGhlc2UgZG9u4oCZdCBz
dWZmaWNpZW50bHkgYWRkcmVzcyB5b3VyIHBvaW50cy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhhbmtzLDxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QnJpYW48bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi0tJm5ic3A7PGJyPg0KQnJpYW4gV2Vp
czxicj4NClNlY3VyaXR5LCBDU0csIENpc2NvIFN5c3RlbXM8YnI+DQpUZWxlcGhvbmU6ICYjNDM7
MSA0MDggNTI2IDQ3OTY8YnI+DQpFbWFpbDogPGEgaHJlZj0ibWFpbHRvOmJld0BjaXNjby5jb20i
PmJld0BjaXNjby5jb208L2E+IDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
Ym9keT4NCjwvaHRtbD4NCg==

--_000_6E58094ECC8D8344914996DAD28F1CCD7FFDBCDGGEMM506MBXchina_--


From nobody Sun Aug 27 06:29:46 2017
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 03E0A13219E; Sun, 27 Aug 2017 06:29:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Adam Montville <adam.w.montville@gmail.com>
To: <secdir@ietf.org>
Cc: draft-ietf-opsawg-mud.all@ietf.org, opsawg@ietf.org, ietf@ietf.org
Subject: Secdir early review of draft-ietf-opsawg-mud-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150384057895.866.9675653302394719026@ietfa.amsl.com>
Date: Sun, 27 Aug 2017 06:29:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/s7L20t1pdtnpGYg7e-pGcjrF_L4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 27 Aug 2017 13:29:39 -0000

Reviewer: Adam Montville
Review result: Has Issues

Hi. I am the assigned SECDIR reviewer for this document's early review reuqest.
What follows is what I would write if this were a last call review, more or
less.

The summary of the review is ready with (potential) issues and nits.

The draft is interesting in that it seeks to define a mechanism for devices to
self-identify in a trusted manner, so that the infrastructure in which the
devices operate may appropriately manage security-related configurations
pertaining to those devices. The examples provided are exclusively network flow
realted, but extension points are provided for future capabilities.

The mechanism is defined as a Manufacturer Usage Description, as expressed in a
file containing a YANG-based JSON serialization. This file is obtained from a
device-provided URL, which is trusted to varying degrees and communitacted to
the infrastructure in one of several different ways (i.e. via DHCP, 802.1AR,
802.1AB). Thus, the device emits a URL via one of the identified methods, and
the URL is used to obtain the MUD, which can then be interpreted and
appropriate action taken.

The security consideraitons appear well-thought and is worth a read.

This seems like a solution intended to take time to reach full potential, given
that there are devices deployed in the real world that know nothing about this,
and that there are different trust mechanisms at play. The intent seems less
about perfection and more about moving the needle, which seems to be the right
approach.

Finally, I found myself wondering if this type of appraoch - communicating
intended use - could be extended to software installed on general purpose
devices. For example, it would be interesting to consider how a given installed
software package could communicate not only its intended use, but it's
preferred configuration.

Some questions to consider (these are potential issues):

At the top of page 9, the draft describes controller behavior for mobile
devices - configurations should be removed when the device is removed. Does
this apply also to intermittent devices? When would a device be considered
"removed" instead of simply powered down? Also, when reading that paragraph I
began wondering about the load on Web servers serving MUD files - not that this
draft should say anything about it, but that it's something manufacturers are
going to have to consider and account for.

Is a stronger statement needed on the first bullet of section 4? Should it
read: Anything not explicitly permitted MUST be denied? Similarly for other
requirements in MUD file processing. At about this point, I began wondering if
additional security considerations may be required for the controller.

Section 9.2 describes DHCP server behavior, and is written in a manner
presuming the DHCP server knows what's happening with these building blocks. I
am not a DHCP expert, so there may be something in DHCP instructing a server to
ignore everything it doesn't understand, but if that is not the case, then what
is expected to happen when DHCP is not expecting these options and is not going
to ignore them?

Nits follow:

First paragraph of section 1.5: s/another example might to follow/another
example might be to follow/

Recommend the following for definition of Thing: the device emitting a MUD URL.

Suggest striking last two sentences of Manufacturer definition, as irrelevant.

Is there a way to make the ASCII art in section 1.7 a little cleaner? One
possibility is to move the right side of the bounding box to the left by two or
three places. Also, the arrows to the line text isn't necessary (e.g.
"----->get URL->" is cleaner as "---get URL--->").

Second bullet on page 11: s/other otherwise/otherwise/

Should there be a newline after "<CODE BEGINS>" at the start of section 6?

On page 17: s/end(ed)/end(s\/ed)/  Basically, the sentence without "ended"
should read, "Information about when support ends, and when to refresh."

Vertial spacing could be improved for the first bit in section 9, so that the
look/feel surrounding OPTION_MUD_URL_V4 matches that of OPTION_MUD_URL_v6

Section 11, first sentence: s/link layer protocols/link layer protocol/


From nobody Sun Aug 27 18:02:17 2017
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8D09132661; Sun, 27 Aug 2017 18:02:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P5EqyPQZssUp; Sun, 27 Aug 2017 18:02:06 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D973F13264C; Sun, 27 Aug 2017 18:02:04 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML713-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DNK81042; Mon, 28 Aug 2017 01:02:01 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 28 Aug 2017 02:01:59 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Mon, 28 Aug 2017 09:01:56 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, Joe Touch <touch@strayalpha.com>, IETF discussion list <ietf@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, "draft-ietf-ospf-encapsulation-cap@ietf.org" <draft-ietf-ospf-encapsulation-cap@ietf.org>
CC: TSV Dir <tsv-dir@ietf.org>
Subject: =?utf-8?B?562U5aSNOiBbT1NQRl0gdHN2LWRpciByZXZpZXcgb2YgZHJhZnQtaWV0Zi1v?= =?utf-8?Q?spf-encapsulation-cap-06?=
Thread-Topic: [OSPF] tsv-dir review of draft-ietf-ospf-encapsulation-cap-06
Thread-Index: AQHTHJL4HJxqaOXXQEa3hG1IIeBfiaKTdSMAgAWD9RA=
Date: Mon, 28 Aug 2017 01:01:45 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BC0B725@NKGEML515-MBX.china.huawei.com>
References: <150280426212.21081.15543071828535131713.idtracker@ietfa.amsl.com> <7ca66dbe-1437-482d-a785-d5e48a558ccb@strayalpha.com> <D5C4B293.C38FA%acee@cisco.com>
In-Reply-To: <D5C4B293.C38FA%acee@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.184.181]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090204.59A36B89.0044, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 5a87bc95096cacfd64cfb2d208cf4e2e
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hqzfajfGWFAXtZgpf14_RycBvQk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 28 Aug 2017 01:02:09 -0000

SGkgQWNlZSwNCg0KU3VyZSwgd2Ugd2lsbCByZXNwb25kIHRvIGFsbCByZXZpZXdzIHNvb24uDQoN
CkJlc3QgcmVnYXJkcywNClhpYW9odQ0KDQo+IC0tLS0t6YKu5Lu25Y6f5Lu2LS0tLS0NCj4g5Y+R
5Lu25Lq6OiBBY2VlIExpbmRlbSAoYWNlZSkgW21haWx0bzphY2VlQGNpc2NvLmNvbV0NCj4g5Y+R
6YCB5pe26Ze0OiAyMDE35bm0OOaciDI15pelIDQ6NDcNCj4g5pS25Lu25Lq6OiBKb2UgVG91Y2g7
IElFVEYgZGlzY3Vzc2lvbiBsaXN0OyBvc3BmQGlldGYub3JnOw0KPiBkcmFmdC1pZXRmLW9zcGYt
ZW5jYXBzdWxhdGlvbi1jYXBAaWV0Zi5vcmcNCj4g5oqE6YCBOiBUU1YgRGlyDQo+IOS4u+mimDog
UmU6IFtPU1BGXSB0c3YtZGlyIHJldmlldyBvZiBkcmFmdC1pZXRmLW9zcGYtZW5jYXBzdWxhdGlv
bi1jYXAtMDYNCj4gDQo+IFhpYW9odSBhbmQgb3RoZXIgQ28tYXV0aG9ycywNCj4gDQo+IFBsZWFz
ZSByZXNwb25kIHRvIEpvZeKAmXMgY29tbWVudHMuIFlvdSBkb27igJl0IG5lY2Vzc2FyaWx5IGhh
dmUgdG8gYWRkcmVzcw0KPiB0aGVtIGFsbCBhcyBoZSBhcyBzdWdnZXN0ZWQgYnV0IHBsZWFzZSBy
ZXNwb25kLg0KPiANCj4gSm9lLA0KPiANCj4gRm9yIHlvdXIgY29tbWVudCBvbiB0aGUgaW50cm9k
dWN0aW9uLCBjYW4geW91IHByb3ZpZGUgdGV4dD8NCj4gDQo+IFRoYW5rcywNCj4gQWNlZQ0KPiAN
Cj4gT24gOC8yNC8xNywgMTI6MzkgQU0sICJPU1BGIG9uIGJlaGFsZiBvZiBKb2UgVG91Y2giIDxv
c3BmLWJvdW5jZXNAaWV0Zi5vcmcNCj4gb24gYmVoYWxmIG9mIHRvdWNoQHN0cmF5YWxwaGEuY29t
PiB3cm90ZToNCj4gDQo+ID5IaSwgYWxsLA0KPiA+DQo+ID5JIGFtIHRoZSBhc3NpZ25lZCBUU1Yt
QVJUIHJldmlld2VyIGZvcg0KPiA+ZHJhZnQtaWV0Zi1vc3BmLWVuY2Fwc3VsYXRpb24tY2FwDQo+
ID4NCj4gPkZvciBiYWNrZ3JvdW5kIG9uIFRTVi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0K
PiA+PGh0dHBzOi8vdHJhYy5pZXRmLm9yZy90cmFjL3Rzdi93aWtpL1RTVi1EaXJlY3RvcmF0ZT4u
DQo+ID4NCj4gPlBsZWFzZSByZXNvbHZlIHRoZXNlIGNvbW1lbnRzIGFsb25nIHdpdGggYW55IG90
aGVyIExhc3QgQ2FsbCBjb21tZW50cw0KPiA+eW91IG1heSByZWNlaXZlLg0KPiA+DQo+ID5Kb2UN
Cj4gPg0KPiA+LS0tLS0tDQo+ID4NCj4gPkkndmUgcmV2aWV3ZWQgdGhpcyBkb2N1bWVudCBhcyBw
YXJ0IG9mIHRoZSB0cmFuc3BvcnQgYXJlYSBkaXJlY3RvcmF0ZSdzDQo+ID5vbmdvaW5nIGVmZm9y
dCB0byByZXZpZXcga2V5IElFVEYgZG9jdW1lbnRzLiBUaGVzZSBjb21tZW50cyB3ZXJlDQo+ID53
cml0dGVuIHByaW1hcmlseSBmb3IgdGhlIHRyYW5zcG9ydCBhcmVhIGRpcmVjdG9ycywgYnV0IGFy
ZSBjb3BpZWQgdG8NCj4gPnRoZSBkb2N1bWVudCdzIGF1dGhvcnMgZm9yIHRoZWlyIGluZm9ybWF0
aW9uIGFuZCB0byBhbGxvdyB0aGVtIHRvDQo+ID5hZGRyZXNzIGFueSBpc3N1ZXMgcmFpc2VkLiBX
aGVuIGRvbmUgYXQgdGhlIHRpbWUgb2YgSUVURiBMYXN0IENhbGwsIHRoZQ0KPiA+YXV0aG9ycyBz
aG91bGQgY29uc2lkZXIgdGhpcyByZXZpZXcgdG9nZXRoZXIgd2l0aCBhbnkgb3RoZXIgbGFzdC1j
YWxsDQo+ID5jb21tZW50cyB0aGV5IHJlY2VpdmUuIFBsZWFzZSBhbHdheXMgQ0MgdHN2LWRpckBp
ZXRmLm9yZyBpZiB5b3UgcmVwbHkNCj4gPnRvIG9yIGZvcndhcmQgdGhpcyByZXZpZXcuDQo+ID4N
Cj4gPiJUaGlzIGRyYWZ0IGhhcyBzZXJpb3VzIGlzc3VlcywgZGVzY3JpYmVkIGluIHRoZSByZXZp
ZXcsIGFuZCBuZWVkcyB0bw0KPiA+YmUgcmV0aG91Z2h0LiINCj4gPg0KPiA+QWx0aG91Z2ggSSBm
b3VuZCBubyB0cmFuc3BvcnQgaXNzdWVzLCB0aGVyZSBhcmUgbWFueSBmdW5kYW1lbnRhbA0KPiA+
cHJvYmxlbXMgdGhhdCBuZWVkIHRvIGJlIGNvcnJlY3RlZCBiZWZvcmUgdGhpcyBkb2N1bWVudCBz
aG91bGQgcHJvY2VlZC4NCj4gPlRoZXNlIGFyZSBzdW1tYXJpemVkIGJlbG93Lg0KPiA+DQo+ID5T
ZWMxOiBUaGUgaW50cm9kdWN0aW9uIGp1bXBzIHRvbyBxdWlja2x5IGludG8gYSBsaXN0IG9mIHNp
dHVhdGlvbnMgaW4NCj4gPndoaWNoIHR1bm5lbHMgYXJlIHVzZWQsIHR3byBvZiB3aGljaCBhcmUg
ZW1lcmdpbmcgKGN1cnJlbnRseSBvbmx5DQo+ID5kcmFmdHMpLiBUaGVyZSBhcmUgbWFueSBiZXR0
ZXIgYW5kIG1vcmUgZXN0YWJsaXNoZWQgZXhhbXBsZXMgKGdvaW5nDQo+ID5iYWNrIHRvIHRoZSBN
LUJvbmUsIHRoZSA2LUJvbmUsIGV0Yy4sIHRvIFZQTnMsIG5ldHdvcmsgdmlydHVhbGl6YXRpb24s
IGV0Yy4pLg0KPiA+VGVybXMgYXJlIHVzZWQgYmVmb3JlIGRlZmluZWQgKHdoYXQgaXMgYW4gaW5n
cmVzcz8gYXJlIHlvdSByZWZlcnJpbmcgdG8NCj4gPnRoZSByb3V0ZXIgb3IgaG9zdCBhdCB3aGlj
aCBhIHR1bm5lbCBpcyBhdHRhY2hlZCwgb3IgdGhlIGlucHV0IHRvIHRoZQ0KPiA+dHVubmVsIGl0
c2VsZj8pLiBUaGUgbGFzdCB0d28gc2VudGVuY2VzIHNob3VsZCBiZWdpbiB0aGUgaW50cm8sIHdo
aWNoDQo+ID5zaG91bGQgZXhwYW5kIGFuZCBleHBsYWluIHdoYXQgaXMgbWVhbnQgKGUuZy4sIGJ5
ICJlZ3Jlc3MgdHVubmVsaW5nIg0KPiA+YW5kIHRoZSByZWFzb24gZm9yIHdhbnRpbmcgdG8gZW5j
b2RlIHR1bm5lbHMgYXMgTFNBcy4NCj4gPg0KPiA+U2VjMjogVGhlIHRlcm1pbm9sb2d5IHNlY3Rp
b24gaXMgaW5jb21wbGV0ZS4gVGhlIHRlcm1zIHR1bm5lbCwgaW5ncmVzcywNCj4gPmVncmVzcywg
ZWdyZXNzIHR1bm5lbGluZywgZXRjLiBhcmUgbm90IGRlZmluZWQgaW4gUkZDNzc3MC4gT25seSB0
aGUgTFNBDQo+ID50ZXJtaW5vbG9neSBpcyByZWxldmFudCBmcm9tIHRoYXQgUkZDLiBPdGhlciB0
ZXJtcyBuZWVkIHRvIGJlIGRlZmluZWQNCj4gPmluIHRoaXMgZG9jIG9yIHVzZWQgZnJvbSBvdGhl
cnMuDQo+ID4NCj4gPlNlYzM6IFRoaXMgc2VjdGlvbiBpcyB3cml0dGVuIGFzIGlmIHRoZSAiRW5j
YXBzdWxhdGlvbiBDYXBhYmlsaXR5IFRMViINCj4gPmlzIGFscmVhZHkgZGVmaW5lZCAoaW4gUkZD
Nzc3MCksIHJhdGhlciB0aGFuIGJlaW5nIGRlZmluZWQgaGVyZWluLiBUaGUNCj4gPnNlY3Rpb24g
dGl0bGUgZG9lc24ndCBtYXRjaCB0aGlzIG5hbWUsIHdoaWNoIGlzIGNvbmZ1c2luZy4gVGhlIHRl
cm0gVExWDQo+ID5pcyBpdHNlbGYgY29uZnVzaW5nLCBhcyB0aGlzIGlzIHJlYWxseSBhIHNpbmds
ZSBUTFYgb2YgdGhlIFJJIE9wYXF1ZQ0KPiA+TFNBIHNldCBvZiB0eXBlcywgd2hpY2ggaXRzZWxm
IGlzIHJlcHJlc2VudGVkIGFzIGEgKHN1YilUTFYgbGlzdC4gSQ0KPiA+YXBwcmVjaWF0ZSB0aGF0
IHRoaXMgdGVybWlub2xvZ3kgd2FzIG1hZGUgY29uZnVzaW5nIGluIHByZXZpb3VzLA0KPiA+ZXN0
YWJsaXNoZWQgZG9jdW1lbnRzLCBidXQgYSBiaXQgb2YgZXhwbGFuYXRpb24gd291bGQgZ28gYSBs
b25nIHdheSAtDQo+ID5hcyB3b3VsZCBzaG93aW5nIHRoZSB0b3AtbGV2ZWwgT1NQRiBSSSBPcGFx
dWUgTFNBIGFuZCB3aGVyZSB0aGUgbmV3DQo+ID5UQkQxIHZhbHVlIHdvdWxkIGFwcGVhciAtIGJl
Zm9yZSBkaXZpbmcgaW50byB0aGUgc3RydWN0dXJlIGluc2lkZSB0aGlzDQo+ID5uZXcgIlRMViIu
DQo+ID4NCj4gPlNlYyA0OiB0aGUgZGlzY3Vzc2lvbiBzaG91bGQgY2xhcmlmeSB3aGF0IGhhcHBl
bnMgaWYgdGhlIGxlbmd0aCBmaWVsZA0KPiA+aXMgbG9uZ2VyIHRoYW4gdGhlIGZpZWxkcyBpbmRp
Y2F0ZWQgYnkgdGhlIHN1Yi1UTFZzIChpcyB0aGlzIGFuIGVycm9yDQo+ID5vciBwYWRkaW5nIHRv
IGJlIGlnbm9yZWQ7IGRvZXMgdGhlIGxhdHRlciBwcmVzZW50IGEgY292ZXJ0IGNoYW5uZWwpLg0K
PiA+YWRkaXRpb25hbGx5LCB0aGlzIHNlY3Rpb24gcmVmZXJzIHRvIFJGQzU1MTIgLSB3aGljaCBp
cyBiZWluZyBvYnNvbGV0ZWQNCj4gPmJ5IGlldGYtaWRyLXR1bm5lbC1lbmNhcHMgLSBhbmQgdGhp
cyBwZW5kaW5nIElEIGlzIHVzZWQgYXMgdGhlIHByaW1hcnkNCj4gPnJlZmVyZW5jZSBpbiBTZWNz
IDUuMSBhbmQgNS4yLiBSZWZlcmVuY2VzIHRvIFJGQzU1MTIgc2hvdWxkIGJlIHJlcGxhY2VkDQo+
ID53aXRoIHRoYXQgSUQgKHdoaWNoIEknbGwgYXNzdW1lIHdpbGwgYmUgcHVibGlzaGVkIGNvbmN1
cnJlbnRseSkuDQo+ID4NCj4gPlNlYyA1OiB0aGlzIHNlY3Rpb24gcmVmZXJzIHRvIHRoZSBjb25j
ZXB0IG9mIGFuICJpbnZhbGlkIiBzdWItVExWOw0KPiA+Z2l2ZW4gdGhlIHByZXZpb3VzIHNlbnRl
bmNlIGV4cGxhaW5zIHRoYXQgdW5rbm93biBzdWItVExWcyBhcmUgc2lsZW50bHkNCj4gPmlnbm9y
ZWQsIHRoZW4gd2hhdCBleGFjdGx5IGlzIGFuIGludmFsaWQgc3ViLVRMVj8gSXQgZnVydGhlciBp
c24ndA0KPiA+Y2xlYXIgd2h5IDIgb2N0ZXRzIG9mIHR5cGUgYW5kIDIgb2N0ZXRzIG9mIGxlbmd0
aCBhcmUgbmVlZGVkIChncmFudGVkDQo+ID5pdCBwcm92aWRlcyBhbGlnbm1lbnQsIGJ1dCBpcyB0
aGF0IHJlYWxseSBpbXBvcnRhbnQgZm9yIHRoaXMgc29ydCBvZg0KPiA+YXBwbGljYXRpb24tbGF5
ZXIgcHJvdG9jb2w/KQ0KPiA+DQo+ID5TZWMgNS4xIGFuZCA1LjI6IGl0IGlzIHVuY2xlYXIgd2h5
IHRoZSB0d28gZnVuZGFtZW50YWwgc3ViLVRMVnMgb2YgdGhpcw0KPiA+VExWIGFyZSBkZWZpbmVk
IGVsc2V3aGVyZTsgaW4gc3BlY2lmaWMsIHRoZSBleGFtcGxlIG9mIHRoZSBzdWItVExWDQo+ID5z
aG91bGQgYXBwZWFyIGhlcmUgKGFjdHVhbGx5IGZvciBlYWNoIG9mIHRoZSBzdWItVExWcykuDQo+
ID4NCj4gPlNlYyA1LjMgaW5mZXJzIElQIGFkZHJlc3MgdmVyc2lvbiBmcm9tIGxlbmd0aCwgd2hl
biB0aGUgdmVyc2lvbiBjb3VsZA0KPiA+KHNob3VsZCkgZWFzaWx5IGVuY29kZWQgZWl0aGVyIGFz
IGRpZmZlcmVudCB0eXBlcyAoeW91IGhhdmUgNjVLIG9mDQo+ID50aGVtISkgb3IgdXNpbmcgYW4g
YWRkaXRpb25hbCBmZXcgYml0cyAoZS5nLiwgY2FydmVkIG91dCBvZiB0aGUNCj4gPmV4Y2Vzc2Vz
IG5vdGVkIGluIFNlYyA1KS4NCj4gPg0KPiA+U2VjIDUuNCAtIEkgaGFkIHRvIHRocmVhZCB0aHJv
dWdoIHNldmVyYWwgZGlmZmVyZW50IHNlY3Rpb25zIG9mIHRoZSBJRFINCj4gPklEIHRvIGZpZ3Vy
ZSBvdXQgd2hhdCBDb2xvciBtZWFudCBhbmQgaG93IGl0IGlzIHVzZWQuIEdyYW50ZWQgdGhhdCBp
cyBhDQo+ID5kaWZmZXJlbnQgcHJvYmxlbSBpbiBhIGRpZmZlcmVudCBkb2MsIElNTyB0aGlzIGRv
YyBzaG91bGQgaW5jbHVkZQ0KPiA+ZW5vdWdoIG9mIGEgc3VtbWFyeSB0aGF0IHRoaXMgc29ydCBv
ZiAndHJhY2ViYWNrJyBzaG91bGQgbm90IGJlIG5lZWRlZA0KPiA+dG8gdW5kZXJzdGFuZCB3aGF0
IGlzIGJlaW5nIGRlc2NyaWJlZC4gRnVydGhlciwgdGhlIG90aGVyIGRvYyBkb2Vzbid0DQo+ID5l
dmVuIGV4cGxhaW4gQ29sb3Igc3VmZmljaWVudGx5LCBJTU8uDQo+ID4NCj4gPlNlY3MgNS42IGFu
ZCA1LjcgLSBUaGVyZSBhcmUgbWFueSBydWxlcyBmb3IgaG93IHRoZSBvdXRlciBlbmNhcHN1bGF0
aW9uDQo+ID5oZWFkZXIgaXMgY29tcG9zZWQsIGFuZCBtYW55IGZpZWxkcyBpdCBtYXkgYWZmZWN0
IGJleW9uZCBRb1MgYW5kIFVEUA0KPiA+ZGVzdGluYXRpb24gcG9ydC4gVGhpcyBzZWN0aW9uIGlz
IGluY29tcGxldGUgaW4gZGVzY3JpYmluZyB2YWx1ZXMgZm9yDQo+ID50aGUgb3V0ZXIgaGVhZGVy
KHMpIG9yIHJlbGF0aW9uc2hpcHMgdG8gdGhlIGlubmVyIGhlYWRlcihzKS4NCj4gPg0KPiA+U2Vj
IDYgLSBJIHdvdWxkIGVuY291cmFnZSBtb3ZpbmcgdGhpcyBzZWN0aW9uIGVhcmxpZXIsIGJlZm9y
ZSB0aGUNCj4gPmRldGFpbHMgb2YgaG93IHRoZSBMU0EgaXMgY29tcG9zZWQuDQo+ID4NCj4gPlNl
YyA3IC0gdGhlIGRvY3VtZW50IHNob3VsZCBkZXNjcmliZSB3aGVyZSBleHBlcmltZW50YWwgdmFs
dWVzDQo+ID5jYW4vc2hvdWxkIGJlIHNhZmVseSB1c2VkIGFuZCBob3cgY29sbGlzaW9ucyBhcmUg
aGFuZGxlZDsgaXQgc2hvdWxkDQo+ID5hbHNvIGV4cGxhaW4gd2hhdCBoYXBwZW5zIHdoZW4gYSBy
ZXNlcnZlZCB2YWx1ZSBpcyBzZWVuIGluIGFuIExTQS4NCj4gPg0KPiA+LS0tLQ0KPiA+DQo+ID4N
Cj4gPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID5P
U1BGIG1haWxpbmcgbGlzdA0KPiA+T1NQRkBpZXRmLm9yZw0KPiA+aHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9vc3BmDQoNCg==


From nobody Mon Aug 28 12:24:43 2017
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2076513293A; Mon, 28 Aug 2017 12:24:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Elwyn Davies <elwynd@dial.pipex.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-teas-pce-central-control.all@ietf.org, ietf@ietf.org, teas@ietf.org
Subject: Genart telechat review of draft-ietf-teas-pce-central-control-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.59.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150394826804.19875.11489576374495678242@ietfa.amsl.com>
Date: Mon, 28 Aug 2017 12:24:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fbxXXTh-3i4KQ1iVR1ncoBRh8rA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 28 Aug 2017 19:24:28 -0000

Reviewer: Elwyn Davies
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-teas-pce-central-control-04
Reviewer: Elwyn Davies
Review Date: 2017-08-28
IETF LC End Date: 2017-08-24
IESG Telechat date: 2017-08-31

Summary: Thanks for addressing my Last Call comments on -03.  The new version
is ready with one introduced nit.  Also I am still of the abstract is somewhat
overlong.

Nit:
s6, para 2: The SDN term 'northbound' has appeared in the new version. Needs
brief explanation.

Major issues:

Minor issues:

Nits/editorial comments:



From nobody Mon Aug 28 17:29:43 2017
Return-Path: <sajassi@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FCBC1321DF; Mon, 28 Aug 2017 17:29:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.519
X-Spam-Level: 
X-Spam-Status: No, score=-14.519 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1tdGZj21ecak; Mon, 28 Aug 2017 17:29:19 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48D87124207; Mon, 28 Aug 2017 17:29:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=228315; q=dns/txt; s=iport; t=1503966559; x=1505176159; h=from:to:cc:subject:date:message-id:mime-version; bh=SVp/uEwfJCQQGp+81CdcSZ08qXV2Ln+LyrbGrchdkiA=; b=l/Gp1kv5qelcYSodiSq6rtR7qLE2yNUfD5PaS2PqunN83qlRXXG6Ke7D y+nK3J5/SKeHS4Szg1TAZznvlSJIDmWYcxQgtyAsHyyxgOI1TJVuwtNCg Tl9jERkZw7Gmh7h4NW5DdD0J1ZYZLI+Iv29ySQnkM0giSEuoql89DdJDi 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ABCADftKRZ/51dJa1TChkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYJvPi1kgRUHnieBcXeVLw6CBCyBOwGDX4QAQBcBAgEBAQEBAQF?= =?us-ascii?q?rKIUZBhoBTAYFBxIBCBQkAQY5FBMEAQ0FFAeJMmQQsWGLZgEBAQEBAQEDAQEBA?= =?us-ascii?q?QEBASGDKoICgzABghtYNYQ5EQUOOAyFSAWKAYcghnIXiDoCh1SDDUmJGoISWoU?= =?us-ascii?q?Mg32BJ4VMljwBDxICNIENdxVJhRgFF4FndgGIWgEEIYEMgQ8BAQE?=
X-IronPort-AV: E=Sophos;i="5.41,442,1498521600";  d="scan'208,217";a="278138942"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Aug 2017 00:29:16 +0000
Received: from XCH-RTP-001.cisco.com (xch-rtp-001.cisco.com [64.101.220.141]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id v7T0TFIL025494 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 29 Aug 2017 00:29:16 GMT
Received: from xch-rtp-005.cisco.com (64.101.220.145) by XCH-RTP-001.cisco.com (64.101.220.141) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Mon, 28 Aug 2017 20:29:14 -0400
Received: from xch-rtp-005.cisco.com ([64.101.220.145]) by XCH-RTP-005.cisco.com ([64.101.220.145]) with mapi id 15.00.1263.000; Mon, 28 Aug 2017 20:29:14 -0400
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: Dale Worley <worley@ariadne.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-bess-evpn-etree.all@ietf.org" <draft-ietf-bess-evpn-etree.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "bess@ietf.org" <bess@ietf.org>
Subject: Re: Genart last call review of draft-ietf-bess-evpn-etree-12
Thread-Topic: Genart last call review of draft-ietf-bess-evpn-etree-12
Thread-Index: AQHTIF3X8pcLT8C3EEqXwUjGvmksiQ==
Date: Tue, 29 Aug 2017 00:29:14 +0000
Message-ID: <D5C97FC2.217743%sajassi@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.1.161129
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.19.76.52]
Content-Type: multipart/alternative; boundary="_000_D5C97FC2217743sajassiciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/I4ItBol8Hny-pwR5u2bcdwJDnf0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 29 Aug 2017 00:29:29 -0000

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

Hi Dale,

Having someone who doesn=92t have EVPN background to read this document tho=
roughly and comments on it, helps greatly with the overall readability of t=
his document. So, thank you for your comments. I tried to address all your =
comments. Please see inline for my replies.

On 8/7/17, 7:29 PM, "Dale Worley" <worley@ariadne.com<mailto:worley@ariadne=
.com>> wrote:

Reviewer: Dale Worley
Review result: On the Right Track

I am the assigned Gen-ART reviewer for this draft.  The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document:  draft-ietf-bess-evpn-etree-12
Reviewer:  Dale R. Worley
Review Date:  2017-08-07
IETF LC End Date:  2017-08-09
IESG Telechat date:  2017-08-17

Summary:

This draft is on the right track but has open issues, described in the
review.  A few of the issues are directly technical.

Reading this draft, I have the sense that it isn't so much a
specification as the description of an idea, which is that EVPN can be
used to implement E-Tree functionality.  It reads as if someone who is
extremely knowledgeable about EVPN is outlining the idea to someone
similar, given that various details don't seem to be worked out
completely and that in several places there are alternative
implementation methods that are mentioned but do not seem to be
rigorously enumerated.  The document seems to more describe *class* of
ways of implementing E-Trees, and not a rigidly delimited class.

As far as I can tell, the idea works, but I suspect that an
implementor would not just be following the specification but
completing it in many respects.  Given that the document seems to
extend the mechanisms of RFC 7432, I suspect that an implementor would
have to carefully work out the details of all the BGP announcements,
and that not all implementations would interoperate.  E.g., "This Leaf
label is advertised to other PE devices, using the E-TREE Extended
Community" sounds to me like it's very under-specified.

The way forward seems to be clear:  The draft needs to be edited
carefully, filling in the missing details and making more explicit and
rigid the various implementation alternatives.  It might be worth
enumerating all of the mentioned implementation choices in one place,
as successful interoperation requires that all devices in a VPN are
using the same choices.  And I think interoperation needs to be
emphasized -- two devices that implement this draft should
interoperate if they are configured to have the same choices of the
implementation choices enumerated in the draft.  Otherwise, this draft
is just the outline for a dozen vendors' similar-but-not-interoperable
proprietary products.

Abstract

   This document
   discusses how those functional requirements can be easily met with
   Ethernet VPN (EVPN) and how EVPN offers a more efficient
   implementation of these functions.

"More efficient" than what?  The abstract reads as if this document is
an alternative method of implementing E-Tree, but I read well into the
draft before it became clear that this draft is an alternative to RFC
7387, rather than that this draft and RFC 7387 are an alternative to
something else.  The abstract does not specifically state all of the
relationships between the specifications it mentions.

I modified both the abstract and the introduction to say:
=94=85 and how such a solution can offer a more efficient implementation of=
 these functions than that of [RFC7796].=94

I also added the following sentence to the introduction:
"Since this document specifies a solution based on [RFC7432], it requires t=
he readers to have the knowledge of [RFC7432] as prerequisite."

And although this mechanism is described as "more efficient", there
doesn't seem to be any discussion of how it is more efficient.  You
don't need a lot of detail for this, but it would be helpful if there
was at least a brief description of what way it is more efficient and
some indication of the degree.

Now, there is, because it compares it with [RF7796] and section 3.1 describ=
es why this solution is more efficient than [RFC7796].

Also, what is relationship between "EVPN" and this document?  Is EVPN
a widely-known technology whose name need not be footnoted?  Is it
something defined in this document?  Importantly, is the usage in this
document a subset within some defined EVPN specification, or is it a
modification/extension of EVPN?

Based on someone else=92s comment, the text has already been modified to sp=
ell out EVPN and [RFC7432]. The abstract now says:
"This document discusses how those functional requirements can be met with =
a solution based on Ethernet VPN (EVPN) [RFC7432] with some extensions and =
how such a solution can offer a more efficient implementation of these func=
tions than that of [RFC7796].=94

Similar modifications has been made to the introduction section.

   This document makes use of the
   most significant bit of the scope governed by the IANA registry
   created by RFC7385, and hence updates RFC7385 accordingly.

The use of "scope" is peculiar here.  Generally, "scope" refers to a
region of some sort of space, so one would say "scope value" or "scope
value field" to refer to a group of bits that designate a scope.  But
checking with RFC 7385 and the IANA registry page for "Border Gateway
Protocol (BGP) Parameters", I am unable to find any occurrence of the
word "scope".  And other than a very similar passage in section 1,
"scope" only appears in this document in the phrase "scope of this
document".  Perhaps "scope" should be "tunnel type"?

I have got rid off the word =93scope=94 and have changed both the abstract =
and introduction to:
"This document makes use of the most significant bit of the PMSI tunnel typ=
e governed by the IANA registry created by RFC7385, and hence updates RFC73=
85 accordingly."

Table of Contents

What is the capitalization rule you're using for section titles?
E.g., sections 3.2.{1,2,3,4} are capitalized in a decidedly different
way that other sections.

Made them all consistent now.

1  Introduction

   The Metro Ethernet Forum (MEF) has defined a rooted-multipoint
   Ethernet service known as Ethernet Tree (E-Tree) [MEF6.1]. In an E-
   Tree service, Attachment Circuits (ACs) are labeled as either Root or
   Leaf ACs. Root ACs can communicate with all other ACs. Leaf ACs can
   communicate with Root ACs but not with other Leaf ACs.

Given the use of "rooted-multipoint", it seems that there is to be
exactly one Root AC per virtual Ethernet, as rooted trees have exactly
one root node.  Where or not that is true is very important for the
conceptual model of the service, but is not stated clearly
here. Perhaps there is a terminology problem, as when I see "rooted"
and "tree" in a sentence, I assume that the "tree" is "rooted", i.e.,
it has exactly one root.  (Similarly in Wikipedia, "Rooted-MultiPoint"
[sic] redirects to "Point-to-multipoint", which says "providing
multiple paths from a *single* [my emphasis] location to multiple
locations".)  However, the last sentences of section 2.1 suggest that
an E-Tree might have more than one Root.

Both MEF 6.1 and RFC7387 (referenced in this document) allow for multiple r=
oots in an E-TREE which itself is defined as a rooted-multipoint service.

Subtle point:  If there are multiple Roots, the text implies that all
Roots can communicate with all other Roots.  It might be worth
mentioning that explicitly, as the naive reader might overlook it.
Indeed, it is possible within this model that all endpoints are Roots,
in which case the VPN is completely connected.

1st paragraph of section 1 (Introduction) explicitly says that:
"Root ACs can communicate with all other ACs. Leaf ACs can communicate with=
 Root ACs but not with other Leaf ACs.=94
In order to make it even more clear, I am changing it to the following:
"Root ACs can communicate with all other ACs (both Root and Leaf ACs). Leaf=
 ACs can communicate with Root ACs but not with other Leaf ACs."

Also, it seems that in scenario 3 of section 2 that a single AC could
have multiple endpoints on it some of which are Root and some are
Leaf, which doesn't fit within the description in this paragraph.

Change the 1st paragraph of the introduction to:
"The Metro Ethernet Forum (MEF) has defined a rooted-multipoint Ethernet se=
rvice known as Ethernet Tree (E-Tree) [MEF6.1]. In an E-Tree service, a cus=
tomer site that is typically represented by an Attachment Circuits (AC) (bu=
t may also be represented by a MAC address) is labeled as either a Root or =
a Leaf site. Root sites can communicate with all other customer sites (both=
 Root and Leaf sites). However, Leaf sites can communicate with Root sites =
but not with other Leaf sits. In this document unless explicitly mentioned =
otherwise, a site is always represented by an AC.=94

Also changed the 1st sentence of section 2.3 to:
"In this scenario, a customer Root or Leaf site is represented by a MAC add=
ress and a PE may receive traffic from both Root AND Leaf sites on a single=
 Attachment Circuit (AC) of an EVI."

(In general, meticulously editing the Introduction section is
extremely helpful to readers who aren't already thoroughly familiar
with the subject.)

   [RFC7387] proposes the solution framework for supporting E-Tree
   service in MPLS networks.

I think this should be "a solution framework".  If one says "the solution
framework", then there is in some way only one solution framework, and
the RFC would "state" it.  Saying that the RFC "proposes" a framework
shows that there could be others that could be proposed.  Similarly in
the next sentence would be "... of an overall solution ...".

Done.


   The document identifies the functional
   components of the overall solution to emulate E-Tree services in
   addition to Ethernet LAN (E-LAN) services on an existing MPLS
   network.

The relationship of E-LAN to E-Tree is not clear, and how the phrase
"on an existing MPLS network" attaches to either is not clear.  I
think you mean at least:

   The document identifies the functional components of the overall
   solution to emulate E-Tree services on an existing MPLS network.

and that the document does the same for E-LAN.  I suspect that there
is some implied relationship between E-Tree and E-LAN, other than that
solution frameworks are described in RFC 7387.

However, the term "E-LAN" does not appear anywhere else in this
document, is it important to include it?  And given that E-Tree gets
its own reference to describe its functional specification, shouldn't
there be a reference giving the functional specification of "E-LAN"?
(As opposed to the implementation specification in RFC 7387.)

Modified the 2nd para of section 1 to:
=93=85 The document identifies the functional components of an overall solu=
tion to emulate E-Tree services in MPLS networks in addition to multipoint-=
to-multipoint Ethernet LAN (E-LAN) services specified in [RFC7432] and [RFC=
7623]."

   [RFC7432] is a solution for multipoint L2VPN services, with advanced
   multi-homing capabilities, using BGP for distributing customer/client
   MAC address reach-ability information over the MPLS/IP network.
   [RFC7623] combines the functionality of EVPN with [802.1ah] Provider
   Backbone Bridging (PBB) for MAC address scalability.

The structure of this paragraph suggests that "EVPN" is defined by RFC
7432, but I had to look at 7432 to verify that.  Perhaps "[RFC7432]
defines EVPN, a solution for ..."?

Done.


"[802.1ah]" appears to be a reference, but there is no entry in
section 9 for it.

Added a reference in section 9.

   This document discusses how the functional requirements for E-Tree
   service can be met with (PBB-)EVPN and how (PBB-)EVPN offers a more
   efficient implementation of these functions.

This paragraph has some of the same problems as the abstract.  But I
am now starting to suspect that the document is proposing using EVPN
as a way to provide E-Tree service *instead of* using the RFC 7387
proposal.  If that is so, this sentence needs to end "a more efficient
implementation of these functions than RFC7387.", and the third
sentence of the Abstract should start "This document discusses how the
functional requirements for E-Tree can be ..." (making clear that it
logically succeeds the first sentence, not the second), and the use of
"EVPN" in the Abstract needs to reference RFC 7432.

Modified the text to make it very clear:
"This document discusses how the functional requirements for E-Tree service=
 can be met with a solution based on (PBB-)EVPN (i.e., [RFC7432] and [RFC76=
23]) with some extensions and how such a solution can offer a more efficien=
t implementation of these functions than that of [RFC7796]."

   This document makes use
   of the most significant bit of the scope governed by the IANA
   registry created by RFC7385, and hence updates RFC7385 accordingly.

The "scope" business is still unresolved.

Modified the text and removed =93scope=94:
"This document makes use of the most significant bit of the PMSI tunnel typ=
e governed by the IANA registry created by RFC7385, and hence updates RFC73=
85 accordingly. Section 2 discusses E-TREE scenarios."

Also, this sentence doesn't say what the new purpose of the bit is.
Perhaps something like, "This document repurposes the most significant
bit of the tunnel type byte governed by the IANA registry created by
RFC7385 to ...".  But that is still opaque, as few people will
immediately know the purpose of a registry referenced only by RFC
number.  Perhaps "... the Tunnel Type byte in the BGP PMSI Tunnel
attribute ...".

Change it to the following in both the Introduction section and the Abstrac=
t:
"This document makes use of the most significant bit of the "Tunnel Type" f=
ield (in PMSI Tunnel Attribute) governed by the IANA registry created by RF=
C7385, and hence updates RFC7385 accordingly."

   Section 2 discusses E-TREE scenarios.

What the proper capitalization of "E-Tree"?

Yes, it should be =93E-Tree=94. I have made the change throughout the docum=
ent.


1.1  Terminology

The text uses many acronyms which may not be widely known by people
not deeply conversant in these technologies.  It may help to put a
define many of them in section 1.1.  (E.g., "EVI" is defined well down
in the second paragraph of section 2.1, whereas it is used in the
first paragraph of that section.)

Yes, they were missing. I have already taken care of it.

2  E-Tree Scenarios

The enumeration of cases is unclear.  I think you mean for scenario 1,
"PE is exclusively Leaf or Root site(s)", etc.  But "OR" doesn't carry
that meaning unambiguously.  You could s/OR/XOR/ to make it
unambiguous, but that would be awkward and very geekish.

Also, I think "MAC address" is more correct than "MAC" here.

Change it to the following to make it more clear:
"- Either Leaf or Root site(s) per PE
- Either Leaf or Root site(s) per Attachment Circuit (AC)
- Either Leaf or Root site(s) per MAC address=94



2.1 Scenario 1: Leaf OR Root site(s) per PE

   In this scenario, a PE may receive traffic from either Root ACs OR
   Leaf ACs for a given MAC-VRF/bridge table, but not both concurrently.

There's a problem with "receive traffic from", because one can say a
PE "receives traffic from" any endpoint in the VPN -- if the traffic
is egressing from the VPN through the PE.  I think you want to phrase
it in terms of "all endpoints attached to the ACs attached to the PE
are Root endpoints or they are all Leaf endpoints".  Or you could
rephrase it in terms of ingressing traffic.  But really, Root and Leaf
are properties of endpoints much more than properties of traffic, and
it's best to use the terms accordingly.

I think with the changes already made, the above sentence is accurate. Basi=
cally, a Root AC corresponds to an AC which is connected to Root endpoint(s=
) and a Leaf AC corresponds to an AC connected to Leaf endpoint(s).

Also, the meaning of "concurrently" is probably not what you want --
strictly, it means that two things cannot happen at the same time, but
it implies that they can happen at different times.  I don't think
that is what you mean.

Removed the term =93concurrently=94.

                   +---------+            +---------+
                   |   PE1   |            |   PE2   |
    +---+          |  +---+  |  +------+  |  +---+  |            +---+
    |CE1+---AC1----+--+   |  |  | MPLS |  |  |   +--+----AC2-----+CE2|
    +---+  (Root)  |  |MAC|  |  |  /IP |  |  |MAC|  |   (Leaf)   +---+
                   |  |VRF|  |  |      |  |  |VRF|  |
                   |  |   |  |  |      |  |  |   |  |            +---+
                   |  |   |  |  |      |  |  |   +--+----AC3-----+CE3|
                   |  +---+  |  +------+  |  +---+  |   (Leaf)   +---+
                   +---------+            +---------+

The figure is useful in showing the relationship of PE, AC, and CE.
(I see now that what I call an "endpoint" is generally known as a
"CE".)  But there is a shortage of connection lines.  I think
something like this would be clearer:

                   +---------+            +---------+
                   |   PE1   |            |   PE2   |
    +---+          |  +---+  |  +------+  |  +---+  |            +---+
    |CE1+---AC1----+--+   |  |  | MPLS |  |  |   +--+----AC2-----+CE2|
    +---+  (Root)  |  |MAC|  |  |  /IP |  |  |MAC|  |   (Leaf)   +---+
                   |  |VRF+------------------+VRF|  |
                   |  |   |  |  |      |  |  |   |  |            +---+
                   |  |   |  |  |      |  |  |   +--+----AC3-----+CE3|
                   |  +---+  |  +------+  |  +---+  |   (Leaf)   +---+
                   +---------+            +---------+

The connection among MAC VRFs is very well understood. It is not point-to-p=
oint but rather multipoint-to-point from each MAC-VRF (e.g., a single downs=
tream label is advertised by the PE to all other PE devices for its MAC-VRF=
). I am afraid representing a P2P connection between MAC-VRF may cause conf=
usions.


   In such scenario, using tailored BGP Route Target (RT) import/export
   policies among the PEs belonging to the same EVI, can be used to
   restrict the communications among Leaf PEs.

Presumably, "In such a scenario ..." but I prefer "In this scenario
...".  But the grammar has a problem, since if you elide the clause
"using ... the same EVI", it reads "In such [a] scenario ... can be
used to ...".  I think you want "In such a scenario, tailored BGP
... policies ... can be used to ...".

Changed it to:
"In this scenario, tailored BGP Route Target (RT) import/export policies am=
ong the PEs belonging to the same EVI can be used to restrict the communica=
tions among Leaf PEs."

I think you want "prevent" rather than "restrict", since by the
definition of E-Tree service, there is to be no communication between
Leaf ACs at all -- restrict has an implication that the limitation is
not absolute (and indeed, is somehow configurable).

Changed it to =93prevent=94.

   from one Leaf AC to another Leaf AC on a MAC-VRF for a given E-TREE
   EVI.

Across the whole document, it's clear that the operation of the
proposed E-Tree mechanism is absolutely independent for each EVI.
E.g., here you note that scenario 1 is "for any PE, *for any EVI*, all
CEs connected to that PE are either all Roots or all Leafs".  But you
could simply state this separation of each EVI from every other EVI at
the top of the document and not have to keep repeating it at various
places throughout the document.

The current text is reading fine to me. However, if  you have specific chan=
ges in mind, please let me know.

That is, I think it's true.  If there are ways in which the
implementation of one EVI interacts the implementation of another EVI,
that needs to be prominently flagged and carefully assessed for
causing subtle problems.  E.g., in section 3.2.1, it seems like the
advertisements of "Ethernet A-D per ES routes" may bundle information
about multiple EVIs.

2.2 Scenario 2: Leaf OR Root site(s) per AC

There is a technical question in that scenario 1 is more restrictive
than scenario 2, so any solution for scenario 2 can be used in
scenario 1.  But only alternative A is presented for scenario 1, even
though alternative B must necessarily work.  Presumably there is a
reason why alternative B is not presented for scenario 1, and I think
it should be stated.

Added the following paragraph to section 2.1:
"For this scenario, if it is desired to use only a single RT per EVI (just =
like E-LAN services in [RFC7432]), then the approach B in scenario 2 (descr=
ibed below) needs to be used."

This fact caused me some confusion when I was reading the document:
The mechanism described in 2.1 seems to be satisfactory for fulfilling
the requirements stated in paragraph 2, so but paragraph 2 introduces
"coloring" of MAC addresses.  I think that the expositions of the
three scenarios could better be done if they were all coordinated with
each other.  Perhaps the choice between alternatives A and B for
coloring MAC addresses is actually common across the three scenarios,
and what really changes between the scenarios is the efficiency
tradeoffs between the two alternatives.

Added the following paragraph to section 2.3:
"For this scenario, the approach B in scenario 2 (described above) is used =
in order to allow for single RT usage by service providers.=94
Also added the following paragraph at the end of the section 2.3:
=93In conclusion, the approach B in scenario 2 is the recommended approach =
across all the above three scenarios and the corresponding solution is deta=
iled in the following sections."

   Approach (A) would require the same data plane enhancements as
   approach (B) if MAC-VRF and bridge tables used per VLAN, are to
   remain consistent with [RFC7432] (section 6).

What is the subject of "are"?
=93MAC-VRF and bridge tables=94. I will remove =93,=94 :
=93=85 if MAC-VRF and bridge tables used per VLAN are to remain consistent =
with [RFC7432] (section 6)."

   In order to avoid data-
   plane enhancements for approach (A), multiple bridge tables per VLAN
   may be considered;

It's not clear what the difference is between "MAC-VRF and bridge
tables used per VLAN" and "multiple bridge tables per VLAN".  Can this
be described in a way that is clearer to people who are not highly
familiar with the subject?

That is described in [RFC7432] which I made it prerequisite for this docume=
nt.

   then two RTs (one for Root and another for Leaf)
   can still be used with approach (B)

This seems to be proposing some sort of mixture of alternatives A and
B.  What exactly are the alternatives that are being specified that
the implementor chooses between?

The last paragraph that I added to section 2.3 should now make it clear:
=93In conclusion, the approach B in scenario 2 is the recommended approach =
across all the above three scenarios and the corresponding solution is deta=
iled in the following sections."

2.3 Scenario 3: Leaf OR Root site(s) per MAC

   This scenario is
   not covered in both [RFC7387] and [MEF6.1]

Literally, this means "It is not true that this scenario is covered in
RFC 7387 and in MEF6.1."  But I think you mean "This scenario is not
covered in either ...".

Changed it to =93either=94 =93or=94.

   the Designated Forwarding (DF)
   filtering per [RFC7432] would not be compatible with the required
   egress filtering

Interestingly, "designated forwarding" is not mentioned anywhere else
in this draft.  Does it appear elsewhere or is it implied in the
mechanics of RFC 7432 that are used throughout this draft?

It is implied mechanism of RFC7432 and that=92s why it says =93per [RFC7432=
].


There seems to be no description of the techniques to be used in this
case.

Now there is with the addition of the two paragraphs described above to thi=
s section.

And given that it seems to be contemplated to support scenario 3,
there are numerous places in the draft where "a Root AC" and "a Leaf
AC" are not correct.  You could use "a Root CE" or "a Root site", etc.

It has already been addressed in. Added the following sentence to the end o=
f 1st para in section 1.
"In this document unless explicitly mentioned otherwise, a site is always r=
epresented by an AC."

3 Operation for EVPN

   In other words,
   [RFC7432] has inherent capability to support E-TREE services without
   defining any new BGP routes but by just defining a new BGP Extended
   Community for leaf indication as shown later in this document
   (section 5.1).

And by implication, the addition of various processing of that leaf
indication.

But this does show that this draft is not just an application of RFC
7432 but an extension of it.

Changed the 1st para of section 3 to:
"[RFC7432] defines the notion of Ethernet Segment Identifier (ESI) MPLS lab=
el used for split-horizon filtering of BUM traffic at the egress PE. Such e=
gress filtering capabilities can be leveraged in provision of E-Tree servic=
es as it will be seen shortly for BUM traffic. For know unicast traffic, ad=
ditional extensions to [RFC7432] is needed (i.e., a new BGP Extended Commun=
ity for leaf indication described in section 5.1) in order to enable ingres=
s filtering as described in detail in the following sections."

3.1 Known Unicast Traffic

   sending ... traffic over MPLS/IP core to be filtered at the egress
   PE ...

The implication seems to be that this "sending" that is avoided is
really multicast, from the ingress PE to all egress PEs.  Naively,
describing this as "over MPLS/IP core" doesn't seem to capture the
meaning, since *all* traffic is going to be send "over the MPLS/IP
core".

The paragraph is talking about know unicast filtering. I read it again and =
it is very clear (at least to me :-).


   To provide such ingress filtering for known unicast traffic, a PE
   MUST indicate to other PEs what kind of sites (root or leaf) its MAC
   addresses are associated with by advertising a leaf indication flag
   (via an Extended Community) along with each of its MAC/IP
   Advertisement routes. The lack of such flag indicates that the MAC
   address is associated with a root site. This scheme applies to all
   scenarios described in section 2.

Read literally, this paragraph says that a leaf indication flag MUST
be present on each advertisement, but then says the absence of the
flag means that it is a root side (implying that the absence of the
flag is legitimate).  There are two alternatives -- a) the flag is a
1/0 flag, with one value meaning Leaf and one meaning Root or b) the
flag is some optional field whose presence means Leaf and whose
absence means Root -- but this wording isn't quite correct for either.

Changed the paragraph to:
"To provide such ingress filtering for known unicast traffic, a PE MUST ind=
icate to other PEs what kind of sites (root or leaf) its MAC addresses are =
associated with. This is done by advertising a leaf indication flag (via an=
 Extended Community) along with each of its MAC/IP Advertisement routes lea=
rned from a leaf site. The lack of such flag indicates that the MAC address=
 is associated with a root site. This scheme applies to all scenarios descr=
ibed in section 2."

Also, this paragraph seems to be saying that the extended community is
always used to indicate Leaf/Root status (though perhaps it specifies
status by its absence).  But the descriptions in section 2 seem to be
saying that alternative A doesn't require the extended community,
which contradicts the MUST in this paragraph.

The modified paragraph above should cover this.

3.2 BUM Traffic

   This specification does not provide support for filtering BUM
   (Broadcast, Unknown, and Multicast) traffic on the ingress PE because
   it is not possible to perform filtering of BUM traffic on the ingress
   PE, as is the case with known unicast described above, due to the
   multi-destination nature of BUM traffic.

This sentence is quite awkward.  I think you can carry all of the
meaning with "This specification does not provide support for
filtering BUM (Broadcast, Unknown, and Multicast) traffic on the
ingress PE because it is not possible to do so, due to the
multi-destination nature of BUM traffic."

Done.

But the phrase "does not provide support" is not correct -- the
ingress PE fully *supports* BUM traffic (except in scenario 3), it's
just that the support doesn't include *filtering* by the ingress PE.

OK. Change it to:
"In this specification, the support for filtering BUM (Broadcast, Unknown, =
and Multicast) traffic does not include ingress filtering because it is not=
 possible to do so, due to the multi-destination nature of BUM traffic."

   the MPLS-encapsulated frames MUST be tagged with an
   indication that they originated from a Leaf AC - i.e., to be tagged
   with a Leaf label as specified in section 5.1.

As written, the sentence requires "... tagged with an indication
whether they originated ...".  The use of "that" states that all the
frames originated from a Leaf AC.

Good catch! I changed =93that=94 to =93when"


Looking ahead to section 5.1, I see that the Leaf label is
considerably longer than the 1 bit that would seem to be necessary for
this function given its description here.  And the next paragraph
suggests that the assignment of Leaf labels is complex.  It would be
helpful if you clarified here all of the functionality of Leaf labels
so the reader has context for following paragraphs.  I suspect the
meaning here is "all MPLS-encapsulated frame are tagged with labels,
and to distinguish Leaf-originated frames, they must be tagged with
labels which are known to be Leaf labels".  Also, is there only one
leaf label (for an EVI), or can there be many, perhaps one for every
Leaf AC?

Added the following sentences to the end of 1st paragraph of section 3.2:
"This Leaf label allows for disposition PE (e.g., egress PE) to perform the=
 necessary egress filtering function in data-plane similar to ESI label in =
[RFC7432]. The allocation of the Leaf label is on a per PE basis (e.g., ind=
ependent of ESI and EVI) as descried in the following sections."

   The main difference between
   downstream and upstream assigned Leaf label is that in case of
   downstream assigned not all egress PE devices need to receive the
   label just like ESI label for ingress replication procedures defined
   in [RFC7432].

This sentence isn't clear to me.  I suspect that it just needs a few
words adjusted.  Also, I suspect that it would help to move the final
clause, "just like ESI label ..." to a separate sentence.

Changed the sentence to:
"The main difference between downstream and upstream assigned Leaf label is=
 that in case of downstream assigned not all egress PE devices need to rece=
ive the label in MPLS encapsulated BUM packets just like ESI label for ingr=
ess replication procedures defined in [RFC7432]."

   On the ingress PE, the PE needs to place all its Leaf ACs for a given
   bridge domain in a single split-horizon group in order to prevent
   intra-PE forwarding among its Leaf ACs.

The phrase "bridge domain" appears only twice in this document.  I
suspect it is synonymous with some other term you are using.

It is now described in terminology section.


My belief is that a "split-horizon group" means a group of ACs that
are visible to each other.  If that is correct, this sentence needs to
be rephrased to something like "... the PE needs to place each of its
Leaf ACs for a given bridge domain into separate split-horizon groups
...".

Split-horizion group means the member of that group cannot send packets to =
each other.

   Other mechanisms
   for identifying root or leaf (e.g., on a per MAC address basis) is
   beyond the scope of this document.

Scenario 3 in section 2.3 posits that a single AC may support both
Leaf and Root endpoints.  So there must be a known method of
performing this identification on a per-MAC address basis, or else
scenario 3 cannot be implemented at present.  That doesn't require
that this document specify or describe a method of doing so, but it
seems that at this point, the document should either identify one or
more ways in which it can be done, or admit that there are no known
mechanisms at this time.  (Or perhaps that there are no known *good*
mechanisms at this time.)  Otherwise the inclusion of scenario 3 is
purely hypothetical.

Changed the sentence to:
"Other mechanisms for identifying root or leaf sites such the use of source=
 MAC address of the receiving frame are optional. The scenarios below are d=
escribed in context of Root/Leaf AC; however, they can be extended to Root/=
Leaf MAC address if needed."

The acronym "ES" us used a lot in this section, meaning "Ethernet
segment".  Is "Ethernet segment" related to "AC"?

Terminology section now provides the definition of an Ethernet Segment.

3.2.1 BUM traffic originated from a single-homed site on a leaf AC

What is the rule for capitalizing or not the words "leaf" and "root"?

They are capitalized if they are used as adjectives. Went through the doc t=
o make sure that=92s the case.


   This Leaf label is
   advertised to other PE devices, using the E-TREE Extended Community
   (section 5.1) along with an Ethernet A-D per ES route with ESI of
   zero and a set of Route Targets (RTs) corresponding to all EVIs on
   the PE with at least one leaf site per EVI.

I'm not sure, but I think you mean s/all EVIs on the PE with at least
one leaf site per EVI/all EVIs which have at least one leaf site on
the PE/.

The original text is correct but I=92ll change it to the following for bett=
er clarification:
"corresponding to all EVIs on the PE where each EVI has at least one Leaf s=
ite."

   The set of Ethernet A-D
   per ES routes may be needed if the number of Route Targets (RTs) that
   need to be sent exceed the limit on a single route per [RFC7432].

I suspect from the text that "Ethernet A-D per ES route" is a single
term, but I have no idea what it is referring to.  And I suspect that
someone has coined a shorter term to use.

This term is borrowed from [RFC7432] and there is no shorter term :-(

I suspect that one or more words in this sentence aren't quite right
and I can't parse it.  For instance "The set of ... routes may be
needed if ..." doesn't make sense -- in what way can a set of routes
be needed only under some conditions?  Perhaps it should be "A set of
... routes", if the meaning is that in some situations only one would
be needed.  Reading this again, I think you mean "Multiple Ethernet
A-D per ES routes will need to be advertised if the number of Route
Targets needed to carry the EVIs exceeds the limit on a single route."

Correct! I will change it to the following since RT=92s are carried by the =
route and not EVIs:
"Multiple Ethernet A-D per ES routes will need to be advertised if the numb=
er of Route Targets (RTs) that need to be carried exceed the limit on a sin=
gle route per [RFC7432]."

   The
   ESI for the Ethernet A-D per ES route is set to zero to indicate
   single-homed sites.

This sentence seems to be talking about some attribute of a route
(which is an operation in the control plane) while the section is
theoretically talking about BUM traffic (which is in the data plane).
This seems to be a general organizational problem, where the details
of the data plane operations are mixed with general descriptions of
the control plane operations needed to support the data plane
operations.  It would be clearer if the data plane specifications and
the control plane specifications were separated (e.g., into adjacent
paragraphs), making it more explicit what information is passed from
the control plane to the data plane.

The entire paragraph in section 3.2.1 is about advertisement of Leaf label =
in control plane.


3.2.3 BUM traffic originated from a multi-homed site on a leaf AC

The first paragraph introduces various matters that aren't discussed
in the rest of the document, or at least aren't much discussed.  If I
understand it right, these considerations don't introduce anything
unexpected other than that an AC which is multi-homed (i.e., connects
to more than one PE) must, for any single EVI, be consistently a Root
or a Leaf on all of those PEs.  If I'm correct, this paragraph could
be made much easier to understand by stating just that and avoiding
details.

However, there may be more involved than that.  E.g., "there is no
forwarding among subnets" may be an additional requirement.  It's hard
to tell, because there are only two occurrences of "forwarding among
subnets", and it's not at all clear what that term is intended to
cover.

It is important to mention that there is no forwarding among subnets. This =
sentence itself is the conclusion of some of the discussions among the co-a=
uthor.

3.2.4 BUM traffic originated from a multi-homed site on a root AC

I think the critical point of this paragraph is omitted: "... but no
Leaf label is added".  Compare with section 3.2.2.

Changed it to:
"In this scenario, both the ingress and egress PE devices follows the proce=
dure defined in [RFC7432] for adding and/or processing an ESI MPLS label - =
i.e., existing procedures for BUM traffic in [RFC7432] are sufficient and t=
here is no need to add a Leaf label.=94


3.3 E-TREE Traffic Flows for EVPN

        - Ethernet known unicast from Root to Roots & Leaf
        - Ethernet known unicast from Leaf to Root
        - Ethernet BUM traffic from Root to Roots & Leafs
        - Ethernet BUM traffic from Leaf to Roots

The grammar of these is not good.  I think you mean "Known unicast
Ethernet from ... to ...", or better "Known unicast traffic from
... to ...".

Changed it to:
=93     - Known unicast traffic from Root to Roots & Leaf
     - Known unicast traffic from Leaf to Root
     - BUM traffic from Root to Roots & Leafs
     - BUM traffic from Leaf to Roots"

   In the case where unicast flows need not be supported,
   the L2VPN PEs can avoid performing any MAC learning function.

I think you want s/unicast/known unicast/ -- there may be situations
where unicast traffic exists, and it could be handled as known unicast
traffic, but the implementation can tolerate handling all of it as
unknown traffic to avoid MAC learning.

OTOH, the choice of supporting scenario 3 requires the choice of MAC
learning, since scenario 3 prevents handling should-be-known unicast
traffic as BUM traffic.  That dependency should be noted somewhere.

Changed it to:
"In the case where only multicast and broadcast flows need to be supported,=
 the L2VPN PEs can avoid performing any MAC learning function."

3.3.1 E-Tree with MAC Learning

I see here much use of "Ethernet Segments".  It seems that it has the
same functional meaning as "ACs".  If so, only one term should be used
consistently.  If not, does the distinction need to be explained?

Ethernet Segments and ACs are different. An AC corresponds to an Ethernet t=
ag (e.g., VLAN ID) on a port (Ethernet Segment). Now that both Ethernet Seg=
ment and Ethernet tag are defined in terminology and the association betwee=
n Ethernet tag and AC is made in the introduction section, there should be =
no ambiguity.

   For the scenario
   described in section 2.1 (or possibly section 2.2), these routes are
   imported only by PEs with at least one Root site in the EVI ...

What is the condition on "possibly in section 2.2"?  (Is this a
distinction between alternatives A and B?)

Modified the sentence to the following for better clarity:
"For scenarios where two different RTs are used per EVI (one to designate R=
oot site and another to designate Leaf site), the MAC/IP Advertisement rout=
es are imported only by PEs with at least one Root site in the EVI - i.e., =
a PE with only Leaf sites will not import these routes."

   To support multicast/broadcast from Leaf to Root sites, ingress
   replication should be sufficient for most scenarios where there are
   only a few Roots (typically two).

This is introducing one of a pair of alternatives (the other one being
described in the following paragraphs).  I think the reader should be
warned in advance what the two alternatives are and what it depends on
(viz., the number of Roots).  That is, a top-down structure.

Modified the paragraph to:
=93To support multicast/broadcast from Leaf to Root sites, either ingress r=
eplication tunnels from each Leaf PE or a P2MP tree rooted at each Leaf PE =
can be used. The following two paragraphs describes when each of these tunn=
eling schemes can be used and how to signal them.=94


   If the number of Roots is large, P2MP tunnels originated at the PEs
   with Leaf sites may be used and thus there will be no need to use the
   modified PMSI tunnel attribute in section 5.2 for composite tunnel
   type.

The wording here is not quite right; I think it allows some ambiguity.
Perhaps

   If the number of Roots is large, P2MP tunnels originated at the PEs
   with Leaf sites may be used (and thus there will be no need to use
   the composite tunnel type values of the modified PMSI tunnel
   attribute in section 5.2).

Modified it to:
=93If the number of Roots is large, P2MP tunnels (e.g., mLDP or RSVP-TE) or=
iginated at the PEs with Leaf sites may be used and thus there will be no n=
eed to use the modified PMSI tunnel attribute and the composite tunnel type=
 values in section 5.2."

3.3.2 E-Tree without MAC Learning

Similarly, I suggest

   Just as in the previous section, if the number of PEs with root
   sites are only a few and thus ingress replication is desired from
   leaf PEs to these root PEs, then the composite tunnel values
   defined in section 5.2 should be used.

Modified it to:
"Just as in the previous section, if the number of Root PEs are only a few =
and thus ingress replication is desired from Leaf PEs to these root PEs, th=
en the modified PMSI attribute and the composite tunnel type values defined=
 in section 5.2 should be used."

4 Operation for PBB-EVPN

   In PBB-EVPN, the PE advertises a Root/Leaf indication along with each
   B-MAC Advertisement route, to indicate whether the associated B-MAC
   address corresponds to a Root or a Leaf site. Just like the EVPN
   case, the new E-TREE Extended Community defined in section [5.1] is
   advertised with each MAC Advertisement route.

I don't understand the distinctions here, but is "MAC Advertisement
route" correct?  There are two uses of "MAC" and 12 uses of "B-MAC" in
this section.

The precise statement should be: =93=85 with each EVPN MAC/IP Advertisement=
 route.=94

4.1 Known Unicast Traffic

   The ingress PE cross-checks this flag with the status of
   the originating site, and if both are a Leaf, then the packet is not
   forwarded.

I think this can be simplified to

   The ingress PE also checks the status of the originating site, and
   if both are a Leaf, then the packet is not forwarded.

Done.

4.2 BUM Traffic

   it updates its egress filtering (based on the
   source B-MAC address), as follows:

The stated algorithm has some important properties.  One is that if a
frame arrives, but its B-MAC address is unknown, then the frame is
forwarded.  That is, traffic not from a known Leaf is assumed to be
from a Root.  This may not be a problem, but it seems like it is an
important property of this specification, and the implementor should
be aware of it.  (OTOH, perhaps this is a generic property of
PBB-EVPN, in which case it need not be stated here.)

It is a generic property of PBB-EVPN.

Another property is that if a B-MAC changes from being a Leaf to being
a Root (by whatever means that might happen), it seems that the new
advertisements of the B-MAC as a Root will *not* remove it from the
list of blocked B-MACs of any Leaf that has seen that B-MAC advertised
as a Leaf.  Unless there is some consideration that I'm not aware of,
I think you want to revise this algorithm in this regard.

Added the following bullet to the list of bullets:
"- If the EVPN MAC/IP Advertisement route indicates that the advertised B-M=
AC has changed its designation from a Leaf to a Root and the local Ethernet=
 Segment is a Leaf, then the source B-MAC address is removed from the B-MAC=
 list corresponding to the local Ethernet Segment used for egress filtering=
 - i.e., to unblock traffic from that B-MAC address."

4.3 E-Tree without MAC Learning

   For PBB-EVPN, the handling of such traffic is per
   section 4.2 without C-MAC learning part of it at both ingress and
   egress PEs.

This could be phrased better.  And is the "non-C-MAC learning" mode of
operation of PBB-EVPN defined in the PBB-EVPN specification?  If not,
I think you might need to describe it in more detail here.

Changed it to:
"For PBB-EVPN, the handling of such traffic is per section 4.2 without the =
need for C-MAC learning (in data-plane) in I-component (C-bridge table) of =
PBB-EVPN PEs (at both ingress and egress PEs)."

5.1 E-Tree Extended Community

   It is used for leaf indication of known unicast and BUM
   traffic.

It's probably worth specifying that it indicates that the frame's
*origin* is a Leaf.

Added the sentence:
"It indicates that the frame is originated from a Leaf site."

   The label value is encoded in the high-order 20 bits of the
   Leaf Label field.

This sentence seems to be in the wrong place, since the case described
in this paragraph doesn't use the Label Value field.  It seems to me
that it would be better to incorporate this information into the value
layout:

Changed the sentence to:
"The value of the 20-bit MPLS label is encoded in the high-order 20 bits of=
 the Leaf Label field.=94


        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       | Type=3D0x06     | Sub-Type=3D0x05 | Flags(1 Octet)|  Reserved=3D0 =
  |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |  Reserved=3D0   |           Leaf Label                  |0 0 0 0|
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

5.2 PMSI Tunnel Attribute

   Composite tunnel type is advertised by the root
   PE to simultaneously indicate a non-ingress replication tunnel ...

There's a certain ambiguity here, as I first read it as "... a
(non-ingress) replication tunnel ..." -- but of course, there is no
"egress replication".  What is meant is "... a non-(ingress
replication) tunnel ...", which I think would be better expressed as
"... a non-ingress-replication tunnel ...".

Done.

   When this Composite Tunnel bit is set, the "tunnel identifier" field
   would begin with a three-octet label, followed by the actual tunnel
   identifier for the transmit tunnel.

Probably better s/would begin/begins/.  (The clause of the condition
"Composite Tunnel bit is set" does not use the subjunctive mood, so
you don't use the subjunctive mood in the consequent clause.)

Done.

It might help to add a figure

         +---------------------------------+
         |  Flags (1 octet)                |
         +---------------------------------+
         |  Tunnel Type (1 octet)          |
         +---------------------------------+
         |  P2MP MPLS Label (3 octets)     |
         +---------------------------------+
         |  Ingress Replication MPLS Label |
         |  (3 octets)                     |
         +---------------------------------+
         |  Tunnel Identifier (variable)   |
         +---------------------------------+

Done.

And s/1 octets/1 octet/ -- even though RFC 6514 makes that mistake!

Done.

   PEs that don't understand the
   new meaning of the high-order bit would treat the tunnel type as an
   undefined tunnel type and would treat the PMSI tunnel attribute as a
   malformed attribute [RFC6514].

It might be worth noting that this processing is why the composite
tunnel bit is allocated in the Tunnel Type field rather than the Flags
field.

Done.

8.1 Considerations for PMSI Tunnel Types

   The registry is to be updated, by removing the entries for 0xFB-0xFE
   and 0x0F, and replacing them by:

   Value          Meaning                            Reference
   0x0B-0x7A      Unassigned
   0x7B-0x7E      Reserved for Experimental Use      this document
   0x7F           Reserved                           this document
   0x80-0xFF      Reserved for Composite Tunnels     this document

   The allocation policy for values 0x00 to 0x7A is IETF Review
   [RFC5226]. The range for experimental use is now 0x7B-0x7E, and value
   in this range are not to be assigned. The status of 0x7F may only be
   changed through Standards Action [RFC5226].

This structure allows the high-order bit to modify the interpretation
of the other bits.  However, section 5.2 says, "... the high-order bit
of the tunnel type field (Composite Tunnel bit) is set while the
remaining low-order seven bits indicate the tunnel type as before."

I think what you intended is to change the "P-Multicast Service
Interface Tunnel (PMSI Tunnel) Tunnel Types" registry to only specify
the low-order seven bits of the Tunnel Type field, with the high-order
bit of Tunnel Type being the Composite Tunnel bit.  Conceptualized
that way, the registry changes to:

   Value          Meaning                            Reference
   0x00-0x7A      (as before)
   0x7B-0x7E      Reserved for Experimental Use      this document
   0x7F           Reserved                           this document

This implies that the octet values 0x80 to 0xFF are subdivided into
assigned, unassigned, experimental, and reserved groups in the
parallel way.

I have already changed it to:
"Value            Meaning                            Reference
0x0C-0x7A      Unassigned
0x7B-0x7E      Experimental                   this document
0x7F                Reserved                           this document
0x80-0xFA      Reserved for Composite tunnel      this document
0xFB-0xFE      Experimental                    [RFC7385]
0xFF                Reserved                           [RFC7385]
"

9.1  Normative References

   [MEF6.1] Metro Ethernet Forum, "Ethernet Services Definitions - Phase
   2", MEF 6.1, April 2008.

Can we get a URL for this?

Done.

Thanks,
Ali

[EOF]



--_000_D5C97FC2217743sajassiciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <4AE1F623546A1C4C8486E4144DDEAEDB@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Hi Dale,</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000"><br>
</font></div>
<div><font color=3D"#ff0000"><font face=3D"Calibri,sans-serif">Having someo=
ne who doesn=92t have EVPN background to read this document thoroughly and =
comments on it, helps greatly with the overall readability of this document=
. So, thank you for your comments.&nbsp;I&nbsp;tried
 to address all your comments. Please see inline for my replies.</font></fo=
nt></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
On 8/7/17, 7:29 PM, &quot;Dale Worley&quot; &lt;<a href=3D"mailto:worley@ar=
iadne.com">worley@ariadne.com</a>&gt; wrote:</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div>Reviewer: Dale Worley</div>
<div>Review result: On the Right Track</div>
<div><br>
</div>
<div>I am the assigned Gen-ART reviewer for this draft.&nbsp;&nbsp;The Gene=
ral Area</div>
<div>Review Team (Gen-ART) reviews all IETF documents being processed</div>
<div>by the IESG for the IETF Chair.&nbsp;&nbsp;Please treat these comments=
 just</div>
<div>like any other last call comments.</div>
<div><br>
</div>
<div>For more information, please see the FAQ at</div>
<div>&lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.</div>
<div><br>
</div>
<div>Document:&nbsp;&nbsp;draft-ietf-bess-evpn-etree-12</div>
<div>Reviewer:&nbsp;&nbsp;Dale R. Worley</div>
<div>Review Date:&nbsp;&nbsp;2017-08-07</div>
<div>IETF LC End Date:&nbsp;&nbsp;2017-08-09</div>
<div>IESG Telechat date:&nbsp;&nbsp;2017-08-17</div>
<div><br>
</div>
<div>Summary:</div>
<div><br>
</div>
<div>This draft is on the right track but has open issues, described in the=
</div>
<div>review.&nbsp;&nbsp;A few of the issues are directly technical.</div>
<div><br>
</div>
<div>Reading this draft, I have the sense that it isn't so much a</div>
<div>specification as the description of an idea, which is that EVPN can be=
</div>
<div>used to implement E-Tree functionality.&nbsp;&nbsp;It reads as if some=
one who is</div>
<div>extremely knowledgeable about EVPN is outlining the idea to someone</d=
iv>
<div>similar, given that various details don't seem to be worked out</div>
<div>completely and that in several places there are alternative</div>
<div>implementation methods that are mentioned but do not seem to be</div>
<div>rigorously enumerated.&nbsp;&nbsp;The document seems to more describe =
*class* of</div>
<div>ways of implementing E-Trees, and not a rigidly delimited class.</div>
<div><br>
</div>
<div>As far as I can tell, the idea works, but I suspect that an</div>
<div>implementor would not just be following the specification but</div>
<div>completing it in many respects.&nbsp;&nbsp;Given that the document see=
ms to</div>
<div>extend the mechanisms of RFC 7432, I suspect that an implementor would=
</div>
<div>have to carefully work out the details of all the BGP announcements,</=
div>
<div>and that not all implementations would interoperate.&nbsp;&nbsp;E.g., =
&quot;This Leaf</div>
<div>label is advertised to other PE devices, using the E-TREE Extended</di=
v>
<div>Community&quot; sounds to me like it's very under-specified.</div>
<div><br>
</div>
<div>The way forward seems to be clear:&nbsp;&nbsp;The draft needs to be ed=
ited</div>
<div>carefully, filling in the missing details and making more explicit and=
</div>
<div>rigid the various implementation alternatives.&nbsp;&nbsp;It might be =
worth</div>
<div>enumerating all of the mentioned implementation choices in one place,<=
/div>
<div>as successful interoperation requires that all devices in a VPN are</d=
iv>
<div>using the same choices.&nbsp;&nbsp;And I think interoperation needs to=
 be</div>
<div>emphasized -- two devices that implement this draft should</div>
<div>interoperate if they are configured to have the same choices of the</d=
iv>
<div>implementation choices enumerated in the draft.&nbsp;&nbsp;Otherwise, =
this draft</div>
<div>is just the outline for a dozen vendors' similar-but-not-interoperable=
</div>
<div>proprietary products.</div>
<div><br>
</div>
<div>Abstract</div>
<div><br>
</div>
<div>&nbsp;&nbsp; This document</div>
<div>&nbsp;&nbsp; discusses how those functional requirements can be easily=
 met with</div>
<div>&nbsp;&nbsp; Ethernet VPN (EVPN) and how EVPN offers a more efficient<=
/div>
<div>&nbsp;&nbsp; implementation of these functions.</div>
<div><br>
</div>
<div>&quot;More efficient&quot; than what?&nbsp;&nbsp;The abstract reads as=
 if this document is</div>
<div>an alternative method of implementing E-Tree, but I read well into the=
</div>
<div>draft before it became clear that this draft is an alternative to RFC<=
/div>
<div>7387, rather than that this draft and RFC 7387 are an alternative to</=
div>
<div>something else.&nbsp;&nbsp;The abstract does not specifically state al=
l of the</div>
<div>relationships between the specifications it mentions.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">I modified both the abstract and the introduction t=
o say:&nbsp;</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000"><font face=3D"Calibri,sans-serif">=94=85 and how su=
ch a solution can offer a more efficient implementation of these functions =
than that of [RFC7796].=94&nbsp;</font></font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000"><br>
</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000" face=3D"Calibri,sans-serif">I</font><font color=3D"=
#ff0000"><font face=3D"Calibri,sans-serif">&nbsp;also added the following&n=
bsp;sentence to the introduction:</font></font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000"><font face=3D"Calibri,sans-serif">&quot;</font>Sinc=
e this document specifies a solution based on [RFC7432], it requires the re=
aders to have the knowledge of [RFC7432] as prerequisite.&quot;</font></div=
>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div><br>
</div>
<div>And although this mechanism is described as &quot;more efficient&quot;=
, there</div>
<div>doesn't seem to be any discussion of how it is more efficient.&nbsp;&n=
bsp;You</div>
<div>don't need a lot of detail for this, but it would be helpful if there<=
/div>
<div>was at least a brief description of what way it is more efficient and<=
/div>
<div>some indication of the degree.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Now, there is, because it compares it with [RF7796]=
 and section 3.1 describes why this solution is more efficient than [RFC779=
6].</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div><br>
</div>
<div>Also, what is relationship between &quot;EVPN&quot; and this document?=
&nbsp;&nbsp;Is EVPN</div>
<div>a widely-known technology whose name need not be footnoted?&nbsp;&nbsp=
;Is it</div>
<div>something defined in this document?&nbsp;&nbsp;Importantly, is the usa=
ge in this</div>
<div>document a subset within some defined EVPN specification, or is it a</=
div>
<div>modification/extension of EVPN?</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Based on someone else=92s comment, the text has alr=
eady been modified to spell out EVPN and [RFC7432]. The abstract now says:<=
/font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;This document discusses how those functional =
requirements can be met with a solution based on Ethernet VPN (EVPN) [RFC74=
32] with some extensions and how such a solution can offer a more efficient=
 implementation of these functions than
 that of [RFC7796].=94</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000"><br>
</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Similar modifications has been made to the introduc=
tion section.</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp; This document makes use of the</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp; most significant bit of the scope governed by the IANA registry</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp; created by RFC7385, and hence updates RFC7385 accordingly.</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">The use o=
f &quot;scope&quot; is peculiar here.&nbsp;&nbsp;Generally, &quot;scope&quo=
t; refers to a</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">region of=
 some sort of space, so one would say &quot;scope value&quot; or &quot;scop=
e</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">value fie=
ld&quot; to refer to a group of bits that designate a scope.&nbsp;&nbsp;But=
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">checking =
with RFC 7385 and the IANA registry page for &quot;Border Gateway</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">Protocol =
(BGP) Parameters&quot;, I am unable to find any occurrence of the</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">word &quo=
t;scope&quot;.&nbsp;&nbsp;And other than a very similar passage in section =
1,</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&quot;sco=
pe&quot; only appears in this document in the phrase &quot;scope of this</d=
iv>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">document&=
quot;.&nbsp;&nbsp;Perhaps &quot;scope&quot; should be &quot;tunnel type&quo=
t;?</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">I have got rid off the word&nbsp;=93scope=94&nbsp;a=
nd have changed both the abstract and&nbsp;introduction&nbsp;to:</font></di=
v>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;This document makes use of the most significa=
nt bit of the PMSI tunnel type governed by the IANA registry created by RFC=
7385, and hence updates RFC7385 accordingly.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">Table of =
Contents</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">What is t=
he capitalization rule you're using for section titles?</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">E.g., sec=
tions 3.2.{1,2,3,4} are capitalized in a decidedly different</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">way that =
other sections.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Made them all consistent now.</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">1&nbsp;&n=
bsp;Introduction</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp; The Metro Ethernet Forum (MEF) has defined a rooted-multipoint</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp; Ethernet service known as Ethernet Tree (E-Tree) [MEF6.1]. In an E-</di=
v>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp; Tree service, Attachment Circuits (ACs) are labeled as either Root or</=
div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp; Leaf ACs. Root ACs can communicate with all other ACs. Leaf ACs can</di=
v>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp; communicate with Root ACs but not with other Leaf ACs.&nbsp;</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">Given the=
 use of &quot;rooted-multipoint&quot;, it seems that there is to be</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">exactly o=
ne Root AC per virtual Ethernet, as rooted trees have exactly</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">one root =
node.&nbsp;&nbsp;Where or not that is true is very important for the</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">conceptua=
l model of the service, but is not stated clearly</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">here. Per=
haps there is a terminology problem, as when I see &quot;rooted&quot;</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">and &quot=
;tree&quot; in a sentence, I assume that the &quot;tree&quot; is &quot;root=
ed&quot;, i.e.,</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">it has ex=
actly one root.&nbsp;&nbsp;(Similarly in Wikipedia, &quot;Rooted-MultiPoint=
&quot;</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">[sic] red=
irects to &quot;Point-to-multipoint&quot;, which says &quot;providing</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">multiple =
paths from a *single* [my emphasis] location to multiple</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">locations=
&quot;.)&nbsp;&nbsp;However, the last sentences of section 2.1 suggest that=
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">an E-Tree=
 might have more than one Root.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Both MEF 6.1 and RFC7387 (referenced in this docume=
nt) allow for multiple roots in an E-TREE which itself is defined as a root=
ed-multipoint service.</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">Subtle po=
int:&nbsp;&nbsp;If there are multiple Roots, the text implies that all</div=
>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">Roots can=
 communicate with all other Roots.&nbsp;&nbsp;It might be worth</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">mentionin=
g that explicitly, as the naive reader might overlook it.</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">Indeed, i=
t is possible within this model that all endpoints are Roots,</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">in which =
case the VPN is completely connected.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">1st paragraph of section 1 (Introduction) explicitl=
y says that:</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;Root ACs can communicate with all other ACs. =
Leaf ACs can communicate with Root ACs but not with other Leaf ACs.=94</fon=
t></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">In order to make it even more clear, I am changing =
it to the following:</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;Root ACs can communicate with all other ACs (=
both Root and Leaf ACs). Leaf ACs can communicate with Root ACs but not wit=
h other Leaf ACs.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">Also, it =
seems that in scenario 3 of section 2 that a single AC could</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">have mult=
iple endpoints on it some of which are Root and some are</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">Leaf, whi=
ch doesn't fit within the description in this paragraph.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Change the 1st paragraph of the introduction to:</f=
ont></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;The Metro Ethernet Forum (MEF) has defined a =
rooted-multipoint Ethernet service known as Ethernet Tree (E-Tree) [MEF6.1]=
. In an E-Tree service, a customer site that is typically represented by an=
 Attachment Circuits (AC) (but may also
 be represented by a MAC address) is labeled as either a Root or a Leaf sit=
e. Root sites can communicate with all other customer sites (both Root and =
Leaf sites). However, Leaf sites can communicate with Root sites but not wi=
th other Leaf sits. In this document
 unless explicitly mentioned otherwise, a site is always represented by an =
AC.=94</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000"><br>
</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Also changed the 1st sentence of section 2.3 to:</f=
ont></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;In this scenario, a customer Root or Leaf sit=
e is represented by a MAC address and a PE may receive traffic from both Ro=
ot AND Leaf sites on a single Attachment Circuit (AC) of an EVI.&quot;</fon=
t></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">(In gener=
al, meticulously editing the Introduction section is</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">extremely=
 helpful to readers who aren't already thoroughly familiar</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">with the =
subject.)</div>
</blockquote>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp; [RFC7387] proposes the solution framework for supporting E-Tree</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp; service in MPLS networks.</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">I think t=
his should be &quot;a solution framework&quot;.&nbsp;&nbsp;If one says &quo=
t;the solution</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">framework=
&quot;, then there is in some way only one solution framework, and</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">the RFC w=
ould &quot;state&quot; it.&nbsp;&nbsp;Saying that the RFC &quot;proposes&qu=
ot; a framework</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">shows tha=
t there could be others that could be proposed.&nbsp;&nbsp;Similarly in</di=
v>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">the next =
sentence would be &quot;... of an overall solution ...&quot;.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Done.</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000"><br>
</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp; The document identifies the functional</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp; components of the overall solution to emulate E-Tree services in</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp; addition to Ethernet LAN (E-LAN) services on an existing MPLS</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp; network.</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">The relat=
ionship of E-LAN to E-Tree is not clear, and how the phrase</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&quot;on =
an existing MPLS network&quot; attaches to either is not clear.&nbsp;&nbsp;=
I</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">think you=
 mean at least:</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp; The document identifies the functional components of the overall</div>
<div style=3D"font-family: Consolas, monospace; font-size: 12px;">&nbsp;&nb=
sp; solution to emulate E-Tree services on an existing MPLS network.</div>
</blockquote>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
and that the document does the same for E-LAN.&nbsp;&nbsp;I suspect that th=
ere</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
is some implied relationship between E-Tree and E-LAN, other than that</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
solution frameworks are described in RFC 7387.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
However, the term &quot;E-LAN&quot; does not appear anywhere else in this</=
div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
document, is it important to include it?&nbsp;&nbsp;And given that E-Tree g=
ets</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
its own reference to describe its functional specification, shouldn't</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
there be a reference giving the functional specification of &quot;E-LAN&quo=
t;?</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
(As opposed to the implementation specification in RFC 7387.)</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><font col=
or=3D"#ff0000">Modified the 2nd para of section 1 to:</font></div>
<div><font color=3D"#ff0000"><font face=3D"Calibri,sans-serif">=93=85 The d=
ocument identifies the functional components of an overall solution to emul=
ate E-Tree services in MPLS networks in addition to&nbsp;multipoint-to-mult=
ipoint&nbsp;Ethernet LAN (E-LAN) services specified
 in [RFC7432] and [RFC7623].&quot;</font></font></div>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; [RFC7432] is a solution for multipoint L2VPN services, with ad=
vanced</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; multi-homing capabilities, using BGP for distributing customer=
/client</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; MAC address reach-ability information over the MPLS/IP network=
.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; [RFC7623] combines the functionality of EVPN with [802.1ah] Pr=
ovider</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; Backbone Bridging (PBB) for MAC address scalability.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
The structure of this paragraph suggests that &quot;EVPN&quot; is defined b=
y RFC</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
7432, but I had to look at 7432 to verify that.&nbsp;&nbsp;Perhaps &quot;[R=
FC7432]</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
defines EVPN, a solution for ...&quot;?</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Done.</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&quot;[802.1ah]&quot; appears to be a reference, but there is no entry in</=
div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
section 9 for it.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Added a reference in section 9.</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; This document discusses how the functional requirements for E-=
Tree</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; service can be met with (PBB-)EVPN and how (PBB-)EVPN offers a=
 more</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; efficient implementation of these functions.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
This paragraph has some of the same problems as the abstract.&nbsp;&nbsp;Bu=
t I</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
am now starting to suspect that the document is proposing using EVPN</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
as a way to provide E-Tree service *instead of* using the RFC 7387</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
proposal.&nbsp;&nbsp;If that is so, this sentence needs to end &quot;a more=
 efficient</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
implementation of these functions than RFC7387.&quot;, and the third</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
sentence of the Abstract should start &quot;This document discusses how the=
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
functional requirements for E-Tree can be ...&quot; (making clear that it</=
div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
logically succeeds the first sentence, not the second), and the use of</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&quot;EVPN&quot; in the Abstract needs to reference RFC 7432.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Modified the text to make it very clear:</font></di=
v>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;This document discusses how the functional re=
quirements for E-Tree service can be met with a solution based on (PBB-)EVP=
N (i.e., [RFC7432] and [RFC7623]) with some extensions and how such a solut=
ion can offer a more efficient implementation
 of these functions than that of [RFC7796].&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; This document makes use</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; of the most significant bit of the scope governed by the IANA<=
/div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; registry created by RFC7385, and hence updates RFC7385 accordi=
ngly.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
The &quot;scope&quot; business is still unresolved.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Modified the text and removed =93scope=94:</font></=
div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;This document makes use of the most significa=
nt bit of the PMSI tunnel type governed by the IANA registry created by RFC=
7385, and hence updates RFC7385 accordingly. Section 2 discusses E-TREE sce=
narios.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Also, this sentence doesn't say what the new purpose of the bit is.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Perhaps something like, &quot;This document repurposes the most significant=
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
bit of the tunnel type byte governed by the IANA registry created by</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
RFC7385 to ...&quot;.&nbsp;&nbsp;But that is still opaque, as few people wi=
ll</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
immediately know the purpose of a registry referenced only by RFC</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
number.&nbsp;&nbsp;Perhaps &quot;... the Tunnel Type byte in the BGP PMSI T=
unnel</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
attribute ...&quot;.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Change it to the following in both the Introduction=
 section and the Abstract:</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;This document makes use of the most significa=
nt bit of the &quot;Tunnel Type&quot; field (in PMSI Tunnel Attribute) gove=
rned by the IANA registry created by RFC7385, and hence updates RFC7385 acc=
ordingly.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; Section 2 discusses E-TREE scenarios.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
What the proper capitalization of &quot;E-Tree&quot;?</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Yes, it should be =93E-Tree=94. I have made the cha=
nge throughout the document.</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
1.1&nbsp;&nbsp;Terminology</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
The text uses many acronyms which may not be widely known by people</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
not deeply conversant in these technologies.&nbsp;&nbsp;It may help to put =
a</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
define many of them in section 1.1.&nbsp;&nbsp;(E.g., &quot;EVI&quot; is de=
fined well down</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
in the second paragraph of section 2.1, whereas it is used in the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
first paragraph of that section.)</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Yes, they were missing. I have already taken care o=
f it.</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
2&nbsp;&nbsp;E-Tree Scenarios</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
The enumeration of cases is unclear.&nbsp;&nbsp;I think you mean for scenar=
io 1,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&quot;PE is exclusively Leaf or Root site(s)&quot;, etc.&nbsp;&nbsp;But &qu=
ot;OR&quot; doesn't carry</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
that meaning unambiguously.&nbsp;&nbsp;You could s/OR/XOR/ to make it</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
unambiguous, but that would be awkward and very geekish.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Also, I think &quot;MAC address&quot; is more correct than &quot;MAC&quot; =
here.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Change it to the following to make it more clear:</=
font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;- Either Leaf or Root site(s) per PE</font></=
div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">- Either Leaf or Root site(s) per Attachment Circui=
t (AC)</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">- Either Leaf or Root site(s) per MAC address=94</f=
ont></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
2.1 Scenario 1: Leaf OR Root site(s) per PE</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; In this scenario, a PE may receive traffic from either Root AC=
s OR</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; Leaf ACs for a given MAC-VRF/bridge table, but not both concur=
rently.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
There's a problem with &quot;receive traffic from&quot;, because one can sa=
y a</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
PE &quot;receives traffic from&quot; any endpoint in the VPN -- if the traf=
fic</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
is egressing from the VPN through the PE.&nbsp;&nbsp;I think you want to ph=
rase</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
it in terms of &quot;all endpoints attached to the ACs attached to the PE</=
div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
are Root endpoints or they are all Leaf endpoints&quot;.&nbsp;&nbsp;Or you =
could</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
rephrase it in terms of ingressing traffic.&nbsp;&nbsp;But really, Root and=
 Leaf</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
are properties of endpoints much more than properties of traffic, and</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
it's best to use the terms accordingly.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">I think with the changes already made, the above&nb=
sp;sentence is accurate. Basically, a Root AC corresponds to an AC which is=
 connected to Root endpoint(s) and a Leaf AC corresponds to an AC connected=
 to Leaf endpoint(s).&nbsp;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Also, the meaning of &quot;concurrently&quot; is probably not what you want=
 --</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
strictly, it means that two things cannot happen at the same time, but</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
it implies that they can happen at different times.&nbsp;&nbsp;I don't thin=
k</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
that is what you mean.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Removed the term&nbsp;=93concurrently=94.</font></d=
iv>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;---------&#43;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#43;---------&#43;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; PE1&nbsp;&nbsp; |&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;=
 PE2&nbsp;&nbsp; |</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&#43;---&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&#43;---&#43;&nbsp;&nbsp;|&nbsp;&nbsp;&#=
43;------&#43;&nbsp;&nbsp;|&nbsp;&nbsp;&#43;---&#43;&nbsp;&nbsp;|&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#43;---&#43;=
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;|CE1&#43;---AC1----&#43;--&#43;&nbsp;&nbsp; |&nbsp;=
&nbsp;|&nbsp;&nbsp;| MPLS |&nbsp;&nbsp;|&nbsp;&nbsp;|&nbsp;&nbsp; &#43;--&#=
43;----AC2-----&#43;CE2|</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&#43;---&#43;&nbsp;&nbsp;(Root)&nbsp;&nbsp;|&nbsp;&=
nbsp;|MAC|&nbsp;&nbsp;|&nbsp;&nbsp;|&nbsp;&nbsp;/IP |&nbsp;&nbsp;|&nbsp;&nb=
sp;|MAC|&nbsp;&nbsp;|&nbsp;&nbsp; (Leaf)&nbsp;&nbsp; &#43;---&#43;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;|VRF|&nbsp;&nbsp;|&nbsp;&nbs=
p;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;|&nbsp;&nbsp;|VRF|&nbsp=
;&nbsp;|</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;|&nbsp;&nbsp; |&nbsp;&nbsp;|=
&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;|&nbsp;&nbsp;=
|&nbsp;&nbsp; |&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&#43;---&#43;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;|&nbsp;&nbsp; |&nbsp;&nbsp;|=
&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;|&nbsp;&nbsp;=
|&nbsp;&nbsp; &#43;--&#43;----AC3-----&#43;CE3|</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&#43;---&#43;&nbsp;&nbsp;|&n=
bsp;&nbsp;&#43;------&#43;&nbsp;&nbsp;|&nbsp;&nbsp;&#43;---&#43;&nbsp;&nbsp=
;|&nbsp;&nbsp; (Leaf)&nbsp;&nbsp; &#43;---&#43;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;---------&#43;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#43;---------&#43;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
The figure is useful in showing the relationship of PE, AC, and CE.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
(I see now that what I call an &quot;endpoint&quot; is generally known as a=
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&quot;CE&quot;.)&nbsp;&nbsp;But there is a shortage of connection lines.&nb=
sp;&nbsp;I think</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
something like this would be clearer:</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;---------&#43;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#43;---------&#43;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; PE1&nbsp;&nbsp; |&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;=
 PE2&nbsp;&nbsp; |</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&#43;---&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&#43;---&#43;&nbsp;&nbsp;|&nbsp;&nbsp;&#=
43;------&#43;&nbsp;&nbsp;|&nbsp;&nbsp;&#43;---&#43;&nbsp;&nbsp;|&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#43;---&#43;=
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;|CE1&#43;---AC1----&#43;--&#43;&nbsp;&nbsp; |&nbsp;=
&nbsp;|&nbsp;&nbsp;| MPLS |&nbsp;&nbsp;|&nbsp;&nbsp;|&nbsp;&nbsp; &#43;--&#=
43;----AC2-----&#43;CE2|</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&#43;---&#43;&nbsp;&nbsp;(Root)&nbsp;&nbsp;|&nbsp;&=
nbsp;|MAC|&nbsp;&nbsp;|&nbsp;&nbsp;|&nbsp;&nbsp;/IP |&nbsp;&nbsp;|&nbsp;&nb=
sp;|MAC|&nbsp;&nbsp;|&nbsp;&nbsp; (Leaf)&nbsp;&nbsp; &#43;---&#43;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;|VRF&#43;------------------&=
#43;VRF|&nbsp;&nbsp;|</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;|&nbsp;&nbsp; |&nbsp;&nbsp;|=
&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;|&nbsp;&nbsp;=
|&nbsp;&nbsp; |&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&#43;---&#43;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;|&nbsp;&nbsp; |&nbsp;&nbsp;|=
&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;|&nbsp;&nbsp;=
|&nbsp;&nbsp; &#43;--&#43;----AC3-----&#43;CE3|</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&#43;---&#43;&nbsp;&nbsp;|&n=
bsp;&nbsp;&#43;------&#43;&nbsp;&nbsp;|&nbsp;&nbsp;&#43;---&#43;&nbsp;&nbsp=
;|&nbsp;&nbsp; (Leaf)&nbsp;&nbsp; &#43;---&#43;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;---------&#43;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#43;---------&#43;</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">The connection among MAC VRFs is very well understo=
od. It is not point-to-point but rather multipoint-to-point from each MAC-V=
RF (e.g., a single downstream label is advertised by the PE to all other PE=
 devices for its MAC-VRF).&nbsp;I am&nbsp;afraid
 representing a P2P connection&nbsp;between MAC-VRF may cause confusions.</=
font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; In such scenario, using tailored BGP Route Target (RT) import/=
export</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; policies among the PEs belonging to the same EVI, can be used =
to</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; restrict the communications among Leaf PEs.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Presumably, &quot;In such a scenario ...&quot; but I prefer &quot;In this s=
cenario</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
...&quot;.&nbsp;&nbsp;But the grammar has a problem, since if you elide the=
 clause</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&quot;using ... the same EVI&quot;, it reads &quot;In such [a] scenario ...=
 can be</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
used to ...&quot;.&nbsp;&nbsp;I think you want &quot;In such a scenario, ta=
ilored BGP</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
... policies ... can be used to ...&quot;.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Changed it to:</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;<span style=3D"orphans: 2; white-space: pre-w=
rap; widows: 2;">In this scenario, tailored BGP Route Target (RT) import/ex=
port
</span><span style=3D"orphans: 2; white-space: pre-wrap; widows: 2;">polici=
es among the PEs belonging to the same EVI can be used to&nbsp;restrict the=
 communications among Leaf PEs.&quot;</span><font style=3D"orphans: 2; whit=
e-space: pre-wrap; widows: 2;">&nbsp;</font></font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
I think you want &quot;prevent&quot; rather than &quot;restrict&quot;, sinc=
e by the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
definition of E-Tree service, there is to be no communication between</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Leaf ACs at all -- restrict has an implication that the limitation is</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
not absolute (and indeed, is somehow configurable).</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Changed it to&nbsp;=93prevent=94.</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; from one Leaf AC to another Leaf AC on a MAC-VRF for a given E=
-TREE</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; EVI.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Across the whole document, it's clear that the operation of the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
proposed E-Tree mechanism is absolutely independent for each EVI.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
E.g., here you note that scenario 1 is &quot;for any PE, *for any EVI*, all=
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
CEs connected to that PE are either all Roots or all Leafs&quot;.&nbsp;&nbs=
p;But you</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
could simply state this separation of each EVI from every other EVI at</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
the top of the document and not have to keep repeating it at various</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
places throughout the document.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">The current text is reading fine to me. However, if=
 &nbsp;you have specific changes in mind, please let me know.</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
That is, I think it's true.&nbsp;&nbsp;If there are ways in which the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
implementation of one EVI interacts the implementation of another EVI,</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
that needs to be prominently flagged and carefully assessed for</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
causing subtle problems.&nbsp;&nbsp;E.g., in section 3.2.1, it seems like t=
he</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
advertisements of &quot;Ethernet A-D per ES routes&quot; may bundle informa=
tion</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
about multiple EVIs.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
2.2 Scenario 2: Leaf OR Root site(s) per AC</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
There is a technical question in that scenario 1 is more restrictive</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
than scenario 2, so any solution for scenario 2 can be used in</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
scenario 1.&nbsp;&nbsp;But only alternative A is presented for scenario 1, =
even</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
though alternative B must necessarily work.&nbsp;&nbsp;Presumably there is =
a</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
reason why alternative B is not presented for scenario 1, and I think</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
it should be stated.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000"><span style=3D"font-family: Calibri, sans-serif;"><=
br>
</span></font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000"><span style=3D"font-family: Calibri, sans-serif;">A=
dded the following paragraph to section 2.1:</span></font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000"><span style=3D"font-family: Calibri, sans-serif;">&=
quot;</span>For this scenario, if it is desired to use only a single RT per=
 EVI (just like E-LAN services in [RFC7432]), then the approach B in scenar=
io 2 (described below) needs to be used.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
This fact caused me some confusion when I was reading the document:</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
The mechanism described in 2.1 seems to be satisfactory for fulfilling</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
the requirements stated in paragraph 2, so but paragraph 2 introduces</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&quot;coloring&quot; of MAC addresses.&nbsp;&nbsp;I think that the expositi=
ons of the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
three scenarios could better be done if they were all coordinated with</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
each other.&nbsp;&nbsp;Perhaps the choice between alternatives A and B for<=
/div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
coloring MAC addresses is actually common across the three scenarios,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
and what really changes between the scenarios is the efficiency</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
tradeoffs between the two alternatives.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Added the following paragraph to section 2.3:</font=
></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;For this scenario, the approach B in scenario=
 2 (described above) is used in order to allow for single RT usage by servi=
ce providers.=94</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Also added the following paragraph at the end of th=
e section 2.3:</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">=93In conclusion, the approach B in scenario 2 is t=
he recommended approach across all the above three scenarios and the corres=
ponding solution is detailed in the following sections.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; Approach (A) would require the same data plane enhancements as=
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; approach (B) if MAC-VRF and bridge tables used per VLAN, are t=
o</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; remain consistent with [RFC7432] (section 6).</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
What is the subject of &quot;are&quot;?</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">=93MAC-VRF and bridge tables=94.&nbsp;I will remove=
 =93,=94 :</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<div style=3D"font-family: Consolas, monospace; font-size: 12px;"><font col=
or=3D"#ff0000">=93=85 if MAC-VRF and bridge tables used per VLAN are to rem=
ain consistent with [RFC7432] (section 6).&quot;</font></div>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; In order to avoid data-</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; plane enhancements for approach (A), multiple bridge tables pe=
r VLAN</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; may be considered;&nbsp;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
It's not clear what the difference is between &quot;MAC-VRF and bridge</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
tables used per VLAN&quot; and &quot;multiple bridge tables per VLAN&quot;.=
&nbsp;&nbsp;Can this</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
be described in a way that is clearer to people who are not highly</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
familiar with the subject?</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">That is described in [RFC7432] which&nbsp;I made it=
&nbsp;prerequisite for this document.</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; then two RTs (one for Root and another for Leaf)</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; can still be used with approach (B)</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
This seems to be proposing some sort of mixture of alternatives A and</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
B.&nbsp;&nbsp;What exactly are the alternatives that are being specified th=
at</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
the implementor chooses between?</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">The last paragraph that I added to section 2.3 shou=
ld now make it clear:</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<span style=3D"color: rgb(255, 0, 0);">=93In conclusion, the approach B in =
scenario 2 is the recommended approach across all the above three scenarios=
 and the corresponding solution is detailed in the following sections.&quot=
;</span></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
2.3 Scenario 3: Leaf OR Root site(s) per MAC</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; This scenario is</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; not covered in both [RFC7387] and [MEF6.1]</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Literally, this means &quot;It is not true that this scenario is covered in=
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
RFC 7387 and in MEF6.1.&quot;&nbsp;&nbsp;But I think you mean &quot;This sc=
enario is not</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
covered in either ...&quot;.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Changed it to&nbsp;=93either=94&nbsp;=93or=94.</fon=
t></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; the Designated Forwarding (DF)</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; filtering per [RFC7432] would not be compatible with the requi=
red</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; egress filtering</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Interestingly, &quot;designated forwarding&quot; is not mentioned anywhere =
else</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
in this draft.&nbsp;&nbsp;Does it appear elsewhere or is it implied in the<=
/div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
mechanics of RFC 7432 that are used throughout this draft?</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">It is implied mechanism of RFC7432 and that=92s why=
 it says&nbsp;=93per [RFC7432].</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
There seems to be no description of the techniques to be used in this</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
case.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Now there is with the addition of the two paragraph=
s described above to this section.</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
And given that it seems to be contemplated to support scenario 3,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
there are numerous places in the draft where &quot;a Root AC&quot; and &quo=
t;a Leaf</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
AC&quot; are not correct.&nbsp;&nbsp;You could use &quot;a Root CE&quot; or=
 &quot;a Root site&quot;, etc.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">It has already been addressed in. Added the followi=
ng sentence to the end of 1st para in section 1.</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;In this document unless explicitly mentioned =
otherwise, a site is always represented by an AC.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
3 Operation for EVPN</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; In other words,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; [RFC7432] has inherent capability to support E-TREE services w=
ithout</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; defining any new BGP routes but by just defining a new BGP Ext=
ended</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; Community for leaf indication as shown later in this document<=
/div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; (section 5.1).</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
And by implication, the addition of various processing of that leaf</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
indication.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
But this does show that this draft is not just an application of RFC</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
7432 but an extension of it.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Changed the 1st para of section 3 to:</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;[RFC7432] defines the notion of Ethernet Segm=
ent Identifier (ESI) MPLS label used for split-horizon filtering of BUM tra=
ffic at the egress PE. Such egress filtering capabilities can be leveraged =
in provision of E-Tree services as it will
 be seen shortly for BUM traffic. For know unicast traffic, additional exte=
nsions to [RFC7432] is needed (i.e., a new BGP Extended Community for leaf =
indication described in section 5.1) in order to enable ingress filtering a=
s described in detail in the following
 sections.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
3.1 Known Unicast Traffic</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; sending ... traffic over MPLS/IP core to be filtered at the eg=
ress</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; PE ...</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
The implication seems to be that this &quot;sending&quot; that is avoided i=
s</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
really multicast, from the ingress PE to all egress PEs.&nbsp;&nbsp;Naively=
,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
describing this as &quot;over MPLS/IP core&quot; doesn't seem to capture th=
e</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
meaning, since *all* traffic is going to be send &quot;over the MPLS/IP</di=
v>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
core&quot;.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">The paragraph is talking about know unicast filteri=
ng.&nbsp;I read it again and it is very clear (at least to me :-).</font></=
div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000"><br>
</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; To provide such ingress filtering for known unicast traffic, a=
 PE</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; MUST indicate to other PEs what kind of sites (root or leaf) i=
ts MAC</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; addresses are associated with by advertising a leaf indication=
 flag</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; (via an Extended Community) along with each of its MAC/IP</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; Advertisement routes. The lack of such flag indicates that the=
 MAC</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; address is associated with a root site. This scheme applies to=
 all</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; scenarios described in section 2.&nbsp;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Read literally, this paragraph says that a leaf indication flag MUST</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
be present on each advertisement, but then says the absence of the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
flag means that it is a root side (implying that the absence of the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
flag is legitimate).&nbsp;&nbsp;There are two alternatives -- a) the flag i=
s a</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
1/0 flag, with one value meaning Leaf and one meaning Root or b) the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
flag is some optional field whose presence means Leaf and whose</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
absence means Root -- but this wording isn't quite correct for either.</div=
>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Changed the paragraph to:</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;To provide such ingress filtering for known u=
nicast traffic, a PE MUST indicate to other PEs what kind of sites (root or=
 leaf) its MAC addresses are associated with. This is done by advertising a=
 leaf indication flag (via an Extended
 Community) along with each of its MAC/IP Advertisement routes learned from=
 a leaf site. The lack of such flag indicates that the MAC address is assoc=
iated with a root site. This scheme applies to all scenarios described in s=
ection 2.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Also, this paragraph seems to be saying that the extended community is</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
always used to indicate Leaf/Root status (though perhaps it specifies</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
status by its absence).&nbsp;&nbsp;But the descriptions in section 2 seem t=
o be</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
saying that alternative A doesn't require the extended community,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
which contradicts the MUST in this paragraph.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">The modified paragraph above should cover this.</fo=
nt></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
3.2 BUM Traffic</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; This specification does not provide support for filtering BUM<=
/div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; (Broadcast, Unknown, and Multicast) traffic on the ingress PE =
because</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; it is not possible to perform filtering of BUM traffic on the =
ingress</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; PE, as is the case with known unicast described above, due to =
the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; multi-destination nature of BUM traffic.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
This sentence is quite awkward.&nbsp;&nbsp;I think you can carry all of the=
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
meaning with &quot;This specification does not provide support for</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
filtering BUM (Broadcast, Unknown, and Multicast) traffic on the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
ingress PE because it is not possible to do so, due to the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
multi-destination nature of BUM traffic.&quot;</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Done.</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
But the phrase &quot;does not provide support&quot; is not correct -- the</=
div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
ingress PE fully *supports* BUM traffic (except in scenario 3), it's</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
just that the support doesn't include *filtering* by the ingress PE.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">OK. Change it to:</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;In this specification, the support for filter=
ing BUM (Broadcast, Unknown, and Multicast) traffic does not include ingres=
s filtering because it is not possible to do so, due to the multi-destinati=
on nature of BUM traffic.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; the MPLS-encapsulated frames MUST be tagged with an</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; indication that they originated from a Leaf AC - i.e., to be t=
agged</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; with a Leaf label as specified in section 5.1.&nbsp;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
As written, the sentence requires &quot;... tagged with an indication</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
whether they originated ...&quot;.&nbsp;&nbsp;The use of &quot;that&quot; s=
tates that all the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
frames originated from a Leaf AC.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Good catch! I changed =93that=94 to =93when&quot;</=
font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Looking ahead to section 5.1, I see that the Leaf label is</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
considerably longer than the 1 bit that would seem to be necessary for</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
this function given its description here.&nbsp;&nbsp;And the next paragraph=
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
suggests that the assignment of Leaf labels is complex.&nbsp;&nbsp;It would=
 be</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
helpful if you clarified here all of the functionality of Leaf labels</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
so the reader has context for following paragraphs.&nbsp;&nbsp;I suspect th=
e</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
meaning here is &quot;all MPLS-encapsulated frame are tagged with labels,</=
div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
and to distinguish Leaf-originated frames, they must be tagged with</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
labels which are known to be Leaf labels&quot;.&nbsp;&nbsp;Also, is there o=
nly one</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
leaf label (for an EVI), or can there be many, perhaps one for every</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Leaf AC?</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Added the following sentences to the end of 1st par=
agraph of section 3.2:</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;This Leaf label allows for disposition PE (e.=
g., egress PE) to perform the necessary egress filtering function in data-p=
lane similar to ESI label in [RFC7432]. The allocation of the Leaf label is=
 on a per PE basis (e.g., independent of
 ESI and EVI) as descried in the following sections.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; The main difference between</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; downstream and upstream assigned Leaf label is that in case of=
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; downstream assigned not all egress PE devices need to receive =
the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; label just like ESI label for ingress replication procedures d=
efined</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; in [RFC7432].</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
This sentence isn't clear to me.&nbsp;&nbsp;I suspect that it just needs a =
few</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
words adjusted.&nbsp;&nbsp;Also, I suspect that it would help to move the f=
inal</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
clause, &quot;just like ESI label ...&quot; to a separate sentence.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Changed the sentence to:</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;The main difference between downstream and up=
stream assigned Leaf label is that in case of downstream assigned not all e=
gress PE devices need to receive the label in MPLS encapsulated BUM packets=
 just like ESI label for ingress replication
 procedures defined in [RFC7432].&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; On the ingress PE, the PE needs to place all its Leaf ACs for =
a given</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; bridge domain in a single split-horizon group in order to prev=
ent</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; intra-PE forwarding among its Leaf ACs.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
The phrase &quot;bridge domain&quot; appears only twice in this document.&n=
bsp;&nbsp;I</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
suspect it is synonymous with some other term you are using.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">It is now described in terminology section.&nbsp;</=
font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000"><br>
</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
My belief is that a &quot;split-horizon group&quot; means a group of ACs th=
at</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
are visible to each other.&nbsp;&nbsp;If that is correct, this sentence nee=
ds to</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
be rephrased to something like &quot;... the PE needs to place each of its<=
/div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Leaf ACs for a given bridge domain into separate split-horizon groups</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
...&quot;.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Split-horizion group means the member of that group=
 cannot send packets to each other.&nbsp;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; Other mechanisms</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; for identifying root or leaf (e.g., on a per MAC address basis=
) is</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; beyond the scope of this document.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Scenario 3 in section 2.3 posits that a single AC may support both</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Leaf and Root endpoints.&nbsp;&nbsp;So there must be a known method of</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
performing this identification on a per-MAC address basis, or else</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
scenario 3 cannot be implemented at present.&nbsp;&nbsp;That doesn't requir=
e</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
that this document specify or describe a method of doing so, but it</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
seems that at this point, the document should either identify one or</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
more ways in which it can be done, or admit that there are no known</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
mechanisms at this time.&nbsp;&nbsp;(Or perhaps that there are no known *go=
od*</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
mechanisms at this time.)&nbsp;&nbsp;Otherwise the inclusion of scenario 3 =
is</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
purely hypothetical.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Changed the sentence to:</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;Other mechanisms for identifying root or leaf=
 sites such the use of source MAC address of the receiving frame are option=
al. The scenarios below are described in context of Root/Leaf AC; however, =
they can be extended to Root/Leaf MAC address
 if needed.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
The acronym &quot;ES&quot; us used a lot in this section, meaning &quot;Eth=
ernet</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
segment&quot;.&nbsp;&nbsp;Is &quot;Ethernet segment&quot; related to &quot;=
AC&quot;?</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000"><font face=3D"Calibri,sans-serif">Terminology secti=
on now provides the&nbsp;definition of an Ethernet&nbsp;Segment.</font></fo=
nt></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
3.2.1 BUM traffic originated from a single-homed site on a leaf AC</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
What is the rule for capitalizing or not the words &quot;leaf&quot; and &qu=
ot;root&quot;?</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">They are capitalized if they are used as adjectives=
. Went through the doc to&nbsp;make sure that=92s the case.</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; This Leaf label is</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; advertised to other PE devices, using the E-TREE Extended Comm=
unity</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; (section 5.1) along with an Ethernet A-D per ES route with ESI=
 of</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; zero and a set of Route Targets (RTs) corresponding to all EVI=
s on</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; the PE with at least one leaf site per EVI.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
I'm not sure, but I think you mean s/all EVIs on the PE with at least</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
one leaf site per EVI/all EVIs which have at least one leaf site on</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
the PE/.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">The original text is correct but I=92ll change it t=
o the following for better clarification:</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;corresponding to all EVIs on the PE where eac=
h EVI has at least one Leaf site.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; The set of Ethernet A-D</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; per ES routes may be needed if the number of Route Targets (RT=
s) that</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; need to be sent exceed the limit on a single route per [RFC743=
2].</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
I suspect from the text that &quot;Ethernet A-D per ES route&quot; is a sin=
gle</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
term, but I have no idea what it is referring to.&nbsp;&nbsp;And I suspect =
that</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
someone has coined a shorter term to use.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">This term is borrowed from [RFC7432] and there is n=
o shorter term :-(</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
I suspect that one or more words in this sentence aren't quite right</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
and I can't parse it.&nbsp;&nbsp;For instance &quot;The set of ... routes m=
ay be</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
needed if ...&quot; doesn't make sense -- in what way can a set of routes</=
div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
be needed only under some conditions?&nbsp;&nbsp;Perhaps it should be &quot=
;A set of</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
... routes&quot;, if the meaning is that in some situations only one would<=
/div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
be needed.&nbsp;&nbsp;Reading this again, I think you mean &quot;Multiple E=
thernet</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
A-D per ES routes will need to be advertised if the number of Route</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Targets needed to carry the EVIs exceeds the limit on a single route.&quot;=
</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Correct! I will change it to the following since&nb=
sp;</font><span style=3D"color: rgb(255, 0, 0);">RT=92s are carried by the =
route and not EVIs</span><span style=3D"color: rgb(255, 0, 0);">:</span></d=
iv>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;Multiple Ethernet A-D per ES routes will need=
 to be advertised if the number of Route Targets (RTs) that need to be carr=
ied exceed the limit on a single route per [RFC7432].&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; The</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; ESI for the Ethernet A-D per ES route is set to zero to indica=
te</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; single-homed sites.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
This sentence seems to be talking about some attribute of a route</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
(which is an operation in the control plane) while the section is</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
theoretically talking about BUM traffic (which is in the data plane).</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
This seems to be a general organizational problem, where the details</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
of the data plane operations are mixed with general descriptions of</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
the control plane operations needed to support the data plane</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
operations.&nbsp;&nbsp;It would be clearer if the data plane specifications=
 and</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
the control plane specifications were separated (e.g., into adjacent</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
paragraphs), making it more explicit what information is passed from</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
the control plane to the data plane.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">The entire paragraph in section 3.2.1 is about adve=
rtisement of Leaf label in control plane.</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
3.2.3 BUM traffic originated from a multi-homed site on a leaf AC</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
The first paragraph introduces various matters that aren't discussed</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
in the rest of the document, or at least aren't much discussed.&nbsp;&nbsp;=
If I</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
understand it right, these considerations don't introduce anything</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
unexpected other than that an AC which is multi-homed (i.e., connects</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
to more than one PE) must, for any single EVI, be consistently a Root</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
or a Leaf on all of those PEs.&nbsp;&nbsp;If I'm correct, this paragraph co=
uld</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
be made much easier to understand by stating just that and avoiding</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
details.</div>
</blockquote>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
However, there may be more involved than that.&nbsp;&nbsp;E.g., &quot;there=
 is no</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
forwarding among subnets&quot; may be an additional requirement.&nbsp;&nbsp=
;It's hard</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
to tell, because there are only two occurrences of &quot;forwarding among</=
div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
subnets&quot;, and it's not at all clear what that term is intended to</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
cover.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">It is important to mention that there is no forward=
ing among&nbsp;subnets. This sentence itself is the conclusion of some of t=
he discussions among the co-author.</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
3.2.4 BUM traffic originated from a multi-homed site on a root AC</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
I think the critical point of this paragraph is omitted: &quot;... but no</=
div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Leaf label is added&quot;.&nbsp;&nbsp;Compare with section 3.2.2.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Changed it to:</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;In this scenario, both the ingress and egress=
 PE devices follows the procedure defined in [RFC7432] for adding and/or pr=
ocessing an ESI MPLS label - i.e., existing procedures for BUM traffic in [=
RFC7432] are sufficient and there is no
 need to add a Leaf label.=94</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
3.3 E-TREE Traffic Flows for EVPN</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- Ethernet known unicast fr=
om Root to Roots &amp; Leaf</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- Ethernet known unicast fr=
om Leaf to Root</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- Ethernet BUM traffic from=
 Root to Roots &amp; Leafs</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- Ethernet BUM traffic from=
 Leaf to Roots</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
The grammar of these is not good.&nbsp;&nbsp;I think you mean &quot;Known u=
nicast</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Ethernet from ... to ...&quot;, or better &quot;Known unicast traffic from<=
/div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
... to ...&quot;.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Changed it to:</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">=93 &nbsp; &nbsp; - Known unicast traffic from Root=
 to Roots &amp; Leaf</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&nbsp; &nbsp; &nbsp;- Known unicast traffic from Le=
af to Root</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&nbsp; &nbsp; &nbsp;- BUM traffic from Root to Root=
s &amp; Leafs</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&nbsp; &nbsp; &nbsp;- BUM traffic from Leaf to Root=
s&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; In the case where unicast flows need not be supported,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; the L2VPN PEs can avoid performing any MAC learning function.&=
nbsp;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
I think you want s/unicast/known unicast/ -- there may be situations</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
where unicast traffic exists, and it could be handled as known unicast</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
traffic, but the implementation can tolerate handling all of it as</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
unknown traffic to avoid MAC learning.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
OTOH, the choice of supporting scenario 3 requires the choice of MAC</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
learning, since scenario 3 prevents handling should-be-known unicast</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
traffic as BUM traffic.&nbsp;&nbsp;That dependency should be noted somewher=
e.</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Changed it to:</font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">&quot;In the case where only multicast and broadcas=
t flows need to be supported, the L2VPN PEs can avoid performing any MAC le=
arning function.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
3.3.1 E-Tree with MAC Learning</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
I see here much use of &quot;Ethernet Segments&quot;.&nbsp;&nbsp;It seems t=
hat it has the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
same functional meaning as &quot;ACs&quot;.&nbsp;&nbsp;If so, only one term=
 should be used</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
consistently.&nbsp;&nbsp;If not, does the distinction need to be explained?=
</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<font color=3D"#ff0000">Ethernet Segments and ACs are different. An AC corr=
esponds to an Ethernet tag (e.g., VLAN ID) on a port (Ethernet Segment). No=
w that both Ethernet Segment and Ethernet tag are defined in terminology an=
d the association between Ethernet
 tag and AC is made in the introduction section, there should be no ambigui=
ty.</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; For the scenario</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; described in section 2.1 (or possibly section 2.2), these rout=
es are</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; imported only by PEs with at least one Root site in the EVI ..=
.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
What is the condition on &quot;possibly in section 2.2&quot;?&nbsp;&nbsp;(I=
s this a</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
distinction between alternatives A and B?)</div>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><font col=
or=3D"#ff0000">Modified the sentence to the following for better clarity:</=
font></div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><font col=
or=3D"#ff0000">&quot;For scenarios where two different RTs are used per EVI=
 (one to designate Root site and another to designate Leaf site), the MAC/I=
P Advertisement routes are imported only
 by PEs with at least one Root site in the EVI - i.e., a PE with only Leaf =
sites will not import these routes.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; To support multicast/broadcast from Leaf to Root sites, ingres=
s</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; replication should be sufficient for most scenarios where ther=
e are</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; only a few Roots (typically two).</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
This is introducing one of a pair of alternatives (the other one being</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
described in the following paragraphs).&nbsp;&nbsp;I think the reader shoul=
d be</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
warned in advance what the two alternatives are and what it depends on</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
(viz., the number of Roots).&nbsp;&nbsp;That is, a top-down structure.</div=
>
</blockquote>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><font col=
or=3D"#ff0000">Modified the paragraph to:</font></div>
<div><font color=3D"#ff0000"><font face=3D"Calibri,sans-serif">=93</font>To=
 support multicast/broadcast from Leaf to Root sites, either ingress replic=
ation tunnels from each Leaf PE or a P2MP tree rooted at each Leaf PE can b=
e used. The following two paragraphs describes
 when each of these tunneling schemes can be used and how to signal them.=
=94</font></div>
<div><font color=3D"#ff0000"><br>
</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; If the number of Roots is large, P2MP tunnels originated at th=
e PEs</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; with Leaf sites may be used and thus there will be no need to =
use the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; modified PMSI tunnel attribute in section 5.2 for composite tu=
nnel</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; type.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
The wording here is not quite right; I think it allows some ambiguity.</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Perhaps</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; If the number of Roots is large, P2MP tunnels originated at th=
e PEs</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; with Leaf sites may be used (and thus there will be no need to=
 use</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; the composite tunnel type values of the modified PMSI tunnel</=
div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; attribute in section 5.2).</div>
</blockquote>
<div><br>
</div>
<div><font color=3D"#ff0000">Modified it to:</font></div>
<div><font color=3D"#ff0000">=93If the number of Roots is large, P2MP tunne=
ls (e.g., mLDP or RSVP-TE) originated at the PEs with Leaf sites may be use=
d and thus there will be no need to use the modified PMSI tunnel attribute =
and the composite tunnel type values
 in section 5.2.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
3.3.2 E-Tree without MAC Learning</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Similarly, I suggest</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; Just as in the previous section, if the number of PEs with roo=
t</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; sites are only a few and thus ingress replication is desired f=
rom</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; leaf PEs to these root PEs, then the composite tunnel values</=
div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; defined in section 5.2 should be used.</div>
</blockquote>
<div><br>
</div>
<div><font color=3D"#ff0000">Modified it to:</font></div>
<div><font color=3D"#ff0000">&quot;Just as in the previous section, if the =
number of Root PEs are only a few and thus ingress replication is desired f=
rom Leaf PEs to these root PEs, then the modified PMSI attribute and the co=
mposite tunnel type values defined in section
 5.2 should be used.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
4 Operation for PBB-EVPN</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; In PBB-EVPN, the PE advertises a Root/Leaf indication along wi=
th each</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; B-MAC Advertisement route, to indicate whether the associated =
B-MAC</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; address corresponds to a Root or a Leaf site. Just like the EV=
PN</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; case, the new E-TREE Extended Community defined in section [5.=
1] is</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; advertised with each MAC Advertisement route.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
I don't understand the distinctions here, but is &quot;MAC Advertisement</d=
iv>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
route&quot; correct?&nbsp;&nbsp;There are two uses of &quot;MAC&quot; and 1=
2 uses of &quot;B-MAC&quot; in</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
this section.</div>
</blockquote>
<div><br>
</div>
<div><font color=3D"#ff0000">The precise statement should be: =93=85 with e=
ach&nbsp;EVPN MAC/IP Advertisement route.=94&nbsp;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
4.1 Known Unicast Traffic</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; The ingress PE cross-checks this flag with the status of</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; the originating site, and if both are a Leaf, then the packet =
is not</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; forwarded.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
I think this can be simplified to</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; The ingress PE also checks the status of the originating site,=
 and</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; if both are a Leaf, then the packet is not forwarded.</div>
</blockquote>
<div><br>
</div>
<div><font color=3D"#ff0000">Done.</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
4.2 BUM Traffic</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; it updates its egress filtering (based on the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; source B-MAC address), as follows:</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
The stated algorithm has some important properties.&nbsp;&nbsp;One is that =
if a</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
frame arrives, but its B-MAC address is unknown, then the frame is</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
forwarded.&nbsp;&nbsp;That is, traffic not from a known Leaf is assumed to =
be</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
from a Root.&nbsp;&nbsp;This may not be a problem, but it seems like it is =
an</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
important property of this specification, and the implementor should</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
be aware of it.&nbsp;&nbsp;(OTOH, perhaps this is a generic property of</di=
v>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
PBB-EVPN, in which case it need not be stated here.)</div>
</blockquote>
<div><br>
</div>
<div><font color=3D"#ff0000">It is a generic&nbsp;property of PBB-EVPN.</fo=
nt></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Another property is that if a B-MAC changes from being a Leaf to being</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
a Root (by whatever means that might happen), it seems that the new</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
advertisements of the B-MAC as a Root will *not* remove it from the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
list of blocked B-MACs of any Leaf that has seen that B-MAC advertised</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
as a Leaf.&nbsp;&nbsp;Unless there is some consideration that I'm not aware=
 of,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
I think you want to revise this algorithm in this regard.</div>
</blockquote>
<div><br>
</div>
<div><font color=3D"#ff0000">Added the following bullet to the list of bull=
ets:&nbsp;</font></div>
<div><font color=3D"#ff0000">&quot;- If the EVPN MAC/IP Advertisement route=
 indicates that the advertised B-MAC has changed its designation from a Lea=
f to a Root and the local Ethernet Segment is a Leaf, then the source B-MAC=
 address is removed from the B-MAC list
 corresponding to the local Ethernet Segment used for egress filtering - i.=
e., to unblock traffic from that B-MAC address.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
4.3 E-Tree without MAC Learning</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; For PBB-EVPN, the handling of such traffic is per</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; section 4.2 without C-MAC learning part of it at both ingress =
and</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; egress PEs.&nbsp;&nbsp;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
This could be phrased better.&nbsp;&nbsp;And is the &quot;non-C-MAC learnin=
g&quot; mode of</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
operation of PBB-EVPN defined in the PBB-EVPN specification?&nbsp;&nbsp;If =
not,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
I think you might need to describe it in more detail here.</div>
</blockquote>
<div><br>
</div>
<div><font color=3D"#ff0000">Changed it to:</font></div>
<div><font color=3D"#ff0000">&quot;For PBB-EVPN, the handling of such traff=
ic is per section 4.2 without the need for C-MAC learning (in data-plane) i=
n I-component (C-bridge table) of PBB-EVPN PEs (at both ingress and egress =
PEs).&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
5.1 E-Tree Extended Community</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; It is used for leaf indication of known unicast and BUM</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; traffic.&nbsp;&nbsp;&nbsp;&nbsp;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
It's probably worth specifying that it indicates that the frame's</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
*origin* is a Leaf.</div>
</blockquote>
<div><br>
</div>
<div><font color=3D"#ff0000">Added the sentence:</font></div>
<div><font color=3D"#ff0000">&quot;It indicates that the frame is originate=
d from a Leaf site.&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; The label value is encoded in the high-order 20 bits of the</d=
iv>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; Leaf Label field.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
This sentence seems to be in the wrong place, since the case described</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
in this paragraph doesn't use the Label Value field.&nbsp;&nbsp;It seems to=
 me</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
that it would be better to incorporate this information into the value</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
layout:</div>
</blockquote>
<div><br>
</div>
<div><font color=3D"#ff0000">Changed the sentence to:</font></div>
<div><font color=3D"#ff0000">&quot;The value of the 20-bit MPLS label is en=
coded in the high-order 20 bits of the Leaf Label field.=94</font></div>
<div><br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;0&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; 3</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;0 1 2 3 4 5 6 7 8 9 0 1 2 3=
 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;=
-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Type=3D0x06&nbsp;&nbsp;&nbsp;&nbsp; =
| Sub-Type=3D0x05 | Flags(1 Octet)|&nbsp;&nbsp;Reserved=3D0&nbsp;&nbsp; |</=
div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;=
-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;Reserved=3D0&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Leaf Label&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|0 0 0 0|</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;=
-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#=
43;-&#43;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
5.2 PMSI Tunnel Attribute</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; Composite tunnel type is advertised by the root</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; PE to simultaneously indicate a non-ingress replication tunnel=
 ...</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
There's a certain ambiguity here, as I first read it as &quot;... a</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
(non-ingress) replication tunnel ...&quot; -- but of course, there is no</d=
iv>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&quot;egress replication&quot;.&nbsp;&nbsp;What is meant is &quot;... a non=
-(ingress</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
replication) tunnel ...&quot;, which I think would be better expressed as</=
div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&quot;... a non-ingress-replication tunnel ...&quot;.</div>
</blockquote>
<div><br>
</div>
<div><font color=3D"#ff0000">Done.</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; When this Composite Tunnel bit is set, the &quot;tunnel identi=
fier&quot; field</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; would begin with a three-octet label, followed by the actual t=
unnel</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; identifier for the transmit tunnel.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Probably better s/would begin/begins/.&nbsp;&nbsp;(The clause of the condit=
ion</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&quot;Composite Tunnel bit is set&quot; does not use the subjunctive mood, =
so</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
you don't use the subjunctive mood in the consequent clause.)</div>
</blockquote>
<div><br>
</div>
<div><font color=3D"#ff0000">Done.</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
It might help to add a figure</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;---------------------=
------------&#43;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;Flags (1 octe=
t)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;|</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;---------------------=
------------&#43;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;Tunnel Type (=
1 octet)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;---------------------=
------------&#43;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;P2MP MPLS Lab=
el (3 octets)&nbsp;&nbsp;&nbsp;&nbsp; |</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;---------------------=
------------&#43;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;Ingress Repli=
cation MPLS Label |</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;(3 octets)&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;---------------------=
------------&#43;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;Tunnel Identi=
fier (variable)&nbsp;&nbsp; |</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;---------------------=
------------&#43;</div>
</blockquote>
<div><br>
</div>
<div><font color=3D"#ff0000">Done.</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
And s/1 octets/1 octet/ -- even though RFC 6514 makes that mistake!</div>
</blockquote>
<div><br>
</div>
<div><font color=3D"#ff0000">Done.</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; PEs that don't understand the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; new meaning of the high-order bit would treat the tunnel type =
as an</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; undefined tunnel type and would treat the PMSI tunnel attribut=
e as a</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; malformed attribute [RFC6514].</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
It might be worth noting that this processing is why the composite</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
tunnel bit is allocated in the Tunnel Type field rather than the Flags</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
field.</div>
</blockquote>
<div><br>
</div>
<div><font color=3D"#ff0000">Done.</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
8.1 Considerations for PMSI Tunnel Types</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; The registry is to be updated, by removing the entries for 0xF=
B-0xFE</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; and 0x0F, and replacing them by:</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;Meaning&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;Reference</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; 0x0B-0x7A&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Unassigned</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; 0x7B-0x7E&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Reserved for Expe=
rimental Use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;this document</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; 0x7F&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; Reserved&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; this document</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; 0x80-0xFF&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Reserved for Comp=
osite Tunnels&nbsp;&nbsp;&nbsp;&nbsp; this document</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; The allocation policy for values 0x00 to 0x7A is IETF Review</=
div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; [RFC5226]. The range for experimental use is now 0x7B-0x7E, an=
d value</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; in this range are not to be assigned. The status of 0x7F may o=
nly be</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; changed through Standards Action [RFC5226].&nbsp;&nbsp;</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
This structure allows the high-order bit to modify the interpretation</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
of the other bits.&nbsp;&nbsp;However, section 5.2 says, &quot;... the high=
-order bit</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
of the tunnel type field (Composite Tunnel bit) is set while the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
remaining low-order seven bits indicate the tunnel type as before.&quot;</d=
iv>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
I think what you intended is to change the &quot;P-Multicast Service</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Interface Tunnel (PMSI Tunnel) Tunnel Types&quot; registry to only specify<=
/div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
the low-order seven bits of the Tunnel Type field, with the high-order</div=
>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
bit of Tunnel Type being the Composite Tunnel bit.&nbsp;&nbsp;Conceptualize=
d</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
that way, the registry changes to:</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;Meaning&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;Reference</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; 0x00-0x7A&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(as before)</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; 0x7B-0x7E&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Reserved for Expe=
rimental Use&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;this document</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; 0x7F&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; Reserved&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; this document</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
This implies that the octet values 0x80 to 0xFF are subdivided into</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
assigned, unassigned, experimental, and reserved groups in the</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
parallel way.</div>
</blockquote>
<div><br>
</div>
<div><font color=3D"#ff0000">I have&nbsp;already&nbsp;changed it to:</font>=
</div>
<div><font color=3D"#ff0000">&quot;Value &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp;Meaning &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Reference</font></div>
<div><font color=3D"#ff0000">0x0C-0x7A &nbsp; &nbsp; &nbsp;Unassigned</font=
></div>
<div><font color=3D"#ff0000">0x7B-0x7E &nbsp; &nbsp; &nbsp;Experimental &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; this document</=
font></div>
<div><font color=3D"#ff0000">0x7F &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp; &nbsp;Reserved &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; this document</font></div>
<div><font color=3D"#ff0000">0x80-0xFA &nbsp; &nbsp; &nbsp;Reserved for Com=
posite tunnel &nbsp; &nbsp; &nbsp;this document</font></div>
<div><font color=3D"#ff0000">0xFB-0xFE &nbsp; &nbsp; &nbsp;Experimental &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;[RFC7385]=
</font></div>
<div><font color=3D"#ff0000">0xFF &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp; &nbsp;Reserved &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; [RFC7385]</font></div>
<div><font color=3D"#ff0000">&quot;</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
9.1&nbsp;&nbsp;Normative References</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; [MEF6.1] Metro Ethernet Forum, &quot;Ethernet Services Definit=
ions - Phase</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
&nbsp;&nbsp; 2&quot;, MEF 6.1, April 2008.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
Can we get a URL for this?</div>
</blockquote>
<div><br>
</div>
<div><font color=3D"#ff0000">Done.</font></div>
<div><br>
</div>
<div><font color=3D"#ff0000">Thanks,</font></div>
<div><font color=3D"#ff0000">Ali</font></div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); padding: 0px 0p=
x 0px 5px; margin: 0px 0px 0px 5px;">
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
[EOF]</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Consolas, monospace; font-s=
ize: 12px;">
<br>
</div>
</blockquote>
</body>
</html>

--_000_D5C97FC2217743sajassiciscocom_--


From nobody Mon Aug 28 20:59:53 2017
Return-Path: <zhencao.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B6F61321AC; Mon, 28 Aug 2017 20:59:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4FSdspV3FVRt; Mon, 28 Aug 2017 20:59:50 -0700 (PDT)
Received: from mail-vk0-x231.google.com (mail-vk0-x231.google.com [IPv6:2607:f8b0:400c:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29F541321A0; Mon, 28 Aug 2017 20:59:47 -0700 (PDT)
Received: by mail-vk0-x231.google.com with SMTP id q189so6491597vke.4; Mon, 28 Aug 2017 20:59:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8+jZNW0UBMWaemdrpcX1K2qEmPDoGOvQlpIK0DjZAFo=; b=LCpHYeRaNvFs1oXrqS34SeH0YCFhW2EZeckfbhN82pNEyZlCdHSueR7gVDhyqKazNw H2GW4TgF7rDVzyrzXkRLCX9bDl8LTBH6nYhxO2x/qUNkKEcr1Pumqmp9P4EOP22lPPaR Bm87mxAh6OG3Jn+OMB+4UnuOypZX4iHVRol1Qwv1huJQXuhrBsydr7s6R0P53x3/OkqC K8hQQD7fxsmW/uKnRX74CSdToJqpHdSDH+5pw5U7Rs+Nr8G5r1JB9/ojKsNN7PHllA3n PWKy95qst+8+LrDeSXvQlqe9t40yYrRu8T2ZOLm4IXhAYapAATAcYjoLW/U0mL1gQgRj fdIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8+jZNW0UBMWaemdrpcX1K2qEmPDoGOvQlpIK0DjZAFo=; b=LEmGPiGv1eeAupHhvdwXR62jTYYPzkt/2CqcyuOCC1Hzxapt6NgkyE3E4oRY5Vg0xi yRSfqHWlaW60d4vGYkwBExJVSUfgT80xNXpv1OWOA1rRQfJS43YwzYLjcTx3Dp5VAnXS b+9URolL7bWYqp8kQPTqXmgWBE8r3vQGrixHNcKZihX81J4Yqd1dl3VnF3sxKcWK10Mc Bb66HH60G3TE9oTid5BigfpUH41Gj+d7hWIiKeNNcES7wo1a2EFJ65BSR2Z7Eve/q4qe lP+OO2mThVWtuyHL2mH6x620rVR2RIii/3ASi+opmNoUkud8qWUAwofx1GtTVQmyhp8i pX/A==
X-Gm-Message-State: AHYfb5ih4azlTK6V9RuK2MNsQhmD5Rv3QnOFDNoQ62VcvJM3DVFBABQ6 XSps/y7dEIrndhjhol+lZJJU7Pb7fw==
X-Received: by 10.31.134.7 with SMTP id i7mr1676447vkd.76.1503979186182; Mon, 28 Aug 2017 20:59:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.41.161 with HTTP; Mon, 28 Aug 2017 20:59:45 -0700 (PDT)
In-Reply-To: <150094520677.26176.17525876529879529582@ietfa.amsl.com>
References: <150094520677.26176.17525876529879529582@ietfa.amsl.com>
From: Zhen Cao <zhencao.ietf@gmail.com>
Date: Tue, 29 Aug 2017 11:59:45 +0800
Message-ID: <CAFxP68z-+dfGipj9xFGMJHCk+km+i3iocK+tGD0BF-TVv6nD9w@mail.gmail.com>
Subject: Re: Intdir early review of draft-ietf-lwig-energy-efficient-07
To: Bernie Volz <volz@cisco.com>
Cc: int-dir@ietf.org, lwip@ietf.org, ietf@ietf.org,  draft-ietf-lwig-energy-efficient.all@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/w3u0IqCt7lfae1tftAR-PPl_eR4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 29 Aug 2017 03:59:52 -0000

Hi Bernie, Thank you so much for the review, and the valuable comments
for us to improve the draft.

We will come up with wording proposals shortly.

Many thanks,
Zhen

On Tue, Jul 25, 2017 at 9:13 AM, Bernie Volz <volz@cisco.com> wrote:
> Reviewer: Bernie Volz
> Review result: Ready with Nits
>
> I am an assigned INT directorate early reviewer for
> draft-ietf-lwig-energy-efficient-07. These comments were written primarily for
> the benefit of the Internet Area Directors.
>
> Document editors and shepherd(s) should treat these comments just like they
> would treat comments from any other IETF contributors and resolve them along
> with any other comments that have been received. For more details on the INT
> Directorate, see http://www.ietf.org/iesg/directorate.html.
>
> I found the document's information interesting, and it is document that is
> benefical to the IETF community in understanding the impact energy savings
> techniques (mostly related to radios for wireless communication) can have on
> protocols (both at lower and higher layers). It is going for Informational
> status, which I think is appropriate for this document.
>
> All my comments are fairly minor nits.
>
> In section 1, "Only few efforts focused on" should likely be "Only few efforts
> have focused on"? (Add have)
>
> In section 1.1, I think this section can be removed as there are no uses of the
> RFC 2119 keywords.
>
> In section 2, there are a few technologies listed here that might use
> references; some do appear later but not all. It is usually a good question as
> to where references are best added since this is overview material. Those
> without any references are ITU-T G.9959 and MS/TP-BACnet.
>
> Also in Figure 2, it is too bad that some power value for listening (when not
> "actively" expecting a packet) isn't included since there is a claim that this
> can use more energy than transmitting, but it would also be a uJ/<time> which
> is unlike the others. Though perhaps indicating a "listening (for X ms)" entry
> could work? Anyway, not a big issue.
>
> In section 3, I presume everyone knows what MAC is
> (draft-bormann-lwig-7228bis-01 does not define it). Also, might be good to
> indicate what RDC is as it is just used (in the MAC and Radio Duty Cycling
> section, so pretty obvious likely).
>
> Also in section 3, "take great care of the problem" is a bit strange wording.
> Perhaps "are at work on the problem"? Or something like that? And, "can work
> perfectly with them" would certainly be great, it may be a stretch of goal -
> "can work well with them" may be better?
>
> In section 3.2, "contributes to the packet overall delay" should be
> "contributes to the packet's overall delay" ('s).
>
> In section 3.3, "in some services this kind of networks, such as over-the-air"
> could be "for some services, such as over-the-air". I think for is better than
> in and not sure "these kinds of networks" (instead of this kind of networks) is
> really needed?
>
> Also, in this section, "that can achieved when" should be "that can be achieved
> when".
>
> In section 3.5.1, "extended sleep modes, traffic filtering" should likely be
> "extended sleep modes, and traffic filtering". (You may or may not prefer the
> last comma in a list, but the "and" should be there).
>
> And, in this section, in "upper layer protocols knows such capabilities
> provided" likely should be "upper layer protocols know such capabilities are
> provided".
>
> And, in this section, I don't think you need to define (STA) in several places;
> once (first time) should be sufficient?
>
> And, in this section, "by not forwarding individually addressed frames
> addresses to" perhaps this should drop "individually addressed"? But perhaps
> I'm not understanding why it is needed?
>
> And, "Upper layer protocols would better synchronize" perhaps could be "Upper
> layer protocols would best synchronize"? Or just "Upper layer protocols should
> synchronize"?
>
> In section 3.5.3, perhaps insert spaces between the 6LoWPAN references to make
> the formatting more flexible?
>
> And, in this section, should TDMA be defined (again a fairly common term, but
> not in draft-bormann-lwig-7228bis-01.
>
> In section 3.5.4, I think you would want to use "connectionless" instead of
> "connection less"?
>
> And, in this section, "data transfer reliability significant" should be "data
> transfer reliability significantly"?
>
> In section 4, "So they are quite ignorant" it isn't exactly clear what "they"
> are. Replace with "So higher level protocols are quite ignorant"?
>
> And, "but both the sender and receiver should spend" should likely be "but both
> the sender and receive will spend"?
>
> In section 6.2, a reference for oneM2M (perhaps to www.onem2m.org) could be
> added?
>
> In section 9, the "Thank Ted Lemon, Joel Jaeggli, and efforts to initiate this
> facilities" sounds more like notes than actual text? Perhaps something like
> "Thanks to Ted Lemon and Joel Jaeglli for initiating and facilitating this
> editing session."?
>
> In section 12.1, for the EN300 reference, there are double quotes that probably
> aren't needed (single would do)?
>
> Finally, thanks for writing the document!
>
> - Bernie Volz
>
>


From nobody Mon Aug 28 21:00:52 2017
Return-Path: <zhencao.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0225132732; Mon, 28 Aug 2017 21:00: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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o8OYKc9wBHVd; Mon, 28 Aug 2017 21:00:42 -0700 (PDT)
Received: from mail-ua0-x22e.google.com (mail-ua0-x22e.google.com [IPv6:2607:f8b0:400c:c08::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77EA31326F4; Mon, 28 Aug 2017 21:00:41 -0700 (PDT)
Received: by mail-ua0-x22e.google.com with SMTP id 104so7036257uas.1; Mon, 28 Aug 2017 21:00:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yJgiNE2BEFFs+yXcH+0Y1Sp0YYNrDg16E95h8FMlWgE=; b=FQ3+CxKRcoX/TqjbVrtXKlI3K7KgfOghEpUk5epLnrDNoS8pFcL862jZo11N6d343y pRIrtisiR1PrNeISe9VwCC+srNz8B9w1g8hQMoWDZvZmCnr9SoDPKvD5v9fVYAERJ1w6 Q/tIgh6LWs8HGB7YChKf1RER+DRaMRkozdkteDkurm7j4sWnVY0eCykIKieWRhFWxz5H 4yeSW4TVR7HSnkzlMh6m0ZvsI5EWRzlB5bJ+INNix3H9wS7OGIfDR6RkOHmi/LRalLmD u02FvR2/W1mUJPb11KdEAr3emAn91CdkvWndv0tTXZbCid8ypDwvuvnRb/S0Ab9K2fCv CY2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yJgiNE2BEFFs+yXcH+0Y1Sp0YYNrDg16E95h8FMlWgE=; b=n9W0JvBJ3T6iUFcIPeTe98z0jjlOYyq1FKJC3NXyU0af7Un2la4baMwc/znjCImWyh /sAsr7RhjZpVEtTM4R5GPw/gaIE/PtqZE4bgBeJGIOXY7CiLuSXR6QNhXvC+8VPYuJFZ 6Ml7wkes1b2bGH12D4uoRmCmkf09gJgb7crf456e4Qbw+jOHlh2rzN3+jLGI2qJvrhkt W2MeqYdinxaRtXlc5AmY8AQd44fynjfNJw+BBHvA9tk2MTbGBLcUwqgAPQx7HOBSe+FA +lk9cTrk95qoCbPnJMpZoWjeQZ0g46zY5ruxFpygVmpeIoVu12akjyg0Nvex8VhY2M9H t9IQ==
X-Gm-Message-State: AHYfb5hKws3wCFDPk7xBELqggC7VbDmQMQ7qzSD09xouE2S2QnhpXWlh HuCi8Vktr6KQSIM+gGrmXXk0oE2I08FWtj0=
X-Received: by 10.176.82.78 with SMTP id j14mr1804901uaa.158.1503979240599; Mon, 28 Aug 2017 21:00:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.41.161 with HTTP; Mon, 28 Aug 2017 21:00:40 -0700 (PDT)
In-Reply-To: <150116690760.11487.2065170484353080456@ietfa.amsl.com>
References: <150116690760.11487.2065170484353080456@ietfa.amsl.com>
From: Zhen Cao <zhencao.ietf@gmail.com>
Date: Tue, 29 Aug 2017 12:00:40 +0800
Message-ID: <CAFxP68w_Qf5Q3=uJ50wOeGGk-WP5ca15iK1AUVHM6xcLVx4=9Q@mail.gmail.com>
Subject: Re: Iotdir early review of draft-ietf-lwig-energy-efficient-07
To: Charles Perkins <charlie.perkins@huawei.com>
Cc: Iot-dir@ietf.org, lwip@ietf.org, ietf@ietf.org,  draft-ietf-lwig-energy-efficient.all@ietf.org, charliep@computer.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JHrtipQSxclGnY11ZfrWoFiqAQM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 29 Aug 2017 04:00:44 -0000

Thank you so much, Charlies, for the review, and the valuable comments
for us to improve the draft.

We will come up with wording proposals shortly.

Many thanks,
Zhen

On Thu, Jul 27, 2017 at 10:48 PM, Charles Perkins
<charlie.perkins@huawei.com> wrote:
> Reviewer: Charles Perkins
> Review result: On the Right Track
>
> [Please excuse if this is a duplicate.  I got an error from datatracker on my first attempt.]
>
> Overall comments:
>
> I think that some important techniques for energy efficiency deserve mention
> or significant enlargement:
>
> - Packet bundling
> - Data aggregation
> - Power management / range reduction
> - Fragmentation is more energy-efficient at lower layers than at higher layers
> - Compression, on the other hand, is more efficient at higher layers,
>   particularly before encryption.
>
> The document needs a concise statement of purpose.  Maybe insert the
> following after the first paragraph of the Introduction:
>
>    In this document we describe techniques that are in common use at Layer 2
>    and at Layer 3, and we indicate the need for higher-layer awareness of
>    lower-layer features.
>
> Also in the introduction, some discussion is needed about cross-layer design.
> Is cross-layer design in scope for the [lwig] Working Group?
>
> In figure 1 and elsewhere, it should not be assumed that RPL is the only
> choice for routing in energy-efficient networks.  So, for instance,
> "RPL" could be replaced by "RTG" in Figure 1.
>
> Shouldn't there be an entry for synchronized reception in Figure 2?  Isn't
> Figure 2 actually a table, and thus should be labeled Table 1?
>
> Section 3.3 (Throughput) does not seem to add much if anything to the
> discussion.  The conclusion about the trade-off is quite obvious.
>
> Particularly in section 3.5.2, but also elsewhere, some examples would
> be very helpful.
>
> Section 6.3 (CoAP timers) seems to be only about one timer.
> Are there more?  What about interactions with TCP timers, etc.?
>
> Section 7 should be entitled "Summary and Conclusions".
> In section 7, it would be nice to offer cross references for each
> conclusion, referring the reader to the relevant section of the document.
> Each conclusion should follow from some previous section of the document.
> Unfortunately that currently isn't quite the case.
>
> The citation [Announcementlayer] does not appear in the body of the article.
>
> There are weird line breaks appearing at certain random points in the
> document.
>
> I have editorial suggestions and corrections which I will
> supply as an rfcdiff file under separate email.
>
> Regards,
> Charlie P.
>


From nobody Tue Aug 29 05:38:12 2017
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AF48D132A8F; Tue, 29 Aug 2017 05:38:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Tim Wicinski <tjw.ietf@gmail.com>
To: <ops-dir@ietf.org>
Cc: ospf@ietf.org, draft-ietf-ospf-encapsulation-cap.all@ietf.org, ietf@ietf.org
Subject: Opsdir last call partial review of draft-ietf-ospf-encapsulation-cap-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.59.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150401028465.13280.5869374542696138659@ietfa.amsl.com>
Date: Tue, 29 Aug 2017 05:38:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XGTQ6RN4EcWyZWdxzxPlhZBMt0s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 29 Aug 2017 12:38:05 -0000

Review is partially done. Another review request has been registered for
completing it.

Reviewer: Tim Wicinski
Review result: Has Issues

Summary: Almost Ready

The content appears to be fine, but there are some outdated (the biggest one is
5226 replaced by 8126), but its the IANA section which appears the most
confusing.

7.1 OSPF Router Information (RI) Registry -  appears fine

7.2 OSPF Tunnel Encapsulation Attribute Sub-TLV Registry

This one defines the values being defined/allocated from "This Document" but in
Section 5, each Sub-TLV is defined in other documents, so it's totally
confusing.


From nobody Tue Aug 29 11:32:00 2017
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13F29132941; Tue, 29 Aug 2017 11:31:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 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, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O0tHFZpSSE_u; Tue, 29 Aug 2017 11:31:51 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7A70132951; Tue, 29 Aug 2017 11:31:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7095; q=dns/txt; s=iport; t=1504031510; x=1505241110; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=VZG6339rYaHJSnvJ6LZ61yhcCRf6ogtZlbY8zvBrtw8=; b=fsuioizn9Lrtr85g2uOm5Px4o+mUtyCD8+vPZMGKccig0qCSGDkVNlYQ rk31AifWh8/+J47cVn8fnZI8fRiMtjMMykcKS10iEiko04jpoG1BKNgde DGrPToJeQY8Khzge5/KR+w7HNybEZ/Xkqz3sznAM+A1nnmopLUOP6T/UV E=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CeAgD5saVZ/xbLJq1dGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBiUqLEZB2IpY1ggQHggWDOwKEWBUBAgEBAQEBAQFrKIUYAQEBAQIBIwR?= =?us-ascii?q?EDgULCxgVFQICVwYBDAgBAYolCK5+gW06i18BAQEBAQEBAwEBAQEBAQEBEQ+DK?= =?us-ascii?q?oUzKwuCcoQwLQJVglSCYQEEiXcWiH2FIog8hDeCIY10ghKFZ4NZJIZ1lkI1IoE?= =?us-ascii?q?NMiEIHBVJhROCCj6MCgEBAQ?=
X-IronPort-AV: E=Sophos;i="5.41,445,1498521600";  d="asc'?scan'208";a="696830849"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Aug 2017 18:31:47 +0000
Received: from [10.61.82.247] (ams3-vpn-dhcp4856.cisco.com [10.61.82.247]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v7TIVlPu007306; Tue, 29 Aug 2017 18:31:47 GMT
Subject: Re: Secdir early review of draft-ietf-opsawg-mud-08
To: Adam Montville <adam.w.montville@gmail.com>, secdir@ietf.org
Cc: draft-ietf-opsawg-mud.all@ietf.org, opsawg@ietf.org, ietf@ietf.org
References: <150384057895.866.9675653302394719026@ietfa.amsl.com>
From: Eliot Lear <lear@cisco.com>
Message-ID: <bea3e871-bc5c-38f8-4027-44c3559afad1@cisco.com>
Date: Tue, 29 Aug 2017 20:31:46 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <150384057895.866.9675653302394719026@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="jmgMsA6Cn433PtjGGFebCXJVwkOsEDnT7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KpAH_gzlynV2M8_cOeaThSzGzH4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 29 Aug 2017 18:31:53 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--jmgMsA6Cn433PtjGGFebCXJVwkOsEDnT7
Content-Type: multipart/mixed; boundary="ek3fMXD6SSlRctE5dK75NveXHsREUe6Fs";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Adam Montville <adam.w.montville@gmail.com>, secdir@ietf.org
Cc: draft-ietf-opsawg-mud.all@ietf.org, opsawg@ietf.org, ietf@ietf.org
Message-ID: <bea3e871-bc5c-38f8-4027-44c3559afad1@cisco.com>
Subject: Re: Secdir early review of draft-ietf-opsawg-mud-08
References: <150384057895.866.9675653302394719026@ietfa.amsl.com>
In-Reply-To: <150384057895.866.9675653302394719026@ietfa.amsl.com>

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

Hi Adam,

Thanks very much for your review.=C2=A0 I'm pleased you like the general
approach.=C2=A0 You hit the nail on the head: this is NOT intended to be =
a
panacea, but a means by which the device (and its manufacturer) can
enlist the network's protection. Indeed as I mentioned the first time I
presented to SAAG, I will say now again (with feeling):

NOTHING in that draft nor anywhere ELSE should excuse a
manufacturer/developer from best coding practices and updating
software.=C2=A0 The best form of protection will ALWAYS ALWAYS be a well
secured device to begin with.

MUD is simply there to add an additional layer for when the hacker gets
there first...

Please now see below.


On 8/27/17 3:29 PM, Adam Montville wrote:
>
> Finally, I found myself wondering if this type of appraoch - communicat=
ing
> intended use - could be extended to software installed on general purpo=
se
> devices. For example, it would be interesting to consider how a given i=
nstalled
> software package could communicate not only its intended use, but it's
> preferred configuration.

I'd very much like to pursue this concept, but it seems to me it has to
be rooted in some sort of hardware trust.

>
> Some questions to consider (these are potential issues):
>
> At the top of page 9, the draft describes controller behavior for mobil=
e
> devices - configurations should be removed when the device is removed. =
Does
> this apply also to intermittent devices?=20
Well indeed so.=C2=A0 I think the discussion around mobility is confusing=
=2E=C2=A0
I've cleaned that up.

> When would a device be considered
> "removed" instead of simply powered down?

I think the best way to look at this is to view the configuration
information as ephemeral, and since the device provides the information
on connect, or otherwise periodically (eg LLDP), you can regenerate the
state.

>  Also, when reading that paragraph I
> began wondering about the load on Web servers serving MUD files - not t=
hat this
> draft should say anything about it, but that it's something manufacture=
rs are
> going to have to consider and account for.
Right.
>
> Is a stronger statement needed on the first bullet of section 4? Should=
 it
> read: Anything not explicitly permitted MUST be denied? Similarly for o=
ther
> requirements in MUD file processing. At about this point, I began wonde=
ring if
> additional security considerations may be required for the controller.

One of the principles we try to observe is that the administrator owns
the network.=C2=A0 As such we should be somewhat cautious about how we ph=
rase
such things.=C2=A0 From a MUD perspective, what you end up with is an
access-list that an administrator might choose to augment.=C2=A0 For
instance, if he or she is running a special load on a Thing using
802.1AR certificates, he might want to augment the access to accommodate
a new feature.

In fact, it may be possible that a manufacturer writes such a complex
MUD file that the network administrator desires an optimization.=C2=A0 We=
 do
not yet have enough experience to know what sort of normative statement
would cover that ;-)

>
> Section 9.2 describes DHCP server behavior, and is written in a manner
> presuming the DHCP server knows what's happening with these building bl=
ocks. I
> am not a DHCP expert, so there may be something in DHCP instructing a s=
erver to
> ignore everything it doesn't understand, but if that is not the case, t=
hen what
> is expected to happen when DHCP is not expecting these options and is n=
ot going
> to ignore them?

This is not a worry.=C2=A0 DHCP servers are very capable of ignoring unkn=
own
options, and they have to be well bullet proofed today or we have FAR
FAR bigger fish to fry ;-)
>
> Nits follow:
>
> First paragraph of section 1.5: s/another example might to follow/anoth=
er
> example might be to follow/
Right!
>
> Recommend the following for definition of Thing: the device emitting a =
MUD URL.

Ok.
>
> Suggest striking last two sentences of Manufacturer definition, as irre=
levant.

Ahhh but this actually is a big deal to system integrators ;-)=C2=A0 They=

want to know what their role in the ecosystem is.

>
> Is there a way to make the ASCII art in section 1.7 a little cleaner? O=
ne
> possibility is to move the right side of the bounding box to the left b=
y two or
> three places.

Sure.=C2=A0 Done.
> Also, the arrows to the line text isn't necessary (e.g.
> "----->get URL->" is cleaner as "---get URL--->").

Done.
>
> Second bullet on page 11: s/other otherwise/otherwise/

right.
> Should there be a newline after "<CODE BEGINS>" at the start of section=
 6?

I'm going to leave that one to the YANG doctors...
>
> On page 17: s/end(ed)/end(s\/ed)/  Basically, the sentence without "end=
ed"
> should read, "Information about when support ends, and when to refresh.=
"

This will change with the updating of the model, based on YANG doctor
feedback.=C2=A0 That very container is likely to be consolidated away.
>
> Vertial spacing could be improved for the first bit in section 9, so th=
at the
> look/feel surrounding OPTION_MUD_URL_V4 matches that of OPTION_MUD_URL_=
v6

Ok.=C2=A0 I think I addressed what you're talking about.
>
> Section 11, first sentence: s/link layer protocols/link layer protocol/=

>
>

Good catch.

Best regards and thanks again for your review.

Eliot


--ek3fMXD6SSlRctE5dK75NveXHsREUe6Fs--

--jmgMsA6Cn433PtjGGFebCXJVwkOsEDnT7
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

iQEcBAEBCAAGBQJZpbMSAAoJEIe2a0bZ0nozLGEH/j1kGQfBV3gOCuIk+flybdTr
GwCxvRmezsLCe4BnMCnA6NJWC0iC+HshNjFqoYG1IAuS5L1K8Kk30CDFAD6yULlo
/kPFgl0M0ftYEuFc3CRniB9G0SBK1ivs6X9gWJwqK+0KqgvLhn0ddPWM7I0F5rL2
ni4fe1pr1bUdErQ8lcXwk0fHcru9y+4C/4FtaJNyhzUaiyNTmlMzTIp2RikZnLbb
RZDzWh77lTeiPzw1J2Qbc3wCZapbCFpc6ovht30gdT3F92NjdqUVEKqSvIN7THQV
GzQeZkdwPXDSh5YUWhgHxrZxOjI6Fv64O4kRo/GPcJ1RP5AvwJ8sHPUFFSHLEPw=
=ueu9
-----END PGP SIGNATURE-----

--jmgMsA6Cn433PtjGGFebCXJVwkOsEDnT7--


From nobody Tue Aug 29 11:50:38 2017
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEFCF1326EC; Tue, 29 Aug 2017 11:50:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q0eZNgiQBKDd; Tue, 29 Aug 2017 11:50:28 -0700 (PDT)
Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15AC013248B; Tue, 29 Aug 2017 11:50:28 -0700 (PDT)
Received: by mail-it0-x22e.google.com with SMTP id o132so4502536itc.1; Tue, 29 Aug 2017 11:50:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1L15XunAXfD0LcRaF4p9Zt64Uw3nYwWAboSpb1hQCJo=; b=uh9eidmszsQMfP4IQQex37GLSKejdH547DSjbsRWfnwcMvaKh8dvZIwD9WyrNvy9vP YrszY1c1tA+dUIFTibEh77xhciBeGS3tfT5rGK4o3DTKC7+/oDR3p18VmAaYhlU7VE0p Di5boZ422Nd3K5Ox6BkXXi+7aY520O4020AOKzGLUvODLlsEoffit7R2NHFbuNpHiaH7 H1i5uwDtt6o3qLWsivL4/j880D3fB3yR7TkuQyneNQFGuT9g4Ess1mHqno+SiUpyJ3lj P+kKJ0hCUnsML1lFdZ2xs0IBS1sTpm2RJvlnFIdqcs2TovemyC6eCiksTS8UOH5aZgzF s3hw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1L15XunAXfD0LcRaF4p9Zt64Uw3nYwWAboSpb1hQCJo=; b=FmgJrh6aqe3V4CGOMPZg63lpSzyCCTOtAD4tlSgA0VKTT99NMAXNaKlF013mkBR4HB ZxT9tehB+SrMrNomMyK9jGi1TuEp125f34yxbm+6YWjna+Smsa6fZwhsjnzn4N/CPbHN 1Sdj3Xp42TAMM+SCO3V5HeEQ/3hQcWnn0DCL9AS5uSlX0kMo5+yG/yeHy/Y8iKv+DzaE J+flKyCEVwBVn7FnpZywKdV5pd4uEM0eJ6eF35LcjFzN7b67FaG53e+vtcLhh5LDjv4R VgMuIePFX6oHB7s51PdrjwBEZ5pHSbPLJ2ErRyxoxqYGWfizFV5pynvTlsJFwgc3LvZ+ q1/w==
X-Gm-Message-State: AHYfb5gHXL032zM6vT+TfG3VT9PeR2t4hIZ3EE0va1DBvnIFiYHgu33z yENV5CRBRdrgCi+Q6AoJ5ONSBZLwMw==
X-Received: by 10.36.249.67 with SMTP id l64mr3371819ith.66.1504032627122; Tue, 29 Aug 2017 11:50:27 -0700 (PDT)
MIME-Version: 1.0
References: <150384057895.866.9675653302394719026@ietfa.amsl.com> <bea3e871-bc5c-38f8-4027-44c3559afad1@cisco.com>
In-Reply-To: <bea3e871-bc5c-38f8-4027-44c3559afad1@cisco.com>
From: Adam Montville <adam.w.montville@gmail.com>
Date: Tue, 29 Aug 2017 18:50:15 +0000
Message-ID: <CACknUNVFJjs4y+tLr7Ks0LO9x-XTx9VLZZqVK8-jA9Cf-NFTOQ@mail.gmail.com>
Subject: Re: Secdir early review of draft-ietf-opsawg-mud-08
To: Eliot Lear <lear@cisco.com>, secdir@ietf.org
Cc: draft-ietf-opsawg-mud.all@ietf.org, opsawg@ietf.org, ietf@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c0475707864dc0557e8e2c4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/L_5xv7CFNCh4EuriAwxplvNGiMs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 29 Aug 2017 18:50:31 -0000

--94eb2c0475707864dc0557e8e2c4
Content-Type: text/plain; charset="UTF-8"

Hi Eliot,

You're welcome. Thanks for taking the time to consider, and even implement
some of, my feedback.

I agree on the hardware rooted trust for software intended use. Seems
plausible, given work coming out of TCG. I'm sure there are others who may
find this train of thought interesting.

Kind regards,

Adam

On Tue, Aug 29, 2017 at 1:31 PM Eliot Lear <lear@cisco.com> wrote:

> Hi Adam,
>
> Thanks very much for your review.  I'm pleased you like the general
> approach.  You hit the nail on the head: this is NOT intended to be a
> panacea, but a means by which the device (and its manufacturer) can
> enlist the network's protection. Indeed as I mentioned the first time I
> presented to SAAG, I will say now again (with feeling):
>
> NOTHING in that draft nor anywhere ELSE should excuse a
> manufacturer/developer from best coding practices and updating
> software.  The best form of protection will ALWAYS ALWAYS be a well
> secured device to begin with.
>
> MUD is simply there to add an additional layer for when the hacker gets
> there first...
>
> Please now see below.
>
>
> On 8/27/17 3:29 PM, Adam Montville wrote:
> >
> > Finally, I found myself wondering if this type of appraoch -
> communicating
> > intended use - could be extended to software installed on general purpose
> > devices. For example, it would be interesting to consider how a given
> installed
> > software package could communicate not only its intended use, but it's
> > preferred configuration.
>
> I'd very much like to pursue this concept, but it seems to me it has to
> be rooted in some sort of hardware trust.
>
> >
> > Some questions to consider (these are potential issues):
> >
> > At the top of page 9, the draft describes controller behavior for mobile
> > devices - configurations should be removed when the device is removed.
> Does
> > this apply also to intermittent devices?
> Well indeed so.  I think the discussion around mobility is confusing.
> I've cleaned that up.
>
> > When would a device be considered
> > "removed" instead of simply powered down?
>
> I think the best way to look at this is to view the configuration
> information as ephemeral, and since the device provides the information
> on connect, or otherwise periodically (eg LLDP), you can regenerate the
> state.
>
> >  Also, when reading that paragraph I
> > began wondering about the load on Web servers serving MUD files - not
> that this
> > draft should say anything about it, but that it's something
> manufacturers are
> > going to have to consider and account for.
> Right.
> >
> > Is a stronger statement needed on the first bullet of section 4? Should
> it
> > read: Anything not explicitly permitted MUST be denied? Similarly for
> other
> > requirements in MUD file processing. At about this point, I began
> wondering if
> > additional security considerations may be required for the controller.
>
> One of the principles we try to observe is that the administrator owns
> the network.  As such we should be somewhat cautious about how we phrase
> such things.  From a MUD perspective, what you end up with is an
> access-list that an administrator might choose to augment.  For
> instance, if he or she is running a special load on a Thing using
> 802.1AR certificates, he might want to augment the access to accommodate
> a new feature.
>
> In fact, it may be possible that a manufacturer writes such a complex
> MUD file that the network administrator desires an optimization.  We do
> not yet have enough experience to know what sort of normative statement
> would cover that ;-)
>
> >
> > Section 9.2 describes DHCP server behavior, and is written in a manner
> > presuming the DHCP server knows what's happening with these building
> blocks. I
> > am not a DHCP expert, so there may be something in DHCP instructing a
> server to
> > ignore everything it doesn't understand, but if that is not the case,
> then what
> > is expected to happen when DHCP is not expecting these options and is
> not going
> > to ignore them?
>
> This is not a worry.  DHCP servers are very capable of ignoring unknown
> options, and they have to be well bullet proofed today or we have FAR
> FAR bigger fish to fry ;-)
> >
> > Nits follow:
> >
> > First paragraph of section 1.5: s/another example might to follow/another
> > example might be to follow/
> Right!
> >
> > Recommend the following for definition of Thing: the device emitting a
> MUD URL.
>
> Ok.
> >
> > Suggest striking last two sentences of Manufacturer definition, as
> irrelevant.
>
> Ahhh but this actually is a big deal to system integrators ;-)  They
> want to know what their role in the ecosystem is.
>
> >
> > Is there a way to make the ASCII art in section 1.7 a little cleaner? One
> > possibility is to move the right side of the bounding box to the left by
> two or
> > three places.
>
> Sure.  Done.
> > Also, the arrows to the line text isn't necessary (e.g.
> > "----->get URL->" is cleaner as "---get URL--->").
>
> Done.
> >
> > Second bullet on page 11: s/other otherwise/otherwise/
>
> right.
> > Should there be a newline after "<CODE BEGINS>" at the start of section
> 6?
>
> I'm going to leave that one to the YANG doctors...
> >
> > On page 17: s/end(ed)/end(s\/ed)/  Basically, the sentence without
> "ended"
> > should read, "Information about when support ends, and when to refresh."
>
> This will change with the updating of the model, based on YANG doctor
> feedback.  That very container is likely to be consolidated away.
> >
> > Vertial spacing could be improved for the first bit in section 9, so
> that the
> > look/feel surrounding OPTION_MUD_URL_V4 matches that of OPTION_MUD_URL_v6
>
> Ok.  I think I addressed what you're talking about.
> >
> > Section 11, first sentence: s/link layer protocols/link layer protocol/
> >
> >
>
> Good catch.
>
> Best regards and thanks again for your review.
>
> Eliot
>
>

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

<div dir=3D"ltr">Hi Eliot,<div><br></div><div>You&#39;re welcome. Thanks fo=
r taking the time to consider, and even implement some of, my feedback.</di=
v><div><br></div><div>I agree on the hardware rooted trust for software int=
ended use. Seems plausible, given work coming out of TCG. I&#39;m sure ther=
e are others who may find this train of thought interesting.</div><div><br>=
</div><div>Kind regards,</div><div><br></div><div>Adam</div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr">On Tue, Aug 29, 2017 at 1:31 PM Eliot Lea=
r &lt;<a href=3D"mailto:lear@cisco.com">lear@cisco.com</a>&gt; wrote:<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">Hi Adam,<br>
<br>
Thanks very much for your review.=C2=A0 I&#39;m pleased you like the genera=
l<br>
approach.=C2=A0 You hit the nail on the head: this is NOT intended to be a<=
br>
panacea, but a means by which the device (and its manufacturer) can<br>
enlist the network&#39;s protection. Indeed as I mentioned the first time I=
<br>
presented to SAAG, I will say now again (with feeling):<br>
<br>
NOTHING in that draft nor anywhere ELSE should excuse a<br>
manufacturer/developer from best coding practices and updating<br>
software.=C2=A0 The best form of protection will ALWAYS ALWAYS be a well<br=
>
secured device to begin with.<br>
<br>
MUD is simply there to add an additional layer for when the hacker gets<br>
there first...<br>
<br>
Please now see below.<br>
<br>
<br>
On 8/27/17 3:29 PM, Adam Montville wrote:<br>
&gt;<br>
&gt; Finally, I found myself wondering if this type of appraoch - communica=
ting<br>
&gt; intended use - could be extended to software installed on general purp=
ose<br>
&gt; devices. For example, it would be interesting to consider how a given =
installed<br>
&gt; software package could communicate not only its intended use, but it&#=
39;s<br>
&gt; preferred configuration.<br>
<br>
I&#39;d very much like to pursue this concept, but it seems to me it has to=
<br>
be rooted in some sort of hardware trust.<br>
<br>
&gt;<br>
&gt; Some questions to consider (these are potential issues):<br>
&gt;<br>
&gt; At the top of page 9, the draft describes controller behavior for mobi=
le<br>
&gt; devices - configurations should be removed when the device is removed.=
 Does<br>
&gt; this apply also to intermittent devices?<br>
Well indeed so.=C2=A0 I think the discussion around mobility is confusing.=
=C2=A0<br>
I&#39;ve cleaned that up.<br>
<br>
&gt; When would a device be considered<br>
&gt; &quot;removed&quot; instead of simply powered down?<br>
<br>
I think the best way to look at this is to view the configuration<br>
information as ephemeral, and since the device provides the information<br>
on connect, or otherwise periodically (eg LLDP), you can regenerate the<br>
state.<br>
<br>
&gt;=C2=A0 Also, when reading that paragraph I<br>
&gt; began wondering about the load on Web servers serving MUD files - not =
that this<br>
&gt; draft should say anything about it, but that it&#39;s something manufa=
cturers are<br>
&gt; going to have to consider and account for.<br>
Right.<br>
&gt;<br>
&gt; Is a stronger statement needed on the first bullet of section 4? Shoul=
d it<br>
&gt; read: Anything not explicitly permitted MUST be denied? Similarly for =
other<br>
&gt; requirements in MUD file processing. At about this point, I began wond=
ering if<br>
&gt; additional security considerations may be required for the controller.=
<br>
<br>
One of the principles we try to observe is that the administrator owns<br>
the network.=C2=A0 As such we should be somewhat cautious about how we phra=
se<br>
such things.=C2=A0 From a MUD perspective, what you end up with is an<br>
access-list that an administrator might choose to augment.=C2=A0 For<br>
instance, if he or she is running a special load on a Thing using<br>
802.1AR certificates, he might want to augment the access to accommodate<br=
>
a new feature.<br>
<br>
In fact, it may be possible that a manufacturer writes such a complex<br>
MUD file that the network administrator desires an optimization.=C2=A0 We d=
o<br>
not yet have enough experience to know what sort of normative statement<br>
would cover that ;-)<br>
<br>
&gt;<br>
&gt; Section 9.2 describes DHCP server behavior, and is written in a manner=
<br>
&gt; presuming the DHCP server knows what&#39;s happening with these buildi=
ng blocks. I<br>
&gt; am not a DHCP expert, so there may be something in DHCP instructing a =
server to<br>
&gt; ignore everything it doesn&#39;t understand, but if that is not the ca=
se, then what<br>
&gt; is expected to happen when DHCP is not expecting these options and is =
not going<br>
&gt; to ignore them?<br>
<br>
This is not a worry.=C2=A0 DHCP servers are very capable of ignoring unknow=
n<br>
options, and they have to be well bullet proofed today or we have FAR<br>
FAR bigger fish to fry ;-)<br>
&gt;<br>
&gt; Nits follow:<br>
&gt;<br>
&gt; First paragraph of section 1.5: s/another example might to follow/anot=
her<br>
&gt; example might be to follow/<br>
Right!<br>
&gt;<br>
&gt; Recommend the following for definition of Thing: the device emitting a=
 MUD URL.<br>
<br>
Ok.<br>
&gt;<br>
&gt; Suggest striking last two sentences of Manufacturer definition, as irr=
elevant.<br>
<br>
Ahhh but this actually is a big deal to system integrators ;-)=C2=A0 They<b=
r>
want to know what their role in the ecosystem is.<br>
<br>
&gt;<br>
&gt; Is there a way to make the ASCII art in section 1.7 a little cleaner? =
One<br>
&gt; possibility is to move the right side of the bounding box to the left =
by two or<br>
&gt; three places.<br>
<br>
Sure.=C2=A0 Done.<br>
&gt; Also, the arrows to the line text isn&#39;t necessary (e.g.<br>
&gt; &quot;-----&gt;get URL-&gt;&quot; is cleaner as &quot;---get URL---&gt=
;&quot;).<br>
<br>
Done.<br>
&gt;<br>
&gt; Second bullet on page 11: s/other otherwise/otherwise/<br>
<br>
right.<br>
&gt; Should there be a newline after &quot;&lt;CODE BEGINS&gt;&quot; at the=
 start of section 6?<br>
<br>
I&#39;m going to leave that one to the YANG doctors...<br>
&gt;<br>
&gt; On page 17: s/end(ed)/end(s\/ed)/=C2=A0 Basically, the sentence withou=
t &quot;ended&quot;<br>
&gt; should read, &quot;Information about when support ends, and when to re=
fresh.&quot;<br>
<br>
This will change with the updating of the model, based on YANG doctor<br>
feedback.=C2=A0 That very container is likely to be consolidated away.<br>
&gt;<br>
&gt; Vertial spacing could be improved for the first bit in section 9, so t=
hat the<br>
&gt; look/feel surrounding OPTION_MUD_URL_V4 matches that of OPTION_MUD_URL=
_v6<br>
<br>
Ok.=C2=A0 I think I addressed what you&#39;re talking about.<br>
&gt;<br>
&gt; Section 11, first sentence: s/link layer protocols/link layer protocol=
/<br>
&gt;<br>
&gt;<br>
<br>
Good catch.<br>
<br>
Best regards and thanks again for your review.<br>
<br>
Eliot<br>
<br>
</blockquote></div></div>

--94eb2c0475707864dc0557e8e2c4--


From nobody Tue Aug 29 13:48:27 2017
Return-Path: <bew@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50ECA1320CC; Tue, 29 Aug 2017 13:48:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level: 
X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0TBEBDEBspig; Tue, 29 Aug 2017 13:48:21 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90745124E15; Tue, 29 Aug 2017 13:48:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=48306; q=dns/txt; s=iport; t=1504039701; x=1505249301; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=/VU45vNSS6vq9tQx0WXLj7/iEvkXzKBNyuRka6BkRZw=; b=bGyeKhE8IsKzkPM5SHwKONt0bVL0XmKQj7TU8RaGR8JrCUDP8NC1pAvn Arpxb4po92HL0noieF08hPWltp8JuFoSYMpj1w76s8asxdfwRGUbwKtTk C/TkbgeZ6ni8X010yWx5CDIjO+ZadT1F/9a2HdXKcZDX31+u4DYLM38FZ I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ARAQBp0qVZ/4YNJK1TBwMZAQEBAQEBA?= =?us-ascii?q?QEBAQEHAQEBAQGDWmSBFQeDLUOKHpAbgU+IW41uDoIELIFggzsCGoN7PxgBAgE?= =?us-ascii?q?BAQEBAQFrKIUZBgwOCVYQAgEGAjgHAwICAh8RFBECBA4FiU1MAxUQkSSdZoInh?= =?us-ascii?q?zYNhAYBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYMqgQt3gzErC4FlgQ2CV4FrAQc?= =?us-ascii?q?LAQkJJAomgkwwgjEFoCw8AodXh32EdoIShWeKcol3glWJdQEfOIECC3cVWwGFB?= =?us-ascii?q?AEcgWd2iRECBAEIF4EMgQ8BAQE?=
X-IronPort-AV: E=Sophos;i="5.41,445,1498521600";  d="scan'208,217";a="473673296"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Aug 2017 20:48:19 +0000
Received: from XCH-RTP-004.cisco.com (xch-rtp-004.cisco.com [64.101.220.144]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id v7TKmJsq020337 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 29 Aug 2017 20:48:19 GMT
Received: from xch-rtp-001.cisco.com (64.101.220.141) by XCH-RTP-004.cisco.com (64.101.220.144) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 29 Aug 2017 16:48:18 -0400
Received: from xch-rtp-001.cisco.com ([64.101.220.141]) by XCH-RTP-001.cisco.com ([64.101.220.141]) with mapi id 15.00.1263.000; Tue, 29 Aug 2017 16:48:18 -0400
From: "Brian Weis (bew)" <bew@cisco.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
CC: "secdir@ietf.org" <secdir@ietf.org>, "draft-weis-gdoi-rekey-ack.all@ietf.org" <draft-weis-gdoi-rekey-ack.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Secdir last call review of draft-weis-gdoi-rekey-ack-05
Thread-Topic: Secdir last call review of draft-weis-gdoi-rekey-ack-05
Thread-Index: AQHTDgJglUgJl63bZkSkx0TnTx/5x6KUGN4AgAMP2QCABQ6cgA==
Date: Tue, 29 Aug 2017 20:48:18 +0000
Message-ID: <DE62366A-0377-4DE1-9ED0-A14E44A7EC05@cisco.com>
References: <150194814585.18635.3104789196001873381@ietfa.amsl.com> <E61F05DB-EEB0-4140-A2D4-DB11163C4E13@cisco.com> <e2b32453-8c4f-9707-0e1f-dab29540fe54@gmail.com>
In-Reply-To: <e2b32453-8c4f-9707-0e1f-dab29540fe54@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.32.174.41]
Content-Type: multipart/alternative; boundary="_000_DE62366A03774DE19ED0A14E44A7EC05ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/P88wTaOBtjNyzWXjAUjw-YKwBR0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 29 Aug 2017 20:48:25 -0000

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

SGkgWWFyb24sDQoNCk9uIEF1ZyAyNiwgMjAxNywgYXQgODozNCBBTSwgWWFyb24gU2hlZmZlciA8
eWFyb25mLmlldGZAZ21haWwuY29tPG1haWx0bzp5YXJvbmYuaWV0ZkBnbWFpbC5jb20+PiB3cm90
ZToNCg0KSGkgQnJpYW4sDQoNClRoYW5rIHlvdSBmb3IgYWRkcmVzc2luZyBtb3N0IG9mIG15IGNv
bW1lbnRzIGluIHRoZSBuZXcgdmVyc2lvbiwgYW5kIGZvciBjbGFyaWZ5aW5nIHBvaW50cyB3aGVy
ZSBJIHdhcyBvZmYgdGhlIG1hcmsuDQoNClRoZSBvbmx5IHJlbWFpbmluZyBjb21tZW50IHRoYXQn
cyBvbmx5IHBhcnRseSBhZGRyZXNzZWQgaXMgdGhlIG9uZSBvbiBjcnlwdG8gYWdpbGl0eS4gUXVv
dGluZyBteXNlbGY6DQoNCndlIG5lZWQgdG8gZGVmaW5lIHdoZXRoZXIgbXVsdGlwbGUgc3VjaCBw
YXlsb2FkcyBjYW4gYmUgc2VudCBzaW11bHRhbmVvdXNseSAoaWYgZS5nLiBzb21lIEdNcyBzdGls
bCBzdXBwb3J0IHRoZSBvbGQgYWxnb3JpdGhtKSBhbmQgd2hhdCdzIHRoZSBleHBlY3RlZCBiZWhh
dmlvci4NCg0KSW4gb3RoZXIgd29yZHMsIHN1cHBvcnRpbmcgbW9yZSBhbGdvcml0aG1zIGluIG5v
dCBzdWZmaWNpZW50LiBUaGUgcXVlc3Rpb24gaXMgd2hldGhlciB3ZSBzdXBwb3J0IGluY3JlbWVu
dGFsIGRlcGxveW1lbnQgb2YgYSBuZXcgYWxnb3JpdGhtIHRvIGEgbGFyZ2UgZ3JvdXAgb2YgR01z
Lg0KDQpTb3JyeSwgd2UgbWlzc2VkIHRoaXMuIEluY3JlbWVudGFsIGRlcGxveW1lbnQgb2YgYW55
IG5ldyBwb2xpY3kgKGFsZ29yaXRobSBvciBvdGhlcndpc2UpIHdpdGhpbiBhIGdyb3VwIGlzIG5v
dCBzbyBzdHJhaWdodGZvcndhcmQuIFRoZXJlIGNhbiByZWFsbHkgb25seSBiZSBvbmUgc2V0IG9m
IHBvbGljeSB1c2VkIGJ5IHRoZSBlbnRpcmUgZ3JvdXAgYmVjYXVzZSBpZiBhIHNlbmRlciBoYXMg
YmVlbiB1cGRhdGVkIHRvIGEgbmV3IHNldCBvZiBwb2xpY3kgaXQgY2Fu4oCZdCByZWFsbHkgdXNl
IGl0IHVudGlsIGFsbCByZWNlaXZlcnMgYXJlIHNpbWlsYXJseSB1cGdyYWRlZC4gVGhpcyBpcyBh
IHBsYWNlIHdoZXJlIGEgY2FwYWJpbGl0aWVzIGV4Y2hhbmdlIGNhbiBiZSB1c2VmdWwgZm9yIGEg
a2V5IHNlcnZlciB0byBkZWNsYXJlIGEgc3dpdGNoIHRvIGEgbmV3IGFsZ29yaXRobSBhZnRlciBh
bGwgbWVtYmVycyBjbGFpbSB0byBzdXBwb3J0IGl0LCBidXQgdGhhdCBtaWdodCBuZXZlciBoYXBw
ZW4gaW4gYSBsYXJnZSBncm91cC4gUHJhY3RpY2FsbHkgc3BlYWtpbmcgaW5jcmVtZW50YWwgdXBk
YXRlcyBpbiBhIGxhcmdlIGdyb3VwIG1pZ2h0IHJlcXVpcmUgdHdvIGRpZmZlcmVudCBncm91cHMg
d2l0aCBhIGJyaWRnZSBiZXR3ZWVuLCBvciBzb21lIG90aGVyIGRlcGxveW1lbnQgc3RydWN0dXJl
LiBTaW5jZSBpdOKAmXMgYSBicm9hZGVyIHByb2JsZW0sIEnigJltIG5vdCBzdXJlIHdoYXQgZWxz
ZSB3ZSBjYW4gZG8gaW4gdGhpcyBkb2N1bWVudCB0byBhZGRyZXNzIGluY3JlbWVudGFsIGRlcGxv
eW1lbnQuDQoNClRoYW5rcywNCkJyaWFuDQoNCg0KVGhhbmtzLA0KWWFyb24NCg0KT24gMjQvMDgv
MTcgMTk6NDgsIEJyaWFuIFdlaXMgKGJldykgd3JvdGU6DQpIaSBZYXJvbiwNClRoYW5rcyBmb3Ig
dGhlIHJldmlldy4gV2XigJl2ZSBhZGRlZCBzb21lIGNsYXJpZmljYXRpb24gYmVsb3csIGFuZCBt
YWRlIHNvbWUgY2hhbmdlcyBpbiAtMDYgdG8gYWRkcmVzcyB5b3VyIGNvbW1lbnRzLiBQbGVhc2Ug
bGV0IHVzIGtub3cgaWYgd2UgZGlkIG5vdCBhZGRyZXNzIHRoZW0gc2F0aXNmYWN0b3JpbHkuDQpP
biBBdWcgNSwgMjAxNywgYXQgODo0OSBBTSwgWWFyb24gU2hlZmZlciA8eWFyb25mLmlldGZAZ21h
aWwuY29tPG1haWx0bzp5YXJvbmYuaWV0ZkBnbWFpbC5jb20+IDxtYWlsdG86eWFyb25mLmlldGZA
Z21haWwuY29tPj4gd3JvdGU6DQoNClJldmlld2VyOiBZYXJvbiBTaGVmZmVyDQpSZXZpZXcgcmVz
dWx0OiBIYXMgSXNzdWVzDQoNClN1bW1hcnk6IHRoaXMgcmV2aWV3ZXIgaXMgbm90IGNsZWFyIGFi
b3V0IHRoZSB2YWx1ZSBvZiB0aGUgcHVzaC1hY2sgKGNvbXBhcmVkDQp0byBhIHB1bGwpIGFuZCBh
Ym91dCB0aGUgc3RyYXRlZ3kgdGhhdCB3YXMgY2hvc2VuLg0KSW4gYSBncm91cCBrZXkgbWFuYWdl
bWVudCBzeXN0ZW0gZWl0aGVyIGEg4oCccHVsbOKAnSAodHJpZ2dlcmVkIGJ5IGEgZ3JvdXAgbWVt
YmVyKSBvciBhIOKAnHB1c2jigJ0gKGJ5IHRoZSBrZXkgc2VydmVyKSIgY291bGQgYmUgdXNlZCB0
byBwcm92aWRlIHVwZGF0ZXMgdG8gdGhlIGdyb3VwLiBIb3dldmVyLCBhIOKAnHB1bGzigJ0gYnkg
dGhlIGdyb3VwIG1lbWJlciBpbXBsaWVzIGEgcG9sbGluZyBtZXRob2QsIHdoaWNoIGhhcyB0aGUg
ZGVmaWNpZW5jeSB0aGF0IHRoZSBrZXkgc2VydmVyIGNhbm5vdCBjYXVzZSBhIHBvbGljeSByZXBs
YWNlbWVudCBhbnkgc29vbmVyIHRoYW4gdGhlIHBvbGxpbmcgbWV0aG9kIGJ5IHRoZSBncm91cCBt
ZW1iZXJzLiBBbHNvIOKAnHBvbGxpbmfigJ0gY2FuIGNhdXNlIGFkZGl0aW9uYWwgdW5uZWNlc3Nh
cnkgdHJhZmZpYy4gU28gaXMgaXMgYmV0dGVyIGZvciBhbnkgdXBkYXRlIG9uIHRoZSBncm91cCBw
b2xpY3kgb3IgcmVuZXdhbCBvZiBncm91cCBrZXlzIHRvIGJlIGRpc3RyaWJ1dGVkIGJ5IHRoZSBH
Q0tTIHVzaW5nIGEgUFVTSCBtZXNzYWdlLiBUaGUgQUNLLW1lc3NhZ2UgaXMgdXNlZCB0byBvZmZl
ciBhIGZlZWRiYWNrIG1lY2hhbmlzbSB0byBhIHBvbGljeSB1cGRhdGUgZm9yIHRoZSBQVVNIIGV4
Y2hhbmdlLg0KDQoqLy8qDQoNCiogIkZvciBleGFtcGxlLCBhIEdDS1MgcG9saWN5IGNhbiB1c2Ug
dGhlIGFja25vd2xlZGdlbWVudHMgdG8gZGV0ZXJtaW5lIFsuLi5dDQp3aGljaCBtZW1iZXJzIG1h
eSBubyBsb25nZXIgYmUgbWVtYmVycyBvZiB0aGUgZ3JvdXAuIiBUaGlzIHNlbnRlbmNlIGlzIHZl
cnkNCmNvbmZ1c2luZzogd2hlbiBhcmUgbWVtYmVycyBub3QgbWVtYmVycz8NCldl4oCZdmUgcmV3
b3JkZWQgdGhpcyB0ZXh0LiBJdOKAmXMgdHJ5aW5nIHRvIGNvbnZleSB0aGF0IGEgbWlzc2luZyBB
Q0sgbWVzc2FnZSAob3IgYSBjZXJ0YWluIG51bWJlciBvZiBpdCkgY2FuIGJlIHVzZWQgdG8gaWRl
bnRpZnkgdGhhdCBhIGdyb3VwIG1lbWJlciBpcyBubyBsb25nZXIgcmVjZWl2aW5nIGdyb3VwIHRy
YWZmaWMsIGFuZCBpcyBub3cgbWF5IGJlIGNvbnNpZGVyZWQgYW4gZXgtZ3JvdXAgbWVtYmVyLiBG
b3IgZXhhbXBsZSwgaXQgY291bGQgYmUgYSBtdWx0aWNhc3QgcmVjZWl2ZXIgdGhhdCBpcyBubyBs
b25nZXIgaW50ZXJlc3RlZCBpbiBiZWluZyBhIHJlY2VpdmVyIGZvciB0aGUgZ3JvdXAuIEJ1dCBp
dCBjb3VsZCBhbHNvIGJlIHRoYXQgYSBuZXR3b3JrIGV2ZW50IGhhcyBjYXVzZWQgaXQgdG8gYmUg
dW5hdmFpbGFibGUgZm9yIGEgc3VmZmljaWVudCBsZW5ndGggb2YgdGltZSBzdWNoIHRoYXQgaXQg
ZG9lc27igJl0IGhhdmUgY3VycmVudCBrZXlpbmcgbWF0ZXJpYWwgYW5kIHRoZXJlZm9yZSBjYW7i
gJl0IGJlIGNvbnNpZGVyZWQgYSBjdXJyZW50IGdyb3VwIG1lbWJlci4gVGhlcmUgaXMgbm8gcmVs
aWFibGUg4oCcSeKAmW0gbGVhdmluZyB0aGUgZ3JvdXDigJ0gbWVzc2FnZSBmbG93LCBhbmQgb2Yg
Y291cnNlIGluIG15IHNlY29uZCBleGFtcGxlIG5vIHN1Y2ggbWVzc2FnZXMgd291bGQgaGF2ZSBi
ZWVuIGludGVuZGVkIGJ5IHRoZSBncm91cCBtZW1iZXIuDQoqIFRoZSBuZXcgcHJvdG9jb2wgY2Fw
YWJpbGl0eSBpcyBkZWZpbmVkIGFzIG9wdGlvbmFsLCBidXQgcmVhbGx5IGlzbid0LiAiQSBHTQ0K
cmVjZWl2aW5nIHRoZSBLRUtfQUNLX1JFUVVFU1RFRCBhdHRyaWJ1dGUgY2FuIGNob29zZSB0byBp
Z25vcmUgaXQsIHRodXMNCmFwcGVhcmluZyBhcyBpZiBpdCBkb2VzIG5vdCBzdXBwb3J0IHRoZSBL
RUtfQUNLX1JFUVVFU1RFRCBhdHRyaWJ1dGUuIEhvd2V2ZXIsDQpHQ0tTIHBvbGljeSBtYXkgY29u
c2lkZXIgYSBub24tcmVzcG9uc2l2ZSBHTSB0byBubyBsb25nZXIgZGVzaXJlIHRvIGJlIGEgbWVt
YmVyDQpvZiB0aGUgZ3JvdXAuIiBTbyBpZiB5b3Ugd2FudCB0byBwbGF5IHRoZSBnYW1lLCB5b3Ug
TVVTVCBzdXBwb3J0IHRoZSBuZXcNCmF0dHJpYnV0ZS4NClBvaW50IHRha2VuLiBXZeKAmXZlIGNo
YW5nZWQgdGhlIHRleHQgdG8gcmVmbGVjdCB0aGlzLg0KKiBJJ20gcHV6emxlZCBhdCB0aGUgb3Zl
cmFsbCBwcm90b2NvbC4gQmVpbmcgYWJsZSB0byBzZW5kIEFDS3MgaXMgYSBHTSBzb2Z0d2FyZQ0K
Y2FwYWJpbGl0eS4gV2h5IG5vdCBoYXZlIHRoZSBHTSBhbm5vdW5jZSB0aGlzIGNhcGFiaWxpdHkg
d2hlbiBpdCBpbml0aWFsbHkNCnJlZ2lzdGVycyB0byB0aGUgR0NLUz8gVGhlbiB0aGUgR0NLUyB3
b3VsZCBrbm93IHdoYXQgdG8gZXhwZWN0LCB3aGVyZWFzIHdpdGgNCnRoZSBjdXJyZW50IHByb3Rv
Y29sIGl0IGlzIGxlZnQgd2FpdGluZyBmb3IgYW4gQUNLIHRoYXQgbWF5IG5ldmVyIGNvbWUsIGVp
dGhlcg0KYmVjYXVzZSB0aGUgR00gaXMgZGVhZCBvciBiZWNhdXNlIGl0IGp1c3QgZG9lc24ndCBm
ZWVsIGxpa2UgcmVzcG9uZGluZy4gQWRkIHRoZQ0KbG9uZyB3YWl0cyAoaml0dGVyIG9mICJhIGZl
dyBzZWNvbmRzIiBhbmQgcG90ZW50aWFsIHJldHJpZXMpLCBhbmQgdGhpcyBsb29rcw0KbGlrZSBh
IGZhciBmcm9tIG9wdGltYWwgbWFuYWdlbWVudCBleHBlcmllbmNlLg0KSW5kZWVkIGEgR00gY291
bGQgYW5ub3VuY2UgaXRzIGNhcGFiaWxpdHksIGJ1dCB3aGV0aGVyIG9yIG5vdCBBQ0tzIGFyZSBk
ZXNpcmVkIGlzIGEgY29tcG9uZW50IG9mIHRoZSBncm91cCBwb2xpY3kuIEluIHRoZSBjb250ZXh0
IG9mIEdET0kgdGhlIEdDS1MgaXMgdGhlIGVudGl0eSB0aGF0IGRlZmluZXMgdGhlIGdyb3VwIHBv
bGljeS4gVGhlcmUgY2FuIGJlIGdyb3VwcyB3aGVyZSB0aGUgQUNLIGlzIHVzZWQsIHdoZXJlYXMg
b3RoZXJzIGRvIG5vdC4gIFRoZSBjYXBhYmlsaXRpZXMgYW5ub3VuY2VtZW50IHlvdSBzdWdnZXN0
IGNvdWxkIGNlcnRhaW5seSBoZWxwIHRoZSBLUyB0byBrbm93IHdoZXRoZXIgb3Igbm90IHRvIGV4
cGVjdCB0aGUgQUNLIGZyb20gYSBwYXJ0aWN1bGFyIEdNLCBidXQgdGhlIGZvY3VzIG9mIHRoaXMg
SS1EIGlzIG9uIHRoZSB0aGUgZGVjbGFyYXRpb24gb2YgdGhlIHJlcXVlc3QgZm9yIEFDS3MgYnkg
dGhlIEdDS1MgYW5kIHRoZSBmb3JtYXQgb2YgdGhlIEFDSy4NCiogMi4yOiAiVGhpcyBpcyBhIHBy
aXZhdGUga2V5IiAtIHRvIGF2b2lkIGNvbmZ1c2lvbiwgSSBzdWdnZXN0OiAiVGhpcyBpcyBhDQpz
ZWNyZXQgc3ltbWV0cmljIGtleSIgKGlmIHRoaXMgaXMgaW5kZWVkIHRoZSBjYXNlKS4gT2J2aW91
c2x5IHVzaW5nIHRoZSBzYW1lDQprZXkgZm9yIGVuY3J5cHRpb24gYW5kIGZvciBITUFDIGlzIG5v
dCBhIGJlc3QgcHJhY3RpY2UuDQpXZeKAmXZlIG1hZGUgdGhpcyBjaGFuZ2UuDQoqIFNlYy4gNTog
QUNLIG1lc3NhZ2VzIGNhbiBhbHNvIGJlIGR1cGxpY2F0ZWQgaW4gdGhlIG5ldHdvcmsuIEkgc3Vn
Z2VzdCB0byBhZGQNCmEgc2VudGVuY2UgZGVzY3JpYmluZyB3aGF0IHRoZSBHQ0tTIHNob3VsZCBk
byBpbiB0aGlzIGNhc2UuDQpUaGUgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMgKHNlY3Rpb24gNy4z
KSBkZXNjcmliZXMgYSBtZXRob2QgZm9yIHRoZSBHQ0tTIHRvIGRldGVjdCByZXBsYXlzLiBUaGlz
IGlzIGFyZ3VhYmx5IGJldHRlciBwbGFjZWQgaW4gdGhpcyBzZWN0aW9uLCBzbyB3ZeKAmXZlIG1v
dmVkIGl0IGhlcmUuLg0KKiBTZWMuIDY6IEkgYW0gY29uZnVzZWQgYWJvdXQgdGhlIG5vdGlvbiBv
ZiAiaml0dGVyIiBoZXJlLiBJZiB0aGUgUFVTSCBtZXNzYWdlcw0KYXJlIHNlbnQgYXMgbXVsdGlj
YXN0ICh0aGUgcmVjb21tZW5kZWQgYWx0ZXJuYXRpdmUgQUZBSUNUKSwgSSdtIG5vdCBzdXJlIGFi
b3V0DQp0aGUgYmVuZWZpdCBvZiB1c2luZyBtdWx0aWNhc3QsIGdpdmVuIHRoYXQgZWFjaCByZWNp
cGllbnQgcmVzcG9uZHMgd2l0aCBhDQp1bmljYXN0IEFDSy4gQW5kIGlmIHRoZSBQVVNIIGlzIHVu
aWNhc3QsIHRoZXJlIHNob3VsZCBiZSBubyByZWFzb24gZm9yIGEgaml0dGVyDQphcyB0aGUgc2Vu
ZGVyIGNhbiB0aHJvdHRsZSB0aGUgUFVTSCBtZXNzYWdlcyBhcyBuZWNlc3NhcnkuDQpUaGUgY29u
Y2VwdCBvZiDigJxqaXR0ZXLigJ0gaXMgbW9zdCB2YWx1YWJsZSBmb3IgcmVzcG9uc2VzIHRvIGEg
bXVsdGljYXN0IFBVU0ggbWVzc2FnZS4gVGhlIHVzZSBvZiBhIG11bHRpY2FzdCBQVVNIIG1lc3Nh
Z2UgbG93ZXIgcHJvY2Vzc2luZyBvbiB0aGUgR0NLUy4gU2luY2UgZWFjaCBHTSBjYW4gZSBnaXZl
biB0aGUgZXhhY3Qgc2FtZSBwb2xpY3ksIHRoZXJl4oCZcyBubyBjYWxsIHRvIHNlbmQgaXQgb3V0
IGFzIGEgdW5pY2FzdCBtZXNzYWdlLiBUaGUgaml0dGVyIGhlbHBzIHNwcmVhZCBvdXQgdGhlIHJl
cGxpZXMgYSBiaXQgdG8gYXZvaWQgaW51bmRhdGluZyB0aGUgR0NLUy4NCiogTW9yZW92ZXIsIGV2
ZXJ5dGhpbmcgd291bGQgYmUgbXVjaCBtb3JlIHByZWRpY3RhYmxlIGlmIHRoZSBHQ0tTIGNvdWxk
DQppbmRpY2F0ZSBpZiBhIGppdHRlciBpcyBleHBlY3RlZCBhbmQgaG93IG11Y2ggb2YgYSBqaXR0
ZXIgKGJhc2VkIG9uIHNpemUgb2YgdGhlDQpncm91cCwgbmV0d29yayB0aHJvdWdocHV0LCBhbmQg
cXVldWUgbGVuZ3RoKS4gU3BlY2lmaWNhbGx5LCB0aGlzIHdvdWxkIGFsbG93DQp0aGUgR0NLUyB0
byB0ZWxsIGhvdyBsb25nIGl0IHNob3VsZCB3YWl0IGZvciBhbiBBQ0suDQpUaGlzIHdvdWxkIGJl
IHNvbWV3aGF0IHVzZWZ1bCwgYnV0IGluIHByYWN0aWNlIG1pZ2h0IG5vdCBoZWxwIHRoZSBHQ0tT
IGFzIG11Y2ggYXMgaXQgc2VlbXMuIFRoZSBqaXR0ZXIgdmFsdWUgcHJvdmlkZWQgd291bGQgYWxz
byBiZSBkZXBlbmRlbnQgb24gc2V2ZXJhbCBuZXR3b3JrIHBhcmFtZXRlcnMgdGhhdCBhcmVu4oCZ
dCB1bmRlciB0aGUgY29udHJvbCBvZiB0aGUgR0NLUyBvciB0aGUgR00uIEV2ZW4gd2hlbiB0aGUg
R00gZG9lcyBub3QgYWRkIGFueSBqaXR0ZXIgdG8gdGhlIEFDSywgdGhlIHVuZGVybHlpbmcgbmV0
d29yayBtYXkgZGVsYXkgdGhlIFBVU0ggYW5kL29yIGZvciB0aGUgQUNLLiBBbmQgYXMgc3RhdGVk
IGluIFNlY3Rpb24gNiwgdGhlIEdDS1MgbWF5IGJlIGNvbmZpZ3VyZWQgd2l0aCBhZGRpdGlvbmFs
IHBvbGljeSBhY3Rpb25zIGxpa2UgcmV0cmFuc21pc3Npb25zIHRvIG92ZXJjb21lIGxvc3QgQUNL
cy4gQWx0b2dldGhlciB0byBhZGQgaml0dGVyIHRvIHRoZSBBQ0sgaXMgbm90IGEgbXVzdCwgaXQg
aXMgYSB3YXkgdG8gaGVscCB0aGUgR0NLUyBkZWFsIHdpdGggYSBodWdlIG51bWJlciBvZiBHTXMu
IEluIHByYWN0aWNlLCB3ZeKAmXZlIGZvdW5kIHRoYXQgaGF2aW5nIHRoZSBHTXMgY2hvb3NlIHRo
ZSBqaXR0ZXIgaGFzIHdvcmtlZCB3ZWxsLCBldmVuIHdoZW4gdGhlIEdNcyBhcmUgZGlmZmVyZW50
IGltcGxlbWVudGF0aW9ucy4NCiogQ3J5cHRvZ3JhcGhpYyBhZ2lsaXR5OiB0aGlzIGRvY3VtZW50
IHNwZWNpZmllcyBvbmx5IG9uZSBhbGdvcml0aG0gZm9yIHRoZQ0KSEFTSCB2YWx1ZSwgYW5kIHNh
eXMgdGhhdCBpZiBhIG5ldyBhbGdvcml0aG0gaXMgbmVlZGVkLCB0aGVyZSB3aWxsIGJlIGEgbmV3
DQpLRUtfQUNLX1JFUVVFU1RFRCBwYXlsb2FkIGRlZmluZWQuIEhvd2V2ZXIgdG8gbWFrZSBzdXJl
IHRoYXQgdGhpcyByZWFsbHkNCiJ3b3JrcyIsIHdlIG5lZWQgdG8gZGVmaW5lIHdoZXRoZXIgbXVs
dGlwbGUgc3VjaCBwYXlsb2FkcyBjYW4gYmUgc2VudA0Kc2ltdWx0YW5lb3VzbHkgKGlmIGUuZy4g
c29tZSBHTXMgc3RpbGwgc3VwcG9ydCB0aGUgb2xkIGFsZ29yaXRobSkgYW5kIHdoYXQncw0KdGhl
IGV4cGVjdGVkIGJlaGF2aW9yLiBJIHdvdWxkIHN1Z2dlc3QgdG8gZGVmaW5lIGFuIGFkZGl0aW9u
YWwgU0hBLTUxMiBwYXlsb2FkDQpqdXN0IHRvIG1ha2UgZm9yIGEgY29uY3JldGUgZXhhbXBsZS4N
ClRoaXMgaXMgYSBnb29kIHN1Z2dlc3Rpb24uIFdl4oCZdmUgYWRkZWQgU0hBLTUxMiB2ZXJzaW9u
cyBvZiB0aGUgZXhpc3RpbmcgS0VLX0FDS19SRVFVRVNURUQgdmFsdWVzLg0KU2VlIDxodHRwczov
L3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtd2Vpcy1nZG9pLXJla2V5LWFjay0wNj4NClRoYW5r
cywNCkJyaWFuDQotLQ0KQnJpYW4gV2Vpcw0KU2VjdXJpdHksIENTRywgQ2lzY28gU3lzdGVtcw0K
VGVsZXBob25lOiArMSA0MDggNTI2IDQ3OTYNCkVtYWlsOiBiZXdAY2lzY28uY29tPG1haWx0bzpi
ZXdAY2lzY28uY29tPiA8bWFpbHRvOmJld0BjaXNjby5jb20+DQoNCg0KVGhhbmtzLA0KWWFyb24N
Cg0KT24gMjQvMDgvMTcgMTk6NDgsIEJyaWFuIFdlaXMgKGJldykgd3JvdGU6DQpIaSBZYXJvbiwN
ClRoYW5rcyBmb3IgdGhlIHJldmlldy4gV2XigJl2ZSBhZGRlZCBzb21lIGNsYXJpZmljYXRpb24g
YmVsb3csIGFuZCBtYWRlIHNvbWUgY2hhbmdlcyBpbiAtMDYgdG8gYWRkcmVzcyB5b3VyIGNvbW1l
bnRzLiBQbGVhc2UgbGV0IHVzIGtub3cgaWYgd2UgZGlkIG5vdCBhZGRyZXNzIHRoZW0gc2F0aXNm
YWN0b3JpbHkuDQpPbiBBdWcgNSwgMjAxNywgYXQgODo0OSBBTSwgWWFyb24gU2hlZmZlciA8eWFy
b25mLmlldGZAZ21haWwuY29tPG1haWx0bzp5YXJvbmYuaWV0ZkBnbWFpbC5jb20+IDxtYWlsdG86
eWFyb25mLmlldGZAZ21haWwuY29tPj4gd3JvdGU6DQoNClJldmlld2VyOiBZYXJvbiBTaGVmZmVy
DQpSZXZpZXcgcmVzdWx0OiBIYXMgSXNzdWVzDQoNClN1bW1hcnk6IHRoaXMgcmV2aWV3ZXIgaXMg
bm90IGNsZWFyIGFib3V0IHRoZSB2YWx1ZSBvZiB0aGUgcHVzaC1hY2sgKGNvbXBhcmVkDQp0byBh
IHB1bGwpIGFuZCBhYm91dCB0aGUgc3RyYXRlZ3kgdGhhdCB3YXMgY2hvc2VuLg0KSW4gYSBncm91
cCBrZXkgbWFuYWdlbWVudCBzeXN0ZW0gZWl0aGVyIGEg4oCccHVsbOKAnSAodHJpZ2dlcmVkIGJ5
IGEgZ3JvdXAgbWVtYmVyKSBvciBhIOKAnHB1c2jigJ0gKGJ5IHRoZSBrZXkgc2VydmVyKSIgY291
bGQgYmUgdXNlZCB0byBwcm92aWRlIHVwZGF0ZXMgdG8gdGhlIGdyb3VwLiBIb3dldmVyLCBhIOKA
nHB1bGzigJ0gYnkgdGhlIGdyb3VwIG1lbWJlciBpbXBsaWVzIGEgcG9sbGluZyBtZXRob2QsIHdo
aWNoIGhhcyB0aGUgZGVmaWNpZW5jeSB0aGF0IHRoZSBrZXkgc2VydmVyIGNhbm5vdCBjYXVzZSBh
IHBvbGljeSByZXBsYWNlbWVudCBhbnkgc29vbmVyIHRoYW4gdGhlIHBvbGxpbmcgbWV0aG9kIGJ5
IHRoZSBncm91cCBtZW1iZXJzLiBBbHNvIOKAnHBvbGxpbmfigJ0gY2FuIGNhdXNlIGFkZGl0aW9u
YWwgdW5uZWNlc3NhcnkgdHJhZmZpYy4gU28gaXMgaXMgYmV0dGVyIGZvciBhbnkgdXBkYXRlIG9u
IHRoZSBncm91cCBwb2xpY3kgb3IgcmVuZXdhbCBvZiBncm91cCBrZXlzIHRvIGJlIGRpc3RyaWJ1
dGVkIGJ5IHRoZSBHQ0tTIHVzaW5nIGEgUFVTSCBtZXNzYWdlLiBUaGUgQUNLLW1lc3NhZ2UgaXMg
dXNlZCB0byBvZmZlciBhIGZlZWRiYWNrIG1lY2hhbmlzbSB0byBhIHBvbGljeSB1cGRhdGUgZm9y
IHRoZSBQVVNIIGV4Y2hhbmdlLg0KDQoqLy8qDQoNCiogIkZvciBleGFtcGxlLCBhIEdDS1MgcG9s
aWN5IGNhbiB1c2UgdGhlIGFja25vd2xlZGdlbWVudHMgdG8gZGV0ZXJtaW5lIFsuLi5dDQp3aGlj
aCBtZW1iZXJzIG1heSBubyBsb25nZXIgYmUgbWVtYmVycyBvZiB0aGUgZ3JvdXAuIiBUaGlzIHNl
bnRlbmNlIGlzIHZlcnkNCmNvbmZ1c2luZzogd2hlbiBhcmUgbWVtYmVycyBub3QgbWVtYmVycz8N
Cldl4oCZdmUgcmV3b3JkZWQgdGhpcyB0ZXh0LiBJdOKAmXMgdHJ5aW5nIHRvIGNvbnZleSB0aGF0
IGEgbWlzc2luZyBBQ0sgbWVzc2FnZSAob3IgYSBjZXJ0YWluIG51bWJlciBvZiBpdCkgY2FuIGJl
IHVzZWQgdG8gaWRlbnRpZnkgdGhhdCBhIGdyb3VwIG1lbWJlciBpcyBubyBsb25nZXIgcmVjZWl2
aW5nIGdyb3VwIHRyYWZmaWMsIGFuZCBpcyBub3cgbWF5IGJlIGNvbnNpZGVyZWQgYW4gZXgtZ3Jv
dXAgbWVtYmVyLiBGb3IgZXhhbXBsZSwgaXQgY291bGQgYmUgYSBtdWx0aWNhc3QgcmVjZWl2ZXIg
dGhhdCBpcyBubyBsb25nZXIgaW50ZXJlc3RlZCBpbiBiZWluZyBhIHJlY2VpdmVyIGZvciB0aGUg
Z3JvdXAuIEJ1dCBpdCBjb3VsZCBhbHNvIGJlIHRoYXQgYSBuZXR3b3JrIGV2ZW50IGhhcyBjYXVz
ZWQgaXQgdG8gYmUgdW5hdmFpbGFibGUgZm9yIGEgc3VmZmljaWVudCBsZW5ndGggb2YgdGltZSBz
dWNoIHRoYXQgaXQgZG9lc27igJl0IGhhdmUgY3VycmVudCBrZXlpbmcgbWF0ZXJpYWwgYW5kIHRo
ZXJlZm9yZSBjYW7igJl0IGJlIGNvbnNpZGVyZWQgYSBjdXJyZW50IGdyb3VwIG1lbWJlci4gVGhl
cmUgaXMgbm8gcmVsaWFibGUg4oCcSeKAmW0gbGVhdmluZyB0aGUgZ3JvdXDigJ0gbWVzc2FnZSBm
bG93LCBhbmQgb2YgY291cnNlIGluIG15IHNlY29uZCBleGFtcGxlIG5vIHN1Y2ggbWVzc2FnZXMg
d291bGQgaGF2ZSBiZWVuIGludGVuZGVkIGJ5IHRoZSBncm91cCBtZW1iZXIuDQoqIFRoZSBuZXcg
cHJvdG9jb2wgY2FwYWJpbGl0eSBpcyBkZWZpbmVkIGFzIG9wdGlvbmFsLCBidXQgcmVhbGx5IGlz
bid0LiAiQSBHTQ0KcmVjZWl2aW5nIHRoZSBLRUtfQUNLX1JFUVVFU1RFRCBhdHRyaWJ1dGUgY2Fu
IGNob29zZSB0byBpZ25vcmUgaXQsIHRodXMNCmFwcGVhcmluZyBhcyBpZiBpdCBkb2VzIG5vdCBz
dXBwb3J0IHRoZSBLRUtfQUNLX1JFUVVFU1RFRCBhdHRyaWJ1dGUuIEhvd2V2ZXIsDQpHQ0tTIHBv
bGljeSBtYXkgY29uc2lkZXIgYSBub24tcmVzcG9uc2l2ZSBHTSB0byBubyBsb25nZXIgZGVzaXJl
IHRvIGJlIGEgbWVtYmVyDQpvZiB0aGUgZ3JvdXAuIiBTbyBpZiB5b3Ugd2FudCB0byBwbGF5IHRo
ZSBnYW1lLCB5b3UgTVVTVCBzdXBwb3J0IHRoZSBuZXcNCmF0dHJpYnV0ZS4NClBvaW50IHRha2Vu
LiBXZeKAmXZlIGNoYW5nZWQgdGhlIHRleHQgdG8gcmVmbGVjdCB0aGlzLg0KKiBJJ20gcHV6emxl
ZCBhdCB0aGUgb3ZlcmFsbCBwcm90b2NvbC4gQmVpbmcgYWJsZSB0byBzZW5kIEFDS3MgaXMgYSBH
TSBzb2Z0d2FyZQ0KY2FwYWJpbGl0eS4gV2h5IG5vdCBoYXZlIHRoZSBHTSBhbm5vdW5jZSB0aGlz
IGNhcGFiaWxpdHkgd2hlbiBpdCBpbml0aWFsbHkNCnJlZ2lzdGVycyB0byB0aGUgR0NLUz8gVGhl
biB0aGUgR0NLUyB3b3VsZCBrbm93IHdoYXQgdG8gZXhwZWN0LCB3aGVyZWFzIHdpdGgNCnRoZSBj
dXJyZW50IHByb3RvY29sIGl0IGlzIGxlZnQgd2FpdGluZyBmb3IgYW4gQUNLIHRoYXQgbWF5IG5l
dmVyIGNvbWUsIGVpdGhlcg0KYmVjYXVzZSB0aGUgR00gaXMgZGVhZCBvciBiZWNhdXNlIGl0IGp1
c3QgZG9lc24ndCBmZWVsIGxpa2UgcmVzcG9uZGluZy4gQWRkIHRoZQ0KbG9uZyB3YWl0cyAoaml0
dGVyIG9mICJhIGZldyBzZWNvbmRzIiBhbmQgcG90ZW50aWFsIHJldHJpZXMpLCBhbmQgdGhpcyBs
b29rcw0KbGlrZSBhIGZhciBmcm9tIG9wdGltYWwgbWFuYWdlbWVudCBleHBlcmllbmNlLg0KSW5k
ZWVkIGEgR00gY291bGQgYW5ub3VuY2UgaXRzIGNhcGFiaWxpdHksIGJ1dCB3aGV0aGVyIG9yIG5v
dCBBQ0tzIGFyZSBkZXNpcmVkIGlzIGEgY29tcG9uZW50IG9mIHRoZSBncm91cCBwb2xpY3kuIElu
IHRoZSBjb250ZXh0IG9mIEdET0kgdGhlIEdDS1MgaXMgdGhlIGVudGl0eSB0aGF0IGRlZmluZXMg
dGhlIGdyb3VwIHBvbGljeS4gVGhlcmUgY2FuIGJlIGdyb3VwcyB3aGVyZSB0aGUgQUNLIGlzIHVz
ZWQsIHdoZXJlYXMgb3RoZXJzIGRvIG5vdC4gIFRoZSBjYXBhYmlsaXRpZXMgYW5ub3VuY2VtZW50
IHlvdSBzdWdnZXN0IGNvdWxkIGNlcnRhaW5seSBoZWxwIHRoZSBLUyB0byBrbm93IHdoZXRoZXIg
b3Igbm90IHRvIGV4cGVjdCB0aGUgQUNLIGZyb20gYSBwYXJ0aWN1bGFyIEdNLCBidXQgdGhlIGZv
Y3VzIG9mIHRoaXMgSS1EIGlzIG9uIHRoZSB0aGUgZGVjbGFyYXRpb24gb2YgdGhlIHJlcXVlc3Qg
Zm9yIEFDS3MgYnkgdGhlIEdDS1MgYW5kIHRoZSBmb3JtYXQgb2YgdGhlIEFDSy4NCiogMi4yOiAi
VGhpcyBpcyBhIHByaXZhdGUga2V5IiAtIHRvIGF2b2lkIGNvbmZ1c2lvbiwgSSBzdWdnZXN0OiAi
VGhpcyBpcyBhDQpzZWNyZXQgc3ltbWV0cmljIGtleSIgKGlmIHRoaXMgaXMgaW5kZWVkIHRoZSBj
YXNlKS4gT2J2aW91c2x5IHVzaW5nIHRoZSBzYW1lDQprZXkgZm9yIGVuY3J5cHRpb24gYW5kIGZv
ciBITUFDIGlzIG5vdCBhIGJlc3QgcHJhY3RpY2UuDQpXZeKAmXZlIG1hZGUgdGhpcyBjaGFuZ2Uu
DQoqIFNlYy4gNTogQUNLIG1lc3NhZ2VzIGNhbiBhbHNvIGJlIGR1cGxpY2F0ZWQgaW4gdGhlIG5l
dHdvcmsuIEkgc3VnZ2VzdCB0byBhZGQNCmEgc2VudGVuY2UgZGVzY3JpYmluZyB3aGF0IHRoZSBH
Q0tTIHNob3VsZCBkbyBpbiB0aGlzIGNhc2UuDQpUaGUgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMg
KHNlY3Rpb24gNy4zKSBkZXNjcmliZXMgYSBtZXRob2QgZm9yIHRoZSBHQ0tTIHRvIGRldGVjdCBy
ZXBsYXlzLiBUaGlzIGlzIGFyZ3VhYmx5IGJldHRlciBwbGFjZWQgaW4gdGhpcyBzZWN0aW9uLCBz
byB3ZeKAmXZlIG1vdmVkIGl0IGhlcmUuLg0KKiBTZWMuIDY6IEkgYW0gY29uZnVzZWQgYWJvdXQg
dGhlIG5vdGlvbiBvZiAiaml0dGVyIiBoZXJlLiBJZiB0aGUgUFVTSCBtZXNzYWdlcw0KYXJlIHNl
bnQgYXMgbXVsdGljYXN0ICh0aGUgcmVjb21tZW5kZWQgYWx0ZXJuYXRpdmUgQUZBSUNUKSwgSSdt
IG5vdCBzdXJlIGFib3V0DQp0aGUgYmVuZWZpdCBvZiB1c2luZyBtdWx0aWNhc3QsIGdpdmVuIHRo
YXQgZWFjaCByZWNpcGllbnQgcmVzcG9uZHMgd2l0aCBhDQp1bmljYXN0IEFDSy4gQW5kIGlmIHRo
ZSBQVVNIIGlzIHVuaWNhc3QsIHRoZXJlIHNob3VsZCBiZSBubyByZWFzb24gZm9yIGEgaml0dGVy
DQphcyB0aGUgc2VuZGVyIGNhbiB0aHJvdHRsZSB0aGUgUFVTSCBtZXNzYWdlcyBhcyBuZWNlc3Nh
cnkuDQpUaGUgY29uY2VwdCBvZiDigJxqaXR0ZXLigJ0gaXMgbW9zdCB2YWx1YWJsZSBmb3IgcmVz
cG9uc2VzIHRvIGEgbXVsdGljYXN0IFBVU0ggbWVzc2FnZS4gVGhlIHVzZSBvZiBhIG11bHRpY2Fz
dCBQVVNIIG1lc3NhZ2UgbG93ZXIgcHJvY2Vzc2luZyBvbiB0aGUgR0NLUy4gU2luY2UgZWFjaCBH
TSBjYW4gZSBnaXZlbiB0aGUgZXhhY3Qgc2FtZSBwb2xpY3ksIHRoZXJl4oCZcyBubyBjYWxsIHRv
IHNlbmQgaXQgb3V0IGFzIGEgdW5pY2FzdCBtZXNzYWdlLiBUaGUgaml0dGVyIGhlbHBzIHNwcmVh
ZCBvdXQgdGhlIHJlcGxpZXMgYSBiaXQgdG8gYXZvaWQgaW51bmRhdGluZyB0aGUgR0NLUy4NCiog
TW9yZW92ZXIsIGV2ZXJ5dGhpbmcgd291bGQgYmUgbXVjaCBtb3JlIHByZWRpY3RhYmxlIGlmIHRo
ZSBHQ0tTIGNvdWxkDQppbmRpY2F0ZSBpZiBhIGppdHRlciBpcyBleHBlY3RlZCBhbmQgaG93IG11
Y2ggb2YgYSBqaXR0ZXIgKGJhc2VkIG9uIHNpemUgb2YgdGhlDQpncm91cCwgbmV0d29yayB0aHJv
dWdocHV0LCBhbmQgcXVldWUgbGVuZ3RoKS4gU3BlY2lmaWNhbGx5LCB0aGlzIHdvdWxkIGFsbG93
DQp0aGUgR0NLUyB0byB0ZWxsIGhvdyBsb25nIGl0IHNob3VsZCB3YWl0IGZvciBhbiBBQ0suDQpU
aGlzIHdvdWxkIGJlIHNvbWV3aGF0IHVzZWZ1bCwgYnV0IGluIHByYWN0aWNlIG1pZ2h0IG5vdCBo
ZWxwIHRoZSBHQ0tTIGFzIG11Y2ggYXMgaXQgc2VlbXMuIFRoZSBqaXR0ZXIgdmFsdWUgcHJvdmlk
ZWQgd291bGQgYWxzbyBiZSBkZXBlbmRlbnQgb24gc2V2ZXJhbCBuZXR3b3JrIHBhcmFtZXRlcnMg
dGhhdCBhcmVu4oCZdCB1bmRlciB0aGUgY29udHJvbCBvZiB0aGUgR0NLUyBvciB0aGUgR00uIEV2
ZW4gd2hlbiB0aGUgR00gZG9lcyBub3QgYWRkIGFueSBqaXR0ZXIgdG8gdGhlIEFDSywgdGhlIHVu
ZGVybHlpbmcgbmV0d29yayBtYXkgZGVsYXkgdGhlIFBVU0ggYW5kL29yIGZvciB0aGUgQUNLLiBB
bmQgYXMgc3RhdGVkIGluIFNlY3Rpb24gNiwgdGhlIEdDS1MgbWF5IGJlIGNvbmZpZ3VyZWQgd2l0
aCBhZGRpdGlvbmFsIHBvbGljeSBhY3Rpb25zIGxpa2UgcmV0cmFuc21pc3Npb25zIHRvIG92ZXJj
b21lIGxvc3QgQUNLcy4gQWx0b2dldGhlciB0byBhZGQgaml0dGVyIHRvIHRoZSBBQ0sgaXMgbm90
IGEgbXVzdCwgaXQgaXMgYSB3YXkgdG8gaGVscCB0aGUgR0NLUyBkZWFsIHdpdGggYSBodWdlIG51
bWJlciBvZiBHTXMuIEluIHByYWN0aWNlLCB3ZeKAmXZlIGZvdW5kIHRoYXQgaGF2aW5nIHRoZSBH
TXMgY2hvb3NlIHRoZSBqaXR0ZXIgaGFzIHdvcmtlZCB3ZWxsLCBldmVuIHdoZW4gdGhlIEdNcyBh
cmUgZGlmZmVyZW50IGltcGxlbWVudGF0aW9ucy4NCiogQ3J5cHRvZ3JhcGhpYyBhZ2lsaXR5OiB0
aGlzIGRvY3VtZW50IHNwZWNpZmllcyBvbmx5IG9uZSBhbGdvcml0aG0gZm9yIHRoZQ0KSEFTSCB2
YWx1ZSwgYW5kIHNheXMgdGhhdCBpZiBhIG5ldyBhbGdvcml0aG0gaXMgbmVlZGVkLCB0aGVyZSB3
aWxsIGJlIGEgbmV3DQpLRUtfQUNLX1JFUVVFU1RFRCBwYXlsb2FkIGRlZmluZWQuIEhvd2V2ZXIg
dG8gbWFrZSBzdXJlIHRoYXQgdGhpcyByZWFsbHkNCiJ3b3JrcyIsIHdlIG5lZWQgdG8gZGVmaW5l
IHdoZXRoZXIgbXVsdGlwbGUgc3VjaCBwYXlsb2FkcyBjYW4gYmUgc2VudA0Kc2ltdWx0YW5lb3Vz
bHkgKGlmIGUuZy4gc29tZSBHTXMgc3RpbGwgc3VwcG9ydCB0aGUgb2xkIGFsZ29yaXRobSkgYW5k
IHdoYXQncw0KdGhlIGV4cGVjdGVkIGJlaGF2aW9yLiBJIHdvdWxkIHN1Z2dlc3QgdG8gZGVmaW5l
IGFuIGFkZGl0aW9uYWwgU0hBLTUxMiBwYXlsb2FkDQpqdXN0IHRvIG1ha2UgZm9yIGEgY29uY3Jl
dGUgZXhhbXBsZS4NClRoaXMgaXMgYSBnb29kIHN1Z2dlc3Rpb24uIFdl4oCZdmUgYWRkZWQgU0hB
LTUxMiB2ZXJzaW9ucyBvZiB0aGUgZXhpc3RpbmcgS0VLX0FDS19SRVFVRVNURUQgdmFsdWVzLg0K
U2VlIDxodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtd2Vpcy1nZG9pLXJla2V5LWFj
ay0wNj4NClRoYW5rcywNCkJyaWFuDQotLQ0KQnJpYW4gV2Vpcw0KU2VjdXJpdHksIENTRywgQ2lz
Y28gU3lzdGVtcw0KVGVsZXBob25lOiArMSA0MDggNTI2IDQ3OTYNCkVtYWlsOiBiZXdAY2lzY28u
Y29tPG1haWx0bzpiZXdAY2lzY28uY29tPiA8bWFpbHRvOmJld0BjaXNjby5jb20+DQoNCi0tDQpC
cmlhbiBXZWlzDQpTZWN1cml0eSwgQ1NHLCBDaXNjbyBTeXN0ZW1zDQpUZWxlcGhvbmU6ICsxIDQw
OCA1MjYgNDc5Ng0KRW1haWw6IGJld0BjaXNjby5jb208bWFpbHRvOmJld0BjaXNjby5jb20+DQoN
Cg==

--_000_DE62366A03774DE19ED0A14E44A7EC05ciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <469B0527BDA78C41ADCAA8616269AAD2@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KSGkgWWFyb24sDQo8ZGl2IGNsYXNz
PSIiPjxiciBjbGFzcz0iIj4NCjxkaXY+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0i
Ij4NCjxkaXYgY2xhc3M9IiI+T24gQXVnIDI2LCAyMDE3LCBhdCA4OjM0IEFNLCBZYXJvbiBTaGVm
ZmVyICZsdDs8YSBocmVmPSJtYWlsdG86eWFyb25mLmlldGZAZ21haWwuY29tIiBjbGFzcz0iIj55
YXJvbmYuaWV0ZkBnbWFpbC5jb208L2E+Jmd0OyB3cm90ZTo8L2Rpdj4NCjxiciBjbGFzcz0iQXBw
bGUtaW50ZXJjaGFuZ2UtbmV3bGluZSI+DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj5I
aSBCcmlhbiw8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpUaGFuayB5b3UgZm9yIGFkZHJl
c3NpbmcgbW9zdCBvZiBteSBjb21tZW50cyBpbiB0aGUgbmV3IHZlcnNpb24sIGFuZCBmb3IgY2xh
cmlmeWluZyBwb2ludHMgd2hlcmUgSSB3YXMgb2ZmIHRoZSBtYXJrLjxiciBjbGFzcz0iIj4NCjxi
ciBjbGFzcz0iIj4NClRoZSBvbmx5IHJlbWFpbmluZyBjb21tZW50IHRoYXQncyBvbmx5IHBhcnRs
eSBhZGRyZXNzZWQgaXMgdGhlIG9uZSBvbiBjcnlwdG8gYWdpbGl0eS4gUXVvdGluZyBteXNlbGY6
PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0Kd2UgbmVlZCB0byBkZWZpbmUgd2hldGhlciBt
dWx0aXBsZSBzdWNoIHBheWxvYWRzIGNhbiBiZSBzZW50IHNpbXVsdGFuZW91c2x5IChpZiBlLmcu
IHNvbWUgR01zIHN0aWxsIHN1cHBvcnQgdGhlIG9sZCBhbGdvcml0aG0pIGFuZCB3aGF0J3MgdGhl
IGV4cGVjdGVkIGJlaGF2aW9yLjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCkluIG90aGVy
IHdvcmRzLCBzdXBwb3J0aW5nIG1vcmUgYWxnb3JpdGhtcyBpbiBub3Qgc3VmZmljaWVudC4gVGhl
IHF1ZXN0aW9uIGlzIHdoZXRoZXIgd2Ugc3VwcG9ydCBpbmNyZW1lbnRhbCBkZXBsb3ltZW50IG9m
IGEgbmV3IGFsZ29yaXRobSB0byBhIGxhcmdlIGdyb3VwIG9mIEdNcy48YnIgY2xhc3M9IiI+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4N
CjxkaXYgY2xhc3M9IiI+U29ycnksIHdlIG1pc3NlZCB0aGlzLiBJbmNyZW1lbnRhbCBkZXBsb3lt
ZW50IG9mIGFueSBuZXcgcG9saWN5IChhbGdvcml0aG0gb3Igb3RoZXJ3aXNlKSB3aXRoaW4gYSBn
cm91cCBpcyBub3Qgc28gc3RyYWlnaHRmb3J3YXJkLiBUaGVyZSBjYW4gcmVhbGx5IG9ubHkgYmUg
b25lIHNldCBvZiBwb2xpY3kgdXNlZCBieSB0aGUgZW50aXJlIGdyb3VwIGJlY2F1c2UgaWYgYSBz
ZW5kZXIgaGFzIGJlZW4gdXBkYXRlZCB0byBhIG5ldw0KIHNldCBvZiBwb2xpY3kgaXQgY2Fu4oCZ
dCByZWFsbHkgdXNlIGl0IHVudGlsIGFsbCByZWNlaXZlcnMgYXJlIHNpbWlsYXJseSB1cGdyYWRl
ZC4gVGhpcyBpcyBhIHBsYWNlIHdoZXJlIGEgY2FwYWJpbGl0aWVzIGV4Y2hhbmdlIGNhbiBiZSB1
c2VmdWwgZm9yIGEga2V5IHNlcnZlciB0byBkZWNsYXJlIGEgc3dpdGNoIHRvIGEgbmV3IGFsZ29y
aXRobSBhZnRlciBhbGwgbWVtYmVycyBjbGFpbSB0byBzdXBwb3J0IGl0LCBidXQgdGhhdCBtaWdo
dCBuZXZlcg0KIGhhcHBlbiBpbiBhIGxhcmdlIGdyb3VwLiBQcmFjdGljYWxseSBzcGVha2luZyBp
bmNyZW1lbnRhbCB1cGRhdGVzIGluIGEgbGFyZ2UgZ3JvdXAgbWlnaHQgcmVxdWlyZSB0d28gZGlm
ZmVyZW50IGdyb3VwcyB3aXRoIGEgYnJpZGdlIGJldHdlZW4sIG9yIHNvbWUgb3RoZXIgZGVwbG95
bWVudCBzdHJ1Y3R1cmUuIFNpbmNlIGl04oCZcyBhIGJyb2FkZXIgcHJvYmxlbSwgSeKAmW0gbm90
IHN1cmUgd2hhdCBlbHNlIHdlIGNhbiBkbyBpbiB0aGlzIGRvY3VtZW50DQogdG8gYWRkcmVzcyBp
bmNyZW1lbnRhbCBkZXBsb3ltZW50LjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+
DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+VGhhbmtzLDwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5Ccmlh
bjwvZGl2Pg0KPGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+
DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQpUaGFua3MsPGJy
IGNsYXNzPSIiPg0KPHNwYW4gY2xhc3M9IkFwcGxlLXRhYi1zcGFuIiBzdHlsZT0id2hpdGUtc3Bh
Y2U6IHByZTsiPjwvc3Bhbj5ZYXJvbjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCk9uIDI0
LzA4LzE3IDE5OjQ4LCBCcmlhbiBXZWlzIChiZXcpIHdyb3RlOjxiciBjbGFzcz0iIj4NCjxibG9j
a3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPkhpIFlhcm9uLDxiciBjbGFzcz0iIj4NClRoYW5r
cyBmb3IgdGhlIHJldmlldy4gV2XigJl2ZSBhZGRlZCBzb21lIGNsYXJpZmljYXRpb24gYmVsb3cs
IGFuZCBtYWRlIHNvbWUgY2hhbmdlcyBpbiAtMDYgdG8gYWRkcmVzcyB5b3VyIGNvbW1lbnRzLiBQ
bGVhc2UgbGV0IHVzIGtub3cgaWYgd2UgZGlkIG5vdCBhZGRyZXNzIHRoZW0gc2F0aXNmYWN0b3Jp
bHkuPGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+T24gQXVn
IDUsIDIwMTcsIGF0IDg6NDkgQU0sIFlhcm9uIFNoZWZmZXIgJmx0OzxhIGhyZWY9Im1haWx0bzp5
YXJvbmYuaWV0ZkBnbWFpbC5jb20iIGNsYXNzPSIiPnlhcm9uZi5pZXRmQGdtYWlsLmNvbTwvYT4m
bmJzcDsmbHQ7PGEgaHJlZj0ibWFpbHRvOnlhcm9uZi5pZXRmQGdtYWlsLmNvbSIgY2xhc3M9IiI+
bWFpbHRvOnlhcm9uZi5pZXRmQGdtYWlsLmNvbTwvYT4mZ3Q7Jmd0OyB3cm90ZTo8YnIgY2xhc3M9
IiI+DQo8YnIgY2xhc3M9IiI+DQpSZXZpZXdlcjogWWFyb24gU2hlZmZlcjxiciBjbGFzcz0iIj4N
ClJldmlldyByZXN1bHQ6IEhhcyBJc3N1ZXM8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpT
dW1tYXJ5OiB0aGlzIHJldmlld2VyIGlzIG5vdCBjbGVhciBhYm91dCB0aGUgdmFsdWUgb2YgdGhl
IHB1c2gtYWNrIChjb21wYXJlZDxiciBjbGFzcz0iIj4NCnRvIGEgcHVsbCkgYW5kIGFib3V0IHRo
ZSBzdHJhdGVneSB0aGF0IHdhcyBjaG9zZW4uPGJyIGNsYXNzPSIiPg0KPC9ibG9ja3F1b3RlPg0K
SW4gYSBncm91cCBrZXkgbWFuYWdlbWVudCBzeXN0ZW0gZWl0aGVyIGEg4oCccHVsbOKAnSAodHJp
Z2dlcmVkIGJ5IGEgZ3JvdXAgbWVtYmVyKSBvciBhIOKAnHB1c2jigJ0gKGJ5IHRoZSBrZXkgc2Vy
dmVyKSZxdW90OyBjb3VsZCBiZSB1c2VkIHRvIHByb3ZpZGUgdXBkYXRlcyB0byB0aGUgZ3JvdXAu
IEhvd2V2ZXIsIGEg4oCccHVsbOKAnSBieSB0aGUgZ3JvdXAgbWVtYmVyIGltcGxpZXMgYSBwb2xs
aW5nIG1ldGhvZCwgd2hpY2ggaGFzIHRoZSBkZWZpY2llbmN5IHRoYXQgdGhlDQoga2V5IHNlcnZl
ciBjYW5ub3QgY2F1c2UgYSBwb2xpY3kgcmVwbGFjZW1lbnQgYW55IHNvb25lciB0aGFuIHRoZSBw
b2xsaW5nIG1ldGhvZCBieSB0aGUgZ3JvdXAgbWVtYmVycy4gQWxzbyDigJxwb2xsaW5n4oCdIGNh
biBjYXVzZSBhZGRpdGlvbmFsIHVubmVjZXNzYXJ5IHRyYWZmaWMuIFNvIGlzIGlzIGJldHRlciBm
b3IgYW55IHVwZGF0ZSBvbiB0aGUgZ3JvdXAgcG9saWN5IG9yIHJlbmV3YWwgb2YgZ3JvdXAga2V5
cyB0byBiZSBkaXN0cmlidXRlZCBieQ0KIHRoZSBHQ0tTIHVzaW5nIGEgUFVTSCBtZXNzYWdlLiBU
aGUgQUNLLW1lc3NhZ2UgaXMgdXNlZCB0byBvZmZlciBhIGZlZWRiYWNrIG1lY2hhbmlzbSB0byBh
IHBvbGljeSB1cGRhdGUgZm9yIHRoZSBQVVNIIGV4Y2hhbmdlLjxiciBjbGFzcz0iIj4NCjxibG9j
a3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCiovLyo8YnIgY2xhc3M9
IiI+DQo8YnIgY2xhc3M9IiI+DQoqICZxdW90O0ZvciBleGFtcGxlLCBhIEdDS1MgcG9saWN5IGNh
biB1c2UgdGhlIGFja25vd2xlZGdlbWVudHMgdG8gZGV0ZXJtaW5lIFsuLi5dPGJyIGNsYXNzPSIi
Pg0Kd2hpY2ggbWVtYmVycyBtYXkgbm8gbG9uZ2VyIGJlIG1lbWJlcnMgb2YgdGhlIGdyb3VwLiZx
dW90OyBUaGlzIHNlbnRlbmNlIGlzIHZlcnk8YnIgY2xhc3M9IiI+DQpjb25mdXNpbmc6IHdoZW4g
YXJlIG1lbWJlcnMgbm90IG1lbWJlcnM/PGJyIGNsYXNzPSIiPg0KPC9ibG9ja3F1b3RlPg0KV2Xi
gJl2ZSByZXdvcmRlZCB0aGlzIHRleHQuIEl04oCZcyB0cnlpbmcgdG8gY29udmV5IHRoYXQgYSBt
aXNzaW5nIEFDSyBtZXNzYWdlIChvciBhIGNlcnRhaW4gbnVtYmVyIG9mIGl0KSBjYW4gYmUgdXNl
ZCB0byBpZGVudGlmeSB0aGF0IGEgZ3JvdXAgbWVtYmVyIGlzIG5vIGxvbmdlciByZWNlaXZpbmcg
Z3JvdXAgdHJhZmZpYywgYW5kIGlzIG5vdyBtYXkgYmUgY29uc2lkZXJlZCBhbiBleC1ncm91cCBt
ZW1iZXIuIEZvciBleGFtcGxlLCBpdCBjb3VsZCBiZQ0KIGEgbXVsdGljYXN0IHJlY2VpdmVyIHRo
YXQgaXMgbm8gbG9uZ2VyIGludGVyZXN0ZWQgaW4gYmVpbmcgYSByZWNlaXZlciBmb3IgdGhlIGdy
b3VwLiBCdXQgaXQgY291bGQgYWxzbyBiZSB0aGF0IGEgbmV0d29yayBldmVudCBoYXMgY2F1c2Vk
IGl0IHRvIGJlIHVuYXZhaWxhYmxlIGZvciBhIHN1ZmZpY2llbnQgbGVuZ3RoIG9mIHRpbWUgc3Vj
aCB0aGF0IGl0IGRvZXNu4oCZdCBoYXZlIGN1cnJlbnQga2V5aW5nIG1hdGVyaWFsIGFuZCB0aGVy
ZWZvcmUgY2Fu4oCZdA0KIGJlIGNvbnNpZGVyZWQgYSBjdXJyZW50IGdyb3VwIG1lbWJlci4gVGhl
cmUgaXMgbm8gcmVsaWFibGUg4oCcSeKAmW0gbGVhdmluZyB0aGUgZ3JvdXDigJ0gbWVzc2FnZSBm
bG93LCBhbmQgb2YgY291cnNlIGluIG15IHNlY29uZCBleGFtcGxlIG5vIHN1Y2ggbWVzc2FnZXMg
d291bGQgaGF2ZSBiZWVuIGludGVuZGVkIGJ5IHRoZSBncm91cCBtZW1iZXIuPGJyIGNsYXNzPSIi
Pg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+KiBUaGUgbmV3IHByb3RvY29sIGNh
cGFiaWxpdHkgaXMgZGVmaW5lZCBhcyBvcHRpb25hbCwgYnV0IHJlYWxseSBpc24ndC4gJnF1b3Q7
QSBHTTxiciBjbGFzcz0iIj4NCnJlY2VpdmluZyB0aGUgS0VLX0FDS19SRVFVRVNURUQgYXR0cmli
dXRlIGNhbiBjaG9vc2UgdG8gaWdub3JlIGl0LCB0aHVzPGJyIGNsYXNzPSIiPg0KYXBwZWFyaW5n
IGFzIGlmIGl0IGRvZXMgbm90IHN1cHBvcnQgdGhlIEtFS19BQ0tfUkVRVUVTVEVEIGF0dHJpYnV0
ZS4gSG93ZXZlciw8YnIgY2xhc3M9IiI+DQpHQ0tTIHBvbGljeSBtYXkgY29uc2lkZXIgYSBub24t
cmVzcG9uc2l2ZSBHTSB0byBubyBsb25nZXIgZGVzaXJlIHRvIGJlIGEgbWVtYmVyPGJyIGNsYXNz
PSIiPg0Kb2YgdGhlIGdyb3VwLiZxdW90OyBTbyBpZiB5b3Ugd2FudCB0byBwbGF5IHRoZSBnYW1l
LCB5b3UgTVVTVCBzdXBwb3J0IHRoZSBuZXc8YnIgY2xhc3M9IiI+DQphdHRyaWJ1dGUuPGJyIGNs
YXNzPSIiPg0KPC9ibG9ja3F1b3RlPg0KUG9pbnQgdGFrZW4uIFdl4oCZdmUgY2hhbmdlZCB0aGUg
dGV4dCB0byByZWZsZWN0IHRoaXMuPGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0
ZSIgY2xhc3M9IiI+KiBJJ20gcHV6emxlZCBhdCB0aGUgb3ZlcmFsbCBwcm90b2NvbC4gQmVpbmcg
YWJsZSB0byBzZW5kIEFDS3MgaXMgYSBHTSBzb2Z0d2FyZTxiciBjbGFzcz0iIj4NCmNhcGFiaWxp
dHkuIFdoeSBub3QgaGF2ZSB0aGUgR00gYW5ub3VuY2UgdGhpcyBjYXBhYmlsaXR5IHdoZW4gaXQg
aW5pdGlhbGx5PGJyIGNsYXNzPSIiPg0KcmVnaXN0ZXJzIHRvIHRoZSBHQ0tTPyBUaGVuIHRoZSBH
Q0tTIHdvdWxkIGtub3cgd2hhdCB0byBleHBlY3QsIHdoZXJlYXMgd2l0aDxiciBjbGFzcz0iIj4N
CnRoZSBjdXJyZW50IHByb3RvY29sIGl0IGlzIGxlZnQgd2FpdGluZyBmb3IgYW4gQUNLIHRoYXQg
bWF5IG5ldmVyIGNvbWUsIGVpdGhlcjxiciBjbGFzcz0iIj4NCmJlY2F1c2UgdGhlIEdNIGlzIGRl
YWQgb3IgYmVjYXVzZSBpdCBqdXN0IGRvZXNuJ3QgZmVlbCBsaWtlIHJlc3BvbmRpbmcuIEFkZCB0
aGU8YnIgY2xhc3M9IiI+DQpsb25nIHdhaXRzIChqaXR0ZXIgb2YgJnF1b3Q7YSBmZXcgc2Vjb25k
cyZxdW90OyBhbmQgcG90ZW50aWFsIHJldHJpZXMpLCBhbmQgdGhpcyBsb29rczxiciBjbGFzcz0i
Ij4NCmxpa2UgYSBmYXIgZnJvbSBvcHRpbWFsIG1hbmFnZW1lbnQgZXhwZXJpZW5jZS48YnIgY2xh
c3M9IiI+DQo8L2Jsb2NrcXVvdGU+DQpJbmRlZWQgYSBHTSBjb3VsZCBhbm5vdW5jZSBpdHMgY2Fw
YWJpbGl0eSwgYnV0IHdoZXRoZXIgb3Igbm90IEFDS3MgYXJlIGRlc2lyZWQgaXMgYSBjb21wb25l
bnQgb2YgdGhlIGdyb3VwIHBvbGljeS4gSW4gdGhlIGNvbnRleHQgb2YgR0RPSSB0aGUgR0NLUyBp
cyB0aGUgZW50aXR5IHRoYXQgZGVmaW5lcyB0aGUgZ3JvdXAgcG9saWN5LiBUaGVyZSBjYW4gYmUg
Z3JvdXBzIHdoZXJlIHRoZSBBQ0sgaXMgdXNlZCwgd2hlcmVhcyBvdGhlcnMgZG8gbm90Lg0KICZu
YnNwO1RoZSBjYXBhYmlsaXRpZXMgYW5ub3VuY2VtZW50IHlvdSBzdWdnZXN0IGNvdWxkIGNlcnRh
aW5seSBoZWxwIHRoZSBLUyB0byBrbm93IHdoZXRoZXIgb3Igbm90IHRvIGV4cGVjdCB0aGUgQUNL
IGZyb20gYSBwYXJ0aWN1bGFyIEdNLCBidXQgdGhlIGZvY3VzIG9mIHRoaXMgSS1EIGlzIG9uIHRo
ZSB0aGUgZGVjbGFyYXRpb24gb2YgdGhlIHJlcXVlc3QgZm9yIEFDS3MgYnkgdGhlIEdDS1MgYW5k
IHRoZSBmb3JtYXQgb2YgdGhlIEFDSy48YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJj
aXRlIiBjbGFzcz0iIj4qIDIuMjogJnF1b3Q7VGhpcyBpcyBhIHByaXZhdGUga2V5JnF1b3Q7IC0g
dG8gYXZvaWQgY29uZnVzaW9uLCBJIHN1Z2dlc3Q6ICZxdW90O1RoaXMgaXMgYTxiciBjbGFzcz0i
Ij4NCnNlY3JldCBzeW1tZXRyaWMga2V5JnF1b3Q7IChpZiB0aGlzIGlzIGluZGVlZCB0aGUgY2Fz
ZSkuIE9idmlvdXNseSB1c2luZyB0aGUgc2FtZTxiciBjbGFzcz0iIj4NCmtleSBmb3IgZW5jcnlw
dGlvbiBhbmQgZm9yIEhNQUMgaXMgbm90IGEgYmVzdCBwcmFjdGljZS48YnIgY2xhc3M9IiI+DQo8
L2Jsb2NrcXVvdGU+DQpXZeKAmXZlIG1hZGUgdGhpcyBjaGFuZ2UuPGJyIGNsYXNzPSIiPg0KPGJs
b2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+KiBTZWMuIDU6IEFDSyBtZXNzYWdlcyBjYW4g
YWxzbyBiZSBkdXBsaWNhdGVkIGluIHRoZSBuZXR3b3JrLiBJIHN1Z2dlc3QgdG8gYWRkPGJyIGNs
YXNzPSIiPg0KYSBzZW50ZW5jZSBkZXNjcmliaW5nIHdoYXQgdGhlIEdDS1Mgc2hvdWxkIGRvIGlu
IHRoaXMgY2FzZS48YnIgY2xhc3M9IiI+DQo8L2Jsb2NrcXVvdGU+DQpUaGUgU2VjdXJpdHkgQ29u
c2lkZXJhdGlvbnMgKHNlY3Rpb24gNy4zKSBkZXNjcmliZXMgYSBtZXRob2QgZm9yIHRoZSBHQ0tT
IHRvIGRldGVjdCByZXBsYXlzLiBUaGlzIGlzIGFyZ3VhYmx5IGJldHRlciBwbGFjZWQgaW4gdGhp
cyBzZWN0aW9uLCBzbyB3ZeKAmXZlIG1vdmVkIGl0IGhlcmUuLjxiciBjbGFzcz0iIj4NCjxibG9j
a3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPiogU2VjLiA2OiBJIGFtIGNvbmZ1c2VkIGFib3V0
IHRoZSBub3Rpb24gb2YgJnF1b3Q7aml0dGVyJnF1b3Q7IGhlcmUuIElmIHRoZSBQVVNIIG1lc3Nh
Z2VzPGJyIGNsYXNzPSIiPg0KYXJlIHNlbnQgYXMgbXVsdGljYXN0ICh0aGUgcmVjb21tZW5kZWQg
YWx0ZXJuYXRpdmUgQUZBSUNUKSwgSSdtIG5vdCBzdXJlIGFib3V0PGJyIGNsYXNzPSIiPg0KdGhl
IGJlbmVmaXQgb2YgdXNpbmcgbXVsdGljYXN0LCBnaXZlbiB0aGF0IGVhY2ggcmVjaXBpZW50IHJl
c3BvbmRzIHdpdGggYTxiciBjbGFzcz0iIj4NCnVuaWNhc3QgQUNLLiBBbmQgaWYgdGhlIFBVU0gg
aXMgdW5pY2FzdCwgdGhlcmUgc2hvdWxkIGJlIG5vIHJlYXNvbiBmb3IgYSBqaXR0ZXI8YnIgY2xh
c3M9IiI+DQphcyB0aGUgc2VuZGVyIGNhbiB0aHJvdHRsZSB0aGUgUFVTSCBtZXNzYWdlcyBhcyBu
ZWNlc3NhcnkuPGJyIGNsYXNzPSIiPg0KPC9ibG9ja3F1b3RlPg0KVGhlIGNvbmNlcHQgb2Yg4oCc
aml0dGVy4oCdIGlzIG1vc3QgdmFsdWFibGUgZm9yIHJlc3BvbnNlcyB0byBhIG11bHRpY2FzdCBQ
VVNIIG1lc3NhZ2UuIFRoZSB1c2Ugb2YgYSBtdWx0aWNhc3QgUFVTSCBtZXNzYWdlIGxvd2VyIHBy
b2Nlc3Npbmcgb24gdGhlIEdDS1MuIFNpbmNlIGVhY2ggR00gY2FuIGUgZ2l2ZW4gdGhlIGV4YWN0
IHNhbWUgcG9saWN5LCB0aGVyZeKAmXMgbm8gY2FsbCB0byBzZW5kIGl0IG91dCBhcyBhIHVuaWNh
c3QgbWVzc2FnZS4gVGhlIGppdHRlcg0KIGhlbHBzIHNwcmVhZCBvdXQgdGhlIHJlcGxpZXMgYSBi
aXQgdG8gYXZvaWQgaW51bmRhdGluZyB0aGUgR0NLUy48YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90
ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj4qIE1vcmVvdmVyLCBldmVyeXRoaW5nIHdvdWxkIGJlIG11
Y2ggbW9yZSBwcmVkaWN0YWJsZSBpZiB0aGUgR0NLUyBjb3VsZDxiciBjbGFzcz0iIj4NCmluZGlj
YXRlIGlmIGEgaml0dGVyIGlzIGV4cGVjdGVkIGFuZCBob3cgbXVjaCBvZiBhIGppdHRlciAoYmFz
ZWQgb24gc2l6ZSBvZiB0aGU8YnIgY2xhc3M9IiI+DQpncm91cCwgbmV0d29yayB0aHJvdWdocHV0
LCBhbmQgcXVldWUgbGVuZ3RoKS4gU3BlY2lmaWNhbGx5LCB0aGlzIHdvdWxkIGFsbG93PGJyIGNs
YXNzPSIiPg0KdGhlIEdDS1MgdG8gdGVsbCBob3cgbG9uZyBpdCBzaG91bGQgd2FpdCBmb3IgYW4g
QUNLLjxiciBjbGFzcz0iIj4NCjwvYmxvY2txdW90ZT4NClRoaXMgd291bGQgYmUgc29tZXdoYXQg
dXNlZnVsLCBidXQgaW4gcHJhY3RpY2UgbWlnaHQgbm90IGhlbHAgdGhlIEdDS1MgYXMgbXVjaCBh
cyBpdCBzZWVtcy4gVGhlIGppdHRlciB2YWx1ZSBwcm92aWRlZCB3b3VsZCBhbHNvIGJlIGRlcGVu
ZGVudCBvbiBzZXZlcmFsIG5ldHdvcmsgcGFyYW1ldGVycyB0aGF0IGFyZW7igJl0IHVuZGVyIHRo
ZSBjb250cm9sIG9mIHRoZSBHQ0tTIG9yIHRoZSBHTS4gRXZlbiB3aGVuIHRoZSBHTSBkb2VzIG5v
dCBhZGQgYW55DQogaml0dGVyIHRvIHRoZSBBQ0ssIHRoZSB1bmRlcmx5aW5nIG5ldHdvcmsgbWF5
IGRlbGF5IHRoZSBQVVNIIGFuZC9vciBmb3IgdGhlIEFDSy4gQW5kIGFzIHN0YXRlZCBpbiBTZWN0
aW9uIDYsIHRoZSBHQ0tTIG1heSBiZSBjb25maWd1cmVkIHdpdGggYWRkaXRpb25hbCBwb2xpY3kg
YWN0aW9ucyBsaWtlIHJldHJhbnNtaXNzaW9ucyB0byBvdmVyY29tZSBsb3N0IEFDS3MuIEFsdG9n
ZXRoZXIgdG8gYWRkIGppdHRlciB0byB0aGUgQUNLIGlzIG5vdCBhDQogbXVzdCwgaXQgaXMgYSB3
YXkgdG8gaGVscCB0aGUgR0NLUyBkZWFsIHdpdGggYSBodWdlIG51bWJlciBvZiBHTXMuIEluIHBy
YWN0aWNlLCB3ZeKAmXZlIGZvdW5kIHRoYXQgaGF2aW5nIHRoZSBHTXMgY2hvb3NlIHRoZSBqaXR0
ZXIgaGFzIHdvcmtlZCB3ZWxsLCBldmVuIHdoZW4gdGhlIEdNcyBhcmUgZGlmZmVyZW50IGltcGxl
bWVudGF0aW9ucy48YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0i
Ij4qIENyeXB0b2dyYXBoaWMgYWdpbGl0eTogdGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgb25seSBv
bmUgYWxnb3JpdGhtIGZvciB0aGU8YnIgY2xhc3M9IiI+DQpIQVNIIHZhbHVlLCBhbmQgc2F5cyB0
aGF0IGlmIGEgbmV3IGFsZ29yaXRobSBpcyBuZWVkZWQsIHRoZXJlIHdpbGwgYmUgYSBuZXc8YnIg
Y2xhc3M9IiI+DQpLRUtfQUNLX1JFUVVFU1RFRCBwYXlsb2FkIGRlZmluZWQuIEhvd2V2ZXIgdG8g
bWFrZSBzdXJlIHRoYXQgdGhpcyByZWFsbHk8YnIgY2xhc3M9IiI+DQomcXVvdDt3b3JrcyZxdW90
Oywgd2UgbmVlZCB0byBkZWZpbmUgd2hldGhlciBtdWx0aXBsZSBzdWNoIHBheWxvYWRzIGNhbiBi
ZSBzZW50PGJyIGNsYXNzPSIiPg0Kc2ltdWx0YW5lb3VzbHkgKGlmIGUuZy4gc29tZSBHTXMgc3Rp
bGwgc3VwcG9ydCB0aGUgb2xkIGFsZ29yaXRobSkgYW5kIHdoYXQnczxiciBjbGFzcz0iIj4NCnRo
ZSBleHBlY3RlZCBiZWhhdmlvci4gSSB3b3VsZCBzdWdnZXN0IHRvIGRlZmluZSBhbiBhZGRpdGlv
bmFsIFNIQS01MTIgcGF5bG9hZDxiciBjbGFzcz0iIj4NCmp1c3QgdG8gbWFrZSBmb3IgYSBjb25j
cmV0ZSBleGFtcGxlLjxiciBjbGFzcz0iIj4NCjwvYmxvY2txdW90ZT4NClRoaXMgaXMgYSBnb29k
IHN1Z2dlc3Rpb24uIFdl4oCZdmUgYWRkZWQgU0hBLTUxMiB2ZXJzaW9ucyBvZiB0aGUgZXhpc3Rp
bmcgS0VLX0FDS19SRVFVRVNURUQgdmFsdWVzLjxiciBjbGFzcz0iIj4NClNlZSAmbHQ7PGEgaHJl
Zj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXdlaXMtZ2RvaS1yZWtleS1hY2st
MDYiIGNsYXNzPSIiPmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC13ZWlzLWdkb2kt
cmVrZXktYWNrLTA2PC9hPiZndDs8YnIgY2xhc3M9IiI+DQpUaGFua3MsPGJyIGNsYXNzPSIiPg0K
QnJpYW48YnIgY2xhc3M9IiI+DQotLSZuYnNwOzxiciBjbGFzcz0iIj4NCkJyaWFuIFdlaXM8YnIg
Y2xhc3M9IiI+DQpTZWN1cml0eSwgQ1NHLCBDaXNjbyBTeXN0ZW1zPGJyIGNsYXNzPSIiPg0KVGVs
ZXBob25lOiAmIzQzOzEgNDA4IDUyNiA0Nzk2PGJyIGNsYXNzPSIiPg0KRW1haWw6Jm5ic3A7PGEg
aHJlZj0ibWFpbHRvOmJld0BjaXNjby5jb20iIGNsYXNzPSIiPmJld0BjaXNjby5jb208L2E+Jm5i
c3A7Jmx0OzxhIGhyZWY9Im1haWx0bzpiZXdAY2lzY28uY29tIiBjbGFzcz0iIj5tYWlsdG86YmV3
QGNpc2NvLmNvbTwvYT4mZ3Q7PGJyIGNsYXNzPSIiPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8
L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXYgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPg0KPGRp
diBjbGFzcz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPjxiciBjbGFzcz0i
Ij4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHR5
cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNs
YXNzPSIiPg0KVGhhbmtzLDxiciBjbGFzcz0iIj4NCjxzcGFuIGNsYXNzPSJBcHBsZS10YWItc3Bh
biIgc3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPllhcm9uPGJyIGNsYXNzPSIiPg0KPGJy
IGNsYXNzPSIiPg0KT24gMjQvMDgvMTcgMTk6NDgsIEJyaWFuIFdlaXMgKGJldykgd3JvdGU6PGJy
IGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+SGkgWWFyb24sPGJy
IGNsYXNzPSIiPg0KVGhhbmtzIGZvciB0aGUgcmV2aWV3LiBXZeKAmXZlIGFkZGVkIHNvbWUgY2xh
cmlmaWNhdGlvbiBiZWxvdywgYW5kIG1hZGUgc29tZSBjaGFuZ2VzIGluIC0wNiB0byBhZGRyZXNz
IHlvdXIgY29tbWVudHMuIFBsZWFzZSBsZXQgdXMga25vdyBpZiB3ZSBkaWQgbm90IGFkZHJlc3Mg
dGhlbSBzYXRpc2ZhY3RvcmlseS48YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRl
IiBjbGFzcz0iIj5PbiBBdWcgNSwgMjAxNywgYXQgODo0OSBBTSwgWWFyb24gU2hlZmZlciAmbHQ7
PGEgaHJlZj0ibWFpbHRvOnlhcm9uZi5pZXRmQGdtYWlsLmNvbSIgY2xhc3M9IiI+eWFyb25mLmll
dGZAZ21haWwuY29tPC9hPiAmbHQ7PGEgaHJlZj0ibWFpbHRvOnlhcm9uZi5pZXRmQGdtYWlsLmNv
bSIgY2xhc3M9IiI+bWFpbHRvOnlhcm9uZi5pZXRmQGdtYWlsLmNvbTwvYT4mZ3Q7Jmd0OyB3cm90
ZTo8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpSZXZpZXdlcjogWWFyb24gU2hlZmZlcjxi
ciBjbGFzcz0iIj4NClJldmlldyByZXN1bHQ6IEhhcyBJc3N1ZXM8YnIgY2xhc3M9IiI+DQo8YnIg
Y2xhc3M9IiI+DQpTdW1tYXJ5OiB0aGlzIHJldmlld2VyIGlzIG5vdCBjbGVhciBhYm91dCB0aGUg
dmFsdWUgb2YgdGhlIHB1c2gtYWNrIChjb21wYXJlZDxiciBjbGFzcz0iIj4NCnRvIGEgcHVsbCkg
YW5kIGFib3V0IHRoZSBzdHJhdGVneSB0aGF0IHdhcyBjaG9zZW4uPGJyIGNsYXNzPSIiPg0KPC9i
bG9ja3F1b3RlPg0KSW4gYSBncm91cCBrZXkgbWFuYWdlbWVudCBzeXN0ZW0gZWl0aGVyIGEg4oCc
cHVsbOKAnSAodHJpZ2dlcmVkIGJ5IGEgZ3JvdXAgbWVtYmVyKSBvciBhIOKAnHB1c2jigJ0gKGJ5
IHRoZSBrZXkgc2VydmVyKSZxdW90OyBjb3VsZCBiZSB1c2VkIHRvIHByb3ZpZGUgdXBkYXRlcyB0
byB0aGUgZ3JvdXAuIEhvd2V2ZXIsIGEg4oCccHVsbOKAnSBieSB0aGUgZ3JvdXAgbWVtYmVyIGlt
cGxpZXMgYSBwb2xsaW5nIG1ldGhvZCwgd2hpY2ggaGFzIHRoZSBkZWZpY2llbmN5IHRoYXQgdGhl
DQoga2V5IHNlcnZlciBjYW5ub3QgY2F1c2UgYSBwb2xpY3kgcmVwbGFjZW1lbnQgYW55IHNvb25l
ciB0aGFuIHRoZSBwb2xsaW5nIG1ldGhvZCBieSB0aGUgZ3JvdXAgbWVtYmVycy4gQWxzbyDigJxw
b2xsaW5n4oCdIGNhbiBjYXVzZSBhZGRpdGlvbmFsIHVubmVjZXNzYXJ5IHRyYWZmaWMuIFNvIGlz
IGlzIGJldHRlciBmb3IgYW55IHVwZGF0ZSBvbiB0aGUgZ3JvdXAgcG9saWN5IG9yIHJlbmV3YWwg
b2YgZ3JvdXAga2V5cyB0byBiZSBkaXN0cmlidXRlZCBieQ0KIHRoZSBHQ0tTIHVzaW5nIGEgUFVT
SCBtZXNzYWdlLiBUaGUgQUNLLW1lc3NhZ2UgaXMgdXNlZCB0byBvZmZlciBhIGZlZWRiYWNrIG1l
Y2hhbmlzbSB0byBhIHBvbGljeSB1cGRhdGUgZm9yIHRoZSBQVVNIIGV4Y2hhbmdlLjxiciBjbGFz
cz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCiov
Lyo8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQoqICZxdW90O0ZvciBleGFtcGxlLCBhIEdD
S1MgcG9saWN5IGNhbiB1c2UgdGhlIGFja25vd2xlZGdlbWVudHMgdG8gZGV0ZXJtaW5lIFsuLi5d
PGJyIGNsYXNzPSIiPg0Kd2hpY2ggbWVtYmVycyBtYXkgbm8gbG9uZ2VyIGJlIG1lbWJlcnMgb2Yg
dGhlIGdyb3VwLiZxdW90OyBUaGlzIHNlbnRlbmNlIGlzIHZlcnk8YnIgY2xhc3M9IiI+DQpjb25m
dXNpbmc6IHdoZW4gYXJlIG1lbWJlcnMgbm90IG1lbWJlcnM/PGJyIGNsYXNzPSIiPg0KPC9ibG9j
a3F1b3RlPg0KV2XigJl2ZSByZXdvcmRlZCB0aGlzIHRleHQuIEl04oCZcyB0cnlpbmcgdG8gY29u
dmV5IHRoYXQgYSBtaXNzaW5nIEFDSyBtZXNzYWdlIChvciBhIGNlcnRhaW4gbnVtYmVyIG9mIGl0
KSBjYW4gYmUgdXNlZCB0byBpZGVudGlmeSB0aGF0IGEgZ3JvdXAgbWVtYmVyIGlzIG5vIGxvbmdl
ciByZWNlaXZpbmcgZ3JvdXAgdHJhZmZpYywgYW5kIGlzIG5vdyBtYXkgYmUgY29uc2lkZXJlZCBh
biBleC1ncm91cCBtZW1iZXIuIEZvciBleGFtcGxlLCBpdCBjb3VsZCBiZQ0KIGEgbXVsdGljYXN0
IHJlY2VpdmVyIHRoYXQgaXMgbm8gbG9uZ2VyIGludGVyZXN0ZWQgaW4gYmVpbmcgYSByZWNlaXZl
ciBmb3IgdGhlIGdyb3VwLiBCdXQgaXQgY291bGQgYWxzbyBiZSB0aGF0IGEgbmV0d29yayBldmVu
dCBoYXMgY2F1c2VkIGl0IHRvIGJlIHVuYXZhaWxhYmxlIGZvciBhIHN1ZmZpY2llbnQgbGVuZ3Ro
IG9mIHRpbWUgc3VjaCB0aGF0IGl0IGRvZXNu4oCZdCBoYXZlIGN1cnJlbnQga2V5aW5nIG1hdGVy
aWFsIGFuZCB0aGVyZWZvcmUgY2Fu4oCZdA0KIGJlIGNvbnNpZGVyZWQgYSBjdXJyZW50IGdyb3Vw
IG1lbWJlci4gVGhlcmUgaXMgbm8gcmVsaWFibGUg4oCcSeKAmW0gbGVhdmluZyB0aGUgZ3JvdXDi
gJ0gbWVzc2FnZSBmbG93LCBhbmQgb2YgY291cnNlIGluIG15IHNlY29uZCBleGFtcGxlIG5vIHN1
Y2ggbWVzc2FnZXMgd291bGQgaGF2ZSBiZWVuIGludGVuZGVkIGJ5IHRoZSBncm91cCBtZW1iZXIu
PGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+KiBUaGUgbmV3
IHByb3RvY29sIGNhcGFiaWxpdHkgaXMgZGVmaW5lZCBhcyBvcHRpb25hbCwgYnV0IHJlYWxseSBp
c24ndC4gJnF1b3Q7QSBHTTxiciBjbGFzcz0iIj4NCnJlY2VpdmluZyB0aGUgS0VLX0FDS19SRVFV
RVNURUQgYXR0cmlidXRlIGNhbiBjaG9vc2UgdG8gaWdub3JlIGl0LCB0aHVzPGJyIGNsYXNzPSIi
Pg0KYXBwZWFyaW5nIGFzIGlmIGl0IGRvZXMgbm90IHN1cHBvcnQgdGhlIEtFS19BQ0tfUkVRVUVT
VEVEIGF0dHJpYnV0ZS4gSG93ZXZlciw8YnIgY2xhc3M9IiI+DQpHQ0tTIHBvbGljeSBtYXkgY29u
c2lkZXIgYSBub24tcmVzcG9uc2l2ZSBHTSB0byBubyBsb25nZXIgZGVzaXJlIHRvIGJlIGEgbWVt
YmVyPGJyIGNsYXNzPSIiPg0Kb2YgdGhlIGdyb3VwLiZxdW90OyBTbyBpZiB5b3Ugd2FudCB0byBw
bGF5IHRoZSBnYW1lLCB5b3UgTVVTVCBzdXBwb3J0IHRoZSBuZXc8YnIgY2xhc3M9IiI+DQphdHRy
aWJ1dGUuPGJyIGNsYXNzPSIiPg0KPC9ibG9ja3F1b3RlPg0KUG9pbnQgdGFrZW4uIFdl4oCZdmUg
Y2hhbmdlZCB0aGUgdGV4dCB0byByZWZsZWN0IHRoaXMuPGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVv
dGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+KiBJJ20gcHV6emxlZCBhdCB0aGUgb3ZlcmFsbCBwcm90
b2NvbC4gQmVpbmcgYWJsZSB0byBzZW5kIEFDS3MgaXMgYSBHTSBzb2Z0d2FyZTxiciBjbGFzcz0i
Ij4NCmNhcGFiaWxpdHkuIFdoeSBub3QgaGF2ZSB0aGUgR00gYW5ub3VuY2UgdGhpcyBjYXBhYmls
aXR5IHdoZW4gaXQgaW5pdGlhbGx5PGJyIGNsYXNzPSIiPg0KcmVnaXN0ZXJzIHRvIHRoZSBHQ0tT
PyBUaGVuIHRoZSBHQ0tTIHdvdWxkIGtub3cgd2hhdCB0byBleHBlY3QsIHdoZXJlYXMgd2l0aDxi
ciBjbGFzcz0iIj4NCnRoZSBjdXJyZW50IHByb3RvY29sIGl0IGlzIGxlZnQgd2FpdGluZyBmb3Ig
YW4gQUNLIHRoYXQgbWF5IG5ldmVyIGNvbWUsIGVpdGhlcjxiciBjbGFzcz0iIj4NCmJlY2F1c2Ug
dGhlIEdNIGlzIGRlYWQgb3IgYmVjYXVzZSBpdCBqdXN0IGRvZXNuJ3QgZmVlbCBsaWtlIHJlc3Bv
bmRpbmcuIEFkZCB0aGU8YnIgY2xhc3M9IiI+DQpsb25nIHdhaXRzIChqaXR0ZXIgb2YgJnF1b3Q7
YSBmZXcgc2Vjb25kcyZxdW90OyBhbmQgcG90ZW50aWFsIHJldHJpZXMpLCBhbmQgdGhpcyBsb29r
czxiciBjbGFzcz0iIj4NCmxpa2UgYSBmYXIgZnJvbSBvcHRpbWFsIG1hbmFnZW1lbnQgZXhwZXJp
ZW5jZS48YnIgY2xhc3M9IiI+DQo8L2Jsb2NrcXVvdGU+DQpJbmRlZWQgYSBHTSBjb3VsZCBhbm5v
dW5jZSBpdHMgY2FwYWJpbGl0eSwgYnV0IHdoZXRoZXIgb3Igbm90IEFDS3MgYXJlIGRlc2lyZWQg
aXMgYSBjb21wb25lbnQgb2YgdGhlIGdyb3VwIHBvbGljeS4gSW4gdGhlIGNvbnRleHQgb2YgR0RP
SSB0aGUgR0NLUyBpcyB0aGUgZW50aXR5IHRoYXQgZGVmaW5lcyB0aGUgZ3JvdXAgcG9saWN5LiBU
aGVyZSBjYW4gYmUgZ3JvdXBzIHdoZXJlIHRoZSBBQ0sgaXMgdXNlZCwgd2hlcmVhcyBvdGhlcnMg
ZG8gbm90Lg0KICZuYnNwO1RoZSBjYXBhYmlsaXRpZXMgYW5ub3VuY2VtZW50IHlvdSBzdWdnZXN0
IGNvdWxkIGNlcnRhaW5seSBoZWxwIHRoZSBLUyB0byBrbm93IHdoZXRoZXIgb3Igbm90IHRvIGV4
cGVjdCB0aGUgQUNLIGZyb20gYSBwYXJ0aWN1bGFyIEdNLCBidXQgdGhlIGZvY3VzIG9mIHRoaXMg
SS1EIGlzIG9uIHRoZSB0aGUgZGVjbGFyYXRpb24gb2YgdGhlIHJlcXVlc3QgZm9yIEFDS3MgYnkg
dGhlIEdDS1MgYW5kIHRoZSBmb3JtYXQgb2YgdGhlIEFDSy48YnIgY2xhc3M9IiI+DQo8YmxvY2tx
dW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj4qIDIuMjogJnF1b3Q7VGhpcyBpcyBhIHByaXZhdGUg
a2V5JnF1b3Q7IC0gdG8gYXZvaWQgY29uZnVzaW9uLCBJIHN1Z2dlc3Q6ICZxdW90O1RoaXMgaXMg
YTxiciBjbGFzcz0iIj4NCnNlY3JldCBzeW1tZXRyaWMga2V5JnF1b3Q7IChpZiB0aGlzIGlzIGlu
ZGVlZCB0aGUgY2FzZSkuIE9idmlvdXNseSB1c2luZyB0aGUgc2FtZTxiciBjbGFzcz0iIj4NCmtl
eSBmb3IgZW5jcnlwdGlvbiBhbmQgZm9yIEhNQUMgaXMgbm90IGEgYmVzdCBwcmFjdGljZS48YnIg
Y2xhc3M9IiI+DQo8L2Jsb2NrcXVvdGU+DQpXZeKAmXZlIG1hZGUgdGhpcyBjaGFuZ2UuPGJyIGNs
YXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+KiBTZWMuIDU6IEFDSyBt
ZXNzYWdlcyBjYW4gYWxzbyBiZSBkdXBsaWNhdGVkIGluIHRoZSBuZXR3b3JrLiBJIHN1Z2dlc3Qg
dG8gYWRkPGJyIGNsYXNzPSIiPg0KYSBzZW50ZW5jZSBkZXNjcmliaW5nIHdoYXQgdGhlIEdDS1Mg
c2hvdWxkIGRvIGluIHRoaXMgY2FzZS48YnIgY2xhc3M9IiI+DQo8L2Jsb2NrcXVvdGU+DQpUaGUg
U2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMgKHNlY3Rpb24gNy4zKSBkZXNjcmliZXMgYSBtZXRob2Qg
Zm9yIHRoZSBHQ0tTIHRvIGRldGVjdCByZXBsYXlzLiBUaGlzIGlzIGFyZ3VhYmx5IGJldHRlciBw
bGFjZWQgaW4gdGhpcyBzZWN0aW9uLCBzbyB3ZeKAmXZlIG1vdmVkIGl0IGhlcmUuLjxiciBjbGFz
cz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPiogU2VjLiA2OiBJIGFtIGNv
bmZ1c2VkIGFib3V0IHRoZSBub3Rpb24gb2YgJnF1b3Q7aml0dGVyJnF1b3Q7IGhlcmUuIElmIHRo
ZSBQVVNIIG1lc3NhZ2VzPGJyIGNsYXNzPSIiPg0KYXJlIHNlbnQgYXMgbXVsdGljYXN0ICh0aGUg
cmVjb21tZW5kZWQgYWx0ZXJuYXRpdmUgQUZBSUNUKSwgSSdtIG5vdCBzdXJlIGFib3V0PGJyIGNs
YXNzPSIiPg0KdGhlIGJlbmVmaXQgb2YgdXNpbmcgbXVsdGljYXN0LCBnaXZlbiB0aGF0IGVhY2gg
cmVjaXBpZW50IHJlc3BvbmRzIHdpdGggYTxiciBjbGFzcz0iIj4NCnVuaWNhc3QgQUNLLiBBbmQg
aWYgdGhlIFBVU0ggaXMgdW5pY2FzdCwgdGhlcmUgc2hvdWxkIGJlIG5vIHJlYXNvbiBmb3IgYSBq
aXR0ZXI8YnIgY2xhc3M9IiI+DQphcyB0aGUgc2VuZGVyIGNhbiB0aHJvdHRsZSB0aGUgUFVTSCBt
ZXNzYWdlcyBhcyBuZWNlc3NhcnkuPGJyIGNsYXNzPSIiPg0KPC9ibG9ja3F1b3RlPg0KVGhlIGNv
bmNlcHQgb2Yg4oCcaml0dGVy4oCdIGlzIG1vc3QgdmFsdWFibGUgZm9yIHJlc3BvbnNlcyB0byBh
IG11bHRpY2FzdCBQVVNIIG1lc3NhZ2UuIFRoZSB1c2Ugb2YgYSBtdWx0aWNhc3QgUFVTSCBtZXNz
YWdlIGxvd2VyIHByb2Nlc3Npbmcgb24gdGhlIEdDS1MuIFNpbmNlIGVhY2ggR00gY2FuIGUgZ2l2
ZW4gdGhlIGV4YWN0IHNhbWUgcG9saWN5LCB0aGVyZeKAmXMgbm8gY2FsbCB0byBzZW5kIGl0IG91
dCBhcyBhIHVuaWNhc3QgbWVzc2FnZS4gVGhlIGppdHRlcg0KIGhlbHBzIHNwcmVhZCBvdXQgdGhl
IHJlcGxpZXMgYSBiaXQgdG8gYXZvaWQgaW51bmRhdGluZyB0aGUgR0NLUy48YnIgY2xhc3M9IiI+
DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj4qIE1vcmVvdmVyLCBldmVyeXRoaW5n
IHdvdWxkIGJlIG11Y2ggbW9yZSBwcmVkaWN0YWJsZSBpZiB0aGUgR0NLUyBjb3VsZDxiciBjbGFz
cz0iIj4NCmluZGljYXRlIGlmIGEgaml0dGVyIGlzIGV4cGVjdGVkIGFuZCBob3cgbXVjaCBvZiBh
IGppdHRlciAoYmFzZWQgb24gc2l6ZSBvZiB0aGU8YnIgY2xhc3M9IiI+DQpncm91cCwgbmV0d29y
ayB0aHJvdWdocHV0LCBhbmQgcXVldWUgbGVuZ3RoKS4gU3BlY2lmaWNhbGx5LCB0aGlzIHdvdWxk
IGFsbG93PGJyIGNsYXNzPSIiPg0KdGhlIEdDS1MgdG8gdGVsbCBob3cgbG9uZyBpdCBzaG91bGQg
d2FpdCBmb3IgYW4gQUNLLjxiciBjbGFzcz0iIj4NCjwvYmxvY2txdW90ZT4NClRoaXMgd291bGQg
YmUgc29tZXdoYXQgdXNlZnVsLCBidXQgaW4gcHJhY3RpY2UgbWlnaHQgbm90IGhlbHAgdGhlIEdD
S1MgYXMgbXVjaCBhcyBpdCBzZWVtcy4gVGhlIGppdHRlciB2YWx1ZSBwcm92aWRlZCB3b3VsZCBh
bHNvIGJlIGRlcGVuZGVudCBvbiBzZXZlcmFsIG5ldHdvcmsgcGFyYW1ldGVycyB0aGF0IGFyZW7i
gJl0IHVuZGVyIHRoZSBjb250cm9sIG9mIHRoZSBHQ0tTIG9yIHRoZSBHTS4gRXZlbiB3aGVuIHRo
ZSBHTSBkb2VzIG5vdCBhZGQgYW55DQogaml0dGVyIHRvIHRoZSBBQ0ssIHRoZSB1bmRlcmx5aW5n
IG5ldHdvcmsgbWF5IGRlbGF5IHRoZSBQVVNIIGFuZC9vciBmb3IgdGhlIEFDSy4gQW5kIGFzIHN0
YXRlZCBpbiBTZWN0aW9uIDYsIHRoZSBHQ0tTIG1heSBiZSBjb25maWd1cmVkIHdpdGggYWRkaXRp
b25hbCBwb2xpY3kgYWN0aW9ucyBsaWtlIHJldHJhbnNtaXNzaW9ucyB0byBvdmVyY29tZSBsb3N0
IEFDS3MuIEFsdG9nZXRoZXIgdG8gYWRkIGppdHRlciB0byB0aGUgQUNLIGlzIG5vdCBhDQogbXVz
dCwgaXQgaXMgYSB3YXkgdG8gaGVscCB0aGUgR0NLUyBkZWFsIHdpdGggYSBodWdlIG51bWJlciBv
ZiBHTXMuIEluIHByYWN0aWNlLCB3ZeKAmXZlIGZvdW5kIHRoYXQgaGF2aW5nIHRoZSBHTXMgY2hv
b3NlIHRoZSBqaXR0ZXIgaGFzIHdvcmtlZCB3ZWxsLCBldmVuIHdoZW4gdGhlIEdNcyBhcmUgZGlm
ZmVyZW50IGltcGxlbWVudGF0aW9ucy48YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJj
aXRlIiBjbGFzcz0iIj4qIENyeXB0b2dyYXBoaWMgYWdpbGl0eTogdGhpcyBkb2N1bWVudCBzcGVj
aWZpZXMgb25seSBvbmUgYWxnb3JpdGhtIGZvciB0aGU8YnIgY2xhc3M9IiI+DQpIQVNIIHZhbHVl
LCBhbmQgc2F5cyB0aGF0IGlmIGEgbmV3IGFsZ29yaXRobSBpcyBuZWVkZWQsIHRoZXJlIHdpbGwg
YmUgYSBuZXc8YnIgY2xhc3M9IiI+DQpLRUtfQUNLX1JFUVVFU1RFRCBwYXlsb2FkIGRlZmluZWQu
IEhvd2V2ZXIgdG8gbWFrZSBzdXJlIHRoYXQgdGhpcyByZWFsbHk8YnIgY2xhc3M9IiI+DQomcXVv
dDt3b3JrcyZxdW90Oywgd2UgbmVlZCB0byBkZWZpbmUgd2hldGhlciBtdWx0aXBsZSBzdWNoIHBh
eWxvYWRzIGNhbiBiZSBzZW50PGJyIGNsYXNzPSIiPg0Kc2ltdWx0YW5lb3VzbHkgKGlmIGUuZy4g
c29tZSBHTXMgc3RpbGwgc3VwcG9ydCB0aGUgb2xkIGFsZ29yaXRobSkgYW5kIHdoYXQnczxiciBj
bGFzcz0iIj4NCnRoZSBleHBlY3RlZCBiZWhhdmlvci4gSSB3b3VsZCBzdWdnZXN0IHRvIGRlZmlu
ZSBhbiBhZGRpdGlvbmFsIFNIQS01MTIgcGF5bG9hZDxiciBjbGFzcz0iIj4NCmp1c3QgdG8gbWFr
ZSBmb3IgYSBjb25jcmV0ZSBleGFtcGxlLjxiciBjbGFzcz0iIj4NCjwvYmxvY2txdW90ZT4NClRo
aXMgaXMgYSBnb29kIHN1Z2dlc3Rpb24uIFdl4oCZdmUgYWRkZWQgU0hBLTUxMiB2ZXJzaW9ucyBv
ZiB0aGUgZXhpc3RpbmcgS0VLX0FDS19SRVFVRVNURUQgdmFsdWVzLjxiciBjbGFzcz0iIj4NClNl
ZSAmbHQ7PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXdlaXMtZ2Rv
aS1yZWtleS1hY2stMDYiIGNsYXNzPSIiPmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFm
dC13ZWlzLWdkb2ktcmVrZXktYWNrLTA2PC9hPiZndDs8YnIgY2xhc3M9IiI+DQpUaGFua3MsPGJy
IGNsYXNzPSIiPg0KQnJpYW48YnIgY2xhc3M9IiI+DQotLSA8YnIgY2xhc3M9IiI+DQpCcmlhbiBX
ZWlzPGJyIGNsYXNzPSIiPg0KU2VjdXJpdHksIENTRywgQ2lzY28gU3lzdGVtczxiciBjbGFzcz0i
Ij4NClRlbGVwaG9uZTogJiM0MzsxIDQwOCA1MjYgNDc5NjxiciBjbGFzcz0iIj4NCkVtYWlsOiA8
YSBocmVmPSJtYWlsdG86YmV3QGNpc2NvLmNvbSIgY2xhc3M9IiI+YmV3QGNpc2NvLmNvbTwvYT4g
Jmx0OzxhIGhyZWY9Im1haWx0bzpiZXdAY2lzY28uY29tIiBjbGFzcz0iIj5tYWlsdG86YmV3QGNp
c2NvLmNvbTwvYT4mZ3Q7PGJyIGNsYXNzPSIiPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Rp
dj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPGJyIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4t
LSZuYnNwOzxiciBjbGFzcz0iIj4NCkJyaWFuIFdlaXM8YnIgY2xhc3M9IiI+DQpTZWN1cml0eSwg
Q1NHLCBDaXNjbyBTeXN0ZW1zPGJyIGNsYXNzPSIiPg0KVGVsZXBob25lOiAmIzQzOzEgNDA4IDUy
NiA0Nzk2PGJyIGNsYXNzPSIiPg0KRW1haWw6IDxhIGhyZWY9Im1haWx0bzpiZXdAY2lzY28uY29t
IiBjbGFzcz0iIj5iZXdAY2lzY28uY29tPC9hPiA8L2Rpdj4NCjxiciBjbGFzcz0iIj4NCjwvZGl2
Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_DE62366A03774DE19ED0A14E44A7EC05ciscocom_--


From nobody Tue Aug 29 14:00:09 2017
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E0E0132944; Tue, 29 Aug 2017 14:00:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v1kzSKQCoijz; Tue, 29 Aug 2017 14:00:04 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A011E124E15; Tue, 29 Aug 2017 14:00:03 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id u26so5222729wma.0; Tue, 29 Aug 2017 14:00:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=6YGrK2gCM29k+y7ct+1x7Dwb+DppKUiUtJ7d7zmm6WI=; b=Ph+680gQ4ibGuDeDQYN0b5wtAp1ZR+r3BunYehMLTBldOEanAZfIqzJxeIJ1hGTyW2 0S8+NuIOFm097gmq+aJ7xtPDZYumiEZ3vGALLHcpxaAYKz0by92yoazVZ9Bfczg+ievz FBL+5LgSqUZF3EMuEFLU3//okvU4HmOG36cPs9uPcWPT0QCqziSs0qyo04jEAnp74KZK b4+Uu59ryEHIghhhW4Np3jxnT0BtI0vo4LG7C4dToc/bwBi7UQZedOG7LkYRyKO5Bu4l GSqUrg5AQeTKcXQlQPFAAp8hyFYR5JaIp/Mkoasy/xDg/tqByUNKbsWdXkPFECc+PcZ5 UeXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=6YGrK2gCM29k+y7ct+1x7Dwb+DppKUiUtJ7d7zmm6WI=; b=N6QlW/dBDQlCDHJBjiOWCVERmeNMEdsP6MfrYV5jIV9D8BMu+HA6I3Y020UeAfEXZ4 hQaPC4UQ5Lb0AIXbuAZ4TLJDM50m1D+WWBW1BEUmLlBL54DTquOuk9CHTzY2lzaeLC/s x7E5RzAU7Y2y6peUePdtsQWvOjrj7r+GkvRS2E8fhfd9jRrevNpk42muXETP6xo3WCSe F6aMQy+I/6aUZW5R92qjZnfAj6MImYLuM+JpzXeBVGabu670MHoFFHn07HZqwHzWzCsP P3DgaETvEwleXI2emNOMygxwfCCOYnH8dncuZo25TTtmzaCWFDEpMjoruRWuwnutqi4/ IiGg==
X-Gm-Message-State: AHYfb5g+RO/mkbLXx8kBSr74+8KmcnSXs3SmKp26djrKrIlK/UniaHzx Bux1RM4j+Qv2UztNQ5k=
X-Received: by 10.28.238.197 with SMTP id j66mr354824wmi.170.1504040401535; Tue, 29 Aug 2017 14:00:01 -0700 (PDT)
Received: from [10.0.0.10] (bzq-109-67-55-26.red.bezeqint.net. [109.67.55.26]) by smtp.gmail.com with ESMTPSA id v60sm5177895wrc.71.2017.08.29.14.00.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Aug 2017 14:00:00 -0700 (PDT)
Subject: Re: Secdir last call review of draft-weis-gdoi-rekey-ack-05
To: "Brian Weis (bew)" <bew@cisco.com>
Cc: "secdir@ietf.org" <secdir@ietf.org>, "draft-weis-gdoi-rekey-ack.all@ietf.org" <draft-weis-gdoi-rekey-ack.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
References: <150194814585.18635.3104789196001873381@ietfa.amsl.com> <E61F05DB-EEB0-4140-A2D4-DB11163C4E13@cisco.com> <e2b32453-8c4f-9707-0e1f-dab29540fe54@gmail.com> <DE62366A-0377-4DE1-9ED0-A14E44A7EC05@cisco.com>
From: Yaron Sheffer <yaronf.ietf@gmail.com>
Message-ID: <d6a9c046-4404-341b-2282-934bb5ca5ec7@gmail.com>
Date: Tue, 29 Aug 2017 23:59:58 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <DE62366A-0377-4DE1-9ED0-A14E44A7EC05@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NqH7j0rf3I_KwZSYYONM7Q-JjDs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 29 Aug 2017 21:00:07 -0000

Hi Brian,

To me, incremental deployment is what crypto-agility is all about. But I 
guess others might disagree. In any case, this limitation needs to be 
discussed when we talk about agility.

Thanks,
	Yaron

On 29/08/17 23:48, Brian Weis (bew) wrote:
> Hi Yaron,
> 
>> On Aug 26, 2017, at 8:34 AM, Yaron Sheffer <yaronf.ietf@gmail.com 
>> <mailto:yaronf.ietf@gmail.com>> wrote:
>>
>> Hi Brian,
>>
>> Thank you for addressing most of my comments in the new version, and 
>> for clarifying points where I was off the mark.
>>
>> The only remaining comment that's only partly addressed is the one on 
>> crypto agility. Quoting myself:
>>
>> we need to define whether multiple such payloads can be sent 
>> simultaneously (if e.g. some GMs still support the old algorithm) and 
>> what's the expected behavior.
>>
>> In other words, supporting more algorithms in not sufficient. The 
>> question is whether we support incremental deployment of a new 
>> algorithm to a large group of GMs.
> 
> Sorry, we missed this. Incremental deployment of any new policy 
> (algorithm or otherwise) within a group is not so straightforward. There 
> can really only be one set of policy used by the entire group because if 
> a sender has been updated to a new set of policy it can’t really use it 
> until all receivers are similarly upgraded. This is a place where a 
> capabilities exchange can be useful for a key server to declare a switch 
> to a new algorithm after all members claim to support it, but that might 
> never happen in a large group. Practically speaking incremental updates 
> in a large group might require two different groups with a bridge 
> between, or some other deployment structure. Since it’s a broader 
> problem, I’m not sure what else we can do in this document to address 
> incremental deployment.
> 
> Thanks,
> Brian
> 
>>
>> Thanks,
>> Yaron
>>
>> On 24/08/17 19:48, Brian Weis (bew) wrote:
>>> Hi Yaron,
>>> Thanks for the review. We’ve added some clarification below, and made 
>>> some changes in -06 to address your comments. Please let us know if 
>>> we did not address them satisfactorily.
>>>> On Aug 5, 2017, at 8:49 AM, Yaron Sheffer <yaronf.ietf@gmail.com 
>>>> <mailto:yaronf.ietf@gmail.com> <mailto:yaronf.ietf@gmail.com>> wrote:
>>>>
>>>> Reviewer: Yaron Sheffer
>>>> Review result: Has Issues
>>>>
>>>> Summary: this reviewer is not clear about the value of the push-ack 
>>>> (compared
>>>> to a pull) and about the strategy that was chosen.
>>> In a group key management system either a “pull” (triggered by a 
>>> group member) or a “push” (by the key server)" could be used to 
>>> provide updates to the group. However, a “pull” by the group member 
>>> implies a polling method, which has the deficiency that the key 
>>> server cannot cause a policy replacement any sooner than the polling 
>>> method by the group members. Also “polling” can cause additional 
>>> unnecessary traffic. So is is better for any update on the group 
>>> policy or renewal of group keys to be distributed by the GCKS using a 
>>> PUSH message. The ACK-message is used to offer a feedback mechanism 
>>> to a policy update for the PUSH exchange.
>>>>
>>>> *//*
>>>>
>>>> * "For example, a GCKS policy can use the acknowledgements to 
>>>> determine [...]
>>>> which members may no longer be members of the group." This sentence 
>>>> is very
>>>> confusing: when are members not members?
>>> We’ve reworded this text. It’s trying to convey that a missing ACK 
>>> message (or a certain number of it) can be used to identify that a 
>>> group member is no longer receiving group traffic, and is now may be 
>>> considered an ex-group member. For example, it could be a multicast 
>>> receiver that is no longer interested in being a receiver for the 
>>> group. But it could also be that a network event has caused it to be 
>>> unavailable for a sufficient length of time such that it doesn’t have 
>>> current keying material and therefore can’t be considered a current 
>>> group member. There is no reliable “I’m leaving the group” message 
>>> flow, and of course in my second example no such messages would have 
>>> been intended by the group member.
>>>> * The new protocol capability is defined as optional, but really 
>>>> isn't. "A GM
>>>> receiving the KEK_ACK_REQUESTED attribute can choose to ignore it, thus
>>>> appearing as if it does not support the KEK_ACK_REQUESTED attribute. 
>>>> However,
>>>> GCKS policy may consider a non-responsive GM to no longer desire to 
>>>> be a member
>>>> of the group." So if you want to play the game, you MUST support the new
>>>> attribute.
>>> Point taken. We’ve changed the text to reflect this.
>>>> * I'm puzzled at the overall protocol. Being able to send ACKs is a 
>>>> GM software
>>>> capability. Why not have the GM announce this capability when it 
>>>> initially
>>>> registers to the GCKS? Then the GCKS would know what to expect, 
>>>> whereas with
>>>> the current protocol it is left waiting for an ACK that may never 
>>>> come, either
>>>> because the GM is dead or because it just doesn't feel like 
>>>> responding. Add the
>>>> long waits (jitter of "a few seconds" and potential retries), and 
>>>> this looks
>>>> like a far from optimal management experience.
>>> Indeed a GM could announce its capability, but whether or not ACKs 
>>> are desired is a component of the group policy. In the context of 
>>> GDOI the GCKS is the entity that defines the group policy. There can 
>>> be groups where the ACK is used, whereas others do not.  The 
>>> capabilities announcement you suggest could certainly help the KS to 
>>> know whether or not to expect the ACK from a particular GM, but the 
>>> focus of this I-D is on the the declaration of the request for ACKs 
>>> by the GCKS and the format of the ACK.
>>>> * 2.2: "This is a private key" - to avoid confusion, I suggest: 
>>>> "This is a
>>>> secret symmetric key" (if this is indeed the case). Obviously using 
>>>> the same
>>>> key for encryption and for HMAC is not a best practice.
>>> We’ve made this change.
>>>> * Sec. 5: ACK messages can also be duplicated in the network. I 
>>>> suggest to add
>>>> a sentence describing what the GCKS should do in this case.
>>> The Security Considerations (section 7.3) describes a method for the 
>>> GCKS to detect replays. This is arguably better placed in this 
>>> section, so we’ve moved it here..
>>>> * Sec. 6: I am confused about the notion of "jitter" here. If the 
>>>> PUSH messages
>>>> are sent as multicast (the recommended alternative AFAICT), I'm not 
>>>> sure about
>>>> the benefit of using multicast, given that each recipient responds 
>>>> with a
>>>> unicast ACK. And if the PUSH is unicast, there should be no reason 
>>>> for a jitter
>>>> as the sender can throttle the PUSH messages as necessary.
>>> The concept of “jitter” is most valuable for responses to a multicast 
>>> PUSH message. The use of a multicast PUSH message lower processing on 
>>> the GCKS. Since each GM can e given the exact same policy, there’s no 
>>> call to send it out as a unicast message. The jitter helps spread out 
>>> the replies a bit to avoid inundating the GCKS.
>>>> * Moreover, everything would be much more predictable if the GCKS could
>>>> indicate if a jitter is expected and how much of a jitter (based on 
>>>> size of the
>>>> group, network throughput, and queue length). Specifically, this 
>>>> would allow
>>>> the GCKS to tell how long it should wait for an ACK.
>>> This would be somewhat useful, but in practice might not help the 
>>> GCKS as much as it seems. The jitter value provided would also be 
>>> dependent on several network parameters that aren’t under the control 
>>> of the GCKS or the GM. Even when the GM does not add any jitter to 
>>> the ACK, the underlying network may delay the PUSH and/or for the 
>>> ACK. And as stated in Section 6, the GCKS may be configured with 
>>> additional policy actions like retransmissions to overcome lost ACKs. 
>>> Altogether to add jitter to the ACK is not a must, it is a way to 
>>> help the GCKS deal with a huge number of GMs. In practice, we’ve 
>>> found that having the GMs choose the jitter has worked well, even 
>>> when the GMs are different implementations.
>>>> * Cryptographic agility: this document specifies only one algorithm 
>>>> for the
>>>> HASH value, and says that if a new algorithm is needed, there will 
>>>> be a new
>>>> KEK_ACK_REQUESTED payload defined. However to make sure that this really
>>>> "works", we need to define whether multiple such payloads can be sent
>>>> simultaneously (if e.g. some GMs still support the old algorithm) 
>>>> and what's
>>>> the expected behavior. I would suggest to define an additional 
>>>> SHA-512 payload
>>>> just to make for a concrete example.
>>> This is a good suggestion. We’ve added SHA-512 versions of the 
>>> existing KEK_ACK_REQUESTED values.
>>> See <https://tools.ietf.org/html/draft-weis-gdoi-rekey-ack-06>
>>> Thanks,
>>> Brian
>>> -- 
>>> Brian Weis
>>> Security, CSG, Cisco Systems
>>> Telephone: +1 408 526 4796
>>> Email: bew@cisco.com <mailto:bew@cisco.com> <mailto:bew@cisco.com>
>>
>>
>> Thanks,
>> Yaron
>>
>> On 24/08/17 19:48, Brian Weis (bew) wrote:
>>> Hi Yaron,
>>> Thanks for the review. We’ve added some clarification below, and made 
>>> some changes in -06 to address your comments. Please let us know if 
>>> we did not address them satisfactorily.
>>>> On Aug 5, 2017, at 8:49 AM, Yaron Sheffer <yaronf.ietf@gmail.com 
>>>> <mailto:yaronf.ietf@gmail.com> <mailto:yaronf.ietf@gmail.com>> wrote:
>>>>
>>>> Reviewer: Yaron Sheffer
>>>> Review result: Has Issues
>>>>
>>>> Summary: this reviewer is not clear about the value of the push-ack 
>>>> (compared
>>>> to a pull) and about the strategy that was chosen.
>>> In a group key management system either a “pull” (triggered by a 
>>> group member) or a “push” (by the key server)" could be used to 
>>> provide updates to the group. However, a “pull” by the group member 
>>> implies a polling method, which has the deficiency that the key 
>>> server cannot cause a policy replacement any sooner than the polling 
>>> method by the group members. Also “polling” can cause additional 
>>> unnecessary traffic. So is is better for any update on the group 
>>> policy or renewal of group keys to be distributed by the GCKS using a 
>>> PUSH message. The ACK-message is used to offer a feedback mechanism 
>>> to a policy update for the PUSH exchange.
>>>>
>>>> *//*
>>>>
>>>> * "For example, a GCKS policy can use the acknowledgements to 
>>>> determine [...]
>>>> which members may no longer be members of the group." This sentence 
>>>> is very
>>>> confusing: when are members not members?
>>> We’ve reworded this text. It’s trying to convey that a missing ACK 
>>> message (or a certain number of it) can be used to identify that a 
>>> group member is no longer receiving group traffic, and is now may be 
>>> considered an ex-group member. For example, it could be a multicast 
>>> receiver that is no longer interested in being a receiver for the 
>>> group. But it could also be that a network event has caused it to be 
>>> unavailable for a sufficient length of time such that it doesn’t have 
>>> current keying material and therefore can’t be considered a current 
>>> group member. There is no reliable “I’m leaving the group” message 
>>> flow, and of course in my second example no such messages would have 
>>> been intended by the group member.
>>>> * The new protocol capability is defined as optional, but really 
>>>> isn't. "A GM
>>>> receiving the KEK_ACK_REQUESTED attribute can choose to ignore it, thus
>>>> appearing as if it does not support the KEK_ACK_REQUESTED attribute. 
>>>> However,
>>>> GCKS policy may consider a non-responsive GM to no longer desire to 
>>>> be a member
>>>> of the group." So if you want to play the game, you MUST support the new
>>>> attribute.
>>> Point taken. We’ve changed the text to reflect this.
>>>> * I'm puzzled at the overall protocol. Being able to send ACKs is a 
>>>> GM software
>>>> capability. Why not have the GM announce this capability when it 
>>>> initially
>>>> registers to the GCKS? Then the GCKS would know what to expect, 
>>>> whereas with
>>>> the current protocol it is left waiting for an ACK that may never 
>>>> come, either
>>>> because the GM is dead or because it just doesn't feel like 
>>>> responding. Add the
>>>> long waits (jitter of "a few seconds" and potential retries), and 
>>>> this looks
>>>> like a far from optimal management experience.
>>> Indeed a GM could announce its capability, but whether or not ACKs 
>>> are desired is a component of the group policy. In the context of 
>>> GDOI the GCKS is the entity that defines the group policy. There can 
>>> be groups where the ACK is used, whereas others do not.  The 
>>> capabilities announcement you suggest could certainly help the KS to 
>>> know whether or not to expect the ACK from a particular GM, but the 
>>> focus of this I-D is on the the declaration of the request for ACKs 
>>> by the GCKS and the format of the ACK.
>>>> * 2.2: "This is a private key" - to avoid confusion, I suggest: 
>>>> "This is a
>>>> secret symmetric key" (if this is indeed the case). Obviously using 
>>>> the same
>>>> key for encryption and for HMAC is not a best practice.
>>> We’ve made this change.
>>>> * Sec. 5: ACK messages can also be duplicated in the network. I 
>>>> suggest to add
>>>> a sentence describing what the GCKS should do in this case.
>>> The Security Considerations (section 7.3) describes a method for the 
>>> GCKS to detect replays. This is arguably better placed in this 
>>> section, so we’ve moved it here..
>>>> * Sec. 6: I am confused about the notion of "jitter" here. If the 
>>>> PUSH messages
>>>> are sent as multicast (the recommended alternative AFAICT), I'm not 
>>>> sure about
>>>> the benefit of using multicast, given that each recipient responds 
>>>> with a
>>>> unicast ACK. And if the PUSH is unicast, there should be no reason 
>>>> for a jitter
>>>> as the sender can throttle the PUSH messages as necessary.
>>> The concept of “jitter” is most valuable for responses to a multicast 
>>> PUSH message. The use of a multicast PUSH message lower processing on 
>>> the GCKS. Since each GM can e given the exact same policy, there’s no 
>>> call to send it out as a unicast message. The jitter helps spread out 
>>> the replies a bit to avoid inundating the GCKS.
>>>> * Moreover, everything would be much more predictable if the GCKS could
>>>> indicate if a jitter is expected and how much of a jitter (based on 
>>>> size of the
>>>> group, network throughput, and queue length). Specifically, this 
>>>> would allow
>>>> the GCKS to tell how long it should wait for an ACK.
>>> This would be somewhat useful, but in practice might not help the 
>>> GCKS as much as it seems. The jitter value provided would also be 
>>> dependent on several network parameters that aren’t under the control 
>>> of the GCKS or the GM. Even when the GM does not add any jitter to 
>>> the ACK, the underlying network may delay the PUSH and/or for the 
>>> ACK. And as stated in Section 6, the GCKS may be configured with 
>>> additional policy actions like retransmissions to overcome lost ACKs. 
>>> Altogether to add jitter to the ACK is not a must, it is a way to 
>>> help the GCKS deal with a huge number of GMs. In practice, we’ve 
>>> found that having the GMs choose the jitter has worked well, even 
>>> when the GMs are different implementations.
>>>> * Cryptographic agility: this document specifies only one algorithm 
>>>> for the
>>>> HASH value, and says that if a new algorithm is needed, there will 
>>>> be a new
>>>> KEK_ACK_REQUESTED payload defined. However to make sure that this really
>>>> "works", we need to define whether multiple such payloads can be sent
>>>> simultaneously (if e.g. some GMs still support the old algorithm) 
>>>> and what's
>>>> the expected behavior. I would suggest to define an additional 
>>>> SHA-512 payload
>>>> just to make for a concrete example.
>>> This is a good suggestion. We’ve added SHA-512 versions of the 
>>> existing KEK_ACK_REQUESTED values.
>>> See <https://tools.ietf.org/html/draft-weis-gdoi-rekey-ack-06>
>>> Thanks,
>>> Brian
>>> -- 
>>> Brian Weis
>>> Security, CSG, Cisco Systems
>>> Telephone: +1 408 526 4796
>>> Email: bew@cisco.com <mailto:bew@cisco.com> <mailto:bew@cisco.com>
> 
> -- 
> Brian Weis
> Security, CSG, Cisco Systems
> Telephone: +1 408 526 4796
> Email: bew@cisco.com <mailto:bew@cisco.com>
> 


From nobody Wed Aug 30 02:23:03 2017
Return-Path: <ibagdona.ietf@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FA521321C4; Wed, 30 Aug 2017 02:23:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ignas Bagdonas <ibagdona.ietf@gmail.com>
To: <ops-dir@ietf.org>
Cc: ietf@ietf.org, teas@ietf.org, draft-ietf-teas-lsp-diversity.all@ietf.org
Subject: Opsdir last call review of draft-ietf-teas-lsp-diversity-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.59.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150408498245.21623.17739725352149405409@ietfa.amsl.com>
Date: Wed, 30 Aug 2017 02:23:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/izbJ5FpnZFwBAT-LAm3YDXb3ho4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 30 Aug 2017 09:23:02 -0000

Reviewer: Ignas Bagdonas
Review result: Has Issues

Hi there.

I have reviewed this document as part of the Operations Directorate's document
review process.

Overall the document seems to be heading in the right direction. There are some
issues related to clarity of RFC2119 language usage, especially less
restrictive forms and how that would relate to interoperability, the handling
of undefined values and errors, terminology could be aligned better to base
GMPLS and TE specifications. The document does not cover manageability or
operational considerations at all - given that it is proposing protocol
extensions that require operator involvement, a section on operational
considerations and possible extensions to management models and procedures
should be covered. The Path-Key based signalling form seems to have interdomain
signalling related security aspects that would need to be looked a bit deeper.
The document would benefit from terminology and acronyms section specific to
the proposed mechanism.

The larger comment on time scale and granularity aspects of SRLG aware path
calculation. The document is based on the assumption of a longer time period
between LSP signalling requests and path reoptimizations. What is the reason
for it, and what would be needed if the proposed solution is expected to
operate in closer to real time environment (minutes instead of weeks)? What is
the source of the time granularity restriction?

Diversity information flooding specifics are stated as being out of scope. How
would that impact interoperability?

PAS identifier name space may be smaller or not comparable with SRLG group
identifier name space, is there a need to have any form of mapping mechanism in
place?

Small nits:

- Example based on figure 1 has got details wrong.

- Terms need to be consistent throughout the document - initiated/controlled is
used interchangeably, this seems to be coming from the merge of the 3 original
drafts.

- There is no "IPv4/IPv6" diversity identifier, they are separate per address
family and text should be expanded to describe them separately.

- Could the text describing the operation of L bit be simplified by stating
that L bit has the same semantics as in any other object - strict/loose hop
selection, and therefore diversity identifier is interpreted as a strict or
loose entity that MUST or MAY be taken into account?

There is a set of editorial nits and fixes throughout the document, a marked
version of the document is attached.

Thank you.

Ignas



From nobody Wed Aug 30 03:55:48 2017
Return-Path: <stefan.winter@restena.lu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C57E4132E9E; Wed, 30 Aug 2017 03:55:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, WEIRD_PORT=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id noWp-QSbVAuO; Wed, 30 Aug 2017 03:55:29 -0700 (PDT)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::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 4F770132E97; Wed, 30 Aug 2017 03:55:29 -0700 (PDT)
Received: from aragorn.restena.lu (aragorn.restena.lu [IPv6:2001:a18:1:8::155]) by smtprelay.restena.lu (Postfix) with ESMTPS id B706643AF0; Wed, 30 Aug 2017 12:55:27 +0200 (CEST)
Subject: Re: [OPS-DIR] Opsdir last call review of draft-ietf-tsvwg-sctp-ndata-12
To: Michael Tuexen <tuexen@fh-muenster.de>
Cc: ops-dir@ietf.org, tsvwg@ietf.org, ietf@ietf.org, draft-ietf-tsvwg-sctp-ndata.all@ietf.org
References: <150287547583.12471.9085655210334710687@ietfa.amsl.com> <FDCFFA8C-8828-4578-A66E-A1AD7FF9BDC9@fh-muenster.de>
From: Stefan Winter <stefan.winter@restena.lu>
Openpgp: id=AD3091F3AB24E05F4F722C03C0DE6A358A39DC66; url=http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC0DE6A358A39DC66
Message-ID: <1a39dff3-55a9-fe1d-7e19-a0fbd0b2751b@restena.lu>
Date: Wed, 30 Aug 2017 12:55:27 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <FDCFFA8C-8828-4578-A66E-A1AD7FF9BDC9@fh-muenster.de>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="UkpaJf7op9RwpXffTxWmLDPqCwTptcxOI"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nZUS8QVGpKMFMlASvEls-xtdt2U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 30 Aug 2017 10:55:33 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--UkpaJf7op9RwpXffTxWmLDPqCwTptcxOI
Content-Type: multipart/mixed; boundary="kdH3TJxgFep85VqxqtldwGOxUxWSjr95F";
 protected-headers="v1"
From: Stefan Winter <stefan.winter@restena.lu>
To: Michael Tuexen <tuexen@fh-muenster.de>
Cc: ops-dir@ietf.org, tsvwg@ietf.org, ietf@ietf.org,
 draft-ietf-tsvwg-sctp-ndata.all@ietf.org
Message-ID: <1a39dff3-55a9-fe1d-7e19-a0fbd0b2751b@restena.lu>
Subject: Re: [OPS-DIR] Opsdir last call review of
 draft-ietf-tsvwg-sctp-ndata-12
References: <150287547583.12471.9085655210334710687@ietfa.amsl.com>
 <FDCFFA8C-8828-4578-A66E-A1AD7FF9BDC9@fh-muenster.de>
In-Reply-To: <FDCFFA8C-8828-4578-A66E-A1AD7FF9BDC9@fh-muenster.de>

--kdH3TJxgFep85VqxqtldwGOxUxWSjr95F
Content-Type: multipart/mixed;
 boundary="------------130DEFEAF385F9D2F7754364"
Content-Language: lb-LU

This is a multi-part message in MIME format.
--------------130DEFEAF385F9D2F7754364
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi,

>> The chapter IANA considerations mentions four bits to be registered: E=
,B,U,I.
>> In the main body, only three of those are actually defined and used (E=
nd of
>> fragmented message, Beginning of fragmented message, Unordered/Ordered=

>> message). Please add a definition of the I bit or remove the IANA regi=
stration
>> request for that bit.
> The I bit is defined in RFC 7053 and that is the reason why we state
> "DATA chunk defined in [RFC4960]and [RFC7053]". In addition to that it =
is
> not mentioned (in contrast to the U, B and E bit), since the delaying o=
f the
> SACK is not specific to the I-DATA chunk.
>
> I have added the following text to the body of Section 2.2:
>
> <t>The handling of the I bit for the I-DATA chunk corresponds to the ha=
ndling
> of the I bit for the DATA chunk described in <xref target=3D'RFC7053'/>=
=2E</t>
>
> to improve the description of the I bit. See
> https://github.com/sctplab/sctp-idata/commit/f16308ffe0e67ce5deb957bd40=
c25c5a0e691b82
> Does that address your issue?

Yes, thank you.


>> And the rest are only musings not needing any action if the authors do=
n't want
>> to action on them:
>>
>> The introduction presents a good use case, quoting: "e.g., when the
>> transmission of an urgent
>>   message is blocked from transmission because the sender has started
>>   the transmission of another, possibly large, message".
>>
>> The later queueing example in figure 1 has three SIDs being queued
>> simultanseously. It is not clear which of those "has already started" =
and which
> There is actually one message queued for stream 0, three messages for s=
tream 1,
> and one message for stream 2.
>> are the important ones being delayed. For a better understanding of th=
e reader,
> The figure is about in which sequence they are put on the wire. So no
> transmission has startet. This examples also does not deal with the cas=
e
> of one stream having a higher priority than another. That would be an
> example using a priority scheduler. This examples illustrates the round=

> robin scheduler.
> The point here is that a single scheduler (the round robin scheduler, f=
or
> example) behaves differently when user message interleaving is used or =
not.
> That is an important point: You can even use the schedulers with regula=
r
> DATA chunk, i.e. with user message interleaving being negotiated.
>> it might be useful to revise the figure so that the head-of-line block=
ing
>> happens for SID 1 because transmission of  0 and 2 has already started=
 (and
>> declare SID 1 to be the "important" message). The ASCII art would just=
 have to
>> indent SID 1 content a bit (placing 0 and 2 earlier in time), and the =
resulting
>> serialisation would then put all the SID 1 messages at the very end, w=
hen 0 and
>> 2 have been completely submitted (right?).
> One could think about adding another example based on the priority sche=
duler
> and giving stream 1 a higher priority. But for illustrating the point o=
f
> schedulers behaving differently depending on the negotiation of user me=
ssage
> interleaving this seems not necessary.

That second example might indeed be useful.

It's simply a bit strange that in the introduction you speak about an
"urgent" message (something deserving a higher-priority sending) and
that another transmission has already started - but then the example has
none of those two.

In fact I wonder why you speak about urgent things in the introduction
at all. Neither the scheduler nor the interleaving are designed to help
urgent things to be sent earlier.

All they do is make the transmission fairer so that *all* chunks get a
more even serialised distribution on the wire.

So, rather than saying that the spec helps urgent things to be sent
earlier, it should maybe rather state that the spec helps every message
getting an equal, and equally distributed, share of the medium.

>> In 2.2.3, is there any particular reason why the "protocol violation" =
error
>> cause is only a MAY? As it enables debugging on the remote end, a SHOU=
LD seems
>> useful.
> This is for consistency with other SCTP specifications. There is always=
 the balance
> between providing more information to help diagnosing the problem and p=
roviding more
> information to an attacker. This allows implementers to do what they pr=
efer.
> For interoperability it is not important if the error cause is included=
 or not.

That's fine, thanks.

Greetings,

Stefan

--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et de la Recherche
2, avenue de l'Universit=E9
L-4365 Esch-sur-Alzette

Tel: +352 424409 1
Fax: +352 422473

PGP key updated to 4096 Bit RSA - I will encrypt all mails if the recipie=
nt's key is known to me

http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xC0DE6A358A39DC66


--------------130DEFEAF385F9D2F7754364
Content-Type: application/pgp-keys;
 name="0x8A39DC66.asc"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="0x8A39DC66.asc"

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2

mQINBFIplEwBEADTSz+DS8nio+RSvfSLLfaOnCGi1nqpn8Pb1laVUyEvnAAzZ5je
miS88GxfiDH6hUGlWzcaW0hCfUHGiohr485adbjxRksPngWgAt/1bRxpifsW3zOb
Fjgog01WWQV5Sihlwc4zr8zvYbFA5BJZ6YdkR9C5J015riv5OS30WTjA65SSXgYr
b7zJWPwmegTFwE093uBFvC39waz3xYpVu5j87nO6w2MVQt/8sY2/2BFPEq+xfOaj
l18UEwc7w8SCgnZdlVNcmEK4UBvJuwS/1lsR2JeQa8Gu1EDxC7PRgMgNXsDSWnnB
e9aVmfG54+6ILe1QH2dwk9sPBQT5w2+vjijrb3Dv9ur+1kN+TNU2XE436jVpnnY/
3OsLdix30STQn4Q/XOm7YoVMeDwwviefilRxzK0dXA+wKj92T68Od82CFxuZqPAg
BCVmWfQM91iK9piqFK+QP+R3vF6+NGDBdwbe68iVKs0v5L8XmbxBQndjpmo+lo2a
smBR2TAIfZHaKdgtBw13u3GPVVKlg/Mpko8ki9JOSem2aFyi3kQEVKptWgXT3POl
97DWJzsR5VyKz6GOx9kJAEISRyLZwm0wqh8+9LCza5oeIKW381lzq1b9x30vOh8C
BSQQJ+cG9ko0yPHAj7Suw2TmPXx1qMctmE6Ahq82ZW30SljdZby8WQuR2wARAQAB
tDxTdGVmYW4gV2ludGVyIChSRVNURU5BIGtleSAyMDEzKykgPHN0ZWZhbi53aW50
ZXJAcmVzdGVuYS5sdT6JAjkEEwECACMFAlIplEwCGwMHCwkIBwMCAQYVCAIJCgsE
FgIDAQIeAQIXgAAKCRDA3mo1ijncZj7/D/99hVS+mJr8dSPCaDaUFFxBiT2eI1Lo
R8VKEerTCRw5BsdL6pN2eRJZ9NmsqWo1ynWVHEzO91bNZ+oZGgyoNohcBAI7p+r0
qUTzkyqwdZO4kMm0pqKoM9xkP3tf2mjGujKjOz4Y7S7wnz2ZFokeUsecoRVJF/++
/qHnmeWLn44J1HUKLHYCjMu+QXGOgGXgz024jQ5eUrnPwzNp0Z90AFVHlWC+bymt
y/ToIUUCQqS5Ff0jzdWLd8U695OG9iGvjBQT1LdEjsfbAwuKV5UcnpxNqUpUwKa5
9hdX5/2cMZP07FI1UXwnBlxa8rJfdb13FLjSKX4vUUHedYUZMjMPgcwl1a+zGE22
lHiSQWgP8QLA/W3BLsi22ERCEPZBfexOeOtaWIItDIz18fIaQoMDoRPshzar0JI2
CzLYsyeKySAtYJEHFVoLmMvhkwzBmgqA/BEswUA67CfCr1jFHRXdpmWM7YkyAmMa
9q6LwquWKS5+MXlUXe/3oZUcgpw/T9Uuy3Jo3RdS7B3jFcWaVr6KsO/A9u1gr/aY
n5M+iJTQSj4vzqtkQaJTpSspRZoKa66HZt3IwSYiDiYZqtM83ynuj9kjnZzGfnuT
aNIi996q6Mptr33mOzIE1wmMqnJYwTr3EcNtf483q/qrJwh5ES8Q9xY7aat/ZcSl
8fKubW4TlfVr8YhGBBARAgAGBQJSKZUGAAoJEPo5vdH/HhVmYTgAn24eoqO/O98o
vNpt08Uab/+/tmYKAJ9kjXm9Njz5h33efzeelZUa484rr7kCDQRSKZRMARAAvBPp
n7FQq7LQ5glohtbL6XIEo1U4X67S0TzUYieENSWSVYuWYIhCBldmWdmH8Bpj/qHe
qdon7v+SLtR4WngzMR9toupKcFfHnbP9kpazTSB2ySHxXWGX1gJOpPXdCcg9iveK
BHEsDn00ThTcPsvtXpnnzET16pXIvOXO0bxTmVZ4INIF1SWgvYma/g8kBbgXLpkj
8tOywBqFiiYPEZlDeCxDHiMgUDh6olda9K/0TZFTdMPUgjKuubfAeaDNCOrVt4Rj
mFOaRLikcZocmgJhm3z/j25x7/mnNu+0di1H/S67YGQJ+pqCFInzIXDx7aRW2+JC
iqsY2X3xOPWZZzjyis5SNnfOcPH3gt2hYz1fy+thsBGf4NgCN01JRqIJ2/MOQCgU
dwh+9l8xqaJvCkUHM4hVh4W62MAe1u7UEqQbvvNEqxM5034vcvlE+/LRkrDCspw+
2YJ9QyroLerVRwW5DVleP8Ifi8VB3yD80nqXYs9aqRy0BkDNIQ43ERhESMt8dJqr
NkxgC6pemZrhNwyDh+hy2kPNGQh/iBpdKuH1o3E24TIZoV2v3YHvzob7aAYHddE/
PofAXhJW7I9mAs+HdWDmnI8ckuPDFpFH+Y/BFGvEXgcnJAJ1wEvf+4LuiIi0MHjR
4EWFn9vvoFDAIqD10h3FSd3D59HGtdSsNn4XaCsAEQEAAYkCHwQYAQIACQUCUimU
TAIbDAAKCRDA3mo1ijncZhBtEACL036ddjc5pFoYIdoUY1vT8SMXJNquewCnL1qu
DADzqDZFU5GNlQEy10krSfBwlTb9ahTtE0JFrOdZwUZtoa1Pgfr8nU6KOgrXPHbN
jS/9dyc5CwGVVIpOavIm2CsMVDJ9LCF/NT+u/t1k6eGfHhPVl3dUQyDa/lzc1chK
UIVQYQkFmr0A/iXP+29lFCaI+IeyU0bSdZhezDwUROn5vEx+fiPZyHDShCb+BxJv
/o2LQp9JHenCiSbO+ioRZdxgbWfoKBuXOfmSStqMWXas/gZ5vS3xq72LNtKPRxgp
jX3P8Zml1XDqpcBau7eK75VKE0Yd06YxnUIsbcEzInUc3uzW/u0DFpXYkMJb0XIv
JyUt5yYPKfV13N8kSkPi5pLxm8yuftXMzfgeFMR7nafY3glTVj/TxElzg6xeZNqf
C2ZjIbBtZg9ylHU8u8wwB+dX282crs0R3N9A064C71/cXlBqcjzjlKH2NUIWGxr+
od3TXFIFjszSU3NgMPKrWNhFLLwS81MpbkOe73s6aDhS8RDyNucoxtKXriLR+4Xi
u4+pyj5ukYP1JqpB3ZobY/XZgCnJMye+7xeTpIDJ1LPORxM3NNAElyb26lxAK2P+
km+EpI0Zzz6rNSCfg5jYQ474+e/GBgaSG4MlaPoZ+XAfN46u1Xjjv1/AkkA4IA6m
5zP5og=3D=3D
=3D3NUt
-----END PGP PUBLIC KEY BLOCK-----

--------------130DEFEAF385F9D2F7754364--

--kdH3TJxgFep85VqxqtldwGOxUxWSjr95F--

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJZppmfAAoJEMDeajWKOdxmrk8P/1+CRYxZ3QZN8Mm1KDB/e8qx
DjTBDoJnVIQSNk8wKUQrt4MabAMNUBG6hBuL+VcDbQ7K19bPDz08rKUDhiDwFHAW
L5nSv0EOQfT/r4up1lY3wkzUUJRZLj14YVk/DgZltgHxrz63VLnHy6V0Vm4tCPQ1
1b9aJY67/8PJ9zRYKoTriOq8reeebEeqTCz5tDS8nlIxahstPMMoWCrt7L20OSrn
tQdTn97pZIzdiR6ULWUBENdzW+5EKWeNUlc1OcxCMqCyCclctCXU6WTGi+upfthk
B9xPyb5vzpMiUqyoTD6CwNSn4+UrtdjL7qZoAJW1zjcczgFlefJo2G/BYT/cgK8A
4SmZMn/gQ2oaVcFlUuqDZf82wGDvqaWvNLLjC7ctaGMc+mRBmOr8cFJoAhCO3EMO
nDj3Sx1jacVwh5HTuW0rkXlJEcT5Qf2AMU8dKqOYpiLJ/cP9NieC2y//PfPcXkID
MsMCm8vCZ9As+phq/BDBy/K2+brtD/IJN4J9JaO1czH8O/RX1U6PLX8adADJWvDI
GL/51//2YciKz6iT5qCgBy/nzuN9ZkNwsY8NHxgYf0eRRa9wmVvIDIOFAbilsgVF
IPIndvakwxpflUWJ93SEMEXG1cm3wraIWkxvgx2HP33zQARwCynPOpvB3hWs2yUY
qzZpMw0gKoTaBBppvw2A
=Jsov
-----END PGP SIGNATURE-----

--UkpaJf7op9RwpXffTxWmLDPqCwTptcxOI--


From nobody Wed Aug 30 04:45:12 2017
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1230913301D; Wed, 30 Aug 2017 04:45:10 -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, RCVD_IN_DNSWL_LOW=-0.7, WEIRD_PORT=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yhSC_DY9RqIz; Wed, 30 Aug 2017 04:45:07 -0700 (PDT)
Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D044132E94; Wed, 30 Aug 2017 04:45:07 -0700 (PDT)
Received: from [IPv6:2003:cd:6bcc:5600:855c:fc83:a144:ed84] (p200300CD6BCC5600855CFC83A144ED84.dip0.t-ipconnect.de [IPv6:2003:cd:6bcc:5600:855c:fc83:a144:ed84]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 09004721BBD31; Wed, 30 Aug 2017 13:45:02 +0200 (CEST)
From: Michael Tuexen <tuexen@fh-muenster.de>
Message-Id: <F05D0F1F-47E2-4477-BFD9-F0119A4609FC@fh-muenster.de>
Content-Type: multipart/signed; boundary="Apple-Mail=_FF631798-8A71-4239-A470-995FA44C095B"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [OPS-DIR] Opsdir last call review of draft-ietf-tsvwg-sctp-ndata-12
Date: Wed, 30 Aug 2017 13:45:01 +0200
In-Reply-To: <1a39dff3-55a9-fe1d-7e19-a0fbd0b2751b@restena.lu>
Cc: ops-dir@ietf.org, tsvwg@ietf.org, ietf@ietf.org, draft-ietf-tsvwg-sctp-ndata.all@ietf.org
To: Stefan Winter <stefan.winter@restena.lu>
References: <150287547583.12471.9085655210334710687@ietfa.amsl.com> <FDCFFA8C-8828-4578-A66E-A1AD7FF9BDC9@fh-muenster.de> <1a39dff3-55a9-fe1d-7e19-a0fbd0b2751b@restena.lu>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/foy2rffMCQ0-H-DN8HF_be3eAlI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 30 Aug 2017 11:45:10 -0000

--Apple-Mail=_FF631798-8A71-4239-A470-995FA44C095B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On 30. Aug 2017, at 12:55, Stefan Winter <stefan.winter@restena.lu> =
wrote:
>=20
> Hi,
>=20
>>> The chapter IANA considerations mentions four bits to be registered: =
E,B,U,I.
>>> In the main body, only three of those are actually defined and used =
(End of
>>> fragmented message, Beginning of fragmented message, =
Unordered/Ordered
>>> message). Please add a definition of the I bit or remove the IANA =
registration
>>> request for that bit.
>> The I bit is defined in RFC 7053 and that is the reason why we state
>> "DATA chunk defined in [RFC4960]and [RFC7053]". In addition to that =
it is
>> not mentioned (in contrast to the U, B and E bit), since the delaying =
of the
>> SACK is not specific to the I-DATA chunk.
>>=20
>> I have added the following text to the body of Section 2.2:
>>=20
>> <t>The handling of the I bit for the I-DATA chunk corresponds to the =
handling
>> of the I bit for the DATA chunk described in <xref =
target=3D'RFC7053'/>.</t>
>>=20
>> to improve the description of the I bit. See
>> =
https://github.com/sctplab/sctp-idata/commit/f16308ffe0e67ce5deb957bd40c25=
c5a0e691b82
>> Does that address your issue?
>=20
> Yes, thank you.
There has also been added a description of all fields, since this issue =
came
up multiple times. See
=
https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?input=3D&url=3Dhttps%3A=
%2F%2Fraw.githubusercontent.com%2Fsctplab%2Fsctp-idata%2Fmaster%2Fdraft-ie=
tf-tsvwg-sctp-ndata.xml&modeAsFormat=3Dhtml%2Fascii&type=3Dtowindow&Submit=
=3DSubmit
>=20
>=20
>>> And the rest are only musings not needing any action if the authors =
don't want
>>> to action on them:
>>>=20
>>> The introduction presents a good use case, quoting: "e.g., when the
>>> transmission of an urgent
>>>  message is blocked from transmission because the sender has started
>>>  the transmission of another, possibly large, message".
>>>=20
>>> The later queueing example in figure 1 has three SIDs being queued
>>> simultanseously. It is not clear which of those "has already =
started" and which
>> There is actually one message queued for stream 0, three messages for =
stream 1,
>> and one message for stream 2.
>>> are the important ones being delayed. For a better understanding of =
the reader,
>> The figure is about in which sequence they are put on the wire. So no
>> transmission has startet. This examples also does not deal with the =
case
>> of one stream having a higher priority than another. That would be an
>> example using a priority scheduler. This examples illustrates the =
round
>> robin scheduler.
>> The point here is that a single scheduler (the round robin scheduler, =
for
>> example) behaves differently when user message interleaving is used =
or not.
>> That is an important point: You can even use the schedulers with =
regular
>> DATA chunk, i.e. with user message interleaving being negotiated.
>>> it might be useful to revise the figure so that the head-of-line =
blocking
>>> happens for SID 1 because transmission of  0 and 2 has already =
started (and
>>> declare SID 1 to be the "important" message). The ASCII art would =
just have to
>>> indent SID 1 content a bit (placing 0 and 2 earlier in time), and =
the resulting
>>> serialisation would then put all the SID 1 messages at the very end, =
when 0 and
>>> 2 have been completely submitted (right?).
>> One could think about adding another example based on the priority =
scheduler
>> and giving stream 1 a higher priority. But for illustrating the point =
of
>> schedulers behaving differently depending on the negotiation of user =
message
>> interleaving this seems not necessary.
>=20
> That second example might indeed be useful.
>=20
> It's simply a bit strange that in the introduction you speak about an
> "urgent" message (something deserving a higher-priority sending) and
> that another transmission has already started - but then the example =
has
> none of those two.
What about removing the word "urgent" from that sentence.
>=20
> In fact I wonder why you speak about urgent things in the introduction
> at all. Neither the scheduler nor the interleaving are designed to =
help
> urgent things to be sent earlier.
>=20
> All they do is make the transmission fairer so that *all* chunks get a
> more even serialised distribution on the wire.
That is not true in general. If you use the priority scheduler, one
stream gets preferred treatment. It also makes sure that the time
of a message spent in the stream queue is shorter. So these messages
get sent earlier.
In the case of the round robin scheduler, you are right that this is
about getting fairer treatment. If you take the WFQ scheduler, the
streams don't get the same treatment, but it depends on the weight
given to the stream.
>=20
> So, rather than saying that the spec helps urgent things to be sent
> earlier, it should maybe rather state that the spec helps every =
message
> getting an equal, and equally distributed, share of the medium.
It is not meant that the spec does this. It was one example, what
a particular stream scheduler does. But there are multiple schedulers
defined in the document.

The RR scheduler example is not intended to illustrate what you can do
with all the schedulers, but that using message interleaving or not
has an impact on the scheduler. That is meant by stating:

This document also defines several stream schedulers for general SCTP =
associations.
The stream schedulers may behave differently depending on whether user =
message
interleaving has been negotiated for the association or not.

This is followed by illustrating this using the RR scheduler.

Best regards
Michael
>=20
>>> In 2.2.3, is there any particular reason why the "protocol =
violation" error
>>> cause is only a MAY? As it enables debugging on the remote end, a =
SHOULD seems
>>> useful.
>> This is for consistency with other SCTP specifications. There is =
always the balance
>> between providing more information to help diagnosing the problem and =
providing more
>> information to an attacker. This allows implementers to do what they =
prefer.
>> For interoperability it is not important if the error cause is =
included or not.
>=20
> That's fine, thanks.
>=20
> Greetings,
>=20
> Stefan
>=20
> --=20
> Stefan WINTER
> Ingenieur de Recherche
> Fondation RESTENA - R=C3=A9seau T=C3=A9l=C3=A9informatique de =
l'Education Nationale et de la Recherche
> 2, avenue de l'Universit=C3=A9
> L-4365 Esch-sur-Alzette
>=20
> Tel: +352 424409 1
> Fax: +352 422473
>=20
> PGP key updated to 4096 Bit RSA - I will encrypt all mails if the =
recipient's key is known to me
>=20
> http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xC0DE6A358A39DC66=

>=20
> <0x8A39DC66.asc>


--Apple-Mail=_FF631798-8A71-4239-A470-995FA44C095B
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIQkDCCBNUw
ggO9oAMCAQICCFBOxvU9EbRkMA0GCSqGSIb3DQEBCwUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQK
ExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMw
IQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0xNDA3MjIxMjA4MjZaFw0xOTA3
MDkyMzU5MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdE
Rk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAx
BAuZgeKmFNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84Ik
Q4wcOItqaACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVg
Te3RCSMqljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sW
VlZDz+HVEz2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjggGG
MIIBgjAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1Ud
IwQYMBaAFDHDeRu69VPXF+CJei0XbAqzK50zMBIGA1UdEwEB/wQIMAYBAf8CAQIwYgYDVR0gBFsw
WTARBg8rBgEEAYGtIYIsAQEEAgIwEQYPKwYBBAGBrSGCLAEBBAMAMBEGDysGAQQBga0hgiwBAQQD
ATAPBg0rBgEEAYGtIYIsAQEEMA0GCysGAQQBga0hgiweMD4GA1UdHwQ3MDUwM6AxoC+GLWh0dHA6
Ly9wa2kwMzM2LnRlbGVzZWMuZGUvcmwvRFRfUk9PVF9DQV8yLmNybDB4BggrBgEFBQcBAQRsMGow
LAYIKwYBBQUHMAGGIGh0dHA6Ly9vY3NwMDMzNi50ZWxlc2VjLmRlL29jc3ByMDoGCCsGAQUFBzAC
hi5odHRwOi8vcGtpMDMzNi50ZWxlc2VjLmRlL2NydC9EVF9ST09UX0NBXzIuY2VyMA0GCSqGSIb3
DQEBCwUAA4IBAQBjICj9nCGGcr45Rlk5MiW8qQGbDczKfUGchm0KbiyzE1l1sTOSG2EnFv/DstU1
gvuEKgFJvWa7Zi+ywgZdbj9u4wFaW8pDY1yVtuExpx/VB19N5mWCTjL5w3x6S81NXHTuIfJ1AuxS
PtLJatOQI25JZzW+f01WpOzML8+3oZeocj7JvEDWWqQIPda8gsO3tzKOsSyOam23NQIZz/U5RFhj
pyQAELC7/E6vbi84u6VXST/YblBvLJeW3B1GmmWJz67M8uXZn1OzPqEvkqnYC8aEHwTG6x7on321
e6UC8STFJGMRNMxakyAqeYg6JUKQqWU7fIbTEhUjKfws2sw5W1QXMIIFojCCBIqgAwIBAgIHF6Qk
oQlIMzANBgkqhkiG9w0BAQsFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQ
MA4GA1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4X
DTE0MDUyNzE0NTQwOVoXDTE5MDcwOTIzNTkwMFowgcYxCzAJBgNVBAYTAkRFMRwwGgYDVQQIExNO
b3JkcmhlaW4tV2VzdGZhbGVuMREwDwYDVQQHEwhNdWVuc3RlcjEgMB4GA1UEChMXRmFjaGhvY2hz
Y2h1bGUgTXVlbnN0ZXIxIzAhBgNVBAsTGkRhdGVudmVyYXJiZWl0dW5nc3plbnRyYWxlMR0wGwYD
VQQDExRGSCBNdWVuc3RlciBDQSAtIEcwMTEgMB4GCSqGSIb3DQEJARYRY2FAZmgtbXVlbnN0ZXIu
ZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4eWyu8GzsIv0iowf2v/9BT0SmCFNX
/eyQe5BncOk1j6XIlY5bnNu1S5uBe3uVgekgTh3gJyVNlaoIfCgAjqCrNJIaNQq5fr/S6L8uFeaU
O8IF/C4RH5P7f9Hn2GUueEjmJhg9CI3LBAhrfAmEEtNmuVfDycN2MjngwDNxUNRfuXbWxuhkgDqJ
0ztJeayHGhFDrGx88eyStx40xy+0c0OFWdWxzBFQlBRHnl+zRftj3c9qy6BY+/fGaA2vV1oKr3h5
X6eyU1T8YlpP1NDe4bylqAteX01sM2Qciu8UAPnNc7Sb93TQjhCFRVDIS3CdN6AOpwz5YWEld6ey
CdmFZ7pvAgMBAAGjggH+MIIB+jASBgNVHRMBAf8ECDAGAQH/AgEBMA4GA1UdDwEB/wQEAwIBBjAR
BgNVHSAECjAIMAYGBFUdIAAwHQYDVR0OBBYEFArzW7zkMYDWNUKJptPDzzfe0d/XMB8GA1UdIwQY
MBaAFEm3xs/oPR9/6kR7Eyn38QpwPt5kMBwGA1UdEQQVMBOBEWNhQGZoLW11ZW5zdGVyLmRlMIGI
BgNVHR8EgYAwfjA9oDugOYY3aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9w
dWIvY3JsL2NhY3JsLmNybDA9oDugOYY3aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9v
dC1jYS9wdWIvY3JsL2NhY3JsLmNybDCB1wYIKwYBBQUHAQEEgcowgccwMwYIKwYBBQUHMAGGJ2h0
dHA6Ly9vY3NwLnBjYS5kZm4uZGUvT0NTUC1TZXJ2ZXIvT0NTUDBHBggrBgEFBQcwAoY7aHR0cDov
L2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRwYI
KwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2Vy
dC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBCwUAA4IBAQDeRwM11kpvuRIPuzWXLapr/ZBtB76V3cuF
l45x/Kx0u03yjB4GaBPcxihn4P1z5KhRYkDBMo8HXkOgbL59aF6VdOlCurEgZvghKvUkKOCyWeYx
S9rTGPBkbGiNn2ATVuLXzF8rDf50ynAIu3otstOOv+3Ifqi1pzCva1nO64khQA5Gd5/BNyu+YHbW
f8ERAf9leu5a7yVI7cv1gCZAHpWJpkUKmfawyY4sAJ2hbGZRBvdACOxrfbuMdSOzPneT2rlmvH+D
7M6DmzVabLYk6UtAxQhldd/T/qsHkWvaWXHt0Eb9STs2Fl03Ls7M3NyLQLhaeR3ysNURYcaEfaB+
lxN+MIIGDTCCBPWgAwIBAgIHG5mIdDexozANBgkqhkiG9w0BAQsFADCBxjELMAkGA1UEBhMCREUx
HDAaBgNVBAgTE05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQK
ExdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVu
dHJhbGUxHTAbBgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBm
aC1tdWVuc3Rlci5kZTAeFw0xNjA3MDQwNzA2MTNaFw0xOTA3MDQwNzA2MTNaMHwxCzAJBgNVBAYT
AkRFMSAwHgYDVQQKDBdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEyMDAGA1UECwwpRmFjaGJlcmVp
Y2ggRWxla3Ryb3RlY2huaWsgdW5kIEluZm9ybWF0aWsxFzAVBgNVBAMMDk1pY2hhZWwgVHVleGVu
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzJoaUG3Zm24XxA/zNg2sbFcL56w8xqMg
+X6G7UsYec3YEncnlkw3jgE5nDefos7UVoCA7wPjFTj8AQt5xfpXElnbM45IPy5Ng7g6dS7biGSM
VRACPXe1PrjgApRAwwGmCPvALnZXkmKP6Zlf+3VLfz9YWIIaeKu3jFM2Lk6Y3gr5U1l8bjHSawOo
WMlfvSsXXLT38zKW7Uz9jS278j0OqHANBPgsE6/LJoCWFInwlvybxhO3nGU7OteUGaPikqzvjLsL
YgpHDi0WjMZfVx/UtUSzZ4EJvmJTBeuVwyKnCbrawnfwYPTQQ6VE1OkAzmsMByBbEwJ996RtG//T
XCG06QIDAQABo4ICRzCCAkMwQAYDVR0gBDkwNzARBg8rBgEEAYGtIYIsAQEEAwUwEQYPKwYBBAGB
rSGCLAIBBAMBMA8GDSsGAQQBga0hgiwBAQQwCQYDVR0TBAIwADAOBgNVHQ8BAf8EBAMCBeAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBTQHa9qhKgSZgCCAPThZkXaEaJ/
dTAfBgNVHSMEGDAWgBQK81u85DGA1jVCiabTw8833tHf1zAgBgNVHREEGTAXgRV0dWV4ZW5AZmgt
bXVlbnN0ZXIuZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2Zo
LW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZu
LmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIHXBggrBgEFBQcBAQSByjCBxzAz
BggrBgEFBQcwAYYnaHR0cDovL29jc3AucGNhLmRmbi5kZS9PQ1NQLVNlcnZlci9PQ1NQMEcGCCsG
AQUFBzAChjtodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jYWNlcnQv
Y2FjZXJ0LmNydDBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDIucGNhLmRmbi5kZS9maC1tdWVuc3Rl
ci1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQELBQADggEBAEj2/6x4kzoCVIiu
aaminPrOHxACyoYsmSRjYPQpgW5xRj/FlolO1nG+ZZ11sqTb3TdCGD69ko5/zs8eGKnv/i0VLCHF
g1JLfpaxElN5RrR/cqRJrbzKshF9aUkBODF8vlf9BCeimMK3fifjbbWRyxHssfEECffujD7/Yvta
NYMO46Roz39lIK2s37IVFq3V5RWzUeTuwpP9t8lOxirOi9eK2OYI/dh0HjR2S5Dr9nMR1dNulrhz
jlFxGc+opefGScrRR9Ec0eqTXlbt1Q9UzNIYVS+OGZY8/bBbprwXVTmwSp8dygEULkIaMbLsaTaW
6TehuL8ousPJkL52SOENgSkxggQpMIIEJQIBATCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozAJBgUrDgMCGgUAoIICKzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0xNzA4MzAxMTQ1MDJaMCMGCSqGSIb3DQEJBDEWBBRkMHobf1qZykVt8aCe
YzqYlK6B0zCB4wYJKwYBBAGCNxAEMYHVMIHSMIHGMQswCQYDVQQGEwJERTEcMBoGA1UECBMTTm9y
ZHJoZWluLVdlc3RmYWxlbjERMA8GA1UEBxMITXVlbnN0ZXIxIDAeBgNVBAoTF0ZhY2hob2Noc2No
dWxlIE11ZW5zdGVyMSMwIQYDVQQLExpEYXRlbnZlcmFyYmVpdHVuZ3N6ZW50cmFsZTEdMBsGA1UE
AxMURkggTXVlbnN0ZXIgQ0EgLSBHMDExIDAeBgkqhkiG9w0BCQEWEWNhQGZoLW11ZW5zdGVyLmRl
AgcbmYh0N7GjMIHlBgsqhkiG9w0BCRACCzGB1aCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozANBgkqhkiG9w0BAQEFAASCAQDDqGNKrr1j9YYwYMsgmX0nYC+yhSSxEPLm
5YotD9ZztKAFEGOA/GUwhq2ZwFviBJczpdPgbpEHIbSJLTdBKeEnTQOPMzH/B/HmWMS9vpuimXwi
HgLZiUItCjb38Bu58Gor1ssogXnoja5sDpPnJHgNrGp6xxvjhnchHpiUh61tP6XgjYVLYWwXn3Ga
63G7ateUCQ0MOKHqCvdQeNblBqNXAgKW8eOqeEpfyUN8sGt+lkNGGaIY+WWpd2+xgVRXKX95lGzI
eZDkru8vBoCWdxhrSmOYRPrU2p+4GG4AzRlckDPG48b6AzhSswV+WUaibvvr1mNJ1gUb3aBDisi5
mmsKAAAAAAAA
--Apple-Mail=_FF631798-8A71-4239-A470-995FA44C095B--


From nobody Wed Aug 30 05:44:08 2017
Return-Path: <liushucheng@huawei.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C92A1331A7; Wed, 30 Aug 2017 05:44:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Will LIU <liushucheng@huawei.com>
To: <ops-dir@ietf.org>
Cc: draft-ietf-sidr-rpki-validation-reconsidered.all@ietf.org, ietf@ietf.org,  sidr@ietf.org
Subject: Opsdir last call review of draft-ietf-sidr-rpki-validation-reconsidered-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.59.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150409704619.21582.12831904999110291317@ietfa.amsl.com>
Date: Wed, 30 Aug 2017 05:44:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/i-nDAEBi_Q-I4kNj65-3TSOeUVg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 30 Aug 2017 12:44:06 -0000

Reviewer: Will LIU
Review result: Ready

I have reviewed draft-ietf-sidr-rpki-validation-reconsidered-08 as part of the
Operational directorate's ongoing effort to review all IETF documents being
processed by the IESG.  These comments were written with the intent of
improving the operational aspects of the IETF drafts. Comments that are not
addressed in last call may be included in AD reviews during the IESG review.
Document editors and WG chairs should treat these comments just like any other
last call comments.

"This document specifies an alternative to the certificate validation procedure
specified in RFC 6487 that reduces aspects of operational fragility in the
management of certificates in the RPKI, while retaining essential security
features. The use of this updated procedure is signalled by form of a set of
alternative Object Identifiers (OIDs) indicating that the alternative version
of RFC 3779 X.509 Extensions for IP Addresses and AS Identifiers, and
certificate policy for the Resource Public Key Infrastructure (RFC 6484)
defined in this document should be used. Furthermore this document provides an
alternative to ROA↓ (RFC 6482), and BGPSec↓ Router Certificate (BGPSec↓ PKI
Profiles - publication requested) validation."

My overall view of the document is 'Ready' for publication.

One small comment is that we usually add a section for terminology for such a
document with so many terms. This can also solve the issue that some of the
acronyms were not given the full name.



From nobody Wed Aug 30 08:22:09 2017
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B0961326FE; Wed, 30 Aug 2017 08:22:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Matthew Miller <linuxwolf+ietf@outer-planes.net>
To: <secdir@ietf.org>
Cc: draft-ietf-teas-pce-central-control.all@ietf.org, ietf@ietf.org, teas@ietf.org
Subject: Secdir last call review of draft-ietf-teas-pce-central-control-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.59.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150410652452.21632.6924902183838903689@ietfa.amsl.com>
Date: Wed, 30 Aug 2017 08:22:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rmxhmKCnWKdJe_VAEfmkwhoP9PE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 30 Aug 2017 15:22:05 -0000

Reviewer: Matthew Miller
Review result: Has Nits

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should
treat these comments just like any other last call comments.

Document:
Reviewer: Matthew A. Miller
Review Date: 2017-08-30
IETF LC End Date: 2017-08-25
IESG Telechat date: 2017-08-31

Summary:

This document is ready for publication as Informational, with one potential nit.

This document describes an overall architecture (with some variants) utilizing
central PCE-based controller for SDN, and its implication on PCEP.  The
document notes the tradeoffs between the variants, including some of the
vulnerabilities.

My nit is in the Security Considerations; I'm not sure how likely in practice
a central controller architecture will be operated with "higher level of
security", and therefore not sure it's worth calling out like this.

I can see how a central controller makes management easier, and that has a
potential benefit of better visibility into the network's operation and
finding problems (including security-related) sooner and better.

Otherwise I think the rest of this section addresses the concerns that a
central controller architecture has.



From nobody Wed Aug 30 09:51:31 2017
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44596126BFD; Wed, 30 Aug 2017 09:51:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 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, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xoxDCKovLZ3m; Wed, 30 Aug 2017 09:51:28 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20D8413213D; Wed, 30 Aug 2017 09:51:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6043; q=dns/txt; s=iport; t=1504111887; x=1505321487; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=/X+PjXpR0lZ2Lj+XfP6za0CNkhSUnSS4mmFboWuR9zk=; b=ksR1vxhgWkUTkUQjmVmJl5rh6emjnlWzwcafsVNHoTal0eBd3UxBb6E9 lJvCDH+DUgwYKF6nczB3D+FhZX83vk9XGLCJkJ6yM3FhWDcFmMqegJQB7 tuKqjqh8O9kEumVjRjdUQIug5sa13SioSGQOrQfK+26TmnlUJj/0ccYDg k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BxAgAj7KZZ/xbLJq1eGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBiUqLEqlQhUcChGoUAQIBAQEBAQEBayiFGQYjFTgJEAsaAiYCAlcGAQw?= =?us-ascii?q?IAQEXihascoIni0IBAQEBAQEBAQEBAQEBAQEBASGBDYIdg1CBYyuBcIENiAiCY?= =?us-ascii?q?QEEigiWZIg5jBOCEoVng1mHGY1QiHM2IYENMiEIHBWFYRyBaT6LQgEBAQ?=
X-IronPort-AV: E=Sophos;i="5.41,449,1498521600"; d="scan'208";a="657131680"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Aug 2017 16:51:22 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v7UGpMkM029954; Wed, 30 Aug 2017 16:51:22 GMT
Subject: Re: [OPS-DIR] Opsdir last call review of draft-ietf-tsvwg-sctp-ndata-12
To: Michael Tuexen <tuexen@fh-muenster.de>, Stefan Winter <stefan.winter@restena.lu>
Cc: ops-dir@ietf.org, draft-ietf-tsvwg-sctp-ndata.all@ietf.org, tsvwg@ietf.org, ietf@ietf.org, IESG IESG <iesg@ietf.org>
References: <150287547583.12471.9085655210334710687@ietfa.amsl.com> <FDCFFA8C-8828-4578-A66E-A1AD7FF9BDC9@fh-muenster.de> <1a39dff3-55a9-fe1d-7e19-a0fbd0b2751b@restena.lu> <F05D0F1F-47E2-4477-BFD9-F0119A4609FC@fh-muenster.de>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <f4d121e4-44f5-e85d-98b1-bbea317a7539@cisco.com>
Date: Wed, 30 Aug 2017 18:51:21 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <F05D0F1F-47E2-4477-BFD9-F0119A4609FC@fh-muenster.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uQZGTbWRI87ReRXQ2HQKkXr8hFk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 30 Aug 2017 16:51:30 -0000

Michael,

I stumbled on the same point as Stefan.

First of, I had to review RFC4960 for TSN/SSN. I was not sure whether 
TSN was per stream or not
It would have helped me to repeat this information in the intro.
Ok, to be candid, I deduced this information from figure 1 and 2.
>>
>>>> And the rest are only musings not needing any action if the authors don't want
>>>> to action on them:
>>>>
>>>> The introduction presents a good use case, quoting: "e.g., when the
>>>> transmission of an urgent
>>>>   message is blocked from transmission because the sender has started
>>>>   the transmission of another, possibly large, message".
>>>>
>>>> The later queueing example in figure 1 has three SIDs being queued
>>>> simultanseously. It is not clear which of those "has already started" and which
>>> There is actually one message queued for stream 0, three messages for stream 1,
>>> and one message for stream 2.
>>>> are the important ones being delayed. For a better understanding of the reader,
>>> The figure is about in which sequence they are put on the wire. So no
>>> transmission has startet. This examples also does not deal with the case
>>> of one stream having a higher priority than another. That would be an
>>> example using a priority scheduler. This examples illustrates the round
>>> robin scheduler.
>>> The point here is that a single scheduler (the round robin scheduler, for
>>> example) behaves differently when user message interleaving is used or not.
>>> That is an important point: You can even use the schedulers with regular
>>> DATA chunk, i.e. with user message interleaving being negotiated.
This was my source of confusion.
With figure 1 and figure 2, you want to show the effect of Round Robin 
Scheduler with and without User Message Interleaving, while we were 
expecting the figure 2 to be the solution from this spec. Hence Stefan 
and I were looking for this "urgent message" in figure 2.

>>>> it might be useful to revise the figure so that the head-of-line blocking
>>>> happens for SID 1 because transmission of  0 and 2 has already started (and
>>>> declare SID 1 to be the "important" message). The ASCII art would just have to
>>>> indent SID 1 content a bit (placing 0 and 2 earlier in time), and the resulting
>>>> serialisation would then put all the SID 1 messages at the very end, when 0 and
>>>> 2 have been completely submitted (right?).
>>> One could think about adding another example based on the priority scheduler
>>> and giving stream 1 a higher priority. But for illustrating the point of
>>> schedulers behaving differently depending on the negotiation of user message
>>> interleaving this seems not necessary.
>> That second example might indeed be useful.
>>
>> It's simply a bit strange that in the introduction you speak about an
>> "urgent" message (something deserving a higher-priority sending) and
>> that another transmission has already started - but then the example has
>> none of those two.
Exactly.
Please add this extra example.
This would also clarify from the introduction that when you write ...

    The sending of such large messages over
    SCTP as specified in [RFC4960] can result in a form of sender side
    head of line blocking (e.g., when the transmission of an urgent
    message is blocked from transmission because the sender has started
    the transmission of another, possibly large, message).

.. the notion of transmission urgency is not within a stream but across 
streams, and that can be achieved with a priority scheduler.
The text might have to be rephrased to explain that this spec provides 
the ability to create stream scheduler with different relative stream 
treatments.
And also that urgent message would be placed in this high priority 
stream scheduler (reliable, I guess, but that's orthogonal) stream.
> What about removing the word "urgent" from that sentence.
>> In fact I wonder why you speak about urgent things in the introduction
>> at all. Neither the scheduler nor the interleaving are designed to help
>> urgent things to be sent earlier.
>>
>> All they do is make the transmission fairer so that *all* chunks get a
>> more even serialised distribution on the wire.
> That is not true in general. If you use the priority scheduler, one
> stream gets preferred treatment. It also makes sure that the time
> of a message spent in the stream queue is shorter. So these messages
> get sent earlier.
> In the case of the round robin scheduler, you are right that this is
> about getting fairer treatment. If you take the WFQ scheduler, the
> streams don't get the same treatment, but it depends on the weight
> given to the stream.
>> So, rather than saying that the spec helps urgent things to be sent
>> earlier, it should maybe rather state that the spec helps every message
>> getting an equal, and equally distributed, share of the medium.
> It is not meant that the spec does this. It was one example, what
> a particular stream scheduler does. But there are multiple schedulers
> defined in the document.
>
> The RR scheduler example is not intended to illustrate what you can do
> with all the schedulers, but that using message interleaving or not
> has an impact on the scheduler. That is meant by stating:
>
> This document also defines several stream schedulers for general SCTP associations.
> The stream schedulers may behave differently depending on whether user message
> interleaving has been negotiated for the association or not.
>
> This is followed by illustrating this using the RR scheduler.
>
> Best regards
Also, I don't see the value of the last sentence in this paragraph, 
especially with RFC2119 MAY.

    This section defines several stream schedulers.  The stream
    schedulers may behave differently depending on whether user message
    interleaving has been negotiated for the association or not.  An
    implementation MAY implement any subset of them.


Regards, Benoit


From nobody Wed Aug 30 10:21:10 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 07793132386; Wed, 30 Aug 2017 10:21:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-opsawg-mud.all@ietf.org, opsawg@ietf.org, ietf@ietf.org
Subject: Genart early review of draft-ietf-opsawg-mud-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.59.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150411366399.21627.17047458871931107094@ietfa.amsl.com>
Date: Wed, 30 Aug 2017 10:21:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/f4RHYIOLhap5dURRiFFDWJ3n-jg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 30 Aug 2017 17:21:04 -0000

Reviewer: Robert Sparks
Review result: Almost Ready

This is an exciting concept, and the draft overall is approachable. I
have identified a few areas I think need more detail, and have a 
longish list of nits (please don't take that to be negative).

==Issues==

I find the structure of the introduction unclear. Please consider
reworking it.  I would suggest even more succinctly listing goals and
constraints, and then intended applicability (these things are in the
current text, but I think you can render them much more efficiently). In
particular, the argument that implementers of things are incented only to
provide the minimal amount of behavior to get their thingyness could be
more strongly highlighted.

The document proposes "reputation services". It needs more words about
whether those exist, and what scopes the architecture imagines (an
enterprise might have a different idea of a reputation service than a
residence). There is a notion of "decent web reputations" in the security
considerations section. Who determines that? The security considerations
section should talk about attacks against the reputation services.

In the first paragraph of Section 2, it's not clear if you are trying
to restrict the models to only those in the two documents in the list
following the paragraph. 

I am not a YANG doctor, so this may be in the weeds, but it feels like
there's a discrepancy between the diagram at the end of section 2 and the
element definitions in section 3. In particular 3.7 doesn't seem to align
with what the diagram or the example in Appendix B uses. Should you be 
defining "from-device-policy" and "to-device-policy" instead of
"packet-direction"? (I'm wondering if 3.7 reflects an older design?)

At section 3.13, the description of my-controller is not quite right.
This bit signals to the mud controller to use a mapping that it knows
about or creates. Something else established that class (and maybe gave
it a name). I talked about this with Eliot and he has a better 
description to use.

It's not clear to me that this is a good use of .well-known. I suggest
getting an expert review on the proposed usage. (I had a quick 
conversation with Mark Nottingham and got some initial feedback that 
I'm passing along here. I'm sure there's more that an in-depth review
would identify.) Why wouldn't a URI template (RFC6570) do the job? 
Rather than use RFC3986's query, consider pointing to HTML5 (which
would bring the more familiar key=value format). 

The document needs to say more about how HTTP is used. I assume you only
intend to use GET, and that you expect redirects to be followed, and that
nothing special needs to be considered with caching? The document needs
to be explicit about it. Take a look at 
<https://mnot.github.io/I-D/bcp56bis/>. (There's been some conversation
about it on the art list, so Eliot, at least, is already aware of it - 
see <https://mailarchive.ietf.org/arch/search/?q=bcp56bis>)

I think there needs to be more discussion of the PKI used for signing MUD
files.

Consider discussing whether the stacks used by typical things will let
them add DHCP options (or include bits in the other protocols being 
enabled). If it's well known (I can't say) that these stacks typically
_won't_ provide that functionality, then you should punch up the
discussion of the controllers mapping other identifiers to MUD URLs on
behalf of the thing.

You suggest the DHCP Client (which is a thing) SHOULD log or report 
improper acknowledgments from servers. That's asking a bit much from
a thing. I suspect the requirement is unrealistic and should be removed
or rewritten to acknowledge that things typically won't do that.

The security and deployment considerations sections talk about what the
need for coordination if control over the domain name used in the URL
changes. It should talk more about what happens if the new administration
of the domain is not interested in facilitating a transition (consider
the case of a young company with a few thousand start-up-ish things out
there that loses a suit over its name). Please discuss whether or not
suddenly losing the MUD assisted network configuration is expected to
leave the devices effectively cut-off. 

Right now, you leave the DHCP server (when it's used) responsible for
clearing state in the MUD controller. Please discuss what happens when
those are distinct elements (as you have in the end of section 9.2) and
the DHCP server reboots. Perhaps it would make sense for the DHCP server
to hand the length of the lease it has granted to the MUD controller and
let the MUD controller clean up on its own?

The document currently suggests that a piece of software inspect the
WHOIS database to see if registration ownership of a domain has changed.
Do you really mean software, or should this be advice to the
administrator of the controller instead? 

==Nits==

I recommend an editorial pass focusing on simplifying sentences. Look
particularly where the word "therefore" is used and consider
restructuring the surrounds. (It is used non-sequitur in a couple of
places). Be careful to call out actors explicitly (I note the places 
that particularly caught my eye below).

Some specific nits:

The abstract speaks only about properties of MUD but does not describe
what MUD _is_, or is good for. A few more words here would help.

Next to last paragraph of section 1 (before 1.1): A means for _who_ to
retrieve the description? (Consider rendering the three list elements on
their own lines.)

The last sentence of section 1 treats "enterprise networks" more
specially than it intends, I think. Why couldn't _any_ network do this?
Could the sentence be reworded to make it clear that enterprise networks
are an example?

First sentence of 1.1: Perhaps you mean "general purpose computing
devices" instead of "general computing"? "their" has an unclear
antecedent.

Last paragraph of 1.3: It's unclear what "such an approach" is intended
to point to. Would "a general solution that required capabilities their
particular device would not use" make more sense?

First paragraph of 1.5: "might to allow" is probably meant to be "might
be to allow". What does it mean for a controller to "need to speak COAP".
Do you mean "controllers capable of speaking COAP"?

Fourth paragraph of 1.5 at the discussion of time and effort: Consider
rephrasing this to focus on the result of the time and effort (high
quality) rather than the time and effort itself.

In the list of abstractions at the end of 1.5, you have three things you
describe as devices and one thing you describe as a class. You later talk
about the abstractions you've described as devices as classes. At this
point in the document what you mean by "class" has not been made as
explicit as it could be.

Section 1.8, item 3: the MUD file doesn't have hosts in it (it has
identifiers of some kind). Consider being more explicit about what
you mean by testing that against a reputation service.

Section 3.1: You say "Which turn was taken". I think you meant
"Which, in turn, was taken". Consider deleting "for those keeping score".

Section 3.3 is missing a word at "the location any MASA service"?

I found the prose in the descriptions of the "manufacturer" and
"same-manufacturer" elements (3.8 and 3.9) very confusing. I think
additional prose introducing the concepts and maybe some examples would
be very useful.

What do you mean by "matches" at 3.10. Do you mean "is"?

The caution in the 2nd paragraph of 3.12 is not clear.

At section 4, consider pointing out that you are not allowing 
DHCP by default, and that devices that are expected to use DHCP
need to have an explicit allow in their MUD file. 

The description of the manufacturer leaf in the MUD YANG model
could be made more useful.

Provide a reference for "giaddr" when you use it in section 9.2.

Section 14, 2nd paragraph: additional segmentation of what?

Second paragraph of Section 15 - it would help to be more precise
with agency. _Who_ should review the class?

In the security considerations section, when you get to the "if for some
reason it is not possible to determine whether ownership has changed",
_who_ are you suggesting conduct further review?

==Micro-nits==

1,$s/enorcement/enforcement/g

s/autjors/authors/




From nobody Wed Aug 30 11:11:25 2017
Return-Path: <afarrel@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7FDC1326EA; Wed, 30 Aug 2017 11:11:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=juniper.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TWIR_MLUpWMf; Wed, 30 Aug 2017 11:11:07 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0103.outbound.protection.outlook.com [104.47.38.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13A53132355; Wed, 30 Aug 2017 11:11:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=h0HId4kAMVZIL8nr6O7Pg/+aClZ8o7CakDNWAaPeiY8=; b=LYMie2bNCCtsMY9ccaSoAn3fwjcrpMgHhkpR08Zw7msKxhauHqbAFCcltUl+ZtUSDI2Pd7PeDBm/AAiE6EWagOzT82yjynFZ1F6by25xdt46uEWfxPlJMDfsvssFweYd+OCQd/IDQN71wQoZ4+ZTsG6ElHaqBVkoW6lpLHOtrVs=
Received: from CO2PR05MB971.namprd05.prod.outlook.com (10.141.226.17) by CO2PR05MB668.namprd05.prod.outlook.com (10.141.230.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.13.2; Wed, 30 Aug 2017 18:11:04 +0000
Received: from CO2PR05MB971.namprd05.prod.outlook.com ([10.141.226.17]) by CO2PR05MB971.namprd05.prod.outlook.com ([10.141.226.17]) with mapi id 15.20.0013.005; Wed, 30 Aug 2017 18:11:04 +0000
From: Adrian Farrel <afarrel@juniper.net>
To: Matthew Miller <linuxwolf+ietf@outer-planes.net>, "secdir@ietf.org" <secdir@ietf.org>
CC: "draft-ietf-teas-pce-central-control.all@ietf.org" <draft-ietf-teas-pce-central-control.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "teas@ietf.org" <teas@ietf.org>
Subject: RE: Secdir last call review of draft-ietf-teas-pce-central-control-04
Thread-Topic: Secdir last call review of draft-ietf-teas-pce-central-control-04
Thread-Index: AQHTIaO9swi/FejJaU6mn0gkr6jvyqKdMj5w
Date: Wed, 30 Aug 2017 18:11:04 +0000
Message-ID: <CO2PR05MB9715B65A021C5E6F79CECDEBB9C0@CO2PR05MB971.namprd05.prod.outlook.com>
References: <150410652452.21632.6924902183838903689@ietfa.amsl.com>
In-Reply-To: <150410652452.21632.6924902183838903689@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=afarrel@juniper.net; 
x-originating-ip: [193.110.55.10]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CO2PR05MB668; 6:PSyP2gD04QaumuEeYzOEvUMA0iErn9ngaixYAE7dlQxq8wv/0DKyO4zW7hfOjcVctZ9XkxSwSmxh7/i9VY0vil0C0uCL9krXbpsD3F7T+CYZ9RSNoUHO3SNiQdm6E9R7ORBHAnCNB3WVmuy/I3y6vwV4slljAxmuA6Zq0BnBUButxb5a+Grrus/TrSE0QhlELODWlIHFUTmzR9HqaYsI8E1e0mm2nv/Bn/y2P5THb3qvDpN5O7wukx+N4elnLG3iTftoroBXV0ZC/JfimfIi1PwlmSTh1StFaA5qEf5pHMmvaaaBP4gdI3fZB62EBjTupDhxC/SLoZcTuORl/ASP4Q==; 5:xtp7Iy1Te7cJ5qf49Moa8vSNqx+9C7fqi616E+FKusCmWV4Q5lZa04caY1Q6hN1hcEyTaWyD6AVVVf6jG7dynDSj9rlyzEyeo0/ipUqkhyAWTilxipLqDMFx6f26DkCNYfF1yk1jpi35O70PhNG02w==; 24:nSncw90/TdaNsYjubfENV9qHCEfRdAxpRaAHslUd94AvibcK22/Bd4dxcrtSz/zY0E0/v8jOObPI6O1Puhge9Ycr8H/252S2OqIC6bhNoj0=; 7:+97kWB2Vc5JwDnL62BxkSrstxOm5WVbM5vRAOwHwIRScF0+7JSQMkoxJcIxVZKmUI4R6u7KSB9MqzXEo6twckAzWiN7dncaTvL4WNufds7mWGgDSO0b5fERFERdBqJvqWr+su/Dek0MfLdnEuTjnp63spRzb/XvicNUCd21PVCdgjUOTR0bpP7UKNb3ogczr0X82efI45bdPYMgXnD/kFDsb3fqejo2Jryw23jtHxTw=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 67763ad8-6349-4e68-4dc6-08d4efd27ab7
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254152)(48565401081)(300000503095)(300135400095)(2017052603199)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:CO2PR05MB668; 
x-ms-traffictypediagnostic: CO2PR05MB668:
x-exchange-antispam-report-test: UriScan:(192374486261705);
x-microsoft-antispam-prvs: <CO2PR05MB668B11B289CAB53C491F98CBB9C0@CO2PR05MB668.namprd05.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(93006095)(93001095)(100000703101)(100105400095)(10201501046)(6055026)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(20161123558100)(20161123562025)(20161123555025)(20161123564025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:CO2PR05MB668; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CO2PR05MB668; 
x-forefront-prvs: 041517DFAB
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39860400002)(13464003)(377424004)(189002)(199003)(74316002)(97736004)(4326008)(105586002)(2906002)(106356001)(33656002)(7696004)(3660700001)(230783001)(3280700002)(229853002)(6436002)(7736002)(76176999)(77096006)(305945005)(54356999)(6506006)(50986999)(2950100002)(66066001)(101416001)(5660300001)(53546010)(68736007)(2501003)(189998001)(14454004)(99286003)(55016002)(8676002)(6116002)(3846002)(81156014)(81166006)(102836003)(9686003)(54906002)(53936002)(8936002)(478600001)(25786009)(86362001)(6246003)(2900100001); DIR:OUT; SFP:1102; SCL:1; SRVR:CO2PR05MB668; H:CO2PR05MB971.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Aug 2017 18:11:04.5367 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO2PR05MB668
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0Vilx1KlxQdNCwixl3HvQEbz6Vg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 30 Aug 2017 18:11:10 -0000

VGhhbmtzIE1hdHRoZXcsDQoNClRoZSBwb2ludCBJIHdhcyBhaW1pbmcgZm9yIGlzIHRoYXQgY29u
dHJvbCBwbGFuZXMgYXJlIG9mdGVuIG9wZXJhdGVkIHdpdGggYSAiZG9tYWluIG9mIHRydXN0IiBv
ciAiY2hhaW4gb2YgdHJ1c3QiIG1vZGVsIChmb3IgYmV0dGVyIG9yIHdvcnNlKSBidXQgdGhhdCBt
YW5hZ2VtZW50IHN5c3RlbXMgYXJlIG9mdGVuIG9wZXJhdGVkIHdpdGggc2VjdXJlIGNoYW5uZWxz
IGJldHdlZW4gbWFuYWdlbWVudCBzdGF0aW9uIGFuZCBtYW5hZ2VkIG5vZGUuDQoNCkkgdGhpbmss
IGluIG90aGVyIHdvcmRzLCB0aGF0IHRoZSBwb2ludCBjb3ZlcmVkIGJ5IHRoZSB0ZXh0IGlzIHRy
dWUgaW4gdG9kYXkncyBuZXR3b3Jrcy4NCg0KQmVzdCwNCkFkcmlhbg0KDQotLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLQ0KRnJvbTogTWF0dGhldyBNaWxsZXIgW21haWx0bzpsaW51eHdvbGYraWV0
ZkBvdXRlci1wbGFuZXMubmV0XSANClNlbnQ6IDMwIEF1Z3VzdCAyMDE3IDE2OjIyDQpUbzogc2Vj
ZGlyQGlldGYub3JnDQpDYzogZHJhZnQtaWV0Zi10ZWFzLXBjZS1jZW50cmFsLWNvbnRyb2wuYWxs
QGlldGYub3JnOyBpZXRmQGlldGYub3JnOyB0ZWFzQGlldGYub3JnDQpTdWJqZWN0OiBTZWNkaXIg
bGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLXRlYXMtcGNlLWNlbnRyYWwtY29udHJvbC0w
NA0KDQpSZXZpZXdlcjogTWF0dGhldyBNaWxsZXINClJldmlldyByZXN1bHQ6IEhhcyBOaXRzDQoN
CkkgaGF2ZSByZXZpZXdlZCB0aGlzIGRvY3VtZW50IGFzIHBhcnQgb2YgdGhlIHNlY3VyaXR5IGRp
cmVjdG9yYXRlJ3Mgb25nb2luZyBlZmZvcnQgdG8gcmV2aWV3IGFsbCBJRVRGIGRvY3VtZW50cyBi
ZWluZyBwcm9jZXNzZWQgYnkgdGhlIElFU0cuICBUaGVzZSBjb21tZW50cyB3ZXJlIHdyaXR0ZW4g
cHJpbWFyaWx5IGZvciB0aGUgYmVuZWZpdCBvZiB0aGUgc2VjdXJpdHkgYXJlYSBkaXJlY3RvcnMu
ICBEb2N1bWVudCBlZGl0b3JzIGFuZCBXRyBjaGFpcnMgc2hvdWxkIHRyZWF0IHRoZXNlIGNvbW1l
bnRzIGp1c3QgbGlrZSBhbnkgb3RoZXIgbGFzdCBjYWxsIGNvbW1lbnRzLg0KDQpEb2N1bWVudDoN
ClJldmlld2VyOiBNYXR0aGV3IEEuIE1pbGxlcg0KUmV2aWV3IERhdGU6IDIwMTctMDgtMzANCklF
VEYgTEMgRW5kIERhdGU6IDIwMTctMDgtMjUNCklFU0cgVGVsZWNoYXQgZGF0ZTogMjAxNy0wOC0z
MQ0KDQpTdW1tYXJ5Og0KDQpUaGlzIGRvY3VtZW50IGlzIHJlYWR5IGZvciBwdWJsaWNhdGlvbiBh
cyBJbmZvcm1hdGlvbmFsLCB3aXRoIG9uZSBwb3RlbnRpYWwgbml0Lg0KDQpUaGlzIGRvY3VtZW50
IGRlc2NyaWJlcyBhbiBvdmVyYWxsIGFyY2hpdGVjdHVyZSAod2l0aCBzb21lIHZhcmlhbnRzKSB1
dGlsaXppbmcgY2VudHJhbCBQQ0UtYmFzZWQgY29udHJvbGxlciBmb3IgU0ROLCBhbmQgaXRzIGlt
cGxpY2F0aW9uIG9uIFBDRVAuICBUaGUgZG9jdW1lbnQgbm90ZXMgdGhlIHRyYWRlb2ZmcyBiZXR3
ZWVuIHRoZSB2YXJpYW50cywgaW5jbHVkaW5nIHNvbWUgb2YgdGhlIHZ1bG5lcmFiaWxpdGllcy4N
Cg0KTXkgbml0IGlzIGluIHRoZSBTZWN1cml0eSBDb25zaWRlcmF0aW9uczsgSSdtIG5vdCBzdXJl
IGhvdyBsaWtlbHkgaW4gcHJhY3RpY2UgYSBjZW50cmFsIGNvbnRyb2xsZXIgYXJjaGl0ZWN0dXJl
IHdpbGwgYmUgb3BlcmF0ZWQgd2l0aCAiaGlnaGVyIGxldmVsIG9mIHNlY3VyaXR5IiwgYW5kIHRo
ZXJlZm9yZSBub3Qgc3VyZSBpdCdzIHdvcnRoIGNhbGxpbmcgb3V0IGxpa2UgdGhpcy4NCg0KSSBj
YW4gc2VlIGhvdyBhIGNlbnRyYWwgY29udHJvbGxlciBtYWtlcyBtYW5hZ2VtZW50IGVhc2llciwg
YW5kIHRoYXQgaGFzIGEgcG90ZW50aWFsIGJlbmVmaXQgb2YgYmV0dGVyIHZpc2liaWxpdHkgaW50
byB0aGUgbmV0d29yaydzIG9wZXJhdGlvbiBhbmQgZmluZGluZyBwcm9ibGVtcyAoaW5jbHVkaW5n
IHNlY3VyaXR5LXJlbGF0ZWQpIHNvb25lciBhbmQgYmV0dGVyLg0KDQpPdGhlcndpc2UgSSB0aGlu
ayB0aGUgcmVzdCBvZiB0aGlzIHNlY3Rpb24gYWRkcmVzc2VzIHRoZSBjb25jZXJucyB0aGF0IGEg
Y2VudHJhbCBjb250cm9sbGVyIGFyY2hpdGVjdHVyZSBoYXMuDQoNCg0K


From nobody Wed Aug 30 15:01:54 2017
Return-Path: <mranga@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EE9F132C2D; Wed, 30 Aug 2017 15:01: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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rjceE1cR4ltK; Wed, 30 Aug 2017 15:01:36 -0700 (PDT)
Received: from mail-wr0-x234.google.com (mail-wr0-x234.google.com [IPv6:2a00:1450:400c:c0c::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FC3113239A; Wed, 30 Aug 2017 15:01:36 -0700 (PDT)
Received: by mail-wr0-x234.google.com with SMTP id z91so21869322wrc.1; Wed, 30 Aug 2017 15:01:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+T7Q6L51NeRK1n4AjvQ2Pjs7eQdrq5lKwzJIajcHE24=; b=Yj44iPYMTTWdRUXtkzaq7eTupHmEonZSi/EmmGttlT8V41IAFr2MfwEXyaimkh5dIu EtrYNxNYLoSlDWfrOfpiBxN39sQiTurhy1uGBmtP62QnPa++6DeqSTXmdwLI5ZgXFbyH fRNxv5E+bWbw9bqfFvzY+kZL4ft/DHT5PrExv/UwEeOxY3Em4Nu7j+PxX1Zu2ZzE75+7 H3g57OplvL97dkmxtiDjMeiw6ZOAlr5RejbRln89xR6b3BY7vEO6HAgRiKPS4keFhcvU NwocAvOUC2izpniiIg05rjTIBYnt+U+6qrKJdESe2++QE1ZhAKnfeos1/x7iFTNV0kkv o5DQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+T7Q6L51NeRK1n4AjvQ2Pjs7eQdrq5lKwzJIajcHE24=; b=A8k7Re/Izo4V+PjhGB18lRIgmrXwzOq43aBu5pnitpAPgX/lOPQuSn1aZ7HEg83UYx qZpL0JkV6hb48+nulMLwplGru5ySpaLfCDKnvA1He0VOSNONZYDmYHwJ7RNr7PKLXqow TwtsSfSCflO8f0sMNku7joDdCIipNn33/fSNV0I1VHeLuiQbnKrIBjc7Afl1PKTJ1v30 jkrbe7PIpeRm4F59VxN36Due7X4J4hJt7ARW5l7skX76i1OLXHdPXy7AUlf9zuhTNuyT UO1NwGX2oM1nKzujn+4XcxOSf123B+MVE6LXVsdEx9P5pEj7W2+PTx3TGABB5fyPW4QJ r3/g==
X-Gm-Message-State: AHYfb5jxV2CZqdJXqeF2d8CeGUWnXugHP9y06vYuchG6Uy/G89rO7ZEl uGV6Tiz3IBUy+NhbEUrBcpjE4i3lriB8
X-Received: by 10.223.143.82 with SMTP id p76mr1693509wrb.261.1504130494642; Wed, 30 Aug 2017 15:01:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.184.71 with HTTP; Wed, 30 Aug 2017 15:00:53 -0700 (PDT)
In-Reply-To: <150411366399.21627.17047458871931107094@ietfa.amsl.com>
References: <150411366399.21627.17047458871931107094@ietfa.amsl.com>
From: "M. Ranganathan" <mranga@gmail.com>
Date: Wed, 30 Aug 2017 18:00:53 -0400
Message-ID: <CAHiu4JMCtxFY9qu6q4h30Y=GExx69yLg7xRbSirgURy=7+4_Lw@mail.gmail.com>
Subject: Re: [OPSAWG] Genart early review of draft-ietf-opsawg-mud-08
To: Robert Sparks <rjsparks@nostrum.com>
Cc: gen-art@ietf.org, draft-ietf-opsawg-mud.all@ietf.org, opsawg@ietf.org,  ietf@ietf.org
Content-Type: multipart/alternative; boundary="f403045f4daad43fa80557ffaba3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/K_ZEgdtF2l0dmO3jHnaqN5Iijq0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 30 Aug 2017 22:01:41 -0000

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

On Wed, Aug 30, 2017 at 1:21 PM, Robert Sparks <rjsparks@nostrum.com> wrote:

>
>
> Right now, you leave the DHCP server (when it's used) responsible for
> clearing state in the MUD controller. Please discuss what happens when
> those are distinct elements (as you have in the end of section 9.2) and
> the DHCP server reboots. Perhaps it would make sense for the DHCP server
> to hand the length of the lease it has granted to the MUD controller and
> let the MUD controller clean up on its own?
>

I would like to add a few words to the comprehensive review presented by
Robert Sparks (I hope it is proper etiquette on this list to do so).

With respect to the observation above:

There is also a cache timeout in the MUD profile. Does it make sense  that
the MUD controller should take the minimum of the DHCP lease time and the
cache timeout and use that to time out the installed ACLs (?) The DHCP
server should also  pass to the MUD controller, some way of identifying the
device to which the lease has been granted (for example the MAC address of
the device).

The draft also not specify how the DHCP server will communicate with the
MUD controller (presumably via a simple REST interface but what is the URL
to be used and how are the parameters passed?). I think this should be
specified for interoperability between DHCP clients and MUD servers. Maybe
words describing this interaction can be added here.

Thanks,

Ranga.



>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>


-- 
M. Ranganathan

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Aug 30, 2017 at 1:21 PM, Robert Sparks <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:rjsparks@nostrum.com" target=3D"_blank">rjsparks@nostrum.co=
m</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
"><br>
<br>
Right now, you leave the DHCP server (when it&#39;s used) responsible for<b=
r>
clearing state in the MUD controller. Please discuss what happens when<br>
those are distinct elements (as you have in the end of section 9.2) and<br>
the DHCP server reboots. Perhaps it would make sense for the DHCP server<br=
>
to hand the length of the lease it has granted to the MUD controller and<br=
>
let the MUD controller clean up on its own?<br></blockquote><div><br></div>=
<div>I would like to add a few words to the comprehensive review presented =
by Robert Sparks (I hope it is proper etiquette on this list to do so).<br>=
<br></div><div>With respect to the observation above:<br></div><div><br>The=
re is also a cache timeout in the MUD profile. Does it make sense=C2=A0 tha=
t the MUD controller should take the minimum of the DHCP lease time and the=
 cache timeout and use that to time out the installed ACLs (?) The DHCP ser=
ver should also=C2=A0 pass to the MUD controller, some way of identifying t=
he device to which the lease has been granted (for example the MAC address =
of the device). <br><br></div><div>The draft also not specify how the DHCP =
server will communicate with the MUD controller (presumably via a simple RE=
ST interface but what is the URL to be used and how are the parameters pass=
ed?). I think this should be specified for interoperability between DHCP cl=
ients and MUD servers. Maybe words describing this interaction can be added=
 here.<br><br></div><div>Thanks,<br><br></div><div>Ranga.<br></div><div><br=
>=C2=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
______________________________<wbr>_________________<br>
OPSAWG mailing list<br>
<a href=3D"mailto:OPSAWG@ietf.org">OPSAWG@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/opsawg" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/opsawg</a><br=
>
</blockquote></div><br><br clear=3D"all"></div><div class=3D"gmail_extra">-=
- <br><div class=3D"gmail_signature">M. Ranganathan<br></div>
</div></div>

--f403045f4daad43fa80557ffaba3--


From nobody Wed Aug 30 15:03:27 2017
Return-Path: <mranga@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C3F4132C03; Wed, 30 Aug 2017 15:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VliVya8fEbci; Wed, 30 Aug 2017 15:03:17 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A400132C2E; Wed, 30 Aug 2017 15:03:17 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id u126so17766500wmg.1; Wed, 30 Aug 2017 15:03:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=l4wZRgVgf6jFPP6U4X4XY1JwLFh4/f0KwaTD+3j5Otk=; b=T32ruub2ear01seLjzvRC8XgGPu0keeDZE1cykiV4fUf5IlYVOAqs94KO9mXCsU2Wt +0X0OGhZAoUr/zhiw247J7fDCWXlVENsJko4UJxC8IWCS5R+gVlc7xP7evXd6R/QJrg/ YasUIXTcGGQTcxRSvY+DMHCnWBo4d3QCFRQJYv/AzPt20xkVIcqZm3ITn03M5wyhu8ko BrSNxPellV6m9BJwe//+3qssptTUg00BL+a17IhquDsjivecZY3nEXNP0DipNL5jMkCp jI8tfBhNLHnMzn8Acs6BkLeLgxXhCSboymjnkS6dp4dxWT6Lrq9GH9Aon6Q/Sb6Qf0SK 9URA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=l4wZRgVgf6jFPP6U4X4XY1JwLFh4/f0KwaTD+3j5Otk=; b=uSv1Tjga50B9PhtRzkUUftyYSlGNGrqD3s/zKnyIonZnEo2hvZ41+aZ32EzSGYo02z 4hpcdcygNkv+50ZihyLD22VbvVwQaSIbKgp2kj4Im1+wabgilA2eVH1HXl/+1rWLZNVW SqE+0yzAMfzomZMLS3sy4fyIa3AIH+im7OMxh74TIFMQnVJA1OB1Zvxpp/l9lZSGJ3t/ lxXBVczUBeKGAv8zgYF6QZNkhE/7D0FLQXHjQSTyjx6ZHu5/JIBH1eW8AAQPbq5ue2BF +kkQbW92FcnfIrhycVK+fyQ2/o3Y3UDlXYuoJ/mE1OZbGhnyK1bNc5AXJnje8oS6woz7 xlAg==
X-Gm-Message-State: AHYfb5g5xdq2ufaWbY8sibS02wqYEfvt+0rm+wi6aQbeMvbxByjF3cqM V4dZwFv+ufB8QeiU8wHkzXn/KKUpBA==
X-Received: by 10.28.167.131 with SMTP id q125mr2470643wme.11.1504130595678; Wed, 30 Aug 2017 15:03:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.184.71 with HTTP; Wed, 30 Aug 2017 15:02:35 -0700 (PDT)
In-Reply-To: <CAHiu4JMCtxFY9qu6q4h30Y=GExx69yLg7xRbSirgURy=7+4_Lw@mail.gmail.com>
References: <150411366399.21627.17047458871931107094@ietfa.amsl.com> <CAHiu4JMCtxFY9qu6q4h30Y=GExx69yLg7xRbSirgURy=7+4_Lw@mail.gmail.com>
From: "M. Ranganathan" <mranga@gmail.com>
Date: Wed, 30 Aug 2017 18:02:35 -0400
Message-ID: <CAHiu4JMcEkiZVZEax2uzk6H2Nz9Ka=p9T60LW2khzcQVDu0j9g@mail.gmail.com>
Subject: Re: [OPSAWG] Genart early review of draft-ietf-opsawg-mud-08
To: Robert Sparks <rjsparks@nostrum.com>
Cc: gen-art@ietf.org, draft-ietf-opsawg-mud.all@ietf.org, opsawg@ietf.org,  ietf@ietf.org
Content-Type: multipart/alternative; boundary="001a114b9bdcd9ecf20557ffb18c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/D3Tcfw7jEuvLVnvBmBFNRqik0ts>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 30 Aug 2017 22:03:20 -0000

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

On Wed, Aug 30, 2017 at 6:00 PM, M. Ranganathan <mranga@gmail.com> wrote:

>
>
> On Wed, Aug 30, 2017 at 1:21 PM, Robert Sparks <rjsparks@nostrum.com>
> wrote:
>
>>
>>
>> Right now, you leave the DHCP server (when it's used) responsible for
>> clearing state in the MUD controller. Please discuss what happens when
>> those are distinct elements (as you have in the end of section 9.2) and
>> the DHCP server reboots. Perhaps it would make sense for the DHCP server
>> to hand the length of the lease it has granted to the MUD controller and
>> let the MUD controller clean up on its own?
>>
>
> I would like to add a few words to the comprehensive review presented by
> Robert Sparks (I hope it is proper etiquette on this list to do so).
>
> With respect to the observation above:
>
> There is also a cache timeout in the MUD profile. Does it make sense  that
> the MUD controller should take the minimum of the DHCP lease time and the
> cache timeout and use that to time out the installed ACLs (?) The DHCP
> server should also  pass to the MUD controller, some way of identifying the
> device to which the lease has been granted (for example the MAC address of
> the device).
>
> The draft also not specify how the DHCP server will communicate with the
> MUD controller (presumably via a simple REST interface but what is the URL
> to be used and how are the parameters passed?). I think this should be
> specified for interoperability between DHCP clients and MUD servers. Maybe
> words describing this interaction can be added here.
>

Sorry: I meant interoperability between DHCP servers and MUD controllers
above.


>
> Thanks,
>
> Ranga.
>
>
>
>>
>> _______________________________________________
>> OPSAWG mailing list
>> OPSAWG@ietf.org
>> https://www.ietf.org/mailman/listinfo/opsawg
>>
>
>
> --
> M. Ranganathan
>



-- 
M. Ranganathan

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Aug 30, 2017 at 6:00 PM, M. Ranganathan <span dir=3D"ltr">&lt;<=
a href=3D"mailto:mranga@gmail.com" target=3D"_blank">mranga@gmail.com</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><br><di=
v class=3D"gmail_extra"><br><div class=3D"gmail_quote"><span class=3D"">On =
Wed, Aug 30, 2017 at 1:21 PM, Robert Sparks <span dir=3D"ltr">&lt;<a href=
=3D"mailto:rjsparks@nostrum.com" target=3D"_blank">rjsparks@nostrum.com</a>=
&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br=
>
<br>
Right now, you leave the DHCP server (when it&#39;s used) responsible for<b=
r>
clearing state in the MUD controller. Please discuss what happens when<br>
those are distinct elements (as you have in the end of section 9.2) and<br>
the DHCP server reboots. Perhaps it would make sense for the DHCP server<br=
>
to hand the length of the lease it has granted to the MUD controller and<br=
>
let the MUD controller clean up on its own?<br></blockquote><div><br></div>=
</span><div>I would like to add a few words to the comprehensive review pre=
sented by Robert Sparks (I hope it is proper etiquette on this list to do s=
o).<br><br></div><div>With respect to the observation above:<br></div><div>=
<br>There is also a cache timeout in the MUD profile. Does it make sense=C2=
=A0 that the MUD controller should take the minimum of the DHCP lease time =
and the cache timeout and use that to time out the installed ACLs (?) The D=
HCP server should also=C2=A0 pass to the MUD controller, some way of identi=
fying the device to which the lease has been granted (for example the MAC a=
ddress of the device). <br><br></div><div>The draft also not specify how th=
e DHCP server will communicate with the MUD controller (presumably via a si=
mple REST interface but what is the URL to be used and how are the paramete=
rs passed?). I think this should be specified for interoperability between =
DHCP clients and MUD servers. Maybe words describing this interaction can b=
e added here.<br></div></div></div></div></blockquote><div><br></div><div>S=
orry: I meant interoperability between DHCP servers and MUD controllers abo=
ve.<br>=C2=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div=
 class=3D"gmail_extra"><div class=3D"gmail_quote"><div><br></div><div>Thank=
s,<br><br></div><div>Ranga.<br></div><span class=3D""><div><br>=C2=A0<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
______________________________<wbr>_________________<br>
OPSAWG mailing list<br>
<a href=3D"mailto:OPSAWG@ietf.org" target=3D"_blank">OPSAWG@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/opsawg" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/opsawg</a><br=
>
</blockquote></span></div><span class=3D"HOEnZb"><font color=3D"#888888"><b=
r><br clear=3D"all"></font></span></div><span class=3D"HOEnZb"><font color=
=3D"#888888"><div class=3D"gmail_extra">-- <br><div class=3D"m_-54452031424=
08874788gmail_signature">M. Ranganathan<br></div>
</div></font></span></div>
</blockquote></div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail_sig=
nature" data-smartmail=3D"gmail_signature">M. Ranganathan<br></div>
</div></div>

--001a114b9bdcd9ecf20557ffb18c--


From nobody Wed Aug 30 19:02:16 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97A07132331 for <ietf@ietfa.amsl.com>; Wed, 30 Aug 2017 19:02:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RYoiBJ0YF_8I for <ietf@ietfa.amsl.com>; Wed, 30 Aug 2017 19:02:13 -0700 (PDT)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (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 7421312008A for <ietf@ietf.org>; Wed, 30 Aug 2017 19:02:13 -0700 (PDT)
Received: from resomta-ch2-18v.sys.comcast.net ([69.252.207.114]) by resqmta-ch2-08v.sys.comcast.net with ESMTP id nEo3dDZESJVCpnEo8dTxgZ; Thu, 31 Aug 2017 02:02:12 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-18v.sys.comcast.net with SMTP id nEo7diKwg0EZInEo7da7Sy; Thu, 31 Aug 2017 02:02:12 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v7V22APD021285; Wed, 30 Aug 2017 22:02:10 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v7V229hs021282; Wed, 30 Aug 2017 22:02:09 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: gen-art@ietf.org, draft-ietf-opsawg-mud.all@ietf.org, opsawg@ietf.org, ietf@ietf.org, mranga@gmail.com, Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [Gen-art] Genart early review of draft-ietf-opsawg-mud-08
In-Reply-To: <150411366399.21627.17047458871931107094@ietfa.amsl.com> (rjsparks@nostrum.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Wed, 30 Aug 2017 22:02:09 -0400
Message-ID: <87shg8fqam.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfBK4GTPIGch3KjJ2fBr5XEi2qlesAQRaXHZM9x4W90G2h/s2+jrwT7m3Pu/xQKaMfsvYHroOSwScdFFpghuUTEs9F/zrJeFodE8ZtLFXO2ezQveHnt1G S0+TH07ULVrjburw9LVT4QxaQ4ZLLeVzZjZFfe/JzgWNndzHoULFWY8b7pDpQ/ZOoG+AwGXY1T80+ljPcPX1VT5HlAKZLmDxxJK9IZg4o2Sr/avwLvktAyck dKfRe6AdomKY+jd/xpxqsLJoP7eALpyM1nfS32zwDLQ28tg2VvYvzGtjQSbLU5odX9MdrH5aHgHxkoQYbw0Bng==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_a___5sLGMOhaV4B6vMMfQY5EJY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 31 Aug 2017 02:02:15 -0000

This draft raises some fascinating questions.  One is "How do we ensure
that the manufacturer cannot proscribe the uses of a device that it is
capable of and that its purchaser desires?"  Another is "How do we
ensure that the manufacturer cannot reduce the permitted uses of the
device after its purchase?"

Dale


From nobody Thu Aug 31 00:15:51 2017
Return-Path: <einarnn@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81733132D18; Thu, 31 Aug 2017 00:15:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level: 
X-Spam-Status: No, score=-14.52 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dcIE0DSjpvqT; Thu, 31 Aug 2017 00:15:48 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 681B1132D13; Thu, 31 Aug 2017 00:15:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1201; q=dns/txt; s=iport; t=1504163748; x=1505373348; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=tQ+gD5jtIXktfWp9vtPK4f0L7IQdQdXbCaWKd+8eWOI=; b=NDDSkayDDWIVOfetkk2AVO8WLWupVIVCjRXbf3kJkQPLAeOxGIn9AnQk Couq7IjkkfHuR/lyB22/d7pyXyre8CGVkKoR3rLIIkjQwWaLH6TgsPHNK 90eEK78VyMhmJUoYTo8I4lcEaaJKkAKQ5kjU6IIb4Dm8MQrDSu27XprZM 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CxAQBvtqdZ/4ENJK1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgy0tZIEVnjWBcZYnghIhC4FggmxPAoQrQBcBAgEBAQEBAQFrKIU?= =?us-ascii?q?YAQEBAQIBAQE4NAsFCwIBCBgeECcLJQIEDgWKKQgQsUWLQwEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBARgFgyqCAoNcgkg1hHWDQ4IxBYoPlmAClE+CE5BbiXiMTAEhAzO?= =?us-ascii?q?BDXcVSRIBhwh2ij0BAQE?=
X-IronPort-AV: E=Sophos;i="5.41,451,1498521600"; d="scan'208";a="279212680"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 31 Aug 2017 07:15:47 +0000
Received: from XCH-RTP-009.cisco.com (xch-rtp-009.cisco.com [64.101.220.149]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v7V7Flod010610 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 31 Aug 2017 07:15:47 GMT
Received: from xch-rtp-009.cisco.com (64.101.220.149) by XCH-RTP-009.cisco.com (64.101.220.149) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 31 Aug 2017 03:15:46 -0400
Received: from xch-rtp-009.cisco.com ([64.101.220.149]) by XCH-RTP-009.cisco.com ([64.101.220.149]) with mapi id 15.00.1263.000; Thu, 31 Aug 2017 03:15:46 -0400
From: "Einar Nilsen-Nygaard (einarnn)" <einarnn@cisco.com>
To: "Dale R. Worley" <worley@ariadne.com>
CC: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-opsawg-mud.all@ietf.org" <draft-ietf-opsawg-mud.all@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "mranga@gmail.com" <mranga@gmail.com>, Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [OPSAWG] [Gen-art] Genart early review of draft-ietf-opsawg-mud-08
Thread-Topic: [OPSAWG] [Gen-art] Genart early review of draft-ietf-opsawg-mud-08
Thread-Index: AQHTIf1EDowo5AKrbEuACYGVNIL1daKeDfNe
Date: Thu, 31 Aug 2017 07:15:46 +0000
Message-ID: <25FFA75E-330B-4A5A-B6B9-D1817A86D7B2@cisco.com>
References: <150411366399.21627.17047458871931107094@ietfa.amsl.com> (rjsparks@nostrum.com),<87shg8fqam.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87shg8fqam.fsf@hobgoblin.ariadne.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Q38_lpZSjxA3G3DfBKVbywuvJ2Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 31 Aug 2017 07:15:50 -0000

I think we need to bear in mind that the MUD files constitute recommendatio=
ns for how a device should be treated and what policies/security should be =
applied to it by a network. This draft, in itself, cannot allow a manufactu=
rer to actually proscribe anything. Today, the only way to achieve what you=
 note below, AFAIK, is for the device to have a software update of some kin=
d applied to it.

Also, we could also argue that a manufacturer-published MUD file actually h=
as the potential to increase transparency as it should explicitly define th=
e traffic flows required for "proper operations".

Cheers,

Einar

> On Aug 31, 2017, at 03:02, Dale R. Worley <worley@ariadne.com> wrote:
>=20
> This draft raises some fascinating questions.  One is "How do we ensure
> that the manufacturer cannot proscribe the uses of a device that it is
> capable of and that its purchaser desires?"  Another is "How do we
> ensure that the manufacturer cannot reduce the permitted uses of the
> device after its purchase?"
>=20
> Dale
>=20
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg


From nobody Thu Aug 31 01:41:50 2017
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0B67132620; Thu, 31 Aug 2017 01:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level: 
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hgd3xnssRLaG; Thu, 31 Aug 2017 01:41:31 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D88C8132358; Thu, 31 Aug 2017 01:41:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8823; q=dns/txt; s=iport; t=1504168890; x=1505378490; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=WK2LzKZOb0zgqg2jYdZ9Hpa6qyPK0Lrh6HBZOFfnWG0=; b=RbFj9UOYfKBdZ207GDMvut6TZXne4ZJ0E7RNsxZXM/vquPMK52j6aNjM gxtHWG2GbBcXiSTYUXjfUuWsPPgOIn05AelCyzrfggBlvknvCr2rZyQAd ZUYWFdO8Ihn/EnlWSzEao+kUBBhj8hWHO7X/paWmB1CqlTrYElqBUdEEL A=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BEAwAJy6dZ/xbLJq1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgy2CJoN3ixSQeSKQaYU+ghIHhUAChGwWAQIBAQEBAQEBayiFGQE?= =?us-ascii?q?FI1YQCxgnAwICRhEGAQwGAgEBii2wHYInJ4sdAQEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBDg+DKoVeC4FlgQ2EX4MpgmEBBKBvhDmCIY13ghOFZ4NZhxuWRSYFLIENMiE?= =?us-ascii?q?IHBVJhRgcgWk+Noo9AQEB?=
X-IronPort-AV: E=Sophos;i="5.41,451,1498521600";  d="asc'?scan'208,217";a="696869282"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Aug 2017 08:41:25 +0000
Received: from [10.61.80.230] (ams3-vpn-dhcp4327.cisco.com [10.61.80.230]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v7V8fOHi030151; Thu, 31 Aug 2017 08:41:25 GMT
Subject: Re: [OPSAWG] Genart early review of draft-ietf-opsawg-mud-08
To: "M. Ranganathan" <mranga@gmail.com>, Robert Sparks <rjsparks@nostrum.com>
Cc: gen-art@ietf.org, draft-ietf-opsawg-mud.all@ietf.org, opsawg@ietf.org, ietf@ietf.org
References: <150411366399.21627.17047458871931107094@ietfa.amsl.com> <CAHiu4JMCtxFY9qu6q4h30Y=GExx69yLg7xRbSirgURy=7+4_Lw@mail.gmail.com>
From: Eliot Lear <lear@cisco.com>
Message-ID: <8a26b512-495b-4315-a885-32acd41c5460@cisco.com>
Date: Thu, 31 Aug 2017 10:41:28 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CAHiu4JMCtxFY9qu6q4h30Y=GExx69yLg7xRbSirgURy=7+4_Lw@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="0qe0LOGonjdSE19rTg8FL8PgpeM1CSBp1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pn9pjgkWqgpGIPjXJv0HeICAkMU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 31 Aug 2017 08:41:33 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--0qe0LOGonjdSE19rTg8FL8PgpeM1CSBp1
Content-Type: multipart/mixed; boundary="bcHIUviXj0h4b1KO2Txhro1v43MXr30kT";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: "M. Ranganathan" <mranga@gmail.com>, Robert Sparks <rjsparks@nostrum.com>
Cc: gen-art@ietf.org, draft-ietf-opsawg-mud.all@ietf.org, opsawg@ietf.org,
 ietf@ietf.org
Message-ID: <8a26b512-495b-4315-a885-32acd41c5460@cisco.com>
Subject: Re: [OPSAWG] Genart early review of draft-ietf-opsawg-mud-08
References: <150411366399.21627.17047458871931107094@ietfa.amsl.com>
 <CAHiu4JMCtxFY9qu6q4h30Y=GExx69yLg7xRbSirgURy=7+4_Lw@mail.gmail.com>
In-Reply-To: <CAHiu4JMCtxFY9qu6q4h30Y=GExx69yLg7xRbSirgURy=7+4_Lw@mail.gmail.com>

--bcHIUviXj0h4b1KO2Txhro1v43MXr30kT
Content-Type: multipart/alternative;
 boundary="------------7ACAF6105FDD6C8F1A23D99D"
Content-Language: en-US

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

Hi Ranga,

Robert wrote a great review, and I'll respond to him in due course with
suggested changes.=C2=A0 I wanted to take just a moment to comment to you=
 on
your point:


On 8/31/17 12:00 AM, M. Ranganathan wrote:
>
>
> On Wed, Aug 30, 2017 at 1:21 PM, Robert Sparks <rjsparks@nostrum.com
> <mailto:rjsparks@nostrum.com>> wrote:
>
>
>
>     Right now, you leave the DHCP server (when it's used) responsible f=
or
>     clearing state in the MUD controller. Please discuss what happens w=
hen
>     those are distinct elements (as you have in the end of section
>     9.2) and
>     the DHCP server reboots. Perhaps it would make sense for the DHCP
>     server
>     to hand the length of the lease it has granted to the MUD
>     controller and
>     let the MUD controller clean up on its own?
>
>
> I would like to add a few words to the comprehensive review presented
> by Robert Sparks (I hope it is proper etiquette on this list to do so).=

>
> With respect to the observation above:
>
> There is also a cache timeout in the MUD profile. Does it make sense=C2=
=A0
> that the MUD controller should take the minimum of the DHCP lease time
> and the cache timeout and use that to time out the installed ACLs (?)
> The DHCP server should also=C2=A0 pass to the MUD controller, some way =
of
> identifying the device to which the lease has been granted (for
> example the MAC address of the device).
>
> The draft also not specify how the DHCP server will communicate with
> the MUD controller (presumably via a simple REST interface but what is
> the URL to be used and how are the parameters passed?). I think this
> should be specified for interoperability between DHCP clients and MUD
> servers. Maybe words describing this interaction can be added here.

That's right.=C2=A0 At the moment, this is an "internalized" function.=C2=
=A0 That
is to say that the DHCP server is said to be tightly coupled to the MUD
controller without standardized interfaces.=C2=A0 In my first implementat=
ion,
I literally just tailed dhcpd syslog entries and triggered MUD based on
DHCPREQUEST messages.=C2=A0 Clean-up state had to do with RELEASE or peri=
odic
SNMP queries.=C2=A0 Our implementation at Cisco does something different.=


However... if the OPSAWG would like, and there is interest, we can
formalize that interface.=C2=A0 I don't want to do it in THIS draft (it's=

already fairly involved), but there's nothing to say we couldn't do some
follow-on work.

Fair enough?

Eliot

--------------7ACAF6105FDD6C8F1A23D99D
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=3Dutf=
-8">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p>Hi Ranga,</p>
    <p>Robert wrote a great review, and I'll respond to him in due
      course with suggested changes.=C2=A0 I wanted to take just a moment=
 to
      comment to you on your point:<br>
    </p>
    <br>
    <div class=3D"moz-cite-prefix">On 8/31/17 12:00 AM, M. Ranganathan
      wrote:<br>
    </div>
    <blockquote type=3D"cite"
cite=3D"mid:CAHiu4JMCtxFY9qu6q4h30Y=3DGExx69yLg7xRbSirgURy=3D7+4_Lw@mail.=
gmail.com">
      <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Du=
tf-8">
      <div dir=3D"ltr"><br>
        <div class=3D"gmail_extra"><br>
          <div class=3D"gmail_quote">On Wed, Aug 30, 2017 at 1:21 PM,
            Robert Sparks <span dir=3D"ltr">&lt;<a
                href=3D"mailto:rjsparks@nostrum.com" target=3D"_blank"
                moz-do-not-send=3D"true">rjsparks@nostrum.com</a>&gt;</sp=
an>
            wrote:<br>
            <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=

              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex"><br>
              <br>
              Right now, you leave the DHCP server (when it's used)
              responsible for<br>
              clearing state in the MUD controller. Please discuss what
              happens when<br>
              those are distinct elements (as you have in the end of
              section 9.2) and<br>
              the DHCP server reboots. Perhaps it would make sense for
              the DHCP server<br>
              to hand the length of the lease it has granted to the MUD
              controller and<br>
              let the MUD controller clean up on its own?<br>
            </blockquote>
            <div><br>
            </div>
            <div>I would like to add a few words to the comprehensive
              review presented by Robert Sparks (I hope it is proper
              etiquette on this list to do so).<br>
              <br>
            </div>
            <div>With respect to the observation above:<br>
            </div>
            <div><br>
              There is also a cache timeout in the MUD profile. Does it
              make sense=C2=A0 that the MUD controller should take the
              minimum of the DHCP lease time and the cache timeout and
              use that to time out the installed ACLs (?) The DHCP
              server should also=C2=A0 pass to the MUD controller, some w=
ay
              of identifying the device to which the lease has been
              granted (for example the MAC address of the device). <br>
              <br>
            </div>
            <div>The draft also not specify how the DHCP server will
              communicate with the MUD controller (presumably via a
              simple REST interface but what is the URL to be used and
              how are the parameters passed?). I think this should be
              specified for interoperability between DHCP clients and
              MUD servers. Maybe words describing this interaction can
              be added here.<br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    That's right.=C2=A0 At the moment, this is an "internalized" function=
=2E=C2=A0
    That is to say that the DHCP server is said to be tightly coupled to
    the MUD controller without standardized interfaces.=C2=A0 In my first=

    implementation, I literally just tailed dhcpd syslog entries and
    triggered MUD based on DHCPREQUEST messages.=C2=A0 Clean-up state had=
 to
    do with RELEASE or periodic SNMP queries.=C2=A0 Our implementation at=

    Cisco does something different.<br>
    <br>
    However... if the OPSAWG would like, and there is interest, we can
    formalize that interface.=C2=A0 I don't want to do it in THIS draft (=
it's
    already fairly involved), but there's nothing to say we couldn't do
    some follow-on work.<br>
    <br>
    Fair enough?<br>
    <br>
    Eliot<br>
  </body>
</html>

--------------7ACAF6105FDD6C8F1A23D99D--

--bcHIUviXj0h4b1KO2Txhro1v43MXr30kT--

--0qe0LOGonjdSE19rTg8FL8PgpeM1CSBp1
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

iQEcBAEBCAAGBQJZp8u4AAoJEIe2a0bZ0nozDTsH+QHLJuJDZ+8NukV0ymJeXV9C
erUw1YFMaTHOAvdKjjvzE1Kv5S4sJmaGn2Y0WhT5ha878xEOx/dfhd4LMtN4JUkP
WuaTHSaLsVrjQkWsQ0BKERLuMVBwz69o/jb+cNXBTn/h+lA79Ufs0L8EarKb0T6s
FSlwCAlGvhBUVbW0/HHJJIKBfcxhU416IAYBiIE1Q6YNrYJMsl0KdE652GW8HaRz
+gMqjtJ145GYcQs+hDLPtvtt/a1ixDCVf91WSZx1cGA5bg70kufqR76e8/yBEk2t
o8kPJwTPVJpeCBsZOTFzZ/eL1vQ1Z5IPBcGzxUhZq00Bgmq1yL1nwdusuIJsdYc=
=F8Zk
-----END PGP SIGNATURE-----

--0qe0LOGonjdSE19rTg8FL8PgpeM1CSBp1--


From nobody Thu Aug 31 05:00:41 2017
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD611132D4E; Thu, 31 Aug 2017 05:00:28 -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, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jeZh6Efl3oEA; Thu, 31 Aug 2017 05:00:24 -0700 (PDT)
Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9C34132D5A; Thu, 31 Aug 2017 05:00:19 -0700 (PDT)
Received: from [IPv6:2003:cd:6bcc:5600:fc86:4367:9fa8:604e] (p200300CD6BCC5600FC8643679FA8604E.dip0.t-ipconnect.de [IPv6:2003:cd:6bcc:5600:fc86:4367:9fa8:604e]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id E0E9871E3F8DC; Thu, 31 Aug 2017 14:00:06 +0200 (CEST)
From: Michael Tuexen <tuexen@fh-muenster.de>
Message-Id: <5CEB294C-AAC8-4F03-901D-487CD62BB491@fh-muenster.de>
Content-Type: multipart/signed; boundary="Apple-Mail=_C4475747-0DBC-4EE5-A518-4111208F0FD3"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [OPS-DIR] Opsdir last call review of draft-ietf-tsvwg-sctp-ndata-12
Date: Thu, 31 Aug 2017 14:00:05 +0200
In-Reply-To: <f4d121e4-44f5-e85d-98b1-bbea317a7539@cisco.com>
Cc: Stefan Winter <stefan.winter@restena.lu>, ops-dir@ietf.org, draft-ietf-tsvwg-sctp-ndata.all@ietf.org, tsvwg@ietf.org, ietf@ietf.org, IESG IESG <iesg@ietf.org>
To: Benoit Claise <bclaise@cisco.com>
References: <150287547583.12471.9085655210334710687@ietfa.amsl.com> <FDCFFA8C-8828-4578-A66E-A1AD7FF9BDC9@fh-muenster.de> <1a39dff3-55a9-fe1d-7e19-a0fbd0b2751b@restena.lu> <F05D0F1F-47E2-4477-BFD9-F0119A4609FC@fh-muenster.de> <f4d121e4-44f5-e85d-98b1-bbea317a7539@cisco.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8M98npCE7P4ak72IZrgaS8JQViE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 31 Aug 2017 12:00:29 -0000

--Apple-Mail=_C4475747-0DBC-4EE5-A518-4111208F0FD3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> On 30. Aug 2017, at 18:51, Benoit Claise <bclaise@cisco.com> wrote:
>=20
> Michael,
>=20
> I stumbled on the same point as Stefan.
Hi Benoit,

thanks for reviewing the document. See my comments in-line.

Best regards
Michael
>=20
> First of, I had to review RFC4960 for TSN/SSN. I was not sure whether =
TSN was per stream or not
> It would have helped me to repeat this information in the intro.
> Ok, to be candid, I deduced this information from figure 1 and 2.

>>>=20
>>>>> And the rest are only musings not needing any action if the =
authors don't want
>>>>> to action on them:
>>>>>=20
>>>>> The introduction presents a good use case, quoting: "e.g., when =
the
>>>>> transmission of an urgent
>>>>>  message is blocked from transmission because the sender has =
started
>>>>>  the transmission of another, possibly large, message".
>>>>>=20
>>>>> The later queueing example in figure 1 has three SIDs being queued
>>>>> simultanseously. It is not clear which of those "has already =
started" and which
>>>> There is actually one message queued for stream 0, three messages =
for stream 1,
>>>> and one message for stream 2.
>>>>> are the important ones being delayed. For a better understanding =
of the reader,
>>>> The figure is about in which sequence they are put on the wire. So =
no
>>>> transmission has startet. This examples also does not deal with the =
case
>>>> of one stream having a higher priority than another. That would be =
an
>>>> example using a priority scheduler. This examples illustrates the =
round
>>>> robin scheduler.
>>>> The point here is that a single scheduler (the round robin =
scheduler, for
>>>> example) behaves differently when user message interleaving is used =
or not.
>>>> That is an important point: You can even use the schedulers with =
regular
>>>> DATA chunk, i.e. with user message interleaving being negotiated.
> This was my source of confusion.
> With figure 1 and figure 2, you want to show the effect of Round Robin =
Scheduler with and without User Message Interleaving, while we were =
expecting the figure 2 to be the solution from this spec. Hence Stefan =
and I were looking for this "urgent message" in figure 2.
I don't know what you mean with "solution from this spec" means. This =
spec introduces
stream schedulers and a protocol extension to allow interleaving of user =
messages.
Using this to implement an "urgent" concept is only one possibility: =
usage of a
strict priority scheduler (SCTP_SS_PRIO). So this "urgent" is =
misleading. It seems
to ring the wrong bells. That is why I suggested to remove it...
>=20
>>>>> it might be useful to revise the figure so that the head-of-line =
blocking
>>>>> happens for SID 1 because transmission of  0 and 2 has already =
started (and
>>>>> declare SID 1 to be the "important" message). The ASCII art would =
just have to
>>>>> indent SID 1 content a bit (placing 0 and 2 earlier in time), and =
the resulting
>>>>> serialisation would then put all the SID 1 messages at the very =
end, when 0 and
>>>>> 2 have been completely submitted (right?).
>>>> One could think about adding another example based on the priority =
scheduler
>>>> and giving stream 1 a higher priority. But for illustrating the =
point of
>>>> schedulers behaving differently depending on the negotiation of =
user message
>>>> interleaving this seems not necessary.
>>> That second example might indeed be useful.
>>>=20
>>> It's simply a bit strange that in the introduction you speak about =
an
>>> "urgent" message (something deserving a higher-priority sending) and
>>> that another transmission has already started - but then the example =
has
>>> none of those two.
> Exactly.
> Please add this extra example.
> This would also clarify from the introduction that when you write ...
>=20
>   The sending of such large messages over
>   SCTP as specified in [RFC4960] can result in a form of sender side
>   head of line blocking (e.g., when the transmission of an urgent
>   message is blocked from transmission because the sender has started
>   the transmission of another, possibly large, message).
>=20
> .. the notion of transmission urgency is not within a stream but =
across streams, and that can be achieved with a priority scheduler.
I would actually prefer to remove the word "urgent" from that sentence. =
This just rings the wrong bells.
> The text might have to be rephrased to explain that this spec provides =
the ability to create stream scheduler with different relative stream =
treatments.
What about:

OLD TEXT
   This document also defines several stream schedulers for general SCTP
   associations.  The stream schedulers may behave differently depending
   on whether user message interleaving has been negotiated for the
   association or not.

NEW TEXT
   This document also defines several stream schedulers for general SCTP
   associations allowing different relative stream treatments.
   The stream schedulers may behave differently depending
   on whether user message interleaving has been negotiated for the
   association or not.

Would that address this issue?
 =20
> And also that urgent message would be placed in this high priority =
stream scheduler (reliable, I guess, but that's orthogonal) stream.
I really would like to get rid of this. I don't think giving the strict
priority scheduler as specific role here is a good idea.

The RR scheduler was chosen as the simplest scheduler to illustrate
that scheduler can behave differently when using interleaving or not.
>> What about removing the word "urgent" from that sentence.
>>> In fact I wonder why you speak about urgent things in the =
introduction
>>> at all. Neither the scheduler nor the interleaving are designed to =
help
>>> urgent things to be sent earlier.
>>>=20
>>> All they do is make the transmission fairer so that *all* chunks get =
a
>>> more even serialised distribution on the wire.
>> That is not true in general. If you use the priority scheduler, one
>> stream gets preferred treatment. It also makes sure that the time
>> of a message spent in the stream queue is shorter. So these messages
>> get sent earlier.
>> In the case of the round robin scheduler, you are right that this is
>> about getting fairer treatment. If you take the WFQ scheduler, the
>> streams don't get the same treatment, but it depends on the weight
>> given to the stream.
>>> So, rather than saying that the spec helps urgent things to be sent
>>> earlier, it should maybe rather state that the spec helps every =
message
>>> getting an equal, and equally distributed, share of the medium.
>> It is not meant that the spec does this. It was one example, what
>> a particular stream scheduler does. But there are multiple schedulers
>> defined in the document.
>>=20
>> The RR scheduler example is not intended to illustrate what you can =
do
>> with all the schedulers, but that using message interleaving or not
>> has an impact on the scheduler. That is meant by stating:
>>=20
>> This document also defines several stream schedulers for general SCTP =
associations.
>> The stream schedulers may behave differently depending on whether =
user message
>> interleaving has been negotiated for the association or not.
>>=20
>> This is followed by illustrating this using the RR scheduler.
>>=20
>> Best regards
> Also, I don't see the value of the last sentence in this paragraph, =
especially with RFC2119 MAY.
>=20
>   This section defines several stream schedulers.  The stream
>   schedulers may behave differently depending on whether user message
>   interleaving has been negotiated for the association or not.  An
>   implementation MAY implement any subset of them.
During the review the question was brought up which scheduler have to be =
implemented
by an implementation. This sentence was add to address it.
If you want, I can remove it.
>=20
>=20
> Regards, Benoit


--Apple-Mail=_C4475747-0DBC-4EE5-A518-4111208F0FD3
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIQkDCCBNUw
ggO9oAMCAQICCFBOxvU9EbRkMA0GCSqGSIb3DQEBCwUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQK
ExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMw
IQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0xNDA3MjIxMjA4MjZaFw0xOTA3
MDkyMzU5MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdE
Rk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAx
BAuZgeKmFNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84Ik
Q4wcOItqaACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVg
Te3RCSMqljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sW
VlZDz+HVEz2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjggGG
MIIBgjAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1Ud
IwQYMBaAFDHDeRu69VPXF+CJei0XbAqzK50zMBIGA1UdEwEB/wQIMAYBAf8CAQIwYgYDVR0gBFsw
WTARBg8rBgEEAYGtIYIsAQEEAgIwEQYPKwYBBAGBrSGCLAEBBAMAMBEGDysGAQQBga0hgiwBAQQD
ATAPBg0rBgEEAYGtIYIsAQEEMA0GCysGAQQBga0hgiweMD4GA1UdHwQ3MDUwM6AxoC+GLWh0dHA6
Ly9wa2kwMzM2LnRlbGVzZWMuZGUvcmwvRFRfUk9PVF9DQV8yLmNybDB4BggrBgEFBQcBAQRsMGow
LAYIKwYBBQUHMAGGIGh0dHA6Ly9vY3NwMDMzNi50ZWxlc2VjLmRlL29jc3ByMDoGCCsGAQUFBzAC
hi5odHRwOi8vcGtpMDMzNi50ZWxlc2VjLmRlL2NydC9EVF9ST09UX0NBXzIuY2VyMA0GCSqGSIb3
DQEBCwUAA4IBAQBjICj9nCGGcr45Rlk5MiW8qQGbDczKfUGchm0KbiyzE1l1sTOSG2EnFv/DstU1
gvuEKgFJvWa7Zi+ywgZdbj9u4wFaW8pDY1yVtuExpx/VB19N5mWCTjL5w3x6S81NXHTuIfJ1AuxS
PtLJatOQI25JZzW+f01WpOzML8+3oZeocj7JvEDWWqQIPda8gsO3tzKOsSyOam23NQIZz/U5RFhj
pyQAELC7/E6vbi84u6VXST/YblBvLJeW3B1GmmWJz67M8uXZn1OzPqEvkqnYC8aEHwTG6x7on321
e6UC8STFJGMRNMxakyAqeYg6JUKQqWU7fIbTEhUjKfws2sw5W1QXMIIFojCCBIqgAwIBAgIHF6Qk
oQlIMzANBgkqhkiG9w0BAQsFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQ
MA4GA1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4X
DTE0MDUyNzE0NTQwOVoXDTE5MDcwOTIzNTkwMFowgcYxCzAJBgNVBAYTAkRFMRwwGgYDVQQIExNO
b3JkcmhlaW4tV2VzdGZhbGVuMREwDwYDVQQHEwhNdWVuc3RlcjEgMB4GA1UEChMXRmFjaGhvY2hz
Y2h1bGUgTXVlbnN0ZXIxIzAhBgNVBAsTGkRhdGVudmVyYXJiZWl0dW5nc3plbnRyYWxlMR0wGwYD
VQQDExRGSCBNdWVuc3RlciBDQSAtIEcwMTEgMB4GCSqGSIb3DQEJARYRY2FAZmgtbXVlbnN0ZXIu
ZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4eWyu8GzsIv0iowf2v/9BT0SmCFNX
/eyQe5BncOk1j6XIlY5bnNu1S5uBe3uVgekgTh3gJyVNlaoIfCgAjqCrNJIaNQq5fr/S6L8uFeaU
O8IF/C4RH5P7f9Hn2GUueEjmJhg9CI3LBAhrfAmEEtNmuVfDycN2MjngwDNxUNRfuXbWxuhkgDqJ
0ztJeayHGhFDrGx88eyStx40xy+0c0OFWdWxzBFQlBRHnl+zRftj3c9qy6BY+/fGaA2vV1oKr3h5
X6eyU1T8YlpP1NDe4bylqAteX01sM2Qciu8UAPnNc7Sb93TQjhCFRVDIS3CdN6AOpwz5YWEld6ey
CdmFZ7pvAgMBAAGjggH+MIIB+jASBgNVHRMBAf8ECDAGAQH/AgEBMA4GA1UdDwEB/wQEAwIBBjAR
BgNVHSAECjAIMAYGBFUdIAAwHQYDVR0OBBYEFArzW7zkMYDWNUKJptPDzzfe0d/XMB8GA1UdIwQY
MBaAFEm3xs/oPR9/6kR7Eyn38QpwPt5kMBwGA1UdEQQVMBOBEWNhQGZoLW11ZW5zdGVyLmRlMIGI
BgNVHR8EgYAwfjA9oDugOYY3aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9w
dWIvY3JsL2NhY3JsLmNybDA9oDugOYY3aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9v
dC1jYS9wdWIvY3JsL2NhY3JsLmNybDCB1wYIKwYBBQUHAQEEgcowgccwMwYIKwYBBQUHMAGGJ2h0
dHA6Ly9vY3NwLnBjYS5kZm4uZGUvT0NTUC1TZXJ2ZXIvT0NTUDBHBggrBgEFBQcwAoY7aHR0cDov
L2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRwYI
KwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2Vy
dC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBCwUAA4IBAQDeRwM11kpvuRIPuzWXLapr/ZBtB76V3cuF
l45x/Kx0u03yjB4GaBPcxihn4P1z5KhRYkDBMo8HXkOgbL59aF6VdOlCurEgZvghKvUkKOCyWeYx
S9rTGPBkbGiNn2ATVuLXzF8rDf50ynAIu3otstOOv+3Ifqi1pzCva1nO64khQA5Gd5/BNyu+YHbW
f8ERAf9leu5a7yVI7cv1gCZAHpWJpkUKmfawyY4sAJ2hbGZRBvdACOxrfbuMdSOzPneT2rlmvH+D
7M6DmzVabLYk6UtAxQhldd/T/qsHkWvaWXHt0Eb9STs2Fl03Ls7M3NyLQLhaeR3ysNURYcaEfaB+
lxN+MIIGDTCCBPWgAwIBAgIHG5mIdDexozANBgkqhkiG9w0BAQsFADCBxjELMAkGA1UEBhMCREUx
HDAaBgNVBAgTE05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQK
ExdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVu
dHJhbGUxHTAbBgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBm
aC1tdWVuc3Rlci5kZTAeFw0xNjA3MDQwNzA2MTNaFw0xOTA3MDQwNzA2MTNaMHwxCzAJBgNVBAYT
AkRFMSAwHgYDVQQKDBdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEyMDAGA1UECwwpRmFjaGJlcmVp
Y2ggRWxla3Ryb3RlY2huaWsgdW5kIEluZm9ybWF0aWsxFzAVBgNVBAMMDk1pY2hhZWwgVHVleGVu
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzJoaUG3Zm24XxA/zNg2sbFcL56w8xqMg
+X6G7UsYec3YEncnlkw3jgE5nDefos7UVoCA7wPjFTj8AQt5xfpXElnbM45IPy5Ng7g6dS7biGSM
VRACPXe1PrjgApRAwwGmCPvALnZXkmKP6Zlf+3VLfz9YWIIaeKu3jFM2Lk6Y3gr5U1l8bjHSawOo
WMlfvSsXXLT38zKW7Uz9jS278j0OqHANBPgsE6/LJoCWFInwlvybxhO3nGU7OteUGaPikqzvjLsL
YgpHDi0WjMZfVx/UtUSzZ4EJvmJTBeuVwyKnCbrawnfwYPTQQ6VE1OkAzmsMByBbEwJ996RtG//T
XCG06QIDAQABo4ICRzCCAkMwQAYDVR0gBDkwNzARBg8rBgEEAYGtIYIsAQEEAwUwEQYPKwYBBAGB
rSGCLAIBBAMBMA8GDSsGAQQBga0hgiwBAQQwCQYDVR0TBAIwADAOBgNVHQ8BAf8EBAMCBeAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBTQHa9qhKgSZgCCAPThZkXaEaJ/
dTAfBgNVHSMEGDAWgBQK81u85DGA1jVCiabTw8833tHf1zAgBgNVHREEGTAXgRV0dWV4ZW5AZmgt
bXVlbnN0ZXIuZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2Zo
LW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZu
LmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIHXBggrBgEFBQcBAQSByjCBxzAz
BggrBgEFBQcwAYYnaHR0cDovL29jc3AucGNhLmRmbi5kZS9PQ1NQLVNlcnZlci9PQ1NQMEcGCCsG
AQUFBzAChjtodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jYWNlcnQv
Y2FjZXJ0LmNydDBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDIucGNhLmRmbi5kZS9maC1tdWVuc3Rl
ci1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQELBQADggEBAEj2/6x4kzoCVIiu
aaminPrOHxACyoYsmSRjYPQpgW5xRj/FlolO1nG+ZZ11sqTb3TdCGD69ko5/zs8eGKnv/i0VLCHF
g1JLfpaxElN5RrR/cqRJrbzKshF9aUkBODF8vlf9BCeimMK3fifjbbWRyxHssfEECffujD7/Yvta
NYMO46Roz39lIK2s37IVFq3V5RWzUeTuwpP9t8lOxirOi9eK2OYI/dh0HjR2S5Dr9nMR1dNulrhz
jlFxGc+opefGScrRR9Ec0eqTXlbt1Q9UzNIYVS+OGZY8/bBbprwXVTmwSp8dygEULkIaMbLsaTaW
6TehuL8ousPJkL52SOENgSkxggQpMIIEJQIBATCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozAJBgUrDgMCGgUAoIICKzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0xNzA4MzExMjAwMDZaMCMGCSqGSIb3DQEJBDEWBBT3Zjz4KhGgMKRKoR1+
G5eOcAssQzCB4wYJKwYBBAGCNxAEMYHVMIHSMIHGMQswCQYDVQQGEwJERTEcMBoGA1UECBMTTm9y
ZHJoZWluLVdlc3RmYWxlbjERMA8GA1UEBxMITXVlbnN0ZXIxIDAeBgNVBAoTF0ZhY2hob2Noc2No
dWxlIE11ZW5zdGVyMSMwIQYDVQQLExpEYXRlbnZlcmFyYmVpdHVuZ3N6ZW50cmFsZTEdMBsGA1UE
AxMURkggTXVlbnN0ZXIgQ0EgLSBHMDExIDAeBgkqhkiG9w0BCQEWEWNhQGZoLW11ZW5zdGVyLmRl
AgcbmYh0N7GjMIHlBgsqhkiG9w0BCRACCzGB1aCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozANBgkqhkiG9w0BAQEFAASCAQCEsHoF6y9d/h/T9TRhZ3uCOviJIUPh9aNV
ksUnsTYnbrDoN9xy4NzGspatHf93gObjt3OXtueV+5OcXHAhC5S2w+78Bn7kIrXcjIh5472p04/S
Q1FokQ0yWlffHPavfzM5iDrafOcEcO6sRDXWKSGDMHK2gi5OBeaqAOImTcG5pDmHK1MMacvjuvcb
js2+0LkVISvXkk+w4iN0FknV7+ljxfDWNMcQ+B0APSnvLjg6QMdU6DdV4tEWINbu37UN5+KyhiN8
Mnfv0JXLhQ0zw7Ms9rrKjCbdwcjIv9lLBw9LDfcJiDsquqCIAhtoc5I4jRUf61ITTWOC5qfaAF6C
ybdnAAAAAAAA
--Apple-Mail=_C4475747-0DBC-4EE5-A518-4111208F0FD3--


From nobody Thu Aug 31 05:14:21 2017
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DEF4132C28; Thu, 31 Aug 2017 05:14:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level: 
X-Spam-Status: No, score=-14.5 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uNG9WH4XqA10; Thu, 31 Aug 2017 05:14:12 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 937181321A5; Thu, 31 Aug 2017 05:14:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8285; q=dns/txt; s=iport; t=1504181651; x=1505391251; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=nbwDEJ9D8OAM51hwM7RC86bUNF+gLqGdFxrKzfU376M=; b=gJ8lUlMMb9HTFABFvR0PsW83eHNDOYNUVWUfzsQ/QDzhrsi6surFaIXC R4saLkt/6an/S2jM5GZVKfnYbBcxIJzK3cDpCr9eSYpaB1/tA7RUgFK0K KEo7k2cy1ReQFGrdbp26GWEQCqLEEFPFYeXiiMeUF5NytKvjLBwLzBsx/ c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CRAQBZ/KdZ/xbLJq1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBhVOPC5B5IneXQoVHAoRZFAECAQEBAQEBAWsohRkBBTg4CRALGC5?= =?us-ascii?q?XBg0GAgEBF4oWsSaLRQEBAQEBAQEBAgEBAQEBAQEBAQEBHYMqg1CBYysLgWVYN?= =?us-ascii?q?YppBYoIlmeIPIwVghOFZ4NZhxuNUohzNiGBDTIhCBwVhWEcgWk+NopMAQEB?=
X-IronPort-AV: E=Sophos;i="5.41,453,1498521600"; d="scan'208";a="657149266"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Aug 2017 12:14:06 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v7VCE42P014125; Thu, 31 Aug 2017 12:14:05 GMT
Subject: Re: [OPS-DIR] Opsdir last call review of draft-ietf-tsvwg-sctp-ndata-12
To: Michael Tuexen <tuexen@fh-muenster.de>
Cc: Stefan Winter <stefan.winter@restena.lu>, ops-dir@ietf.org, draft-ietf-tsvwg-sctp-ndata.all@ietf.org, tsvwg@ietf.org, ietf@ietf.org, IESG IESG <iesg@ietf.org>
References: <150287547583.12471.9085655210334710687@ietfa.amsl.com> <FDCFFA8C-8828-4578-A66E-A1AD7FF9BDC9@fh-muenster.de> <1a39dff3-55a9-fe1d-7e19-a0fbd0b2751b@restena.lu> <F05D0F1F-47E2-4477-BFD9-F0119A4609FC@fh-muenster.de> <f4d121e4-44f5-e85d-98b1-bbea317a7539@cisco.com> <5CEB294C-AAC8-4F03-901D-487CD62BB491@fh-muenster.de>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <41a1e8f1-2398-4d94-7021-638acdd58eb7@cisco.com>
Date: Thu, 31 Aug 2017 14:14:04 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <5CEB294C-AAC8-4F03-901D-487CD62BB491@fh-muenster.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hQzjvnhM6tTl0H0kg2jcoHqXRnI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 31 Aug 2017 12:14:14 -0000

Hi Michael,
>> On 30. Aug 2017, at 18:51, Benoit Claise <bclaise@cisco.com> wrote:
>>
>> Michael,
>>
>> I stumbled on the same point as Stefan.
> Hi Benoit,
>
> thanks for reviewing the document. See my comments in-line.
>
> Best regards
> Michael
>> First of, I had to review RFC4960 for TSN/SSN. I was not sure whether TSN was per stream or not
>> It would have helped me to repeat this information in the intro.
>> Ok, to be candid, I deduced this information from figure 1 and 2.
>>>>>> And the rest are only musings not needing any action if the authors don't want
>>>>>> to action on them:
>>>>>>
>>>>>> The introduction presents a good use case, quoting: "e.g., when the
>>>>>> transmission of an urgent
>>>>>>   message is blocked from transmission because the sender has started
>>>>>>   the transmission of another, possibly large, message".
>>>>>>
>>>>>> The later queueing example in figure 1 has three SIDs being queued
>>>>>> simultanseously. It is not clear which of those "has already started" and which
>>>>> There is actually one message queued for stream 0, three messages for stream 1,
>>>>> and one message for stream 2.
>>>>>> are the important ones being delayed. For a better understanding of the reader,
>>>>> The figure is about in which sequence they are put on the wire. So no
>>>>> transmission has startet. This examples also does not deal with the case
>>>>> of one stream having a higher priority than another. That would be an
>>>>> example using a priority scheduler. This examples illustrates the round
>>>>> robin scheduler.
>>>>> The point here is that a single scheduler (the round robin scheduler, for
>>>>> example) behaves differently when user message interleaving is used or not.
>>>>> That is an important point: You can even use the schedulers with regular
>>>>> DATA chunk, i.e. with user message interleaving being negotiated.
>> This was my source of confusion.
>> With figure 1 and figure 2, you want to show the effect of Round Robin Scheduler with and without User Message Interleaving, while we were expecting the figure 2 to be the solution from this spec. Hence Stefan and I were looking for this "urgent message" in figure 2.
> I don't know what you mean with "solution from this spec" means. This spec introduces
> stream schedulers and a protocol extension to allow interleaving of user messages.
> Using this to implement an "urgent" concept is only one possibility: usage of a
> strict priority scheduler (SCTP_SS_PRIO). So this "urgent" is misleading. It seems
> to ring the wrong bells. That is why I suggested to remove it...
>>>>>> it might be useful to revise the figure so that the head-of-line blocking
>>>>>> happens for SID 1 because transmission of  0 and 2 has already started (and
>>>>>> declare SID 1 to be the "important" message). The ASCII art would just have to
>>>>>> indent SID 1 content a bit (placing 0 and 2 earlier in time), and the resulting
>>>>>> serialisation would then put all the SID 1 messages at the very end, when 0 and
>>>>>> 2 have been completely submitted (right?).
>>>>> One could think about adding another example based on the priority scheduler
>>>>> and giving stream 1 a higher priority. But for illustrating the point of
>>>>> schedulers behaving differently depending on the negotiation of user message
>>>>> interleaving this seems not necessary.
>>>> That second example might indeed be useful.
>>>>
>>>> It's simply a bit strange that in the introduction you speak about an
>>>> "urgent" message (something deserving a higher-priority sending) and
>>>> that another transmission has already started - but then the example has
>>>> none of those two.
>> Exactly.
>> Please add this extra example.
>> This would also clarify from the introduction that when you write ...
>>
>>    The sending of such large messages over
>>    SCTP as specified in [RFC4960] can result in a form of sender side
>>    head of line blocking (e.g., when the transmission of an urgent
>>    message is blocked from transmission because the sender has started
>>    the transmission of another, possibly large, message).
>>
>> .. the notion of transmission urgency is not within a stream but across streams, and that can be achieved with a priority scheduler.
> I would actually prefer to remove the word "urgent" from that sentence. This just rings the wrong bells.
That's a missed opportunity in mind, but your call.
>> The text might have to be rephrased to explain that this spec provides the ability to create stream scheduler with different relative stream treatments.
> What about:
>
> OLD TEXT
>     This document also defines several stream schedulers for general SCTP
>     associations.  The stream schedulers may behave differently depending
>     on whether user message interleaving has been negotiated for the
>     association or not.
>
> NEW TEXT
>     This document also defines several stream schedulers for general SCTP
>     associations allowing different relative stream treatments.
>     The stream schedulers may behave differently depending
>     on whether user message interleaving has been negotiated for the
>     association or not.
>
> Would that address this issue?
ok.
>    
>> And also that urgent message would be placed in this high priority stream scheduler (reliable, I guess, but that's orthogonal) stream.
> I really would like to get rid of this. I don't think giving the strict
> priority scheduler as specific role here is a good idea.
>
> The RR scheduler was chosen as the simplest scheduler to illustrate
> that scheduler can behave differently when using interleaving or not.
>>> What about removing the word "urgent" from that sentence.
>>>> In fact I wonder why you speak about urgent things in the introduction
>>>> at all. Neither the scheduler nor the interleaving are designed to help
>>>> urgent things to be sent earlier.
>>>>
>>>> All they do is make the transmission fairer so that *all* chunks get a
>>>> more even serialised distribution on the wire.
>>> That is not true in general. If you use the priority scheduler, one
>>> stream gets preferred treatment. It also makes sure that the time
>>> of a message spent in the stream queue is shorter. So these messages
>>> get sent earlier.
>>> In the case of the round robin scheduler, you are right that this is
>>> about getting fairer treatment. If you take the WFQ scheduler, the
>>> streams don't get the same treatment, but it depends on the weight
>>> given to the stream.
>>>> So, rather than saying that the spec helps urgent things to be sent
>>>> earlier, it should maybe rather state that the spec helps every message
>>>> getting an equal, and equally distributed, share of the medium.
>>> It is not meant that the spec does this. It was one example, what
>>> a particular stream scheduler does. But there are multiple schedulers
>>> defined in the document.
>>>
>>> The RR scheduler example is not intended to illustrate what you can do
>>> with all the schedulers, but that using message interleaving or not
>>> has an impact on the scheduler. That is meant by stating:
>>>
>>> This document also defines several stream schedulers for general SCTP associations.
>>> The stream schedulers may behave differently depending on whether user message
>>> interleaving has been negotiated for the association or not.
>>>
>>> This is followed by illustrating this using the RR scheduler.
>>>
>>> Best regards
>> Also, I don't see the value of the last sentence in this paragraph, especially with RFC2119 MAY.
>>
>>    This section defines several stream schedulers.  The stream
>>    schedulers may behave differently depending on whether user message
>>    interleaving has been negotiated for the association or not.  An
>>    implementation MAY implement any subset of them.
> During the review the question was brought up which scheduler have to be implemented
> by an implementation. This sentence was add to address it.
> If you want, I can remove it.
The point is that the MAY is that sentence doesn't mean anything.
Maybe you mean:

An implementation MUST implement at least one stream scheduler.

Regards, B.
>>
>> Regards, Benoit


From nobody Thu Aug 31 05:26:20 2017
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C5EC132D89; Thu, 31 Aug 2017 05:26: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, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K8horQYwViPi; Thu, 31 Aug 2017 05:25:59 -0700 (PDT)
Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A9AE132D7A; Thu, 31 Aug 2017 05:25:58 -0700 (PDT)
Received: from [IPv6:2003:cd:6bcc:5600:fc86:4367:9fa8:604e] (p200300CD6BCC5600FC8643679FA8604E.dip0.t-ipconnect.de [IPv6:2003:cd:6bcc:5600:fc86:4367:9fa8:604e]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id EF2AA71E3F8DC; Thu, 31 Aug 2017 14:25:45 +0200 (CEST)
From: Michael Tuexen <tuexen@fh-muenster.de>
Message-Id: <1FFDADBA-4132-4D3B-B68C-A89A50AF1E24@fh-muenster.de>
Content-Type: multipart/signed; boundary="Apple-Mail=_AAD0B188-5B38-426F-8798-1F4C7B98335D"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [OPS-DIR] Opsdir last call review of draft-ietf-tsvwg-sctp-ndata-12
Date: Thu, 31 Aug 2017 14:25:44 +0200
In-Reply-To: <41a1e8f1-2398-4d94-7021-638acdd58eb7@cisco.com>
Cc: Stefan Winter <stefan.winter@restena.lu>, ops-dir@ietf.org, draft-ietf-tsvwg-sctp-ndata.all@ietf.org, tsvwg@ietf.org, ietf@ietf.org, IESG IESG <iesg@ietf.org>
To: Benoit Claise <bclaise@cisco.com>
References: <150287547583.12471.9085655210334710687@ietfa.amsl.com> <FDCFFA8C-8828-4578-A66E-A1AD7FF9BDC9@fh-muenster.de> <1a39dff3-55a9-fe1d-7e19-a0fbd0b2751b@restena.lu> <F05D0F1F-47E2-4477-BFD9-F0119A4609FC@fh-muenster.de> <f4d121e4-44f5-e85d-98b1-bbea317a7539@cisco.com> <5CEB294C-AAC8-4F03-901D-487CD62BB491@fh-muenster.de> <41a1e8f1-2398-4d94-7021-638acdd58eb7@cisco.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Rph9aW943LlW84vJOaOWP3f-vEU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 31 Aug 2017 12:26:02 -0000

--Apple-Mail=_AAD0B188-5B38-426F-8798-1F4C7B98335D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On 31. Aug 2017, at 14:14, Benoit Claise <bclaise@cisco.com> wrote:
>=20
> Hi Michael,
>>> On 30. Aug 2017, at 18:51, Benoit Claise <bclaise@cisco.com> wrote:
>>>=20
>>> Michael,
>>>=20
>>> I stumbled on the same point as Stefan.
>> Hi Benoit,
>>=20
>> thanks for reviewing the document. See my comments in-line.
>>=20
>> Best regards
>> Michael
>>> First of, I had to review RFC4960 for TSN/SSN. I was not sure =
whether TSN was per stream or not
>>> It would have helped me to repeat this information in the intro.
>>> Ok, to be candid, I deduced this information from figure 1 and 2.
>>>>>>> And the rest are only musings not needing any action if the =
authors don't want
>>>>>>> to action on them:
>>>>>>>=20
>>>>>>> The introduction presents a good use case, quoting: "e.g., when =
the
>>>>>>> transmission of an urgent
>>>>>>>  message is blocked from transmission because the sender has =
started
>>>>>>>  the transmission of another, possibly large, message".
>>>>>>>=20
>>>>>>> The later queueing example in figure 1 has three SIDs being =
queued
>>>>>>> simultanseously. It is not clear which of those "has already =
started" and which
>>>>>> There is actually one message queued for stream 0, three messages =
for stream 1,
>>>>>> and one message for stream 2.
>>>>>>> are the important ones being delayed. For a better understanding =
of the reader,
>>>>>> The figure is about in which sequence they are put on the wire. =
So no
>>>>>> transmission has startet. This examples also does not deal with =
the case
>>>>>> of one stream having a higher priority than another. That would =
be an
>>>>>> example using a priority scheduler. This examples illustrates the =
round
>>>>>> robin scheduler.
>>>>>> The point here is that a single scheduler (the round robin =
scheduler, for
>>>>>> example) behaves differently when user message interleaving is =
used or not.
>>>>>> That is an important point: You can even use the schedulers with =
regular
>>>>>> DATA chunk, i.e. with user message interleaving being negotiated.
>>> This was my source of confusion.
>>> With figure 1 and figure 2, you want to show the effect of Round =
Robin Scheduler with and without User Message Interleaving, while we =
were expecting the figure 2 to be the solution from this spec. Hence =
Stefan and I were looking for this "urgent message" in figure 2.
>> I don't know what you mean with "solution from this spec" means. This =
spec introduces
>> stream schedulers and a protocol extension to allow interleaving of =
user messages.
>> Using this to implement an "urgent" concept is only one possibility: =
usage of a
>> strict priority scheduler (SCTP_SS_PRIO). So this "urgent" is =
misleading. It seems
>> to ring the wrong bells. That is why I suggested to remove it...
>>>>>>> it might be useful to revise the figure so that the head-of-line =
blocking
>>>>>>> happens for SID 1 because transmission of  0 and 2 has already =
started (and
>>>>>>> declare SID 1 to be the "important" message). The ASCII art =
would just have to
>>>>>>> indent SID 1 content a bit (placing 0 and 2 earlier in time), =
and the resulting
>>>>>>> serialisation would then put all the SID 1 messages at the very =
end, when 0 and
>>>>>>> 2 have been completely submitted (right?).
>>>>>> One could think about adding another example based on the =
priority scheduler
>>>>>> and giving stream 1 a higher priority. But for illustrating the =
point of
>>>>>> schedulers behaving differently depending on the negotiation of =
user message
>>>>>> interleaving this seems not necessary.
>>>>> That second example might indeed be useful.
>>>>>=20
>>>>> It's simply a bit strange that in the introduction you speak about =
an
>>>>> "urgent" message (something deserving a higher-priority sending) =
and
>>>>> that another transmission has already started - but then the =
example has
>>>>> none of those two.
>>> Exactly.
>>> Please add this extra example.
>>> This would also clarify from the introduction that when you write =
...
>>>=20
>>>   The sending of such large messages over
>>>   SCTP as specified in [RFC4960] can result in a form of sender side
>>>   head of line blocking (e.g., when the transmission of an urgent
>>>   message is blocked from transmission because the sender has =
started
>>>   the transmission of another, possibly large, message).
>>>=20
>>> .. the notion of transmission urgency is not within a stream but =
across streams, and that can be achieved with a priority scheduler.
>> I would actually prefer to remove the word "urgent" from that =
sentence. This just rings the wrong bells.
> That's a missed opportunity in mind, but your call.
Hmm. Let me remove the word "urgent"...
>>> The text might have to be rephrased to explain that this spec =
provides the ability to create stream scheduler with different relative =
stream treatments.
>> What about:
>>=20
>> OLD TEXT
>>    This document also defines several stream schedulers for general =
SCTP
>>    associations.  The stream schedulers may behave differently =
depending
>>    on whether user message interleaving has been negotiated for the
>>    association or not.
>>=20
>> NEW TEXT
>>    This document also defines several stream schedulers for general =
SCTP
>>    associations allowing different relative stream treatments.
>>    The stream schedulers may behave differently depending
>>    on whether user message interleaving has been negotiated for the
>>    association or not.
>>=20
>> Would that address this issue?
> ok.
Fixed.
>>  =20
>>> And also that urgent message would be placed in this high priority =
stream scheduler (reliable, I guess, but that's orthogonal) stream.
>> I really would like to get rid of this. I don't think giving the =
strict
>> priority scheduler as specific role here is a good idea.
>>=20
>> The RR scheduler was chosen as the simplest scheduler to illustrate
>> that scheduler can behave differently when using interleaving or not.
>>>> What about removing the word "urgent" from that sentence.
>>>>> In fact I wonder why you speak about urgent things in the =
introduction
>>>>> at all. Neither the scheduler nor the interleaving are designed to =
help
>>>>> urgent things to be sent earlier.
>>>>>=20
>>>>> All they do is make the transmission fairer so that *all* chunks =
get a
>>>>> more even serialised distribution on the wire.
>>>> That is not true in general. If you use the priority scheduler, one
>>>> stream gets preferred treatment. It also makes sure that the time
>>>> of a message spent in the stream queue is shorter. So these =
messages
>>>> get sent earlier.
>>>> In the case of the round robin scheduler, you are right that this =
is
>>>> about getting fairer treatment. If you take the WFQ scheduler, the
>>>> streams don't get the same treatment, but it depends on the weight
>>>> given to the stream.
>>>>> So, rather than saying that the spec helps urgent things to be =
sent
>>>>> earlier, it should maybe rather state that the spec helps every =
message
>>>>> getting an equal, and equally distributed, share of the medium.
>>>> It is not meant that the spec does this. It was one example, what
>>>> a particular stream scheduler does. But there are multiple =
schedulers
>>>> defined in the document.
>>>>=20
>>>> The RR scheduler example is not intended to illustrate what you can =
do
>>>> with all the schedulers, but that using message interleaving or not
>>>> has an impact on the scheduler. That is meant by stating:
>>>>=20
>>>> This document also defines several stream schedulers for general =
SCTP associations.
>>>> The stream schedulers may behave differently depending on whether =
user message
>>>> interleaving has been negotiated for the association or not.
>>>>=20
>>>> This is followed by illustrating this using the RR scheduler.
>>>>=20
>>>> Best regards
>>> Also, I don't see the value of the last sentence in this paragraph, =
especially with RFC2119 MAY.
>>>=20
>>>   This section defines several stream schedulers.  The stream
>>>   schedulers may behave differently depending on whether user =
message
>>>   interleaving has been negotiated for the association or not.  An
>>>   implementation MAY implement any subset of them.
>> During the review the question was brought up which scheduler have to =
be implemented
>> by an implementation. This sentence was add to address it.
>> If you want, I can remove it.
> The point is that the MAY is that sentence doesn't mean anything.
> Maybe you mean:
>=20
> An implementation MUST implement at least one stream scheduler.
That would require an implementation to implement at least one of
the ones being listed. You are right in the sense that an implementation
MUST implement at least one stream scheduler, but the original text
allows that one not to be specified in this document.

Are you saying that an implementation MUST implement one of list defined
by this document?

Best regards
Michael
>=20
> Regards, B.
>>>=20
>>> Regards, Benoit
>=20


--Apple-Mail=_AAD0B188-5B38-426F-8798-1F4C7B98335D
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIQkDCCBNUw
ggO9oAMCAQICCFBOxvU9EbRkMA0GCSqGSIb3DQEBCwUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQK
ExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMw
IQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0xNDA3MjIxMjA4MjZaFw0xOTA3
MDkyMzU5MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdE
Rk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAx
BAuZgeKmFNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84Ik
Q4wcOItqaACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVg
Te3RCSMqljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sW
VlZDz+HVEz2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjggGG
MIIBgjAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1Ud
IwQYMBaAFDHDeRu69VPXF+CJei0XbAqzK50zMBIGA1UdEwEB/wQIMAYBAf8CAQIwYgYDVR0gBFsw
WTARBg8rBgEEAYGtIYIsAQEEAgIwEQYPKwYBBAGBrSGCLAEBBAMAMBEGDysGAQQBga0hgiwBAQQD
ATAPBg0rBgEEAYGtIYIsAQEEMA0GCysGAQQBga0hgiweMD4GA1UdHwQ3MDUwM6AxoC+GLWh0dHA6
Ly9wa2kwMzM2LnRlbGVzZWMuZGUvcmwvRFRfUk9PVF9DQV8yLmNybDB4BggrBgEFBQcBAQRsMGow
LAYIKwYBBQUHMAGGIGh0dHA6Ly9vY3NwMDMzNi50ZWxlc2VjLmRlL29jc3ByMDoGCCsGAQUFBzAC
hi5odHRwOi8vcGtpMDMzNi50ZWxlc2VjLmRlL2NydC9EVF9ST09UX0NBXzIuY2VyMA0GCSqGSIb3
DQEBCwUAA4IBAQBjICj9nCGGcr45Rlk5MiW8qQGbDczKfUGchm0KbiyzE1l1sTOSG2EnFv/DstU1
gvuEKgFJvWa7Zi+ywgZdbj9u4wFaW8pDY1yVtuExpx/VB19N5mWCTjL5w3x6S81NXHTuIfJ1AuxS
PtLJatOQI25JZzW+f01WpOzML8+3oZeocj7JvEDWWqQIPda8gsO3tzKOsSyOam23NQIZz/U5RFhj
pyQAELC7/E6vbi84u6VXST/YblBvLJeW3B1GmmWJz67M8uXZn1OzPqEvkqnYC8aEHwTG6x7on321
e6UC8STFJGMRNMxakyAqeYg6JUKQqWU7fIbTEhUjKfws2sw5W1QXMIIFojCCBIqgAwIBAgIHF6Qk
oQlIMzANBgkqhkiG9w0BAQsFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQ
MA4GA1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4X
DTE0MDUyNzE0NTQwOVoXDTE5MDcwOTIzNTkwMFowgcYxCzAJBgNVBAYTAkRFMRwwGgYDVQQIExNO
b3JkcmhlaW4tV2VzdGZhbGVuMREwDwYDVQQHEwhNdWVuc3RlcjEgMB4GA1UEChMXRmFjaGhvY2hz
Y2h1bGUgTXVlbnN0ZXIxIzAhBgNVBAsTGkRhdGVudmVyYXJiZWl0dW5nc3plbnRyYWxlMR0wGwYD
VQQDExRGSCBNdWVuc3RlciBDQSAtIEcwMTEgMB4GCSqGSIb3DQEJARYRY2FAZmgtbXVlbnN0ZXIu
ZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4eWyu8GzsIv0iowf2v/9BT0SmCFNX
/eyQe5BncOk1j6XIlY5bnNu1S5uBe3uVgekgTh3gJyVNlaoIfCgAjqCrNJIaNQq5fr/S6L8uFeaU
O8IF/C4RH5P7f9Hn2GUueEjmJhg9CI3LBAhrfAmEEtNmuVfDycN2MjngwDNxUNRfuXbWxuhkgDqJ
0ztJeayHGhFDrGx88eyStx40xy+0c0OFWdWxzBFQlBRHnl+zRftj3c9qy6BY+/fGaA2vV1oKr3h5
X6eyU1T8YlpP1NDe4bylqAteX01sM2Qciu8UAPnNc7Sb93TQjhCFRVDIS3CdN6AOpwz5YWEld6ey
CdmFZ7pvAgMBAAGjggH+MIIB+jASBgNVHRMBAf8ECDAGAQH/AgEBMA4GA1UdDwEB/wQEAwIBBjAR
BgNVHSAECjAIMAYGBFUdIAAwHQYDVR0OBBYEFArzW7zkMYDWNUKJptPDzzfe0d/XMB8GA1UdIwQY
MBaAFEm3xs/oPR9/6kR7Eyn38QpwPt5kMBwGA1UdEQQVMBOBEWNhQGZoLW11ZW5zdGVyLmRlMIGI
BgNVHR8EgYAwfjA9oDugOYY3aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9w
dWIvY3JsL2NhY3JsLmNybDA9oDugOYY3aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9v
dC1jYS9wdWIvY3JsL2NhY3JsLmNybDCB1wYIKwYBBQUHAQEEgcowgccwMwYIKwYBBQUHMAGGJ2h0
dHA6Ly9vY3NwLnBjYS5kZm4uZGUvT0NTUC1TZXJ2ZXIvT0NTUDBHBggrBgEFBQcwAoY7aHR0cDov
L2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRwYI
KwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2Vy
dC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBCwUAA4IBAQDeRwM11kpvuRIPuzWXLapr/ZBtB76V3cuF
l45x/Kx0u03yjB4GaBPcxihn4P1z5KhRYkDBMo8HXkOgbL59aF6VdOlCurEgZvghKvUkKOCyWeYx
S9rTGPBkbGiNn2ATVuLXzF8rDf50ynAIu3otstOOv+3Ifqi1pzCva1nO64khQA5Gd5/BNyu+YHbW
f8ERAf9leu5a7yVI7cv1gCZAHpWJpkUKmfawyY4sAJ2hbGZRBvdACOxrfbuMdSOzPneT2rlmvH+D
7M6DmzVabLYk6UtAxQhldd/T/qsHkWvaWXHt0Eb9STs2Fl03Ls7M3NyLQLhaeR3ysNURYcaEfaB+
lxN+MIIGDTCCBPWgAwIBAgIHG5mIdDexozANBgkqhkiG9w0BAQsFADCBxjELMAkGA1UEBhMCREUx
HDAaBgNVBAgTE05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQK
ExdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVu
dHJhbGUxHTAbBgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBm
aC1tdWVuc3Rlci5kZTAeFw0xNjA3MDQwNzA2MTNaFw0xOTA3MDQwNzA2MTNaMHwxCzAJBgNVBAYT
AkRFMSAwHgYDVQQKDBdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEyMDAGA1UECwwpRmFjaGJlcmVp
Y2ggRWxla3Ryb3RlY2huaWsgdW5kIEluZm9ybWF0aWsxFzAVBgNVBAMMDk1pY2hhZWwgVHVleGVu
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzJoaUG3Zm24XxA/zNg2sbFcL56w8xqMg
+X6G7UsYec3YEncnlkw3jgE5nDefos7UVoCA7wPjFTj8AQt5xfpXElnbM45IPy5Ng7g6dS7biGSM
VRACPXe1PrjgApRAwwGmCPvALnZXkmKP6Zlf+3VLfz9YWIIaeKu3jFM2Lk6Y3gr5U1l8bjHSawOo
WMlfvSsXXLT38zKW7Uz9jS278j0OqHANBPgsE6/LJoCWFInwlvybxhO3nGU7OteUGaPikqzvjLsL
YgpHDi0WjMZfVx/UtUSzZ4EJvmJTBeuVwyKnCbrawnfwYPTQQ6VE1OkAzmsMByBbEwJ996RtG//T
XCG06QIDAQABo4ICRzCCAkMwQAYDVR0gBDkwNzARBg8rBgEEAYGtIYIsAQEEAwUwEQYPKwYBBAGB
rSGCLAIBBAMBMA8GDSsGAQQBga0hgiwBAQQwCQYDVR0TBAIwADAOBgNVHQ8BAf8EBAMCBeAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBTQHa9qhKgSZgCCAPThZkXaEaJ/
dTAfBgNVHSMEGDAWgBQK81u85DGA1jVCiabTw8833tHf1zAgBgNVHREEGTAXgRV0dWV4ZW5AZmgt
bXVlbnN0ZXIuZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2Zo
LW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZu
LmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIHXBggrBgEFBQcBAQSByjCBxzAz
BggrBgEFBQcwAYYnaHR0cDovL29jc3AucGNhLmRmbi5kZS9PQ1NQLVNlcnZlci9PQ1NQMEcGCCsG
AQUFBzAChjtodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jYWNlcnQv
Y2FjZXJ0LmNydDBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDIucGNhLmRmbi5kZS9maC1tdWVuc3Rl
ci1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQELBQADggEBAEj2/6x4kzoCVIiu
aaminPrOHxACyoYsmSRjYPQpgW5xRj/FlolO1nG+ZZ11sqTb3TdCGD69ko5/zs8eGKnv/i0VLCHF
g1JLfpaxElN5RrR/cqRJrbzKshF9aUkBODF8vlf9BCeimMK3fifjbbWRyxHssfEECffujD7/Yvta
NYMO46Roz39lIK2s37IVFq3V5RWzUeTuwpP9t8lOxirOi9eK2OYI/dh0HjR2S5Dr9nMR1dNulrhz
jlFxGc+opefGScrRR9Ec0eqTXlbt1Q9UzNIYVS+OGZY8/bBbprwXVTmwSp8dygEULkIaMbLsaTaW
6TehuL8ousPJkL52SOENgSkxggQpMIIEJQIBATCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozAJBgUrDgMCGgUAoIICKzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0xNzA4MzExMjI1NDRaMCMGCSqGSIb3DQEJBDEWBBRd0E4XEZcDQqh9dQvY
p3u40gZxSjCB4wYJKwYBBAGCNxAEMYHVMIHSMIHGMQswCQYDVQQGEwJERTEcMBoGA1UECBMTTm9y
ZHJoZWluLVdlc3RmYWxlbjERMA8GA1UEBxMITXVlbnN0ZXIxIDAeBgNVBAoTF0ZhY2hob2Noc2No
dWxlIE11ZW5zdGVyMSMwIQYDVQQLExpEYXRlbnZlcmFyYmVpdHVuZ3N6ZW50cmFsZTEdMBsGA1UE
AxMURkggTXVlbnN0ZXIgQ0EgLSBHMDExIDAeBgkqhkiG9w0BCQEWEWNhQGZoLW11ZW5zdGVyLmRl
AgcbmYh0N7GjMIHlBgsqhkiG9w0BCRACCzGB1aCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozANBgkqhkiG9w0BAQEFAASCAQA84RsndYwSXhJOgw5oF/pa+A2XDuSXCSfF
v5cIHQqF4A6YOD8XolKEPG4F25qL1+h3YEe4/vqSW0XLjdDKSxld3nDjmnZpxpmFMLoZaoYzwhiG
tIig9og0nfE1lQ31qLcE+OuSWKOfrS84Xf28X0Y4ukcpfzt2C7P2F8UKh+ZPPjKl2fHlAVnNzSmg
Zxt1dhF5hW7OvMXOxXSQ5rgPlX1nuNtpqBRHRAO4rwXlju1JAkNbWprQ5ff6fN3yIrV/zPCKNUS2
mGeYECoPrRuPRNc7JgavVXFnYxPLihN701XPWxXN92eEEoA3kesETY5iTprINS+eInWRjDcH7MfA
wW7MAAAAAAAA
--Apple-Mail=_AAD0B188-5B38-426F-8798-1F4C7B98335D--


From nobody Thu Aug 31 05:50:56 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93598132D5B; Thu, 31 Aug 2017 05:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MhcSX58KI36o; Thu, 31 Aug 2017 05:50:44 -0700 (PDT)
Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A938A132D8C; Thu, 31 Aug 2017 05:50:44 -0700 (PDT)
Received: by mail-yw0-x22d.google.com with SMTP id s187so2712229ywf.2; Thu, 31 Aug 2017 05:50:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ZjTj+gd9Jygj3Ez/rXn7FvYoqYJUILFoivuog0b57C8=; b=FzT/diQtHLiDD5Z3d5uOeNPE3ZhPkBq4+dMJJRX5/8CaXWGOfpL3TP2ftBe8xugqCH vJ7PahQFq1J0PNTRRnXLEHAgT8Z6kVF+9TgpCJQdxqdhmH9sUVRxuVyPapsi4vPGLYsL fS+l9t88pNTWEKJPOcu4hHhwLnmfsWT2q+O3FNkn/Tqrvxrs4wMpGHPsbohJG03zPlDJ vIf1ToO7hugEDRsE7kTa2u/cI6nT8ngVLFmA4Pa0YjicTS97KghxwutSyC2TaqrO6rZv 1+79ZHWc2K8VHqIlJeOEe5gSmzEbUEnZjWi7BtcAXHgRqjHdm3nYuYk7xQKNaBdYX4l+ XIWg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ZjTj+gd9Jygj3Ez/rXn7FvYoqYJUILFoivuog0b57C8=; b=S3JKX6eWVyxMkTv77OZH3rX1OmPHlvitytocublNP78jON7NOL+/+N+lNpPPRU/Yd8 iRM+gKY0hf30cgzvNMpRr6KQKqj6EGo7aIWWOwceI4WPghwidD4EK0ymnnEeYDtbo/T3 HQFQTGMijbK3vIKhlmjGYH2fNQa3kn307cXdj3mlhXoyupeUyj5NAi+k9QI08Yi3Qja/ myVo0UAq0vjfwPOPvRdd+9MuCul/ZT520qav8ueSAoYMKIvOD73V+P5F+C/hZiZD1yof Upq/sVYrptOYFOhACDhCemzKNs4jvXxXz5/IPjyjFXQ/3tyooyQwqMwTmXAhh1P+pJfb K/Ww==
X-Gm-Message-State: AHYfb5j/m6Y6FBggORJ1tn1av7aHqRULSyVFiAl5U/itmUtfu70MrXsO AgpNJcfiarM9WAfqkJ72zvnc9RoCKg==
X-Google-Smtp-Source: ADKCNb4wQb4IW/X9vrVur9QB3m0/yesiu8U95f20fuxOpUOncwQQykJ/Qqbb4HwWY8/EryPHlgqYg6gLSecd8mspwQ0=
X-Received: by 10.129.122.77 with SMTP id v74mr4548310ywc.218.1504183843774; Thu, 31 Aug 2017 05:50:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.2.148 with HTTP; Thu, 31 Aug 2017 05:50:43 -0700 (PDT)
In-Reply-To: <1FFDADBA-4132-4D3B-B68C-A89A50AF1E24@fh-muenster.de>
References: <150287547583.12471.9085655210334710687@ietfa.amsl.com> <FDCFFA8C-8828-4578-A66E-A1AD7FF9BDC9@fh-muenster.de> <1a39dff3-55a9-fe1d-7e19-a0fbd0b2751b@restena.lu> <F05D0F1F-47E2-4477-BFD9-F0119A4609FC@fh-muenster.de> <f4d121e4-44f5-e85d-98b1-bbea317a7539@cisco.com> <5CEB294C-AAC8-4F03-901D-487CD62BB491@fh-muenster.de> <41a1e8f1-2398-4d94-7021-638acdd58eb7@cisco.com> <1FFDADBA-4132-4D3B-B68C-A89A50AF1E24@fh-muenster.de>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 31 Aug 2017 07:50:43 -0500
Message-ID: <CAKKJt-dM1q9NDe8r=q-aqdWW0i3i8mSYLCNssU4cvjo22GRRyw@mail.gmail.com>
Subject: Re: [OPS-DIR] Opsdir last call review of draft-ietf-tsvwg-sctp-ndata-12
To: Michael Tuexen <tuexen@fh-muenster.de>
Cc: Benoit Claise <bclaise@cisco.com>, Stefan Winter <stefan.winter@restena.lu>, "ops-dir@ietf.org" <ops-dir@ietf.org>, draft-ietf-tsvwg-sctp-ndata.all@ietf.org, "tsvwg@ietf.org" <tsvwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IESG IESG <iesg@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0a87d6af678c05580c17e6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BeCO7UAOD0NRDEFtAeYeYqCOILg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 31 Aug 2017 12:50:47 -0000

--94eb2c0a87d6af678c05580c17e6
Content-Type: text/plain; charset="UTF-8"

Just interjecting ...

On Thu, Aug 31, 2017 at 7:25 AM, Michael Tuexen <tuexen@fh-muenster.de>
wrote:

>
> > On 31. Aug 2017, at 14:14, Benoit Claise <bclaise@cisco.com> wrote:
> >
> > Hi Michael,
> >>> On 30. Aug 2017, at 18:51, Benoit Claise <bclaise@cisco.com> wrote:
> >>>
> >>> Michael,
> >>>
> >>> I stumbled on the same point as Stefan.
> >> Hi Benoit,
> >>
> >> thanks for reviewing the document. See my comments in-line.
> >>
> >> Best regards
> >> Michael
> >>> First of, I had to review RFC4960 for TSN/SSN. I was not sure whether
> TSN was per stream or not
> >>> It would have helped me to repeat this information in the intro.
> >>> Ok, to be candid, I deduced this information from figure 1 and 2.
> >>>>>>> And the rest are only musings not needing any action if the
> authors don't want
> >>>>>>> to action on them:
> >>>>>>>
> >>>>>>> The introduction presents a good use case, quoting: "e.g., when the
> >>>>>>> transmission of an urgent
> >>>>>>>  message is blocked from transmission because the sender has
> started
> >>>>>>>  the transmission of another, possibly large, message".
> >>>>>>>
> >>>>>>> The later queueing example in figure 1 has three SIDs being queued
> >>>>>>> simultanseously. It is not clear which of those "has already
> started" and which
> >>>>>> There is actually one message queued for stream 0, three messages
> for stream 1,
> >>>>>> and one message for stream 2.
> >>>>>>> are the important ones being delayed. For a better understanding
> of the reader,
> >>>>>> The figure is about in which sequence they are put on the wire. So
> no
> >>>>>> transmission has startet. This examples also does not deal with the
> case
> >>>>>> of one stream having a higher priority than another. That would be
> an
> >>>>>> example using a priority scheduler. This examples illustrates the
> round
> >>>>>> robin scheduler.
> >>>>>> The point here is that a single scheduler (the round robin
> scheduler, for
> >>>>>> example) behaves differently when user message interleaving is used
> or not.
> >>>>>> That is an important point: You can even use the schedulers with
> regular
> >>>>>> DATA chunk, i.e. with user message interleaving being negotiated.
> >>> This was my source of confusion.
> >>> With figure 1 and figure 2, you want to show the effect of Round Robin
> Scheduler with and without User Message Interleaving, while we were
> expecting the figure 2 to be the solution from this spec. Hence Stefan and
> I were looking for this "urgent message" in figure 2.
> >> I don't know what you mean with "solution from this spec" means. This
> spec introduces
> >> stream schedulers and a protocol extension to allow interleaving of
> user messages.
> >> Using this to implement an "urgent" concept is only one possibility:
> usage of a
> >> strict priority scheduler (SCTP_SS_PRIO). So this "urgent" is
> misleading. It seems
> >> to ring the wrong bells. That is why I suggested to remove it...
> >>>>>>> it might be useful to revise the figure so that the head-of-line
> blocking
> >>>>>>> happens for SID 1 because transmission of  0 and 2 has already
> started (and
> >>>>>>> declare SID 1 to be the "important" message). The ASCII art would
> just have to
> >>>>>>> indent SID 1 content a bit (placing 0 and 2 earlier in time), and
> the resulting
> >>>>>>> serialisation would then put all the SID 1 messages at the very
> end, when 0 and
> >>>>>>> 2 have been completely submitted (right?).
> >>>>>> One could think about adding another example based on the priority
> scheduler
> >>>>>> and giving stream 1 a higher priority. But for illustrating the
> point of
> >>>>>> schedulers behaving differently depending on the negotiation of
> user message
> >>>>>> interleaving this seems not necessary.
> >>>>> That second example might indeed be useful.
> >>>>>
> >>>>> It's simply a bit strange that in the introduction you speak about an
> >>>>> "urgent" message (something deserving a higher-priority sending) and
> >>>>> that another transmission has already started - but then the example
> has
> >>>>> none of those two.
> >>> Exactly.
> >>> Please add this extra example.
> >>> This would also clarify from the introduction that when you write ...
> >>>
> >>>   The sending of such large messages over
> >>>   SCTP as specified in [RFC4960] can result in a form of sender side
> >>>   head of line blocking (e.g., when the transmission of an urgent
> >>>   message is blocked from transmission because the sender has started
> >>>   the transmission of another, possibly large, message).
> >>>
> >>> .. the notion of transmission urgency is not within a stream but
> across streams, and that can be achieved with a priority scheduler.
> >> I would actually prefer to remove the word "urgent" from that sentence.
> This just rings the wrong bells.
> > That's a missed opportunity in mind, but your call.
> Hmm. Let me remove the word "urgent"...
>

Yes, please! I wasn't wild about it, either.


> >>> The text might have to be rephrased to explain that this spec provides
> the ability to create stream scheduler with different relative stream
> treatments.
> >> What about:
> >>
> >> OLD TEXT
> >>    This document also defines several stream schedulers for general SCTP
> >>    associations.  The stream schedulers may behave differently depending
> >>    on whether user message interleaving has been negotiated for the
> >>    association or not.
> >>
> >> NEW TEXT
> >>    This document also defines several stream schedulers for general SCTP
> >>    associations allowing different relative stream treatments.
> >>    The stream schedulers may behave differently depending
> >>    on whether user message interleaving has been negotiated for the
> >>    association or not.
> >>
> >> Would that address this issue?
> > ok.
> Fixed.
> >>
> >>> And also that urgent message would be placed in this high priority
> stream scheduler (reliable, I guess, but that's orthogonal) stream.
> >> I really would like to get rid of this. I don't think giving the strict
> >> priority scheduler as specific role here is a good idea.
> >>
> >> The RR scheduler was chosen as the simplest scheduler to illustrate
> >> that scheduler can behave differently when using interleaving or not.
> >>>> What about removing the word "urgent" from that sentence.
> >>>>> In fact I wonder why you speak about urgent things in the
> introduction
> >>>>> at all. Neither the scheduler nor the interleaving are designed to
> help
> >>>>> urgent things to be sent earlier.
> >>>>>
> >>>>> All they do is make the transmission fairer so that *all* chunks get
> a
> >>>>> more even serialised distribution on the wire.
> >>>> That is not true in general. If you use the priority scheduler, one
> >>>> stream gets preferred treatment. It also makes sure that the time
> >>>> of a message spent in the stream queue is shorter. So these messages
> >>>> get sent earlier.
> >>>> In the case of the round robin scheduler, you are right that this is
> >>>> about getting fairer treatment. If you take the WFQ scheduler, the
> >>>> streams don't get the same treatment, but it depends on the weight
> >>>> given to the stream.
> >>>>> So, rather than saying that the spec helps urgent things to be sent
> >>>>> earlier, it should maybe rather state that the spec helps every
> message
> >>>>> getting an equal, and equally distributed, share of the medium.
> >>>> It is not meant that the spec does this. It was one example, what
> >>>> a particular stream scheduler does. But there are multiple schedulers
> >>>> defined in the document.
> >>>>
> >>>> The RR scheduler example is not intended to illustrate what you can do
> >>>> with all the schedulers, but that using message interleaving or not
> >>>> has an impact on the scheduler. That is meant by stating:
> >>>>
> >>>> This document also defines several stream schedulers for general SCTP
> associations.
> >>>> The stream schedulers may behave differently depending on whether
> user message
> >>>> interleaving has been negotiated for the association or not.
> >>>>
> >>>> This is followed by illustrating this using the RR scheduler.
> >>>>
> >>>> Best regards
> >>> Also, I don't see the value of the last sentence in this paragraph,
> especially with RFC2119 MAY.
> >>>
> >>>   This section defines several stream schedulers.  The stream
> >>>   schedulers may behave differently depending on whether user message
> >>>   interleaving has been negotiated for the association or not.  An
> >>>   implementation MAY implement any subset of them.
> >> During the review the question was brought up which scheduler have to
> be implemented
> >> by an implementation. This sentence was add to address it.
> >> If you want, I can remove it.
> > The point is that the MAY is that sentence doesn't mean anything.
> > Maybe you mean:
> >
> > An implementation MUST implement at least one stream scheduler.
> That would require an implementation to implement at least one of
> the ones being listed. You are right in the sense that an implementation
> MUST implement at least one stream scheduler, but the original text
> allows that one not to be specified in this document.
>
> Are you saying that an implementation MUST implement one of list defined
> by this document?


I'm pretty sure (and this came up in my AD review) the problem is that the
original specification DID define a stream scheduler, that's wasn't called
a stream scheduler, but SCTP implementations did schedule streams. And that
didn't matter until there was more than one way to schedule streams (as in
this document).

So you're working out better wording that says something like "in addition
to the way the original specification scheduled streams, we're defining
more of them". I think.

?

Spencer

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

<div dir=3D"ltr">Just interjecting ...=C2=A0<div class=3D"gmail_extra"><br>=
<div class=3D"gmail_quote">On Thu, Aug 31, 2017 at 7:25 AM, Michael Tuexen =
<span dir=3D"ltr">&lt;<a href=3D"mailto:tuexen@fh-muenster.de" target=3D"_b=
lank">tuexen@fh-muenster.de</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex"><div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; On 31. Aug 2017, at 14:14, Benoit Claise &lt;<a href=3D"mailto:bclaise=
@cisco.com">bclaise@cisco.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Michael,<br>
&gt;&gt;&gt; On 30. Aug 2017, at 18:51, Benoit Claise &lt;<a href=3D"mailto=
:bclaise@cisco.com">bclaise@cisco.com</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Michael,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I stumbled on the same point as Stefan.<br>
&gt;&gt; Hi Benoit,<br>
&gt;&gt;<br>
&gt;&gt; thanks for reviewing the document. See my comments in-line.<br>
&gt;&gt;<br>
&gt;&gt; Best regards<br>
&gt;&gt; Michael<br>
&gt;&gt;&gt; First of, I had to review RFC4960 for TSN/SSN. I was not sure =
whether TSN was per stream or not<br>
&gt;&gt;&gt; It would have helped me to repeat this information in the intr=
o.<br>
&gt;&gt;&gt; Ok, to be candid, I deduced this information from figure 1 and=
 2.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; And the rest are only musings not needing any =
action if the authors don&#39;t want<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; to action on them:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; The introduction presents a good use case, quo=
ting: &quot;e.g., when the<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; transmission of an urgent<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 message is blocked from transmission bec=
ause the sender has started<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 the transmission of another, possibly la=
rge, message&quot;.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; The later queueing example in figure 1 has thr=
ee SIDs being queued<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; simultanseously. It is not clear which of thos=
e &quot;has already started&quot; and which<br>
&gt;&gt;&gt;&gt;&gt;&gt; There is actually one message queued for stream 0,=
 three messages for stream 1,<br>
&gt;&gt;&gt;&gt;&gt;&gt; and one message for stream 2.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; are the important ones being delayed. For a be=
tter understanding of the reader,<br>
&gt;&gt;&gt;&gt;&gt;&gt; The figure is about in which sequence they are put=
 on the wire. So no<br>
&gt;&gt;&gt;&gt;&gt;&gt; transmission has startet. This examples also does =
not deal with the case<br>
&gt;&gt;&gt;&gt;&gt;&gt; of one stream having a higher priority than anothe=
r. That would be an<br>
&gt;&gt;&gt;&gt;&gt;&gt; example using a priority scheduler. This examples =
illustrates the round<br>
&gt;&gt;&gt;&gt;&gt;&gt; robin scheduler.<br>
&gt;&gt;&gt;&gt;&gt;&gt; The point here is that a single scheduler (the rou=
nd robin scheduler, for<br>
&gt;&gt;&gt;&gt;&gt;&gt; example) behaves differently when user message int=
erleaving is used or not.<br>
&gt;&gt;&gt;&gt;&gt;&gt; That is an important point: You can even use the s=
chedulers with regular<br>
&gt;&gt;&gt;&gt;&gt;&gt; DATA chunk, i.e. with user message interleaving be=
ing negotiated.<br>
&gt;&gt;&gt; This was my source of confusion.<br>
&gt;&gt;&gt; With figure 1 and figure 2, you want to show the effect of Rou=
nd Robin Scheduler with and without User Message Interleaving, while we wer=
e expecting the figure 2 to be the solution from this spec. Hence Stefan an=
d I were looking for this &quot;urgent message&quot; in figure 2.<br>
&gt;&gt; I don&#39;t know what you mean with &quot;solution from this spec&=
quot; means. This spec introduces<br>
&gt;&gt; stream schedulers and a protocol extension to allow interleaving o=
f user messages.<br>
&gt;&gt; Using this to implement an &quot;urgent&quot; concept is only one =
possibility: usage of a<br>
&gt;&gt; strict priority scheduler (SCTP_SS_PRIO). So this &quot;urgent&quo=
t; is misleading. It seems<br>
&gt;&gt; to ring the wrong bells. That is why I suggested to remove it...<b=
r>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; it might be useful to revise the figure so tha=
t the head-of-line blocking<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; happens for SID 1 because transmission of=C2=
=A0 0 and 2 has already started (and<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; declare SID 1 to be the &quot;important&quot; =
message). The ASCII art would just have to<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; indent SID 1 content a bit (placing 0 and 2 ea=
rlier in time), and the resulting<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; serialisation would then put all the SID 1 mes=
sages at the very end, when 0 and<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2 have been completely submitted (right?).<br>
&gt;&gt;&gt;&gt;&gt;&gt; One could think about adding another example based=
 on the priority scheduler<br>
&gt;&gt;&gt;&gt;&gt;&gt; and giving stream 1 a higher priority. But for ill=
ustrating the point of<br>
&gt;&gt;&gt;&gt;&gt;&gt; schedulers behaving differently depending on the n=
egotiation of user message<br>
&gt;&gt;&gt;&gt;&gt;&gt; interleaving this seems not necessary.<br>
&gt;&gt;&gt;&gt;&gt; That second example might indeed be useful.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; It&#39;s simply a bit strange that in the introduction=
 you speak about an<br>
&gt;&gt;&gt;&gt;&gt; &quot;urgent&quot; message (something deserving a high=
er-priority sending) and<br>
&gt;&gt;&gt;&gt;&gt; that another transmission has already started - but th=
en the example has<br>
&gt;&gt;&gt;&gt;&gt; none of those two.<br>
&gt;&gt;&gt; Exactly.<br>
&gt;&gt;&gt; Please add this extra example.<br>
&gt;&gt;&gt; This would also clarify from the introduction that when you wr=
ite ...<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;=C2=A0 =C2=A0The sending of such large messages over<br>
&gt;&gt;&gt;=C2=A0 =C2=A0SCTP as specified in [RFC4960] can result in a for=
m of sender side<br>
&gt;&gt;&gt;=C2=A0 =C2=A0head of line blocking (e.g., when the transmission=
 of an urgent<br>
&gt;&gt;&gt;=C2=A0 =C2=A0message is blocked from transmission because the s=
ender has started<br>
&gt;&gt;&gt;=C2=A0 =C2=A0the transmission of another, possibly large, messa=
ge).<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; .. the notion of transmission urgency is not within a stream b=
ut across streams, and that can be achieved with a priority scheduler.<br>
&gt;&gt; I would actually prefer to remove the word &quot;urgent&quot; from=
 that sentence. This just rings the wrong bells.<br>
&gt; That&#39;s a missed opportunity in mind, but your call.<br>
</div></div>Hmm. Let me remove the word &quot;urgent&quot;...<br></blockquo=
te><div><br></div><div>Yes, please! I wasn&#39;t wild about it, either.</di=
v><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=3D"">&gt;&gt;&gt; The text might have to be rephrased to explai=
n that this spec provides the ability to create stream scheduler with diffe=
rent relative stream treatments.<br>
&gt;&gt; What about:<br>
&gt;&gt;<br>
&gt;&gt; OLD TEXT<br>
&gt;&gt;=C2=A0 =C2=A0 This document also defines several stream schedulers =
for general SCTP<br>
&gt;&gt;=C2=A0 =C2=A0 associations.=C2=A0 The stream schedulers may behave =
differently depending<br>
&gt;&gt;=C2=A0 =C2=A0 on whether user message interleaving has been negotia=
ted for the<br>
&gt;&gt;=C2=A0 =C2=A0 association or not.<br>
&gt;&gt;<br>
&gt;&gt; NEW TEXT<br>
&gt;&gt;=C2=A0 =C2=A0 This document also defines several stream schedulers =
for general SCTP<br>
&gt;&gt;=C2=A0 =C2=A0 associations allowing different relative stream treat=
ments.<br>
&gt;&gt;=C2=A0 =C2=A0 The stream schedulers may behave differently dependin=
g<br>
&gt;&gt;=C2=A0 =C2=A0 on whether user message interleaving has been negotia=
ted for the<br>
&gt;&gt;=C2=A0 =C2=A0 association or not.<br>
&gt;&gt;<br>
&gt;&gt; Would that address this issue?<br>
&gt; ok.<br>
</span>Fixed.<br>
<div><div class=3D"h5">&gt;&gt;<br>
&gt;&gt;&gt; And also that urgent message would be placed in this high prio=
rity stream scheduler (reliable, I guess, but that&#39;s orthogonal) stream=
.<br>
&gt;&gt; I really would like to get rid of this. I don&#39;t think giving t=
he strict<br>
&gt;&gt; priority scheduler as specific role here is a good idea.<br>
&gt;&gt;<br>
&gt;&gt; The RR scheduler was chosen as the simplest scheduler to illustrat=
e<br>
&gt;&gt; that scheduler can behave differently when using interleaving or n=
ot.<br>
&gt;&gt;&gt;&gt; What about removing the word &quot;urgent&quot; from that =
sentence.<br>
&gt;&gt;&gt;&gt;&gt; In fact I wonder why you speak about urgent things in =
the introduction<br>
&gt;&gt;&gt;&gt;&gt; at all. Neither the scheduler nor the interleaving are=
 designed to help<br>
&gt;&gt;&gt;&gt;&gt; urgent things to be sent earlier.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; All they do is make the transmission fairer so that *a=
ll* chunks get a<br>
&gt;&gt;&gt;&gt;&gt; more even serialised distribution on the wire.<br>
&gt;&gt;&gt;&gt; That is not true in general. If you use the priority sched=
uler, one<br>
&gt;&gt;&gt;&gt; stream gets preferred treatment. It also makes sure that t=
he time<br>
&gt;&gt;&gt;&gt; of a message spent in the stream queue is shorter. So thes=
e messages<br>
&gt;&gt;&gt;&gt; get sent earlier.<br>
&gt;&gt;&gt;&gt; In the case of the round robin scheduler, you are right th=
at this is<br>
&gt;&gt;&gt;&gt; about getting fairer treatment. If you take the WFQ schedu=
ler, the<br>
&gt;&gt;&gt;&gt; streams don&#39;t get the same treatment, but it depends o=
n the weight<br>
&gt;&gt;&gt;&gt; given to the stream.<br>
&gt;&gt;&gt;&gt;&gt; So, rather than saying that the spec helps urgent thin=
gs to be sent<br>
&gt;&gt;&gt;&gt;&gt; earlier, it should maybe rather state that the spec he=
lps every message<br>
&gt;&gt;&gt;&gt;&gt; getting an equal, and equally distributed, share of th=
e medium.<br>
&gt;&gt;&gt;&gt; It is not meant that the spec does this. It was one exampl=
e, what<br>
&gt;&gt;&gt;&gt; a particular stream scheduler does. But there are multiple=
 schedulers<br>
&gt;&gt;&gt;&gt; defined in the document.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The RR scheduler example is not intended to illustrate wha=
t you can do<br>
&gt;&gt;&gt;&gt; with all the schedulers, but that using message interleavi=
ng or not<br>
&gt;&gt;&gt;&gt; has an impact on the scheduler. That is meant by stating:<=
br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; This document also defines several stream schedulers for g=
eneral SCTP associations.<br>
&gt;&gt;&gt;&gt; The stream schedulers may behave differently depending on =
whether user message<br>
&gt;&gt;&gt;&gt; interleaving has been negotiated for the association or no=
t.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; This is followed by illustrating this using the RR schedul=
er.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Best regards<br>
&gt;&gt;&gt; Also, I don&#39;t see the value of the last sentence in this p=
aragraph, especially with RFC2119 MAY.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;=C2=A0 =C2=A0This section defines several stream schedulers.=C2=
=A0 The stream<br>
&gt;&gt;&gt;=C2=A0 =C2=A0schedulers may behave differently depending on whe=
ther user message<br>
&gt;&gt;&gt;=C2=A0 =C2=A0interleaving has been negotiated for the associati=
on or not.=C2=A0 An<br>
&gt;&gt;&gt;=C2=A0 =C2=A0implementation MAY implement any subset of them.<b=
r>
&gt;&gt; During the review the question was brought up which scheduler have=
 to be implemented<br>
&gt;&gt; by an implementation. This sentence was add to address it.<br>
&gt;&gt; If you want, I can remove it.<br>
&gt; The point is that the MAY is that sentence doesn&#39;t mean anything.<=
br>
&gt; Maybe you mean:<br>
&gt;<br>
&gt; An implementation MUST implement at least one stream scheduler.<br>
</div></div>That would require an implementation to implement at least one =
of<br>
the ones being listed. You are right in the sense that an implementation<br=
>
MUST implement at least one stream scheduler, but the original text<br>
allows that one not to be specified in this document.<br>
<br>
Are you saying that an implementation MUST implement one of list defined<br=
>
by this document?</blockquote><div><br></div><div>I&#39;m pretty sure (and =
this came up in my AD review) the problem is that the original specificatio=
n DID define a stream scheduler, that&#39;s wasn&#39;t called a stream sche=
duler, but SCTP implementations did schedule streams. And that didn&#39;t m=
atter until there was more than one way to schedule streams (as in this doc=
ument).</div><div><br></div><div>So you&#39;re working out better wording t=
hat says something like &quot;in addition to the way the original specifica=
tion scheduled streams, we&#39;re defining more of them&quot;. I think.</di=
v><div><br></div><div>?</div><div><br></div><div>Spencer=C2=A0</div></div><=
/div></div>

--94eb2c0a87d6af678c05580c17e6--


From nobody Thu Aug 31 06:02:47 2017
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFED1132DF7; Thu, 31 Aug 2017 06:02:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 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, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id elf2Yk8V_Moa; Thu, 31 Aug 2017 06:02:23 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 914C2132D9B; Thu, 31 Aug 2017 06:02:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1265; q=dns/txt; s=iport; t=1504184543; x=1505394143; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=Ce6yeIkEJI/s59yuKOC3mluA45IFqE6VQcAUMASkIWs=; b=cqb3CtP28o8KnQEIlizlhR/tQK/yvs9eO4VJjVPd4r9eXadzSLTESeMI IMONFglU6B22FtKeOcGfjmWOOAQelwdGlS8DjTMvu8K7mLKsHnS5yHlvn IG0lS4MUyr0kPwlGY7XU5vaV6CJsYdNdmiWvpFPs/XRxHhmI6H3N75qpY w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BsAQBYCKhZ/xbLJq1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBlF6pVIVHAoRLFAECAQEBAQEBAWsohRkGOEEQC0ZXBg0IAQGKLbB?= =?us-ascii?q?ki0YBAQEBAQEBAQEBAQEBAQEBASGDKoNQgWMrgn2KaQWgb5RRi1OHG41SiHM2I?= =?us-ascii?q?YENMiEIHBVJhx0+iwIBAQE?=
X-IronPort-AV: E=Sophos;i="5.41,453,1498521600"; d="scan'208";a="655330196"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Aug 2017 13:02:18 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v7VD2IDc002017; Thu, 31 Aug 2017 13:02:18 GMT
Subject: Re: [OPS-DIR] Opsdir last call review of draft-ietf-tsvwg-sctp-ndata-12
To: Michael Tuexen <tuexen@fh-muenster.de>
Cc: Stefan Winter <stefan.winter@restena.lu>, ops-dir@ietf.org, draft-ietf-tsvwg-sctp-ndata.all@ietf.org, tsvwg@ietf.org, ietf@ietf.org, IESG IESG <iesg@ietf.org>
References: <150287547583.12471.9085655210334710687@ietfa.amsl.com> <FDCFFA8C-8828-4578-A66E-A1AD7FF9BDC9@fh-muenster.de> <1a39dff3-55a9-fe1d-7e19-a0fbd0b2751b@restena.lu> <F05D0F1F-47E2-4477-BFD9-F0119A4609FC@fh-muenster.de> <f4d121e4-44f5-e85d-98b1-bbea317a7539@cisco.com> <5CEB294C-AAC8-4F03-901D-487CD62BB491@fh-muenster.de> <41a1e8f1-2398-4d94-7021-638acdd58eb7@cisco.com> <1FFDADBA-4132-4D3B-B68C-A89A50AF1E24@fh-muenster.de>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <cf445d0b-0de5-ca99-a3bb-53403f9d3c7a@cisco.com>
Date: Thu, 31 Aug 2017 15:02:18 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <1FFDADBA-4132-4D3B-B68C-A89A50AF1E24@fh-muenster.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5fPTbtv-x8DdHaUYjCgc8nRHDRU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 31 Aug 2017 13:02:30 -0000

>>>> Also, I don't see the value of the last sentence in this paragraph, especially with RFC2119 MAY.
>>>>
>>>>    This section defines several stream schedulers.  The stream
>>>>    schedulers may behave differently depending on whether user message
>>>>    interleaving has been negotiated for the association or not.  An
>>>>    implementation MAY implement any subset of them.
>>> During the review the question was brought up which scheduler have to be implemented
>>> by an implementation. This sentence was add to address it.
>>> If you want, I can remove it.
>> The point is that the MAY is that sentence doesn't mean anything.
>> Maybe you mean:
>>
>> An implementation MUST implement at least one stream scheduler.
> That would require an implementation to implement at least one of
> the ones being listed. You are right in the sense that an implementation
> MUST implement at least one stream scheduler, but the original text
> allows that one not to be specified in this document.
>
> Are you saying that an implementation MUST implement one of list defined
> by this document?
I'm saying that "An implementation MAY implement any subset of them." as 
a sentence doesn't make sense.
Are we going in circle here?

Regards, B.


From nobody Thu Aug 31 06:25:28 2017
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AFD4132DA2; Thu, 31 Aug 2017 06:25:26 -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, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5bk7OswzUvVw; Thu, 31 Aug 2017 06:25:23 -0700 (PDT)
Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAA40132D83; Thu, 31 Aug 2017 06:25:21 -0700 (PDT)
Received: from [IPv6:2003:cd:6bcc:5600:fc86:4367:9fa8:604e] (p200300CD6BCC5600FC8643679FA8604E.dip0.t-ipconnect.de [IPv6:2003:cd:6bcc:5600:fc86:4367:9fa8:604e]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 2A80471E3F8DC; Thu, 31 Aug 2017 15:25:04 +0200 (CEST)
From: Michael Tuexen <tuexen@fh-muenster.de>
Message-Id: <BD327429-5C8F-4034-A9E7-834FDB1E7FB6@fh-muenster.de>
Content-Type: multipart/signed; boundary="Apple-Mail=_9CC9ACD9-08A6-47E4-B2E6-EC77129A2A2A"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [OPS-DIR] Opsdir last call review of draft-ietf-tsvwg-sctp-ndata-12
Date: Thu, 31 Aug 2017 15:25:02 +0200
In-Reply-To: <CAKKJt-dM1q9NDe8r=q-aqdWW0i3i8mSYLCNssU4cvjo22GRRyw@mail.gmail.com>
Cc: Benoit Claise <bclaise@cisco.com>, Stefan Winter <stefan.winter@restena.lu>, "ops-dir@ietf.org" <ops-dir@ietf.org>, draft-ietf-tsvwg-sctp-ndata.all@ietf.org, "tsvwg@ietf.org" <tsvwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IESG IESG <iesg@ietf.org>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
References: <150287547583.12471.9085655210334710687@ietfa.amsl.com> <FDCFFA8C-8828-4578-A66E-A1AD7FF9BDC9@fh-muenster.de> <1a39dff3-55a9-fe1d-7e19-a0fbd0b2751b@restena.lu> <F05D0F1F-47E2-4477-BFD9-F0119A4609FC@fh-muenster.de> <f4d121e4-44f5-e85d-98b1-bbea317a7539@cisco.com> <5CEB294C-AAC8-4F03-901D-487CD62BB491@fh-muenster.de> <41a1e8f1-2398-4d94-7021-638acdd58eb7@cisco.com> <1FFDADBA-4132-4D3B-B68C-A89A50AF1E24@fh-muenster.de> <CAKKJt-dM1q9NDe8r=q-aqdWW0i3i8mSYLCNssU4cvjo22GRRyw@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ha80kFJZM836_qJRlfcTpYO6VyE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 31 Aug 2017 13:25:27 -0000

--Apple-Mail=_9CC9ACD9-08A6-47E4-B2E6-EC77129A2A2A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> On 31. Aug 2017, at 14:50, Spencer Dawkins at IETF =
<spencerdawkins.ietf@gmail.com> wrote:
>=20
> Just interjecting ...=20
>=20
> On Thu, Aug 31, 2017 at 7:25 AM, Michael Tuexen =
<tuexen@fh-muenster.de> wrote:
>=20
> > On 31. Aug 2017, at 14:14, Benoit Claise <bclaise@cisco.com> wrote:
> >
> > Hi Michael,
> >>> On 30. Aug 2017, at 18:51, Benoit Claise <bclaise@cisco.com> =
wrote:
> >>>
> >>> Michael,
> >>>
> >>> I stumbled on the same point as Stefan.
> >> Hi Benoit,
> >>
> >> thanks for reviewing the document. See my comments in-line.
> >>
> >> Best regards
> >> Michael
> >>> First of, I had to review RFC4960 for TSN/SSN. I was not sure =
whether TSN was per stream or not
> >>> It would have helped me to repeat this information in the intro.
> >>> Ok, to be candid, I deduced this information from figure 1 and 2.
> >>>>>>> And the rest are only musings not needing any action if the =
authors don't want
> >>>>>>> to action on them:
> >>>>>>>
> >>>>>>> The introduction presents a good use case, quoting: "e.g., =
when the
> >>>>>>> transmission of an urgent
> >>>>>>>  message is blocked from transmission because the sender has =
started
> >>>>>>>  the transmission of another, possibly large, message".
> >>>>>>>
> >>>>>>> The later queueing example in figure 1 has three SIDs being =
queued
> >>>>>>> simultanseously. It is not clear which of those "has already =
started" and which
> >>>>>> There is actually one message queued for stream 0, three =
messages for stream 1,
> >>>>>> and one message for stream 2.
> >>>>>>> are the important ones being delayed. For a better =
understanding of the reader,
> >>>>>> The figure is about in which sequence they are put on the wire. =
So no
> >>>>>> transmission has startet. This examples also does not deal with =
the case
> >>>>>> of one stream having a higher priority than another. That would =
be an
> >>>>>> example using a priority scheduler. This examples illustrates =
the round
> >>>>>> robin scheduler.
> >>>>>> The point here is that a single scheduler (the round robin =
scheduler, for
> >>>>>> example) behaves differently when user message interleaving is =
used or not.
> >>>>>> That is an important point: You can even use the schedulers =
with regular
> >>>>>> DATA chunk, i.e. with user message interleaving being =
negotiated.
> >>> This was my source of confusion.
> >>> With figure 1 and figure 2, you want to show the effect of Round =
Robin Scheduler with and without User Message Interleaving, while we =
were expecting the figure 2 to be the solution from this spec. Hence =
Stefan and I were looking for this "urgent message" in figure 2.
> >> I don't know what you mean with "solution from this spec" means. =
This spec introduces
> >> stream schedulers and a protocol extension to allow interleaving of =
user messages.
> >> Using this to implement an "urgent" concept is only one =
possibility: usage of a
> >> strict priority scheduler (SCTP_SS_PRIO). So this "urgent" is =
misleading. It seems
> >> to ring the wrong bells. That is why I suggested to remove it...
> >>>>>>> it might be useful to revise the figure so that the =
head-of-line blocking
> >>>>>>> happens for SID 1 because transmission of  0 and 2 has already =
started (and
> >>>>>>> declare SID 1 to be the "important" message). The ASCII art =
would just have to
> >>>>>>> indent SID 1 content a bit (placing 0 and 2 earlier in time), =
and the resulting
> >>>>>>> serialisation would then put all the SID 1 messages at the =
very end, when 0 and
> >>>>>>> 2 have been completely submitted (right?).
> >>>>>> One could think about adding another example based on the =
priority scheduler
> >>>>>> and giving stream 1 a higher priority. But for illustrating the =
point of
> >>>>>> schedulers behaving differently depending on the negotiation of =
user message
> >>>>>> interleaving this seems not necessary.
> >>>>> That second example might indeed be useful.
> >>>>>
> >>>>> It's simply a bit strange that in the introduction you speak =
about an
> >>>>> "urgent" message (something deserving a higher-priority sending) =
and
> >>>>> that another transmission has already started - but then the =
example has
> >>>>> none of those two.
> >>> Exactly.
> >>> Please add this extra example.
> >>> This would also clarify from the introduction that when you write =
...
> >>>
> >>>   The sending of such large messages over
> >>>   SCTP as specified in [RFC4960] can result in a form of sender =
side
> >>>   head of line blocking (e.g., when the transmission of an urgent
> >>>   message is blocked from transmission because the sender has =
started
> >>>   the transmission of another, possibly large, message).
> >>>
> >>> .. the notion of transmission urgency is not within a stream but =
across streams, and that can be achieved with a priority scheduler.
> >> I would actually prefer to remove the word "urgent" from that =
sentence. This just rings the wrong bells.
> > That's a missed opportunity in mind, but your call.
> Hmm. Let me remove the word "urgent"...
>=20
> Yes, please! I wasn't wild about it, either.
It's done:
=
https://github.com/sctplab/sctp-idata/commit/cf7b331512cd85d6195eb88fa9636=
0673293323f
> =20
> >>> The text might have to be rephrased to explain that this spec =
provides the ability to create stream scheduler with different relative =
stream treatments.
> >> What about:
> >>
> >> OLD TEXT
> >>    This document also defines several stream schedulers for general =
SCTP
> >>    associations.  The stream schedulers may behave differently =
depending
> >>    on whether user message interleaving has been negotiated for the
> >>    association or not.
> >>
> >> NEW TEXT
> >>    This document also defines several stream schedulers for general =
SCTP
> >>    associations allowing different relative stream treatments.
> >>    The stream schedulers may behave differently depending
> >>    on whether user message interleaving has been negotiated for the
> >>    association or not.
> >>
> >> Would that address this issue?
> > ok.
> Fixed.
> >>
> >>> And also that urgent message would be placed in this high priority =
stream scheduler (reliable, I guess, but that's orthogonal) stream.
> >> I really would like to get rid of this. I don't think giving the =
strict
> >> priority scheduler as specific role here is a good idea.
> >>
> >> The RR scheduler was chosen as the simplest scheduler to illustrate
> >> that scheduler can behave differently when using interleaving or =
not.
> >>>> What about removing the word "urgent" from that sentence.
> >>>>> In fact I wonder why you speak about urgent things in the =
introduction
> >>>>> at all. Neither the scheduler nor the interleaving are designed =
to help
> >>>>> urgent things to be sent earlier.
> >>>>>
> >>>>> All they do is make the transmission fairer so that *all* chunks =
get a
> >>>>> more even serialised distribution on the wire.
> >>>> That is not true in general. If you use the priority scheduler, =
one
> >>>> stream gets preferred treatment. It also makes sure that the time
> >>>> of a message spent in the stream queue is shorter. So these =
messages
> >>>> get sent earlier.
> >>>> In the case of the round robin scheduler, you are right that this =
is
> >>>> about getting fairer treatment. If you take the WFQ scheduler, =
the
> >>>> streams don't get the same treatment, but it depends on the =
weight
> >>>> given to the stream.
> >>>>> So, rather than saying that the spec helps urgent things to be =
sent
> >>>>> earlier, it should maybe rather state that the spec helps every =
message
> >>>>> getting an equal, and equally distributed, share of the medium.
> >>>> It is not meant that the spec does this. It was one example, what
> >>>> a particular stream scheduler does. But there are multiple =
schedulers
> >>>> defined in the document.
> >>>>
> >>>> The RR scheduler example is not intended to illustrate what you =
can do
> >>>> with all the schedulers, but that using message interleaving or =
not
> >>>> has an impact on the scheduler. That is meant by stating:
> >>>>
> >>>> This document also defines several stream schedulers for general =
SCTP associations.
> >>>> The stream schedulers may behave differently depending on whether =
user message
> >>>> interleaving has been negotiated for the association or not.
> >>>>
> >>>> This is followed by illustrating this using the RR scheduler.
> >>>>
> >>>> Best regards
> >>> Also, I don't see the value of the last sentence in this =
paragraph, especially with RFC2119 MAY.
> >>>
> >>>   This section defines several stream schedulers.  The stream
> >>>   schedulers may behave differently depending on whether user =
message
> >>>   interleaving has been negotiated for the association or not.  An
> >>>   implementation MAY implement any subset of them.
> >> During the review the question was brought up which scheduler have =
to be implemented
> >> by an implementation. This sentence was add to address it.
> >> If you want, I can remove it.
> > The point is that the MAY is that sentence doesn't mean anything.
> > Maybe you mean:
> >
> > An implementation MUST implement at least one stream scheduler.
> That would require an implementation to implement at least one of
> the ones being listed. You are right in the sense that an =
implementation
> MUST implement at least one stream scheduler, but the original text
> allows that one not to be specified in this document.
>=20
> Are you saying that an implementation MUST implement one of list =
defined
> by this document?
>=20
> I'm pretty sure (and this came up in my AD review) the problem is that =
the original specification DID define a stream scheduler, that's wasn't =
called a stream scheduler, but SCTP implementations did schedule =
streams. And that didn't matter until there was more than one way to =
schedule streams (as in this document).
The original specification did NOT specify a stream scheduler and left =
this completely implementation
specific.
Right now Linux is using (and only supporting a single scheduler) what =
we call in this document
SCTP_SS_FCFS. FreeBSD's default scheduler is what we call in this =
document SCTP_SS_RR and
Solaris uses one of these, forgot which one. Among these kernel =
implementations, only FreeBSD
supports multiple streams schedulers and its selection. Possibly other =
closed source SCTP
implementations might support other schedulers. Don't know.
>=20
> So you're working out better wording that says something like "in =
addition to the way the original specification scheduled streams, we're =
defining more of them". I think.
I think we wanted to say something like:

Here is a list of schedulers. Your implementation might support some of =
them, but this is
left open. So you can't rely on it.

The list of schedulers we specified includes the ones being used as =
default by FreeBSD, Linux and
Solaris and was extended by the ones supported by FreeBSD and the one =
explicitly required by
WebRTC, which is SCTP_SS_WFQ.

What about this change:

OLD TEXT:
   An implementation MAY implement any subset of them.

NEW TEXT:
   An implementation MAY implement any subset of them. If the =
implementation
   is used for WebRTC Datachannels as specified in =
[I-D.ietf-rtcweb-data-channel]
   it MUST implement the Weighted Fair Queueing Scheduler defined in =
Section 3.6.

Best regards
Michael
>=20
> ?
>=20
> Spencer=20


--Apple-Mail=_9CC9ACD9-08A6-47E4-B2E6-EC77129A2A2A
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIQkDCCBNUw
ggO9oAMCAQICCFBOxvU9EbRkMA0GCSqGSIb3DQEBCwUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQK
ExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMw
IQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0xNDA3MjIxMjA4MjZaFw0xOTA3
MDkyMzU5MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdE
Rk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAx
BAuZgeKmFNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84Ik
Q4wcOItqaACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVg
Te3RCSMqljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sW
VlZDz+HVEz2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjggGG
MIIBgjAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1Ud
IwQYMBaAFDHDeRu69VPXF+CJei0XbAqzK50zMBIGA1UdEwEB/wQIMAYBAf8CAQIwYgYDVR0gBFsw
WTARBg8rBgEEAYGtIYIsAQEEAgIwEQYPKwYBBAGBrSGCLAEBBAMAMBEGDysGAQQBga0hgiwBAQQD
ATAPBg0rBgEEAYGtIYIsAQEEMA0GCysGAQQBga0hgiweMD4GA1UdHwQ3MDUwM6AxoC+GLWh0dHA6
Ly9wa2kwMzM2LnRlbGVzZWMuZGUvcmwvRFRfUk9PVF9DQV8yLmNybDB4BggrBgEFBQcBAQRsMGow
LAYIKwYBBQUHMAGGIGh0dHA6Ly9vY3NwMDMzNi50ZWxlc2VjLmRlL29jc3ByMDoGCCsGAQUFBzAC
hi5odHRwOi8vcGtpMDMzNi50ZWxlc2VjLmRlL2NydC9EVF9ST09UX0NBXzIuY2VyMA0GCSqGSIb3
DQEBCwUAA4IBAQBjICj9nCGGcr45Rlk5MiW8qQGbDczKfUGchm0KbiyzE1l1sTOSG2EnFv/DstU1
gvuEKgFJvWa7Zi+ywgZdbj9u4wFaW8pDY1yVtuExpx/VB19N5mWCTjL5w3x6S81NXHTuIfJ1AuxS
PtLJatOQI25JZzW+f01WpOzML8+3oZeocj7JvEDWWqQIPda8gsO3tzKOsSyOam23NQIZz/U5RFhj
pyQAELC7/E6vbi84u6VXST/YblBvLJeW3B1GmmWJz67M8uXZn1OzPqEvkqnYC8aEHwTG6x7on321
e6UC8STFJGMRNMxakyAqeYg6JUKQqWU7fIbTEhUjKfws2sw5W1QXMIIFojCCBIqgAwIBAgIHF6Qk
oQlIMzANBgkqhkiG9w0BAQsFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQ
MA4GA1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4X
DTE0MDUyNzE0NTQwOVoXDTE5MDcwOTIzNTkwMFowgcYxCzAJBgNVBAYTAkRFMRwwGgYDVQQIExNO
b3JkcmhlaW4tV2VzdGZhbGVuMREwDwYDVQQHEwhNdWVuc3RlcjEgMB4GA1UEChMXRmFjaGhvY2hz
Y2h1bGUgTXVlbnN0ZXIxIzAhBgNVBAsTGkRhdGVudmVyYXJiZWl0dW5nc3plbnRyYWxlMR0wGwYD
VQQDExRGSCBNdWVuc3RlciBDQSAtIEcwMTEgMB4GCSqGSIb3DQEJARYRY2FAZmgtbXVlbnN0ZXIu
ZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4eWyu8GzsIv0iowf2v/9BT0SmCFNX
/eyQe5BncOk1j6XIlY5bnNu1S5uBe3uVgekgTh3gJyVNlaoIfCgAjqCrNJIaNQq5fr/S6L8uFeaU
O8IF/C4RH5P7f9Hn2GUueEjmJhg9CI3LBAhrfAmEEtNmuVfDycN2MjngwDNxUNRfuXbWxuhkgDqJ
0ztJeayHGhFDrGx88eyStx40xy+0c0OFWdWxzBFQlBRHnl+zRftj3c9qy6BY+/fGaA2vV1oKr3h5
X6eyU1T8YlpP1NDe4bylqAteX01sM2Qciu8UAPnNc7Sb93TQjhCFRVDIS3CdN6AOpwz5YWEld6ey
CdmFZ7pvAgMBAAGjggH+MIIB+jASBgNVHRMBAf8ECDAGAQH/AgEBMA4GA1UdDwEB/wQEAwIBBjAR
BgNVHSAECjAIMAYGBFUdIAAwHQYDVR0OBBYEFArzW7zkMYDWNUKJptPDzzfe0d/XMB8GA1UdIwQY
MBaAFEm3xs/oPR9/6kR7Eyn38QpwPt5kMBwGA1UdEQQVMBOBEWNhQGZoLW11ZW5zdGVyLmRlMIGI
BgNVHR8EgYAwfjA9oDugOYY3aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9w
dWIvY3JsL2NhY3JsLmNybDA9oDugOYY3aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9v
dC1jYS9wdWIvY3JsL2NhY3JsLmNybDCB1wYIKwYBBQUHAQEEgcowgccwMwYIKwYBBQUHMAGGJ2h0
dHA6Ly9vY3NwLnBjYS5kZm4uZGUvT0NTUC1TZXJ2ZXIvT0NTUDBHBggrBgEFBQcwAoY7aHR0cDov
L2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRwYI
KwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2Vy
dC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBCwUAA4IBAQDeRwM11kpvuRIPuzWXLapr/ZBtB76V3cuF
l45x/Kx0u03yjB4GaBPcxihn4P1z5KhRYkDBMo8HXkOgbL59aF6VdOlCurEgZvghKvUkKOCyWeYx
S9rTGPBkbGiNn2ATVuLXzF8rDf50ynAIu3otstOOv+3Ifqi1pzCva1nO64khQA5Gd5/BNyu+YHbW
f8ERAf9leu5a7yVI7cv1gCZAHpWJpkUKmfawyY4sAJ2hbGZRBvdACOxrfbuMdSOzPneT2rlmvH+D
7M6DmzVabLYk6UtAxQhldd/T/qsHkWvaWXHt0Eb9STs2Fl03Ls7M3NyLQLhaeR3ysNURYcaEfaB+
lxN+MIIGDTCCBPWgAwIBAgIHG5mIdDexozANBgkqhkiG9w0BAQsFADCBxjELMAkGA1UEBhMCREUx
HDAaBgNVBAgTE05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQK
ExdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVu
dHJhbGUxHTAbBgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBm
aC1tdWVuc3Rlci5kZTAeFw0xNjA3MDQwNzA2MTNaFw0xOTA3MDQwNzA2MTNaMHwxCzAJBgNVBAYT
AkRFMSAwHgYDVQQKDBdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEyMDAGA1UECwwpRmFjaGJlcmVp
Y2ggRWxla3Ryb3RlY2huaWsgdW5kIEluZm9ybWF0aWsxFzAVBgNVBAMMDk1pY2hhZWwgVHVleGVu
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzJoaUG3Zm24XxA/zNg2sbFcL56w8xqMg
+X6G7UsYec3YEncnlkw3jgE5nDefos7UVoCA7wPjFTj8AQt5xfpXElnbM45IPy5Ng7g6dS7biGSM
VRACPXe1PrjgApRAwwGmCPvALnZXkmKP6Zlf+3VLfz9YWIIaeKu3jFM2Lk6Y3gr5U1l8bjHSawOo
WMlfvSsXXLT38zKW7Uz9jS278j0OqHANBPgsE6/LJoCWFInwlvybxhO3nGU7OteUGaPikqzvjLsL
YgpHDi0WjMZfVx/UtUSzZ4EJvmJTBeuVwyKnCbrawnfwYPTQQ6VE1OkAzmsMByBbEwJ996RtG//T
XCG06QIDAQABo4ICRzCCAkMwQAYDVR0gBDkwNzARBg8rBgEEAYGtIYIsAQEEAwUwEQYPKwYBBAGB
rSGCLAIBBAMBMA8GDSsGAQQBga0hgiwBAQQwCQYDVR0TBAIwADAOBgNVHQ8BAf8EBAMCBeAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBTQHa9qhKgSZgCCAPThZkXaEaJ/
dTAfBgNVHSMEGDAWgBQK81u85DGA1jVCiabTw8833tHf1zAgBgNVHREEGTAXgRV0dWV4ZW5AZmgt
bXVlbnN0ZXIuZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2Zo
LW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZu
LmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIHXBggrBgEFBQcBAQSByjCBxzAz
BggrBgEFBQcwAYYnaHR0cDovL29jc3AucGNhLmRmbi5kZS9PQ1NQLVNlcnZlci9PQ1NQMEcGCCsG
AQUFBzAChjtodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jYWNlcnQv
Y2FjZXJ0LmNydDBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDIucGNhLmRmbi5kZS9maC1tdWVuc3Rl
ci1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQELBQADggEBAEj2/6x4kzoCVIiu
aaminPrOHxACyoYsmSRjYPQpgW5xRj/FlolO1nG+ZZ11sqTb3TdCGD69ko5/zs8eGKnv/i0VLCHF
g1JLfpaxElN5RrR/cqRJrbzKshF9aUkBODF8vlf9BCeimMK3fifjbbWRyxHssfEECffujD7/Yvta
NYMO46Roz39lIK2s37IVFq3V5RWzUeTuwpP9t8lOxirOi9eK2OYI/dh0HjR2S5Dr9nMR1dNulrhz
jlFxGc+opefGScrRR9Ec0eqTXlbt1Q9UzNIYVS+OGZY8/bBbprwXVTmwSp8dygEULkIaMbLsaTaW
6TehuL8ousPJkL52SOENgSkxggQpMIIEJQIBATCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozAJBgUrDgMCGgUAoIICKzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0xNzA4MzExMzI1MDNaMCMGCSqGSIb3DQEJBDEWBBTud2ygZ2M1PUXG/Tfk
zVgB/c0a/zCB4wYJKwYBBAGCNxAEMYHVMIHSMIHGMQswCQYDVQQGEwJERTEcMBoGA1UECBMTTm9y
ZHJoZWluLVdlc3RmYWxlbjERMA8GA1UEBxMITXVlbnN0ZXIxIDAeBgNVBAoTF0ZhY2hob2Noc2No
dWxlIE11ZW5zdGVyMSMwIQYDVQQLExpEYXRlbnZlcmFyYmVpdHVuZ3N6ZW50cmFsZTEdMBsGA1UE
AxMURkggTXVlbnN0ZXIgQ0EgLSBHMDExIDAeBgkqhkiG9w0BCQEWEWNhQGZoLW11ZW5zdGVyLmRl
AgcbmYh0N7GjMIHlBgsqhkiG9w0BCRACCzGB1aCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozANBgkqhkiG9w0BAQEFAASCAQC93atIFKzuhKDcSAioqnSJ93THbuE3jW2T
+HtMjLaTptpcye+AIfk1S0bo8QSbpCvTL9PDvdK+pSId4zA1kgnk+Hnb7K5OuE1X112EU5jl1D3h
+TzOi+vbuDD4qVadWCyb97xXz11eckdRUlmpqi4SquLusgSZp/lr+pLe9tq8v72MOQOiUxbQUFBo
w4TGCijBXsEzwbspQrdbzsCSlLcGuNPIumBURm5QzWvzYagIMsKX16/XguV+VwicS5RI9NQ9YnbT
0CIhO3gWck5YhvLW/hjx+U+Z+DNG9+HD2dAzdUqI8PIZovnJhDhy+KfhxdpW4chf/Gr/AbqqTC15
5sdbAAAAAAAA
--Apple-Mail=_9CC9ACD9-08A6-47E4-B2E6-EC77129A2A2A--


From nobody Thu Aug 31 06:26:16 2017
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB7D0132DF4; Thu, 31 Aug 2017 06:25:47 -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, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UGz4zIxfN024; Thu, 31 Aug 2017 06:25:45 -0700 (PDT)
Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3260B132E07; Thu, 31 Aug 2017 06:25:39 -0700 (PDT)
Received: from [IPv6:2003:cd:6bcc:5600:fc86:4367:9fa8:604e] (p200300CD6BCC5600FC8643679FA8604E.dip0.t-ipconnect.de [IPv6:2003:cd:6bcc:5600:fc86:4367:9fa8:604e]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 18DB071E3F8E0; Thu, 31 Aug 2017 15:25:23 +0200 (CEST)
From: Michael Tuexen <tuexen@fh-muenster.de>
Message-Id: <33532776-F3E6-443A-B26C-2F80BC2F88E3@fh-muenster.de>
Content-Type: multipart/signed; boundary="Apple-Mail=_98D04D7E-A798-47F3-8D52-6AB88EFB5EB3"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [OPS-DIR] Opsdir last call review of draft-ietf-tsvwg-sctp-ndata-12
Date: Thu, 31 Aug 2017 15:25:22 +0200
In-Reply-To: <cf445d0b-0de5-ca99-a3bb-53403f9d3c7a@cisco.com>
Cc: Stefan Winter <stefan.winter@restena.lu>, ops-dir@ietf.org, draft-ietf-tsvwg-sctp-ndata.all@ietf.org, tsvwg@ietf.org, ietf@ietf.org, IESG IESG <iesg@ietf.org>
To: Benoit Claise <bclaise@cisco.com>
References: <150287547583.12471.9085655210334710687@ietfa.amsl.com> <FDCFFA8C-8828-4578-A66E-A1AD7FF9BDC9@fh-muenster.de> <1a39dff3-55a9-fe1d-7e19-a0fbd0b2751b@restena.lu> <F05D0F1F-47E2-4477-BFD9-F0119A4609FC@fh-muenster.de> <f4d121e4-44f5-e85d-98b1-bbea317a7539@cisco.com> <5CEB294C-AAC8-4F03-901D-487CD62BB491@fh-muenster.de> <41a1e8f1-2398-4d94-7021-638acdd58eb7@cisco.com> <1FFDADBA-4132-4D3B-B68C-A89A50AF1E24@fh-muenster.de> <cf445d0b-0de5-ca99-a3bb-53403f9d3c7a@cisco.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hf6X7APGoFyaJ_6HFnh1iDTe1O0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 31 Aug 2017 13:25:48 -0000

--Apple-Mail=_98D04D7E-A798-47F3-8D52-6AB88EFB5EB3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On 31. Aug 2017, at 15:02, Benoit Claise <bclaise@cisco.com> wrote:
>=20
>=20
>>>>> Also, I don't see the value of the last sentence in this =
paragraph, especially with RFC2119 MAY.
>>>>>=20
>>>>>   This section defines several stream schedulers.  The stream
>>>>>   schedulers may behave differently depending on whether user =
message
>>>>>   interleaving has been negotiated for the association or not.  An
>>>>>   implementation MAY implement any subset of them.
>>>> During the review the question was brought up which scheduler have =
to be implemented
>>>> by an implementation. This sentence was add to address it.
>>>> If you want, I can remove it.
>>> The point is that the MAY is that sentence doesn't mean anything.
>>> Maybe you mean:
>>>=20
>>> An implementation MUST implement at least one stream scheduler.
>> That would require an implementation to implement at least one of
>> the ones being listed. You are right in the sense that an =
implementation
>> MUST implement at least one stream scheduler, but the original text
>> allows that one not to be specified in this document.
>>=20
>> Are you saying that an implementation MUST implement one of list =
defined
>> by this document?
> I'm saying that "An implementation MAY implement any subset of them." =
as a sentence doesn't make sense.
> Are we going in circle here?
What about:

What about this change:

OLD TEXT:
   An implementation MAY implement any subset of them.

NEW TEXT:
   An implementation MAY implement any subset of them. If the =
implementation
   is used for WebRTC Datachannels as specified in =
[I-D.ietf-rtcweb-data-channel]
   it MUST implement the Weighted Fair Queueing Scheduler defined in =
Section 3.6.

Best regards
Michael
>=20
> Regards, B.


--Apple-Mail=_98D04D7E-A798-47F3-8D52-6AB88EFB5EB3
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIQkDCCBNUw
ggO9oAMCAQICCFBOxvU9EbRkMA0GCSqGSIb3DQEBCwUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQK
ExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMw
IQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0xNDA3MjIxMjA4MjZaFw0xOTA3
MDkyMzU5MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdE
Rk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAx
BAuZgeKmFNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84Ik
Q4wcOItqaACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVg
Te3RCSMqljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sW
VlZDz+HVEz2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjggGG
MIIBgjAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1Ud
IwQYMBaAFDHDeRu69VPXF+CJei0XbAqzK50zMBIGA1UdEwEB/wQIMAYBAf8CAQIwYgYDVR0gBFsw
WTARBg8rBgEEAYGtIYIsAQEEAgIwEQYPKwYBBAGBrSGCLAEBBAMAMBEGDysGAQQBga0hgiwBAQQD
ATAPBg0rBgEEAYGtIYIsAQEEMA0GCysGAQQBga0hgiweMD4GA1UdHwQ3MDUwM6AxoC+GLWh0dHA6
Ly9wa2kwMzM2LnRlbGVzZWMuZGUvcmwvRFRfUk9PVF9DQV8yLmNybDB4BggrBgEFBQcBAQRsMGow
LAYIKwYBBQUHMAGGIGh0dHA6Ly9vY3NwMDMzNi50ZWxlc2VjLmRlL29jc3ByMDoGCCsGAQUFBzAC
hi5odHRwOi8vcGtpMDMzNi50ZWxlc2VjLmRlL2NydC9EVF9ST09UX0NBXzIuY2VyMA0GCSqGSIb3
DQEBCwUAA4IBAQBjICj9nCGGcr45Rlk5MiW8qQGbDczKfUGchm0KbiyzE1l1sTOSG2EnFv/DstU1
gvuEKgFJvWa7Zi+ywgZdbj9u4wFaW8pDY1yVtuExpx/VB19N5mWCTjL5w3x6S81NXHTuIfJ1AuxS
PtLJatOQI25JZzW+f01WpOzML8+3oZeocj7JvEDWWqQIPda8gsO3tzKOsSyOam23NQIZz/U5RFhj
pyQAELC7/E6vbi84u6VXST/YblBvLJeW3B1GmmWJz67M8uXZn1OzPqEvkqnYC8aEHwTG6x7on321
e6UC8STFJGMRNMxakyAqeYg6JUKQqWU7fIbTEhUjKfws2sw5W1QXMIIFojCCBIqgAwIBAgIHF6Qk
oQlIMzANBgkqhkiG9w0BAQsFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQ
MA4GA1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4X
DTE0MDUyNzE0NTQwOVoXDTE5MDcwOTIzNTkwMFowgcYxCzAJBgNVBAYTAkRFMRwwGgYDVQQIExNO
b3JkcmhlaW4tV2VzdGZhbGVuMREwDwYDVQQHEwhNdWVuc3RlcjEgMB4GA1UEChMXRmFjaGhvY2hz
Y2h1bGUgTXVlbnN0ZXIxIzAhBgNVBAsTGkRhdGVudmVyYXJiZWl0dW5nc3plbnRyYWxlMR0wGwYD
VQQDExRGSCBNdWVuc3RlciBDQSAtIEcwMTEgMB4GCSqGSIb3DQEJARYRY2FAZmgtbXVlbnN0ZXIu
ZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4eWyu8GzsIv0iowf2v/9BT0SmCFNX
/eyQe5BncOk1j6XIlY5bnNu1S5uBe3uVgekgTh3gJyVNlaoIfCgAjqCrNJIaNQq5fr/S6L8uFeaU
O8IF/C4RH5P7f9Hn2GUueEjmJhg9CI3LBAhrfAmEEtNmuVfDycN2MjngwDNxUNRfuXbWxuhkgDqJ
0ztJeayHGhFDrGx88eyStx40xy+0c0OFWdWxzBFQlBRHnl+zRftj3c9qy6BY+/fGaA2vV1oKr3h5
X6eyU1T8YlpP1NDe4bylqAteX01sM2Qciu8UAPnNc7Sb93TQjhCFRVDIS3CdN6AOpwz5YWEld6ey
CdmFZ7pvAgMBAAGjggH+MIIB+jASBgNVHRMBAf8ECDAGAQH/AgEBMA4GA1UdDwEB/wQEAwIBBjAR
BgNVHSAECjAIMAYGBFUdIAAwHQYDVR0OBBYEFArzW7zkMYDWNUKJptPDzzfe0d/XMB8GA1UdIwQY
MBaAFEm3xs/oPR9/6kR7Eyn38QpwPt5kMBwGA1UdEQQVMBOBEWNhQGZoLW11ZW5zdGVyLmRlMIGI
BgNVHR8EgYAwfjA9oDugOYY3aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9w
dWIvY3JsL2NhY3JsLmNybDA9oDugOYY3aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9v
dC1jYS9wdWIvY3JsL2NhY3JsLmNybDCB1wYIKwYBBQUHAQEEgcowgccwMwYIKwYBBQUHMAGGJ2h0
dHA6Ly9vY3NwLnBjYS5kZm4uZGUvT0NTUC1TZXJ2ZXIvT0NTUDBHBggrBgEFBQcwAoY7aHR0cDov
L2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRwYI
KwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2Vy
dC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBCwUAA4IBAQDeRwM11kpvuRIPuzWXLapr/ZBtB76V3cuF
l45x/Kx0u03yjB4GaBPcxihn4P1z5KhRYkDBMo8HXkOgbL59aF6VdOlCurEgZvghKvUkKOCyWeYx
S9rTGPBkbGiNn2ATVuLXzF8rDf50ynAIu3otstOOv+3Ifqi1pzCva1nO64khQA5Gd5/BNyu+YHbW
f8ERAf9leu5a7yVI7cv1gCZAHpWJpkUKmfawyY4sAJ2hbGZRBvdACOxrfbuMdSOzPneT2rlmvH+D
7M6DmzVabLYk6UtAxQhldd/T/qsHkWvaWXHt0Eb9STs2Fl03Ls7M3NyLQLhaeR3ysNURYcaEfaB+
lxN+MIIGDTCCBPWgAwIBAgIHG5mIdDexozANBgkqhkiG9w0BAQsFADCBxjELMAkGA1UEBhMCREUx
HDAaBgNVBAgTE05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQK
ExdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVu
dHJhbGUxHTAbBgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBm
aC1tdWVuc3Rlci5kZTAeFw0xNjA3MDQwNzA2MTNaFw0xOTA3MDQwNzA2MTNaMHwxCzAJBgNVBAYT
AkRFMSAwHgYDVQQKDBdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEyMDAGA1UECwwpRmFjaGJlcmVp
Y2ggRWxla3Ryb3RlY2huaWsgdW5kIEluZm9ybWF0aWsxFzAVBgNVBAMMDk1pY2hhZWwgVHVleGVu
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzJoaUG3Zm24XxA/zNg2sbFcL56w8xqMg
+X6G7UsYec3YEncnlkw3jgE5nDefos7UVoCA7wPjFTj8AQt5xfpXElnbM45IPy5Ng7g6dS7biGSM
VRACPXe1PrjgApRAwwGmCPvALnZXkmKP6Zlf+3VLfz9YWIIaeKu3jFM2Lk6Y3gr5U1l8bjHSawOo
WMlfvSsXXLT38zKW7Uz9jS278j0OqHANBPgsE6/LJoCWFInwlvybxhO3nGU7OteUGaPikqzvjLsL
YgpHDi0WjMZfVx/UtUSzZ4EJvmJTBeuVwyKnCbrawnfwYPTQQ6VE1OkAzmsMByBbEwJ996RtG//T
XCG06QIDAQABo4ICRzCCAkMwQAYDVR0gBDkwNzARBg8rBgEEAYGtIYIsAQEEAwUwEQYPKwYBBAGB
rSGCLAIBBAMBMA8GDSsGAQQBga0hgiwBAQQwCQYDVR0TBAIwADAOBgNVHQ8BAf8EBAMCBeAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBTQHa9qhKgSZgCCAPThZkXaEaJ/
dTAfBgNVHSMEGDAWgBQK81u85DGA1jVCiabTw8833tHf1zAgBgNVHREEGTAXgRV0dWV4ZW5AZmgt
bXVlbnN0ZXIuZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2Zo
LW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZu
LmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIHXBggrBgEFBQcBAQSByjCBxzAz
BggrBgEFBQcwAYYnaHR0cDovL29jc3AucGNhLmRmbi5kZS9PQ1NQLVNlcnZlci9PQ1NQMEcGCCsG
AQUFBzAChjtodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jYWNlcnQv
Y2FjZXJ0LmNydDBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDIucGNhLmRmbi5kZS9maC1tdWVuc3Rl
ci1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQELBQADggEBAEj2/6x4kzoCVIiu
aaminPrOHxACyoYsmSRjYPQpgW5xRj/FlolO1nG+ZZ11sqTb3TdCGD69ko5/zs8eGKnv/i0VLCHF
g1JLfpaxElN5RrR/cqRJrbzKshF9aUkBODF8vlf9BCeimMK3fifjbbWRyxHssfEECffujD7/Yvta
NYMO46Roz39lIK2s37IVFq3V5RWzUeTuwpP9t8lOxirOi9eK2OYI/dh0HjR2S5Dr9nMR1dNulrhz
jlFxGc+opefGScrRR9Ec0eqTXlbt1Q9UzNIYVS+OGZY8/bBbprwXVTmwSp8dygEULkIaMbLsaTaW
6TehuL8ousPJkL52SOENgSkxggQpMIIEJQIBATCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozAJBgUrDgMCGgUAoIICKzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0xNzA4MzExMzI1MjNaMCMGCSqGSIb3DQEJBDEWBBSLT+lVYYcU8DYKBFMc
nYrMCgulhjCB4wYJKwYBBAGCNxAEMYHVMIHSMIHGMQswCQYDVQQGEwJERTEcMBoGA1UECBMTTm9y
ZHJoZWluLVdlc3RmYWxlbjERMA8GA1UEBxMITXVlbnN0ZXIxIDAeBgNVBAoTF0ZhY2hob2Noc2No
dWxlIE11ZW5zdGVyMSMwIQYDVQQLExpEYXRlbnZlcmFyYmVpdHVuZ3N6ZW50cmFsZTEdMBsGA1UE
AxMURkggTXVlbnN0ZXIgQ0EgLSBHMDExIDAeBgkqhkiG9w0BCQEWEWNhQGZoLW11ZW5zdGVyLmRl
AgcbmYh0N7GjMIHlBgsqhkiG9w0BCRACCzGB1aCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozANBgkqhkiG9w0BAQEFAASCAQAw0aYxbowsuYNAg2cB9jQhf6o3xJVLe4Wu
6ExQL6l2M5bnia72kAcXNW+fOKLTiCNCl47pvc8US/uVxBC+GqiB1aJNn394cs+drIwos9DW+mL7
j/1wuD8QDYjbZOgMfeasFk8lyB9mL7XvUSaFueZnDbEiUnOne4qq5fTduKdFGtqLzs3BtQ9fR7ce
3NjZ0gTgGhXeU/ckQ0vo0FGrtZNfEameKBZYpb+7L/PsHSx/wfuf1BOBTv2rRM+fPpJFfdGUXpM6
Cn02I4oBwoYS50b+aN0JmMjOXWCk5kYZrG1AQiJ/PadS9cfbcFgoEkG8RzXIrjTsqaxduYmQQlJW
fAOVAAAAAAAA
--Apple-Mail=_98D04D7E-A798-47F3-8D52-6AB88EFB5EB3--


From nobody Thu Aug 31 06:46:26 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CD67132DA2; Thu, 31 Aug 2017 06:46:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bI-WytcrKvSk; Thu, 31 Aug 2017 06:46:14 -0700 (PDT)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7C22132D91; Thu, 31 Aug 2017 06:46:13 -0700 (PDT)
Received: by mail-yw0-x22a.google.com with SMTP id s143so3527047ywg.0; Thu, 31 Aug 2017 06:46:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=mfiZmmQ/N6ptode9/iozv1GiLqTvO9Tlyu6sve+pne4=; b=oEcs9orssIoUlouJSL4KDUXeuhvR0ebGidbmRkjQQVbGZvRJ1R6WipV/jirnuroimF 8w0WjPrsuOMGN60zjSBqbGMmj8+fDwry+dOg5MHazCVo0LqmklY823WpHMbLqjfcapeW S8VbnmIe3mWx5xEgRuRqX/u//2IYINxPG7dm9kd5g05GU/1R8qLP+wikdeSveCtgxqbL xY1LJSUwz5Q6gsUR7vFd+zqRZGS6ie32wn+TqkbJexIdHN5zatXB/nknxeDkCesx7WLt 578afsq7ePrx9lG4V/Rzqn+R5ceGZXg9pw1QANzbb8C66RyFKf/z7MbjgRqXtxDvZJHa p4Pw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=mfiZmmQ/N6ptode9/iozv1GiLqTvO9Tlyu6sve+pne4=; b=ColzcBSrZmCwcHoggdmw0iiGBKTkg0yJtpzoAYzlYzLhZybYTTgQdO9VuNa/i0+7lI f1vX2LxidneVejc3vIp0GqtO1nbkABnonAbTUEMXUOGeMLKZ0Y2dES8an2st4JtiMtNf CprmRSoF5vM02caaZXv8QuM8U3aaDtUDiBssfxnntFBcVw19e42uuXf+3sMKeH8GAZiN yrgAW9Gf2LxR6N8XQ20fZ7eklS2zVBLrJs1wRwfudqKuFsaUUDJCsKj9vbvAb2/xp2r9 AAbdsvLOBDL8Ux9vgSnwrmAuHCO9a7a9DclV/BeUJOZ1IWOyPQPI9fHxZTvETg4fJUMN RQzA==
X-Gm-Message-State: AHYfb5gPR+K08Xb2S+Hmkcqao6Gn3QFyKCk17NMP1Dg0R7POIexn1fqE /n/3550hj+RKpuYxdoh//hCfMXrvpg==
X-Google-Smtp-Source: ADKCNb67xkl4YjMIvf0aEzbKvML+Gi5V01zAMq23HQkdMte+Y1uCZAJ6lMRQzVQlwudE8jlbQYQlAUM4c9wonhFzlI8=
X-Received: by 10.129.122.77 with SMTP id v74mr4748957ywc.218.1504187173028; Thu, 31 Aug 2017 06:46:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.2.148 with HTTP; Thu, 31 Aug 2017 06:46:12 -0700 (PDT)
In-Reply-To: <BD327429-5C8F-4034-A9E7-834FDB1E7FB6@fh-muenster.de>
References: <150287547583.12471.9085655210334710687@ietfa.amsl.com> <FDCFFA8C-8828-4578-A66E-A1AD7FF9BDC9@fh-muenster.de> <1a39dff3-55a9-fe1d-7e19-a0fbd0b2751b@restena.lu> <F05D0F1F-47E2-4477-BFD9-F0119A4609FC@fh-muenster.de> <f4d121e4-44f5-e85d-98b1-bbea317a7539@cisco.com> <5CEB294C-AAC8-4F03-901D-487CD62BB491@fh-muenster.de> <41a1e8f1-2398-4d94-7021-638acdd58eb7@cisco.com> <1FFDADBA-4132-4D3B-B68C-A89A50AF1E24@fh-muenster.de> <CAKKJt-dM1q9NDe8r=q-aqdWW0i3i8mSYLCNssU4cvjo22GRRyw@mail.gmail.com> <BD327429-5C8F-4034-A9E7-834FDB1E7FB6@fh-muenster.de>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 31 Aug 2017 08:46:12 -0500
Message-ID: <CAKKJt-fuJWEMd79Z2zRmg4GU8hpVcqSfN+Y6xLioMUmwu8d6fw@mail.gmail.com>
Subject: Re: [OPS-DIR] Opsdir last call review of draft-ietf-tsvwg-sctp-ndata-12
To: Michael Tuexen <tuexen@fh-muenster.de>
Cc: Benoit Claise <bclaise@cisco.com>, Stefan Winter <stefan.winter@restena.lu>, "ops-dir@ietf.org" <ops-dir@ietf.org>, draft-ietf-tsvwg-sctp-ndata.all@ietf.org, "tsvwg@ietf.org" <tsvwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IESG IESG <iesg@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0a87d61fc74005580cde5e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VKRlTIvP7emJQq3jxbIh_qSnvoE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 31 Aug 2017 13:46:18 -0000

--94eb2c0a87d61fc74005580cde5e
Content-Type: text/plain; charset="UTF-8"

Hi, Michael,

On Thu, Aug 31, 2017 at 8:25 AM, Michael Tuexen <tuexen@fh-muenster.de>
wrote:

> > On 31. Aug 2017, at 14:50, Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
> >
> > Just interjecting ...
> >
> > On Thu, Aug 31, 2017 at 7:25 AM, Michael Tuexen <tuexen@fh-muenster.de>
> wrote:
> >
> > > On 31. Aug 2017, at 14:14, Benoit Claise <bclaise@cisco.com> wrote:
> > >
> > > Hi Michael,
> > >>> On 30. Aug 2017, at 18:51, Benoit Claise <bclaise@cisco.com> wrote:
> > >>>
> > >>> Michael,
> > >>>
> > >>> I stumbled on the same point as Stefan.
> > >> Hi Benoit,
> > >>
> > >> thanks for reviewing the document. See my comments in-line.
> > >>
> > >> Best regards
> > >> Michael
> > >>> First of, I had to review RFC4960 for TSN/SSN. I was not sure
> whether TSN was per stream or not
> > >>> It would have helped me to repeat this information in the intro.
> > >>> Ok, to be candid, I deduced this information from figure 1 and 2.
> > >>>>>>> And the rest are only musings not needing any action if the
> authors don't want
> > >>>>>>> to action on them:
> > >>>>>>>
> > >>>>>>> The introduction presents a good use case, quoting: "e.g., when
> the
> > >>>>>>> transmission of an urgent
> > >>>>>>>  message is blocked from transmission because the sender has
> started
> > >>>>>>>  the transmission of another, possibly large, message".
> > >>>>>>>
> > >>>>>>> The later queueing example in figure 1 has three SIDs being
> queued
> > >>>>>>> simultanseously. It is not clear which of those "has already
> started" and which
> > >>>>>> There is actually one message queued for stream 0, three messages
> for stream 1,
> > >>>>>> and one message for stream 2.
> > >>>>>>> are the important ones being delayed. For a better understanding
> of the reader,
> > >>>>>> The figure is about in which sequence they are put on the wire.
> So no
> > >>>>>> transmission has startet. This examples also does not deal with
> the case
> > >>>>>> of one stream having a higher priority than another. That would
> be an
> > >>>>>> example using a priority scheduler. This examples illustrates the
> round
> > >>>>>> robin scheduler.
> > >>>>>> The point here is that a single scheduler (the round robin
> scheduler, for
> > >>>>>> example) behaves differently when user message interleaving is
> used or not.
> > >>>>>> That is an important point: You can even use the schedulers with
> regular
> > >>>>>> DATA chunk, i.e. with user message interleaving being negotiated.
> > >>> This was my source of confusion.
> > >>> With figure 1 and figure 2, you want to show the effect of Round
> Robin Scheduler with and without User Message Interleaving, while we were
> expecting the figure 2 to be the solution from this spec. Hence Stefan and
> I were looking for this "urgent message" in figure 2.
> > >> I don't know what you mean with "solution from this spec" means. This
> spec introduces
> > >> stream schedulers and a protocol extension to allow interleaving of
> user messages.
> > >> Using this to implement an "urgent" concept is only one possibility:
> usage of a
> > >> strict priority scheduler (SCTP_SS_PRIO). So this "urgent" is
> misleading. It seems
> > >> to ring the wrong bells. That is why I suggested to remove it...
> > >>>>>>> it might be useful to revise the figure so that the head-of-line
> blocking
> > >>>>>>> happens for SID 1 because transmission of  0 and 2 has already
> started (and
> > >>>>>>> declare SID 1 to be the "important" message). The ASCII art
> would just have to
> > >>>>>>> indent SID 1 content a bit (placing 0 and 2 earlier in time),
> and the resulting
> > >>>>>>> serialisation would then put all the SID 1 messages at the very
> end, when 0 and
> > >>>>>>> 2 have been completely submitted (right?).
> > >>>>>> One could think about adding another example based on the
> priority scheduler
> > >>>>>> and giving stream 1 a higher priority. But for illustrating the
> point of
> > >>>>>> schedulers behaving differently depending on the negotiation of
> user message
> > >>>>>> interleaving this seems not necessary.
> > >>>>> That second example might indeed be useful.
> > >>>>>
> > >>>>> It's simply a bit strange that in the introduction you speak about
> an
> > >>>>> "urgent" message (something deserving a higher-priority sending)
> and
> > >>>>> that another transmission has already started - but then the
> example has
> > >>>>> none of those two.
> > >>> Exactly.
> > >>> Please add this extra example.
> > >>> This would also clarify from the introduction that when you write ...
> > >>>
> > >>>   The sending of such large messages over
> > >>>   SCTP as specified in [RFC4960] can result in a form of sender side
> > >>>   head of line blocking (e.g., when the transmission of an urgent
> > >>>   message is blocked from transmission because the sender has started
> > >>>   the transmission of another, possibly large, message).
> > >>>
> > >>> .. the notion of transmission urgency is not within a stream but
> across streams, and that can be achieved with a priority scheduler.
> > >> I would actually prefer to remove the word "urgent" from that
> sentence. This just rings the wrong bells.
> > > That's a missed opportunity in mind, but your call.
> > Hmm. Let me remove the word "urgent"...
> >
> > Yes, please! I wasn't wild about it, either.
> It's done:
> https://github.com/sctplab/sctp-idata/commit/
> cf7b331512cd85d6195eb88fa96360673293323f
> >
> > >>> The text might have to be rephrased to explain that this spec
> provides the ability to create stream scheduler with different relative
> stream treatments.
> > >> What about:
> > >>
> > >> OLD TEXT
> > >>    This document also defines several stream schedulers for general
> SCTP
> > >>    associations.  The stream schedulers may behave differently
> depending
> > >>    on whether user message interleaving has been negotiated for the
> > >>    association or not.
> > >>
> > >> NEW TEXT
> > >>    This document also defines several stream schedulers for general
> SCTP
> > >>    associations allowing different relative stream treatments.
> > >>    The stream schedulers may behave differently depending
> > >>    on whether user message interleaving has been negotiated for the
> > >>    association or not.
> > >>
> > >> Would that address this issue?
> > > ok.
> > Fixed.
> > >>
> > >>> And also that urgent message would be placed in this high priority
> stream scheduler (reliable, I guess, but that's orthogonal) stream.
> > >> I really would like to get rid of this. I don't think giving the
> strict
> > >> priority scheduler as specific role here is a good idea.
> > >>
> > >> The RR scheduler was chosen as the simplest scheduler to illustrate
> > >> that scheduler can behave differently when using interleaving or not.
> > >>>> What about removing the word "urgent" from that sentence.
> > >>>>> In fact I wonder why you speak about urgent things in the
> introduction
> > >>>>> at all. Neither the scheduler nor the interleaving are designed to
> help
> > >>>>> urgent things to be sent earlier.
> > >>>>>
> > >>>>> All they do is make the transmission fairer so that *all* chunks
> get a
> > >>>>> more even serialised distribution on the wire.
> > >>>> That is not true in general. If you use the priority scheduler, one
> > >>>> stream gets preferred treatment. It also makes sure that the time
> > >>>> of a message spent in the stream queue is shorter. So these messages
> > >>>> get sent earlier.
> > >>>> In the case of the round robin scheduler, you are right that this is
> > >>>> about getting fairer treatment. If you take the WFQ scheduler, the
> > >>>> streams don't get the same treatment, but it depends on the weight
> > >>>> given to the stream.
> > >>>>> So, rather than saying that the spec helps urgent things to be sent
> > >>>>> earlier, it should maybe rather state that the spec helps every
> message
> > >>>>> getting an equal, and equally distributed, share of the medium.
> > >>>> It is not meant that the spec does this. It was one example, what
> > >>>> a particular stream scheduler does. But there are multiple
> schedulers
> > >>>> defined in the document.
> > >>>>
> > >>>> The RR scheduler example is not intended to illustrate what you can
> do
> > >>>> with all the schedulers, but that using message interleaving or not
> > >>>> has an impact on the scheduler. That is meant by stating:
> > >>>>
> > >>>> This document also defines several stream schedulers for general
> SCTP associations.
> > >>>> The stream schedulers may behave differently depending on whether
> user message
> > >>>> interleaving has been negotiated for the association or not.
> > >>>>
> > >>>> This is followed by illustrating this using the RR scheduler.
> > >>>>
> > >>>> Best regards
> > >>> Also, I don't see the value of the last sentence in this paragraph,
> especially with RFC2119 MAY.
> > >>>
> > >>>   This section defines several stream schedulers.  The stream
> > >>>   schedulers may behave differently depending on whether user message
> > >>>   interleaving has been negotiated for the association or not.  An
> > >>>   implementation MAY implement any subset of them.
> > >> During the review the question was brought up which scheduler have to
> be implemented
> > >> by an implementation. This sentence was add to address it.
> > >> If you want, I can remove it.
> > > The point is that the MAY is that sentence doesn't mean anything.
> > > Maybe you mean:
> > >
> > > An implementation MUST implement at least one stream scheduler.
> > That would require an implementation to implement at least one of
> > the ones being listed. You are right in the sense that an implementation
> > MUST implement at least one stream scheduler, but the original text
> > allows that one not to be specified in this document.
> >
> > Are you saying that an implementation MUST implement one of list defined
> > by this document?
> >
> > I'm pretty sure (and this came up in my AD review) the problem is that
> the original specification DID define a stream scheduler, that's wasn't
> called a stream scheduler, but SCTP implementations did schedule streams.
> And that didn't matter until there was more than one way to schedule
> streams (as in this document).
> The original specification did NOT specify a stream scheduler and left
> this completely implementation
> specific.
> Right now Linux is using (and only supporting a single scheduler) what we
> call in this document
> SCTP_SS_FCFS. FreeBSD's default scheduler is what we call in this document
> SCTP_SS_RR and
> Solaris uses one of these, forgot which one. Among these kernel
> implementations, only FreeBSD
> supports multiple streams schedulers and its selection. Possibly other
> closed source SCTP
> implementations might support other schedulers. Don't know.


Thanks for getting that right for me ...

Spencer


>  > So you're working out better wording that says something like "in
> addition to the way the original specification scheduled streams, we're
> defining more of them". I think.

I think we wanted to say something like:
>
> Here is a list of schedulers. Your implementation might support some of
> them, but this is
> left open. So you can't rely on it.
>
> The list of schedulers we specified includes the ones being used as
> default by FreeBSD, Linux and
> Solaris and was extended by the ones supported by FreeBSD and the one
> explicitly required by
> WebRTC, which is SCTP_SS_WFQ.
>
> What about this change:
>
> OLD TEXT:
>    An implementation MAY implement any subset of them.
>
> NEW TEXT:
>    An implementation MAY implement any subset of them. If the
> implementation
>    is used for WebRTC Datachannels as specified in
> [I-D.ietf-rtcweb-data-channel]
>    it MUST implement the Weighted Fair Queueing Scheduler defined in
> Section 3.6.


That works for me, but I'll let Benoit reply.

Spencer


> Best regards
> Michael
> >
> > ?
> >
> > Spencer
>
>

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

<div dir=3D"ltr">Hi, Michael,<div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Thu, Aug 31, 2017 at 8:25 AM, Michael Tuexen <span dir=3D"lt=
r">&lt;<a href=3D"mailto:tuexen@fh-muenster.de" target=3D"_blank">tuexen@fh=
-muenster.de</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div c=
lass=3D"HOEnZb"><div class=3D"h5">&gt; On 31. Aug 2017, at 14:50, Spencer D=
awkins at IETF &lt;<a href=3D"mailto:spencerdawkins.ietf@gmail.com">spencer=
dawkins.ietf@gmail.com</a><wbr>&gt; wrote:<br>
&gt;<br>
&gt; Just interjecting ...<br>
&gt;<br>
&gt; On Thu, Aug 31, 2017 at 7:25 AM, Michael Tuexen &lt;<a href=3D"mailto:=
tuexen@fh-muenster.de">tuexen@fh-muenster.de</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt; On 31. Aug 2017, at 14:14, Benoit Claise &lt;<a href=3D"mailto:bc=
laise@cisco.com">bclaise@cisco.com</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; Hi Michael,<br>
&gt; &gt;&gt;&gt; On 30. Aug 2017, at 18:51, Benoit Claise &lt;<a href=3D"m=
ailto:bclaise@cisco.com">bclaise@cisco.com</a>&gt; wrote:<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Michael,<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; I stumbled on the same point as Stefan.<br>
&gt; &gt;&gt; Hi Benoit,<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; thanks for reviewing the document. See my comments in-line.<b=
r>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Best regards<br>
&gt; &gt;&gt; Michael<br>
&gt; &gt;&gt;&gt; First of, I had to review RFC4960 for TSN/SSN. I was not =
sure whether TSN was per stream or not<br>
&gt; &gt;&gt;&gt; It would have helped me to repeat this information in the=
 intro.<br>
&gt; &gt;&gt;&gt; Ok, to be candid, I deduced this information from figure =
1 and 2.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; And the rest are only musings not needing=
 any action if the authors don&#39;t want<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; to action on them:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; The introduction presents a good use case=
, quoting: &quot;e.g., when the<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; transmission of an urgent<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 message is blocked from transmissio=
n because the sender has started<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 the transmission of another, possib=
ly large, message&quot;.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; The later queueing example in figure 1 ha=
s three SIDs being queued<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; simultanseously. It is not clear which of=
 those &quot;has already started&quot; and which<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; There is actually one message queued for stre=
am 0, three messages for stream 1,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; and one message for stream 2.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; are the important ones being delayed. For=
 a better understanding of the reader,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; The figure is about in which sequence they ar=
e put on the wire. So no<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; transmission has startet. This examples also =
does not deal with the case<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; of one stream having a higher priority than a=
nother. That would be an<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; example using a priority scheduler. This exam=
ples illustrates the round<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; robin scheduler.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; The point here is that a single scheduler (th=
e round robin scheduler, for<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; example) behaves differently when user messag=
e interleaving is used or not.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; That is an important point: You can even use =
the schedulers with regular<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; DATA chunk, i.e. with user message interleavi=
ng being negotiated.<br>
&gt; &gt;&gt;&gt; This was my source of confusion.<br>
&gt; &gt;&gt;&gt; With figure 1 and figure 2, you want to show the effect o=
f Round Robin Scheduler with and without User Message Interleaving, while w=
e were expecting the figure 2 to be the solution from this spec. Hence Stef=
an and I were looking for this &quot;urgent message&quot; in figure 2.<br>
&gt; &gt;&gt; I don&#39;t know what you mean with &quot;solution from this =
spec&quot; means. This spec introduces<br>
&gt; &gt;&gt; stream schedulers and a protocol extension to allow interleav=
ing of user messages.<br>
&gt; &gt;&gt; Using this to implement an &quot;urgent&quot; concept is only=
 one possibility: usage of a<br>
&gt; &gt;&gt; strict priority scheduler (SCTP_SS_PRIO). So this &quot;urgen=
t&quot; is misleading. It seems<br>
&gt; &gt;&gt; to ring the wrong bells. That is why I suggested to remove it=
...<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; it might be useful to revise the figure s=
o that the head-of-line blocking<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; happens for SID 1 because transmission of=
=C2=A0 0 and 2 has already started (and<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; declare SID 1 to be the &quot;important&q=
uot; message). The ASCII art would just have to<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; indent SID 1 content a bit (placing 0 and=
 2 earlier in time), and the resulting<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; serialisation would then put all the SID =
1 messages at the very end, when 0 and<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; 2 have been completely submitted (right?)=
.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; One could think about adding another example =
based on the priority scheduler<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; and giving stream 1 a higher priority. But fo=
r illustrating the point of<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; schedulers behaving differently depending on =
the negotiation of user message<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; interleaving this seems not necessary.<br>
&gt; &gt;&gt;&gt;&gt;&gt; That second example might indeed be useful.<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; It&#39;s simply a bit strange that in the introdu=
ction you speak about an<br>
&gt; &gt;&gt;&gt;&gt;&gt; &quot;urgent&quot; message (something deserving a=
 higher-priority sending) and<br>
&gt; &gt;&gt;&gt;&gt;&gt; that another transmission has already started - b=
ut then the example has<br>
&gt; &gt;&gt;&gt;&gt;&gt; none of those two.<br>
&gt; &gt;&gt;&gt; Exactly.<br>
&gt; &gt;&gt;&gt; Please add this extra example.<br>
&gt; &gt;&gt;&gt; This would also clarify from the introduction that when y=
ou write ...<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;=C2=A0 =C2=A0The sending of such large messages over<br>
&gt; &gt;&gt;&gt;=C2=A0 =C2=A0SCTP as specified in [RFC4960] can result in =
a form of sender side<br>
&gt; &gt;&gt;&gt;=C2=A0 =C2=A0head of line blocking (e.g., when the transmi=
ssion of an urgent<br>
&gt; &gt;&gt;&gt;=C2=A0 =C2=A0message is blocked from transmission because =
the sender has started<br>
&gt; &gt;&gt;&gt;=C2=A0 =C2=A0the transmission of another, possibly large, =
message).<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; .. the notion of transmission urgency is not within a str=
eam but across streams, and that can be achieved with a priority scheduler.=
<br>
&gt; &gt;&gt; I would actually prefer to remove the word &quot;urgent&quot;=
 from that sentence. This just rings the wrong bells.<br>
&gt; &gt; That&#39;s a missed opportunity in mind, but your call.<br>
&gt; Hmm. Let me remove the word &quot;urgent&quot;...<br>
&gt;<br>
&gt; Yes, please! I wasn&#39;t wild about it, either.<br>
</div></div>It&#39;s done:<br>
<a href=3D"https://github.com/sctplab/sctp-idata/commit/cf7b331512cd85d6195=
eb88fa96360673293323f" rel=3D"noreferrer" target=3D"_blank">https://github.=
com/sctplab/<wbr>sctp-idata/commit/<wbr>cf7b331512cd85d6195eb88fa96360<wbr>=
673293323f</a><br>
<div><div class=3D"h5">&gt;<br>
&gt; &gt;&gt;&gt; The text might have to be rephrased to explain that this =
spec provides the ability to create stream scheduler with different relativ=
e stream treatments.<br>
&gt; &gt;&gt; What about:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; OLD TEXT<br>
&gt; &gt;&gt;=C2=A0 =C2=A0 This document also defines several stream schedu=
lers for general SCTP<br>
&gt; &gt;&gt;=C2=A0 =C2=A0 associations.=C2=A0 The stream schedulers may be=
have differently depending<br>
&gt; &gt;&gt;=C2=A0 =C2=A0 on whether user message interleaving has been ne=
gotiated for the<br>
&gt; &gt;&gt;=C2=A0 =C2=A0 association or not.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; NEW TEXT<br>
&gt; &gt;&gt;=C2=A0 =C2=A0 This document also defines several stream schedu=
lers for general SCTP<br>
&gt; &gt;&gt;=C2=A0 =C2=A0 associations allowing different relative stream =
treatments.<br>
&gt; &gt;&gt;=C2=A0 =C2=A0 The stream schedulers may behave differently dep=
ending<br>
&gt; &gt;&gt;=C2=A0 =C2=A0 on whether user message interleaving has been ne=
gotiated for the<br>
&gt; &gt;&gt;=C2=A0 =C2=A0 association or not.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Would that address this issue?<br>
&gt; &gt; ok.<br>
&gt; Fixed.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt; And also that urgent message would be placed in this high=
 priority stream scheduler (reliable, I guess, but that&#39;s orthogonal) s=
tream.<br>
&gt; &gt;&gt; I really would like to get rid of this. I don&#39;t think giv=
ing the strict<br>
&gt; &gt;&gt; priority scheduler as specific role here is a good idea.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; The RR scheduler was chosen as the simplest scheduler to illu=
strate<br>
&gt; &gt;&gt; that scheduler can behave differently when using interleaving=
 or not.<br>
&gt; &gt;&gt;&gt;&gt; What about removing the word &quot;urgent&quot; from =
that sentence.<br>
&gt; &gt;&gt;&gt;&gt;&gt; In fact I wonder why you speak about urgent thing=
s in the introduction<br>
&gt; &gt;&gt;&gt;&gt;&gt; at all. Neither the scheduler nor the interleavin=
g are designed to help<br>
&gt; &gt;&gt;&gt;&gt;&gt; urgent things to be sent earlier.<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; All they do is make the transmission fairer so th=
at *all* chunks get a<br>
&gt; &gt;&gt;&gt;&gt;&gt; more even serialised distribution on the wire.<br=
>
&gt; &gt;&gt;&gt;&gt; That is not true in general. If you use the priority =
scheduler, one<br>
&gt; &gt;&gt;&gt;&gt; stream gets preferred treatment. It also makes sure t=
hat the time<br>
&gt; &gt;&gt;&gt;&gt; of a message spent in the stream queue is shorter. So=
 these messages<br>
&gt; &gt;&gt;&gt;&gt; get sent earlier.<br>
&gt; &gt;&gt;&gt;&gt; In the case of the round robin scheduler, you are rig=
ht that this is<br>
&gt; &gt;&gt;&gt;&gt; about getting fairer treatment. If you take the WFQ s=
cheduler, the<br>
&gt; &gt;&gt;&gt;&gt; streams don&#39;t get the same treatment, but it depe=
nds on the weight<br>
&gt; &gt;&gt;&gt;&gt; given to the stream.<br>
&gt; &gt;&gt;&gt;&gt;&gt; So, rather than saying that the spec helps urgent=
 things to be sent<br>
&gt; &gt;&gt;&gt;&gt;&gt; earlier, it should maybe rather state that the sp=
ec helps every message<br>
&gt; &gt;&gt;&gt;&gt;&gt; getting an equal, and equally distributed, share =
of the medium.<br>
&gt; &gt;&gt;&gt;&gt; It is not meant that the spec does this. It was one e=
xample, what<br>
&gt; &gt;&gt;&gt;&gt; a particular stream scheduler does. But there are mul=
tiple schedulers<br>
&gt; &gt;&gt;&gt;&gt; defined in the document.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; The RR scheduler example is not intended to illustrat=
e what you can do<br>
&gt; &gt;&gt;&gt;&gt; with all the schedulers, but that using message inter=
leaving or not<br>
&gt; &gt;&gt;&gt;&gt; has an impact on the scheduler. That is meant by stat=
ing:<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; This document also defines several stream schedulers =
for general SCTP associations.<br>
&gt; &gt;&gt;&gt;&gt; The stream schedulers may behave differently dependin=
g on whether user message<br>
&gt; &gt;&gt;&gt;&gt; interleaving has been negotiated for the association =
or not.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; This is followed by illustrating this using the RR sc=
heduler.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Best regards<br>
&gt; &gt;&gt;&gt; Also, I don&#39;t see the value of the last sentence in t=
his paragraph, especially with RFC2119 MAY.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;=C2=A0 =C2=A0This section defines several stream scheduler=
s.=C2=A0 The stream<br>
&gt; &gt;&gt;&gt;=C2=A0 =C2=A0schedulers may behave differently depending o=
n whether user message<br>
&gt; &gt;&gt;&gt;=C2=A0 =C2=A0interleaving has been negotiated for the asso=
ciation or not.=C2=A0 An<br>
&gt; &gt;&gt;&gt;=C2=A0 =C2=A0implementation MAY implement any subset of th=
em.<br>
&gt; &gt;&gt; During the review the question was brought up which scheduler=
 have to be implemented<br>
&gt; &gt;&gt; by an implementation. This sentence was add to address it.<br=
>
&gt; &gt;&gt; If you want, I can remove it.<br>
&gt; &gt; The point is that the MAY is that sentence doesn&#39;t mean anyth=
ing.<br>
&gt; &gt; Maybe you mean:<br>
&gt; &gt;<br>
&gt; &gt; An implementation MUST implement at least one stream scheduler.<b=
r>
&gt; That would require an implementation to implement at least one of<br>
&gt; the ones being listed. You are right in the sense that an implementati=
on<br>
&gt; MUST implement at least one stream scheduler, but the original text<br=
>
&gt; allows that one not to be specified in this document.<br>
&gt;<br>
&gt; Are you saying that an implementation MUST implement one of list defin=
ed<br>
&gt; by this document?<br>
&gt;<br>
&gt; I&#39;m pretty sure (and this came up in my AD review) the problem is =
that the original specification DID define a stream scheduler, that&#39;s w=
asn&#39;t called a stream scheduler, but SCTP implementations did schedule =
streams. And that didn&#39;t matter until there was more than one way to sc=
hedule streams (as in this document).<br>
</div></div>The original specification did NOT specify a stream scheduler a=
nd left this completely implementation<br>
specific.<br>
Right now Linux is using (and only supporting a single scheduler) what we c=
all in this document<br>
SCTP_SS_FCFS. FreeBSD&#39;s default scheduler is what we call in this docum=
ent SCTP_SS_RR and<br>
Solaris uses one of these, forgot which one. Among these kernel implementat=
ions, only FreeBSD<br>
supports multiple streams schedulers and its selection. Possibly other clos=
ed source SCTP<br>
implementations might support other schedulers. Don&#39;t know.</blockquote=
><div><br></div><div>Thanks for getting that right for me ...</div><div><br=
></div><div>Spencer</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">=
=C2=A0&gt; So you&#39;re working out better wording that says something lik=
e &quot;in addition to the way the original specification scheduled streams=
, we&#39;re defining more of them&quot;. I think.</blockquote><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">I think we wanted to say something like:<br>
<br>
Here is a list of schedulers. Your implementation might support some of the=
m, but this is<br>
left open. So you can&#39;t rely on it.<br>
<br>
The list of schedulers we specified includes the ones being used as default=
 by FreeBSD, Linux and<br>
Solaris and was extended by the ones supported by FreeBSD and the one expli=
citly required by<br>
WebRTC, which is SCTP_SS_WFQ.<br>
<br>
What about this change:<br>
<br>
OLD TEXT:<br>
<span class=3D"">=C2=A0 =C2=A0An implementation MAY implement any subset of=
 them.<br>
<br>
</span>NEW TEXT:<br>
=C2=A0 =C2=A0An implementation MAY implement any subset of them. If the imp=
lementation<br>
=C2=A0 =C2=A0is used for WebRTC Datachannels as specified in [I-D.ietf-rtcw=
eb-data-channel]<br>
=C2=A0 =C2=A0it MUST implement the Weighted Fair Queueing Scheduler defined=
 in Section 3.6.</blockquote><div><br></div><div>That works for me, but I&#=
39;ll let Benoit reply.</div><div><br></div><div>Spencer</div><div>=C2=A0</=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">Best regards<br>
Michael<br>
&gt;<br>
&gt; ?<br>
&gt;<br>
&gt; Spencer<br>
<br>
</blockquote></div><br></div></div>

--94eb2c0a87d61fc74005580cde5e--


From nobody Thu Aug 31 07:39:16 2017
Return-Path: <mranga@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D6E8132DF0; Thu, 31 Aug 2017 07:39:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TPa7L4sAbQcd; Thu, 31 Aug 2017 07:39:10 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 659C8132E13; Thu, 31 Aug 2017 07:39:07 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id v2so6285104wmf.0; Thu, 31 Aug 2017 07:39:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=It9yk55Cg9x59By8gfRA1zp0v4KLs7UIz40Zw4xeD1g=; b=AjaTQkH2I5Tl31T+03GbPYVrcDsOsdy66ASICKClysQ6dZjeGOyg52KTQPygRDAb/d idQDXIkQ6/PgvhxJqdIrtzmeKZPe70LuJUl1DfRG4nI+cHXgCc17zux5Q6+V596f4Wg2 yDEgeO0Kj/mmz4gyeLrmMBXbD4adt/JqDWKmJXc55fYb/mR83WvYSMb+vSUqkjXOE1fK 4l2CV1xJVrRofeBmO5EiyjrPEysi4bovAhUmawbUcWXZHTH6BIY3ifNUUYffHp6FezsF Jdtgw0WiYSK1HRIv3NozPP1bo6cPJOs7Z4BztARWYdDtX9sNxCj/SUv4nycz773Xnthx CIDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=It9yk55Cg9x59By8gfRA1zp0v4KLs7UIz40Zw4xeD1g=; b=uEAuMRFGzDw2+AOIqZXHrg+xsEUCMme5FCqbixvxy93qqp2cSRMbRPvLAaLnmmBU2Y Cl9NHVk9CN7jLkf6hE01Lbv9l2noisLu0h7A96ogTNaP+e8dEONVSkWWQ1r+1/kbIwCl kPRfgbzvrSQsVeK25W+ILXU7xY1eN+8HDIseEktS1bnVspBsBzeM1EoESk1BFRORqWJC hhBtBrzx9a8FQ/cYjkfb4+88HomWFQRBfp4HOVVFZC9IR5quBZ9NrJb+asbypyy6Ozni S+OThYhYdyM3uq9Vedkz4Rjzt0QkZ/EN6CoVF/xHTxlM2srzDzlR88fGx54cPtVnzWpS A6iQ==
X-Gm-Message-State: AHPjjUiq8g6ODlje22/oYUa/kisOoCZYNoOMpDgLWGw8rIrr//8IxDKY NhhvQ2YL1zTwfsGAMfgyHQOYqWgO3Q==
X-Google-Smtp-Source: ADKCNb7zbhHE2Ulc3DVXkk4nmfGIHnXxu1R0sxAlirDfGtqhkFcBWXQRa1J1R7HQUuiOC5npM/nOIGU/onWoMFrRNnc=
X-Received: by 10.28.95.134 with SMTP id t128mr624749wmb.67.1504190345428; Thu, 31 Aug 2017 07:39:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.184.71 with HTTP; Thu, 31 Aug 2017 07:38:24 -0700 (PDT)
In-Reply-To: <8a26b512-495b-4315-a885-32acd41c5460@cisco.com>
References: <150411366399.21627.17047458871931107094@ietfa.amsl.com> <CAHiu4JMCtxFY9qu6q4h30Y=GExx69yLg7xRbSirgURy=7+4_Lw@mail.gmail.com> <8a26b512-495b-4315-a885-32acd41c5460@cisco.com>
From: "M. Ranganathan" <mranga@gmail.com>
Date: Thu, 31 Aug 2017 10:38:24 -0400
Message-ID: <CAHiu4JNQL60xjp2rBQ3t4ZAn63gNoN5LgTcGUG8k474DJvDgDQ@mail.gmail.com>
Subject: Re: [OPSAWG] Genart early review of draft-ietf-opsawg-mud-08
To: Eliot Lear <lear@cisco.com>
Cc: Robert Sparks <rjsparks@nostrum.com>, gen-art@ietf.org,  draft-ietf-opsawg-mud.all@ietf.org, opsawg@ietf.org, ietf@ietf.org
Content-Type: multipart/alternative; boundary="001a1148e96e36c57605580d9b61"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hk3emGSkxvaz-VzMt8zUpxYSLfA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 31 Aug 2017 14:39:12 -0000

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

Hi Eliot,

Reply in line below:

On Thu, Aug 31, 2017 at 4:41 AM, Eliot Lear <lear@cisco.com> wrote:

> Hi Ranga,
>
> Robert wrote a great review, and I'll respond to him in due course with
> suggested changes.  I wanted to take just a moment to comment to you on
> your point:
>
> On 8/31/17 12:00 AM, M. Ranganathan wrote:
>
>
>
> On Wed, Aug 30, 2017 at 1:21 PM, Robert Sparks <rjsparks@nostrum.com>
> wrote:
>
>>
>>
>> Right now, you leave the DHCP server (when it's used) responsible for
>> clearing state in the MUD controller. Please discuss what happens when
>> those are distinct elements (as you have in the end of section 9.2) and
>> the DHCP server reboots. Perhaps it would make sense for the DHCP server
>> to hand the length of the lease it has granted to the MUD controller and
>> let the MUD controller clean up on its own?
>>
>
> I would like to add a few words to the comprehensive review presented by
> Robert Sparks (I hope it is proper etiquette on this list to do so).
>
> With respect to the observation above:
>
> There is also a cache timeout in the MUD profile. Does it make sense  that
> the MUD controller should take the minimum of the DHCP lease time and the
> cache timeout and use that to time out the installed ACLs (?) The DHCP
> server should also  pass to the MUD controller, some way of identifying the
> device to which the lease has been granted (for example the MAC address of
> the device).
>
> The draft also not specify how the DHCP server will communicate with the
> MUD controller (presumably via a simple REST interface but what is the URL
> to be used and how are the parameters passed?). I think this should be
> specified for interoperability between DHCP clients and MUD servers. Maybe
> words describing this interaction can be added here.
>
>
> That's right.  At the moment, this is an "internalized" function.  That is
> to say that the DHCP server is said to be tightly coupled to the MUD
> controller without standardized interfaces.  In my first implementation, I
> literally just tailed dhcpd syslog entries and triggered MUD based on
> DHCPREQUEST messages.  Clean-up state had to do with RELEASE or periodic
> SNMP queries.  Our implementation at Cisco does something different.
>
> However... if the OPSAWG would like, and there is interest, we can
> formalize that interface.  I don't want to do it in THIS draft (it's
> already fairly involved), but there's nothing to say we couldn't do some
> follow-on work.
>
> Fair enough?
>
> Eliot
>

No problem with waiting to see if there's interest from OPSAWG and others
before considering this.

By way of explanation on why I think this makes sense to standardize in MUD:

I had envisioned an architecture where the MUD controller runs in the
Service Provider cloud. The DHCP server would run in the CPE router (e.g.
as part of the firmware on a home router + NAT ).

If the statement above makes sense, since the home router is typically not
made by the same party as the service provider software, I was thinking
there should be a standardized interface between the DHCP server and MUD
controller.

Thanks.

Ranga




-- 
M. Ranganathan

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

<div dir=3D"ltr"><div>Hi Eliot,<br><br></div>Reply in line below:<br><div><=
div><div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, =
Aug 31, 2017 at 4:41 AM, Eliot Lear <span dir=3D"ltr">&lt;<a href=3D"mailto=
:lear@cisco.com" target=3D"_blank">lear@cisco.com</a>&gt;</span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF">
    <p>Hi Ranga,</p>
    <p>Robert wrote a great review, and I&#39;ll respond to him in due
      course with suggested changes.=C2=A0 I wanted to take just a moment t=
o
      comment to you on your point:<br>
    </p><span class=3D"gmail-">
    <br>
    <div class=3D"gmail-m_-5244440299816673032moz-cite-prefix">On 8/31/17 1=
2:00 AM, M. Ranganathan
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr"><br>
        <div class=3D"gmail_extra"><br>
          <div class=3D"gmail_quote">On Wed, Aug 30, 2017 at 1:21 PM,
            Robert Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@=
nostrum.com" target=3D"_blank">rjsparks@nostrum.com</a>&gt;</span>
            wrote:<br>
            <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
              <br>
              Right now, you leave the DHCP server (when it&#39;s used)
              responsible for<br>
              clearing state in the MUD controller. Please discuss what
              happens when<br>
              those are distinct elements (as you have in the end of
              section 9.2) and<br>
              the DHCP server reboots. Perhaps it would make sense for
              the DHCP server<br>
              to hand the length of the lease it has granted to the MUD
              controller and<br>
              let the MUD controller clean up on its own?<br>
            </blockquote>
            <div><br>
            </div>
            <div>I would like to add a few words to the comprehensive
              review presented by Robert Sparks (I hope it is proper
              etiquette on this list to do so).<br>
              <br>
            </div>
            <div>With respect to the observation above:<br>
            </div>
            <div><br>
              There is also a cache timeout in the MUD profile. Does it
              make sense=C2=A0 that the MUD controller should take the
              minimum of the DHCP lease time and the cache timeout and
              use that to time out the installed ACLs (?) The DHCP
              server should also=C2=A0 pass to the MUD controller, some way
              of identifying the device to which the lease has been
              granted (for example the MAC address of the device). <br>
              <br>
            </div>
            <div>The draft also not specify how the DHCP server will
              communicate with the MUD controller (presumably via a
              simple REST interface but what is the URL to be used and
              how are the parameters passed?). I think this should be
              specified for interoperability between DHCP clients and
              MUD servers. Maybe words describing this interaction can
              be added here.<br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br></span>
    That&#39;s right.=C2=A0 At the moment, this is an &quot;internalized&qu=
ot; function.=C2=A0
    That is to say that the DHCP server is said to be tightly coupled to
    the MUD controller without standardized interfaces.=C2=A0 In my first
    implementation, I literally just tailed dhcpd syslog entries and
    triggered MUD based on DHCPREQUEST messages.=C2=A0 Clean-up state had t=
o
    do with RELEASE or periodic SNMP queries.=C2=A0 Our implementation at
    Cisco does something different.<br>
    <br>
    However... if the OPSAWG would like, and there is interest, we can
    formalize that interface.=C2=A0 I don&#39;t want to do it in THIS draft=
 (it&#39;s
    already fairly involved), but there&#39;s nothing to say we couldn&#39;=
t do
    some follow-on work.<br>
    <br>
    Fair enough?<span class=3D"gmail-HOEnZb"><font color=3D"#888888"><br>
    <br>
    Eliot<br>
  </font></span></div>

</blockquote></div><br>No problem with waiting to see if there&#39;s intere=
st from OPSAWG and others before considering this.<br><br></div><div class=
=3D"gmail_extra">By way of explanation on why I think this makes sense to s=
tandardize in MUD:<br><br>I had envisioned an architecture where the MUD co=
ntroller runs in the Service Provider cloud. The DHCP server would run in t=
he CPE router (e.g. as part of the firmware on a home router + NAT ).<br><b=
r></div><div class=3D"gmail_extra">If the statement above makes sense, sinc=
e the home router is typically not made by the same party as the service pr=
ovider software, I was thinking there should be a standardized interface be=
tween the DHCP server and MUD controller. <br><br></div><div class=3D"gmail=
_extra">Thanks.<br><br></div><div class=3D"gmail_extra">Ranga<br></div><div=
 class=3D"gmail_extra"><br><br></div><div class=3D"gmail_extra"><br clear=
=3D"all"><br>-- <br><div class=3D"gmail_signature">M. Ranganathan<br></div>
</div></div></div></div></div>

--001a1148e96e36c57605580d9b61--


From nobody Thu Aug 31 12:07:55 2017
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80AF0132936; Thu, 31 Aug 2017 12:07:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level: 
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SB4i4_LT2gXn; Thu, 31 Aug 2017 12:07:42 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74EFB132386; Thu, 31 Aug 2017 12:07:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=37009; q=dns/txt; s=iport; t=1504206461; x=1505416061; h=from:subject:to:cc:references:message-id:date: mime-version:in-reply-to; bh=dckF/tUr53UtqJvW5oOQIQauZWBi26SiZayCVsExxAw=; b=Pk+SfmZBL4p5k6c2XGBtJVZjJMwsDu61nJ35eVcCbUTfUXveMZZoVbSv fysf6UREoRwXTnAINNbpTN+0Fd4pgeLi9y+xfXieMMGrPNTSBX9KR4vmQ OV9vPjFMvM7v0QN5Mp75BG2bbUohsNXtsNKhxd62F+057u+cq6H+KsLeu c=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BuAQDUXahZ/xbLJq1UChkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYMtgRGQIJBwK5YnDoIEByWBYIM7AoRPFwECAQEBAQEBAWsohRg?= =?us-ascii?q?BAQEBAgEaCUgOBQsLDgQGIAoCAkkOBgEMCAEBF4oOCBCwD4InJ4s2AQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBDgoFgyYEhTMrgXCBDYMmgSQFDgKDKYJhBYoPhxaHDIg?= =?us-ascii?q?+hDmCIYEBjHaCE4Vng1mHG5ZFIAE2WzIyIQgcFUmFE4IKPohQgkABAQE?=
X-IronPort-AV: E=Sophos;i="5.41,454,1498521600";  d="asc'?scan'208,217";a="654314000"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Aug 2017 19:07:36 +0000
Received: from [10.61.64.148] (ams3-vpn-dhcp148.cisco.com [10.61.64.148]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v7VJ7ZvI004252; Thu, 31 Aug 2017 19:07:35 GMT
From: Eliot Lear <lear@cisco.com>
Subject: Re: Genart early review of draft-ietf-opsawg-mud-08
To: Robert Sparks <rjsparks@nostrum.com>, gen-art@ietf.org
Cc: draft-ietf-opsawg-mud.all@ietf.org, opsawg@ietf.org, ietf@ietf.org
References: <150411366399.21627.17047458871931107094@ietfa.amsl.com>
Message-ID: <0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com>
Date: Thu, 31 Aug 2017 21:07:40 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <150411366399.21627.17047458871931107094@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="pULS9gljHiv2ktcJk5STwulUp2eUHMRCK"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YyK92DFX3IOnjf4QcKnk35kSAos>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 31 Aug 2017 19:07:47 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--pULS9gljHiv2ktcJk5STwulUp2eUHMRCK
Content-Type: multipart/mixed; boundary="Ma5O97xAdO2Q4S738tCSCi7AXw1KMNJpE";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Robert Sparks <rjsparks@nostrum.com>, gen-art@ietf.org
Cc: draft-ietf-opsawg-mud.all@ietf.org, opsawg@ietf.org, ietf@ietf.org
Message-ID: <0a8c04d6-eb0f-09d0-eeed-da2dacf8260c@cisco.com>
Subject: Re: Genart early review of draft-ietf-opsawg-mud-08
References: <150411366399.21627.17047458871931107094@ietfa.amsl.com>
In-Reply-To: <150411366399.21627.17047458871931107094@ietfa.amsl.com>

--Ma5O97xAdO2Q4S738tCSCi7AXw1KMNJpE
Content-Type: multipart/alternative;
 boundary="------------644AF31A95E871F10DA4D106"
Content-Language: en-US

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

Robert,

As I wrote earlier, this was a great review.=C2=A0 Thanks for that.=C2=A0=
 Please
see below.


On 8/30/17 7:21 PM, Robert Sparks wrote:
> Reviewer: Robert Sparks
> Review result: Almost Ready
>
> This is an exciting concept, and the draft overall is approachable. I
> have identified a few areas I think need more detail, and have a=20
> longish list of nits (please don't take that to be negative).
>
> =3D=3DIssues=3D=3D
>
> I find the structure of the introduction unclear. Please consider
> reworking it.  I would suggest even more succinctly listing goals and
> constraints, and then intended applicability (these things are in the
> current text, but I think you can render them much more efficiently). I=
n
> particular, the argument that implementers of things are incented only =
to
> provide the minimal amount of behavior to get their thingyness could be=

> more strongly highlighted.

I've received conflicting reviews here.=C2=A0 Most like what's there and
while I'm open to specific textual changes, a full reorganization would
likely be destabilizing.

> The document proposes "reputation services". It needs more words about
> whether those exist, and what scopes the architecture imagines (an
> enterprise might have a different idea of a reputation service than a
> residence). There is a notion of "decent web reputations" in the securi=
ty
> considerations section. Who determines that? The security consideration=
s
> section should talk about attacks against the reputation services.

This is discussed in security considerations:
> It may also be useful
> to limit retrieval of MUD URLs to only those sites that are known to
> have decent web reputations.
What I am specifically talking about are web or domain reputation
services.=C2=A0 These are pretty commonplace today.=C2=A0 Your browser us=
es one,
and numerous companies offer them, including our own.=C2=A0 But to be
clearer, I propose to use the term "web or domain reputation services",
so that people know what I'm talking about.




> In the first paragraph of Section 2, it's not clear if you are trying
> to restrict the models to only those in the two documents in the list
> following the paragraph.=20

Right.=C2=A0 This was caught earlier, and I'll correct.

> I am not a YANG doctor, so this may be in the weeds, but it feels like
> there's a discrepancy between the diagram at the end of section 2 and t=
he
> element definitions in section 3. In particular 3.7 doesn't seem to ali=
gn
> with what the diagram or the example in Appendix B uses. Should you be =

> defining "from-device-policy" and "to-device-policy" instead of
> "packet-direction"? (I'm wondering if 3.7 reflects an older design?)

Yupper.=C2=A0 Fixed (I think).
> At section 3.13, the description of my-controller is not quite right.
> This bit signals to the mud controller to use a mapping that it knows
> about or creates. Something else established that class (and maybe gave=

> it a name). I talked about this with Eliot and he has a better=20
> description to use.

Proposed text:

> This null-valued node signals to the MUD controller to use whatever
> mapping it has for this URL to a controller class".=C2=A0 This may requ=
ire
> prompting the administrator for class members.=C2=A0 Future work should=

> seek to automate membership management.

> It's not clear to me that this is a good use of .well-known. I suggest
> getting an expert review on the proposed usage. (I had a quick=20
> conversation with Mark Nottingham and got some initial feedback that=20
> I'm passing along here. I'm sure there's more that an in-depth review
> would identify.) Why wouldn't a URI template (RFC6570) do the job?=20
> Rather than use RFC3986's query, consider pointing to HTML5 (which
> would bring the more familiar key=3Dvalue format).=20

The key issue is that we want to externalize versioning AND hardcode it
in the URL so that it's independent of transport.=C2=A0 Remember, there i=
s
very little information exchange between the Thing and the network, and
I will claim that's a good thing.

> The document needs to say more about how HTTP is used. I assume you onl=
y
> intend to use GET, and that you expect redirects to be followed, and th=
at
> nothing special needs to be considered with caching? The document needs=

> to be explicit about it. Take a look at=20
> <https://mnot.github.io/I-D/bcp56bis/>. (There's been some conversation=

> about it on the art list, so Eliot, at least, is already aware of it - =

> see <https://mailarchive.ietf.org/arch/search/?q=3Dbcp56bis>)

What we say today is the following;
> Processing of this
> URL occurs as specified in {{RFC2818}} and {{RFC3986}}.
There is one aspect of caching semantics we should probably capture,
which is that the cache-validity period should exceed the HTTP cache or
expiry period as specified by max-age or Expires.=C2=A0 Does that sound a=
bout
right to you?

> I think there needs to be more discussion of the PKI used for signing M=
UD
> files.

We do have some discussion in Section 12.2.=C2=A0 I'm happy to add an
additional sentence or two, but would seek guidance on where you think
we're missing.

> Consider discussing whether the stacks used by typical things will let
> them add DHCP options (or include bits in the other protocols being=20
> enabled). If it's well known (I can't say) that these stacks typically
> _won't_ provide that functionality, then you should punch up the
> discussion of the controllers mapping other identifiers to MUD URLs on
> behalf of the thing.

I agree.=C2=A0 We allude to this in the draft.=C2=A0 We say, for instance=
:
> It is possible that there may be other means for a MUD URL to be
> learned by a network.=C2=A0 For instance, if a device has a serial numb=
er,
> it may be possible for the MUD controller to perform a lookup of the
> device, if it has some knowledge as to who the device manufacturer
> is, and what its MUD file server is.=C2=A0 Such mechanisms are not
> described in this memo, but are possible.

The case we have in mind is LoRaWAN.=C2=A0 Should we go further?


> You suggest the DHCP Client (which is a thing) SHOULD log or report=20
> improper acknowledgments from servers. That's asking a bit much from
> a thing. I suspect the requirement is unrealistic and should be removed=

> or rewritten to acknowledge that things typically won't do that.
I think there's a philosophical thing hiding here, though: what
expectations should we have of device.=C2=A0 As a SHOULD we're saying, if=
 you
have good cause not to, ok.=C2=A0 But otherwise, for the sake of the sani=
ty
of the customer, please log.

> The security and deployment considerations sections talk about what the=

> need for coordination if control over the domain name used in the URL
> changes. It should talk more about what happens if the new administrati=
on
> of the domain is not interested in facilitating a transition (consider
> the case of a young company with a few thousand start-up-ish things out=

> there that loses a suit over its name). Please discuss whether or not
> suddenly losing the MUD assisted network configuration is expected to
> leave the devices effectively cut-off.=20

It should not, and here's why:

  * Assuming the device has already been used, there is no reason to
    simply delete the MUD file from one's cache.=C2=A0 The cache-validity=

    value is meant as a timer to keep implementations for harassing the
    MUD file server, but there's the information is still useful, even
    if it may not have been freshened.
  * In the case where the MUD file service is unavailable when the
    device is first turned up, it's as if it had not included a MUD-URL
    in the first place.=C2=A0 While this may be a downgrade attack, there=
 is,
    as I understand it, really no way to get around it, other than for
    the MUD controller to log a problem.

> Right now, you leave the DHCP server (when it's used) responsible for
> clearing state in the MUD controller. Please discuss what happens when
> those are distinct elements (as you have in the end of section 9.2) and=

> the DHCP server reboots. Perhaps it would make sense for the DHCP serve=
r
> to hand the length of the lease it has granted to the MUD controller an=
d
> let the MUD controller clean up on its own?

See other response.

> The document currently suggests that a piece of software inspect the
> WHOIS database to see if registration ownership of a domain has changed=
=2E
> Do you really mean software, or should this be advice to the
> administrator of the controller instead?=20

The controller.=C2=A0 The idea is to catch bad behavior and anomalies.=C2=
=A0 And
the bigger idea is to reduce the number of decisions that the
administrator must make, while providing relevant information with which
to make the decisions.

> =3D=3DNits=3D=3D
>
> I recommend an editorial pass focusing on simplifying sentences. Look
> particularly where the word "therefore" is used and consider
> restructuring the surrounds. (It is used non-sequitur in a couple of
> places). Be careful to call out actors explicitly (I note the places=20
> that particularly caught my eye below).

ok.
> Some specific nits:
>
> The abstract speaks only about properties of MUD but does not describe
> what MUD _is_, or is good for. A few more words here would help.
Right.=C2=A0 See response to Henk.
> Next to last paragraph of section 1 (before 1.1): A means for _who_ to
> retrieve the description? (Consider rendering the three list elements o=
n
> their own lines.)
Right.=C2=A0 Fixed.
> The last sentence of section 1 treats "enterprise networks" more
> specially than it intends, I think. Why couldn't _any_ network do this?=

> Could the sentence be reworded to make it clear that enterprise network=
s
> are an example?

s/enterprise networks/local deployments/

?

> First sentence of 1.1: Perhaps you mean "general purpose computing
> devices" instead of "general computing"? "their" has an unclear
> antecedent.

Indeed.=C2=A0 fixed.

> Last paragraph of 1.3: It's unclear what "such an approach" is intended=

> to point to. Would "a general solution that required capabilities their=

> particular device would not use" make more sense?

Reworded.

> First paragraph of 1.5: "might to allow" is probably meant to be "might=

> be to allow". What does it mean for a controller to "need to speak COAP=
".
> Do you mean "controllers capable of speaking COAP"?
Fixed.
> Fourth paragraph of 1.5 at the discussion of time and effort: Consider
> rephrasing this to focus on the result of the time and effort (high
> quality) rather than the time and effort itself.

Existence is good enough in this case ;-)

> In the list of abstractions at the end of 1.5, you have three things yo=
u
> describe as devices and one thing you describe as a class. You later ta=
lk
> about the abstractions you've described as devices as classes. At this
> point in the document what you mean by "class" has not been made as
> explicit as it could be.
I've tried to review all instances of class to be clear that it is used
consistently.=C2=A0 This is somewhat difficult given natural language, bu=
t I
hope I've gotten it right.

>
> Section 1.8, item 3: the MUD file doesn't have hosts in it (it has
> identifiers of some kind). Consider being more explicit about what
> you mean by testing that against a reputation service.

Actually, it can have hosts in it, but see above.

> Section 3.1: You say "Which turn was taken". I think you meant
> "Which, in turn, was taken". Consider deleting "for those keeping score=
".

Awwww.=C2=A0 Just a bit of humor? ;-)

>
> Section 3.3 is missing a word at "the location any MASA service"?

Ok it's cleaned up.

>
> I found the prose in the descriptions of the "manufacturer" and
> "same-manufacturer" elements (3.8 and 3.9) very confusing. I think
> additional prose introducing the concepts and maybe some examples would=

> be very useful.

Added examples per your suggestion.

>
> What do you mean by "matches" at 3.10. Do you mean "is"?

All of this is applicable in the context of the matches statement in the
ACL model.=C2=A0 I've added some explanatory text at the beginning of the=

chapeau.
>
> The caution in the 2nd paragraph of 3.12 is not clear.

Ok, I've cleaned that up and added an example.

>
> At section 4, consider pointing out that you are not allowing=20
> DHCP by default, and that devices that are expected to use DHCP
> need to have an explicit allow in their MUD file.=20

Hmm.=C2=A0 The issue here is that DHCP is an L2 protocol that isn't
forwarded.=C2=A0 Do you think it needs to be listed anyway?

>
> The description of the manufacturer leaf in the MUD YANG model
> could be made more useful.

ALL the descriptions have been improved.
>
> Provide a reference for "giaddr" when you use it in section 9.2.

Cleaned up (that's defined in RFC 2131, already normatively referenced,
but I expanded).
>
> Section 14, 2nd paragraph: additional segmentation of what?

Make that "network segmentation".
>
> Second paragraph of Section 15 - it would help to be more precise
> with agency. _Who_ should review the class?

Fixed.

>
> In the security considerations section, when you get to the "if for som=
e
> reason it is not possible to determine whether ownership has changed",
> _who_ are you suggesting conduct further review?

It's always the network administrator.
>
> =3D=3DMicro-nits=3D=3D
>
> 1,$s/enorcement/enforcement/g

Doh!

>
> s/autjors/authors/
>

Fixed.

Thanks again,

Eliot


--------------644AF31A95E871F10DA4D106
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=3Dutf=
-8">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p>Robert,</p>
    <p>As I wrote earlier, this was a great review.=C2=A0 Thanks for that=
=2E=C2=A0
      Please see below.</p>
    <br>
    <div class=3D"moz-cite-prefix">On 8/30/17 7:21 PM, Robert Sparks
      wrote:<br>
    </div>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">Reviewer: Robert Sparks
Review result: Almost Ready

This is an exciting concept, and the draft overall is approachable. I
have identified a few areas I think need more detail, and have a=20
longish list of nits (please don't take that to be negative).

=3D=3DIssues=3D=3D

I find the structure of the introduction unclear. Please consider
reworking it.  I would suggest even more succinctly listing goals and
constraints, and then intended applicability (these things are in the
current text, but I think you can render them much more efficiently). In
particular, the argument that implementers of things are incented only to=

provide the minimal amount of behavior to get their thingyness could be
more strongly highlighted.</pre>
    </blockquote>
    <br>
    I've received conflicting reviews here.=C2=A0 Most like what's there =
and
    while I'm open to specific textual changes, a full reorganization
    would likely be destabilizing.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">The document proposes "reputation services". It need=
s more words about
whether those exist, and what scopes the architecture imagines (an
enterprise might have a different idea of a reputation service than a
residence). There is a notion of "decent web reputations" in the security=

considerations section. Who determines that? The security considerations
section should talk about attacks against the reputation services.</pre>
    </blockquote>
    <br>
    This is discussed in security considerations:<br>
    <blockquote type=3D"cite">It may also be useful<br>
      to limit retrieval of MUD URLs to only those sites that are known
      to<br>
      have decent web reputations.<br>
    </blockquote>
    What I am specifically talking about are web or domain reputation
    services.=C2=A0 These are pretty commonplace today.=C2=A0 Your browse=
r uses
    one, and numerous companies offer them, including our own.=C2=A0 But =
to
    be clearer, I propose to use the term "web or domain reputation
    services", so that people know what I'm talking about.<br>
    <br>
    <br>
    <br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
In the first paragraph of Section 2, it's not clear if you are trying
to restrict the models to only those in the two documents in the list
following the paragraph. </pre>
    </blockquote>
    <br>
    Right.=C2=A0 This was caught earlier, and I'll correct.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
I am not a YANG doctor, so this may be in the weeds, but it feels like
there's a discrepancy between the diagram at the end of section 2 and the=

element definitions in section 3. In particular 3.7 doesn't seem to align=

with what the diagram or the example in Appendix B uses. Should you be=20
defining "from-device-policy" and "to-device-policy" instead of
"packet-direction"? (I'm wondering if 3.7 reflects an older design?)</pre=
>
    </blockquote>
    <br>
    Yupper.=C2=A0 Fixed (I think).<br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
At section 3.13, the description of my-controller is not quite right.
This bit signals to the mud controller to use a mapping that it knows
about or creates. Something else established that class (and maybe gave
it a name). I talked about this with Eliot and he has a better=20
description to use.</pre>
    </blockquote>
    <br>
    Proposed text:<br>
    <br>
    <blockquote type=3D"cite">This null-valued node signals to the MUD
      controller to use whatever<br>
      mapping it has for this URL to a controller class".=C2=A0 This may
      require<br>
      prompting the administrator for class members.=C2=A0 Future work sh=
ould<br>
      seek to automate membership management.</blockquote>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
It's not clear to me that this is a good use of .well-known. I suggest
getting an expert review on the proposed usage. (I had a quick=20
conversation with Mark Nottingham and got some initial feedback that=20
I'm passing along here. I'm sure there's more that an in-depth review
would identify.) Why wouldn't a URI template (RFC6570) do the job?=20
Rather than use RFC3986's query, consider pointing to HTML5 (which
would bring the more familiar key=3Dvalue format). </pre>
    </blockquote>
    <br>
    The key issue is that we want to externalize versioning AND hardcode
    it in the URL so that it's independent of transport.=C2=A0 Remember,
    there is very little information exchange between the Thing and the
    network, and I will claim that's a good thing.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
The document needs to say more about how HTTP is used. I assume you only
intend to use GET, and that you expect redirects to be followed, and that=

nothing special needs to be considered with caching? The document needs
to be explicit about it. Take a look at=20
<a class=3D"moz-txt-link-rfc2396E" href=3D"https://mnot.github.io/I-D/bcp=
56bis/">&lt;https://mnot.github.io/I-D/bcp56bis/&gt;</a>. (There's been s=
ome conversation
about it on the art list, so Eliot, at least, is already aware of it -=20
see <a class=3D"moz-txt-link-rfc2396E" href=3D"https://mailarchive.ietf.o=
rg/arch/search/?q=3Dbcp56bis">&lt;https://mailarchive.ietf.org/arch/searc=
h/?q=3Dbcp56bis&gt;</a>)</pre>
    </blockquote>
    <br>
    What we say today is the following;<br>
    <blockquote type=3D"cite">Processing of this<br>
      URL occurs as specified in {{RFC2818}} and {{RFC3986}}.</blockquote=
>
    There is one aspect of caching semantics we should probably capture,
    which is that the cache-validity period should exceed the HTTP cache
    or expiry period as specified by max-age or Expires.=C2=A0 Does that
    sound about right to you?<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
I think there needs to be more discussion of the PKI used for signing MUD=

files.</pre>
    </blockquote>
    <br>
    We do have some discussion in Section 12.2.=C2=A0 I'm happy to add an=

    additional sentence or two, but would seek guidance on where you
    think we're missing.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
Consider discussing whether the stacks used by typical things will let
them add DHCP options (or include bits in the other protocols being=20
enabled). If it's well known (I can't say) that these stacks typically
_won't_ provide that functionality, then you should punch up the
discussion of the controllers mapping other identifiers to MUD URLs on
behalf of the thing.</pre>
    </blockquote>
    <br>
    I agree.=C2=A0 We allude to this in the draft.=C2=A0 We say, for inst=
ance:<br>
    <blockquote type=3D"cite">It is possible that there may be other mean=
s
      for a MUD URL to be<br>
      learned by a network.=C2=A0 For instance, if a device has a serial
      number,<br>
      it may be possible for the MUD controller to perform a lookup of
      the<br>
      device, if it has some knowledge as to who the device manufacturer<=
br>
      is, and what its MUD file server is.=C2=A0 Such mechanisms are not<=
br>
      described in this memo, but are possible.<br>
    </blockquote>
    <br>
    The case we have in mind is LoRaWAN.=C2=A0 Should we go further?<br>
    <br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
You suggest the DHCP Client (which is a thing) SHOULD log or report=20
improper acknowledgments from servers. That's asking a bit much from
a thing. I suspect the requirement is unrealistic and should be removed
or rewritten to acknowledge that things typically won't do that.</pre>
    </blockquote>
    I think there's a philosophical thing hiding here, though: what
    expectations should we have of device.=C2=A0 As a SHOULD we're saying=
, if
    you have good cause not to, ok.=C2=A0 But otherwise, for the sake of =
the
    sanity of the customer, please log.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
The security and deployment considerations sections talk about what the
need for coordination if control over the domain name used in the URL
changes. It should talk more about what happens if the new administration=

of the domain is not interested in facilitating a transition (consider
the case of a young company with a few thousand start-up-ish things out
there that loses a suit over its name). Please discuss whether or not
suddenly losing the MUD assisted network configuration is expected to
leave the devices effectively cut-off. </pre>
    </blockquote>
    <br>
    It should not, and here's why:<br>
    <br>
    <ul>
      <li>Assuming the device has already been used, there is no reason
        to simply delete the MUD file from one's cache.=C2=A0 The
        cache-validity value is meant as a timer to keep implementations
        for harassing the MUD file server, but there's the information
        is still useful, even if it may not have been freshened.</li>
      <li>In the case where the MUD file service is unavailable when the
        device is first turned up, it's as if it had not included a
        MUD-URL in the first place.=C2=A0 While this may be a downgrade
        attack, there is, as I understand it, really no way to get
        around it, other than for the MUD controller to log a problem.<br=
>
      </li>
    </ul>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
Right now, you leave the DHCP server (when it's used) responsible for
clearing state in the MUD controller. Please discuss what happens when
those are distinct elements (as you have in the end of section 9.2) and
the DHCP server reboots. Perhaps it would make sense for the DHCP server
to hand the length of the lease it has granted to the MUD controller and
let the MUD controller clean up on its own?</pre>
    </blockquote>
    <br>
    See other response.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
The document currently suggests that a piece of software inspect the
WHOIS database to see if registration ownership of a domain has changed.
Do you really mean software, or should this be advice to the
administrator of the controller instead? </pre>
    </blockquote>
    <br>
    The controller.=C2=A0 The idea is to catch bad behavior and anomalies=
=2E=C2=A0
    And the bigger idea is to reduce the number of decisions that the
    administrator must make, while providing relevant information with
    which to make the decisions.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
=3D=3DNits=3D=3D

I recommend an editorial pass focusing on simplifying sentences. Look
particularly where the word "therefore" is used and consider
restructuring the surrounds. (It is used non-sequitur in a couple of
places). Be careful to call out actors explicitly (I note the places=20
that particularly caught my eye below).</pre>
    </blockquote>
    <br>
    ok.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
Some specific nits:

The abstract speaks only about properties of MUD but does not describe
what MUD _is_, or is good for. A few more words here would help.</pre>
    </blockquote>
    Right.=C2=A0 See response to Henk.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
Next to last paragraph of section 1 (before 1.1): A means for _who_ to
retrieve the description? (Consider rendering the three list elements on
their own lines.)</pre>
    </blockquote>
    Right.=C2=A0 Fixed.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
The last sentence of section 1 treats "enterprise networks" more
specially than it intends, I think. Why couldn't _any_ network do this?
Could the sentence be reworded to make it clear that enterprise networks
are an example?</pre>
    </blockquote>
    <br>
    s/enterprise networks/local deployments/<br>
    <br>
    ?<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
First sentence of 1.1: Perhaps you mean "general purpose computing
devices" instead of "general computing"? "their" has an unclear
antecedent.</pre>
    </blockquote>
    <br>
    Indeed.=C2=A0 fixed.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
Last paragraph of 1.3: It's unclear what "such an approach" is intended
to point to. Would "a general solution that required capabilities their
particular device would not use" make more sense?</pre>
    </blockquote>
    <br>
    Reworded.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
First paragraph of 1.5: "might to allow" is probably meant to be "might
be to allow". What does it mean for a controller to "need to speak COAP".=

Do you mean "controllers capable of speaking COAP"?
</pre>
    </blockquote>
    Fixed.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">Fourth paragraph of 1.5 at the discussion of time an=
d effort: Consider
rephrasing this to focus on the result of the time and effort (high
quality) rather than the time and effort itself.</pre>
    </blockquote>
    <br>
    Existence is good enough in this case ;-)<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
In the list of abstractions at the end of 1.5, you have three things you
describe as devices and one thing you describe as a class. You later talk=

about the abstractions you've described as devices as classes. At this
point in the document what you mean by "class" has not been made as
explicit as it could be.</pre>
    </blockquote>
    I've tried to review all instances of class to be clear that it is
    used consistently.=C2=A0 This is somewhat difficult given natural
    language, but I hope I've gotten it right.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">

Section 1.8, item 3: the MUD file doesn't have hosts in it (it has
identifiers of some kind). Consider being more explicit about what
you mean by testing that against a reputation service.</pre>
    </blockquote>
    <br>
    Actually, it can have hosts in it, but see above.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">
Section 3.1: You say "Which turn was taken". I think you meant
"Which, in turn, was taken". Consider deleting "for those keeping score".=
</pre>
    </blockquote>
    <br>
    Awwww.=C2=A0 Just a bit of humor? ;-)<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">

Section 3.3 is missing a word at "the location any MASA service"?</pre>
    </blockquote>
    <br>
    Ok it's cleaned up.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">

I found the prose in the descriptions of the "manufacturer" and
"same-manufacturer" elements (3.8 and 3.9) very confusing. I think
additional prose introducing the concepts and maybe some examples would
be very useful.</pre>
    </blockquote>
    <br>
    Added examples per your suggestion.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">

What do you mean by "matches" at 3.10. Do you mean "is"?</pre>
    </blockquote>
    <br>
    All of this is applicable in the context of the matches statement in
    the ACL model.=C2=A0 I've added some explanatory text at the beginnin=
g of
    the chapeau.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">

The caution in the 2nd paragraph of 3.12 is not clear.</pre>
    </blockquote>
    <br>
    Ok, I've cleaned that up and added an example.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">

At section 4, consider pointing out that you are not allowing=20
DHCP by default, and that devices that are expected to use DHCP
need to have an explicit allow in their MUD file. </pre>
    </blockquote>
    <br>
    Hmm.=C2=A0 The issue here is that DHCP is an L2 protocol that isn't
    forwarded.=C2=A0 Do you think it needs to be listed anyway?<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">

The description of the manufacturer leaf in the MUD YANG model
could be made more useful.</pre>
    </blockquote>
    <br>
    ALL the descriptions have been improved.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">

Provide a reference for "giaddr" when you use it in section 9.2.</pre>
    </blockquote>
    <br>
    Cleaned up (that's defined in RFC 2131, already normatively
    referenced, but I expanded).<br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">

Section 14, 2nd paragraph: additional segmentation of what?</pre>
    </blockquote>
    <br>
    Make that "network segmentation".<br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">

Second paragraph of Section 15 - it would help to be more precise
with agency. _Who_ should review the class?</pre>
    </blockquote>
    <br>
    Fixed.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">

In the security considerations section, when you get to the "if for some
reason it is not possible to determine whether ownership has changed",
_who_ are you suggesting conduct further review?</pre>
    </blockquote>
    <br>
    It's always the network administrator.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">

=3D=3DMicro-nits=3D=3D

1,$s/enorcement/enforcement/g</pre>
    </blockquote>
    <br>
    Doh!<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
      <pre wrap=3D"">

s/autjors/authors/

</pre>
    </blockquote>
    <br>
    Fixed.<br>
    <br>
    Thanks again,<br>
    <br>
    Eliot<br>
    <blockquote type=3D"cite"
      cite=3D"mid:150411366399.21627.17047458871931107094@ietfa.amsl.com"=
>
    </blockquote>
    <br>
  </body>
</html>

--------------644AF31A95E871F10DA4D106--

--Ma5O97xAdO2Q4S738tCSCi7AXw1KMNJpE--

--pULS9gljHiv2ktcJk5STwulUp2eUHMRCK
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

iQEcBAEBCAAGBQJZqF58AAoJEIe2a0bZ0nozZJQH/RmARIDac/p6xTK/ga5t/1b/
p86ZgXtuE6Ww5KJkY9J/IANO68HkBWHyNpnF3VDHOrEvXv4jfjcYu6lCdZwD9Fy8
aeRJh2fso+6d+AuEddrBMCtMKsTVBqX5bdNH9NXlavPl09qXOsCI/VGW50nbxF/z
luESyMSY1+JkJxxFE78A0+rx2Kesmvg+5WNvl/S5TJ+v251G66skH8c/0bo3q2GK
h0sugbOpEIF4q8xjX3ZikQpe/jT+Ror6RoG0bX6qgTkSQIn/zk45AI+XWLly9NLp
Oh/EzY6y3BKR6u4X18b6TvF+DEUnVZdTGZ5L+hD6u5I7LAwvPmCAD5MV7c9jnz0=
=ykaw
-----END PGP SIGNATURE-----

--pULS9gljHiv2ktcJk5STwulUp2eUHMRCK--


From nobody Thu Aug 31 12:56:20 2017
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77D841326FE; Thu, 31 Aug 2017 12:56:12 -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, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fIM2XkLmq_q5; Thu, 31 Aug 2017 12:56:09 -0700 (PDT)
Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E7B11326ED; Thu, 31 Aug 2017 12:56:08 -0700 (PDT)
Received: from [IPv6:2003:cd:6bcc:5600:fc8d:74e5:a8fb:f5f9] (p200300CD6BCC5600FC8D74E5A8FBF5F9.dip0.t-ipconnect.de [IPv6:2003:cd:6bcc:5600:fc8d:74e5:a8fb:f5f9]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 813FE71E3F8DF; Thu, 31 Aug 2017 21:56:05 +0200 (CEST)
From: Michael Tuexen <tuexen@fh-muenster.de>
Message-Id: <0E628ABF-6E0E-40A6-87EE-CA94A93FE0A5@fh-muenster.de>
Content-Type: multipart/signed; boundary="Apple-Mail=_28642E5D-A8DE-4456-8499-F55BF38F7C89"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [OPS-DIR] Opsdir last call review of draft-ietf-tsvwg-sctp-ndata-12
Date: Thu, 31 Aug 2017 21:56:04 +0200
In-Reply-To: <CAKKJt-fuJWEMd79Z2zRmg4GU8hpVcqSfN+Y6xLioMUmwu8d6fw@mail.gmail.com>
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Stefan Winter <stefan.winter@restena.lu>, "ops-dir@ietf.org" <ops-dir@ietf.org>, draft-ietf-tsvwg-sctp-ndata.all@ietf.org, "tsvwg@ietf.org" <tsvwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IESG IESG <iesg@ietf.org>
To: Benoit Claise <bclaise@cisco.com>
References: <150287547583.12471.9085655210334710687@ietfa.amsl.com> <FDCFFA8C-8828-4578-A66E-A1AD7FF9BDC9@fh-muenster.de> <1a39dff3-55a9-fe1d-7e19-a0fbd0b2751b@restena.lu> <F05D0F1F-47E2-4477-BFD9-F0119A4609FC@fh-muenster.de> <f4d121e4-44f5-e85d-98b1-bbea317a7539@cisco.com> <5CEB294C-AAC8-4F03-901D-487CD62BB491@fh-muenster.de> <41a1e8f1-2398-4d94-7021-638acdd58eb7@cisco.com> <1FFDADBA-4132-4D3B-B68C-A89A50AF1E24@fh-muenster.de> <CAKKJt-dM1q9NDe8r=q-aqdWW0i3i8mSYLCNssU4cvjo22GRRyw@mail.gmail.com> <BD327429-5C8F-4034-A9E7-834FDB1E7FB6@fh-muenster.de> <CAKKJt-fuJWEMd79Z2zRmg4GU8hpVcqSfN+Y6xLioMUmwu8d6fw@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Sx6nt8b7VOTesunp0fzxNmuB5n8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 31 Aug 2017 19:56:12 -0000

--Apple-Mail=_28642E5D-A8DE-4456-8499-F55BF38F7C89
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On 31. Aug 2017, at 15:46, Spencer Dawkins at IETF =
<spencerdawkins.ietf@gmail.com> wrote:
>=20
> Hi, Michael,
>=20
> On Thu, Aug 31, 2017 at 8:25 AM, Michael Tuexen =
<tuexen@fh-muenster.de> wrote:
> > On 31. Aug 2017, at 14:50, Spencer Dawkins at IETF =
<spencerdawkins.ietf@gmail.com> wrote:
> >
> > Just interjecting ...
> >
> > On Thu, Aug 31, 2017 at 7:25 AM, Michael Tuexen =
<tuexen@fh-muenster.de> wrote:
> >
> > > On 31. Aug 2017, at 14:14, Benoit Claise <bclaise@cisco.com> =
wrote:
> > >
> > > Hi Michael,
> > >>> On 30. Aug 2017, at 18:51, Benoit Claise <bclaise@cisco.com> =
wrote:
> > >>>
> > >>> Michael,
> > >>>
> > >>> I stumbled on the same point as Stefan.
> > >> Hi Benoit,
> > >>
> > >> thanks for reviewing the document. See my comments in-line.
> > >>
> > >> Best regards
> > >> Michael
> > >>> First of, I had to review RFC4960 for TSN/SSN. I was not sure =
whether TSN was per stream or not
> > >>> It would have helped me to repeat this information in the intro.
> > >>> Ok, to be candid, I deduced this information from figure 1 and =
2.
> > >>>>>>> And the rest are only musings not needing any action if the =
authors don't want
> > >>>>>>> to action on them:
> > >>>>>>>
> > >>>>>>> The introduction presents a good use case, quoting: "e.g., =
when the
> > >>>>>>> transmission of an urgent
> > >>>>>>>  message is blocked from transmission because the sender has =
started
> > >>>>>>>  the transmission of another, possibly large, message".
> > >>>>>>>
> > >>>>>>> The later queueing example in figure 1 has three SIDs being =
queued
> > >>>>>>> simultanseously. It is not clear which of those "has already =
started" and which
> > >>>>>> There is actually one message queued for stream 0, three =
messages for stream 1,
> > >>>>>> and one message for stream 2.
> > >>>>>>> are the important ones being delayed. For a better =
understanding of the reader,
> > >>>>>> The figure is about in which sequence they are put on the =
wire. So no
> > >>>>>> transmission has startet. This examples also does not deal =
with the case
> > >>>>>> of one stream having a higher priority than another. That =
would be an
> > >>>>>> example using a priority scheduler. This examples illustrates =
the round
> > >>>>>> robin scheduler.
> > >>>>>> The point here is that a single scheduler (the round robin =
scheduler, for
> > >>>>>> example) behaves differently when user message interleaving =
is used or not.
> > >>>>>> That is an important point: You can even use the schedulers =
with regular
> > >>>>>> DATA chunk, i.e. with user message interleaving being =
negotiated.
> > >>> This was my source of confusion.
> > >>> With figure 1 and figure 2, you want to show the effect of Round =
Robin Scheduler with and without User Message Interleaving, while we =
were expecting the figure 2 to be the solution from this spec. Hence =
Stefan and I were looking for this "urgent message" in figure 2.
> > >> I don't know what you mean with "solution from this spec" means. =
This spec introduces
> > >> stream schedulers and a protocol extension to allow interleaving =
of user messages.
> > >> Using this to implement an "urgent" concept is only one =
possibility: usage of a
> > >> strict priority scheduler (SCTP_SS_PRIO). So this "urgent" is =
misleading. It seems
> > >> to ring the wrong bells. That is why I suggested to remove it...
> > >>>>>>> it might be useful to revise the figure so that the =
head-of-line blocking
> > >>>>>>> happens for SID 1 because transmission of  0 and 2 has =
already started (and
> > >>>>>>> declare SID 1 to be the "important" message). The ASCII art =
would just have to
> > >>>>>>> indent SID 1 content a bit (placing 0 and 2 earlier in =
time), and the resulting
> > >>>>>>> serialisation would then put all the SID 1 messages at the =
very end, when 0 and
> > >>>>>>> 2 have been completely submitted (right?).
> > >>>>>> One could think about adding another example based on the =
priority scheduler
> > >>>>>> and giving stream 1 a higher priority. But for illustrating =
the point of
> > >>>>>> schedulers behaving differently depending on the negotiation =
of user message
> > >>>>>> interleaving this seems not necessary.
> > >>>>> That second example might indeed be useful.
> > >>>>>
> > >>>>> It's simply a bit strange that in the introduction you speak =
about an
> > >>>>> "urgent" message (something deserving a higher-priority =
sending) and
> > >>>>> that another transmission has already started - but then the =
example has
> > >>>>> none of those two.
> > >>> Exactly.
> > >>> Please add this extra example.
> > >>> This would also clarify from the introduction that when you =
write ...
> > >>>
> > >>>   The sending of such large messages over
> > >>>   SCTP as specified in [RFC4960] can result in a form of sender =
side
> > >>>   head of line blocking (e.g., when the transmission of an =
urgent
> > >>>   message is blocked from transmission because the sender has =
started
> > >>>   the transmission of another, possibly large, message).
> > >>>
> > >>> .. the notion of transmission urgency is not within a stream but =
across streams, and that can be achieved with a priority scheduler.
> > >> I would actually prefer to remove the word "urgent" from that =
sentence. This just rings the wrong bells.
> > > That's a missed opportunity in mind, but your call.
> > Hmm. Let me remove the word "urgent"...
> >
> > Yes, please! I wasn't wild about it, either.
> It's done:
> =
https://github.com/sctplab/sctp-idata/commit/cf7b331512cd85d6195eb88fa9636=
0673293323f
> >
> > >>> The text might have to be rephrased to explain that this spec =
provides the ability to create stream scheduler with different relative =
stream treatments.
> > >> What about:
> > >>
> > >> OLD TEXT
> > >>    This document also defines several stream schedulers for =
general SCTP
> > >>    associations.  The stream schedulers may behave differently =
depending
> > >>    on whether user message interleaving has been negotiated for =
the
> > >>    association or not.
> > >>
> > >> NEW TEXT
> > >>    This document also defines several stream schedulers for =
general SCTP
> > >>    associations allowing different relative stream treatments.
> > >>    The stream schedulers may behave differently depending
> > >>    on whether user message interleaving has been negotiated for =
the
> > >>    association or not.
> > >>
> > >> Would that address this issue?
> > > ok.
> > Fixed.
> > >>
> > >>> And also that urgent message would be placed in this high =
priority stream scheduler (reliable, I guess, but that's orthogonal) =
stream.
> > >> I really would like to get rid of this. I don't think giving the =
strict
> > >> priority scheduler as specific role here is a good idea.
> > >>
> > >> The RR scheduler was chosen as the simplest scheduler to =
illustrate
> > >> that scheduler can behave differently when using interleaving or =
not.
> > >>>> What about removing the word "urgent" from that sentence.
> > >>>>> In fact I wonder why you speak about urgent things in the =
introduction
> > >>>>> at all. Neither the scheduler nor the interleaving are =
designed to help
> > >>>>> urgent things to be sent earlier.
> > >>>>>
> > >>>>> All they do is make the transmission fairer so that *all* =
chunks get a
> > >>>>> more even serialised distribution on the wire.
> > >>>> That is not true in general. If you use the priority scheduler, =
one
> > >>>> stream gets preferred treatment. It also makes sure that the =
time
> > >>>> of a message spent in the stream queue is shorter. So these =
messages
> > >>>> get sent earlier.
> > >>>> In the case of the round robin scheduler, you are right that =
this is
> > >>>> about getting fairer treatment. If you take the WFQ scheduler, =
the
> > >>>> streams don't get the same treatment, but it depends on the =
weight
> > >>>> given to the stream.
> > >>>>> So, rather than saying that the spec helps urgent things to be =
sent
> > >>>>> earlier, it should maybe rather state that the spec helps =
every message
> > >>>>> getting an equal, and equally distributed, share of the =
medium.
> > >>>> It is not meant that the spec does this. It was one example, =
what
> > >>>> a particular stream scheduler does. But there are multiple =
schedulers
> > >>>> defined in the document.
> > >>>>
> > >>>> The RR scheduler example is not intended to illustrate what you =
can do
> > >>>> with all the schedulers, but that using message interleaving or =
not
> > >>>> has an impact on the scheduler. That is meant by stating:
> > >>>>
> > >>>> This document also defines several stream schedulers for =
general SCTP associations.
> > >>>> The stream schedulers may behave differently depending on =
whether user message
> > >>>> interleaving has been negotiated for the association or not.
> > >>>>
> > >>>> This is followed by illustrating this using the RR scheduler.
> > >>>>
> > >>>> Best regards
> > >>> Also, I don't see the value of the last sentence in this =
paragraph, especially with RFC2119 MAY.
> > >>>
> > >>>   This section defines several stream schedulers.  The stream
> > >>>   schedulers may behave differently depending on whether user =
message
> > >>>   interleaving has been negotiated for the association or not.  =
An
> > >>>   implementation MAY implement any subset of them.
> > >> During the review the question was brought up which scheduler =
have to be implemented
> > >> by an implementation. This sentence was add to address it.
> > >> If you want, I can remove it.
> > > The point is that the MAY is that sentence doesn't mean anything.
> > > Maybe you mean:
> > >
> > > An implementation MUST implement at least one stream scheduler.
> > That would require an implementation to implement at least one of
> > the ones being listed. You are right in the sense that an =
implementation
> > MUST implement at least one stream scheduler, but the original text
> > allows that one not to be specified in this document.
> >
> > Are you saying that an implementation MUST implement one of list =
defined
> > by this document?
> >
> > I'm pretty sure (and this came up in my AD review) the problem is =
that the original specification DID define a stream scheduler, that's =
wasn't called a stream scheduler, but SCTP implementations did schedule =
streams. And that didn't matter until there was more than one way to =
schedule streams (as in this document).
> The original specification did NOT specify a stream scheduler and left =
this completely implementation
> specific.
> Right now Linux is using (and only supporting a single scheduler) what =
we call in this document
> SCTP_SS_FCFS. FreeBSD's default scheduler is what we call in this =
document SCTP_SS_RR and
> Solaris uses one of these, forgot which one. Among these kernel =
implementations, only FreeBSD
> supports multiple streams schedulers and its selection. Possibly other =
closed source SCTP
> implementations might support other schedulers. Don't know.
>=20
> Thanks for getting that right for me ...
>=20
> Spencer
> =20
>  > So you're working out better wording that says something like "in =
addition to the way the original specification scheduled streams, we're =
defining more of them". I think.
> I think we wanted to say something like:
>=20
> Here is a list of schedulers. Your implementation might support some =
of them, but this is
> left open. So you can't rely on it.
>=20
> The list of schedulers we specified includes the ones being used as =
default by FreeBSD, Linux and
> Solaris and was extended by the ones supported by FreeBSD and the one =
explicitly required by
> WebRTC, which is SCTP_SS_WFQ.
>=20
> What about this change:
>=20
> OLD TEXT:
>    An implementation MAY implement any subset of them.
>=20
> NEW TEXT:
>    An implementation MAY implement any subset of them. If the =
implementation
>    is used for WebRTC Datachannels as specified in =
[I-D.ietf-rtcweb-data-channel]
>    it MUST implement the Weighted Fair Queueing Scheduler defined in =
Section 3.6.
>=20
> That works for me, but I'll let Benoit reply.
Benoit?
>=20
> Spencer
> =20
> Best regards
> Michael
> >
> > ?
> >
> > Spencer
>=20
>=20


--Apple-Mail=_28642E5D-A8DE-4456-8499-F55BF38F7C89
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIQkDCCBNUw
ggO9oAMCAQICCFBOxvU9EbRkMA0GCSqGSIb3DQEBCwUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQK
ExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMw
IQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0xNDA3MjIxMjA4MjZaFw0xOTA3
MDkyMzU5MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdE
Rk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAx
BAuZgeKmFNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84Ik
Q4wcOItqaACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVg
Te3RCSMqljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sW
VlZDz+HVEz2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjggGG
MIIBgjAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1Ud
IwQYMBaAFDHDeRu69VPXF+CJei0XbAqzK50zMBIGA1UdEwEB/wQIMAYBAf8CAQIwYgYDVR0gBFsw
WTARBg8rBgEEAYGtIYIsAQEEAgIwEQYPKwYBBAGBrSGCLAEBBAMAMBEGDysGAQQBga0hgiwBAQQD
ATAPBg0rBgEEAYGtIYIsAQEEMA0GCysGAQQBga0hgiweMD4GA1UdHwQ3MDUwM6AxoC+GLWh0dHA6
Ly9wa2kwMzM2LnRlbGVzZWMuZGUvcmwvRFRfUk9PVF9DQV8yLmNybDB4BggrBgEFBQcBAQRsMGow
LAYIKwYBBQUHMAGGIGh0dHA6Ly9vY3NwMDMzNi50ZWxlc2VjLmRlL29jc3ByMDoGCCsGAQUFBzAC
hi5odHRwOi8vcGtpMDMzNi50ZWxlc2VjLmRlL2NydC9EVF9ST09UX0NBXzIuY2VyMA0GCSqGSIb3
DQEBCwUAA4IBAQBjICj9nCGGcr45Rlk5MiW8qQGbDczKfUGchm0KbiyzE1l1sTOSG2EnFv/DstU1
gvuEKgFJvWa7Zi+ywgZdbj9u4wFaW8pDY1yVtuExpx/VB19N5mWCTjL5w3x6S81NXHTuIfJ1AuxS
PtLJatOQI25JZzW+f01WpOzML8+3oZeocj7JvEDWWqQIPda8gsO3tzKOsSyOam23NQIZz/U5RFhj
pyQAELC7/E6vbi84u6VXST/YblBvLJeW3B1GmmWJz67M8uXZn1OzPqEvkqnYC8aEHwTG6x7on321
e6UC8STFJGMRNMxakyAqeYg6JUKQqWU7fIbTEhUjKfws2sw5W1QXMIIFojCCBIqgAwIBAgIHF6Qk
oQlIMzANBgkqhkiG9w0BAQsFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQ
MA4GA1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4X
DTE0MDUyNzE0NTQwOVoXDTE5MDcwOTIzNTkwMFowgcYxCzAJBgNVBAYTAkRFMRwwGgYDVQQIExNO
b3JkcmhlaW4tV2VzdGZhbGVuMREwDwYDVQQHEwhNdWVuc3RlcjEgMB4GA1UEChMXRmFjaGhvY2hz
Y2h1bGUgTXVlbnN0ZXIxIzAhBgNVBAsTGkRhdGVudmVyYXJiZWl0dW5nc3plbnRyYWxlMR0wGwYD
VQQDExRGSCBNdWVuc3RlciBDQSAtIEcwMTEgMB4GCSqGSIb3DQEJARYRY2FAZmgtbXVlbnN0ZXIu
ZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4eWyu8GzsIv0iowf2v/9BT0SmCFNX
/eyQe5BncOk1j6XIlY5bnNu1S5uBe3uVgekgTh3gJyVNlaoIfCgAjqCrNJIaNQq5fr/S6L8uFeaU
O8IF/C4RH5P7f9Hn2GUueEjmJhg9CI3LBAhrfAmEEtNmuVfDycN2MjngwDNxUNRfuXbWxuhkgDqJ
0ztJeayHGhFDrGx88eyStx40xy+0c0OFWdWxzBFQlBRHnl+zRftj3c9qy6BY+/fGaA2vV1oKr3h5
X6eyU1T8YlpP1NDe4bylqAteX01sM2Qciu8UAPnNc7Sb93TQjhCFRVDIS3CdN6AOpwz5YWEld6ey
CdmFZ7pvAgMBAAGjggH+MIIB+jASBgNVHRMBAf8ECDAGAQH/AgEBMA4GA1UdDwEB/wQEAwIBBjAR
BgNVHSAECjAIMAYGBFUdIAAwHQYDVR0OBBYEFArzW7zkMYDWNUKJptPDzzfe0d/XMB8GA1UdIwQY
MBaAFEm3xs/oPR9/6kR7Eyn38QpwPt5kMBwGA1UdEQQVMBOBEWNhQGZoLW11ZW5zdGVyLmRlMIGI
BgNVHR8EgYAwfjA9oDugOYY3aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9w
dWIvY3JsL2NhY3JsLmNybDA9oDugOYY3aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9v
dC1jYS9wdWIvY3JsL2NhY3JsLmNybDCB1wYIKwYBBQUHAQEEgcowgccwMwYIKwYBBQUHMAGGJ2h0
dHA6Ly9vY3NwLnBjYS5kZm4uZGUvT0NTUC1TZXJ2ZXIvT0NTUDBHBggrBgEFBQcwAoY7aHR0cDov
L2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRwYI
KwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2Vy
dC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBCwUAA4IBAQDeRwM11kpvuRIPuzWXLapr/ZBtB76V3cuF
l45x/Kx0u03yjB4GaBPcxihn4P1z5KhRYkDBMo8HXkOgbL59aF6VdOlCurEgZvghKvUkKOCyWeYx
S9rTGPBkbGiNn2ATVuLXzF8rDf50ynAIu3otstOOv+3Ifqi1pzCva1nO64khQA5Gd5/BNyu+YHbW
f8ERAf9leu5a7yVI7cv1gCZAHpWJpkUKmfawyY4sAJ2hbGZRBvdACOxrfbuMdSOzPneT2rlmvH+D
7M6DmzVabLYk6UtAxQhldd/T/qsHkWvaWXHt0Eb9STs2Fl03Ls7M3NyLQLhaeR3ysNURYcaEfaB+
lxN+MIIGDTCCBPWgAwIBAgIHG5mIdDexozANBgkqhkiG9w0BAQsFADCBxjELMAkGA1UEBhMCREUx
HDAaBgNVBAgTE05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQK
ExdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVu
dHJhbGUxHTAbBgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBm
aC1tdWVuc3Rlci5kZTAeFw0xNjA3MDQwNzA2MTNaFw0xOTA3MDQwNzA2MTNaMHwxCzAJBgNVBAYT
AkRFMSAwHgYDVQQKDBdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEyMDAGA1UECwwpRmFjaGJlcmVp
Y2ggRWxla3Ryb3RlY2huaWsgdW5kIEluZm9ybWF0aWsxFzAVBgNVBAMMDk1pY2hhZWwgVHVleGVu
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzJoaUG3Zm24XxA/zNg2sbFcL56w8xqMg
+X6G7UsYec3YEncnlkw3jgE5nDefos7UVoCA7wPjFTj8AQt5xfpXElnbM45IPy5Ng7g6dS7biGSM
VRACPXe1PrjgApRAwwGmCPvALnZXkmKP6Zlf+3VLfz9YWIIaeKu3jFM2Lk6Y3gr5U1l8bjHSawOo
WMlfvSsXXLT38zKW7Uz9jS278j0OqHANBPgsE6/LJoCWFInwlvybxhO3nGU7OteUGaPikqzvjLsL
YgpHDi0WjMZfVx/UtUSzZ4EJvmJTBeuVwyKnCbrawnfwYPTQQ6VE1OkAzmsMByBbEwJ996RtG//T
XCG06QIDAQABo4ICRzCCAkMwQAYDVR0gBDkwNzARBg8rBgEEAYGtIYIsAQEEAwUwEQYPKwYBBAGB
rSGCLAIBBAMBMA8GDSsGAQQBga0hgiwBAQQwCQYDVR0TBAIwADAOBgNVHQ8BAf8EBAMCBeAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBTQHa9qhKgSZgCCAPThZkXaEaJ/
dTAfBgNVHSMEGDAWgBQK81u85DGA1jVCiabTw8833tHf1zAgBgNVHREEGTAXgRV0dWV4ZW5AZmgt
bXVlbnN0ZXIuZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2Zo
LW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZu
LmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIHXBggrBgEFBQcBAQSByjCBxzAz
BggrBgEFBQcwAYYnaHR0cDovL29jc3AucGNhLmRmbi5kZS9PQ1NQLVNlcnZlci9PQ1NQMEcGCCsG
AQUFBzAChjtodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jYWNlcnQv
Y2FjZXJ0LmNydDBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDIucGNhLmRmbi5kZS9maC1tdWVuc3Rl
ci1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQELBQADggEBAEj2/6x4kzoCVIiu
aaminPrOHxACyoYsmSRjYPQpgW5xRj/FlolO1nG+ZZ11sqTb3TdCGD69ko5/zs8eGKnv/i0VLCHF
g1JLfpaxElN5RrR/cqRJrbzKshF9aUkBODF8vlf9BCeimMK3fifjbbWRyxHssfEECffujD7/Yvta
NYMO46Roz39lIK2s37IVFq3V5RWzUeTuwpP9t8lOxirOi9eK2OYI/dh0HjR2S5Dr9nMR1dNulrhz
jlFxGc+opefGScrRR9Ec0eqTXlbt1Q9UzNIYVS+OGZY8/bBbprwXVTmwSp8dygEULkIaMbLsaTaW
6TehuL8ousPJkL52SOENgSkxggQpMIIEJQIBATCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozAJBgUrDgMCGgUAoIICKzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0xNzA4MzExOTU2MDRaMCMGCSqGSIb3DQEJBDEWBBSH8rs70wJLrTrbzGeG
Pmi0dxdI1zCB4wYJKwYBBAGCNxAEMYHVMIHSMIHGMQswCQYDVQQGEwJERTEcMBoGA1UECBMTTm9y
ZHJoZWluLVdlc3RmYWxlbjERMA8GA1UEBxMITXVlbnN0ZXIxIDAeBgNVBAoTF0ZhY2hob2Noc2No
dWxlIE11ZW5zdGVyMSMwIQYDVQQLExpEYXRlbnZlcmFyYmVpdHVuZ3N6ZW50cmFsZTEdMBsGA1UE
AxMURkggTXVlbnN0ZXIgQ0EgLSBHMDExIDAeBgkqhkiG9w0BCQEWEWNhQGZoLW11ZW5zdGVyLmRl
AgcbmYh0N7GjMIHlBgsqhkiG9w0BCRACCzGB1aCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozANBgkqhkiG9w0BAQEFAASCAQCawfm+8wQ4NHop/SJ99IMuDRN8l/UiXp9N
+oMA0gN7SjermU1wWgDZ01/q/slF1zRfF9Xr55nrtXra6Wd4VUnDGESXcrYqIpWlABJCymFelUIU
CeD3DsqYgJBU8m2hAbABiOE9m8QywShyZb3gWg5ZADw4ggzlsA/oKdaxrYmBowepZLYfccjNYO2g
avuXkl85F0Z/7ooVP3Z2hs/1r/+xjDPtk+nGvU4AzyhZ20gRRke3vmyB2I+82td2z6tsbJGxnBW6
zmGeHH6d157YWqZ9vxLRt8yeAl+hwyvmyTiJD32qjfUrvjlf2SUHFWEsXZDjQTpS7D7j4owWUoh9
qjNeAAAAAAAA
--Apple-Mail=_28642E5D-A8DE-4456-8499-F55BF38F7C89--


From nobody Thu Aug 31 14:07:45 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC2511329E3; Thu, 31 Aug 2017 14:07:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ckW8a9uOzjbh; Thu, 31 Aug 2017 14:07:33 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96CFD132351; Thu, 31 Aug 2017 14:07:33 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id h127so4180329ywf.3; Thu, 31 Aug 2017 14:07:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pzR2w3m+KU9mzWudVXpfvpWdAsEEk/8Hy6LLz3ucd60=; b=DC0h44M2eYEmkDk+7GJXtelQ5lNE92mx6f/8ovCi8hbdPxBRpNKNA0GI8UWPdDA406 WedrhMKdDvFGC2mRF5m6IEnxvz7GZqbwySt0tMa/BOJgKYhS8UlTKrZehfZJ5yQYQ7V3 DQxv+OdHnXIAWNRUtKz6bT7KmHugVATkIEW0MpVEDPWUWryTpDDaUaur2kSDjmlw9Hcu CvobAzOwZUoqrMxUalip9vkPysWdDlwgy/wWSf1gQv5jtYcKbTDBxHA0Jc9oQxQZttkc ryOVwc6/KGiZtLKXVuaDSptvWX/6LCoDJmdTWBJ699/An9tpNzJK5TwzmQrhseklhx88 Q+sA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pzR2w3m+KU9mzWudVXpfvpWdAsEEk/8Hy6LLz3ucd60=; b=PxJ7jiExx0D7eGyTU8xeZStv6r3Qpu1RHjOSlAHf2ljrgn7yBSrvY+SyY9M7BUfb7P h84lGt+JIKyoKEaRJgzGYKhEYIBd5lkmQJ3HeeimqSVWfpi/rywxhsheCf4S8siemjgP wv9X2vDBo2/redwyRHBgiZYVjuPqz/C3Hw8057i2L4wpmTSTlIf6/1FI5Bye9SiTK0lS e41qSCISHH/LkU42ZUb13FtsMf9QBpJy1RGbViYYALuzRRdvClNJT8sogm4UiAwUH6dV 4p3UfakKkoM6xQaxiwd7ps4KrJO8qRAZvXkcspbqrm5tkH+NFw9pnZ3mhBVWMg+dSiPR RtGw==
X-Gm-Message-State: AHYfb5jk4bs88SoDmj3cohwniUoqezn4ciu/g7zHG5UDngmnOq2G4ipd CPgSES3SsDc0H+QWE0OujgScPpOJOA==
X-Google-Smtp-Source: ADKCNb6ATaCmw7rqZBzsxj4fTZI6U0lqobDj1KL/MAufndk2KWtxUzsUs+ZDeIsmB+rKj2C+awPQM3YLn9LQWrggMSQ=
X-Received: by 10.37.88.86 with SMTP id m83mr6032881ybb.170.1504213298155; Thu, 31 Aug 2017 14:01:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.2.148 with HTTP; Thu, 31 Aug 2017 14:01:37 -0700 (PDT)
In-Reply-To: <0E628ABF-6E0E-40A6-87EE-CA94A93FE0A5@fh-muenster.de>
References: <150287547583.12471.9085655210334710687@ietfa.amsl.com> <FDCFFA8C-8828-4578-A66E-A1AD7FF9BDC9@fh-muenster.de> <1a39dff3-55a9-fe1d-7e19-a0fbd0b2751b@restena.lu> <F05D0F1F-47E2-4477-BFD9-F0119A4609FC@fh-muenster.de> <f4d121e4-44f5-e85d-98b1-bbea317a7539@cisco.com> <5CEB294C-AAC8-4F03-901D-487CD62BB491@fh-muenster.de> <41a1e8f1-2398-4d94-7021-638acdd58eb7@cisco.com> <1FFDADBA-4132-4D3B-B68C-A89A50AF1E24@fh-muenster.de> <CAKKJt-dM1q9NDe8r=q-aqdWW0i3i8mSYLCNssU4cvjo22GRRyw@mail.gmail.com> <BD327429-5C8F-4034-A9E7-834FDB1E7FB6@fh-muenster.de> <CAKKJt-fuJWEMd79Z2zRmg4GU8hpVcqSfN+Y6xLioMUmwu8d6fw@mail.gmail.com> <0E628ABF-6E0E-40A6-87EE-CA94A93FE0A5@fh-muenster.de>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 31 Aug 2017 16:01:37 -0500
Message-ID: <CAKKJt-c5CnGnpP9Ky8j6=jvPpygLG+t2UZhF68+XP8p4x06veA@mail.gmail.com>
Subject: Re: [OPS-DIR] Opsdir last call review of draft-ietf-tsvwg-sctp-ndata-12
To: Michael Tuexen <tuexen@fh-muenster.de>
Cc: Benoit Claise <bclaise@cisco.com>, Stefan Winter <stefan.winter@restena.lu>, "ops-dir@ietf.org" <ops-dir@ietf.org>, draft-ietf-tsvwg-sctp-ndata.all@ietf.org, "tsvwg@ietf.org" <tsvwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IESG IESG <iesg@ietf.org>
Content-Type: multipart/alternative; boundary="001a114166d44d94e8055812f3b4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rLzLiirB8qFthRD3XKHH_t3JA2k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 31 Aug 2017 21:07:37 -0000

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

Hi, Michael,

On Thu, Aug 31, 2017 at 2:56 PM, Michael Tuexen <tuexen@fh-muenster.de>
wrote:

>
> > On 31. Aug 2017, at 15:46, Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
> >
> > Hi, Michael,
> >
> > On Thu, Aug 31, 2017 at 8:25 AM, Michael Tuexen <tuexen@fh-muenster.de>
> wrote:
> > > On 31. Aug 2017, at 14:50, Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
> > >
> > > Just interjecting ...
> > >
> > > On Thu, Aug 31, 2017 at 7:25 AM, Michael Tuexen <tuexen@fh-muenster.de>
> wrote:
> > >
> > > > On 31. Aug 2017, at 14:14, Benoit Claise <bclaise@cisco.com> wrote:
> > > >
> > > > Hi Michael,
> > > >>> On 30. Aug 2017, at 18:51, Benoit Claise <bclaise@cisco.com>
> wrote:
> > > >>>
> > > >>> Michael,
> > > >>>
> > > >>> I stumbled on the same point as Stefan.
> > > >> Hi Benoit,
> > > >>
> > > >> thanks for reviewing the document. See my comments in-line.
> > > >>
> > > >> Best regards
> > > >> Michael
> > > >>> First of, I had to review RFC4960 for TSN/SSN. I was not sure
> whether TSN was per stream or not
> > > >>> It would have helped me to repeat this information in the intro.
> > > >>> Ok, to be candid, I deduced this information from figure 1 and 2.
> > > >>>>>>> And the rest are only musings not needing any action if the
> authors don't want
> > > >>>>>>> to action on them:
> > > >>>>>>>
> > > >>>>>>> The introduction presents a good use case, quoting: "e.g.,
> when the
> > > >>>>>>> transmission of an urgent
> > > >>>>>>>  message is blocked from transmission because the sender has
> started
> > > >>>>>>>  the transmission of another, possibly large, message".
> > > >>>>>>>
> > > >>>>>>> The later queueing example in figure 1 has three SIDs being
> queued
> > > >>>>>>> simultanseously. It is not clear which of those "has already
> started" and which
> > > >>>>>> There is actually one message queued for stream 0, three
> messages for stream 1,
> > > >>>>>> and one message for stream 2.
> > > >>>>>>> are the important ones being delayed. For a better
> understanding of the reader,
> > > >>>>>> The figure is about in which sequence they are put on the wire.
> So no
> > > >>>>>> transmission has startet. This examples also does not deal with
> the case
> > > >>>>>> of one stream having a higher priority than another. That would
> be an
> > > >>>>>> example using a priority scheduler. This examples illustrates
> the round
> > > >>>>>> robin scheduler.
> > > >>>>>> The point here is that a single scheduler (the round robin
> scheduler, for
> > > >>>>>> example) behaves differently when user message interleaving is
> used or not.
> > > >>>>>> That is an important point: You can even use the schedulers
> with regular
> > > >>>>>> DATA chunk, i.e. with user message interleaving being
> negotiated.
> > > >>> This was my source of confusion.
> > > >>> With figure 1 and figure 2, you want to show the effect of Round
> Robin Scheduler with and without User Message Interleaving, while we were
> expecting the figure 2 to be the solution from this spec. Hence Stefan and
> I were looking for this "urgent message" in figure 2.
> > > >> I don't know what you mean with "solution from this spec" means.
> This spec introduces
> > > >> stream schedulers and a protocol extension to allow interleaving of
> user messages.
> > > >> Using this to implement an "urgent" concept is only one
> possibility: usage of a
> > > >> strict priority scheduler (SCTP_SS_PRIO). So this "urgent" is
> misleading. It seems
> > > >> to ring the wrong bells. That is why I suggested to remove it...
> > > >>>>>>> it might be useful to revise the figure so that the
> head-of-line blocking
> > > >>>>>>> happens for SID 1 because transmission of  0 and 2 has already
> started (and
> > > >>>>>>> declare SID 1 to be the "important" message). The ASCII art
> would just have to
> > > >>>>>>> indent SID 1 content a bit (placing 0 and 2 earlier in time),
> and the resulting
> > > >>>>>>> serialisation would then put all the SID 1 messages at the
> very end, when 0 and
> > > >>>>>>> 2 have been completely submitted (right?).
> > > >>>>>> One could think about adding another example based on the
> priority scheduler
> > > >>>>>> and giving stream 1 a higher priority. But for illustrating the
> point of
> > > >>>>>> schedulers behaving differently depending on the negotiation of
> user message
> > > >>>>>> interleaving this seems not necessary.
> > > >>>>> That second example might indeed be useful.
> > > >>>>>
> > > >>>>> It's simply a bit strange that in the introduction you speak
> about an
> > > >>>>> "urgent" message (something deserving a higher-priority sending)
> and
> > > >>>>> that another transmission has already started - but then the
> example has
> > > >>>>> none of those two.
> > > >>> Exactly.
> > > >>> Please add this extra example.
> > > >>> This would also clarify from the introduction that when you write
> ...
> > > >>>
> > > >>>   The sending of such large messages over
> > > >>>   SCTP as specified in [RFC4960] can result in a form of sender
> side
> > > >>>   head of line blocking (e.g., when the transmission of an urgent
> > > >>>   message is blocked from transmission because the sender has
> started
> > > >>>   the transmission of another, possibly large, message).
> > > >>>
> > > >>> .. the notion of transmission urgency is not within a stream but
> across streams, and that can be achieved with a priority scheduler.
> > > >> I would actually prefer to remove the word "urgent" from that
> sentence. This just rings the wrong bells.
> > > > That's a missed opportunity in mind, but your call.
> > > Hmm. Let me remove the word "urgent"...
> > >
> > > Yes, please! I wasn't wild about it, either.
> > It's done:
> > https://github.com/sctplab/sctp-idata/commit/cf7b331512cd85d
> 6195eb88fa96360673293323f
> > >
> > > >>> The text might have to be rephrased to explain that this spec
> provides the ability to create stream scheduler with different relative
> stream treatments.
> > > >> What about:
> > > >>
> > > >> OLD TEXT
> > > >>    This document also defines several stream schedulers for general
> SCTP
> > > >>    associations.  The stream schedulers may behave differently
> depending
> > > >>    on whether user message interleaving has been negotiated for the
> > > >>    association or not.
> > > >>
> > > >> NEW TEXT
> > > >>    This document also defines several stream schedulers for general
> SCTP
> > > >>    associations allowing different relative stream treatments.
> > > >>    The stream schedulers may behave differently depending
> > > >>    on whether user message interleaving has been negotiated for the
> > > >>    association or not.
> > > >>
> > > >> Would that address this issue?
> > > > ok.
> > > Fixed.
> > > >>
> > > >>> And also that urgent message would be placed in this high priority
> stream scheduler (reliable, I guess, but that's orthogonal) stream.
> > > >> I really would like to get rid of this. I don't think giving the
> strict
> > > >> priority scheduler as specific role here is a good idea.
> > > >>
> > > >> The RR scheduler was chosen as the simplest scheduler to illustrate
> > > >> that scheduler can behave differently when using interleaving or
> not.
> > > >>>> What about removing the word "urgent" from that sentence.
> > > >>>>> In fact I wonder why you speak about urgent things in the
> introduction
> > > >>>>> at all. Neither the scheduler nor the interleaving are designed
> to help
> > > >>>>> urgent things to be sent earlier.
> > > >>>>>
> > > >>>>> All they do is make the transmission fairer so that *all* chunks
> get a
> > > >>>>> more even serialised distribution on the wire.
> > > >>>> That is not true in general. If you use the priority scheduler,
> one
> > > >>>> stream gets preferred treatment. It also makes sure that the time
> > > >>>> of a message spent in the stream queue is shorter. So these
> messages
> > > >>>> get sent earlier.
> > > >>>> In the case of the round robin scheduler, you are right that this
> is
> > > >>>> about getting fairer treatment. If you take the WFQ scheduler, the
> > > >>>> streams don't get the same treatment, but it depends on the weight
> > > >>>> given to the stream.
> > > >>>>> So, rather than saying that the spec helps urgent things to be
> sent
> > > >>>>> earlier, it should maybe rather state that the spec helps every
> message
> > > >>>>> getting an equal, and equally distributed, share of the medium.
> > > >>>> It is not meant that the spec does this. It was one example, what
> > > >>>> a particular stream scheduler does. But there are multiple
> schedulers
> > > >>>> defined in the document.
> > > >>>>
> > > >>>> The RR scheduler example is not intended to illustrate what you
> can do
> > > >>>> with all the schedulers, but that using message interleaving or
> not
> > > >>>> has an impact on the scheduler. That is meant by stating:
> > > >>>>
> > > >>>> This document also defines several stream schedulers for general
> SCTP associations.
> > > >>>> The stream schedulers may behave differently depending on whether
> user message
> > > >>>> interleaving has been negotiated for the association or not.
> > > >>>>
> > > >>>> This is followed by illustrating this using the RR scheduler.
> > > >>>>
> > > >>>> Best regards
> > > >>> Also, I don't see the value of the last sentence in this
> paragraph, especially with RFC2119 MAY.
> > > >>>
> > > >>>   This section defines several stream schedulers.  The stream
> > > >>>   schedulers may behave differently depending on whether user
> message
> > > >>>   interleaving has been negotiated for the association or not.  An
> > > >>>   implementation MAY implement any subset of them.
> > > >> During the review the question was brought up which scheduler have
> to be implemented
> > > >> by an implementation. This sentence was add to address it.
> > > >> If you want, I can remove it.
> > > > The point is that the MAY is that sentence doesn't mean anything.
> > > > Maybe you mean:
> > > >
> > > > An implementation MUST implement at least one stream scheduler.
> > > That would require an implementation to implement at least one of
> > > the ones being listed. You are right in the sense that an
> implementation
> > > MUST implement at least one stream scheduler, but the original text
> > > allows that one not to be specified in this document.
> > >
> > > Are you saying that an implementation MUST implement one of list
> defined
> > > by this document?
> > >
> > > I'm pretty sure (and this came up in my AD review) the problem is that
> the original specification DID define a stream scheduler, that's wasn't
> called a stream scheduler, but SCTP implementations did schedule streams.
> And that didn't matter until there was more than one way to schedule
> streams (as in this document).
> > The original specification did NOT specify a stream scheduler and left
> this completely implementation
> > specific.
> > Right now Linux is using (and only supporting a single scheduler) what
> we call in this document
> > SCTP_SS_FCFS. FreeBSD's default scheduler is what we call in this
> document SCTP_SS_RR and
> > Solaris uses one of these, forgot which one. Among these kernel
> implementations, only FreeBSD
> > supports multiple streams schedulers and its selection. Possibly other
> closed source SCTP
> > implementations might support other schedulers. Don't know.
> >
> > Thanks for getting that right for me ...
> >
> > Spencer
> >
> >  > So you're working out better wording that says something like "in
> addition to the way the original specification scheduled streams, we're
> defining more of them". I think.
> > I think we wanted to say something like:
> >
> > Here is a list of schedulers. Your implementation might support some of
> them, but this is
> > left open. So you can't rely on it.
> >
> > The list of schedulers we specified includes the ones being used as
> default by FreeBSD, Linux and
> > Solaris and was extended by the ones supported by FreeBSD and the one
> explicitly required by
> > WebRTC, which is SCTP_SS_WFQ.
> >
> > What about this change:
> >
> > OLD TEXT:
> >    An implementation MAY implement any subset of them.
> >
> > NEW TEXT:
> >    An implementation MAY implement any subset of them. If the
> implementation
> >    is used for WebRTC Datachannels as specified in
> [I-D.ietf-rtcweb-data-channel]
> >    it MUST implement the Weighted Fair Queueing Scheduler defined in
> Section 3.6.
> >
> > That works for me, but I'll let Benoit reply.
> Benoit?
>

Since I'm not sure which timezone Benoit is in (except that I know it's
Yang Central Time), I'll respond by saying that I did talk with Benoit on
the call, after sending him this privately:


This is tripping over the same thing I was tripping over - SCTP standards
haven't had a stream scheduler, but SCTP implementations scheduled streams.
So Michael was thinking that you were asking about forcing existing
implementations to implement one of the new ones.

His response was to propose text basically saying "in addition to what
you're doing now, you MAY do one or more of the following".

I'm sorry I garbled my point so badly.

Benoit said on the call (if I understood him correctly) that my explanation
(filtered through your correction) worked for him. The point I was trying
to make earlier was that SCTP implementations scheduled streams somehow,
and that your document wasn't an effort to tell them to stop doing what
they were doing, but that implementers now had more standardized options
than they did before.

I think your proposed text says that well.

At this point, I think you're ready to submit a revised ID to reflect the
comments you've received. I'll review your changes, and that will give
Benoit a chance to interrupt if he needs to - he's quite responsive,
especially when he doesn't spend the evening on a telechat.

Thanks, and it's always a pleasure.

Spencer


> >
> > Spencer
> >
> > Best regards
> > Michael
> > >
> > > ?
> > >
> > > Spencer
> >
> >
>
>

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

<div dir=3D"ltr">Hi, Michael,<div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Thu, Aug 31, 2017 at 2:56 PM, Michael Tuexen <span dir=3D"lt=
r">&lt;<a href=3D"mailto:tuexen@fh-muenster.de" target=3D"_blank">tuexen@fh=
-muenster.de</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div class=3D"m_4016144414174465647gmail-HOEnZb"><div class=3D=
"m_4016144414174465647gmail-h5"><br>
&gt; On 31. Aug 2017, at 15:46, Spencer Dawkins at IETF &lt;<a href=3D"mail=
to:spencerdawkins.ietf@gmail.com" target=3D"_blank">spencerdawkins.ietf@gma=
il.com</a><wbr>&gt; wrote:<br>
&gt;<br>
&gt; Hi, Michael,<br>
&gt;<br>
&gt; On Thu, Aug 31, 2017 at 8:25 AM, Michael Tuexen &lt;<a href=3D"mailto:=
tuexen@fh-muenster.de" target=3D"_blank">tuexen@fh-muenster.de</a>&gt; wrot=
e:<br>
&gt; &gt; On 31. Aug 2017, at 14:50, Spencer Dawkins at IETF &lt;<a href=3D=
"mailto:spencerdawkins.ietf@gmail.com" target=3D"_blank">spencerdawkins.iet=
f@gmail.com</a><wbr>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; Just interjecting ...<br>
&gt; &gt;<br>
&gt; &gt; On Thu, Aug 31, 2017 at 7:25 AM, Michael Tuexen &lt;<a href=3D"ma=
ilto:tuexen@fh-muenster.de" target=3D"_blank">tuexen@fh-muenster.de</a>&gt;=
 wrote:<br>
&gt; &gt;<br>
&gt; &gt; &gt; On 31. Aug 2017, at 14:14, Benoit Claise &lt;<a href=3D"mail=
to:bclaise@cisco.com" target=3D"_blank">bclaise@cisco.com</a>&gt; wrote:<br=
>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Hi Michael,<br>
&gt; &gt; &gt;&gt;&gt; On 30. Aug 2017, at 18:51, Benoit Claise &lt;<a href=
=3D"mailto:bclaise@cisco.com" target=3D"_blank">bclaise@cisco.com</a>&gt; w=
rote:<br>
&gt; &gt; &gt;&gt;&gt;<br>
&gt; &gt; &gt;&gt;&gt; Michael,<br>
&gt; &gt; &gt;&gt;&gt;<br>
&gt; &gt; &gt;&gt;&gt; I stumbled on the same point as Stefan.<br>
&gt; &gt; &gt;&gt; Hi Benoit,<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; thanks for reviewing the document. See my comments in-li=
ne.<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; Best regards<br>
&gt; &gt; &gt;&gt; Michael<br>
&gt; &gt; &gt;&gt;&gt; First of, I had to review RFC4960 for TSN/SSN. I was=
 not sure whether TSN was per stream or not<br>
&gt; &gt; &gt;&gt;&gt; It would have helped me to repeat this information i=
n the intro.<br>
&gt; &gt; &gt;&gt;&gt; Ok, to be candid, I deduced this information from fi=
gure 1 and 2.<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; And the rest are only musings not ne=
eding any action if the authors don&#39;t want<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; to action on them:<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; The introduction presents a good use=
 case, quoting: &quot;e.g., when the<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; transmission of an urgent<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 message is blocked from transm=
ission because the sender has started<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 the transmission of another, p=
ossibly large, message&quot;.<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; The later queueing example in figure=
 1 has three SIDs being queued<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; simultanseously. It is not clear whi=
ch of those &quot;has already started&quot; and which<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; There is actually one message queued for=
 stream 0, three messages for stream 1,<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; and one message for stream 2.<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; are the important ones being delayed=
. For a better understanding of the reader,<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; The figure is about in which sequence th=
ey are put on the wire. So no<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; transmission has startet. This examples =
also does not deal with the case<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; of one stream having a higher priority t=
han another. That would be an<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; example using a priority scheduler. This=
 examples illustrates the round<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; robin scheduler.<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; The point here is that a single schedule=
r (the round robin scheduler, for<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; example) behaves differently when user m=
essage interleaving is used or not.<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; That is an important point: You can even=
 use the schedulers with regular<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; DATA chunk, i.e. with user message inter=
leaving being negotiated.<br>
&gt; &gt; &gt;&gt;&gt; This was my source of confusion.<br>
&gt; &gt; &gt;&gt;&gt; With figure 1 and figure 2, you want to show the eff=
ect of Round Robin Scheduler with and without User Message Interleaving, wh=
ile we were expecting the figure 2 to be the solution from this spec. Hence=
 Stefan and I were looking for this &quot;urgent message&quot; in figure 2.=
<br>
&gt; &gt; &gt;&gt; I don&#39;t know what you mean with &quot;solution from =
this spec&quot; means. This spec introduces<br>
&gt; &gt; &gt;&gt; stream schedulers and a protocol extension to allow inte=
rleaving of user messages.<br>
&gt; &gt; &gt;&gt; Using this to implement an &quot;urgent&quot; concept is=
 only one possibility: usage of a<br>
&gt; &gt; &gt;&gt; strict priority scheduler (SCTP_SS_PRIO). So this &quot;=
urgent&quot; is misleading. It seems<br>
&gt; &gt; &gt;&gt; to ring the wrong bells. That is why I suggested to remo=
ve it...<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; it might be useful to revise the fig=
ure so that the head-of-line blocking<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; happens for SID 1 because transmissi=
on of=C2=A0 0 and 2 has already started (and<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; declare SID 1 to be the &quot;import=
ant&quot; message). The ASCII art would just have to<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; indent SID 1 content a bit (placing =
0 and 2 earlier in time), and the resulting<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; serialisation would then put all the=
 SID 1 messages at the very end, when 0 and<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; 2 have been completely submitted (ri=
ght?).<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; One could think about adding another exa=
mple based on the priority scheduler<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; and giving stream 1 a higher priority. B=
ut for illustrating the point of<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; schedulers behaving differently dependin=
g on the negotiation of user message<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; interleaving this seems not necessary.<b=
r>
&gt; &gt; &gt;&gt;&gt;&gt;&gt; That second example might indeed be useful.<=
br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt; It&#39;s simply a bit strange that in the in=
troduction you speak about an<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt; &quot;urgent&quot; message (something deserv=
ing a higher-priority sending) and<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt; that another transmission has already starte=
d - but then the example has<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt; none of those two.<br>
&gt; &gt; &gt;&gt;&gt; Exactly.<br>
&gt; &gt; &gt;&gt;&gt; Please add this extra example.<br>
&gt; &gt; &gt;&gt;&gt; This would also clarify from the introduction that w=
hen you write ...<br>
&gt; &gt; &gt;&gt;&gt;<br>
&gt; &gt; &gt;&gt;&gt;=C2=A0 =C2=A0The sending of such large messages over<=
br>
&gt; &gt; &gt;&gt;&gt;=C2=A0 =C2=A0SCTP as specified in [RFC4960] can resul=
t in a form of sender side<br>
&gt; &gt; &gt;&gt;&gt;=C2=A0 =C2=A0head of line blocking (e.g., when the tr=
ansmission of an urgent<br>
&gt; &gt; &gt;&gt;&gt;=C2=A0 =C2=A0message is blocked from transmission bec=
ause the sender has started<br>
&gt; &gt; &gt;&gt;&gt;=C2=A0 =C2=A0the transmission of another, possibly la=
rge, message).<br>
&gt; &gt; &gt;&gt;&gt;<br>
&gt; &gt; &gt;&gt;&gt; .. the notion of transmission urgency is not within =
a stream but across streams, and that can be achieved with a priority sched=
uler.<br>
&gt; &gt; &gt;&gt; I would actually prefer to remove the word &quot;urgent&=
quot; from that sentence. This just rings the wrong bells.<br>
&gt; &gt; &gt; That&#39;s a missed opportunity in mind, but your call.<br>
&gt; &gt; Hmm. Let me remove the word &quot;urgent&quot;...<br>
&gt; &gt;<br>
&gt; &gt; Yes, please! I wasn&#39;t wild about it, either.<br>
&gt; It&#39;s done:<br>
&gt; <a href=3D"https://github.com/sctplab/sctp-idata/commit/cf7b331512cd85=
d6195eb88fa96360673293323f" rel=3D"noreferrer" target=3D"_blank">https://gi=
thub.com/sctplab/sct<wbr>p-idata/commit/cf7b331512cd85d<wbr>6195eb88fa96360=
673293323f</a><br>
&gt; &gt;<br>
&gt; &gt; &gt;&gt;&gt; The text might have to be rephrased to explain that =
this spec provides the ability to create stream scheduler with different re=
lative stream treatments.<br>
&gt; &gt; &gt;&gt; What about:<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; OLD TEXT<br>
&gt; &gt; &gt;&gt;=C2=A0 =C2=A0 This document also defines several stream s=
chedulers for general SCTP<br>
&gt; &gt; &gt;&gt;=C2=A0 =C2=A0 associations.=C2=A0 The stream schedulers m=
ay behave differently depending<br>
&gt; &gt; &gt;&gt;=C2=A0 =C2=A0 on whether user message interleaving has be=
en negotiated for the<br>
&gt; &gt; &gt;&gt;=C2=A0 =C2=A0 association or not.<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; NEW TEXT<br>
&gt; &gt; &gt;&gt;=C2=A0 =C2=A0 This document also defines several stream s=
chedulers for general SCTP<br>
&gt; &gt; &gt;&gt;=C2=A0 =C2=A0 associations allowing different relative st=
ream treatments.<br>
&gt; &gt; &gt;&gt;=C2=A0 =C2=A0 The stream schedulers may behave differentl=
y depending<br>
&gt; &gt; &gt;&gt;=C2=A0 =C2=A0 on whether user message interleaving has be=
en negotiated for the<br>
&gt; &gt; &gt;&gt;=C2=A0 =C2=A0 association or not.<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; Would that address this issue?<br>
&gt; &gt; &gt; ok.<br>
&gt; &gt; Fixed.<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt;&gt; And also that urgent message would be placed in this=
 high priority stream scheduler (reliable, I guess, but that&#39;s orthogon=
al) stream.<br>
&gt; &gt; &gt;&gt; I really would like to get rid of this. I don&#39;t thin=
k giving the strict<br>
&gt; &gt; &gt;&gt; priority scheduler as specific role here is a good idea.=
<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; The RR scheduler was chosen as the simplest scheduler to=
 illustrate<br>
&gt; &gt; &gt;&gt; that scheduler can behave differently when using interle=
aving or not.<br>
&gt; &gt; &gt;&gt;&gt;&gt; What about removing the word &quot;urgent&quot; =
from that sentence.<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt; In fact I wonder why you speak about urgent =
things in the introduction<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt; at all. Neither the scheduler nor the interl=
eaving are designed to help<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt; urgent things to be sent earlier.<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt; All they do is make the transmission fairer =
so that *all* chunks get a<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt; more even serialised distribution on the wir=
e.<br>
&gt; &gt; &gt;&gt;&gt;&gt; That is not true in general. If you use the prio=
rity scheduler, one<br>
&gt; &gt; &gt;&gt;&gt;&gt; stream gets preferred treatment. It also makes s=
ure that the time<br>
&gt; &gt; &gt;&gt;&gt;&gt; of a message spent in the stream queue is shorte=
r. So these messages<br>
&gt; &gt; &gt;&gt;&gt;&gt; get sent earlier.<br>
&gt; &gt; &gt;&gt;&gt;&gt; In the case of the round robin scheduler, you ar=
e right that this is<br>
&gt; &gt; &gt;&gt;&gt;&gt; about getting fairer treatment. If you take the =
WFQ scheduler, the<br>
&gt; &gt; &gt;&gt;&gt;&gt; streams don&#39;t get the same treatment, but it=
 depends on the weight<br>
&gt; &gt; &gt;&gt;&gt;&gt; given to the stream.<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt; So, rather than saying that the spec helps u=
rgent things to be sent<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt; earlier, it should maybe rather state that t=
he spec helps every message<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt; getting an equal, and equally distributed, s=
hare of the medium.<br>
&gt; &gt; &gt;&gt;&gt;&gt; It is not meant that the spec does this. It was =
one example, what<br>
&gt; &gt; &gt;&gt;&gt;&gt; a particular stream scheduler does. But there ar=
e multiple schedulers<br>
&gt; &gt; &gt;&gt;&gt;&gt; defined in the document.<br>
&gt; &gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt; &gt;&gt;&gt;&gt; The RR scheduler example is not intended to illu=
strate what you can do<br>
&gt; &gt; &gt;&gt;&gt;&gt; with all the schedulers, but that using message =
interleaving or not<br>
&gt; &gt; &gt;&gt;&gt;&gt; has an impact on the scheduler. That is meant by=
 stating:<br>
&gt; &gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt; &gt;&gt;&gt;&gt; This document also defines several stream schedu=
lers for general SCTP associations.<br>
&gt; &gt; &gt;&gt;&gt;&gt; The stream schedulers may behave differently dep=
ending on whether user message<br>
&gt; &gt; &gt;&gt;&gt;&gt; interleaving has been negotiated for the associa=
tion or not.<br>
&gt; &gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt; &gt;&gt;&gt;&gt; This is followed by illustrating this using the =
RR scheduler.<br>
&gt; &gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt; &gt;&gt;&gt;&gt; Best regards<br>
&gt; &gt; &gt;&gt;&gt; Also, I don&#39;t see the value of the last sentence=
 in this paragraph, especially with RFC2119 MAY.<br>
&gt; &gt; &gt;&gt;&gt;<br>
&gt; &gt; &gt;&gt;&gt;=C2=A0 =C2=A0This section defines several stream sche=
dulers.=C2=A0 The stream<br>
&gt; &gt; &gt;&gt;&gt;=C2=A0 =C2=A0schedulers may behave differently depend=
ing on whether user message<br>
&gt; &gt; &gt;&gt;&gt;=C2=A0 =C2=A0interleaving has been negotiated for the=
 association or not.=C2=A0 An<br>
&gt; &gt; &gt;&gt;&gt;=C2=A0 =C2=A0implementation MAY implement any subset =
of them.<br>
&gt; &gt; &gt;&gt; During the review the question was brought up which sche=
duler have to be implemented<br>
&gt; &gt; &gt;&gt; by an implementation. This sentence was add to address i=
t.<br>
&gt; &gt; &gt;&gt; If you want, I can remove it.<br>
&gt; &gt; &gt; The point is that the MAY is that sentence doesn&#39;t mean =
anything.<br>
&gt; &gt; &gt; Maybe you mean:<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; An implementation MUST implement at least one stream schedul=
er.<br>
&gt; &gt; That would require an implementation to implement at least one of=
<br>
&gt; &gt; the ones being listed. You are right in the sense that an impleme=
ntation<br>
&gt; &gt; MUST implement at least one stream scheduler, but the original te=
xt<br>
&gt; &gt; allows that one not to be specified in this document.<br>
&gt; &gt;<br>
&gt; &gt; Are you saying that an implementation MUST implement one of list =
defined<br>
&gt; &gt; by this document?<br>
&gt; &gt;<br>
&gt; &gt; I&#39;m pretty sure (and this came up in my AD review) the proble=
m is that the original specification DID define a stream scheduler, that&#3=
9;s wasn&#39;t called a stream scheduler, but SCTP implementations did sche=
dule streams. And that didn&#39;t matter until there was more than one way =
to schedule streams (as in this document).<br>
&gt; The original specification did NOT specify a stream scheduler and left=
 this completely implementation<br>
&gt; specific.<br>
&gt; Right now Linux is using (and only supporting a single scheduler) what=
 we call in this document<br>
&gt; SCTP_SS_FCFS. FreeBSD&#39;s default scheduler is what we call in this =
document SCTP_SS_RR and<br>
&gt; Solaris uses one of these, forgot which one. Among these kernel implem=
entations, only FreeBSD<br>
&gt; supports multiple streams schedulers and its selection. Possibly other=
 closed source SCTP<br>
&gt; implementations might support other schedulers. Don&#39;t know.<br>
&gt;<br>
&gt; Thanks for getting that right for me ...<br>
&gt;<br>
&gt; Spencer<br>
&gt;<br>
&gt;=C2=A0 &gt; So you&#39;re working out better wording that says somethin=
g like &quot;in addition to the way the original specification scheduled st=
reams, we&#39;re defining more of them&quot;. I think.<br>
&gt; I think we wanted to say something like:<br>
&gt;<br>
&gt; Here is a list of schedulers. Your implementation might support some o=
f them, but this is<br>
&gt; left open. So you can&#39;t rely on it.<br>
&gt;<br>
&gt; The list of schedulers we specified includes the ones being used as de=
fault by FreeBSD, Linux and<br>
&gt; Solaris and was extended by the ones supported by FreeBSD and the one =
explicitly required by<br>
&gt; WebRTC, which is SCTP_SS_WFQ.<br>
&gt;<br>
&gt; What about this change:<br>
&gt;<br>
&gt; OLD TEXT:<br>
&gt;=C2=A0 =C2=A0 An implementation MAY implement any subset of them.<br>
&gt;<br>
&gt; NEW TEXT:<br>
&gt;=C2=A0 =C2=A0 An implementation MAY implement any subset of them. If th=
e implementation<br>
&gt;=C2=A0 =C2=A0 is used for WebRTC Datachannels as specified in [I-D.ietf=
-rtcweb-data-channel]<br>
&gt;=C2=A0 =C2=A0 it MUST implement the Weighted Fair Queueing Scheduler de=
fined in Section 3.6.<br>
&gt;<br>
&gt; That works for me, but I&#39;ll let Benoit reply.<br>
</div></div>Benoit?<br></blockquote><div><br></div><div>Since I&#39;m not s=
ure which timezone Benoit is in (except that I know it&#39;s Yang Central T=
ime), I&#39;ll respond by saying that I did talk with Benoit on the call, a=
fter sending him this privately:</div></div></div><blockquote style=3D"marg=
in:0 0 0 40px;border:none;padding:0px"><div class=3D"gmail_extra"><div clas=
s=3D"gmail_quote"><div><br></div></div></div><div class=3D"gmail_extra"><di=
v class=3D"gmail_quote"><div><div>This is tripping over the same thing I wa=
s tripping over - SCTP standards haven&#39;t had a stream scheduler, but SC=
TP implementations scheduled streams. So Michael was thinking that you were=
 asking about forcing existing implementations to implement one of the new =
ones.=C2=A0</div></div></div></div><div class=3D"gmail_extra"><div class=3D=
"gmail_quote"><div><div><br></div></div></div></div><div class=3D"gmail_ext=
ra"><div class=3D"gmail_quote"><div><div>His response was to propose text b=
asically saying &quot;in addition to what you&#39;re doing now, you MAY do =
one or more of the following&quot;.=C2=A0</div></div></div></div><div class=
=3D"gmail_extra"><div class=3D"gmail_quote"><div><div><br></div></div></div=
></div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div><div>I&#3=
9;m sorry I garbled my point so badly.</div></div><div><br></div></div></di=
v></blockquote>Benoit said on the call (if I understood him correctly) that=
 my explanation (filtered through your correction) worked for him. The poin=
t I was trying to make earlier was that SCTP implementations scheduled stre=
ams somehow, and that your document wasn&#39;t an effort to tell them to st=
op doing what they were doing, but that implementers now had more standardi=
zed options than they did before.<div><br></div><div>I think your proposed =
text says that well.=C2=A0<br><div><br></div><div>At this point, I think yo=
u&#39;re ready to submit a revised ID to reflect the comments you&#39;ve re=
ceived. I&#39;ll review your changes, and that will give Benoit a chance to=
 interrupt if he needs to - he&#39;s quite responsive, especially when he d=
oesn&#39;t spend the evening on a telechat.</div><div><br></div><div>Thanks=
, and it&#39;s always a pleasure.</div><div><br></div><div>Spencer<br><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><div>=C2=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">
<div class=3D"m_4016144414174465647gmail-HOEnZb"><div class=3D"m_4016144414=
174465647gmail-h5">&gt;<br>
&gt; Spencer<br>
&gt;<br>
&gt; Best regards<br>
&gt; Michael<br>
&gt; &gt;<br>
&gt; &gt; ?<br>
&gt; &gt;<br>
&gt; &gt; Spencer<br>
&gt;<br>
&gt;<br>
<br>
</div></div></blockquote></div><br></div></div></div></div>

--001a114166d44d94e8055812f3b4--


From nobody Thu Aug 31 17:56:08 2017
Return-Path: <cpignata@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2534E133104; Thu, 31 Aug 2017 17:56:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level: 
X-Spam-Status: No, score=-14.521 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SOpRh3nXnbkf; Thu, 31 Aug 2017 17:56:04 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7794C132AA5; Thu, 31 Aug 2017 17:55:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9846; q=dns/txt; s=iport; t=1504227359; x=1505436959; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=KCvqZmLbiHo6HleXa1bYiAXq9I3JHIqkZyocYxQ9hpc=; b=dCzqXhjmQc/ojSXKG2nrak3bvwdXuqPEqZUM1JJCM7kc6D4UWBQL0OKK JlNfi4E73tfP8b7h0AUVi1SrDokwlUboZjjv8czoZccIzMiBkRR57RiNZ LgZkEgPqnp4CHA0X1JuhvrOjlHgXbF9ETm6aPPhjeApMCB+fiJfhhJrzs c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DjAACOr6hZ/4MNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1pkgRUHjhCQH4FPIog5jW4OggQuhRkCGoN1PxgBAgEBAQEBAQF?= =?us-ascii?q?rKIUYAQEBAQIBIxFABQULAgEIDgYEAgImAgICHxEVEAIEDgUbiX4DDQgQrzGCJ?= =?us-ascii?q?4c8DYQaAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYENgh2CAoFOgWMrC4JygleCBoM?= =?us-ascii?q?rMIIxBYl7iRGFJYgCPAKHWYNahCaEdoIThWeDfYZ3jE6JdgEfOIENdxVbAYcId?= =?us-ascii?q?gGJSoEPAQEB?=
X-IronPort-AV: E=Sophos;i="5.41,456,1498521600"; d="scan'208";a="288107835"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Sep 2017 00:55:58 +0000
Received: from XCH-RTP-016.cisco.com (xch-rtp-016.cisco.com [64.101.220.156]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v810twRR022955 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 1 Sep 2017 00:55:58 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-016.cisco.com (64.101.220.156) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 31 Aug 2017 20:55:57 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1263.000; Thu, 31 Aug 2017 20:55:57 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Dan Romascanu <dromasca@gmail.com>
CC: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Service Function Chaining IETF list <sfc@ietf.org>, "draft-ietf-sfc-nsh.all@ietf.org" <draft-ietf-sfc-nsh.all@ietf.org>
Subject: Re: Genart last call review of draft-ietf-sfc-nsh-19
Thread-Topic: Genart last call review of draft-ietf-sfc-nsh-19
Thread-Index: AQHTG1wXf572axcqxkiCBrPJS5Tss6KfhneA
Date: Fri, 1 Sep 2017 00:55:57 +0000
Message-ID: <780ED7FA-6417-40A8-8524-69887C3AB161@cisco.com>
References: <150341604132.6021.14134855950693780483@ietfa.amsl.com>
In-Reply-To: <150341604132.6021.14134855950693780483@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.116.133]
Content-Type: text/plain; charset="utf-8"
Content-ID: <EF23E455649217468F2341A4E01BFAB6@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EsuRviLrst0kYLlrG79NXq86Yr8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Sep 2017 00:56:07 -0000

SGksIERhbiwNCg0KTWFueSB0aGFua3MgZm9yIHlvdXIgZGV0YWlsZWQgYW5kIHZhbHVhYmxlIHJl
dmlldywgYW5kIGFwb2xvZ2llcyBmb3IgdGhlIGRlbGF5IGluIEFjay1pbmcgYW5kIHJlc3BvbmRp
bmcuDQoNClBsZWFzZSBzZWUgaW5saW5lLg0KDQrigJQNCkNhcmxvcyBQaWduYXRhcm8sIGNhcmxv
c0BjaXNjby5jb20NCg0K4oCcU29tZXRpbWVzIEkgdXNlIGJpZyB3b3JkcyB0aGF0IEkgZG8gbm90
IGZ1bGx5IHVuZGVyc3RhbmQsIHRvIG1ha2UgbXlzZWxmIHNvdW5kIG1vcmUgcGhvdG9zeW50aGVz
aXMuIg0KDQo+IE9uIEF1ZyAyMiwgMjAxNywgYXQgMTE6MzQgQU0sIERhbiBSb21hc2NhbnUgPGRy
b21hc2NhQGdtYWlsLmNvbT4gd3JvdGU6DQo+IA0KPiBSZXZpZXdlcjogRGFuIFJvbWFzY2FudQ0K
PiBSZXZpZXcgcmVzdWx0OiBBbG1vc3QgUmVhZHkNCj4gDQo+IEkgYW0gdGhlIGFzc2lnbmVkIEdl
bi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsIEFyZWENCj4gUmV2aWV3
IFRlYW0gKEdlbi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3Nl
ZA0KPiBieSB0aGUgSUVTRyBmb3IgdGhlIElFVEYgQ2hhaXIuICBQbGVhc2UgdHJlYXQgdGhlc2Ug
Y29tbWVudHMganVzdA0KPiBsaWtlIGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQo+IA0K
PiBGb3IgbW9yZSBpbmZvcm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0DQo+IA0KPiA8aHR0
cHM6Ly90cmFjLmlldGYub3JnL3RyYWMvZ2VuL3dpa2kvR2VuQXJ0ZmFxPi4NCj4gDQo+IERvY3Vt
ZW50OiBkcmFmdC1pZXRmLXNmYy1uc2gtMTkNCj4gUmV2aWV3ZXI6IERhbiBSb21hc2NhbnUNCj4g
UmV2aWV3IERhdGU6IDIwMTctMDgtMjINCj4gSUVURiBMQyBFbmQgRGF0ZTogMjAxNy0wOC0yNQ0K
PiBJRVNHIFRlbGVjaGF0IGRhdGU6IDIwMTctMDktMTQNCj4gDQo+IFN1bW1hcnk6DQo+IA0KPiBU
aGlzIGRvY3VtZW50IGRlc2NyaWJlcyB0aGUgaGVhZGVyIChjYWxsZWQgTmV0d29yayBTZXJ2aWNl
IEhlYWRlciAtIE5TSCkgdG8gYmUNCj4gaW5zZXJ0ZWQgaW4gcGFja2V0cyBhbmQgZnJhbWVzIGlu
IG9yZGVyIHRvIGNyZWF0ZSBwYWNrZXRzIGFuZCBmcmFtZXMgdGhhdA0KPiByZWFsaXplIHNlcnZp
Y2UgZnVuY3Rpb25zIGRlc2NyaWJlZCBieSBvdGhlciBTRkMgZG9jdW1lbnRzLiBJdCBuZWVkcyB0
byBiZSByZWFkDQo+IGluIGNvbmp1bmN0aW9uIHdpdGggUkZDIDc2NjUgYW5kIG90aGVyIGRvY3Vt
ZW50cyBhcyB0aGUgU0ZDIGNvbnRyb2wgcGxhbmUgSS1EDQo+IGluIG9yZGVyIHRvIG1ha2Ugc2Vu
c2Ugb2YgdGhlIHJlcXVpcmVkIGZ1bmN0aW9uYWxpdHkuIFRoaXMgcGFydCBvZiB0aGUgU0ZDDQo+
IHNvbHV0aW9uIHNlZW1zIGFsbW9zdCByZWFkeSwgYnV0IGEgZmV3IGlzc3VlcyBtZW50aW9uZWQg
YmVsb3cgbmVlZCBpbiBteQ0KPiBvcGluaW9uIGNsYXJpZmljYXRpb24gYmVmb3JlIHRoZSBkb2N1
bWVudCBpcyBhcHByb3ZlZC4NCg0KVGhhbmsgeW91IGZvciB0aGlzIHN1bW1hcnkg4oCUIHlvdSBy
YWlzZSBnb29kIHBvaW50cy4NCg0KPiANCj4gTWFqb3IgaXNzdWVzOg0KPiANCj4gMS4gU2VjdGlv
biAxMS4xIGNsYWltczogJ0FuIElFRUUgRXRoZXJUeXBlLCAweDg5NEYsIGhhcyBiZWVuIGFsbG9j
YXRlZCBmb3INCj4gTlNIJy4gSSBjb3VsZCBub3QgZmluZCB0aGlzIHZhbHVlIGluIHRoZSB0YWJs
ZXMgZGlzcGxheWVkIGJ5IHRoZSBJRUVFDQo+IFJlZ2lzdHJhdGlvbiBBdXRob3JpdHkgKFJBQykg
LSBmb3IgZXhhbXBsZSBhdA0KPiBodHRwOi8vc3RhbmRhcmRzLW91aS5pZWVlLm9yZy9ldGhlcnR5
cGUvZXRoLnR4dC4gTmVpdGhlciBkb2VzIElBTkEgYXQNCj4gaHR0cHM6Ly93d3cuaWFuYS5vcmcv
YXNzaWdubWVudHMvaWVlZS04MDItbnVtYmVycy9pZWVlLTgwMi1udW1iZXJzLnhodG1sICh3aGlj
aA0KPiB3b3VsZCBub3QgYmUgaW4gYW55IGNhc2UgdGhlIGF1dGhvcml0YXRpdmUgc291cmNlKS4g
Q2FuIHlvdSBwbGVhc2UgaW5kaWNhdGUgdGhlDQo+IHNvdXJjZSB0aGF0IHRoaXMgaXMgaW5kZWVk
IGEgY29uZmlybWVkIElFRUUgRXRoZXJUeXBlIHJlZ2lzdHJhdGlvbi4NCg0KSSBhbSBub3Qgc3Vy
ZSBob3cgb2Z0ZW4gdGhhdCBwYWdlIGlzIHVwZGF0ZWQsIGJ1dCB0aGUgc2FtZSBsaW5rIHlvdSBp
bmNsdWRlLCBodHRwOi8vc3RhbmRhcmRzLW91aS5pZWVlLm9yZy9ldGhlcnR5cGUvZXRoLnR4dCwg
c2hvd3M6DQoNCjB4ODk0Rg0KODk0RjogTlNIIChOZXR3b3JrIFNlcnZpY2UgSGVhZGVyKS4gUmVm
ZXJlbmNlOiBkcmFmdC1pZXRmLXNmYy1uc2gtMTgNCg0KR3JhbnRlZCwgdGhhdCByZWdpc3RyYXRp
b24gd2lsbCBiZSB1cGRhdGVkIHdpdGggdGhlIFJGQyBudW1iZXIgaW5zdGVhZCBvZiB0aGUgSS1E
LCB3aGVuIGl0IHB1Ymxpc2hlcy4NCg0KPiANCj4gMi4gU2VjdGlvbiA1IHJlZmVycyB0byBpZXRm
LXJ0Z3dnLWR0LWVuY2FwIHdoaWNoIGlzIGV4cGlyZWQuIElmIEkgdW5kZXJzdGFuZA0KPiBjb3Jy
ZWN0bHkgdGhlIHN0YXR1cyBvZiB0aGlzIHdvcmssIHRoZXJlIGlzIGEgZGVzaWduIHRlYW0gaW4g
cGxhY2UgaW4gdGhlDQo+IFJvdXRpbmcgQXJlYSBjcmVhdGVkIHRvIGxvb2sgYXQgY29tbW9uIGlz
c3VlcyBmb3IgdGhlIGRpZmZlcmVudCBkYXRhIHBsYW5lDQo+IGVuY2Fwc3VsYXRpb25zIGJlaW5n
IGRpc2N1c3NlZCBpbiB2YXJpb3VzIFdHcyBpbmNsdWRpbmcgU0ZDLiBUaGlzIGxlYXZlcyB0aGUN
Cj4gaXNzdWUgdW5zZXR0bGVkIGF0IHRoaXMgc3RhZ2UgYW5kIHRoaXMgbWF5IGJlIGEgcHJvYmxl
bSBmb3IgYSBzdGFuZGFyZHMgdHJhY2sNCj4gZG9jdW1lbnQuIEkgc3VnZ2VzdCB0aGF0IGZpcnN0
IHRoZSByZWZlcmVuY2UgdG8gdGhlIGV4cGlyZWQgZG9jdW1lbnQgaXMNCj4gcmVtb3ZlZCwgc2Vj
b25kIHRoYXQgdGhlIGlzc3VlIGlzIG1hcmtlZCBhcyAnb3BlbicgYW5kIHN1YmplY3QgZm9yIGZ1
dHVyZSB3b3JrLg0KPiANCg0KR29vZCBzdWdnZXN0aW9uLiBJbnN0ZWFkIG9mIHJlbW92aW5nIHRo
ZSByZWZlcmVuY2UgYWxsIHRvZ2V0aGVyLCB3ZSBjYW4gbWFyayBpdCBhcyBleGVtcGxpZnlpbmcg
b2Ygb25lIGFwcHJvYWNoLg0KDQo+IE1pbm9yIGlzc3VlczoNCj4gDQo+IDEuICBUd28gdmFsdWVz
ICdFeHBlcmltZW50IDEnIGFuZCAnRXhwZXJpbWVudCAyJyBhcmUgZGVmaW5lZCBpbiBzZWN0aW9u
IDIuMiBhbmQNCj4gMTEuMi41IGZvciB0aGUgTmV4dCBQcm90b2NvbC4gVGhpcyBzZWVtcyBhIGxp
dHRsZSBvZGQuIFdoeSAyPyBXaHkgYXJlIHRoZXkNCj4gZGVmaW5lZCBhdCB0aGUgZW5kIG9mIHRo
ZSByYW5nZT8gTWF5YmUgdGhlcmUgaXMgYW4gZXhwbGFuYXRpb24gZm9yIHRob3NlIHdobw0KPiBr
bm93IHRoZSBoaXN0b3J5IGJ1dCBmb3IgYW4gdW4taW5pdGlhdGVkIHJlYWRlciBvciBhIGZ1dHVy
ZSBpbXBsZW1lbnRlciB0aGlzDQo+IHNlZW1zIG9kZC4NCg0KVGhlcmUgaXMgbm8gc3Ryb25nIHJh
dGlvbmFsIGJlaGluZCB0aGUgbnVtYmVyIG9mIHZhbHVlcyAodHdvKSBvciB0aGUgbG9jYXRpb24g
KHRvd2FyZHMgdGhlIGVuZCBvZiB0aGUgcmFuZ2UpLiBUaGVyZSBhcmUgdHdvIHZhbHVlcyBhcyBp
dCBzZWVtcyBhcHByb3ByaWF0ZSBnaXZlbiB0aGUgc2FtZSBvZiB0aGUgbnVtYmVyIHNwYWNlICgy
IG91dCBvZiAyNTYpLg0KDQpQZXJoYXBzLCBpdOKAmXMgc29tZXdoYXQgZm9sbG93aW5nIGNvbW1v
biBwcmFjdGljZSBzdGFydGVkIGF0IGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmMzNjky
I3NlY3Rpb24tMi4xICgyIHZhbHVlcyBmb3IgYW5kIDgtYml0IGZpZWxkLCBjbG9zZXIgdG8gdGhl
IGVuZCkuDQoNCj4gDQo+IDIuIEluIFNlY3Rpb24gMi4yIEkgc2VlOg0KPiANCj4+IEFsbCBvdGhl
ciBmbGFnIGZpZWxkcywgbWFya2VkIFUsIGFyZSB1bmFzc2lnbmVkIGFuZCBhdmFpbGFibGUgZm9y
DQo+ICAgZnV0dXJlIHVzZSwgc2VlIFNlY3Rpb24gMTEuMi4xLiAgVW5hc3NpZ25lZCBiaXRzIE1V
U1QgYmUgc2V0IHRvIHplcm8NCj4gICB1cG9uIG9yaWdpbmF0aW9uLCBhbmQgTVVTVCBiZSBpZ25v
cmVkIGFuZCBwcmVzZXJ2ZWQgdW5tb2RpZmllZCBieQ0KPiAgIG90aGVyIE5TSCBzdXBwb3J0aW5n
IGVsZW1lbnRzLiAgRWxlbWVudHMgd2hpY2ggZG8gbm90IHVuZGVyc3RhbmQgdGhlDQo+ICAgbWVh
bmluZyBvZiBhbnkgb2YgdGhlc2UgYml0cyBNVVNUIE5PVCBtb2RpZnkgdGhlaXIgYWN0aW9ucyBi
YXNlZCBvbg0KPiAgIHRob3NlIHVua25vd24gYml0cy4NCj4gDQo+IFRoZSB3YXkgdGhlIGxhc3Qg
c2VudGVuY2UgaXMgd3JpdHRlbiBpdCBzZWVtcyB0byBvcGVuIHRoZSBwYXRoIGZvciBlbGVtZW50
cw0KPiB0aGF0IGNsYWltIHRvICd1bmRlcnN0YW5kJyB0aGUgbWVhbmluZyBvZiBzb21lIFVuYXNz
aWduZWQgYml0IHRvIG1vZGlmeSBpdHMNCj4gYmVoYXZpb3IgYmFzZWQgdXBvbiBpdC4gVGhpcyBk
b2VzIG5vdCBzZWVtIGdvb2QsIGFzIGF0IHRyYW5zbWlzc2lvbiBhbGwNCj4gVW5hc3NpZ25lZCBi
aXRzIE1VU1QgYmUgc2V0IHRvIHplcm8uIEkgd291bGQgc3VnZ2VzdCB0byBtYWtlIHRoZSBzdGF0
ZW1lbnQNCj4gc2ltcGxlciBhbmQganVzdCBzYXkgdGhhdCBhdCByZWNlcHRpb24gYWxsIGVsZW1l
bnRzIE1VU1QgTk9UIG1vZGlmeSB0aGVpcg0KPiBhY3Rpb25zIGJhc2VkIG9uIHRoZXNlIGJpdHMu
DQo+IA0KDQpWZXJ5IGdvb2QgcG9pbnQsIGFuZCBnb29kIGltcHJvdmVtZW50LiBBcHBsaWVkLg0K
DQo+IDMuIEluIFNlY3Rpb24gMi4yIEkgc2VlOg0KPiANCj4+IDB4RiAtIFRoaXMgdmFsdWUgaXMg
cmVzZXJ2ZWQgZm9yIGV4cGVyaW1lbnRhdGlvbiBhbmQgdGVzdGluZywgYXMgcGVyDQo+ICAgW1JG
QzM2OTJdLiAgSW1wbGVtZW50YXRpb25zIG5vdCBleHBsaWNpdGx5IGNvbmZpZ3VyZWQgdG8gYmUg
cGFydCBvZg0KPiAgIGFuIGV4cGVyaW1lbnQgU0hPVUxEIHNpbGVudGx5IGRpc2NhcmQgcGFja2V0
cyB3aXRoIE1EIFR5cGUgMHhGLg0KPiANCj4gV2h5IGlzIHRoaXMgYSBTSE9VTEQgYW5kIG5vdCBh
IE1VU1Q/DQo+IA0KDQpUbyB1c2UgTVVTVHMgdmVyeSBzcGFyaW5nbHkgYW5kIGxlYXZlIGEgbGl0
dGxlIGJpdCBvZiBsZWV3YXkgZm9yIGV4cGVyaW1lbnRhdGlvbiwgZm9sbG93aW5nIGFwcHJvcHJp
YXRlIGp1c3RpZmljYXRpb24uDQoNCj4gNC4gSSBiZWxpZXZlIHRoYXQgIFtJLUQuaWV0Zi1zZmMt
Y29udHJvbC1wbGFuZV0gbmVlZHMgdG8gYmUgYSBOb3JtYXRpdmUNCj4gUmVmZXJlbmNlLiBUaGVy
ZSBhcmUgc2V2ZXJhbCBwbGFjZXMgaW4gdGhlIGRvY3VtZW50IChlLmcuIGluIFNlY3Rpb24gMi4z
KSB3aGVyZQ0KPiB0aGlzIGRvY3VtZW50IGlzIHJlZmVycmVkIHRvIGRlc2NyaWJlIGJlaGF2aW9y
IG9yIGFjdGlvbnMgcmVsYXRlZCB0byB0aGUgZmllbGRzDQo+IG9mIHRoZSBoZWFkZXIuDQo+IA0K
DQpUaGUgY29udHJvbCBwbGFuZSBJLUQgaXMsIGJ5IFdHIGRlY2lzaW9uLCBpbnRlbmRlZCB0byBu
b3QgYmUgbm9ybWF0aXZlIGFzIE5TSCBpcyB0aGUgZGF0YSBwbGFuZSBpbmRlcGVuZGVudCBvZiB0
aGUgQ1Agc3BlYy4NCg0KSSBzZWUgdGhhdCBbSS1ELmlldGYtc2ZjLWNvbnRyb2wtcGxhbmVdIGlz
IGNpdGVkIGluIHR3byBwbGFjZXM6DQoNCjEuDQogICAgICAgW0ktRC5pZXRmLXNmYy1jb250cm9s
LXBsYW5lXSBwcm92aWRlcyBhbiBleGFtcGxlIG9mIHN1Y2ggaW4NCg0KMi4NCiAgIHByb2Nlc3Mu
ICBUaGVzZSBjb25zaWRlcmF0aW9ucyBhcmUgZGVwbG95bWVudC1zcGVjaWZpYy4gIEhvd2V2ZXIs
IHRoZQ0KICAgY29udHJvbCBwbGFuZSBpcyBlbnRpdGxlZCB0byBpbnN0cnVjdCBTRkMtYXdhcmUg
U0ZzIHdpdGggdGhlIGRhdGENCiAgIHN0cnVjdHVyZSBvZiBjb250ZXh0IGhlYWRlciB0b2dldGhl
ciB3aXRoIGl0cyBzY29waW5nIChzZWUNCiAgIFNlY3Rpb24gMy4zLjMgb2YgW0ktRC5pZXRmLXNm
Yy1jb250cm9sLXBsYW5lXSkuDQoNCg0KV2UgYWxyZWFkeSBjYXVnaHQgdGhlIGlzc3VlIHdpdGgg
IzIgYW5kIGNoYW5nZWQgaXQgdG8sIGluIG91ciB3b3JraW5nIGNvcHkgd29ya2luZyB3aXRoIHRo
ZSBjaGFpcnMsIHRvOg0KDQogICBwcm9jZXNzLiAgVGhlc2UgY29uc2lkZXJhdGlvbnMgYXJlIGRl
cGxveW1lbnQtc3BlY2lmaWMuICBIb3dldmVyLCB0aGUNCiAgIGNvbnRyb2wgcGxhbmUgaXMgZW50
aXRsZWQgdG8gaW5zdHJ1Y3QgU0ZDLWF3YXJlIFNGcyB3aXRoIHRoZSBkYXRhDQogICBzdHJ1Y3R1
cmUgb2YgY29udGV4dCBoZWFkZXIgdG9nZXRoZXIgd2l0aCBpdHMgc2NvcGluZyAoc2VlIGUuZy4s
DQogICBTZWN0aW9uIDMuMy4zIG9mIFtJLUQuaWV0Zi1zZmMtY29udHJvbC1wbGFuZV0pLg0KDQpB
cyB0aGF04oCZcyBvbmUgcG9zc2libGUsIGFuZCBub24tbm9ybWF0aXZlIHdheSwgb3V0IG9mIG1h
bnkgd2F5cy4NCg0KPiA1LiBUaGUgdmVyc2lvbiBudW1iZXIgaGFzIG9ubHkgdHdvIGJpdHMgYXNz
aWduZWQuIE1vcmVvdmVyLCB0aGlzIGRvY3VtZW50DQo+IHJlc2VydmVzIGFscmVhZHkgdHdvIHZh
bHVlcyB3aXRob3V0IGFueSBleHBsYW5hdGlvbiB3aHkgKG9ubHkgMDAgaXMgbWFuZGF0b3J5DQo+
IHRvIHVzZSwgYXMgZmFyIGFzIEkgdW5kZXJzdGFuZCkuIFRoaXMgbmVlZHMgdG8gYmUgZXhwbGFp
bmVkIChtYXliZSAnaGlzdG9yaWNhbCcNCj4gcmVhc29ucyAtIGJ1dCB1bmNsZWFyIGZvciBmdXR1
cmUgcmVhZGVycyBhbmQgdXNlcnMpIGFuZCBtYXkgYmUgYSBsaW1pdGF0aW9uIGFzDQo+IHRoZSBw
cm90b2NvbCBkZXZlbG9wcy4NCg0KVGhlIHZlcnNpb24gZmllbGQgaXMgaW5kZWVkIGEgdHdvLWJp
dCBmaWVsZC4gT25lIHJlc2VydmVkIGFuZCB3aWxsIG5vdCBiZSB1c2VkLiBPbmUgdXNlZCBieSB0
aGlzIHNwZWMsIGFuZCB0d28gdW5hc3NpZ25lZCBvbmVzLiANCg0KV2UgcmVhbGx5IGV4cGVjdCB0
byBub3QgYmUgYnVtcGluZyB1cCB2ZXJzaW9uIG51bWJlciBvZnRlciDigJQgb3IgZXZlcuKApg0K
DQo+IA0KPiBOaXRzL2VkaXRvcmlhbCBjb21tZW50czoNCj4gDQo+IDEuIFBsZWFzZSBtYWtlIHN1
cmUgdGhhdCBhY3JvbnltcyBhcmUgZXhwYW5kZWQgYXQgZmlyc3Qgb2NjdXJyZW5jZSAoZS5nLiBF
Q01QKQ0KPiBhbmQgaWYgbmVjZXNzYXJ5IGFwcHJvcHJpYXRlIHJlZmVyZW5jZXMgYXJlIGJlaW5n
IHByb3ZpZGVkLg0KPiANCg0KQWNrIOKAlCBkb25lLg0KDQpUaGFua3MgYWdhaW4hDQoNCkNhcmxv
cy4NCg0KPiANCg0K


From nobody Thu Aug 31 20:31:23 2017
Return-Path: <cpignata@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B490A13311D; Thu, 31 Aug 2017 20:31:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level: 
X-Spam-Status: No, score=-14.521 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZNkZNlhXI3Y8; Thu, 31 Aug 2017 20:31:18 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4F181330FE; Thu, 31 Aug 2017 20:31:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=35786; q=dns/txt; s=iport; t=1504236677; x=1505446277; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=NQKyHh8LlPRXAwFfvPJ9+eliQEdu7DoJnflygYhtyfc=; b=Mlddew71NmMpB0kBzGXrVcqePREfSAZsJMtdp3/vzolQuCmNTWdzHK98 xZ3scXOX+V5C6BJZ6NPVxz1YBGbFbUAD2DL1m8uwNFw7f6Mk8rFc7vxXZ Pm/TBcyBAHiDgfo6I4tcFNt+Hb9hpJRyEnxfUTe83gOYFaZ9VQy/1u1cf s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C/AAAH1KhZ/4sNJK1TChkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYNaZIEVB44QkB+BTyJ3lTAOggQshRsCGoN1PxgBAgEBAQEBAQF?= =?us-ascii?q?rKIUYAQEBAQIBDgwJBA0xAgcLBQsCAQgSBgICJgICAjAVAg4CBA4FiikIEK8og?= =?us-ascii?q?W06i2MBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYENgh2BYiCBToFjKwuBZVg1hEo?= =?us-ascii?q?FDoMrMIIxBYl1jjyIPgKHWYNaiRyCE4Vng32Gd4ocjCgBHziBDXcVWwGFAgMcG?= =?us-ascii?q?YFOdogegTGBDwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.41,456,1498521600"; d="scan'208";a="279625934"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Sep 2017 03:31:13 +0000
Received: from XCH-RTP-016.cisco.com (xch-rtp-016.cisco.com [64.101.220.156]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id v813VCmK024240 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 1 Sep 2017 03:31:13 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-016.cisco.com (64.101.220.156) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 31 Aug 2017 23:31:11 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1263.000; Thu, 31 Aug 2017 23:31:11 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Warren Kumari <warren@kumari.net>
CC: IETF Discuss <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>, "draft-ietf-sfc-nsh@ietf.org" <draft-ietf-sfc-nsh@ietf.org>, "Joel M. Halpern" <jmh@joelhalpern.com>, "sfc-chairs@ietf.org" <sfc-chairs@ietf.org>, Service Function Chaining IETF list <sfc@ietf.org>, Alia Atlas <akatlas@gmail.com>, Jim Guichard <james.n.guichard@huawei.com>
Subject: Re: Last Call: <draft-ietf-sfc-nsh-18.txt> (Network Service Header (NSH)) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-sfc-nsh-18.txt> (Network Service Header (NSH)) to Proposed Standard
Thread-Index: AQHTEvZcFCn6REBjS0aBK4QSCafTu6KLJ8CAgBSa4wA=
Date: Fri, 1 Sep 2017 03:31:11 +0000
Message-ID: <2F5DB4AD-3672-43DE-B420-510B85440106@cisco.com>
References: <150249274009.24438.5552125434164888108.idtracker@ietfa.amsl.com> <CAHw9_iJWhJxJGngi6yv2Di3XsF-cMZv-mxKV=NNGruEDJcM+eg@mail.gmail.com>
In-Reply-To: <CAHw9_iJWhJxJGngi6yv2Di3XsF-cMZv-mxKV=NNGruEDJcM+eg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.116.133]
Content-Type: text/plain; charset="utf-8"
Content-ID: <7E73222A2B79E445883C482A66282F34@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kaqipSawxt-sjs7_rE2_vtpHtng>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Sep 2017 03:31:22 -0000

V2FycmVuLA0KDQpNYW55IHRoYW5rcyBmb3IgdGFraW5nIHRoZSB0aW1lIHRvIHJldmlldyB0aGlz
IGRvY3VtZW50ISBBbmQgYXBvbG9naWVzIGZvciB0aGUgZGVsYXllZC1hY2suDQoNCklmIHJlYWRp
bmcgcGFydHMgb2YgdGhpcyBkb2N1bWVudCwgYW5kIOKAnG9ubHkgc2tpbW1pbmcgc2VjdGlvbnMg
Ni4xIC0gU2VjdGlvbiA44oCdIGxlZnQgeW91IHNvIGNvbmZ1c2VkLCBiZXdpbGRlcmVkIGFuZCBk
aXp6eSwgdGhlcmUgaXMgbm90aGluZyB3ZSBjYW4gc3RhcnQgd2l0aCBvdGhlciB0aGFuIGFja25v
d2xlZGdpbmcgdGhhdCB0aGVyZSBpcyBhbiBpc3N1ZSB0aGF0IHdlIHdpbGwgY29ycmVjdC4gSXQg
aXMgYW4gaW5hZGVxdWF0ZSBvdXRjb21lLCBhbmQgd2Ugd2lsbCByZWN0aWZ5IGl0LiBNdWNoIG9m
IGl0IHNlZW1zIHRvIGVpdGhlciBiZSB0cmFja2VkIHRvIGxvY2FsaXplZCBzb3VyY2VzLCBvciBo
YXMgcHJvcG9zZWQgcmVzb2x1dGlvbnMgaW4gdGhpcyByZXNwb25zZS4NCg0KQmVmb3JlIGRpdmlu
ZyBpbnRvIGlubGluZWQgaXNzdWUtYnktaXNzdWUgY29tbWVudHMsIHRoZXJl4oCZcyBhIGZldyBo
aWdoLWxldmVsIG9ic2VydmF0aW9ucyBJ4oCZZCBsaWtlIHRvIG1ha2UgaW4gcmVzcG9uc2UgdG8g
eW91ciByZXZpZXc6DQoNCjEuIFNldmVyYWwgb3RoZXIgcmV2aWV3ZXJzLCBpbmNsdWRpbmcgT3Bz
IERpciwgUlRHIERpciwgYW5kIEdlbkFSVCwgbWFuYWdlZCB0byByZWFkIGFuZCB1bmRlcnN0YW5k
IHRoZSBkb2N1bWVudCwgcHJvdmlkZSBjb25zdHJ1Y3RpdmUgY29tbWVudHMsIGFuZCBzdXJ2aXZl
IHRoZSBleHBlcmllbmNlIHVuaGFybWVkIDotKSBKdXN0IHRvIGJlIGNsZWFyLCB0aGF0IGRvZXMg
bm90IG1lYW4gdGhhdCB0aGUgZG9jdW1lbnQgaXMgYXMgY2xlYXIgYXMgaXQgb3VnaHQgdG8gYmUs
IG9yIG90aGVyd2lzZSBuZWdhdGVzIHlvdXIgY29uZnVzaW9uLiBXZSB3aWxsIGltcHJvdmUgaXQg
YW5kIGZpeCBpdC4NCg0KMi4gWW91ciBzdWdnZXN0aW9uIG9mICJhIGNsZWFyIG1vZGVsIGF0IHRo
ZSBiZWdpbm5pbmcgb2YgdGhlIGRvY3VtZW504oCdIGlzIHNwb3Qgb24uIFdlIHdpbGwgYWRkIGJv
dGggYSBtb2RlbCBhbmQgc29tZSBwcm9zZSBlYXJseSBvbi4gSW4gZmFjdCwgSmltIEd1aWNoYXJk
IHN1Z2dlc3RlZCBhbiBvdXRsaW5lIGFuZCB2b2x1bnRlZXJlZCB0byBjcmFmdCBhIGJpdCBvZiB0
aGF0IHRleHQuIA0KDQpFYXJsaWVyIHZlcnNpb24gb2YgdGhpcyBkb2N1bWVudCBpbmNsdWRlZCBh
IG51bWJlciBvZiBleGFtcGxlcyB0aGF0LCBpbiBvdXIgdmlldywgd291bGQgaGF2ZSBjbGFyaWZp
ZWQgbXVjaCBjb25mdXNpb24uIFNlZSBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQt
aWV0Zi1zZmMtbnNoLTA1I3NlY3Rpb24tOS4gU2V2ZXJhbCBmb2xrcywgaW5jbHVkaW5nIHRoZSBy
ZXNwb25zaWJsZSBBRCwgb2JqZWN0ZWQgdG8gdGhhdCBzZWN0aW9uIChvbiBncm91bmRzIG9mIHRo
ZSBpbmFiaWxpdHkgb2YgYW4gZXhhbXBsZSBzZWN0aW9uIHRvIGluY2x1ZGUgZXZlcnlvbmXigJlz
IGZhdm9yaXRlIGVuY2Fwc3VsYXRpb24pLiBUaGVyZSBpcyBzb21lIHRydXRoIHRvIHRoYXQuIA0K
DQpUaGF0IHNhaWQsIGRvIHlvdSBiZWxpZXZlIHRoYXQgc3VjaCBleGFtcGxlIHNlY3Rpb24gbWln
aHQgaGF2ZSBoZWxwZWQgeW91PyAoVGhpcyBpcywgaW4gYWRkaXRpb24gdG8gc29tZSBlYXJseS1v
biBjbGFyaWZpY2F0aW9ucykuDQoNCjMuIEl0IGlzIG91dHNpZGUgdGhlIHNjb3BlIG9mIHRoaXMg
ZG9jdW1lbnQgdG8gcGFydGFrZSBpbnRvIHJlbGlnaW91cyBkZWJhdGVzIG9mIHRoZSBtZWFuaW5n
IG9mIGVuY2Fwc3VsYXRpb24gdmVyc3VzIHR1bm5lbGluZyB2ZXJzdXMgc2hpbW1pbmcuDQoNCklu
IGZhY3QsIHRoaXMgZG9jdW1lbnQgZG9lcyBub3QgaW5jbHVkZSB0aGUgd29yZCDigJxzaGlt4oCd
LCB3aGF0c29ldmVyLiBZb3Ugc2VlbSB0byBoYXZlIHRha2VuIGludGVsbGVjdHVhbCBvZmZlbnNl
IHRvIHRoZSBjb21iaW5hdGlvbiDigJxpbnNlcnRlZCBvbnRv4oCdLiBBbmQgc3Vic2VxdWVudGx5
IHlvdSBzYXk6ICcqaW5zZXJ0ZWQgb250byogc291bmRzIGxpa2UgYSBzaGlt4oCZLCBhbmQgdGhl
biBidWlsZCBhIHJlYnV0dGFsIG9mIHRoZSB1c2Ugb2YgdGhlIHdvcmQg4oCYc2hpbeKAmSA6LSkg
SSBiZWxpZXZlIHBhcnQgb2YgdGhlIHByb2JsZW0gaXMgdGhhdCB5b3UgYXJlIHJldmlld2luZyDi
gJxzaGlt4oCdLi4uDQoNClNvLCBtb3ZpbmcgZm9yd2FyZCwgd2Ugd2lsbCBkbyBhIGNvdXBsZSBv
ZiB0aGluZ3M6DQoNCkZpcnN0LCBhZGQgYSBtb2RlbCBhbmQgc29tZSB0ZXh0LCBlYXJseSBvbiBh
dCB0aGUgYmVnaW5uaW5nIG9mIHRoZSBkb2N1bWVudC4gVGhpcyBpcyBuZWVkZWQgZm9yIGlzc3Vl
ICMxLg0KDQpTZWNvbmQsIHdhaXQgZm9yIHlvdXIgdGhvdWdodHMgYW5kIG90aGVyIGZvbGtz4oCZ
IGd1aWRhbmNlIG9uIHdoZXRoZXIgdG8gcmUtaW5jbHVkZSB0aGUgbm93IHJlbW92ZWQg4oCcRXhh
bXBsZXPigJ0gc2VjdGlvbi4gSXQgc2VlbXMgdG8gdXMgdGhhdCB0aGUgbG9vc2VuZXNzIGluIHNv
bWUgdGV4dCBpcyBncmVhdGx5IGFnZ3JhdmF0ZWQgYnkgdGhlIGxhY2sgb2YgcGFja2V0IGZvcm1h
dHMuIFRoaXMgaXMgYWxzbyByZWxldmFudCB0byBpc3N1ZSAjMS4NCg0KV291bGQgeW91IGFncmVl
Pw0KDQpUaGlyZCwgd2Ugd2lsbCBzaGFycGVuIHRoZSB0ZXh0IHRocm91Z2hvdXQgaW4gdGhlIHVz
ZSBvZiBlbmNhcC4NCg0KSXNzdWUgIzQgcmVtYWlucyB1bnJlc29sdmVkLCBhcyBJIHdvdWxkIGxp
a2UgdG8gY2hlY2sgYW5kIG5vdCBicmVhayB0aGUgYmFsYW5jZSBvZiB0ZXh0LiBJIHdpbGwgcHVu
dCB0aGlzIHRvIHRoZSBTaGVwaGVyZC4NCg0KSW4gc3VtbWFyeSwgd2Ugd2lsbCBjbGFyaWZ5IGlz
c3VlcyAjMSBhbmQgIzMgZm9yIE5TSCwgYW5kIHdvdWxkIGxpa2UgdG8gcmUtYWRkIHBhayBmb3Jt
YXRzLiBBbGwgb3RoZXIgaXNzdWVzIGhhdmUgcHJvcG9zZWQgcmVzb2x1dGlvbnMgaW5saW5lLiAN
Cg0KVGhhbmtzIGFnYWluIGZvciBwb2ludGluZyBhbGwgb2YgdGhlc2Ugb3V0Lg0KDQpQbGVhc2Ug
ZmluZCByZXNwb25zZXMgYW5kIGZvbGxvdy11cHMgaW5saW5lLg0KDQpXZSB3aWxsIGNvbWUgYmFj
ayB3aXRoIHByb3Bvc2VkIGRpZmZzIGZvciB0aGUgdHdvIHBlbmRpbmcgaXNzdWVzIGxhYmVsZWQg
4oCcbWFqb3LigJ0gKCMxIGFuZCAjNCkuDQoNCkFkZGl0aW9uYWxseSwgYWxsIE5pdHMgYXJlIGFk
ZHJlc3NlZCBpbiBvdXIgd29ya2luZyBjb3B5LiBNYW55IHRoYW5rcyBmb3IgdGFraW5nIHRoZSB0
aW1lIHRvIGlkZW50aWZ5IGFsbCB0aG9zZSBhbmQgcHJvcG9zZSBzdWdnZXN0aW9ucy4gU29tZSBv
ZiB0aGVtIGFyZSBmaXhlZCBkaWZmZXJlbnRseSB0aG91Z2ggKHdoZW4geW91IHdyb3RlIOKAnEFz
IFNGIG9yIFNGQyBQcm94eSAtPiBBIFNGIG9yIFNGQyBQcm94eeKAnSwgdGhhdCBpcyBhY3R1YWxs
eSDigJxBbiBTRuKAnSAoZ3JhbW1hcikuDQoNCkFzIGFuIGFzaWRlLCBhbmQgYXMgYSByZXZpZXcg
b2YgeW91ciByZXZpZXcsIHR3byBxdWljayBzdWdnZXN0aW9uczoNCg0KMS4gVGhlIHN0cmVhbS1v
Zi1jb3VuY2lvdXNuZXNzIG5hcnJhdGl2ZSB2ZXJ5IHBvb3JseSBzdWl0cyBhIHRlY2huaWNhbCBy
ZXZpZXcgb2YgYSBzcGVjLiBXaGlsZSBJIGFtIHN1cmUgYSBwbHVyYWxpdHkgb2YgdGhvdWdodHMg
aW50ZXJjb25uZWN0LCBzb21laG93LCBpdCBpcyB2ZXJ5IGhhcmQgdG8gZm9sbG93Lg0KDQoyLiBX
aGlsZSBJIGFtIHN1cmUgeW91IGtub3cgdGhlIGxlZ2VuZCBmb3Ig4oCcW09dIFtQXSBhbmQgW1Jd
4oCdLCB0aGUgZmlyc3QgdGhpbmcgdGhhdCBjYW1lIHRvIG1pbmQgdG8gbWUgd2FzIOKAnHdlbGws
IFtRXSBpcyBtaXNzaW5nIeKAnSA6LSkgSSBjYW4gZ3Vlc3MgT3JpZ2luYWwsIFByb3Bvc2VkLCBS
ZWFzb24vUmF0aW9uYWwgYWZ0ZXIgYSB3aGlsZSwgYnV0IHJlYWxseSwgaXQgZG9lcyBub3QgdW5p
dmVyc2FsbHkgdHJhbnNsYXRlLi4uDQoNCg0KPiBPbiBBdWcgMTgsIDIwMTcsIGF0IDg6NTEgUE0s
IFdhcnJlbiBLdW1hcmkgPHdhcnJlbkBrdW1hcmkubmV0PiB3cm90ZToNCj4gDQo+IE9uIEZyaSwg
QXVnIDExLCAyMDE3IGF0IDc6MDUgUE0sIFRoZSBJRVNHIDxpZXNnLXNlY3JldGFyeUBpZXRmLm9y
Zz4gd3JvdGU6DQo+PiANCj4+IFRoZSBJRVNHIGhhcyByZWNlaXZlZCBhIHJlcXVlc3QgZnJvbSB0
aGUgU2VydmljZSBGdW5jdGlvbiBDaGFpbmluZyBXRyAoc2ZjKQ0KPj4gdG8gY29uc2lkZXIgdGhl
IGZvbGxvd2luZyBkb2N1bWVudDogLSAnTmV0d29yayBTZXJ2aWNlIEhlYWRlciAoTlNIKScNCj4+
ICA8ZHJhZnQtaWV0Zi1zZmMtbnNoLTE4LnR4dD4gYXMgUHJvcG9zZWQgU3RhbmRhcmQNCj4+IA0K
Pj4gVGhlIElFU0cgcGxhbnMgdG8gbWFrZSBhIGRlY2lzaW9uIGluIHRoZSBuZXh0IGZldyB3ZWVr
cywgYW5kIHNvbGljaXRzIGZpbmFsDQo+PiBjb21tZW50cyBvbiB0aGlzIGFjdGlvbi4gUGxlYXNl
IHNlbmQgc3Vic3RhbnRpdmUgY29tbWVudHMgdG8gdGhlDQo+PiBpZXRmQGlldGYub3JnIG1haWxp
bmcgbGlzdHMgYnkgMjAxNy0wOC0yNS4gRXhjZXB0aW9uYWxseSwgY29tbWVudHMgbWF5IGJlDQo+
PiBzZW50IHRvIGllc2dAaWV0Zi5vcmcgaW5zdGVhZC4gSW4gZWl0aGVyIGNhc2UsIHBsZWFzZSBy
ZXRhaW4gdGhlIGJlZ2lubmluZyBvZg0KPj4gdGhlIFN1YmplY3QgbGluZSB0byBhbGxvdyBhdXRv
bWF0ZWQgc29ydGluZy4NCj4+IA0KPj4gQWJzdHJhY3QNCj4+IA0KPj4gDQo+PiAgIFRoaXMgZG9j
dW1lbnQgZGVzY3JpYmVzIGEgTmV0d29yayBTZXJ2aWNlIEhlYWRlciAoTlNIKSBpbnNlcnRlZCBv
bnRvDQo+PiAgIHBhY2tldHMgb3IgZnJhbWVzIHRvIHJlYWxpemUgc2VydmljZSBmdW5jdGlvbiBw
YXRocy4gIE5TSCBhbHNvDQo+PiAgIHByb3ZpZGVzIGEgbWVjaGFuaXNtIGZvciBtZXRhZGF0YSBl
eGNoYW5nZSBhbG9uZyB0aGUgaW5zdGFudGlhdGVkDQo+PiAgIHNlcnZpY2UgcGF0aHMuICBOU0gg
aXMgdGhlIFNGQyBlbmNhcHN1bGF0aW9uIHJlcXVpcmVkIHRvIHN1cHBvcnQgdGhlDQo+PiAgIFNl
cnZpY2UgRnVuY3Rpb24gQ2hhaW5pbmcgKFNGQykgYXJjaGl0ZWN0dXJlIChkZWZpbmVkIGluIFJG
Qzc2NjUpLg0KPj4gDQo+IA0KPiA8bm8gaGF0cz4NCj4gDQo+IEluIG15IG9waW5pb24gdGhpcyBk
b2N1bWVudCBzdGlsbCBuZWVkcyBzaWduaWZpY2FudCB3b3JrLiBDaHJpc3RpYW4ncw0KPiBncmVh
dCBTZWNEaXIgcmV2aWV3IGxpc3RzIG1hbnkgaXNzdWVzIHdoaWNoIG5lZWQgdG8gYmUgYWRkcmVz
c2VkOw0KPiBzaW5jZSBoZSBoYXMgYWxyZWFkeSByYWlzZWQgY29uY2VybnMsIEkgYW0gbm90IGZv
Y3VzaW5nIG9uIHRoZQ0KPiBzZWN1cml0eSBhbmQgcHJpdmFjeSBzdHVmZiBpbiBteSBidXQgcmV2
aWV3LiBJbnN0ZWFkLCBJJ2xsIGRpc2N1c3MNCj4gc29tZSBvZiB0aGUgb3RoZXIgaXNzdWVzLg0K
PiANCj4gSSBvbmx5IHNraW1tZWQgc2VjdGlvbnMgNi4xIC0gU2VjdGlvbiA4Lg0KPiANCj4gQXMg
dGhpcyBpcyBvdXRwdXQgb2YgdGhlIFNGQyBXRywgd2hpY2ggaXMgY2hhcnRlcmVkIHRvLCBhbW9u
Z3N0IG90aGVyDQo+IHRoaW5nLCBjcmVhdGUgYSAiR2VuZXJpYyBTRkMgRW5jYXBzdWxhdGlvbiIg
KHdpdGggc29tZSBtb3JlIGRldGFpbHMpDQo+IEknbGwgdGFrZSBpdCBhcyBnaXZlbiB0aGF0IHRo
aXMgaXMgZGVzaXJlZCAvIG5lZWRlZC4NCj4gDQo+IElzc3VlczoNCj4gDQo+IElzc3VlIDE6IEkg
ZmluZCB0aGUgZW50aXJlIGRvY3VtZW50IHRvIGJlIGNvbmZ1c2luZyBhYm91dCB3aGF0IGFuIE5T
SA0KPiBhY3R1YWxseSBpcywgYW5kIGFmdGVyIHNwZW5kaW5nIG11Y2ggdGltZSByZWFkaW5nLCBh
bSBzdGlsbCBmYWlybHkNCj4gY29uZnVzZWQuDQo+IEEgY2xlYXIgbW9kZWwgYXQgdGhlIGJlZ2lu
bmluZyBvZiB0aGUgZG9jdW1lbnQgd2hpY2ggZXhwbGFpbnMgaG93DQo+IHRoZXNlIGJpdHMgZml0
IHRvZ2V0aGVyIHdvdWxkIGJlIHZlcnkgaGVscGZ1bC4gSSBhbSBmYW1pbGlhciB3aXRoDQo+IFJG
Qzc2NjUgKHRoZSBhcmNoaXRlY3R1cmUgZG9jdW1lbnQpOyBteSBjb25mdXNpb24gc3RlbXMgZnJv
bSB0aGlzDQo+IGRyYWZ0Lg0KPiANCj4gRm9yIGV4YW1wbGUgdGhlIEFic3RyYWN0IHNheXM6DQo+
ICJUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBhIE5ldHdvcmsgU2VydmljZSBIZWFkZXIgKE5TSCkg
aW5zZXJ0ZWQgb250bw0KPiBwYWNrZXRzIG9yIGZyYW1lcyB0byByZWFsaXplIHNlcnZpY2UgZnVu
Y3Rpb24gcGF0aHMuIE5TSCBhbHNvIHByb3ZpZGVzDQo+IGEgbWVjaGFuaXNtIGZvciBtZXRhZGF0
YSBleGNoYW5nZSBhbG9uZyB0aGUgaW5zdGFudGlhdGVkIHNlcnZpY2UNCj4gcGF0aHMuICBOU0gg
aXMgdGhlIFNGQyBlbmNhcHN1bGF0aW9uIHJlcXVpcmVkIHRvIHN1cHBvcnQgdGhlIFNlcnZpY2UN
Cj4gRnVuY3Rpb24gQ2hhaW5pbmcgKFNGQykgYXJjaGl0ZWN0dXJlICIuDQo+IA0KPiBPaCwgb2ss
IHNvIGl0IGlzIHNvbWV0aGluZyBpbnNlcnRlZCBvbnRvIHBhY2tldHMgb3IgZnJhbWVzLi4uDQo+
ICppbnNlcnRlZCBvbnRvKiBzb3VuZHMgbGlrZSBhIHNoaW0sIGhvd2V2ZXIsICAiTlNIIGlzIHRo
ZSBTRkMNCj4gZW5jYXBzdWxhdGlvbi4uLiIuICBpbmRpY2F0ZXMgdGhhdCBJIGhhZCB0aGUgd3Jv
bmcgbWVudGFsIG1vZGVsIGFuZA0KPiB0aGlzIGlzIGFjdHVhbGx5IGFuIGVuY2Fwc3VsYXRpb24s
IGtpbmRhIGxpa2UgR1JFLiAoVGhpcyBpcyByZWluZm9yY2VkDQo+IHdpdGggKGVuZCBvZiBTZWN0
aW9uIDEpICJOU0ggaXMgdGhlIFNGQyBlbmNhcHN1bGF0aW9uIHJlZmVyZW5jZWQgaW4NCj4gW1JG
Qzc2NjVdLiIpIE9rLCBzbyB0aGlzIGVuY2Fwc3VsYXRlcyB0aGUgcGFja2V0LCBnb3QgaXQuLi4N
Cj4gSSByZWFkIHNvbWUgbW9yZSwgYW5kIHRoZW4gZmluZCAoaW4gc2VjdGlvbiAyKSB0aGF0ICJB
biBvdXRlcg0KPiB0cmFuc3BvcnQgaGVhZGVyIGlzIGltcG9zZWQsIG9uIE5TSCBhbmQgdGhlIG9y
aWdpbmFsIHBhY2tldC9mcmFtZSwgZm9yDQo+IG5ldHdvcmsgZm9yd2FyZGluZy4iLiBPaCwgc28g
dGhpcyBpcyAqYWN0dWFsbHkqIGEgc2hpbSAvIGhlYWRlciB3aGljaA0KPiBnb2VzIGJlZm9yZSB0
aGUgcGFja2V0LCBhbmQgdGhlbiB0aGUgd2hvbGUgdGhpbmcgZ2V0cyBlbmNhcHN1bGF0ZWQ/IEl0
DQo+IHNob3VsZG4ndCBoYXZlIGJlZW4gdGhpcyBoYXJkIHRvIGZpZ3VyZSBvdXQsIGJ1dCBPaywg
bm93IEkgZ2V0IGl0Li4uT3INCj4gZG8gST8gT2gsIGhhbmcgb24sIHdoYXQgdHJhbnNwb3J0IGhl
YWRlciBkbyBJIHVzZT8hDQo+IEl0IGlzIG9ubHkgbXVjaCBtdWNoIGxhdGVyLCBpbiBTZWN0aW9u
IDQgKHBhZ2UgMTUpIHRoYXQgSSBmaW5kICJPbmNlDQo+IE5TSCBpcyBhZGRlZCB0byBhIHBhY2tl
dCwgYW4gb3V0ZXIgZW5jYXBzdWxhdGlvbiBpcyB1c2VkIHRvIGZvcndhcmQNCj4gdGhlIG9yaWdp
bmFsIHBhY2tldCBhbmQgdGhlIGFzc29jaWF0ZWQgbWV0YWRhdGEgdG8gdGhlIHN0YXJ0IG9mIGEN
Cj4gc2VydmljZSBjaGFpbi4gLi4uIFRoZSBzZXJ2aWNlIGhlYWRlciBpcyBpbmRlcGVuZGVudCBv
ZiB0aGUNCj4gZW5jYXBzdWxhdGlvbiB1c2VkIGFuZCBpcyBlbmNhcHN1bGF0ZWQgaW4gZXhpc3Rp
bmcgdHJhbnNwb3J0cy4gIFRoZQ0KPiBwcmVzZW5jZSBvZiBOU0ggaXMgaW5kaWNhdGVkIHZpYSBw
cm90b2NvbCB0eXBlIG9yIG90aGVyIGluZGljYXRvciBpbg0KPiB0aGUgb3V0ZXIgZW5jYXBzdWxh
dGlvbi4iIC0gSSdtIG5vdyByZWFsbHkgY29uZnVzZWQgLSBmaXJzdCBJIHRob3VnaHQNCj4gaXQg
d2FzIGEgc2hpbSAvIGhlYWRlciwgdGhlbiBJIHRob3VnaHQgaXQgd2FzIGFuIGVuY2Fwc3VsYXRp
b24sIG5vdyBJDQo+IChmaW5hbGx5KSBzZWUgdGhhdCBpdCBpcyBhIGhlYWRlciB3aGljaCBnb2Vz
IGJlZm9yZSB0aGUgcGFja2V0DQo+IChlbmNhcHN1bGF0aW5nIGl0KSBiZWZvcmUgaXQgZ2V0cyBl
bmNhcHN1bGF0ZWQgYWdhaW4gaW50byBzb21ldGhpbmcNCj4gZWxzZS4gSXQgd291bGQgYmUgbXVj
aCBiZXR0ZXIgaWYgdGhlIGRvY3VtZW50IHdhcyBjbGVhcmVyIGF0IHRoZQ0KPiBiZWdpbm5pbmcg
YWJvdXQgaG93IGFsbCB0aGlzIGZpdHMgdG9nZXRoZXIgLyB3aGF0IHRoZSBOU0ggYWN0dWFsbHkN
Cj4gKmlzKiAtLSBhbiBhbmFsb2d5IHRvIGxheWVyaW5nLCBvciBhcyBhIHNoaW0gd2hpY2ggZ29l
cyBiZXR3ZWVuIGENCj4gdHVubmVsaW5nIGhlYWRlciBhbmQgdGhlIG9yaWdpbmFsIHBhY2tldCB3
b3VsZCBtYWtlIHRoaXMgbXVjaCBjbGVhcmVyDQo+IChhbmQgdGhlIHJlYWRlciBtdWNoIGxlc3Mg
YW5ub3llZCEpLg0KDQrigJxpbnNlcnRlZCBvbnRv4oCdIHN1YnN0aXR1dGVkIHdpdGgg4oCcaW1w
b3NlZCBvbuKAnSA6LSkNCg0KQXMgbWVudGlvbmVkLCB3ZSB3aWxsIGFsc28gYWRkIGNsYXJpZnlp
bmcgdGV4dCB0byB0aGUgaW50cm8uDQoNCj4gDQo+IElzc3VlIDI6IFNlY3Rpb24gMS4yLiAgRGVm
aW5pdGlvbiBvZiBUZXJtcw0KPiAiTWV0YWRhdGE6ICBEZWZpbmVkIGluIFtSRkM3NjY1XS4iIC0g
VGhlIGRlZmluaXRpb24gb2YgbWV0YWRhdGEgaW4NCj4gUkZDNzY2NSBzYXlzOiAiTWV0YWRhdGE6
IFByb3ZpZGVzIHRoZSBhYmlsaXR5IHRvIGV4Y2hhbmdlIGNvbnRleHQNCj4gaW5mb3JtYXRpb24g
YmV0d2VlbiBjbGFzc2lmaWVycyBhbmQgU0ZzLCBhbmQgYW1vbmcgU0ZzLiIuIFRoaXMgaXMgbm90
DQo+IGFuIGFkZXF1YXRlIGRlZmluaXRpb24gZm9yIHVzZSBpbiB0aGlzIGRvY3VtZW50IC0gdGhl
IGRvY3VtZW50IGRlZmluZXMNCj4gYSBjb250ZXh0IGhlYWRlciB3aGljaCBjYXJyaWVzIG1ldGFk
YXRhLCBhbmQgaXQgbmVlZCB0byBiZSBiZXR0ZXINCj4gZGVmaW5lZCB0aGFuIHNvbWV0aGluZyB3
aGljaCBwcm92aWRlcyBhbiBhYmlsaXR5Lg0KPiBBcGFydCBmcm9tIFJGQzc2NjUgYWN0dWFsbHkg
KmRlZmluaW5nKiBtZXRhZGF0YSwgaXQgZG9lc24ndCByZWFsbHkNCj4gZGVzY3JpYmUgd2hhdCB5
b3UgZG8gd2l0aCBpdC4gQXMgdGhpcyBkb2N1bWVudCBkaXNjdXNzZXMgbWV0YWRhdGEgbXVjaA0K
PiBtb3JlIChhbmQgaG93IHRvIGNhcnJ5IGl0KSwgSSB0aGluayB0aGF0IGl0IG5lZWRzIHRvIG11
Y2ggYmV0dGVyDQo+IGRlZmluZSB3aGF0IGl0IGlzLCB3aGF0IGl0cyBwdXJwb3NlIGlzLCBhbmQg
aG93IHRvIHVzZSBpdC4NCj4gDQoNCk9LLCBuZXcgZGVmaW5pdGlvbiwgY29tbWVudHMgd2VsY29t
ZToNCg0KICAgIDx0IGhhbmdUZXh0PSJNZXRhZGF0YToiPg0KICAgICAgICAgICAgRGVmaW5lZCBp
biA8eHJlZiB0YXJnZXQ9IlJGQzc2NjUiPjwveHJlZj4uDQpUaGUgbWV0YWRhdGEsIG9yIGNvbnRl
eHQgaW5mb3JtYXRpb24gc2hhcmVkIGJldHdlZW4gY2xhc3NpZmllcnMgYW5kIFNGcywgYW5kIGFt
b25nIFNGcywNCmlzIGNhcnJpZWQgb24gdGhlIE5TSCdzIENvbnRleHQgSGVhZGVycy4gSXQgYWxs
b3dzIHN1bW1hcml6aW5nIGEgY2xhc3NpZmljYXRpb24gcmVzdWx0DQppbiB0aGUgcGFja2V0IGl0
c2VsZiwgYXZvaWRpbmcgc3Vic2VxdWVudCByZS1jbGFzc2lmaWNhdGlvbnMuDQoNCiAgICAgICBF
eGFtcGxlcyBvZiBtZXRhZGF0YSBpbmNsdWRlIGNsYXNzaWZpY2F0aW9uIGluZm9ybWF0aW9uIHVz
ZWQgZm9yDQogICAgICAgcG9saWN5IGVuZm9yY2VtZW50IGFuZCBuZXR3b3JrIGNvbnRleHQgZm9y
IGZvcndhcmRpbmcgcG9zdA0KICAgICAgIHNlcnZpY2UgZGVsaXZlcnkuICANCg0KDQogICAgICAg
ICAgICA8L3Q+DQoNCg0KPiBJc3N1ZSAzOiBTZWN0aW9uIDIuICBOZXR3b3JrIFNlcnZpY2UgSGVh
ZGVyDQo+ICJBbiBvdXRlciB0cmFuc3BvcnQgaGVhZGVyIGlzIGltcG9zZWQsIG9uIE5TSCBhbmQg
dGhlIG9yaWdpbmFsDQo+IHBhY2tldC9mcmFtZSwgZm9yIG5ldHdvcmsgZm9yd2FyZGluZy4iIC0g
dGhpcyBpcyB2ZXJ5IHBvb3JseSB3b3JkZWQsDQo+IGFuZCBJIGRvbid0IHJlYWxseSBrbm93IHdo
YXQgSSdtIHN1cHBvc2VkIHRvIGRvIGhlcmUuIEknbSBhc3N1bWluZw0KPiB0aGF0IEknbSBzdXBw
b3NlZCB0byBjb25jYXRlbmF0ZSB0aGUgTlNIIGFuZCB0aGUgcGFja2V0LCBhbmQgdGhlbg0KPiBl
bmNhcHN1bGF0ZSB0aGlzIGluIHNvbWUgdHJhbnNwb3J0IG9mIG15IGNob29zaW5nLCBidXQgdGhp
cyBuZWVkcyBtb3JlDQo+IHByZWNpc2lvbi4NCj4gDQoNCkFncmVlZC4gUmV3b3JkZWQuIEhlcmXi
gJlzIGEgc3VnZ2VzdGlvbiwgZXhwbGljaXQgdGV4dCB3ZWxjb21lOg0KDQogICAgICA8dD4NCkFu
IE5TSCBpcyBpbXBvc2VkIG9uIHRoZSBvcmlnaW5hbCBwYWNrZXQvZnJhbWUuDQogICBUaGlzIE5T
SCBjb250YWlucyBzZXJ2aWNlIHBhdGggaW5mb3JtYXRpb24gYW5kDQogICBvcHRpb25hbGx5IG1l
dGFkYXRhIHRoYXQgYXJlIGFkZGVkIHRvIGEgcGFja2V0IG9yIGZyYW1lIGFuZCB1c2VkIHRvDQog
ICBjcmVhdGUgYSBzZXJ2aWNlIHBsYW5lLiBTdWJzZXF1ZW50bHksIGFuIG91dGVyIGVuY2Fwc3Vs
YXRpb24gaXMgaW1wb3NlZCBvbg0KdGhlIE5TSCwgd2hpYyBpcyB1c2VkIGZvciBuZXR3b3JrIGZv
cndhcmRpbmcuDQogICAgIDwvdD4NCg0KDQo+IElzc3VlIDQ6IFRoZSBkb2N1bWVudCB0YWxrcyBh
Ym91dCB1c2luZyB0aGUgVFRMIHRvIGF2b2lkIGxvb3BzLCBhbmQNCj4gYWxzbyB0aGUgU2Vydmlj
ZSBJbmRleCAoU0kpLiAiVGhlIFNlcnZpY2UgSW5kZXggTVVTVCBiZSBkZWNyZW1lbnRlZCBieQ0K
PiBhIHZhbHVlIG9mIDEgYnkgU2VydmljZSBGdW5jdGlvbnMgb3IgYnkgU0ZDIFByb3h5IG5vZGVz
IGFmdGVyDQo+IHBlcmZvcm1pbmcgcmVxdWlyZWQgc2VydmljZXMgIGFuZCB0aGUgbmV3IGRlY3Jl
bWVudGVkIFNJIHZhbHVlIE1VU1QgYmUNCj4gdXNlZCBpbiB0aGUgZWdyZXNzIHBhY2tldOKAmXMg
TlNILiAuLi4gQWRkaXRpb25hbGx5LCB3aGlsZSB0aGUgVFRMIGZpZWxkDQo+IGlzIHRoZSBtYWlu
IG1lY2hhbmlzbSBmb3Igc2VydmljZSBwbGFuZSBsb29wIGRldGVjdGlvbiwgdGhlIFNJIGNhbg0K
PiBhbHNvIGJlIHVzZWQgZm9yIGRldGVjdGluZyBzZXJ2aWNlIHBsYW5lIGxvb3BzLiIuIE11Y2gg
YmV0dGVyIHRleHQgaXMNCj4gbmVlZGVkIGhlcmUgdG8gZGlzY3VzcyBob3cgdGhlc2UgaW50ZXJh
Y3QuIExldHMgc2F5IHRoZSBUVEwgaXMgMTQsIGFuZA0KPiB0aGUgU0kgaXMgMS4gVGhlIHBhY2tl
dCBpcyBub3cgaGFuZGVkIHRvIHRoZSBuZXh0IFNGLCB3aGljaCBkZWNyZW1lbnRzDQo+IGl0IHRv
IDAuIE5vdyB3aGF0PyBJdCB0aGlzIHRoZSBzYW1lIGFzIHRoZSBUVEwgaGl0dGluZyAwPyBJZiBp
dCBhbg0KPiBlcnJvcj8gRG8gSSB3cmFwIGFuZCBnbyBiYWNrIHRvIDI1NT8gV2hhdCBhcmUgdGhl
cmUgMiBtZWNoYW5pc21zIGZvcg0KPiB0aGlzPyBNdWNoIGZ1cnRoZXIgZG93biwgaW4gU2VjdGlv
biA2LjEsIHdlIGhhdmU6ICJTSSBzZXJ2ZXMgYXMgYQ0KPiBtZWNoYW5pc20gZm9yIGRldGVjdGlu
ZyBpbnZhbGlkIHNlcnZpY2UgZnVuY3Rpb24gcGF0aHMuICBJbg0KPiBwYXJ0aWN1bGFyLCBhbiBT
SSB2YWx1ZSBvZiB6ZXJvIGluZGljYXRlcyB0aGF0IGZvcndhcmRpbmcgaXMgaW5jb3JyZWN0DQo+
IGFuZCB0aGUgcGFja2V0IG11c3QgYmUgZGlzY2FyZGVkLiIgVGhpcyBhbnN3ZXJzIG1hbnkgb2Yg
dGhlIGFib3ZlLCBidXQNCj4gaGF2aW5nIHRoZSB0ZXh0IGJldHRlciBvcmdhbml6ZWQgd291bGQg
c2ltcGxpZnkgdGhlIGRvY3VtZW50Lg0KPiANCg0KSSBhbSBoZXNpdGFudCB0byB0b3VjaCB0aGF0
IHRleHQgcmlnaHQgbm93IGFzIGl0IHN1bW1hcml6ZXMgYSBkZWxpY2F0ZSBiYWxhbmNlIHJlYWNo
ZWQgYnkgdGhlIFdHLg0KDQpMZXQgbWUgZ28gYmFjayB0byB0aGUgV0cgYW5kIHByb3Bvc2UgdGV4
dCBmb3IgdGhpcy4NCg0KPiBJc3N1ZSA1OiBTZWN0aW9uIDYuIFNlcnZpY2UgUGF0aCBGb3J3YXJk
aW5nIHdpdGggTlNIIFN1YnNlY3Rpb24gNi4xLg0KPiBTRkZzIGFuZCBPdmVybGF5IFNlbGVjdGlv
bg0KPiBJJ20gYXNzdW1pbmcgdGhhdCB0aGVyZSBpcyBtdWNoIG1vcmUgZGV0YWlsIGluIG90aGVy
IGRvY3VtZW50cyB3aGljaA0KPiBjb3ZlciBob3cgdG8gdXNlIHRoZSBTUEkgLyBTSSB0byBkbyB0
aGUgZm9yd2FyZGluZyAtLSBjYW4geW91IHBsZWFzZQ0KPiBpbnNlcnQgYSByZWZlcmVuY2U/IEkn
bSBzb21ld2hhdCBjb25mdXNlZCBieSB0aGUgbGV2ZWwgb2YgZGV0YWlsDQo+IGJldHdlZW4gdGhp
cyBkb2N1bWVudCBhbmQgPHdoYXRldmVyIHRoZSBvdGhlciBvbmUgaXM+LiBUaGlzIGRvZXNuJ3QN
Cj4gY29udGFpbiBlbm91Z2ggdG8gaW1wbGVtZW50LCBidXQgc2VlbSB0byBpbmNsdWRlIG1vcmUg
dGhhbiBJJ2QgZXhwZWN0DQo+IHRvIGNsYXJpZnkgaG93IHRvIGludGVyZmFjZSB3aXRoIHNvbWUg
b3RoZXIgZG9jLg0KDQpUaGUgZGV0YWlsIGhlcmUgc2VlbXMgYWRlcXVhdGUuDQoNCj4gDQo+IA0K
PiANCj4gDQo+IA0KPiBRdWVzdGlvbnMgLyBjb25jZXJuczoNCj4gU2VjdGlvbiAyLjIuICBOU0gg
QmFzZSBIZWFkZXINCj4gIlRUTDogSW5kaWNhdGVzIHRoZSBtYXhpbXVtIFNGRiBob3BzIGZvciBh
biBTRlAuICBUaGlzIGZpZWxkIGlzIHVzZWQNCj4gZm9yIHNlcnZpY2UgcGxhbmUgbG9vcCBkZXRl
Y3Rpb24uIC4uLiAgRWFjaCBTRkYgaW52b2x2ZWQgaW4gZm9yd2FyZGluZw0KPiBhbiBOU0ggcGFj
a2V0IE1VU1QgZGVjcmVtZW50IHRoZSBUVEwgdmFsdWUgYnkgMSBwcmlvciB0byBOU0gNCj4gZm9y
d2FyZGluZyBsb29rdXAuICBEZWNyZW1lbnRpbmcgYnkgMSBmcm9tIGFuIGluY29taW5nIHZhbHVl
IG9mIDANCj4gc2hhbGwgcmVzdWx0IGluIGEgVFRMIHZhbHVlIG9mIDYzLiAgVGhlIHBhY2tldCBN
VVNUIE5PVCBiZSBmb3J3YXJkZWQNCj4gaWYgVFRMIGlzLCBhZnRlciBkZWNyZW1lbnQsIDAuIg0K
PiBXaHkgZG9lcyBkZWNyZW1lbnRpbmcgYnkgMSBmcm9tIDAgcmVzdWx0IGluIDYzPyBVbmRlciB3
aGF0ICh2YWxpZCkNCj4gY29uZGl0aW9ucyB3aWxsIEkgcmVjZWl2ZSBhIHBhY2tldCB3aXRoIGFu
IGluY29taW5nIHZhbHVlIG9mIDA/ICh3aHkNCj4gaXMgdGhpcyBub3QgYW4gZXJyb3I/KQ0KPiAN
Cg0KV3JhcD8NCg0KPiBTZWN0aW9uIDIuNC4gIE5TSCBNRCBUeXBlIDENCj4gIldoZW4gdGhlIEJh
c2UgSGVhZGVyIHNwZWNpZmllcyBNRCBUeXBlID0gMHgxLCBhIEZpeGVkIExlbmd0aCBDb250ZXh0
DQo+IEhlYWRlciAoMTYtYnl0ZXMpIE1VU1QgYmUgcHJlc2VudCBpbW1lZGlhdGVseSBmb2xsb3dp
bmcgdGhlIFNlcnZpY2UNCj4gUGF0aCBIZWFkZXIsIGFzIHBlciBGaWd1cmUgNC4gIFRoZSB2YWx1
ZSBvZiBhIEZpeGVkIExlbmd0aCBDb250ZXh0DQo+IEhlYWRlciB0aGF0IGNhcnJpZXMgbm8gbWV0
YWRhdGEgTVVTVCBiZSBzZXQgdG8gemVyby4iLiAiVGhpcw0KPiBzcGVjaWZpY2F0aW9uIGRvZXMg
bm90IG1ha2UgYW55IGFzc3VtcHRpb25zIGFib3V0IHRoZSBjb250ZW50IG9mIHRoZQ0KPiAxNiBi
eXRlIENvbnRleHQgSGVhZGVyIHRoYXQgbXVzdCBiZSBwcmVzZW50IHdoZW4gdGhlIE1EIFR5cGUg
ZmllbGQgaXMNCj4gc2V0IHRvIDEsIGFuZCBkb2VzIG5vdCBkZXNjcmliZSB0aGUgc3RydWN0dXJl
IG9yIG1lYW5pbmcgb2YgdGhlDQo+IGluY2x1ZGVkIG1ldGFkYXRhLiIuIFNvLCB0aGUgc3BlY2lm
aWNhdGlvbiBkb2Vzbid0IG1ha2UgYW55DQo+IGFzc3VtcHRpb25zIGFib3V0IHRoZSBGaXhlZCBM
ZW5ndGggQ29udGV4dCBIZWFkZXIgKEkgZ3Vlc3MgaXQgaXMgYW4NCj4gb3BhcXVlIGJsb2IpLCBi
dXQgaWYgaXQgaGFzIG5vIG1ldGFkYXRhIGlzIG11c3QgYmUgMD8gQW5kIGlmIHRoZXJlIGlzDQo+
IG5vIG1ldGFkYXRhLCB3aHkgIHdvdWxkIEkgbmVlZCB0byB3YXN0ZSAxNiBieXRlcz8gQW5kIHRo
aXMgZG9jdW1lbnQNCj4gZGVmaW5lcyAyIE1EIHR5cGVzIC0tIHdoeSB3b3VsZCBJIHVzZSB0aGlz
IG9uZSBpbnN0ZWFkIG9mIGEgVHlwZSAyPw0KPiAod2hpY2ggc2VlbXMgY2xlYW5lciwgYW5kIHNo
b3J0ZXIpLg0KDQpUaGVyZSBhcmUgdHdvIE1EIFR5cGVzIHRvIHVzZS4gRml4ZWQgaXMgSFcgZnJp
ZW5kbHksIFRMViBpcyBTVyBmcmllbmRseS4gDQoNCkFzIHVzdWFsLCB0aGVyZSBpcyBhIHRyYWRl
b2ZmLCBhbmQgeW91IGNob29zZSBNRCBUeXBlIGJhc2VkIG9uIHdoYXQgeW91IHdhbnQgdG8gb3B0
aW1pemUgZm9yLg0KDQoNCj4gS2luZCBvZiByZWxhdGVkIHRvIElzc3VlIDIsIEkNCj4gdGhpbmsg
dGhhdCB0aGVyZSBuZWVkcyB0byBiZSBtb3JlIGRpc2N1c3Npb25zIChwZXJoYXBzIGluIHNvbWUg
b3RoZXINCj4gZG9jdW1lbnQsIHdoaWNoIG5lZWRzIGEgcmVmZXJlbmNlKSB3aGF0IHRoZSBwdXJw
b3NlIG9mIHRoZSBtZXRhZGF0YQ0KPiBpcywgd2h5IGl0IGlzIHNvbWV0aW1lcyBtZXRhZGF0YSBh
bmQgc29tZXRpbWVzIENvbnRleHQgSGVhZGVyLCB3aGF0IGENCj4gcmVjZWl2ZXIgaXMgc3VwcG9z
ZWQgdG8gZG8gd2l0aCB0aGlzLCBldGMuDQo+IA0KDQpDb250ZXh0IGhlYWRlciBjYXJyaWVzIG1l
dGFkYXRhLg0KDQo+IFNlY3Rpb24gMi40Og0KPiAiQW4gU0ZDLWF3YXJlIFNGIE1VU1QgcmVjZWl2
ZSB0aGUgZGF0YSBzZW1hbnRpY3MgZmlyc3QgaW4gb3JkZXIgdG8NCj4gcHJvY2VzcyB0aGUgZGF0
YSBwbGFjZWQgaW4gdGhlIG1hbmRhdG9yeSBjb250ZXh0IGZpZWxkLiAgVGhlIGRhdGENCj4gc2Vt
YW50aWNzIGluY2x1ZGUgYm90aCB0aGUgYWxsb2NhdGlvbiBzY2hlbWEgYW5kIHRoZSBtZWFuaW5n
IG9mIHRoZQ0KPiBpbmNsdWRlZCBkYXRhLiAgSG93IGFuIFNGQy1hd2FyZSBTRiBnZXRzIHRoZSBk
YXRhIHNlbWFudGljcyBpcyBvdXRzaWRlDQo+IHRoZSBzY29wZSBvZiB0aGlzIHNwZWNpZmljYXRp
b24uIiAgLS0gcmVsYXRlZCB0byB0aGUgYWJvdmUsIEkgc3RpbGwNCj4gZG9uJ3QgZ2V0IHRoaXMu
IElzICJ0aGUgZGF0YSBwbGFjZWQgaW4gdGhlIG1hbmRhdG9yeSBjb250ZXh0IGZpZWxkIiA9PQ0K
PiAibWV0YWRhdGEiPyAgQW5kIHRoZXJlIGlzIG5vIHR5cGUgaW5mb3JtYXRpb24gYXNzb2NpYXRl
ZCwgc28gcmVjZWl2ZXINCj4gY2Fubm90IGxvb2sgYXQgaXQgYW5kIGtub3cgd2hhdCBpdCBpcywg
b3RoZXIgdGhhbiAiSSBleHBlY3RlZCBhIGJsb2IsDQo+IHRoaXMgaXMgYSBibG9iLCBibG9icyBJ
IHJlY2VpdmUgc2hvdWxkIGJlIG9mIHR5cGUgWCwgbGV0IG1lIHRyeQ0KPiBkZWNvZGVkIGl0IGFz
IG9uZT8iIC0tIHNob3VsZG4ndCB0aGVyZSBiZSBzb21lIHNvcnQgb2YgaGludCBpbiB0aGUgTlNI
DQo+IGFzIHRvIHdoYXQgdGhlIGNvbnRleHQgZmllbGQgaXMgY2FycnlpbmcgKGxpa2UgVHlwZSAy
IGhhcyk/IEkndmUNCj4gbG9va2VkIGF0ICBJLUQuZ3VpY2hhcmQtc2ZjLW5zaC1kYy1hbGxvY2F0
aW9uIGFuZA0KPiBJLUQubmFwcGVyLXNmYy1uc2gtYnJvYWRiYW5kLWFsbG9jYXRpb24gd2hpY2gg
ZGlzY3VzcyBob3cgYml0cyBpbiB0aGUNCj4gY29udGV4dCBoZWFkZXIgY2FuIGJlIGFsbG9jYXRl
ZCwgYnV0IHdvdWxkIGEgcmVjZWl2ZXIgZGlmZmVyZW50aWF0ZQ0KPiB3aGljaCB0eXBlIGlzIGlu
IHVzZSAob3RoZXIgdGhhbiBiZWluZyBjb25maWd1cmVkIHRvIGtub3cgdGhhdCBibG9icw0KPiBh
cmUgYWx3YXlzIG9mIHR5cGUgWCkuIEFnYWluLCBJJ20gaG9waW5nIHRoYXQgdGhlcmUgaXMgYW4g
U0ZDIGRvY3VtZW50DQo+IHdoaWNoIGV4cGxhaW5zIHRoZSBhcmNoaXRlY3R1cmUgaW4gbW9yZSBk
ZXRhaWwgdGhlbiBSRkM3NjY1Lg0KDQpNRCBUeXBlIDEgaXMgbm90IHNlbGYtZGVzY3JpYmluZy4N
Cg0KPiANCj4gU2VjdGlvbiAgMi41LjEuICBPcHRpb25hbCBWYXJpYWJsZSBMZW5ndGggTWV0YWRh
dGENCj4gT3B0aW9uYWwgdmFyaWFibGUgbGVuZ3RoIENvbnRleHQgSGVhZGVycyBoYXZlIGEgQ2xh
c3MgKHNjb3BlIG9mIHRoZQ0KPiBUeXBlKSwgYSBUeXBlIChleHBsaWNpdCB0eXBlIG9mIG1ldGFk
YXRhLCBkZWZpbmVkIGJ5IHRoZSBDbGFzcyBvd25lciksDQo+IGFuZCBhIExlbmd0aC4NCj4gQSBs
ZW5ndGggb2YgMCBtZWFucyB0aGF0IHRoZSBjb250ZXh0IGhlYWRlciBoYXMgbm8gZGF0YS4gSXQg
d291bGQgYmUNCj4gdXNlZnVsIHRvIGV4cGxhaW4gd2hhdCB0aGlzIGFjdHVhbGx5IG1lYW5zIC0t
IGl0IHNvdW5kcyBsaWtlIGEgbWVzc2FnZQ0KPiB3aXRoIG5vIGNvbnRlbnQsIGJ1dCBwZXJoYXBz
IHJlY2VpdmVycyBhcmUgc3VwcG9zZWQgdG8gdXNlIHRoZSBUeXBlIGluDQo+IHRoaXMgY2FzZSB0
byBkbyBzb21ldGhpbmc/DQoNClllcyA6LSkgUHJlY2lzZWx5Lg0KDQo+IA0KPiBTZWN0aW9uIDMu
ICBOU0ggQWN0aW9ucw0KPiAiTlNILWF3YXJlIG5vZGVzIGFyZSB0aGUgb25seSBub2RlcyB0aGF0
IG1heSBhbHRlciB0aGUgY29udGVudCBvZiBOU0gNCj4gaGVhZGVycy4iIC0tIHRoaXMgc2VudGVu
Y2UgaXMgbm9uc2Vuc2ljYWwuIElmIGEgbm9kZSBkb2Vzbid0IGtub3cNCj4gc29tZXRoaW5nIGlz
IGFuIE5TSCAoaXMgaXQgbm90IE5TSC1hd2FyZSksIHRlbGxpbmcgaXQgbm90IHRvIHRvdWNoIE5T
SA0KPiBoZWFkZXJzIGlzIGJhc2ljYWxseSAiRGV2aWNlcyBvbiB0aGUgSW50ZXJuZXQgc2hvdWxk
bid0IHBva2UgYXQgdGhpbmdzDQo+IHRoYXQgdGhleSBkb24ndCB1bmRlcnN0YW5k4oCdLg0KDQpJ
dCBtaWdodCBiZSBvYnZpb3VzIG9yIHJlZHVuZGFudCwgYnV0IGl0IGlzIG5vdCBub25zZW5zaWNh
bC4gDQoNCldlIHdpbGwgcmV3b3JkIGl0IHRob3VnaC4gOi0pDQoNCj4gDQo+IFNlY3Rpb24gMzoN
Cj4gIkF0IHRoZSBlbmQgb2YgYSBzZXJ2aWNlIGZ1bmN0aW9uIHBhdGgsIGFuIFNGRiwgTVVTVCBi
ZSB0aGUgbGFzdCBub2RlDQo+IG9wZXJhdGluZyBvbiB0aGUgc2VydmljZSBoZWFkZXIgYW5kIE1V
U1QgcmVtb3ZlIE5TSCBiZWZvcmUgZm9yd2FyZGluZw0KPiBvciBkZWxpdmVyaW5nIHRoZSB1bi1l
bmNhcHN1bGF0ZWQgcGFja2V0LiIgLSBJJ20gc29tZXdoYXQgY29uZnVzZWQNCj4gd2hhdCB0aGlz
IGlzIHRyeWluZyB0byBzYXksIGFuZCBhc3N1bWUgdGhhdCBpdCBpcyBzaW1wbHkgc3VwZXJmbHVv
dXMNCj4gY29tbWFzLiBCdXQsIHdpdGggdGhvc2UgcmVtb3ZlZCB0aGUgc2VudGVuY2UgaXMgc3Rp
bGwgY29uZnVzaW5nIHRvIG1lDQo+IC0tIGEgU0ZGIGlzIHRoZSB0aGluZyB0aGF0IGRvZXMgdGhl
IGZvcndhcmRpbmcsIGFuZCBzbywgYnkgZGVmaW5pdGlvbg0KPiBpdCBoYXMgdG8gYmUgdGhlIGxh
c3QgdGhpbmcgb3BlcmF0aW5nIG9uIHRoZSBzZXJ2aWNlIGhlYWRlciAodW5sZXNzDQo+IHRoZSBw
YWNrZXQgaXMgZHJvcHBlZCkgLS0gc28sIHdoYXQgZG9lcyB0aGUgZmlyc3QgTVVTVCBtZWFuPw0K
DQpZZXMsIHRoZXJlIGlzIGEgc3VwZXJmbHVvdXMgY29tbWEuIEJ1dCB0aGUgbWVhbmluZyBvZiB0
aGUgc2VudGVuY2UgaXMg4oCcZG8gbm90IGxlYWsgTlNIIG91dHNpZGUgdGhlIFNGQyBkb21haW7i
gJ0uDQoNCknigJlsbCByZXdvcmQgaXQuDQoNCj4gDQo+IFNlY3Rpb24gNC4gIE5TSCBUcmFuc3Bv
cnQgRW5jYXBzdWxhdGlvbg0KPiAiVGhlIHByZXNlbmNlIG9mIE5TSCBpcyBpbmRpY2F0ZWQgdmlh
IHByb3RvY29sIHR5cGUgb3Igb3RoZXIgaW5kaWNhdG9yDQo+IGluIHRoZSBvdXRlciBlbmNhcHN1
bGF0aW9uLiIgLS0ganVzdCBmb3IgbXkgaW50ZXJlc3QsIHdoYXQgYWxsDQo+IGVuY2Fwc3VsYXRp
b25zIGFscmVhZHkgaGF2ZSB0aGlzIGRlZmluZWQgLyBhbGxvY2F0ZWQ/DQoNCkV0aGVybmV0LCBH
UkUsIFZYTEFOLUdQRSwgb3RoZXJzLg0KDQo+IA0KPiBTZWN0aW9uIDUuICBGcmFnbWVudGF0aW9u
IENvbnNpZGVyYXRpb25zDQo+ICJBcyBkaXNjdXNzZWQgaW4gW0ktRC5pZXRmLXJ0Z3dnLWR0LWVu
Y2FwXSwgd2l0aGluIGFuIGFkbWluaXN0cmF0aXZlDQo+IGRvbWFpbiwgYW4gb3BlcmF0b3IgY2Fu
IGVuc3VyZSB0aGF0IHRoZSB1bmRlcmxheSBNVFUgaXMgc3VmZmljaWVudCB0bw0KPiBjYXJyeSBT
RkMgdHJhZmZpYyB3aXRob3V0IHJlcXVpcmluZyBmcmFnbWVudGF0aW9uLiIgLS0gSSB0aGluayB0
aGF0DQo+IHRoYXQgaXMgc3RyZXRjaGluZyB3aGF0IEktRC5pZXRmLXJ0Z3dnLWR0LWVuY2FwIHNh
eXMgYSBiaXQgZmFyLiBOU0gNCj4gVHlwZSAxIGFkZHMgMjQgb2N0ZXRzICg0IG9jdGV0IEJhc2Ug
SGVhZGVyLCA0IG9jdGV0IFNlcnZpY2UgUGF0aA0KPiBIZWFkZXIsIDE2IG9jdGV0IENvbnRleHQg
SGVhZGVyKSwgcGx1cyB0aGUgZ2V0cyB3cmFwcGVkIGluIGEgbmV3DQo+IHRyYW5zcG9ydCwgc28g
bGV0J3Mgc2F5IDI0IG9jdGV0cyBmb3IgR1JFLiBUaGlzIG1lYW5zIHRoYXQsIGZvciBhDQo+IDE1
MDBieXRlIHBhY2tldCBJIG5lZWQgYW4gTVRVIG9mIDE1NDggKEknbSBub3Qgc3VyZSBhbGwgb3Bl
cmF0b3JzIGNhbg0KPiBzdXBwb3J0IHRoYXQgZXZlcnl3aGVyZSkuIFRoZSBUeXBlIDIgaGVhZGVy
IGlzIG9mIHZhcmlhYmxlIGxlbmd0aCAoYW5kDQo+IEkgZG9uJ3QgdGhpbmsgSSBzYXcgYSBsaW1p
dCkuDQoNClRoaXMgdGV4dCBpcyByZXdvcmRlZCBiYXNlZCBvbiBHZW5BUlQuDQoNCj4gIiBGb3Ig
ZXhhbXBsZSwgd2hlbiBOU0ggaXMgZW5jYXBzdWxhdGVkIGluIElQLCBJUC1sZXZlbCBmcmFnbWVu
dGF0aW9uDQo+IGNvdXBsZWQgd2l0aCBQYXRoIE1UVSBEaXNjb3ZlcnkgKFBNVFVEKSBpcyB1c2Vk
LiBXaGVuLCBvbiB0aGUgb3RoZXINCj4gaGFuZCwgdGhlIHVuZGVybGF5IGRvZXMgbm90IHN1cHBv
cnQgZnJhZ21lbnRhdGlvbiBwcm9jZWR1cmVzLCBhbiBlcnJvcg0KPiBtZXNzYWdlIFNIT1VMRCBi
ZSBsb2dnZWQgd2hlbiBkcm9wcGluZyBhIHBhY2tldCB0b28gYmlnLiIgLS0gSSB0aGluaw0KPiB0
aGF0IG1vcmUgZ3VpZGFuY2UgLyB0ZXh0IGlzIG5lZWRlZCBoZXJlLCBlLmcgZm9yIHY2LiBKdXN0
IGRyb3BwaW5nDQo+IHRoZSBwYWNrZXQgYW5kIGxvZ2dpbmcgYW4gZXJyb3IgZG9lc24ndCBzb2x2
ZSB0aGUgYmFzZSBpc3N1ZSBjYXVzaW5nDQo+IHRoZSBwcm9ibGVtLiBJZiB0aGlzIHByb3RvY29s
IHdhc24ndCBhbiAiZW5jYXBzdWxhdGlvbiIgSSB3b3VsZG4ndA0KPiBmZWVsIHNvIHN0cm9uZ2x5
LCBidXQgaWYgdGhlIHByb3RvY29sIHNheXMgdGhhdCBpdCBwcm92aWRpbmcgYW4NCj4gZW5jYXBz
dWxhdGlvbiBpdCBuZWVkcyB0byBoYW5kbGUgdGhpbmdzIHRoYXQgZW5jYXBzdWxhdGlvbiBwcm90
b2NvbHMNCj4gZG8uDQoNClRoaXMgdGV4dCBjYW1lIGZyb20gT3BzRGlyIHJldmlldy4NCg0KPiAN
Cj4gDQo+IA0KPiANCj4gTml0czoNCg0KDQpBbGwgZml4ZWQuDQoNCkJlc3QsDQoNCuKAlA0KQ2Fy
bG9zIFBpZ25hdGFybywgY2FybG9zQGNpc2NvLmNvbQ0KDQrigJxTb21ldGltZXMgSSB1c2UgYmln
IHdvcmRzIHRoYXQgSSBkbyBub3QgZnVsbHkgdW5kZXJzdGFuZCwgdG8gbWFrZSBteXNlbGYgc291
bmQgbW9yZSBwaG90b3N5bnRoZXNpcy4iDQoNCg0KDQo+IFNlY3Rpb24gMS4gSW50cm9kdWN0aW9u
DQo+IC4uLiBjdXJyZW50IHNlcnZpY2UgZnVuY3Rpb24gZGVwbG95bWVudCBtb2RlbHMgaGF2ZSBi
ZWVuIHJlbGF0aXZlbHkNCj4gc3RhdGljLCBhbmQgYm91bmQgdG8gdG9wb2xvZ3kNCj4gW09dIHN0
YXRpYywgYW5kIGJvdW5kDQo+IFtQXSBzdGF0aWMgYW5kIGJvdW5kDQo+IFtSXSBncmFtbWFyDQo+
IA0KPiAuLi4NCj4gU3BlY2lmaWNhbGx5LCB0aGUgZm9sbG93aW5nIGZ1bmN0aW9ucyBhcmUgbmVj
ZXNzYXJ5Og0KPiANCj4gICAgICBUaGUgbW92ZW1lbnQgb2Ygc2VydmljZSBmdW5jdGlvbnMgYW5k
IGFwcGxpY2F0aW9uIHdvcmtsb2FkcyBpbiB0aGUNCj4gICAgICBuZXR3b3JrLg0KPiANCj4gICAg
ICBUaGUgYWJpbGl0eSB0byBlYXNpbHkgYmluZCBzZXJ2aWNlIHBvbGljeSB0byBncmFudWxhciBp
bmZvcm1hdGlvbiwNCj4gICAgICBzdWNoIGFzIHBlci1zdWJzY3JpYmVyIHN0YXRlLg0KPiANCj4g
W1JdOiBOdW1iZXJzIG9yIGJ1bGxldHMgd291bGQgbWFrZSB0aGUgbXVjaCBlYXNpZXIgdG8gcmVh
ZC4NCj4gDQo+IA0KPiBTZWN0aW9uIDEuMiAtIERlZmluaXRpb24gb2YgVGVybXMNCj4gIkJ5dGU6
ICBBbGwgcmVmZXJlbmNlcyB0byAiYnl0ZXMiIGluIHRoaXMgZG9jdW1lbnQgcmVmZXIgdG8gOC1i
aXQNCj4gYnl0ZXMsIG9yIG9jdGV0cy4iIC0tIHRoaXMgaXMgYSBjaXJjdWxhciBkZWZpbml0aW9u
ICh0aGUgc2VjdGlvbiBpcw0KPiBEZWZpbml0aW9uIG9mIFRlcm1zLCBub3QgVGVybWlub2xvZ3kp
IC0gc3VnZ2VzdCBkcm9wcGluZyB0aGUgOC1iaXQNCj4gYnl0ZXMsIG9jdGV0cyBjb3ZlcnMgaXQu
DQo+IA0KPiBUaHJvdWdob3V0IHRoZSBkb2N1bWVudDoNCj4gVGhlIGRvY3VtZW50IHNheXMgIkEg
U2VydmljZSBDbGFzc2lmaWVyIGFkZHMgTlNILiAgTlNIIGlzIHJlbW92ZWQgYnkNCj4gLi4uIiwg
YW5kICJOU0ggb2ZmZXJzIGEgY29tbW9uIGFuZCBzdGFuZGFyZHMtYmFzZWQgaGVhZGVyIiAtLSBp
cyBOU0ggYQ0KPiB0ZWNobm9sb2d5IChhcyBpbXBsaWVkIGJ5IHRoZSBzZWNvbmQgcGhyYXNlKSwg
b3IgYSB0aGluZyBhZGRlZCB0byBhDQo+IHBhY2tldCAobGlrZSB0aGUgZmlyc3QgaW1wbGllcyku
IFdoYXRldmVyIHRoZSBjYXNlLCBmb3IgdGhlIGZpcnN0LCAiQQ0KPiBTZXJ2aWNlIENsYXNzaWZp
ZXIgYWRkcyAqdGhlKiBOU0guICAqVGhlKiBOU0ggaXMgcmVtb3ZlZCBieSAuLi4iIChvciwNCj4g
ImFuIikuDQo+IA0KPiANCj4gU2VjdGlvbiAxLjQuIE5TSC1iYXNlZCBTZXJ2aWNlIENoYWluaW5n
DQo+ICAgTlNIIGNyZWF0ZXMgYSBkZWRpY2F0ZWQgc2VydmljZSBwbGFuZSwgbW9yZSBzcGVjaWZp
Y2FsbHksIE5TSA0KPiBbT10gcGxhbmUsIG1vcmUNCj4gW1BdIHBsYW5lOyBtb3JlDQo+IFtSXSBn
cmFtbWFyDQo+IA0KPiAxLiAgVG9wb2xvZ2ljYWwgSW5kZXBlbmRlbmNlOiBTZXJ2aWNlIGZvcndh
cmRpbmcgb2NjdXJzIHdpdGhpbiB0aGUNCj4gICAgICAgc2VydmljZSBwbGFuZSwgdGhlIHVuZGVy
bHlpbmcgbmV0d29yayB0b3BvbG9neSBkb2VzIG5vdCByZXF1aXJlDQo+IA0KPiBbT10gcGxhbmUs
IHRoZQ0KPiBbUF0gcGxhbmU7IHRoZSAgICAob3IgInBsYW5lLCBzbyB0aGUiKQ0KPiBbUl0gZ3Jh
bW1hcg0KPiANCj4gDQo+IFNlY3Rpb24gIDIuMi4gIE5TSCBCYXNlIEhlYWRlcg0KPiAiTUQgVHlw
ZTogSW5kaWNhdGVzIHRoZSBmb3JtYXQgb2YgTlNIIGJleW9uZCB0aGUgbWFuZGF0b3J5IEJhc2Ug
SGVhZGVyDQo+IGFuZCB0aGUgU2VydmljZSBQYXRoIEhlYWRlci4gIE1EIFR5cGUgZGVmaW5lcyB0
aGUgZm9ybWF0IG9mIHRoZQ0KPiBtZXRhZGF0YSBiZWluZyBjYXJyaWVkLiIgLS0gcGxlYXNlIGV4
cGFuZCBNRCBoZXJlLiBJIHdhc3RlZCBtdWNoIHRpbWUNCj4gYmVmb3JlIGd1ZXNzaW5nIHRoYXQg
dGhpcyB3YXMgTWV0YURhdGEgVHlwZS4NCj4gDQo+IA0KPiBHaXZlbiB0aGUNCj4gICB3aWRlc3By
ZWFkIGltcGxlbWVudGF0aW9uIG9mIGV4aXN0aW5nIGhhcmR3YXJlIHRoYXQgdXNlcyB0aGUgZmly
c3QNCj4gICBuaWJibGUgYWZ0ZXIgYW4gTVBMUyBsYWJlbCBzdGFjayBmb3IgRUNNUCBkZWNpc2lv
biBwcm9jZXNzaW5nLCB0aGlzDQo+ICAgZG9jdW1lbnQgcmVzZXJ2ZXMgdmVyc2lvbiAwMWIgYW5k
IHRoaXMgdmFsdWUgTVVTVCBOT1QgYmUgdXNlZCBpbg0KPiBbT10gMDFiIGFuZCB0aGlzIHZhbHVl
DQo+IFtQXSAwMWIuIFRoaXMgdmFsdWUNCj4gW1JdIGdyYW1tYXIgLS0gcnVuIG9uIHNlbnRlbmNl
LCBhbmQgaXQgcmVhZHMgYXdrd2FyZGx5IHdpdGggYQ0KPiBzZW1pY29sb24gYmVmb3JlIHRoZSAi
YW5kIiAoYnV0IHRoYXQgd291bGQgYmUgZ3JhbW1hdGljYWxseSBjb3JyZWN0LA0KPiBpZiBwcmVm
ZXJyZWQuKQ0KPiANCj4gDQo+IEZvcndhcmRpbmcgT0FNDQo+ICAgcGFja2V0cyB1bm1vZGlmaWVk
IGJ5IFNGQyBlbGVtZW50cyB0aGF0IGRvIG5vdCBzdXBwb3J0IFNGQyBPQU0NCj4gICBwcm9jZWR1
cmVzIG1heSBiZSBhY2NlcHRhYmxlIGZvciBhIHN1YnNldCBvZiBPQU0gZnVuY3Rpb25zLCBidXQg
Y2FuDQo+ICAgcmVzdWx0IGluIHVuZXhwZWN0ZWQgb3V0Y29tZXMgZm9yIG90aGVycywgdGh1cyBp
dCBpcyByZWNvbW1lbmRlZCB0bw0KPiBbDQo+IE9dIG90aGVycywgdGh1cw0KPiBbUF0gb3RoZXJz
OyB0aHVzDQo+IFtSXSBncmFtbWFyDQo+IA0KPiBUaGlzIHNwZWNpZmljYXRpb24gZG9lcyBub3Qg
ZGlzYWxsb3cgdGhlIE1EIFR5cGUgdmFsdWUgZnJvbSBjaGFuZ2luZw0KPiAgIGFsb25nIGFuIFNG
UDsgaG93ZXZlciwgdGhlIHNwZWNpZmljYXRpb24gb2YgdGhlIG5lY2Vzc2FyeSBtZWNoYW5pc20N
Cj4gICB0byBhbGxvdyB0aGUgTUQgVHlwZSB0byBjaGFuZ2UgYWxvbmcgYW4gU0ZQIGFyZSBvdXRz
aWRlIHRoZSBzY29wZSBvZg0KPiAgIHRoaXMgZG9jdW1lbnQsIGFuZCB3b3VsZCBuZWVkIHRvIGJl
IGRlZmluZWQgZm9yIHRoYXQgZnVuY3Rpb25hbGl0eSB0bw0KPiBbDQo+IE9dIGRvY3VtZW50LCBh
bmQNCj4gW1BdIGRvY3VtZW50IGFuZA0KPiBbUl0gZ3JhbW1hcg0KPiANCj4gDQo+IA0KPiBTZWN0
aW9uIDIuNDoNCj4gQXMgU0Ygb3IgU0ZDIFByb3h5IC0+IEEgU0Ygb3IgU0ZDIFByb3h5DQo+IA0K
PiBTZWN0aW9uIDIuNS4xOg0KPiAidGhlIFNGQy1hd2FyZSBTRiBNVVNUIE5PVCBwcm9jZXNzIHRo
ZSBwYWNrZXQgYW5kIE1VU1QgbG9nIGF0IGxlYXN0DQo+IG9uY2UgcGVyIHRoZSBTUEkgZm9yIHdo
aWNoIHRoZSBtYW5kYXRvcnkgbWV0YWRhdGEgaXMgbWlzc2luZy4iIC0tDQo+IGZlZWxzIGxpa2Ug
eW91IGFyZSBtaXNzaW5nIHNvbWUgd29yZHMgYWZ0ZXIgImxvZyIgLS0gcHJlc3VtYWJseSAibXVz
dA0KPiBsb2cgYW4gZXJyb3IiLCBvciAidGhpcyBldmVudCIsIG9yIHNvbWV0aGluZy4NCj4gDQo+
IA0KPiBTZWN0aW9uIDYuMS4gU0ZGcyBhbmQgT3ZlcmxheSBTZWxlY3Rpb24NCj4gVGhpcyBpbmRp
cmVjdGlvbiAtLSBTUEkgdG8gb3ZlcmxheSAtLSBjcmVhdGVzIGEgdHJ1ZSBzZXJ2aWNlIHBsYW5l
Lg0KPiAgIFRoYXQgaXMsIHRoZSBTRkYvU0YgdG9wb2xvZ3kgaXMgY29uc3RydWN0ZWQgd2l0aG91
dCBpbXBhY3RpbmcgdGhlDQo+ICAgbmV0d29yayB0b3BvbG9neSBidXQgbW9yZSBpbXBvcnRhbnRs
eSwgc2VydmljZSBwbGFuZSBvbmx5DQo+IA0KPiBbT10gdG9wb2xvZ3kgYnV0IG1vcmUgaW1wb3J0
YW50bHksDQo+IFtQXSB0b3BvbG9neTsgYnV0IG1vcmUgaW1wb3J0YW50bHksDQo+IFtSXSBncmFt
bWFyDQo+IA0KPiBUaGlzIGNhbiBiZSB2aWEgdGhlIG92ZXJsYXkgb3INCj4gICB1bmRlcmxheSBh
bmQgaW4gc29tZSBjYXNlIHJlcXVpcmUgYWRkaXRpb25hbCBjb25maWd1cmF0aW9uIG9uIHRoZSBT
Ri4NCj4gDQo+IFtPXSBzb21lIGNhc2UNCj4gW1BdIHNvbWUgY2FzZXMNCj4gW1JdIEkgdGhpbmsg
dGhpcyBpcyB3aGF0IHdhcyBpbnRlbmRlZA0KPiANCj4gU2VjdGlvbiA2LjQuIFNlcnZpY2UgR3Jh
cGhzDQo+IFRoZXNlIGNsYXNzaWZpZXJzIG1heSBhbHNvIG9mIGNvdXJzZQ0KPiANCj4gW09dIG1h
eSBhbHNvIG9mIGNvdXJzZQ0KPiBbUF0gbWF5LCBvZiBjb3Vyc2UsIGFsc28NCj4gW1JdIHJlYWRh
YmlsaXR5DQo+IA0KPiAgIG1vZGlmeSB0aGUgbWV0YWRhdGEgYXNzb2NpYXRlZCB3aXRoIHRoZSBw
YWNrZXQuDQo+IA0KPiBTZWN0aW9uIDcuMS4gTlNIIE1ldGFkYXRhIGFuZCBQb2xpY3kgRW5mb3Jj
ZW1lbnQNCj4gDQo+ICAgQXMgZGVzY3JpYmVkIGluIFNlY3Rpb24gMiwgTlNIIHByb3ZpZGVzIHRo
ZSBhYmlsaXR5IHRvIGNhcnJ5IG1ldGFkYXRhDQo+ICAgYWxvbmcgYSBzZXJ2aWNlIHBhdGguICBU
aGlzIG1ldGFkYXRhIG1heSBiZSBkZXJpdmVkIGZyb20gc2V2ZXJhbA0KPiAgIHNvdXJjZXMsIGNv
bW1vbiBleGFtcGxlcyBpbmNsdWRlOg0KPiANCj4gW09dIHNvdXJjZXMsIGNvbW1vbg0KPiBbUF0g
c291cmNlcy4gQ29tbW9uDQo+IFtSXSBncmFtbWFyDQo+IA0KPiAgICAgIE5ldHdvcmsgbm9kZXMv
ZGV2aWNlczogSW5mb3JtYXRpb24gcHJvdmlkZWQgYnkgbmV0d29yayBub2RlcyBjYW4NCj4gICAg
ICBpbmRpY2F0ZSBuZXR3b3JrLWNlbnRyaWMgaW5mb3JtYXRpb24gKHN1Y2ggYXMgVlJGIG9yIHRl
bmFudCkgdGhhdA0KPiAgICAgIG1heSBiZSB1c2VkIGJ5IHNlcnZpY2UgZnVuY3Rpb25zLCBvciBj
b252ZXllZCB0byBhbm90aGVyIG5ldHdvcmsNCj4gDQo+IFtPXSBmdW5jdGlvbnMsIG9yIGNvbnZl
eWVkDQo+IFtQXSBmdW5jdGlvbnMgb3IgY29udmV5ZWQNCj4gW1JdIGdyYW1tYXINCj4gDQo+IFRo
ZSBncmFudWxhcml0eSBvZiBjbGFzc2lmaWNhdGlvbiBtYXkgdmFyeS4gIEZvcg0KPiAgIGV4YW1w
bGUsIGEgbmV0d29yayBzd2l0Y2gsIGFjdGluZyBhcyBhIGNsYXNzaWZpZXIsIG1pZ2h0IG9ubHkg
YmUgYWJsZQ0KPiAgIHRvIGNsYXNzaWZ5IGJhc2VkIG9uIGEgNS10dXBsZSwgd2hlcmVhcywgYSBz
ZXJ2aWNlIGZ1bmN0aW9uIG1heSBiZQ0KPiANCj4gW09dIHdoZXJlYXMsIGEgc2VydmljZQ0KPiBb
UF0gd2hpbGUgYSBzZXJ2aWNlDQo+IFtSXSByZWFkYWJpbGl0eQ0KPiANCj4gSW4gYm90aCBvZiB0
aGUgZXhhbXBsZXMgYWJvdmUsIHRoZSBzZXJ2aWNlIGZ1bmN0aW9ucyBwZXJmb3JtIHBvbGljeQ0K
PiAgIGRlY2lzaW9ucyBiYXNlZCBvbiB0aGUgcmVzdWx0IG9mIHRoZSBpbml0aWFsIGNsYXNzaWZp
Y2F0aW9uOiB0aGUgU0ZzDQo+ICAgZGlkIG5vdCBuZWVkIHRvIHBlcmZvcm0gcmUtY2xhc3NpZmlj
YXRpb24sIHJhdGhlciB0aGV5IHJlbHkgb24gYQ0KPiANCj4gW09dIHJlLWNsYXNzaWZpY2F0aW9u
LCByYXRoZXINCj4gW1BdIHJlLWNsYXNzaWZpY2F0aW9uOyBpbnN0ZWFkLA0KPiBbUl0gZ3JhbW1h
ci9yZWFkYWJpbGl0eQ0KPiANCj4gICBhbnRlY2VkZW50IGNsYXNzaWZpY2F0aW9uIGZvciBsb2Nh
bCBwb2xpY3kgZW5mb3JjZW1lbnQuDQo+IA0KPiAgIERlcGVuZGluZyBvbiB0aGUgaW5mb3JtYXRp
b24gY2FycmllZCBpbiB0aGUgbWV0YWRhdGEsIGRhdGEgcHJpdmFjeQ0KPiAgIGNvbnNpZGVyYXRp
b25zIG1heSBuZWVkIHRvIGJlIGNvbnNpZGVyZWQuICBGb3IgZXhhbXBsZSwgaWYgdGhlDQo+IA0K
PiBUaGlzIGZlZWxzIGxpa2UgaXRzIHB1bnRpbmcgb24gdGhlIHByb2JsZW0gbW9yZSB0aGFuIGl0
IHNob3VsZCwgYnV0DQo+IEknbSBhdm9pZGluZyBwcml2YWN5IGFuZCBzZWN1cml0eSBpbiB0aGlz
IHBhcnRpY3VsYXIgcmV2aWV3Lg0KPiANCj4gICBtZXRhZGF0YSBjb252ZXlzIHRlbmFudCBpbmZv
cm1hdGlvbiwgdGhhdCBpbmZvcm1hdGlvbiBtYXkgbmVlZCB0byBiZQ0KPiAgIGF1dGhlbnRpY2F0
ZWQgYW5kL29yIGVuY3J5cHRlZCBiZXR3ZWVuIHRoZSBvcmlnaW5hdG9yIGFuZCB0aGUNCj4gICBp
bnRlbmRlZCByZWNpcGllbnRzICh3aGljaCBtYXkgaW5jbHVkZSBpbnRlbmRlZCBTRnMgb25seSkg
LiAgTlNIDQo+IA0KPiBbT10gKSAuDQo+IFtQXSApLg0KPiBbUl0gcHVuY3R1YXRpb24NCj4gDQo+
ICAgaXRzZWxmIGRvZXMgbm90IHByb3ZpZGUgcHJpdmFjeSBmdW5jdGlvbnMsIHJhdGhlciBpdCBy
ZWxpZXMgb24gdGhlDQo+ICAgdHJhbnNwb3J0L292ZXJsYXkgbGF5ZXIuICBBbiBvcGVyYXRvciBj
YW4gc2VsZWN0IHRoZSBhcHByb3ByaWF0ZQ0KPiAgIHRyYW5zcG9ydCB0byBlbnN1cmUgY29uZmlk
ZW50aWFsbHkgKGFuZCBvdGhlciBzZWN1cml0eSkNCj4gDQo+IFtPXSBjb25maWRlbnRpYWxseQ0K
PiBbUF0gY29uZmlkZW50aWFsaXR5DQo+IFtSXSB3b3JkIGNob2ljZQ0KPiANCj4gDQo+IFNlY3Rp
b24gOC4gU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMNCj4gDQo+IE5TSCBpcyBhbHdheXMgZW5jYXBz
dWxhdGVkIGluIGEgdHJhbnNwb3J0IHByb3RvY29sIChhcyBkZXRhaWxlZCBpbg0KPiAgIFNlY3Rp
b24gNCBvZiB0aGlzIHNwZWNpZmljYXRpb24pIGFuZCB0aGVyZWZvcmUsIHdoZW4gcmVxdWlyZWQs
DQo+IA0KPiBbT10gKSBhbmQgdGhlcmVmb3JlLA0KPiBbUF0gKTsgYW5kLCB0aGVyZWZvcmUsDQo+
IFtSXSBncmFtbWFyDQo+IA0KPiANCj4gDQo+IA0KPiBXDQo+IA0KPiANCj4gDQo+IA0KPiAtLSAN
Cj4gSSBkb24ndCB0aGluayB0aGUgZXhlY3V0aW9uIGlzIHJlbGV2YW50IHdoZW4gaXQgd2FzIG9i
dmlvdXNseSBhIGJhZA0KPiBpZGVhIGluIHRoZSBmaXJzdCBwbGFjZS4NCj4gVGhpcyBpcyBsaWtl
IHB1dHRpbmcgcmFiaWQgd2Vhc2VscyBpbiB5b3VyIHBhbnRzLCBhbmQgbGF0ZXIgZXhwcmVzc2lu
Zw0KPiByZWdyZXQgYXQgaGF2aW5nIGNob3NlbiB0aG9zZSBwYXJ0aWN1bGFyIHJhYmlkIHdlYXNl
bHMgYW5kIHRoYXQgcGFpcg0KPiBvZiBwYW50cy4NCj4gICAtLS1tYWYNCg0K


From nobody Thu Aug 31 20:57:13 2017
Return-Path: <dromasca@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 997A8132FCE; Thu, 31 Aug 2017 20:57:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qok_0yaUw-T9; Thu, 31 Aug 2017 20:57:01 -0700 (PDT)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6D16132F02; Thu, 31 Aug 2017 20:57:00 -0700 (PDT)
Received: by mail-qk0-x22f.google.com with SMTP id a21so6124979qkg.5; Thu, 31 Aug 2017 20:57:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=i/icXPFYVQpDSBea1AbaucJnkQxEgvsP01kAJQkue6Q=; b=ttFnjjUqwHfd8c2qFOUJ3EOgOlhVh7GZ5+rDYXNbA6fhSHkwlDmOaz+AXI108ckKj8 c3wjEyC8WEOo/2T6OvW1phgU/CY+WRiOPL2UFE1RkVWuTAF5vcOQ/en67UE2Ot99mjWC fEwMPrm35V4rmQfriCnJONC/r7S1o0r86rQSLvEQg8kXECxC5yHVBM2HSYmXvBwyeceW bOiW7buyphDJPSR8MuJs37eHBQDwDS+JRFlUB4qtnsVPTxP8iw2RiRK0TbY8Cm+qd615 o/thfdXcWXEIQ9M9cTU7EPh9bi60Y6j70lPOhF8c3yADr0FIQNSxox4pHRjWYqBmkGCW RN6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=i/icXPFYVQpDSBea1AbaucJnkQxEgvsP01kAJQkue6Q=; b=TAy72dFbKM1bMaB9j0uafHLVdAfXjSn9t8xLQUtqY+S1qNzYpw/uKpRNcEcodgM90M 4v8Mcuzrinj/Flm2L9zSJA/4knfC7OERrC4EOkjMH/bBGdUxoXk3ngdm8gY0Dvy9+s1Z wGZOcJE8yo4IY/kBAYQmlb1Nyxk1EOCsVYNwX2eYGGqLlEU42oevD3mvWAn3uSLdNiky dIEGs8y8zveHh4cwFOBn5VoryM/KuF+wHL+Gau0SnC0vKuw7RNlDYTbSsAQcSzFrtAak g25+wahPhvflPBu6H10uC8W3kpzcsy2pdaUGjlbM5SYgqEjvpsPUvSpMA9XpC2mm1PSc OJaQ==
X-Gm-Message-State: AHPjjUhDvMP9OVc2NVYOeNsSSVbJE7Ed3VhqOIYCmDRirmEgOeJUguEn IPw9udQsWDrBLZmPT9M1yfmy2KVnGQ==
X-Google-Smtp-Source: ADKCNb71zxywlVGeTG3KVasCGz4EdKvbQeINmLBYiWcozOG1iyFQBZ6ZmliVYLaPRYJSuxxdmhLZ8ekB4bZWkKfrlmM=
X-Received: by 10.55.141.66 with SMTP id p63mr836067qkd.190.1504238219931; Thu, 31 Aug 2017 20:56:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.19.206 with HTTP; Thu, 31 Aug 2017 20:56:59 -0700 (PDT)
In-Reply-To: <780ED7FA-6417-40A8-8524-69887C3AB161@cisco.com>
References: <150341604132.6021.14134855950693780483@ietfa.amsl.com> <780ED7FA-6417-40A8-8524-69887C3AB161@cisco.com>
From: Dan Romascanu <dromasca@gmail.com>
Date: Fri, 1 Sep 2017 06:56:59 +0300
Message-ID: <CAFgnS4XoR7eqW=+4i63Q=YGdqOVGCkBELkvfym_7kONtKKhaKg@mail.gmail.com>
Subject: Re: Genart last call review of draft-ietf-sfc-nsh-19
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>,  Service Function Chaining IETF list <sfc@ietf.org>,  "draft-ietf-sfc-nsh.all@ietf.org" <draft-ietf-sfc-nsh.all@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c085986c1b7b1055818c0ff"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FgzA-BsR2rATo7trQwjybJUD4dw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Sep 2017 03:57:05 -0000

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

Hi Carlos,

Thank you for addressing my comments. Your suggested edits seem to address
the issues.

Regards,

Dan


On Fri, Sep 1, 2017 at 3:55 AM, Carlos Pignataro (cpignata) <
cpignata@cisco.com> wrote:

> Hi, Dan,
>
> Many thanks for your detailed and valuable review, and apologies for the
> delay in Ack-ing and responding.
>
> Please see inline.
>
> =E2=80=94
> Carlos Pignataro, carlos@cisco.com
>
> =E2=80=9CSometimes I use big words that I do not fully understand, to mak=
e myself
> sound more photosynthesis."
>
> > On Aug 22, 2017, at 11:34 AM, Dan Romascanu <dromasca@gmail.com> wrote:
> >
> > Reviewer: Dan Romascanu
> > Review result: Almost Ready
> >
> > I am the assigned Gen-ART reviewer for this draft. The General Area
> > Review Team (Gen-ART) reviews all IETF documents being processed
> > by the IESG for the IETF Chair.  Please treat these comments just
> > like any other last call comments.
> >
> > For more information, please see the FAQ at
> >
> > <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> >
> > Document: draft-ietf-sfc-nsh-19
> > Reviewer: Dan Romascanu
> > Review Date: 2017-08-22
> > IETF LC End Date: 2017-08-25
> > IESG Telechat date: 2017-09-14
> >
> > Summary:
> >
> > This document describes the header (called Network Service Header - NSH=
)
> to be
> > inserted in packets and frames in order to create packets and frames th=
at
> > realize service functions described by other SFC documents. It needs to
> be read
> > in conjunction with RFC 7665 and other documents as the SFC control
> plane I-D
> > in order to make sense of the required functionality. This part of the
> SFC
> > solution seems almost ready, but a few issues mentioned below need in m=
y
> > opinion clarification before the document is approved.
>
> Thank you for this summary =E2=80=94 you raise good points.
>
> >
> > Major issues:
> >
> > 1. Section 11.1 claims: 'An IEEE EtherType, 0x894F, has been allocated
> for
> > NSH'. I could not find this value in the tables displayed by the IEEE
> > Registration Authority (RAC) - for example at
> > http://standards-oui.ieee.org/ethertype/eth.txt. Neither does IANA at
> > https://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xhtm=
l
> (which
> > would not be in any case the authoritative source). Can you please
> indicate the
> > source that this is indeed a confirmed IEEE EtherType registration.
>
> I am not sure how often that page is updated, but the same link you
> include, http://standards-oui.ieee.org/ethertype/eth.txt, shows:
>
> 0x894F
> 894F: NSH (Network Service Header). Reference: draft-ietf-sfc-nsh-18
>
> Granted, that registration will be updated with the RFC number instead of
> the I-D, when it publishes.
>
> >
> > 2. Section 5 refers to ietf-rtgwg-dt-encap which is expired. If I
> understand
> > correctly the status of this work, there is a design team in place in t=
he
> > Routing Area created to look at common issues for the different data
> plane
> > encapsulations being discussed in various WGs including SFC. This leave=
s
> the
> > issue unsettled at this stage and this may be a problem for a standards
> track
> > document. I suggest that first the reference to the expired document is
> > removed, second that the issue is marked as 'open' and subject for
> future work.
> >
>
> Good suggestion. Instead of removing the reference all together, we can
> mark it as exemplifying of one approach.
>
> > Minor issues:
> >
> > 1.  Two values 'Experiment 1' and 'Experiment 2' are defined in section
> 2.2 and
> > 11.2.5 for the Next Protocol. This seems a little odd. Why 2? Why are
> they
> > defined at the end of the range? Maybe there is an explanation for thos=
e
> who
> > know the history but for an un-initiated reader or a future implementer
> this
> > seems odd.
>
> There is no strong rational behind the number of values (two) or the
> location (towards the end of the range). There are two values as it seems
> appropriate given the same of the number space (2 out of 256).
>
> Perhaps, it=E2=80=99s somewhat following common practice started at
> https://tools.ietf.org/html/rfc3692#section-2.1 (2 values for and 8-bit
> field, closer to the end).
>
> >
> > 2. In Section 2.2 I see:
> >
> >> All other flag fields, marked U, are unassigned and available for
> >   future use, see Section 11.2.1.  Unassigned bits MUST be set to zero
> >   upon origination, and MUST be ignored and preserved unmodified by
> >   other NSH supporting elements.  Elements which do not understand the
> >   meaning of any of these bits MUST NOT modify their actions based on
> >   those unknown bits.
> >
> > The way the last sentence is written it seems to open the path for
> elements
> > that claim to 'understand' the meaning of some Unassigned bit to modify
> its
> > behavior based upon it. This does not seem good, as at transmission all
> > Unassigned bits MUST be set to zero. I would suggest to make the
> statement
> > simpler and just say that at reception all elements MUST NOT modify the=
ir
> > actions based on these bits.
> >
>
> Very good point, and good improvement. Applied.
>
> > 3. In Section 2.2 I see:
> >
> >> 0xF - This value is reserved for experimentation and testing, as per
> >   [RFC3692].  Implementations not explicitly configured to be part of
> >   an experiment SHOULD silently discard packets with MD Type 0xF.
> >
> > Why is this a SHOULD and not a MUST?
> >
>
> To use MUSTs very sparingly and leave a little bit of leeway for
> experimentation, following appropriate justification.
>
> > 4. I believe that  [I-D.ietf-sfc-control-plane] needs to be a Normative
> > Reference. There are several places in the document (e.g. in Section
> 2.3) where
> > this document is referred to describe behavior or actions related to th=
e
> fields
> > of the header.
> >
>
> The control plane I-D is, by WG decision, intended to not be normative as
> NSH is the data plane independent of the CP spec.
>
> I see that [I-D.ietf-sfc-control-plane] is cited in two places:
>
> 1.
>        [I-D.ietf-sfc-control-plane] provides an example of such in
>
> 2.
>    process.  These considerations are deployment-specific.  However, the
>    control plane is entitled to instruct SFC-aware SFs with the data
>    structure of context header together with its scoping (see
>    Section 3.3.3 of [I-D.ietf-sfc-control-plane]).
>
>
> We already caught the issue with #2 and changed it to, in our working cop=
y
> working with the chairs, to:
>
>    process.  These considerations are deployment-specific.  However, the
>    control plane is entitled to instruct SFC-aware SFs with the data
>    structure of context header together with its scoping (see e.g.,
>    Section 3.3.3 of [I-D.ietf-sfc-control-plane]).
>
> As that=E2=80=99s one possible, and non-normative way, out of many ways.
>
> > 5. The version number has only two bits assigned. Moreover, this docume=
nt
> > reserves already two values without any explanation why (only 00 is
> mandatory
> > to use, as far as I understand). This needs to be explained (maybe
> 'historical'
> > reasons - but unclear for future readers and users) and may be a
> limitation as
> > the protocol develops.
>
> The version field is indeed a two-bit field. One reserved and will not be
> used. One used by this spec, and two unassigned ones.
>
> We really expect to not be bumping up version number ofter =E2=80=94 or e=
ver=E2=80=A6
>
> >
> > Nits/editorial comments:
> >
> > 1. Please make sure that acronyms are expanded at first occurrence (e.g=
.
> ECMP)
> > and if necessary appropriate references are being provided.
> >
>
> Ack =E2=80=94 done.
>
> Thanks again!
>
> Carlos.
>
> >
>
>

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

<div dir=3D"ltr"><div><div><div>Hi Carlos,<br><br></div>Thank you for addre=
ssing my comments. Your suggested edits seem to address the issues. <br><br=
></div>Regards,<br><br></div>Dan<br><br></div><div class=3D"gmail_extra"><b=
r><div class=3D"gmail_quote">On Fri, Sep 1, 2017 at 3:55 AM, Carlos Pignata=
ro (cpignata) <span dir=3D"ltr">&lt;<a href=3D"mailto:cpignata@cisco.com" t=
arget=3D"_blank">cpignata@cisco.com</a>&gt;</span> wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">Hi, Dan,<br>
<br>
Many thanks for your detailed and valuable review, and apologies for the de=
lay in Ack-ing and responding.<br>
<br>
Please see inline.<br>
<br>
=E2=80=94<br>
Carlos Pignataro, <a href=3D"mailto:carlos@cisco.com">carlos@cisco.com</a><=
br>
<br>
=E2=80=9CSometimes I use big words that I do not fully understand, to make =
myself sound more photosynthesis.&quot;<br>
<span class=3D""><br>
&gt; On Aug 22, 2017, at 11:34 AM, Dan Romascanu &lt;<a href=3D"mailto:drom=
asca@gmail.com">dromasca@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Reviewer: Dan Romascanu<br>
&gt; Review result: Almost Ready<br>
&gt;<br>
&gt; I am the assigned Gen-ART reviewer for this draft. The General Area<br=
>
&gt; Review Team (Gen-ART) reviews all IETF documents being processed<br>
&gt; by the IESG for the IETF Chair.=C2=A0 Please treat these comments just=
<br>
&gt; like any other last call comments.<br>
&gt;<br>
&gt; For more information, please see the FAQ at<br>
&gt;<br>
&gt; &lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" rel=3D"n=
oreferrer" target=3D"_blank">https://trac.ietf.org/trac/<wbr>gen/wiki/GenAr=
tfaq</a>&gt;.<br>
&gt;<br>
&gt; Document: draft-ietf-sfc-nsh-19<br>
&gt; Reviewer: Dan Romascanu<br>
&gt; Review Date: 2017-08-22<br>
&gt; IETF LC End Date: 2017-08-25<br>
&gt; IESG Telechat date: 2017-09-14<br>
&gt;<br>
&gt; Summary:<br>
&gt;<br>
&gt; This document describes the header (called Network Service Header - NS=
H) to be<br>
&gt; inserted in packets and frames in order to create packets and frames t=
hat<br>
&gt; realize service functions described by other SFC documents. It needs t=
o be read<br>
&gt; in conjunction with RFC 7665 and other documents as the SFC control pl=
ane I-D<br>
&gt; in order to make sense of the required functionality. This part of the=
 SFC<br>
&gt; solution seems almost ready, but a few issues mentioned below need in =
my<br>
&gt; opinion clarification before the document is approved.<br>
<br>
</span>Thank you for this summary =E2=80=94 you raise good points.<br>
<span class=3D""><br>
&gt;<br>
&gt; Major issues:<br>
&gt;<br>
&gt; 1. Section 11.1 claims: &#39;An IEEE EtherType, 0x894F, has been alloc=
ated for<br>
&gt; NSH&#39;. I could not find this value in the tables displayed by the I=
EEE<br>
&gt; Registration Authority (RAC) - for example at<br>
&gt; <a href=3D"http://standards-oui.ieee.org/ethertype/eth.txt" rel=3D"nor=
eferrer" target=3D"_blank">http://standards-oui.ieee.org/<wbr>ethertype/eth=
.txt</a>. Neither does IANA at<br>
&gt; <a href=3D"https://www.iana.org/assignments/ieee-802-numbers/ieee-802-=
numbers.xhtml" rel=3D"noreferrer" target=3D"_blank">https://www.iana.org/<w=
br>assignments/ieee-802-numbers/<wbr>ieee-802-numbers.xhtml</a> (which<br>
&gt; would not be in any case the authoritative source). Can you please ind=
icate the<br>
&gt; source that this is indeed a confirmed IEEE EtherType registration.<br=
>
<br>
</span>I am not sure how often that page is updated, but the same link you =
include, <a href=3D"http://standards-oui.ieee.org/ethertype/eth.txt" rel=3D=
"noreferrer" target=3D"_blank">http://standards-oui.ieee.org/<wbr>ethertype=
/eth.txt</a>, shows:<br>
<br>
0x894F<br>
894F: NSH (Network Service Header). Reference: draft-ietf-sfc-nsh-18<br>
<br>
Granted, that registration will be updated with the RFC number instead of t=
he I-D, when it publishes.<br>
<span class=3D""><br>
&gt;<br>
&gt; 2. Section 5 refers to ietf-rtgwg-dt-encap which is expired. If I unde=
rstand<br>
&gt; correctly the status of this work, there is a design team in place in =
the<br>
&gt; Routing Area created to look at common issues for the different data p=
lane<br>
&gt; encapsulations being discussed in various WGs including SFC. This leav=
es the<br>
&gt; issue unsettled at this stage and this may be a problem for a standard=
s track<br>
&gt; document. I suggest that first the reference to the expired document i=
s<br>
&gt; removed, second that the issue is marked as &#39;open&#39; and subject=
 for future work.<br>
&gt;<br>
<br>
</span>Good suggestion. Instead of removing the reference all together, we =
can mark it as exemplifying of one approach.<br>
<span class=3D""><br>
&gt; Minor issues:<br>
&gt;<br>
&gt; 1.=C2=A0 Two values &#39;Experiment 1&#39; and &#39;Experiment 2&#39; =
are defined in section 2.2 and<br>
&gt; 11.2.5 for the Next Protocol. This seems a little odd. Why 2? Why are =
they<br>
&gt; defined at the end of the range? Maybe there is an explanation for tho=
se who<br>
&gt; know the history but for an un-initiated reader or a future implemente=
r this<br>
&gt; seems odd.<br>
<br>
</span>There is no strong rational behind the number of values (two) or the=
 location (towards the end of the range). There are two values as it seems =
appropriate given the same of the number space (2 out of 256).<br>
<br>
Perhaps, it=E2=80=99s somewhat following common practice started at <a href=
=3D"https://tools.ietf.org/html/rfc3692#section-2.1" rel=3D"noreferrer" tar=
get=3D"_blank">https://tools.ietf.org/html/<wbr>rfc3692#section-2.1</a> (2 =
values for and 8-bit field, closer to the end).<br>
<span class=3D""><br>
&gt;<br>
&gt; 2. In Section 2.2 I see:<br>
&gt;<br>
&gt;&gt; All other flag fields, marked U, are unassigned and available for<=
br>
&gt;=C2=A0 =C2=A0future use, see Section 11.2.1.=C2=A0 Unassigned bits MUST=
 be set to zero<br>
&gt;=C2=A0 =C2=A0upon origination, and MUST be ignored and preserved unmodi=
fied by<br>
&gt;=C2=A0 =C2=A0other NSH supporting elements.=C2=A0 Elements which do not=
 understand the<br>
&gt;=C2=A0 =C2=A0meaning of any of these bits MUST NOT modify their actions=
 based on<br>
&gt;=C2=A0 =C2=A0those unknown bits.<br>
&gt;<br>
&gt; The way the last sentence is written it seems to open the path for ele=
ments<br>
&gt; that claim to &#39;understand&#39; the meaning of some Unassigned bit =
to modify its<br>
&gt; behavior based upon it. This does not seem good, as at transmission al=
l<br>
&gt; Unassigned bits MUST be set to zero. I would suggest to make the state=
ment<br>
&gt; simpler and just say that at reception all elements MUST NOT modify th=
eir<br>
&gt; actions based on these bits.<br>
&gt;<br>
<br>
</span>Very good point, and good improvement. Applied.<br>
<span class=3D""><br>
&gt; 3. In Section 2.2 I see:<br>
&gt;<br>
&gt;&gt; 0xF - This value is reserved for experimentation and testing, as p=
er<br>
&gt;=C2=A0 =C2=A0[RFC3692].=C2=A0 Implementations not explicitly configured=
 to be part of<br>
&gt;=C2=A0 =C2=A0an experiment SHOULD silently discard packets with MD Type=
 0xF.<br>
&gt;<br>
&gt; Why is this a SHOULD and not a MUST?<br>
&gt;<br>
<br>
</span>To use MUSTs very sparingly and leave a little bit of leeway for exp=
erimentation, following appropriate justification.<br>
<span class=3D""><br>
&gt; 4. I believe that=C2=A0 [I-D.ietf-sfc-control-plane] needs to be a Nor=
mative<br>
&gt; Reference. There are several places in the document (e.g. in Section 2=
.3) where<br>
&gt; this document is referred to describe behavior or actions related to t=
he fields<br>
&gt; of the header.<br>
&gt;<br>
<br>
</span>The control plane I-D is, by WG decision, intended to not be normati=
ve as NSH is the data plane independent of the CP spec.<br>
<br>
I see that [I-D.ietf-sfc-control-plane] is cited in two places:<br>
<br>
1.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0[I-D.ietf-sfc-control-plane] provides an example=
 of such in<br>
<br>
2.<br>
=C2=A0 =C2=A0process.=C2=A0 These considerations are deployment-specific.=
=C2=A0 However, the<br>
=C2=A0 =C2=A0control plane is entitled to instruct SFC-aware SFs with the d=
ata<br>
=C2=A0 =C2=A0structure of context header together with its scoping (see<br>
=C2=A0 =C2=A0Section 3.3.3 of [I-D.ietf-sfc-control-plane]).<br>
<br>
<br>
We already caught the issue with #2 and changed it to, in our working copy =
working with the chairs, to:<br>
<br>
=C2=A0 =C2=A0process.=C2=A0 These considerations are deployment-specific.=
=C2=A0 However, the<br>
=C2=A0 =C2=A0control plane is entitled to instruct SFC-aware SFs with the d=
ata<br>
=C2=A0 =C2=A0structure of context header together with its scoping (see e.g=
.,<br>
=C2=A0 =C2=A0Section 3.3.3 of [I-D.ietf-sfc-control-plane]).<br>
<br>
As that=E2=80=99s one possible, and non-normative way, out of many ways.<br=
>
<span class=3D""><br>
&gt; 5. The version number has only two bits assigned. Moreover, this docum=
ent<br>
&gt; reserves already two values without any explanation why (only 00 is ma=
ndatory<br>
&gt; to use, as far as I understand). This needs to be explained (maybe &#3=
9;historical&#39;<br>
&gt; reasons - but unclear for future readers and users) and may be a limit=
ation as<br>
&gt; the protocol develops.<br>
<br>
</span>The version field is indeed a two-bit field. One reserved and will n=
ot be used. One used by this spec, and two unassigned ones.<br>
<br>
We really expect to not be bumping up version number ofter =E2=80=94 or eve=
r=E2=80=A6<br>
<span class=3D""><br>
&gt;<br>
&gt; Nits/editorial comments:<br>
&gt;<br>
&gt; 1. Please make sure that acronyms are expanded at first occurrence (e.=
g. ECMP)<br>
&gt; and if necessary appropriate references are being provided.<br>
&gt;<br>
<br>
</span>Ack =E2=80=94 done.<br>
<br>
Thanks again!<br>
<br>
Carlos.<br>
<br>
&gt;<br>
<br>
</blockquote></div><br></div>

--94eb2c085986c1b7b1055818c0ff--


From nobody Thu Aug 31 21:26:06 2017
Return-Path: <cpignata@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87E631326EA; Thu, 31 Aug 2017 21:25:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level: 
X-Spam-Status: No, score=-14.521 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lNj4CJnTsBpU; Thu, 31 Aug 2017 21:25:56 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BD53132F2F; Thu, 31 Aug 2017 21:25:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5526; q=dns/txt; s=iport; t=1504239956; x=1505449556; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=18h61dS+FxVOuwa2vAS4aWU0I5nVf4za32bc6WH2Ilg=; b=IUnhg1LDHNtslITwBCaTGjBrP1QpXgQ5Oo8WqG0a3yTrrvN/u6iZ4ZWi ftAHhP+61LjORc4crTulpc+/b0og/Id4rZwPemOapl9iXBzUP7SCQYjsn F1x3T/6s5gLbGlCUAdxk9hDOHH8x6wN3BRvFGHYsz8anrLPOCk6Zbgeao o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C+AAAF4ahZ/51dJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1qBeQeOEJAfgU8ilieCEoVHAhqDdT8YAQIBAQEBAQEBayiFGAE?= =?us-ascii?q?BAQECASMRMxIFCwIBCA4KAgImAgICMBUQAgQOBYopCK9PgieLYgEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBHoENgh2CAoFOgg4LgnKEdYMTMIIxBYl1jjyIPgKUT4IThWe?= =?us-ascii?q?KdIocjCgBHziBDXcVWwGFBRyBZ3aJT4EPAQEB?=
X-IronPort-AV: E=Sophos;i="5.41,456,1498521600"; d="scan'208";a="474880743"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Sep 2017 04:25:45 +0000
Received: from XCH-RTP-018.cisco.com (xch-rtp-018.cisco.com [64.101.220.158]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id v814PjAx024706 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 1 Sep 2017 04:25:45 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-018.cisco.com (64.101.220.158) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 1 Sep 2017 00:25:44 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1263.000; Fri, 1 Sep 2017 00:25:44 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Wesley Eddy <wes@mti-systems.com>
CC: "tsv-art@ietf.org" <tsv-art@ietf.org>, IETF Discuss <ietf@ietf.org>, Service Function Chaining IETF list <sfc@ietf.org>, "draft-ietf-sfc-nsh.all@ietf.org" <draft-ietf-sfc-nsh.all@ietf.org>
Subject: Re: Tsvart last call review of draft-ietf-sfc-nsh-19
Thread-Topic: Tsvart last call review of draft-ietf-sfc-nsh-19
Thread-Index: AQHTG3ZXOtnqynvgGkaCoRatoAbe6qKfwOGA
Date: Fri, 1 Sep 2017 04:25:44 +0000
Message-ID: <55F080C0-5639-4CE7-B5E2-8F86665CB617@cisco.com>
References: <150342731718.6066.9872092086965343963@ietfa.amsl.com>
In-Reply-To: <150342731718.6066.9872092086965343963@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.116.133]
Content-Type: text/plain; charset="utf-8"
Content-ID: <37C63ACB55306B459192FCE044B30F02@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mAzD9H1ljLNQpOlDt3FtSFCaA0w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Sep 2017 04:25:59 -0000

SGVsbG8sIFdlc2xleSwNCg0KVGhhbmtzIGZvciB0aGUgcmV2aWV3ISBQbGVhc2UgZmluZCBzb21l
IGZvbGxvdy11cHMgaW5saW5lLg0KDQrigJQNCkNhcmxvcyBQaWduYXRhcm8sIGNhcmxvc0BjaXNj
by5jb20NCg0K4oCcU29tZXRpbWVzIEkgdXNlIGJpZyB3b3JkcyB0aGF0IEkgZG8gbm90IGZ1bGx5
IHVuZGVyc3RhbmQsIHRvIG1ha2UgbXlzZWxmIHNvdW5kIG1vcmUgcGhvdG9zeW50aGVzaXMuIg0K
DQo+IE9uIEF1ZyAyMiwgMjAxNywgYXQgMjo0MSBQTSwgV2VzbGV5IEVkZHkgPHdlc0BtdGktc3lz
dGVtcy5jb20+IHdyb3RlOg0KPiANCj4gUmV2aWV3ZXI6IFdlc2xleSBFZGR5DQo+IFJldmlldyBy
ZXN1bHQ6IE5vdCBSZWFkeQ0KPiANCj4gSW4gZ2VuZXJhbCwgdGhlIGRvY3VtZW50IGRlc2NyaWJl
cyB0aGUgTlNIIHN0cnVjdHVyZSBhbmQgc29tZSBsb29zZSBleGFtcGxlcyBvZg0KPiBob3cgaXQg
bWlnaHQgYmUgdXNlZCwgYnV0IHRoaXMgaXNuJ3QgYSB2ZXJ5IGNsZWFyIHByb3RvY29sIHNwZWNp
ZmljYXRpb24uICBJdCdzDQo+IG1vc3RseSBqdXN0IGFib3V0IE5TSCBmb3JtYXQgYW5kIGxlc3Mg
b24gdGhlIGV4cGVjdGVkIGJlaGF2aW9ycyBvZiBOU0gNCj4gc3BlYWtlcnMsIGhvdyB0byBtYWlu
dGFpbiBzdGF0ZSBvZiB0aGUgTlNIIHBlZXJzIG9yIG90aGVyIGRhdGEgc3RydWN0dXJlcywgZXRj
Lg0KPiBJdCBzZWVtcyBsaWtlIHRoZXJlIGNvdWxkIGVhc2lseSBiZSBwcm9ibGVtcyBpbiBpbnRl
cm9wZXJhdGlvbnMgYmV0d2Vlbg0KPiB2ZW5kb3JzIGNvZGluZyBzb2xlbHkgYmFzZWQgb24gdGhl
IGRvY3VtZW50Lg0KPiANCj4gU2VjdGlvbiA1IG9uIGZyYWdtZW50YXRpb24gY29uc2lkZXJhdGlv
bnMgaXMgbmVidWxvdXMgYW5kIGhhcyB0ZWNobmljYWwgaXNzdWVzLg0KPiBTcGVjaWZpY2FsbHks
IGl0IHNheXMgdGhhdCBQTVRVRCBzaG91bGQgYmUgdXNlZCB3aGVuIE5TSCBpcyBlbmNhcHN1bGF0
ZWQgaW4NCj4gSVAuICBQTVRVRCByZXF1aXJlcyBJQ01QIHRvIHdvcmssIGFuZCBoYXMga25vd24g
aXNzdWVzIHdoZW4gSUNNUCBpcyBibG9ja2VkIGluDQo+IHRoZSBwYXRoLg0KDQpQbGVhc2Ugbm90
ZSB0aGF0IHRoaXMgc3BlY2lmaWNhdGlvbiBpcyBzY29wZWQgdG8gd2l0aGluIGEgbWFuYWdlbWVu
dCBkb21haW4sIGFuZCBub3QgdGhlIG9wZW4gSW50ZXJuZXQuDQoNCkFzIHN1Y2gsIHRoZSBleHBl
Y3RhdGlvbiBpcyB0aGF0IHRoZSAybmQgcGFyYWdyYXBoIG9mIFNlY3Rpb24gNSBzdWZmaWNlcy4g
QW5kIHdpdGhpbiBzYWlkIGFkbWluaXN0cmF0aXZlIGRvbWFpbiwgaXQgaXMgYWxzbyBleHBlY3Rl
ZCB0aGF0IElDTVBzIHdpbGwgbm90IGJlIGJsb2NrZWQgKGV2ZW4gd2hlbiB0aGV5IGFyZSB1bnJl
bGlhYmxlIGJ5IG5hdHVyZSkuDQoNCj4gIElzIHRoZXJlIGEgcmVxdWlyZW1lbnQgaXMgU0ZDIG5l
dHdvcmtzIHJ1bm5pbmcgTlNIIHRoYXQgSUNNUCBuZWVkcw0KPiB0byBiZSBjYXJyaWVkIGJ5IHRo
ZSBuZXR3b3JrPyAgRnVydGhlciwgdGhlcmUgaXMgbm8gZGlzY3Vzc2lvbiBoZXJlIG9uIFBMUE1U
VUQNCj4gdmVyc3VzIFBNVFVELCBub3IgcmVmZXJlbmNlIHRvIHRoZSBzcGVjaWZpYyBSRkNzLCBh
bGdvcml0aG1zLCBhbmQgb3B0aW9ucyBvcg0KPiBjb25maWd1cmF0aW9uIHBhcmFtZXRlcnMgc3Vn
Z2VzdGVkIHRvIGRvIHRoaXMgcHJvcGVybHkgaW4gU0ZDIHN5c3RlbXMuDQoNClRoZXJlIGlzIG5v
IHJlcXVpcmVtZW50IHRoYW4gSUNNUCBpcyBjYXJyaWVkIGJ5IHRoZSBuZXR3b3JrLCBzaW5jZSBO
U0ggY2FuIHJ1biBkaXJlY3RseSBvdmVyIEV0aGVybmV0IGZvciBleGFtcGxlLg0KDQpGdXJ0aGVy
LCBub3RlIHRoYXQgdGhlIHJlbGV2YW50IHNlbnRlbmNlIGJlZ2luczoNCuKAnCAgIEZvciBleGFt
cGxlLCB3aGVuIHRoZSBOU0ggaXMgZW5jYXBzdWxhdGVkIGluIElQLCBJUC1sZXZlbCINCk1ha2lu
ZyBpdCBhbiBleGFtcGxlIGFuZCBub3QgYSBub3JtYXRpdmUgYnJvYWQgcmVxdWlyZW1lbnQuDQoN
ClBMUE1UVUQgaXMgbm90IG1lbnRpb25lZCBzaW5jZSB0aGVyZSBpcyBubyBUQ1AgYW5kIG5vIG90
aGVyIHBhY2tldGl6YXRpb24gbGF5ZXIgZm9yIHdoaWNoLCB0byBteSBrbm93bGVkZ2UsIFBMUE1U
VUQgaXMgc3BlY2lmaWVkLg0KDQo+IA0KPiBJbiBTZWN0aW9uIDYsIHRoZSBhc3N1bXB0aW9ucywg
ZXhwZWN0YXRpb25zLCBvciBoYXJkIHJlcXVpcmVtZW50cyBmb3IgbWFwcGluZw0KPiBOU0ggb250
byBhbiB1bmRlcmx5aW5nICJ0cmFuc3BvcnQiIGFyZSBub3QgdmVyeSBjbGVhci4gIE9ubHkgZXhh
bXBsZXMgYXJlDQo+IGdpdmVuLCBhbmQgc29tZSBvZiB0aGVzZSAoZS5nLiBFdGhlcm5ldCkgYXJl
IG5vdCBjYXBhYmxlIG9mIGRvaW5nIHRoaW5ncyBsaWtlDQo+IGRldGVjdGluZyBmcmFnbWVudGF0
aW9uIGlzc3Vlcy4gIE90aGVyIGV4YW1wbGVzIChlLmcuIEdSRSkgYXJlIHR1bm5lbHMgd2hlcmUN
Cj4gdGhlcmUgbWF5IGJlIG1vcmUgc3RhdGUuICBUaGVyZSBpcyBubyBkaXNjdXNzaW9uIGFib3V0
IHdoZXRoZXIgdGhlcmUgYXJlDQo+IGFzc3VtcHRpb25zIGFib3V0IHBhY2tldCBvcmRlcmluZy9y
ZW9yZGVyaW5nLCBkdXBsaWNhdGlvbiwgbG9zc2VzLCBjb3JydXB0aW9uLA0KPiBldGMuDQoNCkkg
dGhpbmsgeW91IGhhdmUgYSBnb29kIHBvaW50IGhlcmUgaW4gZW5jbG9zaW5nIOKAnHRyYW5zcG9y
dOKAnSB3aXRoaW4gcXVvdGVzLiBXaGF0IGlzIG1lYW50IGhlcmUgaXMgYW4gZW5jYXBzdWxhdGlv
biwgYW5kIG5vdCBhIHRyYW5zcG9ydCBpbiB0aGUgVFNWIHNlbnNlIG9mIHRoZSB0ZXJtLg0KDQpX
ZSBjYW4gdXNlIG1vcmUgcHJlY2lzaW9uIG9uIHRoaXMuIFdvdWxkIHRoYXQgaGVscCBhIGJpdD8N
Cg0KPiANCj4gSXQgaXNuJ3QgY2xlYXIgd2h5IHRoZSBwYXJ0aWN1bGFyIGVuY2Fwc3VsYXRpb25z
IGRpc2N1c3NlZCBoYXZlIGJlZW4gY2hvc2VuDQo+IHJhdGhlciB0aGFuIFVEUCBvciBUQ1AtYmFz
ZWQgb3B0aW9ucy4NCj4gDQoNClRoZSBtYXJrZXQgY2hvc2UgdGhvc2UuIE5vdGUgdGhhdCB0aGVy
ZSBhcmUgVURQLWJhc2VkIG9wdGlvbnMsIHN1Y2ggYXMgVnhsYW4tZ3BlLg0KDQo+IFRoZXJlIHNo
b3VsZCBwcm9iYWJseSBiZSBtb3JlIGRpc2N1c3Npb24gYWJvdXQgd2hhdCB0eXBlcyBvZiBuZXR3
b3JrIHBhdGhzIE5TSA0KPiBpcyBzdWl0YWJsZSBmb3IgYW5kIHRoYXQgdGhlIGNob2ljZSBvZiBh
biBlbmNhcHN1bGF0aW9uIGZvciBOU0ggbmVlZHMgdG8gYmUNCj4gYXBwcm9wcmlhdGUgdG8gdGhl
IHVuZGVybHlpbmcgcGF0aCBiZXR3ZWVuIHNlcnZpY2UgZW50aXRpZXMuICBTb21lDQo+IGVuY2Fw
c3VsYXRpb25zIHdpbGwgbmVlZCB0byBiZSB0dW5lZCBmb3IgdGhlIGNvbWJpbmF0aW9uIG9mIHBh
dGggYW5kIG9mZmVyZWQNCj4gbG9hZCBvZiB0cmFmZmljLiAgU29tZSBjYW4gcHJvdmlkZSBtdWNo
IG1vcmUgZmVlZGJhY2sgdG8gdGhlIE5TSCAibGF5ZXIiIHRoYW4NCj4gb3RoZXJzIHRoYXQgYXJl
IG1haW5seSBvcGVuLWxvb3AuDQoNClNpbmNlIHRoZXJlIGFyZSBubyByZXF1aXJlbWVudCBvZiB0
aGUgdW5kZXJseWluZyBsYXllciwgbm8gcGFydGljdWxhciBmZWVkYmFjayBuZWVkZWQuDQoNCj4g
DQo+IFByb3BhZ2F0aW9uIG9mIGVycm9ycyB0aHJvdWdoIGEgc2VydmljZSBmdW5jdGlvbiBjaGFp
biBvciBzaWduYWxpbmcgb2YgZXJyb3JzDQo+IGJhY2t3YXJkcyBvbiBhIGNoYWluIHNlZW1zIGxp
a2UgaXQgYmVhcnMgZnVydGhlciBkaXNjdXNzaW9uLg0KPiANCj4gDQoNCk9BTSwgd2hpY2ggaW5j
bHVkZXMgcHJvcGFnYXRpb24gb2YgZXJyb3JzLCBpcyBleHBsaWNpdGx5IG91dHNpZGUgdGhlIHNj
b3BlIG9mIHRoaXMgc3BlYyAoc2VlIE8gYml0IGRlZmluaXRpb24pLg0KDQpJIHdvdWxkIGxpa2Ug
dG8gaGVhciB5b3VyIGZlZWRiYWNrIChhbmQsIGlkZWFsbHksIHNwZWNpZmljIHJlY29tbWVuZGF0
aW9ucyBhbmQgc3VnZ2VzdGlvbnMpIHJlZ2FyZGluZyB0aGUgdXNlIG9mIOKAnHRyYW5zcG9ydOKA
nSBpbiBTZWN0aW9uIDYuDQoNClRoYW5rcyENCg0K4oCUIENhcmxvcy4NCg0KDQo=


From nobody Thu Aug 31 21:28:58 2017
Return-Path: <cpignata@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7D1D126BF0; Thu, 31 Aug 2017 21:28:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level: 
X-Spam-Status: No, score=-14.52 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U-CKjdH6V1KY; Thu, 31 Aug 2017 21:28:52 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F75D132EE3; Thu, 31 Aug 2017 21:28:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=29084; q=dns/txt; s=iport; t=1504240132; x=1505449732; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=dxBhhaWKG0DrfEQN7KtuIqRswE0UuL5GaEZ1z5BoBfE=; b=UYuqsYiB75Gnsj+H/xjQH+QJmtfw9ky4+sGp5CHUQoAs62MQFFOPSPOs 3b36jKCq8+zlF1rPDEk9GMa/xLfmZCnuh8v+VXjXXF4fKF0dhvDGOR6P5 n/v769CxBQ1V5f0dYVD93S+3R57/IN+bdIL7dOq/McINCo/2X3ZUA9f7P 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C/AAAF4ahZ/5ldJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1pkgRUHjhCQH4FPIoJwhUmNbg6CBC6FGQIag3U/GAECAQEBAQE?= =?us-ascii?q?BAWsohRkGI1EFEAIBCA4GKwMCAgIfERQRAgQOBRuJMkwDFRCvP4InhzsNhBoBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAQEdgyqCAoFOgWMrC4JygleCBjiCczCCMQWJe4k?= =?us-ascii?q?RhSWIAjwCh1mDWoQmhHaCE4Vng32Gd4xOiXYBDxA4gQ13FVsBhwh2AYlOgQ8BA?= =?us-ascii?q?QE?=
X-IronPort-AV: E=Sophos;i="5.41,456,1498521600";  d="scan'208,217";a="479886876"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Sep 2017 04:28:51 +0000
Received: from XCH-RTP-020.cisco.com (xch-rtp-020.cisco.com [64.101.220.160]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v814SoKR005074 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 1 Sep 2017 04:28:51 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-020.cisco.com (64.101.220.160) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 1 Sep 2017 00:28:50 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1263.000; Fri, 1 Sep 2017 00:28:50 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Dan Romascanu <dromasca@gmail.com>
CC: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Service Function Chaining IETF list <sfc@ietf.org>, "draft-ietf-sfc-nsh.all@ietf.org" <draft-ietf-sfc-nsh.all@ietf.org>
Subject: Re: Genart last call review of draft-ietf-sfc-nsh-19
Thread-Topic: Genart last call review of draft-ietf-sfc-nsh-19
Thread-Index: AQHTG1wXf572axcqxkiCBrPJS5Tss6KfhneAgAAyl4CAAAjkAA==
Date: Fri, 1 Sep 2017 04:28:49 +0000
Message-ID: <7BB49936-077F-4909-82BB-C9976C03C4AE@cisco.com>
References: <150341604132.6021.14134855950693780483@ietfa.amsl.com> <780ED7FA-6417-40A8-8524-69887C3AB161@cisco.com> <CAFgnS4XoR7eqW=+4i63Q=YGdqOVGCkBELkvfym_7kONtKKhaKg@mail.gmail.com>
In-Reply-To: <CAFgnS4XoR7eqW=+4i63Q=YGdqOVGCkBELkvfym_7kONtKKhaKg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.116.133]
Content-Type: multipart/alternative; boundary="_000_7BB49936077F490982BBC9976C03C4AEciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/S2ebsxkkz2A310irdlNgg9BtYvk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Sep 2017 04:28:56 -0000

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

VGhhbmtzIHRvIHlvdSwgRGFuIQ0KDQrigJQNCkNhcmxvcyBQaWduYXRhcm8sIGNhcmxvc0BjaXNj
by5jb208bWFpbHRvOmNhcmxvc0BjaXNjby5jb20+DQoNCuKAnFNvbWV0aW1lcyBJIHVzZSBiaWcg
d29yZHMgdGhhdCBJIGRvIG5vdCBmdWxseSB1bmRlcnN0YW5kLCB0byBtYWtlIG15c2VsZiBzb3Vu
ZCBtb3JlIHBob3Rvc3ludGhlc2lzLiINCg0KT24gQXVnIDMxLCAyMDE3LCBhdCAxMTo1NiBQTSwg
RGFuIFJvbWFzY2FudSA8ZHJvbWFzY2FAZ21haWwuY29tPG1haWx0bzpkcm9tYXNjYUBnbWFpbC5j
b20+PiB3cm90ZToNCg0KSGkgQ2FybG9zLA0KDQpUaGFuayB5b3UgZm9yIGFkZHJlc3NpbmcgbXkg
Y29tbWVudHMuIFlvdXIgc3VnZ2VzdGVkIGVkaXRzIHNlZW0gdG8gYWRkcmVzcw0KdGhlIGlzc3Vl
cy4NCg0KUmVnYXJkcywNCg0KRGFuDQoNCg0KT24gRnJpLCBTZXAgMSwgMjAxNyBhdCAzOjU1IEFN
LCBDYXJsb3MgUGlnbmF0YXJvIChjcGlnbmF0YSkgPA0KY3BpZ25hdGFAY2lzY28uY29tPG1haWx0
bzpjcGlnbmF0YUBjaXNjby5jb20+PiB3cm90ZToNCg0KSGksIERhbiwNCg0KTWFueSB0aGFua3Mg
Zm9yIHlvdXIgZGV0YWlsZWQgYW5kIHZhbHVhYmxlIHJldmlldywgYW5kIGFwb2xvZ2llcyBmb3Ig
dGhlDQpkZWxheSBpbiBBY2staW5nIGFuZCByZXNwb25kaW5nLg0KDQpQbGVhc2Ugc2VlIGlubGlu
ZS4NCg0K4oCUDQpDYXJsb3MgUGlnbmF0YXJvLCBjYXJsb3NAY2lzY28uY29tPG1haWx0bzpjYXJs
b3NAY2lzY28uY29tPg0KDQrigJxTb21ldGltZXMgSSB1c2UgYmlnIHdvcmRzIHRoYXQgSSBkbyBu
b3QgZnVsbHkgdW5kZXJzdGFuZCwgdG8gbWFrZSBteXNlbGYNCnNvdW5kIG1vcmUgcGhvdG9zeW50
aGVzaXMuIg0KDQpPbiBBdWcgMjIsIDIwMTcsIGF0IDExOjM0IEFNLCBEYW4gUm9tYXNjYW51IDxk
cm9tYXNjYUBnbWFpbC5jb208bWFpbHRvOmRyb21hc2NhQGdtYWlsLmNvbT4+IHdyb3RlOg0KDQpS
ZXZpZXdlcjogRGFuIFJvbWFzY2FudQ0KUmV2aWV3IHJlc3VsdDogQWxtb3N0IFJlYWR5DQoNCkkg
YW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5l
cmFsIEFyZWENClJldmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50
cyBiZWluZyBwcm9jZXNzZWQNCmJ5IHRoZSBJRVNHIGZvciB0aGUgSUVURiBDaGFpci4gIFBsZWFz
ZSB0cmVhdCB0aGVzZSBjb21tZW50cyBqdXN0DQpsaWtlIGFueSBvdGhlciBsYXN0IGNhbGwgY29t
bWVudHMuDQoNCkZvciBtb3JlIGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQNCg0K
PGh0dHBzOi8vdHJhYy5pZXRmLm9yZy90cmFjL2dlbi93aWtpL0dlbkFydGZhcT4uDQoNCkRvY3Vt
ZW50OiBkcmFmdC1pZXRmLXNmYy1uc2gtMTkNClJldmlld2VyOiBEYW4gUm9tYXNjYW51DQpSZXZp
ZXcgRGF0ZTogMjAxNy0wOC0yMg0KSUVURiBMQyBFbmQgRGF0ZTogMjAxNy0wOC0yNQ0KSUVTRyBU
ZWxlY2hhdCBkYXRlOiAyMDE3LTA5LTE0DQoNClN1bW1hcnk6DQoNClRoaXMgZG9jdW1lbnQgZGVz
Y3JpYmVzIHRoZSBoZWFkZXIgKGNhbGxlZCBOZXR3b3JrIFNlcnZpY2UgSGVhZGVyIC0gTlNIKQ0K
dG8gYmUNCmluc2VydGVkIGluIHBhY2tldHMgYW5kIGZyYW1lcyBpbiBvcmRlciB0byBjcmVhdGUg
cGFja2V0cyBhbmQgZnJhbWVzIHRoYXQNCnJlYWxpemUgc2VydmljZSBmdW5jdGlvbnMgZGVzY3Jp
YmVkIGJ5IG90aGVyIFNGQyBkb2N1bWVudHMuIEl0IG5lZWRzIHRvDQpiZSByZWFkDQppbiBjb25q
dW5jdGlvbiB3aXRoIFJGQyA3NjY1IGFuZCBvdGhlciBkb2N1bWVudHMgYXMgdGhlIFNGQyBjb250
cm9sDQpwbGFuZSBJLUQNCmluIG9yZGVyIHRvIG1ha2Ugc2Vuc2Ugb2YgdGhlIHJlcXVpcmVkIGZ1
bmN0aW9uYWxpdHkuIFRoaXMgcGFydCBvZiB0aGUNClNGQw0Kc29sdXRpb24gc2VlbXMgYWxtb3N0
IHJlYWR5LCBidXQgYSBmZXcgaXNzdWVzIG1lbnRpb25lZCBiZWxvdyBuZWVkIGluIG15DQpvcGlu
aW9uIGNsYXJpZmljYXRpb24gYmVmb3JlIHRoZSBkb2N1bWVudCBpcyBhcHByb3ZlZC4NCg0KVGhh
bmsgeW91IGZvciB0aGlzIHN1bW1hcnkg4oCUIHlvdSByYWlzZSBnb29kIHBvaW50cy4NCg0KDQpN
YWpvciBpc3N1ZXM6DQoNCjEuIFNlY3Rpb24gMTEuMSBjbGFpbXM6ICdBbiBJRUVFIEV0aGVyVHlw
ZSwgMHg4OTRGLCBoYXMgYmVlbiBhbGxvY2F0ZWQNCmZvcg0KTlNIJy4gSSBjb3VsZCBub3QgZmlu
ZCB0aGlzIHZhbHVlIGluIHRoZSB0YWJsZXMgZGlzcGxheWVkIGJ5IHRoZSBJRUVFDQpSZWdpc3Ry
YXRpb24gQXV0aG9yaXR5IChSQUMpIC0gZm9yIGV4YW1wbGUgYXQNCmh0dHA6Ly9zdGFuZGFyZHMt
b3VpLmllZWUub3JnL2V0aGVydHlwZS9ldGgudHh0LiBOZWl0aGVyIGRvZXMgSUFOQSBhdA0KaHR0
cHM6Ly93d3cuaWFuYS5vcmcvYXNzaWdubWVudHMvaWVlZS04MDItbnVtYmVycy9pZWVlLTgwMi1u
dW1iZXJzLnhodG1sDQood2hpY2gNCndvdWxkIG5vdCBiZSBpbiBhbnkgY2FzZSB0aGUgYXV0aG9y
aXRhdGl2ZSBzb3VyY2UpLiBDYW4geW91IHBsZWFzZQ0KaW5kaWNhdGUgdGhlDQpzb3VyY2UgdGhh
dCB0aGlzIGlzIGluZGVlZCBhIGNvbmZpcm1lZCBJRUVFIEV0aGVyVHlwZSByZWdpc3RyYXRpb24u
DQoNCkkgYW0gbm90IHN1cmUgaG93IG9mdGVuIHRoYXQgcGFnZSBpcyB1cGRhdGVkLCBidXQgdGhl
IHNhbWUgbGluayB5b3UNCmluY2x1ZGUsIGh0dHA6Ly9zdGFuZGFyZHMtb3VpLmllZWUub3JnL2V0
aGVydHlwZS9ldGgudHh0LCBzaG93czoNCg0KMHg4OTRGDQo4OTRGOiBOU0ggKE5ldHdvcmsgU2Vy
dmljZSBIZWFkZXIpLiBSZWZlcmVuY2U6IGRyYWZ0LWlldGYtc2ZjLW5zaC0xOA0KDQpHcmFudGVk
LCB0aGF0IHJlZ2lzdHJhdGlvbiB3aWxsIGJlIHVwZGF0ZWQgd2l0aCB0aGUgUkZDIG51bWJlciBp
bnN0ZWFkIG9mDQp0aGUgSS1ELCB3aGVuIGl0IHB1Ymxpc2hlcy4NCg0KDQoyLiBTZWN0aW9uIDUg
cmVmZXJzIHRvIGlldGYtcnRnd2ctZHQtZW5jYXAgd2hpY2ggaXMgZXhwaXJlZC4gSWYgSQ0KdW5k
ZXJzdGFuZA0KY29ycmVjdGx5IHRoZSBzdGF0dXMgb2YgdGhpcyB3b3JrLCB0aGVyZSBpcyBhIGRl
c2lnbiB0ZWFtIGluIHBsYWNlIGluIHRoZQ0KUm91dGluZyBBcmVhIGNyZWF0ZWQgdG8gbG9vayBh
dCBjb21tb24gaXNzdWVzIGZvciB0aGUgZGlmZmVyZW50IGRhdGENCnBsYW5lDQplbmNhcHN1bGF0
aW9ucyBiZWluZyBkaXNjdXNzZWQgaW4gdmFyaW91cyBXR3MgaW5jbHVkaW5nIFNGQy4gVGhpcyBs
ZWF2ZXMNCnRoZQ0KaXNzdWUgdW5zZXR0bGVkIGF0IHRoaXMgc3RhZ2UgYW5kIHRoaXMgbWF5IGJl
IGEgcHJvYmxlbSBmb3IgYSBzdGFuZGFyZHMNCnRyYWNrDQpkb2N1bWVudC4gSSBzdWdnZXN0IHRo
YXQgZmlyc3QgdGhlIHJlZmVyZW5jZSB0byB0aGUgZXhwaXJlZCBkb2N1bWVudCBpcw0KcmVtb3Zl
ZCwgc2Vjb25kIHRoYXQgdGhlIGlzc3VlIGlzIG1hcmtlZCBhcyAnb3BlbicgYW5kIHN1YmplY3Qg
Zm9yDQpmdXR1cmUgd29yay4NCg0KDQpHb29kIHN1Z2dlc3Rpb24uIEluc3RlYWQgb2YgcmVtb3Zp
bmcgdGhlIHJlZmVyZW5jZSBhbGwgdG9nZXRoZXIsIHdlIGNhbg0KbWFyayBpdCBhcyBleGVtcGxp
Znlpbmcgb2Ygb25lIGFwcHJvYWNoLg0KDQpNaW5vciBpc3N1ZXM6DQoNCjEuICBUd28gdmFsdWVz
ICdFeHBlcmltZW50IDEnIGFuZCAnRXhwZXJpbWVudCAyJyBhcmUgZGVmaW5lZCBpbiBzZWN0aW9u
DQoyLjIgYW5kDQoxMS4yLjUgZm9yIHRoZSBOZXh0IFByb3RvY29sLiBUaGlzIHNlZW1zIGEgbGl0
dGxlIG9kZC4gV2h5IDI/IFdoeSBhcmUNCnRoZXkNCmRlZmluZWQgYXQgdGhlIGVuZCBvZiB0aGUg
cmFuZ2U/IE1heWJlIHRoZXJlIGlzIGFuIGV4cGxhbmF0aW9uIGZvciB0aG9zZQ0Kd2hvDQprbm93
IHRoZSBoaXN0b3J5IGJ1dCBmb3IgYW4gdW4taW5pdGlhdGVkIHJlYWRlciBvciBhIGZ1dHVyZSBp
bXBsZW1lbnRlcg0KdGhpcw0Kc2VlbXMgb2RkLg0KDQpUaGVyZSBpcyBubyBzdHJvbmcgcmF0aW9u
YWwgYmVoaW5kIHRoZSBudW1iZXIgb2YgdmFsdWVzICh0d28pIG9yIHRoZQ0KbG9jYXRpb24gKHRv
d2FyZHMgdGhlIGVuZCBvZiB0aGUgcmFuZ2UpLiBUaGVyZSBhcmUgdHdvIHZhbHVlcyBhcyBpdCBz
ZWVtcw0KYXBwcm9wcmlhdGUgZ2l2ZW4gdGhlIHNhbWUgb2YgdGhlIG51bWJlciBzcGFjZSAoMiBv
dXQgb2YgMjU2KS4NCg0KUGVyaGFwcywgaXTigJlzIHNvbWV3aGF0IGZvbGxvd2luZyBjb21tb24g
cHJhY3RpY2Ugc3RhcnRlZCBhdA0KaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzM2OTIj
c2VjdGlvbi0yLjEgKDIgdmFsdWVzIGZvciBhbmQgOC1iaXQNCmZpZWxkLCBjbG9zZXIgdG8gdGhl
IGVuZCkuDQoNCg0KMi4gSW4gU2VjdGlvbiAyLjIgSSBzZWU6DQoNCkFsbCBvdGhlciBmbGFnIGZp
ZWxkcywgbWFya2VkIFUsIGFyZSB1bmFzc2lnbmVkIGFuZCBhdmFpbGFibGUgZm9yDQogZnV0dXJl
IHVzZSwgc2VlIFNlY3Rpb24gMTEuMi4xLiAgVW5hc3NpZ25lZCBiaXRzIE1VU1QgYmUgc2V0IHRv
IHplcm8NCiB1cG9uIG9yaWdpbmF0aW9uLCBhbmQgTVVTVCBiZSBpZ25vcmVkIGFuZCBwcmVzZXJ2
ZWQgdW5tb2RpZmllZCBieQ0KIG90aGVyIE5TSCBzdXBwb3J0aW5nIGVsZW1lbnRzLiAgRWxlbWVu
dHMgd2hpY2ggZG8gbm90IHVuZGVyc3RhbmQgdGhlDQogbWVhbmluZyBvZiBhbnkgb2YgdGhlc2Ug
Yml0cyBNVVNUIE5PVCBtb2RpZnkgdGhlaXIgYWN0aW9ucyBiYXNlZCBvbg0KIHRob3NlIHVua25v
d24gYml0cy4NCg0KVGhlIHdheSB0aGUgbGFzdCBzZW50ZW5jZSBpcyB3cml0dGVuIGl0IHNlZW1z
IHRvIG9wZW4gdGhlIHBhdGggZm9yDQplbGVtZW50cw0KdGhhdCBjbGFpbSB0byAndW5kZXJzdGFu
ZCcgdGhlIG1lYW5pbmcgb2Ygc29tZSBVbmFzc2lnbmVkIGJpdCB0byBtb2RpZnkNCml0cw0KYmVo
YXZpb3IgYmFzZWQgdXBvbiBpdC4gVGhpcyBkb2VzIG5vdCBzZWVtIGdvb2QsIGFzIGF0IHRyYW5z
bWlzc2lvbiBhbGwNClVuYXNzaWduZWQgYml0cyBNVVNUIGJlIHNldCB0byB6ZXJvLiBJIHdvdWxk
IHN1Z2dlc3QgdG8gbWFrZSB0aGUNCnN0YXRlbWVudA0Kc2ltcGxlciBhbmQganVzdCBzYXkgdGhh
dCBhdCByZWNlcHRpb24gYWxsIGVsZW1lbnRzIE1VU1QgTk9UIG1vZGlmeSB0aGVpcg0KYWN0aW9u
cyBiYXNlZCBvbiB0aGVzZSBiaXRzLg0KDQoNClZlcnkgZ29vZCBwb2ludCwgYW5kIGdvb2QgaW1w
cm92ZW1lbnQuIEFwcGxpZWQuDQoNCjMuIEluIFNlY3Rpb24gMi4yIEkgc2VlOg0KDQoweEYgLSBU
aGlzIHZhbHVlIGlzIHJlc2VydmVkIGZvciBleHBlcmltZW50YXRpb24gYW5kIHRlc3RpbmcsIGFz
IHBlcg0KIFtSRkMzNjkyXS4gIEltcGxlbWVudGF0aW9ucyBub3QgZXhwbGljaXRseSBjb25maWd1
cmVkIHRvIGJlIHBhcnQgb2YNCiBhbiBleHBlcmltZW50IFNIT1VMRCBzaWxlbnRseSBkaXNjYXJk
IHBhY2tldHMgd2l0aCBNRCBUeXBlIDB4Ri4NCg0KV2h5IGlzIHRoaXMgYSBTSE9VTEQgYW5kIG5v
dCBhIE1VU1Q/DQoNCg0KVG8gdXNlIE1VU1RzIHZlcnkgc3BhcmluZ2x5IGFuZCBsZWF2ZSBhIGxp
dHRsZSBiaXQgb2YgbGVld2F5IGZvcg0KZXhwZXJpbWVudGF0aW9uLCBmb2xsb3dpbmcgYXBwcm9w
cmlhdGUganVzdGlmaWNhdGlvbi4NCg0KNC4gSSBiZWxpZXZlIHRoYXQgIFtJLUQuaWV0Zi1zZmMt
Y29udHJvbC1wbGFuZV0gbmVlZHMgdG8gYmUgYSBOb3JtYXRpdmUNClJlZmVyZW5jZS4gVGhlcmUg
YXJlIHNldmVyYWwgcGxhY2VzIGluIHRoZSBkb2N1bWVudCAoZS5nLiBpbiBTZWN0aW9uDQoyLjMp
IHdoZXJlDQp0aGlzIGRvY3VtZW50IGlzIHJlZmVycmVkIHRvIGRlc2NyaWJlIGJlaGF2aW9yIG9y
IGFjdGlvbnMgcmVsYXRlZCB0byB0aGUNCmZpZWxkcw0Kb2YgdGhlIGhlYWRlci4NCg0KDQpUaGUg
Y29udHJvbCBwbGFuZSBJLUQgaXMsIGJ5IFdHIGRlY2lzaW9uLCBpbnRlbmRlZCB0byBub3QgYmUg
bm9ybWF0aXZlIGFzDQpOU0ggaXMgdGhlIGRhdGEgcGxhbmUgaW5kZXBlbmRlbnQgb2YgdGhlIENQ
IHNwZWMuDQoNCkkgc2VlIHRoYXQgW0ktRC5pZXRmLXNmYy1jb250cm9sLXBsYW5lXSBpcyBjaXRl
ZCBpbiB0d28gcGxhY2VzOg0KDQoxLg0KICAgICAgW0ktRC5pZXRmLXNmYy1jb250cm9sLXBsYW5l
XSBwcm92aWRlcyBhbiBleGFtcGxlIG9mIHN1Y2ggaW4NCg0KMi4NCiAgcHJvY2Vzcy4gIFRoZXNl
IGNvbnNpZGVyYXRpb25zIGFyZSBkZXBsb3ltZW50LXNwZWNpZmljLiAgSG93ZXZlciwgdGhlDQog
IGNvbnRyb2wgcGxhbmUgaXMgZW50aXRsZWQgdG8gaW5zdHJ1Y3QgU0ZDLWF3YXJlIFNGcyB3aXRo
IHRoZSBkYXRhDQogIHN0cnVjdHVyZSBvZiBjb250ZXh0IGhlYWRlciB0b2dldGhlciB3aXRoIGl0
cyBzY29waW5nIChzZWUNCiAgU2VjdGlvbiAzLjMuMyBvZiBbSS1ELmlldGYtc2ZjLWNvbnRyb2wt
cGxhbmVdKS4NCg0KDQpXZSBhbHJlYWR5IGNhdWdodCB0aGUgaXNzdWUgd2l0aCAjMiBhbmQgY2hh
bmdlZCBpdCB0bywgaW4gb3VyIHdvcmtpbmcgY29weQ0Kd29ya2luZyB3aXRoIHRoZSBjaGFpcnMs
IHRvOg0KDQogIHByb2Nlc3MuICBUaGVzZSBjb25zaWRlcmF0aW9ucyBhcmUgZGVwbG95bWVudC1z
cGVjaWZpYy4gIEhvd2V2ZXIsIHRoZQ0KICBjb250cm9sIHBsYW5lIGlzIGVudGl0bGVkIHRvIGlu
c3RydWN0IFNGQy1hd2FyZSBTRnMgd2l0aCB0aGUgZGF0YQ0KICBzdHJ1Y3R1cmUgb2YgY29udGV4
dCBoZWFkZXIgdG9nZXRoZXIgd2l0aCBpdHMgc2NvcGluZyAoc2VlIGUuZy4sDQogIFNlY3Rpb24g
My4zLjMgb2YgW0ktRC5pZXRmLXNmYy1jb250cm9sLXBsYW5lXSkuDQoNCkFzIHRoYXTigJlzIG9u
ZSBwb3NzaWJsZSwgYW5kIG5vbi1ub3JtYXRpdmUgd2F5LCBvdXQgb2YgbWFueSB3YXlzLg0KDQo1
LiBUaGUgdmVyc2lvbiBudW1iZXIgaGFzIG9ubHkgdHdvIGJpdHMgYXNzaWduZWQuIE1vcmVvdmVy
LCB0aGlzIGRvY3VtZW50DQpyZXNlcnZlcyBhbHJlYWR5IHR3byB2YWx1ZXMgd2l0aG91dCBhbnkg
ZXhwbGFuYXRpb24gd2h5IChvbmx5IDAwIGlzDQptYW5kYXRvcnkNCnRvIHVzZSwgYXMgZmFyIGFz
IEkgdW5kZXJzdGFuZCkuIFRoaXMgbmVlZHMgdG8gYmUgZXhwbGFpbmVkIChtYXliZQ0KJ2hpc3Rv
cmljYWwnDQpyZWFzb25zIC0gYnV0IHVuY2xlYXIgZm9yIGZ1dHVyZSByZWFkZXJzIGFuZCB1c2Vy
cykgYW5kIG1heSBiZSBhDQpsaW1pdGF0aW9uIGFzDQp0aGUgcHJvdG9jb2wgZGV2ZWxvcHMuDQoN
ClRoZSB2ZXJzaW9uIGZpZWxkIGlzIGluZGVlZCBhIHR3by1iaXQgZmllbGQuIE9uZSByZXNlcnZl
ZCBhbmQgd2lsbCBub3QgYmUNCnVzZWQuIE9uZSB1c2VkIGJ5IHRoaXMgc3BlYywgYW5kIHR3byB1
bmFzc2lnbmVkIG9uZXMuDQoNCldlIHJlYWxseSBleHBlY3QgdG8gbm90IGJlIGJ1bXBpbmcgdXAg
dmVyc2lvbiBudW1iZXIgb2Z0ZXIg4oCUIG9yIGV2ZXLigKYNCg0KDQpOaXRzL2VkaXRvcmlhbCBj
b21tZW50czoNCg0KMS4gUGxlYXNlIG1ha2Ugc3VyZSB0aGF0IGFjcm9ueW1zIGFyZSBleHBhbmRl
ZCBhdCBmaXJzdCBvY2N1cnJlbmNlIChlLmcNCg0K

--_000_7BB49936077F490982BBC9976C03C4AEciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <9BDB4EB6348CD948B661F878F32C4031@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KVGhhbmtzIHRvIHlvdSwgRGFuIQ0K
PGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdiBzdHlsZT0i
Y29sb3I6IHJnYigwLCAwLCAwKTsgbGV0dGVyLXNwYWNpbmc6IG5vcm1hbDsgdGV4dC1hbGlnbjog
c3RhcnQ7IHRleHQtaW5kZW50OiAwcHg7IHRleHQtdHJhbnNmb3JtOiBub25lOyB3aGl0ZS1zcGFj
ZTogbm9ybWFsOyB3b3JkLXNwYWNpbmc6IDBweDsgLXdlYmtpdC10ZXh0LXN0cm9rZS13aWR0aDog
MHB4OyB3b3JkLXdyYXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdl
YmtpdC1saW5lLWJyZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0K4oCUPGJyIGNs
YXNzPSIiPg0KQ2FybG9zIFBpZ25hdGFybywmbmJzcDs8YSBocmVmPSJtYWlsdG86Y2FybG9zQGNp
c2NvLmNvbSIgY2xhc3M9IiI+Y2FybG9zQGNpc2NvLmNvbTwvYT48YnIgY2xhc3M9IiI+DQo8YnIg
Y2xhc3M9IiI+DQo8aSBjbGFzcz0iIj7igJxTb21ldGltZXMgSSB1c2UgYmlnIHdvcmRzIHRoYXQg
SSBkbyBub3QgZnVsbHkgdW5kZXJzdGFuZCwgdG8gbWFrZSBteXNlbGYgc291bmQgbW9yZSBwaG90
b3N5bnRoZXNpcy4mcXVvdDs8L2k+PC9kaXY+DQo8L2Rpdj4NCjxiciBjbGFzcz0iIj4NCjxkaXY+
DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+T24gQXVn
IDMxLCAyMDE3LCBhdCAxMTo1NiBQTSwgRGFuIFJvbWFzY2FudSAmbHQ7PGEgaHJlZj0ibWFpbHRv
OmRyb21hc2NhQGdtYWlsLmNvbSIgY2xhc3M9IiI+ZHJvbWFzY2FAZ21haWwuY29tPC9hPiZndDsg
d3JvdGU6PC9kaXY+DQo8YnIgY2xhc3M9IkFwcGxlLWludGVyY2hhbmdlLW5ld2xpbmUiPg0KPGRp
diBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+SGkgQ2FybG9zLDxiciBjbGFzcz0iIj4NCjxiciBj
bGFzcz0iIj4NClRoYW5rIHlvdSBmb3IgYWRkcmVzc2luZyBteSBjb21tZW50cy4gWW91ciBzdWdn
ZXN0ZWQgZWRpdHMgc2VlbSB0byBhZGRyZXNzPGJyIGNsYXNzPSIiPg0KdGhlIGlzc3Vlcy48YnIg
Y2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpSZWdhcmRzLDxiciBjbGFzcz0iIj4NCjxiciBjbGFz
cz0iIj4NCkRhbjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCk9u
IEZyaSwgU2VwIDEsIDIwMTcgYXQgMzo1NSBBTSwgQ2FybG9zIFBpZ25hdGFybyAoY3BpZ25hdGEp
ICZsdDs8YnIgY2xhc3M9IiI+DQo8YSBocmVmPSJtYWlsdG86Y3BpZ25hdGFAY2lzY28uY29tIiBj
bGFzcz0iIj5jcGlnbmF0YUBjaXNjby5jb208L2E+Jmd0OyB3cm90ZTo8YnIgY2xhc3M9IiI+DQo8
YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj5IaSwgRGFuLDxi
ciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCk1hbnkgdGhhbmtzIGZvciB5b3VyIGRldGFpbGVk
IGFuZCB2YWx1YWJsZSByZXZpZXcsIGFuZCBhcG9sb2dpZXMgZm9yIHRoZTxiciBjbGFzcz0iIj4N
CmRlbGF5IGluIEFjay1pbmcgYW5kIHJlc3BvbmRpbmcuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNz
PSIiPg0KUGxlYXNlIHNlZSBpbmxpbmUuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0K4oCU
PGJyIGNsYXNzPSIiPg0KQ2FybG9zIFBpZ25hdGFybywgPGEgaHJlZj0ibWFpbHRvOmNhcmxvc0Bj
aXNjby5jb20iIGNsYXNzPSIiPmNhcmxvc0BjaXNjby5jb208L2E+PGJyIGNsYXNzPSIiPg0KPGJy
IGNsYXNzPSIiPg0K4oCcU29tZXRpbWVzIEkgdXNlIGJpZyB3b3JkcyB0aGF0IEkgZG8gbm90IGZ1
bGx5IHVuZGVyc3RhbmQsIHRvIG1ha2UgbXlzZWxmPGJyIGNsYXNzPSIiPg0Kc291bmQgbW9yZSBw
aG90b3N5bnRoZXNpcy4mcXVvdDs8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo8YmxvY2tx
dW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj5PbiBBdWcgMjIsIDIwMTcsIGF0IDExOjM0IEFNLCBE
YW4gUm9tYXNjYW51ICZsdDs8YSBocmVmPSJtYWlsdG86ZHJvbWFzY2FAZ21haWwuY29tIiBjbGFz
cz0iIj5kcm9tYXNjYUBnbWFpbC5jb208L2E+Jmd0OyB3cm90ZTo8YnIgY2xhc3M9IiI+DQo8YnIg
Y2xhc3M9IiI+DQpSZXZpZXdlcjogRGFuIFJvbWFzY2FudTxiciBjbGFzcz0iIj4NClJldmlldyBy
ZXN1bHQ6IEFsbW9zdCBSZWFkeTxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCkkgYW0gdGhl
IGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsIEFy
ZWE8YnIgY2xhc3M9IiI+DQpSZXZpZXcgVGVhbSAoR2VuLUFSVCkgcmV2aWV3cyBhbGwgSUVURiBk
b2N1bWVudHMgYmVpbmcgcHJvY2Vzc2VkPGJyIGNsYXNzPSIiPg0KYnkgdGhlIElFU0cgZm9yIHRo
ZSBJRVRGIENoYWlyLiAmbmJzcDtQbGVhc2UgdHJlYXQgdGhlc2UgY29tbWVudHMganVzdDxiciBj
bGFzcz0iIj4NCmxpa2UgYW55IG90aGVyIGxhc3QgY2FsbCBjb21tZW50cy48YnIgY2xhc3M9IiI+
DQo8YnIgY2xhc3M9IiI+DQpGb3IgbW9yZSBpbmZvcm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUgRkFR
IGF0PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJmx0OzxhIGhyZWY9Imh0dHBzOi8vdHJh
Yy5pZXRmLm9yZy90cmFjL2dlbi93aWtpL0dlbkFydGZhcSIgY2xhc3M9IiI+aHR0cHM6Ly90cmFj
LmlldGYub3JnL3RyYWMvZ2VuL3dpa2kvR2VuQXJ0ZmFxPC9hPiZndDsuPGJyIGNsYXNzPSIiPg0K
PGJyIGNsYXNzPSIiPg0KRG9jdW1lbnQ6IGRyYWZ0LWlldGYtc2ZjLW5zaC0xOTxiciBjbGFzcz0i
Ij4NClJldmlld2VyOiBEYW4gUm9tYXNjYW51PGJyIGNsYXNzPSIiPg0KUmV2aWV3IERhdGU6IDIw
MTctMDgtMjI8YnIgY2xhc3M9IiI+DQpJRVRGIExDIEVuZCBEYXRlOiAyMDE3LTA4LTI1PGJyIGNs
YXNzPSIiPg0KSUVTRyBUZWxlY2hhdCBkYXRlOiAyMDE3LTA5LTE0PGJyIGNsYXNzPSIiPg0KPGJy
IGNsYXNzPSIiPg0KU3VtbWFyeTo8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpUaGlzIGRv
Y3VtZW50IGRlc2NyaWJlcyB0aGUgaGVhZGVyIChjYWxsZWQgTmV0d29yayBTZXJ2aWNlIEhlYWRl
ciAtIE5TSCk8YnIgY2xhc3M9IiI+DQo8L2Jsb2NrcXVvdGU+DQp0byBiZTxiciBjbGFzcz0iIj4N
CjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPmluc2VydGVkIGluIHBhY2tldHMgYW5k
IGZyYW1lcyBpbiBvcmRlciB0byBjcmVhdGUgcGFja2V0cyBhbmQgZnJhbWVzIHRoYXQ8YnIgY2xh
c3M9IiI+DQpyZWFsaXplIHNlcnZpY2UgZnVuY3Rpb25zIGRlc2NyaWJlZCBieSBvdGhlciBTRkMg
ZG9jdW1lbnRzLiBJdCBuZWVkcyB0bzxiciBjbGFzcz0iIj4NCjwvYmxvY2txdW90ZT4NCmJlIHJl
YWQ8YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj5pbiBjb25q
dW5jdGlvbiB3aXRoIFJGQyA3NjY1IGFuZCBvdGhlciBkb2N1bWVudHMgYXMgdGhlIFNGQyBjb250
cm9sPGJyIGNsYXNzPSIiPg0KPC9ibG9ja3F1b3RlPg0KcGxhbmUgSS1EPGJyIGNsYXNzPSIiPg0K
PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+aW4gb3JkZXIgdG8gbWFrZSBzZW5zZSBv
ZiB0aGUgcmVxdWlyZWQgZnVuY3Rpb25hbGl0eS4gVGhpcyBwYXJ0IG9mIHRoZTxiciBjbGFzcz0i
Ij4NCjwvYmxvY2txdW90ZT4NClNGQzxiciBjbGFzcz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNp
dGUiIGNsYXNzPSIiPnNvbHV0aW9uIHNlZW1zIGFsbW9zdCByZWFkeSwgYnV0IGEgZmV3IGlzc3Vl
cyBtZW50aW9uZWQgYmVsb3cgbmVlZCBpbiBteTxiciBjbGFzcz0iIj4NCm9waW5pb24gY2xhcmlm
aWNhdGlvbiBiZWZvcmUgdGhlIGRvY3VtZW50IGlzIGFwcHJvdmVkLjxiciBjbGFzcz0iIj4NCjwv
YmxvY2txdW90ZT4NCjxiciBjbGFzcz0iIj4NClRoYW5rIHlvdSBmb3IgdGhpcyBzdW1tYXJ5IOKA
lCB5b3UgcmFpc2UgZ29vZCBwb2ludHMuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPGJs
b2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KTWFqb3IgaXNzdWVz
OjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCjEuIFNlY3Rpb24gMTEuMSBjbGFpbXM6ICdB
biBJRUVFIEV0aGVyVHlwZSwgMHg4OTRGLCBoYXMgYmVlbiBhbGxvY2F0ZWQ8YnIgY2xhc3M9IiI+
DQo8L2Jsb2NrcXVvdGU+DQpmb3I8YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRl
IiBjbGFzcz0iIj5OU0gnLiBJIGNvdWxkIG5vdCBmaW5kIHRoaXMgdmFsdWUgaW4gdGhlIHRhYmxl
cyBkaXNwbGF5ZWQgYnkgdGhlIElFRUU8YnIgY2xhc3M9IiI+DQpSZWdpc3RyYXRpb24gQXV0aG9y
aXR5IChSQUMpIC0gZm9yIGV4YW1wbGUgYXQ8YnIgY2xhc3M9IiI+DQo8YSBocmVmPSJodHRwOi8v
c3RhbmRhcmRzLW91aS5pZWVlLm9yZy9ldGhlcnR5cGUvZXRoLnR4dCIgY2xhc3M9IiI+aHR0cDov
L3N0YW5kYXJkcy1vdWkuaWVlZS5vcmcvZXRoZXJ0eXBlL2V0aC50eHQ8L2E+LiBOZWl0aGVyIGRv
ZXMgSUFOQSBhdDxiciBjbGFzcz0iIj4NCjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlhbmEub3JnL2Fz
c2lnbm1lbnRzL2llZWUtODAyLW51bWJlcnMvaWVlZS04MDItbnVtYmVycy54aHRtbCIgY2xhc3M9
IiI+aHR0cHM6Ly93d3cuaWFuYS5vcmcvYXNzaWdubWVudHMvaWVlZS04MDItbnVtYmVycy9pZWVl
LTgwMi1udW1iZXJzLnhodG1sPC9hPjxiciBjbGFzcz0iIj4NCjwvYmxvY2txdW90ZT4NCih3aGlj
aDxiciBjbGFzcz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPndvdWxkIG5v
dCBiZSBpbiBhbnkgY2FzZSB0aGUgYXV0aG9yaXRhdGl2ZSBzb3VyY2UpLiBDYW4geW91IHBsZWFz
ZTxiciBjbGFzcz0iIj4NCjwvYmxvY2txdW90ZT4NCmluZGljYXRlIHRoZTxiciBjbGFzcz0iIj4N
CjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPnNvdXJjZSB0aGF0IHRoaXMgaXMgaW5k
ZWVkIGEgY29uZmlybWVkIElFRUUgRXRoZXJUeXBlIHJlZ2lzdHJhdGlvbi48YnIgY2xhc3M9IiI+
DQo8L2Jsb2NrcXVvdGU+DQo8YnIgY2xhc3M9IiI+DQpJIGFtIG5vdCBzdXJlIGhvdyBvZnRlbiB0
aGF0IHBhZ2UgaXMgdXBkYXRlZCwgYnV0IHRoZSBzYW1lIGxpbmsgeW91PGJyIGNsYXNzPSIiPg0K
aW5jbHVkZSwgPGEgaHJlZj0iaHR0cDovL3N0YW5kYXJkcy1vdWkuaWVlZS5vcmcvZXRoZXJ0eXBl
L2V0aC50eHQiIGNsYXNzPSIiPmh0dHA6Ly9zdGFuZGFyZHMtb3VpLmllZWUub3JnL2V0aGVydHlw
ZS9ldGgudHh0PC9hPiwgc2hvd3M6PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KMHg4OTRG
PGJyIGNsYXNzPSIiPg0KODk0RjogTlNIIChOZXR3b3JrIFNlcnZpY2UgSGVhZGVyKS4gUmVmZXJl
bmNlOiBkcmFmdC1pZXRmLXNmYy1uc2gtMTg8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpH
cmFudGVkLCB0aGF0IHJlZ2lzdHJhdGlvbiB3aWxsIGJlIHVwZGF0ZWQgd2l0aCB0aGUgUkZDIG51
bWJlciBpbnN0ZWFkIG9mPGJyIGNsYXNzPSIiPg0KdGhlIEktRCwgd2hlbiBpdCBwdWJsaXNoZXMu
PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xh
c3M9IiI+PGJyIGNsYXNzPSIiPg0KMi4gU2VjdGlvbiA1IHJlZmVycyB0byBpZXRmLXJ0Z3dnLWR0
LWVuY2FwIHdoaWNoIGlzIGV4cGlyZWQuIElmIEk8YnIgY2xhc3M9IiI+DQo8L2Jsb2NrcXVvdGU+
DQp1bmRlcnN0YW5kPGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9
IiI+Y29ycmVjdGx5IHRoZSBzdGF0dXMgb2YgdGhpcyB3b3JrLCB0aGVyZSBpcyBhIGRlc2lnbiB0
ZWFtIGluIHBsYWNlIGluIHRoZTxiciBjbGFzcz0iIj4NClJvdXRpbmcgQXJlYSBjcmVhdGVkIHRv
IGxvb2sgYXQgY29tbW9uIGlzc3VlcyBmb3IgdGhlIGRpZmZlcmVudCBkYXRhPGJyIGNsYXNzPSIi
Pg0KPC9ibG9ja3F1b3RlPg0KcGxhbmU8YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJj
aXRlIiBjbGFzcz0iIj5lbmNhcHN1bGF0aW9ucyBiZWluZyBkaXNjdXNzZWQgaW4gdmFyaW91cyBX
R3MgaW5jbHVkaW5nIFNGQy4gVGhpcyBsZWF2ZXM8YnIgY2xhc3M9IiI+DQo8L2Jsb2NrcXVvdGU+
DQp0aGU8YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj5pc3N1
ZSB1bnNldHRsZWQgYXQgdGhpcyBzdGFnZSBhbmQgdGhpcyBtYXkgYmUgYSBwcm9ibGVtIGZvciBh
IHN0YW5kYXJkczxiciBjbGFzcz0iIj4NCjwvYmxvY2txdW90ZT4NCnRyYWNrPGJyIGNsYXNzPSIi
Pg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+ZG9jdW1lbnQuIEkgc3VnZ2VzdCB0
aGF0IGZpcnN0IHRoZSByZWZlcmVuY2UgdG8gdGhlIGV4cGlyZWQgZG9jdW1lbnQgaXM8YnIgY2xh
c3M9IiI+DQpyZW1vdmVkLCBzZWNvbmQgdGhhdCB0aGUgaXNzdWUgaXMgbWFya2VkIGFzICdvcGVu
JyBhbmQgc3ViamVjdCBmb3I8YnIgY2xhc3M9IiI+DQo8L2Jsb2NrcXVvdGU+DQpmdXR1cmUgd29y
ay48YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj48YnIgY2xh
c3M9IiI+DQo8L2Jsb2NrcXVvdGU+DQo8YnIgY2xhc3M9IiI+DQpHb29kIHN1Z2dlc3Rpb24uIElu
c3RlYWQgb2YgcmVtb3ZpbmcgdGhlIHJlZmVyZW5jZSBhbGwgdG9nZXRoZXIsIHdlIGNhbjxiciBj
bGFzcz0iIj4NCm1hcmsgaXQgYXMgZXhlbXBsaWZ5aW5nIG9mIG9uZSBhcHByb2FjaC48YnIgY2xh
c3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj5N
aW5vciBpc3N1ZXM6PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KMS4gJm5ic3A7VHdvIHZh
bHVlcyAnRXhwZXJpbWVudCAxJyBhbmQgJ0V4cGVyaW1lbnQgMicgYXJlIGRlZmluZWQgaW4gc2Vj
dGlvbjxiciBjbGFzcz0iIj4NCjwvYmxvY2txdW90ZT4NCjIuMiBhbmQ8YnIgY2xhc3M9IiI+DQo8
YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj4xMS4yLjUgZm9yIHRoZSBOZXh0IFByb3Rv
Y29sLiBUaGlzIHNlZW1zIGEgbGl0dGxlIG9kZC4gV2h5IDI/IFdoeSBhcmU8YnIgY2xhc3M9IiI+
DQo8L2Jsb2NrcXVvdGU+DQp0aGV5PGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0
ZSIgY2xhc3M9IiI+ZGVmaW5lZCBhdCB0aGUgZW5kIG9mIHRoZSByYW5nZT8gTWF5YmUgdGhlcmUg
aXMgYW4gZXhwbGFuYXRpb24gZm9yIHRob3NlPGJyIGNsYXNzPSIiPg0KPC9ibG9ja3F1b3RlPg0K
d2hvPGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+a25vdyB0
aGUgaGlzdG9yeSBidXQgZm9yIGFuIHVuLWluaXRpYXRlZCByZWFkZXIgb3IgYSBmdXR1cmUgaW1w
bGVtZW50ZXI8YnIgY2xhc3M9IiI+DQo8L2Jsb2NrcXVvdGU+DQp0aGlzPGJyIGNsYXNzPSIiPg0K
PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+c2VlbXMgb2RkLjxiciBjbGFzcz0iIj4N
CjwvYmxvY2txdW90ZT4NCjxiciBjbGFzcz0iIj4NClRoZXJlIGlzIG5vIHN0cm9uZyByYXRpb25h
bCBiZWhpbmQgdGhlIG51bWJlciBvZiB2YWx1ZXMgKHR3bykgb3IgdGhlPGJyIGNsYXNzPSIiPg0K
bG9jYXRpb24gKHRvd2FyZHMgdGhlIGVuZCBvZiB0aGUgcmFuZ2UpLiBUaGVyZSBhcmUgdHdvIHZh
bHVlcyBhcyBpdCBzZWVtczxiciBjbGFzcz0iIj4NCmFwcHJvcHJpYXRlIGdpdmVuIHRoZSBzYW1l
IG9mIHRoZSBudW1iZXIgc3BhY2UgKDIgb3V0IG9mIDI1NikuPGJyIGNsYXNzPSIiPg0KPGJyIGNs
YXNzPSIiPg0KUGVyaGFwcywgaXTigJlzIHNvbWV3aGF0IGZvbGxvd2luZyBjb21tb24gcHJhY3Rp
Y2Ugc3RhcnRlZCBhdDxiciBjbGFzcz0iIj4NCjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5v
cmcvaHRtbC9yZmMzNjkyI3NlY3Rpb24tMi4xIiBjbGFzcz0iIj5odHRwczovL3Rvb2xzLmlldGYu
b3JnL2h0bWwvcmZjMzY5MiNzZWN0aW9uLTIuMTwvYT4gKDIgdmFsdWVzIGZvciBhbmQgOC1iaXQ8
YnIgY2xhc3M9IiI+DQpmaWVsZCwgY2xvc2VyIHRvIHRoZSBlbmQpLjxiciBjbGFzcz0iIj4NCjxi
ciBjbGFzcz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPjxiciBjbGFzcz0i
Ij4NCjIuIEluIFNlY3Rpb24gMi4yIEkgc2VlOjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4N
CjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPkFsbCBvdGhlciBmbGFnIGZpZWxkcywg
bWFya2VkIFUsIGFyZSB1bmFzc2lnbmVkIGFuZCBhdmFpbGFibGUgZm9yPGJyIGNsYXNzPSIiPg0K
PC9ibG9ja3F1b3RlPg0KJm5ic3A7ZnV0dXJlIHVzZSwgc2VlIFNlY3Rpb24gMTEuMi4xLiAmbmJz
cDtVbmFzc2lnbmVkIGJpdHMgTVVTVCBiZSBzZXQgdG8gemVybzxiciBjbGFzcz0iIj4NCiZuYnNw
O3Vwb24gb3JpZ2luYXRpb24sIGFuZCBNVVNUIGJlIGlnbm9yZWQgYW5kIHByZXNlcnZlZCB1bm1v
ZGlmaWVkIGJ5PGJyIGNsYXNzPSIiPg0KJm5ic3A7b3RoZXIgTlNIIHN1cHBvcnRpbmcgZWxlbWVu
dHMuICZuYnNwO0VsZW1lbnRzIHdoaWNoIGRvIG5vdCB1bmRlcnN0YW5kIHRoZTxiciBjbGFzcz0i
Ij4NCiZuYnNwO21lYW5pbmcgb2YgYW55IG9mIHRoZXNlIGJpdHMgTVVTVCBOT1QgbW9kaWZ5IHRo
ZWlyIGFjdGlvbnMgYmFzZWQgb248YnIgY2xhc3M9IiI+DQombmJzcDt0aG9zZSB1bmtub3duIGJp
dHMuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KVGhlIHdheSB0aGUgbGFzdCBzZW50ZW5j
ZSBpcyB3cml0dGVuIGl0IHNlZW1zIHRvIG9wZW4gdGhlIHBhdGggZm9yPGJyIGNsYXNzPSIiPg0K
PC9ibG9ja3F1b3RlPg0KZWxlbWVudHM8YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJj
aXRlIiBjbGFzcz0iIj50aGF0IGNsYWltIHRvICd1bmRlcnN0YW5kJyB0aGUgbWVhbmluZyBvZiBz
b21lIFVuYXNzaWduZWQgYml0IHRvIG1vZGlmeTxiciBjbGFzcz0iIj4NCjwvYmxvY2txdW90ZT4N
Cml0czxiciBjbGFzcz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPmJlaGF2
aW9yIGJhc2VkIHVwb24gaXQuIFRoaXMgZG9lcyBub3Qgc2VlbSBnb29kLCBhcyBhdCB0cmFuc21p
c3Npb24gYWxsPGJyIGNsYXNzPSIiPg0KVW5hc3NpZ25lZCBiaXRzIE1VU1QgYmUgc2V0IHRvIHpl
cm8uIEkgd291bGQgc3VnZ2VzdCB0byBtYWtlIHRoZTxiciBjbGFzcz0iIj4NCjwvYmxvY2txdW90
ZT4NCnN0YXRlbWVudDxiciBjbGFzcz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNz
PSIiPnNpbXBsZXIgYW5kIGp1c3Qgc2F5IHRoYXQgYXQgcmVjZXB0aW9uIGFsbCBlbGVtZW50cyBN
VVNUIE5PVCBtb2RpZnkgdGhlaXI8YnIgY2xhc3M9IiI+DQphY3Rpb25zIGJhc2VkIG9uIHRoZXNl
IGJpdHMuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPC9ibG9ja3F1b3RlPg0KPGJyIGNs
YXNzPSIiPg0KVmVyeSBnb29kIHBvaW50LCBhbmQgZ29vZCBpbXByb3ZlbWVudC4gQXBwbGllZC48
YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFz
cz0iIj4zLiBJbiBTZWN0aW9uIDIuMiBJIHNlZTo8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+
DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj4weEYgLSBUaGlzIHZhbHVlIGlzIHJl
c2VydmVkIGZvciBleHBlcmltZW50YXRpb24gYW5kIHRlc3RpbmcsIGFzIHBlcjxiciBjbGFzcz0i
Ij4NCjwvYmxvY2txdW90ZT4NCiZuYnNwO1tSRkMzNjkyXS4gJm5ic3A7SW1wbGVtZW50YXRpb25z
IG5vdCBleHBsaWNpdGx5IGNvbmZpZ3VyZWQgdG8gYmUgcGFydCBvZjxiciBjbGFzcz0iIj4NCiZu
YnNwO2FuIGV4cGVyaW1lbnQgU0hPVUxEIHNpbGVudGx5IGRpc2NhcmQgcGFja2V0cyB3aXRoIE1E
IFR5cGUgMHhGLjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCldoeSBpcyB0aGlzIGEgU0hP
VUxEIGFuZCBub3QgYSBNVVNUPzxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCjwvYmxvY2tx
dW90ZT4NCjxiciBjbGFzcz0iIj4NClRvIHVzZSBNVVNUcyB2ZXJ5IHNwYXJpbmdseSBhbmQgbGVh
dmUgYSBsaXR0bGUgYml0IG9mIGxlZXdheSBmb3I8YnIgY2xhc3M9IiI+DQpleHBlcmltZW50YXRp
b24sIGZvbGxvd2luZyBhcHByb3ByaWF0ZSBqdXN0aWZpY2F0aW9uLjxiciBjbGFzcz0iIj4NCjxi
ciBjbGFzcz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPjQuIEkgYmVsaWV2
ZSB0aGF0ICZuYnNwO1tJLUQuaWV0Zi1zZmMtY29udHJvbC1wbGFuZV0gbmVlZHMgdG8gYmUgYSBO
b3JtYXRpdmU8YnIgY2xhc3M9IiI+DQpSZWZlcmVuY2UuIFRoZXJlIGFyZSBzZXZlcmFsIHBsYWNl
cyBpbiB0aGUgZG9jdW1lbnQgKGUuZy4gaW4gU2VjdGlvbjxiciBjbGFzcz0iIj4NCjwvYmxvY2tx
dW90ZT4NCjIuMykgd2hlcmU8YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBj
bGFzcz0iIj50aGlzIGRvY3VtZW50IGlzIHJlZmVycmVkIHRvIGRlc2NyaWJlIGJlaGF2aW9yIG9y
IGFjdGlvbnMgcmVsYXRlZCB0byB0aGU8YnIgY2xhc3M9IiI+DQo8L2Jsb2NrcXVvdGU+DQpmaWVs
ZHM8YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj5vZiB0aGUg
aGVhZGVyLjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCjwvYmxvY2txdW90ZT4NCjxiciBj
bGFzcz0iIj4NClRoZSBjb250cm9sIHBsYW5lIEktRCBpcywgYnkgV0cgZGVjaXNpb24sIGludGVu
ZGVkIHRvIG5vdCBiZSBub3JtYXRpdmUgYXM8YnIgY2xhc3M9IiI+DQpOU0ggaXMgdGhlIGRhdGEg
cGxhbmUgaW5kZXBlbmRlbnQgb2YgdGhlIENQIHNwZWMuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNz
PSIiPg0KSSBzZWUgdGhhdCBbSS1ELmlldGYtc2ZjLWNvbnRyb2wtcGxhbmVdIGlzIGNpdGVkIGlu
IHR3byBwbGFjZXM6PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KMS48YnIgY2xhc3M9IiI+
DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtbSS1ELmlldGYtc2ZjLWNvbnRy
b2wtcGxhbmVdIHByb3ZpZGVzIGFuIGV4YW1wbGUgb2Ygc3VjaCBpbjxiciBjbGFzcz0iIj4NCjxi
ciBjbGFzcz0iIj4NCjIuPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7cHJvY2Vzcy4gJm5ic3A7
VGhlc2UgY29uc2lkZXJhdGlvbnMgYXJlIGRlcGxveW1lbnQtc3BlY2lmaWMuICZuYnNwO0hvd2V2
ZXIsIHRoZTxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO2NvbnRyb2wgcGxhbmUgaXMgZW50aXRs
ZWQgdG8gaW5zdHJ1Y3QgU0ZDLWF3YXJlIFNGcyB3aXRoIHRoZSBkYXRhPGJyIGNsYXNzPSIiPg0K
Jm5ic3A7Jm5ic3A7c3RydWN0dXJlIG9mIGNvbnRleHQgaGVhZGVyIHRvZ2V0aGVyIHdpdGggaXRz
IHNjb3BpbmcgKHNlZTxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO1NlY3Rpb24gMy4zLjMgb2Yg
W0ktRC5pZXRmLXNmYy1jb250cm9sLXBsYW5lXSkuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIi
Pg0KPGJyIGNsYXNzPSIiPg0KV2UgYWxyZWFkeSBjYXVnaHQgdGhlIGlzc3VlIHdpdGggIzIgYW5k
IGNoYW5nZWQgaXQgdG8sIGluIG91ciB3b3JraW5nIGNvcHk8YnIgY2xhc3M9IiI+DQp3b3JraW5n
IHdpdGggdGhlIGNoYWlycywgdG86PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJm5ic3A7
Jm5ic3A7cHJvY2Vzcy4gJm5ic3A7VGhlc2UgY29uc2lkZXJhdGlvbnMgYXJlIGRlcGxveW1lbnQt
c3BlY2lmaWMuICZuYnNwO0hvd2V2ZXIsIHRoZTxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO2Nv
bnRyb2wgcGxhbmUgaXMgZW50aXRsZWQgdG8gaW5zdHJ1Y3QgU0ZDLWF3YXJlIFNGcyB3aXRoIHRo
ZSBkYXRhPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7c3RydWN0dXJlIG9mIGNvbnRleHQgaGVh
ZGVyIHRvZ2V0aGVyIHdpdGggaXRzIHNjb3BpbmcgKHNlZSBlLmcuLDxiciBjbGFzcz0iIj4NCiZu
YnNwOyZuYnNwO1NlY3Rpb24gMy4zLjMgb2YgW0ktRC5pZXRmLXNmYy1jb250cm9sLXBsYW5lXSku
PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KQXMgdGhhdOKAmXMgb25lIHBvc3NpYmxlLCBh
bmQgbm9uLW5vcm1hdGl2ZSB3YXksIG91dCBvZiBtYW55IHdheXMuPGJyIGNsYXNzPSIiPg0KPGJy
IGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+NS4gVGhlIHZlcnNp
b24gbnVtYmVyIGhhcyBvbmx5IHR3byBiaXRzIGFzc2lnbmVkLiBNb3Jlb3ZlciwgdGhpcyBkb2N1
bWVudDxiciBjbGFzcz0iIj4NCnJlc2VydmVzIGFscmVhZHkgdHdvIHZhbHVlcyB3aXRob3V0IGFu
eSBleHBsYW5hdGlvbiB3aHkgKG9ubHkgMDAgaXM8YnIgY2xhc3M9IiI+DQo8L2Jsb2NrcXVvdGU+
DQptYW5kYXRvcnk8YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0i
Ij50byB1c2UsIGFzIGZhciBhcyBJIHVuZGVyc3RhbmQpLiBUaGlzIG5lZWRzIHRvIGJlIGV4cGxh
aW5lZCAobWF5YmU8YnIgY2xhc3M9IiI+DQo8L2Jsb2NrcXVvdGU+DQonaGlzdG9yaWNhbCc8YnIg
Y2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj5yZWFzb25zIC0gYnV0
IHVuY2xlYXIgZm9yIGZ1dHVyZSByZWFkZXJzIGFuZCB1c2VycykgYW5kIG1heSBiZSBhPGJyIGNs
YXNzPSIiPg0KPC9ibG9ja3F1b3RlPg0KbGltaXRhdGlvbiBhczxiciBjbGFzcz0iIj4NCjxibG9j
a3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPnRoZSBwcm90b2NvbCBkZXZlbG9wcy48YnIgY2xh
c3M9IiI+DQo8L2Jsb2NrcXVvdGU+DQo8YnIgY2xhc3M9IiI+DQpUaGUgdmVyc2lvbiBmaWVsZCBp
cyBpbmRlZWQgYSB0d28tYml0IGZpZWxkLiBPbmUgcmVzZXJ2ZWQgYW5kIHdpbGwgbm90IGJlPGJy
IGNsYXNzPSIiPg0KdXNlZC4gT25lIHVzZWQgYnkgdGhpcyBzcGVjLCBhbmQgdHdvIHVuYXNzaWdu
ZWQgb25lcy48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpXZSByZWFsbHkgZXhwZWN0IHRv
IG5vdCBiZSBidW1waW5nIHVwIHZlcnNpb24gbnVtYmVyIG9mdGVyIOKAlCBvciBldmVy4oCmPGJy
IGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9
IiI+PGJyIGNsYXNzPSIiPg0KTml0cy9lZGl0b3JpYWwgY29tbWVudHM6PGJyIGNsYXNzPSIiPg0K
PGJyIGNsYXNzPSIiPg0KMS4gUGxlYXNlIG1ha2Ugc3VyZSB0aGF0IGFjcm9ueW1zIGFyZSBleHBh
bmRlZCBhdCBmaXJzdCBvY2N1cnJlbmNlIChlLmc8L2Jsb2NrcXVvdGU+DQo8L2Jsb2NrcXVvdGU+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8YnIgY2xhc3M9IiI+DQo8
L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_7BB49936077F490982BBC9976C03C4AEciscocom_--


From nobody Thu Aug 31 21:53:30 2017
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCBD1132F7E for <ietf@ietfa.amsl.com>; Thu, 31 Aug 2017 21:53:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level: 
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wKn2hFD1EIes for <ietf@ietfa.amsl.com>; Thu, 31 Aug 2017 21:53:27 -0700 (PDT)
Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.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 B3BD1132FB8 for <ietf@ietf.org>; Thu, 31 Aug 2017 21:53:27 -0700 (PDT)
Received: from pps.filterd (m0098409.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v814pFhe112611 for <ietf@ietf.org>; Fri, 1 Sep 2017 00:53:23 -0400
Received: from e11.ny.us.ibm.com (e11.ny.us.ibm.com [129.33.205.201]) by mx0a-001b2d01.pphosted.com with ESMTP id 2cpskdxka0-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 01 Sep 2017 00:53:22 -0400
Received: from localhost by e11.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, 1 Sep 2017 00:53:21 -0400
Received: from b01cxnp22035.gho.pok.ibm.com (9.57.198.25) by e11.ny.us.ibm.com (146.89.104.198) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 1 Sep 2017 00:53:20 -0400
Received: from b01ledav004.gho.pok.ibm.com (b01ledav004.gho.pok.ibm.com [9.57.199.109]) by b01cxnp22035.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v814rKA332440402 for <ietf@ietf.org>; Fri, 1 Sep 2017 04:53:20 GMT
Received: from b01ledav004.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id AEA37112047 for <ietf@ietf.org>; Fri,  1 Sep 2017 00:53:05 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b01ledav004.gho.pok.ibm.com (Postfix) with ESMTPS id 9B2CE112054 for <ietf@ietf.org>; Fri,  1 Sep 2017 00:53:05 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v814rJBq012263 for <ietf@ietf.org>; Fri, 1 Sep 2017 00:53:19 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v814rJMg012235 for ietf@ietf.org; Fri, 1 Sep 2017 00:53:19 -0400
From: narten@us.ibm.com
Date: Fri, 01 Sep 2017 00:53:19 -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-GCONF: 00
x-cbid: 17090104-2213-0000-0000-00000212C430
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00007644; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000226; SDB=6.00910527; UDB=6.00456767; IPR=6.00690807;  BA=6.00005563; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00016954; XFM=3.00000015; UTC=2017-09-01 04:53:21
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17090104-2214-0000-0000-00005766BF9E
Message-Id: <201709010453.v814rJMg012235@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-08-31_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=13 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1709010070
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7-U2lrOP3CSprLKjFb-xCGHx9l0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Sep 2017 04:53:30 -0000

Total of 49 messages in the last 7 days.
 
script run at: Fri Sep  1 00:53:13 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 18.37% |    9 | 16.72% |   181630 | tuexen@fh-muenster.de
  2.04% |    1 | 21.29% |   231353 | sajassi@cisco.com
  6.12% |    3 | 10.25% |   111340 | spencerdawkins.ietf@gmail.com
  6.12% |    3 |  6.74% |    73215 | lear@cisco.com
  6.12% |    3 |  3.89% |    42270 | mranga@gmail.com
  6.12% |    3 |  3.46% |    37608 | bclaise@cisco.com
  4.08% |    2 |  4.72% |    51260 | cpignata@cisco.com
  4.08% |    2 |  3.78% |    41044 | yaronf.ietf@gmail.com
  4.08% |    2 |  2.70% |    29309 | adam.w.montville@gmail.com
  2.04% |    1 |  4.34% |    47115 | bew@cisco.com
  4.08% |    2 |  2.10% |    22858 | zhencao.ietf@gmail.com
  2.04% |    1 |  2.91% |    31651 | juberti@google.com
  2.04% |    1 |  2.57% |    27918 | dromasca@gmail.com
  2.04% |    1 |  1.95% |    21145 | roni.even@huawei.com
  2.04% |    1 |  1.53% |    16609 | stefan.winter@restena.lu
  2.04% |    1 |  1.27% |    13808 | xuxiaohu@huawei.com
  2.04% |    1 |  1.25% |    13602 | rjsparks@nostrum.com
  2.04% |    1 |  1.18% |    12831 | afarrel@juniper.net
  2.04% |    1 |  0.91% |     9905 | narten@us.ibm.com
  2.04% |    1 |  0.91% |     9885 | stewart.bryant@gmail.com
  2.04% |    1 |  0.87% |     9451 | einarnn@cisco.com
  2.04% |    1 |  0.67% |     7287 | ibagdona.ietf@gmail.com
  2.04% |    1 |  0.65% |     7051 | worley@ariadne.com
  2.04% |    1 |  0.61% |     6674 | johnl@taugh.com
  2.04% |    1 |  0.58% |     6312 | liushucheng@huawei.com
  2.04% |    1 |  0.57% |     6176 | linuxwolf+ietf@outer-planes.net
  2.04% |    1 |  0.56% |     6033 | elwynd@dial.pipex.com
  2.04% |    1 |  0.53% |     5757 | ron.even.tlv@gmail.com
  2.04% |    1 |  0.49% |     5362 | tjw.ietf@gmail.com
--------+------+--------+----------+------------------------
100.00% |   49 |100.00% |  1086459 | Total


From nobody Thu Aug 31 23:59:47 2017
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19906133280; Thu, 31 Aug 2017 23:59:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level: 
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id khhEJ17sxwvH; Thu, 31 Aug 2017 23:59:40 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 133C7133174; Thu, 31 Aug 2017 23:59:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=46152; q=dns/txt; s=iport; t=1504249179; x=1505458779; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=OCVcTD8UJ8w/FMbswvfqL5cF+zEIAAaPxleozhQ/ZNY=; b=CKzV3cIwVpm6tHWxhioTw52d0r7CZPeF9bXqQunngALteiitIlzRl6BG QxPB1flbuJOwLInzrsUA6eCNhOnTq5B9mafEMwa2uZcZzf+0rCjAzJzi5 o4CMNr2MQummtiYTVHHvHIlBf49TB/Qr83TiBzXcDZ2AvUIc/CMsW8WET Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BvAQDvBKlZ/xbLJq1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBhD6BFY8LkHErd4dCkAAuhRkChFEVAQIBAQEBAQEBayiFGAEBAQE?= =?us-ascii?q?CARoJTQkFCwsYIAEGAwICISURBgEMBgIBAReJfgMNCBCvXYInJ4cUDYQaAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBGAWDKoNQgWMrgXBYNYJXhTGCYQWKCJYrPIdbYYc?= =?us-ascii?q?fhHaCE4Vng1mHG4xOgQSIczUigQ0yIQgcFUmEXzkcgWk+NgWKWQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.41,457,1498521600";  d="scan'208,217";a="654323011"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Sep 2017 06:59:33 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v816xXfG020836; Fri, 1 Sep 2017 06:59:33 GMT
Subject: Re: [OPS-DIR] Opsdir last call review of draft-ietf-tsvwg-sctp-ndata-12
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Michael Tuexen <tuexen@fh-muenster.de>
Cc: Stefan Winter <stefan.winter@restena.lu>, "ops-dir@ietf.org" <ops-dir@ietf.org>, draft-ietf-tsvwg-sctp-ndata.all@ietf.org, "tsvwg@ietf.org" <tsvwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IESG IESG <iesg@ietf.org>
References: <150287547583.12471.9085655210334710687@ietfa.amsl.com> <FDCFFA8C-8828-4578-A66E-A1AD7FF9BDC9@fh-muenster.de> <1a39dff3-55a9-fe1d-7e19-a0fbd0b2751b@restena.lu> <F05D0F1F-47E2-4477-BFD9-F0119A4609FC@fh-muenster.de> <f4d121e4-44f5-e85d-98b1-bbea317a7539@cisco.com> <5CEB294C-AAC8-4F03-901D-487CD62BB491@fh-muenster.de> <41a1e8f1-2398-4d94-7021-638acdd58eb7@cisco.com> <1FFDADBA-4132-4D3B-B68C-A89A50AF1E24@fh-muenster.de> <CAKKJt-dM1q9NDe8r=q-aqdWW0i3i8mSYLCNssU4cvjo22GRRyw@mail.gmail.com> <BD327429-5C8F-4034-A9E7-834FDB1E7FB6@fh-muenster.de> <CAKKJt-fuJWEMd79Z2zRmg4GU8hpVcqSfN+Y6xLioMUmwu8d6fw@mail.gmail.com> <0E628ABF-6E0E-40A6-87EE-CA94A93FE0A5@fh-muenster.de> <CAKKJt-c5CnGnpP9Ky8j6=jvPpygLG+t2UZhF68+XP8p4x06veA@mail.gmail.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <78e79022-4f9b-c093-27fb-b6392d4cc689@cisco.com>
Date: Fri, 1 Sep 2017 08:59:32 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CAKKJt-c5CnGnpP9Ky8j6=jvPpygLG+t2UZhF68+XP8p4x06veA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------4BCF4298F57F46930484D486"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_6LMysrkzf6XvC7Sen0dLlmP1KU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Sep 2017 06:59:44 -0000

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

On 8/31/2017 11:01 PM, Spencer Dawkins at IETF wrote:
> Hi, Michael,
>
> On Thu, Aug 31, 2017 at 2:56 PM, Michael Tuexen <tuexen@fh-muenster.de 
> <mailto:tuexen@fh-muenster.de>> wrote:
>
>
>     > On 31. Aug 2017, at 15:46, Spencer Dawkins at IETF
>     <spencerdawkins.ietf@gmail.com
>     <mailto:spencerdawkins.ietf@gmail.com>> wrote:
>     >
>     > Hi, Michael,
>     >
>     > On Thu, Aug 31, 2017 at 8:25 AM, Michael Tuexen
>     <tuexen@fh-muenster.de <mailto:tuexen@fh-muenster.de>> wrote:
>     > > On 31. Aug 2017, at 14:50, Spencer Dawkins at IETF
>     <spencerdawkins.ietf@gmail.com
>     <mailto:spencerdawkins.ietf@gmail.com>> wrote:
>     > >
>     > > Just interjecting ...
>     > >
>     > > On Thu, Aug 31, 2017 at 7:25 AM, Michael Tuexen
>     <tuexen@fh-muenster.de <mailto:tuexen@fh-muenster.de>> wrote:
>     > >
>     > > > On 31. Aug 2017, at 14:14, Benoit Claise <bclaise@cisco.com
>     <mailto:bclaise@cisco.com>> wrote:
>     > > >
>     > > > Hi Michael,
>     > > >>> On 30. Aug 2017, at 18:51, Benoit Claise
>     <bclaise@cisco.com <mailto:bclaise@cisco.com>> wrote:
>     > > >>>
>     > > >>> Michael,
>     > > >>>
>     > > >>> I stumbled on the same point as Stefan.
>     > > >> Hi Benoit,
>     > > >>
>     > > >> thanks for reviewing the document. See my comments in-line.
>     > > >>
>     > > >> Best regards
>     > > >> Michael
>     > > >>> First of, I had to review RFC4960 for TSN/SSN. I was not
>     sure whether TSN was per stream or not
>     > > >>> It would have helped me to repeat this information in the
>     intro.
>     > > >>> Ok, to be candid, I deduced this information from figure 1
>     and 2.
>     > > >>>>>>> And the rest are only musings not needing any action
>     if the authors don't want
>     > > >>>>>>> to action on them:
>     > > >>>>>>>
>     > > >>>>>>> The introduction presents a good use case, quoting:
>     "e.g., when the
>     > > >>>>>>> transmission of an urgent
>     > > >>>>>>>  message is blocked from transmission because the
>     sender has started
>     > > >>>>>>>  the transmission of another, possibly large, message".
>     > > >>>>>>>
>     > > >>>>>>> The later queueing example in figure 1 has three SIDs
>     being queued
>     > > >>>>>>> simultanseously. It is not clear which of those "has
>     already started" and which
>     > > >>>>>> There is actually one message queued for stream 0,
>     three messages for stream 1,
>     > > >>>>>> and one message for stream 2.
>     > > >>>>>>> are the important ones being delayed. For a better
>     understanding of the reader,
>     > > >>>>>> The figure is about in which sequence they are put on
>     the wire. So no
>     > > >>>>>> transmission has startet. This examples also does not
>     deal with the case
>     > > >>>>>> of one stream having a higher priority than another.
>     That would be an
>     > > >>>>>> example using a priority scheduler. This examples
>     illustrates the round
>     > > >>>>>> robin scheduler.
>     > > >>>>>> The point here is that a single scheduler (the round
>     robin scheduler, for
>     > > >>>>>> example) behaves differently when user message
>     interleaving is used or not.
>     > > >>>>>> That is an important point: You can even use the
>     schedulers with regular
>     > > >>>>>> DATA chunk, i.e. with user message interleaving being
>     negotiated.
>     > > >>> This was my source of confusion.
>     > > >>> With figure 1 and figure 2, you want to show the effect of
>     Round Robin Scheduler with and without User Message Interleaving,
>     while we were expecting the figure 2 to be the solution from this
>     spec. Hence Stefan and I were looking for this "urgent message" in
>     figure 2.
>     > > >> I don't know what you mean with "solution from this spec"
>     means. This spec introduces
>     > > >> stream schedulers and a protocol extension to allow
>     interleaving of user messages.
>     > > >> Using this to implement an "urgent" concept is only one
>     possibility: usage of a
>     > > >> strict priority scheduler (SCTP_SS_PRIO). So this "urgent"
>     is misleading. It seems
>     > > >> to ring the wrong bells. That is why I suggested to remove
>     it...
>     > > >>>>>>> it might be useful to revise the figure so that the
>     head-of-line blocking
>     > > >>>>>>> happens for SID 1 because transmission of  0 and 2 has
>     already started (and
>     > > >>>>>>> declare SID 1 to be the "important" message). The
>     ASCII art would just have to
>     > > >>>>>>> indent SID 1 content a bit (placing 0 and 2 earlier in
>     time), and the resulting
>     > > >>>>>>> serialisation would then put all the SID 1 messages at
>     the very end, when 0 and
>     > > >>>>>>> 2 have been completely submitted (right?).
>     > > >>>>>> One could think about adding another example based on
>     the priority scheduler
>     > > >>>>>> and giving stream 1 a higher priority. But for
>     illustrating the point of
>     > > >>>>>> schedulers behaving differently depending on the
>     negotiation of user message
>     > > >>>>>> interleaving this seems not necessary.
>     > > >>>>> That second example might indeed be useful.
>     > > >>>>>
>     > > >>>>> It's simply a bit strange that in the introduction you
>     speak about an
>     > > >>>>> "urgent" message (something deserving a higher-priority
>     sending) and
>     > > >>>>> that another transmission has already started - but then
>     the example has
>     > > >>>>> none of those two.
>     > > >>> Exactly.
>     > > >>> Please add this extra example.
>     > > >>> This would also clarify from the introduction that when
>     you write ...
>     > > >>>
>     > > >>>   The sending of such large messages over
>     > > >>>   SCTP as specified in [RFC4960] can result in a form of
>     sender side
>     > > >>>   head of line blocking (e.g., when the transmission of an
>     urgent
>     > > >>>   message is blocked from transmission because the sender
>     has started
>     > > >>>   the transmission of another, possibly large, message).
>     > > >>>
>     > > >>> .. the notion of transmission urgency is not within a
>     stream but across streams, and that can be achieved with a
>     priority scheduler.
>     > > >> I would actually prefer to remove the word "urgent" from
>     that sentence. This just rings the wrong bells.
>     > > > That's a missed opportunity in mind, but your call.
>     > > Hmm. Let me remove the word "urgent"...
>     > >
>     > > Yes, please! I wasn't wild about it, either.
>     > It's done:
>     >
>     https://github.com/sctplab/sctp-idata/commit/cf7b331512cd85d6195eb88fa96360673293323f
>     <https://github.com/sctplab/sctp-idata/commit/cf7b331512cd85d6195eb88fa96360673293323f>
>     > >
>     > > >>> The text might have to be rephrased to explain that this
>     spec provides the ability to create stream scheduler with
>     different relative stream treatments.
>     > > >> What about:
>     > > >>
>     > > >> OLD TEXT
>     > > >>    This document also defines several stream schedulers for
>     general SCTP
>     > > >>    associations.  The stream schedulers may behave
>     differently depending
>     > > >>    on whether user message interleaving has been negotiated
>     for the
>     > > >>    association or not.
>     > > >>
>     > > >> NEW TEXT
>     > > >>    This document also defines several stream schedulers for
>     general SCTP
>     > > >>    associations allowing different relative stream treatments.
>     > > >>    The stream schedulers may behave differently depending
>     > > >>    on whether user message interleaving has been negotiated
>     for the
>     > > >>    association or not.
>     > > >>
>     > > >> Would that address this issue?
>     > > > ok.
>     > > Fixed.
>     > > >>
>     > > >>> And also that urgent message would be placed in this high
>     priority stream scheduler (reliable, I guess, but that's
>     orthogonal) stream.
>     > > >> I really would like to get rid of this. I don't think
>     giving the strict
>     > > >> priority scheduler as specific role here is a good idea.
>     > > >>
>     > > >> The RR scheduler was chosen as the simplest scheduler to
>     illustrate
>     > > >> that scheduler can behave differently when using
>     interleaving or not.
>     > > >>>> What about removing the word "urgent" from that sentence.
>     > > >>>>> In fact I wonder why you speak about urgent things in
>     the introduction
>     > > >>>>> at all. Neither the scheduler nor the interleaving are
>     designed to help
>     > > >>>>> urgent things to be sent earlier.
>     > > >>>>>
>     > > >>>>> All they do is make the transmission fairer so that
>     *all* chunks get a
>     > > >>>>> more even serialised distribution on the wire.
>     > > >>>> That is not true in general. If you use the priority
>     scheduler, one
>     > > >>>> stream gets preferred treatment. It also makes sure that
>     the time
>     > > >>>> of a message spent in the stream queue is shorter. So
>     these messages
>     > > >>>> get sent earlier.
>     > > >>>> In the case of the round robin scheduler, you are right
>     that this is
>     > > >>>> about getting fairer treatment. If you take the WFQ
>     scheduler, the
>     > > >>>> streams don't get the same treatment, but it depends on
>     the weight
>     > > >>>> given to the stream.
>     > > >>>>> So, rather than saying that the spec helps urgent things
>     to be sent
>     > > >>>>> earlier, it should maybe rather state that the spec
>     helps every message
>     > > >>>>> getting an equal, and equally distributed, share of the
>     medium.
>     > > >>>> It is not meant that the spec does this. It was one
>     example, what
>     > > >>>> a particular stream scheduler does. But there are
>     multiple schedulers
>     > > >>>> defined in the document.
>     > > >>>>
>     > > >>>> The RR scheduler example is not intended to illustrate
>     what you can do
>     > > >>>> with all the schedulers, but that using message
>     interleaving or not
>     > > >>>> has an impact on the scheduler. That is meant by stating:
>     > > >>>>
>     > > >>>> This document also defines several stream schedulers for
>     general SCTP associations.
>     > > >>>> The stream schedulers may behave differently depending on
>     whether user message
>     > > >>>> interleaving has been negotiated for the association or not.
>     > > >>>>
>     > > >>>> This is followed by illustrating this using the RR scheduler.
>     > > >>>>
>     > > >>>> Best regards
>     > > >>> Also, I don't see the value of the last sentence in this
>     paragraph, especially with RFC2119 MAY.
>     > > >>>
>     > > >>>   This section defines several stream schedulers.  The stream
>     > > >>>   schedulers may behave differently depending on whether
>     user message
>     > > >>>   interleaving has been negotiated for the association or
>     not.  An
>     > > >>>   implementation MAY implement any subset of them.
>     > > >> During the review the question was brought up which
>     scheduler have to be implemented
>     > > >> by an implementation. This sentence was add to address it.
>     > > >> If you want, I can remove it.
>     > > > The point is that the MAY is that sentence doesn't mean
>     anything.
>     > > > Maybe you mean:
>     > > >
>     > > > An implementation MUST implement at least one stream scheduler.
>     > > That would require an implementation to implement at least one of
>     > > the ones being listed. You are right in the sense that an
>     implementation
>     > > MUST implement at least one stream scheduler, but the original
>     text
>     > > allows that one not to be specified in this document.
>     > >
>     > > Are you saying that an implementation MUST implement one of
>     list defined
>     > > by this document?
>     > >
>     > > I'm pretty sure (and this came up in my AD review) the problem
>     is that the original specification DID define a stream scheduler,
>     that's wasn't called a stream scheduler, but SCTP implementations
>     did schedule streams. And that didn't matter until there was more
>     than one way to schedule streams (as in this document).
>     > The original specification did NOT specify a stream scheduler
>     and left this completely implementation
>     > specific.
>     > Right now Linux is using (and only supporting a single
>     scheduler) what we call in this document
>     > SCTP_SS_FCFS. FreeBSD's default scheduler is what we call in
>     this document SCTP_SS_RR and
>     > Solaris uses one of these, forgot which one. Among these kernel
>     implementations, only FreeBSD
>     > supports multiple streams schedulers and its selection. Possibly
>     other closed source SCTP
>     > implementations might support other schedulers. Don't know.
>     >
>     > Thanks for getting that right for me ...
>     >
>     > Spencer
>     >
>     >  > So you're working out better wording that says something like
>     "in addition to the way the original specification scheduled
>     streams, we're defining more of them". I think.
>     > I think we wanted to say something like:
>     >
>     > Here is a list of schedulers. Your implementation might support
>     some of them, but this is
>     > left open. So you can't rely on it.
>     >
>     > The list of schedulers we specified includes the ones being used
>     as default by FreeBSD, Linux and
>     > Solaris and was extended by the ones supported by FreeBSD and
>     the one explicitly required by
>     > WebRTC, which is SCTP_SS_WFQ.
>     >
>     > What about this change:
>     >
>     > OLD TEXT:
>     >    An implementation MAY implement any subset of them.
>     >
>     > NEW TEXT:
>     >    An implementation MAY implement any subset of them. If the
>     implementation
>     >    is used for WebRTC Datachannels as specified in
>     [I-D.ietf-rtcweb-data-channel]
>     >    it MUST implement the Weighted Fair Queueing Scheduler
>     defined in Section 3.6.
>     >
>     > That works for me, but I'll let Benoit reply.
>     Benoit?
>
>
> Since I'm not sure which timezone Benoit is in (except that I know 
> it's Yang Central Time), I'll respond by saying that I did talk with 
> Benoit on the call, after sending him this privately:
>
>
>     This is tripping over the same thing I was tripping over - SCTP
>     standards haven't had a stream scheduler, but SCTP implementations
>     scheduled streams. So Michael was thinking that you were asking
>     about forcing existing implementations to implement one of the new
>     ones.
>
>     His response was to propose text basically saying "in addition to
>     what you're doing now, you MAY do one or more of the following".
>
>     I'm sorry I garbled my point so badly.
>
> Benoit said on the call (if I understood him correctly) that my 
> explanation (filtered through your correction) worked for him. The 
> point I was trying to make earlier was that SCTP implementations 
> scheduled streams somehow, and that your document wasn't an effort to 
> tell them to stop doing what they were doing, but that implementers 
> now had more standardized options than they did before.
>
> I think your proposed text says that well.
>
> At this point, I think you're ready to submit a revised ID to reflect 
> the comments you've received. I'll review your changes, and that will 
> give Benoit a chance to interrupt if he needs to -
no interrupt needed. I'll trust the venerable Spencer.

Regards, Benoit
> he's quite responsive, especially when he doesn't spend the evening on 
> a telechat.
>
> Thanks, and it's always a pleasure.
>
> Spencer
>
>     >
>     > Spencer
>     >
>     > Best regards
>     > Michael
>     > >
>     > > ?
>     > >
>     > > Spencer
>     >
>     >
>
>


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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 8/31/2017 11:01 PM, Spencer Dawkins
      at IETF wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAKKJt-c5CnGnpP9Ky8j6=jvPpygLG+t2UZhF68+XP8p4x06veA@mail.gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div dir="ltr">Hi, Michael,
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Thu, Aug 31, 2017 at 2:56 PM,
            Michael Tuexen <span dir="ltr">&lt;<a
                href="mailto:tuexen@fh-muenster.de" target="_blank"
                moz-do-not-send="true">tuexen@fh-muenster.de</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <div class="m_4016144414174465647gmail-HOEnZb">
                <div class="m_4016144414174465647gmail-h5"><br>
                  &gt; On 31. Aug 2017, at 15:46, Spencer Dawkins at
                  IETF &lt;<a
                    href="mailto:spencerdawkins.ietf@gmail.com"
                    target="_blank" moz-do-not-send="true">spencerdawkins.ietf@gmail.com</a><wbr>&gt;
                  wrote:<br>
                  &gt;<br>
                  &gt; Hi, Michael,<br>
                  &gt;<br>
                  &gt; On Thu, Aug 31, 2017 at 8:25 AM, Michael Tuexen
                  &lt;<a href="mailto:tuexen@fh-muenster.de"
                    target="_blank" moz-do-not-send="true">tuexen@fh-muenster.de</a>&gt;
                  wrote:<br>
                  &gt; &gt; On 31. Aug 2017, at 14:50, Spencer Dawkins
                  at IETF &lt;<a
                    href="mailto:spencerdawkins.ietf@gmail.com"
                    target="_blank" moz-do-not-send="true">spencerdawkins.ietf@gmail.com</a><wbr>&gt;
                  wrote:<br>
                  &gt; &gt;<br>
                  &gt; &gt; Just interjecting ...<br>
                  &gt; &gt;<br>
                  &gt; &gt; On Thu, Aug 31, 2017 at 7:25 AM, Michael
                  Tuexen &lt;<a href="mailto:tuexen@fh-muenster.de"
                    target="_blank" moz-do-not-send="true">tuexen@fh-muenster.de</a>&gt;
                  wrote:<br>
                  &gt; &gt;<br>
                  &gt; &gt; &gt; On 31. Aug 2017, at 14:14, Benoit
                  Claise &lt;<a href="mailto:bclaise@cisco.com"
                    target="_blank" moz-do-not-send="true">bclaise@cisco.com</a>&gt;
                  wrote:<br>
                  &gt; &gt; &gt;<br>
                  &gt; &gt; &gt; Hi Michael,<br>
                  &gt; &gt; &gt;&gt;&gt; On 30. Aug 2017, at 18:51,
                  Benoit Claise &lt;<a href="mailto:bclaise@cisco.com"
                    target="_blank" moz-do-not-send="true">bclaise@cisco.com</a>&gt;
                  wrote:<br>
                  &gt; &gt; &gt;&gt;&gt;<br>
                  &gt; &gt; &gt;&gt;&gt; Michael,<br>
                  &gt; &gt; &gt;&gt;&gt;<br>
                  &gt; &gt; &gt;&gt;&gt; I stumbled on the same point as
                  Stefan.<br>
                  &gt; &gt; &gt;&gt; Hi Benoit,<br>
                  &gt; &gt; &gt;&gt;<br>
                  &gt; &gt; &gt;&gt; thanks for reviewing the document.
                  See my comments in-line.<br>
                  &gt; &gt; &gt;&gt;<br>
                  &gt; &gt; &gt;&gt; Best regards<br>
                  &gt; &gt; &gt;&gt; Michael<br>
                  &gt; &gt; &gt;&gt;&gt; First of, I had to review
                  RFC4960 for TSN/SSN. I was not sure whether TSN was
                  per stream or not<br>
                  &gt; &gt; &gt;&gt;&gt; It would have helped me to
                  repeat this information in the intro.<br>
                  &gt; &gt; &gt;&gt;&gt; Ok, to be candid, I deduced
                  this information from figure 1 and 2.<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; And the rest
                  are only musings not needing any action if the authors
                  don't want<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; to action on
                  them:<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; The
                  introduction presents a good use case, quoting: "e.g.,
                  when the<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; transmission of
                  an urgent<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;  message is
                  blocked from transmission because the sender has
                  started<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;  the
                  transmission of another, possibly large, message".<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; The later
                  queueing example in figure 1 has three SIDs being
                  queued<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;
                  simultanseously. It is not clear which of those "has
                  already started" and which<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; There is actually
                  one message queued for stream 0, three messages for
                  stream 1,<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; and one message for
                  stream 2.<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; are the
                  important ones being delayed. For a better
                  understanding of the reader,<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; The figure is about
                  in which sequence they are put on the wire. So no<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; transmission has
                  startet. This examples also does not deal with the
                  case<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; of one stream
                  having a higher priority than another. That would be
                  an<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; example using a
                  priority scheduler. This examples illustrates the
                  round<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; robin scheduler.<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; The point here is
                  that a single scheduler (the round robin scheduler,
                  for<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; example) behaves
                  differently when user message interleaving is used or
                  not.<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; That is an
                  important point: You can even use the schedulers with
                  regular<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; DATA chunk, i.e.
                  with user message interleaving being negotiated.<br>
                  &gt; &gt; &gt;&gt;&gt; This was my source of
                  confusion.<br>
                  &gt; &gt; &gt;&gt;&gt; With figure 1 and figure 2, you
                  want to show the effect of Round Robin Scheduler with
                  and without User Message Interleaving, while we were
                  expecting the figure 2 to be the solution from this
                  spec. Hence Stefan and I were looking for this "urgent
                  message" in figure 2.<br>
                  &gt; &gt; &gt;&gt; I don't know what you mean with
                  "solution from this spec" means. This spec introduces<br>
                  &gt; &gt; &gt;&gt; stream schedulers and a protocol
                  extension to allow interleaving of user messages.<br>
                  &gt; &gt; &gt;&gt; Using this to implement an "urgent"
                  concept is only one possibility: usage of a<br>
                  &gt; &gt; &gt;&gt; strict priority scheduler
                  (SCTP_SS_PRIO). So this "urgent" is misleading. It
                  seems<br>
                  &gt; &gt; &gt;&gt; to ring the wrong bells. That is
                  why I suggested to remove it...<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; it might be
                  useful to revise the figure so that the head-of-line
                  blocking<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; happens for SID
                  1 because transmission of  0 and 2 has already started
                  (and<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; declare SID 1
                  to be the "important" message). The ASCII art would
                  just have to<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; indent SID 1
                  content a bit (placing 0 and 2 earlier in time), and
                  the resulting<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; serialisation
                  would then put all the SID 1 messages at the very end,
                  when 0 and<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; 2 have been
                  completely submitted (right?).<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; One could think
                  about adding another example based on the priority
                  scheduler<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; and giving stream 1
                  a higher priority. But for illustrating the point of<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; schedulers behaving
                  differently depending on the negotiation of user
                  message<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; interleaving this
                  seems not necessary.<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt; That second example
                  might indeed be useful.<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt; It's simply a bit
                  strange that in the introduction you speak about an<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt; "urgent" message
                  (something deserving a higher-priority sending) and<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt; that another
                  transmission has already started - but then the
                  example has<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt; none of those two.<br>
                  &gt; &gt; &gt;&gt;&gt; Exactly.<br>
                  &gt; &gt; &gt;&gt;&gt; Please add this extra example.<br>
                  &gt; &gt; &gt;&gt;&gt; This would also clarify from
                  the introduction that when you write ...<br>
                  &gt; &gt; &gt;&gt;&gt;<br>
                  &gt; &gt; &gt;&gt;&gt;   The sending of such large
                  messages over<br>
                  &gt; &gt; &gt;&gt;&gt;   SCTP as specified in
                  [RFC4960] can result in a form of sender side<br>
                  &gt; &gt; &gt;&gt;&gt;   head of line blocking (e.g.,
                  when the transmission of an urgent<br>
                  &gt; &gt; &gt;&gt;&gt;   message is blocked from
                  transmission because the sender has started<br>
                  &gt; &gt; &gt;&gt;&gt;   the transmission of another,
                  possibly large, message).<br>
                  &gt; &gt; &gt;&gt;&gt;<br>
                  &gt; &gt; &gt;&gt;&gt; .. the notion of transmission
                  urgency is not within a stream but across streams, and
                  that can be achieved with a priority scheduler.<br>
                  &gt; &gt; &gt;&gt; I would actually prefer to remove
                  the word "urgent" from that sentence. This just rings
                  the wrong bells.<br>
                  &gt; &gt; &gt; That's a missed opportunity in mind,
                  but your call.<br>
                  &gt; &gt; Hmm. Let me remove the word "urgent"...<br>
                  &gt; &gt;<br>
                  &gt; &gt; Yes, please! I wasn't wild about it, either.<br>
                  &gt; It's done:<br>
                  &gt; <a
href="https://github.com/sctplab/sctp-idata/commit/cf7b331512cd85d6195eb88fa96360673293323f"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">https://github.com/sctplab/sct<wbr>p-idata/commit/cf7b331512cd85d<wbr>6195eb88fa96360673293323f</a><br>
                  &gt; &gt;<br>
                  &gt; &gt; &gt;&gt;&gt; The text might have to be
                  rephrased to explain that this spec provides the
                  ability to create stream scheduler with different
                  relative stream treatments.<br>
                  &gt; &gt; &gt;&gt; What about:<br>
                  &gt; &gt; &gt;&gt;<br>
                  &gt; &gt; &gt;&gt; OLD TEXT<br>
                  &gt; &gt; &gt;&gt;    This document also defines
                  several stream schedulers for general SCTP<br>
                  &gt; &gt; &gt;&gt;    associations.  The stream
                  schedulers may behave differently depending<br>
                  &gt; &gt; &gt;&gt;    on whether user message
                  interleaving has been negotiated for the<br>
                  &gt; &gt; &gt;&gt;    association or not.<br>
                  &gt; &gt; &gt;&gt;<br>
                  &gt; &gt; &gt;&gt; NEW TEXT<br>
                  &gt; &gt; &gt;&gt;    This document also defines
                  several stream schedulers for general SCTP<br>
                  &gt; &gt; &gt;&gt;    associations allowing different
                  relative stream treatments.<br>
                  &gt; &gt; &gt;&gt;    The stream schedulers may behave
                  differently depending<br>
                  &gt; &gt; &gt;&gt;    on whether user message
                  interleaving has been negotiated for the<br>
                  &gt; &gt; &gt;&gt;    association or not.<br>
                  &gt; &gt; &gt;&gt;<br>
                  &gt; &gt; &gt;&gt; Would that address this issue?<br>
                  &gt; &gt; &gt; ok.<br>
                  &gt; &gt; Fixed.<br>
                  &gt; &gt; &gt;&gt;<br>
                  &gt; &gt; &gt;&gt;&gt; And also that urgent message
                  would be placed in this high priority stream scheduler
                  (reliable, I guess, but that's orthogonal) stream.<br>
                  &gt; &gt; &gt;&gt; I really would like to get rid of
                  this. I don't think giving the strict<br>
                  &gt; &gt; &gt;&gt; priority scheduler as specific role
                  here is a good idea.<br>
                  &gt; &gt; &gt;&gt;<br>
                  &gt; &gt; &gt;&gt; The RR scheduler was chosen as the
                  simplest scheduler to illustrate<br>
                  &gt; &gt; &gt;&gt; that scheduler can behave
                  differently when using interleaving or not.<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; What about removing the
                  word "urgent" from that sentence.<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt; In fact I wonder why
                  you speak about urgent things in the introduction<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt; at all. Neither the
                  scheduler nor the interleaving are designed to help<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt; urgent things to be
                  sent earlier.<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt;<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt; All they do is make the
                  transmission fairer so that *all* chunks get a<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt; more even serialised
                  distribution on the wire.<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; That is not true in
                  general. If you use the priority scheduler, one<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; stream gets preferred
                  treatment. It also makes sure that the time<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; of a message spent in the
                  stream queue is shorter. So these messages<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; get sent earlier.<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; In the case of the round
                  robin scheduler, you are right that this is<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; about getting fairer
                  treatment. If you take the WFQ scheduler, the<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; streams don't get the same
                  treatment, but it depends on the weight<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; given to the stream.<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt; So, rather than saying
                  that the spec helps urgent things to be sent<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt; earlier, it should
                  maybe rather state that the spec helps every message<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;&gt; getting an equal, and
                  equally distributed, share of the medium.<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; It is not meant that the
                  spec does this. It was one example, what<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; a particular stream
                  scheduler does. But there are multiple schedulers<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; defined in the document.<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; The RR scheduler example is
                  not intended to illustrate what you can do<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; with all the schedulers,
                  but that using message interleaving or not<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; has an impact on the
                  scheduler. That is meant by stating:<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; This document also defines
                  several stream schedulers for general SCTP
                  associations.<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; The stream schedulers may
                  behave differently depending on whether user message<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; interleaving has been
                  negotiated for the association or not.<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; This is followed by
                  illustrating this using the RR scheduler.<br>
                  &gt; &gt; &gt;&gt;&gt;&gt;<br>
                  &gt; &gt; &gt;&gt;&gt;&gt; Best regards<br>
                  &gt; &gt; &gt;&gt;&gt; Also, I don't see the value of
                  the last sentence in this paragraph, especially with
                  RFC2119 MAY.<br>
                  &gt; &gt; &gt;&gt;&gt;<br>
                  &gt; &gt; &gt;&gt;&gt;   This section defines several
                  stream schedulers.  The stream<br>
                  &gt; &gt; &gt;&gt;&gt;   schedulers may behave
                  differently depending on whether user message<br>
                  &gt; &gt; &gt;&gt;&gt;   interleaving has been
                  negotiated for the association or not.  An<br>
                  &gt; &gt; &gt;&gt;&gt;   implementation MAY implement
                  any subset of them.<br>
                  &gt; &gt; &gt;&gt; During the review the question was
                  brought up which scheduler have to be implemented<br>
                  &gt; &gt; &gt;&gt; by an implementation. This sentence
                  was add to address it.<br>
                  &gt; &gt; &gt;&gt; If you want, I can remove it.<br>
                  &gt; &gt; &gt; The point is that the MAY is that
                  sentence doesn't mean anything.<br>
                  &gt; &gt; &gt; Maybe you mean:<br>
                  &gt; &gt; &gt;<br>
                  &gt; &gt; &gt; An implementation MUST implement at
                  least one stream scheduler.<br>
                  &gt; &gt; That would require an implementation to
                  implement at least one of<br>
                  &gt; &gt; the ones being listed. You are right in the
                  sense that an implementation<br>
                  &gt; &gt; MUST implement at least one stream
                  scheduler, but the original text<br>
                  &gt; &gt; allows that one not to be specified in this
                  document.<br>
                  &gt; &gt;<br>
                  &gt; &gt; Are you saying that an implementation MUST
                  implement one of list defined<br>
                  &gt; &gt; by this document?<br>
                  &gt; &gt;<br>
                  &gt; &gt; I'm pretty sure (and this came up in my AD
                  review) the problem is that the original specification
                  DID define a stream scheduler, that's wasn't called a
                  stream scheduler, but SCTP implementations did
                  schedule streams. And that didn't matter until there
                  was more than one way to schedule streams (as in this
                  document).<br>
                  &gt; The original specification did NOT specify a
                  stream scheduler and left this completely
                  implementation<br>
                  &gt; specific.<br>
                  &gt; Right now Linux is using (and only supporting a
                  single scheduler) what we call in this document<br>
                  &gt; SCTP_SS_FCFS. FreeBSD's default scheduler is what
                  we call in this document SCTP_SS_RR and<br>
                  &gt; Solaris uses one of these, forgot which one.
                  Among these kernel implementations, only FreeBSD<br>
                  &gt; supports multiple streams schedulers and its
                  selection. Possibly other closed source SCTP<br>
                  &gt; implementations might support other schedulers.
                  Don't know.<br>
                  &gt;<br>
                  &gt; Thanks for getting that right for me ...<br>
                  &gt;<br>
                  &gt; Spencer<br>
                  &gt;<br>
                  &gt;  &gt; So you're working out better wording that
                  says something like "in addition to the way the
                  original specification scheduled streams, we're
                  defining more of them". I think.<br>
                  &gt; I think we wanted to say something like:<br>
                  &gt;<br>
                  &gt; Here is a list of schedulers. Your implementation
                  might support some of them, but this is<br>
                  &gt; left open. So you can't rely on it.<br>
                  &gt;<br>
                  &gt; The list of schedulers we specified includes the
                  ones being used as default by FreeBSD, Linux and<br>
                  &gt; Solaris and was extended by the ones supported by
                  FreeBSD and the one explicitly required by<br>
                  &gt; WebRTC, which is SCTP_SS_WFQ.<br>
                  &gt;<br>
                  &gt; What about this change:<br>
                  &gt;<br>
                  &gt; OLD TEXT:<br>
                  &gt;    An implementation MAY implement any subset of
                  them.<br>
                  &gt;<br>
                  &gt; NEW TEXT:<br>
                  &gt;    An implementation MAY implement any subset of
                  them. If the implementation<br>
                  &gt;    is used for WebRTC Datachannels as specified
                  in [I-D.ietf-rtcweb-data-channel]<br>
                  &gt;    it MUST implement the Weighted Fair Queueing
                  Scheduler defined in Section 3.6.<br>
                  &gt;<br>
                  &gt; That works for me, but I'll let Benoit reply.<br>
                </div>
              </div>
              Benoit?<br>
            </blockquote>
            <div><br>
            </div>
            <div>Since I'm not sure which timezone Benoit is in (except
              that I know it's Yang Central Time), I'll respond by
              saying that I did talk with Benoit on the call, after
              sending him this privately:</div>
          </div>
        </div>
        <blockquote style="margin:0 0 0 40px;border:none;padding:0px">
          <div class="gmail_extra">
            <div class="gmail_quote">
              <div><br>
              </div>
            </div>
          </div>
          <div class="gmail_extra">
            <div class="gmail_quote">
              <div>
                <div>This is tripping over the same thing I was tripping
                  over - SCTP standards haven't had a stream scheduler,
                  but SCTP implementations scheduled streams. So Michael
                  was thinking that you were asking about forcing
                  existing implementations to implement one of the new
                  ones. </div>
              </div>
            </div>
          </div>
          <div class="gmail_extra">
            <div class="gmail_quote">
              <div>
                <div><br>
                </div>
              </div>
            </div>
          </div>
          <div class="gmail_extra">
            <div class="gmail_quote">
              <div>
                <div>His response was to propose text basically saying
                  "in addition to what you're doing now, you MAY do one
                  or more of the following". </div>
              </div>
            </div>
          </div>
          <div class="gmail_extra">
            <div class="gmail_quote">
              <div>
                <div><br>
                </div>
              </div>
            </div>
          </div>
          <div class="gmail_extra">
            <div class="gmail_quote">
              <div>
                <div>I'm sorry I garbled my point so badly.</div>
              </div>
              <div><br>
              </div>
            </div>
          </div>
        </blockquote>
        Benoit said on the call (if I understood him correctly) that my
        explanation (filtered through your correction) worked for him.
        The point I was trying to make earlier was that SCTP
        implementations scheduled streams somehow, and that your
        document wasn't an effort to tell them to stop doing what they
        were doing, but that implementers now had more standardized
        options than they did before.
        <div><br>
        </div>
        <div>I think your proposed text says that well. <br>
          <div><br>
          </div>
          <div>At this point, I think you're ready to submit a revised
            ID to reflect the comments you've received. I'll review your
            changes, and that will give Benoit a chance to interrupt if
            he needs to - </div>
        </div>
      </div>
    </blockquote>
    no interrupt needed. I'll trust the venerable Spencer.<br>
    <br>
    Regards, Benoit<br>
    <blockquote type="cite"
cite="mid:CAKKJt-c5CnGnpP9Ky8j6=jvPpygLG+t2UZhF68+XP8p4x06veA@mail.gmail.com">
      <div dir="ltr">
        <div>
          <div>he's quite responsive, especially when he doesn't spend
            the evening on a telechat.</div>
          <div><br>
          </div>
          <div>Thanks, and it's always a pleasure.</div>
          <div><br>
          </div>
          <div>Spencer<br>
            <div class="gmail_extra">
              <div class="gmail_quote">
                <div> </div>
                <blockquote class="gmail_quote" style="margin:0px 0px
                  0px 0.8ex;border-left:1px solid
                  rgb(204,204,204);padding-left:1ex">
                  <div class="m_4016144414174465647gmail-HOEnZb">
                    <div class="m_4016144414174465647gmail-h5">&gt;<br>
                      &gt; Spencer<br>
                      &gt;<br>
                      &gt; Best regards<br>
                      &gt; Michael<br>
                      &gt; &gt;<br>
                      &gt; &gt; ?<br>
                      &gt; &gt;<br>
                      &gt; &gt; Spencer<br>
                      &gt;<br>
                      &gt;<br>
                      <br>
                    </div>
                  </div>
                </blockquote>
              </div>
              <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------4BCF4298F57F46930484D486--

