
From nobody Mon May  1 04:18:38 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 58CD61286B1; Mon,  1 May 2017 04:18:30 -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 a6LV5uxYJrs0; Mon,  1 May 2017 04:18:28 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73D85124BFA; Mon,  1 May 2017 04:16:01 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id v41BFwS3012338; Mon, 1 May 2017 12:15:58 +0100
Received: from 950129200 (xeams.riffcube.co.uk [188.246.205.89]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id v41BFqS6012301 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 1 May 2017 12:15:55 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Cc: <netmod-chairs@ietf.org>, <warren@kumari.net>, <draft-ietf-netmod-yang-model-classification@ietf.org>, <netmod@ietf.org>
References: <149360589744.9906.9498469901914786081.idtracker@ietfa.amsl.com>
In-Reply-To: <149360589744.9906.9498469901914786081.idtracker@ietfa.amsl.com>
Subject: RE: [netmod] Last Call: <draft-ietf-netmod-yang-model-classification-06.txt> (YANG Module Classification) to Informational RFC
Date: Mon, 1 May 2017 12:15:46 +0100
Message-ID: <009f01d2c26c$4d733ca0$e859b5e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIDb54VphIAoa/Moaa5Fy8079WHh6F99QaQ
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23042.006
X-TM-AS-Result: No--28.113-10.0-31-10
X-imss-scan-details: No--28.113-10.0-31-10
X-TMASE-MatchedRID: C/snMIRQLS1fsB4HYR80ZggKAWhuC2ojb6bRSg4rpzsifM7JMNHW6wLy tDvV39h+ODYCThDek8N/zL5S7kM+hC4rw5gWcmxP+mHRL3uzOiKeimGtNywjttp1biJhIyNRXa2 +zE1cP+W4C2CZooc2fxsHDLcsSEIj1RbX+21X57Ogx+na8dyT1TtSuYjPEOigyL0CMroLynWrSt WuvqILVNInOZzevFRlfyi2iaH+RVvoZURPehMJ0i/MZ1E/Ptpx8GRhP/nTHNYsugxReYWqZqHZ5 NtLmicGLUwfBRI7MK94bFH7fUFhlDzemDCU+QwmSEQN/D/3cG6sKrCNemuWXi+Z/NhcdOmxW9mH 5DAsbhdUYj2YBex0VT6GA+hFKox/cqx1y4k8YIeEkZYbtr2mLfioIsi7Sa0gauHKE5Laxl8Pu/0 Lj0myK5b/mTnkM/SIHDnwvr6B+jQYB2fOueQzjzl/1fD/GopdyJ1gFgOMhOm2s0ar5ZAS9Ku6xV HLhqfxrFldG3ZH+DkEkwvLesmd5A==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9wZd3JdTe-feWa6yh2OPl2vSdT0>
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, 01 May 2017 11:18:30 -0000

Hi,

I've been reading, reviewing, and discussing this document for a number of
revisions. Of special concern was the relationship to RFC 8049 and
draft-wu-opsawg-service-model-explained.

The last two revisions have captured the essence of these discussions, and I am
happy with the document as it stands. I think it should be published as an
Informational RFC.

Thanks,
Adrian

> -----Original Message-----
> From: netmod [mailto:netmod-bounces@ietf.org] On Behalf Of The IESG
> Sent: 01 May 2017 03:32
> To: IETF-Announce
> Cc: netmod-chairs@ietf.org; warren@kumari.net; draft-ietf-netmod-yang-
> model-classification@ietf.org; netmod@ietf.org
> Subject: [netmod] Last Call:
<draft-ietf-netmod-yang-model-classification-06.txt>
> (YANG Module Classification) to Informational RFC
> 
> 
> The IESG has received a request from the NETCONF Data Modeling Language
> WG (netmod) to consider the following document:
> - 'YANG Module Classification'
>   <draft-ietf-netmod-yang-model-classification-06.txt> as Informational
> RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-05-14. 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 YANG data modeling language is currently being considered for a
>    wide variety of applications throughout the networking industry at
>    large.  Many standards-defining organizations (SDOs), open source
>    software projects, vendors and users are using YANG to develop and
>    publish YANG modules for a wide variety of applications.  At the same
>    time, there is currently no well-known terminology to categorize
>    various types of YANG modules.
> 
>    A consistent terminology would help with the categorization of YANG
>    modules, assist in the analysis of the YANG data modeling efforts in
>    the IETF and other organizations, and bring clarity to the YANG-
>    related discussions between the different groups.
> 
>    This document describes a set of concepts and associated terms to
>    support consistent classification of YANG modules.
> 
> 
> 
> 
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classification/
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-
> classification/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> 
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod


From nobody Mon May  1 04:41:15 2017
Return-Path: <kathleen.moriarty.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 9D508129422; Mon,  1 May 2017 04:41:06 -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 xSsgZCK-V6cN; Mon,  1 May 2017 04:41:04 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d: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 43C69129BDD; Mon,  1 May 2017 04:38:24 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id u75so91740107qka.3; Mon, 01 May 2017 04:38:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gmfD5FetHrd8FVmpwPxOpRDw9yWQ3Wq/hZKyxiBFchI=; b=cmPVVc7HnZ+MI/BZ4MNPjApwMM1N8A6QLShM8wARKwmM4zWPbSEYm2FMvM5rj1Ddt0 9ngJ3IY3L4BqmZ5QL1QVkE4OpRumH6jn6pwV36gZY6FkFxzwoq/n/IPW7uO55HbnuCCP sz9xrbGA9HvwzZ9btt4Dv615pAJsRB/v9g5e86fovicdSfAYvOeZTDZmL97xMMJE6R5p swgfkCqLWEz0jdqYsTOJciFnEwI0vgEUUdizdSX2BLSP3wtWuZjk/kEYgiEIUDdl+Dt7 Ykh+dAFzwNyftWeEcm7S7qLI0x77NfncMA9neT3VZVaROlMvEq6WmlcbfN234zeM9dXo i0fw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gmfD5FetHrd8FVmpwPxOpRDw9yWQ3Wq/hZKyxiBFchI=; b=HYj2is9PIsE4E9lxuBUF9ia0xTnLVWVenWl4rjuzfFybkzFzewCz+RIxP7L/YWUoJi /Qvfn/hMl2icWI97V6rGGTKW6SBs2NXXH2cfQ2QNg5fItxCnryIG+fdGjDNF2XlSlpuq o3rFjuKj73aGY2ah2pEiljVfkUL71NT9AmomsYf9d3X5YN6S/XyacMuzkMEP3nfhBuXU vQa3+DYo62rPdPBPdNCDG9sDr7tHeTMkds8TEzoaGbY9ErGipk1kCCKWb2vin5M/OM78 cxvxxsFtKgyC4aZpdF0TB8eQuK2mFIUbQIAIfiIaVDUJL54iPcIfxVotrjFQoLIaOifc PsEA==
X-Gm-Message-State: AN3rC/7kKssamzJPCf4HQiP/bPHYOnkfAkya/4qGjuQ43GIcRIH1R1Th r8nj4nOGoAT1HUbE2rQ=
X-Received: by 10.55.77.209 with SMTP id a200mr21691870qkb.11.1493638702975; Mon, 01 May 2017 04:38:22 -0700 (PDT)
Received: from [192.168.1.13] (209-6-124-204.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.124.204]) by smtp.gmail.com with ESMTPSA id z65sm10570355qkz.29.2017.05.01.04.38.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 01 May 2017 04:38:22 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Mailer: iPhone Mail (14D27)
In-Reply-To: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net>
Date: Mon, 1 May 2017 07:38:21 -0400
Cc: IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <67E8252A-76D9-4273-9218-972CE9A672DB@gmail.com>
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wfxZO2XGAvtTnTFWAXNS22hKKLc>
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, 01 May 2017 11:41:07 -0000

Hi Mark,

Thank you for your comments.  This draft is in the process of a major revisi=
on and will have another IETF last call.  I think most of your pikers have b=
een considered, but we'll make sure prior to posting an update.

Best regards,
Kathleen=20

Sent from my iPhone

> On Apr 30, 2017, at 11:45 PM, Mark Nottingham <mnot@mnot.net> wrote:
>=20
> Sorry for the late review; on the plus side, I'm coming to it with fresh e=
yes.
>=20
> Overall, this document reads as if it was originally written to highlight t=
he downsides of increased use of encryption, and then rewritten to be more n=
eutral in tone. Unfortunately, some of the original intent posited there sti=
ll seeps through.
>=20
> In doing so, it often fails to convey that there are any options other tha=
n "this has to be done by the network." I know that this has been cast as a s=
urvey of potential impacts, and therefore doesn't necessary need to enumerat=
e alternatives, but the way that it's written could easily lead a reader to t=
hink that there aren't alternatives. It also is odd that alternatives are no=
t enumerated when they're often well-known, and the really interesting issue=
s are in the tradeoffs between doing something in the network (i.e., as a th=
ird party) vs. by one of the endpoints (a first party to communication) or t=
heir delegates.
>=20
> For example, Section 2.2 talks about the importance of passive monitoring f=
or traffic surveys, but fails to discuss alternative means of gathering data=
 (e.g., anonymised data from content providers; telemetry from client implem=
entations) that are superior in some ways, limited in others. It would be a u=
seful contribution to characterise the tradeoffs here, so this is an opportu=
nity lost.
>=20
> Section 2.3.2.1 points out that "Web proxies are widely used", but fails t=
o note that the vast bulk of caching is done by endpoints -- browsers, CDNs a=
nd reverse proxies, thereby sidestepping the issues of encryption (although t=
hey have their own unique challenges). Discussing why this form of caching h=
as become prevalent might help inform network operators as to why getting th=
e economics and trust relationships of intermediation right is important.
>=20
> Section 2.3.2.2 motivates DPI as "Input for Differential Treatment", but f=
ails to note the developing efforts to coordinate client and server behaviou=
r to adapt to network conditions, without the need for stripping encryption.=

>=20
> Section 2.4 talks about need for compression proxies, but fails to note th=
e deployment of them in overlay networks (e.g., by Google Chrome, UCBrowser,=
 Opera Mini, etc.). There is a minefield of issues surrounding them, of cour=
se, but it's useful context.
>=20
> Section 2.5.2 does note that endpoint-based alternatives might be possible=
, but fizzles out after that. Exploring why they haven't developed would be a=
 substantial contribution.
>=20
> A few additional points:
>=20
> * The Introduction says "it is important to catalog existing standard func=
tions around network management, security and troubleshooting that have depe=
nding upon the availability of open information to function." Using the word=
 "standard" here is misleading; some of the described functions are not envi=
sioned or enshrined by Internet Standards.
>=20
> * The Introduction says "The IETF reiterates its view that pervasive monit=
oring is an attack..."  It's odd to have an Informational document "reiterat=
e" a BCP.
>=20
> * Much of the Introduction motivates this document as being about "network=
 management, security and troubleshooting." Then, later, it inserts things l=
ike "monitoring services", policy enforcement, and parental controls. These a=
re qualitatively very different things. Being able to monitor and run the ne=
twork to provide a service is not the same as being able to impose your will=
 upon the users of that service. Elevating the latter to the status of the f=
ormer is not something we should even unintentionally imply, even if it is c=
ommon practice.
>=20
> * Section 1.1 asserts that "Increased use of encryption (either opportunis=
tic or authenticated) will impact operations for security and network manage=
ment, causing a shift in how these functions are performed." This is an asse=
rtion about the future that's quite strong. I could see it saying that they *=
have* impacted, and then giving examples, or that they *might* impact them i=
n the future, but asserting that it *will* impact them seems like an asserti=
on that doesn't have IETF consensus.
>=20
> * Section 2.6.5 talks about injecting HTTP headers into a connection and f=
ails to note the significant privacy issues brought about by this practice. U=
sing encryption to defeat this is, to many in the IETF community, a feature,=
 not a bug.
>=20
>=20
> Hope this helps,
>=20
> --
> Mark Nottingham   https://www.mnot.net/
>=20


From nobody Mon May  1 07:13:51 2017
Return-Path: <jonathan@hansfords.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 63170128DE7; Mon,  1 May 2017 07:13:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level: 
X-Spam-Status: No, score=-1.988 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, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hansfords.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 c0CLqa2hQ8Jw; Mon,  1 May 2017 07:13:46 -0700 (PDT)
Received: from server.myfast.site (server.myfast.site [212.113.130.90]) (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 30CD4129BAE; Mon,  1 May 2017 07:11:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=hansfords.net; s=default; h=Content-Type:MIME-Version:Subject:References: In-Reply-To:Message-ID:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=mJSd6fXjPECiED7jZJ5lngW8yQK047lOexPx0uEdFww=; b=kJZniIpwsGAtD4L1+DYtwDzRR Xw53HmkP0vEcStc1fnTGGI7pr0oRDd5clQUDhX6z0u7tgE6RmlUTG/GMK8dp2HIsy6gRUctL/rOgV 0lj+Bb7PCAO3dav6huMhU/RwI3MDHtaBcL1wvRdr+n4OszZmbXTvfGJdc1c5EanYp+S9IrzezfmDH gxaFmQNW5fOs8JsSU/x2Ea02v89xKRVWasWRzVWJH5LotO6dEsjaq0zhlvKsTnK1R4KFRyYAwwjBN QxcTkRGBccd4NHJFlizbHgGnjV0qGJiHFTZkk7xmAG0rXbdEaV/rjAryY6jrjFVZiPPda/IK/xJDN qtH/yJeDw==;
Received: from [84.92.116.209] (port=33059 helo=[192.168.1.24]) by server.myfast.site with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from <jonathan@hansfords.net>) id 1d5C3H-001xXe-8u; Mon, 01 May 2017 15:11:47 +0100
Date: Mon, 1 May 2017 15:11:36 +0100
From: Jonathan Hansford <jonathan@hansfords.net>
To: IETF-Announce <ietf-announce@ietf.org>, ietf@ietf.org
Cc: netmod-chairs@ietf.org, warren@kumari.net,  draft-ietf-netmod-yang-model-classification@ietf.org, netmod@ietf.org
Message-ID: <46a76c75-fd04-4134-9a97-26d1567963d7@Spark>
In-Reply-To: <149360589744.9906.9498469901914786081.idtracker@ietfa.amsl.com>
References: <149360589744.9906.9498469901914786081.idtracker@ietfa.amsl.com>
Subject: Re: [netmod] Last Call: <draft-ietf-netmod-yang-model-classification-06.txt> (YANG Module Classification) to Informational RFC
X-Readdle-Message-ID: 46a76c75-fd04-4134-9a97-26d1567963d7@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="59074222_6b8b4567_ee4"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.myfast.site
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - hansfords.net
X-Get-Message-Sender-Via: server.myfast.site: authenticated_id: jonathan@hansfords.net
X-Authenticated-Sender: server.myfast.site: jonathan@hansfords.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/78B5snT1Q6KChhwOxm4gBjsBXQI>
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, 01 May 2017 14:13:49 -0000

--59074222_6b8b4567_ee4
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I have no substantive comments, but have noticed, among other things, a f=
ew somewhat inconsequential typos that could nevertheless impact readabil=
ity, particularly for those for whom English is a second language:
=E2=80=A2 Page 3, penultimate bullet: s/by network operator/by a network =
operator
=E2=80=A2 Why is figure 1 on page 5 when it is first referenced at the to=
p of page 4=3F
=E2=80=A2 Section 2.1, second paragraph (2 typos): s/peole or extarnal/pe=
ople or external
=E2=80=A2 Section 2.1, last paragraph: I don't understand the second sent=
ence that starts: =E2=80=9CAlthough it provides information =E2=80=A6=E2=80=
=9D
=E2=80=A2 Section 2.2, second paragraph: i don't understand the first sen=
tence that starts: =E2=80=9CAlthough the =5BR=46C7950=5D, =5BR=46C7950=5D=
 =E2=80=A6=E2=80=9D
=E2=80=A2 Section 3.3, second paragraph: s/include ability/include the ab=
ility
=E2=80=A2 Section 6: small point but I believe the second acknowledgement=
 should be me(=21), =E2=80=9CJonathan Hansford=E2=80=9D, not =E2=80=9CDav=
id=E2=80=9D

Jonathan

=3DO)

On 1 May 2017, 03:32 +0100, The IESG <iesg-secretary=40ietf.org>, wrote:
>
> The IESG has received a request from the NETCON=46 Data Modeling Langua=
ge
> WG (netmod) to consider the following document:
> - 'YANG Module Classification'
> <draft-ietf-netmod-yang-model-classification-06.txt> as Informational
> R=46C
>
> 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=40ietf.org mailing lists by 2017-05-14. Exceptionally, comments ma=
y be
> sent to iesg=40ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
> The YANG data modeling language is currently being considered for a
> wide variety of applications throughout the networking industry at
> large. Many standards-defining organizations (SDOs), open source
> software projects, vendors and users are using YANG to develop and
> publish YANG modules for a wide variety of applications. At the same
> time, there is currently no well-known terminology to categorize
> various types of YANG modules.
>
> A consistent terminology would help with the categorization of YANG
> modules, assist in the analysis of the YANG data modeling efforts in
> the IET=46 and other organizations, and bring clarity to the YANG-
> related discussions between the different groups.
>
> This document describes a set of concepts and associated terms to
> support consistent classification of YANG modules.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classific=
ation/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classific=
ation/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> netmod mailing list
> netmod=40ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

--59074222_6b8b4567_ee4
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<html xmlns=3D=22http://www.w3.org/1999/xhtml=22>
<head>
<title></title>
</head>
<body>
<div name=3D=22messageBodySection=22>I have no substantive comments, but =
have noticed, among other things, a few somewhat inconsequential typos th=
at could nevertheless impact readability, particularly for those for whom=
 English is a second language:<br />
=E2=80=A2 Page 3, penultimate bullet: s/by network operator/by a network =
operator<br />
=E2=80=A2 Why is figure 1 on page 5 when it is first referenced at the to=
p of page 4=3F<br />
=E2=80=A2 Section 2.1, second paragraph (2 typos): s/peole or extarnal/pe=
ople or external<br />
=E2=80=A2 Section 2.1, last paragraph: I don't understand the second sent=
ence that starts: =E2=80=9CAlthough it provides information =E2=80=A6=E2=80=
=9D<br />
=E2=80=A2 Section 2.2, second paragraph: i don't understand the first sen=
tence that starts: =E2=80=9CAlthough the =5BR=46C7950=5D, =5BR=46C7950=5D=
 =E2=80=A6=E2=80=9D<br />
=E2=80=A2 Section 3.3, second paragraph: s/include ability/include the ab=
ility<br />
=E2=80=A2 Section 6: small point but I believe the second acknowledgement=
 should be me(=21), =E2=80=9CJonathan Hansford=E2=80=9D, not =E2=80=9CDav=
id=E2=80=9D</div>
<div name=3D=22messageSignatureSection=22><br />
Jonathan<br />
<br />
=3DO)</div>
<div name=3D=22messageReplySection=22><br />
<div name=3D=22messageReplySection=22><br />
On 1 May 2017, 03:32 +0100, The IESG &lt;iesg-secretary=40ietf.org&gt;, w=
rote:<br />
<blockquote type=3D=22cite=22><br />
The IESG has received a request from the NETCON=46 Data Modeling Language=
<br />
WG (netmod) to consider the following document:<br />
- 'YANG Module Classification'<br />
&lt;draft-ietf-netmod-yang-model-classification-06.txt&gt; as Information=
al<br />
R=46C<br />
<br />
The IESG plans to make a decision in the next few weeks, and solicits<br =
/>
final comments on this action. Please send substantive comments to the<br=
 />
ietf=40ietf.org mailing lists by 2017-05-14. Exceptionally, comments may =
be<br />
sent to iesg=40ietf.org instead. In either case, please retain the<br />
beginning of the Subject line to allow automated sorting.<br />
<br />
Abstract<br />
<br />
<br />
The YANG data modeling language is currently being considered for a<br />=

wide variety of applications throughout the networking industry at<br />
large. Many standards-defining organizations (SDOs), open source<br />
software projects, vendors and users are using YANG to develop and<br />
publish YANG modules for a wide variety of applications. At the same<br /=
>
time, there is currently no well-known terminology to categorize<br />
various types of YANG modules.<br />
<br />
A consistent terminology would help with the categorization of YANG<br />=

modules, assist in the analysis of the YANG data modeling efforts in<br /=
>
the IET=46 and other organizations, and bring clarity to the YANG-<br />
related discussions between the different groups.<br />
<br />
This document describes a set of concepts and associated terms to<br />
support consistent classification of YANG modules.<br />
<br />
<br />
<br />
<br />
The file can be obtained via<br />
https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classificat=
ion/<br />
<br />
IESG discussion can be tracked via<br />
https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classificat=
ion/ballot/<br />
<br />
<br />
No IPR declarations have been submitted directly on this I-D.<br />
<br />
<br />
<br />
<br />
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br />
netmod mailing list<br />
netmod=40ietf.org<br />
https://www.ietf.org/mailman/listinfo/netmod<br /></blockquote>
</div>
</div>
</body>
</html>

--59074222_6b8b4567_ee4--


From nobody Mon May  1 07:37:41 2017
Return-Path: <lear@ofcourseimright.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 A22BC129C35; Mon,  1 May 2017 07:37:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Eliot Lear <lear@ofcourseimright.com>
To: <art@ietf.org>
Cc: dnssd@ietf.org, ietf@ietf.org, draft-ietf-dnssd-mdns-dns-interop.all@ietf.org
Subject: Artart telechat review of draft-ietf-dnssd-mdns-dns-interop-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149364945162.9895.14720756538747663998@ietfa.amsl.com>
Date: Mon, 01 May 2017 07:37:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CU18gr4rG3G2hoAbgzCg82Le96U>
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, 01 May 2017 14:37:32 -0000

Reviewer: Eliot Lear
Review result: Ready with Issues

Well written and comprehensive.  Just a few comments.

First, the use of "rejected" several times in the document leads one
to conclude that the WG is making design decisions at this time for
input into the next document. Combined with when the profile is
applicable, and its rough outline, one gets the impression of a first
step towards its writing.  Stating the audience and next steps would
help the reader.

Second, in Section 4.3, ppg 7-8, the following sentence:

   ... DNS-SD
   implementations ought somehow to identify the <Domain> portion of
   the Service Instance Name and treat it subject to IDNA2008 in case
   the domain is to be queried from the global DNS.

The sentence implies that it will not be easy to separate <Domain>
from <Instance> and <Service>, when the previous paragraphs seem to
make it clear that one can clearly identify <Service>.  Is this
because one might envision naked octets that begin with underscore in
either the <Domain> or <Instance> sections?  If so, it might be worth
reiterating that.

Third, while one might say that the fundamental issue has to do with
processing of labels in some form versus not doing so, most of the
document is spent on the case of IDNA2008 v. LDH v. naked UTF8.  The
abstract really should probably state that up front.  Similarly, the
impact to both deployments and implementations should be tersely
summarized.

The key callouts to me are suggestions as to when to perform IDNA2008
processing and when to not do so, potential restriction of character
sets, etc.

Fourth: the following sentence leads to a question:

   A practical consequence of this is that zone operators need to be
   prepared not to apply the LDH rule to all labels.

The implication here is that zone operators make this decision.  I
*think* what we are talking about here are user interfaces, no?  BIND
handles this just fine, right?[1]

Finally one nit: expand LDH on first use.

Eliot
[1] http://www.dns-sd.org/servertestsetup.html



From nobody Mon May  1 09:44:00 2017
Return-Path: <lhotka@nic.cz>
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 CB6DE129C19 for <ietf@ietfa.amsl.com>; Mon,  1 May 2017 09:43:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vF1-3ZwbDHls for <ietf@ietfa.amsl.com>; Mon,  1 May 2017 09:43:55 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (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 061FA129BAE for <ietf@ietf.org>; Mon,  1 May 2017 09:41:31 -0700 (PDT)
Received: from [IPv6:2a01:5e0:29:ffff:f0aa:7cb8:eafe:97e4] (unknown [IPv6:2a01:5e0:29:ffff:f0aa:7cb8:eafe:97e4]) by mail.nic.cz (Postfix) with ESMTPSA id 3AF4662404; Mon,  1 May 2017 18:41:29 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1493656889; bh=30hWcQB3fxzyRpl1sxT1inZOzg/IJhibx46rwQSxS5Q=; h=From:Date:To; b=srJE20I+0vcx/nJACNWmS1Ep8pEFhcOzYwx7r6NFk2gs3ZMp1zumRVAF8m93/sGCa hQ18JanlCsWuYICy/e9TKxsHzmNP4SUXpuLg5Jx+1euzcT3cUGI5ydzXc4vE49+3fH RNCLkfug4eq8XbvY10sNdSkTSCPKlhyky2qJdnNM=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Regional Routing Protocol (RRP).
From: Ladislav Lhotka <lhotka@nic.cz>
In-Reply-To: <20170428154432.o6q753ilzsgbmd4s@nic.fr>
Date: Mon, 1 May 2017 18:41:26 +0200
Cc: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <05E74EEA-5928-4066-86AB-C9C76886037A@nic.cz>
References: <AM4PR0401MB22410362BF8678D2CBD3F9E4BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com> <20170428154432.o6q753ilzsgbmd4s@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.3273)
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qEmLrodMhY14lgxb9lOfEgFHyl4>
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, 01 May 2017 16:43:58 -0000

> On 28 Apr 2017, at 17:44, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
> 
> On Fri, Apr 28, 2017 at 03:25:24PM +0000,
> Khaled Omar <eng.khaled.omar@hotmail.com> wrote 
> a message of 581 lines which said:
> 
>> Please don't upload the 2nd version of the KRP ID and please upload
>> the 1st new version with another draft title Regional Routing
>> Protocol (RRP) discussing the same topic as KRP.
> 
> Interesting social experiment, this bot which tries to exercice the
> limits of the patience of IETF people. Quite tenacious.

Indeed, see my earlier response:

https://www6.ietf.org/mail-archive/web/ietf/current/msg100262.html

Lada

--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67






From nobody Mon May  1 10:05:37 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 39CD612EAB6; Mon,  1 May 2017 10:05:35 -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_50=0.8, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 6E0PHDMQJ3eq; Mon,  1 May 2017 10:05:33 -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 D1C0612EA24; Mon,  1 May 2017 10:02:24 -0700 (PDT)
Received: from mb.local ([IPv6:2620:11a:c081:20:a48c:7fae:30c1:868]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id v41H2Njv093174 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Mon, 1 May 2017 17:02:23 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2620:11a:c081:20:a48c:7fae:30c1:868] claimed to be mb.local
Subject: Re: [GROW] Genart last call review of draft-ietf-grow-large-communities-usage-06
To: Stewart Bryant <stewart.bryant@gmail.com>, Randy Bush <randy@psg.com>, Job Snijders <job@instituut.net>
Cc: gen-art@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, grow@ietf.org, ietf@ietf.org
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local> <m2vaq1p5oi.wl-randy@psg.com> <1c121aaf-fae7-94ec-71ae-7ac618d86f31@gmail.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <a49c9368-4e49-6699-451e-0af2c1550b73@bogus.com>
Date: Mon, 1 May 2017 10:02:17 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:53.0) Gecko/20100101 Thunderbird/53.0
MIME-Version: 1.0
In-Reply-To: <1c121aaf-fae7-94ec-71ae-7ac618d86f31@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6cbvW9DhjU6InIb8PImk84hLP5Cnq5ute"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/peASL0c3NWs2D4BHsiYfg1rlEmQ>
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, 01 May 2017 17:05:35 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--6cbvW9DhjU6InIb8PImk84hLP5Cnq5ute
Content-Type: multipart/mixed; boundary="EasfOUg8AucxkCedbdiKJmp34E1r8tMFl";
 protected-headers="v1"
From: joel jaeggli <joelja@bogus.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, Randy Bush <randy@psg.com>,
 Job Snijders <job@instituut.net>
Cc: gen-art@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org,
 grow@ietf.org, ietf@ietf.org
Message-ID: <a49c9368-4e49-6699-451e-0af2c1550b73@bogus.com>
Subject: Re: [GROW] Genart last call review of
 draft-ietf-grow-large-communities-usage-06
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com>
 <20170418235858.sgsa64r7b5th7zam@Vurt.local> <m2vaq1p5oi.wl-randy@psg.com>
 <1c121aaf-fae7-94ec-71ae-7ac618d86f31@gmail.com>
In-Reply-To: <1c121aaf-fae7-94ec-71ae-7ac618d86f31@gmail.com>

--EasfOUg8AucxkCedbdiKJmp34E1r8tMFl
Content-Type: text/plain; charset=windows-1252
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 4/19/17 1:52 AM, Stewart Bryant wrote:
>=20
>=20
> On 19/04/2017 02:06, Randy Bush wrote:
>>>> 5.  Security Considerations
>>>>
>>>>     Operators should note the recommendations in Section 11 of BGP
>>>>     Operations and Security [RFC7454].
>>>>
>>>> SB> You do not address the question of whether there are new
>>>> SB> considerations, or considerations that are of increased importan=
ce?
>>> It is my understanding that RFC 8092 "BGP Large Communities" are just=

>>> like RFC 1997 "BGP Communities", but ...  larger (for lack of better
>>> words). Referencing RFC 7454 seems plenteous.
>>>
>>> So, what if there are not any additional considerations, If there wer=
e,
>>> they would've been (or are) covered in RFC 8092's security section,
>>> right?
>>>
>>> This is an Internet-Draft targetted for Informational status, I'm not=

>>> sure what you expect here.
>>>
>>>> SB> Is there is text somewhere that discusses the integrity and
>>>> SB> synchronization of the parameters and any consequences that aris=
e?
>>> the what now? Can you elaborate on the above?
>> you're supposed to guess
>>
>> the normal hack here is
>>
>>    this document introduces no new security issues beyond those discus=
sed
>>    in 1997
>=20
> Guessing is horrible, but if that is what you do, that is what you do,
> and if the risks are the accepted norm in the BGP
> community I am fine.
>=20
> Is corruption (deliberate or otherwise) of the community strings
> something that BGPsec will address?

That seems like a dubious premise given that they are optional. One can
simply remove them and substitute / add additional ones if you so
inclined and that occcurs in the normal course of events.

> - Stewart
>=20



--EasfOUg8AucxkCedbdiKJmp34E1r8tMFl--

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

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

iEYEARECAAYFAlkHahoACgkQ8AA1q7Z/VrKAgwCeNRJ4Rq4yCzjbue3BROF7PRli
wygAnjyZkFcrUzk4doNKVfxCYPhTYqeq
=1FTo
-----END PGP SIGNATURE-----

--6cbvW9DhjU6InIb8PImk84hLP5Cnq5ute--


From nobody Mon May  1 11:29:24 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 8B4EA12945F; Mon,  1 May 2017 11:29:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 F1Y_wvwIQ-3D; Mon,  1 May 2017 11:29:14 -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 76383129B2C; Mon,  1 May 2017 11:26:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10727; q=dns/txt; s=iport; t=1493663183; x=1494872783; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=u0zSpdQzWlxboJYRJRGuA9YRz+rNNSLO9eQHzZJEuqw=; b=Sn2S8sIyo3zXWSMGHn9HiaFadAYIKKPRP2UwKd4t6TRHPNSNzu8Qz0sD 37atCPSxDXJ1+Mfu3Zeaurv+WWUEhUHMDHD1hlKauWS6YAAvHIMGYMEqd 62sAv1+MDEp2brNxfC1BDLwA3BdCRa06g+YbwQCtzVrwBWJTOAx5Q2WTr w=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AsAQAZfQdZ/xbLJq1TChkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYkrihhzkFqQNoU3gg8Hhh0ChHoYAQIBAQEBAQEBayiFFQEBAQE?= =?us-ascii?q?CASNPBwULCw4KKgICVwYBDAgBAYoTCK4bgiYrimIBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEOD4hognCEOxKDHIJfAQSdU4QNghOBfYp0ggKIeYZjlC0fOIEKLiAIGRW?= =?us-ascii?q?FMIIGPoksAQEB?=
X-IronPort-AV: E=Sophos;i="5.37,401,1488844800";  d="asc'?scan'208,217";a="652565854"
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; 01 May 2017 18:26:21 +0000
Received: from [10.61.67.64] (ams3-vpn-dhcp832.cisco.com [10.61.67.64]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v41IQKiQ017520; Mon, 1 May 2017 18:26:21 GMT
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
To: Mark Nottingham <mnot@mnot.net>, IESG <iesg@ietf.org>
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
From: Eliot Lear <lear@cisco.com>
Message-ID: <87a8801b-67f7-21c8-ad09-9faf66e58d04@cisco.com>
Date: Mon, 1 May 2017 20:26:20 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="I3IRmj056N3jVHvIVdVJhMbeoJc6GdelA"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hwd1jB2xm7Ff-tKnBlbMD1seG6M>
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, 01 May 2017 18:29:17 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--I3IRmj056N3jVHvIVdVJhMbeoJc6GdelA
Content-Type: multipart/mixed; boundary="keJw3R2IwaHIsBMsCC6pEXF16XgwDDupG";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Mark Nottingham <mnot@mnot.net>, IESG <iesg@ietf.org>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <87a8801b-67f7-21c8-ad09-9faf66e58d04@cisco.com>
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net>
In-Reply-To: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net>

--keJw3R2IwaHIsBMsCC6pEXF16XgwDDupG
Content-Type: multipart/alternative;
 boundary="------------604A2F86FC0891D0DF2C84E9"

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

Hi Mark,

On 5/1/17 5:45 AM, Mark Nottingham wrote:
> Sorry for the late review; on the plus side, I'm coming to it with fres=
h eyes.
>
> Overall, this document reads as if it was originally written to highlig=
ht the downsides of increased use of encryption, and then rewritten to be=
 more neutral in tone. Unfortunately, some of the original intent posited=
 there still seeps through.
What I'm becoming concerned about is us not talking about what we're
talking about.  If encryption presents challenges in some deployments,
certainly one should say so.  One should also say what workarounds are
available, and maybe even what challenges or complexities those
workarounds themselves introduce.

And so for instance:
> Section 2.3.2.2 motivates DPI as "Input for Differential Treatment", bu=
t fails to note the developing efforts to coordinate client and server be=
haviour to adapt to network conditions, without the need for stripping en=
cryption.

There are two key issues to DPI is intended to tackle:

  * The ability to identify a class of traffic at all, perhaps without
    so much as the benefit of fixed TCP/UDP port assignments, as is
    often the case with media streams; and
  * Trust between the end devices and the network administration, where
    the administrator wants to know that a traffic class is used solely
    for authorized purposes (e.g., nobody's prioritizing Age of Empires
    by attempting to mimic an IP-based phone).

When encryption is present, the DPI fails.  To remedy this there are
essentially four approaches:

 1. Trust one of the endpoints, if possible, to report that the
    communication is authentic and authorized;
 2. Require that set-up of communications (such as a media streams)
    occur through a trusted 3rd party that reports 5-tuple information
    (including call completion);
 3. Make do with what information can be gleaned outside the payload
    (e.g., packet timing, sequencing, etc - so-called meta-information);
 4. Give up.

I'm sure smarter people than me have come up with options 5, 6, etc, but
you get the idea.

The trust relationships have to be in place for options 1 or 2 to work,
and for the mobile operator use case that might be quite tricky. =20
Option 2 presents a state management issue, and may or may not incur a
latency penalty during setup.  Both 1 and 2 have attendant complexity of
additional communication paths, but as they say, there ain't no such
thing as a free lunch, and that really is or should be the point of the
draft.=20

It may not be feasible to go into even this much detail in each case,
and we shouldn't require that, so long as the problem statement is well
supported.

This seems to be what you're looking for in the context of caching:

> Section 2.3.2.1 points out that "Web proxies are widely used", but fail=
s to note that the vast bulk of caching is done by endpoints -- browsers,=
 CDNs and reverse proxies, thereby sidestepping the issues of encryption =
(although they have their own unique challenges). Discussing why this for=
m of caching has become prevalent might help inform network operators as =
to why getting the economics and trust relationships of intermediation ri=
ght is important.

I like the idea of examining the economic relationships between, say,
the end user's service provider and the end user, versus the end user
service provider and the content provider, etc., and where value might
be had with regard to those who have business relationships and those
who don't.  Note the case where the user is an employee is different
than when the user is a service provider customer, the former of which
is discussed in Section 4.

One caution: this document risks turning into a tome if the discussion
goes too long.  Better to be succinct and reference where one can.

Eliot

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

<html>
  <head>
    <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Ty=
pe">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <p>Hi Mark,</p>
    <div class=3D"moz-cite-prefix">On 5/1/17 5:45 AM, Mark Nottingham
      wrote:<br>
    </div>
    <blockquote cite=3D"mid:C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net=
"
      type=3D"cite">
      <pre wrap=3D"">Sorry for the late review; on the plus side, I'm com=
ing to it with fresh eyes.

Overall, this document reads as if it was originally written to highlight=
 the downsides of increased use of encryption, and then rewritten to be m=
ore neutral in tone. Unfortunately, some of the original intent posited t=
here still seeps through.</pre>
    </blockquote>
    What I'm becoming concerned about is us not talking about what we're
    talking about.=C2=A0 If encryption presents challenges in some
    deployments, certainly one should say so.=C2=A0 One should also say w=
hat
    workarounds are available, and maybe even what challenges or
    complexities those workarounds themselves introduce.<br>
    <br>
    And so for instance:<br>
    <blockquote cite=3D"mid:C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net=
"
      type=3D"cite">
      <pre wrap=3D"">
Section 2.3.2.2 motivates DPI as "Input for Differential Treatment", but =
fails to note the developing efforts to coordinate client and server beha=
viour to adapt to network conditions, without the need for stripping encr=
yption.</pre>
    </blockquote>
    <br>
    There are two key issues to DPI is intended to tackle:<br>
    <ul>
      <li>The ability to identify a class of traffic at all, perhaps
        without so much as the benefit of fixed TCP/UDP port
        assignments, as is often the case with media streams; and</li>
      <li>Trust between the end devices and the network administration,
        where the administrator wants to know that a traffic class is
        used solely for authorized purposes (e.g., nobody's prioritizing
        Age of Empires by attempting to mimic an IP-based phone).<br>
      </li>
    </ul>
    When encryption is present, the DPI fails.=C2=A0 To remedy this there=
 are
    essentially four approaches:<br>
    <ol>
      <li>Trust one of the endpoints, if possible, to report that the
        communication is authentic and authorized;</li>
      <li>Require that set-up of communications (such as a media
        streams) occur through a trusted 3rd party that reports 5-tuple
        information (including call completion);<br>
      </li>
      <li>Make do with what information can be gleaned outside the
        payload (e.g., packet timing, sequencing, etc - so-called
        meta-information);</li>
      <li>Give up.<br>
      </li>
    </ol>
    I'm sure smarter people than me have come up with options 5, 6, etc,
    but you get the idea.<br>
    <br>
    The trust relationships have to be in place for options 1 or 2 to
    work, and for the mobile operator use case that might be quite
    tricky. =C2=A0 Option 2 presents a state management issue, and may or=
 may
    not incur a latency penalty during setup.=C2=A0 Both 1 and 2 have
    attendant complexity of additional communication paths, but as they
    say, there ain't no such thing as a free lunch, and that really is
    or should be the point of the draft.=C2=A0 <br>
    <br>
    It may not be feasible to go into even this much detail in each
    case, and we shouldn't require that, so long as the problem
    statement is well supported.<br>
    <br>
    This seems to be what you're looking for in the context of caching:<b=
r>
    <br>
    <blockquote type=3D"cite">
      <pre wrap=3D"">Section 2.3.2.1 points out that "Web proxies are wid=
ely used", but fails to note that the vast bulk of caching is done by end=
points -- browsers, CDNs and reverse proxies, thereby sidestepping the is=
sues of encryption (although they have their own unique challenges). Disc=
ussing why this form of caching has become prevalent might help inform ne=
twork operators as to why getting the economics and trust relationships o=
f intermediation right is important.</pre>
    </blockquote>
    <br>
    I like the idea of examining the economic relationships between,
    say, the end user's service provider and the end user, versus the
    end user service provider and the content provider, etc., and where
    value might be had with regard to those who have business
    relationships and those who don't.=C2=A0 Note the case where the user=
 is
    an employee is different than when the user is a service provider
    customer, the former of which is discussed in Section 4.<br>
    <br>
    One caution: this document risks turning into a tome if the
    discussion goes too long.=C2=A0 Better to be succinct and reference w=
here
    one can.<br>
    <br>
    Eliot<br>
  </body>
</html>

--------------604A2F86FC0891D0DF2C84E9--

--keJw3R2IwaHIsBMsCC6pEXF16XgwDDupG--

--I3IRmj056N3jVHvIVdVJhMbeoJc6GdelA
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

iQEcBAEBCAAGBQJZB33MAAoJEIe2a0bZ0noz/NoH/RyMTkvt42wvgJqmmBLPOEPq
i+ksTsgA/IbZlUrOSuRS0tz1eSUWUs6jLbiDstzgCSjPhnnVSCKbOAfYLwg7/HrE
dVJUoGc2slNYZlOKnzzSb7OIUbVM7BhszQtmpmUk/priu3qHV4/66Tv/9Yz4seu/
0EwnPJttkufkFxbKMpNYPwyhrI357cMCzTr0DPA5jKMJXHw03m2K5+h+IbRmzlcE
zx6S3Mcr5x+rCnrVJWRFLIxZwqyKL5QjDeJQkBC0Pl7Yo6IPO9SVEvAAkwhc5P5I
RmVuV2U9IB0+UeQJ4SlgdSdbZz+p3N9nBr/TlAzzU2QyxXbH9t25lqNctQGn4MQ=
=1cWk
-----END PGP SIGNATURE-----

--I3IRmj056N3jVHvIVdVJhMbeoJc6GdelA--


From nobody Mon May  1 12:29:29 2017
Return-Path: <ajs@anvilwalrusden.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 76F95128961; Mon,  1 May 2017 12:29:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=yitter.info header.b=Z8PvbI49; dkim=pass (1024-bit key) header.d=yitter.info header.b=emSblbKE
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VQDgG4EcAfJl; Mon,  1 May 2017 12:29:24 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EC6712EAC0; Mon,  1 May 2017 12:26:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 160BFBB834; Mon,  1 May 2017 19:26:33 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1493666793; bh=lDOLQBrkOxbH0E3BMLmfpkuovT4b4/yW/JvO8ZmF7/I=; h=Date:From:To:Subject:From; b=Z8PvbI49IdwQFNk4efrimPEYyzYC4Qa+0wKoOvZ96n+s1dMDfokY9IpJeo4wqE5V/ DioogtVBJgy0TMtIPx7SzviGLRd8Ua7OWqJn4TgoPdN2l/1p9R+G1LBZ/rew/TB9A3 O22Dh3dFkuqTKWFmIImt/i4j9d7CVc2x7OFqBC0Y=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X_HLTl48sqvu; Mon,  1 May 2017 19:26:31 +0000 (UTC)
Date: Mon, 1 May 2017 15:26:29 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1493666791; bh=lDOLQBrkOxbH0E3BMLmfpkuovT4b4/yW/JvO8ZmF7/I=; h=Date:From:To:Subject:From; b=emSblbKElAJndLUB1ObWL+E3m2PSoqg9QQlPKvf/qSUfGiheWdzmZfuBGfgUh/EUU /fZEKijPD3x9mTMnS8FYpCJU5uJO8106kXdI0SCRtuKRoxfjp7zDuURpeackmtuyb7 B5cbELvcZHiJ7nVUUYJS2YXXBJzedTuZye1S9RSo=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: draft-freytag-lager-variant-rules@ietf.org, IETF-Discussion list <ietf@ietf.org>
Subject: draft-freytag-lager-variant-rules-05
Message-ID: <20170501192629.vqkgfr73bguhmdmo@mx4.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/po47ZJR1xWuxFx_h-8IRTvYBTwo>
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, 01 May 2017 19:29:28 -0000

Dear colleagues,

I have read draft-freytag-lager-variant-rules-05, which is in IETF LC.
I have a few comments.

I understand the purpose of this document to be, essentially, a good
practices document for designing variants, with a particular focus on
LGRs appropriate to domain names using IDNA.  I think it is a good
idea to have such a document, and the discussion this document has
received has not, as nearly as I can tell, been terribly clear about
whether such a thing is a good idea or is not.  It seems to me that it
is a good thing to offer advice to people in how to design their
policies, given that (e.g.) RFC 5890 and friends says that they do
need such a policy.  Since I'm one of the people who, as much as
anyone else, has failed to do his share of lifting on i18n the last
few years, I am acutely aware of the gap this document proposes to
fill.  Whether variants were a good idea in the first place is sort of
irrelevant: the fact is that we have them, and they seem unlikely to
go away as we attempt to internationalize protocols that were never
designed to adapt to normal natural language ways of thinking about
identification.

Therefore, overall I think this is a good document and that it should
be published as an RFC.  I think some of the prose is occasionally a
little hard to follow, but I also think that difficulty comes partly
from wrestling with precision.  I believe the precision is important
in this case, and I can't really come up with a way of making the text
better without affecting that precision.

At the same time, I wonder whether the document is setting itself too
great a task at the beginning, in expanding its applicability to any
internationalized identifier.  Indentifiers that are not label-based
are not obvious candidates for use with this approach.  Identifiers
that carry linguistic semantics may well not need this approach
either.  And after reading the document I'm not even sure that this
document really is applicable even to domain names that are not in the
DNS (in case we think we can distinguish between "domain names" and
"DNS-only domain names") or are not using IDNA.  I don't feel super
strongly about this, but maybe the Intro could say this instead:

OLD

   Label Generation Rulesets (LGRs) that define the set of permissible
   labels, may be applied to a variety of identifier systems, although
   to date, the most common use is to define policies for implementing
   Internationalized Domain Names (IDNs) for some zone of the Domain
   Name System (DNS).  Without restricting any of the more general
   applications of this document, the explanations and examples in this
   document may be stated in terms of IDNs.

NEW

   Label Generation Rulesets (LGRs) that define the set of
   permsissible labels may be applied to identifier systems that rely
   on labels, such as the Domain Name System (DNS, [RFC 1034] [RFC
   1035]).  To date, LGRs have mostly been used to define policies for
   implementing Internationalized Domain Names (IDNs) using IDNA2008
   [RFC 5890] [other ref's here] in the DNS.  This document aims to
   discuss the generation of LGRs for such circumstances, but the
   techniques and considerations here are almost certainly applicable
   to a wider range of internationalized identifiers.

Given the "good practices" thrust I think is here, section 3 seems to
go out of its way not to say, "Don't do that."  If the point of an LGR
is partly to make useful and comprehensible policies in a distributed
system like the Internet, then having a variant system where A~B and
B~C but !(C~A) is probably not that helpful.  So, while it is
_possible_ to have LGRs that do not exhibit transitivity or symmetry,
such uses had better be pretty well-contained if they are to be
useful.  Section 3 could say that more bluntly, I think.

In my opinion, section 14 is a clear example of why the idea of
"multiple LGRs" is harmful.  Given that people have come to believe in
them, this section needs to stay and it is probably fine.  But it sure
makes the whole system harder to follow.  As a consequence, the advice
at the end of §16 seems too weak:

OLD

   In summary, conditional contexts can be an essential tool, but some
   additional care must be taken to ensure that an LGR containing
   conditional contexts is well behaved.

I'd suggest instead

NEW

   In summary, conditional contexts can be useful for some cases, but
   additional care must be taken to ensure that an LGR containing
   conditional contexts is well behaved.  LGR designers would be well
   advised to avoid using conditional contexts and to prefer
   unconditional rules whenever practical, even though it will
   doubtless reduce the number of labels practically available.
 
I hope these remarks are helpful to the IESG and the document author.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Mon May  1 13:05:27 2017
Return-Path: <asmusf@ix.netcom.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 E384E12E957; Mon,  1 May 2017 13:05:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ix.netcom.com; domainkeys=pass (2048-bit key) header.from=asmusf@ix.netcom.com header.d=ix.netcom.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yIiT9fyjUOOf; Mon,  1 May 2017 13:05:22 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E009212AF6E; Mon,  1 May 2017 13:02:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ix.netcom.com; s=dk12062016; t=1493668942; bh=kAWTy1+7xs72sC47JdvOAsyFc8VB1B25alqX Q3HLpFM=; h=Received:Subject:To:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type: Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; b=d4G24fx 23Yt6zqxXFLhtXND/2KaFDZ0KkOjlgJYNeGk1KY9uqZe5GEhK/UHv6LdR1Zb4LM2pMJ O39C+snNnQe3+0SD2NigQzYYU4hOKg8d18Wh4JFNPYnBUJJ7krCKDuAwbcWLjqH+H6f izElcEmSSqXRnQfP2niYKuCWouL0Yh2TC28o41NDVheHs1VmCAi4ZKqXuvISfCV+6mk E7kqvBR2ooAV+cKVOMqnHrZ6ot3pMYcBi7E6G4ccq662Q9bGorV+xSB4uj0ToeCX7CK liv004v1IMh5LjH8rbV80Pxw/1GC2fr7eLSZQbF/zKaWxfvxC9ezmdUg+Fn9oPN91KA ==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=ix.netcom.com; b=DMrqBlk+oDwT8M0xkJl0KV6AZu46B39Q49/esJvrnZ5SsOtDtmNw5TxwcijEgIDxaMBkupBu1k8NziY1hjb76EooLZEynJYaGxUbwO/2pdx4TJL8d4TITc/+fgK2Eami6Q8qGuZat9PktwhN9qWVRg+zoSEBbWJ6eQ2GBjcSYtz+FvgAM/poJR4o+vct0AAZ/e4OofZ0zhaPMvfq/+kb7DvTDmM6SNJGf913dBOAKuZtAZwsqMQTWrJ9NZc+0HvJyhMD7Mb0fVyNfIHRRP0G9V+d5upCDAQ7hZ+a+LALvMrbc2zvhM+peF1woMWLMEZ8LOVM7QI4xxUmDNrnfNzYBA==; h=Received:Subject:To:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [94.100.23.163] (helo=[10.4.50.183]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <asmusf@ix.netcom.com>) id 1d5HWV-0003rq-Pc; Mon, 01 May 2017 16:02:19 -0400
Subject: Re: draft-freytag-lager-variant-rules-05
To: Andrew Sullivan <ajs@anvilwalrusden.com>, draft-freytag-lager-variant-rules@ietf.org, IETF-Discussion list <ietf@ietf.org>
References: <20170501192629.vqkgfr73bguhmdmo@mx4.yitter.info>
From: Asmus Freytag <asmusf@ix.netcom.com>
Message-ID: <e0388525-ef31-fe95-2a74-3a338aee50e3@ix.netcom.com>
Date: Mon, 1 May 2017 13:02:19 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170501192629.vqkgfr73bguhmdmo@mx4.yitter.info>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2545e64a33c2ff5d0776af8c71c042610489b3a04f9d62ea9350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 94.100.23.163
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BMrGQA9K4wJNM1VQ36iKJ8H5fHU>
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, 01 May 2017 20:05:25 -0000

On 5/1/2017 12:26 PM, Andrew Sullivan wrote:
> Dear colleagues,
>
> I have read draft-freytag-lager-variant-rules-05, which is in IETF LC.
> I have a few comments.
>
> I understand the purpose of this document to be, essentially, a good
> practices document for designing variants, with a particular focus on
> LGRs appropriate to domain names using IDNA.  I think it is a good
> idea to have such a document, and the discussion this document has
> received has not, as nearly as I can tell, been terribly clear about
> whether such a thing is a good idea or is not.
Correct, most of the encouragement (i.e. "this is a good idea to have 
such a
document") has been received off-line from people otherwise on this list 
and
hence is not been 'visible'.
>   It seems to me that it
> is a good thing to offer advice to people in how to design their
> policies, given that (e.g.) RFC 5890 and friends says that they do
> need such a policy.
And in particular as a new ID propose to help reinforce that responsibility.
>   Since I'm one of the people who, as much as
> anyone else, has failed to do his share of lifting on i18n the last
> few years, I am acutely aware of the gap this document proposes to
> fill.  Whether variants were a good idea in the first place is sort of
> irrelevant: the fact is that we have them, and they seem unlikely to
> go away as we attempt to internationalize protocols that were never
> designed to adapt to normal natural language ways of thinking about
> identification.

Variants come in two flavors that have very different implications. Many 
people
think of *allocatable* variants first. These are problematic in many 
ways and
are in a way visible to the users of the DNS. There are a limited 
constellation
of linguistic conditions where they represent an appropriate choice.

In contrast, *blocked* variants make certain labels mutually exclusive. 
This
directly affects applicants (and registries) in that some particular 
label may
no longer be available. Ordinary users are not affected, other than perhaps
positively by not having to deal with two labels that display 
identically, etc.

The motivation for these two types of variants is rather different. The 
way I
would put it: since we have the variant mechanism, and since we have, with
RFC 7940 for the first time a universal way to specify them, that is not
implicitly to a given geographic region, we might as well consider the 
benefits
(particularly of *blocked* variants) to increase robustness of the DNS,
even for regions where *allocatable* variants are not a relevant issue.

But to do that, we need to know the distinction between these two types
and the implications of ways to specify variant relations. That is what this
document tries to convey.
>
> Therefore, overall I think this is a good document and that it should
> be published as an RFC.  I think some of the prose is occasionally a
> little hard to follow, but I also think that difficulty comes partly
> from wrestling with precision.  I believe the precision is important
> in this case, and I can't really come up with a way of making the text
> better without affecting that precision.
>
> At the same time, I wonder whether the document is setting itself too
> great a task at the beginning, in expanding its applicability to any
> internationalized identifier.  Indentifiers that are not label-based
> are not obvious candidates for use with this approach.  Identifiers
> that carry linguistic semantics may well not need this approach
> either.  And after reading the document I'm not even sure that this
> document really is applicable even to domain names that are not in the
> DNS (in case we think we can distinguish between "domain names" and
> "DNS-only domain names") or are not using IDNA.  I don't feel super
> strongly about this, but maybe the Intro could say this instead:
>
> OLD
>
>     Label Generation Rulesets (LGRs) that define the set of permissible
>     labels, may be applied to a variety of identifier systems, although
>     to date, the most common use is to define policies for implementing
>     Internationalized Domain Names (IDNs) for some zone of the Domain
>     Name System (DNS).  Without restricting any of the more general
>     applications of this document, the explanations and examples in this
>     document may be stated in terms of IDNs.
>
> NEW
>
>     Label Generation Rulesets (LGRs) that define the set of
>     permsissible labels may be applied to identifier systems that rely
>     on labels, such as the Domain Name System (DNS, [RFC 1034] [RFC
>     1035]).  To date, LGRs have mostly been used to define policies for
>     implementing Internationalized Domain Names (IDNs) using IDNA2008
>     [RFC 5890] [other ref's here] in the DNS.  This document aims to
>     discuss the generation of LGRs for such circumstances, but the
>     techniques and considerations here are almost certainly applicable
>     to a wider range of internationalized identifiers.
I don't have any objection to making a change like that.
>
> Given the "good practices" thrust I think is here, section 3 seems to
> go out of its way not to say, "Don't do that."  If the point of an LGR
> is partly to make useful and comprehensible policies in a distributed
> system like the Internet, then having a variant system where A~B and
> B~C but !(C~A) is probably not that helpful.  So, while it is
> _possible_ to have LGRs that do not exhibit transitivity or symmetry,
> such uses had better be pretty well-contained if they are to be
> useful.  Section 3 could say that more bluntly, I think.

I was asked the same question recently "is it allowed to have 
non-symmetric or non-
transitive" variant definitions. My best answer, essentially came out as 
"while such
things can be specified, symmetric and transitive definitions have such 
advantages
it's simply common sense to require them."

And the advantages that I was thinking of had to do with optimized 
evaluation of
these LGRs, but making policies "useful and comprehensible policies in a 
distributed
system like the Internet," is an important issue as well.

So, I'd concur and would be happy to tweak the language to be more "blunt".
>
> In my opinion, section 14 is a clear example of why the idea of
> "multiple LGRs" is harmful.  Given that people have come to believe in
> them, this section needs to stay and it is probably fine.  But it sure
> makes the whole system harder to follow.  As a consequence, the advice
> at the end of §16 seems too weak:
>
> OLD
>
>     In summary, conditional contexts can be an essential tool, but some
>     additional care must be taken to ensure that an LGR containing
>     conditional contexts is well behaved.
>
> I'd suggest instead
>
> NEW
>
>     In summary, conditional contexts can be useful for some cases, but
>     additional care must be taken to ensure that an LGR containing
>     conditional contexts is well behaved.  LGR designers would be well
>     advised to avoid using conditional contexts and to prefer
>     unconditional rules whenever practical, even though it will
>     doubtless reduce the number of labels practically available.
I would have no objection to changing the language in this way.
>   
> I hope these remarks are helpful to the IESG and the document author.
I certainly found them very helpful,

Thanks,
A./
>
> Best regards,
>
> A
>


From nobody Mon May  1 16:17:09 2017
Return-Path: <ldaigle@thinkingcat.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 21F1612EB22; Mon,  1 May 2017 16:17:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.588
X-Spam-Level: 
X-Spam-Status: No, score=-4.588 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, T_DKIM_INVALID=0.01, 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=thinkingcat.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 jT3-mJZwFjJV; Mon,  1 May 2017 16:17:03 -0700 (PDT)
Received: from homiemail-a88.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5049D12EA94; Mon,  1 May 2017 16:14:48 -0700 (PDT)
Received: from homiemail-a88.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a88.g.dreamhost.com (Postfix) with ESMTP id B6CC1A003A1E; Mon,  1 May 2017 16:14:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thinkingcat.com; h=from:to :cc:subject:date:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=thinkingcat.com; bh=P aSzrGoH8va9dCkFh+kWJzxxKrY=; b=colYxY05NR/6o+Pv8o86no5ynKk7k7Bhw OW7YVHUONRJMFmcPx1+fDDurVmgpKOzc9Hwtn8HWYfHfokxtSMYuGMUtQ43sMsud 5hUYTyGG4hDhnOZ4wFJGd2YUzeTmvfk44DOxd0N56+yLEsnu99OaYnlBJZJlCQGn icAPdlM0ck=
Received: from [192.168.1.5] (pool-173-72-147-193.clppva.fios.verizon.net [173.72.147.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: leslie@oceanpurl.net) by homiemail-a88.g.dreamhost.com (Postfix) with ESMTPSA id 055E5A003A1D; Mon,  1 May 2017 16:14:46 -0700 (PDT)
From: "Leslie Daigle" <ldaigle@thinkingcat.com>
To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
Cc: "IETF Discussion" <ietf@ietf.org>, iaoc@ietf.org
Subject: Re: [IAOC] IAOC requesting input on (potential) meeting cities
Date: Mon, 01 May 2017 19:14:45 -0400
Message-ID: <524C6CE6-8033-409E-8E0C-23521C6E449B@thinkingcat.com>
In-Reply-To: <22EB34C2-CF25-4E18-8185-47F27363A6AD@consulintel.es>
References: <E67FDB14-9895-48E0-A334-167172D322DB@nohats.ca> <20170403152624.GA11714@gsp.org> <93404c29-78ba-ff9b-9170-f5f2a5389a31@gmail.com> <E068F01A-B720-4E7A-A60F-AA5BDA22D535@consulintel.es> <20170404181505.GA4004@localhost> <CAAQiQRcvu-BfBA_NEqZwXsHEn6ujpa2=w7P5Vu2f6GLXjKqkcA@mail.gmail.com> <20170404202446.GB4004@localhost> <2987213d-075e-beff-64f8-d316709c404a@cs.tcd.ie> <20170404204617.GC16732@puck.nether.net> <3D4D193E-0D41-44DD-BB0C-E7741A7A2260@gmail.com> <20170404221042.GC4004@localhost> <7E834C8D-FCFB-48C4-925A-73B5FDEC60FD@consulintel.es> <22EB34C2-CF25-4E18-8185-47F27363A6AD@consulintel.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_FFD977EA-03F3-459E-B26E-624E83692C5A_="
X-Mailer: MailMate (1.9.6r5347)
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SUEfqhpAq2V9PgkNV7dbW1R1M98>
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, 01 May 2017 23:17:07 -0000

--=_MailMate_FFD977EA-03F3-459E-B26E-624E83692C5A_=
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Jordi,

I=E2=80=99m sorry you feel the IAOC has been unresponsive to your questio=
ns. I=20
would ask for your continued understanding that we are still reviewing=20
options, and won=E2=80=99t have full information ourselves until we are c=
loser=20
to closure.

In my message of April 12, wherein I outlined the information we do=20
have, I closed with:

> The IAOC is continuing to gather data on travel to the US, concerns=20
> about traveling outside of it, and what alternatives are possible for=20
> IETF 102. Our focus is currently on whether holding IETF 102 in San=20
> Francisco is the best option to meet the needs of IETF work,=20
> recognizing that we cannot predict the future. While it may take=20
> several weeks to allow for review and negotiation of any alternatives=20
> (if applicable), we are moving as quickly as possible because we=20
> realize that people will need time to plan their travel.

I believe you are asking us to share data that we don=E2=80=99t even have=
 yet.=20
  If we were to move the IETF 102 meeting, costs to the IETF as an=20
organization would be dependent not only on the cancellation provisions=20
in the current contract, but also on the alternate location chosen and=20
its contract options. We don=E2=80=99t have all of those numbers yet. And=
,=20
while it is certainly part of our deliberations about moving a meeting,=20
these are not things we can expose and ask the community to vote on.

The IAOC has moved at this point from gathering data on travel to the US=20
to weighing what options best meet the needs of IETF work in light of=20
that data and the other aspects of IETF 102 planning.  As soon as we can=20
move out of that stage and share the results with the community, we will=20
do so.

Leslie.


--=20

-------------------------------------------------------------------
Leslie Daigle
Principal, ThinkingCat Enterprises LLC
ldaigle@thinkingcat.com
-------------------------------------------------------------------

On 11 Apr 2017, at 7:11, JORDI PALET MARTINEZ wrote:

> Can we get an answer from the IAOC to the questions below?
>
> If we cancel San Francisco, how much that is going to cost to the IETF=20
> for each of two planned meetings?
>
> Can we cancel the actual hotel contract considering the new US=20
> situation? If not, has this been considered for new contracts to avoid=20
> this problem?
>
> Otherwise there is any reason that can justify the lack of=20
> transparency in this?
>
> Regards,
> Jordi
>
>
> -----Mensaje original-----
> De: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
> Fecha: mi=C3=A9rcoles, 5 de abril de 2017, 10:26
> Para: <iaoc@ietf.org>
> Asunto: Re: IAOC requesting input on (potential) meeting cities
>
>     One important question here, same as we had in the case of=20
> Singapore.
>
>     If we cancel San Francisco, how much that is going to cost to the=20
> IETF for each of two planned meetings?
>
>     Furthermore, can the IAOC respond to this:
>
>     Can we cancel the actual hotel contract considering the new US=20
> situation? If not, has this been considered for new contracts to avoid=20
> this problem?
>
>     I think the relevant information in the contract need to be=20
> disclosed and have it now on the table, otherwise we will be wasting=20
> the time discussing possibilities that are actually impossible to=20
> assume for the IETF =E2=80=A6
>
>     My general position is:
>     1) I will prefer not cancelling already planned meetings.
>     2) I will prefer not =E2=80=9Cblocking=E2=80=9D any regions or coun=
tries from=20
> future meetings, including US.
>     3) However, for already contracted meetings, if this is going to=20
> cost IETF thousands of dollars, we can=E2=80=99t afford that.
>     4) We must work with authorities to avoid people being banned for=20
> attending the meetings.
>
>     Maybe I=E2=80=99ve missed responses to some of my answers already, =
in=20
> any case, can the IAOC provide urgently those with a complete summary=20
> of the situation?
>
>     Regards,
>     Jordi
>
>
>     -----Mensaje original-----
>     De: Eliot Lear <lear@cisco.com>
>     Responder a: <lear@cisco.com>
>     Fecha: mi=C3=A9rcoles, 5 de abril de 2017, 6:39
>     Para: Nico Williams <nico@cryptonector.com>, Yoav Nir=20
> <ynir.ietf@gmail.com>
>     CC: IETF <ietf@ietf.org>, JORDI PALET MARTINEZ=20
> <jordi.palet@consulintel.es>, Jared Mauch <jared@puck.nether.net>
>     Asunto: Re: IAOC requesting input on (potential) meeting cities
>
>         Nico,
>
>         On 4/5/17 12:10 AM, Nico Williams wrote:
>         > I do suspect that the U.S. will be a more difficult location=20
> for more
>         > attendees than other locations.  Certainly the news we all=20
> see is not
>         > encouraging as to hosting IETF meetings in the U.S.  This I=20
> don't deny.
>         > Though it's also possible that this is becoming a=20
> self-reinforcing meme
>         > and that we're just not seeing incidents in other countries=20
> in the news.
>         > In any case, the U.S. certainly does not have a monopoly on=20
> the border
>         > harasment business.
>
>         Certainly people have had trouble getting into other=20
> countries, most
>         notably Canada where an IAB member was refused entry.  But=20
> this isn't
>         just news.  It is a series of declarations by the U.S.=20
> government of
>         their intentions, and the IAOC has to plan ahead.  That's why=20
> Jared's
>         request for data is simply not tenable *at this stage*.  If it=20
> turns out
>         that things aren't so bad, the IAOC can react accordingly. =20
> However, as
>         I wrote in my original email, there is now good reason to=20
> believe that
>         things will get worse, due to the European Parliament=E2=80=99s=
=20
> decision to
>         require visas from U.S. citizens.
>
>         > Some people may wish to boycott the U.S. by refusing to host=20
> events
>         > there.  There is some precedent for such a boycott.  For=20
> example, some
>         > time back an obscure agency of the Texas state government=20
> decided to
>         > guard its surplus budget by policing public drunkenness at=20
> hotel bars,
>         > which led to a number of conferences pulling out of Texas,=20
> and the
>         > ensuing bad PR led the legislature to rein in said agency.
>         >
>         > However, at the scale of a state/province the politics of=20
> boycotts is
>         > generally not partisan, but at a national/global scale it=20
> tends to be
>         > rankly partisan, and boycotts may not be productive and may=20
> be divisive,
>         > and should be approached with care.  Here "care" means: get=20
> some
>         > evidence of negative impact on participation.
>
>         We ALREADY have evidence, as some people couldn't make=20
> Chicago, and said
>         so on this very list (and, by the way, were shamefully=20
> attacked and
>         dismissed (no, it certainly wasn't you)).  What we don't have=20
> is an
>         understanding of the order of magnitude of the impact, and=20
> that is going
>         to be very hard to gather in so  fluid a situation with so=20
> long a
>         lookahead.  The point, by the way, as I see it, is not to=20
> punish the
>         U.S. but to hold a successful meeting (that is what the=20
> mtgvenue draft
>         states as well).
>
>         > Reducing frequency of
>         > U.S. meetings is not a boycott, and is something the IETF=20
> has been doing
>         > for a long time anyways.  Further reducing that frequency in=20
> the short
>         > term would be perfectly fine, though it would also reduce=20
> opportunities
>         > for gather the stats we really need to make a sound,=20
> non-partisan
>         > decision to boycott if the stats warrant it.
>         >
>
>         Turn this around: suppose we do keep the meeting in San=20
> Francisco, for
>         instance, and some number of people cannot get there for=20
> whatever
>         reason, or cannot otherwise function on an equal footing. =20
> Would the
>         IAOC then be attacked for having ignored the vast number of=20
> warnings
>         that have been signaled?
>
>         Eliot
>
>
>
>
>
>
>
>
> **********************************************
> 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=20
> or confidential. The information is intended to be for the use of the=20
> individual(s) named above. If you are not the intended recipient be=20
> aware that any disclosure, copying, distribution or use of the=20
> contents of this information, including attached files, is prohibited.

--=_MailMate_FFD977EA-03F3-459E-B26E-624E83692C5A_=
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">Jordi,</p>

<p dir=3D"auto">I=E2=80=99m sorry you feel the IAOC has been unresponsive=
 to your questions. I would ask for your continued understanding that we =
are still reviewing options, and won=E2=80=99t have full information ours=
elves until we are closer to closure.</p>

<p dir=3D"auto">In my message of April 12, wherein I outlined the informa=
tion we do have, I closed with:</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir=3D"auto">T=
he IAOC is continuing to gather data on travel to the US, concerns about =
traveling outside of it, and what alternatives are possible for IETF 102.=
 Our focus is currently on whether holding IETF 102 in San Francisco is t=
he best option to meet the needs of IETF work, recognizing that we cannot=
 predict the future. While it may take several weeks to allow for review =
and negotiation of any alternatives (if applicable), we are moving as qui=
ckly as possible because we realize that people will need time to plan th=
eir travel.</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">I believe you are asking us to share data that we don=E2=80=
=99t even have yet.  If we were to move the IETF 102 meeting, costs to th=
e IETF as an organization would be dependent not only on the cancellation=
 provisions in the current contract, but also on the alternate location c=
hosen and its contract options. We don=E2=80=99t have all of those number=
s yet. And, while it is certainly part of our deliberations about moving =
a meeting, these are not things we can expose and ask the community to vo=
te on. </p>

<p dir=3D"auto">The IAOC has moved at this point from gathering data on t=
ravel to the US to weighing what options best meet the needs of IETF work=
 in light of that data and the other aspects of IETF 102 planning.  As so=
on as we can move out of that stage and share the results with the commun=
ity, we will do so.</p>

<p dir=3D"auto">Leslie.</p>

<p dir=3D"auto">-- </p>

<hr style=3D"background:#333; background-image:linear-gradient(to right, =
#ccc, #333, #ccc); border:0; height:1px" height=3D"1">

<p dir=3D"auto">Leslie Daigle<br>
Principal, ThinkingCat Enterprises LLC</p>

<h2 style=3D"font-size:1.2em"><a href=3D"mailto:ldaigle@thinkingcat.com" =
style=3D"color:#3983C4">ldaigle@thinkingcat.com</a></h2>

<p dir=3D"auto">On 11 Apr 2017, at 7:11, JORDI PALET MARTINEZ wrote:</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir=3D"auto">C=
an we get an answer from the IAOC to the questions below?<br>
<br>
If we cancel San Francisco, how much that is going to cost to the IETF fo=
r each of two planned meetings?<br>
<br>
Can we cancel the actual hotel contract considering the new US situation?=
 If not, has this been considered for new contracts to avoid this problem=
?<br>
<br>
Otherwise there is any reason that can justify the lack of transparency i=
n this?<br>
<br>
Regards,<br>
Jordi<br>
<br>
<br>
-----Mensaje original-----<br>
De: JORDI PALET MARTINEZ &lt;jordi.palet@consulintel.es&gt;<br>
Fecha: mi=C3=A9rcoles, 5 de abril de 2017, 10:26<br>
Para: &lt;iaoc@ietf.org&gt;<br>
Asunto: Re: IAOC requesting input on (potential) meeting cities<br>
<br>
    One important question here, same as we had in the case of Singapore.=
<br>
<br>
    If we cancel San Francisco, how much that is going to cost to the IET=
F for each of two planned meetings?<br>
<br>
    Furthermore, can the IAOC respond to this:<br>
<br>
    Can we cancel the actual hotel contract considering the new US situat=
ion? If not, has this been considered for new contracts to avoid this pro=
blem?<br>
<br>
    I think the relevant information in the contract need to be disclosed=
 and have it now on the table, otherwise we will be wasting the time disc=
ussing possibilities that are actually impossible to assume for the IETF =
=E2=80=A6<br>
<br>
    My general position is:<br>
    1) I will prefer not cancelling already planned meetings.<br>
    2) I will prefer not =E2=80=9Cblocking=E2=80=9D any regions or countr=
ies from future meetings, including US.<br>
    3) However, for already contracted meetings, if this is going to cost=
 IETF thousands of dollars, we can=E2=80=99t afford that.<br>
    4) We must work with authorities to avoid people being banned for att=
ending the meetings.<br>
<br>
    Maybe I=E2=80=99ve missed responses to some of my answers already, in=
 any case, can the IAOC provide urgently those with a complete summary of=
 the situation?<br>
<br>
    Regards,<br>
    Jordi<br>
<br>
<br>
    -----Mensaje original-----<br>
    De: Eliot Lear &lt;lear@cisco.com&gt;<br>
    Responder a: &lt;lear@cisco.com&gt;<br>
    Fecha: mi=C3=A9rcoles, 5 de abril de 2017, 6:39<br>
    Para: Nico Williams &lt;nico@cryptonector.com&gt;, Yoav Nir &lt;ynir.=
ietf@gmail.com&gt;<br>
    CC: IETF &lt;ietf@ietf.org&gt;, JORDI PALET MARTINEZ &lt;jordi.palet@=
consulintel.es&gt;, Jared Mauch &lt;jared@puck.nether.net&gt;<br>
    Asunto: Re: IAOC requesting input on (potential) meeting cities<br>
<br>
        Nico,<br>
<br>
        On 4/5/17 12:10 AM, Nico Williams wrote:<br>
        &gt; I do suspect that the U.S. will be a more difficult location=
 for more<br>
        &gt; attendees than other locations.  Certainly the news we all s=
ee is not<br>
        &gt; encouraging as to hosting IETF meetings in the U.S.  This I =
don't deny.<br>
        &gt; Though it's also possible that this is becoming a self-reinf=
orcing meme<br>
        &gt; and that we're just not seeing incidents in other countries =
in the news.<br>
        &gt; In any case, the U.S. certainly does not have a monopoly on =
the border<br>
        &gt; harasment business.<br>
<br>
        Certainly people have had trouble getting into other countries, m=
ost<br>
        notably Canada where an IAB member was refused entry.  But this i=
sn't<br>
        just news.  It is a series of declarations by the U.S. government=
 of<br>
        their intentions, and the IAOC has to plan ahead.  That's why Jar=
ed's<br>
        request for data is simply not tenable *at this stage*.  If it tu=
rns out<br>
        that things aren't so bad, the IAOC can react accordingly.  Howev=
er, as<br>
        I wrote in my original email, there is now good reason to believe=
 that<br>
        things will get worse, due to the European Parliament=E2=80=99s d=
ecision to<br>
        require visas from U.S. citizens.<br>
<br>
        &gt; Some people may wish to boycott the U.S. by refusing to host=
 events<br>
        &gt; there.  There is some precedent for such a boycott.  For exa=
mple, some<br>
        &gt; time back an obscure agency of the Texas state government de=
cided to<br>
        &gt; guard its surplus budget by policing public drunkenness at h=
otel bars,<br>
        &gt; which led to a number of conferences pulling out of Texas, a=
nd the<br>
        &gt; ensuing bad PR led the legislature to rein in said agency.<b=
r>
        &gt;<br>
        &gt; However, at the scale of a state/province the politics of bo=
ycotts is<br>
        &gt; generally not partisan, but at a national/global scale it te=
nds to be<br>
        &gt; rankly partisan, and boycotts may not be productive and may =
be divisive,<br>
        &gt; and should be approached with care.  Here "care" means: get =
some<br>
        &gt; evidence of negative impact on participation.<br>
<br>
        We ALREADY have evidence, as some people couldn't make Chicago, a=
nd said<br>
        so on this very list (and, by the way, were shamefully attacked a=
nd<br>
        dismissed (no, it certainly wasn't you)).  What we don't have is =
an<br>
        understanding of the order of magnitude of the impact, and that i=
s going<br>
        to be very hard to gather in so  fluid a situation with so long a=
<br>
        lookahead.  The point, by the way, as I see it, is not to punish =
the<br>
        U.S. but to hold a successful meeting (that is what the mtgvenue =
draft<br>
        states as well).<br>
<br>
        &gt; Reducing frequency of<br>
        &gt; U.S. meetings is not a boycott, and is something the IETF ha=
s been doing<br>
        &gt; for a long time anyways.  Further reducing that frequency in=
 the short<br>
        &gt; term would be perfectly fine, though it would also reduce op=
portunities<br>
        &gt; for gather the stats we really need to make a sound, non-par=
tisan<br>
        &gt; decision to boycott if the stats warrant it.<br>
        &gt;<br>
<br>
        Turn this around: suppose we do keep the meeting in San Francisco=
, for<br>
        instance, and some number of people cannot get there for whatever=
<br>
        reason, or cannot otherwise function on an equal footing.  Would =
the<br>
        IAOC then be attacked for having ignored the vast number of warni=
ngs<br>
        that have been signaled?<br>
<br>
        Eliot<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
<a href=3D"http://www.consulintel.es" style=3D"color:#777">http://www.con=
sulintel.es</a><br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or c=
onfidential. The information is intended to be for the use of the individ=
ual(s) named above. If you are not the intended recipient be aware that a=
ny disclosure, copying, distribution or use of the contents of this infor=
mation, including attached files, is prohibited.</p>
</blockquote></div>
<div style=3D"white-space:normal">
</div>
</div>
</body>
</html>

--=_MailMate_FFD977EA-03F3-459E-B26E-624E83692C5A_=--


From nobody Mon May  1 16:18:22 2017
Return-Path: <ldaigle@thinkingcat.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 4942912EB77; Mon,  1 May 2017 16:18:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.69
X-Spam-Level: 
X-Spam-Status: No, score=-2.69 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, T_DKIM_INVALID=0.01, 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=thinkingcat.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 oa7iMfqV17i4; Mon,  1 May 2017 16:18:19 -0700 (PDT)
Received: from homiemail-a88.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2ADEC12EB4B; Mon,  1 May 2017 16:15:29 -0700 (PDT)
Received: from homiemail-a88.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a88.g.dreamhost.com (Postfix) with ESMTP id E7F54A003A1E; Mon,  1 May 2017 16:15:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thinkingcat.com; h=from:to :cc:subject:date:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=thinkingcat.com; bh=C TvyBzI/qsEg+BjxsXybnV9V1AA=; b=XYbc7eSlAPfUjuhJ11AWUmCWJUAtvbQzg gF2QxO9bZ6XT0+J6RUTT5uET2I4hIV0taqujbIUDi9ibEDNnWMNpOglfeB2ahp0r 75X+VvPIdYCKEaeRosKdohaYTK0I7sO7hE5CzRYGH5G5k9dkMyrA9az4Ei7CIwSi PeFGczQNXM=
Received: from [192.168.1.5] (pool-173-72-147-193.clppva.fios.verizon.net [173.72.147.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: leslie@oceanpurl.net) by homiemail-a88.g.dreamhost.com (Postfix) with ESMTPSA id 634A7A003A1D; Mon,  1 May 2017 16:15:28 -0700 (PDT)
From: "Leslie Daigle" <ldaigle@thinkingcat.com>
To: "Vinayak Hegde" <vinayakh@gmail.com>
Cc: "IETF Discussion Mailing List" <ietf@ietf.org>, "iaoc@ietf.org" <iaoc@ietf.org>
Subject: Re: [IAOC] Update on feedback on US-based meetings, and IETF 102
Date: Mon, 01 May 2017 19:15:27 -0400
Message-ID: <37771A55-9DE6-4840-861B-6A6700380B6B@thinkingcat.com>
In-Reply-To: <CAKe6YvN08wvC9N_GQQc2nNYa61EcqKmtZ=ajQUnfBUJvtEC6pw@mail.gmail.com>
References: <149204035801.15694.8437554373033456064.idtracker@ietfa.amsl.com> <CAKe6YvN08wvC9N_GQQc2nNYa61EcqKmtZ=ajQUnfBUJvtEC6pw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
X-Mailer: MailMate (1.9.6r5347)
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pZPch9rPTHOK4-VRVcLCiIh2yxw>
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, 01 May 2017 23:18:20 -0000

Hi,

Comments in-line =E2=80=94

On 14 Apr 2017, at 5:06, Vinayak Hegde wrote:

> On Thu, Apr 13, 2017 at 5:09 AM, IAOC Chair <iaoc-chair@ietf.org>=20
> wrote:
>> On March 31, 2017, we put out a request for input on experiences with=20
>> travel to the recent IETF meeting in the US, and solicited=20
>> information pertinent to plans to attend IETF meetings within or=20
>> outside the US in the coming years.  We have had over 350 responses=20
>> to the questionnaire, and we appreciate each and every one of them!  =20
>> We did not gather the data in such a way for it to reflect a=20
>> representative sample of the IETF community, or of potential meeting=20
>> attendees. But we did gain insights from those who responded that we=20
>> did not have before.
>
> Can the data be put out in an anonymized fashion without revealing PII
> (such as name or email) ? The data has been interpreted for the
> community but it might be useful for the community to look at the data
> gathered as well. It might help change opinions or people on the fence
> or people to rethink their positions.

The IAOC reviewed this again last week.  The short answer is:  no there=20
isn=E2=80=99t a way to put out more information from the survey.  We gath=
ered=20
the information with the offer of anonymity, and we don=E2=80=99t believe=
 it=20
would be right to re-interpret that after the fact.

>
>> Over 40% of the respondents said they had attended 20 or more IETF=20
>> meetings, and over 50% of them said they were authors of active=20
>> working group documents.  Slightly more than 40% stated US residency,=20
>> and just less than 60% said they were not US-resident.
>
> Since the US-meeting disproportionately affects those traveling to the
> US, I think that might be an axis against which data needs to be
> interpreted. The burden on many US citizens would be (possibly) extra
> travel in case the meeting is not located nearby (such as in Canada or
> Mexico).
>
> Also many nationalities might not need to apply for US visa or face
> lesser stringent barriers to entry. So knowing the country of
> citizenship might be useful in the data.
>
>> The general comments on meeting in the US played along the same lines=20
>> as has been shared on the IETF discussion list:  people are variously=20
>> for moving all meetings out of the US, or adamantly against, or=20
>> somewhere in between, each position supported by good reasons.
>
> Again might be useful to see the data.
>
>> The IAOC is continuing to gather data on travel to the US, concerns=20
>> about traveling outside of it, and what alternatives are possible for=20
>> IETF 102.  Our focus is currently on whether holding IETF 102 in San=20
>> Francisco is the best option to meet the needs of IETF work,=20
>> recognizing that we cannot predict the future.  While it may take=20
>> several weeks to allow for review and negotiation of any alternatives=20
>> (if applicable), we are moving as quickly as possible because we=20
>> realize that people will need time to plan their travel.
>
> Is there a rough timeline for this ?

The rough timeline is still =E2=80=9Cseveral weeks=E2=80=9D, I=E2=80=99m =
afraid.  It is=20
gated not only on our choices, but the time it takes to get information=20
about potentially-viable sites, and negotiate a contract (if an=20
alternate site seems reasonable).   Speaking for myself only, I would=20
like to have the question settled not later than a year before the=20
scheduled meeting.   That is only sensible, in terms of finding credible=20
alternative sites, and in terms of giving prospective attendees=20
sufficient advance notice to be able to make their own plans.

Thanks,
Leslie.


>
> -- Vinayak


--=20

-------------------------------------------------------------------
Leslie Daigle
Principal, ThinkingCat Enterprises LLC
ldaigle@thinkingcat.com
-------------------------------------------------------------------


From nobody Mon May  1 19:40:06 2017
Return-Path: <martin.thomson@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 6F95F12EB1E; Mon,  1 May 2017 19:39:50 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Thomson <martin.thomson@gmail.com>
To: <art@ietf.org>
Cc: draft-ietf-anima-grasp.all@ietf.org, ietf@ietf.org, anima@ietf.org
Subject: Artart telechat review of draft-ietf-anima-grasp-11
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149369279041.9906.5712707340786253297@ietfa.amsl.com>
Date: Mon, 01 May 2017 19:39:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qg_tYfrT0KBnokX2Omv2vWJFCQc>
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, 02 May 2017 02:39:50 -0000

Reviewer: Martin Thomson
Review result: Not Ready

This document describes a generic protocol that is for doing just
about anything and run over just about any transport protocol.  Within
that remit, the document is coherent and though I agree with Barry
about unnecessary verbiage, it seems to achieve the goals it sets.

I don't believe that this document describes a protocol that could be
deployed.

Caveat here: I didn't review this as thoroughly as I would have liked.
 It's a large document, though it's clear that it isn't large enough
to cover its intended scope in a couple of key areas.  There is with
lots of content in some areas - some of it quite detailed.  But there
is surprisingly little detail in areas that I would have imagined to
be critical.  The two areas that concern me most are transport and
security.


The draft talks very little about how messages get to their
destinations.  There's a brief section on UDP/TCP usage in one place
and an admonishment to use DTLS/TLS in another, but those sections
don't seem to have ever met each other.  I'm forced to conclude that
this is well ahead of the other pieces that will fill in those gaps. 
Given that there are no drafts associated with the ANIMA working group
that attempt to fill those gaps, I really don't know how this would
ever get deployed.  The status of the implementations only really
confirms this.

As an aside, use of UDP needs a few more details.  A few that spring
to mind:

  Congestion - Since this appears to be a lock-step protocol, that is
probably acceptable (one packet per round trip is generally considered
fine).

  Loss - This doesn't appear to have any provision for loss recovery. 
For a long-running negotiation that includes wait steps, this seems
necessary.

  Middleboxes - If a peer has to wait a long time for a negotiation,
what happens if the NAT binding goes away in the meantime?  How does a
peer ensure reachability?  Can middleboxes verify that endpoints are
willing to communicate?

The locators concept relates to this.  It would appear to be
under-specified, largely as a result of not having any concrete
transport definitions.  For instance, how would you use each of the
different locators used in the protocol?  Though it might seem
obvious, even the IPv6 locator doesn't actually include a definition
of what you might do with it.  

Does the endpoint construct a UDP packet with the CBOR of a GRASP
message as its payload and unicast it to the identified IP and port? 
Seems obvious, needs writing down.  

The same goes for the FQDN, which I suppose involves an AAAA/A record
lookup. It needs to say that, unless it's really SRV or something
else.  And URIs aren't generically usable, so a lot more work would be
needed to make sense of a URI.


Security seems to be critical, but the key question of establishing a
trust domain is left out of scope.  That conveniently removes some
hard problems, but I believe that there were a few inconvenient
problems that were removed at the same time.  For instance,
authentication and confidentiality mechanisms for discovery seem to be
non-existent.  (D)TLS can't secure a multicast signal, but no effort
has been put into providing an authentication framework.


Nits

The document really isn't clear about how multi-round negotiation
works.  A picture might help here.  I ask because the definition of
how timers run is a little unclear.  I probably missed the text about
this, but I assume that an endpoint that responds to M_REQ_NEG with
M_NEGOTIATE  starts a new timer, and if a multiple rounds are used the
timer is reset each time that M_NEGOTIATE is sent.  Is there any need
for any overall negotiation timer, or do you just multiply out the hop
(loop) count?

The existence of "dry run" negotiations leads me to ask how a protocol
participant is expected to behave when negotiating.  Is it expected to
enact intermediate values, or does it commit only when the negotiation
concludes?



From nobody Mon May  1 20:06:58 2017
Return-Path: <randy@psg.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 EDC351294C9; Mon,  1 May 2017 20:06:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 J9wo8djHGYYm; Mon,  1 May 2017 20:06:48 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 1C3F7126D73; Mon,  1 May 2017 20:04:17 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1d5O6p-0000BU-ES; Tue, 02 May 2017 03:04:15 +0000
Date: Tue, 02 May 2017 12:04:13 +0900
Message-ID: <m21ss80xjm.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
In-Reply-To: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net>
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nmW5Vhvs1k_-xvxtiZ7nC7RTlNw>
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, 02 May 2017 03:06:50 -0000

> For example, Section 2.2 talks about the importance of passive
> monitoring for traffic surveys, but fails to discuss alternative means

possibly our friends from z=FCrich have some ideas here

randy


From nobody Mon May  1 21:31:47 2017
Return-Path: <bill.wu@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 04FF412EB54; Mon,  1 May 2017 21:31:41 -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 0exbS9zpHEcJ; Mon,  1 May 2017 21:31:39 -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 745C5129568; Mon,  1 May 2017 21:28:55 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DFV32154; Tue, 02 May 2017 04:28:53 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 2 May 2017 05:28:52 +0100
Received: from NKGEML513-MBS.china.huawei.com ([169.254.2.108]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Tue, 2 May 2017 12:28:47 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
CC: "netmod-chairs@ietf.org" <netmod-chairs@ietf.org>, "warren@kumari.net" <warren@kumari.net>, "draft-ietf-netmod-yang-model-classification@ietf.org" <draft-ietf-netmod-yang-model-classification@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
Subject: RE: [netmod] Last Call: <draft-ietf-netmod-yang-model-classification-06.txt> (YANG Module Classification) to Informational RFC
Thread-Topic: [netmod] Last Call: <draft-ietf-netmod-yang-model-classification-06.txt> (YANG Module Classification) to Informational RFC
Thread-Index: AQHSwiNUA4ZngZJx/kSLs6o/LYmtAaHeziwAgAGmIfA=
Date: Tue, 2 May 2017 04:28:47 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9A89EC27@nkgeml513-mbs.china.huawei.com>
References: <149360589744.9906.9498469901914786081.idtracker@ietfa.amsl.com> <009f01d2c26c$4d733ca0$e859b5e0$@olddog.co.uk>
In-Reply-To: <009f01d2c26c$4d733ca0$e859b5e0$@olddog.co.uk>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.136.78.218]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.59080B05.00F0, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.2.108, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 65d4effaa3c4ac2934fc772f446b612f
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fRNjyjBXOjLsC1_Qf2cR9UxuklA>
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, 02 May 2017 04:31:41 -0000

VGhhbmtzIGZvciB1cGRhdGluZywgdGhlIGNoYW5nZXMgaW4gKHYtMDYpc291bmRzIGdyZWF0Lg0K
SSBzdXBwb3J0IHRoZSBwdWJsaWNhdGlvbiBvZiB0aGlzIGRvY3VtZW50Lg0KDQotUWluDQotLS0t
LdPKvP7Urbz+LS0tLS0NCreivP7IyzogbmV0bW9kIFttYWlsdG86bmV0bW9kLWJvdW5jZXNAaWV0
Zi5vcmddILT6se0gQWRyaWFuIEZhcnJlbA0Kt6LLzcqxvOQ6IDIwMTfE6jXUwjHI1SAxOToxNg0K
ytW8/sjLOiBpZXRmQGlldGYub3JnDQqzrcvNOiBuZXRtb2QtY2hhaXJzQGlldGYub3JnOyB3YXJy
ZW5Aa3VtYXJpLm5ldDsgZHJhZnQtaWV0Zi1uZXRtb2QteWFuZy1tb2RlbC1jbGFzc2lmaWNhdGlv
bkBpZXRmLm9yZzsgbmV0bW9kQGlldGYub3JnDQrW98ziOiBSZTogW25ldG1vZF0gTGFzdCBDYWxs
OiA8ZHJhZnQtaWV0Zi1uZXRtb2QteWFuZy1tb2RlbC1jbGFzc2lmaWNhdGlvbi0wNi50eHQ+IChZ
QU5HIE1vZHVsZSBDbGFzc2lmaWNhdGlvbikgdG8gSW5mb3JtYXRpb25hbCBSRkMNCg0KSGksDQoN
CkkndmUgYmVlbiByZWFkaW5nLCByZXZpZXdpbmcsIGFuZCBkaXNjdXNzaW5nIHRoaXMgZG9jdW1l
bnQgZm9yIGEgbnVtYmVyIG9mIHJldmlzaW9ucy4gT2Ygc3BlY2lhbCBjb25jZXJuIHdhcyB0aGUg
cmVsYXRpb25zaGlwIHRvIFJGQyA4MDQ5IGFuZCBkcmFmdC13dS1vcHNhd2ctc2VydmljZS1tb2Rl
bC1leHBsYWluZWQuDQoNClRoZSBsYXN0IHR3byByZXZpc2lvbnMgaGF2ZSBjYXB0dXJlZCB0aGUg
ZXNzZW5jZSBvZiB0aGVzZSBkaXNjdXNzaW9ucywgYW5kIEkgYW0gaGFwcHkgd2l0aCB0aGUgZG9j
dW1lbnQgYXMgaXQgc3RhbmRzLiBJIHRoaW5rIGl0IHNob3VsZCBiZSBwdWJsaXNoZWQgYXMgYW4g
SW5mb3JtYXRpb25hbCBSRkMuDQoNClRoYW5rcywNCkFkcmlhbg0KDQo+IC0tLS0tT3JpZ2luYWwg
TWVzc2FnZS0tLS0tDQo+IEZyb206IG5ldG1vZCBbbWFpbHRvOm5ldG1vZC1ib3VuY2VzQGlldGYu
b3JnXSBPbiBCZWhhbGYgT2YgVGhlIElFU0cNCj4gU2VudDogMDEgTWF5IDIwMTcgMDM6MzINCj4g
VG86IElFVEYtQW5ub3VuY2UNCj4gQ2M6IG5ldG1vZC1jaGFpcnNAaWV0Zi5vcmc7IHdhcnJlbkBr
dW1hcmkubmV0OyBkcmFmdC1pZXRmLW5ldG1vZC15YW5nLSANCj4gbW9kZWwtY2xhc3NpZmljYXRp
b25AaWV0Zi5vcmc7IG5ldG1vZEBpZXRmLm9yZw0KPiBTdWJqZWN0OiBbbmV0bW9kXSBMYXN0IENh
bGw6DQo8ZHJhZnQtaWV0Zi1uZXRtb2QteWFuZy1tb2RlbC1jbGFzc2lmaWNhdGlvbi0wNi50eHQ+
DQo+IChZQU5HIE1vZHVsZSBDbGFzc2lmaWNhdGlvbikgdG8gSW5mb3JtYXRpb25hbCBSRkMNCj4g
DQo+IA0KPiBUaGUgSUVTRyBoYXMgcmVjZWl2ZWQgYSByZXF1ZXN0IGZyb20gdGhlIE5FVENPTkYg
RGF0YSBNb2RlbGluZyANCj4gTGFuZ3VhZ2UgV0cgKG5ldG1vZCkgdG8gY29uc2lkZXIgdGhlIGZv
bGxvd2luZyBkb2N1bWVudDoNCj4gLSAnWUFORyBNb2R1bGUgQ2xhc3NpZmljYXRpb24nDQo+ICAg
PGRyYWZ0LWlldGYtbmV0bW9kLXlhbmctbW9kZWwtY2xhc3NpZmljYXRpb24tMDYudHh0PiBhcyAN
Cj4gSW5mb3JtYXRpb25hbCBSRkMNCj4gDQo+IFRoZSBJRVNHIHBsYW5zIHRvIG1ha2UgYSBkZWNp
c2lvbiBpbiB0aGUgbmV4dCBmZXcgd2Vla3MsIGFuZCBzb2xpY2l0cyANCj4gZmluYWwgY29tbWVu
dHMgb24gdGhpcyBhY3Rpb24uIFBsZWFzZSBzZW5kIHN1YnN0YW50aXZlIGNvbW1lbnRzIHRvIHRo
ZSANCj4gaWV0ZkBpZXRmLm9yZyBtYWlsaW5nIGxpc3RzIGJ5IDIwMTctMDUtMTQuIEV4Y2VwdGlv
bmFsbHksIGNvbW1lbnRzIG1heSANCj4gYmUgc2VudCB0byBpZXNnQGlldGYub3JnIGluc3RlYWQu
IEluIGVpdGhlciBjYXNlLCBwbGVhc2UgcmV0YWluIHRoZSANCj4gYmVnaW5uaW5nIG9mIHRoZSBT
dWJqZWN0IGxpbmUgdG8gYWxsb3cgYXV0b21hdGVkIHNvcnRpbmcuDQo+IA0KPiBBYnN0cmFjdA0K
PiANCj4gDQo+ICAgIFRoZSBZQU5HIGRhdGEgbW9kZWxpbmcgbGFuZ3VhZ2UgaXMgY3VycmVudGx5
IGJlaW5nIGNvbnNpZGVyZWQgZm9yIGENCj4gICAgd2lkZSB2YXJpZXR5IG9mIGFwcGxpY2F0aW9u
cyB0aHJvdWdob3V0IHRoZSBuZXR3b3JraW5nIGluZHVzdHJ5IGF0DQo+ICAgIGxhcmdlLiAgTWFu
eSBzdGFuZGFyZHMtZGVmaW5pbmcgb3JnYW5pemF0aW9ucyAoU0RPcyksIG9wZW4gc291cmNlDQo+
ICAgIHNvZnR3YXJlIHByb2plY3RzLCB2ZW5kb3JzIGFuZCB1c2VycyBhcmUgdXNpbmcgWUFORyB0
byBkZXZlbG9wIGFuZA0KPiAgICBwdWJsaXNoIFlBTkcgbW9kdWxlcyBmb3IgYSB3aWRlIHZhcmll
dHkgb2YgYXBwbGljYXRpb25zLiAgQXQgdGhlIHNhbWUNCj4gICAgdGltZSwgdGhlcmUgaXMgY3Vy
cmVudGx5IG5vIHdlbGwta25vd24gdGVybWlub2xvZ3kgdG8gY2F0ZWdvcml6ZQ0KPiAgICB2YXJp
b3VzIHR5cGVzIG9mIFlBTkcgbW9kdWxlcy4NCj4gDQo+ICAgIEEgY29uc2lzdGVudCB0ZXJtaW5v
bG9neSB3b3VsZCBoZWxwIHdpdGggdGhlIGNhdGVnb3JpemF0aW9uIG9mIFlBTkcNCj4gICAgbW9k
dWxlcywgYXNzaXN0IGluIHRoZSBhbmFseXNpcyBvZiB0aGUgWUFORyBkYXRhIG1vZGVsaW5nIGVm
Zm9ydHMgaW4NCj4gICAgdGhlIElFVEYgYW5kIG90aGVyIG9yZ2FuaXphdGlvbnMsIGFuZCBicmlu
ZyBjbGFyaXR5IHRvIHRoZSBZQU5HLQ0KPiAgICByZWxhdGVkIGRpc2N1c3Npb25zIGJldHdlZW4g
dGhlIGRpZmZlcmVudCBncm91cHMuDQo+IA0KPiAgICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBh
IHNldCBvZiBjb25jZXB0cyBhbmQgYXNzb2NpYXRlZCB0ZXJtcyB0bw0KPiAgICBzdXBwb3J0IGNv
bnNpc3RlbnQgY2xhc3NpZmljYXRpb24gb2YgWUFORyBtb2R1bGVzLg0KPiANCj4gDQo+IA0KPiAN
Cj4gVGhlIGZpbGUgY2FuIGJlIG9idGFpbmVkIHZpYQ0KPiBodHRwczovL2RhdGF0cmFja2VyLmll
dGYub3JnL2RvYy9kcmFmdC1pZXRmLW5ldG1vZC15YW5nLW1vZGVsLWNsYXNzaWZpDQo+IGNhdGlv
bi8NCj4gDQo+IElFU0cgZGlzY3Vzc2lvbiBjYW4gYmUgdHJhY2tlZCB2aWENCj4gaHR0cHM6Ly9k
YXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1uZXRtb2QteWFuZy1tb2RlbC0NCj4g
Y2xhc3NpZmljYXRpb24vYmFsbG90Lw0KPiANCj4gDQo+IE5vIElQUiBkZWNsYXJhdGlvbnMgaGF2
ZSBiZWVuIHN1Ym1pdHRlZCBkaXJlY3RseSBvbiB0aGlzIEktRC4NCj4gDQo+IA0KPiANCj4gDQo+
IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IG5ldG1v
ZCBtYWlsaW5nIGxpc3QNCj4gbmV0bW9kQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vbmV0bW9kDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQpuZXRtb2QgbWFpbGluZyBsaXN0DQpuZXRtb2RAaWV0Zi5vcmcN
Cmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbmV0bW9kDQo=


From nobody Mon May  1 22:42:54 2017
Return-Path: <weigengyu@bupt.edu.cn>
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 5AE7A129A8D for <ietf@ietfa.amsl.com>; Mon,  1 May 2017 22:42:52 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, 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 SrBz1vypzFPT for <ietf@ietfa.amsl.com>; Mon,  1 May 2017 22:42:50 -0700 (PDT)
Received: from mx1.bupt.edu.cn (mx1.bupt.edu.cn [211.68.68.2]) by ietfa.amsl.com (Postfix) with ESMTP id 8AB55129AB5 for <ietf@ietf.org>; Mon,  1 May 2017 22:40:20 -0700 (PDT)
Received: from WeiGengyuPC (unknown [114.255.40.42]) by mx1.bupt.edu.cn (AnyMacro(G7)) with ESMTPA id E53B719F36A; Tue,  2 May 2017 13:31:27 +0800 (HKT)
Message-ID: <AF06737CE0C34EA88BFFFCA04B89CC95@WeiGengyuPC>
From: "weigengyu" <weigengyu@bupt.edu.cn>
To: "Yoshifumi Nishida" <nishida@sfc.wide.ad.jp>, "Brian Raymor" <Brian.Raymor@microsoft.com>
Cc: <tsv-art@ietf.org>, "Yoshifumi Nishida" <nishida@sfc.wide.ad.jp>, <draft-ietf-core-coap-tcp-tls@ietf.org>, <core@ietf.org>, <ietf@ietf.org>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com> <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydcc7k2i5=OSSvvtzU2B1Qa62b3RR3iY0wBfQ2pOYQrkQ@mail.gmail.com> <BY2PR21MB00849DB795086F08F6D7A98A831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249yeS8sZaJcADuz+bYAJa-CXs4v291Fm=adRouO1R=svPDw@mail.gmail.com> <BY2PR21MB008453149ADC1A998FEA56D3831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydRLFpG=yHYvaZvPBiQuW5x=4HZqCZyTAb2HHeDuP+wAA@mail.gmail.com>
In-Reply-To: <CAO249ydRLFpG=yHYvaZvPBiQuW5x=4HZqCZyTAb2HHeDuP+wAA@mail.gmail.com>
Subject: Re: [core] TSV-ART review of draft-ietf-core-coap-tcp-tls-07
Date: Tue, 2 May 2017 13:31:27 +0800
Organization: BUPT
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0018_01D2C348.6680E2B0"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3528.331
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iY1lUPR_BkTRSdb8vWJ8dT-Mf-c>
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, 02 May 2017 05:42:52 -0000

ÕâÊÇһ·â MIME ¸ñʽµĶ෽Óʼþ¡£

------=_NextPart_000_0018_01D2C348.6680E2B0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi all,=20

Transfering CoAP defined in -08 draft for reliable transmission =
facilities is as important as CoAP over CON/NON message.=20
In -08 draft, it is just clear how to make a new message for tranfering =
over TCP,=20
or other reliable facilities in the scenario (I) CoAP/UDP ---> (C2C) =
Proxy ----> CoAP over TCP.=20
But in -08 draft it is unclear how to work for the scenario (II) =
CoAP/TCP ---> (C2C) Proxy ----> CoAP over UDP.=20

The problem is when the C2C Proxy have got a message form the CoAP/TCP =
side,=20
how the Proxy make a decision to delivery CON or NON message carrying =
CoAP over UDP?=20
Even for the scenario (I), the problem is the same when delivering the =
CoAP response.

In these scenarios a key problem is that should the CoAP semantics be =
End-to-End or Hop-by-Hop when a C2C proxy is existed.=20

Regards,=20

Gengyu WEI
Network Technology Center
School of Computer=20
Beijing University of Posts and Telecommunications

From: Yoshifumi Nishida=20
Sent: Sunday, April 30, 2017 12:24 PM
To: Brian Raymor=20
Cc: tsv-art@ietf.org ; Yoshifumi Nishida ; =
draft-ietf-core-coap-tcp-tls@ietf.org ; core@ietf.org ; ietf@ietf.org=20
Subject: Re: [core] TSV-ART review of draft-ietf-core-coap-tcp-tls-07

Hello,=20
As far as I've read -08 draft, I think this point has not been addressed =
yet. I hope some folks could elaborate a bit more if they think this is =
not an important point for the draft.
--
Yoshi

On Fri, Apr 21, 2017 at 2:57 PM, Brian Raymor =
<Brian.Raymor@microsoft.com> wrote:

  I think that I understand your perceptions better. Prior to adoption =
of coap-tcp-tls and before I was active in the WG, I recall discussions =
related to the confusion over application vs transport reliability in =
CoAP especially as related to CON and NON. What was intended?



  Tim Carey outlined some concerns in:

  =
https://tools.ietf.org/html/draft-carey-core-std-msg-vs-trans-adapt-00#se=
ction-2



  This topic was presented in detail at IETF 93 - =
https://www.ietf.org/proceedings/93/slides/slides-93-core-0.pdf - =
starting on slide 23.



  And in a related thread on the mailing list back in 2015 - =
https://www.ietf.org/mail-archive/web/core/current/msg06280.html - =
Carsten responded:



  > In any case, CON and NON are about message layer semantics, not =
about application semantics

  > -- you gave them a meaning they don't have.=20



  By IETF 94, the authors were reporting =E2=80=93 =E2=80=9CMost of the =
Confusion around              CON/NON was resolved=E2=80=9D.=20



  Where relevant, I=E2=80=99ve added clarifications - such as the =
Appendix related to differences in Observe for reliable transports.



  Both Carsten and Hannes could probably offer more context if needed.



  From: Yoshifumi Nishida [mailto:nishida@sfc.wide.ad.jp]=20
  Sent: Friday, April 21, 2017 2:08 PM
  To: Brian Raymor <Brian.Raymor@microsoft.com>
  Cc: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>; tsv-art@ietf.org; =
draft-ietf-core-coap-tcp-tls@ietf.org; core@ietf.org; ietf@ietf.org
  Subject: Re: TSV-ART review of draft-ietf-core-coap-tcp-tls-07



  Hi Brian,



  Just in case,

  Reliable transports only provide reliability at transport level. It =
doesn't provide reliability in application protocol level.=20



  RFC7252 has reliability mechanisms in it since it uses UDP. This means =
it has abilities to check both transport and app level reliability.

  This draft only provides transport level reliability and apps will =
need to detect app protocol failure by themselves.=20

  This means 7252 and this draft are not totally equivalent from the =
viewpoint of applications.=20



  I am not saying this is wrong or bad, but I believe app developer =
should aware this point.

  --

  Yoshi



  On Fri, Apr 21, 2017 at 11:15 AM, Brian Raymor =
<Brian.Raymor@microsoft.com> wrote:

    Hi Yoshi,



    > OK. I also think we should state that the protocol should notify =
the failure events to applications.=20

    > Since errors can happen not only in TCP, but also TLS and =
websocket level, mentioning only TCP close or reset might not=20

    > be enough.



    After reviewing with the authors, an additional clarification was =
appended to 3.4 Connection Health - =
https://github.com/core-wg/coap-tcp-tls/pull/140/files



    The opinion of the authors (and Gengyu WEI=E2=80=99s recent response =
- https://www.ietf.org/mail-archive/web/core/current/msg08622.html) is =
that RFC6455 covers the WebSocket case and does not need to be repeated =
here.



    > When we use 7252, I think applications basically don't need to =
implement timeouts or retry mechanisms as the protocol

    > provides such things.=20



    RFC7252 provides timeouts and retries because it's implementing a =
TCP-like reliability mechanism over UDP - =
https://tools.ietf.org/html/rfc7252#section-2.1



    > However, when we use this one, it seems applications will need to =
have such mechanisms. Isn't it a bit confusing? I am thinking that

    > there need to be some guidance here.

    > BTW, PONG is one example.



    For coap-tcp-tls, there are multiple early implementations. This has =
never been reported as a source of confusion.=20



    >> My sense is that we should treat this as an update to RFC7959 =
based on the original language:

    > I don't have a strong opinion here. Updating 7959 is fine for me =
if it's clearer to CoAP people.



    I've merged the change - =
https://github.com/core-wg/coap-tcp-tls/pull/138/files



    Thanks again for helping us to improve the quality of the draft,



    =E2=80=A6Brian






-------------------------------------------------------------------------=
-------
_______________________________________________
core mailing list
core@ietf.org
https://www.ietf.org/mailman/listinfo/core

------=_NextPart_000_0018_01D2C348.6680E2B0
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD>
<BODY dir=3Dltr>
<DIV dir=3Dltr>
<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>Hi all, </DIV>
<DIV>&nbsp;</DIV>
<DIV>Transfering CoAP defined in -08 draft for reliable transmission =
facilities=20
is as important as CoAP over CON/NON message. </DIV>
<DIV>In -08 draft, it is just clear how to make a new message for =
tranfering=20
over TCP, </DIV>
<DIV>or other reliable facilities in the scenario (I) CoAP/UDP ---&gt; =
(C2C)=20
Proxy ----&gt; CoAP over TCP. </DIV>
<DIV>But in -08 draft it is unclear how to work for the scenario (II) =
CoAP/TCP=20
---&gt; (C2C) Proxy ----&gt; CoAP over UDP. </DIV>
<DIV>&nbsp;</DIV>
<DIV>The problem is when the C2C Proxy have got a message form the =
CoAP/TCP=20
side, </DIV>
<DIV>how the Proxy make a decision to delivery CON or NON message =
carrying CoAP=20
over UDP? </DIV>
<DIV>Even for the scenario (I), the problem is the same when delivering =
the CoAP=20
response.</DIV>
<DIV>&nbsp;</DIV>
<DIV>In these scenarios a key problem is that should the CoAP semantics =
be=20
End-to-End or Hop-by-Hop when a C2C proxy is existed. </DIV>
<DIV>&nbsp;</DIV>
<DIV>Regards, </DIV>
<DIV>&nbsp;</DIV>
<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: =
#000000">Gengyu=20
WEI<BR>Network Technology Center<BR>School of Computer <BR>Beijing =
University of=20
Posts and Telecommunications</DIV>
<DIV=20
style=3D'FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: =
"Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; =
DISPLAY: inline'>
<DIV style=3D"FONT: 10pt tahoma">
<DIV>&nbsp;</DIV>
<DIV style=3D"BACKGROUND: #f5f5f5">
<DIV style=3D"font-color: black"><B>From:</B> <A =
title=3Dnishida@sfc.wide.ad.jp=20
href=3D"mailto:nishida@sfc.wide.ad.jp">Yoshifumi Nishida</A> </DIV>
<DIV><B>Sent:</B> Sunday, April 30, 2017 12:24 PM</DIV>
<DIV><B>To:</B> <A title=3DBrian.Raymor@microsoft.com=20
href=3D"mailto:Brian.Raymor@microsoft.com">Brian Raymor</A> </DIV>
<DIV><B>Cc:</B> <A title=3Dtsv-art@ietf.org=20
href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.org</A> ; <A=20
title=3Dnishida@sfc.wide.ad.jp =
href=3D"mailto:nishida@sfc.wide.ad.jp">Yoshifumi=20
Nishida</A> ; <A title=3Ddraft-ietf-core-coap-tcp-tls@ietf.org=20
href=3D"mailto:draft-ietf-core-coap-tcp-tls@ietf.org">draft-ietf-core-coa=
p-tcp-tls@ietf.org</A>=20
; <A title=3Dcore@ietf.org =
href=3D"mailto:core@ietf.org">core@ietf.org</A> ; <A=20
title=3Dietf@ietf.org href=3D"mailto:ietf@ietf.org">ietf@ietf.org</A> =
</DIV>
<DIV><B>Subject:</B> Re: [core] TSV-ART review of=20
draft-ietf-core-coap-tcp-tls-07</DIV></DIV></DIV>
<DIV>&nbsp;</DIV></DIV>
<DIV=20
style=3D'FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: =
"Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; =
DISPLAY: inline'>
<DIV dir=3Dltr>Hello,=20
<DIV>As far as I've read -08 draft, I think this point has not been =
addressed=20
yet. I hope some folks could elaborate a bit more if they think this is =
not an=20
important point for the draft.</DIV>
<DIV>--</DIV>
<DIV>Yoshi</DIV>
<DIV>
<DIV class=3Dgmail_extra>
<DIV>&nbsp;</DIV>
<DIV class=3Dgmail_quote>On Fri, Apr 21, 2017 at 2:57 PM, Brian Raymor =
<SPAN=20
dir=3Dltr>&lt;<A href=3D"mailto:Brian.Raymor@microsoft.com"=20
target=3D_blank>Brian.Raymor@microsoft.com</A>&gt;</SPAN> wrote:<BR>
<BLOCKQUOTE class=3Dgmail_quote=20
style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc =
1px solid">
  <DIV lang=3DEN-US vlink=3D"purple" link=3D"blue">
  <DIV=20
  =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677W=
ordSection1>
  <P class=3DMsoNormal><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>I think =
that I=20
  understand your perceptions better. Prior to adoption of coap-tcp-tls =
and=20
  before I was active in the WG, I recall discussions related to the =
confusion=20
  over application vs transport reliability in CoAP especially as =
related to CON=20
  and NON. What was intended?<U></U><U></U></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'><U></U><U></U></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>Tim Carey =
outlined=20
  some concerns in:<U></U><U></U></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'><A=20
  =
href=3D"https://tools.ietf.org/html/draft-carey-core-std-msg-vs-trans-ada=
pt-00#section-2"=20
  =
target=3D_blank>https://tools.ietf.org/html/dr<WBR>aft-carey-core-std-msg=
-vs-tran<WBR>s-adapt-00#section-2</A><U></U><U></U></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'><U></U><U></U></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>This =
topic was=20
  presented in detail at IETF 93 - <A=20
  =
href=3D"https://www.ietf.org/proceedings/93/slides/slides-93-core-0.pdf" =

  =
target=3D_blank>https://www.ietf.org/proceedin<WBR>gs/93/slides/slides-93=
-core-0.<WBR>pdf</A>=20
  - starting on slide 23.<U></U><U></U></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'><U></U><U></U></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>And in a =
related=20
  thread on the mailing list back in 2015 - <A=20
  =
href=3D"https://www.ietf.org/mail-archive/web/core/current/msg06280.html"=
=20
  =
target=3D_blank>https://www.ietf.org/mail-arch<WBR>ive/web/core/current/m=
sg06280.<WBR>html</A>=20
  - Carsten responded:<U></U><U></U></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'><U></U><U></U></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>&gt; In =
any case,=20
  CON and NON are about message layer semantics, not about application=20
  semantics<U></U><U></U></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>&gt; -- =
you gave=20
  them a meaning they don't have. <U></U><U></U></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'><U></U><U></U></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>By IETF =
94, the=20
  authors were reporting =E2=80=93 =E2=80=9CMost of the Confusion=20
  =
around&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
  CON/NON was resolved=E2=80=9D. <U></U><U></U></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'><U></U><U></U></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>Where =
relevant,=20
  I=E2=80=99ve added clarifications - such as the Appendix related to =
differences in=20
  Observe for reliable transports.<U></U><U></U></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'><U></U><U></U></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>Both =
Carsten and=20
  Hannes could probably offer more context if =
needed.<U></U><U></U></SPAN></P>
  <P class=3DMsoNormal><A=20
  =
name=3Dm_-185370657942848524_m_7105224061284585916_m_-1893619406420712677=
__MailEndCompose><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'><U></U><U></U></SPAN></A>&nbsp;</P><SPAN></SPAN>
  <P class=3DMsoNormal><B><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'>From:</SPAN></B><SPAN=20
  style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'> =
Yoshifumi Nishida=20
  [mailto:<A href=3D"mailto:nishida@sfc.wide.ad.jp"=20
  target=3D_blank>nishida@sfc.wide.ad.jp</A><WBR>] <BR><B>Sent:</B> =
Friday, April=20
  21, 2017 2:08 PM<BR><B>To:</B> Brian Raymor &lt;<A=20
  href=3D"mailto:Brian.Raymor@microsoft.com"=20
  target=3D_blank>Brian.Raymor@microsoft.com</A>&gt;<BR><B>Cc:</B> =
Yoshifumi=20
  Nishida &lt;<A href=3D"mailto:nishida@sfc.wide.ad.jp"=20
  target=3D_blank>nishida@sfc.wide.ad.jp</A>&gt;; <A=20
  href=3D"mailto:tsv-art@ietf.org" target=3D_blank>tsv-art@ietf.org</A>; =
<A=20
  href=3D"mailto:draft-ietf-core-coap-tcp-tls@ietf.org"=20
  target=3D_blank>draft-ietf-core-coap-tcp-tls@i<WBR>etf.org</A>; <A=20
  href=3D"mailto:core@ietf.org" target=3D_blank>core@ietf.org</A>; <A=20
  href=3D"mailto:ietf@ietf.org" =
target=3D_blank>ietf@ietf.org</A><BR><B>Subject:</B>=20
  Re: TSV-ART review of=20
  draft-ietf-core-coap-tcp-tls-0<WBR>7<U></U><U></U></SPAN></P>
  <DIV>
  <DIV class=3Dm_-185370657942848524m_7105224061284585916h5>
  <P class=3DMsoNormal><U></U><U></U>&nbsp;</P>
  <P class=3DMsoNormal>Hi Brian,<U></U><U></U></P>
  <DIV>
  <P class=3DMsoNormal><U></U><U></U>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal>Just in case,<U></U><U></U></P></DIV>
  <DIV>
  <P class=3DMsoNormal>Reliable transports only provide reliability at =
transport=20
  level. It doesn't provide reliability in application protocol level.=20
  <U></U><U></U></P></DIV>
  <DIV>
  <P class=3DMsoNormal><U></U><U></U>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal>RFC7252 has reliability mechanisms in it since it =
uses UDP.=20
  This means it has abilities to check both transport and app level=20
  reliability.<U></U><U></U></P></DIV>
  <DIV>
  <P class=3DMsoNormal>This draft only provides transport level =
reliability and=20
  apps will need to detect app protocol failure by themselves.=20
  <U></U><U></U></P></DIV>
  <DIV>
  <P class=3DMsoNormal>This means 7252 and this draft are not totally =
equivalent=20
  from the viewpoint of applications. <U></U><U></U></P></DIV>
  <DIV>
  <P class=3DMsoNormal><U></U><U></U>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal>I am not saying this is wrong or bad, but I =
believe app=20
  developer should aware this point.<U></U><U></U></P></DIV>
  <DIV>
  <P class=3DMsoNormal>--<U></U><U></U></P></DIV>
  <DIV>
  <P class=3DMsoNormal>Yoshi<U></U><U></U></P></DIV>
  <P class=3DMsoNormal><U></U><U></U>&nbsp;</P>
  <DIV>
  <P class=3DMsoNormal>On Fri, Apr 21, 2017 at 11:15 AM, Brian Raymor =
&lt;<A=20
  href=3D"mailto:Brian.Raymor@microsoft.com"=20
  target=3D_blank>Brian.Raymor@microsoft.com</A>&gt; =
wrote:<U></U><U></U></P>
  <BLOCKQUOTE=20
  style=3D"BORDER-TOP: medium none; BORDER-RIGHT: medium none; =
BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 0in; =
PADDING-LEFT: 6pt; MARGIN-LEFT: 4.8pt; BORDER-LEFT: #cccccc 1pt solid; =
PADDING-RIGHT: 0in; MARGIN-RIGHT: 0in">
    <DIV>
    <DIV>
    <DIV>
    <DIV>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext>Hi=20
    Yoshi,<U></U><U></U></P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext><U></U><U></U>&nbsp;</P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext>&gt;=20
    OK. I also think we should state that the protocol should notify the =
failure=20
    events to applications. <U></U><U></U></P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext>&gt;=20
    Since errors can happen not only in TCP, but also TLS and websocket =
level,=20
    mentioning only TCP close or reset might not <U></U><U></U></P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext>&gt;=20
    be enough.<U></U><U></U></P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext><U></U><U></U>&nbsp;</P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext>After=20
    reviewing with the authors, an additional clarification was appended =
to 3.4=20
    Connection Health - <A=20
    href=3D"https://github.com/core-wg/coap-tcp-tls/pull/140/files"=20
    =
target=3D_blank>https://github.com/core-wg/coa<WBR>p-tcp-tls/pull/140/fil=
es</A><U></U><U></U></P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext><U></U><U></U>&nbsp;</P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext>The=20
    opinion of the authors (and Gengyu WEI=E2=80=99s recent response - =
<A=20
    =
href=3D"https://www.ietf.org/mail-archive/web/core/current/msg08622.html"=
=20
    =
target=3D_blank>https://www.ietf.org/mail-arch<WBR>ive/web/core/current/m=
sg08622.<WBR>html</A>)=20
    is that RFC6455 covers the WebSocket case and does not need to be =
repeated=20
    here.<U></U><U></U></P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext><U></U><U></U>&nbsp;</P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext>&gt;=20
    When we use 7252, I think applications basically don't need to =
implement=20
    timeouts or retry mechanisms as the protocol<U></U><U></U></P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext>&gt;=20
    provides such things. <U></U><U></U></P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext><U></U><U></U>&nbsp;</P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext>RFC7252=20
    provides timeouts and retries because it's implementing a TCP-like=20
    reliability mechanism over UDP - <A=20
    href=3D"https://tools.ietf.org/html/rfc7252#section-2.1"=20
    =
target=3D_blank>https://tools.ietf.org/html/rf<WBR>c7252#section-2.1</A><=
U></U><U></U></P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext><U></U><U></U>&nbsp;</P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext>&gt;=20
    However, when we use this one, it seems applications will need to =
have such=20
    mechanisms. Isn't it a bit confusing? I am thinking =
that<U></U><U></U></P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext>&gt;=20
    there need to be some guidance here.<U></U><U></U></P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext>&gt;=20
    BTW, PONG is one example.<U></U><U></U></P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext><U></U><U></U>&nbsp;</P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext>For=20
    coap-tcp-tls, there are multiple early implementations. This has =
never been=20
    reported as a source of confusion. <U></U><U></U></P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext><U></U><U></U>&nbsp;</P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext>&gt;&gt;=20
    My sense is that we should treat this as an update to RFC7959 based =
on the=20
    original language:<U></U><U></U></P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext>&gt;=20
    I don't have a strong opinion here. Updating 7959 is fine for me if =
it's=20
    clearer to CoAP people.<U></U><U></U></P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext><U></U><U></U>&nbsp;</P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext>I've=20
    merged the change - <A=20
    href=3D"https://github.com/core-wg/coap-tcp-tls/pull/138/files"=20
    =
target=3D_blank>https://github.com/core-wg/coa<WBR>p-tcp-tls/pull/138/fil=
es</A><U></U><U></U></P>
    <P=20
    =
class=3Dm_-185370657942848524m_7105224061284585916m_-1893619406420712677g=
mail-m-3058448815637676647msoplaintext><U></U><U></U>&nbsp;</P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>Thanks =
again for=20
    helping us to improve the quality of the =
draft,</SPAN><U></U><U></U></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: =
#888888'></SPAN><SPAN=20
    style=3D"COLOR: #888888"><U></U><U></U></SPAN>&nbsp;</P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: =
#888888'>=E2=80=A6Brian</SPAN><SPAN=20
    style=3D"COLOR: =
#888888"><U></U><U></U></SPAN></P></DIV></DIV></DIV></DIV></BLOCKQUOTE></=
DIV>
  <DIV>
  <DIV>
  <DIV>
  <P=20
  =
class=3DMsoNormal><U></U><U></U>&nbsp;</P></DIV></DIV></DIV></DIV></DIV><=
/DIV></DIV></BLOCKQUOTE></DIV>
<DIV>&nbsp;</DIV></DIV></DIV></DIV>
<P>
<HR>
_______________________________________________<BR>core mailing=20
list<BR>core@ietf.org<BR>https://www.ietf.org/mailman/listinfo/core<BR></=
DIV></DIV></DIV></BODY></HTML>

------=_NextPart_000_0018_01D2C348.6680E2B0--


From nobody Mon May  1 23:04:42 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 59D9D127241; Mon,  1 May 2017 23:04:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[BAYES_20=-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 YGyYAkrUqBNa; Mon,  1 May 2017 23:04:30 -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 8483E12944F; Mon,  1 May 2017 23:01:31 -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 v4261NeX011017; Tue, 2 May 2017 08:01:23 +0200 (CEST)
Received: from [192.168.217.124] (p5DC7F3A7.dip0.t-ipconnect.de [93.199.243.167]) (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 3wH9dt6zcNzDHJm; Tue,  2 May 2017 08:01:22 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [core] TSV-ART review of draft-ietf-core-coap-tcp-tls-07
From: Carsten Bormann <cabo@tzi.org>
X-Priority: 3
In-Reply-To: <AF06737CE0C34EA88BFFFCA04B89CC95@WeiGengyuPC>
Date: Tue, 2 May 2017 08:01:22 +0200
Cc: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>, Brian Raymor <Brian.Raymor@microsoft.com>, tsv-art@ietf.org, draft-ietf-core-coap-tcp-tls@ietf.org, core@ietf.org, ietf@ietf.org
X-Mao-Original-Outgoing-Id: 515397682.389267-2ea9c47a5b4bedb8e9e5a58c0f6ad50b
Content-Transfer-Encoding: quoted-printable
Message-Id: <76EDF265-DC6F-41DE-B4F4-6BB7F948DC05@tzi.org>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com> <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydcc7k2i5=OSSvvtzU2B1Qa62b3RR3iY0wBfQ2pOYQrkQ@mail.gmail.com> <BY2PR21MB00849DB795086F08F6D7A98A831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249yeS8sZaJcADuz+bYAJa-CXs4v291Fm=adRouO1R=svPDw@mail.gmail.com> <BY2PR21MB008453149ADC1A998FEA56D3831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydRLFpG=yHYvaZvPBiQuW5x=4HZqCZyTAb2HHeDuP+wAA@mail.gmail.com> <AF06737CE0C34EA88BFFFCA04B89CC95@WeiGengyuPC>
To: weigengyu <weigengyu@bupt.edu.cn>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9Vv7Ydd7OTMdy57ed7ObegmB3y4>
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, 02 May 2017 06:04:32 -0000

On May 2, 2017, at 07:31, weigengyu <weigengyu@bupt.edu.cn> wrote:
>=20
> The problem is when the C2C Proxy have got a message form the CoAP/TCP =
side,=20
> how the Proxy make a decision to delivery CON or NON message carrying =
CoAP over UDP?=20

The question is not very different from the UDP to UDP proxying case.
If a request came in via a UDP CON (which is the equivalent of using a =
reliable transport protocol), should the proxy use CON or NON for the =
forwarded request?

I=E2=80=99d say, in both cases, CON should be the default way of =
forwarding the reliable request.
But there may be specific cases where a NON may be appropriate =E2=80=94 =
CoAP does not provide the client with a way to control the proxy here.

Is that a problem?  Tell me more about your use case.

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


From nobody Mon May  1 23:23:02 2017
Return-Path: <weigengyu@bupt.edu.cn>
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 7F168128DE5 for <ietf@ietfa.amsl.com>; Mon,  1 May 2017 23:23:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.237
X-Spam-Level: *
X-Spam-Status: No, score=1.237 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, STOX_REPLY_TYPE=0.439] 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 oniok3ELdiSR for <ietf@ietfa.amsl.com>; Mon,  1 May 2017 23:22:59 -0700 (PDT)
Received: from mx1.bupt.edu.cn (mx1.bupt.edu.cn [211.68.68.2]) by ietfa.amsl.com (Postfix) with ESMTP id 97C0D12EA74 for <ietf@ietf.org>; Mon,  1 May 2017 23:20:19 -0700 (PDT)
Received: from WeiGengyuPC (unknown [114.255.40.42]) by mx1.bupt.edu.cn (AnyMacro(G7)) with ESMTPA id B08E519F380; Tue,  2 May 2017 14:11:34 +0800 (HKT)
Message-ID: <A257B9FAE62943A6BB540A8F3D457BDA@WeiGengyuPC>
From: "weigengyu" <weigengyu@bupt.edu.cn>
To: "Carsten Bormann" <cabo@tzi.org>
Cc: "Yoshifumi Nishida" <nishida@sfc.wide.ad.jp>, "Brian Raymor" <Brian.Raymor@microsoft.com>, <tsv-art@ietf.org>, <draft-ietf-core-coap-tcp-tls@ietf.org>, <core@ietf.org>, <ietf@ietf.org>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com> <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydcc7k2i5=OSSvvtzU2B1Qa62b3RR3iY0wBfQ2pOYQrkQ@mail.gmail.com> <BY2PR21MB00849DB795086F08F6D7A98A831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249yeS8sZaJcADuz+bYAJa-CXs4v291Fm=adRouO1R=svPDw@mail.gmail.com> <BY2PR21MB008453149ADC1A998FEA56D3831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydRLFpG=yHYvaZvPBiQuW5x=4HZqCZyTAb2HHeDuP+wAA@mail.gmail.com> <AF06737CE0C34EA88BFFFCA04B89CC95@WeiGengyuPC> <76EDF265-DC6F-41DE-B4F4-6BB7F948DC05@tzi.org>
In-Reply-To: <76EDF265-DC6F-41DE-B4F4-6BB7F948DC05@tzi.org>
Subject: Re: [core] TSV-ART review of draft-ietf-core-coap-tcp-tls-07
Date: Tue, 2 May 2017 14:11:33 +0800
Organization: BUPT
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3528.331
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YP1CK_mR5j9evj0iuJT6Bd5mAeY>
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, 02 May 2017 06:23:00 -0000

Hi，

> The question is not very different from the UDP to UDP proxying case.
Something is different.

> If a request came in via a UDP CON (which is the equivalent of using a 
> reliable transport protocol),
> should the proxy use CON or NON for the forwarded request?
If it keeps the semantics end-to-end,  the proxy just forwards the message.
If it has the semantics hop-by-hop, the proxy can decide what type of 
message to transfer.

Regards,

Gengyu WEI
Network Technology Center
School of Computer
Beijing University of Posts and Telecommunications
-----原始邮件----- 
From: Carsten Bormann
Sent: Tuesday, May 02, 2017 2:01 PM
To: weigengyu
Cc: Yoshifumi Nishida ; Brian Raymor ; tsv-art@ietf.org ; 
draft-ietf-core-coap-tcp-tls@ietf.org ; core@ietf.org ; ietf@ietf.org
Subject: Re: [core] TSV-ART review of draft-ietf-core-coap-tcp-tls-07

On May 2, 2017, at 07:31, weigengyu <weigengyu@bupt.edu.cn> wrote:
>
> The problem is when the C2C Proxy have got a message form the CoAP/TCP 
> side,
> how the Proxy make a decision to delivery CON or NON message carrying CoAP 
> over UDP?

The question is not very different from the UDP to UDP proxying case.
If a request came in via a UDP CON (which is the equivalent of using a 
reliable transport protocol), should the proxy use CON or NON for the 
forwarded request?

I’d say, in both cases, CON should be the default way of forwarding the 
reliable request.
But there may be specific cases where a NON may be appropriate — CoAP does 
not provide the client with a way to control the proxy here.

Is that a problem?  Tell me more about your use case.

Grüße, Carsten


From nobody Tue May  2 02:43:49 2017
Return-Path: <ietf@trammell.ch>
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 A222F131604; Tue,  2 May 2017 02:43:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_40=-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 yf7ez3IMI_9K; Tue,  2 May 2017 02:43:46 -0700 (PDT)
Received: from capri.iway.ch (capri.iway.ch [212.25.24.45]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A61BD131464; Tue,  2 May 2017 02:39:47 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 7E986340E46; Tue,  2 May 2017 11:39:45 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/7408.2348);  Tue,  2 May 2017 11:39:45 +0200 (CEST)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Tue,  2 May 2017 11:39:45 +0200 (CEST)
Received: from [195.176.111.24] (account ietf@trammell.ch HELO public-docking-cx-1383.ethz.ch) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.14) with ESMTPSA id 16213131; Tue, 02 May 2017 11:39:45 +0200
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_5BC48B55-A6BC-4357-96E6-5800076B3B4F"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Brian Trammell (IETF) <ietf@trammell.ch>
In-Reply-To: <m21ss80xjm.wl-randy@psg.com>
Date: Tue, 2 May 2017 11:39:44 +0200
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion Mailing List <ietf@ietf.org>, IESG <iesg@ietf.org>
Message-Id: <EDF21A00-1446-492C-A7B7-1A485704717C@trammell.ch>
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net> <m21ss80xjm.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fPWcTQ4XANVjrVIZDcA1V27fIw0>
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, 02 May 2017 09:43:49 -0000

--Apple-Mail=_5BC48B55-A6BC-4357-96E6-5800076B3B4F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

you rang? :)

I'll refrain from wider comment on the current revision of the document; =
I think the authors continue to receive good feedback on its scope and =
structure, and I'll have a look during next last call.

Section 2.2 seems to be lumping together three things which aren't =
necessarily related: longitudinal studies of Internet traffic for =
operational and academic purposes, traffic matrix generation (a specific =
operational measurement purpose which has received a good deal of =
academic attention), and application classification / aggregation by =
application-layer semantics. The first two of these do use similar =
inputs (e.g. IPFIX data aggregated to the per-layer-4-flow level at the =
finest), but require application-layer data only if they additionally =
classify or aggregate traffic at the application layer.

For example, a simple traffic matrix might use IP packet and octet =
counts aggregated by prefix, and requires only IP-layer data to =
generate. A matrix focused on isolating transport-layer performance =
problems would need to estimate TCP parameters for each flow or group of =
flows, using TCP headers (typically TCP flags, sequence and =
acknowledgment numbers, as well as timestamps if available) in addition =
to IP headers to generate loss, retransmission, and RTT statistics. A =
more detailed matrix still could classify traffic as belonging to a =
specific application through application-layer header and payload =
inspection.

It's true that each layer you encrypt reduces the utility of passive =
measurement to determine certain things. For example, a study trying to =
estimate the amount of streaming video over a given link can do this =
much more easily and with higher fidelity by inspecting HTTP headers =
than it can by applying heuristics to the time-series of interpacket =
times and packet sizes. It's true that the inferences made in a =
measurement will have to get more clever as the amount of observable =
data decreases, and those inferences may be so weak as to make a =
particular measurement useless. But it's not true that these studies =
always need application-layer headers or payload, or even transport =
layer headers for the simplest matrices.

One note on the text here: "CAIDA" isn't one data set, they run many =
projects, many of which are active (e.g. Archipelago, which does various =
topology measurements); the best-known passive facility, the CAIDA =
darkspace telescope, surveys background radiation, and mainly catches =
backscatter. The application-layer semantics of which are either =
necessarily in cleartext (because there exists no cryptographic context =
to encrypt a backscatter reply to garbage) or irrelevant, so increasing =
encryption shouldn't cause a problem there.

Cheers,

Brian

> On 02 May 2017, at 05:04, Randy Bush <randy@psg.com> wrote:
>=20
>> For example, Section 2.2 talks about the importance of passive
>> monitoring for traffic surveys, but fails to discuss alternative =
means
>=20
> possibly our friends from z=C3=BCrich have some ideas here
>=20
> randy
>=20


--Apple-Mail=_5BC48B55-A6BC-4357-96E6-5800076B3B4F
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIcBAEBCgAGBQJZCFPgAAoJEIoSt78L6kajzmsP/A4ZCHZs0pzSoMDXSCNupr7V
Zi+0NVPtmxIFydwHm/G1zJ6MY9Be4O/jqvdWnypiC80AC+z8Fbwnb5mNBQ4tILhz
nDbc7T2oRYbukg1Tt2sF/5ZIwxOrNxd1jNeeURHWe/Y/qrhjyQufzzdBYFVOHMQL
vsVjk7GywJ3KXUZ6yfIVWKU23uusSKvDNa83uVCNuTvK4NsRAv2DEPZDZNmy+AZJ
BaxC+eeHI999cFqZmTVnNjYYc0BZXrKlSJCJ5mNX+Ispvt67ZZ7yWD8X07LDEKCQ
qFVnDm+eBB09KCWFSS621ENTg6jiyt/+H919tDdCI5/xhfDlyovPEQW/Wdq1oBrY
xe4oflM/Sh3cMq2cxwMrbCAfByTxWOt7z/hKMyh4M6fS6EdFlApR7WQ+XOLjWcPL
A2xvD9hzURaTXfPu46cSabToBy0tibLTBlj8CGslSixWRB8PJmaEiAO1+6k2sSOA
8yRoHgxNA7bHLAgmxwnB8dID7ML5nHv3aYf2lUVki62zaPX5otOfngd2RtJqCI+9
olCXR5l917phPBa2ET0Qzo5zV0WrCRNd11WX/R/3gbPMqHkvGpZODSi8AinBnmm1
GUmPVK9kHLpSXpgr4RD5Y643srmqwrVJ6lj/UkomdhxXRHx4+tLFI/I4oVxgGez9
+U7a15s7UGDC64Vm3VOr
=aipH
-----END PGP SIGNATURE-----

--Apple-Mail=_5BC48B55-A6BC-4357-96E6-5800076B3B4F--


From nobody Tue May  2 03:36:15 2017
Return-Path: <ietf@trammell.ch>
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 AB658126BFD; Tue,  2 May 2017 03:36:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8] autolearn=ham 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 aAigLu78cBl5; Tue,  2 May 2017 03:36:11 -0700 (PDT)
Received: from capri.iway.ch (capri.iway.ch [IPv6:2001:8e0:40:325::45]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A97F1315C5; Tue,  2 May 2017 03:32:17 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 3E36D34053A; Tue,  2 May 2017 12:32:15 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/7408.13995);  Tue,  2 May 2017 12:32:14 +0200 (CEST)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Tue,  2 May 2017 12:32:14 +0200 (CEST)
Received: from [195.176.111.24] (account ietf@trammell.ch HELO public-docking-cx-1383.ethz.ch) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.14) with ESMTPSA id 16221086; Tue, 02 May 2017 12:32:14 +0200
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_117FFD57-6E25-4954-8304-95B9F8A4DAAF"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Brian Trammell (IETF) <ietf@trammell.ch>
In-Reply-To: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net>
Date: Tue, 2 May 2017 12:32:13 +0200
Cc: IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
Message-Id: <21A01174-4FB6-4F8C-AA3D-DCF6D1FEBA01@trammell.ch>
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4ibVqMUj8Q3nx0LN3R8aEf7X0Jw>
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, 02 May 2017 10:36:14 -0000

--Apple-Mail=_117FFD57-6E25-4954-8304-95B9F8A4DAAF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

hi Mark,

...hm, apparently I *will* comment on the structure of the current =
document, inline below...

> On 01 May 2017, at 05:45, Mark Nottingham <mnot@mnot.net> wrote:
>=20
> Overall, this document reads as if it was originally written to =
highlight the downsides of increased use of encryption, and then =
rewritten to be more neutral in tone. Unfortunately, some of the =
original intent posited there still seeps through.
>=20
> In doing so, it often fails to convey that there are any options other =
than "this has to be done by the network." I know that this has been =
cast as a survey of potential impacts, and therefore doesn't necessary =
need to enumerate alternatives, but the way that it's written could =
easily lead a reader to think that there aren't alternatives. It also is =
odd that alternatives are not enumerated when they're often well-known, =
and the really interesting issues are in the tradeoffs between doing =
something in the network (i.e., as a third party) vs. by one of the =
endpoints (a first party to communication) or their delegates.

I think the statement of alternatives is a different document, though; =
it's one that needs to be written, yes, but the division of problem =
space and solution space is IMO useful here. I see this as the analogous =
to the split between RFC 7624 and =
draft-iab-privsec-confidentiality-mitigations. It was quite useful in =
having the former as a complete statement of what we think the problem =
is (in more detail that 7258's declaration) before recommending =
solutions. And, indeed, it's entirely possible that an IETF consensus =
statement on the solutions available for a given problem is "we have =
decided that this is not actually a problem we should design for", as in =
RFC 2804.

Cheers,

Brian

--Apple-Mail=_117FFD57-6E25-4954-8304-95B9F8A4DAAF
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIcBAEBCgAGBQJZCGAtAAoJEIoSt78L6kajl+IP/jlxfsFJYGcL7wtQ5tp9n8Dg
a3s/GxwxViSsPzz4dvhFUTWL+i4hXQLz1CwFpR9isTbbitU3vwCwL/ioakWMTRqO
3wsmjEwpsWID7gq4zTjcO+faZOToZNpv9bgCSAcIAKAqueStPgNN4JyWx+5K95R4
81ZyJneuznXc/d85/ZYAqT6tq0Uzf/BQqMNc9tTgUn7T9XIaDqTidb/uY/5n+OhT
HUJq/Ijhqw6bapFqv985Tae9sq7KNgF9NO8wr7n72mB36yPYKXOaJJMPq2JyA41P
w7Mn1FT5AtDywC61ve47+NI/FwyII5zfMvv9XjY/Iw2e6LvfHSYt3s7n0uAGHE5B
kYYNIHrUmJixcCs02YO3GK/F+HqkD8fZJg3JQG+BT/IJLdSAShUP9RsIzlJ9WMpX
0hbzxRWKzHt7bPPIk0lFOX2+IG+3k6ZeiBcUx71GSau0qWu4Vq3KDWq7aFNjHP3V
buglw6rOF1MdwXxob4i6tfkKesMEgW60pgVMRe3ihYZ0cgOIwfxboTeRdzoTqVFN
reYrR1+JlHk+6XDBqDkHhQtnb5eStGKs7FbG9zhgy6CzTOhlNVgJa6Y8+qUV5w5Y
zXE7CVktX9aQRuxayDfvPUve6fBK28eiXfoXFVIAYoBVWaoWfAh/wqlj/mrW3Gr6
g/Fv304rs/G+PtlAFU6S
=K92R
-----END PGP SIGNATURE-----

--Apple-Mail=_117FFD57-6E25-4954-8304-95B9F8A4DAAF--


From nobody Tue May  2 06:31:10 2017
Return-Path: <jclarke@cisco.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 B73D3128796; Tue,  2 May 2017 06:30:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joe Clarke <jclarke@cisco.com>
To: <ops-dir@ietf.org>
Cc: v6ops@ietf.org, ietf@ietf.org, draft-ietf-v6ops-v4v6-xlat-prefix.all@ietf.org
Subject: Opsdir early review of draft-ietf-v6ops-v4v6-xlat-prefix-00
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149373185172.9923.9255526962045750289@ietfa.amsl.com>
Date: Tue, 02 May 2017 06:30:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yvbBTVJuCD-kYZEi_umUzzEOEkU>
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, 02 May 2017 13:30:52 -0000

Reviewer: Joe Clarke
Review result: Has Issues

Hello, Tore and Fred.  Thanks for requesting an OPSDIR review of this
draft.  Up front, I'd like to say that I enjoyed hearing the
discussion on why certain decisions were made, especially with concern
to ease of use for operators and compatibility with other established
translation approaches.   That said, I have a few minor
issues/questions and nits concerning this draft.  I think they will be
easy to address.

ISSUES/QUESTIONS:

You set out to define WKP as _the_ well-known prefix.  For the most
part you adhere to this language in the draft.  However, in section 3,
you state (highlighting added by me):

Also, because the WKP is a /96, an operator preferring to use _a WKP_
over an NSP can only do so for only one of his IPv4/IPv6 translation
mechanisms.  All others must necessarily use an NSP.

And then in section 5:

When 64:ff9b:1::/48 or a more-specific prefix is used with the
[RFC6052] algorithm, it is considered to be a Network-Specific
Prefix.

I believe what you're saying is that while you define 64:ff9b:1::/48
as a WKP in _this_ draft, respective to RFC6052, it is an NSP. 
However, the combination of text in both sections was a bit confusing
to me, and perhaps it would be useful to clarify your use of terms.

===

In Section 3, you state:

Since the WKP 64:ff9b::/96 was reserved by [RFC6052], several new
IPv4/IPv6 translation mechanisms have been defined by the IETF

I think it would be useful to mention some of these new translation
mechanisms as non-normative references, and if need be, show an
example of interoperability.

NITS:

In your Abstract, you mention RFC6890, but this does not appear to be
an xref to it, and it should be.

===

In Section 4.1 you state:

OLD:
The second criterion is that the prefix length chosen is is a
multiple of 16.  This ensures the prefix ends on a colon boundary
when representing it in text, easing operator interaction with it.

NEW:
The second criterion is that the prefix length chosen is a
multiple of 16.  This ensures the prefix ends on a colon boundary
when representing it in text, easing operator interaction with it.

(Removed a redundant "is".)

===

In Section 4.1 again:

OLD:
The [RFC6052] algorithm specifies IPv4/IPv6 translation prefixes as
short as /32.  In order to facilitate multiple instances of
translation mechanisms using /32s, while at the same time aligning on
a 16-bit boundary, it would be necessary to reserve a /16.  Doing so
was however considered as too wasteful by the IPv6 Operations working
group.

NEW:
The [RFC6052] algorithm specifies IPv4/IPv6 translation prefixes as
short as /32.  In order to facilitate multiple instances of
translation mechanisms using /32s, while at the same time aligning on
a 16-bit boundary, it would be necessary to reserve a /16.  Doing so,
however, was considered too wasteful by the IPv6 Operations working
group.

===

In Section 6:

OLD:
The Stateless IP/ICMP Translation algorithm [RFC7915] is one well-
known algorithm that can operate in a checksum-neutral manner, when
using the [RFC6052] algorithm for all of its address translations.
However, in order to attain checksum neutrality is imperative that
the translation prefix is chosen carefully.  Specifically, in order
for a 96-bit [RFC6052] prefix to be checksum neutral, all the six
16-bit words in the prefix must add up to a multiple of 0xffff.

NEW:
The Stateless IP/ICMP Translation algorithm [RFC7915] is one well-
known algorithm that can operate in a checksum-neutral manner, when
using the [RFC6052] algorithm for all of its address translations.
However, in order to attain checksum neutrality it is imperative that
the translation prefix is chosen carefully.  Specifically, in order
for a 96-bit [RFC6052] prefix to be checksum neutral, all the six
16-bit words in the prefix must add up to a multiple of 0xffff.

(Added a missing "it".)

===


From nobody Tue May  2 07:50:52 2017
Return-Path: <alissa@cooperw.in>
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 8D9E6129BA2 for <ietf@ietfa.amsl.com>; Tue,  2 May 2017 07:50:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.021
X-Spam-Level: 
X-Spam-Status: No, score=-0.021 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_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=cooperw.in header.b=OP095F+v; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=W54h41FG
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nqd82bf_FTfc for <ietf@ietfa.amsl.com>; Tue,  2 May 2017 07:50:49 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3030131683 for <ietf@ietf.org>; Tue,  2 May 2017 07:46:32 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 3DE8C207E2 for <ietf@ietf.org>; Tue,  2 May 2017 10:46:32 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Tue, 02 May 2017 10:46:32 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:reply-to:subject:to:x-me-sender:x-me-sender :x-sasl-enc:x-sasl-enc; s=fm1; bh=fRQh2daO+TdUlKqygjQunEzq23IfA9 ggnFZzUR2Eqt4=; b=OP095F+vDIjFAXWrKjQz7c+8uTmYyyu10shYnPCoLWHnTd kC8EPTvOLJtAQpquJGzUuTdZ5HKgEX2cOe88D9u2o6rI5SkdrK8HY/sxHSdFPl2X PmSkD/19Meky5D7gUbeHpUG9AHhrUNSvLOsB8kJ0H9DUrYjflutEObYASIWOkVCn 1xlE1c+AgzoeZRj4/DwWpdbWkmymeC0Z3xsl7xyxn9RlTXcFXOa1qQEVJZgpS0Lu QBn2ozMR4Unnj0v/vNfjf8qdYV6dXlAZcUgb8dhB/YgkNroP/FYQAoVdseOuzIDM a6Mj5gGi5QYYdlZk6Uyyg9tSqAicjVO7cpitn5YQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:reply-to:subject:to :x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=fRQh2d aO+TdUlKqygjQunEzq23IfA9ggnFZzUR2Eqt4=; b=W54h41FGls8oU+47da+1f8 aJtYpNigdjMIGC/3YnRW/B+mtaBw8NnqRaYCG4zDlWxdCSYpQLjmZJOZiXBX4iqn OR+XGpzPLS+vKn7LYhyXkeLEKtACbf5gIwiMhqplvxklnDC2ZpMm0x4MHaw0j0ge GpsWlbAYeYofVHrQ7LLFXr1NvhNr8/ttK3qbrTCx9cK0HvXcv+ZikAP5ExVPDD/+ yDrfDYqEcbiXZovVliKO1MzJ5f3lghZePW43gN3MphRzKmXDpuilzlUiCidSI1P8 lovJ+EwbQM4PtWhO84+/2eseG7VFg1s3SFY0SuWl9/yGqX2JVomocA85HG2BT2rQ ==
X-ME-Sender: <xms:yJsIWbghFt57NHcF_mQFLqskPGWKUcvgLERZ0e_eqK_mkUq3El6fbQ>
X-Sasl-enc: D17jDiip2DsCfamOFeEfdlOUYxUreAG3copzd0QOyLWp 1493736392
Received: from dhcp-10-150-9-186.cisco.com (unknown [173.38.117.77]) by mail.messagingengine.com (Postfix) with ESMTPA id EEEE42475F for <ietf@ietf.org>; Tue,  2 May 2017 10:46:31 -0400 (EDT)
From: Alissa Cooper <alissa@cooperw.in>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Reply-To: IAOC <iaoc@ietf.org>
Subject: Feedback on meeting dates
Date: Tue, 2 May 2017 10:46:31 -0400
Message-Id: <A3093E7C-5B69-458D-854B-3E2B1AF3B726@cooperw.in>
To: IETF Discussion <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aaGWFpxPyLptVsKxvgSRNI9Kgvc>
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, 02 May 2017 14:50:50 -0000

Typically, as the IAOC is evaluating dates for future IETF meetings 3-5 =
years in advance, we send a note to the community listing selected =
meeting dates to seek feedback about potential conflicts with the dates. =
As the IAOC evaluates options for IETF 102 (currently scheduled for July =
22-27, 2018 in San Francisco), some of the potential options include =
moving the meeting to the week prior (July 15-20) or the week after =
(July 29-Aug 3) at a North American location outside of the US. So =
we=E2=80=99re sending this note to solicit feedback about potential =
conflicts with those dates.

We are aware that the July 15-20, 2018 dates conflict with 3GPP SA3-LI =
and ANSI T10 meetings. If those conflicts would cause problems for you, =
or if you are aware of other meetings or events that conflict with July =
15-20 or July 29-Aug 3, 2018 and that would have a significant impact on =
participation at IETF 102 were it to be re-scheduled, please send that =
feedback to iaoc@ietf.org, preferably by May 9, 2018.

As Leslie previously indicated, the IAOC is still reviewing all options =
for IETF 102, including both moving it and not moving it. Your timely =
feedback about date conflicts is appreciated as an input into that =
review process.

Thanks,
Alissa Cooper
IETF Chair=


From nobody Tue May  2 08:04:39 2017
Return-Path: <fredbaker.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 D8AB0129483; Tue,  2 May 2017 08:04: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 QkN7nOtP5dvh; Tue,  2 May 2017 08:04:19 -0700 (PDT)
Received: from mail-wr0-x244.google.com (mail-wr0-x244.google.com [IPv6:2a00:1450:400c:c0c::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6212C129C48; Tue,  2 May 2017 08:00:34 -0700 (PDT)
Received: by mail-wr0-x244.google.com with SMTP id w50so18018341wrc.0; Tue, 02 May 2017 08:00:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2wmV8QaEM0maQQlHLupXU4ebkY8R0aEYVYkyBINHq50=; b=UIF6XQnFgEDXCIDEAt81zYZOcDvPAUK031rA2K0aR4KcSLa/O1qVim25aa0U6mBXgC 5EHriJOsJBABc2vA9cbkx4L0rIthOzuTQ65yDeK40mklbfU+Ul4smYndH5jiaLy0tpb0 Mei/agJavBPWaLuSfK/kXQYUTkUPa2nBED+X+8PrMgfq39xJgdEvjPgC8CwPrX4fuCCH txWWaHc6NniZkR44z5W+67runHF5l5Q9JDvI81Sr483faeziB+apDyGLF9uah2X+Cd3p vV0IzuPlQi59sVXDfaTbrttNggMXWeQGdIjhNSKCM8cFPwIqp2uLzapXXxUnbm0hi6XP z5oQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2wmV8QaEM0maQQlHLupXU4ebkY8R0aEYVYkyBINHq50=; b=o3jDeq/10snfU77Z6YMmXsi8G7YXJvRhmeFLkamFZcm3r9eIsKHTN7XghqW69htPy4 Jc3nkjZ1ApbmigNN3tM5UJg6GMn3+MTKL/+l25ruHhGiI86iSrd5DM7cjQrr5C7kasc2 WL6ApB6nuO+1/d6BmbFXMltHMaGrS5IV0yf+WXP3WIbHhf6XCwt+jsBPFNvOnP4Tipbx YGTYsRxrbbqW+fZr7KENWnc/8uqmB1KPNnmeK8g3sBxjTMDaiIhMVBPX+/0ZDcNjoAgZ wzzULp8sqjNOahDGWzKsCOF3415+QPmg37ZW92FQJak43c6qygEaohUFgIYJfStLiZ2Z 7Osg==
X-Gm-Message-State: AN3rC/47i6ip+I3BklqeDYKZwC1AAo7pzHbYWtNESuhIyMb5y0NTckKI mfmUFbNvAbs/br7kYlE=
X-Received: by 10.223.170.195 with SMTP id i3mr22855918wrc.49.1493737232886; Tue, 02 May 2017 08:00:32 -0700 (PDT)
Received: from 135.66.20.149.in-addr.arpa (135.66.20.149.in-addr.arpa. [149.20.66.135]) by smtp.gmail.com with ESMTPSA id i199sm1224083wmf.33.2017.05.02.08.00.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 May 2017 08:00:31 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Opsdir early review of draft-ietf-v6ops-v4v6-xlat-prefix-00
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <149373185172.9923.9255526962045750289@ietfa.amsl.com>
Date: Tue, 2 May 2017 11:00:27 -0400
Cc: ops-dir@ietf.org, v6ops@ietf.org, ietf@ietf.org, draft-ietf-v6ops-v4v6-xlat-prefix.all@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <7789CECA-165C-417F-B485-03A154327AC1@gmail.com>
References: <149373185172.9923.9255526962045750289@ietfa.amsl.com>
To: Joe Clarke <jclarke@cisco.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-I57qF-9dpiQXkhWwQlIPi5k1k4>
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, 02 May 2017 15:04:21 -0000

Thanks!

> On May 2, 2017, at 9:30 AM, Joe Clarke <jclarke@cisco.com> wrote:
> 
> Reviewer: Joe Clarke
> Review result: Has Issues
> 
> Hello, Tore and Fred.  Thanks for requesting an OPSDIR review of this
> draft.  Up front, I'd like to say that I enjoyed hearing the
> discussion on why certain decisions were made, especially with concern
> to ease of use for operators and compatibility with other established
> translation approaches.   That said, I have a few minor
> issues/questions and nits concerning this draft.  I think they will be
> easy to address.
> 
> ISSUES/QUESTIONS:
> 
> You set out to define WKP as _the_ well-known prefix.  For the most
> part you adhere to this language in the draft.  However, in section 3,
> you state (highlighting added by me):
> 
> Also, because the WKP is a /96, an operator preferring to use _a WKP_
> over an NSP can only do so for only one of his IPv4/IPv6 translation
> mechanisms.  All others must necessarily use an NSP.
> 
> And then in section 5:
> 
> When 64:ff9b:1::/48 or a more-specific prefix is used with the
> [RFC6052] algorithm, it is considered to be a Network-Specific
> Prefix.
> 
> I believe what you're saying is that while you define 64:ff9b:1::/48
> as a WKP in _this_ draft, respective to RFC6052, it is an NSP. 
> However, the combination of text in both sections was a bit confusing
> to me, and perhaps it would be useful to clarify your use of terms.
> 
> ===
> 
> In Section 3, you state:
> 
> Since the WKP 64:ff9b::/96 was reserved by [RFC6052], several new
> IPv4/IPv6 translation mechanisms have been defined by the IETF
> 
> I think it would be useful to mention some of these new translation
> mechanisms as non-normative references, and if need be, show an
> example of interoperability.
> 
> NITS:
> 
> In your Abstract, you mention RFC6890, but this does not appear to be
> an xref to it, and it should be.
> 
> ===
> 
> In Section 4.1 you state:
> 
> OLD:
> The second criterion is that the prefix length chosen is is a
> multiple of 16.  This ensures the prefix ends on a colon boundary
> when representing it in text, easing operator interaction with it.
> 
> NEW:
> The second criterion is that the prefix length chosen is a
> multiple of 16.  This ensures the prefix ends on a colon boundary
> when representing it in text, easing operator interaction with it.
> 
> (Removed a redundant "is".)
> 
> ===
> 
> In Section 4.1 again:
> 
> OLD:
> The [RFC6052] algorithm specifies IPv4/IPv6 translation prefixes as
> short as /32.  In order to facilitate multiple instances of
> translation mechanisms using /32s, while at the same time aligning on
> a 16-bit boundary, it would be necessary to reserve a /16.  Doing so
> was however considered as too wasteful by the IPv6 Operations working
> group.
> 
> NEW:
> The [RFC6052] algorithm specifies IPv4/IPv6 translation prefixes as
> short as /32.  In order to facilitate multiple instances of
> translation mechanisms using /32s, while at the same time aligning on
> a 16-bit boundary, it would be necessary to reserve a /16.  Doing so,
> however, was considered too wasteful by the IPv6 Operations working
> group.
> 
> ===
> 
> In Section 6:
> 
> OLD:
> The Stateless IP/ICMP Translation algorithm [RFC7915] is one well-
> known algorithm that can operate in a checksum-neutral manner, when
> using the [RFC6052] algorithm for all of its address translations.
> However, in order to attain checksum neutrality is imperative that
> the translation prefix is chosen carefully.  Specifically, in order
> for a 96-bit [RFC6052] prefix to be checksum neutral, all the six
> 16-bit words in the prefix must add up to a multiple of 0xffff.
> 
> NEW:
> The Stateless IP/ICMP Translation algorithm [RFC7915] is one well-
> known algorithm that can operate in a checksum-neutral manner, when
> using the [RFC6052] algorithm for all of its address translations.
> However, in order to attain checksum neutrality it is imperative that
> the translation prefix is chosen carefully.  Specifically, in order
> for a 96-bit [RFC6052] prefix to be checksum neutral, all the six
> 16-bit words in the prefix must add up to a multiple of 0xffff.
> 
> (Added a missing "it".)
> 
> ===
> 


From nobody Tue May  2 08:43:27 2017
Return-Path: <farmer@umn.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 108C5129BFC for <ietf@ietfa.amsl.com>; Tue,  2 May 2017 08:43:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.801
X-Spam-Level: 
X-Spam-Status: No, score=-3.801 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_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 79j8X0ZsyjcT for <ietf@ietfa.amsl.com>; Tue,  2 May 2017 08:43:18 -0700 (PDT)
Received: from mta-p5.oit.umn.edu (mta-p5.oit.umn.edu [134.84.196.205]) (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 9E90A129C2A for <ietf@ietf.org>; Tue,  2 May 2017 08:40:25 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p5.oit.umn.edu (Postfix) with ESMTP id 2989379 for <ietf@ietf.org>; Tue,  2 May 2017 15:40:25 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p5.oit.umn.edu ([127.0.0.1]) by localhost (mta-p5.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7zpAZdAFPARi for <ietf@ietf.org>; Tue,  2 May 2017 10:40:24 -0500 (CDT)
Received: from mail-ua0-f197.google.com (mail-ua0-f197.google.com [209.85.217.197]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p5.oit.umn.edu (Postfix) with ESMTPS id D568B18B for <ietf@ietf.org>; Tue,  2 May 2017 10:40:23 -0500 (CDT)
Received: by mail-ua0-f197.google.com with SMTP id i6so27677518uag.22 for <ietf@ietf.org>; Tue, 02 May 2017 08:40:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=mKDR4TsVoAf5yD6T1Wnu1N90c7rw1rJXMSzEYqzFvWQ=; b=P33IFbt3gm/TDFYFRFy8Gtrhern9a7HyCKyyOVFu+j8W1is5Pj0Wq6kTO5Yf3klSlP uJyZAlN2UjU2bohS+E0MAhIFDoXuvnWwYPoL4Vrjz7ARuWMWiX+1SYRGAuod9O8wZatN S2E0DcLDp/0caRqrb5u9QEdjICZM2x13ZHwgi6jDUtFpxfAocZqrunRHT+VXuGiPuDjM PNnhC9OOmZSVZhbJmvtLdti5AODzPpPZsyFqLX5aDew4Q7qwuDGXNkIGW/Lh4+/e0mzq JrvZiDUF0WIB3kV2M0VVeASXRsyanBZ7F31aUx+wgGmUlPcS0ITtt3pE8cD0yAR6tKyB henw==
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=mKDR4TsVoAf5yD6T1Wnu1N90c7rw1rJXMSzEYqzFvWQ=; b=rLOpJEq8EP/iYZteQTd3jUA+7G8lCjOf/APGFW47SCxEzn5x3zfgKfnkjKxQOgUXnA 3bBFkehLWveK6KVaNS+JDkCSqFnUj+rRft3A3tZGTSwLHSAgCQ+1ChNmBfVPwGGiifvC LE76hUTYHMV0khP21Wm5pIhredcXO/GDbOB/drYz4/N3N51/qmSop2784GU0GUANWb8f hULwyGtedSQLNsAcAMCRtTe5DaPfGhqM+w4oJSVjVHZteXkHoHwbWH8T4Wpur2B7b3+Q ZQa6Q2KAjuT82eXxjxfqThO2NybPrikI/HdPmURauIG527gjTxtUXos4TPh+i2WmOc4r hj1Q==
X-Gm-Message-State: AN3rC/65taSiH1lUDzwUl92V4defgjPCPAqdMky9RIeMzRHBPEZLR/fo altcwTFDqGtezqDgW9k/Qn/qINF5wV4G4Bdq+oUUfZBuAcliiCjoTnIuNMNMpBvZAF77rTrB52r WUzZ4gADHnbYI3rs=
X-Received: by 10.159.48.8 with SMTP id h8mr16594679uab.142.1493739623336; Tue, 02 May 2017 08:40:23 -0700 (PDT)
X-Received: by 10.159.48.8 with SMTP id h8mr16594660uab.142.1493739622956; Tue, 02 May 2017 08:40:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.44.69 with HTTP; Tue, 2 May 2017 08:40:22 -0700 (PDT)
In-Reply-To: <7789CECA-165C-417F-B485-03A154327AC1@gmail.com>
References: <149373185172.9923.9255526962045750289@ietfa.amsl.com> <7789CECA-165C-417F-B485-03A154327AC1@gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Tue, 2 May 2017 10:40:22 -0500
Message-ID: <CAN-Dau0dVSL7cAZs2YWHpeU8rpU76bn00-7XiS2Rj+eOAOCS4A@mail.gmail.com>
Subject: Re: [v6ops] Opsdir early review of draft-ietf-v6ops-v4v6-xlat-prefix-00
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: V6 Ops List <v6ops@ietf.org>, draft-ietf-v6ops-v4v6-xlat-prefix.all@ietf.org,  IETF-Discussion Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=f403045dce5e9d1e9c054e8c5bd4
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/omd4xUC_yUTOoOWGgfnBo7rvaY0>
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, 02 May 2017 15:43:22 -0000

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

Prompted by this review, I reread the document and found what I think are a
couple additional typos.

Section 4.2, Prefix Value, compares two options: 64:ff9a:ffff:ffff::/48 and
64:ff9b:1::/48. However in the fifth paragraph of the section, I believe
there are two errant references to 64:ff9b:1::/96, that should instead
be 64:ff9b:1::/48,
unless I'm misunderstanding the intent of the paragraph.

Thanks.

On Tue, May 2, 2017 at 10:00 AM, Fred Baker <fredbaker.ietf@gmail.com>
wrote:

> Thanks!
>
> > On May 2, 2017, at 9:30 AM, Joe Clarke <jclarke@cisco.com> wrote:
> >
> > Reviewer: Joe Clarke
> > Review result: Has Issues
> >
> > Hello, Tore and Fred.  Thanks for requesting an OPSDIR review of this
> > draft.  Up front, I'd like to say that I enjoyed hearing the
> > discussion on why certain decisions were made, especially with concern
> > to ease of use for operators and compatibility with other established
> > translation approaches.   That said, I have a few minor
> > issues/questions and nits concerning this draft.  I think they will be
> > easy to address.
> >
> > ISSUES/QUESTIONS:
> >
> > You set out to define WKP as _the_ well-known prefix.  For the most
> > part you adhere to this language in the draft.  However, in section 3,
> > you state (highlighting added by me):
> >
> > Also, because the WKP is a /96, an operator preferring to use _a WKP_
> > over an NSP can only do so for only one of his IPv4/IPv6 translation
> > mechanisms.  All others must necessarily use an NSP.
> >
> > And then in section 5:
> >
> > When 64:ff9b:1::/48 or a more-specific prefix is used with the
> > [RFC6052] algorithm, it is considered to be a Network-Specific
> > Prefix.
> >
> > I believe what you're saying is that while you define 64:ff9b:1::/48
> > as a WKP in _this_ draft, respective to RFC6052, it is an NSP.
> > However, the combination of text in both sections was a bit confusing
> > to me, and perhaps it would be useful to clarify your use of terms.
> >
> > ===
> >
> > In Section 3, you state:
> >
> > Since the WKP 64:ff9b::/96 was reserved by [RFC6052], several new
> > IPv4/IPv6 translation mechanisms have been defined by the IETF
> >
> > I think it would be useful to mention some of these new translation
> > mechanisms as non-normative references, and if need be, show an
> > example of interoperability.
> >
> > NITS:
> >
> > In your Abstract, you mention RFC6890, but this does not appear to be
> > an xref to it, and it should be.
> >
> > ===
> >
> > In Section 4.1 you state:
> >
> > OLD:
> > The second criterion is that the prefix length chosen is is a
> > multiple of 16.  This ensures the prefix ends on a colon boundary
> > when representing it in text, easing operator interaction with it.
> >
> > NEW:
> > The second criterion is that the prefix length chosen is a
> > multiple of 16.  This ensures the prefix ends on a colon boundary
> > when representing it in text, easing operator interaction with it.
> >
> > (Removed a redundant "is".)
> >
> > ===
> >
> > In Section 4.1 again:
> >
> > OLD:
> > The [RFC6052] algorithm specifies IPv4/IPv6 translation prefixes as
> > short as /32.  In order to facilitate multiple instances of
> > translation mechanisms using /32s, while at the same time aligning on
> > a 16-bit boundary, it would be necessary to reserve a /16.  Doing so
> > was however considered as too wasteful by the IPv6 Operations working
> > group.
> >
> > NEW:
> > The [RFC6052] algorithm specifies IPv4/IPv6 translation prefixes as
> > short as /32.  In order to facilitate multiple instances of
> > translation mechanisms using /32s, while at the same time aligning on
> > a 16-bit boundary, it would be necessary to reserve a /16.  Doing so,
> > however, was considered too wasteful by the IPv6 Operations working
> > group.
> >
> > ===
> >
> > In Section 6:
> >
> > OLD:
> > The Stateless IP/ICMP Translation algorithm [RFC7915] is one well-
> > known algorithm that can operate in a checksum-neutral manner, when
> > using the [RFC6052] algorithm for all of its address translations.
> > However, in order to attain checksum neutrality is imperative that
> > the translation prefix is chosen carefully.  Specifically, in order
> > for a 96-bit [RFC6052] prefix to be checksum neutral, all the six
> > 16-bit words in the prefix must add up to a multiple of 0xffff.
> >
> > NEW:
> > The Stateless IP/ICMP Translation algorithm [RFC7915] is one well-
> > known algorithm that can operate in a checksum-neutral manner, when
> > using the [RFC6052] algorithm for all of its address translations.
> > However, in order to attain checksum neutrality it is imperative that
> > the translation prefix is chosen carefully.  Specifically, in order
> > for a 96-bit [RFC6052] prefix to be checksum neutral, all the six
> > 16-bit words in the prefix must add up to a multiple of 0xffff.
> >
> > (Added a missing "it".)
> >
> > ===
> >
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>



-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815 <(612)%20626-0815>
Minneapolis, MN 55414-3029   Cell: 612-812-9952 <(612)%20812-9952>
===============================================

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

<div dir=3D"ltr">Prompted by this review, I reread the document and found w=
hat I think are a couple additional typos. =C2=A0<div><br></div><div>Sectio=
n 4.2, Prefix Value, compares=C2=A0<font color=3D"#000000"><span style=3D"f=
ont-size:13.3333px">two options: 64:ff9a:ffff:ffff::/48 and 64:ff9b:1::/48.=
 However in the fifth paragraph of the section, I believe there=C2=A0are tw=
o errant references=C2=A0to=C2=A0</span></font><span style=3D"color:rgb(0,0=
,0);font-size:13.3333px">64:ff9b:1::/96, that should instead be=C2=A0</span=
><font color=3D"#000000"><span style=3D"font-size:13.3333px">64:ff9b:1::/48=
, unless I&#39;m misunderstanding the intent of the paragraph.=C2=A0=C2=A0<=
/span></font><div><font color=3D"#000000"><span style=3D"font-size:13.3333p=
x"><br></span></font></div><div><font color=3D"#000000"><span style=3D"font=
-size:13.3333px">Thanks.<br></span></font><div class=3D"gmail_extra"><br><d=
iv class=3D"gmail_quote">On Tue, May 2, 2017 at 10:00 AM, Fred Baker <span =
dir=3D"ltr">&lt;<a href=3D"mailto:fredbaker.ietf@gmail.com" target=3D"_blan=
k">fredbaker.ietf@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">Thanks!<br>
<br>
&gt; On May 2, 2017, at 9:30 AM, Joe Clarke &lt;<a href=3D"mailto:jclarke@c=
isco.com" target=3D"_blank">jclarke@cisco.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Reviewer: Joe Clarke<br>
&gt; Review result: Has Issues<br>
&gt;<br>
&gt; Hello, Tore and Fred.=C2=A0 Thanks for requesting an OPSDIR review of =
this<br>
&gt; draft.=C2=A0 Up front, I&#39;d like to say that I enjoyed hearing the<=
br>
&gt; discussion on why certain decisions were made, especially with concern=
<br>
&gt; to ease of use for operators and compatibility with other established<=
br>
&gt; translation approaches.=C2=A0 =C2=A0That said, I have a few minor<br>
&gt; issues/questions and nits concerning this draft.=C2=A0 I think they wi=
ll be<br>
&gt; easy to address.<br>
&gt;<br>
&gt; ISSUES/QUESTIONS:<br>
&gt;<br>
&gt; You set out to define WKP as _the_ well-known prefix.=C2=A0 For the mo=
st<br>
&gt; part you adhere to this language in the draft.=C2=A0 However, in secti=
on 3,<br>
&gt; you state (highlighting added by me):<br>
&gt;<br>
&gt; Also, because the WKP is a /96, an operator preferring to use _a WKP_<=
br>
&gt; over an NSP can only do so for only one of his IPv4/IPv6 translation<b=
r>
&gt; mechanisms.=C2=A0 All others must necessarily use an NSP.<br>
&gt;<br>
&gt; And then in section 5:<br>
&gt;<br>
&gt; When 64:ff9b:1::/48 or a more-specific prefix is used with the<br>
&gt; [RFC6052] algorithm, it is considered to be a Network-Specific<br>
&gt; Prefix.<br>
&gt;<br>
&gt; I believe what you&#39;re saying is that while you define 64:ff9b:1::/=
48<br>
&gt; as a WKP in _this_ draft, respective to RFC6052, it is an NSP.<br>
&gt; However, the combination of text in both sections was a bit confusing<=
br>
&gt; to me, and perhaps it would be useful to clarify your use of terms.<br=
>
&gt;<br>
&gt; =3D=3D=3D<br>
&gt;<br>
&gt; In Section 3, you state:<br>
&gt;<br>
&gt; Since the WKP 64:ff9b::/96 was reserved by [RFC6052], several new<br>
&gt; IPv4/IPv6 translation mechanisms have been defined by the IETF<br>
&gt;<br>
&gt; I think it would be useful to mention some of these new translation<br=
>
&gt; mechanisms as non-normative references, and if need be, show an<br>
&gt; example of interoperability.<br>
&gt;<br>
&gt; NITS:<br>
&gt;<br>
&gt; In your Abstract, you mention RFC6890, but this does not appear to be<=
br>
&gt; an xref to it, and it should be.<br>
&gt;<br>
&gt; =3D=3D=3D<br>
&gt;<br>
&gt; In Section 4.1 you state:<br>
&gt;<br>
&gt; OLD:<br>
&gt; The second criterion is that the prefix length chosen is is a<br>
&gt; multiple of 16.=C2=A0 This ensures the prefix ends on a colon boundary=
<br>
&gt; when representing it in text, easing operator interaction with it.<br>
&gt;<br>
&gt; NEW:<br>
&gt; The second criterion is that the prefix length chosen is a<br>
&gt; multiple of 16.=C2=A0 This ensures the prefix ends on a colon boundary=
<br>
&gt; when representing it in text, easing operator interaction with it.<br>
&gt;<br>
&gt; (Removed a redundant &quot;is&quot;.)<br>
&gt;<br>
&gt; =3D=3D=3D<br>
&gt;<br>
&gt; In Section 4.1 again:<br>
&gt;<br>
&gt; OLD:<br>
&gt; The [RFC6052] algorithm specifies IPv4/IPv6 translation prefixes as<br=
>
&gt; short as /32.=C2=A0 In order to facilitate multiple instances of<br>
&gt; translation mechanisms using /32s, while at the same time aligning on<=
br>
&gt; a 16-bit boundary, it would be necessary to reserve a /16.=C2=A0 Doing=
 so<br>
&gt; was however considered as too wasteful by the IPv6 Operations working<=
br>
&gt; group.<br>
&gt;<br>
&gt; NEW:<br>
&gt; The [RFC6052] algorithm specifies IPv4/IPv6 translation prefixes as<br=
>
&gt; short as /32.=C2=A0 In order to facilitate multiple instances of<br>
&gt; translation mechanisms using /32s, while at the same time aligning on<=
br>
&gt; a 16-bit boundary, it would be necessary to reserve a /16.=C2=A0 Doing=
 so,<br>
&gt; however, was considered too wasteful by the IPv6 Operations working<br=
>
&gt; group.<br>
&gt;<br>
&gt; =3D=3D=3D<br>
&gt;<br>
&gt; In Section 6:<br>
&gt;<br>
&gt; OLD:<br>
&gt; The Stateless IP/ICMP Translation algorithm [RFC7915] is one well-<br>
&gt; known algorithm that can operate in a checksum-neutral manner, when<br=
>
&gt; using the [RFC6052] algorithm for all of its address translations.<br>
&gt; However, in order to attain checksum neutrality is imperative that<br>
&gt; the translation prefix is chosen carefully.=C2=A0 Specifically, in ord=
er<br>
&gt; for a 96-bit [RFC6052] prefix to be checksum neutral, all the six<br>
&gt; 16-bit words in the prefix must add up to a multiple of 0xffff.<br>
&gt;<br>
&gt; NEW:<br>
&gt; The Stateless IP/ICMP Translation algorithm [RFC7915] is one well-<br>
&gt; known algorithm that can operate in a checksum-neutral manner, when<br=
>
&gt; using the [RFC6052] algorithm for all of its address translations.<br>
&gt; However, in order to attain checksum neutrality it is imperative that<=
br>
&gt; the translation prefix is chosen carefully.=C2=A0 Specifically, in ord=
er<br>
&gt; for a 96-bit [RFC6052] prefix to be checksum neutral, all the six<br>
&gt; 16-bit words in the prefix must add up to a multiple of 0xffff.<br>
&gt;<br>
&gt; (Added a missing &quot;it&quot;.)<br>
&gt;<br>
&gt; =3D=3D=3D<br>
&gt;<br>
<br>
______________________________<wbr>_________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/v6ops</a><br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"m_-657169350583777597gmail_signature">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>David Farmer=C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a href=3D"mailto:Email%3Afarmer@umn.edu=
" target=3D"_blank">Email:farmer@umn.edu</a><br>Networking &amp; Telecommun=
ication Services<br>Office of Information Technology<br>University of Minne=
sota=C2=A0=C2=A0 <br>2218 University Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phon=
e: <a href=3D"tel:(612)%20626-0815" value=3D"+16126260815" target=3D"_blank=
">612-626-0815</a><br>Minneapolis, MN 55414-3029=C2=A0=C2=A0 Cell: <a href=
=3D"tel:(612)%20812-9952" value=3D"+16128129952" target=3D"_blank">612-812-=
9952</a><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D </div>
</div></div></div></div>

--f403045dce5e9d1e9c054e8c5bd4--


From nobody Tue May  2 09:58:09 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 7256213144B; Tue,  2 May 2017 09:57:47 -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: spring@ietf.org, draft-ietf-spring-ipv6-use-cases.all@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-ietf-spring-ipv6-use-cases-10
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149374426742.21414.16408814015665498739@ietfa.amsl.com>
Date: Tue, 02 May 2017 09:57:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aoOLvGaSwlSvvSOv1_vCI-73F-g>
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, 02 May 2017 16:57:47 -0000

Reviewer: Stewart Bryant
Review result: Not 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-spring-ipv6-use-cases-??
Reviewer: Stewart Bryant
Review Date: 2017-05-02
IETF LC End Date: 2017-05-04
IESG Telechat date: Not scheduled for a telechat

Summary:

I have a number of concerns about this draft, which I detail below.

A significant part of the justification seems to evolve around the
inability of MPLS to function in
an IPv6 only network. This is something that the MPLS WG should
provide expert input on.

Major issues:
   In addition there are cases where the operators could have made
the
   design choice to disable IPv4, for ease of management and scale
   (return to single-stack) or due to an address constraint, for
example
   because they do not possess enough IPv4 addresses resources to
number
   all the endpoints and other network elements on which they desire
to
   run MPLS.

SB> But as I show below MPLS WG either has fixed this or is very
close
SB> to fixing this, so I don't see how you can justify designing a
SB> major modification to the IPv6 dataplane on the basis of the above

SB> statement.

===============

   In such scenario the support for MPLS operations on an IPv6-only
   network would be required.  However today's IPv6-only networks are
   not fully capable of supporting MPLS.  There is ongoing work in
the
   MPLS Working Group, described in [RFC7439] to identify gaps that
must
   be addressed in order to allow MPLS-related protocols and
   applications to be used with IPv6-only networks.  

SB> That draft was published two years ago. An RFC was published to
SB> address the LDP gap mid 2016. RFC7506 fixed the RAO in April
2015,
SB> MIBs are being replaced by YANG. I am not sure you need GMPLS,
SB> L2VPN or L3VPN in the application you cite.
SB>
SB> I think a more up to date evaluation of the ability of MPLS
SB> to run in an IPv6 network is needed.
SB>
SB> Additionally if you are talking MPLS-SR then the shortfall is 
SB> different still because you rely on the SR extensions to the IGPs
SB> and not the classic MPLS signalling protocols.

============

   2.  There is a strict lack of an MPLS dataplane in a portion of
the
       end to end path

SB> It is not the lack of MPLS in a portion of the network, since you
SB> can tunnel MPLS over IP. The constraint applies when you need
SB> take an MPLS action at node that does not have MPLS forwarding
logic.
SB> I wonder how common this is in practise given that I understand
that 
SB> other work in IPv6 SR is driving towards convincing people that
SB> the number of actual SR actions on a path is tiny.

   4.  There is a need to connect millions of addressable segment
       endpoints, thus high routing scalability is a requirement. 
IPv6
       addresses are inherently summarizable: a very large operator
       could scale by summarizing IPv6 subnets at various internal
       boundaries.  This is very simple and is a basic property of IP
       routing.  MPLS node segments are not summarizable.  To reach
the
       same scale, an operator would need to introduce additional
       complexity, such as mechanisms known with the industry term
       Seamless MPLS [I-D.ietf-mpls-seamless-mpls].

SB> As far as I can see that draft has died, indeed it died in 2014.
SB> Assuming it has not be re-incarnated in another name, this calls
SB> into question the validity of the use case.
SB>
SB> I think to compare apples with apples here, we need to take a
SB> look at specific examples to verify that the scaling concern
arises.
SB> As part of that we need to consider whether the intrinsic
hierarchy
SB> MPLS, and the availability of MPLS context labels addresses the
issue.

SB> As far as I can see that draft has died, indeed it died in 2014.
SB> Assuming it has not be re-incarnated in another name, this calls
SB> into question the validity of the use case.
SB>
SB> I think to compare apples with apples here, we need to take a
SB> look at specific examples to verify that the scaling concern
arises.
SB> As part of that we need to consider whether the intrinsic
hierarchy
SB> MPLS, and the availability of MPLS context labels addresses the
issue.

   In any environment with requirements such as those listed above,
an
   IPv6 data plane 

SB> No, an IPv6 dataplane extended to include source routing
capability
SB> ... You do not get this through an off the shelf IPv6 dataplane
SB> other than perhaps MPLS/IPv6.
SB> ... and we should not belittle the difficulty of doing the
proposed
SB> SRv6 extensions, not all h/w can easily do it, and a lot of h/w
can 
SB> only introduce a tiny number of segments.

   provides a powerful combination of capabilities for a
   network operator to realize benefits in explicit routing,
protection
   and restoration, high routing scalability, traffic engineering,
   service chaining, service differentiation and application
flexibility
   via programmability.

SB> There is a bit of an (unexplained) leap from the introduction of 
SB> IPv6 to the above set of use cases.

============

   The use cases described in the section do not constitute an
   exhaustive list of all the possible scenarios; this section only
   includes some of the most common envisioned deployment models for
   IPv6 Segment Routing.  In addition to the use cases described in
this
   document the spring architecture should be able to be applied to
all
   the use cases described in [RFC7855] for the spring MPLS data
plane,
   when an IPv6 data plane is present.

SB> The second sentence reduces to the need to make MPLS work in
SB> an IPv6 environment.

==========

   The ability to steer traffic to an appropriate egress or utilize a
   specific type of media (e.g., low-power, WIFI, wired, femto-cell,
   bluetooth, MOCA, HomePlug, etc.) within the home itself are
obvious
   cases which may be of interest to an application running within a
   home network.

SB> So the interesting thing here is that to set up a SR you normally
SB> need to know the topology so you can plan the path, but homenet
SB> chose a distance vector protocol, which is a protocol genre that 
SB> normally does not understand the topology.

========

   Information included in the spring header, whether imposed by the
   end-host itself, a customer edge router, or within the access
network
   of the ISP, may be of use at the far ends of the data
communication
   as well.  For example, an application running on an end-host with
   application-support in a data center can utilize the spring header
as
   a channel to include information that affects its treatment within
   the data center itself, allowing for application-level steering
and
   load-balancing without relying upon implicit application
   classification techniques at the data-center edge.  Further, as
more
   and more application traffic is encrypted, the ability to extract
   (and include in the spring header) just enough information to
enable
   the network and data center to load-balance and steer traffic
   appropriately becomes more and more important.

SB> However there is a trust issue with sharing information in this
way
SB> and it was a breach of trust that caused the source routing
feature 
SB> to be removed from IPv6 in the first place.
SB>
SB> For this to be a valid use case I think you need to address the 
SB> trust and security issues to explain why they are no longer
relevant
SB> or make it clear that they need to be addressed.

========

   The need to setup a source-based path, going through some specific
   middle/intermediate points in the network may be related to
different
   requirements:

SB> There needs to be some discussion on the trust model here and
SB> attack vectors associated with this proposal.

==========

   This document presents use cases to be considered by the spring
   architecture and potential IPv6 extensions.  As such, it does not
   introduce any security considerations.  However, there are a
number
   of security concerns with source routing at the IP layer
[RFC5095].
   It is expected that any solution that addresses these use cases to
   also address any security concerns.

SB> It is not clear that the introduction of this technology to these
SB> applications does not introduce a solutions agnostic increase in
SB> security risk.
SB> 

Minor issues:

   The objective of this document is to illustrate some use cases
that
   need to be taken into account by the Source Packet Routing in
   Networking (SPRING) architecture in the context of an IPv6
   environment.

SB> It is unclear whether it is feeding the SR architecture (which is
SB> currently in AD evaluation) or the SRv6 design.
SB>
SB> It seems a bit late to be progressing this if it is a requirement
SB> on the architecture.

================

   Source Packet Routing in Networking (SPRING) architecture
leverages
   the source routing paradigm.  An ingress node steers a packet
through
   a controlled set of instructions, called segments, by prepending
the
   packet with SPRING header.  

SB> That is what I think it should do, but that is not the design
direction
SB> of the current IPv6 proposal. The design of record modifies the 
SB> IPv6 header.

==========

   In today's networks, source routing is typically accomplished by
   encapsulating IP packets in MPLS LSPs that are signaled via
RSVP-TE.

SB> There is an interesting question as to whether RSVP-TE is a
SB> source routing paradygm or simply an explicit routing paradygm.
SB> Source routing is more commonly associated with a route imposed
SB> on a packet rather than the identify of a route being imposed on
SB> a packet.

   3.  There is a need or desire to remove routing state from any
node
       other than the source, such that the source is the only node
that
       knows and will know the path a packet will take, a priori

SB> That is a SR goal, not a goal specific to IPv6

==========

   A spring enabled home provides the ability to steer traffic into a
   specific path from end-hosts in the home, or from a customer edge
   router in the home.  

SB> Where does Babel fit into this? Isn't the purpose of Babel
SB> to do this in a standard IPv6 dataplane?

=========

   Some Data Center operators are transitioning their Data Center
   infrastructure from IPv4 to native IPv6 only, in order to cope
with
   IPv4 address depletion and to achieve larger scale.  In such
   environment, source routing (through Segment Routing IPv6) can be
   used to steer traffic across specific paths through the network. 

SB> I do not see how the first sentence leads to the second.

==========

   In an environment, where each single cache system can be uniquely
   identified by its own IPv6 address, a list containing a sequence
of
   the caches in a hierarchy can be built.  At each node (cache) in
the
   list, the presence of the requested content if checked.  If the
   requested content is found at the cache (cache hits scenario) the
   sequence ends, even if there are more nodes in the list; otherwise
   next element in the list (next node/cache) is examined.

SB> This needs some discussion on the alternative approaches:
SB> for example service function chaining and an ICN overlay.

Nits/editorial comments: 
   Therefore, there are scenarios where it may be possible to run
IPv6
   on top of MPLS, and as such, the MPLS Segment Routing architecture

SB> I think that is a design rather than an architecture.

=============

   This is an another
   example of scenario where a solution relying on IPv6 without
   requiring the use of MPLS could represent a valid option to solve
the
   problem and meet operators' requirements.

SB> "could" is not a particularly strong justification.


From nobody Tue May  2 12:05:05 2017
Return-Path: <housley@vigilsec.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 7B90C12751F; Tue,  2 May 2017 12:04:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Russ Housley <housley@vigilsec.com>
To: <gen-art@ietf.org>
Cc: ietf@ietf.org, draft-ietf-nfsv4-versioning.all@ietf.org, nfsv4@ietf.org
Subject: Genart last call review of draft-ietf-nfsv4-versioning-09
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149375188938.21443.7482767478129358123@ietfa.amsl.com>
Date: Tue, 02 May 2017 12:04:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/erPfhnd8AsMLygIdaN7Q2WMhF7g>
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, 02 May 2017 19:04:50 -0000

Reviewer: Russ Housley
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 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
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-nfsv4-versioning-09
Reviewer: Russ Housley
Review Date: 2017-05-02
IETF LC End Date: 2017-03-08
IESG Telechat date: Unknown

Summary: Almost Ready

Major Concerns:

This document, once approved, will update RFC 5661 and RFC 7862.  It
seems to me that it should also update RFC 7530.  It fulfills a
promise
made in Section 11 of RFC 7530.

Minor Concerns:

In Section 4.2, the last bullet in the section is unusual.  That
bullet
add a new context for the entire list of bullets.  It would be better
for the introduction to the list to provide the full context at the
beginning.

Nits:

Throughout the document, some bullet items end with periods and
others
do not.  Use of the period is more common.  Please pick one style and
use it throughout the document.

The last sentence of the Introduction is not clear.  After reading it
several times, I think you are trying to say:

   ... enabling interoperation to proceed just as if both
   implementations supported only the parts of the protocol
   that are being used.

In Section 2.3:
s/(not necessarily proper)/(not necessarily a proper subset)/

In Section 4.4.2, in the last set of bullets, the first bullet begins
with "The minor version consists", but it should begin with "When the
minor version consists".  The "so" following the comma should also be
removed.

In Section 6, 2nd paragraph, I found the text confusing because
"following" is used with two very different meanings in the same
sentence.  I suggest: S/to following/to obeying/



From nobody Tue May  2 12:21:51 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 AD80112D0C3; Tue,  2 May 2017 12:21:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Level: 
X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham 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 wuV44xSX559H; Tue,  2 May 2017 12:21:47 -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 3F9D3129461; Tue,  2 May 2017 12:18:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v42JIW7D005375; Tue, 2 May 2017 21:18:32 +0200 (CEST)
Received: from [192.168.217.113] (p5DC7F3A7.dip0.t-ipconnect.de [93.199.243.167]) (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 3wHWKh3dJszDHjL; Tue,  2 May 2017 21:18:32 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Last Call: <draft-nottingham-rfc5988bis-05.txt> (Web Linking) to Proposed Standard
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <149339514498.2963.17820948075543728710.idtracker@ietfa.amsl.com>
Date: Tue, 2 May 2017 21:18:32 +0200
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Barry Leiba <barryleiba@computer.org>, draft-nottingham-rfc5988bis@ietf.org
X-Mao-Original-Outgoing-Id: 515445511.915529-2e154204e3f776008bf1e7519cbbb466
Content-Transfer-Encoding: quoted-printable
Message-Id: <4BECE06F-D3E5-4F9B-9DBF-AE9150942190@tzi.org>
References: <149339514498.2963.17820948075543728710.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WHctL0CY-rCc4yT-aIRZoFttWxw>
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, 02 May 2017 19:21:51 -0000

Review of draft-nottingham-rfc5988bis-05.txt
Reviewer: Carsten Bormann
Review result: Ready with a few issues

(This is not a complete review, but in its present state might serve
to initiate discussion of items relevant to RFC 6690 and thus
draft-ietf-core-links-json.)

This specification updates RFC 5988.  The objectives for this update
are not clearly stated, but it seems to be based on experience with
RFC 5988 as well as based on advances possible with the publication of
RFC 7230.

# Major technical

T1: The draft does not take position what should happen when
serializations allowed by RFC 5988 but not by the present spec occur,
e.g.: ;type=3Dtext/plain (would now need to be ;type=3D"text/plain").

T2: The draft says "Serialisations SHOULD coordinate their target
attributes to avoid conflicts in semantics or syntax."  To me it seems
that this gives link applications such as the one specified in RFC
6690 the go-ahead to define their own registries of target attributes.
The draft should take a position on this.

# Minor technical

T3: One of the major items of progress that this specification exhibits
is that target attributes are no longer defined by the ABNF of the
link-header serialization (which usually has two alternatives, one of
which may be forgotten) but by the ABNF of the attribute value string
itself.  ANBF tools usually can process ABNF rules, but not directly
the bare ABNF "alternations" (rule RHS) used here.  This may also make
it a bit harder to reference the ABNF from a dependent specification,
as there is no rule name for that alternation given.

# Minor editorial

E1: The abstract should probably mention that this replaces RFC 5988.

# Nits

The spec seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but
does not include the phrase in its RFC 2119 key words list.  (Pet
peeve.)

s/ for indicate/ for indicating/

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



From nobody Tue May  2 14:25:58 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 1148F12E053; Tue,  2 May 2017 14:25:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 iMJBq945D06H; Tue,  2 May 2017 14:25:47 -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 40A4312E03F; Tue,  2 May 2017 14:23:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10984; q=dns/txt; s=iport; t=1493760213; x=1494969813; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=5UxF2PF0n/J1CXCZH21wPFLuuw/My35BYmGYuA+J0Lg=; b=U/x6XVGk7ZpqqXLugRQTKzuTzs3mdhA5o8rIhwBmthMgoah8cn7VAnuC K51AC2BjfY4r/e5IAV1Gi+tidm4jUPoc95/+NQae7IS/CRp1fn2eadXVm AZHBZ42fHQr0+JqKxwET96UdaIg8TfJyiBsiUlUGNYhFR0ZUS7fiR28Mu I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B5AQC99whZ/xbLJq1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBhDeBDINoihhzkDshkDeFN4IPIQEMgkCCbEoChQ8YAQIBAQEBAQE?= =?us-ascii?q?BayiFFQEBAQECAQEBIUsEBwULCQIYIwcCAicfEQYBDAYCAQGKEggOkjedYYImK?= =?us-ascii?q?4p1AQEBAQEBAQEBAQEBAQEBAQEBAQEBGAWGX4FeKwuCZYdpgl8BBJZWhn6HG4t?= =?us-ascii?q?2ggKFN4NChmOMBogrHziBCi4gCBkVRIUmgUw+NokJAQEB?=
X-IronPort-AV: E=Sophos;i="5.38,281,1491264000";  d="scan'208,217";a="652591866"
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; 02 May 2017 21:23:29 +0000
Received: from [10.60.67.90] (ams-bclaise-8919.cisco.com [10.60.67.90]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v42LNTRt029284; Tue, 2 May 2017 21:23:29 GMT
Subject: Re: [netmod] Last Call: <draft-ietf-netmod-yang-model-classification-06.txt> (YANG Module Classification) to Informational RFC
To: Jonathan Hansford <jonathan@hansfords.net>, IETF-Announce <ietf-announce@ietf.org>, ietf@ietf.org
References: <149360589744.9906.9498469901914786081.idtracker@ietfa.amsl.com> <46a76c75-fd04-4134-9a97-26d1567963d7@Spark>
Cc: netmod-chairs@ietf.org, warren@kumari.net, draft-ietf-netmod-yang-model-classification@ietf.org, netmod@ietf.org
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <d7e4de44-60be-54ad-4727-16b05ebe7a4b@cisco.com>
Date: Tue, 2 May 2017 23:23:29 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <46a76c75-fd04-4134-9a97-26d1567963d7@Spark>
Content-Type: multipart/alternative; boundary="------------7410EE1787B6D4CFEB1AD49B"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/s1kOhi3HnivvhTUxYx4E0wOj-us>
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, 02 May 2017 21:25:49 -0000

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

Thanks Jonathan,

See in line.

> I have no substantive comments, but have noticed, among other things, 
> a few somewhat inconsequential typos that could nevertheless impact 
> readability, particularly for those for whom English is a second language:
> • Page 3, penultimate bullet: s/by network operator/by a network operator
> • Why is figure 1 on page 5 when it is first referenced at the top of 
> page 4?
> • Section 2.1, second paragraph (2 typos): s/peole or extarnal/people 
> or external
> • Section 2.1, last paragraph: I don't understand the second sentence 
> that starts: “Although it provides information …”
> • Section 2.2, second paragraph: i don't understand the first sentence 
> that starts: “Although the [RFC7950], [RFC7950] …”
I guess this should be:

    Although YANG [RFC7950 <https://tools.ietf.org/html/rfc7950>] doesn't explain the relationship of
    the terms '(YANG) data model' and '(YANG) module', the authors
    understand there is a 1:1 relationship between a data model and a
    YANG module, but a data model may also be expressed using a
    collection of YANG modules (and submodules).  The module provides a
    coherent data model representation of the software environment
    consisting of the operating system and applications running on the
    device.  The decomposition, ordering, and execution of changes to the
    operating system and application configuration is the task of the
    agent that implements the module.

Re-reading this paragraph, its logical place is in the terminology 
section 1.1, next to data model and module definitions.

Regards, Benoit
> • Section 3.3, second paragraph: s/include ability/include the ability
> • Section 6: small point but I believe the second acknowledgement 
> should be me(!), “Jonathan Hansford”, not “David”
>
> Jonathan
>
> =O)
>
>
> On 1 May 2017, 03:32 +0100, The IESG <iesg-secretary@ietf.org>, wrote:
>>
>> The IESG has received a request from the NETCONF Data Modeling Language
>> WG (netmod) to consider the following document:
>> - 'YANG Module Classification'
>> <draft-ietf-netmod-yang-model-classification-06.txt> as Informational
>> RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2017-05-14. 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 YANG data modeling language is currently being considered for a
>> wide variety of applications throughout the networking industry at
>> large. Many standards-defining organizations (SDOs), open source
>> software projects, vendors and users are using YANG to develop and
>> publish YANG modules for a wide variety of applications. At the same
>> time, there is currently no well-known terminology to categorize
>> various types of YANG modules.
>>
>> A consistent terminology would help with the categorization of YANG
>> modules, assist in the analysis of the YANG data modeling efforts in
>> the IETF and other organizations, and bring clarity to the YANG-
>> related discussions between the different groups.
>>
>> This document describes a set of concepts and associated terms to
>> support consistent classification of YANG modules.
>>
>>
>>
>>
>> The file can be obtained via
>> https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classification/
>>
>> IESG discussion can be tracked via
>> https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classification/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>>
>>
>>
>> _______________________________________________
>> netmod mailing list
>> netmod@ietf.org
>> https://www.ietf.org/mailman/listinfo/netmod


--------------7410EE1787B6D4CFEB1AD49B
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">
    <div class="moz-cite-prefix">Thanks Jonathan,<br>
      <br>
      See in line.<br>
      <br>
    </div>
    <blockquote cite="mid:46a76c75-fd04-4134-9a97-26d1567963d7@Spark"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <title></title>
      <div name="messageBodySection">I have no substantive comments, but
        have noticed, among other things, a few somewhat inconsequential
        typos that could nevertheless impact readability, particularly
        for those for whom English is a second language:<br>
        • Page 3, penultimate bullet: s/by network operator/by a network
        operator<br>
        • Why is figure 1 on page 5 when it is first referenced at the
        top of page 4?<br>
        • Section 2.1, second paragraph (2 typos): s/peole or
        extarnal/people or external<br>
        • Section 2.1, last paragraph: I don't understand the second
        sentence that starts: “Although it provides information …”<br>
        • Section 2.2, second paragraph: i don't understand the first
        sentence that starts: “Although the [RFC7950], [RFC7950] …”</div>
    </blockquote>
    I guess this should be:<br>
    <pre class="newpage">   Although YANG [<a href="https://tools.ietf.org/html/rfc7950" title="&quot;The YANG 1.1 Data Modeling Language&quot;">RFC7950</a>] doesn't explain the relationship of
   the terms '(YANG) data model' and '(YANG) module', the authors
   understand there is a 1:1 relationship between a data model and a
   YANG module, but a data model may also be expressed using a
   collection of YANG modules (and submodules).  The module provides a
   coherent data model representation of the software environment
   consisting of the operating system and applications running on the
   device.  The decomposition, ordering, and execution of changes to the
   operating system and application configuration is the task of the
   agent that implements the module.
</pre>
    Re-reading this paragraph, its logical place is in the terminology
    section 1.1, next to data model and module definitions.<br>
    <br>
    Regards, Benoit<br>
    <blockquote cite="mid:46a76c75-fd04-4134-9a97-26d1567963d7@Spark"
      type="cite">
      <div name="messageBodySection">
        • Section 3.3, second paragraph: s/include ability/include the
        ability<br>
        • Section 6: small point but I believe the second
        acknowledgement should be me(!), “Jonathan Hansford”, not
        “David”</div>
      <div name="messageSignatureSection"><br>
        Jonathan<br>
        <br>
        =O)</div>
      <div name="messageReplySection"><br>
        <div name="messageReplySection"><br>
          On 1 May 2017, 03:32 +0100, The IESG
          <a class="moz-txt-link-rfc2396E" href="mailto:iesg-secretary@ietf.org">&lt;iesg-secretary@ietf.org&gt;</a>, wrote:<br>
          <blockquote type="cite"><br>
            The IESG has received a request from the NETCONF Data
            Modeling Language<br>
            WG (netmod) to consider the following document:<br>
            - 'YANG Module Classification'<br>
            &lt;draft-ietf-netmod-yang-model-classification-06.txt&gt;
            as Informational<br>
            RFC<br>
            <br>
            The IESG plans to make a decision in the next few weeks, and
            solicits<br>
            final comments on this action. Please send substantive
            comments to the<br>
            <a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2017-05-14. Exceptionally,
            comments may be<br>
            sent to <a class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain
            the<br>
            beginning of the Subject line to allow automated sorting.<br>
            <br>
            Abstract<br>
            <br>
            <br>
            The YANG data modeling language is currently being
            considered for a<br>
            wide variety of applications throughout the networking
            industry at<br>
            large. Many standards-defining organizations (SDOs), open
            source<br>
            software projects, vendors and users are using YANG to
            develop and<br>
            publish YANG modules for a wide variety of applications. At
            the same<br>
            time, there is currently no well-known terminology to
            categorize<br>
            various types of YANG modules.<br>
            <br>
            A consistent terminology would help with the categorization
            of YANG<br>
            modules, assist in the analysis of the YANG data modeling
            efforts in<br>
            the IETF and other organizations, and bring clarity to the
            YANG-<br>
            related discussions between the different groups.<br>
            <br>
            This document describes a set of concepts and associated
            terms to<br>
            support consistent classification of YANG modules.<br>
            <br>
            <br>
            <br>
            <br>
            The file can be obtained via<br>
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classification/">https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classification/</a><br>
            <br>
            IESG discussion can be tracked via<br>
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classification/ballot/">https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classification/ballot/</a><br>
            <br>
            <br>
            No IPR declarations have been submitted directly on this
            I-D.<br>
            <br>
            <br>
            <br>
            <br>
            _______________________________________________<br>
            netmod mailing list<br>
            <a class="moz-txt-link-abbreviated" href="mailto:netmod@ietf.org">netmod@ietf.org</a><br>
            <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/netmod">https://www.ietf.org/mailman/listinfo/netmod</a><br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------7410EE1787B6D4CFEB1AD49B--


From nobody Tue May  2 14:29:58 2017
Return-Path: <ietf-trust@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 42839129BBB; Tue,  2 May 2017 06:43:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: The IETF Trust <ietf-trust@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: Proposed Changes to License Agreements between ICANN and IETF Trust
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: trustees@ietf.org
Message-ID: <149373262717.9880.7516296670939349912.idtracker@ietfa.amsl.com>
Date: Tue, 02 May 2017 06:43:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0Gb-RijTuLOst_jAio91mdnHE1o>
X-Mailman-Approved-At: Tue, 02 May 2017 14:29:57 -0700
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, 02 May 2017 13:43:47 -0000

All;

We are in the process of transferring the IANA domains to the Trust
from ICANN using CSC as the registrar.

The agreement with CSC requires the incorporation of the IANA IPR
License Agreements’ Exhibit E Domain Name Registrar Requirements. 
Exhibit E is the same in each of the three IANA IPR License
Agreements between the Trust and ICANN, specifically the licenses
for the IANA Names Services, the IANA Numbers Services and the IANA
Protocol Parameter Services.

The implementation of the domain name registrar requirements needed
additional details than in the current Exhibit E. These details have
been worked out with ICANN, reviewed by the CCG and approved by the
IETF Trust for this review by the community.

Specifically the proposed changes affect the following: under the
circumstance where the Administrative and Technical Contacts must
approve the change to the Technical Contact the Registrar must
provide notice of a receipt of a request to each to change the
Technical Contact.

Additionally, under the circumstance where the Registrant (Trust)
can override the need for the other parties to approve a change to
the Technical Contact, the Registrant must provide documentation
that notice of the change was provided to both the Administrative
and Technical Contacts and that no response was received after a
period of no less than ten business days.

These conditions are also incorporated under the circumstances where
the domain is set to prohibit registrar transfers, to prohibit
deletions, and to remove the configuration to renew the domain
automatically.

A markup of the License Agreement Exhibit E reflects those proposed
details and can be found here as Proposed Amendment to License
Agreements 1 May 17: https://trustee.ietf.org/iana.html

CSC has agreed that it can implement the proposed changes.

It is believed the next steps are:

  a.  Community Review
  b.  Acceptance of proposed changes to Exhibit E by the Trust
  c.  Trust and ICANN execute amendments to the three License 
	Agreements
  d.  Incorporate the changes in CSC Agreement Schedule A
	(Schedule A is the same as Exhibit E of the License Agreements)
  e.  Trust puts Schedule A of the CSC Agreement out for Community 
	Review 
  f.  Community Review
  g.  Trust executes CSC Agreement
  h.  CSC Test of conformance to the requirements 
  i.  All IANA domains transferred upon successful test

Your feedback by 17 May 2017 on the proposed amendments to Exhibit E
of the IANA IPR License Agreements and the next steps are
appreciated.

Thanks.

Kaveh Ranjbar
Chair
IETF Trust


From nobody Tue May  2 16:04:18 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 074901296CD; Tue,  2 May 2017 16:04:02 -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 SpLORBmE6cVW; Tue,  2 May 2017 16:03:59 -0700 (PDT)
Received: from mail-pg0-x243.google.com (mail-pg0-x243.google.com [IPv6:2607:f8b0:400e:c05::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 9ECD4129515; Tue,  2 May 2017 16:01:55 -0700 (PDT)
Received: by mail-pg0-x243.google.com with SMTP id v1so24936532pgv.3; Tue, 02 May 2017 16:01:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=nABeFVGEteVxrwA3WaMfm5HI0sp9CxaZ2upwSNaRnzM=; b=qlx8SLhnpeh1FqS/fBb3zbi01Qog1R+uZweSX8vEiywoqper7C6S9RoUMzWK495tOt 95DDK/3ncpkZtCGjPSCQJC9NieAGx8QfZJRFN+efSTjQVPDE26FlUTJi+WZ5Fin8MfQG 6+v7xwWe0ANt2IPnq7M6FWb/aY4qdTBmk3JVhhN0ajt+Tnb/AzBvaPj509Xkthfk4jZc hoXoIQSdJmkGMk/Sqzms8DpY/YA87K1NXObFqM6JDKfEl/7w4DhLRFD4jy0OY3W2dFIN 9NcS2B27OIearPofNefms3sxK06nHn4u1WRlnxC8zBL8ZpPhkjLfzCMKc8kcgwTF8+Kv /fQg==
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:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=nABeFVGEteVxrwA3WaMfm5HI0sp9CxaZ2upwSNaRnzM=; b=DplQTVIJPHvtsZdXCExK3V3JLjMCNrFjzzu/Nhrzmsc64ARSEwqnhqgEnruz8UuTo0 f+T/5F7iW5nY1iCIvAgdi2ofmtZOuy0b7fvF6r5OAXxAJg7uUwaOEh04kHHnWvQ9j0xS T2hwvFBpldX79vIzu2H8YhZGoACxtqeiXEM+t7j5bV1keFE4AWFBi/uFCQnAWE+Ajb5y 8mKjK+4x4f0YzISIUKO6MyMqC7wGwHiZo90zXBHFGrn6BVLWju6Vt0l1JMQ9DeXEM0E6 WUzaYcewGh5sYjOlNP3k9QSXnnWCY9cDbVaITDyOicIMwYpVi11mKX7LWyBMNK6mFFfY Ph/g==
X-Gm-Message-State: AN3rC/4m12at13vuYjt72Yr9U3WhyL+TptfqhtBuR8/sggPHMyiKTRzx TSop57ve00OEIA==
X-Received: by 10.84.192.37 with SMTP id b34mr45181043pld.174.1493766115295; Tue, 02 May 2017 16:01:55 -0700 (PDT)
Received: from ?IPv6:2406:e001:3a49:1:28cc:dc4c:9703:6781? ([2406:e001:3a49:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id p28sm791331pfd.53.2017.05.02.16.01.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 May 2017 16:01:54 -0700 (PDT)
Subject: Re: [v6ops] Opsdir early review of draft-ietf-v6ops-v4v6-xlat-prefix-00
To: Joe Clarke <jclarke@cisco.com>, ops-dir@ietf.org
References: <149373185172.9923.9255526962045750289@ietfa.amsl.com>
Cc: v6ops@ietf.org, ietf@ietf.org, draft-ietf-v6ops-v4v6-xlat-prefix.all@ietf.org
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <06e8313e-38ed-7ea5-76f0-db2f6352844e@gmail.com>
Date: Wed, 3 May 2017 11:01:54 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <149373185172.9923.9255526962045750289@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pMuAyuE3Z45tgGT0qJqDJmnU96A>
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, 02 May 2017 23:04:02 -0000

On 03/05/2017 01:30, Joe Clarke wrote:
...
> NITS:
> 
> In your Abstract, you mention RFC6890, but this does not appear to be
> an xref to it, and it should be.

afaik, the RFC Editor style does not allow xrefs in the Abstract.

(Also: draft-bchv-rfc6890bis will update 6890 soon. I don't know whether
that's relevant.)

    Brian


From nobody Tue May  2 16:09:39 2017
Return-Path: <jclarke@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 5CDB312EAF0; Tue,  2 May 2017 16:09:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 0h7OsoB650Mb; Tue,  2 May 2017 16:09:24 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B166127097; Tue,  2 May 2017 16:06:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=624; q=dns/txt; s=iport; t=1493766395; x=1494975995; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=sS2HCvjTUHNvtKHaOu/En2ooNbMt7HBuTHPzrj1VXm0=; b=I/pNkjdzTBSnL7ZLyIq3DP6KWgOn2s3p4KsxnaZ53WBP00Ub/W94aKtH bDEA8hX47Qbn0YInQb5splU6GSQ+7Lkey6iwTdehDoWdIycMW74Z62JqA /FtnbXd0Hq0sCeEHbPWd2W99RSRYQcgHzmxo8K1Vu04Oift/jmHxS9xL1 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DNAACkDwlZ/5JdJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1VigQyOAJFPiCKNTIIPKIV8AoRQPxgBAgEBAQEBAQFrKIUVAQE?= =?us-ascii?q?BAQIBOj8FCwIBCBgeECERJQIEDgWKBgMNCLJZhzkNg1sBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEdhl+BXiuCcIJUKIFngzSCMQWdGTsBjkKEToFqGI9ciHeCKCeIagE?= =?us-ascii?q?fOIEKbxVWAYZddgGJCAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.38,281,1491264000"; d="scan'208";a="418830551"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 May 2017 23:06:34 +0000
Received: from XCH-ALN-012.cisco.com (xch-aln-012.cisco.com [173.36.7.22]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v42N6YS5029729 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 2 May 2017 23:06:34 GMT
Received: from xch-rcd-015.cisco.com (173.37.102.25) by XCH-ALN-012.cisco.com (173.36.7.22) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 2 May 2017 18:06:33 -0500
Received: from xch-rcd-015.cisco.com ([173.37.102.25]) by XCH-RCD-015.cisco.com ([173.37.102.25]) with mapi id 15.00.1210.000; Tue, 2 May 2017 18:06:33 -0500
From: "Joe Clarke (jclarke)" <jclarke@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: "ops-dir@ietf.org" <ops-dir@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-v6ops-v4v6-xlat-prefix.all@ietf.org" <draft-ietf-v6ops-v4v6-xlat-prefix.all@ietf.org>
Subject: Re: [v6ops] Opsdir early review of draft-ietf-v6ops-v4v6-xlat-prefix-00
Thread-Topic: [v6ops] Opsdir early review of draft-ietf-v6ops-v4v6-xlat-prefix-00
Thread-Index: AQHSw5gYiMaIOea5YEmnrvODvaYgVqHhqktV
Date: Tue, 2 May 2017 23:06:33 +0000
Message-ID: <8392FFDD-AA72-47B6-B689-1EE2C8967A2E@cisco.com>
References: <149373185172.9923.9255526962045750289@ietfa.amsl.com>, <06e8313e-38ed-7ea5-76f0-db2f6352844e@gmail.com>
In-Reply-To: <06e8313e-38ed-7ea5-76f0-db2f6352844e@gmail.com>
Accept-Language: en-US
Content-Language: en-US
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/zghS_fBO7JB-kih3v6aStuj-Xf4>
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, 02 May 2017 23:09:25 -0000

PGP Key : http://www.marcuscom.com/pgp.asc

> On May 2, 2017, at 19:01, Brian E Carpenter <brian.e.carpenter@gmail.com>=
 wrote:
>=20
>> On 03/05/2017 01:30, Joe Clarke wrote:
>> ...
>> NITS:
>>=20
>> In your Abstract, you mention RFC6890, but this does not appear to be
>> an xref to it, and it should be.
>=20
> afaik, the RFC Editor style does not allow xrefs in the Abstract.

I've seen some that do (ostensibly).  But this if this isn't required, it w=
asn't critical.

Joe

>=20
> (Also: draft-bchv-rfc6890bis will update 6890 soon. I don't know whether
> that's relevant.)
>=20
>    Brian


From nobody Tue May  2 16:51:01 2017
Return-Path: <davenoveck@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 C9FE212922E; Tue,  2 May 2017 16:50:45 -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 TdINOFsHzeqv; Tue,  2 May 2017 16:50:43 -0700 (PDT)
Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::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 DE6D6129BC8; Tue,  2 May 2017 16:48:57 -0700 (PDT)
Received: by mail-it0-x22a.google.com with SMTP id e65so28222225ita.1; Tue, 02 May 2017 16:48:57 -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=f1WYamJ6MhRIrh8VhyDg6ZTGF89M6xNA5fWwZ2pTCng=; b=Hv9j8fSo8Ol9AT1qjIwCwcK+OZDsiG51TuBEuK/X0yEPpwgTeuEyrHZLWnJ3mOpQ7l FUGVTRaiErnTckhewpQFrwI3gGgmY6HWYmh6aU+fzcn0zRn1eqULvrVlGceJfx9oHypX LVTBDSY+GoIHpyLB2OxNXF42BTXn50vkw/i/3I9NmmwwEc/0iKqko8xkxCnhLW+fMNhV VNCMvcSZswHhy9y7hYA/Ru1jA4oRmkFX0PfmgIh/fbXyEm4YIWeB1fxCI1K65+5sCHlp juvW/Hs8Y3nuaDVSqb7Y1Nj/0WvXb19Qb0aMF9KgXJQNSl0Y/JW0RCZxbUiHlE+v7lXb Wr9w==
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=f1WYamJ6MhRIrh8VhyDg6ZTGF89M6xNA5fWwZ2pTCng=; b=TX/ix36AJCBNwAca32FlEnHCd7HEp+MecjaZ1KXB3AETEMyMBqlUUcXwm7LIyhYLFd DTIUAnmS3um2CkvWqXNqm78yTbtgNdMS9CyqggvMnQ4pVsEA/xBUIJOobC5uMNq8FSdL 9X0/G5kkJ1uXFVW2+MVze9gkHViL11/ju3Sl7cVBkLLEzrYNTZDGiX9Oi7LiiezbAQFs uIWRYsZrZuDM+WAyjbPo1Vg5EurN+8w+DskFUBl4v6a1Jt8YCs9SAQy27cflvNy+BiZO 0jfIaTszogfnnHt8zF4ft+fg767yLnKiMhWpO2l7UJ4WozO1tEvpeqWbGoLkrTtWyv5l wFwQ==
X-Gm-Message-State: AN3rC/6TzAeUSmijWFZv6pzf5B+jq3gREPOC4KA4Q6KLk/8TcqN7Uany o9+5tP6SQNwFY4skShLwtTUQPrHoeXCM
X-Received: by 10.36.137.212 with SMTP id s203mr5379805itd.57.1493768937205; Tue, 02 May 2017 16:48:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.175.14 with HTTP; Tue, 2 May 2017 16:48:56 -0700 (PDT)
In-Reply-To: <149375188938.21443.7482767478129358123@ietfa.amsl.com>
References: <149375188938.21443.7482767478129358123@ietfa.amsl.com>
From: David Noveck <davenoveck@gmail.com>
Date: Tue, 2 May 2017 19:48:56 -0400
Message-ID: <CADaq8jfqDuaLdsmWuvJpyyKc+krqHBYdif1BEBrGvRBSTnKrzg@mail.gmail.com>
Subject: Re: Genart last call review of draft-ietf-nfsv4-versioning-09
To: Russ Housley <housley@vigilsec.com>
Cc: "gen-art >> General area reviewing team" <gen-art@ietf.org>, ietf@ietf.org, draft-ietf-nfsv4-versioning.all@ietf.org, "nfsv4@ietf.org" <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c05f6a0e0fb78054e932ea3
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IVRPAXPV3APBPUm1wT5X5jbi3uY>
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, 02 May 2017 23:50:46 -0000

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

Thanks for the review.

> This document, once approved, will update RFC 5661 and RFC 7862.

Yes, because it invalidates statements regarding versioning made in
those documents.

> It seems to me that it should also update RFC 7530.

I don't see why.  What is in RFC7530 regarding versioning still
remains valid once this document is approved.

> It fulfills a promise made in Section 11 of RFC 7530.

Section 11 says that a document such as this would be desirable
but it doesn't make any sort of promise.

I think the question is what is the proper stanard for one RFC to
update another.  I followed my own understanding.  If that is wrong, I
will change it.



> In Section 4.2, the last bullet in the section is unusual.  That
> bullet add a new context for the entire list of bullets.
> It would be better
> for the introduction to the list to provide the full context at the
> beginning.

Actually, the last bullet in saying "these items" is not referring to
the items in all the bullets, but only those in the last bullet.

Still, this is confusing.  The last bullet shoud be merged into the third.


> Throughout the document, some bullet items end with periods and
> others do not.
> Use of the period is more common.  Please pick one style and
> use it throughout the document.

Will do.

> The last sentence of the Introduction is not clear.  After reading it
> several times, I think you are trying to say:

>   ... enabling interoperation to proceed just as if both
>   implementations supported only the parts of the protocol
>   that are being used.

I'm having trouble understanding that.  I think the problem we
re both having is that, except for callbacks, the client doesn't
support features it uses them.  I think we have a fundamentally
asymmetric situation and we keep tripping over ourselves as we
try to present it symmetrically.

How about:

As described in Section 4.4, two implementations can each choose  a
subset of available extensions, with the client able to use the subset
of the extensions that it is prepared to use that the server supports
as well.  Support for this common subset is not affected by the fact
that extensions outside this common subset may be supported by the
server or potentially used by the client.


> In Section 2.3:
> s/(not necessarily proper)/(not necessarily a proper subset)/

Will change.

> In Section 4.4.2, in the last set of bullets, the first bullet begins
> with "The minor version consists", but it should begin with "When the
> minor version consists".  The "so" following the comma should also be
> removed.

Will fix.  Your version is better.

> In Section 6, 2nd paragraph, I found the text confusing because
> "following" is used with two very different meanings in the same
> sentence.  I suggest: S/to following/to obeying/

I think I prefer S/the following rules/the rules listed below/.

On Tue, May 2, 2017 at 3:04 PM, Russ Housley <housley@vigilsec.com> wrote:

> Reviewer: Russ Housley
> 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 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
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Document: draft-ietf-nfsv4-versioning-09
> Reviewer: Russ Housley
> Review Date: 2017-05-02
> IETF LC End Date: 2017-03-08
> IESG Telechat date: Unknown
>
> Summary: Almost Ready
>
> Major Concerns:
>
> This document, once approved, will update RFC 5661 and RFC 7862.  It
> seems to me that it should also update RFC 7530.  It fulfills a
> promise
> made in Section 11 of RFC 7530.
>
> Minor Concerns:
>
> In Section 4.2, the last bullet in the section is unusual.  That
> bullet
> add a new context for the entire list of bullets.  It would be better
> for the introduction to the list to provide the full context at the
> beginning.
>
> Nits:
>
> Throughout the document, some bullet items end with periods and
> others
> do not.  Use of the period is more common.  Please pick one style and
> use it throughout the document.
>
> The last sentence of the Introduction is not clear.  After reading it
> several times, I think you are trying to say:
>
>    ... enabling interoperation to proceed just as if both
>    implementations supported only the parts of the protocol
>    that are being used.
>
> In Section 2.3:
> s/(not necessarily proper)/(not necessarily a proper subset)/
>
> In Section 4.4.2, in the last set of bullets, the first bullet begins
> with "The minor version consists", but it should begin with "When the
> minor version consists".  The "so" following the comma should also be
> removed.
>
> In Section 6, 2nd paragraph, I found the text confusing because
> "following" is used with two very different meanings in the same
> sentence.  I suggest: S/to following/to obeying/
>
>
>

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

<div dir=3D"ltr"><div><span style=3D"font-size:16px">Thanks for the review.=
</span></div><span style=3D"font-size:16px"><div><span style=3D"font-size:1=
6px"><br></span></div>&gt; This document, once approved, will update RFC 56=
61 and RFC 7862.=C2=A0=C2=A0</span><div><span style=3D"font-size:16px"><br>=
</span></div><div><span style=3D"font-size:16px">Yes, because it invalidate=
s statements regarding versioning made in</span></div><div><span style=3D"f=
ont-size:16px">those documents.</span></div><div><span style=3D"font-size:1=
6px"><br></span></div><div><span style=3D"font-size:16px">&gt; It=C2=A0</sp=
an><span style=3D"font-size:16px">seems to me that it should also update RF=
C 7530.=C2=A0=C2=A0</span></div><div><span style=3D"font-size:16px"><br></s=
pan></div><div><span style=3D"font-size:16px">I don&#39;t see why.=C2=A0 Wh=
at is in RFC7530 regarding versioning=C2=A0still</span></div><div><span sty=
le=3D"font-size:16px">remains=C2=A0valid once this document is approved.</s=
pan></div><div><span style=3D"font-size:16px"><br></span></div><div><span s=
tyle=3D"font-size:16px">&gt; It fulfills a=C2=A0</span><span style=3D"font-=
size:16px">promise=C2=A0</span><span style=3D"font-size:16px">made in Secti=
on 11 of RFC 7530.</span></div><div><br></div><div>Section 11 says that a d=
ocument such as this would be desirable=C2=A0</div><div>but it doesn&#39;t =
make any sort of promise.</div><div><br></div><div>I think the question is =
what is the proper stanard for one RFC to</div><div>update another.=C2=A0 I=
 followed my own understanding.=C2=A0 If that is wrong, I</div><div>will ch=
ange it.<br><br style=3D"font-size:16px"><br style=3D"font-size:16px"><br s=
tyle=3D"font-size:16px"><span style=3D"font-size:16px">&gt; In Section 4.2,=
 the last bullet in the section is unusual.=C2=A0 That</span><br style=3D"f=
ont-size:16px"><span style=3D"font-size:16px">&gt; bullet=C2=A0</span><span=
 style=3D"font-size:16px">add a new context for the entire list of bullets.=
=C2=A0=C2=A0</span></div><div><span style=3D"font-size:16px">&gt; It would =
be better</span><br style=3D"font-size:16px"><span style=3D"font-size:16px"=
>&gt; for the introduction to the list to provide the full context at the</=
span><br style=3D"font-size:16px"><span style=3D"font-size:16px">&gt; begin=
ning.</span></div><div><br></div><div>Actually, the last bullet in saying &=
quot;these items&quot; is not referring to=C2=A0</div><div>the items in all=
 the bullets, but only those in the last bullet.</div><div><br></div><div>S=
till, this is confusing.=C2=A0 The last bullet shoud be merged into the thi=
rd.<br><br style=3D"font-size:16px"><br style=3D"font-size:16px"><span styl=
e=3D"font-size:16px">&gt; Throughout the document, some bullet items end wi=
th periods and</span><br style=3D"font-size:16px"><span style=3D"font-size:=
16px">&gt; others=C2=A0</span><span style=3D"font-size:16px">do not. =C2=A0=
</span></div><div><span style=3D"font-size:16px">&gt; Use of the period is =
more common.=C2=A0 Please pick one style and</span><br style=3D"font-size:1=
6px"><span style=3D"font-size:16px">&gt; use it throughout the document.</s=
pan></div><div><br></div><div>Will do.<br></div><div><br style=3D"font-size=
:16px"><span style=3D"font-size:16px">&gt; The last sentence of the Introdu=
ction is not clear.=C2=A0 After reading it</span><br style=3D"font-size:16p=
x"><span style=3D"font-size:16px">&gt; several times, I think you are tryin=
g to say:</span><br style=3D"font-size:16px"><br style=3D"font-size:16px"><=
span style=3D"font-size:16px">&gt; =C2=A0 ... enabling interoperation to pr=
oceed just as if both</span><br style=3D"font-size:16px"><span style=3D"fon=
t-size:16px">&gt; =C2=A0 implementations supported only the parts of the pr=
otocol</span><br style=3D"font-size:16px"><span style=3D"font-size:16px">&g=
t; =C2=A0 that are being used.</span></div><div><br></div><div>I&#39;m havi=
ng trouble understanding that.=C2=A0 I think the problem we</div><div>re bo=
th having is that, except for callbacks, the client doesn&#39;t</div><div>s=
upport features it uses them.=C2=A0 I think we have a fundamentally</div><d=
iv>asymmetric situation and we keep tripping over ourselves as we</div><div=
>try to present it symmetrically.</div><div><br></div><div>How about:</div>=
<div><br></div><blockquote style=3D"margin:0px 0px 0px 40px;border:none;pad=
ding:0px"><pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:p=
re-wrap"><font face=3D"arial, helvetica, sans-serif">As described in Sectio=
n 4.4, two implementations can each choose  a subset of available extension=
s, with the client able to use the subset of the extensions that it is prep=
ared to use that the server supports as well.  Support for this common subs=
et is not affected by the fact that extensions outside this common subset m=
ay be supported by the server or potentially used by the client.</font></pr=
e></blockquote><div><br style=3D"font-size:16px"><span style=3D"font-size:1=
6px">&gt; In Section 2.3:</span><br style=3D"font-size:16px"><span style=3D=
"font-size:16px">&gt; s/(not necessarily proper)/(not necessarily a proper =
subset)/</span></div><div><br></div><div>Will change.</div><div><br style=
=3D"font-size:16px"><span style=3D"font-size:16px">&gt; In Section 4.4.2, i=
n the last set of bullets, the first bullet begins</span><br style=3D"font-=
size:16px"><span style=3D"font-size:16px">&gt; with &quot;The minor version=
 consists&quot;, but it should begin with &quot;When the</span><br style=3D=
"font-size:16px"><span style=3D"font-size:16px">&gt; minor version consists=
&quot;.=C2=A0 The &quot;so&quot; following the comma should also be</span><=
br style=3D"font-size:16px"><span style=3D"font-size:16px">&gt; removed.</s=
pan></div><div><br></div><div>Will fix.=C2=A0 Your version is better.<br st=
yle=3D"font-size:16px"><br style=3D"font-size:16px"><span style=3D"font-siz=
e:16px">&gt; In Section 6, 2nd paragraph, I found the text confusing becaus=
e</span><br style=3D"font-size:16px"><span style=3D"font-size:16px">&gt; &q=
uot;following&quot; is used with two very different meanings in the same</s=
pan><br style=3D"font-size:16px"><span style=3D"font-size:16px">&gt; senten=
ce.=C2=A0 I suggest: S/to following/to obeying/</span><br></div><div><span =
style=3D"font-size:16px"><br></span></div><div><span style=3D"font-size:16p=
x">I think I prefer S/</span><span style=3D"color:rgb(0,0,0);white-space:pr=
e-wrap">the following rules/the rules listed below/.</span></div></div><div=
 class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, May 2, 2017 a=
t 3:04 PM, Russ Housley <span dir=3D"ltr">&lt;<a href=3D"mailto:housley@vig=
ilsec.com" target=3D"_blank">housley@vigilsec.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">Reviewer: Russ Housley<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. Please wait for direction from your<br>
document shepherd or AD before posting a new version of the draft.<br>
<br>
For more information, please see the FAQ at<br>
&lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" rel=
=3D"noreferrer" target=3D"_blank">http://wiki.tools.ietf.org/<wbr>area/gen/=
trac/wiki/GenArtfaq</a>&gt;.<br>
<br>
Document: draft-ietf-nfsv4-versioning-09<br>
Reviewer: Russ Housley<br>
Review Date: 2017-05-02<br>
IETF LC End Date: 2017-03-08<br>
IESG Telechat date: Unknown<br>
<br>
Summary: Almost Ready<br>
<br>
Major Concerns:<br>
<br>
This document, once approved, will update RFC 5661 and RFC 7862.=C2=A0 It<b=
r>
seems to me that it should also update RFC 7530.=C2=A0 It fulfills a<br>
promise<br>
made in Section 11 of RFC 7530.<br>
<br>
Minor Concerns:<br>
<br>
In Section 4.2, the last bullet in the section is unusual.=C2=A0 That<br>
bullet<br>
add a new context for the entire list of bullets.=C2=A0 It would be better<=
br>
for the introduction to the list to provide the full context at the<br>
beginning.<br>
<br>
Nits:<br>
<br>
Throughout the document, some bullet items end with periods and<br>
others<br>
do not.=C2=A0 Use of the period is more common.=C2=A0 Please pick one style=
 and<br>
use it throughout the document.<br>
<br>
The last sentence of the Introduction is not clear.=C2=A0 After reading it<=
br>
several times, I think you are trying to say:<br>
<br>
=C2=A0 =C2=A0... enabling interoperation to proceed just as if both<br>
=C2=A0 =C2=A0implementations supported only the parts of the protocol<br>
=C2=A0 =C2=A0that are being used.<br>
<br>
In Section 2.3:<br>
s/(not necessarily proper)/(not necessarily a proper subset)/<br>
<br>
In Section 4.4.2, in the last set of bullets, the first bullet begins<br>
with &quot;The minor version consists&quot;, but it should begin with &quot=
;When the<br>
minor version consists&quot;.=C2=A0 The &quot;so&quot; following the comma =
should also be<br>
removed.<br>
<br>
In Section 6, 2nd paragraph, I found the text confusing because<br>
&quot;following&quot; is used with two very different meanings in the same<=
br>
sentence.=C2=A0 I suggest: S/to following/to obeying/<br>
<br>
<br>
</blockquote></div><br></div>

--94eb2c05f6a0e0fb78054e932ea3--


From nobody Tue May  2 17:41:42 2017
Return-Path: <randy@psg.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 758071274D0 for <ietf@ietfa.amsl.com>; Tue,  2 May 2017 17:41:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 UXzLH2sRWynN for <ietf@ietfa.amsl.com>; Tue,  2 May 2017 17:41:40 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 2A7F612954B for <ietf@ietf.org>; Tue,  2 May 2017 17:38:59 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1d5iJk-0005PY-TG; Wed, 03 May 2017 00:38:57 +0000
Date: Wed, 03 May 2017 09:38:54 +0900
Message-ID: <m2tw52ydsx.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Alissa Cooper <alissa@cooperw.in>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: Feedback on meeting dates
In-Reply-To: <A3093E7C-5B69-458D-854B-3E2B1AF3B726@cooperw.in>
References: <A3093E7C-5B69-458D-854B-3E2B1AF3B726@cooperw.in>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rK1uCognUcflQvmKKn7q8SuR6UE>
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, 03 May 2017 00:41:41 -0000

you did not suggest a narrower email addy for response, so here you go.

> moving the meeting to the week prior (July 15-20) or the week after
> (July 29-Aug 3) at a North American location outside of the US.

i have no problem with this.  worth a little difficulty to get it out of
the states.

randy


From nobody Tue May  2 18:54:48 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 AA31312869B; Tue,  2 May 2017 18:54:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 VQ3Td2AeiN9R; Tue,  2 May 2017 18:54:43 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (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 0D9EA12954B; Tue,  2 May 2017 18:52:20 -0700 (PDT)
Received: from [192.168.3.104] (unknown [124.189.96.14]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 2967722E253; Tue,  2 May 2017 21:52:00 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Last Call: <draft-nottingham-rfc5988bis-05.txt> (Web Linking) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4BECE06F-D3E5-4F9B-9DBF-AE9150942190@tzi.org>
Date: Wed, 3 May 2017 11:51:57 +1000
Cc: IETF Discussion Mailing List <ietf@ietf.org>, Alexey Melnikov <alexey.melnikov@isode.com>, Barry Leiba <barryleiba@computer.org>, draft-nottingham-rfc5988bis@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <40BA436B-C276-4280-B63B-BFBF17F160C9@mnot.net>
References: <149339514498.2963.17820948075543728710.idtracker@ietfa.amsl.com> <4BECE06F-D3E5-4F9B-9DBF-AE9150942190@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fh_N_WQG69LFg03_HXj7QSXmFoU>
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, 03 May 2017 01:54:47 -0000

Hi Carsten,

Thanks for the review. Responses below.

> On 3 May 2017, at 5:18 am, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> Review of draft-nottingham-rfc5988bis-05.txt
> Reviewer: Carsten Bormann
> Review result: Ready with a few issues
>=20
> (This is not a complete review, but in its present state might serve
> to initiate discussion of items relevant to RFC 6690 and thus
> draft-ietf-core-links-json.)
>=20
> This specification updates RFC 5988.  The objectives for this update
> are not clearly stated, but it seems to be based on experience with
> RFC 5988 as well as based on advances possible with the publication of
> RFC 7230.
>=20
> # Major technical
>=20
> T1: The draft does not take position what should happen when
> serializations allowed by RFC 5988 but not by the present spec occur,
> e.g.: ;type=3Dtext/plain (would now need to be ;type=3D"text/plain").

It assumes the general approach we take in HTTP; absent more specific =
requirements, recipients need to be permissive. Perhaps it would be good =
to link to <http://httpwg.org/specs/rfc7230.html#conformance> somewhere =
near the top...


> T2: The draft says "Serialisations SHOULD coordinate their target
> attributes to avoid conflicts in semantics or syntax."  To me it seems
> that this gives link applications such as the one specified in RFC
> 6690 the go-ahead to define their own registries of target attributes.
> The draft should take a position on this.

Seems reasonable; will do.


> # Minor technical
>=20
> T3: One of the major items of progress that this specification =
exhibits
> is that target attributes are no longer defined by the ABNF of the
> link-header serialization (which usually has two alternatives, one of
> which may be forgotten) but by the ABNF of the attribute value string
> itself.  ANBF tools usually can process ABNF rules, but not directly
> the bare ABNF "alternations" (rule RHS) used here.  This may also make
> it a bit harder to reference the ABNF from a dependent specification,
> as there is no rule name for that alternation given.

This is the approach we took in RFC732x; it more accurately models how =
parsing and extensibility are done.=20


> # Minor editorial
>=20
> E1: The abstract should probably mention that this replaces RFC 5988.

I will consult the oracle (Alexey) and determine what the current =
preferred approach is here.=20


> # Nits
>=20
> The spec seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but
> does not include the phrase in its RFC 2119 key words list.  (Pet
> peeve.)

Already fixed in source.


> s/ for indicate/ for indicating/

Ack.

Thanks again!


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


From nobody Tue May  2 18:59:57 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 78E36129B8D for <ietf@ietfa.amsl.com>; Tue,  2 May 2017 18:59:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.098
X-Spam-Level: 
X-Spam-Status: No, score=0.098 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 SViBypfVhMP2 for <ietf@ietfa.amsl.com>; Tue,  2 May 2017 18:59:53 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (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 B935412EAFF for <ietf@ietf.org>; Tue,  2 May 2017 18:57:21 -0700 (PDT)
Received: from [192.168.3.104] (unknown [124.189.96.14]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id A032622E253 for <ietf@ietf.org>; Tue,  2 May 2017 21:57:20 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Working Group Last Call -- draft-ietf-httpbis-immutable-02
Message-Id: <AA8A7700-C76C-46E8-A5DD-085D79C90A6C@mnot.net>
Date: Wed, 3 May 2017 11:57:18 +1000
To: IETF Discussion Mailing List <ietf@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bUaaPvWNxbbWd2EuGMz-Ja7kEOg>
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, 03 May 2017 01:59:55 -0000

Everyone,

Patrick (as editor) feels that we're ready for WGLC on this draft, and =
there are no open issues.

Please have a look at:
  https://tools.ietf.org/html/draft-ietf-httpbis-immutable-02

and raise any issues that you see (here or on the issues list). =
Statements of support or planned implementation would also be helpful in =
judging consensus, so don't be shy.

WGLC will end in two weeks, on 17 May.

Regards,

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


From nobody Tue May  2 19:04:50 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 1E0AF1273E2 for <ietf@ietfa.amsl.com>; Tue,  2 May 2017 19:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.098
X-Spam-Level: 
X-Spam-Status: No, score=0.098 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 j06CSCfxgtCb for <ietf@ietfa.amsl.com>; Tue,  2 May 2017 19:04:46 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (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 3256812E035 for <ietf@ietf.org>; Tue,  2 May 2017 19:01:46 -0700 (PDT)
Received: from [192.168.3.104] (unknown [124.189.96.14]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 01A5B22E253 for <ietf@ietf.org>; Tue,  2 May 2017 22:01:44 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
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: Working Group Last Call -- draft-ietf-httpbis-immutable-02
Date: Wed, 3 May 2017 12:01:42 +1000
References: <AA8A7700-C76C-46E8-A5DD-085D79C90A6C@mnot.net>
To: IETF Discussion Mailing List <ietf@ietf.org>
In-Reply-To: <AA8A7700-C76C-46E8-A5DD-085D79C90A6C@mnot.net>
Message-Id: <98C372E0-BD51-48F5-9CE4-BEA74E35F5FE@mnot.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0eT5vVlwkjh9e2r_Nh-np8SOJuw>
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, 03 May 2017 02:04:48 -0000

Sorry, bad mail completion. Ignore this...

> On 3 May 2017, at 11:57 am, Mark Nottingham <mnot@mnot.net> wrote:
>=20
> Everyone,
>=20
> Patrick (as editor) feels that we're ready for WGLC on this draft, and =
there are no open issues.
>=20
> Please have a look at:
>  https://tools.ietf.org/html/draft-ietf-httpbis-immutable-02
>=20
> and raise any issues that you see (here or on the issues list). =
Statements of support or planned implementation would also be helpful in =
judging consensus, so don't be shy.
>=20
> WGLC will end in two weeks, on 17 May.
>=20
> Regards,
>=20


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


From nobody Tue May  2 23:06:12 2017
Return-Path: <julian.reschke@gmx.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 51B0E129B44; Tue,  2 May 2017 23:06:10 -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, 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 pYTY3FlxiVmQ; Tue,  2 May 2017 23:06:08 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.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 6F38D12EA96; Tue,  2 May 2017 23:03:40 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.84.34]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LdpcB-1doAXS2gOx-00j42p; Wed, 03 May 2017 08:03:13 +0200
Subject: Re: Last Call: <draft-nottingham-rfc5988bis-05.txt> (Web Linking) to Proposed Standard
To: Mark Nottingham <mnot@mnot.net>, Carsten Bormann <cabo@tzi.org>
References: <149339514498.2963.17820948075543728710.idtracker@ietfa.amsl.com> <4BECE06F-D3E5-4F9B-9DBF-AE9150942190@tzi.org> <40BA436B-C276-4280-B63B-BFBF17F160C9@mnot.net>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Barry Leiba <barryleiba@computer.org>, IETF Discussion Mailing List <ietf@ietf.org>, draft-nottingham-rfc5988bis@ietf.org
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <94dcee17-bc7c-5b3a-e72f-fd827de90300@gmx.de>
Date: Wed, 3 May 2017 08:03:11 +0200
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: <40BA436B-C276-4280-B63B-BFBF17F160C9@mnot.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:nPREDXZrveWUI8Fw2/kNsIswuHumzgvDy3KP6T35VChxr3arRSP XwUHilp+bvpJtsoa2QSOaRD8gIrCFX2nol2yXZsxnHfj1HB7TkKsU3/+PBfsW5yFSkgRfYA W9/Hn3s+s2R1H7CchtKQw1yBpqw1tVI38rlyXDEi3LemL5OU4QzyHs9dBVaOJbaa0H9Y4JS dQClz6heBiqPYighJBZYg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:Nrg4ztrurxY=:v0o0U3lDV48ryNZDQynt/X uM+2X3rO36TZbnIr6kMoW4Yb/2ZoLdf4LAYCmkMKObvI+NSdislFXKv7qzP19lMoxhYffU7mw VX5Pw1zN67FDpUgtLXg0haTFG72zTtKPHgGHKCNon1mksS15ek3uNCtKBn3QFTKXphUo7HH4C A2yy9D9HDjenR+77JF57wB8qi5/aE3ohVaXUIU68dtNUZ3Q1Ta0HhUfrgkigdCLZxKKlsGFfi XnT7rXPNi6gTvMMAc52TKW6iO6tO7YXLe8p0bbd2XUTKEhiNAjCxf2nQB9uB5g1dnA0A4eUtV wXdpzoaY7EIABB0lRebnq69DWShNKgKBITxQgB5Eo+Uy+sNHABGESLnqO6A1VvN0J/o1EXV+I oPNCzJOXKjnmoEqKHWgFqq4T4e5koK7DioITz+V0ld+93x8Nji9e9TKaOl9WZqwkyYi/4uaQn zgLP0a0dlYyXl+rIpYnOGt162Mpvd/lJOcK06s/p0PAweMzwbXKzNNktQFTCRMoMB2/nrF6Eq xvthnlh9LCeBkTpv+up8cWRJFksYyO7rOc+qL00huEAE5isbNhnkAn5LKr5gU1cH9u/dSbrnv 5oT4FgMmNQ6b1omSNUaSGC1Iu6kE+jNDdRTYicRFRGcOcTUis+KFeacWcqzwc9SwIH+CucosA /m8rDpTRJa0Lwx6ilySVmKsL18ymDJlElSdqEVGUmpvHUotkRJWMaHNKUb1s0fgCXXc4xlXTX 6+7jNrKbf/s+saufNn0MJ0PbJ4bQpIQozdwavnJ9QwZJR7a308t8ulZM1mvNyfb4+Nb8ZkpeQ H1hUQdv
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8LBZe8B6c_Y-wYVasDWPRrc7Q5w>
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, 03 May 2017 06:06:10 -0000

On 2017-05-03 03:51, Mark Nottingham wrote:
> Hi Carsten,
>
> Thanks for the review. Responses below.
>
>> On 3 May 2017, at 5:18 am, Carsten Bormann <cabo@tzi.org> wrote:
>>
>> Review of draft-nottingham-rfc5988bis-05.txt
>> Reviewer: Carsten Bormann
>> Review result: Ready with a few issues
>>
>> (This is not a complete review, but in its present state might serve
>> to initiate discussion of items relevant to RFC 6690 and thus
>> draft-ietf-core-links-json.)
>>
>> This specification updates RFC 5988.  The objectives for this update
>> are not clearly stated, but it seems to be based on experience with
>> RFC 5988 as well as based on advances possible with the publication of
>> RFC 7230.
>>
>> # Major technical
>>
>> T1: The draft does not take position what should happen when
>> serializations allowed by RFC 5988 but not by the present spec occur,
>> e.g.: ;type=text/plain (would now need to be ;type="text/plain").
>
> It assumes the general approach we take in HTTP; absent more specific requirements, recipients need to be permissive. Perhaps it would be good to link to <http://httpwg.org/specs/rfc7230.html#conformance> somewhere near the top...

"Need to"?

"Unless noted otherwise, a recipient MAY attempt to recover a usable 
protocol element from an invalid construct. HTTP does not define 
specific error handling mechanisms except when they have a direct impact 
on security, since different applications of the protocol require 
different error handling strategies. For example, a Web browser might 
wish to transparently recover from a response where the Location header 
field doesn't parse according to the ABNF, whereas a systems control 
client might consider any form of error recovery to be dangerous." -- 
<https://greenbytes.de/tech/webdav/rfc7230.html#rfc.section.2.5.p.9>

So in RFC 7230 this is truly OPTIONAL.

> ...


Best regards, Julian


From nobody Wed May  3 00:10:58 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 AFD761200F3; Wed,  3 May 2017 00:10:50 -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-bess-evpn-vpws.all@ietf.org, ietf@ietf.org, bess@ietf.org
Subject: Genart telechat review of draft-ietf-bess-evpn-vpws-12
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149379545069.21463.6266932682208619112@ietfa.amsl.com>
Date: Wed, 03 May 2017 00:10:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HRix5j9vXnV7YFFHGFrsX-sclzo>
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, 03 May 2017 07:10:51 -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-ietf-bess-evpn-vpws-??
Reviewer: Roni Even
Review Date: 2017-05-03
IETF LC End Date: 2017-04-28
IESG Telechat date: 2017-05-11

Summary:
The document is ready for publication.

Major issues:

Minor issues:

Nits/editorial comments: 



From nobody Wed May  3 00:20:37 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 30BF5129C70; Wed,  3 May 2017 00:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 mSVpsloKrg6d; Wed,  3 May 2017 00:20:33 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (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 AC2A512E05C; Wed,  3 May 2017 00:17:47 -0700 (PDT)
Received: from [192.168.3.104] (unknown [124.189.96.14]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id B955022E255; Wed,  3 May 2017 03:17:25 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Last Call: <draft-nottingham-rfc5988bis-05.txt> (Web Linking) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <94dcee17-bc7c-5b3a-e72f-fd827de90300@gmx.de>
Date: Wed, 3 May 2017 17:17:22 +1000
Cc: Carsten Bormann <cabo@tzi.org>, Alexey Melnikov <alexey.melnikov@isode.com>, Barry Leiba <barryleiba@computer.org>, IETF Discussion Mailing List <ietf@ietf.org>, draft-nottingham-rfc5988bis@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <4D3EEE29-B653-4384-96AC-379E3A63B1F5@mnot.net>
References: <149339514498.2963.17820948075543728710.idtracker@ietfa.amsl.com> <4BECE06F-D3E5-4F9B-9DBF-AE9150942190@tzi.org> <40BA436B-C276-4280-B63B-BFBF17F160C9@mnot.net> <94dcee17-bc7c-5b3a-e72f-fd827de90300@gmx.de>
To: "Julian F. Reschke" <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TawQW-LyxXd_zzHeFaEAdYAApew>
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, 03 May 2017 07:20:36 -0000

> On 3 May 2017, at 4:03 pm, Julian Reschke <julian.reschke@gmx.de> =
wrote:
>=20
> "Need to"?
>=20
> "Unless noted otherwise, a recipient MAY attempt to recover a usable =
protocol element from an invalid construct. HTTP does not define =
specific error handling mechanisms except when they have a direct impact =
on security, since different applications of the protocol require =
different error handling strategies. For example, a Web browser might =
wish to transparently recover from a response where the Location header =
field doesn't parse according to the ABNF, whereas a systems control =
client might consider any form of error recovery to be dangerous." -- =
<https://greenbytes.de/tech/webdav/rfc7230.html#rfc.section.2.5.p.9>
>=20
> So in RFC 7230 this is truly OPTIONAL.

That's correct.=20

The attitude that we took in the HTTP specs was that there are so many =
possible use cases for HTTP, we can't constrain their error handling, =
unless it's a serious security or interop issue.

The problem is that many people want close compatibility with the error =
handling of the biggest HTTP clients -- browsers. We talked about =
defining a profile of HTTP for them; it's currently being written as =
Fetch (but not in the IETF).

When we do RFC723xbis, we might want to reconsider whether this was a =
good path to take.

Regards,

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


From nobody Wed May  3 01:00:19 2017
Return-Path: <julian.reschke@gmx.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 0D686129C6B; Wed,  3 May 2017 01:00:12 -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_50=0.8, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, 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 f1Vx1jlP8gJr; Wed,  3 May 2017 01:00:07 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 A30ED129B83; Wed,  3 May 2017 00:57:24 -0700 (PDT)
Received: from [192.168.1.34] ([5.10.171.186]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LlE86-1dgX5O0zZO-00b3AW; Wed, 03 May 2017 09:57:08 +0200
Subject: Re: Last Call: <draft-nottingham-rfc5988bis-05.txt> (Web Linking) to Proposed Standard
To: Carsten Bormann <cabo@tzi.org>, ietf@ietf.org
References: <149339514498.2963.17820948075543728710.idtracker@ietfa.amsl.com> <4BECE06F-D3E5-4F9B-9DBF-AE9150942190@tzi.org>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Barry Leiba <barryleiba@computer.org>, draft-nottingham-rfc5988bis@ietf.org
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <a6a4b727-5a01-8d8c-2c43-c2c51e668836@gmx.de>
Date: Wed, 3 May 2017 09:57:08 +0200
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: <4BECE06F-D3E5-4F9B-9DBF-AE9150942190@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:4UCMVIhVcq2cZntrq/Zhjb1axCUN6Yyf0FuNNdQPr1iUbh6lrcd yB0hH4Q5zK+ab+qCyZ2cX/5eDPhikkLSCsajNaZxH8qi25LlaGYpwtvFsiClR6arpcTr6nt 8Pg4yRdTPk+wnbRNpVyXQcApeMgCVRHX045PVnA3LCsQKOPTDLwOq1YaEXXLUUJgF7s+zem MpsWjR4vwCzxMPfcCX81g==
X-UI-Out-Filterresults: notjunk:1;V01:K0:OAQAN3Pfgw0=:Lga/fac1ok1Ju4Rl9LzbAQ Ayaj0soUubzXkUdWDyYMVPb1unrt3OlrWx3vcVspBfpSupKoGruDmwxxkoUSjy09lgsuzFJlV bf1gyWGyK8Igtf46Yu17YfcAl7i32JvJ30M1VzZQq5VYkVjTL8Phv9A0UEHOCrfbHBDDWmQR4 MmIi7vld1fKlRLLY1EDloFj8soIWkf5MQe2F/Xy9LrBMhbCgNKGT9adW2YpC5eWE0Aug8zB2c +vdjgPqwKFwPtprXXS9tRD1Gw7LMB7h+hLsyyj0ZIp7ICwbxa58syp4m9SZyDWNfs0XjWDmUq TRn0booVnI9NRofSr0nBmAPh0ZZtipwAhkn76UPTzrywj2w8ETDsaTTD5sFtiJnCfvc7d4XAS fxdRcgk+T1SJDlTJ4xkGHG8mMHTYOVU6yISX/YXfpDnefD4NlDjGdLW3wumQv3xzauBdmWgV6 974L53GbnoxiQwxj+FhZJKFn4z2Tw4Oo//U0T4FtX7Q5dxUkVAb8+maAd0Aw90TFAXfqdSec9 4oakb1ZpGbpj0GzROkNmdDNBwUybmHEFCf8u1h60BfMcVn5SuJUN7VsNCdzuiE2NpCYuorkBW 37Wjw2pSDDvJeXX2NDhPmPyQBqEKm9AHTgGq78xWXBkIpQwB/d6SNiWIErNhEQ8nCvBOk70Sa kzYGUyEMwdHDNZfwdgprlPxwrGGWETnlqs+Y4bUl1mvlAo+TW9CvzflSSyTT5WlPytF2/sTXP FjEQJ8dDW/dHokU5jRBUNz5ayu3mB+fxOd2HdGB6986EKM5qr8HXQ4AfF9yVjGay1dslbCs4z bzdobHg
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FVaY9AxLYuxtwfjaLe4Xur5IYSU>
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, 03 May 2017 08:00:12 -0000

On 2017-05-02 21:18, Carsten Bormann wrote:
> Review of draft-nottingham-rfc5988bis-05.txt
> Reviewer: Carsten Bormann
> Review result: Ready with a few issues
>
> (This is not a complete review, but in its present state might serve
> to initiate discussion of items relevant to RFC 6690 and thus
> draft-ietf-core-links-json.)
>
> This specification updates RFC 5988.  The objectives for this update
> are not clearly stated, but it seems to be based on experience with
> RFC 5988 as well as based on advances possible with the publication of
> RFC 7230.
>
> # Major technical
>
> T1: The draft does not take position what should happen when
> serializations allowed by RFC 5988 but not by the present spec occur,
> e.g.: ;type=text/plain (would now need to be ;type="text/plain").
> ...

FWIW, it's allowed in RFC 5988, but there's a five year old erratum 
about it (<https://www.rfc-editor.org/errata_search.php?eid=3158>). 
Unfortunately, the status is "held for document update", not "approved".

(And yes, there's the orthogonal topic that people are not aware of 
errata, see my experiment to improve that: 
<https://greenbytes.de/tech/webdav/rfc5988.html#header.link>).

Best regards, Julian



From nobody Wed May  3 02:32:41 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 F0C4212954E; Wed,  3 May 2017 02:32:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Jonathan Hardwick <jonathan.hardwick@metaswitch.com>
To: <rtg-dir@ietf.org>
Cc: draft-ietf-rtgwg-device-model.all@ietf.org, ietf@ietf.org, rtgwg@ietf.org
Subject: Rtgdir early review of draft-ietf-rtgwg-device-model-02
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149380395894.21423.18366134547138249926@ietfa.amsl.com>
Date: Wed, 03 May 2017 02:32:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5WTa20bawdVtQvcD6m0s4dZITqA>
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, 03 May 2017 09:32:39 -0000

Reviewer: Daniele Ceccarelli
Review result: Has Nits

Hello,
 
I’ve been selected as the QA reviewer for
draft-ietf-rtgwg-device-model-02.
 
I believe the draft is well written and quite easy to understand, I
just have some minor suggestion that might be help improving the
readability (mostly for non subject experts).
 
-	Title: the title is not very clear, while the abstract explains very
well in the first sentence what the goal of the draft is, what about
changing it into: “A logical organization for network device YANG
models” ?
-	Introduction: You are referencing an individual draft. This could be
a block for the draft, but most of all does it make sense to have two
separate drafts (in two different WGs), one to say the value of
organizing YANG models  and the other one defining a logical
organization for the models? (maybe too late for such change)
-	Introduction: this sentence is a bit confusing: 
“  This document refers to two new modules that are expected to be 
implemented.  These models are defined to support the configuration 
and operation of network-devices that allow for the partitioning of 
resources from both, or either, management and networking  
perspectives.  Two forms of resource partitioning are referenced:”
                Maybe a modules/models mismatch? You start saying that
the doc refers to two MODULES, then you say that MODELS are defined
and the list two FORMS OF RESOURCE PARTITIONING.
-	Intro: “    Should structural-mount/YSDL not be available, the more
explicit tree structure presented in earlier versions of this document
will need to  be utilized.” If it was described in previous versions
of the document it is no longer available, or ?
-	Scope: as I got it while reading and as it is confirmed in the
draft, the scope is “limited”  to physical and virtual switches and
routers and not devices operating at the lower layers. Since you say
“we consider network devices that support protocols  and functions
defined within the IETF Routing Area” I would expect it to cover also
lower layer devices. 
-	Section 2: Section 2 and its subsection are very clear and explain
well the concepts but it is not clear where the list comes from. It
partially overlaps with the “overall structure” example above but at
least having all of them in the overall structure plus some others
(provided as example and not analyzed in the details with dedicated
subsection ) would help.
 
BR
Daniele  



From nobody Wed May  3 03:23:51 2017
Return-Path: <fredbaker.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 F18BE12947F; Wed,  3 May 2017 03:23:41 -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 AzKKcCIbTyuc; Wed,  3 May 2017 03:23:39 -0700 (PDT)
Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F58F1294A4; Wed,  3 May 2017 03:21:21 -0700 (PDT)
Received: by mail-wm0-x244.google.com with SMTP id y10so11630432wmh.0; Wed, 03 May 2017 03:21:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=rZbdHYtfYjfsXJIXrrLvj38ladSzLZBOFy7InbpDnxQ=; b=F7b3kkHpNy7IXCbQ2qQJxthR9SRwdoscj0uCa8GpISDiT3TOMg24F3VOoMQurGvlOb jWK151kxPuWUTDFSYrxXz2NXfmRpCtSwdm1fMYrWRpdJO20409CE40aR64bJMGwy5boF S6Xs+npQj53YBTs3G/KeruUuEZF2VKdTx8R49LJ4+31WuietbVH0A48LLpfzaYiZdikv rFkje0uPs0dNgHKDBHmzB61hiu8KWhqSWGz5s5mF/77+nDm+Vsup4MwANA+k2dTMhZU7 SF2ag8bVd0csuJYlL+6G6Dm51DYe6sLa+hSp/KQEtDBj8I0XBmn2wiMq6zCxp3BTsJvF GNuQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=rZbdHYtfYjfsXJIXrrLvj38ladSzLZBOFy7InbpDnxQ=; b=AOcT0Ur3a8mZu9lZAltTQihE0U38f5otkurFrB0oGM5Naq7QPFAuCr1Mrw22Jg7N+u OZTcvZystOM4p74Wlta+gP1Ox5as9Vv3ABdP2OU11Irs46r8fqpHsDlNRK+14DMr+VhX 9AiNQEpHlU8OV1JTLDKN4B57LBYqQO37S7ar0GvOXsiIUO971l5Ln1i0N9eLEsPlrk+4 E33z5EhTrdZBEps2US9xrtGg4aAv/x+VTdf2MIFpCujthDBKfPiMsqeQzeYtHsVFZcIN yLpYNiS6YT+OQF0j63qsTo7iz8+mZDaiqymAhIaXjbOOEAtQtGWLmhsHWjm9IKFODccm fGmA==
X-Gm-Message-State: AODbwcBI65MxrjiGO01OyY0CU2aCLk1vxLpCgZke0p0ler653gIN18m6 0qNBS89cmlXLZg==
X-Received: by 10.28.193.138 with SMTP id r132mr221724wmf.87.1493806880047; Wed, 03 May 2017 03:21:20 -0700 (PDT)
Received: from 211.66.20.149.in-addr.arpa (211.66.20.149.in-addr.arpa. [149.20.66.211]) by smtp.gmail.com with ESMTPSA id u200sm4395602wmd.16.2017.05.03.03.21.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 May 2017 03:21:19 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [v6ops] Opsdir early review of draft-ietf-v6ops-v4v6-xlat-prefix-00
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <8392FFDD-AA72-47B6-B689-1EE2C8967A2E@cisco.com>
Date: Wed, 3 May 2017 06:21:14 -0400
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-v6ops-v4v6-xlat-prefix.all@ietf.org" <draft-ietf-v6ops-v4v6-xlat-prefix.all@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B40D28DD-B8F9-4BA7-A8E1-61AD390829D4@gmail.com>
References: <149373185172.9923.9255526962045750289@ietfa.amsl.com> <06e8313e-38ed-7ea5-76f0-db2f6352844e@gmail.com> <8392FFDD-AA72-47B6-B689-1EE2C8967A2E@cisco.com>
To: Joe Clarke <jclarke@cisco.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WZkQwYqsbjygu5yEbHk-1tjSZqw>
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, 03 May 2017 10:23:42 -0000

One of the issues with a document that updates another document is that =
it is supposed to say in the abstract that it does.

> On May 2, 2017, at 7:06 PM, Joe Clarke (jclarke) <jclarke@cisco.com> =
wrote:
>=20
>=20
>=20
> PGP Key : http://www.marcuscom.com/pgp.asc
>=20
>> On May 2, 2017, at 19:01, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>>=20
>>> On 03/05/2017 01:30, Joe Clarke wrote:
>>> ...
>>> NITS:
>>>=20
>>> In your Abstract, you mention RFC6890, but this does not appear to =
be
>>> an xref to it, and it should be.
>>=20
>> afaik, the RFC Editor style does not allow xrefs in the Abstract.
>=20
> I've seen some that do (ostensibly).  But this if this isn't required, =
it wasn't critical.
>=20
> Joe
>=20
>>=20
>> (Also: draft-bchv-rfc6890bis will update 6890 soon. I don't know =
whether
>> that's relevant.)
>>=20
>>   Brian


From nobody Wed May  3 05:54:06 2017
Return-Path: <phil@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 91A741294C8; Wed,  3 May 2017 05:54:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.022
X-Spam-Level: 
X-Spam-Status: No, score=-2.022 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_HELO_PASS=-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=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 RWksgt7WIRKx; Wed,  3 May 2017 05:54:02 -0700 (PDT)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0091.outbound.protection.outlook.com [104.47.42.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DB281294EC; Wed,  3 May 2017 05:51:28 -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=1fYL5aMCLgRxvROUAsm7o/fdkG4GtsJyV+x8tY7MryI=; b=JZV9cZCn4prVGq7BVYVFuVkXPz2i7F1eB8DJeROx6s1HdNBDXuU1CR1Wv5Qdbi09UATZveUlnoozv307V9ja4krulEimcMp3LXLHVFc4LLWNal/DvPS5BSvFMCXtKEEhhtCjEhKM8+oJhia8yXIl4PCVQjlx+NU8bLrD4/r6oKE=
Received: from DM2PR0501CA0015.namprd05.prod.outlook.com (10.162.29.153) by BN1PR05MB043.namprd05.prod.outlook.com (10.255.202.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1075.1; Wed, 3 May 2017 12:51:26 +0000
Received: from CO1NAM05FT059.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e50::207) by DM2PR0501CA0015.outlook.office365.com (2a01:111:e400:5148::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1075.1 via Frontend Transport; Wed, 3 May 2017 12:51:27 +0000
Authentication-Results: spf=softfail (sender IP is 66.129.239.12) smtp.mailfrom=juniper.net; ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=fail action=none header.from=juniper.net;
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.12 as permitted sender)
Received: from p-emfe01a-sac.jnpr.net (66.129.239.12) by CO1NAM05FT059.mail.protection.outlook.com (10.152.96.177) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.1.1019.24 via Frontend Transport; Wed, 3 May 2017 12:51:26 +0000
Received: from p-mailhub01.juniper.net (10.160.2.17) by p-emfe01a-sac.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 3 May 2017 05:50:56 -0700
Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26])	by p-mailhub01.juniper.net (8.14.4/8.11.3) with ESMTP id v43CotRd028026;	Wed, 3 May 2017 05:50:56 -0700	(envelope-from phil@juniper.net)
Received: from idle.juniper.net (localhost [127.0.0.1])	by idle.juniper.net (8.14.4/8.14.3) with ESMTP id v43ComaK047821;	Wed, 3 May 2017 08:50:49 -0400 (EDT)	(envelope-from phil@idle.juniper.net)
Message-ID: <201705031250.v43ComaK047821@idle.juniper.net>
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>
CC: Brian E Carpenter <brian.e.carpenter@gmail.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, "draft-ietf-v6ops-v4v6-xlat-prefix.all@ietf.org" <draft-ietf-v6ops-v4v6-xlat-prefix.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [OPS-DIR] [v6ops] Opsdir early review of draft-ietf-v6ops-v4v6-xlat-prefix-00
In-Reply-To: <8392FFDD-AA72-47B6-B689-1EE2C8967A2E@cisco.com>
Date: Wed, 3 May 2017 08:50:48 -0400
From: Phil Shafer <phil@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:66.129.239.12; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(39410400002)(39400400002)(39850400002)(39860400002)(39450400003)(39840400002)(2980300002)(189002)(199003)(9170700003)(8276002)(54356999)(50986999)(2950100002)(6916009)(356003)(230783001)(8936002)(229853002)(8676002)(5003940100001)(305945005)(54906002)(48376002)(189998001)(558084003)(50466002)(110136004)(5660300001)(6246003)(38730400002)(7126002)(77096006)(478600001)(53936002)(4326008)(7696004)(106466001)(81166006)(47776003)(105596002)(2810700001)(39060400002)(2906002)(86362001)(1076002)(76506005)(53416004); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR05MB043; H:p-emfe01a-sac.jnpr.net; FPR:; SPF:SoftFail; MLV:ovrnspm; MX:1; A:1; PTR:InfoDomainNonexistent; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; CO1NAM05FT059; 1:9UBspxCGDjhqUC2NpiasH8xQWiuAckUwIdI0X1byTY1Fop90dqX/jFUUlXIIxcSAhZMsferxozIZD0HVex7r0aKgIoIICT/W/0rkPvwkEmSkO+OxmFn9KgjNfNeNL9On6xuqvB42zN6WRHb/83/sekbnWDXcRDiIsDMhe7CpXDnKoyy46kv5358uJa+tuagUjuwNDydLDelXGi4wqr8oK+kDmoOQR1uHJ8IGOtktSlI1F5E+uyI7Ne8saV2k13z2r9hCjLKac87SDODCLMWCVnG8D/lbdrDgOlzERJp7S0xKGMVwiaPee673Fa8lOsdnFZ7EsymLdjaR08l5mxy3oi/CTrd2V4XaRpdxShLYVfx8UwrO5KQZ+OefBEd5knS/r+MxY5knxFEOjKhAlQI849Z9B16UOY44POvzEIWW7Qd+YZZ55R7vB0GJ4ntNaePrv0GhJGrQF5v7hxxv9EK5kVtiXz2KUTGpgDOadTT3ov+qdea8ZTqDndHn9L4nnbmt0TcUoRUyg2uNuO2OcTKk3wyVgZgfW+QCTN5WfC2WHkwmAVY5M6uCWn9kLU1skAfIJHOhsaP+hw6x9+394WDzWfzAQ9gkduVw3w6Kxty1I1PpcJ/Dx8sltE9czEh1y+qw
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: cc6a2b48-f8c2-495c-6d78-08d492231c8e
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081)(201702281549075); SRVR:BN1PR05MB043; 
X-Microsoft-Exchange-Diagnostics: 1; BN1PR05MB043; 3:2OxT0DAoW4ZrkK4/Qs7VgtODJQt8lKPjRYNyPlhmSaL46+XQFKDD4MbV67N0N01TxhXyxDa47TFZdvg8IZ8U/TZ+G3MTO74mfEKlifIMiTSUJ8hTTkCwf7eD45IUiPvyjh11EMtYLE79mQlaPdywfj6jfn398KCUt7VxxwoIBMrq4oSzzxKHYAt4F3fEhB/68hAN7owEVdfPp1v796lWAKfub8wmksiHg5nRD6Kg0BQbUADuq3XtZNkSDvpKHgbTT+cTzyKuC/jDS8VZa4iv7nOxedyjkIziYKJj9meXFSeAWE99cEvv2ABIfqbT6YwLiJwihG2ITqTIyHJq9K9jjxAJrfshL6sXVPR4aJ5tK8H0CBBWjXv9FySa4O77242N9HwFNbtO6N1NIhp5nquRiI37HhLAgpfQtvgijgeEBm2B1M8zzR6CdBek4aRBxFVgJA3uzZzJX8avUnnojrxMKDu/+OfIGaz24G8u3ybES5NVFoqltjg/R1r6rhSMRpGB
X-Microsoft-Exchange-Diagnostics: 1; BN1PR05MB043; 25:cQkTAKaEnCTj0ey/p5XRAEXAaYokYOb3s976JqU52dKtgBzYkMdioeViZg7mG+eCW0zlmxd9+s6DbFeQEWSDYphziEsQbIh1e+eYnF+jXwnW/hZGwzM4tyQ/bnR4r7Et4Qji+OtR53zAhqBR6i37wTvJRcy+YZ/Mgu4W5rTR3u/5JQTS0ksWu+UqxzKnet/cDkfPK2qsa2WdDrvKRCIcaoy5F90uhE7takYEPst9VhvztzGfZA6z9xvTmeCJfwXMZhwO8Xg/iya+VChVISdYj9J9TQEFOXfp8RzuEYwAZfc4b3qvbuOyRsJWvZkHcQPuoX2axtvtHSix8NbD+b73sSGvqg6ImP7Ddaiy7b942vKVopDHGF7q7McRGIQoU/BTgDwT4gt8Yr0Yoyn7rnl5vXh/bbCrUX3GWuO8ZR9DnQSaCl7Zx3ZIpq2bZdnq69tBKvqVaQ7IKNgcWIj/iK0munSOTxs4mInqLjTKFjeHQFQ=; 31:D5BAPBJwzGC8FszN8leu2fxmk1hkup3CwYEKVl6P4BryHKZIBQAdLaYkhW8cahPwjjkMmPztQhltKpT0pZFRTzMvwHNkb9gnSTCKD/cQQ7iS2oqpnuRipoJuPcpIEUwa9MyeahEQwPpujMiUEjo/OtT3MsynZnCor2JPZfFk0RzAfXuHt8Dwd2KLfgiqRgqcUVZP3gRCteh/A4d1L2WiDdUdszMFi/cCfcp8wMMpXa60B6vvIN9aA7LUaMsWZHonKSSOPVeZuOUCNekF7DqxSlEtzU9hI4F0uRK/8/Ydvq4=
X-Microsoft-Exchange-Diagnostics: 1; BN1PR05MB043; 20:Sa4xmtqRtAup668Utk9HhcrOJspD9ir6oLRKE42PovG0eoNGuBPyZCV6NVQSFS71WDxC7sdbMFjGtaegG+KRXkFXmM1imE4S/fkHM1Ahd2kAx8QsDILE7GCG1vAa4Atw+vx28IN4n2+KNT0e03yDSvbmD023gDIFk66eOjZcg0wugOpGL7iu/KzbrUshhw8U+Fo0vp3V+rXb+2L3XPc3hhPmJKP7zemGZzxPo5MYgF1o1SG5RFHcRniZ5Y8DiH+1bD0mI3x1u9kCLZVq4L9WqcIhtT4oJMbZX34tsI/vRmyTpRlvgsLcu/Dne1CjlKxN5gcIgnJ0UbwpPYyy+An+3tEYAtQpzdthlFtAWsw4q5qL1faycnDEcSo3P76Ddpg3ZeunXeDyD2zUOz/fJBKgOK1ccxQ10hSKN/JBi83pNnibNw4gIzsfWyzM0QKuoDbRpXv12uvTweT/xUqDRF8iyZYcZJed7Gavfr96kwRwYjMDnhG9ErjkhDmHumppgVEh
X-Microsoft-Antispam-PRVS: <BN1PR05MB043AA0C2FCC74284F47B22EC9160@BN1PR05MB043.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(13018025)(13024025)(13017025)(13023025)(8121501046)(13015025)(5005006)(3002001)(93006095)(93003095)(10201501046)(6055026)(6041248)(20161123564025)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123558100)(20161123560025)(6072148); SRVR:BN1PR05MB043; BCL:0; PCL:0; RULEID:; SRVR:BN1PR05MB043; 
X-Microsoft-Exchange-Diagnostics: 1; BN1PR05MB043; 4:aH8u1a/2yKNgnaPHnAYG+UiTdXf1kHcNqngeEYysOxYevstH0JXQIjR9hUG3MCiaHuBvd+3XsJMzWWE0ZrXzYl+iOZt2xnK97ncdqMd1iaUaRTW2VZxoNeaYMGSXO27y8nOaZ3xvry17DCIKI/YtKQEufJkTrLaubABzymQhEqWs5ZMBZjgTp9OKH4sga8kfWrXtd/hgvuPnzvbNKCbCDdcKsxmxXacqzHi+wYi4i1/eXQZjhVhxvoPNensWiAOlBwaE+Mgt/hfMDByxqeYd+iATiOxpzIVmtKpQakaLLxL0byGDobHVHy9jSz/PO+8U6AqfYs/R3TdZbEcukd9rLyYZkAOxKBOPYUx0+nUqxH/kpS7jKNQKsiQUEhcgHpcZAp/hZf1pvuxk8PMTSjaluXWnqhnbtBeP3EzHlWxVIAnpZcXCeEoWGC91kudnKbvGfWL+/yjDJ6uPJyaiOV001ceN4Z/148nW74i8kLhq9Q0K9P63/J4Xw0wiE1/JY3SLyJxjHATu6XyUjfQ2lFGOh2JV0t0icnMKwvK4rqeEdBhSGRBhe+8M0wm4Ie+uvzasOSyxbwxmOWeHNC8FaezKAjBrjB8Ar6Bbt6Pdv1aLAvVYQKS53PlnGYrDfBArd8hY/s0YV1ZCc1txPOOU0bjEeyXUapc9rmVMZBJe7Yt0+R8SHeatDaFxAoCty51Y+LA0jChF13v6j4skHtBTUFnIq3CaC/lnDP2VOQ3SurGRkNGk3urQPa6ATbpwHlnfHW9oSXc9BXa3xg8UPxGWF2kfH3H5FwBXtzRAH4Ew3rZZ2EBAI0V6MQB60K/ppqywP9vq6cvMlstWMSqKqhxzXqmSkzkQ4yQ5osuOvoHTngGxdp7xOKIITmDr5oIlZoGmS7WPboekJzdsqfLdofMJqnp/ng==
X-Forefront-PRVS: 029651C7A1
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BN1PR05MB043; 23:iANeDwwLvikuXy8M60fGvClYEO8MHcJwOe/Nf5vJe9?= =?us-ascii?Q?LcHe4faUP0+o9TKmBo7jMrZnjKxRJAfveAESrHvR1EVif9YQA+uM3qfQglQf?= =?us-ascii?Q?IX3eKBUJkJ6pcADMS4hCv/W0YS0KIdicDz31pnxT9hsKEVQ6eP8lH3eFMKEX?= =?us-ascii?Q?kEFgDajKQ5pmmX0qjp36XvH+6BoPWzdjPdV73VXjF6R3q0BTZDvNoCZo5w0j?= =?us-ascii?Q?qu8q1/ZLWdN+ezFNKhogvvCu4+eWFGU24f5P/2mI9xvHjawRRageMD3ZBVcl?= =?us-ascii?Q?kQXZ7UG6BfG1mapuQ17b0ncgFZgJRpeOg9Bq+lZI4YJt0NcFED6oN60qjtit?= =?us-ascii?Q?isf7z/XflbfoTB6GvJUKyAUuZlWuEXlpJg2alYvKroImApeVNd+T+dcfZPMa?= =?us-ascii?Q?YybBUT0r/QYSRPoZrAW0YqCnyG0nzP6zNTkchPCxthJnluZ7zZNceNPXNuCs?= =?us-ascii?Q?dQfTh14fhuneMSvgd4gOP0gP6iSTzOoeVF/q0rrKMEzP+bEznys74HVq2cty?= =?us-ascii?Q?4DxAtrRUYCRCp7h8fqLqjcqJPzwfwN/qsvAadq+s2CYuhw0B+WaRl3JTlLJr?= =?us-ascii?Q?iOebE4uy2kGEsFnnAwJDnyIGwGJPCIDaZUyIkZtMhoNWxgMjEqi+49kSJlrr?= =?us-ascii?Q?yG/DinVW+Ym9dDRhor97xB71/OGVBSj71TlaEgXplVmHtkdx8PTZpH6wFxP4?= =?us-ascii?Q?WUcXaz2fQJkqcRBIbjHo2spkLsoOXHDjqJVQDF6wNTMLqhqRoFUL7kGEx0aW?= =?us-ascii?Q?pBdgRmwlYhqiELJCxzWgFRykGm5wYWgq0dKBs/zgQfbHKkSmAeFhftb09Hn1?= =?us-ascii?Q?upX5KQVinnx65kGXZdUwQOhXKTd3wmW3aPyusOkWzSo7L+jBJ3TVDYhDcy8M?= =?us-ascii?Q?TQUCHdSmJZUlXRNFCGyN/1hvuh94u5llc0zCE42H4Li4oSsWy5w2cuA3Rdqp?= =?us-ascii?Q?AnhipSuSeoU6Rfrb2F+VdWdOgnu9OVUZ25fu8hc6NI5IujSwvy5aiAef4Aiv?= =?us-ascii?Q?NCsGud3ec/EGCvH0SckPhD0Zqu/UojWkBjUYyzK4+zlTThopHs1BCNIE/99R?= =?us-ascii?Q?bjdriG/+W0A5zK0hVQZJjSN1ELCpmHhgFOG6w08FGQaSu1BKZIUkwcOBhMPv?= =?us-ascii?Q?Y1hZXpkZGDH2xsuh/t6IpVf+5xwNgBcMDks4hrUmUG8OBt+0Zzw+G6ZKg5Gz?= =?us-ascii?Q?XxyVoNIuAPIQ+M6Yh+Uy3w+i/zjw1aiTTwSiDQieCLWLvy6KefqLINcQ=3D?= =?us-ascii?Q?=3D?=
X-Microsoft-Exchange-Diagnostics: 1; BN1PR05MB043; 6:2pkJaFSbqdyWtxHvIqgRia8RIhgBii4fYNjIOTmXFGwyZZaN2jki9X4cW1RRqwf7237gZfYlPdXQZK5C/FGCaEcU8DcnjNqhI5Uhsbj3Reouf6dT+RP0Ywjg28KwjBBQp15OvbHex5KOLlP25lY8UIRFUbBtkJor2P6wBPw1H/Wn4hXbN6smviX5NEnBoPHs/545M42c6TSGmbWFlEaeHJfKFunUN5cUC6NdQKwopRRYnj976dSFfhfRil0PDJ/83w3nphEhEHjcXK2UPyQESGPsXk3YUi5uZ15KB4BjWRv16w8EsXjYnSI3K6S9w4oLZUzcZAcbdAKwZFRl1xLTnsbUq6PoQAx/UGPdpaR/8Uq07tzjTTCGTtcxL41uEA/Tu1WqW6qQjtNcBPyHeNxq1Kw++v3M+EJzMEIUnxcZqx0g7VBqm7nX45fOpF2qKiSxlX+B8S4d9qxsx1ZQVLQBJUEDOUS3i8vSSbnHKmFHPppbpMA39ahQitkhv2ZCnFwbWPcInzD2BDLcTXlysvbrdGOl4F5LMLWUwpjE1wgAT/A=; 5:ncUMV+RAEuW7KcfjFifWExGeT+HT4asZ4ccIpK1BewSKZtaT6viAqEF4X61q/USJbsjgOA/qv0mpz3lFyOyPlDU+Nrrz5XQ6q/WcTWL5WsC67AkC20abRzwu7g7bzkckGSd3WR1oAv4sPz1tCI+waQ==; 24:/rj7y3flFwI0dMSepps4ccPQMFhWVVLDZED6ujAl/gJC6v8Fa9BDuSoFR0CFoZH4NWA5CRLZS3JpjamAbYc6/fZ724XD0CZ7ppLxFhfGL78=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; BN1PR05MB043; 7:9vM+/30Wt8Sd9ONIASuXZKnUFPu5ICEy+TeZxyGf730hqXW17NdmKqaHiHJLEbhYOH7FZd7f47DYv/ZG81ER02ZNka52cNOAEbpZoLMQLfVVsx1OMOOCMe8cowHFWH2wwgx7uZCLTDLQj+uTWziutn7HRQfpje0HkXACOqtVc4/RvrB+NsuZtfJWX9sdQl8B5y/OSMIwyy4hi4z4mct4SQAx7OsivGUj0tI11HQG7no0PfA0z8zfThkCtTKHDjPfpv/QTu3wGt4tGkidvOusy0PhB3xQQ3qN/3f0eq5tuoFnb8Cx+EHy1qnDjdkrVsxY6uZEic6N5cX9chKz7+xjcg==
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 May 2017 12:51:26.3997 (UTC)
X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.12];  Helo=[p-emfe01a-sac.jnpr.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN1PR05MB043
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/l_kxNEv2oLVDJXgCq764k7pLBGM>
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, 03 May 2017 12:54:05 -0000

"Joe Clarke (jclarke)" writes:
>I've seen some that do (ostensibly).  But this if this isn't required, it wasn't critical.

idnits certainly complains about it.

Thanks,
 Phil


From nobody Wed May  3 07:54:21 2017
Return-Path: <stewart@g3ysx.org.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 9AF471294D2; Wed,  3 May 2017 07:54:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart@g3ysx.org.uk>
To: <rtg-dir@ietf.org>
Cc: rtgwg@ietf.org, ietf@ietf.org, draft-ietf-rtgwg-routing-types.all@ietf.org
Subject: Rtgdir early partial review of draft-ietf-rtgwg-routing-types-02
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149382325961.21410.10726283274929738928@ietfa.amsl.com>
Date: Wed, 03 May 2017 07:54:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PxaFOK86hUqod-ySXvvJ5dXJJjU>
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, 03 May 2017 14:54:20 -0000

Review is partially done. Another review request has been registered
for completing it.

Reviewer: Stewart Bryant
Review result: Has Issues

Firstly I should say that I am not an expert in YANG, hence my
suggestion that you may wish to assign an additional reviewer.

However in reviewing this a number of questions and issues arose:

2.  Overview

   This document defines the following data types:

SB> Accessibility note - the order of types seems random. It might
SB> be more helpful to the reader if they were, in a systematic order
SB> for example alphabetical and/or dependency order.

=======

 router-id
      Router Identifiers are commonly used to identify a nodes in
SB> s/a nodes/nodes/

=======

   route-target-type
      This type defines the import and export rules of Route Targets,
as
      descibed in Section 4.3.1 of [RFC4364].  An example usage can
be
SB> s/descibed/described/
      found in [I-D.ietf-idr-bgp-model].

========

SB> I am surprised that IP multicast addresses are here, but IP
addresses are not.
SB> I would have thought that both should be in the same place.

========

SB> In some protocols we use the NTP and the 1588 timer types, I
assume
SB> they are defined elsewhere.

========

   mpls-label
      The 20 bits label values in an MPLS label stack entry,
specified
      in [RFC3032].  This label value does not include the encodings
of
      Traffic Class and TTL (time to live).  The label range
specified
      by this type covers the general use values and the
special-purpose
      label values.  An example usage can be found in
      [I-D.ietf-mpls-base-yang].

SB> I am surprised that you don't start with label and then define the

SB> other label definitions in terms of existing definitions.
SB> The obvious order being label, sp-label, gp-label, generalized

========

S/ "This identity represents IPv4 address family.";/"This identity
represents the IPv4 address family.";

========

     //The rest of the values deinfed in the IANA registry
SB> s/deinfed/defined/

SB> However a question arises, the list stops at mt-v6
SB> Why do you stop at this point in the IANA list?
SB>
https://www.iana.org/assignments/address-family-numbers/address-family-numbers.xhtml
SB> It cannot be because some of the later ones are less relevant, as
some of the 
SB> included ones are rather rare. One the other hand there are some
later ones that 
SB> seem modern and useful.
SB>
SB> Also why do you have types in this list that you do not later
define in detail?

===========

SB> You have generalized label in the list top, but not in
SB> the YANG model itself.

===========



From nobody Wed May  3 09:29:39 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 A0A8C129457; Wed,  3 May 2017 09:29:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.823
X-Spam-Level: 
X-Spam-Status: No, score=-11.823 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 qFGtvTobCnuG; Wed,  3 May 2017 09:29:30 -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 88B0012945C; Wed,  3 May 2017 09:27:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2253; q=dns/txt; s=iport; t=1493828833; x=1495038433; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=SayP8P2W2uQ1ep0zSF5gHhruohBIugfLmnaGNxGj+P0=; b=NqdhY5D8y2jMhWezp/H1/KtzopU3RsqMWnlIIo7Yr8WqrteywzTWHnTF V1gGoI/f/YGDpGV3Ipki1E5eGe28leyjwBLh47EWYBHp6pcs58oYFX51C kHxAOW4Hx87To+IQH9MXDspXKb3BxXRNj+1UEzwB10LxeOjxlYb4o1IYJ g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DrAQB9BApZ/xbLJq1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBhUOOc5BhlW6CD4YkAoUCFwECAQEBAQEBAWsohRYBBRggQRALGC5?= =?us-ascii?q?XBgEMBgIBAReKBrNQinEBAQEBAQEBAQEBAQEBAQEBAQEghl+CCYJwikgBBJ1ck?= =?us-ascii?q?xSKfYZjjAiILCEDM4EKLiAIGRWHNz42iF4BAQE?=
X-IronPort-AV: E=Sophos;i="5.38,284,1491264000"; d="scan'208";a="651592783"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 May 2017 16:26:50 +0000
Received: from [10.60.67.90] (ams-bclaise-8919.cisco.com [10.60.67.90]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v43GQnkL003543; Wed, 3 May 2017 16:26:49 GMT
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
To: "Brian Trammell (IETF)" <ietf@trammell.ch>, Mark Nottingham <mnot@mnot.net>
Cc: IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net> <21A01174-4FB6-4F8C-AA3D-DCF6D1FEBA01@trammell.ch>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <8cb6fefd-200e-1d90-6a36-c32530ecbaf8@cisco.com>
Date: Wed, 3 May 2017 18:26:48 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0
MIME-Version: 1.0
In-Reply-To: <21A01174-4FB6-4F8C-AA3D-DCF6D1FEBA01@trammell.ch>
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/aew7v1cvN7UvWvVIksz1Vhh_eJ4>
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, 03 May 2017 16:29:32 -0000

Dear all,
> hi Mark,
>
> ...hm, apparently I *will* comment on the structure of the current document, inline below...
>
>> On 01 May 2017, at 05:45, Mark Nottingham <mnot@mnot.net> wrote:
>>
>> Overall, this document reads as if it was originally written to highlight the downsides of increased use of encryption, and then rewritten to be more neutral in tone. Unfortunately, some of the original intent posited there still seeps through.
>>
>> In doing so, it often fails to convey that there are any options other than "this has to be done by the network." I know that this has been cast as a survey of potential impacts, and therefore doesn't necessary need to enumerate alternatives, but the way that it's written could easily lead a reader to think that there aren't alternatives. It also is odd that alternatives are not enumerated when they're often well-known, and the really interesting issues are in the tradeoffs between doing something in the network (i.e., as a third party) vs. by one of the endpoints (a first party to communication) or their delegates.
> I think the statement of alternatives is a different document, though; it's one that needs to be written, yes, but the division of problem space and solution space is IMO useful here.
I would agree.
The operators are used to manage their network in a certain way.
The change for more encrypted traffic will force a change of those 
operational practices.
This document should serve as for a starting point to have this debate 
at the IETF, based on the documentation of those operational practices.
> I see this as the analogous to the split between RFC 7624 and draft-iab-privsec-confidentiality-mitigations. It was quite useful in having the former as a complete statement of what we think the problem is (in more detail that 7258's declaration) before recommending solutions. And, indeed, it's entirely possible that an IETF consensus statement on the solutions available for a given problem is "we have decided that this is not actually a problem we should design for", as in RFC 2804.
And again agree. Not all problems in this document are valid IETF 
problems. It doesn't mean that we should not document them.

Regards, Benoit
>
> Cheers,
>
> Brian


From nobody Wed May  3 09:45:00 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 DB266129B40 for <ietf@ietfa.amsl.com>; Wed,  3 May 2017 09:44:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.099
X-Spam-Level: 
X-Spam-Status: No, score=0.099 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 Lvb_D5y28DTK for <ietf@ietfa.amsl.com>; Wed,  3 May 2017 09:44:58 -0700 (PDT)
Received: from mx36-42.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 9801C129B5C for <ietf@ietf.org>; Wed,  3 May 2017 09:42:46 -0700 (PDT)
Received: from xsmtp05.mail2web.com ([168.144.250.245]) by mx36.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.86) (envelope-from <huitema@huitema.net>) id 1d5xMS-0000t2-PU for ietf@ietf.org; Wed, 03 May 2017 18:42:45 +0200
Received: from [10.5.2.16] (helo=xmail06.myhosting.com) by xsmtp05.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1d5xMR-0000UA-5r for ietf@ietf.org; Wed, 03 May 2017 12:42:43 -0400
Received: (qmail 13650 invoked from network); 3 May 2017 16:42:42 -0000
Received: from unknown (HELO [192.168.1.102]) (Authenticated-user:_huitema@huitema.net@[172.56.42.199]) (envelope-sender <huitema@huitema.net>) by xmail06.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf@ietf.org>; 3 May 2017 16:42:42 -0000
To: Benoit Claise <bclaise@cisco.com>, "Brian Trammell (IETF)" <ietf@trammell.ch>, Mark Nottingham <mnot@mnot.net>
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net> <21A01174-4FB6-4F8C-AA3D-DCF6D1FEBA01@trammell.ch> <8cb6fefd-200e-1d90-6a36-c32530ecbaf8@cisco.com>
Cc: IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <8114ef76-591f-630e-5464-2b63d0efea61@huitema.net>
Date: Wed, 3 May 2017 09:42:38 -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: <8cb6fefd-200e-1d90-6a36-c32530ecbaf8@cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
X-Originating-IP: 168.144.250.245
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: s0sct1PQhAABKnZB5plbIVbU93hg6Kq00BjAzYBqWlVTHAar8Je/lORhy3PZJU8LERWeKKG4PAQY Nyavp7c49EdlGitVsfXsrKty9N3esIJTugiLDom8V25hond3K4RsO76XSTAwtV4mg4i2ouCDa4AU hvIWAV5xUW/+gAh4vXqX/inInMqwA34LjWdRhw/hRcOb18WfxGyg6Om6u4YYm7A8kLZJCK84g5CU umyjI4Y5hjoyEb9Oq0NWpyO3vrfYy2h1mQR50Wwo5hSyeApVLD3dKxLhoxcmaInYbR5vlqGudzLe k2TYFBStSOMccbr5Uz0sPgnpAk2KA2vJwMd1uWhCmLzOxTAcQmFWVARhgNqBNFD3an3wiMp49rVr ybSB0ktSrwQbrgk6jfwMHIN4qnTFgIfDMShmlQFqCr5hA8xAXSGwpLGc/Znuh3MoIpK0zxlyuc4U Cg7S2SnA283ffrbRF0J+AL6gRRwFcty0/RGJ+cv73CChOPjKA0/DVd83mzKXD5o/Ia+BqyQ7Q0nt IZ2PVtMHd8bHCmdzlxzVIEgwyGTHIAoNFX+jcW7DGmdE6eBVl9/A6GtGi+mfMSANmjLzCyMdOETT xDqixVDal2Zqxiuap5uKiBpffUsHYsfmkrboF55pyqAvfOP9PRiFk64VFGHGL6a4Aiv0Hpn+svlW gWWsfzmdEBxk/w4+z2XWHxcEeYXaEh7Ip8nBmIzXZwpqT8auRNlXQctohljUCg/QBwCSBizyANgQ OnVZQVhWKhBaevb8pkwVq3+XN9bPyjRMyLUEno1frs9vZR0iI5iTGneI1cCMIcE6R6jtJ8btb7sy ltanepIHrA9+HqSAzbOGPeC5oMoq/jHul4QOoSYQxK4Q6pnz1PG2i0Jcu7De
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gvG9YFuEraaeD8Y4OtJhncOFN0U>
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, 03 May 2017 16:45:00 -0000

On 5/3/2017 9:26 AM, Benoit Claise wrote:

> The operators are used to manage their network in a certain way.
> The change for more encrypted traffic will force a change of those
> operational practices.
> This document should serve as for a starting point to have this debate
> at the IETF, based on the documentation of those operational practices.=
=20

My problem is that it is easy to get consensus on some practices, such
as "gathering statistics for traffic engineering", and much less so on
other practices, such as "opening the HTTP headers and adding
supercookies." The current document does not differentiate at all. It it
was published as is, the naive reader could just deduce that "the IETF
endorses adding supercookies to HTTP headers" -- to take just one
example. I understand that documenting alternatives for each of these
practices in the analysis document is impractical, but we need to find a
way to "document the controversy" -- when it exists of course.

-- Christian Huitema



From nobody Wed May  3 10:30:58 2017
Return-Path: <kathleen.moriarty.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 5850A129AEA; Wed,  3 May 2017 10:30:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 po7x0nT2hUAu; Wed,  3 May 2017 10:30:50 -0700 (PDT)
Received: from mail-pg0-x231.google.com (mail-pg0-x231.google.com [IPv6:2607:f8b0:400e: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 4EB7F1296D2; Wed,  3 May 2017 10:29:37 -0700 (PDT)
Received: by mail-pg0-x231.google.com with SMTP id t7so81560925pgt.3; Wed, 03 May 2017 10:29:37 -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=nm4YLwiB6G9mSbDNH6YjSq+qxcMeSaHBbgRVJaUyyNM=; b=mmqpOd0VJhWwf1x0VtP/KRv+jFz7yI00R1OzrUSHVfpkDgjtIrv57PkxCUks9yEURx 5RHTFTQ1qv/icLd8Q1abOoASCE0KExmV9tW5kVyJswb7CFXBxvyT1ERLOPxodDLpzbSx 3JTsPfmfE8e/wmT55X0cU8lky7s6N3BiavugwyIRS1j9eoBzjKtOWovqcBcgKnmAI1dg ww7RUo9L2eiQP4fv89jPI6m07+KrW5PCnwPO6Pjq8jwyzZGV60H9RULht6OhxGLB0DnO HzWqcy/5B+BBPVna3zUjHD3irIBdGLZPsKyk40p8q+5Ywf3Mpe+bzuq3F8saJ8KGmoMI GSIQ==
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=nm4YLwiB6G9mSbDNH6YjSq+qxcMeSaHBbgRVJaUyyNM=; b=MqMi6w+sTAjidRA5DJ8BRtiXldChqE1aMGa5JQIyczIQOuXwrvmpuhfJYISACGAjEO B8cvtYU0XyXBI5YeK1ploV1tQ89lJD+Sp4dj3L5vOmus1piHcw7kZV5lyx8nMdhu0d1I DNGIrOWoykvGspnw3Mocz89g30ezR9Rpy/84d3d0N+52vWkI7AEWfupzR51Kj9M0gdMX PFae9b61KcNF1fSj25mvwxl26m1G89i06d74RMEkqNPhVmHAc2Ku9vAopy2h1CNb0sx5 M8/BBe34NWQ/lshZxX7L/4OcuCBcAYcX7H+yAgs08ub/6D6hvopW/Iw9g1rX71JxBsAc JAsQ==
X-Gm-Message-State: AN3rC/7aFeuoQC7yh1y730S5EDcmKp6EYeZwHjRHZ8nKq33gKmN+rfis Uhq8sN19/cEyUc9SIiqFJ3COW8Hxlw==
X-Received: by 10.84.241.136 with SMTP id b8mr51035736pll.107.1493832576886; Wed, 03 May 2017 10:29:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.185.143 with HTTP; Wed, 3 May 2017 10:28:56 -0700 (PDT)
In-Reply-To: <8114ef76-591f-630e-5464-2b63d0efea61@huitema.net>
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net> <21A01174-4FB6-4F8C-AA3D-DCF6D1FEBA01@trammell.ch> <8cb6fefd-200e-1d90-6a36-c32530ecbaf8@cisco.com> <8114ef76-591f-630e-5464-2b63d0efea61@huitema.net>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Wed, 3 May 2017 13:28:56 -0400
Message-ID: <CAHbuEH4+SFUyq5w1VvY8Mr3GU7kuyEj=WMBEvV+RvjNwNS7oPA@mail.gmail.com>
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
To: Christian Huitema <huitema@huitema.net>
Cc: Benoit Claise <bclaise@cisco.com>, "Brian Trammell (IETF)" <ietf@trammell.ch>, Mark Nottingham <mnot@mnot.net>,  IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2B2UHaNznq_fn2pX0yYWkshxXC0>
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, 03 May 2017 17:30:53 -0000

On Wed, May 3, 2017 at 12:42 PM, Christian Huitema <huitema@huitema.net> wrote:
> On 5/3/2017 9:26 AM, Benoit Claise wrote:
>
>> The operators are used to manage their network in a certain way.
>> The change for more encrypted traffic will force a change of those
>> operational practices.
>> This document should serve as for a starting point to have this debate
>> at the IETF, based on the documentation of those operational practices.
>
> My problem is that it is easy to get consensus on some practices, such
> as "gathering statistics for traffic engineering", and much less so on
> other practices, such as "opening the HTTP headers and adding
> supercookies." The current document does not differentiate at all. It it
> was published as is, the naive reader could just deduce that "the IETF
> endorses adding supercookies to HTTP headers" -- to take just one
> example. I understand that documenting alternatives for each of these
> practices in the analysis document is impractical, but we need to find a
> way to "document the controversy" -- when it exists of course.

There's an explicit statement that says the IETF does not endorse the
documented practices.  It's not the practices, but the overall
document that we should have consensus on - that it is important to
document these practices so we have a starting point for discussion.
As Brian suggested, the follow on documents could do just that for
individual practices.  It's good to understand what is happening in
reality so we can help solve problems.

For the supercookie example, it is meant to be read with the preceding
text, which essentially does say what you are requesting - this is
something we don't want to happen - without a conversation, we won't
reach balance.  I'll clear up the text for that in the next version if
we haven't already.

>
> -- Christian Huitema
>
>



-- 

Best regards,
Kathleen


From nobody Wed May  3 10:47:49 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 3332D12957C; Wed,  3 May 2017 10:47:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level: 
X-Spam-Status: No, score=-4.321 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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
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 OGki2dHvUwnI; Wed,  3 May 2017 10:47:46 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 394241292F4; Wed,  3 May 2017 10:46:01 -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=1493833561; x=1525369561; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=UleDKFMk8rm/GQlqhHm8L3P7BFbg66sCkrr6n0wdmDE=; b=YiDAKjQIyaIXEQtJjNIFO9scPm3lFw3nvg2yEcbRud59LD6KBct5t3v6 oEje33IRlzQzKpMYI5bIljG1ia232f1gFfrXa3bDSVyRHx+1IE6qBs0xj H5d4WH4zjkIG3AaNge6TWwhpy/pyNFZ+NtcLH6lRMEpKX+aGE1OSLxmIi w=;
X-IronPort-AV: E=Sophos;i="5.38,284,1491289200";  d="scan'208,217";a="377941173"
Received: from unknown (HELO Ironmsg04-L.qualcomm.com) ([10.53.140.111]) by wolverine02.qualcomm.com with ESMTP; 03 May 2017 10:46:00 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8517"; a="1340705153"
X-MGA-submission: =?us-ascii?q?MDHc5b04MB7ZJCzUZDLup/M1fzquN+bXETKbPW?= =?us-ascii?q?x3f2SYNaMAndazRVZ/Rrk3KwE/FAv0Tdu6dhiwTGG5R5eIso1IrGX3DW?= =?us-ascii?q?wDE49cLa1+ggJUHNMSswRCQPw21IpajLgIlZK3hTZZjxyvQaMWETq0K3?= =?us-ascii?q?8A?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 03 May 2017 10:45:59 -0700
Received: from [10.64.122.14] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Wed, 3 May 2017 10:45:59 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Christian Huitema <huitema@huitema.net>
CC: Benoit Claise <bclaise@cisco.com>, Brian Trammell <ietf@trammell.ch>, Mark Nottingham <mnot@mnot.net>, IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
Date: Wed, 3 May 2017 12:45:57 -0500
Message-ID: <BF887C92-1ADD-47F7-A958-04538372AA15@qti.qualcomm.com>
In-Reply-To: <8114ef76-591f-630e-5464-2b63d0efea61@huitema.net>
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net> <21A01174-4FB6-4F8C-AA3D-DCF6D1FEBA01@trammell.ch> <8cb6fefd-200e-1d90-6a36-c32530ecbaf8@cisco.com> <8114ef76-591f-630e-5464-2b63d0efea61@huitema.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_3A2FD70E-70AE-4287-9C80-986DE92EB56B_="
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01F.na.qualcomm.com (10.85.0.32) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/B3gFaWhd19rkrKeCuAPHVEz723E>
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, 03 May 2017 17:47:48 -0000

--=_MailMate_3A2FD70E-70AE-4287-9C80-986DE92EB56B_=
Content-Type: text/plain; format=flowed; markup=markdown

On 3 May 2017, at 11:42, Christian Huitema wrote:

> My problem is that it is easy to get consensus on some practices, such
> as "gathering statistics for traffic engineering", and much less so on
> other practices, such as "opening the HTTP headers and adding
> supercookies."

I have no idea what "getting consensus on some practices" means. It is 
certainly easy to get IETF consensus that both practices *exist*. They 
do; of that there is no question. If the IETF were being asked to come 
to consensus that both practices *were good*, yes, that would be 
difficult. Luckily, that's not what's being asked.

> The current document does not differentiate at all. It it
> was published as is, the naive reader could just deduce that "the IETF
> endorses adding supercookies to HTTP headers" -- to take just one
> example.

I cannot come up with any way to read the mention of super cookies in 
section 8 as an endorsement at all.

If you're referring to the discussion of header insertion in 2.6.5, the 
only thing that could be vaguely construed as endorsing would be the 
phrase in inverted commas (which I take to be indicating irony) 
'header-enrichment'. If the suggestion is that the irony will be missed 
and someone might read that as endorsing, then saying "so-called 
'header-enrichment'" might make it crystal clear.

Either way, lack of overt disapproval is not endorsement.

This argument is not an argument about consensus. The intent of the 
document (AFAICT) is to catalog the practices, not to register 
endorsement or disapproval of them. If the text of the document fails to 
do the former, or mistakenly does do the latter, then that should be 
fixed. But arguing lack of consensus is just a red herring.

pr
--=_MailMate_3A2FD70E-70AE-4287-9C80-986DE92EB56B_=
Content-Type: text/html
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 3 May 2017, at 11:42, Christian Huitema wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">My problem is that it is easy to get consensus on some pr=
actices, such<br>
as "gathering statistics for traffic engineering", and much less so on<br=
>
other practices, such as "opening the HTTP headers and adding<br>
supercookies."</p>
</blockquote>

<p dir=3D"auto">I have no idea what "getting consensus on some practices"=
 means. It is certainly easy to get IETF consensus that both practices <e=
m>exist</em>. They do; of that there is no question. If the IETF were bei=
ng asked to come to consensus that both practices <em>were good</em>, yes=
, that would be difficult. Luckily, that's not what's being asked. </p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">The current document does not differentiate at all. It it=
<br>
was published as is, the naive reader could just deduce that "the IETF<br=
>
endorses adding supercookies to HTTP headers" -- to take just one<br>
example.</p>
</blockquote>

<p dir=3D"auto">I cannot come up with any way to read the mention of supe=
r cookies in section 8 as an endorsement at all.</p>

<p dir=3D"auto">If you're referring to the discussion of header insertion=
 in 2.6.5, the only thing that could be vaguely construed as endorsing wo=
uld be the phrase in inverted commas (which I take to be indicating irony=
) 'header-enrichment'. If the suggestion is that the irony will be missed=
 and someone might read that as endorsing, then saying "so-called 'header=
-enrichment'" might make it crystal clear.</p>

<p dir=3D"auto">Either way, lack of overt disapproval is not endorsement.=
</p>

<p dir=3D"auto">This argument is not an argument about consensus. The int=
ent of the document (AFAICT) is to catalog the practices, not to register=
 endorsement or disapproval of them. If the text of the document fails to=
 do the former, or mistakenly does do the latter, then that should be fix=
ed. But arguing lack of consensus is just a red herring.</p>

<p dir=3D"auto">pr</p>
</div>
</div>
</body>
</html>

--=_MailMate_3A2FD70E-70AE-4287-9C80-986DE92EB56B_=--


From nobody Wed May  3 10:48:43 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 7AF85129AEB; Wed,  3 May 2017 10:48:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.503
X-Spam-Level: 
X-Spam-Status: No, score=-14.503 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 5fo0HKH3hmvo; Wed,  3 May 2017 10:48:38 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12549129B0D; Wed,  3 May 2017 10:46:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5856; q=dns/txt; s=iport; t=1493833606; x=1495043206; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=6ku7x6S6rGPDQtXF3VYvs7iQYiY0nfhHGGP9eHv24Ao=; b=lvEUS9UsTEW4MnzJ1VmHYld2JjKipplWikHC1fOvVgFVEe8k4SmwdEi+ xMi/5BJOqf+ydFacud1BkIpAQ0cofe4/HyGNNI/R6SwF0qTG68p4+cJbF 9+3RTDXlGP4IgUJ4JA3xF9dLmhnibTED0TtYjrpFlKFJLKW0iOFYnHJEh A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AsAQCjFgpZ/4wNJK1SAQkZAQEBAQEBA?= =?us-ascii?q?QEBAQEHAQEBAQGDVWKBDAeDYYoYkkSUfIIPLoV2AhqEJj8YAQIBAQEBAQEBayi?= =?us-ascii?q?FFgYjETcOEAIBCBoCJgICAjAVEAIEAQ0DAoohDrEugiaKbQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBARgFgQuHMoJnNIQ7AQMkgwaCXwWdXAGKTYhGkWCUMwEfOIEKbxV?= =?us-ascii?q?FhnBEMoYhgTCBDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.38,284,1491264000"; d="scan'208";a="244474688"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 03 May 2017 17:46:45 +0000
Received: from XCH-RTP-014.cisco.com (xch-rtp-014.cisco.com [64.101.220.154]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v43HkjZ0009079 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 3 May 2017 17:46:46 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-014.cisco.com (64.101.220.154) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 3 May 2017 13:46:45 -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; Wed, 3 May 2017 13:46:45 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Stewart Bryant <stewart@g3ysx.org.uk>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>
CC: "rtgwg@ietf.org" <rtgwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-rtgwg-routing-types.all@ietf.org" <draft-ietf-rtgwg-routing-types.all@ietf.org>
Subject: Re: Rtgdir early partial review of draft-ietf-rtgwg-routing-types-02
Thread-Topic: Rtgdir early partial review of draft-ietf-rtgwg-routing-types-02
Thread-Index: AQHSxB0oh6coHWzZ/0ef7UXdupRAiqHi3diA
Date: Wed, 3 May 2017 17:46:45 +0000
Message-ID: <D52F8264.AC8ED%acee@cisco.com>
References: <149382325961.21410.10726283274929738928@ietfa.amsl.com>
In-Reply-To: <149382325961.21410.10726283274929738928@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.197]
Content-Type: text/plain; charset="utf-8"
Content-ID: <5DE9A38BD98C924DA5BE70F4677D8D88@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QIlNGR5pI4Lf-ZRsfSfm3FzjjhI>
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, 03 May 2017 17:48:41 -0000

SGkgU3Rld2FydCwNCg0KVGhhbmtzIGZvciByZXZpZXcuIFdlIG5lZWQgdG8gcHVibGlzaCBhIG5l
dyB2ZXJzaW9uIG9mIHRoaXMgZHJhZnQgYXMgd2UNCmhhdmUgc2lnbmlmaWNhdGlvbiBjaGFuZ2Vz
IGluIG91ciBHaXRIdWIgcmVwb3NpdG9yeS4NCg0KT24gNS8zLzE3LCAxMDo1NCBBTSwgIlN0ZXdh
cnQgQnJ5YW50IiA8c3Rld2FydEBnM3lzeC5vcmcudWs+IHdyb3RlOg0KDQo+UmV2aWV3IGlzIHBh
cnRpYWxseSBkb25lLiBBbm90aGVyIHJldmlldyByZXF1ZXN0IGhhcyBiZWVuIHJlZ2lzdGVyZWQN
Cj5mb3IgY29tcGxldGluZyBpdC4NCj4NCj5SZXZpZXdlcjogU3Rld2FydCBCcnlhbnQNCj5SZXZp
ZXcgcmVzdWx0OiBIYXMgSXNzdWVzDQo+DQo+Rmlyc3RseSBJIHNob3VsZCBzYXkgdGhhdCBJIGFt
IG5vdCBhbiBleHBlcnQgaW4gWUFORywgaGVuY2UgbXkNCj5zdWdnZXN0aW9uIHRoYXQgeW91IG1h
eSB3aXNoIHRvIGFzc2lnbiBhbiBhZGRpdGlvbmFsIHJldmlld2VyLg0KDQpUaGVyZSBpcyBubyBw
YXVjaXR5IG9mIFlBTkcgcmV2aWV3ZXJzIGZvciB0aGlzIGRvY3VtZW50Lg0KPg0KPkhvd2V2ZXIg
aW4gcmV2aWV3aW5nIHRoaXMgYSBudW1iZXIgb2YgcXVlc3Rpb25zIGFuZCBpc3N1ZXMgYXJvc2U6
DQo+DQo+Mi4gIE92ZXJ2aWV3DQo+DQo+ICAgVGhpcyBkb2N1bWVudCBkZWZpbmVzIHRoZSBmb2xs
b3dpbmcgZGF0YSB0eXBlczoNCj4NCj5TQj4gQWNjZXNzaWJpbGl0eSBub3RlIC0gdGhlIG9yZGVy
IG9mIHR5cGVzIHNlZW1zIHJhbmRvbS4gSXQgbWlnaHQNCj5TQj4gYmUgbW9yZSBoZWxwZnVsIHRv
IHRoZSByZWFkZXIgaWYgdGhleSB3ZXJlLCBpbiBhIHN5c3RlbWF0aWMgb3JkZXINCj5TQj4gZm9y
IGV4YW1wbGUgYWxwaGFiZXRpY2FsIGFuZC9vciBkZXBlbmRlbmN5IG9yZGVyLg0KDQpUaGV5IGFy
ZSBncm91cGVkIGJ5IGZ1bmN0aW9uYWxpdHkgd2l0aCBmdW5jdGlvbmFsbHkgc2ltaWxhciB0eXBl
cyBiZWluZw0KZ3JvdXBlZCB0b2dldGhlci4gVGhpcyBpcyBzaW1pbGFyIGluIG9yZ2FuaXphdGlv
biB0byBhIEMgaGVhZGVyIGZpbGUuDQoNCg0KPg0KPj09PT09PT0NCj4NCj4gcm91dGVyLWlkDQo+
ICAgICAgUm91dGVyIElkZW50aWZpZXJzIGFyZSBjb21tb25seSB1c2VkIHRvIGlkZW50aWZ5IGEg
bm9kZXMgaW4NCj5TQj4gcy9hIG5vZGVzL25vZGVzLw0KDQpXaWxsIGZpeCBpbiBuZXh0IHJldmlz
aW9uIChpZiBub3QgYWxyZWFkeSBmaXhlZCBpbiB0aGUgZ2l0IHJlcG9zaXRvcnkpLg0KDQo+PT09
PT09PQ0KPg0KPiAgIHJvdXRlLXRhcmdldC10eXBlDQo+ICAgICAgVGhpcyB0eXBlIGRlZmluZXMg
dGhlIGltcG9ydCBhbmQgZXhwb3J0IHJ1bGVzIG9mIFJvdXRlIFRhcmdldHMsDQo+YXMNCj4gICAg
ICBkZXNjaWJlZCBpbiBTZWN0aW9uIDQuMy4xIG9mIFtSRkM0MzY0XS4gIEFuIGV4YW1wbGUgdXNh
Z2UgY2FuDQo+YmUNCj5TQj4gcy9kZXNjaWJlZC9kZXNjcmliZWQvDQo+ICAgICAgZm91bmQgaW4g
W0ktRC5pZXRmLWlkci1iZ3AtbW9kZWxdLg0KDQpXaWxsIGZpeCBpbiBuZXh0IHJldmlzaW9uIChp
ZiBub3QgYWxyZWFkeSBmaXhlZCBpbiB0aGUgZ2l0IHJlcG9zaXRvcnkpLg0KDQo+DQo+PT09PT09
PT0NCj4NCj5TQj4gSSBhbSBzdXJwcmlzZWQgdGhhdCBJUCBtdWx0aWNhc3QgYWRkcmVzc2VzIGFy
ZSBoZXJlLCBidXQgSVANCj5hZGRyZXNzZXMgYXJlIG5vdC4NCj5TQj4gSSB3b3VsZCBoYXZlIHRo
b3VnaHQgdGhhdCBib3RoIHNob3VsZCBiZSBpbiB0aGUgc2FtZSBwbGFjZS4NCg0KSVAvSVB2NiBh
ZGRyZXNzZXMgYXJlIGFscmVhZHkgZGVmaW5lZCBpbiBSRkMgNjk5MSBhbmQgYXJlIGltcG9ydGVk
IGJ5IHRoaXMNCm1vZHVsZS4gDQo+DQo+PT09PT09PT0NCj4NCj5TQj4gSW4gc29tZSBwcm90b2Nv
bHMgd2UgdXNlIHRoZSBOVFAgYW5kIHRoZSAxNTg4IHRpbWVyIHR5cGVzLCBJDQo+YXNzdW1lDQo+
U0I+IHRoZXkgYXJlIGRlZmluZWQgZWxzZXdoZXJlLg0KDQpOb2JvZHkgaGFzIHN1Z2dlc3RlZCB0
aGVzZSBoZXJldG9mb3JlLiBJZiB5b3UgcHJvdmlkZSB0eXBlcyBhbmQgd2hlcmUgdGhleQ0Kd291
bGQgYmUgdXNlZCwgd2Ugd2lsbCBzdHJvbmdseSBjb25zaWRlciBpbmNsdWRpbmcgdGhlbS4NCg0K
Pg0KPj09PT09PT09DQo+DQo+ICAgbXBscy1sYWJlbA0KPiAgICAgIFRoZSAyMCBiaXRzIGxhYmVs
IHZhbHVlcyBpbiBhbiBNUExTIGxhYmVsIHN0YWNrIGVudHJ5LA0KPnNwZWNpZmllZA0KPiAgICAg
IGluIFtSRkMzMDMyXS4gIFRoaXMgbGFiZWwgdmFsdWUgZG9lcyBub3QgaW5jbHVkZSB0aGUgZW5j
b2RpbmdzDQo+b2YNCj4gICAgICBUcmFmZmljIENsYXNzIGFuZCBUVEwgKHRpbWUgdG8gbGl2ZSku
ICBUaGUgbGFiZWwgcmFuZ2UNCj5zcGVjaWZpZWQNCj4gICAgICBieSB0aGlzIHR5cGUgY292ZXJz
IHRoZSBnZW5lcmFsIHVzZSB2YWx1ZXMgYW5kIHRoZQ0KPnNwZWNpYWwtcHVycG9zZQ0KPiAgICAg
IGxhYmVsIHZhbHVlcy4gIEFuIGV4YW1wbGUgdXNhZ2UgY2FuIGJlIGZvdW5kIGluDQo+ICAgICAg
W0ktRC5pZXRmLW1wbHMtYmFzZS15YW5nXS4NCj4NCj5TQj4gSSBhbSBzdXJwcmlzZWQgdGhhdCB5
b3UgZG9uJ3Qgc3RhcnQgd2l0aCBsYWJlbCBhbmQgdGhlbiBkZWZpbmUgdGhlDQo+DQo+U0I+IG90
aGVyIGxhYmVsIGRlZmluaXRpb25zIGluIHRlcm1zIG9mIGV4aXN0aW5nIGRlZmluaXRpb25zLg0K
PlNCPiBUaGUgb2J2aW91cyBvcmRlciBiZWluZyBsYWJlbCwgc3AtbGFiZWwsIGdwLWxhYmVsLCBn
ZW5lcmFsaXplZA0KDQpZQU5HIElkZW50aXRpZXMgYXJlIHZlcnkgZXh0ZW5kYWJsZSBidXQgc29t
ZXdoYXQgbGltaXRlZCBpbiBzZW1hbnRpY3MuIEZvcg0KZXhhbXBsZSwgYSBiYXNlIGlkZW50aXR5
IGlzIOKAnGEgbmV3IGdsb2JhbGx5IHVuaXF1ZSwgYWJzdHJhY3QsIGFuZCB1bnR5cGVkDQppZGVu
dGl0eS7igJ0gU28sIHRoZSBzcC1sYWJlbCBpZGVudGl0aWVzIGNhbm5vdCBoYXZlIGEgYmFzZSB0
eXBlIG9mIGxhYmVsDQooUkZDIDc5NTApLiBJIGhhdmUgd29uZGVyZWQgd2h5IHRoZSBjYW7igJl0
IGhhdmUgYSB0eXBlIG15c2VsZi4NCg0KPg0KPj09PT09PT09DQo+DQo+Uy8gIlRoaXMgaWRlbnRp
dHkgcmVwcmVzZW50cyBJUHY0IGFkZHJlc3MgZmFtaWx5LiI7LyJUaGlzIGlkZW50aXR5DQo+cmVw
cmVzZW50cyB0aGUgSVB2NCBhZGRyZXNzIGZhbWlseS4iOw0KPg0KPj09PT09PT09DQo+DQo+ICAg
ICAvL1RoZSByZXN0IG9mIHRoZSB2YWx1ZXMgZGVpbmZlZCBpbiB0aGUgSUFOQSByZWdpc3RyeQ0K
PlNCPiBzL2RlaW5mZWQvZGVmaW5lZC8NCj4NCj5TQj4gSG93ZXZlciBhIHF1ZXN0aW9uIGFyaXNl
cywgdGhlIGxpc3Qgc3RvcHMgYXQgbXQtdjYNCj5TQj4gV2h5IGRvIHlvdSBzdG9wIGF0IHRoaXMg
cG9pbnQgaW4gdGhlIElBTkEgbGlzdD8NCj5TQj4NCj5odHRwczovL3d3dy5pYW5hLm9yZy9hc3Np
Z25tZW50cy9hZGRyZXNzLWZhbWlseS1udW1iZXJzL2FkZHJlc3MtZmFtaWx5LW51bQ0KPmJlcnMu
eGh0bWwNCj5TQj4gSXQgY2Fubm90IGJlIGJlY2F1c2Ugc29tZSBvZiB0aGUgbGF0ZXIgb25lcyBh
cmUgbGVzcyByZWxldmFudCwgYXMNCj5zb21lIG9mIHRoZSANCj5TQj4gaW5jbHVkZWQgb25lcyBh
cmUgcmF0aGVyIHJhcmUuIE9uZSB0aGUgb3RoZXIgaGFuZCB0aGVyZSBhcmUgc29tZQ0KPmxhdGVy
IG9uZXMgdGhhdCANCj5TQj4gc2VlbSBtb2Rlcm4gYW5kIHVzZWZ1bC4NCj5TQj4NCj5TQj4gQWxz
byB3aHkgZG8geW91IGhhdmUgdHlwZXMgaW4gdGhpcyBsaXN0IHRoYXQgeW91IGRvIG5vdCBsYXRl
cg0KPmRlZmluZSBpbiBkZXRhaWw/DQoNCkkgaGF2ZSBpbmNsdWRlZCB0aGUgcmVzdCBvZiB0aGUg
SUFOQSBkZWZpbmVkIEFGcyBpbiB0aGUgR2l0SHViIHZlcnNpb24uDQpUaGVyZSB3aWxsIGJlIG5v
IG90aGVyIFlBTkcgZGVzY3JpcHRpb24gb2YgdGhlc2UgYWRkcmVzcyBmYW1pbGllcy4NCkhvd2V2
ZXIsIEkgaGF2ZSBlbWJlbGxpc2hlZCB0aGVzZSBhIGJpdCB0byBhdCBsZWFzdCBoYXZlIHRoZSBm
dWxsDQpleHBhbnNpb24gb2YgYWNyb255bXMuIFRoZXNlIHdpbGwgYmUgbW92ZWQgdG8gYSBzZXBh
cmF0ZQ0KaWFuYS1yb3V0aW5nLXR5cGVzIG1vZHVsZSBpbiB0aGUgc2FtZSBkcmFmdC4NCg0KPg0K
Pj09PT09PT09PT09DQo+DQo+U0I+IFlvdSBoYXZlIGdlbmVyYWxpemVkIGxhYmVsIGluIHRoZSBs
aXN0IHRvcCwgYnV0IG5vdCBpbg0KPlNCPiB0aGUgWUFORyBtb2RlbCBpdHNlbGYuDQoNCkl0IGlz
IG9uIHBhZ2UgMTYuIA0KDQpUaGFua3MsDQpBY2VlIA0KPg0KPj09PT09PT09PT09DQo+DQo+DQoN
Cg==


From nobody Wed May  3 16:58:01 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 A054F128CB9; Wed,  3 May 2017 16:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.098
X-Spam-Level: 
X-Spam-Status: No, score=0.098 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 6Dhqt7DsqyB2; Wed,  3 May 2017 16:57:49 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (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 57BC1128CD5; Wed,  3 May 2017 16:57:49 -0700 (PDT)
Received: from [192.168.3.104] (unknown [124.189.96.14]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id E961822E255; Wed,  3 May 2017 19:57:40 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <BF887C92-1ADD-47F7-A958-04538372AA15@qti.qualcomm.com>
Date: Thu, 4 May 2017 09:57:37 +1000
Cc: Christian Huitema <huitema@huitema.net>, Benoit Claise <bclaise@cisco.com>, Brian Trammell <ietf@trammell.ch>, IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <BD3807D4-6253-4A3E-BA34-00CA1DAB5037@mnot.net>
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net> <21A01174-4FB6-4F8C-AA3D-DCF6D1FEBA01@trammell.ch> <8cb6fefd-200e-1d90-6a36-c32530ecbaf8@cisco.com> <8114ef76-591f-630e-5464-2b63d0efea61@huitema.net> <BF887C92-1ADD-47F7-A958-04538372AA15@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ch2-xsFwI45GF6o9CaAUU9rAe94>
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, 03 May 2017 23:57:53 -0000

On 4 May 2017, at 3:45 am, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:

>> The current document does not differentiate at all. It it
>> was published as is, the naive reader could just deduce that "the =
IETF
>> endorses adding supercookies to HTTP headers" -- to take just one
>> example.
> =20
> I cannot come up with any way to read the mention of super cookies in =
section 8 as an endorsement at all.
>=20
> If you're referring to the discussion of header insertion in 2.6.5, =
the only thing that could be vaguely construed as endorsing would be the =
phrase in inverted commas (which I take to be indicating irony) =
'header-enrichment'. If the suggestion is that the irony will be missed =
and someone might read that as endorsing, then saying "so-called =
'header-enrichment'" might make it crystal clear.
>=20
> Either way, lack of overt disapproval is not endorsement.

I don't know, Pete. In my experience, people often misread intent in =
specs, even when we think it's very clearly spelled out, because we are =
blinded by how close we are to it. On the other side, developers =
routinely cherry-pick a statement in isolation to prove their point, =
rather than taking in the whole. This happens all of the time in HTTP, =
despite our best efforts to educate.

Relying on irony to convey intent in specifications is spectacularly =
poor practice; we should know better than this by now.

So I don't think it does any harm to over-communicate; if we're going to =
talk about a controversial practice like header "enrichment", it seems =
reasonable to me that we should put the appropriate context with it, =
rather than relying on the reader having a full understanding not only =
of the whole document, but the context within which it was written.

Even more so when the person misreading (or misusing) it might be a =
legislator or regulator who has comparatively little technical depth, =
but great impact.

Cheers,


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


From nobody Wed May  3 19:48:04 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 E22D312960D; Wed,  3 May 2017 19:47:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.123
X-Spam-Level: 
X-Spam-Status: No, score=-5.123 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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, 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=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 8lNzEpyFUGVh; Wed,  3 May 2017 19:47:53 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89DBF120725; Wed,  3 May 2017 19:47:52 -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=1493866072; x=1525402072; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=zGQDYLNxIU+EBA+nujGnXzQFd/u/g1XyJ4b/k6/dces=; b=OUK0A/vbhJv4DkFTKIS0E95IMmeM30CSblwF+KB7FW7feVFbdYBzyqt7 8pxX7jj5sxUESlAtgnYD+q4y1D0GMa/1N1ILppm13raxdpzS9It1XAST8 AAQBohTmWScg9qhRjo2BPudv8B6/0OvftAK3kr7Wg3Bzky+GZ1RRqN6aV Q=;
X-IronPort-AV: E=Sophos;i="5.38,286,1491289200"; d="scan'208";a="282617602"
Received: from unknown (HELO ironmsg02-L.qualcomm.com) ([10.53.140.109]) by wolverine01.qualcomm.com with ESMTP; 03 May 2017 19:47:51 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8517"; a="918012679"
X-MGA-submission: =?us-ascii?q?MDHog7Rs+jdueZOrmaeNKyTAbVbP3Q1342Drl9?= =?us-ascii?q?4+9Ij81DWVzurDChtWbZ3/01orafdVLTf0uQi4AjDeUdzLiNwhqFRg3u?= =?us-ascii?q?web0bucGABLYRspMW7MfRkZhbIMHyQsb/VCAPLmdoKRBOfdUm1x/gPAw?= =?us-ascii?q?VE?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 03 May 2017 19:47:50 -0700
Received: from [10.64.122.14] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Wed, 3 May 2017 19:47:49 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Mark Nottingham <mnot@mnot.net>
CC: Christian Huitema <huitema@huitema.net>, Benoit Claise <bclaise@cisco.com>, Brian Trammell <ietf@trammell.ch>, IESG <iesg@ietf.org>,  IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
Date: Wed, 3 May 2017 21:47:48 -0500
Message-ID: <0859CEA7-B961-4C4D-BB1B-EB8F8D59E882@qti.qualcomm.com>
In-Reply-To: <BD3807D4-6253-4A3E-BA34-00CA1DAB5037@mnot.net>
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net> <21A01174-4FB6-4F8C-AA3D-DCF6D1FEBA01@trammell.ch> <8cb6fefd-200e-1d90-6a36-c32530ecbaf8@cisco.com> <8114ef76-591f-630e-5464-2b63d0efea61@huitema.net> <BF887C92-1ADD-47F7-A958-04538372AA15@qti.qualcomm.com> <BD3807D4-6253-4A3E-BA34-00CA1DAB5037@mnot.net>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; markup=markdown
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01F.na.qualcomm.com (10.85.0.32) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vhubhCvAMsLKUFYyoI_1-nmJ6gI>
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, 04 May 2017 02:47:56 -0000

On 3 May 2017, at 18:57, Mark Nottingham wrote:

> ...I don't think it does any harm to over-communicate; if we're going 
> to talk about a controversial practice like header "enrichment", it 
> seems reasonable to me that we should put the appropriate context with 
> it, rather than relying on the reader having a full understanding not 
> only of the whole document, but the context within which it was 
> written.

As I said earlier, I think it's perfectly appropriate to make sure that 
we're not endorsing any of these practices in this document, so I have 
no problem "over-communicating", for example in 2.6.5. And so long as 
"appropriate context" doesn't mean "we must explain in excruciating 
detail the wrongness of each and every wrong thing about these 
practices", I'm fine giving a little context. I just worry from some of 
the comments that some folks don't want to make mention of any practice 
without both an explicit rejection of the practice (beyond the context 
setting at the beginning of the document that it is not the purpose of 
the document to endorse, but instead simply catalog, these practices) 
and a statement of alternatives to each of the practices. I think that's 
unreasonable to ask of this sort of document. So long as it says up 
front that it is not endorsing any practice, and there is nothing in the 
description of any particular practice that could be mistaken for an 
endorsement, that's enough.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Wed May  3 20:38:29 2017
Return-Path: <randy@psg.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 30D94129B3A; Wed,  3 May 2017 20:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 JwJlRUE9XLUx; Wed,  3 May 2017 20:38:19 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 7254B129B51; Wed,  3 May 2017 20:38:11 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1d67ai-0002gt-Uc; Thu, 04 May 2017 03:38:09 +0000
Date: Thu, 04 May 2017 12:38:05 +0900
Message-ID: <m2shkl47he.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Cc: Christian Huitema <huitema@huitema.net>, IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
In-Reply-To: <CAHbuEH4+SFUyq5w1VvY8Mr3GU7kuyEj=WMBEvV+RvjNwNS7oPA@mail.gmail.com> <BF887C92-1ADD-47F7-A958-04538372AA15@qti.qualcomm.com> <8cb6fefd-200e-1d90-6a36-c32530ecbaf8@cisco.com>
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net> <21A01174-4FB6-4F8C-AA3D-DCF6D1FEBA01@trammell.ch> <8cb6fefd-200e-1d90-6a36-c32530ecbaf8@cisco.com> <8114ef76-591f-630e-5464-2b63d0efea61@huitema.net> <CAHbuEH4+SFUyq5w1VvY8Mr3GU7kuyEj=WMBEvV+RvjNwNS7oPA@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vSp9EFFWsJMFX09HjHM6yaXVe3I>
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, 04 May 2017 03:38:21 -0000

Benoit Claise wrote:
> The operators are used to manage their network in a certain way.

the ways operators manage their networks is highly varied.

but, in reality, what packet data do i need beyond the basic four-tuple
and congestion markings?

> The change for more encrypted traffic will force a change of those
> operational practices.

not necessarily.  of course it will seriously impact those operators
doing dpi, http header insertion, etc.  many of us consider this a
feature of encryption not a bug.

> This document should serve as for a starting point to have this debate
> at the IETF> practices.

it is.  and it should not go forward until we have had this debate.  and
we clearly have significant differences today.

> based on the documentation of those operational practices.

the set of operational practices is manifold.

Kathleen Moriarty wrote:
> There's an explicit statement that says the IETF does not endorse the
> documented practices.

standard wiggle 14.3.  please specifically call them out as negatively
affecting privacy and dis-recommended.

> It's not the practices, but the overall document that we should have
> consensus on - that it is important to document these practices so we
> have a starting point for discussion.

as christian alluded, the practices are not a closed set.

Pete Resnick wrote:
> I cannot come up with any way to read the mention of super cookies in
> section 8 as an endorsement at all.

or as an anti-endorsement.  so you would lay out the road map with no
marking of the evil paths.

> Either way, lack of overt disapproval is not endorsement.

in the real world of "buy our X device which implements rfc 666's
description of how to murder users" it is endorsement.

randy


From nobody Wed May  3 23:12:52 2017
Return-Path: <petr.spacek@nic.cz>
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 10D80129B7E for <ietf@ietfa.amsl.com>; Wed,  3 May 2017 23:12:50 -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_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2uqLun_yvyon for <ietf@ietfa.amsl.com>; Wed,  3 May 2017 23:12:48 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (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 7C40E129401 for <ietf@ietf.org>; Wed,  3 May 2017 23:12:47 -0700 (PDT)
Received: from [192.168.3.170] (unknown [95.82.146.6]) by mail.nic.cz (Postfix) with ESMTPSA id 5F16B608A7 for <ietf@ietf.org>; Thu,  4 May 2017 08:12:45 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1493878365; bh=/ZNX41V5lBvhov6GKgpX8ANiQtzTiBkF0iE8O+3Ny0Q=; h=To:From:Date; b=rx0jHZPuW/j1IacRLL89efnUxOeNC0dcI2S9NnDQGRfdRFcncdZdPtBEQY64xUFBw oO/AVyvsOdnod2bsAw7b5vEbyHYC+7p1OMKyF5E/F6qUTxwnIhw96GBfTWsczhNikr Gj/ig+CcpMZVQNaXESr0voVHPE4N8/3TvxJU7dGs=
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
To: ietf@ietf.org
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net> <21A01174-4FB6-4F8C-AA3D-DCF6D1FEBA01@trammell.ch> <8cb6fefd-200e-1d90-6a36-c32530ecbaf8@cisco.com> <8114ef76-591f-630e-5464-2b63d0efea61@huitema.net> <BF887C92-1ADD-47F7-A958-04538372AA15@qti.qualcomm.com> <BD3807D4-6253-4A3E-BA34-00CA1DAB5037@mnot.net> <0859CEA7-B961-4C4D-BB1B-EB8F8D59E882@qti.qualcomm.com>
From: =?UTF-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>
Organization: CZ.NIC
Message-ID: <6c2b0099-2293-a654-3009-969c17bf5c26@nic.cz>
Date: Thu, 4 May 2017 08:12:34 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <0859CEA7-B961-4C4D-BB1B-EB8F8D59E882@qti.qualcomm.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qW0pgXcMjVH3ddOx-YGA4E5HeZw>
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, 04 May 2017 06:12:50 -0000

On 4.5.2017 04:47, Pete Resnick wrote:
> On 3 May 2017, at 18:57, Mark Nottingham wrote:
> 
>> ...I don't think it does any harm to over-communicate; if we're going
>> to talk about a controversial practice like header "enrichment", it
>> seems reasonable to me that we should put the appropriate context with
>> it, rather than relying on the reader having a full understanding not
>> only of the whole document, but the context within which it was written.
> 
> As I said earlier, I think it's perfectly appropriate to make sure that
> we're not endorsing any of these practices in this document, so I have
> no problem "over-communicating", for example in 2.6.5. And so long as
> "appropriate context" doesn't mean "we must explain in excruciating
> detail the wrongness of each and every wrong thing about these
> practices", I'm fine giving a little context. I just worry from some of

I agree with Pete here. Little more context, or just repeated notice
"this practice is evil and listed here for completeness"
would be enough for this document.

Redundancy in natural languages helps to get the point across.
Let's add some redundancy!

Petr Špaček  @  CZ.NIC

> the comments that some folks don't want to make mention of any practice
> without both an explicit rejection of the practice (beyond the context
> setting at the beginning of the document that it is not the purpose of
> the document to endorse, but instead simply catalog, these practices)
> and a statement of alternatives to each of the practices. I think that's
> unreasonable to ask of this sort of document. So long as it says up
> front that it is not endorsing any practice, and there is nothing in the
> description of any particular practice that could be mistaken for an
> endorsement, that's enough.
> 
> pr


From nobody Thu May  4 00:07:10 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 6D330129B63; Thu,  4 May 2017 00:07:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.822
X-Spam-Level: 
X-Spam-Status: No, score=-11.822 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 WMeVV_61JS5H; Thu,  4 May 2017 00:07:02 -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 83156129401; Thu,  4 May 2017 00:07:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6932; q=dns/txt; s=iport; t=1493881621; x=1495091221; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=Zx1SOPDfesw23BypdNWVaMMXLvf6jAFCMCS5vCG7J6s=; b=Xr1DacwG6IBr4iQeQ7sLcmThoFu6JF2tufvX9hMEmanRBDVcezc2R3X8 VhZpBEpwKseZ+zAB7qbMNDThylO2LwpiX7Ie/dp3GcSdiXomzKsl0m8fl z53xwMCIp39oFFEd5CT8Zxg8kmlFQdksvj0arbG147kTFuaHih5vHgUFv k=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D+AAAG0gpZ/xbLJq1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgyqGAYoYc5BikDeFOIIPB4YdAoUCGAECAQEBAQEBAWsohRYBBSN?= =?us-ascii?q?WEAsECgoqAgJXBgEMCAEBihywYIImK4o+AQEBAQEBAQEBAQEBAQEBAQEBAQEBD?= =?us-ascii?q?g+IaIFkgQyHaYJfAQSdYoQNghOELohHggKIeyOGQpQ1HziBCi4gCBkVhTYcgWU?= =?us-ascii?q?+iS0BAQE?=
X-IronPort-AV: E=Sophos;i="5.38,287,1491264000";  d="asc'?scan'208,217";a="652625888"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 May 2017 07:06:59 +0000
Received: from [10.61.106.170] (dhcp-10-61-106-170.cisco.com [10.61.106.170]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v4476wW5016706;  Thu, 4 May 2017 07:06:58 GMT
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
To: Mark Nottingham <mnot@mnot.net>, Pete Resnick <presnick@qti.qualcomm.com>
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net> <21A01174-4FB6-4F8C-AA3D-DCF6D1FEBA01@trammell.ch> <8cb6fefd-200e-1d90-6a36-c32530ecbaf8@cisco.com> <8114ef76-591f-630e-5464-2b63d0efea61@huitema.net> <BF887C92-1ADD-47F7-A958-04538372AA15@qti.qualcomm.com> <BD3807D4-6253-4A3E-BA34-00CA1DAB5037@mnot.net>
Cc: Christian Huitema <huitema@huitema.net>, IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
From: Eliot Lear <lear@cisco.com>
Message-ID: <77af81f1-5ab0-c94c-4f3d-9d31edf55b2b@cisco.com>
Date: Thu, 4 May 2017 09:06:57 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <BD3807D4-6253-4A3E-BA34-00CA1DAB5037@mnot.net>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Qi3LKmJoVkEooqhtC3jHBpMD5onm8co96"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vNIYS4QBjNKPbsDZIXf-yCsYir8>
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, 04 May 2017 07:07:03 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Qi3LKmJoVkEooqhtC3jHBpMD5onm8co96
Content-Type: multipart/mixed; boundary="u16p7j5AKFfgxfOsHbrXTxRgjaPv63Kxa";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Mark Nottingham <mnot@mnot.net>, Pete Resnick <presnick@qti.qualcomm.com>
Cc: Christian Huitema <huitema@huitema.net>, IESG <iesg@ietf.org>,
 IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <77af81f1-5ab0-c94c-4f3d-9d31edf55b2b@cisco.com>
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net>
 <21A01174-4FB6-4F8C-AA3D-DCF6D1FEBA01@trammell.ch>
 <8cb6fefd-200e-1d90-6a36-c32530ecbaf8@cisco.com>
 <8114ef76-591f-630e-5464-2b63d0efea61@huitema.net>
 <BF887C92-1ADD-47F7-A958-04538372AA15@qti.qualcomm.com>
 <BD3807D4-6253-4A3E-BA34-00CA1DAB5037@mnot.net>
In-Reply-To: <BD3807D4-6253-4A3E-BA34-00CA1DAB5037@mnot.net>

--u16p7j5AKFfgxfOsHbrXTxRgjaPv63Kxa
Content-Type: multipart/alternative;
 boundary="------------F36D1852E02B4682469E1E77"

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

Just a comment on this:

On 5/4/17 1:57 AM, Mark Nottingham wrote:
> Even more so when the person misreading (or misusing) it might be a leg=
islator or regulator who has comparatively little technical depth, but gr=
eat impact.

That is *not* the concern that you should be focused on.

First, find me a legislator who has actually read an RFC, and I'll buy
you one of those fancy drinks you like.  Even most regulators do not
read RFCs, but when they do they are generally focused on normative
product requirements.  This document has no such requirements to grasp.

Nor should a press quote even be a serious concern, given how little
press 7258 and the IAB statement generated.

The only serious concern one might have is whether someone would look at
the document and decide that there is a problem statement for work that
would subvert security to take place, either within the IETF or
elsewhere.  Within the IETF we have a rough consensus process that
anyone can use.  It doesn't guarantee a result, but it is the best we
have, and I couldn't imagine someone *not* being called out for taking
something out of context, especially on this topic.

That leaves other organizations. some of whose members might even
intentionally misconstrue this work as justification to start new (bad)
work.  That's a real risk and it has happened before.  Repeatedly.  My
observation is that when this has happened in the past, the long term
consequences to the industry have been minimal, first because because we
have happily been able to stop some of the dumber ideas, and also
because our documents had good technical grounding while others did
not.  Furthermore, if we don't publish in order to avoid being
misconstrued, it means we cannot have an honest discussion amongst
ourselves, nor can we document any consequences of our decisions, and
that opens this organization up to far more serious (and deserved)
criticism by regulators, antagonists, academics, the press, and, well, us=
=2E

Eliot


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

<html>
  <head>
    <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Ty=
pe">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <p>Just a comment on this:<br>
    </p>
    <div class=3D"moz-cite-prefix">On 5/4/17 1:57 AM, Mark Nottingham
      wrote:<br>
    </div>
    <blockquote cite=3D"mid:BD3807D4-6253-4A3E-BA34-00CA1DAB5037@mnot.net=
"
      type=3D"cite">
      <pre wrap=3D"">Even more so when the person misreading (or misusing=
) it might be a legislator or regulator who has comparatively little tech=
nical depth, but great impact.
</pre>
    </blockquote>
    <br>
    That is <b>not</b> the concern that you should be focused on.<br>
    <br>
    First, find me a legislator who has actually read an RFC, and I'll
    buy you one of those fancy drinks you like.=C2=A0 Even most regulator=
s do
    not read RFCs, but when they do they are generally focused on
    normative product requirements.=C2=A0 This document has no such
    requirements to grasp.<br>
    <br>
    Nor should a press quote even be a serious concern, given how little
    press 7258 and the IAB statement generated.<br>
    <br>
    The only serious concern one might have is whether someone would
    look at the document and decide that there is a problem statement
    for work that would subvert security to take place, either within
    the IETF or elsewhere.=C2=A0 Within the IETF we have a rough consensu=
s
    process that anyone can use.=C2=A0 It doesn't guarantee a result, but=
 it
    is the best we have, and I couldn't imagine someone <b>not</b>
    being called out for taking something out of context, especially on
    this topic.<br>
    <br>
    That leaves other organizations. some of whose members might even
    intentionally misconstrue this work as justification to start new
    (bad) work.=C2=A0 That's a real risk and it has happened before.=C2=A0=

    Repeatedly.=C2=A0 My observation is that when this has happened in th=
e
    past, the long term consequences to the industry have been minimal,
    first because because we have happily been able to stop some of the
    dumber ideas, and also because our documents had good technical
    grounding while others did not.=C2=A0 Furthermore, if we don't publis=
h in
    order to avoid being misconstrued, it means we cannot have an honest
    discussion amongst ourselves, nor can we document any consequences
    of our decisions, and that opens this organization up to far more
    serious (and deserved) criticism by regulators, antagonists,
    academics, the press, and, well, us.<br>
    <br>
    Eliot<br>
    <br>
  </body>
</html>

--------------F36D1852E02B4682469E1E77--

--u16p7j5AKFfgxfOsHbrXTxRgjaPv63Kxa--

--Qi3LKmJoVkEooqhtC3jHBpMD5onm8co96
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

iQEcBAEBCAAGBQJZCtMSAAoJEIe2a0bZ0nozHhQIAJw7FE6CiZoubyFd00l2IwN+
5vuyeWeX5avzLbiZgMXqgZGY58idXlUQDsmjweIDAKxavF0DWfIJcFeQSpL6gCLO
O/uneh/APAzsjDLlCENfZGcepVRA0PgYRc58lvPb0YHVZau+21ojhjQbHfBZQ/Y5
Gc+t2AiuePqUwM1zdMkibAp5pn6tYaXojuRxYAhc9MLRi0gcwO+3QFWLdpuPYcaI
SYrNDlljEZxC3lmDhYgsWMJORUdM6LVhfk5pOSXu2oyjWgxSIjvGh6BMm3wFvljs
Bah3x9H3ZpIj3A6k20t+IPjqFiAeFCQNwgtkKFX5W3omnyZuMDwwh/su77NmYI8=
=PO1j
-----END PGP SIGNATURE-----

--Qi3LKmJoVkEooqhtC3jHBpMD5onm8co96--


From nobody Thu May  4 00:14:14 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 38918129401; Thu,  4 May 2017 00:14:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.703
X-Spam-Level: 
X-Spam-Status: No, score=-0.703 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 eNcXGblj2wDL; Thu,  4 May 2017 00:14:05 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (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 AD21F126C89; Thu,  4 May 2017 00:14:05 -0700 (PDT)
Received: from [192.168.3.100] (unknown [124.189.96.14]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 713A622E256; Thu,  4 May 2017 03:14:02 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <0859CEA7-B961-4C4D-BB1B-EB8F8D59E882@qti.qualcomm.com>
Date: Thu, 4 May 2017 17:14:00 +1000
Cc: Christian Huitema <huitema@huitema.net>, Benoit Claise <bclaise@cisco.com>, Brian Trammell <ietf@trammell.ch>, IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <68406978-0066-47EF-BE54-CF62421F5E61@mnot.net>
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net> <21A01174-4FB6-4F8C-AA3D-DCF6D1FEBA01@trammell.ch> <8cb6fefd-200e-1d90-6a36-c32530ecbaf8@cisco.com> <8114ef76-591f-630e-5464-2b63d0efea61@huitema.net> <BF887C92-1ADD-47F7-A958-04538372AA15@qti.qualcomm.com> <BD3807D4-6253-4A3E-BA34-00CA1DAB5037@mnot.net> <0859CEA7-B961-4C4D-BB1B-EB8F8D59E882@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/by1XmqAzEkIrOIeaZ2UAAbqpKCc>
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, 04 May 2017 07:14:08 -0000

> On 4 May 2017, at 12:47 pm, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:
>=20
> As I said earlier, I think it's perfectly appropriate to make sure =
that we're not endorsing any of these practices in this document, so I =
have no problem "over-communicating", for example in 2.6.5. And so long =
as "appropriate context" doesn't mean "we must explain in excruciating =
detail the wrongness of each and every wrong thing about these =
practices", I'm fine giving a little context. I just worry from some of =
the comments that some folks don't want to make mention of any practice =
without both an explicit rejection of the practice (beyond the context =
setting at the beginning of the document that it is not the purpose of =
the document to endorse, but instead simply catalog, these practices) =
and a statement of alternatives to each of the practices. I think that's =
unreasonable to ask of this sort of document. So long as it says up =
front that it is not endorsing any practice, and there is nothing in the =
description of any particular practice that could be mistaken for an =
endorsement, that's enough.

I'm not advocating going deep into the weeds. OTOH I chafe at the idea =
of a catalogue that has the theme "useful things that your network can =
do" that has things like header enrichment thrown in with *no* context =
-- which is the current state in -11.

Looking forward to the next revision.

Cheers,


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





From nobody Thu May  4 03:57:34 2017
Return-Path: <alexey.melnikov@isode.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 C2FA1129482; Thu,  4 May 2017 03:57:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.602
X-Spam-Level: 
X-Spam-Status: No, score=-0.602 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=isode.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 ynQctc5uljYc; Thu,  4 May 2017 03:57:31 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 5720B129461; Thu,  4 May 2017 03:57:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1493895450; d=isode.com; s=june2016; i=@isode.com; bh=gmyefWS3xh5lbnmGvuXLnVajpmH6e3ZEO/lEs2kmpPs=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=QP6zcl7CaeeW/YozYyZRmucf9VZACS48NBDbEAQar1jU1x/CopCMXyXJPjt6B+CuwizWMQ xXag8vfPRAwANmPdSUXeDCgrEYrEVK98X5XyVSNCXm0Obr961vVSEMn9ir1WVrFsRj4X0j NlPXfQeruiCHFBxuVu2hQR6x4yhTxf4=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <WQsJGQBV0oi5@waldorf.isode.com>; Thu, 4 May 2017 11:57:30 +0100
Subject: Re: Last Call: <draft-nottingham-rfc5988bis-05.txt> (Web Linking) to Proposed Standard
To: Julian Reschke <julian.reschke@gmx.de>, Carsten Bormann <cabo@tzi.org>, ietf@ietf.org
References: <149339514498.2963.17820948075543728710.idtracker@ietfa.amsl.com> <4BECE06F-D3E5-4F9B-9DBF-AE9150942190@tzi.org> <a6a4b727-5a01-8d8c-2c43-c2c51e668836@gmx.de>
Cc: Barry Leiba <barryleiba@computer.org>, draft-nottingham-rfc5988bis@ietf.org
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <05d7a3a5-d8a2-356b-f29b-75738bc393a3@isode.com>
Date: Thu, 4 May 2017 11:56:31 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
In-Reply-To: <a6a4b727-5a01-8d8c-2c43-c2c51e668836@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dvQdB8nmj5nTklDCeanF5SNJFYk>
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, 04 May 2017 10:57:33 -0000

On 03/05/2017 08:57, Julian Reschke wrote:
> On 2017-05-02 21:18, Carsten Bormann wrote:
>> Review of draft-nottingham-rfc5988bis-05.txt
>> Reviewer: Carsten Bormann
>> Review result: Ready with a few issues
>>
>> (This is not a complete review, but in its present state might serve
>> to initiate discussion of items relevant to RFC 6690 and thus
>> draft-ietf-core-links-json.)
>>
>> This specification updates RFC 5988.  The objectives for this update
>> are not clearly stated, but it seems to be based on experience with
>> RFC 5988 as well as based on advances possible with the publication of
>> RFC 7230.
>>
>> # Major technical
>>
>> T1: The draft does not take position what should happen when
>> serializations allowed by RFC 5988 but not by the present spec occur,
>> e.g.: ;type=text/plain (would now need to be ;type="text/plain").
>> ...
>
> FWIW, it's allowed in RFC 5988, but there's a five year old erratum 
> about it (<https://www.rfc-editor.org/errata_search.php?eid=3158>). 
> Unfortunately, the status is "held for document update", not "approved".
The change was not purely in the "oh, this is what we meant" category, 
so I think "held for document update" is fine. The change was 
incorporated in draft-nottingham-rfc5988bis-05.txt.

> (And yes, there's the orthogonal topic that people are not aware of 
> errata, see my experiment to improve that: 
> <https://greenbytes.de/tech/webdav/rfc5988.html#header.link>).
>
> Best regards, Julian



From nobody Thu May  4 13:20:45 2017
Return-Path: <aretana@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 4411F129B7D; Thu,  4 May 2017 13:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.123
X-Spam-Level: 
X-Spam-Status: No, score=-13.123 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 6Xb2V-QBQziv; Thu,  4 May 2017 13:20:25 -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 2A956129B6D; Thu,  4 May 2017 13:20:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1200; q=dns/txt; s=iport; t=1493929224; x=1495138824; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=tqZE1nb4XPYXe7meInpUz/mtHUQZzIP6Z51jilHYCvc=; b=EEV3nHduVHb/CPJKkrU7oevohpEUZbMoFBV/VH3cwtEHMI8FyLYfhvix Je91jaYiAowgfeJZahsZ8SeUVHRsBUAIKOb2hV+oBY/aUxIsbyjn4KTxf BCiruhwZKECi75Bwk7A9IwrXMkXxdwzYijuE9dx5y7whqCbwGubGEjlDB U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BSAQDAiwtZ/5tdJa1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBg1WBbgeDYYoYkVaIIo1Ngg+GJAIahDM/GAECAQEBAQEBAWsohRYBBAE?= =?us-ascii?q?jEUUFCwIBBgIaAiYCAgIfERUQAgQBDQUbiW0DDQiTbZ1hgiaHLA2DLgEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAR2BC4VUgV4rgnCCVIIPgwYugjEBBJZdhk07AY5DhFG?= =?us-ascii?q?RZ4siiRIBHziBCm8VWAGGX3aHdIENAQEB?=
X-IronPort-AV: E=Sophos;i="5.38,289,1491264000"; d="scan'208";a="230972077"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 May 2017 20:20:23 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v44KKNQ2007049 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 4 May 2017 20:20:23 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 4 May 2017 15:20:22 -0500
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1210.000; Thu, 4 May 2017 15:20:23 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "spring@ietf.org" <spring@ietf.org>, "draft-ietf-spring-ipv6-use-cases.all@ietf.org" <draft-ietf-spring-ipv6-use-cases.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Genart last call review of draft-ietf-spring-ipv6-use-cases-10
Thread-Topic: Genart last call review of draft-ietf-spring-ipv6-use-cases-10
Thread-Index: AQHSw2U/QCNPBxU/5UGUwuQ3s2zt9KHksa8A
Date: Thu, 4 May 2017 20:20:23 +0000
Message-ID: <3E209B45-90CE-4EEB-9D2B-E14EFE28DCE0@cisco.com>
References: <149374426742.21414.16408814015665498739@ietfa.amsl.com>
In-Reply-To: <149374426742.21414.16408814015665498739@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1f.0.170216
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.15.4]
Content-Type: text/plain; charset="utf-8"
Content-ID: <12F4954EB767504EBAE4A46677536D83@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vhcHPTtMIqRbRj3mHmPp_7BMuoQ>
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, 04 May 2017 20:20:26 -0000

T24gNS8yLzE3LCAxMjo1NyBQTSwgIlN0ZXdhcnQgQnJ5YW50IiA8c3Rld2FydC5icnlhbnRAZ21h
aWwuY29tPiB3cm90ZToNCg0KU3Rld2FydDoNCg0KSGkhICBIb3cgYXJlIHlvdT8NCg0KVGhhbmtz
IGZvciB0aGUgZGV0YWlsZWQgcmV2aWV3IQ0KDQo+IEEgc2lnbmlmaWNhbnQgcGFydCBvZiB0aGUg
anVzdGlmaWNhdGlvbiBzZWVtcyB0byBldm9sdmUgYXJvdW5kIHRoZQ0KPiBpbmFiaWxpdHkgb2Yg
TVBMUyB0byBmdW5jdGlvbiBpbiBhbiBJUHY2IG9ubHkgbmV0d29yay4NCg0KSXQgc2VlbXMgdG8g
bWUgdGhhdCB0aGlzIHN0YXRlbWVudCBzdW1tYXJpemVzIG1hbnkgb2YgdGhlIGNvbmNlcm5zIHlv
dSBsaXN0ZWQgYXMgTWFqb3IgaW4gdGhlIHJldmlldy4gIEkgY2FuIHNlZSB3aHkgaXQgc2VlbXMg
bGlrZSB0aGUganVzdGlmaWNhdGlvbiBpczog4oCcYmVjYXVzZSBNUExTIGRvZXNu4oCZdCB3b3Jr
LCB0aGVuIHdlIGhhdmUgdG8gZG8gSVB2Ni7igJ0g4oCTIGJ1dCBJIHRoaW5rIHRoYXQgZXZlbiBp
ZiBhIGNvbXBsZXRlIHNvbHV0aW9uIGV4aXN0cyAoZm9yIGFuIE1QTFMgZGVwbG95bWVudCBvbiBh
biBJUHY2LW9ubHkgbmV0d29yayksIHNvbWUgb3BlcmF0b3JzIHdvdWxkIHN0aWxsIG1ha2UgdGhl
IGRlc2lnbiBjaG9pY2Ugb2YgcHJlZmVycmluZyBhbiBJUHY2LW9ubHkgZGVwbG95bWVudC4NCg0K
SSB0aGluayB0aGF0IGl0IHdvdWxkIGJlIGdvb2QgZm9yIHRoZSBhdXRob3JzIHRvIHJlZm9jdXMg
dGhlIGp1c3RpZmljYXRpb24gYXdheSBmcm9tIOKAnGJlY2F1c2UgWCBkb2VzbuKAmXQgd29ya+KA
nS4gIFdvdWxkIHRoYXQgYWRkcmVzcyB0aGlzIHBhcnQgb2YgeW91ciBjb25jZXJucz8NCg0KVGhh
bmtzIQ0KDQpBbHZhcm8uDQoNCg==


From nobody Thu May  4 14:59:16 2017
Return-Path: <simon.tls@a-oben.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 0B39D127333; Thu,  4 May 2017 14:59:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.801
X-Spam-Level: 
X-Spam-Status: No, score=-2.801 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 1n2Y54K8Oo0j; Thu,  4 May 2017 14:59:05 -0700 (PDT)
Received: from a-oben.org (squint.a-oben.org [144.76.111.201]) (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 D3834128B37; Thu,  4 May 2017 14:59:04 -0700 (PDT)
Received: from [81.164.186.174] (helo=[192.168.0.234]) by a-oben.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.88) (envelope-from <simon.tls@a-oben.org>) id 1d6Ols-00062O-4Q; Thu, 04 May 2017 23:59:03 +0200
Subject: Re: [TLS] Last Call: <draft-ietf-tls-ecdhe-psk-aead-03.txt> (ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transport Layer Security (TLS)) to Proposed Standard
To: ietf@ietf.org
References: <149391606578.6842.3727373203321848879.idtracker@ietfa.amsl.com>
Cc: "tls@ietf.org" <tls@ietf.org>
From: Simon Friedberger <simon.tls@a-oben.org>
Message-ID: <4373f972-bf9b-4dbe-1b59-7f51846831f3@a-oben.org>
Date: Thu, 4 May 2017 23:58:47 +0200
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: <149391606578.6842.3727373203321848879.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HK3Y_Vq_cyiw9oFP6-tVsdnMIT4>
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, 04 May 2017 21:59:07 -0000

Nits:

	RFC 4279 reference is missing.

	"TLS 1.3 and above version, " should probably be "TLS 1.3 and above" or "TLS 1.3 and higher versions"

On 04/05/17 18:41, The IESG wrote:
> The IESG has received a request from the Transport Layer Security WG
> (tls) to consider the following document:
> - 'ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transport Layer
>    Security (TLS)'
>   <draft-ietf-tls-ecdhe-psk-aead-03.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-05-18. 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 defines several new cipher suites for the Transport
>    Layer Security (TLS) protocol.  The cipher suites are all based on
>    the Ephemeral Elliptic Curve Diffie-Hellman with Pre-Shared Key
>    (ECDHE_PSK) key exchange together with the Authenticated Encryption
>    with Associated Data (AEAD) algorithms AES-GCM and AES-CCM.  PSK
>    provides light and efficient authentication, ECDHE provides perfect
>    forward secrecy, and AES-GCM and AES-CCM provides encryption and
>    integrity protection.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-tls-ecdhe-psk-aead/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-tls-ecdhe-psk-aead/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls


From nobody Thu May  4 15:08:45 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 B99F9129508; Thu,  4 May 2017 15:08:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: recentattendees@ietf.org, ietf@ietf.org
Subject: IETF 99 Hackathon Registration and Meeting Information
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: IETF Agenda <agenda@ietf.org>
Message-ID: <149393572366.6807.1754316023319166602.idtracker@ietfa.amsl.com>
Date: Thu, 04 May 2017 15:08:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ITnNRcZ8Hek8KiyWKEvVk0PH0dk>
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, 04 May 2017 22:08:44 -0000

IETF 99
Prague, Czech Republic
July 16-21, 2017
Host: Comcast/NBCUniversal and CZ.NIC

IETF 99 Information: https://ietf.org/meeting/99/index.html
Register online at: https://ietf.org/meeting/register.html

1.  Registration
2.  Value Added Tax (VAT)
3.  Visas & Letters of Invitation
4.  Accommodations
5.  Social Event!
6.  Hackathon

1. Registration:

Registration fees do not include the VAT of 21%. The VAT will be added to the fee and paid over to the tax authorities.

	A. Early-Bird Registration: USD 700.00, if paid in full prior to 23:59 UTC 2017-07-07
	B. After Early-Bird cutoff: USD 875.00
	C. Full-time Student Registrations: USD 150.00 (with proper ID)
	D. One Day Pass Registration: USD 375.00
	E. Registration Cancellation   
	Cutoff for registration cancellation is Monday, 10 July 2017 at UTC 23:59. 
	Cancellations are subject to a 10% (ten percent) cancellation fee if requested by 
	that date and time.
	F. Online Registration and Payment ends Friday, 14 July, 2017, 17:00 local Prague time
	G. On-site Registration begins on Sunday, 16 July 2017 at 10:00 local Prague time.

2. Value Added Tax (VAT)

	You may be entitled to recoup some or all of the VAT.
	In addition to a receipt from the IETF, all IETF 99
	attendees will receive a VAT compliant invoice from BC&A
	(VMC), our tax agent. For this meeting the Czech VAT of
	21% has been added to the Registration Fee. More
	information is available at:
	https://www.ietf.org/meeting/99/vat.html

3. Visas & Letters of Invitation:

	Letters of invitation are available through the registration
	system. Once you register for IETF 99 you may request a local
	letter of invitation through a link in your confirmation email or
	the self-service portal. 

4.  Accommodations:
	
	1. Hilton Prague (Headquarters Hotel, block of 600 rooms)
	Room Rate:  $148 (single) $164 (double) USD. Includes in-room high-speed
	Internet and breakfast.
	VAT of 15% (taxes subject to change) is excluded from
	the above prices.
	Reservation Cutoff Date: 19 June 2017
	Cancel with No Penalty: 7 Days prior to arrival
	Distance to Meeting Venue: N/A
	More detail at: http://www.ietf.org/meeting/99/hotel.html
	Reservations: http://eventsathilton.com/show/58ca77f5e6f1441222ee7b5e
	
	2. Hilton Prague Old Town (Overflow hotel, block of 140)
	Room Rate: $148 (single) $163 (double) USD. Includes in-room high-speed
	Internet and breakfast.
	VAT of 15% (taxes subject to change) is excluded from
	the above prices.
	Reservations Cutoff Date: 27 June 2017
	Cancel with No Penalty: Up to 72 hours prior to check-in/arrival
	Distance to Meeting Venue: 11 minute walk
	Reservations: http://eventsathilton.com/show/58ca6c33e6f1441222ee7b58

5. Social Event
	Date: Tuesday, 18 July 2017
	Time: 18:30 - 22:00
	Cost: $20 USD per ticket, limit two per attendee. Children 10 and under are free. 
	Hosted by: CZ.NIC, Comcast, and NBC Universal
	Location: Kafka museum at Hergetova Cihelna
	
	Join us on Tuesday, July 18 from 18:30 to 22:00 for a
	tour of the Kafka museum at Hergetova Cihelna. A boat
	ride to the event will start the evening off before you
	experience an interactive tour of different eras of
	Prague's history and meet iconic Czech personas that
	changed the country. The event will have Czech and other
	cuisines, beer, wine and non-alcoholic beverages.

	More information here: https://www.ietf99.cz/#socialevent
	Link to purchase Social Tickets: https://www.ietf.org/registration/ietf99/eventticket.py

6. Hackathon
	The IETF is holding a Hackathon at IETF 99 to encourage
   	developers to discuss, collaborate and develop utilities, ideas,
   	sample code and solutions that show practical implementations of
   	IETF standards.

	When: Saturday July 15 and Sunday July 16
	Where: Hilton Prague, Room TBD
	Signup for the Hackathon: https://www.ietf.org/registration/ietf99/hackathonregistration.py
	More information can be found here: http://ietf.org/hackathon/99-hackathon.html 
	Keep up to date by subscribing to: https://www.ietf.org/mailman/listinfo/hackathon

	The IETF is still seeking a Hackathon sponsor for 2017! For more information please see: 
	https://iaoc.ietf.org/host-and-sponsorship.html
	Contact Howard Baggott if interested, baggott@isoc.org.

	The Hackathon is free to attend and open to all. Extend
	the invitation to colleagues outside the IETF!

	Descriptions and information regarding the technologies
	for the hackathon are located on the IETF 99 Meeting Wiki:
	https://www.ietf.org/registration/MeetingWiki/wiki/99hackathon

	Don’t see anything that interests you? Feel free to add
	your preferred technology to the list, sign up as its
	Champion and show up to work on it. Note: you must login to
	the wiki to add content. If you do add a new technology, we
	strongly suggest that you send an email to hackathon@ietf.org
	to let others know. You may generate interest in your
	technology, and find other people who want to contribute to
	it.

	To request a wiki account, please click on the “login”
	button on the bottom right corner of the page, and choose
	“register.” If you need a new password please click on the
	“login” button on the bottom right corner of the page and
	choose “Send new password.”


From nobody Thu May  4 20:34:22 2017
Return-Path: <peter@akayla.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 C226B127078; Thu,  4 May 2017 20:34:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Peter Yee <peter@akayla.com>
To: <gen-art@ietf.org>
Cc: manet@ietf.org, ietf@ietf.org, draft-ietf-manet-olsrv2-multipath.all@ietf.org
Subject: Genart last call review of draft-ietf-manet-olsrv2-multipath-12
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149395525273.6861.14988459288524802803@ietfa.amsl.com>
Date: Thu, 04 May 2017 20:34:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hj7fesrD0gsujL7cxSplTGccQ3Q>
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, 05 May 2017 03:34:13 -0000

Reviewer: Peter Yee
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-manet-olsrv2-multipath-12
Reviewer: Peter Yee
Review Date: 2017-05-04
IETF LC End Date: 2017-05-04
IESG Telechat date: 2017-05-11

Summary: This Experimental draft is ready with nits.  The draft
specifies an interoperable, multipath extension to OLSRv2.  Other than
the nits, I find the draft to be a fine experiment to help determine
how well OLSRv2 can be improved by allowing multiple, disjoint paths
between nodes.

Major issues: None

Minor issues: None

Nits/editorial comments: 

General:

I'd suggesting changing occurrences of "multi-path" to "multipath" for
consistency with prior works, including the primary work by the same
authors [ADHOC11].

Consider changing "Multi-path Dijkstra Algorithm" to "multipath
Dijkstra's algorithm".  In any case, use the name consistently - it
varies throughout the document.

Change "Round-Robin" (and variations in capitalization) to
"round-robin" throughout the document.

Stick to one capitalization form for "MP-OLSRv2 Routing Process".

Section 10 was not reviewed because it contains RFC Editor
instructions to delete it.

Specific:

Page 3, section 1, 2nd paragraph, last sentence: append a comma after
"reliability".

Page 3, section 1, 3rd paragraph, 1st sentence: delete the leading
"The".  Insert "the "before "Multi-path Dijkstra".  [See general
comment about hyphenating multi-path].

Page, section 1.1, 4th bullet item: delete the second "the".

Page 4, 1st full paragraph, 2nd sentence: change "Standard" to
"Standards".  Delete comma after "Track".

Page 4, 2nd bullet item, 3rd sentence: change "setting" to "applying".
 (This is an aesthetics comment - take it or leave it.)

Page 4, 4th bullet item, 3rd sentence: expand acronym "MPR" on first
usage and in general do so for all acronyms that would not be
immediately obvious to a large audience.

Page 4, 5th bullet item, 4th sentence: delete "the" before "loose".

Page 4, 6th bullet, 3rd sentence: append "parts" after "following".

Page 6, section 3, 1st paragraph, 2nd sentence: delete both commas.

Page 6, section 3, 2nd paragraph, 2nd sentence: delete "the" before
"information".  Insert "a" before "DiffServ".  Change "Code Point" to
codepoint.  [RFC 2474 only refers to these a "Code Point" in specific
names, but otherwise uses the generic form "codepoint".

Page 6, section 3, 3rd paragraph, 1st sentence: insert "a" before
"new".

Page 6, section 3, 3rd paragraph, 3rd sentence: insert "the" before
"loose".

Page 7, section 4, 3rd bullet item: insert "the" before "shortest".

Page 8, partial paragraph at top: change "as" to "using the".

Page 8, section 5.1, SR_TC_INTERVAL definition: change "a" to "an".

Page 8, section 5.1, SR_HOLD_TIME_MULTIPLIER definition:  change
"minimal" to "minimum".  Change "a" to "an" unless that acronym is
spoken like a word and not spelled out.

Page 8, section 6, 2nd sentence: delete comma after "datagram".

Page 9, section 6.1, 1st sentence: insert "the" before "MP-OLSRv2".  

Page 9, section 6.1.1, 1st paragraph, 1st sentence: change
"signalling" to "signaling".  [Other words in the document tend to
suggest that the American spellings are being used rather than British
forms.]

Page 9, section 6.2.1, 1st sentence: insert "the" before "loose".

Page 10, section 7.1, 1st paragraph, 2nd sentence: delete the comma. 
Insert "the" before each of "MP-OLSRv2" and "OLSRv2".

Page 11, section 8, 2nd sentence: insert "the" before "topology".

Page 11, section 8, 3rd sentence: change "between" to "from the".

Page 11, section 8.1, 2nd paragraph, 2nd sentence: insert "the" before
"SR_TC_INTERVAL".

Page 11, section 8.1, 2nd paragraph, 3rd sentence: delete "The".

Page 11, section 8.1, 2nd paragraph, 5th sentence: insert "the" before
"SOURCE_ROUTE TLV".

Page 12, section 8.3, 1st bullet item: change "possiblity" to
"possibility".

Page 12, section 8.3, 2nd bullet item, 2nd sentence: perhaps change
"Or else" to "Otherwise".

Page 12, section 8.4, 1st paragraph: insert "a" before "DiffServ". 
Change "Code Point" to "codepoint".

Page 13, 1st paragraph, last sentence: insert "the" before "OLSRv2".

Page 13, 3rd paragraph, 2nd sentence: insert "the" before "format".

Page 13, the paragraph: insert "the" before "following".

Page 13, last paragraph, 2nd sentence: insert "the" before "outer" and
"source".

Page 14, section 8.5.1, 1st paragraph after the 1st set of bullet
items: insert "the" before "SR-OLSRv2".

Page 14, section 8.5.1, 2nd paragraph after the 1st set of bullet
items, 3rd sentence: insert "the" before "OLSRv2".

Page 14, section 8.5.1, 2nd paragraph after the 1st set of bullet
items, 4th sentence: change "much" to "many".

Page 14, section 8.5.1, 3rd paragraph after the 1st set of bullet
items: shouldn't this be up to "NUMBER_OF_PATHS" rather than always
"NUMBER_OF_PATHS" paths that are created?  Meaning that it's possible
the algorithm will not have sufficient disjoint paths to choose from
in some (probably degenerate) cases?  Delete the second comma in the
sentence.

Page 14, section 8.5.1, 2nd set of bullet items, 2nd bullet item, 1st
sentence: change "A" to "An".

Page 14, section 8.5.1, 2nd set of bullet items, 2nd bullet item, 2nd
sentence: insert "the" before "Multi-path".

Page 14, section 8.5.2, 1st sentence: insert "the" before
"Multi-path".

Page 15, 1st full paragraph, 1st sentence: change the second
occurrence of "Dijkstra" to "Dijkstra's".

Page 15, 2nd bullet item, 2nd sentence: change "is" to "does".

Page 15, 1st paragraph after bullet items, 3rd sentence: change
"vetex" to "vertex".

Page 15, 1st paragraph after figure, 2nd sentence: change "of" to
"for".

Page 16, 1st sentence: change "Dijkstra" to "Dijkstra's".

Page 16, 1st paragraph after numbered list: insert "the" before
"Multi-path".

Page 16, section 8.6, 1st paragraph, last sentence: insert "whether"
before "the set".

Page 16, section 9, 1st sentence: change "guideline" to "guidelines".

Page 16, section 9, 2nd sentence: delete the comma after "certain".

Page 17, "if id<fe<fp" bullet item: would it make more sense to use "a
greater" instead of "more"?

Page 19, section 11, 2nd paragraph, 1st sentence: change "Process" to
"Processes".

Page 19, section 11, 2nd paragraph, 2nd sentence: delete "be".

Page 19, section 11, 3rd paragraph: append "with" after "As".

Page 19, section 11, 4th paragraph, 1st sentence: insert "The" before
"MP-OLSRv2".

Page 19, section 11, 4th paragraph, 2nd sentence: insert "the" before
"source".

Page 20, 1st paragraph, 4th sentence: should "ancient" be "the
oldest"?

Page 20, 1st paragraph, 5th sentence: delete comma after "that". 
Insert "a" before "large".  Maybe change "initiates" to "sends". 
Delete the comma after "which".

Page 24, 1st paragraph after Figure 2, 1st sentence:  insert "the"
before "name".  Change "name" to "names".

Page 24, 1st paragraph after Figure 2, 2nd sentence: change
"parenthesis" to "parentheses".

Page 24, 3rd paragraph after Figure 2, 3rd sentence: while I
understand "punishment", that term hasn't been used previously and
might be confusing.  A variant occurs elsewhere in the document. 
Consider explaining what you mean by punishment.

Page 24, 2nd paragraph after Figure 3, 1st sentence: change "path" to
"paths".  Append "in order" after "paths".

Page 24, 3rd paragraph after Figure 3, 2nd sentence: change
"undesired" to "undesirable".


From nobody Fri May  5 01:19:39 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 DF5E4126CF6 for <ietf@ietfa.amsl.com>; Fri,  5 May 2017 01:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.401
X-Spam-Level: 
X-Spam-Status: No, score=-5.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, 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 WiadjuWtRsho for <ietf@ietfa.amsl.com>; Fri,  5 May 2017 01:19:34 -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 0A656129477 for <ietf@ietf.org>; Fri,  5 May 2017 01:19:33 -0700 (PDT)
Received: from pps.filterd (m0098414.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v454nKZQ140495 for <ietf@ietf.org>; Fri, 5 May 2017 00:53:22 -0400
Received: from e18.ny.us.ibm.com (e18.ny.us.ibm.com [129.33.205.208]) by mx0b-001b2d01.pphosted.com with ESMTP id 2a8hfj2kcb-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 05 May 2017 00:53:22 -0400
Received: from localhost by e18.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, 5 May 2017 00:53:21 -0400
Received: from b01cxnp22033.gho.pok.ibm.com (9.57.198.23) by e18.ny.us.ibm.com (146.89.104.205) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 5 May 2017 00:53:19 -0400
Received: from b01ledav002.gho.pok.ibm.com (b01ledav002.gho.pok.ibm.com [9.57.199.107]) by b01cxnp22033.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v454rIKp43909240 for <ietf@ietf.org>; Fri, 5 May 2017 04:53:18 GMT
Received: from b01ledav002.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 880C2124037 for <ietf@ietf.org>; Fri,  5 May 2017 00:53:13 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b01ledav002.gho.pok.ibm.com (Postfix) with ESMTPS id 6FC4B124035 for <ietf@ietf.org>; Fri,  5 May 2017 00:53:13 -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 v454rH22024634 for <ietf@ietf.org>; Fri, 5 May 2017 00:53:17 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v454rHd7024617 for ietf@ietf.org; Fri, 5 May 2017 00:53:17 -0400
From: narten@us.ibm.com
Date: Fri, 05 May 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: 17050504-0044-0000-0000-00000322569F
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00007024; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000209; SDB=6.00856348; UDB=6.00423979; IPR=6.00635616;  BA=6.00005326; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00015312; XFM=3.00000014; UTC=2017-05-05 04:53:19
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17050504-0045-0000-0000-0000075060F9
Message-Id: <201705050453.v454rHd7024617@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-05-05_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=99 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1705050050
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zyHsQ8KNr3QuwQHM4ECvI5C0s0w>
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, 05 May 2017 08:19:37 -0000

Total of 74 messages in the last 7 days.
 
script run at: Fri May  5 00:53:12 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  9.46% |    7 |  7.18% |    55406 | mnot@mnot.net
  6.76% |    5 |  4.22% |    32599 | randy@psg.com
  4.05% |    3 |  3.88% |    29980 | kathleen.moriarty.ietf@gmail.com
  2.70% |    2 |  5.04% |    38872 | weigengyu@bupt.edu.cn
  2.70% |    2 |  4.83% |    37253 | ldaigle@thinkingcat.com
  4.05% |    3 |  3.23% |    24920 | brian.e.carpenter@gmail.com
  2.70% |    2 |  4.15% |    32062 | lear@cisco.com
  2.70% |    2 |  3.57% |    27591 | bclaise@cisco.com
  2.70% |    2 |  2.70% |    20820 | presnick@qti.qualcomm.com
  2.70% |    2 |  2.66% |    20530 | fredbaker.ietf@gmail.com
  2.70% |    2 |  2.61% |    20154 | ietf@trammell.ch
  2.70% |    2 |  2.27% |    17541 | julian.reschke@gmx.de
  2.70% |    2 |  2.24% |    17298 | jclarke@cisco.com
  2.70% |    2 |  2.10% |    16210 | cabo@tzi.org
  1.35% |    1 |  3.34% |    25781 | nishida@sfc.wide.ad.jp
  1.35% |    1 |  2.84% |    21957 | davenoveck@gmail.com
  1.35% |    1 |  2.83% |    21884 | farmer@umn.edu
  2.70% |    2 |  1.46% |    11246 | jmh@joelhalpern.com
  1.35% |    1 |  2.18% |    16814 | phil@juniper.net
  1.35% |    1 |  2.17% |    16765 | stewart.bryant@gmail.com
  1.35% |    1 |  1.93% |    14861 | asmusf@ix.netcom.com
  1.35% |    1 |  1.90% |    14695 | jonathan@hansfords.net
  1.35% |    1 |  1.62% |    12497 | peter@akayla.com
  1.35% |    1 |  1.57% |    12143 | acee@cisco.com
  1.35% |    1 |  1.48% |    11452 | ajs@anvilwalrusden.com
  1.35% |    1 |  1.43% |    11075 | marius.georgescu@rcs-rds.ro
  1.35% |    1 |  1.37% |    10605 | bill.wu@huawei.com
  1.35% |    1 |  1.30% |    10021 | ietf-secretariat@ietf.org
  1.35% |    1 |  1.29% |     9975 | blong@google.com
  1.35% |    1 |  1.26% |     9740 | adrian@olddog.co.uk
  1.35% |    1 |  1.24% |     9569 | joelja@bogus.com
  1.35% |    1 |  1.18% |     9143 | huitema@huitema.net
  1.35% |    1 |  1.17% |     9038 | aretana@cisco.com
  1.35% |    1 |  1.16% |     8926 | alissa@cooperw.in
  1.35% |    1 |  1.12% |     8680 | martin.thomson@gmail.com
  1.35% |    1 |  1.11% |     8598 | jordi.palet@consulintel.es
  1.35% |    1 |  1.11% |     8534 | buhrmi@gmail.com
  1.35% |    1 |  1.09% |     8418 | petr.spacek@nic.cz
  1.35% |    1 |  1.07% |     8292 | shtsuchi@arista.com
  1.35% |    1 |  1.04% |     8039 | alexey.melnikov@isode.com
  1.35% |    1 |  1.00% |     7721 | simon.tls@a-oben.org
  1.35% |    1 |  0.95% |     7367 | ietf-trust@ietf.org
  1.35% |    1 |  0.95% |     7364 | stewart@g3ysx.org.uk
  1.35% |    1 |  0.93% |     7209 | jonathan.hardwick@metaswitch.com
  1.35% |    1 |  0.92% |     7105 | lhotka@nic.cz
  1.35% |    1 |  0.88% |     6811 | lear@ofcourseimright.com
  1.35% |    1 |  0.87% |     6709 | housley@vigilsec.com
  1.35% |    1 |  0.82% |     6344 | nick@foobar.org
  1.35% |    1 |  0.70% |     5372 | ron.even.tlv@gmail.com
--------+------+--------+----------+------------------------
100.00% |   74 |100.00% |   771986 | Total


From nobody Fri May  5 01:31:18 2017
Return-Path: <bob.hinden@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 0ED83129401; Fri,  5 May 2017 01:31:17 -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 neTnMR-Qh75F; Fri,  5 May 2017 01:31:15 -0700 (PDT)
Received: from mail-wr0-x242.google.com (mail-wr0-x242.google.com [IPv6:2a00:1450:400c:c0c::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E1D0129447; Fri,  5 May 2017 01:31:14 -0700 (PDT)
Received: by mail-wr0-x242.google.com with SMTP id g12so3651196wrg.2; Fri, 05 May 2017 01:31:14 -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=ELmhcFUdD2F50vBVI4sLPKUyBZF1rumlccSeD9oTOgE=; b=sRYoO+wqfFcFuaCtdTRL6AUZ81X6uFSnyJDTfyRXDRhFvZz0lyeMuCeM28gf/d1onp fo10qARwXCDhcJAZBcT8Yt4gl7cGIpxXpuLAevt0jWqbFqOuasehUBNYFaLq8N0MSXh7 o7owxd5tY1Lj0HAwi31v04ZPBh5jM3jnuin3XqBnukEm6q27+9BFK36/mZ6sOxLCzKia g05wsgYO4A7X0n3BVjjY1SA8LZKbmPVIqw1AaAUYlfxOxZKGrxnwNRQIXG5wjxbOZpVP gj5Ui5aZP1GUynjrzaKPe0Z7IWoMTUCYMQ59FIvuQlvBlzgXWizFbPzIdU4PDJRqN8hJ q2MQ==
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=ELmhcFUdD2F50vBVI4sLPKUyBZF1rumlccSeD9oTOgE=; b=MIDRh5gY5e21tZvLYgStedD8Rskgd6EDgmxoYQ/8nerbdYa3bEGzcl5cmZTg1b+Dz4 rrw0LsGRWkHJrKqgUHgv+i/fI5IRZZ44htmaCkNHzS6DrLXkqmh4LQrQpyn/pJqT1xsL z61wyKUefRuTRwoowvR5wVjWEVTitUrKJiJdAaDOVJ/E9xvoZnBcmbJJ7BXPlngTpU9k I/n1L2SNEg/gA2QJRVvry6YVHD/qKnEyDxj5S60UA+44aGvGgytCHwaenC7C387149pv P5st3aFGAOPs3NHnds+hR20aZyB7i6OOdGUD84tyFUiKVWYku+yUR2gKrBF4Qs2S1p4g NmtA==
X-Gm-Message-State: AN3rC/6+0mU2vp+A9gUPRaaXGzps9LuMCc3PP+gVDfxgT+fAogpdGwsP 5UiBna0JCqmVlw==
X-Received: by 10.223.136.131 with SMTP id f3mr32540527wrf.70.1493973072988; Fri, 05 May 2017 01:31:12 -0700 (PDT)
Received: from [192.168.1.33] ([77.125.68.206]) by smtp.gmail.com with ESMTPSA id t124sm1165589wma.10.2017.05.05.01.31.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 May 2017 01:31:11 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <7CFCE1D1-CBBA-4B1A-AC4D-587D1ED8464B@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_6E34E0DB-172F-4225-8403-B5869E2075C8"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Rtgdir last call review of draft-ietf-6man-rfc1981bis-06
Date: Fri, 5 May 2017 11:31:08 +0300
In-Reply-To: <149283456181.25913.15133934620501134310@ietfa.amsl.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, rtg-dir@ietf.org, IPv6 List <ipv6@ietf.org>, IETF <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
To: Ines Robles <mariainesrobles@googlemail.com>
References: <149283456181.25913.15133934620501134310@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-hrDOsHa01rGjJKOAuTudGVbW7k>
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, 05 May 2017 08:31:17 -0000

--Apple-Mail=_6E34E0DB-172F-4225-8403-B5869E2075C8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Ines,

Thanks for the review.

Comments below.

Bob


> On Apr 22, 2017, at 7:16 AM, Ines Robles =
<mariainesrobles@googlemail.com> wrote:
>=20
> Reviewer: Ines Robles
> Review result: Has Nits
>=20
> Document: draft-ietf-6man-rfc1981bis-06.txt
>=20
> Reviewer: Ines Robles
>=20
> Review Date: April 21, 2017
>=20
> Intended status: Standards Track
>=20
>=20
> Summary:
>=20
> This document describes Path MTU Discovery for IP version 6
>=20
> I believe the draft is technically good. I have no =E2=80=9CMajor=E2=80=9D=
 issues
> with this I-D. I have some minor comments.
>=20

Good, thanks.

>=20
> Comments:
>=20
> 1- I think that it would be nice to add a graphical example that
> describes the process of the Path MTU Discovery (including a Packet
> Too Big Message). e.g. Figure 1 of RFC 5927[1].

I will consider it, but sure what it would look like.  Suggestions?

>=20
> 2- Section 1:
>=20
> 	2.1- I would add a reference when you mention black hole =
connection.
> What about section 2.1 of [2] or [3]?
>=20

I will add RFC2923.  The other is an expired draft that I don=E2=80=99t =
think it appropriate to reference.

> 3- Section 2:
>=20
> 	3.1- EMTU_S =3D> When it is defined, it references RFC6691. But =
this
> term is not mentioned in RFC6691. I would add additionally a reference
> to RFC 1122 [4] which defines EMTU_S.
>=20

OK

> 	3.2- I would add also the same references for EMTU_R.

OK

>=20
> 4.Section 3:
>=20
> 	4.1- In the first paragraph, I would add a reference to ICMPv6 =
the
> first time that ICMPv6 Packet Too Big message is mentioned. And I
> would add here also "(ICMPv6 PTB)" since it used further in the
> document.

There is a reference to ICMPv6 the first time it shows up in Section 1.  =
I don=E2=80=99t think another is needed for ICMPv6 PTB.

>=20
> 	4.2- In the first paragraph: "...to send smaller fragments or =
..."
> --> I think it would be clearer "to send smaller packets or=E2=80=A6"

I agree, =E2=80=9Cpackets=E2=80=9D is better here.  It=E2=80=99s =
consistent with the definition in Section 2.

>=20
> 	4.3- Second Paragraph: "...process ends when the node's =
estimate..."
> -> "...process ends when the source node's estimate=E2=80=A6"?

OK

>=20
> 	4.4- Last Paragraph: "can to appear" -> "can appear" . "...but =
is in
> fact..." -> "...but it is in fact=E2=80=A6"

OK

>=20
> 5. Section 4:
>=20
> 	4.1- about this: "The node MUST reduce the size of the packets =
it is
> sending along the path". I would add an explanation to which size the
> packet should be reduced (maybe based in an initial example)

This is described in the previous paragraph.

>=20
>=20
> 6.Section 5:
>=20
> 	6.1- I would add a reference to RFC 1122 [4] when MMS_S is =
mentioned.

OK

>=20
>=20
> 	6.2- Section 5.5: "Some transport protocols are not allowed to
> repacketize when doing a retransmission..." I would add some
> examples.

I will look into that.

>=20
> 7. Section 6:
>=20
> 	7.1- What about to mention Blind Performance-Degrading Attack =
[5]?

This is protected against by not allow the MTU to be set below 1280 and =
changes in rfc2460bis fragmentation.

>=20
>=20
>>=20
> [1] https://tools.ietf.org/html/rfc5927#section-7.3
> [2] https://tools.ietf.org/html/rfc2923
> [3] =
https://tools.ietf.org/html/draft-jacquin-opsawg-icmp-blackhole-problem-00=

> [4] https://tools.ietf.org/html/rfc1122#page-58
> [5] https://tools.ietf.org/html/rfc5927#section-7




--Apple-Mail=_6E34E0DB-172F-4225-8403-B5869E2075C8
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQEcBAEBCgAGBQJZDDhMAAoJEK7rdBF357uotFEH/iBvAO+rLMUDG2lue9f3YbcK
eAIte8Hc7uQJaUlkvJtAP5AAIeyOKeEW/h4CiaGyUKGKGEHRM1MLL0HJUIM/lUkX
hPCnM0w/FfeMr40CLly7EQvYXf0W8ScyadcEddN5ItyLKAOz6uBBk3q233NhDrtq
wHLaXABYkbT9N+2OVWcB0Ob7R1S7colsaoXqBlmW/cDdxfwRHhQyXzdTMUV1Ys9a
iYeiM7ArDR5UWH01oPFH1g8XRpnY9FqtpHbCKPZ/YBOdE44hxLdUwLwK3bfA8C/t
WsKQjDfMUDi3B2xB/AJEa3rpL+01SHcZWJdQ69JWnPl9bGyFr+KEoL4sJ2YdpoQ=
=5dpn
-----END PGP SIGNATURE-----

--Apple-Mail=_6E34E0DB-172F-4225-8403-B5869E2075C8--


From nobody Fri May  5 02:52:33 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 B9379127444; Fri,  5 May 2017 02:52:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 67bj1w3HyFaQ; Fri,  5 May 2017 02:52:17 -0700 (PDT)
Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::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 713E2129494; Fri,  5 May 2017 02:52:14 -0700 (PDT)
Received: by mail-wr0-x229.google.com with SMTP id z52so741043wrc.2; Fri, 05 May 2017 02:52:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=dAVff+ELhE+R+mrhkGqWGeDb0Pokp/P4b7/LNu1q6UU=; b=ovKfyDLS6QgKlIdeHcUOqDkYns3Jv4sI7O99SdCadR7wI3uiblWtxl8iJeTQg+xBgv rlr58ezXMH6naqOp6MRBWVgMMOY3LzUSalg7b9lNb8KCvbkJlkE8u3VKbcZGiUUAi1UX SpXN1qGsD68WXSXQvsxWcgUKb59BB46bQ3bh2RfOzNwotHN2QMnSW549riW37TW/EMtw lKB4BJGNTd3EFjxyjM7DmVobtpWM4ypgb011cbkLNjP62ezMK+INwSrU3DpLwx2Qpfx4 itcreic28s7crwXeL3cfHwGCIFySQ6jrRngY/kURrAs4uhXWj4wk3c2D2gvqead44ZwX YPgg==
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=dAVff+ELhE+R+mrhkGqWGeDb0Pokp/P4b7/LNu1q6UU=; b=bYBu/wzmkhwfQXU7f0/bmssq8YcqeqF9jkymcV07gBrN2yb7VF9IO2j6VWWrKwtEie 9NurNNFM5gn5BeGhF/ygSIGxGpI+5quvom9lFx5FHqPth87a9VvQNBQlFDMSAvBcvT5e KtpoADhRuuh4vYV7+YBYEZRRp0HARSiG0/burXgR3BOhUB6ENa9S909lpFpbt+dwaSa1 KXxFF2t+rNdNY+naFoAumHgViEILGbLw6xIQYO+b9VPAw3xZqEklowqb/4Sl+H7dZJRK W/XpYU2lsQwYByoQnnk+DMf+pwM0V7wFTV0+S3UZz4WeJJuvVclAKn9YWpm4T3VZ1fnd FPIA==
X-Gm-Message-State: AN3rC/7Du2H1Qmqe/Wi9iljeWOrpPhZ2he/E3cdxc4MUFNua3ydncfM/ dI+lFS6siWvzsA==
X-Received: by 10.223.142.135 with SMTP id q7mr30804325wrb.180.1493977933007;  Fri, 05 May 2017 02:52:13 -0700 (PDT)
Received: from [10.66.12.31] ([131.227.23.37]) by smtp.gmail.com with ESMTPSA id f2sm1570032wmh.27.2017.05.05.02.52.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 May 2017 02:52:12 -0700 (PDT)
Subject: Re: Genart last call review of draft-ietf-spring-ipv6-use-cases-10
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <149374426742.21414.16408814015665498739@ietfa.amsl.com> <3E209B45-90CE-4EEB-9D2B-E14EFE28DCE0@cisco.com>
Cc: "spring@ietf.org" <spring@ietf.org>, "draft-ietf-spring-ipv6-use-cases.all@ietf.org" <draft-ietf-spring-ipv6-use-cases.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <87a1534f-079d-3707-9f5d-9327e831bf7a@gmail.com>
Date: Fri, 5 May 2017 10:52:16 +0100
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: <3E209B45-90CE-4EEB-9D2B-E14EFE28DCE0@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/raK6wQxrdU17ADlkv7WX_FzXPvY>
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, 05 May 2017 09:52:19 -0000

On 04/05/2017 21:20, Alvaro Retana (aretana) wrote:
> On 5/2/17, 12:57 PM, "Stewart Bryant" <stewart.bryant@gmail.com> wrote:
>
> Stewart:
>
> Hi!  How are you?
>
> Thanks for the detailed review!
>
>> A significant part of the justification seems to evolve around the
>> inability of MPLS to function in an IPv6 only network.
> It seems to me that this statement summarizes many of the concerns you listed as Major in the review.  I can see why it seems like the justification is: “because MPLS doesn’t work, then we have to do IPv6.” – but I think that even if a complete solution exists (for an MPLS deployment on an IPv6-only network), some operators would still make the design choice of preferring an IPv6-only deployment.
>
> I think that it would be good for the authors to refocus the justification away from “because X doesn’t work”.  Would that address this part of your concerns?
>
> Thanks!
>
> Alvaro.
>

Hi Alvaro,

That would be a step in the right direction particularly if Carlos' OPS 
comments were also addressed.

Without going back over the detail, I seem to remember I had a question 
as to how the homenet case worked given that SR needs topology info, and 
homenet has chosen a DV protocol.

I also had a concerns about the validity of the scaling justification, 
and I think there are issues of trust that need to be discussed.

Both of those may be addressable simply by providing more detail as 
Carlos suggests.

Alternatively maybe it would be better to have a single use case: 
Operators that wish to deploy SR without an MPLS control plane, although 
as I note, you don't need an MPLS control plane to make MPLS SR work.

- Stewart


From nobody Fri May  5 03:10:52 2017
Return-Path: <sprevidi@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 5241F1294D3; Fri,  5 May 2017 03:10:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 RfgpFvhUJ_1y; Fri,  5 May 2017 03:10:41 -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 9F7D4129494; Fri,  5 May 2017 03:10:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=490; q=dns/txt; s=iport; t=1493979041; x=1495188641; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=6fgWWXgrLGODipEaRFnPqE7Lv9VKfrai0wFqmrHJlIY=; b=LYjymKMQlCHAZrR/NdAATWrUonv+qwNmF8EueKr214dFyNyyyK92LX8z xWk70toT5w1gtwHeP0yfTfd+1eAKTrg7E7ZU0JUwLFmBwQZlAppIE14O7 zLUubYRDqvz3V5EhpvJdgoZepu8CSE/bTPhVICD8GXu5Cbh3Z9huARCjv Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BBAQAvTgxZ/5NdJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1WBbgeDYYoYkVeIIo1Ogg+GJAIahCw/GAECAQEBAQEBAWsohRU?= =?us-ascii?q?BAQEBAgEjEUUFCwIBCBgCAiYCAgIfERUQAgQBDQWKCAMNCLERgiaHKg2DLgEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAR2BC4VUgV4rgnCCVIUVLoIxAQSdNDsBjkSEUoF?= =?us-ascii?q?sAY97iyOJEwEfOIEKbxVYAYZfdodogQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.38,292,1491264000"; d="scan'208";a="422199871"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 May 2017 10:10:40 +0000
Received: from XCH-RTP-005.cisco.com (xch-rtp-005.cisco.com [64.101.220.145]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id v45AAe3I024908 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 5 May 2017 10:10:40 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-005.cisco.com (64.101.220.145) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 5 May 2017 06:10:39 -0400
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1210.000; Fri, 5 May 2017 06:10:39 -0400
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>
CC: "gen-art@ietf.org" <gen-art@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "draft-ietf-spring-ipv6-use-cases.all@ietf.org" <draft-ietf-spring-ipv6-use-cases.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [spring] Genart last call review of draft-ietf-spring-ipv6-use-cases-10
Thread-Topic: [spring] Genart last call review of draft-ietf-spring-ipv6-use-cases-10
Thread-Index: AQHSxRPsenC9nUhN5Uqlm4iwP4zQyaHlw3QAgAAFHwA=
Date: Fri, 5 May 2017 10:10:39 +0000
Message-ID: <B91C6D2C-897A-404C-80B3-EAA8BDEC4414@cisco.com>
References: <149374426742.21414.16408814015665498739@ietfa.amsl.com> <3E209B45-90CE-4EEB-9D2B-E14EFE28DCE0@cisco.com> <87a1534f-079d-3707-9f5d-9327e831bf7a@gmail.com>
In-Reply-To: <87a1534f-079d-3707-9f5d-9327e831bf7a@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.61.108.100]
Content-Type: text/plain; charset="utf-8"
Content-ID: <D3A25BE6182C184FB902973E454FD477@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xru3DVVbkZfIWe464Sc1rTkm8Hs>
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, 05 May 2017 10:10:44 -0000

DQo+IE9uIE1heSA1LCAyMDE3LCBhdCAxMTo1MiBBTSwgU3Rld2FydCBCcnlhbnQgPHN0ZXdhcnQu
YnJ5YW50QGdtYWlsLmNvbT4gd3JvdGU6DQo+IA0KPiBBbHRlcm5hdGl2ZWx5IG1heWJlIGl0IHdv
dWxkIGJlIGJldHRlciB0byBoYXZlIGEgc2luZ2xlIHVzZSBjYXNlOiBPcGVyYXRvcnMgdGhhdCB3
aXNoIHRvIGRlcGxveSBTUiB3aXRob3V0IGFuIE1QTFMgY29udHJvbCBwbGFuZSwNCg0KDQpJ4oCZ
ZCBhZ3JlZSB3aXRoIHRoZSBhYm92ZS4gTGV04oCZcyBzaW1wbGlmeSB0aGUgZG9jdW1lbnQgd2l0
aCwgYXQgdGhlIGVuZCwgd2hhdCBpcyB0aGUgc2ltcGxlc3QgYW5kIG1vc3QgZXZpZGVudCB1c2Ug
Y2FzZS4NCg0Kcy4NCg0K


From nobody Fri May  5 03:17:26 2017
Return-Path: <rraszuk@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 0697412957C; Fri,  5 May 2017 03:17:17 -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 fGcHv4iikGDD; Fri,  5 May 2017 03:17:15 -0700 (PDT)
Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FD3A129494; Fri,  5 May 2017 03:17:15 -0700 (PDT)
Received: by mail-io0-x232.google.com with SMTP id k91so2277201ioi.1; Fri, 05 May 2017 03:17: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=yEGkMWhVniH89nHOiu7Tkhj1wwabo+LZ5ZvEd+xmQGc=; b=EJv5h3vekD8I6pNuI6CAaEEiDJTeBrSPWgJWaYjr2uqDsENes8MdrNSCIPjB8CMCZl SQzQqwJEMGI/LG2bZAmAEB4YWWDJ/jWeIGtVFFJLPHq/vG8O1K1Wi37BpehkGol9a/YJ msOGxkaaAjlEpGyqlzwi3qFk7VayhiEd9eg3R7ocejgjl+5m8aaWB0WO4iPTzNVQ880J fyi7/LTYkZfkRrbbcqTS8v0PnTvk8Uoveyiyh8Qt35Cej9qT/01eWn7Kt2Gkg4/OoLZg cdx6GT8dRHJcwufHpmJ9d5XD5Vtn0pqUGdxj8vKc1LkWTzppOqSpftqIehP2x7cn3nlt r1MA==
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=yEGkMWhVniH89nHOiu7Tkhj1wwabo+LZ5ZvEd+xmQGc=; b=HUH+de8Mvx03MEL0LdKEtY0w55YBGGwb2DGvDjt79HggovqZ8FA+fEEVsiOTQe7Xmm 1w1h8iYl1iqIkAwSJtnu+2z/FJq7qnB4qzPfGNppMvuXd1lpbkSYy01dlPiWI04bnUHe alsgzXzC42gqFtu9k2bqFnXK3CpDL8Z1oewzrDuJCmiMlrWHS9ENIo6psYuATHQ8OnWy 7IThRyQJMoqynF0dATpZqOboYJu66ixB7FB+6UzqNV2sDtnQ6nACM0Aksnq6fMuajRsy ARbzy8OZe/HfvCRtXb33D7JX97wEh9Vb/hUt2QX6QkhfOfxZ9XJLBztM7+T7lHnwIaD+ tIDw==
X-Gm-Message-State: AN3rC/5GY2K6U02xTBlCLfl1rh3Ugirj8/STbqTTuc1SFPKkBEMVWXg8 3Ddw4V+psHvDi5V/dJtvcDL5t1AE7A==
X-Received: by 10.107.189.198 with SMTP id n189mr44287128iof.179.1493979434568;  Fri, 05 May 2017 03:17:14 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.79.62.24 with HTTP; Fri, 5 May 2017 03:17:13 -0700 (PDT)
Received: by 10.79.62.24 with HTTP; Fri, 5 May 2017 03:17:13 -0700 (PDT)
In-Reply-To: <B91C6D2C-897A-404C-80B3-EAA8BDEC4414@cisco.com>
References: <149374426742.21414.16408814015665498739@ietfa.amsl.com> <3E209B45-90CE-4EEB-9D2B-E14EFE28DCE0@cisco.com> <87a1534f-079d-3707-9f5d-9327e831bf7a@gmail.com> <B91C6D2C-897A-404C-80B3-EAA8BDEC4414@cisco.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 5 May 2017 06:17:13 -0400
X-Google-Sender-Auth: MRtjQW9V0HAM4B60QUfH-ukWZU0
Message-ID: <CA+b+ERnsEn3JBpb8b7Jwcm32K=-iGA3GOPokWwnaXqSpDW89Vg@mail.gmail.com>
Subject: Re: [spring] Genart last call review of draft-ietf-spring-ipv6-use-cases-10
To: stefano previdi <sprevidi@cisco.com>
Cc: IETF Discussion <ietf@ietf.org>, Stewart Bryant <stewart.bryant@gmail.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>,  "draft-ietf-spring-ipv6-use-cases.all@ietf.org" <draft-ietf-spring-ipv6-use-cases.all@ietf.org>,  "gen-art@ietf.org" <gen-art@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c0c85e47fd130054ec431f1
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/db4i8vaTCUoE0DQas6oEvjYhqgU>
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, 05 May 2017 10:17:17 -0000

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

And to add one observation ..

Stewart makes a point that SR-MPLS can be deployed without mpls control
plane.

Well it sure does not require LDP however IGP or BGP extensions for SR-MPLS
signalling is also an example of mpls control plane ... even if much
simpler than traditional cases it is still required.

Cheers,
R.

On May 5, 2017 12:10 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
wrote:

>
> > On May 5, 2017, at 11:52 AM, Stewart Bryant <stewart.bryant@gmail.com>
> wrote:
> >
> > Alternatively maybe it would be better to have a single use case:
> Operators that wish to deploy SR without an MPLS control plane,
>
>
> I=E2=80=99d agree with the above. Let=E2=80=99s simplify the document wit=
h, at the end,
> what is the simplest and most evident use case.
>
> s.
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>

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

<div dir=3D"auto">And to add one observation ..=C2=A0<div dir=3D"auto"><br>=
</div><div dir=3D"auto">Stewart makes a point that SR-MPLS can be deployed =
without mpls control plane.<div dir=3D"auto"><br></div><div dir=3D"auto">We=
ll it sure does not require LDP however IGP or BGP extensions for SR-MPLS s=
ignalling is also an example of mpls control plane ... even if much simpler=
 than traditional cases it is still required.</div><div dir=3D"auto"><br></=
div><div dir=3D"auto">Cheers,</div><div dir=3D"auto">R.</div></div></div><d=
iv class=3D"gmail_extra"><br><div class=3D"gmail_quote">On May 5, 2017 12:1=
0 PM, &quot;Stefano Previdi (sprevidi)&quot; &lt;<a href=3D"mailto:sprevidi=
@cisco.com">sprevidi@cisco.com</a>&gt; wrote:<br type=3D"attribution"><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"><br>
&gt; On May 5, 2017, at 11:52 AM, Stewart Bryant &lt;<a href=3D"mailto:stew=
art.bryant@gmail.com">stewart.bryant@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Alternatively maybe it would be better to have a single use case: Oper=
ators that wish to deploy SR without an MPLS control plane,<br>
<br>
<br>
I=E2=80=99d agree with the above. Let=E2=80=99s simplify the document with,=
 at the end, what is the simplest and most evident use case.<br>
<br>
s.<br>
<br>
______________________________<wbr>_________________<br>
spring mailing list<br>
<a href=3D"mailto:spring@ietf.org">spring@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/spring" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/spring</a><br=
>
</blockquote></div></div>

--94eb2c0c85e47fd130054ec431f1--


From nobody Fri May  5 04:57:23 2017
Return-Path: <townsley@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 E5CA7127275; Fri,  5 May 2017 04:57:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.123
X-Spam-Level: 
X-Spam-Status: No, score=-13.123 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 zUXbdf7RTbLa; Fri,  5 May 2017 04:57:04 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9990127867; Fri,  5 May 2017 04:57:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2740; q=dns/txt; s=iport; t=1493985424; x=1495195024; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Z6TFohnic1feC+UV8UtcDpcYJ0ObdcZjdnJOPslOllI=; b=TdpWMFajG67Km4qo9J0+B2QU1TBa1fByWGIV7iEfkc7P8v0BmtowCGmh da/KvszPlYy96AU3HqiTzFABqgqibWQtsnAM0osH8rr190AyKoBTRdioc WNfp1joyNlYahCJfUIDIvQKMXQXBNnGpi6cmMJc8N1nQj1x08zV7scCAv o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BBAQA5ZwxZ/4sNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1WBbgeDYYoYkVeIIo1Ogg+GJAIahC0/GAECAQEBAQEBAWsohRU?= =?us-ascii?q?BAQEBAgEjEUUFCwIBBgIYAgImAgICHxEVEAIEDgUbiW0DDQiTY51hgiaHKg2DL?= =?us-ascii?q?gEBAQEBAQEBAQEBAQEBAQEBAQEBAR2BC4cyK4JwglSCDxeCby6CMQEEnTQ7AY5?= =?us-ascii?q?EhFKRaIsjiRMBHziBCm8VWAGGX3aHaIENAQEB?=
X-IronPort-AV: E=Sophos;i="5.38,292,1491264000"; d="scan'208";a="420429941"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 05 May 2017 11:57:02 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id v45Bv2x9001207 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 5 May 2017 11:57:02 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 5 May 2017 06:57:01 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1210.000; Fri, 5 May 2017 06:57:01 -0500
From: "Mark Townsley (townsley)" <townsley@cisco.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
CC: "Alvaro Retana (aretana)" <aretana@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "draft-ietf-spring-ipv6-use-cases.all@ietf.org" <draft-ietf-spring-ipv6-use-cases.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Genart last call review of draft-ietf-spring-ipv6-use-cases-10
Thread-Topic: Genart last call review of draft-ietf-spring-ipv6-use-cases-10
Thread-Index: AQHSw2U/BOotKSR5yE+0kCHjckN3AaHk9L6AgADi1wCAACLZAA==
Date: Fri, 5 May 2017 11:57:01 +0000
Message-ID: <FD28EC8A-CA02-4D6D-B6A3-D3B19C68DE4D@cisco.com>
References: <149374426742.21414.16408814015665498739@ietfa.amsl.com> <3E209B45-90CE-4EEB-9D2B-E14EFE28DCE0@cisco.com> <87a1534f-079d-3707-9f5d-9327e831bf7a@gmail.com>
In-Reply-To: <87a1534f-079d-3707-9f5d-9327e831bf7a@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.228.43.90]
Content-Type: text/plain; charset="utf-8"
Content-ID: <0762E6F421E4884295107E55B614AE63@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wsNTwqBuSPXHOSJro_5cTgMpAU4>
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, 05 May 2017 11:57:06 -0000

DQo+IE9uIE1heSA1LCAyMDE3LCBhdCAxMTo1MiBBTSwgU3Rld2FydCBCcnlhbnQgPHN0ZXdhcnQu
YnJ5YW50QGdtYWlsLmNvbT4gd3JvdGU6DQo+IA0KPiANCj4gT24gMDQvMDUvMjAxNyAyMToyMCwg
QWx2YXJvIFJldGFuYSAoYXJldGFuYSkgd3JvdGU6DQo+PiBPbiA1LzIvMTcsIDEyOjU3IFBNLCAi
U3Rld2FydCBCcnlhbnQiIDxzdGV3YXJ0LmJyeWFudEBnbWFpbC5jb20+IHdyb3RlOg0KPj4gDQo+
PiBTdGV3YXJ0Og0KPj4gDQo+PiBIaSEgIEhvdyBhcmUgeW91Pw0KPj4gDQo+PiBUaGFua3MgZm9y
IHRoZSBkZXRhaWxlZCByZXZpZXchDQo+PiANCj4+PiBBIHNpZ25pZmljYW50IHBhcnQgb2YgdGhl
IGp1c3RpZmljYXRpb24gc2VlbXMgdG8gZXZvbHZlIGFyb3VuZCB0aGUNCj4+PiBpbmFiaWxpdHkg
b2YgTVBMUyB0byBmdW5jdGlvbiBpbiBhbiBJUHY2IG9ubHkgbmV0d29yay4NCj4+IEl0IHNlZW1z
IHRvIG1lIHRoYXQgdGhpcyBzdGF0ZW1lbnQgc3VtbWFyaXplcyBtYW55IG9mIHRoZSBjb25jZXJu
cyB5b3UgbGlzdGVkIGFzIE1ham9yIGluIHRoZSByZXZpZXcuICBJIGNhbiBzZWUgd2h5IGl0IHNl
ZW1zIGxpa2UgdGhlIGp1c3RpZmljYXRpb24gaXM6IOKAnGJlY2F1c2UgTVBMUyBkb2VzbuKAmXQg
d29yaywgdGhlbiB3ZSBoYXZlIHRvIGRvIElQdjYu4oCdIOKAkyBidXQgSSB0aGluayB0aGF0IGV2
ZW4gaWYgYSBjb21wbGV0ZSBzb2x1dGlvbiBleGlzdHMgKGZvciBhbiBNUExTIGRlcGxveW1lbnQg
b24gYW4gSVB2Ni1vbmx5IG5ldHdvcmspLCBzb21lIG9wZXJhdG9ycyB3b3VsZCBzdGlsbCBtYWtl
IHRoZSBkZXNpZ24gY2hvaWNlIG9mIHByZWZlcnJpbmcgYW4gSVB2Ni1vbmx5IGRlcGxveW1lbnQu
DQo+PiANCj4+IEkgdGhpbmsgdGhhdCBpdCB3b3VsZCBiZSBnb29kIGZvciB0aGUgYXV0aG9ycyB0
byByZWZvY3VzIHRoZSBqdXN0aWZpY2F0aW9uIGF3YXkgZnJvbSDigJxiZWNhdXNlIFggZG9lc27i
gJl0IHdvcmvigJ0uICBXb3VsZCB0aGF0IGFkZHJlc3MgdGhpcyBwYXJ0IG9mIHlvdXIgY29uY2Vy
bnM/DQo+PiANCj4+IFRoYW5rcyENCj4+IA0KPj4gQWx2YXJvLg0KPj4gDQo+IA0KPiBIaSBBbHZh
cm8sDQo+IA0KPiBUaGF0IHdvdWxkIGJlIGEgc3RlcCBpbiB0aGUgcmlnaHQgZGlyZWN0aW9uIHBh
cnRpY3VsYXJseSBpZiBDYXJsb3MnIE9QUyBjb21tZW50cyB3ZXJlIGFsc28gYWRkcmVzc2VkLg0K
PiANCj4gV2l0aG91dCBnb2luZyBiYWNrIG92ZXIgdGhlIGRldGFpbCwgSSBzZWVtIHRvIHJlbWVt
YmVyIEkgaGFkIGEgcXVlc3Rpb24gYXMgdG8gaG93IHRoZSBob21lbmV0IGNhc2Ugd29ya2VkIGdp
dmVuIHRoYXQgU1IgbmVlZHMgdG9wb2xvZ3kgaW5mbywgYW5kIGhvbWVuZXQgaGFzIGNob3NlbiBh
IERWIHByb3RvY29sLg0KDQpITkNQIHBlcmZvcm1zIHRvcG9sb2d5IGRpc2NvdmVyeSBhbmQgcHJl
Zml4IGFzc2lnbm1lbnQgd2l0aGluIHRoZSBob21lIG5ldHdvcmssIGluZGVwZW5kZW50IG9mIHRo
ZSByb3V0aW5nIHByb3RvY29sIGJlaW5nIHVzZWQuDQoNCi0gTWFyaw0KDQo+IA0KPiBJIGFsc28g
aGFkIGEgY29uY2VybnMgYWJvdXQgdGhlIHZhbGlkaXR5IG9mIHRoZSBzY2FsaW5nIGp1c3RpZmlj
YXRpb24sIGFuZCBJIHRoaW5rIHRoZXJlIGFyZSBpc3N1ZXMgb2YgdHJ1c3QgdGhhdCBuZWVkIHRv
IGJlIGRpc2N1c3NlZC4NCj4gDQo+IEJvdGggb2YgdGhvc2UgbWF5IGJlIGFkZHJlc3NhYmxlIHNp
bXBseSBieSBwcm92aWRpbmcgbW9yZSBkZXRhaWwgYXMgQ2FybG9zIHN1Z2dlc3RzLg0KPiANCj4g
QWx0ZXJuYXRpdmVseSBtYXliZSBpdCB3b3VsZCBiZSBiZXR0ZXIgdG8gaGF2ZSBhIHNpbmdsZSB1
c2UgY2FzZTogT3BlcmF0b3JzIHRoYXQgd2lzaCB0byBkZXBsb3kgU1Igd2l0aG91dCBhbiBNUExT
IGNvbnRyb2wgcGxhbmUsIGFsdGhvdWdoIGFzIEkgbm90ZSwgeW91IGRvbid0IG5lZWQgYW4gTVBM
UyBjb250cm9sIHBsYW5lIHRvIG1ha2UgTVBMUyBTUiB3b3JrLg0KPiANCj4gLSBTdGV3YXJ0DQo+
IA0KDQo=


From nobody Fri May  5 05:32:30 2017
Return-Path: <bob.hinden@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 8AC93129454; Fri,  5 May 2017 05:32:20 -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 SH6gYUAgyIhK; Fri,  5 May 2017 05:32:19 -0700 (PDT)
Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 006B812922E; Fri,  5 May 2017 05:32:18 -0700 (PDT)
Received: by mail-wm0-x244.google.com with SMTP id z129so1075120wmb.1; Fri, 05 May 2017 05:32:18 -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=DUcxZ758Lle09aFYrVG/RGBN4K9Di+SbyXtKju4ibik=; b=SIX1y/ELMSz8pKYRoyxLSE7ETZmEKQQfVlL0MIo3Oa8j0Zb5sg7VUibYQpKFb/6PPK 2W5WHOv3hyNRK13AvOayjMYccysGyRk96h4wv9vbgGGGmCgT3uFwgOGhaknLHIyI5hUE cDtCft8HkagkG8puqFv2PoRc/Wvcd0b+3goTLHjvY3IG9ZGjEMVuQrui+3ACJhkHJcca r0t1iJYSEi+zO793YDo2R9SGrdLZp7LpjzlHdBeyQ5Mko7dZGXn9JMAh5z3p21oxi8DZ gFkK0SYrhbSWmb3tN3fSaWEOI+Ga1JbO0FTPp7PF9utDVG/xA5iE6GK7ge4jRB4RkN6T 1IYA==
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=DUcxZ758Lle09aFYrVG/RGBN4K9Di+SbyXtKju4ibik=; b=al/w6winfUI8SRfVrtcLcOfcgLCSLnA4Ou8LXUoThTKuYzhPQfAuO9dqOqbMAnN+Nm lGqcDgaKhCbzVDV+FrglHyk2TL+vy0SXaa/M1JYtt8Yu+DG7I1aS/F6SheJ6EVql0H5a 5/ZicWjgF5TJdVIJNs9vO8cgTiBxI/SRm/vPFTN5HF1WisybSs8D9mxSG0VJYKgN2GuT T6LY1URrFGLBG/8ErOKeCifDmsbYmBW2Hx+bTy8W1l1vA+6IfIh5a+rUUSgrrDte/svg 0rYYSbgS3wUV2uRfBEqT/GrlSPNuf9KP2w14M2k3W4nlDiyjK/WsGJIRMaU3eh3sbZ0h JIxQ==
X-Gm-Message-State: AODbwcC6Z07/pAHAMG9qlOdAlU3uoM4viJGW93cSHkUYXYgVyP9bVPK5 9WXpg5BO+Mf4ShWxR5c=
X-Received: by 10.28.212.148 with SMTP id l142mr4872267wmg.37.1493987537525; Fri, 05 May 2017 05:32:17 -0700 (PDT)
Received: from [192.168.1.33] (IGLD-84-229-142-252.inter.net.il. [84.229.142.252]) by smtp.gmail.com with ESMTPSA id g21sm6065377wrg.22.2017.05.05.05.32.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 May 2017 05:32:16 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <F757715A-9D42-40BB-8D86-F1733E3ABAFF@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_51C3213C-2FC5-4844-8F7A-2082C4423B43"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Genart telechat review of draft-ietf-6man-rfc1981bis-06
Date: Fri, 5 May 2017 15:32:12 +0300
In-Reply-To: <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu>
Cc: Bob Hinden <bob.hinden@gmail.com>, Stewart Bryant <stewart.bryant@gmail.com>, gen-art@ietf.org, IPv6 List <ipv6@ietf.org>, IETF <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
To: Joe Touch <touch@isi.edu>
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iQDSAk5F2uDA3NPr1acWeNFZ2RA>
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, 05 May 2017 12:32:21 -0000

--Apple-Mail=_51C3213C-2FC5-4844-8F7A-2082C4423B43
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii


> On Apr 25, 2017, at 9:26 PM, Joe Touch <touch@isi.edu> wrote:
> 
> Hi, Stewart,
> 
> 
> On 4/24/2017 10:12 AM, Stewart Bryant wrote:
>> Minor issues:
>> 
>> A node MUST NOT reduce its estimate of the Path MTU below the IPv6
>> minimum link MTU.
>> 
>> SB> I missed this last time.
>> SB>
>> SB> Presumably you mean "A node MUST NOT reduce its estimate of the
>> SB> Path MTU below the IPv6 minimum link MTU in response to such
>> SB> a message."
> This seems fine to me, FWIW - i.e., limiting the advice in this doc to
> the mechanism in  this doc.

I will add something, but this sentence follows:

   If a node receives a Packet Too Big message reporting a next-hop
   MTU that is less than the IPv6 minimum link MTU, it MUST discard it.

so I think the context was clear.

Bob


> 
>> SB>
>> SB> Otherwise I would have thought that this was entirely a matter
>> SB> for the host whether it wanted to use a Path MTU below the IPv6
>> SB> link minimum. Nothing breaks if the host takes a more conservative
>> SB> decision.
> I don't agree; the host at that point is violating RFC2460. It should
> never think that an IPv6 link or path with an MTU below what RFC2460
> requires is valid.
> 
> Joe
> 


--Apple-Mail=_51C3213C-2FC5-4844-8F7A-2082C4423B43
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQEcBAEBCgAGBQJZDHDNAAoJEK7rdBF357uoSFQIALuKblyJvhz/ED6AfV0n4bKC
2ZPGlJFe43EqasJ9JEqIJ05AvO41lUm2o4o71RpHA3yagmA2/mNp15wCFSYcmgnM
nHqfidzs/4Vjri+JhQchC7cjYcyvnDsEr0xMhH8ndHIuvK/0jlAnf0L8ZxdI1RV1
kICkeLmHYf7eK6Nz61dSMmAog8ExNVhJIKr8gE6N5iqbeErKl+cbRqXMYAZR8yd7
5V2uafBP4KcoliljcapnB33ty6EKwl7vOU2I+2k2J6SbKhJjnFgwC2BCRUw/kfw1
RVVvjNUbsCdgPeJKBvU3/H/qJiWMW9g2mC3JKgNIRvUbUBp6gNKrsIGTZHwDnXo=
=636B
-----END PGP SIGNATURE-----

--Apple-Mail=_51C3213C-2FC5-4844-8F7A-2082C4423B43--


From nobody Fri May  5 05:43:11 2017
Return-Path: <j.schoenwaelder@jacobs-university.de>
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 F3EE1129412; Fri,  5 May 2017 05:43:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?b?SsO8cmdlbiBTY2jDtm53w6RsZGVy?= <j.schoenwaelder@jacobs-university.de>
To: <ops-dir@ietf.org>
Cc: draft-ietf-calext-caldav-attachments.all@ietf.org, ietf@ietf.org, calsify@ietf.org
Subject: Opsdir last call review of draft-ietf-calext-caldav-attachments-02
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149398818895.6889.8986355977868020205@ietfa.amsl.com>
Date: Fri, 05 May 2017 05:43:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/M1bLfp981oSNVo6QPRln12CcCvM>
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, 05 May 2017 12:43:09 -0000

Reviewer: Jürgen Schönwälder
Review result: Ready

This document adds attachments to calendars accessed via CalDAV. The
specification is clearly written and I did not find any operational
issues that are not already addressed by the specification.




From nobody Fri May  5 08:02:40 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 7E878128D2E; Fri,  5 May 2017 08:02:25 -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=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 G-L3G7xQFULo; Fri,  5 May 2017 08:02:25 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (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 A11BE12943B; Fri,  5 May 2017 07:55:05 -0700 (PDT)
X-AuditID: c6180641-45bff70000000cb9-43-590c4be9cc1d
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usplmg21.ericsson.net (Symantec Mail Security) with SMTP id 4A.47.03257.9EB4C095; Fri,  5 May 2017 11:54:52 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0339.000; Fri, 5 May 2017 10:55:01 -0400
From: Daniel Migault <daniel.migault@ericsson.com>
To: =?utf-8?B?SsO8cmdlbiBTY2jDtm53w6RsZGVy?= <j.schoenwaelder@jacobs-university.de>, "ops-dir@ietf.org" <ops-dir@ietf.org>
CC: "draft-ietf-calext-caldav-attachments.all@ietf.org" <draft-ietf-calext-caldav-attachments.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "calsify@ietf.org" <calsify@ietf.org>
Subject: RE: Opsdir last call review of draft-ietf-calext-caldav-attachments-02
Thread-Topic: Opsdir last call review of draft-ietf-calext-caldav-attachments-02
Thread-Index: AQHSxZ0p/MBfqHrEE0KJb2QH45crLKHl0+yA
Date: Fri, 5 May 2017 14:55:00 +0000
Message-ID: <2DD56D786E600F45AC6BDE7DA4E8A8C118BD8751@eusaamb107.ericsson.se>
References: <149398818895.6889.8986355977868020205@ietfa.amsl.com>
In-Reply-To: <149398818895.6889.8986355977868020205@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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDLMWRmVeSWpSXmKPExsUyuXRPuO4bb55Ig7m3FS02vWhmtdjx+SGr xbON81ksrm78yWjR27SE2YHVY8mSn0weGw54BjBFcdmkpOZklqUW6dslcGXsfvKeveADW8Wq 51vZGhhvsHUxcnJICJhIfPj/B8jm4hASOMoo8Xf5Z3YIZxmjxI3fO1lAqtgEjCTaDvWzg9gi AjUSk689YwUpYhbYzijRefcmUDsHh7BAoMSh2YoQNUESPQtWsEHYRhI7jl4E62URUJG4ePoe K4jNK+ArcfteNzOILSTgJHFzwlMmEJtTwFlizuXJYPWMAmIS30+tAYszC4hL3HoynwniagGJ JXvOM0PYohIvH/9jhbCVJD7+ns8Ocg6zgKbE+l36EK2KElO6H7JDrBWUODnzCcsERtFZSKbO QuiYhaRjFpKOBYwsqxg5SosLcnLTjQw3MQLj5JgEm+MOxr29nocYBTgYlXh4HxhzRwqxJpYV V+YeYpTgYFYS4f3UxxMpxJuSWFmVWpQfX1Sak1p8iFGag0VJnPdd+YUIIYH0xJLU7NTUgtQi mCwTB6dUA6O6wP76bf8uTFZsn+7dmJX1r/9ni8f7695pk+SZH2hJ75azq/o4k/vEhbkbWB+x eJo139F0bZepuDU1V1lkk9XGxLWB3eI3KiU06v0+1+9le6+Qu6ddq/t0suj8xPYnSnvP7Of+ ZaJ1/YfohdwX1W1RIv97BRP9g4rcoq7OXv976cfHL3+mVimxFGckGmoxFxUnAgDyNJkfjwIA AA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Bv-WJFgQX5QMDdUEQ2u7lqTWZJw>
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, 05 May 2017 15:02:26 -0000

VGhhbmtzIEp1cmdlbiBmb3IgdGhlIHJldmlldy4NCllvdXJzLCANCkRhbmllbA0KDQotLS0tLU9y
aWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogSsO8cmdlbiBTY2jDtm53w6RsZGVyIFttYWlsdG86
ai5zY2hvZW53YWVsZGVyQGphY29icy11bml2ZXJzaXR5LmRlXSANClNlbnQ6IEZyaWRheSwgTWF5
IDA1LCAyMDE3IDg6NDMgQU0NClRvOiBvcHMtZGlyQGlldGYub3JnDQpDYzogZHJhZnQtaWV0Zi1j
YWxleHQtY2FsZGF2LWF0dGFjaG1lbnRzLmFsbEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzsgY2Fs
c2lmeUBpZXRmLm9yZw0KU3ViamVjdDogT3BzZGlyIGxhc3QgY2FsbCByZXZpZXcgb2YgZHJhZnQt
aWV0Zi1jYWxleHQtY2FsZGF2LWF0dGFjaG1lbnRzLTAyDQoNClJldmlld2VyOiBKw7xyZ2VuIFNj
aMO2bnfDpGxkZXINClJldmlldyByZXN1bHQ6IFJlYWR5DQoNClRoaXMgZG9jdW1lbnQgYWRkcyBh
dHRhY2htZW50cyB0byBjYWxlbmRhcnMgYWNjZXNzZWQgdmlhIENhbERBVi4gVGhlIHNwZWNpZmlj
YXRpb24gaXMgY2xlYXJseSB3cml0dGVuIGFuZCBJIGRpZCBub3QgZmluZCBhbnkgb3BlcmF0aW9u
YWwgaXNzdWVzIHRoYXQgYXJlIG5vdCBhbHJlYWR5IGFkZHJlc3NlZCBieSB0aGUgc3BlY2lmaWNh
dGlvbi4NCg0KDQoNCg==


From nobody Fri May  5 09:41:05 2017
Return-Path: <jclarke@cisco.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 83135129AEB; Fri,  5 May 2017 09:41:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joe Clarke <jclarke@cisco.com>
To: <ops-dir@ietf.org>
Cc: idr@ietf.org, draft-ietf-idr-sla-exchange.all@ietf.org, ietf@ietf.org
Subject: Opsdir early review of draft-ietf-idr-sla-exchange-10
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149400246349.8370.5477015906856459639@ietfa.amsl.com>
Date: Fri, 05 May 2017 09:41:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8rzXIIohM7XrHB-2l6fmxHqaWao>
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, 05 May 2017 16:41:03 -0000

Reviewer: Joe Clarke
Review result: Has Issues

I have been asked to do a review of this draft as a representative of
OPS-DIR.  This draft lays out a means to exchange SLA/QoS policies via
BGP UPDATE messages.

Overall, I found this draft a bit difficult to read.  There are
grammatical issues such as the user of "thru" instead of "through",
odd commas, and missing articles.  But this is not a grammatical
overview.

I think this draft would benefit from some examples that show what
some practical QoS policies would look like that convey the required
classes within the maximum BGP message size (that is, in section 7 add
more specific examples of what policies may look like in the ADVERTISE
messages).  What do the authors feel typical uses of this would look
like from the UPDATE message perspective?  What kind of processing
overhead can one typically expect if a router, for example, will be
the QoS Attribute Speaker and SLA Consumer?

Below are some specific per-section questions and issues:

Section 2:

You state that a BGP Speaker need not be a QoS Attribute Speaker, but
even if the QoS data is opaque to the BGP Speaker, it would still need
to know that the QoS Attribute Speaker exists and there is data to be
added to the UPDATE.  So why the two entities don't need to be
co-resident in the same process, a BGP Speaker needs to be QoS aware
to some extent in order for this exchange to work.

Additionally, why are SLA Producer and Consumer broken out whereas QoS
and BGP just have "speakers?"  For consistency, maybe you just state
that there exists an SLA-aware QoS Attribute Speaker.

You do not define NLRI and AFI/SAFI in your terminology.

===

Section 3.2:

Why the need to have the SLA SubType Flags be set to 0?  Couldn't you
just as easily set the Source AS and Destination AS Counts to 0?  You
state that a value of 0 for Source AS when flags are 1 is illegal, so
I believe this would work.

For SLA ID, you state:

The SLA ID applies to aggregate traffic to prefixes for a given
AFI/SAFI that share the same Source AS and SLA ID.

The SLA ID applies to aggregate traffic that shares the same SLA ID? 
This seems circular to me.  I'm not really clear on how I would
allocate an SLA ID and how I align that with the intended QoS
policies.

Would the intent of having a 0-length SLA Content be to remove the
policy for the given prefixes?  I'm not clear exactly as to that use
case.

I'm confused a bit as to how the Destination AS List works. 
Initially, I thought this would only be set by the sending AS to
indicate to which external ASes the content applies.  However, each
QoS Attribute Speaker can update the Destination AS List.  In Sections
4.1.2, 5.1 and 5.2 you attempt to address this, but it is still not
clear what kind of updating or trimming of the Destination AS list
should be done (and in Section 5.2 you allude to rules to trim the
Destination AS List, but I did not see those rules).  This could be
clarified with an example of what can happen at various hops in the
network.

===

Section 3.3:

Related to a point above, if the SLA Content needs to be set per
direction, would I use the same SLA ID to do that?  I don't think
that's clear enough in the current text.

You state:

Any Traffic Class Element advertised in the QoS Attribute only
applies to the advertised AFI/SAFI NLRI within the BGP UPDATE
message the QoS Attribute is contained in.

However, if I understand correctly, I could specify IPFIX attributes
of sourceIPv6Prefix and/or destinationIPv6Prefix that does not line up
with the NLRIs, would that not constitute an error?  Or Maybe my
AFI/SAFI are 1/1, and I'm trying to match IPv6.  This seems more like
an error, but you only state what to do if the AFI/SAFI is not
supported.

===

Section 3.3.2.2:

Why have such a huge range for length here?  I can specify that the
number of bytes to specify the amount of L2 overhead to use is 255. 
Why not advise that length should be 4, and then use an IEEE FP number
like you did for the TSPEC?  At the very least, I think this should be
reined in a bit.

===

Section 3.3.2.7:

I think you have a typo in precedence.  I think you want to say:

- MINRATE_IN_PROFILE_MARKING takes highest precedence (that is
    over MAXRATE_IN_PROFILE_MARKING),

- MAXRATE_IN_PROFILE_MARKING takes precedence over
   MINRATE_OUT_PROFILE_MARKING, and

- MINRATE_OUT_PROFILE_MARKING takes precedence over
   MAXRATE_OUT_PROFILE_MARKING 

===

Section 5.2

What I did not see is what the actual SLA Consumer should do after it
processes the SLA Content.  I realize this can delve into
implementation details, but perhaps it's worth mentioning that the SLA
Consumer can use protocols like NETCONF or RESTCONF to configure the
policies on the necessary interfaces.



From nobody Fri May  5 10:05:27 2017
Return-Path: <touch@isi.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 DF2C0127863; Fri,  5 May 2017 10:05:19 -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_50=0.8, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 cI4r5TOTOwqP; Fri,  5 May 2017 10:05:18 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 C96AD124D37; Fri,  5 May 2017 10:05:18 -0700 (PDT)
Received: from [128.9.184.57] ([128.9.184.57]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v45H4iNZ008671 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 5 May 2017 10:04:45 -0700 (PDT)
Subject: Re: Genart telechat review of draft-ietf-6man-rfc1981bis-06
To: Bob Hinden <bob.hinden@gmail.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, gen-art@ietf.org, IPv6 List <ipv6@ietf.org>, IETF <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu> <F757715A-9D42-40BB-8D86-F1733E3ABAFF@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <fa6510c0-8d43-295d-a5f7-fbea7b86e64f@isi.edu>
Date: Fri, 5 May 2017 10:04:45 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0
MIME-Version: 1.0
In-Reply-To: <F757715A-9D42-40BB-8D86-F1733E3ABAFF@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NfBy9VtoA5ZpRySKOcqwAFT8YAU>
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, 05 May 2017 17:05:20 -0000

Hi, Bob,

AOK. Thanks,

Joe

On 5/5/2017 5:32 AM, Bob Hinden wrote:
>> On Apr 25, 2017, at 9:26 PM, Joe Touch <touch@isi.edu> wrote:
>>
>> Hi, Stewart,
>>
>>
>> On 4/24/2017 10:12 AM, Stewart Bryant wrote:
>>> Minor issues:
>>>
>>> A node MUST NOT reduce its estimate of the Path MTU below the IPv6
>>> minimum link MTU.
>>>
>>> SB> I missed this last time.
>>> SB>
>>> SB> Presumably you mean "A node MUST NOT reduce its estimate of the
>>> SB> Path MTU below the IPv6 minimum link MTU in response to such
>>> SB> a message."
>> This seems fine to me, FWIW - i.e., limiting the advice in this doc to
>> the mechanism in  this doc.
> I will add something, but this sentence follows:
>
>    If a node receives a Packet Too Big message reporting a next-hop
>    MTU that is less than the IPv6 minimum link MTU, it MUST discard it.
>
> so I think the context was clear.
>
> Bob
>
>
>>> SB>
>>> SB> Otherwise I would have thought that this was entirely a matter
>>> SB> for the host whether it wanted to use a Path MTU below the IPv6
>>> SB> link minimum. Nothing breaks if the host takes a more conservative
>>> SB> decision.
>> I don't agree; the host at that point is violating RFC2460. It should
>> never think that an IPv6 link or path with an MTU below what RFC2460
>> requires is valid.
>>
>> Joe
>>


From nobody Fri May  5 12:29:07 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 B7F4A124E15; Fri,  5 May 2017 12:29:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.819
X-Spam-Level: 
X-Spam-Status: No, score=0.819 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-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 Tb0u4qhAPozc; Fri,  5 May 2017 12:29: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 4D53E12714F; Fri,  5 May 2017 12:29:05 -0700 (PDT)
Received: from Orochi.local ([172.56.4.191]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v45JSr0H042791 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 5 May 2017 14:28:54 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [172.56.4.191] claimed to be Orochi.local
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
To: Eliot Lear <lear@cisco.com>, Mark Nottingham <mnot@mnot.net>, Pete Resnick <presnick@qti.qualcomm.com>
Cc: Christian Huitema <huitema@huitema.net>, IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net> <21A01174-4FB6-4F8C-AA3D-DCF6D1FEBA01@trammell.ch> <8cb6fefd-200e-1d90-6a36-c32530ecbaf8@cisco.com> <8114ef76-591f-630e-5464-2b63d0efea61@huitema.net> <BF887C92-1ADD-47F7-A958-04538372AA15@qti.qualcomm.com> <BD3807D4-6253-4A3E-BA34-00CA1DAB5037@mnot.net> <77af81f1-5ab0-c94c-4f3d-9d31edf55b2b@cisco.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <777c900d-8be2-a41c-c7ea-5705a9b1405e@nostrum.com>
Date: Fri, 5 May 2017 15:28:47 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <77af81f1-5ab0-c94c-4f3d-9d31edf55b2b@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IJANCWvYOwbJFVpvJXb8CtuXfRw>
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, 05 May 2017 19:29:07 -0000

On 5/4/17 03:06, Eliot Lear wrote:
> Furthermore, if we don't publish in order to avoid being misconstrued...

I have not yet heard anyone publicly say this document should not be 
published, and I find it a bit disingenuous to construe requests for 
improvement in such a way. <https://yourlogicalfallacyis.com/strawman>

/a


From nobody Fri May  5 12:45:29 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 367F61293FF; Fri,  5 May 2017 12:45:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.103
X-Spam-Level: 
X-Spam-Status: No, score=-13.103 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 cvwshx11zwWt; Fri,  5 May 2017 12:45:13 -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 F1B7F128D19; Fri,  5 May 2017 12:45:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2453; q=dns/txt; s=iport; t=1494013513; x=1495223113; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=a7nGq3ehbthP8eMLAHyzA9s1nhCTmfyfnjxjxIoqh8w=; b=KTYMPIGZc5RIKT2kN3IjR7nWeqvdSejc/1cNvRXS9lc+0S3hgz/BgrZy qyRHQNMf7t9TqVfMccbYPy63akqFQrFoRpcjfW9xP6RrOBXTmW6TgQljb 3wxyNcPiMgWs+esWSEn51DAxcM6anMW5UCuCLfqJI57ZPGlzNUBqkfHeJ k=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AoAQCS0wxZ/xbLJq1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBhDeEdIoYc5BjlXCCDwclhXgChQgYAQIBAQEBAQEBayiFFgEFI1Y?= =?us-ascii?q?QCxgqAgJXBgEMCAEBihwOsRSCJopoAQEBAQEBAQEBAQEBAQEBAQEBAQEPCgWIa?= =?us-ascii?q?IJwh2mCXwEEnW+EDYITe4t8gWwBiROGaJQ3HziBCi4gCBkVhzo+iSsBAQE?=
X-IronPort-AV: E=Sophos;i="5.38,294,1491264000";  d="asc'?scan'208";a="694216819"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 May 2017 19:45:10 +0000
Received: from [10.61.245.236] ([10.61.245.236]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v45JjASa018613; Fri, 5 May 2017 19:45:10 GMT
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
To: Adam Roach <adam@nostrum.com>, Mark Nottingham <mnot@mnot.net>, Pete Resnick <presnick@qti.qualcomm.com>
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net> <21A01174-4FB6-4F8C-AA3D-DCF6D1FEBA01@trammell.ch> <8cb6fefd-200e-1d90-6a36-c32530ecbaf8@cisco.com> <8114ef76-591f-630e-5464-2b63d0efea61@huitema.net> <BF887C92-1ADD-47F7-A958-04538372AA15@qti.qualcomm.com> <BD3807D4-6253-4A3E-BA34-00CA1DAB5037@mnot.net> <77af81f1-5ab0-c94c-4f3d-9d31edf55b2b@cisco.com> <777c900d-8be2-a41c-c7ea-5705a9b1405e@nostrum.com>
Cc: Christian Huitema <huitema@huitema.net>, IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
From: Eliot Lear <lear@cisco.com>
Message-ID: <e220add1-b124-1eed-a01e-fa5aab557aa3@cisco.com>
Date: Fri, 5 May 2017 21:45:09 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <777c900d-8be2-a41c-c7ea-5705a9b1405e@nostrum.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ujss82KD7D6Uw5n05jiPD1tB7Q1uOokqe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YmwaREwFiB07szqSZkvihE00uAU>
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, 05 May 2017 19:45:15 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--ujss82KD7D6Uw5n05jiPD1tB7Q1uOokqe
Content-Type: multipart/mixed; boundary="QFBjb6WpVqTO3E5Jg8RWeLWxXivpnCBie";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Adam Roach <adam@nostrum.com>, Mark Nottingham <mnot@mnot.net>,
 Pete Resnick <presnick@qti.qualcomm.com>
Cc: Christian Huitema <huitema@huitema.net>, IESG <iesg@ietf.org>,
 IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <e220add1-b124-1eed-a01e-fa5aab557aa3@cisco.com>
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net>
 <21A01174-4FB6-4F8C-AA3D-DCF6D1FEBA01@trammell.ch>
 <8cb6fefd-200e-1d90-6a36-c32530ecbaf8@cisco.com>
 <8114ef76-591f-630e-5464-2b63d0efea61@huitema.net>
 <BF887C92-1ADD-47F7-A958-04538372AA15@qti.qualcomm.com>
 <BD3807D4-6253-4A3E-BA34-00CA1DAB5037@mnot.net>
 <77af81f1-5ab0-c94c-4f3d-9d31edf55b2b@cisco.com>
 <777c900d-8be2-a41c-c7ea-5705a9b1405e@nostrum.com>
In-Reply-To: <777c900d-8be2-a41c-c7ea-5705a9b1405e@nostrum.com>

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

Ho


On 5/5/17 9:28 PM, Adam Roach wrote:
> I have not yet heard anyone publicly say this document should not be
> published, and I find it a bit disingenuous to construe requests for
> improvement in such a way. <https://yourlogicalfallacyis.com/strawman>

What is disingenuous is reviewing a document to death, requiring
consensus on people's expressed concerns, and then claiming, =E2=80=9Coh =
no,
we're not stopping publication=E2=80=9D.

Eliot


--QFBjb6WpVqTO3E5Jg8RWeLWxXivpnCBie--

--ujss82KD7D6Uw5n05jiPD1tB7Q1uOokqe
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

iQEcBAEBCAAGBQJZDNZFAAoJEIe2a0bZ0nozPpcIAMRclaXpD3xONycag/o2evDu
uFtDhVoKpkfR+MsUihKw5nHF6GrH8Lk8BzbpU42jQDyPa8ON1OT/ihwSEul649Rn
g9YkuX8qQz/2PvoC5QcW4AZtB0vhO2pC9JdxNNp7weZFIXqxLIrlthl2neESYOb3
SbfbSK2T5V/E9Z8vNj2aPCG1e/sabp0S4EdI1iqKXwBelPJhXcCK/i4e+mUOKqq/
fHhNNJWKFfL3VYG2/9Fx3SCkAeOrfkupDrBShpt3E7EY5f+m1lDIYSiplqNC93t3
+lDrAk6YDyMiuncpkJPCx3WxNBK/eD0QYyhbaEIjkUMOQ7S3a6miXbAIrt36ulY=
=zV4+
-----END PGP SIGNATURE-----

--ujss82KD7D6Uw5n05jiPD1tB7Q1uOokqe--


From nobody Fri May  5 16:45:32 2017
Return-Path: <randy@psg.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 6C2A71294DB; Fri,  5 May 2017 16:45:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 YU13aOZZrLOW; Fri,  5 May 2017 16:45:23 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 67B0C126CD6; Fri,  5 May 2017 16:45:23 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1d6muX-0007XW-8E; Fri, 05 May 2017 23:45:21 +0000
Date: Sat, 06 May 2017 08:45:19 +0900
Message-ID: <m2h90y27hs.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Eliot Lear <lear@cisco.com>
Cc: IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Comments on draft-mm-wg-effect-encrypt-11
In-Reply-To: <e220add1-b124-1eed-a01e-fa5aab557aa3@cisco.com>
References: <C49A16E7-1680-4FC9-A423-15A32EFF3D8F@mnot.net> <21A01174-4FB6-4F8C-AA3D-DCF6D1FEBA01@trammell.ch> <8cb6fefd-200e-1d90-6a36-c32530ecbaf8@cisco.com> <8114ef76-591f-630e-5464-2b63d0efea61@huitema.net> <BF887C92-1ADD-47F7-A958-04538372AA15@qti.qualcomm.com> <BD3807D4-6253-4A3E-BA34-00CA1DAB5037@mnot.net> <77af81f1-5ab0-c94c-4f3d-9d31edf55b2b@cisco.com> <777c900d-8be2-a41c-c7ea-5705a9b1405e@nostrum.com> <e220add1-b124-1eed-a01e-fa5aab557aa3@cisco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=ISO-2022-JP
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UUqmNbHBiEnxJKDYNqnibN81wuo>
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, 05 May 2017 23:45:24 -0000

> What is disingenuous is reviewing a document to death, requiring
> consensus on people's expressed concerns

aside from the hyperbole, i think this is what we're supposed to be
doing

> then claiming, $B!H(Boh no, we're not stopping publication$B!I(B.

puhleeze.

there seems to be some useful disagreemet here; and it would help if we
focused on it and tried to work it through until we can get consensus.

< stating what might be obvious >

as i read it, a fair number of folk (i among them) think that a number
of practices described neutrally in the document should be flagged as
negative.

the reason this is an important distinction is that if and when we get
downstream to writing documents more in the solution space, the
behaviors marked as negtive do not need to be spported.  e.g. some see
encryption preventing http header insertion as a feature, not a bug.

and it is ok to have this discussion.

randy


From nobody Sat May  6 21:24:32 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 841D5127A91 for <ietf@ietfa.amsl.com>; Sat,  6 May 2017 21:24:30 -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, HTML_MESSAGE=0.001, 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=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 190_98kOH2dx for <ietf@ietfa.amsl.com>; Sat,  6 May 2017 21:24:29 -0700 (PDT)
Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::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 0524D126557 for <ietf@ietf.org>; Sat,  6 May 2017 21:24:28 -0700 (PDT)
Received: by mail-vk0-x234.google.com with SMTP id x71so15257023vkd.0 for <ietf@ietf.org>; Sat, 06 May 2017 21:24:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8n74Wh9cNR+RnxLuohWUbePE5/m6zlfN7EpeFZfshAQ=; b=1fduc9cg8bZQqIeMDOf2QMGxC+ifFZCY1EghUmsCeMCThKIDG3cDC/xzLSvJ/cIfT3 K2Zd0H3yAxHT8W5hg0hiMA6g8OJ2hXvVXNqmvfg7t13wphn3qxxp8iDfp0xE/2LnKZ53 EuPaiSR8iGxZuhiXPGxpeenyyll8y4fjsEBeZqwNTa4lv8h8bKQrmzZ3y4b6bEidE4s7 MrFxBARCRY2s0N3q9BpHM3JXLmThRhGdY/M+TYM3RaTst3Z7rnwsSOQyPFj3+PHgbQrY jQePrqwGDVUMS2ifTnP3DVo4tMXXvLOh8I9HWgA+zF5/Qbl6F4oqbOaXScXka5hHamXj wtsg==
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=8n74Wh9cNR+RnxLuohWUbePE5/m6zlfN7EpeFZfshAQ=; b=Td3i9NkcLduPS+Tp811yYzlAzoN14mLS6B6XgK7DxRg061YDOz/LHRQn8dtU8GPX35 m2QE+cgzZuakGMpQ3/sq/qrXzr07tMmjJjkBV96Ey+olFTWxbW6Zo9F+RK/8q8IwE5AG 74ixo05Ig1OTp0A41yvLPOXrZ56VrW3ByQ2TPXWLLon5FIIWPmnvobti+vDcxQilZvvs x6KsGaL00KD39rfpzsjabKaa2I22zZwaeIxYNoZom2o39IA+0NiIB8vMmSlZhVu7CtNE yWbL6GfSHhBLqBZxwhct8leKdhAe6dWfxLTNPH3EYL032bCiK0WvLXiFzbl2/jAH8qNK dxYw==
X-Gm-Message-State: AODbwcDDX4fLo/sW+mBzgs1ldE61e1Crcq0e3FjO3V2SRoz20okix4ff 3AKN+RIW7MVsA1GHrQA4I3zctRetXCd2
X-Received: by 10.31.136.10 with SMTP id k10mr4658470vkd.51.1494131066897; Sat, 06 May 2017 21:24:26 -0700 (PDT)
MIME-Version: 1.0
References: <149360667193.9876.7534874775326889081@ietfa.amsl.com>
In-Reply-To: <149360667193.9876.7534874775326889081@ietfa.amsl.com>
From: Warren Kumari <warren@kumari.net>
Date: Sun, 07 May 2017 04:24:15 +0000
Message-ID: <CAHw9_i+4+fUZ4WVJLGv103nzvuFdugpN0gks7CcYgyKGyrSinA@mail.gmail.com>
Subject: Re: Genart telechat review of draft-ietf-dnsop-nsec-aggressiveuse-09
To: Joel Halpern <jmh@joelhalpern.com>, "dnsop-chairs@ietf.org" <dnsop-chairs@ietf.org>, gen-art@ietf.org
Cc: dnsop@ietf.org, draft-ietf-dnsop-nsec-aggressiveuse.all@ietf.org,  ietf@ietf.org
Content-Type: multipart/alternative; boundary=001a114517cc7d9d69054ee77f9d
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sC-GoMIUpI8d1XxUTBI2H5G4YKA>
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, 07 May 2017 04:24:31 -0000

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

Good catch -- these were included in the IETF Last Call notice, and there
was discussion with the chairs and responsible AD. They will be noted in
the downref registry; however, the write-up should have included a mention
of this. I've CCed the chairs / will ask the AD to update the write-up for
completeness...

W



On Mon, May 1, 2017 at 4:44 AM Joel Halpern <jmh@joelhalpern.com> wrote:

> 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-dnsop-nsec-aggressiveuse-09
> Reviewer: Joel Halpern
> Review Date: 2017-04-30
> IETF LC End Date: 2017-03-27
> IESG Telechat date: 2017-05-25
>
> Summary: This document is almost ready for publication as a Proposed
> Standard RFC
>
> Major issues:
>     Procedural - ID Nits notes that there are normative references to
> RFCs 7129 and 7719.  Those are informational RFCs.  The shepherd
> writeup does not note these downrefs.  (I see this was also noted by
> Jouni Korhonen, but I do not see a resolution.)
>
> Minor issues:
>
> Nits/editorial comments:
>
>
>

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

<div><div>Good catch -- these were included in the IETF Last Call notice, a=
nd there was discussion with the chairs and responsible AD. They will be no=
ted in the downref registry; however, the write-up should have included a m=
ention of this. I&#39;ve CCed the chairs / will ask the AD to update the wr=
ite-up for completeness...</div></div><div><br></div><div>W</div><div><br><=
/div><div><div><br></div><div><br></div><div><div class=3D"gmail_quote"><di=
v>On Mon, May 1, 2017 at 4:44 AM Joel Halpern &lt;<a href=3D"mailto:jmh@joe=
lhalpern.com" target=3D"_blank">jmh@joelhalpern.com</a>&gt; wrote:<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">Reviewer: Joel Halpern<br>
Review result: Ready with Issues<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. Please wait for direction from your<br>
document shepherd or AD before posting a new version of the draft.<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/gen/wiki/GenArtfaq</a>&g=
t;.<br>
<br>
Document: draft-ietf-dnsop-nsec-aggressiveuse-09<br>
Reviewer: Joel Halpern<br>
Review Date: 2017-04-30<br>
IETF LC End Date: 2017-03-27<br>
IESG Telechat date: 2017-05-25<br>
<br>
Summary: This document is almost ready for publication as a Proposed<br>
Standard RFC<br>
<br>
Major issues:<br>
=C2=A0 =C2=A0 Procedural - ID Nits notes that there are normative reference=
s to<br>
RFCs 7129 and 7719.=C2=A0 Those are informational RFCs.=C2=A0 The shepherd<=
br>
writeup does not note these downrefs.=C2=A0 (I see this was also noted by<b=
r>
Jouni Korhonen, but I do not see a resolution.)<br>
<br>
Minor issues:<br>
<br>
Nits/editorial comments:<br>
<br>
<br>
</blockquote></div></div></div>

--001a114517cc7d9d69054ee77f9d--


From nobody Sat May  6 22:48:54 2017
Return-Path: <nishida@sfc.wide.ad.jp>
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 06215126D73; Sat,  6 May 2017 22:48:53 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 7XuLe0mPvBF8; Sat,  6 May 2017 22:48:50 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57280126C25; Sat,  6 May 2017 22:48:49 -0700 (PDT)
Received: from mail-oi0-f52.google.com (mail-oi0-f52.google.com [209.85.218.52]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 2F4E829C87A; Sun,  7 May 2017 14:48:46 +0900 (JST)
Received: by mail-oi0-f52.google.com with SMTP id w10so22692923oif.0; Sat, 06 May 2017 22:48:46 -0700 (PDT)
X-Gm-Message-State: AN3rC/6MOFFxyEd6rZxayELgqHrYrxxPGiyoC0OeWB+FFogtOlz49oIl 6k3efAmegnfEloGT1lacFbWx5F6r7w==
X-Received: by 10.157.55.163 with SMTP id x32mr18153638otb.72.1494136124712; Sat, 06 May 2017 22:48:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.4.55 with HTTP; Sat, 6 May 2017 22:48:44 -0700 (PDT)
In-Reply-To: <A257B9FAE62943A6BB540A8F3D457BDA@WeiGengyuPC>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com> <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydcc7k2i5=OSSvvtzU2B1Qa62b3RR3iY0wBfQ2pOYQrkQ@mail.gmail.com> <BY2PR21MB00849DB795086F08F6D7A98A831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249yeS8sZaJcADuz+bYAJa-CXs4v291Fm=adRouO1R=svPDw@mail.gmail.com> <BY2PR21MB008453149ADC1A998FEA56D3831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydRLFpG=yHYvaZvPBiQuW5x=4HZqCZyTAb2HHeDuP+wAA@mail.gmail.com> <AF06737CE0C34EA88BFFFCA04B89CC95@WeiGengyuPC> <76EDF265-DC6F-41DE-B4F4-6BB7F948DC05@tzi.org> <A257B9FAE62943A6BB540A8F3D457BDA@WeiGengyuPC>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Date: Sat, 6 May 2017 22:48:44 -0700
X-Gmail-Original-Message-ID: <CAO249ydx76RYJMspYXqe=uR4BAJNfc0CNnS-SArNe3bS9b55Jw@mail.gmail.com>
Message-ID: <CAO249ydx76RYJMspYXqe=uR4BAJNfc0CNnS-SArNe3bS9b55Jw@mail.gmail.com>
Subject: Re: [core] TSV-ART review of draft-ietf-core-coap-tcp-tls-07
To: weigengyu <weigengyu@bupt.edu.cn>
Cc: Carsten Bormann <cabo@tzi.org>, Yoshifumi Nishida <nishida@sfc.wide.ad.jp>, Brian Raymor <Brian.Raymor@microsoft.com>, tsv-art@ietf.org,  draft-ietf-core-coap-tcp-tls@ietf.org, core@ietf.org, ietf@ietf.org
Content-Type: multipart/alternative; boundary=001a114095e8f5cd0e054ee8ac2b
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WmT7Ij38dIxzC7oOguOTguXCsao>
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, 07 May 2017 05:48:53 -0000

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

On Mon, May 1, 2017 at 11:11 PM, weigengyu <weigengyu@bupt.edu.cn> wrote:

> Hi=EF=BC=8C
>
> The question is not very different from the UDP to UDP proxying case.
>>
> Something is different.
>
> If a request came in via a UDP CON (which is the equivalent of using a
>> reliable transport protocol),
>> should the proxy use CON or NON for the forwarded request?
>>
> If it keeps the semantics end-to-end,  the proxy just forwards the messag=
e.
> If it has the semantics hop-by-hop, the proxy can decide what type of
> message to transfer.


My interpretation for 5.2.3 in RFC7252 is CoAP layer can ignore the
preference of applications and alter the message type by its decisions. It
seems to me proxies can choose message types as they want.
--
Yoshi





> Gengyu WEI
> Network Technology Center
> School of Computer
> Beijing University of Posts and Telecommunications
> -----=E5=8E=9F=E5=A7=8B=E9=82=AE=E4=BB=B6----- From: Carsten Bormann
> Sent: Tuesday, May 02, 2017 2:01 PM
> To: weigengyu
> Cc: Yoshifumi Nishida ; Brian Raymor ; tsv-art@ietf.org ;
> draft-ietf-core-coap-tcp-tls@ietf.org ; core@ietf.org ; ietf@ietf.org
> Subject: Re: [core] TSV-ART review of draft-ietf-core-coap-tcp-tls-07
>
> On May 2, 2017, at 07:31, weigengyu <weigengyu@bupt.edu.cn> wrote:
>
>>
>> The problem is when the C2C Proxy have got a message form the CoAP/TCP
>> side,
>> how the Proxy make a decision to delivery CON or NON message carrying
>> CoAP over UDP?
>>
>
> The question is not very different from the UDP to UDP proxying case.
> If a request came in via a UDP CON (which is the equivalent of using a
> reliable transport protocol), should the proxy use CON or NON for the
> forwarded request?
>
> I=E2=80=99d say, in both cases, CON should be the default way of forwardi=
ng the
> reliable request.
> But there may be specific cases where a NON may be appropriate =E2=80=94 =
CoAP does
> not provide the client with a way to control the proxy here.
>
> Is that a problem?  Tell me more about your use case.
>
> Gr=C3=BC=C3=9Fe, Carsten
>
>

--001a114095e8f5cd0e054ee8ac2b
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 Mon, May 1, 2017 at 11:11 PM, weigengyu <span dir=3D"ltr">&lt;<a href=3D=
"mailto:weigengyu@bupt.edu.cn" target=3D"_blank">weigengyu@bupt.edu.cn</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">Hi=EF=BC=8C<span class=
=3D""><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The question is not very different from the UDP to UDP proxying case.<br>
</blockquote></span>
Something is different.<span class=3D""><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
If a request came in via a UDP CON (which is the equivalent of using a reli=
able transport protocol),<br>
should the proxy use CON or NON for the forwarded request?<br>
</blockquote></span>
If it keeps the semantics end-to-end,=C2=A0 the proxy just forwards the mes=
sage.<br>
If it has the semantics hop-by-hop, the proxy can decide what type of messa=
ge to transfer.</blockquote><div><br></div><div>My interpretation for 5.2.3=
 in RFC7252 is CoAP layer can ignore the preference of applications and alt=
er the message type by its decisions. It seems to me proxies can choose mes=
sage types as they want.</div><div>--</div><div>Yoshi =C2=A0 =C2=A0</div><d=
iv><br></div><div><br></div><div><br></div><div><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><span class=3D""><br>
Gengyu WEI<br>
Network Technology Center<br>
School of Computer<br>
Beijing University of Posts and Telecommunications<br></span>
-----=E5=8E=9F=E5=A7=8B=E9=82=AE=E4=BB=B6----- From: Carsten Bormann<br>
Sent: Tuesday, May 02, 2017 2:01 PM<br>
To: weigengyu<br>
Cc: Yoshifumi Nishida ; Brian Raymor ; <a href=3D"mailto:tsv-art@ietf.org" =
target=3D"_blank">tsv-art@ietf.org</a> ; <a href=3D"mailto:draft-ietf-core-=
coap-tcp-tls@ietf.org" target=3D"_blank">draft-ietf-core-coap-tcp-tls@i<wbr=
>etf.org</a> ; <a href=3D"mailto:core@ietf.org" target=3D"_blank">core@ietf=
.org</a> ; <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org=
</a><span class=3D"im HOEnZb"><br>
Subject: Re: [core] TSV-ART review of draft-ietf-core-coap-tcp-tls-0<wbr>7<=
br>
<br></span><div class=3D"HOEnZb"><div class=3D"h5">
On May 2, 2017, at 07:31, weigengyu &lt;<a href=3D"mailto:weigengyu@bupt.ed=
u.cn" target=3D"_blank">weigengyu@bupt.edu.cn</a>&gt; wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
The problem is when the C2C Proxy have got a message form the CoAP/TCP side=
,<br>
how the Proxy make a decision to delivery CON or NON message carrying CoAP =
over UDP?<br>
</blockquote>
<br>
The question is not very different from the UDP to UDP proxying case.<br>
If a request came in via a UDP CON (which is the equivalent of using a reli=
able transport protocol), should the proxy use CON or NON for the forwarded=
 request?<br>
<br>
I=E2=80=99d say, in both cases, CON should be the default way of forwarding=
 the reliable request.<br>
But there may be specific cases where a NON may be appropriate =E2=80=94 Co=
AP does not provide the client with a way to control the proxy here.<br>
<br>
Is that a problem?=C2=A0 Tell me more about your use case.<br>
<br>
Gr=C3=BC=C3=9Fe, Carsten<br>
<br>
</div></div></blockquote></div><br></div></div>

--001a114095e8f5cd0e054ee8ac2b--


From nobody Sun May  7 09:25:00 2017
Return-Path: <shitanshu_shah@hotmail.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 C2197127419; Sun,  7 May 2017 09:24:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level: 
X-Spam-Status: No, score=-1.146 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LQGNryx86ipi; Sun,  7 May 2017 09:24:56 -0700 (PDT)
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-oln040092002086.outbound.protection.outlook.com [40.92.2.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B810B126CE8; Sun,  7 May 2017 09:24:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=kKo0QH+qBJVhmG2XkhXF575Tm+a3SsrsiAtaX5bBmqY=; b=Tn6fCq33yZTZl5D8z3bgYmDgg7+A2CkJIvyFb2xJzNURkfDd19lWMqy4w5xfUpq1+KEHB9GCMzUmOUb2GyDPq4F1cofSYEE1w5bFRE2hkP63HHNBPk2dSdB1ith41PEb1cjlSMfTTVDQQv5QiQkufuYa4CiY1yBUxSJrnla6oeUnPmGa4NFLOJfGPAp7cyQwDetoqmYyL0/DIP3Fy+9p8f6Kl/NVUDUNoeklTzlWMWS10D+BoIF70WelS0ktRnCE/7dho612sS7Lc7y8PwC1u+GbyTfcU43j7GK4y1I3rV++NqQhqz7ohi+uHf8xcfBrTtQDuIdfhbZnXAJlSpj2ZQ==
Received: from BY2NAM01FT042.eop-nam01.prod.protection.outlook.com (10.152.68.56) by BY2NAM01HT162.eop-nam01.prod.protection.outlook.com (10.152.69.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1047.9; Sun, 7 May 2017 16:24:51 +0000
Received: from BY2PR13MB0789.namprd13.prod.outlook.com (10.152.68.57) by BY2NAM01FT042.mail.protection.outlook.com (10.152.68.172) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1047.9 via Frontend Transport; Sun, 7 May 2017 16:24:51 +0000
Received: from BY2PR13MB0789.namprd13.prod.outlook.com ([10.164.169.9]) by BY2PR13MB0789.namprd13.prod.outlook.com ([10.164.169.9]) with mapi id 15.01.1084.015; Sun, 7 May 2017 16:24:51 +0000
From: Shitanshu Shah <shitanshu_shah@hotmail.com>
To: Joe Clarke <jclarke@cisco.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
CC: "idr@ietf.org" <idr@ietf.org>, "draft-ietf-idr-sla-exchange.all@ietf.org" <draft-ietf-idr-sla-exchange.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Opsdir early review of draft-ietf-idr-sla-exchange-10
Thread-Topic: Opsdir early review of draft-ietf-idr-sla-exchange-10
Thread-Index: AQHSxb5nxADcrfnZeka1+vZACdnIwqHpDDyz
Date: Sun, 7 May 2017 16:24:51 +0000
Message-ID: <BY2PR13MB07892B8E9249E59ED7CE692AE5E90@BY2PR13MB0789.namprd13.prod.outlook.com>
References: <149400246349.8370.5477015906856459639@ietfa.amsl.com>
In-Reply-To: <149400246349.8370.5477015906856459639@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:9947602216EA64DA54798EE7E0DBB43BF8CA4EA66D3787559058E746134C9E83; UpperCasedChecksum:FB6F99646E28FD6EC73285E1F2ECC6DF11186E66E207CB58E1E58037583D9B9D; SizeAsReceived:8401; Count:46
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [zOxyrrItBaR2YR0G0S3aMsEUZ8oL5Dms]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BY2NAM01HT162; 5:z7UxWQ5bzRXQMnigOgIkya26vYqAP9hq66AKI3g4o8WUrOh/V9fB45xlcJWhswxHpp+So6XFVsG643bawWwoUNp6SM01HRR6zrVX6bhZHOePrn3oYKTtlug8TsfJd3+fNDYWgwAO4CL162f2Cge6VQ==; 24:IcGx9C1a1sedwUU9d6deGO1YqpsJGfsJQmcY1AQ1MdsDKZZfo0bzAk6V1cJLWsAtsPnvJipZVjZwKJDFnMBIDxvZ44lflJrc8tpodFwtBgw=; 7:reqrmVHYQWbPVA1UivLzqFfUwHWkvdIpP6ukYLyH/dVpPKNRc2EYueL4c340YqAaKFXCuF2x3dgT3j4XSZOhzJwYlcNf0YwIrslv+1GdlbtklcnaR05RuDvh/ncfV7xq2DDBQgfPRT7tGm/X0DC5pUwQVinTfRaO8bQggHOQIeLX2kltsUZwUbs7Z/dyss/9th7ThfNfj2neil9pFa9TqCMWrZcAySWsHuT8o2hpZ7MVTLfLY6ech7DZDoj3GflsynVcFSIugdCpLUIma5v0wXaHIXA9ZhXpPGin8XPrgN48fS2FajpygWKs8EDJ5Hl0
x-incomingheadercount: 46
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:BY2NAM01HT162; H:BY2PR13MB0789.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: bc771417-6762-411d-8f90-08d49565965b
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:BY2NAM01HT162; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:BY2NAM01HT162; BCL:0; PCL:0; RULEID:; SRVR:BY2NAM01HT162; 
x-forefront-prvs: 03008837BD
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BY2PR13MB07892B8E9249E59ED7CE692AE5E90BY2PR13MB0789namp_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 May 2017 16:24:51.1494 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2NAM01HT162
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cHWMzbUJ3duP-KrpTRU564Xxz3U>
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, 07 May 2017 16:24:58 -0000

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




________________________________
From: Joe Clarke <jclarke@cisco.com>
Sent: Friday, May 5, 2017 10:41 AM
To: ops-dir@ietf.org
Cc: idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@ietf.org
Subject: Opsdir early review of draft-ietf-idr-sla-exchange-10

Reviewer: Joe Clarke
Review result: Has Issues

I have been asked to do a review of this draft as a representative of
OPS-DIR.  This draft lays out a means to exchange SLA/QoS policies via
BGP UPDATE messages.

Overall, I found this draft a bit difficult to read.  There are
grammatical issues such as the user of "thru" instead of "through",
odd commas, and missing articles.  But this is not a grammatical
overview.

I think this draft would benefit from some examples that show what
some practical QoS policies would look like that convey the required
classes within the maximum BGP message size (that is, in section 7 add
more specific examples of what policies may look like in the ADVERTISE
messages).  What do the authors feel typical uses of this would look
like from the UPDATE message perspective?  What kind of processing
overhead can one typically expect if a router, for example, will be
the QoS Attribute Speaker and SLA Consumer?

Below are some specific per-section questions and issues:

Section 2:

You state that a BGP Speaker need not be a QoS Attribute Speaker, but
even if the QoS data is opaque to the BGP Speaker, it would still need
to know that the QoS Attribute Speaker exists and there is data to be
added to the UPDATE.  So why the two entities don't need to be
co-resident in the same process, a BGP Speaker needs to be QoS aware
to some extent in order for this exchange to work.

Additionally, why are SLA Producer and Consumer broken out whereas QoS
and BGP just have "speakers?"  For consistency, maybe you just state
that there exists an SLA-aware QoS Attribute Speaker.

You do not define NLRI and AFI/SAFI in your terminology.

=3D=3D=3D

Section 3.2:

Why the need to have the SLA SubType Flags be set to 0?  Couldn't you
just as easily set the Source AS and Destination AS Counts to 0?  You
state that a value of 0 for Source AS when flags are 1 is illegal, so
I believe this would work.

For SLA ID, you state:

The SLA ID applies to aggregate traffic to prefixes for a given
AFI/SAFI that share the same Source AS and SLA ID.

The SLA ID applies to aggregate traffic that shares the same SLA ID?
This seems circular to me.  I'm not really clear on how I would
allocate an SLA ID and how I align that with the intended QoS
policies.

Would the intent of having a 0-length SLA Content be to remove the
policy for the given prefixes?  I'm not clear exactly as to that use
case.

I'm confused a bit as to how the Destination AS List works.
Initially, I thought this would only be set by the sending AS to
indicate to which external ASes the content applies.  However, each
QoS Attribute Speaker can update the Destination AS List.  In Sections
4.1.2, 5.1 and 5.2 you attempt to address this, but it is still not
clear what kind of updating or trimming of the Destination AS list
should be done (and in Section 5.2 you allude to rules to trim the
Destination AS List, but I did not see those rules).  This could be
clarified with an example of what can happen at various hops in the
network.

=3D=3D=3D

Section 3.3:

Related to a point above, if the SLA Content needs to be set per
direction, would I use the same SLA ID to do that?  I don't think
that's clear enough in the current text.

You state:

Any Traffic Class Element advertised in the QoS Attribute only
applies to the advertised AFI/SAFI NLRI within the BGP UPDATE
message the QoS Attribute is contained in.

However, if I understand correctly, I could specify IPFIX attributes
of sourceIPv6Prefix and/or destinationIPv6Prefix that does not line up
with the NLRIs, would that not constitute an error?  Or Maybe my
AFI/SAFI are 1/1, and I'm trying to match IPv6.  This seems more like
an error, but you only state what to do if the AFI/SAFI is not
supported.

=3D=3D=3D

Section 3.3.2.2:

Why have such a huge range for length here?  I can specify that the
number of bytes to specify the amount of L2 overhead to use is 255.
Why not advise that length should be 4, and then use an IEEE FP number
like you did for the TSPEC?  At the very least, I think this should be
reined in a bit.

=3D=3D=3D

Section 3.3.2.7:

I think you have a typo in precedence.  I think you want to say:

- MINRATE_IN_PROFILE_MARKING takes highest precedence (that is
    over MAXRATE_IN_PROFILE_MARKING),

- MAXRATE_IN_PROFILE_MARKING takes precedence over
   MINRATE_OUT_PROFILE_MARKING, and

- MINRATE_OUT_PROFILE_MARKING takes precedence over
   MAXRATE_OUT_PROFILE_MARKING

=3D=3D=3D

Section 5.2

What I did not see is what the actual SLA Consumer should do after it
processes the SLA Content.  I realize this can delve into
implementation details, but perhaps it's worth mentioning that the SLA
Consumer can use protocols like NETCONF or RESTCONF to configure the
policies on the necessary interfaces.



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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Arial,Helvetica,sans-serif;" dir=3D"ltr">
<p><br>
</p>
<br>
<br>
<div style=3D"color: rgb(0, 0, 0);">
<div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"x_divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" =
color=3D"#000000" style=3D"font-size:11pt"><b>From:</b> Joe Clarke &lt;jcla=
rke@cisco.com&gt;<br>
<b>Sent:</b> Friday, May 5, 2017 10:41 AM<br>
<b>To:</b> ops-dir@ietf.org<br>
<b>Cc:</b> idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@iet=
f.org<br>
<b>Subject:</b> Opsdir early review of draft-ietf-idr-sla-exchange-10</font=
>
<div>&nbsp;</div>
</div>
</div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">Reviewer: Joe Clarke<br>
Review result: Has Issues<br>
<br>
I have been asked to do a review of this draft as a representative of<br>
OPS-DIR.&nbsp; This draft lays out a means to exchange SLA/QoS policies via=
<br>
BGP UPDATE messages.<br>
<br>
Overall, I found this draft a bit difficult to read.&nbsp; There are<br>
grammatical issues such as the user of &quot;thru&quot; instead of &quot;th=
rough&quot;,<br>
odd commas, and missing articles.&nbsp; But this is not a grammatical<br>
overview.<br>
<br>
I think this draft would benefit from some examples that show what<br>
some practical QoS policies would look like that convey the required<br>
classes within the maximum BGP message size (that is, in section 7 add<br>
more specific examples of what policies may look like in the ADVERTISE<br>
messages).&nbsp; What do the authors feel typical uses of this would look<b=
r>
like from the UPDATE message perspective?&nbsp; What kind of processing<br>
overhead can one typically expect if a router, for example, will be<br>
the QoS Attribute Speaker and SLA Consumer?<br>
<br>
Below are some specific per-section questions and issues:<br>
<br>
Section 2:<br>
<br>
You state that a BGP Speaker need not be a QoS Attribute Speaker, but<br>
even if the QoS data is opaque to the BGP Speaker, it would still need<br>
to know that the QoS Attribute Speaker exists and there is data to be<br>
added to the UPDATE.&nbsp; So why the two entities don't need to be<br>
co-resident in the same process, a BGP Speaker needs to be QoS aware<br>
to some extent in order for this exchange to work.<br>
<br>
Additionally, why are SLA Producer and Consumer broken out whereas QoS<br>
and BGP just have &quot;speakers?&quot;&nbsp; For consistency, maybe you ju=
st state<br>
that there exists an SLA-aware QoS Attribute Speaker.<br>
<br>
You do not define NLRI and AFI/SAFI in your terminology.<br>
<br>
=3D=3D=3D<br>
<br>
Section 3.2:<br>
<br>
Why the need to have the SLA SubType Flags be set to 0?&nbsp; Couldn't you<=
br>
just as easily set the Source AS and Destination AS Counts to 0?&nbsp; You<=
br>
state that a value of 0 for Source AS when flags are 1 is illegal, so<br>
I believe this would work.<br>
<br>
For SLA ID, you state:<br>
<br>
The SLA ID applies to aggregate traffic to prefixes for a given<br>
AFI/SAFI that share the same Source AS and SLA ID.<br>
<br>
The SLA ID applies to aggregate traffic that shares the same SLA ID? <br>
This seems circular to me.&nbsp; I'm not really clear on how I would<br>
allocate an SLA ID and how I align that with the intended QoS<br>
policies.<br>
<br>
Would the intent of having a 0-length SLA Content be to remove the<br>
policy for the given prefixes?&nbsp; I'm not clear exactly as to that use<b=
r>
case.<br>
<br>
I'm confused a bit as to how the Destination AS List works. <br>
Initially, I thought this would only be set by the sending AS to<br>
indicate to which external ASes the content applies.&nbsp; However, each<br=
>
QoS Attribute Speaker can update the Destination AS List.&nbsp; In Sections=
<br>
4.1.2, 5.1 and 5.2 you attempt to address this, but it is still not<br>
clear what kind of updating or trimming of the Destination AS list<br>
should be done (and in Section 5.2 you allude to rules to trim the<br>
Destination AS List, but I did not see those rules).&nbsp; This could be<br=
>
clarified with an example of what can happen at various hops in the<br>
network.<br>
<br>
=3D=3D=3D<br>
<br>
Section 3.3:<br>
<br>
Related to a point above, if the SLA Content needs to be set per<br>
direction, would I use the same SLA ID to do that?&nbsp; I don't think<br>
that's clear enough in the current text.<br>
<br>
You state:<br>
<br>
Any Traffic Class Element advertised in the QoS Attribute only<br>
applies to the advertised AFI/SAFI NLRI within the BGP UPDATE<br>
message the QoS Attribute is contained in.<br>
<br>
However, if I understand correctly, I could specify IPFIX attributes<br>
of sourceIPv6Prefix and/or destinationIPv6Prefix that does not line up<br>
with the NLRIs, would that not constitute an error?&nbsp; Or Maybe my<br>
AFI/SAFI are 1/1, and I'm trying to match IPv6.&nbsp; This seems more like<=
br>
an error, but you only state what to do if the AFI/SAFI is not<br>
supported.<br>
<br>
=3D=3D=3D<br>
<br>
Section 3.3.2.2:<br>
<br>
Why have such a huge range for length here?&nbsp; I can specify that the<br=
>
number of bytes to specify the amount of L2 overhead to use is 255. <br>
Why not advise that length should be 4, and then use an IEEE FP number<br>
like you did for the TSPEC?&nbsp; At the very least, I think this should be=
<br>
reined in a bit.<br>
<br>
=3D=3D=3D<br>
<br>
Section 3.3.2.7:<br>
<br>
I think you have a typo in precedence.&nbsp; I think you want to say:<br>
<br>
- MINRATE_IN_PROFILE_MARKING takes highest precedence (that is<br>
&nbsp;&nbsp;&nbsp; over MAXRATE_IN_PROFILE_MARKING),<br>
<br>
- MAXRATE_IN_PROFILE_MARKING takes precedence over<br>
&nbsp;&nbsp; MINRATE_OUT_PROFILE_MARKING, and<br>
<br>
- MINRATE_OUT_PROFILE_MARKING takes precedence over<br>
&nbsp;&nbsp; MAXRATE_OUT_PROFILE_MARKING <br>
<br>
=3D=3D=3D<br>
<br>
Section 5.2<br>
<br>
What I did not see is what the actual SLA Consumer should do after it<br>
processes the SLA Content.&nbsp; I realize this can delve into<br>
implementation details, but perhaps it's worth mentioning that the SLA<br>
Consumer can use protocols like NETCONF or RESTCONF to configure the<br>
policies on the necessary interfaces.<br>
<br>
<br>
</div>
</span></font></div>
</div>
</body>
</html>

--_000_BY2PR13MB07892B8E9249E59ED7CE692AE5E90BY2PR13MB0789namp_--


From nobody Sun May  7 20:18:00 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 4668112025C; Sun,  7 May 2017 20:17:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 WVbUQ80mJ8Ua; Sun,  7 May 2017 20:17:56 -0700 (PDT)
Received: from mail-yb0-x234.google.com (mail-yb0-x234.google.com [IPv6:2607:f8b0:4002:c09::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 AC48F126CD6; Sun,  7 May 2017 20:17:56 -0700 (PDT)
Received: by mail-yb0-x234.google.com with SMTP id p143so8559489yba.2; Sun, 07 May 2017 20:17:56 -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=RXrwk9tjsQVQVx3ZiCsrWvjUljNWtkOCV+vRd08ULJ0=; b=tkYl8Re/NymyBwUfn+Z+IKxeAZYFGUdoLLYxM8oXRNT3/ZL6pk9iVqwq27hJbQQQGX hBInDkiJuFf7d0gV2kzXf56NkufGuccX6cuM2bjApd7oLDqm9+DOTawjMdXchL38AXw+ Zm6tCNuiSOUrG3uaooDSy06oNAMduoviNAEu3xemcJdpMQ5QH47RnQpRs4FMge2QjrFV jv3DRPj5O7/Rl27x3oDRQX1FZnqhK6EiPIlk7+w/TX8UzPE/7wFsV3+xyORfGe1GSR/Y vgL16zNKy9veHkHlyUEB2ZS1BhbBD4YVhYsZhmr7pwJ5O7UwkvwPXISotexyU5UeIRju xUJg==
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=RXrwk9tjsQVQVx3ZiCsrWvjUljNWtkOCV+vRd08ULJ0=; b=Khig0Rvt208YQaKd3UqjM3dWeSVc/+OQeqmwzkXtzO0+CG+WLR+o70CoUw1cDtgSbX c1dztHpICgO6AEy74bLSXHB9egSfMqZNdOs9/yHZ27NvPPPml9owhg2NnJVTuJAZ5fNo Ew1GRVqvL/SdxcipIjhQydbreNCF1gzeOHpCgbvJV8Isn/05GATxJYZGnF95QKodkQUE 8bhN13pVN+LvIuQSKOnbjh6NOUptHsPO3PUbJ6v+GSTkh3kyXN9FxgM8vscwF5tvfoQM cwqk+9wF9/CNVIQIlo4O5XfB8uHLyhwVMZbGsWax+zgVooQywERUss3rOdRDU3R8ckJE KS3g==
X-Gm-Message-State: AODbwcCIoxPfZqPsZcpo3q9t6D+R9Fe8byBc6cVkgcr6kHWPqq8n3ZjF A71kIvq5zmJxBAVz80nN4Lt2u5GsaQ==
X-Received: by 10.37.177.32 with SMTP id g32mr8970365ybj.82.1494213475927; Sun, 07 May 2017 20:17:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.161.198 with HTTP; Sun, 7 May 2017 20:17:55 -0700 (PDT)
In-Reply-To: <CAO249ydRLFpG=yHYvaZvPBiQuW5x=4HZqCZyTAb2HHeDuP+wAA@mail.gmail.com>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com> <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydcc7k2i5=OSSvvtzU2B1Qa62b3RR3iY0wBfQ2pOYQrkQ@mail.gmail.com> <BY2PR21MB00849DB795086F08F6D7A98A831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249yeS8sZaJcADuz+bYAJa-CXs4v291Fm=adRouO1R=svPDw@mail.gmail.com> <BY2PR21MB008453149ADC1A998FEA56D3831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydRLFpG=yHYvaZvPBiQuW5x=4HZqCZyTAb2HHeDuP+wAA@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sun, 7 May 2017 22:17:55 -0500
Message-ID: <CAKKJt-em-dLP9qyhTOZ00x4oOGuXVLdbbNaVVKH3kLw=6JZ_dw@mail.gmail.com>
Subject: Re: [Tsv-art] TSV-ART review of draft-ietf-core-coap-tcp-tls-07
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Cc: Brian Raymor <Brian.Raymor@microsoft.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>,  "draft-ietf-core-coap-tcp-tls@ietf.org" <draft-ietf-core-coap-tcp-tls@ietf.org>, "core@ietf.org" <core@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=f403045e5564738dfc054efaafc2
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WV9Ef8R7aNe31Wtm_S4C3M30a2M>
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, 08 May 2017 03:17:59 -0000

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

Hi, Yoshi,

On Sat, Apr 29, 2017 at 11:24 PM, Yoshifumi Nishida <nishida@sfc.wide.ad.jp=
>
wrote:

> Hello,
> As far as I've read -08 draft, I think this point has not been addressed
> yet. I hope some folks could elaborate a bit more if they think this is n=
ot
> an important point for the draft.
>

I've seen the subsequent e-mails in reply to yours, but it's not obvious to
me whether you think this point was addressed after reading those e-mails.

What do you think?

Thanks,

Spencer


> --
> Yoshi
>
> On Fri, Apr 21, 2017 at 2:57 PM, Brian Raymor <Brian.Raymor@microsoft.com=
>
> wrote:
>
>> I think that I understand your perceptions better. Prior to adoption of
>> coap-tcp-tls and before I was active in the WG, I recall discussions
>> related to the confusion over application vs transport reliability in Co=
AP
>> especially as related to CON and NON. What was intended?
>>
>>
>>
>> Tim Carey outlined some concerns in:
>>
>> https://tools.ietf.org/html/draft-carey-core-std-msg-vs-tran
>> s-adapt-00#section-2
>>
>>
>>
>> This topic was presented in detail at IETF 93 -
>> https://www.ietf.org/proceedings/93/slides/slides-93-core-0.pdf -
>> starting on slide 23.
>>
>>
>>
>> And in a related thread on the mailing list back in 2015 -
>> https://www.ietf.org/mail-archive/web/core/current/msg06280.html -
>> Carsten responded:
>>
>>
>>
>> > In any case, CON and NON are about message layer semantics, not about
>> application semantics
>>
>> > -- you gave them a meaning they don't have.
>>
>>
>>
>> By IETF 94, the authors were reporting =E2=80=93 =E2=80=9CMost of the Co=
nfusion
>> around              CON/NON was resolved=E2=80=9D.
>>
>>
>>
>> Where relevant, I=E2=80=99ve added clarifications - such as the Appendix=
 related
>> to differences in Observe for reliable transports.
>>
>>
>>
>> Both Carsten and Hannes could probably offer more context if needed.
>>
>>
>>
>> *From:* Yoshifumi Nishida [mailto:nishida@sfc.wide.ad.jp]
>> *Sent:* Friday, April 21, 2017 2:08 PM
>> *To:* Brian Raymor <Brian.Raymor@microsoft.com>
>> *Cc:* Yoshifumi Nishida <nishida@sfc.wide.ad.jp>; tsv-art@ietf.org;
>> draft-ietf-core-coap-tcp-tls@ietf.org; core@ietf.org; ietf@ietf.org
>> *Subject:* Re: TSV-ART review of draft-ietf-core-coap-tcp-tls-07
>>
>>
>>
>> Hi Brian,
>>
>>
>>
>> Just in case,
>>
>> Reliable transports only provide reliability at transport level. It
>> doesn't provide reliability in application protocol level.
>>
>>
>>
>> RFC7252 has reliability mechanisms in it since it uses UDP. This means i=
t
>> has abilities to check both transport and app level reliability.
>>
>> This draft only provides transport level reliability and apps will need
>> to detect app protocol failure by themselves.
>>
>> This means 7252 and this draft are not totally equivalent from the
>> viewpoint of applications.
>>
>>
>>
>> I am not saying this is wrong or bad, but I believe app developer should
>> aware this point.
>>
>> --
>>
>> Yoshi
>>
>>
>>
>> On Fri, Apr 21, 2017 at 11:15 AM, Brian Raymor <
>> Brian.Raymor@microsoft.com> wrote:
>>
>> Hi Yoshi,
>>
>>
>>
>> > OK. I also think we should state that the protocol should notify the
>> failure events to applications.
>>
>> > Since errors can happen not only in TCP, but also TLS and websocket
>> level, mentioning only TCP close or reset might not
>>
>> > be enough.
>>
>>
>>
>> After reviewing with the authors, an additional clarification was
>> appended to 3.4 Connection Health - https://github.com/core-wg/coa
>> p-tcp-tls/pull/140/files
>>
>>
>>
>> The opinion of the authors (and Gengyu WEI=E2=80=99s recent response -
>> https://www.ietf.org/mail-archive/web/core/current/msg08622.html) is
>> that RFC6455 covers the WebSocket case and does not need to be repeated
>> here.
>>
>>
>>
>> > When we use 7252, I think applications basically don't need to
>> implement timeouts or retry mechanisms as the protocol
>>
>> > provides such things.
>>
>>
>>
>> RFC7252 provides timeouts and retries because it's implementing a
>> TCP-like reliability mechanism over UDP - https://tools.ietf.org/html/rf
>> c7252#section-2.1
>>
>>
>>
>> > However, when we use this one, it seems applications will need to have
>> such mechanisms. Isn't it a bit confusing? I am thinking that
>>
>> > there need to be some guidance here.
>>
>> > BTW, PONG is one example.
>>
>>
>>
>> For coap-tcp-tls, there are multiple early implementations. This has
>> never been reported as a source of confusion.
>>
>>
>>
>> >> My sense is that we should treat this as an update to RFC7959 based o=
n
>> the original language:
>>
>> > I don't have a strong opinion here. Updating 7959 is fine for me if
>> it's clearer to CoAP people.
>>
>>
>>
>> I've merged the change - https://github.com/core-wg/coa
>> p-tcp-tls/pull/138/files
>>
>>
>>
>> Thanks again for helping us to improve the quality of the draft,
>>
>>
>>
>> =E2=80=A6Brian
>>
>>
>>
>
>
> _______________________________________________
> Tsv-art mailing list
> Tsv-art@ietf.org
> https://www.ietf.org/mailman/listinfo/tsv-art
>
>

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

<div dir=3D"ltr">Hi, Yoshi,<div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On Sat, Apr 29, 2017 at 11:24 PM, Yoshifumi Nishida <span dir=3D"=
ltr">&lt;<a href=3D"mailto:nishida@sfc.wide.ad.jp" target=3D"_blank">nishid=
a@sfc.wide.ad.jp</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"><d=
iv dir=3D"ltr">Hello,<div>As far as I&#39;ve read -08 draft, I think this p=
oint has not been addressed yet. I hope some folks could elaborate a bit mo=
re if they think this is not an important point for the draft.</div></div><=
/blockquote><div><br></div><div>I&#39;ve seen the subsequent e-mails in rep=
ly to yours, but it&#39;s not obvious to me whether you think this point wa=
s addressed after reading those e-mails.</div><div><br></div><div>What do y=
ou think?</div><div><br></div><div>Thanks,</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"><div dir=3D"ltr"><div=
>--</div><div>Yoshi</div><div><div class=3D"gmail_extra"><br><div class=3D"=
gmail_quote">On Fri, Apr 21, 2017 at 2:57 PM, Brian Raymor <span dir=3D"ltr=
">&lt;<a href=3D"mailto:Brian.Raymor@microsoft.com" target=3D"_blank">Brian=
.Raymor@microsoft.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_-7965682870498344231m_-185370657942848524m_7105224061284585=
916m_-1893619406420712677WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">I think that I understand your perceptions better. =
Prior to adoption of coap-tcp-tls and before I was active in the WG, I reca=
ll discussions related to the confusion over application
 vs transport reliability in CoAP especially as related to CON and NON. Wha=
t was intended?<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">Tim Carey outlined some concerns in:<u></u><u></u><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><a href=3D"https://tools.ietf.org/html/draft-carey-=
core-std-msg-vs-trans-adapt-00#section-2" target=3D"_blank">https://tools.i=
etf.org/html/dr<wbr>aft-carey-core-std-msg-vs-tran<wbr>s-adapt-00#section-2=
</a><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">This topic was presented in detail at IETF 93 -
<a href=3D"https://www.ietf.org/proceedings/93/slides/slides-93-core-0.pdf"=
 target=3D"_blank">https://www.ietf.org/proceedin<wbr>gs/93/slides/slides-9=
3-core-0.<wbr>pdf</a> - starting on slide 23.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">And in a related thread on the mailing list back in=
 2015 -
<a href=3D"https://www.ietf.org/mail-archive/web/core/current/msg06280.html=
" target=3D"_blank">https://www.ietf.org/mail-arch<wbr>ive/web/core/current=
/msg06280.<wbr>html</a> - Carsten responded:<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">&gt; In any case, CON and NON are about message lay=
er semantics, not about application semantics<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">&gt; -- you gave them a meaning they don&#39;t have=
.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">By IETF 94, the authors were reporting =E2=80=93 =
=E2=80=9CMost of the Confusion around=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 CON/NON was resolved=E2=80=9D.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">Where relevant, I=E2=80=99ve added clarifications -=
 such as the Appendix related to differences in Observe for reliable transp=
orts.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">Both Carsten and Hannes could probably offer more c=
ontext if needed.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><a name=3D"m_-7965682870498344231_m_-185370657942848=
524_m_7105224061284585916_m_-1893619406420712677__MailEndCompose"><span sty=
le=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"><u></u>=
=C2=A0<u></u></span></a></p>
<span></span>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> Yoshifumi Nishida [mailto:<a h=
ref=3D"mailto:nishida@sfc.wide.ad.jp" target=3D"_blank">nishida@sfc.wide.ad=
.jp</a><wbr>]
<br>
<b>Sent:</b> Friday, April 21, 2017 2:08 PM<br>
<b>To:</b> Brian Raymor &lt;<a href=3D"mailto:Brian.Raymor@microsoft.com" t=
arget=3D"_blank">Brian.Raymor@microsoft.com</a>&gt;<br>
<b>Cc:</b> Yoshifumi Nishida &lt;<a href=3D"mailto:nishida@sfc.wide.ad.jp" =
target=3D"_blank">nishida@sfc.wide.ad.jp</a>&gt;; <a href=3D"mailto:tsv-art=
@ietf.org" target=3D"_blank">tsv-art@ietf.org</a>; <a href=3D"mailto:draft-=
ietf-core-coap-tcp-tls@ietf.org" target=3D"_blank">draft-ietf-core-coap-tcp=
-tls@i<wbr>etf.org</a>; <a href=3D"mailto:core@ietf.org" target=3D"_blank">=
core@ietf.org</a>; <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@=
ietf.org</a><br>
<b>Subject:</b> Re: TSV-ART review of draft-ietf-core-coap-tcp-tls-0<wbr>7<=
u></u><u></u></span></p><div><div class=3D"h5"><div><div class=3D"m_-796568=
2870498344231m_-185370657942848524m_7105224061284585916h5">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Hi Brian,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Just in case,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Reliable transports only provide reliability at tran=
sport level. It doesn&#39;t provide reliability in application protocol lev=
el.=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">RFC7252 has reliability mechanisms in it since it us=
es UDP. This means it has abilities to check both transport and app level r=
eliability.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This draft only provides transport level reliability=
 and apps will need to detect app protocol failure by themselves.=C2=A0<u><=
/u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This means 7252 and this draft are not totally equiv=
alent from the viewpoint of applications.=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">I am not saying this is wrong or bad, but I believe =
app developer should aware this point.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Yoshi<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Fri, Apr 21, 2017 at 11:15 AM, Brian Raymor &lt;<=
a href=3D"mailto:Brian.Raymor@microsoft.com" target=3D"_blank">Brian.Raymor=
@microsoft.com</a>&gt; wrote:<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">
<div>
<div>
<div>
<div>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">Hi Yoshi,<u=
></u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">=C2=A0<u></=
u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">&gt; OK. I =
also think we should state that the protocol should notify the failure even=
ts to applications.=C2=A0<u></u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">&gt; Since =
errors can happen not only in TCP, but also TLS and websocket level, mentio=
ning only TCP close or reset might not
<u></u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">&gt; be eno=
ugh.<u></u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">=C2=A0<u></=
u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">After revie=
wing with the authors, an additional clarification was appended to 3.4 Conn=
ection Health -
<a href=3D"https://github.com/core-wg/coap-tcp-tls/pull/140/files" target=
=3D"_blank">
https://github.com/core-wg/coa<wbr>p-tcp-tls/pull/140/files</a><u></u><u></=
u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">=C2=A0<u></=
u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">The opinion=
 of the authors (and Gengyu WEI=E2=80=99s recent response -
<a href=3D"https://www.ietf.org/mail-archive/web/core/current/msg08622.html=
" target=3D"_blank">
https://www.ietf.org/mail-arch<wbr>ive/web/core/current/msg08622.<wbr>html<=
/a>) is that RFC6455 covers the WebSocket case and does not need to be repe=
ated here.<u></u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">=C2=A0<u></=
u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">&gt; When w=
e use 7252, I think applications basically don&#39;t need to implement time=
outs or retry mechanisms as the protocol<u></u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">&gt; provid=
es such things. <u></u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">=C2=A0<u></=
u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">RFC7252 pro=
vides timeouts and retries because it&#39;s implementing a TCP-like reliabi=
lity mechanism over UDP -
<a href=3D"https://tools.ietf.org/html/rfc7252#section-2.1" target=3D"_blan=
k">https://tools.ietf.org/html/rf<wbr>c7252#section-2.1</a><u></u><u></u></=
p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">=C2=A0<u></=
u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">&gt; Howeve=
r, when we use this one, it seems applications will need to have such mecha=
nisms. Isn&#39;t it a bit confusing? I am thinking that<u></u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">&gt; there =
need to be some guidance here.<u></u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">&gt; BTW, P=
ONG is one example.<u></u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">=C2=A0<u></=
u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">For coap-tc=
p-tls, there are multiple early implementations. This has never been report=
ed as a source of confusion.
<u></u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">=C2=A0<u></=
u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">&gt;&gt; My=
 sense is that we should treat this as an update to RFC7959 based on the or=
iginal language:<u></u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">&gt; I don&=
#39;t have a strong opinion here. Updating 7959 is fine for me if it&#39;s =
clearer to CoAP people.<u></u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">=C2=A0<u></=
u><u></u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">I&#39;ve me=
rged the change - <a href=3D"https://github.com/core-wg/coap-tcp-tls/pull/1=
38/files" target=3D"_blank">
https://github.com/core-wg/coa<wbr>p-tcp-tls/pull/138/files</a><u></u><u></=
u></p>
<p class=3D"m_-7965682870498344231m_-185370657942848524m_710522406128458591=
6m_-1893619406420712677gmail-m-3058448815637676647msoplaintext">=C2=A0<u></=
u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">Thanks again for helping us to improve the quality =
of the draft,</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#888888">=C2=A0</span><span style=3D"color:#88=
8888"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#888888">=E2=80=A6Brian</span><span style=3D"c=
olor:#888888"><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
</div></div></div></div></div>
</div>

</blockquote></div><br></div></div></div>
<br>______________________________<wbr>_________________<br>
Tsv-art mailing list<br>
<a href=3D"mailto:Tsv-art@ietf.org">Tsv-art@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tsv-art" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/tsv-art</a><=
br>
<br></blockquote></div><br></div></div>

--f403045e5564738dfc054efaafc2--


From nobody Sun May  7 20:44:01 2017
Return-Path: <enkechen@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 A903412025C; Sun,  7 May 2017 20:43:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 N95JqMe6N0Un; Sun,  7 May 2017 20:43:58 -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 E1CF8120046; Sun,  7 May 2017 20:43:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2130; q=dns/txt; s=iport; t=1494215038; x=1495424638; h=subject:references:cc:to:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=LYH46W9o2esjrq0H0tHZcx/6S3jShixYQ4+vB29E5gY=; b=EHbGSokBplOCQKk5tEHZG6vFHHN2hQsE6WAGfqwWzEH8UPkD5Iu9h6kS 0u6mWj4m1mze9clX4nDRjKxKytdZsnOE+33A8zM9N8Am2KtJkcKLJBDk6 FvBUEvf4OY1I1Ngt/0HdtMa2LHdtuMuJ5Y216mIjXQnxgriIGjnMw2Hk+ Q=;
X-IronPort-AV: E=Sophos;i="5.38,307,1491264000"; d="scan'208";a="418118842"
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; 08 May 2017 03:43:57 +0000
Received: from [10.24.44.82] ([10.24.44.82]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id v483hurm014391; Mon, 8 May 2017 03:43:56 GMT
Subject: Re: [Idr] Last Call: <draft-ietf-idr-shutdown-08.txt> (BGP Administrative Shutdown Communication) to Proposed Standard
References: <149400686065.8457.16928207738917615877.idtracker@ietfa.amsl.com>
Cc: draft-ietf-idr-shutdown@ietf.org, idr@ietf.org, idr-chairs@ietf.org, Enke Chen <enkechen@cisco.com>
To: ietf@ietf.org
From: Enke Chen <enkechen@cisco.com>
Message-ID: <9d8cf31a-fc21-096b-543e-58750894a22a@cisco.com>
Date: Sun, 7 May 2017 20:43:56 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <149400686065.8457.16928207738917615877.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RT-lWeoxyHUbxlpIWYjaV8I5fyg>
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, 08 May 2017 03:44:00 -0000

Hi, Folks:

Just spotted this (apologies for not catching it earlier):

The draft specifies only 0 - 128 as valid in the one-octet length field.
Not sure if there is a strong reason for such an apparent over-specification.

It seems to me that the spec can and should be simplified by removing the
restriction, that is, to allow any value (0 - 255) to be valid.  That would
also eliminate one error condition for the implementation.

Thanks.  -- Enke

---
2.  Shutdown Communication

Length:  this 8-bit field represents the length of the Shutdown
      Communication field in octets.  The length value MUST range from 0
      to 128 inclusive.

4.  Error Handling

   If a Shutdown Communication with an invalid Length value,
----

On 5/5/17 10:54 AM, The IESG wrote:
> 
> The IESG has received a request from the Inter-Domain Routing WG (idr) to
> consider the following document:
> - 'BGP Administrative Shutdown Communication'
>   <draft-ietf-idr-shutdown-08.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-05-19. 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 enhances the BGP Cease NOTIFICATION message
>    "Administrative Shutdown" and "Administrative Reset" subcodes for
>    operators to transmit a short freeform message to describe why a BGP
>    session was shutdown or reset.  This document updates RFC 4486.
> 
> 
> 
> 
> 
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> 
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
> 


From nobody Sun May  7 22:00:24 2017
Return-Path: <weigengyu@bupt.edu.cn>
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 ADF1E128DF2 for <ietf@ietfa.amsl.com>; Sun,  7 May 2017 22:00:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, 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 ujFOzIZIIriJ for <ietf@ietfa.amsl.com>; Sun,  7 May 2017 22:00:20 -0700 (PDT)
Received: from mx1.bupt.edu.cn (mx1.bupt.edu.cn [211.68.68.2]) by ietfa.amsl.com (Postfix) with ESMTP id 159F7126CBF for <ietf@ietf.org>; Sun,  7 May 2017 22:00:20 -0700 (PDT)
Received: from WeiGengyuPC (unknown [114.246.133.86]) by mx1.bupt.edu.cn (AnyMacro(G7)) with ESMTPA id 0815F19F382; Mon,  8 May 2017 12:52:21 +0800 (HKT)
Message-ID: <08549A3D9D2643EA99EE576FBF1E8C29@WeiGengyuPC>
From: "weigengyu" <weigengyu@bupt.edu.cn>
To: "Spencer Dawkins at IETF" <spencerdawkins.ietf@gmail.com>, "Yoshifumi Nishida" <nishida@sfc.wide.ad.jp>
Cc: <tsv-art@ietf.org>, <draft-ietf-core-coap-tcp-tls@ietf.org>, <core@ietf.org>, <ietf@ietf.org>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com> <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydcc7k2i5=OSSvvtzU2B1Qa62b3RR3iY0wBfQ2pOYQrkQ@mail.gmail.com> <BY2PR21MB00849DB795086F08F6D7A98A831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249yeS8sZaJcADuz+bYAJa-CXs4v291Fm=adRouO1R=svPDw@mail.gmail.com> <BY2PR21MB008453149ADC1A998FEA56D3831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydRLFpG=yHYvaZvPBiQuW5x=4HZqCZyTAb2HHeDuP+wAA@mail.gmail.com> <CAKKJt-em-dLP9qyhTOZ00x4oOGuXVLdbbNaVVKH3kLw=6JZ_dw@mail.gmail.com>
In-Reply-To: <CAKKJt-em-dLP9qyhTOZ00x4oOGuXVLdbbNaVVKH3kLw=6JZ_dw@mail.gmail.com>
Subject: Re: [core] [Tsv-art] TSV-ART review of draft-ietf-core-coap-tcp-tls-07
Date: Mon, 8 May 2017 12:52:20 +0800
Organization: BUPT
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0032_01D2C7F9.EE8C4540"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3528.331
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CV2D2tq4cloFS_rJWMDLlT0zxXc>
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, 08 May 2017 05:00:23 -0000

ÕâÊÇһ·â MIME ¸ñʽµĶ෽Óʼþ¡£

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

Hi,=20

A question related.=20
It needs clarifying the CoAP End-to-End Semancetics for the following =
scenarios:=20

1. CoAP EP1/UDP  ----> CoAP to CoAP Proxy  ----> CoAP EP2/UDP
2. CoAP EP1/UDP  ----> CoAP to CoAP Proxy  ----> CoAP EP2/TCP

The CoAP semantics including request/response and messages is defined in =
RFC7252.=20
How the CoAP end-to-end semantics keep in a way among three cases.=20

The CoAP end-to-end semancetics is required to keep=20
  (1) between CoAP EP1 and CoAP EP2,=20
  (2) or between CoAP EP1 and C2C proxy, and between C2C Proxy and CoAP =
EP2,=20
       in another wors, the CoAP is hop-by-hop.=20
  (3) or both (1) and (2).  =20

For (1), the proxy needs just to forward the message what received.=20
For (2), the proxy needs to make a CoAP message by its decisions.
For (3), the proxy needs to have functions of (1) and (2) and to =
distinguish (1) from (2).=20

I wonder which is required? What needs to support? =20

Regards,

Gengyu WEI
Network Technology Center
School of Computer=20
Beijing University of Posts and Telecommunications

From: Spencer Dawkins at IETF=20
Sent: Monday, May 08, 2017 11:17 AM
To: Yoshifumi Nishida=20
Cc: tsv-art@ietf.org ; draft-ietf-core-coap-tcp-tls@ietf.org ; =
core@ietf.org ; ietf@ietf.org=20
Subject: Re: [core] [Tsv-art] TSV-ART review of =
draft-ietf-core-coap-tcp-tls-07

Hi, Yoshi,=20

On Sat, Apr 29, 2017 at 11:24 PM, Yoshifumi Nishida =
<nishida@sfc.wide.ad.jp> wrote:

  Hello,=20
  As far as I've read -08 draft, I think this point has not been =
addressed yet. I hope some folks could elaborate a bit more if they =
think this is not an important point for the draft.

I've seen the subsequent e-mails in reply to yours, but it's not obvious =
to me whether you think this point was addressed after reading those =
e-mails.

What do you think?

Thanks,

Spencer

  --
  Yoshi

  On Fri, Apr 21, 2017 at 2:57 PM, Brian Raymor =
<Brian.Raymor@microsoft.com> wrote:

    I think that I understand your perceptions better. Prior to adoption =
of coap-tcp-tls and before I was active in the WG, I recall discussions =
related to the confusion over application vs transport reliability in =
CoAP especially as related to CON and NON. What was intended?



    Tim Carey outlined some concerns in:

    =
https://tools.ietf.org/html/draft-carey-core-std-msg-vs-trans-adapt-00#se=
ction-2



    This topic was presented in detail at IETF 93 - =
https://www.ietf.org/proceedings/93/slides/slides-93-core-0.pdf - =
starting on slide 23.



    And in a related thread on the mailing list back in 2015 - =
https://www.ietf.org/mail-archive/web/core/current/msg06280.html - =
Carsten responded:



    > In any case, CON and NON are about message layer semantics, not =
about application semantics

    > -- you gave them a meaning they don't have.=20



    By IETF 94, the authors were reporting =E2=80=93 =E2=80=9CMost of =
the Confusion around              CON/NON was resolved=E2=80=9D.=20



    Where relevant, I=E2=80=99ve added clarifications - such as the =
Appendix related to differences in Observe for reliable transports.



    Both Carsten and Hannes could probably offer more context if needed.



    From: Yoshifumi Nishida [mailto:nishida@sfc.wide.ad.jp]=20
    Sent: Friday, April 21, 2017 2:08 PM
    To: Brian Raymor <Brian.Raymor@microsoft.com>
    Cc: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>; tsv-art@ietf.org; =
draft-ietf-core-coap-tcp-tls@ietf.org; core@ietf.org; ietf@ietf.org
    Subject: Re: TSV-ART review of draft-ietf-core-coap-tcp-tls-07



    Hi Brian,



    Just in case,

    Reliable transports only provide reliability at transport level. It =
doesn't provide reliability in application protocol level.=20



    RFC7252 has reliability mechanisms in it since it uses UDP. This =
means it has abilities to check both transport and app level =
reliability.

    This draft only provides transport level reliability and apps will =
need to detect app protocol failure by themselves.=20

    This means 7252 and this draft are not totally equivalent from the =
viewpoint of applications.=20



    I am not saying this is wrong or bad, but I believe app developer =
should aware this point.

    --

    Yoshi



    On Fri, Apr 21, 2017 at 11:15 AM, Brian Raymor =
<Brian.Raymor@microsoft.com> wrote:

      Hi Yoshi,



      > OK. I also think we should state that the protocol should notify =
the failure events to applications.=20

      > Since errors can happen not only in TCP, but also TLS and =
websocket level, mentioning only TCP close or reset might not=20

      > be enough.



      After reviewing with the authors, an additional clarification was =
appended to 3.4 Connection Health - =
https://github.com/core-wg/coap-tcp-tls/pull/140/files



      The opinion of the authors (and Gengyu WEI=E2=80=99s recent =
response - =
https://www.ietf.org/mail-archive/web/core/current/msg08622.html) is =
that RFC6455 covers the WebSocket case and does not need to be repeated =
here.



      > When we use 7252, I think applications basically don't need to =
implement timeouts or retry mechanisms as the protocol

      > provides such things.=20



      RFC7252 provides timeouts and retries because it's implementing a =
TCP-like reliability mechanism over UDP - =
https://tools.ietf.org/html/rfc7252#section-2.1



      > However, when we use this one, it seems applications will need =
to have such mechanisms. Isn't it a bit confusing? I am thinking that

      > there need to be some guidance here.

      > BTW, PONG is one example.



      For coap-tcp-tls, there are multiple early implementations. This =
has never been reported as a source of confusion.=20



      >> My sense is that we should treat this as an update to RFC7959 =
based on the original language:

      > I don't have a strong opinion here. Updating 7959 is fine for me =
if it's clearer to CoAP people.



      I've merged the change - =
https://github.com/core-wg/coap-tcp-tls/pull/138/files



      Thanks again for helping us to improve the quality of the draft,



      =E2=80=A6Brian





  _______________________________________________
  Tsv-art mailing list
  Tsv-art@ietf.org
  https://www.ietf.org/mailman/listinfo/tsv-art





-------------------------------------------------------------------------=
-------
_______________________________________________
core mailing list
core@ietf.org
https://www.ietf.org/mailman/listinfo/core

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

<HTML><HEAD></HEAD>
<BODY dir=3Dltr>
<DIV dir=3Dltr>
<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>Hi, </DIV>
<DIV>&nbsp;</DIV>
<DIV>A question related. </DIV>
<DIV>It needs clarifying the CoAP End-to-End Semancetics for the =
following=20
scenarios: </DIV>
<DIV>&nbsp;</DIV>
<DIV>1. CoAP EP1/UDP&nbsp; ----&gt; CoAP to CoAP Proxy&nbsp; ----&gt; =
CoAP=20
EP2/UDP</DIV>
<DIV>2. CoAP EP1/UDP&nbsp; ----&gt; CoAP to CoAP Proxy&nbsp; ----&gt; =
CoAP=20
EP2/TCP</DIV>
<DIV>&nbsp;</DIV>
<DIV>The CoAP semantics including request/response and messages is =
defined in=20
RFC7252. </DIV>
<DIV>How the CoAP end-to-end semantics keep in a way among three cases. =
</DIV>
<DIV>&nbsp;</DIV>
<DIV>The CoAP end-to-end semancetics is required to keep </DIV>
<DIV>&nbsp; (1) between CoAP EP1 and CoAP EP2, </DIV>
<DIV>&nbsp; (2) or between CoAP EP1 and C2C proxy, and between C2C Proxy =
and=20
CoAP EP2, </DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in another wors, the CoAP is=20
hop-by-hop. </DIV>
<DIV>&nbsp; (3) or both (1) and (2).&nbsp;&nbsp; </DIV>
<DIV>&nbsp;</DIV>
<DIV>For (1), the proxy needs just to forward the message what received. =
</DIV>
<DIV>For (2), the proxy needs to make a CoAP message by its =
decisions.</DIV>
<DIV>For (3), the proxy needs to have functions of (1) and (2) and to=20
distinguish (1) from (2). </DIV>
<DIV>&nbsp;</DIV>
<DIV>I wonder which is required? What needs to support?&nbsp; </DIV>
<DIV>&nbsp;</DIV>
<DIV>Regards,</DIV>
<DIV>&nbsp;</DIV>
<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: =
#000000">Gengyu=20
WEI<BR>Network Technology Center<BR>School of Computer <BR>Beijing =
University of=20
Posts and Telecommunications</DIV>
<DIV=20
style=3D'FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: =
"Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; =
DISPLAY: inline'>
<DIV style=3D"FONT: 10pt tahoma">
<DIV><FONT size=3D3 face=3DCalibri></FONT>&nbsp;</DIV>
<DIV style=3D"BACKGROUND: #f5f5f5">
<DIV style=3D"font-color: black"><B>From:</B> <A=20
title=3Dspencerdawkins.ietf@gmail.com=20
href=3D"mailto:spencerdawkins.ietf@gmail.com">Spencer Dawkins at =
IETF</A> </DIV>
<DIV><B>Sent:</B> Monday, May 08, 2017 11:17 AM</DIV>
<DIV><B>To:</B> <A title=3Dnishida@sfc.wide.ad.jp=20
href=3D"mailto:nishida@sfc.wide.ad.jp">Yoshifumi Nishida</A> </DIV>
<DIV><B>Cc:</B> <A title=3Dtsv-art@ietf.org=20
href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.org</A> ; <A=20
title=3Ddraft-ietf-core-coap-tcp-tls@ietf.org=20
href=3D"mailto:draft-ietf-core-coap-tcp-tls@ietf.org">draft-ietf-core-coa=
p-tcp-tls@ietf.org</A>=20
; <A title=3Dcore@ietf.org =
href=3D"mailto:core@ietf.org">core@ietf.org</A> ; <A=20
title=3Dietf@ietf.org href=3D"mailto:ietf@ietf.org">ietf@ietf.org</A> =
</DIV>
<DIV><B>Subject:</B> Re: [core] [Tsv-art] TSV-ART review of=20
draft-ietf-core-coap-tcp-tls-07</DIV></DIV></DIV>
<DIV>&nbsp;</DIV></DIV>
<DIV=20
style=3D'FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: =
"Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; =
DISPLAY: inline'>
<DIV dir=3Dltr>Hi, Yoshi,=20
<DIV class=3Dgmail_extra>
<DIV>&nbsp;</DIV>
<DIV class=3Dgmail_quote>On Sat, Apr 29, 2017 at 11:24 PM, Yoshifumi =
Nishida <SPAN=20
dir=3Dltr>&lt;<A href=3D"mailto:nishida@sfc.wide.ad.jp"=20
target=3D_blank>nishida@sfc.wide.ad.jp</A>&gt;</SPAN> wrote:<BR>
<BLOCKQUOTE class=3Dgmail_quote=20
style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc =
1px solid">
  <DIV dir=3Dltr>Hello,=20
  <DIV>As far as I've read -08 draft, I think this point has not been =
addressed=20
  yet. I hope some folks could elaborate a bit more if they think this =
is not an=20
  important point for the draft.</DIV></DIV></BLOCKQUOTE>
<DIV>&nbsp;</DIV>
<DIV>I've seen the subsequent e-mails in reply to yours, but it's not =
obvious to=20
me whether you think this point was addressed after reading those =
e-mails.</DIV>
<DIV>&nbsp;</DIV>
<DIV>What do you think?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Spencer</DIV>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE class=3Dgmail_quote=20
style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc =
1px solid">
  <DIV dir=3Dltr>
  <DIV>--</DIV>
  <DIV>Yoshi</DIV>
  <DIV>
  <DIV class=3Dgmail_extra>
  <DIV>&nbsp;</DIV>
  <DIV class=3Dgmail_quote>On Fri, Apr 21, 2017 at 2:57 PM, Brian Raymor =
<SPAN=20
  dir=3Dltr>&lt;<A href=3D"mailto:Brian.Raymor@microsoft.com"=20
  target=3D_blank>Brian.Raymor@microsoft.com</A>&gt;</SPAN> wrote:<BR>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: =
#ccc 1px solid">
    <DIV lang=3DEN-US vlink=3D"purple" link=3D"blue">
    <DIV=20
    =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677WordSection1>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>I think =
that I=20
    understand your perceptions better. Prior to adoption of =
coap-tcp-tls and=20
    before I was active in the WG, I recall discussions related to the =
confusion=20
    over application vs transport reliability in CoAP especially as =
related to=20
    CON and NON. What was intended?<U></U><U></U></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'><U></U><U></U></SPAN>&nbsp;</P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>Tim =
Carey=20
    outlined some concerns in:<U></U><U></U></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'><A=20
    =
href=3D"https://tools.ietf.org/html/draft-carey-core-std-msg-vs-trans-ada=
pt-00#section-2"=20
    =
target=3D_blank>https://tools.ietf.org/html/dr<WBR>aft-carey-core-std-msg=
-vs-tran<WBR>s-adapt-00#section-2</A><U></U><U></U></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'><U></U><U></U></SPAN>&nbsp;</P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>This =
topic was=20
    presented in detail at IETF 93 - <A=20
    =
href=3D"https://www.ietf.org/proceedings/93/slides/slides-93-core-0.pdf" =

    =
target=3D_blank>https://www.ietf.org/proceedin<WBR>gs/93/slides/slides-93=
-core-0.<WBR>pdf</A>=20
    - starting on slide 23.<U></U><U></U></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'><U></U><U></U></SPAN>&nbsp;</P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>And in =
a related=20
    thread on the mailing list back in 2015 - <A=20
    =
href=3D"https://www.ietf.org/mail-archive/web/core/current/msg06280.html"=
=20
    =
target=3D_blank>https://www.ietf.org/mail-arch<WBR>ive/web/core/current/m=
sg06280.<WBR>html</A>=20
    - Carsten responded:<U></U><U></U></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'><U></U><U></U></SPAN>&nbsp;</P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>&gt; In =
any case,=20
    CON and NON are about message layer semantics, not about application =

    semantics<U></U><U></U></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>&gt; -- =
you gave=20
    them a meaning they don't have. <U></U><U></U></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'><U></U><U></U></SPAN>&nbsp;</P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>By IETF =
94, the=20
    authors were reporting =E2=80=93 =E2=80=9CMost of the Confusion=20
    =
around&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
    CON/NON was resolved=E2=80=9D. <U></U><U></U></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'><U></U><U></U></SPAN>&nbsp;</P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>Where =
relevant,=20
    I=E2=80=99ve added clarifications - such as the Appendix related to =
differences in=20
    Observe for reliable transports.<U></U><U></U></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'><U></U><U></U></SPAN>&nbsp;</P>
    <P class=3DMsoNormal><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>Both =
Carsten and=20
    Hannes could probably offer more context if =
needed.<U></U><U></U></SPAN></P>
    <P class=3DMsoNormal><A=20
    =
name=3Dm_-7965682870498344231_m_-185370657942848524_m_7105224061284585916=
_m_-1893619406420712677__MailEndCompose><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'><U></U><U></U></SPAN></A>&nbsp;</P><SPAN></SPAN>
    <P class=3DMsoNormal><B><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'>From:</SPAN></B><SPAN=20
    style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'> =
Yoshifumi=20
    Nishida [mailto:<A href=3D"mailto:nishida@sfc.wide.ad.jp"=20
    target=3D_blank>nishida@sfc.wide.ad.jp</A><WBR>] <BR><B>Sent:</B> =
Friday,=20
    April 21, 2017 2:08 PM<BR><B>To:</B> Brian Raymor &lt;<A=20
    href=3D"mailto:Brian.Raymor@microsoft.com"=20
    target=3D_blank>Brian.Raymor@microsoft.com</A>&gt;<BR><B>Cc:</B> =
Yoshifumi=20
    Nishida &lt;<A href=3D"mailto:nishida@sfc.wide.ad.jp"=20
    target=3D_blank>nishida@sfc.wide.ad.jp</A>&gt;; <A=20
    href=3D"mailto:tsv-art@ietf.org" =
target=3D_blank>tsv-art@ietf.org</A>; <A=20
    href=3D"mailto:draft-ietf-core-coap-tcp-tls@ietf.org"=20
    target=3D_blank>draft-ietf-core-coap-tcp-tls@i<WBR>etf.org</A>; <A=20
    href=3D"mailto:core@ietf.org" target=3D_blank>core@ietf.org</A>; <A=20
    href=3D"mailto:ietf@ietf.org"=20
    target=3D_blank>ietf@ietf.org</A><BR><B>Subject:</B> Re: TSV-ART =
review of=20
    draft-ietf-core-coap-tcp-tls-0<WBR>7<U></U><U></U></SPAN></P>
    <DIV>
    <DIV class=3Dh5>
    <DIV>
    <DIV=20
    =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916h=
5>
    <P class=3DMsoNormal><U></U><U></U>&nbsp;</P>
    <P class=3DMsoNormal>Hi Brian,<U></U><U></U></P>
    <DIV>
    <P class=3DMsoNormal><U></U><U></U>&nbsp;</P></DIV>
    <DIV>
    <P class=3DMsoNormal>Just in case,<U></U><U></U></P></DIV>
    <DIV>
    <P class=3DMsoNormal>Reliable transports only provide reliability at =
transport=20
    level. It doesn't provide reliability in application protocol level. =

    <U></U><U></U></P></DIV>
    <DIV>
    <P class=3DMsoNormal><U></U><U></U>&nbsp;</P></DIV>
    <DIV>
    <P class=3DMsoNormal>RFC7252 has reliability mechanisms in it since =
it uses=20
    UDP. This means it has abilities to check both transport and app =
level=20
    reliability.<U></U><U></U></P></DIV>
    <DIV>
    <P class=3DMsoNormal>This draft only provides transport level =
reliability and=20
    apps will need to detect app protocol failure by themselves.=20
    <U></U><U></U></P></DIV>
    <DIV>
    <P class=3DMsoNormal>This means 7252 and this draft are not totally =
equivalent=20
    from the viewpoint of applications. <U></U><U></U></P></DIV>
    <DIV>
    <P class=3DMsoNormal><U></U><U></U>&nbsp;</P></DIV>
    <DIV>
    <P class=3DMsoNormal>I am not saying this is wrong or bad, but I =
believe app=20
    developer should aware this point.<U></U><U></U></P></DIV>
    <DIV>
    <P class=3DMsoNormal>--<U></U><U></U></P></DIV>
    <DIV>
    <P class=3DMsoNormal>Yoshi<U></U><U></U></P></DIV>
    <P class=3DMsoNormal><U></U><U></U>&nbsp;</P>
    <DIV>
    <P class=3DMsoNormal>On Fri, Apr 21, 2017 at 11:15 AM, Brian Raymor =
&lt;<A=20
    href=3D"mailto:Brian.Raymor@microsoft.com"=20
    target=3D_blank>Brian.Raymor@microsoft.com</A>&gt; =
wrote:<U></U><U></U></P>
    <BLOCKQUOTE=20
    style=3D"BORDER-TOP: medium none; BORDER-RIGHT: medium none; =
BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 0in; =
PADDING-LEFT: 6pt; MARGIN-LEFT: 4.8pt; BORDER-LEFT: #cccccc 1pt solid; =
PADDING-RIGHT: 0in; MARGIN-RIGHT: 0in">
      <DIV>
      <DIV>
      <DIV>
      <DIV>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext>Hi=20
      Yoshi,<U></U><U></U></P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext><U></U><U></=
U>&nbsp;</P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext>&gt;=20
      OK. I also think we should state that the protocol should notify =
the=20
      failure events to applications. <U></U><U></U></P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext>&gt;=20
      Since errors can happen not only in TCP, but also TLS and =
websocket level,=20
      mentioning only TCP close or reset might not <U></U><U></U></P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext>&gt;=20
      be enough.<U></U><U></U></P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext><U></U><U></=
U>&nbsp;</P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext>After=20
      reviewing with the authors, an additional clarification was =
appended to=20
      3.4 Connection Health - <A=20
      href=3D"https://github.com/core-wg/coap-tcp-tls/pull/140/files"=20
      =
target=3D_blank>https://github.com/core-wg/coa<WBR>p-tcp-tls/pull/140/fil=
es</A><U></U><U></U></P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext><U></U><U></=
U>&nbsp;</P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext>The=20
      opinion of the authors (and Gengyu WEI=E2=80=99s recent response - =
<A=20
      =
href=3D"https://www.ietf.org/mail-archive/web/core/current/msg08622.html"=
=20
      =
target=3D_blank>https://www.ietf.org/mail-arch<WBR>ive/web/core/current/m=
sg08622.<WBR>html</A>)=20
      is that RFC6455 covers the WebSocket case and does not need to be =
repeated=20
      here.<U></U><U></U></P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext><U></U><U></=
U>&nbsp;</P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext>&gt;=20
      When we use 7252, I think applications basically don't need to =
implement=20
      timeouts or retry mechanisms as the protocol<U></U><U></U></P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext>&gt;=20
      provides such things. <U></U><U></U></P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext><U></U><U></=
U>&nbsp;</P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext>RFC7252=20
      provides timeouts and retries because it's implementing a TCP-like =

      reliability mechanism over UDP - <A=20
      href=3D"https://tools.ietf.org/html/rfc7252#section-2.1"=20
      =
target=3D_blank>https://tools.ietf.org/html/rf<WBR>c7252#section-2.1</A><=
U></U><U></U></P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext><U></U><U></=
U>&nbsp;</P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext>&gt;=20
      However, when we use this one, it seems applications will need to =
have=20
      such mechanisms. Isn't it a bit confusing? I am thinking=20
      that<U></U><U></U></P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext>&gt;=20
      there need to be some guidance here.<U></U><U></U></P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext>&gt;=20
      BTW, PONG is one example.<U></U><U></U></P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext><U></U><U></=
U>&nbsp;</P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext>For=20
      coap-tcp-tls, there are multiple early implementations. This has =
never=20
      been reported as a source of confusion. <U></U><U></U></P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext><U></U><U></=
U>&nbsp;</P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext>&gt;&gt;=20
      My sense is that we should treat this as an update to RFC7959 =
based on the=20
      original language:<U></U><U></U></P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext>&gt;=20
      I don't have a strong opinion here. Updating 7959 is fine for me =
if it's=20
      clearer to CoAP people.<U></U><U></U></P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext><U></U><U></=
U>&nbsp;</P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext>I've=20
      merged the change - <A=20
      href=3D"https://github.com/core-wg/coap-tcp-tls/pull/138/files"=20
      =
target=3D_blank>https://github.com/core-wg/coa<WBR>p-tcp-tls/pull/138/fil=
es</A><U></U><U></U></P>
      <P=20
      =
class=3Dm_-7965682870498344231m_-185370657942848524m_7105224061284585916m=
_-1893619406420712677gmail-m-3058448815637676647msoplaintext><U></U><U></=
U>&nbsp;</P>
      <P class=3DMsoNormal><SPAN=20
      style=3D'FONT-SIZE: 11pt; FONT-FAMILY: =
"Calibri",sans-serif'>Thanks again=20
      for helping us to improve the quality of the=20
      draft,</SPAN><U></U><U></U></P>
      <P class=3DMsoNormal><SPAN=20
      style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; =
COLOR: #888888'></SPAN><SPAN=20
      style=3D"COLOR: #888888"><U></U><U></U></SPAN>&nbsp;</P>
      <P class=3DMsoNormal><SPAN=20
      style=3D'FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; =
COLOR: #888888'>=E2=80=A6Brian</SPAN><SPAN=20
      style=3D"COLOR: =
#888888"><U></U><U></U></SPAN></P></DIV></DIV></DIV></DIV></BLOCKQUOTE></=
DIV>
    <DIV>
    <DIV>
    <DIV>
    <P=20
    =
class=3DMsoNormal><U></U><U></U>&nbsp;</P></DIV></DIV></DIV></DIV></DIV><=
/DIV></DIV></DIV></DIV></BLOCKQUOTE></DIV>
  =
<DIV>&nbsp;</DIV></DIV></DIV></DIV><BR>______________________________<WBR=
>_________________<BR>Tsv-art=20
  mailing list<BR><A =
href=3D"mailto:Tsv-art@ietf.org">Tsv-art@ietf.org</A><BR><A=20
  href=3D"https://www.ietf.org/mailman/listinfo/tsv-art" =
rel=3Dnoreferrer=20
  =
target=3D_blank>https://www.ietf.org/mailman/<WBR>listinfo/tsv-art</A><BR=
><BR></BLOCKQUOTE></DIV>
<DIV>&nbsp;</DIV></DIV></DIV>
<P>
<HR>
_______________________________________________<BR>core mailing=20
list<BR>core@ietf.org<BR>https://www.ietf.org/mailman/listinfo/core<BR></=
DIV></DIV></DIV></BODY></HTML>

------=_NextPart_000_0032_01D2C7F9.EE8C4540--


From nobody Mon May  8 00:31:14 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 A31C9120726; Mon,  8 May 2017 00:31:13 -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 zn_fK4q7mr91; Mon,  8 May 2017 00:31:10 -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 7FB481252BA; Mon,  8 May 2017 00:31:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v487V3UJ006405; Mon, 8 May 2017 09:31:03 +0200 (CEST)
Received: from [172.20.10.9] (ip-109-43-3-45.web.vodafone.de [109.43.3.45]) (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 3wLvLZ4KZKzDGnc; Mon,  8 May 2017 09:31:02 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [core] [Tsv-art] TSV-ART review of draft-ietf-core-coap-tcp-tls-07
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAKKJt-em-dLP9qyhTOZ00x4oOGuXVLdbbNaVVKH3kLw=6JZ_dw@mail.gmail.com>
Date: Mon, 8 May 2017 09:31:00 +0200
Cc: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>, "tsv-art@ietf.org" <tsv-art@ietf.org>, "draft-ietf-core-coap-tcp-tls@ietf.org" <draft-ietf-core-coap-tcp-tls@ietf.org>,  "core@ietf.org" <core@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-Mao-Original-Outgoing-Id: 515921460.808467-f6d599a9985d35a22970a1c6d17b9be2
Content-Transfer-Encoding: quoted-printable
Message-Id: <4F24893A-C088-45EB-97CE-126231933918@tzi.org>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com> <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydcc7k2i5=OSSvvtzU2B1Qa62b3RR3iY0wBfQ2pOYQrkQ@mail.gmail.com> <BY2PR21MB00849DB795086F08F6D7A98A831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249yeS8sZaJcADuz+bYAJa-CXs4v291Fm=adRouO1R=svPDw@mail.gmail.com> <BY2PR21MB008453149ADC1A998FEA56D3831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydRLFpG=yHYvaZvPBiQuW5x=4HZqCZyTAb2HHeDuP+wAA@mail.gmail.com> <CAKKJt-em-dLP9qyhTOZ00x4oOGuXVLdbbNaVVKH3kLw=6JZ_dw@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_z_ACzoO-8I6doChoDyosMT5BFs>
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, 08 May 2017 07:31:14 -0000

Hi Spencer,=20

I=E2=80=99m not Yoshi :-), but I just have started working on an update =
of
https://lwig-wg.github.io/coap/#rfc.section.6
with some of the new information that relates to CoAP over reliable; I =
hope that I will be able to push this during this week.

Note that CoAP over TCP/TLS/WS does address application layer =
acknowledgement beyond the request-response acknowledgement semantics by =
introducing the custody option of the PING/PONG signaling messages.  =
This may be useful in compensating the decrease of information available =
to the CoAP application as a result of moving some of the transport =
functionality into TCP.

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



> On May 8, 2017, at 05:17, Spencer Dawkins at IETF =
<spencerdawkins.ietf@gmail.com> wrote:
>=20
> Hi, Yoshi,
>=20
> On Sat, Apr 29, 2017 at 11:24 PM, Yoshifumi Nishida =
<nishida@sfc.wide.ad.jp> wrote:
> Hello,
> As far as I've read -08 draft, I think this point has not been =
addressed yet. I hope some folks could elaborate a bit more if they =
think this is not an important point for the draft.
>=20
> I've seen the subsequent e-mails in reply to yours, but it's not =
obvious to me whether you think this point was addressed after reading =
those e-mails.
>=20
> What do you think?
>=20
> Thanks,
>=20
> Spencer
> =20
> --
> Yoshi
>=20
> On Fri, Apr 21, 2017 at 2:57 PM, Brian Raymor =
<Brian.Raymor@microsoft.com> wrote:
> I think that I understand your perceptions better. Prior to adoption =
of coap-tcp-tls and before I was active in the WG, I recall discussions =
related to the confusion over application vs transport reliability in =
CoAP especially as related to CON and NON. What was intended?
>=20
> =20
>=20
> Tim Carey outlined some concerns in:
>=20
> =
https://tools.ietf.org/html/draft-carey-core-std-msg-vs-trans-adapt-00#sec=
tion-2
>=20
> =20
>=20
> This topic was presented in detail at IETF 93 - =
https://www.ietf.org/proceedings/93/slides/slides-93-core-0.pdf - =
starting on slide 23.
>=20
> =20
>=20
> And in a related thread on the mailing list back in 2015 - =
https://www.ietf.org/mail-archive/web/core/current/msg06280.html - =
Carsten responded:
>=20
> =20
>=20
> > In any case, CON and NON are about message layer semantics, not =
about application semantics
>=20
> > -- you gave them a meaning they don't have.
>=20
> =20
>=20
> By IETF 94, the authors were reporting =E2=80=93 =E2=80=9CMost of the =
Confusion around              CON/NON was resolved=E2=80=9D.
>=20
> =20
>=20
> Where relevant, I=E2=80=99ve added clarifications - such as the =
Appendix related to differences in Observe for reliable transports.
>=20
> =20
>=20
> Both Carsten and Hannes could probably offer more context if needed.
>=20
> =20
>=20
> From: Yoshifumi Nishida [mailto:nishida@sfc.wide.ad.jp]=20
> Sent: Friday, April 21, 2017 2:08 PM
> To: Brian Raymor <Brian.Raymor@microsoft.com>
> Cc: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>; tsv-art@ietf.org; =
draft-ietf-core-coap-tcp-tls@ietf.org; core@ietf.org; ietf@ietf.org
> Subject: Re: TSV-ART review of draft-ietf-core-coap-tcp-tls-07
>=20
> =20
>=20
> Hi Brian,
>=20
> =20
>=20
> Just in case,
>=20
> Reliable transports only provide reliability at transport level. It =
doesn't provide reliability in application protocol level.=20
>=20
> =20
>=20
> RFC7252 has reliability mechanisms in it since it uses UDP. This means =
it has abilities to check both transport and app level reliability.
>=20
> This draft only provides transport level reliability and apps will =
need to detect app protocol failure by themselves.=20
>=20
> This means 7252 and this draft are not totally equivalent from the =
viewpoint of applications.=20
>=20
> =20
>=20
> I am not saying this is wrong or bad, but I believe app developer =
should aware this point.
>=20
> --
>=20
> Yoshi
>=20
> =20
>=20
> On Fri, Apr 21, 2017 at 11:15 AM, Brian Raymor =
<Brian.Raymor@microsoft.com> wrote:
>=20
> Hi Yoshi,
>=20
> =20
>=20
> > OK. I also think we should state that the protocol should notify the =
failure events to applications.=20
>=20
> > Since errors can happen not only in TCP, but also TLS and websocket =
level, mentioning only TCP close or reset might not
>=20
> > be enough.
>=20
> =20
>=20
> After reviewing with the authors, an additional clarification was =
appended to 3.4 Connection Health - =
https://github.com/core-wg/coap-tcp-tls/pull/140/files
>=20
> =20
>=20
> The opinion of the authors (and Gengyu WEI=E2=80=99s recent response - =
https://www.ietf.org/mail-archive/web/core/current/msg08622.html) is =
that RFC6455 covers the WebSocket case and does not need to be repeated =
here.
>=20
> =20
>=20
> > When we use 7252, I think applications basically don't need to =
implement timeouts or retry mechanisms as the protocol
>=20
> > provides such things.=20
>=20
> =20
>=20
> RFC7252 provides timeouts and retries because it's implementing a =
TCP-like reliability mechanism over UDP - =
https://tools.ietf.org/html/rfc7252#section-2.1
>=20
> =20
>=20
> > However, when we use this one, it seems applications will need to =
have such mechanisms. Isn't it a bit confusing? I am thinking that
>=20
> > there need to be some guidance here.
>=20
> > BTW, PONG is one example.
>=20
> =20
>=20
> For coap-tcp-tls, there are multiple early implementations. This has =
never been reported as a source of confusion.
>=20
> =20
>=20
> >> My sense is that we should treat this as an update to RFC7959 based =
on the original language:
>=20
> > I don't have a strong opinion here. Updating 7959 is fine for me if =
it's clearer to CoAP people.
>=20
> =20
>=20
> I've merged the change - =
https://github.com/core-wg/coap-tcp-tls/pull/138/files
>=20
> =20
>=20
> Thanks again for helping us to improve the quality of the draft,
>=20
> =20
>=20
> =E2=80=A6Brian
>=20
> =20
>=20
>=20
>=20
> _______________________________________________
> Tsv-art mailing list
> Tsv-art@ietf.org
> https://www.ietf.org/mailman/listinfo/tsv-art
>=20
>=20
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core


From nobody Mon May  8 00:49:03 2017
Return-Path: <nishida@sfc.wide.ad.jp>
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 14FA6120724; Mon,  8 May 2017 00:48:54 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 pXjefL2CpjAs; Mon,  8 May 2017 00:48:50 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 924EB1200C1; Mon,  8 May 2017 00:48:50 -0700 (PDT)
Received: from mail-oi0-f49.google.com (mail-oi0-f49.google.com [209.85.218.49]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 9B4AB29CD87; Mon,  8 May 2017 16:48:47 +0900 (JST)
Received: by mail-oi0-f49.google.com with SMTP id b204so41445558oii.1; Mon, 08 May 2017 00:48:47 -0700 (PDT)
X-Gm-Message-State: AN3rC/4HAnIyCgJbKJcGZJtmk7S5g5AFtRKistuTTpqWqXW6FqvjjKSf Ko3VCg8D/C5kWFKuNHtX1M442V+YmA==
X-Received: by 10.202.91.214 with SMTP id p205mr20485392oib.216.1494229726232;  Mon, 08 May 2017 00:48:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.4.55 with HTTP; Mon, 8 May 2017 00:48:45 -0700 (PDT)
In-Reply-To: <CAKKJt-em-dLP9qyhTOZ00x4oOGuXVLdbbNaVVKH3kLw=6JZ_dw@mail.gmail.com>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com> <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydcc7k2i5=OSSvvtzU2B1Qa62b3RR3iY0wBfQ2pOYQrkQ@mail.gmail.com> <BY2PR21MB00849DB795086F08F6D7A98A831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249yeS8sZaJcADuz+bYAJa-CXs4v291Fm=adRouO1R=svPDw@mail.gmail.com> <BY2PR21MB008453149ADC1A998FEA56D3831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydRLFpG=yHYvaZvPBiQuW5x=4HZqCZyTAb2HHeDuP+wAA@mail.gmail.com> <CAKKJt-em-dLP9qyhTOZ00x4oOGuXVLdbbNaVVKH3kLw=6JZ_dw@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Date: Mon, 8 May 2017 00:48:45 -0700
X-Gmail-Original-Message-ID: <CAO249yfpK5_gmHhb5og+8oS=E1Lq7cfK+LAb=+i3ON9voMqrmA@mail.gmail.com>
Message-ID: <CAO249yfpK5_gmHhb5og+8oS=E1Lq7cfK+LAb=+i3ON9voMqrmA@mail.gmail.com>
Subject: Re: [Tsv-art] TSV-ART review of draft-ietf-core-coap-tcp-tls-07
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>, Brian Raymor <Brian.Raymor@microsoft.com>,  "tsv-art@ietf.org" <tsv-art@ietf.org>,  "draft-ietf-core-coap-tcp-tls@ietf.org" <draft-ietf-core-coap-tcp-tls@ietf.org>, "core@ietf.org" <core@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a113d551c0b88f1054efe7898
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/N0qvDk7IvhAiv099tWBULUvW4RU>
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, 08 May 2017 07:48:54 -0000

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

Hi Spencer,

I still expect to see some more comments on this point (my review point 2:)
I basically would like to see more explanations about how to avoid protocol
deadlock or some clarifications that this won't be an issue.
--
Yoshi

On Sun, May 7, 2017 at 8:17 PM, Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:

> Hi, Yoshi,
>
> On Sat, Apr 29, 2017 at 11:24 PM, Yoshifumi Nishida <
> nishida@sfc.wide.ad.jp> wrote:
>
>> Hello,
>> As far as I've read -08 draft, I think this point has not been addressed
>> yet. I hope some folks could elaborate a bit more if they think this is =
not
>> an important point for the draft.
>>
>
> I've seen the subsequent e-mails in reply to yours, but it's not obvious
> to me whether you think this point was addressed after reading those
> e-mails.
>
> What do you think?
>
> Thanks,
>
> Spencer
>
>
>> --
>> Yoshi
>>
>> On Fri, Apr 21, 2017 at 2:57 PM, Brian Raymor <Brian.Raymor@microsoft.co=
m
>> > wrote:
>>
>>> I think that I understand your perceptions better. Prior to adoption of
>>> coap-tcp-tls and before I was active in the WG, I recall discussions
>>> related to the confusion over application vs transport reliability in C=
oAP
>>> especially as related to CON and NON. What was intended?
>>>
>>>
>>>
>>> Tim Carey outlined some concerns in:
>>>
>>> https://tools.ietf.org/html/draft-carey-core-std-msg-vs-tran
>>> s-adapt-00#section-2
>>>
>>>
>>>
>>> This topic was presented in detail at IETF 93 -
>>> https://www.ietf.org/proceedings/93/slides/slides-93-core-0.pdf -
>>> starting on slide 23.
>>>
>>>
>>>
>>> And in a related thread on the mailing list back in 2015 -
>>> https://www.ietf.org/mail-archive/web/core/current/msg06280.html -
>>> Carsten responded:
>>>
>>>
>>>
>>> > In any case, CON and NON are about message layer semantics, not about
>>> application semantics
>>>
>>> > -- you gave them a meaning they don't have.
>>>
>>>
>>>
>>> By IETF 94, the authors were reporting =E2=80=93 =E2=80=9CMost of the C=
onfusion
>>> around              CON/NON was resolved=E2=80=9D.
>>>
>>>
>>>
>>> Where relevant, I=E2=80=99ve added clarifications - such as the Appendi=
x related
>>> to differences in Observe for reliable transports.
>>>
>>>
>>>
>>> Both Carsten and Hannes could probably offer more context if needed.
>>>
>>>
>>>
>>> *From:* Yoshifumi Nishida [mailto:nishida@sfc.wide.ad.jp]
>>> *Sent:* Friday, April 21, 2017 2:08 PM
>>> *To:* Brian Raymor <Brian.Raymor@microsoft.com>
>>> *Cc:* Yoshifumi Nishida <nishida@sfc.wide.ad.jp>; tsv-art@ietf.org;
>>> draft-ietf-core-coap-tcp-tls@ietf.org; core@ietf.org; ietf@ietf.org
>>> *Subject:* Re: TSV-ART review of draft-ietf-core-coap-tcp-tls-07
>>>
>>>
>>>
>>> Hi Brian,
>>>
>>>
>>>
>>> Just in case,
>>>
>>> Reliable transports only provide reliability at transport level. It
>>> doesn't provide reliability in application protocol level.
>>>
>>>
>>>
>>> RFC7252 has reliability mechanisms in it since it uses UDP. This means
>>> it has abilities to check both transport and app level reliability.
>>>
>>> This draft only provides transport level reliability and apps will need
>>> to detect app protocol failure by themselves.
>>>
>>> This means 7252 and this draft are not totally equivalent from the
>>> viewpoint of applications.
>>>
>>>
>>>
>>> I am not saying this is wrong or bad, but I believe app developer shoul=
d
>>> aware this point.
>>>
>>> --
>>>
>>> Yoshi
>>>
>>>
>>>
>>> On Fri, Apr 21, 2017 at 11:15 AM, Brian Raymor <
>>> Brian.Raymor@microsoft.com> wrote:
>>>
>>> Hi Yoshi,
>>>
>>>
>>>
>>> > OK. I also think we should state that the protocol should notify the
>>> failure events to applications.
>>>
>>> > Since errors can happen not only in TCP, but also TLS and websocket
>>> level, mentioning only TCP close or reset might not
>>>
>>> > be enough.
>>>
>>>
>>>
>>> After reviewing with the authors, an additional clarification was
>>> appended to 3.4 Connection Health - https://github.com/core-wg/coa
>>> p-tcp-tls/pull/140/files
>>>
>>>
>>>
>>> The opinion of the authors (and Gengyu WEI=E2=80=99s recent response -
>>> https://www.ietf.org/mail-archive/web/core/current/msg08622.html) is
>>> that RFC6455 covers the WebSocket case and does not need to be repeated
>>> here.
>>>
>>>
>>>
>>> > When we use 7252, I think applications basically don't need to
>>> implement timeouts or retry mechanisms as the protocol
>>>
>>> > provides such things.
>>>
>>>
>>>
>>> RFC7252 provides timeouts and retries because it's implementing a
>>> TCP-like reliability mechanism over UDP - https://tools.ietf.org/html/r=
f
>>> c7252#section-2.1
>>>
>>>
>>>
>>> > However, when we use this one, it seems applications will need to hav=
e
>>> such mechanisms. Isn't it a bit confusing? I am thinking that
>>>
>>> > there need to be some guidance here.
>>>
>>> > BTW, PONG is one example.
>>>
>>>
>>>
>>> For coap-tcp-tls, there are multiple early implementations. This has
>>> never been reported as a source of confusion.
>>>
>>>
>>>
>>> >> My sense is that we should treat this as an update to RFC7959 based
>>> on the original language:
>>>
>>> > I don't have a strong opinion here. Updating 7959 is fine for me if
>>> it's clearer to CoAP people.
>>>
>>>
>>>
>>> I've merged the change - https://github.com/core-wg/coa
>>> p-tcp-tls/pull/138/files
>>>
>>>
>>>
>>> Thanks again for helping us to improve the quality of the draft,
>>>
>>>
>>>
>>> =E2=80=A6Brian
>>>
>>>
>>>
>>
>>
>> _______________________________________________
>> Tsv-art mailing list
>> Tsv-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/tsv-art
>>
>>
>

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

<div dir=3D"ltr">Hi Spencer,<div><br></div><div>I still expect to see some =
more comments on this point (my review point 2:)</div><div>I basically woul=
d like to see more explanations about how to avoid protocol deadlock or som=
e clarifications that this won&#39;t be an issue.</div><div>--</div><div>Yo=
shi</div><div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On =
Sun, May 7, 2017 at 8:17 PM, Spencer Dawkins at IETF <span dir=3D"ltr">&lt;=
<a href=3D"mailto:spencerdawkins.ietf@gmail.com" target=3D"_blank">spencerd=
awkins.ietf@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><div dir=3D"ltr">Hi, Yoshi,<div class=3D"gmail_extra"><br><div class=3D"=
gmail_quote"><span class=3D"">On Sat, Apr 29, 2017 at 11:24 PM, Yoshifumi N=
ishida <span dir=3D"ltr">&lt;<a href=3D"mailto:nishida@sfc.wide.ad.jp" targ=
et=3D"_blank">nishida@sfc.wide.ad.jp</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"><div dir=3D"ltr">Hello,<div>As far as I&#39;ve read -08 d=
raft, I think this point has not been addressed yet. I hope some folks coul=
d elaborate a bit more if they think this is not an important point for the=
 draft.</div></div></blockquote><div><br></div></span><div>I&#39;ve seen th=
e subsequent e-mails in reply to yours, but it&#39;s not obvious to me whet=
her you think this point was addressed after reading those e-mails.</div><d=
iv><br></div><div>What do you think?</div><div><br></div><div>Thanks,</div>=
<div><br></div><div>Spencer</div><div>=C2=A0</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><div><div class=3D"h5"><div dir=3D"ltr"><div>--</div><div>Yoshi</div>=
<div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Apr =
21, 2017 at 2:57 PM, Brian Raymor <span dir=3D"ltr">&lt;<a href=3D"mailto:B=
rian.Raymor@microsoft.com" target=3D"_blank">Brian.Raymor@microsoft.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">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_-2388476382627849178m_-7965682870498344231m_-18537065794284=
8524m_7105224061284585916m_-1893619406420712677WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">I think that I understand your perceptions better. =
Prior to adoption of coap-tcp-tls and before I was active in the WG, I reca=
ll discussions related to the confusion over application
 vs transport reliability in CoAP especially as related to CON and NON. Wha=
t was intended?<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">Tim Carey outlined some concerns in:<u></u><u></u><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><a href=3D"https://tools.ietf.org/html/draft-carey-=
core-std-msg-vs-trans-adapt-00#section-2" target=3D"_blank">https://tools.i=
etf.org/html/dr<wbr>aft-carey-core-std-msg-vs-tran<wbr>s-adapt-00#section-2=
</a><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">This topic was presented in detail at IETF 93 -
<a href=3D"https://www.ietf.org/proceedings/93/slides/slides-93-core-0.pdf"=
 target=3D"_blank">https://www.ietf.org/proceedin<wbr>gs/93/slides/slides-9=
3-core-0.<wbr>pdf</a> - starting on slide 23.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">And in a related thread on the mailing list back in=
 2015 -
<a href=3D"https://www.ietf.org/mail-archive/web/core/current/msg06280.html=
" target=3D"_blank">https://www.ietf.org/mail-arch<wbr>ive/web/core/current=
/msg06280.<wbr>html</a> - Carsten responded:<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">&gt; In any case, CON and NON are about message lay=
er semantics, not about application semantics<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">&gt; -- you gave them a meaning they don&#39;t have=
.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">By IETF 94, the authors were reporting =E2=80=93 =
=E2=80=9CMost of the Confusion around=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 CON/NON was resolved=E2=80=9D.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">Where relevant, I=E2=80=99ve added clarifications -=
 such as the Appendix related to differences in Observe for reliable transp=
orts.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">Both Carsten and Hannes could probably offer more c=
ontext if needed.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><a name=3D"m_-2388476382627849178_m_-796568287049834=
4231_m_-185370657942848524_m_7105224061284585916_m_-1893619406420712677__Ma=
ilEndCompose"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quo=
t;,sans-serif"><u></u>=C2=A0<u></u></span></a></p>
<span></span>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> Yoshifumi Nishida [mailto:<a h=
ref=3D"mailto:nishida@sfc.wide.ad.jp" target=3D"_blank">nishida@sfc.wide.ad=
.jp</a><wbr>]
<br>
<b>Sent:</b> Friday, April 21, 2017 2:08 PM<br>
<b>To:</b> Brian Raymor &lt;<a href=3D"mailto:Brian.Raymor@microsoft.com" t=
arget=3D"_blank">Brian.Raymor@microsoft.com</a>&gt;<br>
<b>Cc:</b> Yoshifumi Nishida &lt;<a href=3D"mailto:nishida@sfc.wide.ad.jp" =
target=3D"_blank">nishida@sfc.wide.ad.jp</a>&gt;; <a href=3D"mailto:tsv-art=
@ietf.org" target=3D"_blank">tsv-art@ietf.org</a>; <a href=3D"mailto:draft-=
ietf-core-coap-tcp-tls@ietf.org" target=3D"_blank">draft-ietf-core-coap-tcp=
-tls@i<wbr>etf.org</a>; <a href=3D"mailto:core@ietf.org" target=3D"_blank">=
core@ietf.org</a>; <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@=
ietf.org</a><br>
<b>Subject:</b> Re: TSV-ART review of draft-ietf-core-coap-tcp-tls-0<wbr>7<=
u></u><u></u></span></p><div><div class=3D"m_-2388476382627849178h5"><div><=
div class=3D"m_-2388476382627849178m_-7965682870498344231m_-185370657942848=
524m_7105224061284585916h5">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Hi Brian,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Just in case,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Reliable transports only provide reliability at tran=
sport level. It doesn&#39;t provide reliability in application protocol lev=
el.=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">RFC7252 has reliability mechanisms in it since it us=
es UDP. This means it has abilities to check both transport and app level r=
eliability.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This draft only provides transport level reliability=
 and apps will need to detect app protocol failure by themselves.=C2=A0<u><=
/u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This means 7252 and this draft are not totally equiv=
alent from the viewpoint of applications.=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">I am not saying this is wrong or bad, but I believe =
app developer should aware this point.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Yoshi<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Fri, Apr 21, 2017 at 11:15 AM, Brian Raymor &lt;<=
a href=3D"mailto:Brian.Raymor@microsoft.com" target=3D"_blank">Brian.Raymor=
@microsoft.com</a>&gt; wrote:<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">
<div>
<div>
<div>
<div>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">Hi Yoshi,<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">=C2=A0<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">&gt; OK. I also think we should state that the protocol should n=
otify the failure events to applications.=C2=A0<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">&gt; Since errors can happen not only in TCP, but also TLS and w=
ebsocket level, mentioning only TCP close or reset might not
<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">&gt; be enough.<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">=C2=A0<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">After reviewing with the authors, an additional clarification wa=
s appended to 3.4 Connection Health -
<a href=3D"https://github.com/core-wg/coap-tcp-tls/pull/140/files" target=
=3D"_blank">
https://github.com/core-wg/coa<wbr>p-tcp-tls/pull/140/files</a><u></u><u></=
u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">=C2=A0<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">The opinion of the authors (and Gengyu WEI=E2=80=99s recent resp=
onse -
<a href=3D"https://www.ietf.org/mail-archive/web/core/current/msg08622.html=
" target=3D"_blank">
https://www.ietf.org/mail-arch<wbr>ive/web/core/current/msg08622.<wbr>html<=
/a>) is that RFC6455 covers the WebSocket case and does not need to be repe=
ated here.<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">=C2=A0<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">&gt; When we use 7252, I think applications basically don&#39;t =
need to implement timeouts or retry mechanisms as the protocol<u></u><u></u=
></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">&gt; provides such things. <u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">=C2=A0<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">RFC7252 provides timeouts and retries because it&#39;s implement=
ing a TCP-like reliability mechanism over UDP -
<a href=3D"https://tools.ietf.org/html/rfc7252#section-2.1" target=3D"_blan=
k">https://tools.ietf.org/html/rf<wbr>c7252#section-2.1</a><u></u><u></u></=
p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">=C2=A0<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">&gt; However, when we use this one, it seems applications will n=
eed to have such mechanisms. Isn&#39;t it a bit confusing? I am thinking th=
at<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">&gt; there need to be some guidance here.<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">&gt; BTW, PONG is one example.<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">=C2=A0<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">For coap-tcp-tls, there are multiple early implementations. This=
 has never been reported as a source of confusion.
<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">=C2=A0<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">&gt;&gt; My sense is that we should treat this as an update to R=
FC7959 based on the original language:<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">&gt; I don&#39;t have a strong opinion here. Updating 7959 is fi=
ne for me if it&#39;s clearer to CoAP people.<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">=C2=A0<u></u><u></u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">I&#39;ve merged the change - <a href=3D"https://github.com/core-=
wg/coap-tcp-tls/pull/138/files" target=3D"_blank">
https://github.com/core-wg/coa<wbr>p-tcp-tls/pull/138/files</a><u></u><u></=
u></p>
<p class=3D"m_-2388476382627849178m_-7965682870498344231m_-1853706579428485=
24m_7105224061284585916m_-1893619406420712677gmail-m-3058448815637676647mso=
plaintext">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">Thanks again for helping us to improve the quality =
of the draft,</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#888888">=C2=A0</span><span style=3D"color:#88=
8888"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#888888">=E2=80=A6Brian</span><span style=3D"c=
olor:#888888"><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
</div></div></div></div></div>
</div>

</blockquote></div><br></div></div></div>
<br></div></div><span class=3D"">______________________________<wbr>_______=
__________<br>
Tsv-art mailing list<br>
<a href=3D"mailto:Tsv-art@ietf.org" target=3D"_blank">Tsv-art@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tsv-art" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/tsv-art</a><=
br>
<br></span></blockquote></div><br></div></div>
</blockquote></div><br></div></div></div>

--001a113d551c0b88f1054efe7898--


From nobody Mon May  8 00:49:56 2017
Return-Path: <nishida@sfc.wide.ad.jp>
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 75B3A120724; Mon,  8 May 2017 00:49:25 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 N0D_dl3i6jgI; Mon,  8 May 2017 00:49:13 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A126F1293E1; Mon,  8 May 2017 00:49:09 -0700 (PDT)
Received: from mail-oi0-f51.google.com (mail-oi0-f51.google.com [209.85.218.51]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id E67E729CD95; Mon,  8 May 2017 16:49:07 +0900 (JST)
Received: by mail-oi0-f51.google.com with SMTP id b204so41452538oii.1; Mon, 08 May 2017 00:49:07 -0700 (PDT)
X-Gm-Message-State: AN3rC/4+48eTdK132t8p//hRWfZFPE3yVQsVEvpzkOyPEmTkapWImpYf IwkVha6XiMVsEih98fdLpbUyL+P/Lw==
X-Received: by 10.157.17.29 with SMTP id g29mr12212497ote.86.1494229746695; Mon, 08 May 2017 00:49:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.4.55 with HTTP; Mon, 8 May 2017 00:49:05 -0700 (PDT)
In-Reply-To: <4F24893A-C088-45EB-97CE-126231933918@tzi.org>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com> <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydcc7k2i5=OSSvvtzU2B1Qa62b3RR3iY0wBfQ2pOYQrkQ@mail.gmail.com> <BY2PR21MB00849DB795086F08F6D7A98A831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249yeS8sZaJcADuz+bYAJa-CXs4v291Fm=adRouO1R=svPDw@mail.gmail.com> <BY2PR21MB008453149ADC1A998FEA56D3831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydRLFpG=yHYvaZvPBiQuW5x=4HZqCZyTAb2HHeDuP+wAA@mail.gmail.com> <CAKKJt-em-dLP9qyhTOZ00x4oOGuXVLdbbNaVVKH3kLw=6JZ_dw@mail.gmail.com> <4F24893A-C088-45EB-97CE-126231933918@tzi.org>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Date: Mon, 8 May 2017 00:49:05 -0700
X-Gmail-Original-Message-ID: <CAO249ye9DoKihJQsiwYEmhRWRXe8WqqW49XOvMABu_-gnkficg@mail.gmail.com>
Message-ID: <CAO249ye9DoKihJQsiwYEmhRWRXe8WqqW49XOvMABu_-gnkficg@mail.gmail.com>
Subject: Re: [Tsv-art] [core] TSV-ART review of draft-ietf-core-coap-tcp-tls-07
To: Carsten Bormann <cabo@tzi.org>
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>,  Yoshifumi Nishida <nishida@sfc.wide.ad.jp>,  "draft-ietf-core-coap-tcp-tls@ietf.org" <draft-ietf-core-coap-tcp-tls@ietf.org>, "core@ietf.org" <core@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a1141dfb043d382054efe7925
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EslPawsEtHuStUNn7-bXNLLPiLw>
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, 08 May 2017 07:49:26 -0000

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

Hi Carsten,

Great. I will take a look at it when it's published.
Thanks for the efforts!
--
Yoshi

On Mon, May 8, 2017 at 12:31 AM, Carsten Bormann <cabo@tzi.org> wrote:

> Hi Spencer,
>
> I=E2=80=99m not Yoshi :-), but I just have started working on an update o=
f
> https://lwig-wg.github.io/coap/#rfc.section.6
> with some of the new information that relates to CoAP over reliable; I
> hope that I will be able to push this during this week.
>
> Note that CoAP over TCP/TLS/WS does address application layer
> acknowledgement beyond the request-response acknowledgement semantics by
> introducing the custody option of the PING/PONG signaling messages.  This
> may be useful in compensating the decrease of information available to th=
e
> CoAP application as a result of moving some of the transport functionalit=
y
> into TCP.
>
> Gr=C3=BC=C3=9Fe, Carsten
>
>
>
> > On May 8, 2017, at 05:17, Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
> >
> > Hi, Yoshi,
> >
> > On Sat, Apr 29, 2017 at 11:24 PM, Yoshifumi Nishida <
> nishida@sfc.wide.ad.jp> wrote:
> > Hello,
> > As far as I've read -08 draft, I think this point has not been addresse=
d
> yet. I hope some folks could elaborate a bit more if they think this is n=
ot
> an important point for the draft.
> >
> > I've seen the subsequent e-mails in reply to yours, but it's not obviou=
s
> to me whether you think this point was addressed after reading those
> e-mails.
> >
> > What do you think?
> >
> > Thanks,
> >
> > Spencer
> >
> > --
> > Yoshi
> >
> > On Fri, Apr 21, 2017 at 2:57 PM, Brian Raymor <
> Brian.Raymor@microsoft.com> wrote:
> > I think that I understand your perceptions better. Prior to adoption of
> coap-tcp-tls and before I was active in the WG, I recall discussions
> related to the confusion over application vs transport reliability in CoA=
P
> especially as related to CON and NON. What was intended?
> >
> >
> >
> > Tim Carey outlined some concerns in:
> >
> > https://tools.ietf.org/html/draft-carey-core-std-msg-vs-
> trans-adapt-00#section-2
> >
> >
> >
> > This topic was presented in detail at IETF 93 - https://www.ietf.org/
> proceedings/93/slides/slides-93-core-0.pdf - starting on slide 23.
> >
> >
> >
> > And in a related thread on the mailing list back in 2015 -
> https://www.ietf.org/mail-archive/web/core/current/msg06280.html -
> Carsten responded:
> >
> >
> >
> > > In any case, CON and NON are about message layer semantics, not about
> application semantics
> >
> > > -- you gave them a meaning they don't have.
> >
> >
> >
> > By IETF 94, the authors were reporting =E2=80=93 =E2=80=9CMost of the C=
onfusion around
>             CON/NON was resolved=E2=80=9D.
> >
> >
> >
> > Where relevant, I=E2=80=99ve added clarifications - such as the Appendi=
x related
> to differences in Observe for reliable transports.
> >
> >
> >
> > Both Carsten and Hannes could probably offer more context if needed.
> >
> >
> >
> > From: Yoshifumi Nishida [mailto:nishida@sfc.wide.ad.jp]
> > Sent: Friday, April 21, 2017 2:08 PM
> > To: Brian Raymor <Brian.Raymor@microsoft.com>
> > Cc: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>; tsv-art@ietf.org;
> draft-ietf-core-coap-tcp-tls@ietf.org; core@ietf.org; ietf@ietf.org
> > Subject: Re: TSV-ART review of draft-ietf-core-coap-tcp-tls-07
> >
> >
> >
> > Hi Brian,
> >
> >
> >
> > Just in case,
> >
> > Reliable transports only provide reliability at transport level. It
> doesn't provide reliability in application protocol level.
> >
> >
> >
> > RFC7252 has reliability mechanisms in it since it uses UDP. This means
> it has abilities to check both transport and app level reliability.
> >
> > This draft only provides transport level reliability and apps will need
> to detect app protocol failure by themselves.
> >
> > This means 7252 and this draft are not totally equivalent from the
> viewpoint of applications.
> >
> >
> >
> > I am not saying this is wrong or bad, but I believe app developer shoul=
d
> aware this point.
> >
> > --
> >
> > Yoshi
> >
> >
> >
> > On Fri, Apr 21, 2017 at 11:15 AM, Brian Raymor <
> Brian.Raymor@microsoft.com> wrote:
> >
> > Hi Yoshi,
> >
> >
> >
> > > OK. I also think we should state that the protocol should notify the
> failure events to applications.
> >
> > > Since errors can happen not only in TCP, but also TLS and websocket
> level, mentioning only TCP close or reset might not
> >
> > > be enough.
> >
> >
> >
> > After reviewing with the authors, an additional clarification was
> appended to 3.4 Connection Health - https://github.com/core-wg/
> coap-tcp-tls/pull/140/files
> >
> >
> >
> > The opinion of the authors (and Gengyu WEI=E2=80=99s recent response -
> https://www.ietf.org/mail-archive/web/core/current/msg08622.html) is that
> RFC6455 covers the WebSocket case and does not need to be repeated here.
> >
> >
> >
> > > When we use 7252, I think applications basically don't need to
> implement timeouts or retry mechanisms as the protocol
> >
> > > provides such things.
> >
> >
> >
> > RFC7252 provides timeouts and retries because it's implementing a
> TCP-like reliability mechanism over UDP - https://tools.ietf.org/html/
> rfc7252#section-2.1
> >
> >
> >
> > > However, when we use this one, it seems applications will need to hav=
e
> such mechanisms. Isn't it a bit confusing? I am thinking that
> >
> > > there need to be some guidance here.
> >
> > > BTW, PONG is one example.
> >
> >
> >
> > For coap-tcp-tls, there are multiple early implementations. This has
> never been reported as a source of confusion.
> >
> >
> >
> > >> My sense is that we should treat this as an update to RFC7959 based
> on the original language:
> >
> > > I don't have a strong opinion here. Updating 7959 is fine for me if
> it's clearer to CoAP people.
> >
> >
> >
> > I've merged the change - https://github.com/core-wg/
> coap-tcp-tls/pull/138/files
> >
> >
> >
> > Thanks again for helping us to improve the quality of the draft,
> >
> >
> >
> > =E2=80=A6Brian
> >
> >
> >
> >
> >
> > _______________________________________________
> > Tsv-art mailing list
> > Tsv-art@ietf.org
> > https://www.ietf.org/mailman/listinfo/tsv-art
> >
> >
> > _______________________________________________
> > core mailing list
> > core@ietf.org
> > https://www.ietf.org/mailman/listinfo/core
>
> _______________________________________________
> Tsv-art mailing list
> Tsv-art@ietf.org
> https://www.ietf.org/mailman/listinfo/tsv-art
>

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

<div dir=3D"ltr">Hi Carsten,<div><br></div><div>Great. I will take a look a=
t it when it&#39;s published.</div><div>Thanks for the efforts!</div><div>-=
-</div><div>Yoshi<div><div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote">On Mon, May 8, 2017 at 12:31 AM, Carsten Bormann <span dir=3D"ltr">&lt=
;<a href=3D"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org</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">Hi Spencer,<br>
<br>
I=E2=80=99m not Yoshi :-), but I just have started working on an update of<=
br>
<a href=3D"https://lwig-wg.github.io/coap/#rfc.section.6" rel=3D"noreferrer=
" target=3D"_blank">https://lwig-wg.github.io/<wbr>coap/#rfc.section.6</a><=
br>
with some of the new information that relates to CoAP over reliable; I hope=
 that I will be able to push this during this week.<br>
<br>
Note that CoAP over TCP/TLS/WS does address application layer acknowledgeme=
nt beyond the request-response acknowledgement semantics by introducing the=
 custody option of the PING/PONG signaling messages.=C2=A0 This may be usef=
ul in compensating the decrease of information available to the CoAP applic=
ation as a result of moving some of the transport functionality into TCP.<b=
r>
<br>
Gr=C3=BC=C3=9Fe, Carsten<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
&gt; On May 8, 2017, at 05:17, Spencer Dawkins at IETF &lt;<a href=3D"mailt=
o:spencerdawkins.ietf@gmail.com">spencerdawkins.ietf@gmail.com</a><wbr>&gt;=
 wrote:<br>
&gt;<br>
&gt; Hi, Yoshi,<br>
&gt;<br>
&gt; On Sat, Apr 29, 2017 at 11:24 PM, Yoshifumi Nishida &lt;<a href=3D"mai=
lto:nishida@sfc.wide.ad.jp">nishida@sfc.wide.ad.jp</a>&gt; wrote:<br>
&gt; Hello,<br>
&gt; As far as I&#39;ve read -08 draft, I think this point has not been add=
ressed yet. I hope some folks could elaborate a bit more if they think this=
 is not an important point for the draft.<br>
&gt;<br>
&gt; I&#39;ve seen the subsequent e-mails in reply to yours, but it&#39;s n=
ot obvious to me whether you think this point was addressed after reading t=
hose e-mails.<br>
&gt;<br>
&gt; What do you think?<br>
&gt;<br>
&gt; Thanks,<br>
&gt;<br>
&gt; Spencer<br>
&gt;<br>
&gt; --<br>
&gt; Yoshi<br>
&gt;<br>
&gt; On Fri, Apr 21, 2017 at 2:57 PM, Brian Raymor &lt;<a href=3D"mailto:Br=
ian.Raymor@microsoft.com">Brian.Raymor@microsoft.com</a>&gt; wrote:<br>
&gt; I think that I understand your perceptions better. Prior to adoption o=
f coap-tcp-tls and before I was active in the WG, I recall discussions rela=
ted to the confusion over application vs transport reliability in CoAP espe=
cially as related to CON and NON. What was intended?<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Tim Carey outlined some concerns in:<br>
&gt;<br>
&gt; <a href=3D"https://tools.ietf.org/html/draft-carey-core-std-msg-vs-tra=
ns-adapt-00#section-2" rel=3D"noreferrer" target=3D"_blank">https://tools.i=
etf.org/html/<wbr>draft-carey-core-std-msg-vs-<wbr>trans-adapt-00#section-2=
</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; This topic was presented in detail at IETF 93 - <a href=3D"https://www=
.ietf.org/proceedings/93/slides/slides-93-core-0.pdf" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/<wbr>proceedings/93/slides/slides-<wbr=
>93-core-0.pdf</a> - starting on slide 23.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; And in a related thread on the mailing list back in 2015 - <a href=3D"=
https://www.ietf.org/mail-archive/web/core/current/msg06280.html" rel=3D"no=
referrer" target=3D"_blank">https://www.ietf.org/mail-<wbr>archive/web/core=
/current/<wbr>msg06280.html</a> - Carsten responded:<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; &gt; In any case, CON and NON are about message layer semantics, not a=
bout application semantics<br>
&gt;<br>
&gt; &gt; -- you gave them a meaning they don&#39;t have.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; By IETF 94, the authors were reporting =E2=80=93 =E2=80=9CMost of the =
Confusion around=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 CON/NON wa=
s resolved=E2=80=9D.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Where relevant, I=E2=80=99ve added clarifications - such as the Append=
ix related to differences in Observe for reliable transports.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Both Carsten and Hannes could probably offer more context if needed.<b=
r>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; From: Yoshifumi Nishida [mailto:<a href=3D"mailto:nishida@sfc.wide.ad.=
jp">nishida@sfc.wide.ad.jp</a><wbr>]<br>
&gt; Sent: Friday, April 21, 2017 2:08 PM<br>
&gt; To: Brian Raymor &lt;<a href=3D"mailto:Brian.Raymor@microsoft.com">Bri=
an.Raymor@microsoft.com</a>&gt;<br>
&gt; Cc: Yoshifumi Nishida &lt;<a href=3D"mailto:nishida@sfc.wide.ad.jp">ni=
shida@sfc.wide.ad.jp</a>&gt;; <a href=3D"mailto:tsv-art@ietf.org">tsv-art@i=
etf.org</a>; <a href=3D"mailto:draft-ietf-core-coap-tcp-tls@ietf.org">draft=
-ietf-core-coap-tcp-tls@<wbr>ietf.org</a>; <a href=3D"mailto:core@ietf.org"=
>core@ietf.org</a>; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
&gt; Subject: Re: TSV-ART review of draft-ietf-core-coap-tcp-tls-<wbr>07<br=
>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Hi Brian,<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Just in case,<br>
&gt;<br>
&gt; Reliable transports only provide reliability at transport level. It do=
esn&#39;t provide reliability in application protocol level.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; RFC7252 has reliability mechanisms in it since it uses UDP. This means=
 it has abilities to check both transport and app level reliability.<br>
&gt;<br>
&gt; This draft only provides transport level reliability and apps will nee=
d to detect app protocol failure by themselves.<br>
&gt;<br>
&gt; This means 7252 and this draft are not totally equivalent from the vie=
wpoint of applications.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; I am not saying this is wrong or bad, but I believe app developer shou=
ld aware this point.<br>
&gt;<br>
&gt; --<br>
&gt;<br>
&gt; Yoshi<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; On Fri, Apr 21, 2017 at 11:15 AM, Brian Raymor &lt;<a href=3D"mailto:B=
rian.Raymor@microsoft.com">Brian.Raymor@microsoft.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Yoshi,<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; &gt; OK. I also think we should state that the protocol should notify =
the failure events to applications.<br>
&gt;<br>
&gt; &gt; Since errors can happen not only in TCP, but also TLS and websock=
et level, mentioning only TCP close or reset might not<br>
&gt;<br>
&gt; &gt; be enough.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; After reviewing with the authors, an additional clarification was appe=
nded to 3.4 Connection Health - <a href=3D"https://github.com/core-wg/coap-=
tcp-tls/pull/140/files" rel=3D"noreferrer" target=3D"_blank">https://github=
.com/core-wg/<wbr>coap-tcp-tls/pull/140/files</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The opinion of the authors (and Gengyu WEI=E2=80=99s recent response -=
 <a href=3D"https://www.ietf.org/mail-archive/web/core/current/msg08622.htm=
l" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mail-<wbr>arch=
ive/web/core/current/<wbr>msg08622.html</a>) is that RFC6455 covers the Web=
Socket case and does not need to be repeated here.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; &gt; When we use 7252, I think applications basically don&#39;t need t=
o implement timeouts or retry mechanisms as the protocol<br>
&gt;<br>
&gt; &gt; provides such things.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; RFC7252 provides timeouts and retries because it&#39;s implementing a =
TCP-like reliability mechanism over UDP - <a href=3D"https://tools.ietf.org=
/html/rfc7252#section-2.1" rel=3D"noreferrer" target=3D"_blank">https://too=
ls.ietf.org/html/<wbr>rfc7252#section-2.1</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; &gt; However, when we use this one, it seems applications will need to=
 have such mechanisms. Isn&#39;t it a bit confusing? I am thinking that<br>
&gt;<br>
&gt; &gt; there need to be some guidance here.<br>
&gt;<br>
&gt; &gt; BTW, PONG is one example.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; For coap-tcp-tls, there are multiple early implementations. This has n=
ever been reported as a source of confusion.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; &gt;&gt; My sense is that we should treat this as an update to RFC7959=
 based on the original language:<br>
&gt;<br>
&gt; &gt; I don&#39;t have a strong opinion here. Updating 7959 is fine for=
 me if it&#39;s clearer to CoAP people.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; I&#39;ve merged the change - <a href=3D"https://github.com/core-wg/coa=
p-tcp-tls/pull/138/files" rel=3D"noreferrer" target=3D"_blank">https://gith=
ub.com/core-wg/<wbr>coap-tcp-tls/pull/138/files</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Thanks again for helping us to improve the quality of the draft,<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =E2=80=A6Brian<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; ______________________________<wbr>_________________<br>
&gt; Tsv-art mailing list<br>
&gt; <a href=3D"mailto:Tsv-art@ietf.org">Tsv-art@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/tsv-art" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/tsv-art=
</a><br>
&gt;<br>
&gt;<br>
</div></div><span class=3D"im HOEnZb">&gt; ______________________________<w=
br>_________________<br>
&gt; core mailing list<br>
&gt; <a href=3D"mailto:core@ietf.org">core@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/core" rel=3D"noreferr=
er" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/core</a><b=
r>
<br>
</span><div class=3D"HOEnZb"><div class=3D"h5">____________________________=
__<wbr>_________________<br>
Tsv-art mailing list<br>
<a href=3D"mailto:Tsv-art@ietf.org">Tsv-art@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tsv-art" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/tsv-art</a><=
br>
</div></div></blockquote></div><br></div></div></div></div>

--001a1141dfb043d382054efe7925--


From nobody Mon May  8 02:45:22 2017
Return-Path: <weigengyu@bupt.edu.cn>
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 9FA491292FD for <ietf@ietfa.amsl.com>; Mon,  8 May 2017 02:45:21 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, 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 stYQE1C-2Zdh for <ietf@ietfa.amsl.com>; Mon,  8 May 2017 02:45:20 -0700 (PDT)
Received: from mx1.bupt.edu.cn (mx1.bupt.edu.cn [211.68.68.2]) by ietfa.amsl.com (Postfix) with ESMTP id BC8C9126D73 for <ietf@ietf.org>; Mon,  8 May 2017 02:45:19 -0700 (PDT)
Received: from WeiGengyuPC (unknown [114.246.133.86]) by mx1.bupt.edu.cn (AnyMacro(G7)) with ESMTPA id CD78719F374; Mon,  8 May 2017 17:39:16 +0800 (HKT)
Message-ID: <8CB7E4B806F74B8294BA4441076E8EE0@WeiGengyuPC>
From: "weigengyu" <weigengyu@bupt.edu.cn>
To: "Yoshifumi Nishida" <nishida@sfc.wide.ad.jp>, "Carsten Bormann" <cabo@tzi.org>
Cc: <ietf@ietf.org>, "Yoshifumi Nishida" <nishida@sfc.wide.ad.jp>, <draft-ietf-core-coap-tcp-tls@ietf.org>, "Spencer Dawkins at IETF" <spencerdawkins.ietf@gmail.com>, <core@ietf.org>, <tsv-art@ietf.org>
References: <CAO249ye7KNdcbQfmOfik7QYFiXS9zcTE5n19pngHLgeur2XFpg@mail.gmail.com> <BY2PR21MB0084E781B2831EBC6A5F4E88831B0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydcc7k2i5=OSSvvtzU2B1Qa62b3RR3iY0wBfQ2pOYQrkQ@mail.gmail.com> <BY2PR21MB00849DB795086F08F6D7A98A831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249yeS8sZaJcADuz+bYAJa-CXs4v291Fm=adRouO1R=svPDw@mail.gmail.com> <BY2PR21MB008453149ADC1A998FEA56D3831A0@BY2PR21MB0084.namprd21.prod.outlook.com> <CAO249ydRLFpG=yHYvaZvPBiQuW5x=4HZqCZyTAb2HHeDuP+wAA@mail.gmail.com> <CAKKJt-em-dLP9qyhTOZ00x4oOGuXVLdbbNaVVKH3kLw=6JZ_dw@mail.gmail.com> <4F24893A-C088-45EB-97CE-126231933918@tzi.org> <CAO249ye9DoKihJQsiwYEmhRWRXe8WqqW49XOvMABu_-gnkficg@mail.gmail.com>
In-Reply-To: <CAO249ye9DoKihJQsiwYEmhRWRXe8WqqW49XOvMABu_-gnkficg@mail.gmail.com>
Subject: Re: [core] [Tsv-art] TSV-ART review of draft-ietf-core-coap-tcp-tls-07
Date: Mon, 8 May 2017 17:39:16 +0800
Organization: BUPT
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0031_01D2C822.03E94C30"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3528.331
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/E_h7yAQdd5xRQ1j5WVvETvJuL6Q>
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, 08 May 2017 09:45:21 -0000

ÕâÊÇһ·â MIME ¸ñʽµĶ෽Óʼþ¡£

------=_NextPart_000_0031_01D2C822.03E94C30
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,=20

The clairification raised is my question.=20

We did implement the protocol as the senarios described.
The problems were we met, not be thought out.=20

I wish there will be an answer.=20

Regards,=20

Gengyu WEI
Network Technology Center
School of Computer=20
Beijing University of Posts and Telecommunications

From: Yoshifumi Nishida=20
Sent: Monday, May 08, 2017 3:49 PM
To: Carsten Bormann=20
Cc: ietf@ietf.org ; Yoshifumi Nishida ; =
draft-ietf-core-coap-tcp-tls@ietf.org ; Spencer Dawkins at IETF ; =
core@ietf.org ; tsv-art@ietf.org=20
Subject: Re: [core] [Tsv-art] TSV-ART review of =
draft-ietf-core-coap-tcp-tls-07

Hi Carsten,=20

Great. I will take a look at it when it's published.
Thanks for the efforts!
--
Yoshi=20

On Mon, May 8, 2017 at 12:31 AM, Carsten Bormann <cabo@tzi.org> wrote:

  Hi Spencer,

  I=E2=80=99m not Yoshi :-), but I just have started working on an =
update of
  https://lwig-wg.github.io/coap/#rfc.section.6
  with some of the new information that relates to CoAP over reliable; I =
hope that I will be able to push this during this week.

  Note that CoAP over TCP/TLS/WS does address application layer =
acknowledgement beyond the request-response acknowledgement semantics by =
introducing the custody option of the PING/PONG signaling messages.  =
This may be useful in compensating the decrease of information available =
to the CoAP application as a result of moving some of the transport =
functionality into TCP.

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




  > On May 8, 2017, at 05:17, Spencer Dawkins at IETF =
<spencerdawkins.ietf@gmail.com> wrote:
  >
  > Hi, Yoshi,
  >
  > On Sat, Apr 29, 2017 at 11:24 PM, Yoshifumi Nishida =
<nishida@sfc.wide.ad.jp> wrote:
  > Hello,
  > As far as I've read -08 draft, I think this point has not been =
addressed yet. I hope some folks could elaborate a bit more if they =
think this is not an important point for the draft.
  >
  > I've seen the subsequent e-mails in reply to yours, but it's not =
obvious to me whether you think this point was addressed after reading =
those e-mails.
  >
  > What do you think?
  >
  > Thanks,
  >
  > Spencer
  >
  > --
  > Yoshi
  >
  > On Fri, Apr 21, 2017 at 2:57 PM, Brian Raymor =
<Brian.Raymor@microsoft.com> wrote:
  > I think that I understand your perceptions better. Prior to adoption =
of coap-tcp-tls and before I was active in the WG, I recall discussions =
related to the confusion over application vs transport reliability in =
CoAP especially as related to CON and NON. What was intended?
  >
  >
  >
  > Tim Carey outlined some concerns in:
  >
  > =
https://tools.ietf.org/html/draft-carey-core-std-msg-vs-trans-adapt-00#se=
ction-2
  >
  >
  >
  > This topic was presented in detail at IETF 93 - =
https://www.ietf.org/proceedings/93/slides/slides-93-core-0.pdf - =
starting on slide 23.
  >
  >
  >
  > And in a related thread on the mailing list back in 2015 - =
https://www.ietf.org/mail-archive/web/core/current/msg06280.html - =
Carsten responded:
  >
  >
  >
  > > In any case, CON and NON are about message layer semantics, not =
about application semantics
  >
  > > -- you gave them a meaning they don't have.
  >
  >
  >
  > By IETF 94, the authors were reporting =E2=80=93 =E2=80=9CMost of =
the Confusion around              CON/NON was resolved=E2=80=9D.
  >
  >
  >
  > Where relevant, I=E2=80=99ve added clarifications - such as the =
Appendix related to differences in Observe for reliable transports.
  >
  >
  >
  > Both Carsten and Hannes could probably offer more context if needed.
  >
  >
  >
  > From: Yoshifumi Nishida [mailto:nishida@sfc.wide.ad.jp]
  > Sent: Friday, April 21, 2017 2:08 PM
  > To: Brian Raymor <Brian.Raymor@microsoft.com>
  > Cc: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>; tsv-art@ietf.org; =
draft-ietf-core-coap-tcp-tls@ietf.org; core@ietf.org; ietf@ietf.org
  > Subject: Re: TSV-ART review of draft-ietf-core-coap-tcp-tls-07
  >
  >
  >
  > Hi Brian,
  >
  >
  >
  > Just in case,
  >
  > Reliable transports only provide reliability at transport level. It =
doesn't provide reliability in application protocol level.
  >
  >
  >
  > RFC7252 has reliability mechanisms in it since it uses UDP. This =
means it has abilities to check both transport and app level =
reliability.
  >
  > This draft only provides transport level reliability and apps will =
need to detect app protocol failure by themselves.
  >
  > This means 7252 and this draft are not totally equivalent from the =
viewpoint of applications.
  >
  >
  >
  > I am not saying this is wrong or bad, but I believe app developer =
should aware this point.
  >
  > --
  >
  > Yoshi
  >
  >
  >
  > On Fri, Apr 21, 2017 at 11:15 AM, Brian Raymor =
<Brian.Raymor@microsoft.com> wrote:
  >
  > Hi Yoshi,
  >
  >
  >
  > > OK. I also think we should state that the protocol should notify =
the failure events to applications.
  >
  > > Since errors can happen not only in TCP, but also TLS and =
websocket level, mentioning only TCP close or reset might not
  >
  > > be enough.
  >
  >
  >
  > After reviewing with the authors, an additional clarification was =
appended to 3.4 Connection Health - =
https://github.com/core-wg/coap-tcp-tls/pull/140/files
  >
  >
  >
  > The opinion of the authors (and Gengyu WEI=E2=80=99s recent response =
- https://www.ietf.org/mail-archive/web/core/current/msg08622.html) is =
that RFC6455 covers the WebSocket case and does not need to be repeated =
here.
  >
  >
  >
  > > When we use 7252, I think applications basically don't need to =
implement timeouts or retry mechanisms as the protocol
  >
  > > provides such things.
  >
  >
  >
  > RFC7252 provides timeouts and retries because it's implementing a =
TCP-like reliability mechanism over UDP - =
https://tools.ietf.org/html/rfc7252#section-2.1
  >
  >
  >
  > > However, when we use this one, it seems applications will need to =
have such mechanisms. Isn't it a bit confusing? I am thinking that
  >
  > > there need to be some guidance here.
  >
  > > BTW, PONG is one example.
  >
  >
  >
  > For coap-tcp-tls, there are multiple early implementations. This has =
never been reported as a source of confusion.
  >
  >
  >
  > >> My sense is that we should treat this as an update to RFC7959 =
based on the original language:
  >
  > > I don't have a strong opinion here. Updating 7959 is fine for me =
if it's clearer to CoAP people.
  >
  >
  >
  > I've merged the change - =
https://github.com/core-wg/coap-tcp-tls/pull/138/files
  >
  >
  >
  > Thanks again for helping us to improve the quality of the draft,
  >
  >
  >
  > =E2=80=A6Brian
  >
  >
  >
  >
  >
  > _______________________________________________
  > Tsv-art mailing list
  > Tsv-art@ietf.org
  > https://www.ietf.org/mailman/listinfo/tsv-art
  >
  >

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


  _______________________________________________
  Tsv-art mailing list
  Tsv-art@ietf.org
  https://www.ietf.org/mailman/listinfo/tsv-art




-------------------------------------------------------------------------=
-------
_______________________________________________
core mailing list
core@ietf.org
https://www.ietf.org/mailman/listinfo/core

------=_NextPart_000_0031_01D2C822.03E94C30
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD>
<BODY dir=3Dltr>
<DIV dir=3Dltr>
<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>Hi, </DIV>
<DIV>&nbsp;</DIV>
<DIV>The clairification raised is my question. </DIV>
<DIV>&nbsp;</DIV>
<DIV>We did implement the protocol as the senarios described.</DIV>
<DIV>The problems were we met, not be thought out. </DIV>
<DIV>&nbsp;</DIV>
<DIV>I wish there will be an answer. </DIV>
<DIV>&nbsp;</DIV>
<DIV>Regards, </DIV>
<DIV>&nbsp;</DIV>
<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: =
#000000">Gengyu=20
WEI<BR>Network Technology Center<BR>School of Computer <BR>Beijing =
University of=20
Posts and Telecommunications</DIV>
<DIV=20
style=3D'FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: =
"Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; =
DISPLAY: inline'>
<DIV style=3D"FONT: 10pt tahoma">
<DIV><FONT size=3D3 face=3DCalibri></FONT>&nbsp;</DIV>
<DIV style=3D"BACKGROUND: #f5f5f5">
<DIV style=3D"font-color: black"><B>From:</B> <A =
title=3Dnishida@sfc.wide.ad.jp=20
href=3D"mailto:nishida@sfc.wide.ad.jp">Yoshifumi Nishida</A> </DIV>
<DIV><B>Sent:</B> Monday, May 08, 2017 3:49 PM</DIV>
<DIV><B>To:</B> <A title=3Dcabo@tzi.org =
href=3D"mailto:cabo@tzi.org">Carsten=20
Bormann</A> </DIV>
<DIV><B>Cc:</B> <A title=3Dietf@ietf.org=20
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</A> ; <A =
title=3Dnishida@sfc.wide.ad.jp=20
href=3D"mailto:nishida@sfc.wide.ad.jp">Yoshifumi Nishida</A> ; <A=20
title=3Ddraft-ietf-core-coap-tcp-tls@ietf.org=20
href=3D"mailto:draft-ietf-core-coap-tcp-tls@ietf.org">draft-ietf-core-coa=
p-tcp-tls@ietf.org</A>=20
; <A title=3Dspencerdawkins.ietf@gmail.com=20
href=3D"mailto:spencerdawkins.ietf@gmail.com">Spencer Dawkins at =
IETF</A> ; <A=20
title=3Dcore@ietf.org href=3D"mailto:core@ietf.org">core@ietf.org</A> ; =
<A=20
title=3Dtsv-art@ietf.org =
href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.org</A>=20
</DIV>
<DIV><B>Subject:</B> Re: [core] [Tsv-art] TSV-ART review of=20
draft-ietf-core-coap-tcp-tls-07</DIV></DIV></DIV>
<DIV>&nbsp;</DIV></DIV>
<DIV=20
style=3D'FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: =
"Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; =
DISPLAY: inline'>
<DIV dir=3Dltr>Hi Carsten,=20
<DIV>&nbsp;</DIV>
<DIV>Great. I will take a look at it when it's published.</DIV>
<DIV>Thanks for the efforts!</DIV>
<DIV>--</DIV>
<DIV>Yoshi=20
<DIV>
<DIV class=3Dgmail_extra>
<DIV>&nbsp;</DIV>
<DIV class=3Dgmail_quote>On Mon, May 8, 2017 at 12:31 AM, Carsten =
Bormann <SPAN=20
dir=3Dltr>&lt;<A href=3D"mailto:cabo@tzi.org"=20
target=3D_blank>cabo@tzi.org</A>&gt;</SPAN> wrote:<BR>
<BLOCKQUOTE class=3Dgmail_quote=20
style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc =
1px solid">Hi=20
  Spencer,<BR><BR>I=E2=80=99m not Yoshi :-), but I just have started =
working on an=20
  update of<BR><A href=3D"https://lwig-wg.github.io/coap/#rfc.section.6" =

  rel=3Dnoreferrer=20
  =
target=3D_blank>https://lwig-wg.github.io/<WBR>coap/#rfc.section.6</A><BR=
>with=20
  some of the new information that relates to CoAP over reliable; I hope =
that I=20
  will be able to push this during this week.<BR><BR>Note that CoAP over =

  TCP/TLS/WS does address application layer acknowledgement beyond the=20
  request-response acknowledgement semantics by introducing the custody =
option=20
  of the PING/PONG signaling messages.&nbsp; This may be useful in =
compensating=20
  the decrease of information available to the CoAP application as a =
result of=20
  moving some of the transport functionality into =
TCP.<BR><BR>Gr=C3=BC=C3=9Fe, Carsten<BR>
  <DIV class=3DHOEnZb>
  <DIV class=3Dh5><BR><BR><BR>&gt; On May 8, 2017, at 05:17, Spencer =
Dawkins at=20
  IETF &lt;<A=20
  =
href=3D"mailto:spencerdawkins.ietf@gmail.com">spencerdawkins.ietf@gmail.c=
om</A><WBR>&gt;=20
  wrote:<BR>&gt;<BR>&gt; Hi, Yoshi,<BR>&gt;<BR>&gt; On Sat, Apr 29, 2017 =
at=20
  11:24 PM, Yoshifumi Nishida &lt;<A=20
  href=3D"mailto:nishida@sfc.wide.ad.jp">nishida@sfc.wide.ad.jp</A>&gt;=20
  wrote:<BR>&gt; Hello,<BR>&gt; As far as I've read -08 draft, I think =
this=20
  point has not been addressed yet. I hope some folks could elaborate a =
bit more=20
  if they think this is not an important point for the =
draft.<BR>&gt;<BR>&gt;=20
  I've seen the subsequent e-mails in reply to yours, but it's not =
obvious to me=20
  whether you think this point was addressed after reading those=20
  e-mails.<BR>&gt;<BR>&gt; What do you think?<BR>&gt;<BR>&gt;=20
  Thanks,<BR>&gt;<BR>&gt; Spencer<BR>&gt;<BR>&gt; --<BR>&gt;=20
  Yoshi<BR>&gt;<BR>&gt; On Fri, Apr 21, 2017 at 2:57 PM, Brian Raymor =
&lt;<A=20
  =
href=3D"mailto:Brian.Raymor@microsoft.com">Brian.Raymor@microsoft.com</A>=
&gt;=20
  wrote:<BR>&gt; I think that I understand your perceptions better. =
Prior to=20
  adoption of coap-tcp-tls and before I was active in the WG, I recall=20
  discussions related to the confusion over application vs transport =
reliability=20
  in CoAP especially as related to CON and NON. What was=20
  intended?<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; Tim Carey outlined some =
concerns=20
  in:<BR>&gt;<BR>&gt; <A=20
  =
href=3D"https://tools.ietf.org/html/draft-carey-core-std-msg-vs-trans-ada=
pt-00#section-2"=20
  rel=3Dnoreferrer=20
  =
target=3D_blank>https://tools.ietf.org/html/<WBR>draft-carey-core-std-msg=
-vs-<WBR>trans-adapt-00#section-2</A><BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;=20
  This topic was presented in detail at IETF 93 - <A=20
  =
href=3D"https://www.ietf.org/proceedings/93/slides/slides-93-core-0.pdf" =

  rel=3Dnoreferrer=20
  =
target=3D_blank>https://www.ietf.org/<WBR>proceedings/93/slides/slides-<W=
BR>93-core-0.pdf</A>=20
  - starting on slide 23.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; And in a =
related=20
  thread on the mailing list back in 2015 - <A=20
  =
href=3D"https://www.ietf.org/mail-archive/web/core/current/msg06280.html"=
=20
  rel=3Dnoreferrer=20
  =
target=3D_blank>https://www.ietf.org/mail-<WBR>archive/web/core/current/<=
WBR>msg06280.html</A>=20
  - Carsten responded:<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; &gt; In any case, =
CON and=20
  NON are about message layer semantics, not about application=20
  semantics<BR>&gt;<BR>&gt; &gt; -- you gave them a meaning they don't=20
  have.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; By IETF 94, the authors were =
reporting =E2=80=93=20
  =E2=80=9CMost of the Confusion=20
  =
around&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
  CON/NON was resolved=E2=80=9D.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; Where =
relevant, I=E2=80=99ve=20
  added clarifications - such as the Appendix related to differences in =
Observe=20
  for reliable transports.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; Both Carsten =
and=20
  Hannes could probably offer more context if=20
  needed.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; From: Yoshifumi Nishida =
[mailto:<A=20
  =
href=3D"mailto:nishida@sfc.wide.ad.jp">nishida@sfc.wide.ad.jp</A><WBR>]<B=
R>&gt;=20
  Sent: Friday, April 21, 2017 2:08 PM<BR>&gt; To: Brian Raymor &lt;<A=20
  =
href=3D"mailto:Brian.Raymor@microsoft.com">Brian.Raymor@microsoft.com</A>=
&gt;<BR>&gt;=20
  Cc: Yoshifumi Nishida &lt;<A=20
  href=3D"mailto:nishida@sfc.wide.ad.jp">nishida@sfc.wide.ad.jp</A>&gt;; =
<A=20
  href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.org</A>; <A=20
  =
href=3D"mailto:draft-ietf-core-coap-tcp-tls@ietf.org">draft-ietf-core-coa=
p-tcp-tls@<WBR>ietf.org</A>;=20
  <A href=3D"mailto:core@ietf.org">core@ietf.org</A>; <A=20
  href=3D"mailto:ietf@ietf.org">ietf@ietf.org</A><BR>&gt; Subject: Re: =
TSV-ART=20
  review of =
draft-ietf-core-coap-tcp-tls-<WBR>07<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;=20
  Hi Brian,<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; Just in =
case,<BR>&gt;<BR>&gt;=20
  Reliable transports only provide reliability at transport level. It =
doesn't=20
  provide reliability in application protocol=20
  level.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; RFC7252 has reliability =
mechanisms in=20
  it since it uses UDP. This means it has abilities to check both =
transport and=20
  app level reliability.<BR>&gt;<BR>&gt; This draft only provides =
transport=20
  level reliability and apps will need to detect app protocol failure by =

  themselves.<BR>&gt;<BR>&gt; This means 7252 and this draft are not =
totally=20
  equivalent from the viewpoint of =
applications.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;=20
  I am not saying this is wrong or bad, but I believe app developer =
should aware=20
  this point.<BR>&gt;<BR>&gt; --<BR>&gt;<BR>&gt;=20
  Yoshi<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; On Fri, Apr 21, 2017 at 11:15 =
AM, Brian=20
  Raymor &lt;<A=20
  =
href=3D"mailto:Brian.Raymor@microsoft.com">Brian.Raymor@microsoft.com</A>=
&gt;=20
  wrote:<BR>&gt;<BR>&gt; Hi Yoshi,<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; &gt; =
OK. I=20
  also think we should state that the protocol should notify the failure =
events=20
  to applications.<BR>&gt;<BR>&gt; &gt; Since errors can happen not only =
in TCP,=20
  but also TLS and websocket level, mentioning only TCP close or reset =
might=20
  not<BR>&gt;<BR>&gt; &gt; be enough.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; =
After=20
  reviewing with the authors, an additional clarification was appended =
to 3.4=20
  Connection Health - <A=20
  href=3D"https://github.com/core-wg/coap-tcp-tls/pull/140/files" =
rel=3Dnoreferrer=20
  =
target=3D_blank>https://github.com/core-wg/<WBR>coap-tcp-tls/pull/140/fil=
es</A><BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;=20
  The opinion of the authors (and Gengyu WEI=E2=80=99s recent response - =
<A=20
  =
href=3D"https://www.ietf.org/mail-archive/web/core/current/msg08622.html"=
=20
  rel=3Dnoreferrer=20
  =
target=3D_blank>https://www.ietf.org/mail-<WBR>archive/web/core/current/<=
WBR>msg08622.html</A>)=20
  is that RFC6455 covers the WebSocket case and does not need to be =
repeated=20
  here.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; &gt; When we use 7252, I think=20
  applications basically don't need to implement timeouts or retry =
mechanisms as=20
  the protocol<BR>&gt;<BR>&gt; &gt; provides such=20
  things.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; RFC7252 provides timeouts and =
retries=20
  because it's implementing a TCP-like reliability mechanism over UDP - =
<A=20
  href=3D"https://tools.ietf.org/html/rfc7252#section-2.1" =
rel=3Dnoreferrer=20
  =
target=3D_blank>https://tools.ietf.org/html/<WBR>rfc7252#section-2.1</A><=
BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;=20
  &gt; However, when we use this one, it seems applications will need to =
have=20
  such mechanisms. Isn't it a bit confusing? I am thinking =
that<BR>&gt;<BR>&gt;=20
  &gt; there need to be some guidance here.<BR>&gt;<BR>&gt; &gt; BTW, =
PONG is=20
  one example.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; For coap-tcp-tls, there =
are=20
  multiple early implementations. This has never been reported as a =
source of=20
  confusion.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; &gt;&gt; My sense is that =
we should=20
  treat this as an update to RFC7959 based on the original=20
  language:<BR>&gt;<BR>&gt; &gt; I don't have a strong opinion here. =
Updating=20
  7959 is fine for me if it's clearer to CoAP=20
  people.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; I've merged the change - <A=20
  href=3D"https://github.com/core-wg/coap-tcp-tls/pull/138/files" =
rel=3Dnoreferrer=20
  =
target=3D_blank>https://github.com/core-wg/<WBR>coap-tcp-tls/pull/138/fil=
es</A><BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;=20
  Thanks again for helping us to improve the quality of the=20
  draft,<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;=20
  =E2=80=A6Brian<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;=20
  ______________________________<WBR>_________________<BR>&gt; Tsv-art =
mailing=20
  list<BR>&gt; <A =
href=3D"mailto:Tsv-art@ietf.org">Tsv-art@ietf.org</A><BR>&gt; <A=20
  href=3D"https://www.ietf.org/mailman/listinfo/tsv-art" =
rel=3Dnoreferrer=20
  =
target=3D_blank>https://www.ietf.org/mailman/<WBR>listinfo/tsv-art</A><BR=
>&gt;<BR>&gt;<BR></DIV></DIV><SPAN=20
  class=3D"im HOEnZb">&gt;=20
  ______________________________<WBR>_________________<BR>&gt; core =
mailing=20
  list<BR>&gt; <A =
href=3D"mailto:core@ietf.org">core@ietf.org</A><BR>&gt; <A=20
  href=3D"https://www.ietf.org/mailman/listinfo/core" rel=3Dnoreferrer=20
  =
target=3D_blank>https://www.ietf.org/mailman/<WBR>listinfo/core</A><BR><B=
R></SPAN>
  <DIV class=3DHOEnZb>
  <DIV =
class=3Dh5>______________________________<WBR>_________________<BR>Tsv-ar=
t=20
  mailing list<BR><A =
href=3D"mailto:Tsv-art@ietf.org">Tsv-art@ietf.org</A><BR><A=20
  href=3D"https://www.ietf.org/mailman/listinfo/tsv-art" =
rel=3Dnoreferrer=20
  =
target=3D_blank>https://www.ietf.org/mailman/<WBR>listinfo/tsv-art</A><BR=
></DIV></DIV></BLOCKQUOTE></DIV>
<DIV>&nbsp;</DIV></DIV></DIV></DIV></DIV>
<P>
<HR>
_______________________________________________<BR>core mailing=20
list<BR>core@ietf.org<BR>https://www.ietf.org/mailman/listinfo/core<BR></=
DIV></DIV></DIV></BODY></HTML>

------=_NextPart_000_0031_01D2C822.03E94C30--


From nobody Mon May  8 03:16:20 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 AAAEF1292C5; Mon,  8 May 2017 03:16:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.6
X-Spam-Level: 
X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 OYLgCNoxX8YH; Mon,  8 May 2017 03:16:03 -0700 (PDT)
Received: from mail-wr0-x244.google.com (mail-wr0-x244.google.com [IPv6:2a00:1450:400c:c0c::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E6A4126FB3; Mon,  8 May 2017 03:16:03 -0700 (PDT)
Received: by mail-wr0-x244.google.com with SMTP id g12so7710991wrg.2; Mon, 08 May 2017 03:16:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=otNqVbd/gv619R2if1cwTHsQmKj5wW3dKdwjbrU36NI=; b=BtrP+lFrfAtLE1aW7ms1huOJ7iLQEUSg9AfrjOvx+3nPT05RA/F8VvPngnrSpYsSjs JhTaHklQZm1YNmBdWq5dJssZ9Aoz/QYfclkSKg/zMXqlj7drPZ3Ko0k4LN4u2RykFr0b R/rlHD81GvHi3at5m89s2roKN6dEXkESpFD/KFuLLwOfM9YprALep8c4IXnrhUV5uLHu sI4OQy6dUSxdo9+0wNosBLAitQ3FsPmvSQFCAteAoqev8lXCd9icdeTSq6dlaHpYGsTD 6nemctLd5AwcSxeO5IUe9ycLoCBujIyNufiYes5YQ2MdnqM/bTvqIj1tpUpKjtjoVPGZ 4jPQ==
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=otNqVbd/gv619R2if1cwTHsQmKj5wW3dKdwjbrU36NI=; b=NqAfu8ZiXMt3wdJec/L+/K2O3mg0CZdT1EG4Fe3/TREogCLTQcUc+LVxhcldgf8CuG /WhunyPRRNkumYpHzRPKsNr7mLQ7XKZWvtX1u6Rb0JfoA1uBrwD+bkZM/LPcUbhRvE4i LZr+1isB08TR6eGu4shcDjJUDploTOjyHD+i8nTB/agVspJnQ+8oQ7AWtenMzapmtge+ jFkQP1uwLxgYh3zJESJPbkH8L5moy0g0FJHbKsE/R0bDXkUlV3vbaay6w6uNJHnyNeHl 7boSp3C9Ym+bN++ifgm9tScgQzs0vV2+tb6xFunZlUBl/gMvPWFvv2d9cwobOwqpYwmY 62Jg==
X-Gm-Message-State: AN3rC/4XtdzP3z/DqH8+tA8IqXlYBTUQ2bTbiPCEVHHtGhRW5eq96oY1 1H1nhhXbF97s3XCMnFz8Iw==
X-Received: by 10.223.147.97 with SMTP id 88mr36914030wro.134.1494238561473; Mon, 08 May 2017 03:16:01 -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 j133sm9679706wmg.26.2017.05.08.03.16.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 May 2017 03:16:01 -0700 (PDT)
Subject: Re: [spring] Genart last call review of draft-ietf-spring-ipv6-use-cases-10
To: Robert Raszuk <robert@raszuk.net>, stefano previdi <sprevidi@cisco.com>
References: <149374426742.21414.16408814015665498739@ietfa.amsl.com> <3E209B45-90CE-4EEB-9D2B-E14EFE28DCE0@cisco.com> <87a1534f-079d-3707-9f5d-9327e831bf7a@gmail.com> <B91C6D2C-897A-404C-80B3-EAA8BDEC4414@cisco.com> <CA+b+ERnsEn3JBpb8b7Jwcm32K=-iGA3GOPokWwnaXqSpDW89Vg@mail.gmail.com>
Cc: IETF Discussion <ietf@ietf.org>, "Alvaro Retana (aretana)" <aretana@cisco.com>, "draft-ietf-spring-ipv6-use-cases.all@ietf.org" <draft-ietf-spring-ipv6-use-cases.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "spring@ietf.org" <spring@ietf.org>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <28cabccc-5426-9938-e2bf-169de0959ddc@gmail.com>
Date: Mon, 8 May 2017 11:15:46 +0100
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: <CA+b+ERnsEn3JBpb8b7Jwcm32K=-iGA3GOPokWwnaXqSpDW89Vg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MJziiWBMMqICtkKM0xDHzSTB0ks>
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, 08 May 2017 10:16:05 -0000

On 05/05/2017 11:17, Robert Raszuk wrote:
> And to add one observation ..
>
> Stewart makes a point that SR-MPLS can be deployed without mpls 
> control plane.
>
> Well it sure does not require LDP however IGP or BGP extensions for 
> SR-MPLS signalling is also an example of mpls control plane ... even 
> if much simpler than traditional cases it is still required.

Yes, but those are required anyway to support SRv6. You always have to 
provide the mapping between the function, the function identifier and 
the function location.

- Stewart


From nobody Mon May  8 05:13:02 2017
Return-Path: <rraszuk@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 27CD4127137; Mon,  8 May 2017 05:12:54 -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 V24cOp6NsUMB; Mon,  8 May 2017 05:12:52 -0700 (PDT)
Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::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 C657C127077; Mon,  8 May 2017 05:12:52 -0700 (PDT)
Received: by mail-it0-x230.google.com with SMTP id o5so64701747ith.1; Mon, 08 May 2017 05:12:52 -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=DEw0636DT+LHPwPQHoTyJb79xvdPPhvrhz0Bmz2nhhU=; b=sdtOPGIvBh04o72AAUPSDCVN0d6TJoMJ6dBHQ1q5x6bs04Cc4DzOyqpKuf+ss9AcYM dm/a4WM5Nm/24CGeS3sZJIVMdPo/D5/kt1jge690jqEeBAO9KSz+U3VoY6L/jA2AgJT5 thDtybgcA0ymwE40kGpZPstxKPzE9xralysiRPZM1gEJ/0UnPvLgF9OmbgfegNR2vrbN PqGBKIAX8VBqe/Qmf5dLGuSNSBzotZXSTFi+u5zI5JHmziIHe0OILFfqp8/Fqw54tNV1 UV9ix+HeLaUel4Dyw39z/YAOeaIVsfYvlUtHRDk/4oaJobOyZbZj8y2nOmFgFJEj+0rN s6dQ==
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=DEw0636DT+LHPwPQHoTyJb79xvdPPhvrhz0Bmz2nhhU=; b=ggYXpVIDTmal8i+ccJoDWM0Vg/RGv1bRMmuGmnFSi6x7HOJm5eWkKkpKs+jNA9rQYv mmLt989iIkhru7vYylzzalPtM/ni8CC7X2naAQh0Qn/pRZHh19JAE2xcYoMThDxdDkG8 l/egt1Bxg7Jls7Bhd6UtjlOhaEiYpVZM2b/+N4LwJiL3Dbw++VOPayjlrInT2iKHe1r5 ucz92i3Jhh6/MgVYtKBDE2iKvaMVMgmTlGfqO4PycKiUMNkToHNOF87JmEvF1bi6G3VW 7DPSMjfchUBLDFq/oosUTy9TzK/1YgFpMpdlp69Sm9790kJoZwd484PpZbs2VoDMPZRE ZEWQ==
X-Gm-Message-State: AN3rC/4p6DcHNVO2NPlY621KeZi5P7TJE7zJGn3Cit0SvQK2c6rdmISi OLl2Wqx4zzmisKthBLMB+HPAN083Qw==
X-Received: by 10.36.125.197 with SMTP id b188mr19525052itc.59.1494245572101;  Mon, 08 May 2017 05:12:52 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.79.62.24 with HTTP; Mon, 8 May 2017 05:12:51 -0700 (PDT)
In-Reply-To: <28cabccc-5426-9938-e2bf-169de0959ddc@gmail.com>
References: <149374426742.21414.16408814015665498739@ietfa.amsl.com> <3E209B45-90CE-4EEB-9D2B-E14EFE28DCE0@cisco.com> <87a1534f-079d-3707-9f5d-9327e831bf7a@gmail.com> <B91C6D2C-897A-404C-80B3-EAA8BDEC4414@cisco.com> <CA+b+ERnsEn3JBpb8b7Jwcm32K=-iGA3GOPokWwnaXqSpDW89Vg@mail.gmail.com> <28cabccc-5426-9938-e2bf-169de0959ddc@gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 8 May 2017 14:12:51 +0200
X-Google-Sender-Auth: MHaCcDzodrmDLFJVGoCU5lXV5o8
Message-ID: <CA+b+ERkzBo2YZPfi-GBp_JdPLsDDOSqwtSmYR0Cjj1kXJhKH4A@mail.gmail.com>
Subject: Re: [spring] Genart last call review of draft-ietf-spring-ipv6-use-cases-10
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: stefano previdi <sprevidi@cisco.com>, IETF Discussion <ietf@ietf.org>,  "Alvaro Retana (aretana)" <aretana@cisco.com>,  "draft-ietf-spring-ipv6-use-cases.all@ietf.org" <draft-ietf-spring-ipv6-use-cases.all@ietf.org>,  "gen-art@ietf.org" <gen-art@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Content-Type: multipart/alternative; boundary=001a114043b0884fbe054f0228a8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1h7RcZBZk0bj5cfAk9z25k4jQfU>
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, 08 May 2017 12:12:54 -0000

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

Hi Stewart,

> =E2=80=8B
Yes, but those are required anyway to support SRv6

That is incorrect.

Please watch Les's presentation during last IETF where he clearly and
correctly stated that IGP extensions for SRv6 are optional and not required
(unlike in the case of SR-MPLS where such signalling of global labels is
indeed necessary to build "global labels" based forwarding).

As a matter of fact I knew this will generate confusion in IETF and
recommended to make it very clear in the drafts. Distribution of SID
functions does not need to be carried in routing protocols. And SRv6 SID
locator function is native to IPv6 routing hence no extensions needed. Sure
they can be carried in IGPs or BGP but this is just an option not
necessity.

Best,
Robert.



On Mon, May 8, 2017 at 12:15 PM, Stewart Bryant <stewart.bryant@gmail.com>
wrote:

>
>
> On 05/05/2017 11:17, Robert Raszuk wrote:
>
>> And to add one observation ..
>>
>> Stewart makes a point that SR-MPLS can be deployed without mpls control
>> plane.
>>
>> Well it sure does not require LDP however IGP or BGP extensions for
>> SR-MPLS signalling is also an example of mpls control plane ... even if
>> much simpler than traditional cases it is still required.
>>
>
> =E2=80=8B=E2=80=8B
> Yes, but those are required anyway to support SRv6. You always have to
> provide the mapping between the function, the function identifier and the
> function location.
>
> - Stewart
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small"><div class=3D"gmail_default" style=3D"d=
isplay:inline"><br></div></div><div class=3D"gmail_default" style=3D"font-f=
amily:arial,helvetica,sans-serif;font-size:small"><div class=3D"gmail_defau=
lt" style=3D"display:inline">Hi Stewart,</div></div><div class=3D"gmail_def=
ault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><div=
 class=3D"gmail_default" style=3D"display:inline"><br></div></div><div clas=
s=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-si=
ze:small"><div class=3D"gmail_default" style=3D"display:inline">&gt; =E2=80=
=8B</div><span style=3D"font-family:arial,sans-serif">Yes, but those are re=
quired anyway to support SRv6</span><br></div><div class=3D"gmail_default" =
style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><span styl=
e=3D"font-family:arial,sans-serif"><br></span></div><div class=3D"gmail_def=
ault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><spa=
n style=3D"font-family:arial,sans-serif">That is incorrect.=C2=A0</span></d=
iv><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-s=
erif;font-size:small"><span style=3D"font-family:arial,sans-serif"><br></sp=
an></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,=
sans-serif;font-size:small"><span style=3D"font-family:arial,sans-serif">Pl=
ease watch Les&#39;s presentation during last IETF where he clearly and cor=
rectly stated that IGP extensions for SRv6 are optional and not required (u=
nlike in the case of SR-MPLS where such signalling of global labels is inde=
ed necessary to build &quot;global labels&quot; based forwarding).=C2=A0</s=
pan></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica=
,sans-serif;font-size:small"><span style=3D"font-family:arial,sans-serif"><=
br></span></div><div class=3D"gmail_default" style=3D"font-family:arial,hel=
vetica,sans-serif;font-size:small"><span style=3D"font-family:arial,sans-se=
rif">As a matter of fact I knew this will generate confusion in IETF and re=
commended to make it very clear in the drafts. Distribution of SID function=
s does not need to be carried in routing protocols. And SRv6 SID locator fu=
nction is native to IPv6 routing hence no extensions needed. Sure they can =
be carried in IGPs or BGP but this is just an option not necessity.=C2=A0</=
span></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetic=
a,sans-serif;font-size:small"><span style=3D"font-family:arial,sans-serif">=
<br></span></div><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small"><span style=3D"font-family:arial,sans-s=
erif">Best,</span></div><div class=3D"gmail_default" style=3D"font-family:a=
rial,helvetica,sans-serif;font-size:small"><span style=3D"font-family:arial=
,sans-serif">Robert.</span></div><div class=3D"gmail_default" style=3D"font=
-family:arial,helvetica,sans-serif;font-size:small"><span style=3D"font-fam=
ily:arial,sans-serif"><br></span></div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif;font-size:small"><span style=3D"=
font-family:arial,sans-serif"><br></span></div><div class=3D"gmail_extra"><=
br><div class=3D"gmail_quote">On Mon, May 8, 2017 at 12:15 PM, 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:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex"><span class=3D"gmail-"><br>
<br>
On 05/05/2017 11:17, Robert Raszuk 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">
And to add one observation ..<br>
<br>
Stewart makes a point that SR-MPLS can be deployed without mpls control pla=
ne.<br>
<br>
Well it sure does not require LDP however IGP or BGP extensions for SR-MPLS=
 signalling is also an example of mpls control plane ... even if much simpl=
er than traditional cases it is still required.<br>
</blockquote>
<br></span>
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small;display:inline">=E2=80=8B=E2=80=8B</div>Yes, but those ar=
e required anyway to support SRv6. You always have to provide the mapping b=
etween the function, the function identifier and the function location.<spa=
n class=3D"gmail-HOEnZb"><font color=3D"#888888"><br>
<br>
- Stewart<br>
<br>
</font></span></blockquote></div><br></div></div>

--001a114043b0884fbe054f0228a8--


From nobody Mon May  8 05:15:54 2017
Return-Path: <ietf@kuehlewind.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 0FA5112944B for <ietf@ietfa.amsl.com>; Mon,  8 May 2017 05:15:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.697
X-Spam-Level: 
X-Spam-Status: No, score=0.697 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.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 8A53WPophWNG for <ietf@ietfa.amsl.com>; Mon,  8 May 2017 05:15:44 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FA9A127077 for <ietf@ietf.org>; Mon,  8 May 2017 05:15:44 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=RKl6njQoSRDn94HGwRDt9x9rkW0Gl7pDYxqaNwCwS8uUoMU6NTc/dnI8mdTjP2qZv8FTcXajbltqWXRYsHcbvqBYlRJ3vWNAE5a34fPVdfSONaER4JxBJP3akFBsobkUzdbg24LUaCXivuXZmlmpk/ZQZ6itwJUKlgnRi3H57LE=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 29726 invoked from network); 8 May 2017 14:15:42 +0200
Received: from p5dec259c.dip0.t-ipconnect.de (HELO ?192.168.178.33?) (93.236.37.156) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 8 May 2017 14:15:42 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Artart telechat review of draft-ietf-alto-multi-cost-08
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <HE1PR0701MB2459B2173C921635A61CC24695100@HE1PR0701MB2459.eurprd07.prod.outlook.com>
Date: Mon, 8 May 2017 14:15:40 +0200
Cc: "art@ietf.org" <art@ietf.org>, "alto@ietf.org" <alto@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-alto-multi-cost.all@ietf.org" <draft-ietf-alto-multi-cost.all@ietf.org>, "Randriamasy, Sabine (Nokia - FR/Nozay)" <sabine.randriamasy@nokia-bell-labs.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A376548-9BB0-4D7B-81C6-1BD951227FEA@kuehlewind.net>
References: <149144445494.22036.11923880719369865745@ietfa.amsl.com> <DB6PR0701MB24543D95D78557DDEACA2D71951E0@DB6PR0701MB2454.eurprd07.prod.outlook.com> <CABkgnnWAn9r4ZGtVq6yLyYcC7w5rDy4dV+98q0K__Nnm2UfRew@mail.gmail.com> <HE1PR0701MB2459B2173C921635A61CC24695100@HE1PR0701MB2459.eurprd07.prod.outlook.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.3273)
X-PPP-Message-ID: <20170508121542.29717.60305@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gikkHc4rhU3rWvjLaMLYxwdRTdg>
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, 08 May 2017 12:15:47 -0000

Hi Martin,

just to double check: do you think this document is ready now and all =
your comments have been addressed?

Mirja


> Am 27.04.2017 um 13:57 schrieb Randriamasy, Sabine (Nokia - FR/Nozay) =
<sabine.randriamasy@nokia-bell-labs.com>:
>=20
> Hello Martin,
>=20
> I just posted an update where the " Requirements Language" text has =
been moved in a section 1.1.
> As I saw it on a number of other ietf drafts, I also added the =
sentence=20
> "When the words appear in lower case, their natural language meaning =
is used."
>=20
> The update and status are available at =
https://datatracker.ietf.org/doc/draft-ietf-alto-multi-cost/
>=20
> Thanks,
> Sabine
>=20
>=20
>>> -----Original Message-----
>>> From: Martin Thomson [mailto:martin.thomson@gmail.com]
>>> Sent: 26 April 2017 08:39
>>> To: Randriamasy, Sabine (Nokia - FR/Nozay) =
<sabine.randriamasy@nokia-
>>> bell-labs.com>
>>> Cc: art@ietf.org; alto@ietf.org; ietf@ietf.org; =
draft-ietf-alto-multi-
>>> cost.all@ietf.org
>>> Subject: Re: Artart telechat review of draft-ietf-alto-multi-cost-08
>>>=20
>>> On 26 April 2017 at 03:26, Randriamasy, Sabine (Nokia - FR/Nozay)
>>> <sabine.randriamasy@nokia-bell-labs.com> wrote:
>>>>>> This document doesn't cite RFC 2119, but it uses the keywords.
>>>> [SR     ] RFC 2119 is cited on page 1, section " Requirements =
Language" and
>>> section "9.1.  Normative References". Should it be referenced =
elsewhere?
>>>=20
>>> The convention is to put those in the body, I missed it in the =
boilerplate.
>>>=20
>>> I skimmed the other changes, and they look fine.


From nobody Mon May  8 09:42:42 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 C3003127419; Mon,  8 May 2017 09:42:34 -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: grow@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, ietf@ietf.org
Subject: Genart telechat review of draft-ietf-grow-large-communities-usage-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149426175471.26213.8623473991144702688@ietfa.amsl.com>
Date: Mon, 08 May 2017 09:42:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AC3Vno3um4tngdkshrKFN8P2kuY>
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, 08 May 2017 16:42:35 -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 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-grow-large-communities-usage-??
Reviewer: Stewart Bryant
Review Date: 2017-05-08
IETF LC End Date: 2017-04-21
IESG Telechat date: 2017-05-11

Summary: This is now ready for publication.

Major issues: None.

Minor issues: None.

Nits/editorial comments: None.



From nobody Mon May  8 09:48:49 2017
Return-Path: <job@ntt.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 44A11126DFF for <ietf@ietfa.amsl.com>; Mon,  8 May 2017 09:48:35 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, 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 4wlOycpO0p6r for <ietf@ietfa.amsl.com>; Mon,  8 May 2017 09:48:34 -0700 (PDT)
Received: from mail3.dllstx09.us.to.gin.ntt.net (mail3.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::26]) (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 496A5126C23 for <ietf@ietf.org>; Mon,  8 May 2017 09:48:34 -0700 (PDT)
Received: by mail3.dllstx09.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <job@ntt.net>) id 1d7lpn-0001pr-DL (job@us.ntt.net) for ietf@ietf.org; Mon, 08 May 2017 16:48:33 +0000
Received: by mail-wm0-f54.google.com with SMTP id m123so71313741wma.0 for <ietf@ietf.org>; Mon, 08 May 2017 09:48:31 -0700 (PDT)
X-Gm-Message-State: AN3rC/5CgEiUs76C+TVMoaaFfYWAi3USvwkNp1HlMeZZaRSxgnA5m95e vB2FnDIku75r4hrAkDSlpmxEdQ2BfA==
X-Received: by 10.28.185.211 with SMTP id j202mr12473309wmf.65.1494262110113;  Mon, 08 May 2017 09:48:30 -0700 (PDT)
MIME-Version: 1.0
References: <149426175471.26213.8623473991144702688@ietfa.amsl.com>
In-Reply-To: <149426175471.26213.8623473991144702688@ietfa.amsl.com>
From: Job Snijders <job@ntt.net>
Date: Mon, 08 May 2017 16:48:19 +0000
X-Gmail-Original-Message-ID: <CACWOCC92=s26xXj4m2_BpTRk39ykZumpLmKjbGYrM=154mTD=Q@mail.gmail.com>
Message-ID: <CACWOCC92=s26xXj4m2_BpTRk39ykZumpLmKjbGYrM=154mTD=Q@mail.gmail.com>
Subject: Re: Genart telechat review of draft-ietf-grow-large-communities-usage-07
To: Stewart Bryant <stewart.bryant@gmail.com>, gen-art@ietf.org
Cc: draft-ietf-grow-large-communities-usage.all@ietf.org, grow@ietf.org,  ietf@ietf.org
Content-Type: multipart/alternative; boundary=001a1148db1c46892b054f0602c8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9O4Fgjge_t0zxKCmwf6goEOV67w>
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, 08 May 2017 16:48:35 -0000

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

Thanks Stewart!

On Mon, 8 May 2017 at 18:42, Stewart Bryant <stewart.bryant@gmail.com>
wrote:

> 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 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-grow-large-communities-usage-??
> Reviewer: Stewart Bryant
> Review Date: 2017-05-08
> IETF LC End Date: 2017-04-21
> IESG Telechat date: 2017-05-11
>
> Summary: This is now ready for publication.
>
> Major issues: None.
>
> Minor issues: None.
>
> Nits/editorial comments: None.
>
>
>

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

<div>Thanks Stewart!</div><div><br><div class=3D"gmail_quote"><div>On Mon, =
8 May 2017 at 18:42, Stewart Bryant &lt;<a href=3D"mailto:stewart.bryant@gm=
ail.com">stewart.bryant@gmail.com</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">Reviewer: Stewart Bryant<br>
Review result: 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. Please wait for direction from your<br>
document shepherd or AD before posting a new version of the draft.<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/gen/wiki/GenArtfaq</a>&g=
t;.<br>
<br>
Document: draft-ietf-grow-large-communities-usage-??<br>
Reviewer: Stewart Bryant<br>
Review Date: 2017-05-08<br>
IETF LC End Date: 2017-04-21<br>
IESG Telechat date: 2017-05-11<br>
<br>
Summary: This is now ready for publication.<br>
<br>
Major issues: None.<br>
<br>
Minor issues: None.<br>
<br>
Nits/editorial comments: None.<br>
<br>
<br>
</blockquote></div></div>

--001a1148db1c46892b054f0602c8--


From nobody Mon May  8 09:54:03 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 C9B0A129508 for <ietf@ietfa.amsl.com>; Mon,  8 May 2017 09:54:01 -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, 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=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 OaEEbHRK5YPW for <ietf@ietfa.amsl.com>; Mon,  8 May 2017 09:54: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 47F16126C23 for <ietf@ietf.org>; Mon,  8 May 2017 09:54:00 -0700 (PDT)
Received: by mail-ua0-x231.google.com with SMTP id e55so46517761uaa.2 for <ietf@ietf.org>; Mon, 08 May 2017 09:54:00 -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=AIrQrqsn2/dbgUUBI49F6B+V8sfe4XLA1h3TxFVZ1qY=; b=1IOgaKbRog2WotRYwqmT/3UCiKNnoEsqlpvmt9usxjLVWrbnp5Uft1+uxBjJjKxEYm TjAN6GmEMtLQ++4KaRJ2792kOcsrvUMoyrI9Bur3kYbqyWXxMVabn/2AthTBoRu8CqZG +DyfSCD9QQ53tjtSXcsQVMmfpK3+o/KaDJkhoCRPP7EBXvB8TV27jT83Caz3Ky9m60O7 NgVHeHcgd63yFPg8wYNRj7buTI4Y0jZjTeT90Zp5dQcI99IcKKHD4AzjQ/aIy3CSJxVp Jog17D3X9W6I2UND3ZdfVUs4XoqH3hRfv7o1Lit3DZ4UPOol7gbjjXjZsfiIAGOWVYFc 1cBg==
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=AIrQrqsn2/dbgUUBI49F6B+V8sfe4XLA1h3TxFVZ1qY=; b=UQlAozX3g+ctern+qiNCGvN4wM/4RPzwOtFzemq54XKkoBfEJRw5v/13Thbr8/D2hp o5gTkgve6RB/jYR7GwbPSTiRr/PNXxteONxmCiZr0fe5Ryj9RZSxRVGhL5Ef6S5ew68o yusnD81ng+lpZz2LYpsGrQUyIvZBhHq0+MzQd6J4gTzlLtFQDb0q17O7bA7WvBQXWCgm j+rMjO5Lcs1bLHC9Rb6kWiowbNeZd3Knwc/PzfbL70TRsqbBBWk5VcOTa3xqtwWPpMn5 Rqa/EK7UffbB5v4OY6NaG8SdNRzCOCy1+2Z56VLEVjFT8Kq1APfnI5sC18VKekOpJw7f G07w==
X-Gm-Message-State: AN3rC/590xAeDrcISegMVG4tDB8W9MeZZRByqtiXo2wuFDn1PzpxitaS nDUPzy35fbM5EkBKAYypVRxDO2WDvI9V
X-Received: by 10.176.23.227 with SMTP id p35mr21569844uaf.155.1494262439302;  Mon, 08 May 2017 09:53:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.71.83 with HTTP; Mon, 8 May 2017 09:53:18 -0700 (PDT)
In-Reply-To: <CACWOCC92=s26xXj4m2_BpTRk39ykZumpLmKjbGYrM=154mTD=Q@mail.gmail.com>
References: <149426175471.26213.8623473991144702688@ietfa.amsl.com> <CACWOCC92=s26xXj4m2_BpTRk39ykZumpLmKjbGYrM=154mTD=Q@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
Date: Mon, 8 May 2017 12:53:18 -0400
Message-ID: <CAHw9_iKrTnh6EPvxRx-kZkrTz_8hrh3Fj_dOis1t-Z3OqR+y2Q@mail.gmail.com>
Subject: Re: Genart telechat review of draft-ietf-grow-large-communities-usage-07
To: Job Snijders <job@ntt.net>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, General Area Review Team <gen-art@ietf.org>,  draft-ietf-grow-large-communities-usage.all@ietf.org,  "grow@ietf.org" <grow@ietf.org>, "ietf@ietf.org Discuss" <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BHcxnwH9L2yaUr6N1-JNkvYyHQo>
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, 08 May 2017 16:54:02 -0000

On Mon, May 8, 2017 at 12:48 PM, Job Snijders <job@ntt.net> wrote:
> Thanks Stewart!

Yes, indeed. Thank you Stewart - Directorate reviews are always appreciated.

W

>
> On Mon, 8 May 2017 at 18:42, Stewart Bryant <stewart.bryant@gmail.com>
> wrote:
>>
>> 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 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-grow-large-communities-usage-??
>> Reviewer: Stewart Bryant
>> Review Date: 2017-05-08
>> IETF LC End Date: 2017-04-21
>> IESG Telechat date: 2017-05-11
>>
>> Summary: This is now ready for publication.
>>
>> Major issues: None.
>>
>> Minor issues: None.
>>
>> Nits/editorial comments: None.
>>
>>
>



-- 
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 May  8 12:13:45 2017
Return-Path: <jheitz@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 925C0129649; Mon,  8 May 2017 12:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 i55sqf4HX5Vd; Mon,  8 May 2017 12:13:42 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9F2A124D37; Mon,  8 May 2017 12:13:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3004; q=dns/txt; s=iport; t=1494270821; x=1495480421; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=wukmENlBzFNd+y7ItLBkWrEfBo13BiixpOu4wRuuwgo=; b=aORqdZWKQHC3y3jFJ1IpyH1F23EO0OBCYFVI2yHhwhzlFWNPpCiJUjr7 PfcORmzI0n3I3pVy59z/HJPjVSDaRdPwIYmyW7XhvptZr4UFgO/TTnaq1 xziP8gP8PltmqNefroOumSVsT9TXhpLPXUc8Yovp8E4ZuFhgOn8lh7dq0 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DNAACCwhBZ/4QNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1VigQwHjXmRV5Vygg8hC4V4AoRlPxgBAgEBAQEBAQFrKIUVAQE?= =?us-ascii?q?BAQMBATg0CwwEAgEIEQQBAQEeBQsnCx0IAgQBDQUIihgOtX+KdQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBARgFhl+BXoMbikwFnXkBhxuLc4INhTyKLJQ9AR84gQpwFUZ?= =?us-ascii?q?AhGmBSnaHXgGBDAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.38,310,1491264000"; d="scan'208";a="245740763"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 May 2017 19:13:40 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v48JDeuZ013631 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 8 May 2017 19:13:40 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 8 May 2017 14:13:39 -0500
Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1210.000; Mon, 8 May 2017 14:13:39 -0500
From: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
To: "Enke Chen (enkechen)" <enkechen@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
CC: "draft-ietf-idr-shutdown@ietf.org" <draft-ietf-idr-shutdown@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>
Subject: RE: [Idr] Last Call: <draft-ietf-idr-shutdown-08.txt> (BGP Administrative Shutdown Communication) to Proposed Standard
Thread-Topic: [Idr] Last Call: <draft-ietf-idr-shutdown-08.txt> (BGP Administrative Shutdown Communication) to Proposed Standard
Thread-Index: AQHSxciggI3I1x2tSEiYPH6G0J5TkKHqIuMAgACuc/A=
Date: Mon, 8 May 2017 19:13:39 +0000
Message-ID: <a9996bc76e604acfbe797389ed0d81f6@XCH-ALN-014.cisco.com>
References: <149400686065.8457.16928207738917615877.idtracker@ietfa.amsl.com> <9d8cf31a-fc21-096b-543e-58750894a22a@cisco.com>
In-Reply-To: <9d8cf31a-fc21-096b-543e-58750894a22a@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [128.107.151.51]
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/fDeHjMXvyOf80Gd2rlnutSb7BWI>
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, 08 May 2017 19:13:43 -0000

It is deliberately kept short to minimize the potential for abuse.
We could have argued about the length. Should it be 100, 120, 127,
but it's not an argument worth wasting time on.
Not using the whole range of the length byte opens the door to using
the rest of the range to indicate a future new information field.

Thanks,
Jakob.


> -----Original Message-----
> From: Enke Chen (enkechen)
> Sent: Sunday, May 07, 2017 8:44 PM
> To: ietf@ietf.org
> Cc: draft-ietf-idr-shutdown@ietf.org; idr@ietf.org; idr-chairs@ietf.org; =
Enke Chen (enkechen) <enkechen@cisco.com>
> Subject: Re: [Idr] Last Call: <draft-ietf-idr-shutdown-08.txt> (BGP Admin=
istrative Shutdown Communication) to
> Proposed Standard
>=20
> Hi, Folks:
>=20
> Just spotted this (apologies for not catching it earlier):
>=20
> The draft specifies only 0 - 128 as valid in the one-octet length field.
> Not sure if there is a strong reason for such an apparent over-specificat=
ion.
>=20
> It seems to me that the spec can and should be simplified by removing the
> restriction, that is, to allow any value (0 - 255) to be valid.  That wou=
ld
> also eliminate one error condition for the implementation.
>=20
> Thanks.  -- Enke
>=20
> ---
> 2.  Shutdown Communication
>=20
> Length:  this 8-bit field represents the length of the Shutdown
>       Communication field in octets.  The length value MUST range from 0
>       to 128 inclusive.
>=20
> 4.  Error Handling
>=20
>    If a Shutdown Communication with an invalid Length value,
> ----
>=20
> On 5/5/17 10:54 AM, The IESG wrote:
> >
> > The IESG has received a request from the Inter-Domain Routing WG (idr) =
to
> > consider the following document:
> > - 'BGP Administrative Shutdown Communication'
> >   <draft-ietf-idr-shutdown-08.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-05-19. 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 enhances the BGP Cease NOTIFICATION message
> >    "Administrative Shutdown" and "Administrative Reset" subcodes for
> >    operators to transmit a short freeform message to describe why a BGP
> >    session was shutdown or reset.  This document updates RFC 4486.
> >
> >
> >
> >
> >
> > The file can be obtained via
> > https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/
> >
> > IESG discussion can be tracked via
> > https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> >
> >
> > _______________________________________________
> > Idr mailing list
> > Idr@ietf.org
> > https://www.ietf.org/mailman/listinfo/idr
> >


From nobody Mon May  8 12:30:49 2017
Return-Path: <job@ntt.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 03C58128D3E for <ietf@ietfa.amsl.com>; Mon,  8 May 2017 12:30:49 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, 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 XFNYsgTSo7ZU for <ietf@ietfa.amsl.com>; Mon,  8 May 2017 12:30:46 -0700 (PDT)
Received: from mail3.dllstx09.us.to.gin.ntt.net (mail3.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::26]) (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 642F6127871 for <ietf@ietf.org>; Mon,  8 May 2017 12:30:46 -0700 (PDT)
Received: by mail3.dllstx09.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <job@ntt.net>) id 1d7oMm-0002F3-K1 (job@us.ntt.net) for ietf@ietf.org; Mon, 08 May 2017 19:30:45 +0000
Received: by mail-wr0-f171.google.com with SMTP id l9so52768003wre.1 for <ietf@ietf.org>; Mon, 08 May 2017 12:30:44 -0700 (PDT)
X-Gm-Message-State: AN3rC/5sVtD4Qzrp/Mbiye6+6NGmzVLsPnF1jUO2ONR2Ddgm2eimexMz Q9QEe8w8wEYGxaMHJCxlrd65qJon5A==
X-Received: by 10.223.131.67 with SMTP id 61mr38212742wrd.37.1494271843197; Mon, 08 May 2017 12:30:43 -0700 (PDT)
MIME-Version: 1.0
References: <149400686065.8457.16928207738917615877.idtracker@ietfa.amsl.com> <9d8cf31a-fc21-096b-543e-58750894a22a@cisco.com> <a9996bc76e604acfbe797389ed0d81f6@XCH-ALN-014.cisco.com>
In-Reply-To: <a9996bc76e604acfbe797389ed0d81f6@XCH-ALN-014.cisco.com>
From: Job Snijders <job@ntt.net>
Date: Mon, 08 May 2017 19:30:32 +0000
X-Gmail-Original-Message-ID: <CACWOCC8Te+L6NMy8Jga7W7uOjh5aB0C4tMdsDpq06O2_zQPExQ@mail.gmail.com>
Message-ID: <CACWOCC8Te+L6NMy8Jga7W7uOjh5aB0C4tMdsDpq06O2_zQPExQ@mail.gmail.com>
Subject: Re: [Idr] Last Call: <draft-ietf-idr-shutdown-08.txt> (BGP Administrative Shutdown Communication) to Proposed Standard
To: "Enke Chen (enkechen)" <enkechen@cisco.com>, "Jakob Heitz (jheitz)" <jheitz@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
Cc: "draft-ietf-idr-shutdown@ietf.org" <draft-ietf-idr-shutdown@ietf.org>,  "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c0d1078697ec5054f084638
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/A_AKXSwnUOwzBfFM-htDv2LxSYo>
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, 08 May 2017 19:30:49 -0000

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

Dear Jakob, Enke

Enke raised an interesting point.

I've received no feedback from anyone that 128 isn't sufficient. This work
was circulated at NANOG, APRICOT, GPF and UKNOF to get feedback. Due to
lack of demand for anything bigger it doesn't seem worth it to go back and
change the existing implementations.

The implementation complexity is very low already. You can review Peter van
Dijk's implemention report to get a sense of how things are done.
https://mailarchive.ietf.org/arch/msg/idr/8ueDFbC4ZBd1WwolRS78aFA8oyw

Kind regards,

Job

On Mon, 8 May at 21:13, Jakob Heitz (jheitz) <jheitz@cisco.com> wrote:

> It is deliberately kept short to minimize the potential for abuse.
> We could have argued about the length. Should it be 100, 120, 127,
> but it's not an argument worth wasting time on.
> Not using the whole range of the length byte opens the door to using
> the rest of the range to indicate a future new information field.
>
> Thanks,
> Jakob.
>
>
> > -----Original Message-----
> > From: Enke Chen (enkechen)
> > Sent: Sunday, May 07, 2017 8:44 PM
> > To: ietf@ietf.org
> > Cc: draft-ietf-idr-shutdown@ietf.org; idr@ietf.org; idr-chairs@ietf.org;
> Enke Chen (enkechen) <enkechen@cisco.com>
> > Subject: Re: [Idr] Last Call: <draft-ietf-idr-shutdown-08.txt> (BGP
> Administrative Shutdown Communication) to
> > Proposed Standard
> >
> > Hi, Folks:
> >
> > Just spotted this (apologies for not catching it earlier):
> >
> > The draft specifies only 0 - 128 as valid in the one-octet length field.
> > Not sure if there is a strong reason for such an apparent
> over-specification.
> >
> > It seems to me that the spec can and should be simplified by removing the
> > restriction, that is, to allow any value (0 - 255) to be valid.  That
> would
> > also eliminate one error condition for the implementation.
> >
> > Thanks.  -- Enke
> >
> > ---
> > 2.  Shutdown Communication
> >
> > Length:  this 8-bit field represents the length of the Shutdown
> >       Communication field in octets.  The length value MUST range from 0
> >       to 128 inclusive.
> >
> > 4.  Error Handling
> >
> >    If a Shutdown Communication with an invalid Length value,
> > ----
> >
> > On 5/5/17 10:54 AM, The IESG wrote:
> > >
> > > The IESG has received a request from the Inter-Domain Routing WG (idr)
> to
> > > consider the following document:
> > > - 'BGP Administrative Shutdown Communication'
> > >   <draft-ietf-idr-shutdown-08.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-05-19. 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 enhances the BGP Cease NOTIFICATION message
> > >    "Administrative Shutdown" and "Administrative Reset" subcodes for
> > >    operators to transmit a short freeform message to describe why a BGP
> > >    session was shutdown or reset.  This document updates RFC 4486.
> > >
> > >
> > >
> > >
> > >
> > > The file can be obtained via
> > > https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/
> > >
> > > IESG discussion can be tracked via
> > > https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/ballot/
> > >
> > >
> > > No IPR declarations have been submitted directly on this I-D.
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Idr mailing list
> > > Idr@ietf.org
> > > https://www.ietf.org/mailman/listinfo/idr
> > >
>

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

<div>Dear Jakob, Enke</div><div><br></div><div>Enke raised an interesting p=
oint.=C2=A0</div><div><br></div><div>I&#39;ve received no feedback from any=
one that 128 isn&#39;t sufficient. This work was circulated at NANOG, APRIC=
OT, GPF and UKNOF to get feedback. Due to lack of demand for anything bigge=
r it doesn&#39;t seem worth it to go back and change the existing implement=
ations. =C2=A0</div><div><br></div><div>The implementation complexity is ve=
ry low already. You can review Peter van Dijk&#39;s implemention report to =
get a sense of how things are done.=C2=A0<a href=3D"https://mailarchive.iet=
f.org/arch/msg/idr/8ueDFbC4ZBd1WwolRS78aFA8oyw">https://mailarchive.ietf.or=
g/arch/msg/idr/8ueDFbC4ZBd1WwolRS78aFA8oyw</a></div><div><br></div><div>Kin=
d regards,</div><div><br></div><div>Job</div><div><br></div><div><div class=
=3D"gmail_quote"><div>On Mon, 8 May at 21:13, Jakob Heitz (jheitz) &lt;<a h=
ref=3D"mailto:jheitz@cisco.com">jheitz@cisco.com</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">It is deliberately kept short to minimize the =
potential for abuse.<br>
We could have argued about the length. Should it be 100, 120, 127,<br>
but it&#39;s not an argument worth wasting time on.<br>
Not using the whole range of the length byte opens the door to using<br>
the rest of the range to indicate a future new information field.<br>
<br>
Thanks,<br>
Jakob.<br>
<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Enke Chen (enkechen)<br>
&gt; Sent: Sunday, May 07, 2017 8:44 PM<br>
&gt; To: <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</=
a><br>
&gt; Cc: <a href=3D"mailto:draft-ietf-idr-shutdown@ietf.org" target=3D"_bla=
nk">draft-ietf-idr-shutdown@ietf.org</a>; <a href=3D"mailto:idr@ietf.org" t=
arget=3D"_blank">idr@ietf.org</a>; <a href=3D"mailto:idr-chairs@ietf.org" t=
arget=3D"_blank">idr-chairs@ietf.org</a>; Enke Chen (enkechen) &lt;<a href=
=3D"mailto:enkechen@cisco.com" target=3D"_blank">enkechen@cisco.com</a>&gt;=
<br>
&gt; Subject: Re: [Idr] Last Call: &lt;draft-ietf-idr-shutdown-08.txt&gt; (=
BGP Administrative Shutdown Communication) to<br>
&gt; Proposed Standard<br>
&gt;<br>
&gt; Hi, Folks:<br>
&gt;<br>
&gt; Just spotted this (apologies for not catching it earlier):<br>
&gt;<br>
&gt; The draft specifies only 0 - 128 as valid in the one-octet length fiel=
d.<br>
&gt; Not sure if there is a strong reason for such an apparent over-specifi=
cation.<br>
&gt;<br>
&gt; It seems to me that the spec can and should be simplified by removing =
the<br>
&gt; restriction, that is, to allow any value (0 - 255) to be valid.=C2=A0 =
That would<br>
&gt; also eliminate one error condition for the implementation.<br>
&gt;<br>
&gt; Thanks.=C2=A0 -- Enke<br>
&gt;<br>
&gt; ---<br>
&gt; 2.=C2=A0 Shutdown Communication<br>
&gt;<br>
&gt; Length:=C2=A0 this 8-bit field represents the length of the Shutdown<b=
r>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Communication field in octets.=C2=A0 The len=
gth value MUST range from 0<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0to 128 inclusive.<br>
&gt;<br>
&gt; 4.=C2=A0 Error Handling<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 If a Shutdown Communication with an invalid Length value,=
<br>
&gt; ----<br>
&gt;<br>
&gt; On 5/5/17 10:54 AM, The IESG wrote:<br>
&gt; &gt;<br>
&gt; &gt; The IESG has received a request from the Inter-Domain Routing WG =
(idr) to<br>
&gt; &gt; consider the following document:<br>
&gt; &gt; - &#39;BGP Administrative Shutdown Communication&#39;<br>
&gt; &gt;=C2=A0 =C2=A0&lt;draft-ietf-idr-shutdown-08.txt&gt; as Proposed St=
andard<br>
&gt; &gt;<br>
&gt; &gt; The IESG plans to make a decision in the next few weeks, and soli=
cits<br>
&gt; &gt; final comments on this action. Please send substantive comments t=
o the<br>
&gt; &gt; <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org<=
/a> mailing lists by 2017-05-19. Exceptionally, comments may be<br>
&gt; &gt; sent to <a href=3D"mailto:iesg@ietf.org" target=3D"_blank">iesg@i=
etf.org</a> instead. In either case, please retain the<br>
&gt; &gt; beginning of the Subject line to allow automated sorting.<br>
&gt; &gt;<br>
&gt; &gt; Abstract<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 This document enhances the BGP Cease NOTIFICATION me=
ssage<br>
&gt; &gt;=C2=A0 =C2=A0 &quot;Administrative Shutdown&quot; and &quot;Admini=
strative Reset&quot; subcodes for<br>
&gt; &gt;=C2=A0 =C2=A0 operators to transmit a short freeform message to de=
scribe why a BGP<br>
&gt; &gt;=C2=A0 =C2=A0 session was shutdown or reset.=C2=A0 This document u=
pdates RFC 4486.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; The file can be obtained via<br>
&gt; &gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-idr-shutdo=
wn/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/=
draft-ietf-idr-shutdown/</a><br>
&gt; &gt;<br>
&gt; &gt; IESG discussion can be tracked via<br>
&gt; &gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-idr-shutdo=
wn/ballot/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.o=
rg/doc/draft-ietf-idr-shutdown/ballot/</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; No IPR declarations have been submitted directly on this I-D.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; Idr mailing list<br>
&gt; &gt; <a href=3D"mailto:Idr@ietf.org" target=3D"_blank">Idr@ietf.org</a=
><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/idr" rel=3D"nore=
ferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/idr</a><br>
&gt; &gt;<br>
</blockquote></div></div>

--94eb2c0d1078697ec5054f084638--


From nobody Mon May  8 12:36:13 2017
Return-Path: <enkechen@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 7F032127871; Mon,  8 May 2017 12:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 Xi0S2dg-oNA7; Mon,  8 May 2017 12:36:09 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7451F124234; Mon,  8 May 2017 12:36:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3758; q=dns/txt; s=iport; t=1494272169; x=1495481769; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=q+rOZMsfuFZzy/l3jKmrznGQl1OMCDLEtYRGlivGmR8=; b=XxMMNLvIB044Kq374y0i219pqZTLouaIsZcxJq7kolmv1EGX2KyQv8S6 08jm7thE5nO1qcl/fWeSGlXThKWCK2R1qeCi62/WxbulZoJWxbbtjoh+T /FetC/ml0q+/P9vZZ2xpCE7MQ+kHM90BWkBB9FBJ7udk+W/peyFzXdwUT U=;
X-IronPort-AV: E=Sophos;i="5.38,310,1491264000"; d="scan'208";a="24769386"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 May 2017 19:36:08 +0000
Received: from [10.41.60.195] ([10.41.60.195]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v48Ja7ot010806; Mon, 8 May 2017 19:36:08 GMT
Subject: Re: [Idr] Last Call: <draft-ietf-idr-shutdown-08.txt> (BGP Administrative Shutdown Communication) to Proposed Standard
To: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
References: <149400686065.8457.16928207738917615877.idtracker@ietfa.amsl.com> <9d8cf31a-fc21-096b-543e-58750894a22a@cisco.com> <a9996bc76e604acfbe797389ed0d81f6@XCH-ALN-014.cisco.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-idr-shutdown@ietf.org" <draft-ietf-idr-shutdown@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>, Enke Chen <enkechen@cisco.com>
From: Enke Chen <enkechen@cisco.com>
Message-ID: <6a3bfb3a-fd06-4291-b3f2-abb92f70ec04@cisco.com>
Date: Mon, 8 May 2017 12:36:07 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <a9996bc76e604acfbe797389ed0d81f6@XCH-ALN-014.cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kj8pVBpqJb7WIBg9BvcWhmS0EgI>
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, 08 May 2017 19:36:12 -0000

Jakob,
Hi, Jakob:

I understand this is not a good use of time.  But since it is in the
spec, I would like to understand the reasons.  If there are good reasons
for doing things differently, then they should be documented in the spec
so that people do not question again.

On 5/8/17 12:13 PM, Jakob Heitz (jheitz) wrote:
> It is deliberately kept short to minimize the potential for abuse.

128 is ok, and 129- 255 would be considered abuse?

In protocol design we have had so many mistakes related to small
length fields.  There is rarely an issue because one field has an
extra byte. 

> We could have argued about the length. Should it be 100, 120, 127,
> but it's not an argument worth wasting time on.

Yes, that is precisely the reason that this value "128" should not be
specified.

> Not using the whole range of the length byte opens the door to using
> the rest of the range to indicate a future new information field.

You mean "129-255" are reserved rather than "invalid"?  Then that should
be made clear in the spec.

Thanks.  -- Enke

> 
> Thanks,
> Jakob.
> 
> 
>> -----Original Message-----
>> From: Enke Chen (enkechen)
>> Sent: Sunday, May 07, 2017 8:44 PM
>> To: ietf@ietf.org
>> Cc: draft-ietf-idr-shutdown@ietf.org; idr@ietf.org; idr-chairs@ietf.org; Enke Chen (enkechen) <enkechen@cisco.com>
>> Subject: Re: [Idr] Last Call: <draft-ietf-idr-shutdown-08.txt> (BGP Administrative Shutdown Communication) to
>> Proposed Standard
>>
>> Hi, Folks:
>>
>> Just spotted this (apologies for not catching it earlier):
>>
>> The draft specifies only 0 - 128 as valid in the one-octet length field.
>> Not sure if there is a strong reason for such an apparent over-specification.
>>
>> It seems to me that the spec can and should be simplified by removing the
>> restriction, that is, to allow any value (0 - 255) to be valid.  That would
>> also eliminate one error condition for the implementation.
>>
>> Thanks.  -- Enke
>>
>> ---
>> 2.  Shutdown Communication
>>
>> Length:  this 8-bit field represents the length of the Shutdown
>>       Communication field in octets.  The length value MUST range from 0
>>       to 128 inclusive.
>>
>> 4.  Error Handling
>>
>>    If a Shutdown Communication with an invalid Length value,
>> ----
>>
>> On 5/5/17 10:54 AM, The IESG wrote:
>>>
>>> The IESG has received a request from the Inter-Domain Routing WG (idr) to
>>> consider the following document:
>>> - 'BGP Administrative Shutdown Communication'
>>>   <draft-ietf-idr-shutdown-08.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-05-19. 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 enhances the BGP Cease NOTIFICATION message
>>>    "Administrative Shutdown" and "Administrative Reset" subcodes for
>>>    operators to transmit a short freeform message to describe why a BGP
>>>    session was shutdown or reset.  This document updates RFC 4486.
>>>
>>>
>>>
>>>
>>>
>>> The file can be obtained via
>>> https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/
>>>
>>> IESG discussion can be tracked via
>>> https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/ballot/
>>>
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Idr mailing list
>>> Idr@ietf.org
>>> https://www.ietf.org/mailman/listinfo/idr
>>>


From nobody Mon May  8 12:47:16 2017
Return-Path: <job@ntt.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 C7CBA128D2E for <ietf@ietfa.amsl.com>; Mon,  8 May 2017 12:47:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level: 
X-Spam-Status: No, score=-0.701 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 Fr0dT6cIr4pd for <ietf@ietfa.amsl.com>; Mon,  8 May 2017 12:47:05 -0700 (PDT)
Received: from mail3.dllstx09.us.to.gin.ntt.net (mail3.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::26]) (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 E0CE5124D37 for <ietf@ietf.org>; Mon,  8 May 2017 12:47:05 -0700 (PDT)
Received: by mail3.dllstx09.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <job@ntt.net>) id 1d7ocb-0004C9-1i (job@us.ntt.net) for ietf@ietf.org; Mon, 08 May 2017 19:47:05 +0000
Received: by mail-wm0-f45.google.com with SMTP id u65so96867445wmu.1 for <ietf@ietf.org>; Mon, 08 May 2017 12:47:04 -0700 (PDT)
X-Gm-Message-State: AODbwcAQXhPP/DeQKu0oLq0/dPUyw3Nqgo9ry9FP/vJ5DPfR6gLbFZMv TQcy+CN8Fy6u9hOWXAzWgIEBeI6WEQ==
X-Received: by 10.28.68.195 with SMTP id r186mr10971907wma.22.1494272823839; Mon, 08 May 2017 12:47:03 -0700 (PDT)
MIME-Version: 1.0
References: <149400686065.8457.16928207738917615877.idtracker@ietfa.amsl.com> <9d8cf31a-fc21-096b-543e-58750894a22a@cisco.com> <a9996bc76e604acfbe797389ed0d81f6@XCH-ALN-014.cisco.com> <6a3bfb3a-fd06-4291-b3f2-abb92f70ec04@cisco.com>
In-Reply-To: <6a3bfb3a-fd06-4291-b3f2-abb92f70ec04@cisco.com>
From: Job Snijders <job@ntt.net>
Date: Mon, 08 May 2017 19:46:53 +0000
X-Gmail-Original-Message-ID: <CACWOCC_mRwMXhrQFzNKin2G4VvT6GoGMGQQiW-rss_5kRY3Yrw@mail.gmail.com>
Message-ID: <CACWOCC_mRwMXhrQFzNKin2G4VvT6GoGMGQQiW-rss_5kRY3Yrw@mail.gmail.com>
Subject: Re: [Idr] Last Call: <draft-ietf-idr-shutdown-08.txt> (BGP Administrative Shutdown Communication) to Proposed Standard
To: Enke Chen <enkechen@cisco.com>, "Jakob Heitz (jheitz)" <jheitz@cisco.com>
Cc: "draft-ietf-idr-shutdown@ietf.org" <draft-ietf-idr-shutdown@ietf.org>,  "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a1148f4fcdd104d054f088097
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uwx6miXXz_PIO035_eO_mI1BJuw>
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, 08 May 2017 19:47:08 -0000

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

On Mon, 8 May 2017 at 21:36, Enke Chen <enkechen@cisco.com> wrote:

> I understand this is not a good use of time.  But since it is in the
> spec, I would like to understand the reasons.  If there are good reasons
> for doing things differently, then they should be documented in the spec
> so that people do not question again.



In the security section: "This specification minimizes the effects of
visual spoofing by limiting the length of the Shutdown Communication."

On 5/8/17 12:13 PM, Jakob Heitz (jheitz) wrote:
> > It is deliberately kept short to minimize the potential for abuse.
>
> 128 is ok, and 129- 255 would be considered abuse?


Those are an error according to the draft.

Kind regards,

Job

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

<br><div class=3D"gmail_quote"><div>On Mon, 8 May 2017 at 21:36, Enke Chen =
&lt;<a href=3D"mailto:enkechen@cisco.com">enkechen@cisco.com</a>&gt; wrote:=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">I understand this is not a good us=
e of time.=C2=A0 But since it is in the<br>
spec, I would like to understand the reasons.=C2=A0 If there are good reaso=
ns<br>
for doing things differently, then they should be documented in the spec<br=
>
so that people do not question again.</blockquote><div><br></div><div><br><=
/div><div>In the security section: &quot;<span style=3D"font-size:1em">This=
=C2=A0</span><span style=3D"font-size:1em">specification minimizes the effe=
cts of visual spoofing by limiting=C2=A0</span><span style=3D"font-size:1em=
">the length of the Shutdown Communication.&quot;</span></div><div><br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">
On 5/8/17 12:13 PM, Jakob Heitz (jheitz) wrote:<br>
&gt; It is deliberately kept short to minimize the potential for abuse.<br>
<br>
128 is ok, and 129- 255 would be considered abuse?</blockquote><div><br></d=
iv><div>Those are an error according to the draft.</div><div><br></div><div=
>Kind regards,</div><div><br></div><div>Job</div><div><br></div></div>

--001a1148f4fcdd104d054f088097--


From nobody Mon May  8 13:28:29 2017
Return-Path: <rraszuk@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 D36811293DA; Mon,  8 May 2017 13:28:19 -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 oz5Qv3oaVLxz; Mon,  8 May 2017 13:28:18 -0700 (PDT)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::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 505E51292D3; Mon,  8 May 2017 13:28:18 -0700 (PDT)
Received: by mail-io0-x22c.google.com with SMTP id o12so29669340iod.3; Mon, 08 May 2017 13:28: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=9bz4778u3tAdINKkilzof8aC9cTy6j0Nj061hu0vhZU=; b=Vzh5F+glCP+kvY4Eb5K5F5AunwHzwb3NciDABtAk+rDOcBXiKqdUJLyXgGvHNEDas2 6xfVaD+2AI/12wkoratGYoN8vD8n7KCllIVrQIZio8S2cBDD+oKavKw0noyV2fNJD8da 9+KtK+nyzzHM7utw/N/N6IHjdGZxsJswTRy69dKtPJocGWpQZlCULP2K7psw3On5hnMH 1P5CtrMrDKds2bazWAVi5NsjT3bxL1RSNJKMzAzDOSKW8O3pamkKzVf8nPjSpSzypdmz GW5bwKWHkRBrBY3sz6q1FNuHujYWlfwI4dXpXJE6ryD66TjbcgLE450TF3azFtEHo5+d nLYQ==
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=9bz4778u3tAdINKkilzof8aC9cTy6j0Nj061hu0vhZU=; b=qx4c6K4GwsLxN5M6yyo2HnneR443WCDAN7x3g+gDoXD1cH6IW7PmwZam/vvsm4PpYT RWICUxlTKTGls1oEN79Kpjht3fcFjnIbGwxnmberXOXiscK8OG8yZlGuXUqBkOJnrRc6 bcDzqk9lJoR6ILHGkEMSYS5IP6bTeBYqqTlIt9JTs+MY9EMyWJM6NKTsG7zlCu8tsa5f 5WMObSrQNj+lPGk1c/F7M3w7OEmmwlDQvIMcZJvU4W9x0NxrGyR1D5UCde5JKffjd5qN 0W6BImWNSREJjyJUF6oaJPIhoFi/bkGboaLMuSzJitBEj1rIWHPoGHFHrY747zt0Vfe/ 5owA==
X-Gm-Message-State: AN3rC/7QFhDF7J7DfLPH0bDVVg89NDa000FCfj9jW5wQwUA2M21HhQrz czdZ0uMNQ+Jz7gI3xFZ/plvKVhkZFQ==
X-Received: by 10.107.5.12 with SMTP id 12mr51093111iof.186.1494275297668; Mon, 08 May 2017 13:28:17 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.79.62.24 with HTTP; Mon, 8 May 2017 13:28:17 -0700 (PDT)
In-Reply-To: <CACWOCC_mRwMXhrQFzNKin2G4VvT6GoGMGQQiW-rss_5kRY3Yrw@mail.gmail.com>
References: <149400686065.8457.16928207738917615877.idtracker@ietfa.amsl.com> <9d8cf31a-fc21-096b-543e-58750894a22a@cisco.com> <a9996bc76e604acfbe797389ed0d81f6@XCH-ALN-014.cisco.com> <6a3bfb3a-fd06-4291-b3f2-abb92f70ec04@cisco.com> <CACWOCC_mRwMXhrQFzNKin2G4VvT6GoGMGQQiW-rss_5kRY3Yrw@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 8 May 2017 22:28:17 +0200
X-Google-Sender-Auth: ErD8-fwp6ULT4WHrzOccW_b0vec
Message-ID: <CA+b+ER=WoxhLN_xNw1e=HvxJbyVo7nDokrXF04Kt2nC7gV6=kA@mail.gmail.com>
Subject: Re: [Idr] Last Call: <draft-ietf-idr-shutdown-08.txt> (BGP Administrative Shutdown Communication) to Proposed Standard
To: Job Snijders <job@ntt.net>
Cc: Enke Chen <enkechen@cisco.com>, "Jakob Heitz (jheitz)" <jheitz@cisco.com>,  "idr-chairs@ietf.org" <idr-chairs@ietf.org>,  "draft-ietf-idr-shutdown@ietf.org" <draft-ietf-idr-shutdown@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary=001a113ef634507513054f091401
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SFaRDbkF17q1seqpV43TacFw0Nk>
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, 08 May 2017 20:28:20 -0000

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

Hi Job,

Assuming that by "visual spoofing" you really mean this:
http://websec.github.io/unicode-security-guide/visual-spoofing/ how does
limiting the length of the field helps to minimize it ?

It is UTF which is a problem here regardless of the length.

Ok so we leave 129-255 for further use .. brilliant. Assume someone comes
tomorrow and has a great use case for sending one byte of information in
the cease. So he defines length 129 right ? And even if operator did not
type anything for the "shutdown case" ... first 128 bytes goes empty, then
goes one newly defined octet. Is this really how protocol encoding should
be done in 2017 ? Is concept of TLV so complex ?

Cheers,
R.


On Mon, May 8, 2017 at 9:46 PM, Job Snijders <job@ntt.net> wrote:

>
> On Mon, 8 May 2017 at 21:36, Enke Chen <enkechen@cisco.com> wrote:
>
>> I understand this is not a good use of time.  But since it is in the
>> spec, I would like to understand the reasons.  If there are good reasons
>> for doing things differently, then they should be documented in the spec
>> so that people do not question again.
>
>
>
> In the security section: "This specification minimizes the effects of
> visual spoofing by limiting the length of the Shutdown Communication."
>
> On 5/8/17 12:13 PM, Jakob Heitz (jheitz) wrote:
>> > It is deliberately kept short to minimize the potential for abuse.
>>
>> 128 is ok, and 129- 255 would be considered abuse?
>
>
> Those are an error according to the draft.
>
> Kind regards,
>
> Job
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small">Hi Job,</div><div class=3D"gmail_defaul=
t" style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br></d=
iv><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-s=
erif;font-size:small">Assuming that by &quot;visual spoofing&quot; you real=
ly mean this:=C2=A0<a href=3D"http://websec.github.io/unicode-security-guid=
e/visual-spoofing/">http://websec.github.io/unicode-security-guide/visual-s=
poofing/</a> how does limiting the length of the field helps to minimize it=
 ?=C2=A0</div><div class=3D"gmail_default" style=3D"font-family:arial,helve=
tica,sans-serif;font-size:small"><br></div><div class=3D"gmail_default" sty=
le=3D"font-family:arial,helvetica,sans-serif;font-size:small">It is UTF whi=
ch is a problem here regardless of the length.=C2=A0</div><div class=3D"gma=
il_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:small=
"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,helveti=
ca,sans-serif;font-size:small">Ok so we leave 129-255 for further use .. br=
illiant. Assume someone comes tomorrow and has a great use case for sending=
 one byte of information in the cease. So he defines length 129 right ? And=
 even if operator did not type anything for the &quot;shutdown case&quot; .=
.. first 128 bytes goes empty, then goes one newly defined octet. Is this r=
eally how protocol encoding should be done in 2017 ? Is concept of TLV so c=
omplex ?=C2=A0</div><div class=3D"gmail_default" style=3D"font-family:arial=
,helvetica,sans-serif;font-size:small"><br></div><div class=3D"gmail_defaul=
t" style=3D"font-family:arial,helvetica,sans-serif;font-size:small">Cheers,=
</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,san=
s-serif;font-size:small">R.</div><div class=3D"gmail_default" style=3D"font=
-family:arial,helvetica,sans-serif;font-size:small"><br></div></div><div cl=
ass=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, May 8, 2017 at 9=
:46 PM, Job Snijders <span dir=3D"ltr">&lt;<a href=3D"mailto:job@ntt.net" t=
arget=3D"_blank">job@ntt.net</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><div class=3D"gmail_quote"><span class=3D""><div>On Mon, 8 Ma=
y 2017 at 21:36, Enke Chen &lt;<a href=3D"mailto:enkechen@cisco.com" target=
=3D"_blank">enkechen@cisco.com</a>&gt; wrote:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">I understand this is not a good use of time.=C2=A0 But since it =
is in the<br>
spec, I would like to understand the reasons.=C2=A0 If there are good reaso=
ns<br>
for doing things differently, then they should be documented in the spec<br=
>
so that people do not question again.</blockquote><div><br></div><div><br><=
/div></span><div>In the security section: &quot;<span style=3D"font-size:1e=
m">This=C2=A0</span><span style=3D"font-size:1em">specification minimizes t=
he effects of visual spoofing by limiting=C2=A0</span><span style=3D"font-s=
ize:1em">the length of the Shutdown Communication.&quot;</span></div><span =
class=3D""><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 5/8/17 12:13 PM, Jakob Heitz (jheitz) wrote:<br>
&gt; It is deliberately kept short to minimize the potential for abuse.<br>
<br>
128 is ok, and 129- 255 would be considered abuse?</blockquote><div><br></d=
iv></span><div>Those are an error according to the draft.</div><div><br></d=
iv><div>Kind regards,</div><div><br></div><div>Job</div><div><br></div></di=
v>
<br>______________________________<wbr>_________________<br>
Idr mailing list<br>
<a href=3D"mailto:Idr@ietf.org">Idr@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/idr" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/idr</a><br>
<br></blockquote></div><br></div>

--001a113ef634507513054f091401--


From nobody Mon May  8 13:36:47 2017
Return-Path: <job@ntt.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 B95561293DF for <ietf@ietfa.amsl.com>; Mon,  8 May 2017 13:36:39 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 F5fc8R09c6_W for <ietf@ietfa.amsl.com>; Mon,  8 May 2017 13:36:36 -0700 (PDT)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (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 68F611298A1 for <ietf@ietf.org>; Mon,  8 May 2017 13:36:34 -0700 (PDT)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <job@ntt.net>) id 1d7pOU-000Dgi-7C (job@us.ntt.net) for ietf@ietf.org; Mon, 08 May 2017 20:36:34 +0000
Received: by mail-wm0-f41.google.com with SMTP id b84so68523203wmh.0 for <ietf@ietf.org>; Mon, 08 May 2017 13:36:34 -0700 (PDT)
X-Gm-Message-State: AODbwcDcWI4AcsAfexvCcxlI70QtHxgslGcZreBm1cMW5+/UWiZ38R0S JRJ2etydczHQssN6MIbXUdIA852hLA==
X-Received: by 10.28.68.195 with SMTP id r186mr11079898wma.22.1494275792520; Mon, 08 May 2017 13:36:32 -0700 (PDT)
MIME-Version: 1.0
References: <149400686065.8457.16928207738917615877.idtracker@ietfa.amsl.com> <9d8cf31a-fc21-096b-543e-58750894a22a@cisco.com> <a9996bc76e604acfbe797389ed0d81f6@XCH-ALN-014.cisco.com> <6a3bfb3a-fd06-4291-b3f2-abb92f70ec04@cisco.com> <CACWOCC_mRwMXhrQFzNKin2G4VvT6GoGMGQQiW-rss_5kRY3Yrw@mail.gmail.com> <CA+b+ER=WoxhLN_xNw1e=HvxJbyVo7nDokrXF04Kt2nC7gV6=kA@mail.gmail.com>
In-Reply-To: <CA+b+ER=WoxhLN_xNw1e=HvxJbyVo7nDokrXF04Kt2nC7gV6=kA@mail.gmail.com>
From: Job Snijders <job@ntt.net>
Date: Mon, 08 May 2017 20:36:21 +0000
X-Gmail-Original-Message-ID: <CACWOCC96qHdFNC7dDVLaGgtkVHY_ftSPScggX-yEXhigqpRx2Q@mail.gmail.com>
Message-ID: <CACWOCC96qHdFNC7dDVLaGgtkVHY_ftSPScggX-yEXhigqpRx2Q@mail.gmail.com>
Subject: Re: [Idr] Last Call: <draft-ietf-idr-shutdown-08.txt> (BGP Administrative Shutdown Communication) to Proposed Standard
To: Job Snijders <job@ntt.net>, Robert Raszuk <robert@raszuk.net>
Cc: Enke Chen <enkechen@cisco.com>, "Jakob Heitz (jheitz)" <jheitz@cisco.com>,  "draft-ietf-idr-shutdown@ietf.org" <draft-ietf-idr-shutdown@ietf.org>,  "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a1148f4fccf5e57054f09310e
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AuM9Y8T4jYOKvEuu9lXa5HCwiCQ>
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, 08 May 2017 20:36:40 -0000

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

Hi Robert,

The reference is to a different type of visual spoofing. The idea was to
limit the string length to prevent spoofing of additional syslog messages
or other fake cli output.

We already covered the extensibility aspect in the working group.

Kind regards,

Job

On Mon, 8 May 2017 at 22:28, Robert Raszuk <robert@raszuk.net> wrote:

> Hi Job,
>
> Assuming that by "visual spoofing" you really mean this:
> http://websec.github.io/unicode-security-guide/visual-spoofing/ how does
> limiting the length of the field helps to minimize it ?
>
> It is UTF which is a problem here regardless of the length.
>
> Ok so we leave 129-255 for further use .. brilliant. Assume someone comes
> tomorrow and has a great use case for sending one byte of information in
> the cease. So he defines length 129 right ? And even if operator did not
> type anything for the "shutdown case" ... first 128 bytes goes empty, then
> goes one newly defined octet. Is this really how protocol encoding should
> be done in 2017 ? Is concept of TLV so complex ?
>
> Cheers,
> R.
>
>
> On Mon, May 8, 2017 at 9:46 PM, Job Snijders <job@ntt.net> wrote:
>
>>
>> On Mon, 8 May 2017 at 21:36, Enke Chen <enkechen@cisco.com> wrote:
>>
>>> I understand this is not a good use of time.  But since it is in the
>>> spec, I would like to understand the reasons.  If there are good reasons
>>> for doing things differently, then they should be documented in the spec
>>> so that people do not question again.
>>
>>
>>
>> In the security section: "This specification minimizes the effects of
>> visual spoofing by limiting the length of the Shutdown Communication."
>>
>> On 5/8/17 12:13 PM, Jakob Heitz (jheitz) wrote:
>>> > It is deliberately kept short to minimize the potential for abuse.
>>>
>>> 128 is ok, and 129- 255 would be considered abuse?
>>
>>
>> Those are an error according to the draft.
>>
>> Kind regards,
>>
>> Job
>>
>>
>> _______________________________________________
>> Idr mailing list
>> Idr@ietf.org
>> https://www.ietf.org/mailman/listinfo/idr
>>
>>

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

<div>Hi Robert,</div><div><br></div><div>The reference is to a different ty=
pe of visual spoofing. The idea was to limit the string length to prevent s=
poofing of additional syslog messages or other fake cli output.=C2=A0</div>=
<div><br></div><div>We already covered the extensibility aspect in the work=
ing group.=C2=A0</div><div><br></div><div>Kind regards,</div><div><br></div=
><div>Job</div><div><br><div class=3D"gmail_quote"><div>On Mon, 8 May 2017 =
at 22:28, Robert Raszuk &lt;<a href=3D"mailto:robert@raszuk.net">robert@ras=
zuk.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div cl=
ass=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-=
size:small">Hi Job,</div><div class=3D"gmail_default" style=3D"font-family:=
arial,helvetica,sans-serif;font-size:small"><br></div><div class=3D"gmail_d=
efault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small">As=
suming that by &quot;visual spoofing&quot; you really mean this:=C2=A0<a hr=
ef=3D"http://websec.github.io/unicode-security-guide/visual-spoofing/" targ=
et=3D"_blank">http://websec.github.io/unicode-security-guide/visual-spoofin=
g/</a> how does limiting the length of the field helps to minimize it ?=C2=
=A0</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,=
sans-serif;font-size:small"><br></div><div class=3D"gmail_default" style=3D=
"font-family:arial,helvetica,sans-serif;font-size:small">It is UTF which is=
 a problem here regardless of the length.=C2=A0</div><div class=3D"gmail_de=
fault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br=
></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sa=
ns-serif;font-size:small">Ok so we leave 129-255 for further use .. brillia=
nt. Assume someone comes tomorrow and has a great use case for sending one =
byte of information in the cease. So he defines length 129 right ? And even=
 if operator did not type anything for the &quot;shutdown case&quot; ... fi=
rst 128 bytes goes empty, then goes one newly defined octet. Is this really=
 how protocol encoding should be done in 2017 ? Is concept of TLV so comple=
x ?=C2=A0</div><div class=3D"gmail_default" style=3D"font-family:arial,helv=
etica,sans-serif;font-size:small"><br></div><div class=3D"gmail_default" st=
yle=3D"font-family:arial,helvetica,sans-serif;font-size:small">Cheers,</div=
><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-ser=
if;font-size:small">R.</div><div class=3D"gmail_default" style=3D"font-fami=
ly:arial,helvetica,sans-serif;font-size:small"><br></div></div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote"></div></div><div class=3D"g=
mail_extra"><div class=3D"gmail_quote">On Mon, May 8, 2017 at 9:46 PM, Job =
Snijders <span>&lt;<a href=3D"mailto:job@ntt.net" target=3D"_blank">job@ntt=
.net</a>&gt;</span> wrote:<br></div></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"><br><div class=3D"gmail=
_quote"><span><div>On Mon, 8 May 2017 at 21:36, Enke Chen &lt;<a href=3D"ma=
ilto:enkechen@cisco.com" target=3D"_blank">enkechen@cisco.com</a>&gt; wrote=
:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">I understand this is not a good u=
se of time.=C2=A0 But since it is in the<br>
spec, I would like to understand the reasons.=C2=A0 If there are good reaso=
ns<br>
for doing things differently, then they should be documented in the spec<br=
>
so that people do not question again.</blockquote><div><br></div><div><br><=
/div></span><div>In the security section: &quot;<span style=3D"font-size:1e=
m">This=C2=A0</span><span style=3D"font-size:1em">specification minimizes t=
he effects of visual spoofing by limiting=C2=A0</span><span style=3D"font-s=
ize:1em">the length of the Shutdown Communication.&quot;</span></div><span>=
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
On 5/8/17 12:13 PM, Jakob Heitz (jheitz) wrote:<br>
&gt; It is deliberately kept short to minimize the potential for abuse.<br>
<br>
128 is ok, and 129- 255 would be considered abuse?</blockquote><div><br></d=
iv></span><div>Those are an error according to the draft.</div><div><br></d=
iv><div>Kind regards,</div><div><br></div><div>Job</div><div><br></div></di=
v>
<br></blockquote></div></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">____________________________________=
___________<br>
Idr mailing list<br>
<a href=3D"mailto:Idr@ietf.org" target=3D"_blank">Idr@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/idr" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/idr</a><br>
<br></blockquote></div></div></blockquote></div></div>

--001a1148f4fccf5e57054f09310e--


From nobody Mon May  8 13:39:33 2017
Return-Path: <rraszuk@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 0E17E1293DF; Mon,  8 May 2017 13:39:22 -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 LKH2AvEdCakK; Mon,  8 May 2017 13:39:20 -0700 (PDT)
Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001: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 44A611292D3; Mon,  8 May 2017 13:39:20 -0700 (PDT)
Received: by mail-io0-x236.google.com with SMTP id p24so58308533ioi.0; Mon, 08 May 2017 13:39:20 -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=MRE7dw18+GPlLwDWi4N28Hk57UnqG8rMuNVlRWHwWhw=; b=kg08J0L0uLMMi+kil20V443s0QKMbez1hT9qSXm5c/60Rtc22lsQOUOEPDSTOKDBmI X9MLtm0xz89mXApzFE0FqWufrJ0LDnUzglANRrKX0giZk1iez+MhMdIEHJf+/nbHuKw7 eOEqC1+ZUdEokZoJH4prIYXHYZsrcPUoQTyJED+7S/junUGpu6UfNr0Hj4Z3fqFgDGcZ JX+5FHFTHDprVxzKyz0wOC92EODSIQbb2cCpWDQgjU1RUh5yb/FL/vo/JisUXALj/aRg cVQI2tFaNiV/FUDNj3WSrsHCKw/pMtwu/K8DjVAcAZ8RbTH9RVsGZloPRrTgsgdkvAUi VRjw==
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=MRE7dw18+GPlLwDWi4N28Hk57UnqG8rMuNVlRWHwWhw=; b=cr6Ev7TVmqCSrkfAFD6/wxHlNpqYA2g/iqHl5KYLGRuzUE7ieC6gYF+JZRr3W1C2dv gPDgAdWmIWB+RWDxOj/mj/gTJdeSGF0t38Q/5uiIdEH5OBVZsYIHfHJASqNjnba9liDm hUsHF6XMs1gpCSbkLmfn3xffn8vNeJb1hZS8b3DPzXJcaPbZLl56ar81fjWZwiCH9sd3 NmKrCtLoJ2u3qFRrhURXO9slTnvUOUAnb+th6OBIzVANk/QvBlhjEqucB6mBFIAl3LGF zWBLWLT7i7ms8nsROpuRv55LWjDSISvl82PcAwTwTNpmwErKHPPBMcfZbXfqgaOeY1VC l0SA==
X-Gm-Message-State: AN3rC/5WgAy0oTh0iMAZF/ONSJBJjH4hlnvLqymF5y4xFI2paGdAm3cg rc9tr1VnI2/Ol1MSXWgpiFGgiHJk/g==
X-Received: by 10.107.5.12 with SMTP id 12mr51133662iof.186.1494275959595; Mon, 08 May 2017 13:39:19 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.79.62.24 with HTTP; Mon, 8 May 2017 13:39:18 -0700 (PDT)
In-Reply-To: <CACWOCC96qHdFNC7dDVLaGgtkVHY_ftSPScggX-yEXhigqpRx2Q@mail.gmail.com>
References: <149400686065.8457.16928207738917615877.idtracker@ietfa.amsl.com> <9d8cf31a-fc21-096b-543e-58750894a22a@cisco.com> <a9996bc76e604acfbe797389ed0d81f6@XCH-ALN-014.cisco.com> <6a3bfb3a-fd06-4291-b3f2-abb92f70ec04@cisco.com> <CACWOCC_mRwMXhrQFzNKin2G4VvT6GoGMGQQiW-rss_5kRY3Yrw@mail.gmail.com> <CA+b+ER=WoxhLN_xNw1e=HvxJbyVo7nDokrXF04Kt2nC7gV6=kA@mail.gmail.com> <CACWOCC96qHdFNC7dDVLaGgtkVHY_ftSPScggX-yEXhigqpRx2Q@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 8 May 2017 22:39:18 +0200
X-Google-Sender-Auth: Xwm23bC7F9km8ZNxdoY823dGNtE
Message-ID: <CA+b+ERnJCZ3NPne-V8=3UvgeY=qVGRXSBBtJVnkpP0dyzVtUcA@mail.gmail.com>
Subject: Re: [Idr] Last Call: <draft-ietf-idr-shutdown-08.txt> (BGP Administrative Shutdown Communication) to Proposed Standard
To: Job Snijders <job@ntt.net>
Cc: Enke Chen <enkechen@cisco.com>, "Jakob Heitz (jheitz)" <jheitz@cisco.com>,  "draft-ietf-idr-shutdown@ietf.org" <draft-ietf-idr-shutdown@ietf.org>,  "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a113ef634c4ab8e054f093b04
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/l0fLikCI52nivSmQUl1KMMk2ZWE>
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, 08 May 2017 20:39:22 -0000

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

Then this is not "visual spoofing"  ... you are just protecting from forms
of "visual attacks"

Best,
R.

On Mon, May 8, 2017 at 10:36 PM, Job Snijders <job@ntt.net> wrote:

> Hi Robert,
>
> The reference is to a different type of visual spoofing. The idea was to
> limit the string length to prevent spoofing of additional syslog messages
> or other fake cli output.
>
> We already covered the extensibility aspect in the working group.
>
> Kind regards,
>
> Job
>
> On Mon, 8 May 2017 at 22:28, Robert Raszuk <robert@raszuk.net> wrote:
>
>> Hi Job,
>>
>> Assuming that by "visual spoofing" you really mean this:
>> http://websec.github.io/unicode-security-guide/visual-spoofing/ how does
>> limiting the length of the field helps to minimize it ?
>>
>> It is UTF which is a problem here regardless of the length.
>>
>> Ok so we leave 129-255 for further use .. brilliant. Assume someone comes
>> tomorrow and has a great use case for sending one byte of information in
>> the cease. So he defines length 129 right ? And even if operator did not
>> type anything for the "shutdown case" ... first 128 bytes goes empty, then
>> goes one newly defined octet. Is this really how protocol encoding should
>> be done in 2017 ? Is concept of TLV so complex ?
>>
>> Cheers,
>> R.
>>
>>
>> On Mon, May 8, 2017 at 9:46 PM, Job Snijders <job@ntt.net> wrote:
>>
>>>
>>> On Mon, 8 May 2017 at 21:36, Enke Chen <enkechen@cisco.com> wrote:
>>>
>>>> I understand this is not a good use of time.  But since it is in the
>>>> spec, I would like to understand the reasons.  If there are good reasons
>>>> for doing things differently, then they should be documented in the spec
>>>> so that people do not question again.
>>>
>>>
>>>
>>> In the security section: "This specification minimizes the effects of
>>> visual spoofing by limiting the length of the Shutdown Communication."
>>>
>>> On 5/8/17 12:13 PM, Jakob Heitz (jheitz) wrote:
>>>> > It is deliberately kept short to minimize the potential for abuse.
>>>>
>>>> 128 is ok, and 129- 255 would be considered abuse?
>>>
>>>
>>> Those are an error according to the draft.
>>>
>>> Kind regards,
>>>
>>> Job
>>>
>>>
>>> _______________________________________________
>>> Idr mailing list
>>> Idr@ietf.org
>>> https://www.ietf.org/mailman/listinfo/idr
>>>
>>>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small"><br></div><div class=3D"gmail_default" =
style=3D"font-family:arial,helvetica,sans-serif;font-size:small">Then this =
is not &quot;visual spoofing&quot; =C2=A0... you are just protecting from f=
orms of &quot;visual attacks&quot;</div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div =
class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;fon=
t-size:small">Best,</div><div class=3D"gmail_default" style=3D"font-family:=
arial,helvetica,sans-serif;font-size:small">R.</div></div><div class=3D"gma=
il_extra"><br><div class=3D"gmail_quote">On Mon, May 8, 2017 at 10:36 PM, J=
ob Snijders <span dir=3D"ltr">&lt;<a href=3D"mailto:job@ntt.net" target=3D"=
_blank">job@ntt.net</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"=
><div>Hi Robert,</div><div><br></div><div>The reference is to a different t=
ype of visual spoofing. The idea was to limit the string length to prevent =
spoofing of additional syslog messages or other fake cli output.=C2=A0</div=
><div><br></div><div>We already covered the extensibility aspect in the wor=
king group.=C2=A0</div><div><br></div><div>Kind regards,</div><div><br></di=
v><div>Job</div><div class=3D"HOEnZb"><div class=3D"h5"><div><br><div class=
=3D"gmail_quote"><div>On Mon, 8 May 2017 at 22:28, Robert Raszuk &lt;<a hre=
f=3D"mailto:robert@raszuk.net" target=3D"_blank">robert@raszuk.net</a>&gt; =
wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><div><div class=3D"gmail_def=
ault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small">Hi J=
ob,</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,=
sans-serif;font-size:small"><br></div><div class=3D"gmail_default" style=3D=
"font-family:arial,helvetica,sans-serif;font-size:small">Assuming that by &=
quot;visual spoofing&quot; you really mean this:=C2=A0<a href=3D"http://web=
sec.github.io/unicode-security-guide/visual-spoofing/" target=3D"_blank">ht=
tp://websec.github.io/<wbr>unicode-security-guide/visual-<wbr>spoofing/</a>=
 how does limiting the length of the field helps to minimize it ?=C2=A0</di=
v><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-se=
rif;font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-f=
amily:arial,helvetica,sans-serif;font-size:small">It is UTF which is a prob=
lem here regardless of the length.=C2=A0</div><div class=3D"gmail_default" =
style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br></div>=
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small">Ok so we leave 129-255 for further use .. brilliant. Ass=
ume someone comes tomorrow and has a great use case for sending one byte of=
 information in the cease. So he defines length 129 right ? And even if ope=
rator did not type anything for the &quot;shutdown case&quot; ... first 128=
 bytes goes empty, then goes one newly defined octet. Is this really how pr=
otocol encoding should be done in 2017 ? Is concept of TLV so complex ?=C2=
=A0</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,=
sans-serif;font-size:small"><br></div><div class=3D"gmail_default" style=3D=
"font-family:arial,helvetica,sans-serif;font-size:small">Cheers,</div><div =
class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;fon=
t-size:small">R.</div><div class=3D"gmail_default" style=3D"font-family:ari=
al,helvetica,sans-serif;font-size:small"><br></div></div><div class=3D"gmai=
l_extra"><br><div class=3D"gmail_quote"></div></div><div class=3D"gmail_ext=
ra"><div class=3D"gmail_quote">On Mon, May 8, 2017 at 9:46 PM, Job Snijders=
 <span>&lt;<a href=3D"mailto:job@ntt.net" target=3D"_blank">job@ntt.net</a>=
&gt;</span> wrote:<br></div></div><div class=3D"gmail_extra"><div class=3D"=
gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><br><div class=3D"gmail_quote">=
<span><div>On Mon, 8 May 2017 at 21:36, Enke Chen &lt;<a href=3D"mailto:enk=
echen@cisco.com" target=3D"_blank">enkechen@cisco.com</a>&gt; wrote:<br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">I understand this is not a good use of ti=
me.=C2=A0 But since it is in the<br>
spec, I would like to understand the reasons.=C2=A0 If there are good reaso=
ns<br>
for doing things differently, then they should be documented in the spec<br=
>
so that people do not question again.</blockquote><div><br></div><div><br><=
/div></span><div>In the security section: &quot;<span style=3D"font-size:1e=
m">This=C2=A0</span><span style=3D"font-size:1em">specification minimizes t=
he effects of visual spoofing by limiting=C2=A0</span><span style=3D"font-s=
ize:1em">the length of the Shutdown Communication.&quot;</span></div><span>=
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
On 5/8/17 12:13 PM, Jakob Heitz (jheitz) wrote:<br>
&gt; It is deliberately kept short to minimize the potential for abuse.<br>
<br>
128 is ok, and 129- 255 would be considered abuse?</blockquote><div><br></d=
iv></span><div>Those are an error according to the draft.</div><div><br></d=
iv><div>Kind regards,</div><div><br></div><div>Job</div><div><br></div></di=
v>
<br></blockquote></div></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">______________________________<wbr>_=
________________<br>
Idr mailing list<br>
<a href=3D"mailto:Idr@ietf.org" target=3D"_blank">Idr@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/idr" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/idr</a><br>
<br></blockquote></div></div></blockquote></div></div>
</div></div></blockquote></div><br></div>

--001a113ef634c4ab8e054f093b04--


From nobody Mon May  8 13:49:32 2017
Return-Path: <job@ntt.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 6AF7A129A9D for <ietf@ietfa.amsl.com>; Mon,  8 May 2017 13:49:31 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 c3tf0jO2jYWI for <ietf@ietfa.amsl.com>; Mon,  8 May 2017 13:49:29 -0700 (PDT)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (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 BD353128961 for <ietf@ietf.org>; Mon,  8 May 2017 13:49:29 -0700 (PDT)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <job@ntt.net>) id 1d7paz-000FAV-Ja (job@us.ntt.net) for ietf@ietf.org; Mon, 08 May 2017 20:49:29 +0000
Received: by mail-wm0-f46.google.com with SMTP id m123so78358531wma.0 for <ietf@ietf.org>; Mon, 08 May 2017 13:49:29 -0700 (PDT)
X-Gm-Message-State: AN3rC/4qcrlQxJEOK78bkMH8Bi55u9Etv3cD8yvvvh9KRb64OoRNFT6V c5BPVQwfGwEKpGNyz0AeVeO3mBBMeQ==
X-Received: by 10.28.185.211 with SMTP id j202mr12992783wmf.65.1494276567947;  Mon, 08 May 2017 13:49:27 -0700 (PDT)
MIME-Version: 1.0
References: <149400686065.8457.16928207738917615877.idtracker@ietfa.amsl.com> <9d8cf31a-fc21-096b-543e-58750894a22a@cisco.com> <a9996bc76e604acfbe797389ed0d81f6@XCH-ALN-014.cisco.com> <6a3bfb3a-fd06-4291-b3f2-abb92f70ec04@cisco.com> <CACWOCC_mRwMXhrQFzNKin2G4VvT6GoGMGQQiW-rss_5kRY3Yrw@mail.gmail.com> <CA+b+ER=WoxhLN_xNw1e=HvxJbyVo7nDokrXF04Kt2nC7gV6=kA@mail.gmail.com> <CACWOCC96qHdFNC7dDVLaGgtkVHY_ftSPScggX-yEXhigqpRx2Q@mail.gmail.com> <CA+b+ERnJCZ3NPne-V8=3UvgeY=qVGRXSBBtJVnkpP0dyzVtUcA@mail.gmail.com>
In-Reply-To: <CA+b+ERnJCZ3NPne-V8=3UvgeY=qVGRXSBBtJVnkpP0dyzVtUcA@mail.gmail.com>
From: Job Snijders <job@ntt.net>
Date: Mon, 08 May 2017 20:49:17 +0000
X-Gmail-Original-Message-ID: <CACWOCC-nQsG5snXCsjWroLmV3Biva6yo-FAr1MqRDiBLMfwYUg@mail.gmail.com>
Message-ID: <CACWOCC-nQsG5snXCsjWroLmV3Biva6yo-FAr1MqRDiBLMfwYUg@mail.gmail.com>
Subject: Re: [Idr] Last Call: <draft-ietf-idr-shutdown-08.txt> (BGP Administrative Shutdown Communication) to Proposed Standard
To: Job Snijders <job@ntt.net>, Robert Raszuk <robert@raszuk.net>
Cc: Enke Chen <enkechen@cisco.com>, "Jakob Heitz (jheitz)" <jheitz@cisco.com>,  "draft-ietf-idr-shutdown@ietf.org" <draft-ietf-idr-shutdown@ietf.org>,  "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a1148db1c0778c1054f096044
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ixppJQbU6dlbwrg2pa66cvBIexQ>
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, 08 May 2017 20:49:31 -0000

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

Hi Robert,

If you (and others) think that "visual attack" is a better phrasing, I'd be
happy to change "visual spoofing" to "visual attacks" in the security
section.

Kind regards,

Job

On Mon, 8 May 2017 at 22:39, Robert Raszuk <robert@raszuk.net> wrote:

>
> Then this is not "visual spoofing"  ... you are just protecting from forms
> of "visual attacks"
>
> Best,
> R.
>
> On Mon, May 8, 2017 at 10:36 PM, Job Snijders <job@ntt.net> wrote:
>
>> Hi Robert,
>>
>> The reference is to a different type of visual spoofing. The idea was to
>> limit the string length to prevent spoofing of additional syslog messages
>> or other fake cli output.
>>
>> We already covered the extensibility aspect in the working group.
>>
>> Kind regards,
>>
>> Job
>>
>> On Mon, 8 May 2017 at 22:28, Robert Raszuk <robert@raszuk.net> wrote:
>>
>>> Hi Job,
>>>
>>> Assuming that by "visual spoofing" you really mean this:
>>> http://websec.github.io/unicode-security-guide/visual-spoofing/ how
>>> does limiting the length of the field helps to minimize it ?
>>>
>>> It is UTF which is a problem here regardless of the length.
>>>
>>> Ok so we leave 129-255 for further use .. brilliant. Assume someone
>>> comes tomorrow and has a great use case for sending one byte of information
>>> in the cease. So he defines length 129 right ? And even if operator did not
>>> type anything for the "shutdown case" ... first 128 bytes goes empty, then
>>> goes one newly defined octet. Is this really how protocol encoding should
>>> be done in 2017 ? Is concept of TLV so complex ?
>>>
>>> Cheers,
>>> R.
>>>
>>>
>>> On Mon, May 8, 2017 at 9:46 PM, Job Snijders <job@ntt.net> wrote:
>>>
>>>>
>>>> On Mon, 8 May 2017 at 21:36, Enke Chen <enkechen@cisco.com> wrote:
>>>>
>>>>> I understand this is not a good use of time.  But since it is in the
>>>>> spec, I would like to understand the reasons.  If there are good
>>>>> reasons
>>>>> for doing things differently, then they should be documented in the
>>>>> spec
>>>>> so that people do not question again.
>>>>
>>>>
>>>>
>>>> In the security section: "This specification minimizes the effects of
>>>> visual spoofing by limiting the length of the Shutdown Communication."
>>>>
>>>> On 5/8/17 12:13 PM, Jakob Heitz (jheitz) wrote:
>>>>> > It is deliberately kept short to minimize the potential for abuse.
>>>>>
>>>>> 128 is ok, and 129- 255 would be considered abuse?
>>>>
>>>>
>>>> Those are an error according to the draft.
>>>>
>>>> Kind regards,
>>>>
>>>> Job
>>>>
>>>>
>>>> _______________________________________________
>>>> Idr mailing list
>>>> Idr@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/idr
>>>>
>>>>
>

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

<div><div>Hi Robert,</div><div><br></div><div>If you (and others) think tha=
t &quot;visual attack&quot; is a better phrasing, I&#39;d be happy to chang=
e &quot;visual spoofing&quot; to &quot;visual attacks&quot; in the security=
 section.=C2=A0</div><div><br></div><div>Kind regards,</div><div><br></div>=
<div>Job</div><div><br><div class=3D"gmail_quote"><div>On Mon, 8 May 2017 a=
t 22:39, Robert Raszuk &lt;<a href=3D"mailto:robert@raszuk.net">robert@rasz=
uk.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div cla=
ss=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-s=
ize:small"><br></div><div class=3D"gmail_default" style=3D"font-family:aria=
l,helvetica,sans-serif;font-size:small">Then this is not &quot;visual spoof=
ing&quot; =C2=A0... you are just protecting from forms of &quot;visual atta=
cks&quot;</div><div class=3D"gmail_default" style=3D"font-family:arial,helv=
etica,sans-serif;font-size:small"><br></div><div class=3D"gmail_default" st=
yle=3D"font-family:arial,helvetica,sans-serif;font-size:small">Best,</div><=
div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif=
;font-size:small">R.</div></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Mon, May 8, 2017 at 10:36 PM, Job Snijders <span>&lt;<a=
 href=3D"mailto:job@ntt.net" target=3D"_blank">job@ntt.net</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>Hi Robert,</div><div><br></div=
><div>The reference is to a different type of visual spoofing. The idea was=
 to limit the string length to prevent spoofing of additional syslog messag=
es or other fake cli output.=C2=A0</div><div><br></div><div>We already cove=
red the extensibility aspect in the working group.=C2=A0</div><div><br></di=
v><div>Kind regards,</div><div><br></div><div>Job</div><div class=3D"m_4001=
006608646124484HOEnZb"><div class=3D"m_4001006608646124484h5"><div><br><div=
 class=3D"gmail_quote"><div>On Mon, 8 May 2017 at 22:28, Robert Raszuk &lt;=
<a href=3D"mailto:robert@raszuk.net" target=3D"_blank">robert@raszuk.net</a=
>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class=3D"gma=
il_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:small=
">Hi Job,</div><div class=3D"gmail_default" style=3D"font-family:arial,helv=
etica,sans-serif;font-size:small"><br></div><div class=3D"gmail_default" st=
yle=3D"font-family:arial,helvetica,sans-serif;font-size:small">Assuming tha=
t by &quot;visual spoofing&quot; you really mean this:=C2=A0<a href=3D"http=
://websec.github.io/unicode-security-guide/visual-spoofing/" target=3D"_bla=
nk">http://websec.github.io/unicode-security-guide/visual-spoofing/</a> how=
 does limiting the length of the field helps to minimize it ?=C2=A0</div><d=
iv class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;=
font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-famil=
y:arial,helvetica,sans-serif;font-size:small">It is UTF which is a problem =
here regardless of the length.=C2=A0</div><div class=3D"gmail_default" styl=
e=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div=
 class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;fo=
nt-size:small">Ok so we leave 129-255 for further use .. brilliant. Assume =
someone comes tomorrow and has a great use case for sending one byte of inf=
ormation in the cease. So he defines length 129 right ? And even if operato=
r did not type anything for the &quot;shutdown case&quot; ... first 128 byt=
es goes empty, then goes one newly defined octet. Is this really how protoc=
ol encoding should be done in 2017 ? Is concept of TLV so complex ?=C2=A0</=
div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-=
serif;font-size:small"><br></div><div class=3D"gmail_default" style=3D"font=
-family:arial,helvetica,sans-serif;font-size:small">Cheers,</div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-siz=
e:small">R.</div><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small"><br></div></div><div class=3D"gmail_ext=
ra"><br><div class=3D"gmail_quote"></div></div><div class=3D"gmail_extra"><=
div class=3D"gmail_quote">On Mon, May 8, 2017 at 9:46 PM, Job Snijders <spa=
n>&lt;<a href=3D"mailto:job@ntt.net" target=3D"_blank">job@ntt.net</a>&gt;<=
/span> wrote:<br></div></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"><br><div class=3D"gmail_quote"><span=
><div>On Mon, 8 May 2017 at 21:36, Enke Chen &lt;<a href=3D"mailto:enkechen=
@cisco.com" target=3D"_blank">enkechen@cisco.com</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">I understand this is not a good use of time.=
=C2=A0 But since it is in the<br>
spec, I would like to understand the reasons.=C2=A0 If there are good reaso=
ns<br>
for doing things differently, then they should be documented in the spec<br=
>
so that people do not question again.</blockquote><div><br></div><div><br><=
/div></span><div>In the security section: &quot;<span style=3D"font-size:1e=
m">This=C2=A0</span><span style=3D"font-size:1em">specification minimizes t=
he effects of visual spoofing by limiting=C2=A0</span><span style=3D"font-s=
ize:1em">the length of the Shutdown Communication.&quot;</span></div><span>=
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
On 5/8/17 12:13 PM, Jakob Heitz (jheitz) wrote:<br>
&gt; It is deliberately kept short to minimize the potential for abuse.<br>
<br>
128 is ok, and 129- 255 would be considered abuse?</blockquote><div><br></d=
iv></span><div>Those are an error according to the draft.</div><div><br></d=
iv><div>Kind regards,</div><div><br></div><div>Job</div><div><br></div></di=
v>
<br></blockquote></div></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">____________________________________=
___________<br>
Idr mailing list<br>
<a href=3D"mailto:Idr@ietf.org" target=3D"_blank">Idr@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/idr" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/idr</a><br>
<br></blockquote></div></div></blockquote></div></div>
</div></div></blockquote></div><br></div>
</blockquote></div></div></div>

--001a1148db1c0778c1054f096044--


From nobody Mon May  8 15:39:52 2017
Return-Path: <martin.thomson@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 A4376124BE8; Mon,  8 May 2017 15:39: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, 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 j-BK8Hj-5YUX; Mon,  8 May 2017 15:39:39 -0700 (PDT)
Received: from mail-wr0-x236.google.com (mail-wr0-x236.google.com [IPv6:2a00:1450:400c:c0c::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 19A531200FC; Mon,  8 May 2017 15:39:38 -0700 (PDT)
Received: by mail-wr0-x236.google.com with SMTP id z52so55911671wrc.2; Mon, 08 May 2017 15:39: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=bvZwFeBKOpn3zmOdduGxZxz4nx3C5F2aXmUevdpGyX4=; b=HTgbzrHoJI9D5F+sUXlf93JfsVBblGPfh171fZ+8V7bWjj58K43aKEssE9i6FCYLkx deR+SbR/lZhrMUbQxNSR+YY3gdV7Sdx0yuAIdcDEjTd88Q4chdxiJqJR9vaWoB6CFdaC gY4NaYjIP/gFauprMcF6l9WDbu7ZSmtqE31i+O0ZtCN9MPTTNQ5F8bWpY62wWK6c8QMB pCm2vgmMAWkplLOM2Ih4DvSezMHKTMKn0TsbpkvB3HUPYNLFAuc6BnygVdiTN65NIThE 7wzR1Bdy3Khnw7PiFnXor9u1S+2j3F4rwL+hWEZ+s5LgzSTHrC5C/l6ZNsKddR12vyEx b4hw==
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=bvZwFeBKOpn3zmOdduGxZxz4nx3C5F2aXmUevdpGyX4=; b=ORulXaiTfRXlM8Y863dBi2JqqEJHfhNdFZzHNjaJ754IHRWR+ueO4Ku+BjMCX57dyi R1fKG5AccHmX0IJdEecZ2jkao8x6FSogv4zQM2dASVZtLo2zQxUrcLELLf70dY3bsOYU JFPfnN7f+0HkrO3Yn0tK3s4+3ZCkd4axaMfv35Xg+SpH7f72XJ4NoFpmo+hxNz4gS7fy /UvSbvotKrIk5IpKZ2L+vzFCaZ2W1w2U7UMtm6D9yMs3GRmCLhjyFT77FHsvwaQgkMPU bFn4YD3bNprkTWbZXIYil5Zl1yX7umMKvPLPYn5tGvKCyh13RBPmgMW3g7xUVRakaebd QLsw==
X-Gm-Message-State: AODbwcA32ukmP7Pxuf2sqUiYlU++U999MuXIjw6FJ8ukv0l9TJ4phZ7V XsIw3Uqlu00XNjTRtv2WhZsNZnBlj9Ps
X-Received: by 10.46.0.70 with SMTP id 67mr7516197lja.113.1494283177290; Mon, 08 May 2017 15:39:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.83.2 with HTTP; Mon, 8 May 2017 15:39:36 -0700 (PDT)
In-Reply-To: <2A376548-9BB0-4D7B-81C6-1BD951227FEA@kuehlewind.net>
References: <149144445494.22036.11923880719369865745@ietfa.amsl.com> <DB6PR0701MB24543D95D78557DDEACA2D71951E0@DB6PR0701MB2454.eurprd07.prod.outlook.com> <CABkgnnWAn9r4ZGtVq6yLyYcC7w5rDy4dV+98q0K__Nnm2UfRew@mail.gmail.com> <HE1PR0701MB2459B2173C921635A61CC24695100@HE1PR0701MB2459.eurprd07.prod.outlook.com> <2A376548-9BB0-4D7B-81C6-1BD951227FEA@kuehlewind.net>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 9 May 2017 08:39:36 +1000
Message-ID: <CABkgnnUiyvokXWbgWFp96in3=Ge5PUhoKjNNZpxhykaMTyxQ-A@mail.gmail.com>
Subject: Re: Artart telechat review of draft-ietf-alto-multi-cost-08
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Cc: "art@ietf.org" <art@ietf.org>, "alto@ietf.org" <alto@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-alto-multi-cost.all@ietf.org" <draft-ietf-alto-multi-cost.all@ietf.org>, "Randriamasy, Sabine (Nokia - FR/Nozay)" <sabine.randriamasy@nokia-bell-labs.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U68ROlgVmxk5RlHg0DuNkHVT_gU>
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, 08 May 2017 22:39:41 -0000

Yes, I believe that the changes made were sufficient.

On 8 May 2017 at 22:15, Mirja Kuehlewind (IETF) <ietf@kuehlewind.net> wrote:
> Hi Martin,
>
> just to double check: do you think this document is ready now and all your comments have been addressed?
>
> Mirja
>
>
>> Am 27.04.2017 um 13:57 schrieb Randriamasy, Sabine (Nokia - FR/Nozay) <sabine.randriamasy@nokia-bell-labs.com>:
>>
>> Hello Martin,
>>
>> I just posted an update where the " Requirements Language" text has been moved in a section 1.1.
>> As I saw it on a number of other ietf drafts, I also added the sentence
>> "When the words appear in lower case, their natural language meaning is used."
>>
>> The update and status are available at https://datatracker.ietf.org/doc/draft-ietf-alto-multi-cost/
>>
>> Thanks,
>> Sabine
>>
>>
>>>> -----Original Message-----
>>>> From: Martin Thomson [mailto:martin.thomson@gmail.com]
>>>> Sent: 26 April 2017 08:39
>>>> To: Randriamasy, Sabine (Nokia - FR/Nozay) <sabine.randriamasy@nokia-
>>>> bell-labs.com>
>>>> Cc: art@ietf.org; alto@ietf.org; ietf@ietf.org; draft-ietf-alto-multi-
>>>> cost.all@ietf.org
>>>> Subject: Re: Artart telechat review of draft-ietf-alto-multi-cost-08
>>>>
>>>> On 26 April 2017 at 03:26, Randriamasy, Sabine (Nokia - FR/Nozay)
>>>> <sabine.randriamasy@nokia-bell-labs.com> wrote:
>>>>>>> This document doesn't cite RFC 2119, but it uses the keywords.
>>>>> [SR     ] RFC 2119 is cited on page 1, section " Requirements Language" and
>>>> section "9.1.  Normative References". Should it be referenced elsewhere?
>>>>
>>>> The convention is to put those in the body, I missed it in the boilerplate.
>>>>
>>>> I skimmed the other changes, and they look fine.
>


From nobody Mon May  8 15:52:59 2017
Return-Path: <ietf@kuehlewind.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 F1B0A127078 for <ietf@ietfa.amsl.com>; Mon,  8 May 2017 15:52:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.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 Wwyu_k2nXZwb for <ietf@ietfa.amsl.com>; Mon,  8 May 2017 15:52:56 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 230611200FC for <ietf@ietf.org>; Mon,  8 May 2017 15:52:55 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=N9xJ4hnwmzrqrN18QcxoFGPfPG7tBB81qzYkfr1RD5CbY64f3Z1UxX4s7dpfMFsjj0iulaY8XL8CQYsQsIkF/2a6HFIrTvogqoOPaAHrqakePJHu8wOxW5wbTqjJkKZkvyK5TaqxuWI8vX8MCnh/OvTcJUw9p5PJge/hbENyUV8=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 1211 invoked from network); 9 May 2017 00:45:32 +0200
Received: from p5dec259c.dip0.t-ipconnect.de (HELO ?192.168.178.33?) (93.236.37.156) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 9 May 2017 00:45:32 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [alto] Artart telechat review of draft-ietf-alto-multi-cost-08
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <CABkgnnUiyvokXWbgWFp96in3=Ge5PUhoKjNNZpxhykaMTyxQ-A@mail.gmail.com>
Date: Tue, 9 May 2017 00:45:31 +0200
Cc: "art@ietf.org" <art@ietf.org>, "draft-ietf-alto-multi-cost.all@ietf.org" <draft-ietf-alto-multi-cost.all@ietf.org>,  "alto@ietf.org" <alto@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <61DA787B-0E86-4343-88F6-5EF03ABA274A@kuehlewind.net>
References: <149144445494.22036.11923880719369865745@ietfa.amsl.com> <DB6PR0701MB24543D95D78557DDEACA2D71951E0@DB6PR0701MB2454.eurprd07.prod.outlook.com> <CABkgnnWAn9r4ZGtVq6yLyYcC7w5rDy4dV+98q0K__Nnm2UfRew@mail.gmail.com> <HE1PR0701MB2459B2173C921635A61CC24695100@HE1PR0701MB2459.eurprd07.prod.outlook.com> <2A376548-9BB0-4D7B-81C6-1BD951227FEA@kuehlewind.net> <CABkgnnUiyvokXWbgWFp96in3=Ge5PUhoKjNNZpxhykaMTyxQ-A@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.3273)
X-PPP-Message-ID: <20170508224532.1197.62492@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8dtX1vb-FTdBgpyCkMNHhLi07QI>
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, 08 May 2017 22:52:58 -0000

Thanks!

> Am 09.05.2017 um 00:39 schrieb Martin Thomson =
<martin.thomson@gmail.com>:
>=20
> Yes, I believe that the changes made were sufficient.
>=20
> On 8 May 2017 at 22:15, Mirja Kuehlewind (IETF) <ietf@kuehlewind.net> =
wrote:
>> Hi Martin,
>>=20
>> just to double check: do you think this document is ready now and all =
your comments have been addressed?
>>=20
>> Mirja
>>=20
>>=20
>>> Am 27.04.2017 um 13:57 schrieb Randriamasy, Sabine (Nokia - =
FR/Nozay) <sabine.randriamasy@nokia-bell-labs.com>:
>>>=20
>>> Hello Martin,
>>>=20
>>> I just posted an update where the " Requirements Language" text has =
been moved in a section 1.1.
>>> As I saw it on a number of other ietf drafts, I also added the =
sentence
>>> "When the words appear in lower case, their natural language meaning =
is used."
>>>=20
>>> The update and status are available at =
https://datatracker.ietf.org/doc/draft-ietf-alto-multi-cost/
>>>=20
>>> Thanks,
>>> Sabine
>>>=20
>>>=20
>>>>> -----Original Message-----
>>>>> From: Martin Thomson [mailto:martin.thomson@gmail.com]
>>>>> Sent: 26 April 2017 08:39
>>>>> To: Randriamasy, Sabine (Nokia - FR/Nozay) =
<sabine.randriamasy@nokia-
>>>>> bell-labs.com>
>>>>> Cc: art@ietf.org; alto@ietf.org; ietf@ietf.org; =
draft-ietf-alto-multi-
>>>>> cost.all@ietf.org
>>>>> Subject: Re: Artart telechat review of =
draft-ietf-alto-multi-cost-08
>>>>>=20
>>>>> On 26 April 2017 at 03:26, Randriamasy, Sabine (Nokia - FR/Nozay)
>>>>> <sabine.randriamasy@nokia-bell-labs.com> wrote:
>>>>>>>> This document doesn't cite RFC 2119, but it uses the keywords.
>>>>>> [SR     ] RFC 2119 is cited on page 1, section " Requirements =
Language" and
>>>>> section "9.1.  Normative References". Should it be referenced =
elsewhere?
>>>>>=20
>>>>> The convention is to put those in the body, I missed it in the =
boilerplate.
>>>>>=20
>>>>> I skimmed the other changes, and they look fine.
>>=20
>=20
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto


From nobody Mon May  8 20:16:20 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 2F2E11294C4; Mon,  8 May 2017 20:16:11 -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, HTML_MESSAGE=0.001, 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 L52N0Pvtd_90; Mon,  8 May 2017 20:16:09 -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 D316D129353; Mon,  8 May 2017 20:16:07 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DGF77445; Tue, 09 May 2017 03:16:06 +0000 (GMT)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 9 May 2017 04:16:05 +0100
Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.200]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0235.001; Tue, 9 May 2017 11:16:02 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Robert Raszuk <robert@raszuk.net>, Stewart Bryant <stewart.bryant@gmail.com>
CC: "spring@ietf.org" <spring@ietf.org>, IETF Discussion <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-spring-ipv6-use-cases.all@ietf.org" <draft-ietf-spring-ipv6-use-cases.all@ietf.org>, stefano previdi <sprevidi@cisco.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>
Subject: =?utf-8?B?562U5aSNOiBbc3ByaW5nXSBHZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZiBk?= =?utf-8?Q?raft-ietf-spring-ipv6-use-cases-10?=
Thread-Topic: [spring] Genart last call review of draft-ietf-spring-ipv6-use-cases-10
Thread-Index: AQHSxRPsHUHPb/nrU0uQtoD7Jn0ZhaHk+kkAgAAFI4CAAAHWgIAEtpcAgAAgtoCAAX0ogA==
Date: Tue, 9 May 2017 03:16:01 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB9C502@NKGEML515-MBS.china.huawei.com>
References: <149374426742.21414.16408814015665498739@ietfa.amsl.com> <3E209B45-90CE-4EEB-9D2B-E14EFE28DCE0@cisco.com> <87a1534f-079d-3707-9f5d-9327e831bf7a@gmail.com> <B91C6D2C-897A-404C-80B3-EAA8BDEC4414@cisco.com> <CA+b+ERnsEn3JBpb8b7Jwcm32K=-iGA3GOPokWwnaXqSpDW89Vg@mail.gmail.com> <28cabccc-5426-9938-e2bf-169de0959ddc@gmail.com> <CA+b+ERkzBo2YZPfi-GBp_JdPLsDDOSqwtSmYR0Cjj1kXJhKH4A@mail.gmail.com>
In-Reply-To: <CA+b+ERkzBo2YZPfi-GBp_JdPLsDDOSqwtSmYR0Cjj1kXJhKH4A@mail.gmail.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: multipart/alternative; boundary="_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB9C502NKGEML515MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.59113476.00B3, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.5.200, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 1a5edad125ecfd25b5f3fcb2f52b822b
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZS9uWjKwuKC-usUzZoyZ5f0kmi0>
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, 09 May 2017 03:16:11 -0000

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

SGkgUm9iZXJ0LA0KDQpFeGNlcHQgdGhlIGZ1bmN0aW9uIGluZGljYXRlZCBieSBhbGwgemVyb3Ms
IGl0IGRvZXMgcmVxdWlyZSBtYXBwaW5ncyBiZXR3ZWVuIGZ1bmN0aW9ucywgZnVuY3Rpb24gaW5k
aWNhdGlvbnMgYW5kIGxvY2F0b3JzLiBUYWtlIHRlbmFudCBuZXR3b3JrIGZ1bmN0aW9uIGFzIGFu
IGV4YW1wbGXimLoNCg0KQmVzdCByZWdhcmRzLA0KWGlhb2h1DQoNCuWPkeS7tuS6ujogc3ByaW5n
IFttYWlsdG86c3ByaW5nLWJvdW5jZXNAaWV0Zi5vcmddIOS7o+ihqCBSb2JlcnQgUmFzenVrDQrl
j5HpgIHml7bpl7Q6IDIwMTflubQ15pyIOOaXpSAyMDoxMw0K5pS25Lu25Lq6OiBTdGV3YXJ0IEJy
eWFudA0K5oqE6YCBOiBzcHJpbmdAaWV0Zi5vcmc7IElFVEYgRGlzY3Vzc2lvbjsgZ2VuLWFydEBp
ZXRmLm9yZzsgZHJhZnQtaWV0Zi1zcHJpbmctaXB2Ni11c2UtY2FzZXMuYWxsQGlldGYub3JnOyBz
dGVmYW5vIHByZXZpZGk7IEFsdmFybyBSZXRhbmEgKGFyZXRhbmEpDQrkuLvpopg6IFJlOiBbc3By
aW5nXSBHZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLXNwcmluZy1pcHY2LXVz
ZS1jYXNlcy0xMA0KDQoNCkhpIFN0ZXdhcnQsDQoNCj4g4oCLDQpZZXMsIGJ1dCB0aG9zZSBhcmUg
cmVxdWlyZWQgYW55d2F5IHRvIHN1cHBvcnQgU1J2Ng0KDQpUaGF0IGlzIGluY29ycmVjdC4NCg0K
UGxlYXNlIHdhdGNoIExlcydzIHByZXNlbnRhdGlvbiBkdXJpbmcgbGFzdCBJRVRGIHdoZXJlIGhl
IGNsZWFybHkgYW5kIGNvcnJlY3RseSBzdGF0ZWQgdGhhdCBJR1AgZXh0ZW5zaW9ucyBmb3IgU1J2
NiBhcmUgb3B0aW9uYWwgYW5kIG5vdCByZXF1aXJlZCAodW5saWtlIGluIHRoZSBjYXNlIG9mIFNS
LU1QTFMgd2hlcmUgc3VjaCBzaWduYWxsaW5nIG9mIGdsb2JhbCBsYWJlbHMgaXMgaW5kZWVkIG5l
Y2Vzc2FyeSB0byBidWlsZCAiZ2xvYmFsIGxhYmVscyIgYmFzZWQgZm9yd2FyZGluZykuDQoNCkFz
IGEgbWF0dGVyIG9mIGZhY3QgSSBrbmV3IHRoaXMgd2lsbCBnZW5lcmF0ZSBjb25mdXNpb24gaW4g
SUVURiBhbmQgcmVjb21tZW5kZWQgdG8gbWFrZSBpdCB2ZXJ5IGNsZWFyIGluIHRoZSBkcmFmdHMu
IERpc3RyaWJ1dGlvbiBvZiBTSUQgZnVuY3Rpb25zIGRvZXMgbm90IG5lZWQgdG8gYmUgY2Fycmll
ZCBpbiByb3V0aW5nIHByb3RvY29scy4gQW5kIFNSdjYgU0lEIGxvY2F0b3IgZnVuY3Rpb24gaXMg
bmF0aXZlIHRvIElQdjYgcm91dGluZyBoZW5jZSBubyBleHRlbnNpb25zIG5lZWRlZC4gU3VyZSB0
aGV5IGNhbiBiZSBjYXJyaWVkIGluIElHUHMgb3IgQkdQIGJ1dCB0aGlzIGlzIGp1c3QgYW4gb3B0
aW9uIG5vdCBuZWNlc3NpdHkuDQoNCkJlc3QsDQpSb2JlcnQuDQoNCg0KDQpPbiBNb24sIE1heSA4
LCAyMDE3IGF0IDEyOjE1IFBNLCBTdGV3YXJ0IEJyeWFudCA8c3Rld2FydC5icnlhbnRAZ21haWwu
Y29tPG1haWx0bzpzdGV3YXJ0LmJyeWFudEBnbWFpbC5jb20+PiB3cm90ZToNCg0KDQpPbiAwNS8w
NS8yMDE3IDExOjE3LCBSb2JlcnQgUmFzenVrIHdyb3RlOg0KQW5kIHRvIGFkZCBvbmUgb2JzZXJ2
YXRpb24gLi4NCg0KU3Rld2FydCBtYWtlcyBhIHBvaW50IHRoYXQgU1ItTVBMUyBjYW4gYmUgZGVw
bG95ZWQgd2l0aG91dCBtcGxzIGNvbnRyb2wgcGxhbmUuDQoNCldlbGwgaXQgc3VyZSBkb2VzIG5v
dCByZXF1aXJlIExEUCBob3dldmVyIElHUCBvciBCR1AgZXh0ZW5zaW9ucyBmb3IgU1ItTVBMUyBz
aWduYWxsaW5nIGlzIGFsc28gYW4gZXhhbXBsZSBvZiBtcGxzIGNvbnRyb2wgcGxhbmUgLi4uIGV2
ZW4gaWYgbXVjaCBzaW1wbGVyIHRoYW4gdHJhZGl0aW9uYWwgY2FzZXMgaXQgaXMgc3RpbGwgcmVx
dWlyZWQuDQoNCuKAi+KAiw0KWWVzLCBidXQgdGhvc2UgYXJlIHJlcXVpcmVkIGFueXdheSB0byBz
dXBwb3J0IFNSdjYuIFlvdSBhbHdheXMgaGF2ZSB0byBwcm92aWRlIHRoZSBtYXBwaW5nIGJldHdl
ZW4gdGhlIGZ1bmN0aW9uLCB0aGUgZnVuY3Rpb24gaWRlbnRpZmllciBhbmQgdGhlIGZ1bmN0aW9u
IGxvY2F0aW9uLg0KDQotIFN0ZXdhcnQNCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseTrlrovkvZM7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1
IDMgNSA0IDYgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBh
bm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IlxA5a6L5L2TIjsNCglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30NCi8qIFN0eWxlIERl
ZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJ
e21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7
DQoJZm9udC1mYW1pbHk65a6L5L2TO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNv
LXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVy
bGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxl
LXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5l
O30NCnNwYW4uZ21haWwtDQoJe21zby1zdHlsZS1uYW1lOmdtYWlsLTt9DQpzcGFuLmdtYWlsLWhv
ZW56Yg0KCXttc28tc3R5bGUtbmFtZTpnbWFpbC1ob2VuemI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTkN
Cgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmki
LCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1z
dHlsZS10eXBlOmV4cG9ydC1vbmx5O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4w
cHQgNzkyLjBwdDsNCgltYXJnaW46NzIuMHB0IDkwLjBwdCA3Mi4wcHQgOTAuMHB0O30NCmRpdi5X
b3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0
ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEw
MjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNo
YXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAv
Pg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFu
Zz0iWkgtQ04iIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNl
Y3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjE2LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+SGkgUm9iZXJ0LDxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjE2LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTYuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90Oztjb2xvcjojMUY0OTdEIj5FeGNlcHQgdGhlIGZ1bmN0aW9uIGluZGljYXRlZCBieSBhbGwg
emVyb3MsIGl0IGRvZXMgcmVxdWlyZSBtYXBwaW5ncyBiZXR3ZWVuIGZ1bmN0aW9ucywgZnVuY3Rp
b24gaW5kaWNhdGlvbnMgYW5kIGxvY2F0b3JzLiBUYWtlIHRlbmFudCBuZXR3b3JrDQogZnVuY3Rp
b24gYXMgYW4gZXhhbXBsZTwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxNi4wcHQ7Zm9udC1mYW1pbHk6V2luZ2RpbmdzO2NvbG9yOiMxRjQ5N0QiPko8L3NwYW4+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTYuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxNi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjE2LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+QmVzdCByZWdhcmRzLDxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjE2LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+WGlhb2h1PG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LXNpemU6MTYuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1z
ZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRp
bmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2Jv
cmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij7l
j5Hku7bkuro8c3BhbiBsYW5nPSJFTi1VUyI+Ojwvc3Bhbj48L3NwYW4+PC9iPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+IHNwcmluZyBbbWFpbHRvOnNwcmluZy1i
b3VuY2VzQGlldGYub3JnXQ0KPC9zcGFuPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
Ij7ku6PooaggPC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTox
MC4wcHQiPlJvYmVydCBSYXN6dWs8YnI+DQo8L3NwYW4+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQiPuWPkemAgeaXtumXtDxzcGFuIGxhbmc9IkVOLVVTIj46PC9zcGFuPjwvc3Bhbj48
L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij4gMjAxNzwvc3Bh
bj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+5bm0PHNwYW4gbGFuZz0iRU4tVVMiPjU8
L3NwYW4+5pyIPHNwYW4gbGFuZz0iRU4tVVMiPjg8L3NwYW4+5pelPHNwYW4gbGFuZz0iRU4tVVMi
PiAyMDoxMzxicj4NCjwvc3Bhbj48Yj7mlLbku7bkuro8c3BhbiBsYW5nPSJFTi1VUyI+Ojwvc3Bh
bj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiPiBTdGV3YXJ0IEJyeWFudDxicj4NCjwvc3Bhbj48Yj7m
ioTpgIE8c3BhbiBsYW5nPSJFTi1VUyI+Ojwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiPiBz
cHJpbmdAaWV0Zi5vcmc7IElFVEYgRGlzY3Vzc2lvbjsgZ2VuLWFydEBpZXRmLm9yZzsgZHJhZnQt
aWV0Zi1zcHJpbmctaXB2Ni11c2UtY2FzZXMuYWxsQGlldGYub3JnOyBzdGVmYW5vIHByZXZpZGk7
IEFsdmFybyBSZXRhbmEgKGFyZXRhbmEpPGJyPg0KPC9zcGFuPjxiPuS4u+mimDxzcGFuIGxhbmc9
IkVOLVVTIj46PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyI+IFJlOiBbc3ByaW5nXSBHZW5h
cnQgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLXNwcmluZy1pcHY2LXVzZS1jYXNlcy0x
MDxvOnA+PC9vOnA+PC9zcGFuPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1z
ZXJpZiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4N
CjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
Ij5IaSBTdGV3YXJ0LDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mZ3Q7IOKAizxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7Ij5ZZXMsIGJ1dCB0aG9zZSBhcmUgcmVxdWlyZWQgYW55d2F5IHRvIHN1cHBv
cnQgU1J2NjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJp
YWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7Ij5UaGF0IGlzIGluY29ycmVjdC4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJp
YWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+UGxlYXNlIHdhdGNoIExlcydzIHByZXNl
bnRhdGlvbiBkdXJpbmcgbGFzdCBJRVRGIHdoZXJlIGhlIGNsZWFybHkgYW5kIGNvcnJlY3RseSBz
dGF0ZWQgdGhhdCBJR1AgZXh0ZW5zaW9ucyBmb3IgU1J2NiBhcmUgb3B0aW9uYWwgYW5kIG5vdCBy
ZXF1aXJlZCAodW5saWtlIGluIHRoZSBjYXNlIG9mIFNSLU1QTFMNCiB3aGVyZSBzdWNoIHNpZ25h
bGxpbmcgb2YgZ2xvYmFsIGxhYmVscyBpcyBpbmRlZWQgbmVjZXNzYXJ5IHRvIGJ1aWxkICZxdW90
O2dsb2JhbCBsYWJlbHMmcXVvdDsgYmFzZWQgZm9yd2FyZGluZykuJm5ic3A7PG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkFzIGEgbWF0dGVy
IG9mIGZhY3QgSSBrbmV3IHRoaXMgd2lsbCBnZW5lcmF0ZSBjb25mdXNpb24gaW4gSUVURiBhbmQg
cmVjb21tZW5kZWQgdG8gbWFrZSBpdCB2ZXJ5IGNsZWFyIGluIHRoZSBkcmFmdHMuIERpc3RyaWJ1
dGlvbiBvZiBTSUQgZnVuY3Rpb25zIGRvZXMgbm90IG5lZWQgdG8gYmUgY2FycmllZCBpbg0KIHJv
dXRpbmcgcHJvdG9jb2xzLiBBbmQgU1J2NiBTSUQgbG9jYXRvciBmdW5jdGlvbiBpcyBuYXRpdmUg
dG8gSVB2NiByb3V0aW5nIGhlbmNlIG5vIGV4dGVuc2lvbnMgbmVlZGVkLiBTdXJlIHRoZXkgY2Fu
IGJlIGNhcnJpZWQgaW4gSUdQcyBvciBCR1AgYnV0IHRoaXMgaXMganVzdCBhbiBvcHRpb24gbm90
IG5lY2Vzc2l0eS4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90OyI+QmVzdCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPlJvYmVydC48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+T24gTW9uLCBN
YXkgOCwgMjAxNyBhdCAxMjoxNSBQTSwgU3Rld2FydCBCcnlhbnQgJmx0OzxhIGhyZWY9Im1haWx0
bzpzdGV3YXJ0LmJyeWFudEBnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5zdGV3YXJ0LmJyeWFu
dEBnbWFpbC5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PGJyPg0KPGJyPg0KPHNwYW4gY2xhc3M9
ImdtYWlsLSI+T24gMDUvMDUvMjAxNyAxMToxNywgUm9iZXJ0IFJhc3p1ayB3cm90ZTo8bzpwPjwv
bzpwPjwvc3Bhbj48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiPkFuZCB0byBhZGQgb25lIG9ic2VydmF0aW9uIC4uPGJyPg0KPGJyPg0KU3Rld2FydCBt
YWtlcyBhIHBvaW50IHRoYXQgU1ItTVBMUyBjYW4gYmUgZGVwbG95ZWQgd2l0aG91dCBtcGxzIGNv
bnRyb2wgcGxhbmUuPGJyPg0KPGJyPg0KV2VsbCBpdCBzdXJlIGRvZXMgbm90IHJlcXVpcmUgTERQ
IGhvd2V2ZXIgSUdQIG9yIEJHUCBleHRlbnNpb25zIGZvciBTUi1NUExTIHNpZ25hbGxpbmcgaXMg
YWxzbyBhbiBleGFtcGxlIG9mIG1wbHMgY29udHJvbCBwbGFuZSAuLi4gZXZlbiBpZiBtdWNoIHNp
bXBsZXIgdGhhbiB0cmFkaXRpb25hbCBjYXNlcyBpdCBpcyBzdGlsbCByZXF1aXJlZC48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+4oCL4oCLPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxz
cGFuIGxhbmc9IkVOLVVTIj5ZZXMsIGJ1dCB0aG9zZSBhcmUgcmVxdWlyZWQgYW55d2F5IHRvIHN1
cHBvcnQgU1J2Ni4gWW91IGFsd2F5cyBoYXZlIHRvIHByb3ZpZGUgdGhlIG1hcHBpbmcgYmV0d2Vl
biB0aGUgZnVuY3Rpb24sIHRoZSBmdW5jdGlvbiBpZGVudGlmaWVyIGFuZCB0aGUgZnVuY3Rpb24g
bG9jYXRpb24uPHNwYW4gc3R5bGU9ImNvbG9yOiM4ODg4ODgiPjxicj4NCjxicj4NCjxzcGFuIGNs
YXNzPSJnbWFpbC1ob2VuemIiPi0gU3Rld2FydDwvc3Bhbj48L3NwYW4+PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB9C502NKGEML515MBSchi_--


From nobody Mon May  8 21:21:09 2017
Return-Path: <rraszuk@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 6E944120227; Mon,  8 May 2017 21:21:07 -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 LzIqy9nAus6E; Mon,  8 May 2017 21:21:05 -0700 (PDT)
Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E84DA129AB2; Mon,  8 May 2017 21:20:56 -0700 (PDT)
Received: by mail-io0-x231.google.com with SMTP id k91so63031769ioi.1; Mon, 08 May 2017 21:20:56 -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=njPnFQctFH4WXmNQUG7xNWkbk+K19hDrbu9y/KNTig8=; b=vWm3hgiGum52dAVoRljBoc5PIGsY/66babkWMGqS71Y4HD3sue84gJrsvq+5Q5aKXS 9nPXrLey3NBGM+1oK1JXf0e4Jhm5Vc7TU16es8JCiTOKBgu2LLATy0r9qy3yqOnkSUpb 0+NTFzVd0p6vfvgKcrim3GMacBa53jQUrB7wIi6p5Se5rWo+WgTimGXj9OEW5un1Soxi hxyQLp08tPoiF9fMxWnBxMgoi0JRoG1B+P662umTXSBMw2nZPzXEP5bzRNlMhBXl+Yp6 3R6rPd+Y/hFRHopLpCa7OTX3/1PnWHzxSOo4gFNayInl3SdrPEK1gkMd6rC+t97A/ere a+SQ==
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=njPnFQctFH4WXmNQUG7xNWkbk+K19hDrbu9y/KNTig8=; b=H9xTxIqrYD+1qDByUjv8xol9DqZEQdKyXtzrehM6KmixlFlw9gpgfA8bwbX3VOHDTs nb4ROut580eyRUa1uGNDVdo14bBE0ow4Bvd6OaMUM2ggAIag5sEbaXX8iAd1EFOZ4Xwn TYNPxWjZEc7+Id43wwio3spsCHE+IJ+CLpoLoqEg5qX6G7jN3khiX3aUjWnEMIHs8wYA IpVJsFWsmAyqJaYZ/JWPNdczzuv9wcgOitKTPiBej6/QsfVh1qJmvyh0BCVGiPflSkKS CGi9WQz+EWF60KSLhYght5XDGT+mU6ILKTgkavUwWkAo8e14op5RAHAdkHPKbJf/6ssX YeOw==
X-Gm-Message-State: AN3rC/6VqMdqp1c8MmvyabCr2qYXoUoJCsWm6h5CaLNM7oPZ7I40+/C3 ZZgaK+nL1oC6WMfcJ5l1tLY6Gm47bg==
X-Received: by 10.107.189.198 with SMTP id n189mr60124928iof.179.1494303656302;  Mon, 08 May 2017 21:20:56 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.79.62.24 with HTTP; Mon, 8 May 2017 21:20:55 -0700 (PDT)
Received: by 10.79.62.24 with HTTP; Mon, 8 May 2017 21:20:55 -0700 (PDT)
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB9C502@NKGEML515-MBS.china.huawei.com>
References: <149374426742.21414.16408814015665498739@ietfa.amsl.com> <3E209B45-90CE-4EEB-9D2B-E14EFE28DCE0@cisco.com> <87a1534f-079d-3707-9f5d-9327e831bf7a@gmail.com> <B91C6D2C-897A-404C-80B3-EAA8BDEC4414@cisco.com> <CA+b+ERnsEn3JBpb8b7Jwcm32K=-iGA3GOPokWwnaXqSpDW89Vg@mail.gmail.com> <28cabccc-5426-9938-e2bf-169de0959ddc@gmail.com> <CA+b+ERkzBo2YZPfi-GBp_JdPLsDDOSqwtSmYR0Cjj1kXJhKH4A@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB9C502@NKGEML515-MBS.china.huawei.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 9 May 2017 06:20:55 +0200
X-Google-Sender-Auth: 0YcMhw_1G9X72BWL3kXVgdFIMz0
Message-ID: <CA+b+ER=JGvBB6F1dMpcwoFvBRA+H-cxrhvZpcuapGNHVdSpD0g@mail.gmail.com>
Subject: =?UTF-8?B?UmU6IFtzcHJpbmddIOetlOWkjTogR2VuYXJ0IGxhc3QgY2FsbCByZXZpZXcgb2YgZHJhZg==?= =?UTF-8?B?dC1pZXRmLXNwcmluZy1pcHY2LXVzZS1jYXNlcy0xMA==?=
To: Xuxiaohu <xuxiaohu@huawei.com>
Cc: stefano previdi <sprevidi@cisco.com>, Stewart Bryant <stewart.bryant@gmail.com>,  "Alvaro Retana (aretana)" <aretana@cisco.com>,  "draft-ietf-spring-ipv6-use-cases.all@ietf.org" <draft-ietf-spring-ipv6-use-cases.all@ietf.org>,  "gen-art@ietf.org" <gen-art@ietf.org>, IETF Discussion <ietf@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c0c85e49ee560054f0faeb2
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BVhBzw6soB-uizQbSGQcP6ZJbEc>
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, 09 May 2017 04:21:07 -0000

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

Hi,

Can you point me to any SRv6 document mandating that such mapping MUST be
done in a routing protocol ?

Thx,
R.


On May 9, 2017 05:16, "Xuxiaohu" <xuxiaohu@huawei.com> wrote:

Hi Robert,



Except the function indicated by all zeros, it does require mappings
between functions, function indications and locators. Take tenant network
function as an exampleJ



Best regards,

Xiaohu



*=E5=8F=91=E4=BB=B6=E4=BA=BA:* spring [mailto:spring-bounces@ietf.org] *=E4=
=BB=A3=E8=A1=A8 *Robert Raszuk
*=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4:* 2017=E5=B9=B45=E6=9C=888=E6=97=A5 2=
0:13
*=E6=94=B6=E4=BB=B6=E4=BA=BA:* Stewart Bryant
*=E6=8A=84=E9=80=81:* spring@ietf.org; IETF Discussion; gen-art@ietf.org;
draft-ietf-spring-ipv6-use-cases.all@ietf.org; stefano previdi; Alvaro
Retana (aretana)
*=E4=B8=BB=E9=A2=98:* Re: [spring] Genart last call review of draft-ietf-sp=
ring-ipv6-use-
cases-10





Hi Stewart,



> =E2=80=8B

Yes, but those are required anyway to support SRv6



That is incorrect.



Please watch Les's presentation during last IETF where he clearly and
correctly stated that IGP extensions for SRv6 are optional and not required
(unlike in the case of SR-MPLS where such signalling of global labels is
indeed necessary to build "global labels" based forwarding).



As a matter of fact I knew this will generate confusion in IETF and
recommended to make it very clear in the drafts. Distribution of SID
functions does not need to be carried in routing protocols. And SRv6 SID
locator function is native to IPv6 routing hence no extensions needed. Sure
they can be carried in IGPs or BGP but this is just an option not
necessity.



Best,

Robert.







On Mon, May 8, 2017 at 12:15 PM, Stewart Bryant <stewart.bryant@gmail.com>
wrote:



On 05/05/2017 11:17, Robert Raszuk wrote:

And to add one observation ..

Stewart makes a point that SR-MPLS can be deployed without mpls control
plane.

Well it sure does not require LDP however IGP or BGP extensions for SR-MPLS
signalling is also an example of mpls control plane ... even if much
simpler than traditional cases it is still required.



=E2=80=8B=E2=80=8B

Yes, but those are required anyway to support SRv6. You always have to
provide the mapping between the function, the function identifier and the
function location.

- Stewart



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

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

<div dir=3D"auto"><div>Hi,<div dir=3D"auto"><br></div><div dir=3D"auto">Can=
 you point me to any SRv6 document mandating that such mapping MUST be done=
 in a routing protocol ?</div><div dir=3D"auto"><br></div><div dir=3D"auto"=
>Thx,</div><div dir=3D"auto">R.</div><br><div class=3D"gmail_extra"><br><di=
v class=3D"gmail_quote">On May 9, 2017 05:16, &quot;Xuxiaohu&quot; &lt;<a h=
ref=3D"mailto:xuxiaohu@huawei.com">xuxiaohu@huawei.com</a>&gt; wrote:<br ty=
pe=3D"attribution"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">





<div lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple">
<div class=3D"m_-6070289715234172439WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi Robert,=
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=
=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Except the=
 function indicated by all zeros, it does require mappings between function=
s, function indications and locators. Take tenant network
 function as an example</span><span lang=3D"EN-US" style=3D"font-size:16.0p=
t;font-family:Wingdings;color:#1f497d">J</span><span lang=3D"EN-US" style=
=3D"font-size:16.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;=
;color:#1f497d"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=
=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Best regar=
ds,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Xiaohu<u><=
/u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=
=A0<u></u></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 #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt">=E5=8F=91=E4=BB=
=B6=E4=BA=BA<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt"> spring [mailto:<a href=3D"mailto:spring-bounces@i=
etf.org" target=3D"_blank">spring-bounces@ietf.<wbr>org</a>]
</span><b><span style=3D"font-size:10.0pt">=E4=BB=A3=E8=A1=A8 </span></b><s=
pan lang=3D"EN-US" style=3D"font-size:10.0pt">Robert Raszuk<br>
</span><b><span style=3D"font-size:10.0pt">=E5=8F=91=E9=80=81=E6=97=B6=E9=
=97=B4<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" style=3D=
"font-size:10.0pt"> 2017</span><span style=3D"font-size:10.0pt">=E5=B9=B4<s=
pan lang=3D"EN-US">5</span>=E6=9C=88<span lang=3D"EN-US">8</span>=E6=97=A5<=
span lang=3D"EN-US"> 20:13<br>
</span><b>=E6=94=B6=E4=BB=B6=E4=BA=BA<span lang=3D"EN-US">:</span></b><span=
 lang=3D"EN-US"> Stewart Bryant<br>
</span><b>=E6=8A=84=E9=80=81<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> <a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf.or=
g</a>; IETF Discussion; <a href=3D"mailto:gen-art@ietf.org" target=3D"_blan=
k">gen-art@ietf.org</a>; <a href=3D"mailto:draft-ietf-spring-ipv6-use-cases=
.all@ietf.org" target=3D"_blank">draft-ietf-spring-ipv6-use-<wbr>cases.all@=
ietf.org</a>; stefano previdi; Alvaro Retana (aretana)<br>
</span><b>=E4=B8=BB=E9=A2=98<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> Re: [spring] Genart last call review of draft-ietf-spring-ipv6-use-=
<wbr>cases-10<u></u><u></u></span></span></p>
</div>
</div><div class=3D"elided-text">
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">Hi Stewart,<u></u><u></u></span></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">&gt; =E2=80=8B<u></u><u></u></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">Yes, but those are required anyway to suppo=
rt SRv6<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">That is incorrect.=C2=A0<u></u><u></u></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">Please watch Les&#39;s presentation during =
last IETF where he clearly and correctly stated that IGP extensions for SRv=
6 are optional and not required (unlike in the case of SR-MPLS
 where such signalling of global labels is indeed necessary to build &quot;=
global labels&quot; based forwarding).=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">As a matter of fact I knew this will genera=
te confusion in IETF and recommended to make it very clear in the drafts. D=
istribution of SID functions does not need to be carried in
 routing protocols. And SRv6 SID locator function is native to IPv6 routing=
 hence no extensions needed. Sure they can be carried in IGPs or BGP but th=
is is just an option not necessity.=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">Best,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">Robert.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">On Mon, May 8, 2017 at 12:15 PM=
, Stewart Bryant &lt;<a href=3D"mailto:stewart.bryant@gmail.com" target=3D"=
_blank">stewart.bryant@gmail.com</a>&gt; wrote:<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><br>
<br>
<span class=3D"m_-6070289715234172439gmail-">On 05/05/2017 11:17, Robert Ra=
szuk wrote:<u></u><u></u></span></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">And to add one observation ..<b=
r>
<br>
Stewart makes a point that SR-MPLS can be deployed without mpls control pla=
ne.<br>
<br>
Well it sure does not require LDP however IGP or BGP extensions for SR-MPLS=
 signalling is also an example of mpls control plane ... even if much simpl=
er than traditional cases it is still required.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">=E2=80=8B=E2=80=8B<u></u><u></u></span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
Yes, but those are required anyway to support SRv6. You always have to prov=
ide the mapping between the function, the function identifier and the funct=
ion location.<span style=3D"color:#888888"><br>
<br>
<span class=3D"m_-6070289715234172439gmail-hoenzb">- Stewart</span></span><=
u></u><u></u></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
</div>
</div>
</div></div>
</div>
</div>

<br>______________________________<wbr>_________________<br>
spring mailing list<br>
<a href=3D"mailto:spring@ietf.org">spring@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/spring" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/spring</a><br=
>
<br></blockquote></div><br></div></div></div>

--94eb2c0c85e49ee560054f0faeb2--


From nobody Mon May  8 22:07:04 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 9D1B9127B52; Mon,  8 May 2017 22:06:56 -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, HTML_MESSAGE=0.001, 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 sWPfQSISok_O; Mon,  8 May 2017 22:06:53 -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 6F23712778E; Mon,  8 May 2017 22:06:52 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml705-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DGF88022; Tue, 09 May 2017 05:06:50 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml705-cah.china.huawei.com (10.201.108.46) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 9 May 2017 06:06:48 +0100
Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.200]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Tue, 9 May 2017 13:06:42 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Robert Raszuk <robert@raszuk.net>
CC: stefano previdi <sprevidi@cisco.com>, Stewart Bryant <stewart.bryant@gmail.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>, "draft-ietf-spring-ipv6-use-cases.all@ietf.org" <draft-ietf-spring-ipv6-use-cases.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, IETF Discussion <ietf@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Subject: =?utf-8?B?562U5aSNOiBbc3ByaW5nXSDnrZTlpI06IEdlbmFydCBsYXN0IGNhbGwgcmV2?= =?utf-8?Q?iew_of_draft-ietf-spring-ipv6-use-cases-10?=
Thread-Topic: =?utf-8?B?W3NwcmluZ10g562U5aSNOiBHZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZiBk?= =?utf-8?Q?raft-ietf-spring-ipv6-use-cases-10?=
Thread-Index: AQHSyHurFkSx//gff0esdxW+rJXFe6HrcNwg
Date: Tue, 9 May 2017 05:06:42 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB9C58E@NKGEML515-MBS.china.huawei.com>
References: <149374426742.21414.16408814015665498739@ietfa.amsl.com> <3E209B45-90CE-4EEB-9D2B-E14EFE28DCE0@cisco.com> <87a1534f-079d-3707-9f5d-9327e831bf7a@gmail.com> <B91C6D2C-897A-404C-80B3-EAA8BDEC4414@cisco.com> <CA+b+ERnsEn3JBpb8b7Jwcm32K=-iGA3GOPokWwnaXqSpDW89Vg@mail.gmail.com> <28cabccc-5426-9938-e2bf-169de0959ddc@gmail.com> <CA+b+ERkzBo2YZPfi-GBp_JdPLsDDOSqwtSmYR0Cjj1kXJhKH4A@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB9C502@NKGEML515-MBS.china.huawei.com> <CA+b+ER=JGvBB6F1dMpcwoFvBRA+H-cxrhvZpcuapGNHVdSpD0g@mail.gmail.com>
In-Reply-To: <CA+b+ER=JGvBB6F1dMpcwoFvBRA+H-cxrhvZpcuapGNHVdSpD0g@mail.gmail.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: multipart/alternative; boundary="_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB9C58ENKGEML515MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090201.59114E6A.00CA, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.5.200, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 21030fa153099750610f973086d9c908
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/g8PUj18iPZN3sg9P_toB7ASsFak>
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, 09 May 2017 05:06:57 -0000

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

Tm9ib2R5IHNhaWQgdGhhdCBzdWNoIG1hcHBpbmcgbXVzdCBiZSBkaXN0cmlidXRlZCBpbiBhIHJv
dXRpbmcgcHJvdG9jb2zimLogICBXZSBqdXN0IHNhaWQgdGhhdCBzdWNoIG1hcHBpbmcgaXMgYWx3
YXlzIHJlcXVpcmVkIG5vIG1hdHRlciB3ZSB1c2UgYW4gTVBMUyBsYWJlbCBhcyBmdW5jdGlvbiBp
bnN0cnVjdGlvbiBvciB1c2luZyB0aGUgbGF0dGVyIHBhcnQgb2YgYW4gSVB2NiBhZGRyZXNzIGFz
IGZ1bmN0aW9uIGluc3RydWN0aW9uLg0KDQpCZXN0IHJlZ2FyZHMsDQpYaWFvaHUNCg0KDQrlj5Hk
u7bkuro6IHJyYXN6dWtAZ21haWwuY29tIFttYWlsdG86cnJhc3p1a0BnbWFpbC5jb21dIOS7o+ih
qCBSb2JlcnQgUmFzenVrDQrlj5HpgIHml7bpl7Q6IDIwMTflubQ15pyIOeaXpSAxMjoyMQ0K5pS2
5Lu25Lq6OiBYdXhpYW9odQ0K5oqE6YCBOiBzdGVmYW5vIHByZXZpZGk7IFN0ZXdhcnQgQnJ5YW50
OyBBbHZhcm8gUmV0YW5hIChhcmV0YW5hKTsgZHJhZnQtaWV0Zi1zcHJpbmctaXB2Ni11c2UtY2Fz
ZXMuYWxsQGlldGYub3JnOyBnZW4tYXJ0QGlldGYub3JnOyBJRVRGIERpc2N1c3Npb247IHNwcmlu
Z0BpZXRmLm9yZw0K5Li76aKYOiBSZTogW3NwcmluZ10g562U5aSNOiBHZW5hcnQgbGFzdCBjYWxs
IHJldmlldyBvZiBkcmFmdC1pZXRmLXNwcmluZy1pcHY2LXVzZS1jYXNlcy0xMA0KDQpIaSwNCg0K
Q2FuIHlvdSBwb2ludCBtZSB0byBhbnkgU1J2NiBkb2N1bWVudCBtYW5kYXRpbmcgdGhhdCBzdWNo
IG1hcHBpbmcgTVVTVCBiZSBkb25lIGluIGEgcm91dGluZyBwcm90b2NvbCA/DQoNClRoeCwNClIu
DQoNCg0KT24gTWF5IDksIDIwMTcgMDU6MTYsICJYdXhpYW9odSIgPHh1eGlhb2h1QGh1YXdlaS5j
b208bWFpbHRvOnh1eGlhb2h1QGh1YXdlaS5jb20+PiB3cm90ZToNCkhpIFJvYmVydCwNCg0KRXhj
ZXB0IHRoZSBmdW5jdGlvbiBpbmRpY2F0ZWQgYnkgYWxsIHplcm9zLCBpdCBkb2VzIHJlcXVpcmUg
bWFwcGluZ3MgYmV0d2VlbiBmdW5jdGlvbnMsIGZ1bmN0aW9uIGluZGljYXRpb25zIGFuZCBsb2Nh
dG9ycy4gVGFrZSB0ZW5hbnQgbmV0d29yayBmdW5jdGlvbiBhcyBhbiBleGFtcGxl4pi6DQoNCkJl
c3QgcmVnYXJkcywNClhpYW9odQ0KDQrlj5Hku7bkuro6IHNwcmluZyBbbWFpbHRvOnNwcmluZy1i
b3VuY2VzQGlldGYub3JnPG1haWx0bzpzcHJpbmctYm91bmNlc0BpZXRmLm9yZz5dIOS7o+ihqCBS
b2JlcnQgUmFzenVrDQrlj5HpgIHml7bpl7Q6IDIwMTflubQ15pyIOOaXpSAyMDoxMw0K5pS25Lu2
5Lq6OiBTdGV3YXJ0IEJyeWFudA0K5oqE6YCBOiBzcHJpbmdAaWV0Zi5vcmc8bWFpbHRvOnNwcmlu
Z0BpZXRmLm9yZz47IElFVEYgRGlzY3Vzc2lvbjsgZ2VuLWFydEBpZXRmLm9yZzxtYWlsdG86Z2Vu
LWFydEBpZXRmLm9yZz47IGRyYWZ0LWlldGYtc3ByaW5nLWlwdjYtdXNlLWNhc2VzLmFsbEBpZXRm
Lm9yZzxtYWlsdG86ZHJhZnQtaWV0Zi1zcHJpbmctaXB2Ni11c2UtY2FzZXMuYWxsQGlldGYub3Jn
Pjsgc3RlZmFubyBwcmV2aWRpOyBBbHZhcm8gUmV0YW5hIChhcmV0YW5hKQ0K5Li76aKYOiBSZTog
W3NwcmluZ10gR2VuYXJ0IGxhc3QgY2FsbCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1zcHJpbmctaXB2
Ni11c2UtY2FzZXMtMTANCg0KDQpIaSBTdGV3YXJ0LA0KDQo+IOKAiw0KWWVzLCBidXQgdGhvc2Ug
YXJlIHJlcXVpcmVkIGFueXdheSB0byBzdXBwb3J0IFNSdjYNCg0KVGhhdCBpcyBpbmNvcnJlY3Qu
DQoNClBsZWFzZSB3YXRjaCBMZXMncyBwcmVzZW50YXRpb24gZHVyaW5nIGxhc3QgSUVURiB3aGVy
ZSBoZSBjbGVhcmx5IGFuZCBjb3JyZWN0bHkgc3RhdGVkIHRoYXQgSUdQIGV4dGVuc2lvbnMgZm9y
IFNSdjYgYXJlIG9wdGlvbmFsIGFuZCBub3QgcmVxdWlyZWQgKHVubGlrZSBpbiB0aGUgY2FzZSBv
ZiBTUi1NUExTIHdoZXJlIHN1Y2ggc2lnbmFsbGluZyBvZiBnbG9iYWwgbGFiZWxzIGlzIGluZGVl
ZCBuZWNlc3NhcnkgdG8gYnVpbGQgImdsb2JhbCBsYWJlbHMiIGJhc2VkIGZvcndhcmRpbmcpLg0K
DQpBcyBhIG1hdHRlciBvZiBmYWN0IEkga25ldyB0aGlzIHdpbGwgZ2VuZXJhdGUgY29uZnVzaW9u
IGluIElFVEYgYW5kIHJlY29tbWVuZGVkIHRvIG1ha2UgaXQgdmVyeSBjbGVhciBpbiB0aGUgZHJh
ZnRzLiBEaXN0cmlidXRpb24gb2YgU0lEIGZ1bmN0aW9ucyBkb2VzIG5vdCBuZWVkIHRvIGJlIGNh
cnJpZWQgaW4gcm91dGluZyBwcm90b2NvbHMuIEFuZCBTUnY2IFNJRCBsb2NhdG9yIGZ1bmN0aW9u
IGlzIG5hdGl2ZSB0byBJUHY2IHJvdXRpbmcgaGVuY2Ugbm8gZXh0ZW5zaW9ucyBuZWVkZWQuIFN1
cmUgdGhleSBjYW4gYmUgY2FycmllZCBpbiBJR1BzIG9yIEJHUCBidXQgdGhpcyBpcyBqdXN0IGFu
IG9wdGlvbiBub3QgbmVjZXNzaXR5Lg0KDQpCZXN0LA0KUm9iZXJ0Lg0KDQoNCg0KT24gTW9uLCBN
YXkgOCwgMjAxNyBhdCAxMjoxNSBQTSwgU3Rld2FydCBCcnlhbnQgPHN0ZXdhcnQuYnJ5YW50QGdt
YWlsLmNvbTxtYWlsdG86c3Rld2FydC5icnlhbnRAZ21haWwuY29tPj4gd3JvdGU6DQoNCg0KT24g
MDUvMDUvMjAxNyAxMToxNywgUm9iZXJ0IFJhc3p1ayB3cm90ZToNCkFuZCB0byBhZGQgb25lIG9i
c2VydmF0aW9uIC4uDQoNClN0ZXdhcnQgbWFrZXMgYSBwb2ludCB0aGF0IFNSLU1QTFMgY2FuIGJl
IGRlcGxveWVkIHdpdGhvdXQgbXBscyBjb250cm9sIHBsYW5lLg0KDQpXZWxsIGl0IHN1cmUgZG9l
cyBub3QgcmVxdWlyZSBMRFAgaG93ZXZlciBJR1Agb3IgQkdQIGV4dGVuc2lvbnMgZm9yIFNSLU1Q
TFMgc2lnbmFsbGluZyBpcyBhbHNvIGFuIGV4YW1wbGUgb2YgbXBscyBjb250cm9sIHBsYW5lIC4u
LiBldmVuIGlmIG11Y2ggc2ltcGxlciB0aGFuIHRyYWRpdGlvbmFsIGNhc2VzIGl0IGlzIHN0aWxs
IHJlcXVpcmVkLg0KDQrigIvigIsNClllcywgYnV0IHRob3NlIGFyZSByZXF1aXJlZCBhbnl3YXkg
dG8gc3VwcG9ydCBTUnY2LiBZb3UgYWx3YXlzIGhhdmUgdG8gcHJvdmlkZSB0aGUgbWFwcGluZyBi
ZXR3ZWVuIHRoZSBmdW5jdGlvbiwgdGhlIGZ1bmN0aW9uIGlkZW50aWZpZXIgYW5kIHRoZSBmdW5j
dGlvbiBsb2NhdGlvbi4NCg0KLSBTdGV3YXJ0DQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCnNwcmluZyBtYWlsaW5nIGxpc3QNCnNwcmluZ0BpZXRm
Lm9yZzxtYWlsdG86c3ByaW5nQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9zcHJpbmcNCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseTrlrovkvZM7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1
IDMgNSA0IDYgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBh
bm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IlxA5a6L5L2TIjsNCglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30NCi8qIFN0eWxlIERl
ZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJ
e21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7
DQoJZm9udC1mYW1pbHk65a6L5L2TO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNv
LXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVy
bGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxl
LXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5l
O30NCnAuTXNvQWNldGF0ZSwgbGkuTXNvQWNldGF0ZSwgZGl2Lk1zb0FjZXRhdGUNCgl7bXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiLmibnms6jmoYbmlofmnKwgQ2hhciI7
DQoJbWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjkuMHB0
Ow0KCWZvbnQtZmFtaWx5OuWui+S9kzt9DQpzcGFuLm0tNjA3MDI4OTcxNTIzNDE3MjQzOWdtYWls
LQ0KCXttc28tc3R5bGUtbmFtZTptXy02MDcwMjg5NzE1MjM0MTcyNDM5Z21haWwtO30NCnNwYW4u
bS02MDcwMjg5NzE1MjM0MTcyNDM5Z21haWwtaG9lbnpiDQoJe21zby1zdHlsZS1uYW1lOm1fLTYw
NzAyODk3MTUyMzQxNzI0MzlnbWFpbC1ob2VuemI7fQ0Kc3Bhbi5DaGFyDQoJe21zby1zdHlsZS1u
YW1lOiLmibnms6jmoYbmlofmnKwgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1z
by1zdHlsZS1saW5rOuaJueazqOahhuaWh+acrDsNCglmb250LWZhbWlseTrlrovkvZM7fQ0Kc3Bh
bi5FbWFpbFN0eWxlMjENCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1m
YW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBE
ZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5O30NCkBwYWdlIFdvcmRTZWN0aW9u
MQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzIuMHB0IDkwLjBwdCA3Mi4wcHQg
OTAuMHB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9z
dHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVk
aXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28g
OV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJl
ZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9o
ZWFkPg0KPGJvZHkgbGFuZz0iWkgtQ04iIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRp
diBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjE2LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Tm9ib2R5IHNhaWQg
dGhhdCBzdWNoIG1hcHBpbmcgbXVzdCBiZSBkaXN0cmlidXRlZCBpbiBhIHJvdXRpbmcgcHJvdG9j
b2w8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTYuMHB0O2ZvbnQt
ZmFtaWx5OldpbmdkaW5ncztjb2xvcjojMUY0OTdEIj5KPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjE2LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7DQogV2Ug
anVzdCBzYWlkIHRoYXQgc3VjaCBtYXBwaW5nIGlzIGFsd2F5cyByZXF1aXJlZCBubyBtYXR0ZXIg
d2UgdXNlIGFuIE1QTFMgbGFiZWwgYXMgZnVuY3Rpb24gaW5zdHJ1Y3Rpb24gb3IgdXNpbmcgdGhl
IGxhdHRlciBwYXJ0IG9mIGFuIElQdjYgYWRkcmVzcyBhcyBmdW5jdGlvbiBpbnN0cnVjdGlvbi48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxNi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1zaXplOjE2LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+QmVzdCByZWdhcmRzLDxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1zaXplOjE2LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+WGlhb2h1PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTYuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxNi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYg
c3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzow
Y20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAwY20iPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQiPuWPkeS7
tuS6ujxzcGFuIGxhbmc9IkVOLVVTIj46PC9zcGFuPjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij4gcnJhc3p1a0BnbWFpbC5jb20gW21haWx0bzpy
cmFzenVrQGdtYWlsLmNvbV0NCjwvc3Bhbj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dCI+5Luj6KGoIDwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0Ij5Sb2JlcnQgUmFzenVrPGJyPg0KPC9zcGFuPjxiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0Ij7lj5HpgIHml7bpl7Q8c3BhbiBsYW5nPSJFTi1VUyI+Ojwvc3Bhbj48L3NwYW4+
PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+IDIwMTc8L3Nw
YW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQiPuW5tDxzcGFuIGxhbmc9IkVOLVVTIj41
PC9zcGFuPuaciDxzcGFuIGxhbmc9IkVOLVVTIj45PC9zcGFuPuaXpTxzcGFuIGxhbmc9IkVOLVVT
Ij4gMTI6MjE8YnI+DQo8L3NwYW4+PGI+5pS25Lu25Lq6PHNwYW4gbGFuZz0iRU4tVVMiPjo8L3Nw
YW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIj4gWHV4aWFvaHU8YnI+DQo8L3NwYW4+PGI+5oqE6YCB
PHNwYW4gbGFuZz0iRU4tVVMiPjo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIj4gc3RlZmFu
byBwcmV2aWRpOyBTdGV3YXJ0IEJyeWFudDsgQWx2YXJvIFJldGFuYSAoYXJldGFuYSk7IGRyYWZ0
LWlldGYtc3ByaW5nLWlwdjYtdXNlLWNhc2VzLmFsbEBpZXRmLm9yZzsgZ2VuLWFydEBpZXRmLm9y
ZzsgSUVURiBEaXNjdXNzaW9uOyBzcHJpbmdAaWV0Zi5vcmc8YnI+DQo8L3NwYW4+PGI+5Li76aKY
PHNwYW4gbGFuZz0iRU4tVVMiPjo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIj4gUmU6IFtz
cHJpbmddIDwvc3Bhbj4NCuetlOWkjTxzcGFuIGxhbmc9IkVOLVVTIj46IEdlbmFydCBsYXN0IGNh
bGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtc3ByaW5nLWlwdjYtdXNlLWNhc2VzLTEwPG86cD48L286
cD48L3NwYW4+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+SGksPG86cD48
L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+Q2FuIHlvdSBwb2ludCBtZSB0byBh
bnkgU1J2NiBkb2N1bWVudCBtYW5kYXRpbmcgdGhhdCBzdWNoIG1hcHBpbmcgTVVTVCBiZSBkb25l
IGluIGEgcm91dGluZyBwcm90b2NvbCA/PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIGxhbmc9IkVOLVVTIj5UaHgsPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPlIuPG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPk9uIE1heSA5LCAyMDE3
IDA1OjE2LCAmcXVvdDtYdXhpYW9odSZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnh1eGlhb2h1
QGh1YXdlaS5jb20iPnh1eGlhb2h1QGh1YXdlaS5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTYuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5IaSBSb2Jl
cnQsPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjE2
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10
b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjE2LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+RXhjZXB0IHRoZSBmdW5jdGlv
biBpbmRpY2F0ZWQgYnkgYWxsIHplcm9zLCBpdCBkb2VzIHJlcXVpcmUgbWFwcGluZ3MgYmV0d2Vl
biBmdW5jdGlvbnMsDQogZnVuY3Rpb24gaW5kaWNhdGlvbnMgYW5kIGxvY2F0b3JzLiBUYWtlIHRl
bmFudCBuZXR3b3JrIGZ1bmN0aW9uIGFzIGFuIGV4YW1wbGU8L3NwYW4+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTYuMHB0O2ZvbnQtZmFtaWx5OldpbmdkaW5ncztjb2xvcjoj
MUY0OTdEIj5KPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjE2LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2Vy
aWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjE2LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+QmVzdCByZWdhcmRz
LDwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxNi4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
O2NvbG9yOiMxRjQ5N0QiPlhpYW9odTwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxNi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48c3BhbiBs
YW5nPSJFTi1VUyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0
Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0
REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij7lj5Hku7bkuro8c3BhbiBsYW5n
PSJFTi1VUyI+Ojwvc3Bhbj48L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdCI+IHNwcmluZyBbbWFpbHRvOjxhIGhyZWY9Im1haWx0bzpzcHJpbmctYm91
bmNlc0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPnNwcmluZy1ib3VuY2VzQGlldGYub3JnPC9h
Pl0NCjwvc3Bhbj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+5Luj6KGoIDwvc3Bh
bj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij5Sb2JlcnQg
UmFzenVrPGJyPg0KPC9zcGFuPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij7lj5Hp
gIHml7bpl7Q8c3BhbiBsYW5nPSJFTi1VUyI+Ojwvc3Bhbj48L3NwYW4+PC9iPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+IDIwMTc8L3NwYW4+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQiPuW5tDxzcGFuIGxhbmc9IkVOLVVTIj41PC9zcGFuPuaciDxzcGFu
IGxhbmc9IkVOLVVTIj44PC9zcGFuPuaXpTxzcGFuIGxhbmc9IkVOLVVTIj4gMjA6MTM8YnI+DQo8
L3NwYW4+PGI+5pS25Lu25Lq6PHNwYW4gbGFuZz0iRU4tVVMiPjo8L3NwYW4+PC9iPjxzcGFuIGxh
bmc9IkVOLVVTIj4gU3Rld2FydCBCcnlhbnQ8YnI+DQo8L3NwYW4+PGI+5oqE6YCBPHNwYW4gbGFu
Zz0iRU4tVVMiPjo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIj4gPGEgaHJlZj0ibWFpbHRv
OnNwcmluZ0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPg0Kc3ByaW5nQGlldGYub3JnPC9hPjsg
SUVURiBEaXNjdXNzaW9uOyA8YSBocmVmPSJtYWlsdG86Z2VuLWFydEBpZXRmLm9yZyIgdGFyZ2V0
PSJfYmxhbmsiPg0KZ2VuLWFydEBpZXRmLm9yZzwvYT47IDxhIGhyZWY9Im1haWx0bzpkcmFmdC1p
ZXRmLXNwcmluZy1pcHY2LXVzZS1jYXNlcy5hbGxAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj4N
CmRyYWZ0LWlldGYtc3ByaW5nLWlwdjYtdXNlLWNhc2VzLmFsbEBpZXRmLm9yZzwvYT47IHN0ZWZh
bm8gcHJldmlkaTsgQWx2YXJvIFJldGFuYSAoYXJldGFuYSk8YnI+DQo8L3NwYW4+PGI+5Li76aKY
PHNwYW4gbGFuZz0iRU4tVVMiPjo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIj4gUmU6IFtz
cHJpbmddIEdlbmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtc3ByaW5nLWlwdjYt
dXNlLWNhc2VzLTEwPC9zcGFuPjwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8i
PjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0K
PGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
OyI+Jm5ic3A7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90OyI+SGkgU3Rld2FydCw8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMi
PjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy
Z2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mbmJzcDs8L3NwYW4+
PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+
DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMi
IHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7Ij4mZ3Q7IOKAizwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
OyI+WWVzLCBidXQgdGhvc2UgYXJlIHJlcXVpcmVkIGFueXdheSB0byBzdXBwb3J0IFNSdjY8L3Nw
YW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mbmJzcDs8
L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5UaGF0
IGlzIGluY29ycmVjdC4mbmJzcDs8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7Ij4mbmJzcDs8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7Ij5QbGVhc2Ugd2F0Y2ggTGVzJ3MgcHJlc2VudGF0aW9uIGR1cmlu
ZyBsYXN0IElFVEYgd2hlcmUgaGUgY2xlYXJseSBhbmQgY29ycmVjdGx5IHN0YXRlZCB0aGF0IElH
UCBleHRlbnNpb25zIGZvciBTUnY2IGFyZQ0KIG9wdGlvbmFsIGFuZCBub3QgcmVxdWlyZWQgKHVu
bGlrZSBpbiB0aGUgY2FzZSBvZiBTUi1NUExTIHdoZXJlIHN1Y2ggc2lnbmFsbGluZyBvZiBnbG9i
YWwgbGFiZWxzIGlzIGluZGVlZCBuZWNlc3NhcnkgdG8gYnVpbGQgJnF1b3Q7Z2xvYmFsIGxhYmVs
cyZxdW90OyBiYXNlZCBmb3J3YXJkaW5nKS4mbmJzcDs8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMi
PjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mbmJzcDs8L3NwYW4+PHNwYW4gbGFuZz0iRU4t
VVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlh
bCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5BcyBhIG1hdHRlciBvZiBmYWN0IEkga25l
dyB0aGlzIHdpbGwgZ2VuZXJhdGUgY29uZnVzaW9uIGluIElFVEYgYW5kIHJlY29tbWVuZGVkIHRv
IG1ha2UgaXQgdmVyeSBjbGVhciBpbiB0aGUgZHJhZnRzLg0KIERpc3RyaWJ1dGlvbiBvZiBTSUQg
ZnVuY3Rpb25zIGRvZXMgbm90IG5lZWQgdG8gYmUgY2FycmllZCBpbiByb3V0aW5nIHByb3RvY29s
cy4gQW5kIFNSdjYgU0lEIGxvY2F0b3IgZnVuY3Rpb24gaXMgbmF0aXZlIHRvIElQdjYgcm91dGlu
ZyBoZW5jZSBubyBleHRlbnNpb25zIG5lZWRlZC4gU3VyZSB0aGV5IGNhbiBiZSBjYXJyaWVkIGlu
IElHUHMgb3IgQkdQIGJ1dCB0aGlzIGlzIGp1c3QgYW4gb3B0aW9uIG5vdCBuZWNlc3NpdHkuJm5i
c3A7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+
Jm5ic3A7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
OyI+QmVzdCw8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMi
IHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7Ij5Sb2JlcnQuPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90OyI+Jm5ic3A7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1z
ZXJpZiZxdW90OyI+Jm5ic3A7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxh
bmc9IkVOLVVTIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyI+T24gTW9uLCBNYXkgOCwgMjAxNyBhdCAx
MjoxNSBQTSwgU3Rld2FydCBCcnlhbnQgJmx0OzxhIGhyZWY9Im1haWx0bzpzdGV3YXJ0LmJyeWFu
dEBnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5zdGV3YXJ0LmJyeWFudEBnbWFpbC5jb208L2E+
Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8i
PjxzcGFuIGxhbmc9IkVOLVVTIj48YnI+DQo8YnI+DQo8c3BhbiBjbGFzcz0ibS02MDcwMjg5NzE1
MjM0MTcyNDM5Z21haWwtIj5PbiAwNS8wNS8yMDE3IDExOjE3LCBSb2JlcnQgUmFzenVrIHdyb3Rl
Ojwvc3Bhbj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxz
cGFuIGxhbmc9IkVOLVVTIj5BbmQgdG8gYWRkIG9uZSBvYnNlcnZhdGlvbiAuLjxicj4NCjxicj4N
ClN0ZXdhcnQgbWFrZXMgYSBwb2ludCB0aGF0IFNSLU1QTFMgY2FuIGJlIGRlcGxveWVkIHdpdGhv
dXQgbXBscyBjb250cm9sIHBsYW5lLjxicj4NCjxicj4NCldlbGwgaXQgc3VyZSBkb2VzIG5vdCBy
ZXF1aXJlIExEUCBob3dldmVyIElHUCBvciBCR1AgZXh0ZW5zaW9ucyBmb3IgU1ItTVBMUyBzaWdu
YWxsaW5nIGlzIGFsc28gYW4gZXhhbXBsZSBvZiBtcGxzIGNvbnRyb2wgcGxhbmUgLi4uIGV2ZW4g
aWYgbXVjaCBzaW1wbGVyIHRoYW4gdHJhZGl0aW9uYWwgY2FzZXMgaXQgaXMgc3RpbGwgcmVxdWly
ZWQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBs
YW5nPSJFTi1VUyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVv
dDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij7igIvigIs8L3NwYW4+PHNwYW4g
bGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21hcmdpbi1ib3R0b206MTIu
MHB0Ij48c3BhbiBsYW5nPSJFTi1VUyI+WWVzLCBidXQgdGhvc2UgYXJlIHJlcXVpcmVkIGFueXdh
eSB0byBzdXBwb3J0IFNSdjYuIFlvdSBhbHdheXMgaGF2ZSB0byBwcm92aWRlIHRoZSBtYXBwaW5n
IGJldHdlZW4gdGhlIGZ1bmN0aW9uLCB0aGUgZnVuY3Rpb24gaWRlbnRpZmllciBhbmQgdGhlIGZ1
bmN0aW9uIGxvY2F0aW9uLjxzcGFuIHN0eWxlPSJjb2xvcjojODg4ODg4Ij48YnI+DQo8YnI+DQo8
c3BhbiBjbGFzcz0ibS02MDcwMjg5NzE1MjM0MTcyNDM5Z21haWwtaG9lbnpiIj4tIFN0ZXdhcnQ8
L3NwYW4+PC9zcGFuPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBsYW5nPSJF
Ti1VUyI+PGJyPg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X188YnI+DQpzcHJpbmcgbWFpbGluZyBsaXN0PGJyPg0KPGEgaHJlZj0ibWFpbHRvOnNwcmluZ0Bp
ZXRmLm9yZyI+c3ByaW5nQGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vc3ByaW5nIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zcHJpbmc8L2E+PG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB9C58ENKGEML515MBSchi_--


From nobody Mon May  8 23:02:36 2017
Return-Path: <rraszuk@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 083801242EA; Mon,  8 May 2017 23:02:28 -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 ycolszmd9WCF; Mon,  8 May 2017 23:02:25 -0700 (PDT)
Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 905451200E5; Mon,  8 May 2017 23:02:25 -0700 (PDT)
Received: by mail-it0-x232.google.com with SMTP id o5so80462674ith.1; Mon, 08 May 2017 23:02: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=JUeZCYucNk4WYoZzQurwdV5vVgFrKXVFml8jwJZ1ht4=; b=ka+acNur2VbcO8KUOLcX9rsbUgQ919rt1noEbY5POIstrvZ2smiVAuAopx1qxhckm6 63HDtHGkKceimSeoYSoCvhdsW3Vpo8ws762qQeJEyS/ilc3BNu9vu7EXkN9A4frND0Mc iNivxR6t7q0SJ9/AjuHEtF5OEL/k6awmFKsR4a8jY/jfltNwoYNtKxZ8gOFS8Zd9huxb vNKFPGHV3mswQKLpP4VEKCPh2Kmi/NsYdQGXLY4muST+m31mHef4Oqk6TLmql6XSK+oo A0oppuSa3QQHadQr0qcSCV5wVcxNxOGBKOQ2gSd7R3k29qy8JaS2zkQS0dgPCcmp3SBQ 0GiA==
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=JUeZCYucNk4WYoZzQurwdV5vVgFrKXVFml8jwJZ1ht4=; b=ne4TgnaiyC4nSyZAIMLBbQhATJ5XVqQrdzrkhrpkhy8d4F8UL8eyi3cuY2KD71uQ+7 I4Vs+DX76EsPZP4xEIvhrE4cRYOrKN0tg38EMv/f48dLuQC4TZEaldhXzUBowxKoubby LbhGhmz2898JRwoGWlKnDG9rdhW/WjDFRYRREJXnfKDzIU+m5awg/ZAgfCeBtSMfLUii I9SK4IWsS8MT2SpeW5oK4lIQPMh7rRTojY+8cqZsNFnz7T64RI+Ytu2t+SBXLfgCU9IQ lBgR7OS6Smjcy/5nygmDju04zCiKWId238DcOlAfpdJmXoYX4kzkYpr7SDoLhlvO1PcI 72Jw==
X-Gm-Message-State: AN3rC/42LVVFcwCpxYRLQcvJNiMXCjlMPnwvWqVz6eT1ILCn0/Td2pYn Mz663IcmsEKYpGNtrl2g8WGS7gkzCg==
X-Received: by 10.36.125.197 with SMTP id b188mr23225181itc.59.1494309744927;  Mon, 08 May 2017 23:02:24 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.79.62.24 with HTTP; Mon, 8 May 2017 23:02:24 -0700 (PDT)
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB9C58E@NKGEML515-MBS.china.huawei.com>
References: <149374426742.21414.16408814015665498739@ietfa.amsl.com> <3E209B45-90CE-4EEB-9D2B-E14EFE28DCE0@cisco.com> <87a1534f-079d-3707-9f5d-9327e831bf7a@gmail.com> <B91C6D2C-897A-404C-80B3-EAA8BDEC4414@cisco.com> <CA+b+ERnsEn3JBpb8b7Jwcm32K=-iGA3GOPokWwnaXqSpDW89Vg@mail.gmail.com> <28cabccc-5426-9938-e2bf-169de0959ddc@gmail.com> <CA+b+ERkzBo2YZPfi-GBp_JdPLsDDOSqwtSmYR0Cjj1kXJhKH4A@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB9C502@NKGEML515-MBS.china.huawei.com> <CA+b+ER=JGvBB6F1dMpcwoFvBRA+H-cxrhvZpcuapGNHVdSpD0g@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB9C58E@NKGEML515-MBS.china.huawei.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 9 May 2017 08:02:24 +0200
X-Google-Sender-Auth: _I5z0WaDvdobMhT93YtEMDvOJqg
Message-ID: <CA+b+ERnFqrNiYnbaSVsVjM4MxEeU5QRHdCYpGdpq9Ta7bVkB-w@mail.gmail.com>
Subject: =?UTF-8?B?UmU6IOetlOWkjTogW3NwcmluZ10g562U5aSNOiBHZW5hcnQgbGFzdCBjYWxsIHJldmlldw==?= =?UTF-8?B?IG9mIGRyYWZ0LWlldGYtc3ByaW5nLWlwdjYtdXNlLWNhc2VzLTEw?=
To: Xuxiaohu <xuxiaohu@huawei.com>
Cc: stefano previdi <sprevidi@cisco.com>, Stewart Bryant <stewart.bryant@gmail.com>,  "Alvaro Retana (aretana)" <aretana@cisco.com>,  "draft-ietf-spring-ipv6-use-cases.all@ietf.org" <draft-ietf-spring-ipv6-use-cases.all@ietf.org>,  "gen-art@ietf.org" <gen-art@ietf.org>, IETF Discussion <ietf@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Content-Type: multipart/alternative; boundary=001a114043b087ec9c054f1119e3
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FNA5a6kRnSWfCJNzIy8tgGEz0Mw>
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, 09 May 2017 06:02:28 -0000

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

Xiaohu,

Mapping can be also well known .. for example from the RFC clearly defining
the functions. That clearly removes the need of *any* control plane to
dynamically carry the values.

Cheers,
R.

On Tue, May 9, 2017 at 7:06 AM, Xuxiaohu <xuxiaohu@huawei.com> wrote:

> Nobody said that such mapping must be distributed in a routing protocolJ
> We just said that such mapping is always required no matter we use an MPL=
S
> label as function instruction or using the latter part of an IPv6 address
> as function instruction.
>
>
>
> Best regards,
>
> Xiaohu
>
>
>
>
>
> *=E5=8F=91=E4=BB=B6=E4=BA=BA:* rraszuk@gmail.com [mailto:rraszuk@gmail.co=
m] *=E4=BB=A3=E8=A1=A8 *Robert Raszuk
> *=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4:* 2017=E5=B9=B45=E6=9C=889=E6=97=A5=
 12:21
> *=E6=94=B6=E4=BB=B6=E4=BA=BA:* Xuxiaohu
> *=E6=8A=84=E9=80=81:* stefano previdi; Stewart Bryant; Alvaro Retana (are=
tana);
> draft-ietf-spring-ipv6-use-cases.all@ietf.org; gen-art@ietf.org; IETF
> Discussion; spring@ietf.org
> *=E4=B8=BB=E9=A2=98:* Re: [spring] =E7=AD=94=E5=A4=8D: Genart last call r=
eview of
> draft-ietf-spring-ipv6-use-cases-10
>
>
>
> Hi,
>
>
>
> Can you point me to any SRv6 document mandating that such mapping MUST be
> done in a routing protocol ?
>
>
>
> Thx,
>
> R.
>
>
>
>
>
> On May 9, 2017 05:16, "Xuxiaohu" <xuxiaohu@huawei.com> wrote:
>
> Hi Robert,
>
>
>
> Except the function indicated by all zeros, it does require mappings
> between functions, function indications and locators. Take tenant network
> function as an exampleJ
>
>
>
> Best regards,
>
> Xiaohu
>
>
>
> *=E5=8F=91=E4=BB=B6=E4=BA=BA:* spring [mailto:spring-bounces@ietf.org] *=
=E4=BB=A3=E8=A1=A8 *Robert Raszuk
> *=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4:* 2017=E5=B9=B45=E6=9C=888=E6=97=A5=
 20:13
> *=E6=94=B6=E4=BB=B6=E4=BA=BA:* Stewart Bryant
> *=E6=8A=84=E9=80=81:* spring@ietf.org; IETF Discussion; gen-art@ietf.org;
> draft-ietf-spring-ipv6-use-cases.all@ietf.org; stefano previdi; Alvaro
> Retana (aretana)
> *=E4=B8=BB=E9=A2=98:* Re: [spring] Genart last call review of draft-ietf-=
spring-ipv6-use-
> cases-10
>
>
>
>
>
> Hi Stewart,
>
>
>
> > =E2=80=8B
>
> Yes, but those are required anyway to support SRv6
>
>
>
> That is incorrect.
>
>
>
> Please watch Les's presentation during last IETF where he clearly and
> correctly stated that IGP extensions for SRv6 are optional and not requir=
ed
> (unlike in the case of SR-MPLS where such signalling of global labels is
> indeed necessary to build "global labels" based forwarding).
>
>
>
> As a matter of fact I knew this will generate confusion in IETF and
> recommended to make it very clear in the drafts. Distribution of SID
> functions does not need to be carried in routing protocols. And SRv6 SID
> locator function is native to IPv6 routing hence no extensions needed. Su=
re
> they can be carried in IGPs or BGP but this is just an option not
> necessity.
>
>
>
> Best,
>
> Robert.
>
>
>
>
>
>
>
> On Mon, May 8, 2017 at 12:15 PM, Stewart Bryant <stewart.bryant@gmail.com=
>
> wrote:
>
>
>
> On 05/05/2017 11:17, Robert Raszuk wrote:
>
> And to add one observation ..
>
> Stewart makes a point that SR-MPLS can be deployed without mpls control
> plane.
>
> Well it sure does not require LDP however IGP or BGP extensions for
> SR-MPLS signalling is also an example of mpls control plane ... even if
> much simpler than traditional cases it is still required.
>
>
>
> =E2=80=8B=E2=80=8B
>
> Yes, but those are required anyway to support SRv6. You always have to
> provide the mapping between the function, the function identifier and the
> function location.
>
> - Stewart
>
>
>
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small">Xiaohu,</div><div class=3D"gmail_defaul=
t" style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br></d=
iv><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-s=
erif;font-size:small">Mapping can be also well known .. for example from th=
e RFC clearly defining the functions. That clearly removes the need of *any=
* control plane to dynamically carry the values.=C2=A0</div><div class=3D"g=
mail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:sma=
ll"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,helve=
tica,sans-serif;font-size:small">Cheers,<br>R.</div></div><div class=3D"gma=
il_extra"><br><div class=3D"gmail_quote">On Tue, May 9, 2017 at 7:06 AM, Xu=
xiaohu <span dir=3D"ltr">&lt;<a href=3D"mailto:xuxiaohu@huawei.com" target=
=3D"_blank">xuxiaohu@huawei.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">





<div lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple">
<div class=3D"m_7291623561399760046WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Nobody sai=
d that such mapping must be distributed in a routing protocol</span><span l=
ang=3D"EN-US" style=3D"font-size:16.0pt;font-family:Wingdings;color:#1f497d=
">J</span><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-family:&quot;=
Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0=C2=A0
 We just said that such mapping is always required no matter we use an MPLS=
 label as function instruction or using the latter part of an IPv6 address =
as function instruction.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=
=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Best regar=
ds,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Xiaohu<u><=
/u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=
=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=
=A0<u></u></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 #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt">=E5=8F=91=E4=BB=
=B6=E4=BA=BA<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt"> <a href=3D"mailto:rraszuk@gmail.com" target=3D"_b=
lank">rraszuk@gmail.com</a> [mailto:<a href=3D"mailto:rraszuk@gmail.com" ta=
rget=3D"_blank">rraszuk@gmail.com</a>]
</span><b><span style=3D"font-size:10.0pt">=E4=BB=A3=E8=A1=A8 </span></b><s=
pan lang=3D"EN-US" style=3D"font-size:10.0pt">Robert Raszuk<br>
</span><b><span style=3D"font-size:10.0pt">=E5=8F=91=E9=80=81=E6=97=B6=E9=
=97=B4<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" style=3D=
"font-size:10.0pt"> 2017</span><span style=3D"font-size:10.0pt">=E5=B9=B4<s=
pan lang=3D"EN-US">5</span>=E6=9C=88<span lang=3D"EN-US">9</span>=E6=97=A5<=
span lang=3D"EN-US"> 12:21<br>
</span><b>=E6=94=B6=E4=BB=B6=E4=BA=BA<span lang=3D"EN-US">:</span></b><span=
 lang=3D"EN-US"> Xuxiaohu<br>
</span><b>=E6=8A=84=E9=80=81<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> stefano previdi; Stewart Bryant; Alvaro Retana (aretana); <a href=
=3D"mailto:draft-ietf-spring-ipv6-use-cases.all@ietf.org" target=3D"_blank"=
>draft-ietf-spring-ipv6-use-<wbr>cases.all@ietf.org</a>; <a href=3D"mailto:=
gen-art@ietf.org" target=3D"_blank">gen-art@ietf.org</a>; IETF Discussion; =
<a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf.org</a><br=
>
</span><b>=E4=B8=BB=E9=A2=98<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> Re: [spring] </span>
=E7=AD=94=E5=A4=8D<span lang=3D"EN-US">: Genart last call review of draft-i=
etf-spring-ipv6-use-<wbr>cases-10<u></u><u></u></span></span></p>
</div>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi,<u></u><u></u></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Can you point me to any SRv6 do=
cument mandating that such mapping MUST be done in a routing protocol ?<u><=
/u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thx,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">R.<u></u><u></u></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">On May 9, 2017 05:16, &quot;Xux=
iaohu&quot; &lt;<a href=3D"mailto:xuxiaohu@huawei.com" target=3D"_blank">xu=
xiaohu@huawei.com</a>&gt; wrote:<u></u><u></u></span></p>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi Robert,=
</span><span lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</sp=
an><span lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Except the=
 function indicated by all zeros, it does require mappings between function=
s,
 function indications and locators. Take tenant network function as an exam=
ple</span><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-family:Wingdi=
ngs;color:#1f497d">J</span><span lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</sp=
an><span lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Best regar=
ds,</span><span lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Xiaohu</sp=
an><span lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</sp=
an><span lang=3D"EN-US"><u></u><u></u></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 #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt">=E5=8F=91=E4=BB=
=B6=E4=BA=BA<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt"> spring [mailto:<a href=3D"mailto:spring-bounces@i=
etf.org" target=3D"_blank">spring-bounces@ietf.<wbr>org</a>]
</span><b><span style=3D"font-size:10.0pt">=E4=BB=A3=E8=A1=A8 </span></b><s=
pan lang=3D"EN-US" style=3D"font-size:10.0pt">Robert Raszuk<br>
</span><b><span style=3D"font-size:10.0pt">=E5=8F=91=E9=80=81=E6=97=B6=E9=
=97=B4<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" style=3D=
"font-size:10.0pt"> 2017</span><span style=3D"font-size:10.0pt">=E5=B9=B4<s=
pan lang=3D"EN-US">5</span>=E6=9C=88<span lang=3D"EN-US">8</span>=E6=97=A5<=
span lang=3D"EN-US"> 20:13<br>
</span><b>=E6=94=B6=E4=BB=B6=E4=BA=BA<span lang=3D"EN-US">:</span></b><span=
 lang=3D"EN-US"> Stewart Bryant<br>
</span><b>=E6=8A=84=E9=80=81<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> <a href=3D"mailto:spring@ietf.org" target=3D"_blank">
spring@ietf.org</a>; IETF Discussion; <a href=3D"mailto:gen-art@ietf.org" t=
arget=3D"_blank">
gen-art@ietf.org</a>; <a href=3D"mailto:draft-ietf-spring-ipv6-use-cases.al=
l@ietf.org" target=3D"_blank">
draft-ietf-spring-ipv6-use-<wbr>cases.all@ietf.org</a>; stefano previdi; Al=
varo Retana (aretana)<br>
</span><b>=E4=B8=BB=E9=A2=98<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> Re: [spring] Genart last call review of draft-ietf-spring-ipv6-use-=
<wbr>cases-10</span></span><span lang=3D"EN-US"><u></u><u></u></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">=C2=A0</span><span lang=3D"EN-US"><u></u><u=
></u></span></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">Hi Stewart,</span><span lang=3D"EN-US"><u><=
/u><u></u></span></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">=C2=A0</span><span lang=3D"EN-US"><u></u><u=
></u></span></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">&gt; =E2=80=8B</span><span lang=3D"EN-US"><=
u></u><u></u></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">Yes, but those are required anyway to suppo=
rt SRv6</span><span lang=3D"EN-US"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">=C2=A0</span><span lang=3D"EN-US"><u></u><u=
></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">That is incorrect.=C2=A0</span><span lang=
=3D"EN-US"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">=C2=A0</span><span lang=3D"EN-US"><u></u><u=
></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">Please watch Les&#39;s presentation during =
last IETF where he clearly and correctly stated that IGP extensions for SRv=
6 are
 optional and not required (unlike in the case of SR-MPLS where such signal=
ling of global labels is indeed necessary to build &quot;global labels&quot=
; based forwarding).=C2=A0</span><span lang=3D"EN-US"><u></u><u></u></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">=C2=A0</span><span lang=3D"EN-US"><u></u><u=
></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">As a matter of fact I knew this will genera=
te confusion in IETF and recommended to make it very clear in the drafts.
 Distribution of SID functions does not need to be carried in routing proto=
cols. And SRv6 SID locator function is native to IPv6 routing hence no exte=
nsions needed. Sure they can be carried in IGPs or BGP but this is just an =
option not necessity.=C2=A0</span><span lang=3D"EN-US"><u></u><u></u></span=
></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">=C2=A0</span><span lang=3D"EN-US"><u></u><u=
></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">Best,</span><span lang=3D"EN-US"><u></u><u>=
</u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">Robert.</span><span lang=3D"EN-US"><u></u><=
u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">=C2=A0</span><span lang=3D"EN-US"><u></u><u=
></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">=C2=A0</span><span lang=3D"EN-US"><u></u><u=
></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">On Mon, May 8, 2017 at 12:15 PM=
, Stewart Bryant &lt;<a href=3D"mailto:stewart.bryant@gmail.com" target=3D"=
_blank">stewart.bryant@gmail.com</a>&gt; wrote:<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><br>
<br>
<span class=3D"m_7291623561399760046m-6070289715234172439gmail-">On 05/05/2=
017 11:17, Robert Raszuk wrote:</span><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">And to add one observation ..<b=
r>
<br>
Stewart makes a point that SR-MPLS can be deployed without mpls control pla=
ne.<br>
<br>
Well it sure does not require LDP however IGP or BGP extensions for SR-MPLS=
 signalling is also an example of mpls control plane ... even if much simpl=
er than traditional cases it is still required.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;">=E2=80=8B=E2=80=8B</span><span lang=3D"EN-U=
S"><u></u><u></u></span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
Yes, but those are required anyway to support SRv6. You always have to prov=
ide the mapping between the function, the function identifier and the funct=
ion location.<span style=3D"color:#888888"><br>
<br>
<span class=3D"m_7291623561399760046m-6070289715234172439gmail-hoenzb">- St=
ewart</span></span><u></u><u></u></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
<br>
______________________________<wbr>_________________<br>
spring mailing list<br>
<a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/spring" target=3D"_blank">=
https://www.ietf.org/mailman/<wbr>listinfo/spring</a><u></u><u></u></span><=
/p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
</div>
</div>
</div>
</div></div></div>
</div>
</div>

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

--001a114043b087ec9c054f1119e3--


From nobody Tue May  9 01:47:37 2017
Return-Path: <zhencao.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 6AAEE129B4B; Tue,  9 May 2017 01:47:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Zhen Cao <zhencao.ietf@gmail.com>
To: <int-dir@ietf.org>
Cc: manet@ietf.org, ietf@ietf.org, draft-ietf-manet-olsrv2-multipath.all@ietf.org
Subject: Intdir telechat review of draft-ietf-manet-olsrv2-multipath-12
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149431964538.10555.11264594833770083998@ietfa.amsl.com>
Date: Tue, 09 May 2017 01:47:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0mjnC8v2c7gUPIenBmQT_bHeksU>
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, 09 May 2017 08:47:25 -0000

Reviewer: Zhen Cao
Review result: Ready with Issues

I am an assigned INT directorate reviewer for this draft. These
comments were written primarily for the benefit of the Internet Area
Directors. Document editors and shepherds should treat these comments
just like they would treat comments from any other IETF contributors
and resolve them along with any other Last Call comments that have
been received. For more details of the INT directorate, see
<http://www.ietf.org/iesg/directorate.html>.

I believe this document is ready to publish almost as it is. 

One issue I found during my review lies in Sec. 8.4 where IPv4 loose
source routing being discussed.  To avoid unnecessary fragmentation, I
am suggesting the following wording change: 

S/  If the length of the path (n) is greater than MAX_SRC_HOPS
      (Section 5), only the "key" routers in the path are kept...
/  If the length of the path (n) is greater than MAX_SRC_HOPS 
      (Section 5), or the adding of source routing header exceeds the
path MTU, 
only the "key" routers in the path are kept...

Cheers,
Zhen




From nobody Tue May  9 03:13:38 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 BCF75129BA3; Tue,  9 May 2017 03:13:36 -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, RP_MATCHES_RCVD=-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 IxeZOp4pJJK4; Tue,  9 May 2017 03:13:35 -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 E52701200F3; Tue,  9 May 2017 03:13:33 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.38,313,1491260400"; d="scan'208";a="181637638"
Received: from unknown (HELO baemasmds016.greenlnk.net) ([10.15.207.101]) by ukmta1.baesystems.com with ESMTP; 09 May 2017 11:13:31 +0100
X-IronPort-AV: E=Sophos;i="5.38,313,1491260400"; d="scan'208";a="170502794"
Received: from glkxh0002v.greenlnk.net ([10.109.2.33]) by baemasmds016.greenlnk.net with ESMTP; 09 May 2017 11:13:12 +0100
Received: from GLKXM0003V.GREENLNK.net ([169.254.4.172]) by GLKXH0002V.GREENLNK.net ([10.109.2.33]) with mapi id 14.03.0248.002; Tue, 9 May 2017 11:13:12 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
CC: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multipath@ietf.org" <draft-ietf-manet-olsrv2-multipath@ietf.org>, "manet-chairs@ietf.org" <manet-chairs@ietf.org>
Subject: RE: [manet] Last Call: <draft-ietf-manet-olsrv2-multipath-12.txt> (Multi-path Extension for the Optimized Link State Routing Protocol version 2 (OLSRv2)) to Experimental RFC
Thread-Topic: [manet] Last Call: <draft-ietf-manet-olsrv2-multipath-12.txt> (Multi-path Extension for the Optimized Link State Routing Protocol version 2 (OLSRv2)) to Experimental RFC
Thread-Index: AQHSuiCA8lo3GCHD2k6nFUb/R8wgmaHr37cA
Date: Tue, 9 May 2017 10:13:11 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6330DE9@GLKXM0003v.GREENLNK.net>
References: <149272508088.22258.8263343290438640855.idtracker@ietfa.amsl.com>
In-Reply-To: <149272508088.22258.8263343290438640855.idtracker@ietfa.amsl.com>
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="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jT7BE13E75c536KGXk5NIdPzTsg>
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, 09 May 2017 10:13:37 -0000

A few comments on this draft.

IPv6 specifies complete source routing. But this specification can only con=
sider what happens within the MANET. So for a packet from somewhere in the =
MANET to somewhere well outside the MANET, the packet must be source routed=
 to the gateway between MANET and rest of Internet, and not source routed a=
fter that. This I think should be explicitly mentioned. Whether that is con=
sidered compliant with IPv6 I leave to others.

7.1 SR_addr would better say "originator" address rather than "network" add=
ress. (That makes it an address without a netmask, see RFC 7181.)

8.1 This is suggesting creating TC messages that have on neighbour addresse=
s but have only a SOURCE_ROUTE TLV. This is not the design I would have sug=
gested as consistent with how I would expect an extension to OLSRv2 to do t=
hings. We need to consider two kinds of routers: those sending TC messages =
anyway, those that (other than this extension) do not. In the former case y=
ou could just add the SOURCE_ROUTE TLV to those TC messages it sends. Then =
that information is maintained up to date. Routers that don't usually send =
TC messages could send TC messages with just that TLV. But then there's an =
issue over validity time. A parameter SR_HOLD_TIME_MULTIPLIER is introduced=
. There's no need for that - you can simply incorporate that into the valid=
ity time recorded in the message. That avoids a need to handle the two case=
s of routers differently. There is then an oddity that you get some routers=
 sending TC messages with normal validity times and addresses, and some tha=
t can be sent less frequently with no addresses and longer validity times. =
But that's suspect - note that it's not done in OLSRv2 for attached network=
s (another reason to send TC messages although no neighbours need reporting=
). That's because longer intervals make reacting to new routers joining (an=
d network reassembly after fragmentation) slow. Rather a better design woul=
d simply be to add SOURCE_ROUTE TLV to normal TC messages. When sending TC =
messages for just that reason, that could be just the usual case, but you c=
ould allow as an option in this case to send less frequently with validity =
time increased accordingly. When not using that option, once a router needs=
 to send a TC message, it could then decide to report neighbours, increasin=
g the topology distributed and allowing more routes, this also being an opt=
ion.

8.3 second bullet. You should here (and possibly elsewhere) exclude routers=
 with routing willingness zero.

8.3 there seems to be an inconsistency. When operating proactively and no m=
ultiple routes, drop the packet, but reactively use standard routing. The l=
atter seems more appropriate in the former case also.

9 CUTOFF_RATIO. Insists of strictly, but as defined earlier, may be >=3D 1`.

-- =

Christopher Dearlove
Senior Principal Engineer
BAE Systems Applied Intelligence Laboratories
__________________________________________________________________________

T: =A0+44 3300 467500 =A0| =A0E: chris.dearlove@baesystems.com

BAE Systems Applied Intelligence, Chelmsford Technology Park, Great Baddow,=
 Chelmsford, Essex CM2 8HN.
www.baesystems.com/ai
BAE Systems Applied Intelligence Limited
Registered in England & Wales No: 01337451
Registered Office: Surrey Research Park, Guildford, Surrey, GU2 7YP


-----Original Message-----
From: manet [mailto:manet-bounces@ietf.org] On Behalf Of The IESG
Sent: 20 April 2017 22:51
To: IETF-Announce
Cc: manet@ietf.org; draft-ietf-manet-olsrv2-multipath@ietf.org; manet-chair=
s@ietf.org
Subject: [manet] Last Call: <draft-ietf-manet-olsrv2-multipath-12.txt> (Mul=
ti-path Extension for the Optimized Link State Routing Protocol version 2 (=
OLSRv2)) to Experimental RFC

----------------------! WARNING ! ---------------------- This message origi=
nates from outside our organisation, either from an external partner or fro=
m the internet.
Consider carefully whether you should click on any links, open any attachme=
nts or reply.
Follow the 'Report Suspicious Emails' link on IT matters for instructions o=
n reporting suspicious email messages.
--------------------------------------------------------

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.


The IESG has received a request from the Mobile Ad-hoc Networks WG
(manet) to consider the following document:
- 'Multi-path Extension for the Optimized Link State Routing Protocol
   version 2 (OLSRv2)'
  <draft-ietf-manet-olsrv2-multipath-12.txt> as Experimental RFC

The IESG plans to make a decision in the next few weeks, and solicits final=
 comments on this action. Please send substantive comments to the ietf@ietf=
.org mailing lists by 2017-05-04. Exceptionally, comments may be sent to ie=
sg@ietf.org instead. In either case, please retain the beginning of the Sub=
ject line to allow automated sorting.

Abstract


   This document specifies a multi-path extension for the Optimized Link
   State Routing Protocol version 2 (OLSRv2) to discover multiple
   disjoint paths, so as to improve reliability of the OLSRv2 protocol.
   The interoperability with OLSRv2 is retained.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-multipath/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-multipath/ballot/


No IPR declarations have been submitted directly on this I-D.




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


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From nobody Tue May  9 08:52:23 2017
Return-Path: <chair@ietf.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 F3E0412E052 for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 08:52:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level: 
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_50=0.8, 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 AAWb8eZXBfhd for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 08:52:21 -0700 (PDT)
Received: from [10.128.65.37] (unknown [66.201.36.5]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 84E8412E856 for <ietf@ietf.org>; Tue,  9 May 2017 08:52:01 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9995F830-0C42-4505-8577-6B1C3021AAD4"
Reply-To: Chair Ietf <chair@ietf.org>, IETF Discussion <ietf@ietf.org>
Subject: Looking Ahead, Facing Change
Date: Tue, 9 May 2017 08:52:00 -0700
Message-Id: <E6E88ACA-3BA6-4A4D-91A7-510CC8509F99@ietf.org>
To: IETF Discussion <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/URNBUupwKjb9fSa6mhraUOoG8po>
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, 09 May 2017 15:52:22 -0000

--Apple-Mail=_9995F830-0C42-4505-8577-6B1C3021AAD4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I put a few reflections up on the blog today: =
https://www.ietf.org/blog/2017/05/looking-ahead-facing-change/ =
<https://www.ietf.org/blog/2017/05/looking-ahead-facing-change/>

Alissa Cooper
IETF Chair



--Apple-Mail=_9995F830-0C42-4505-8577-6B1C3021AAD4
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="">I put a few reflections up on the blog today:&nbsp;<a href="https://www.ietf.org/blog/2017/05/looking-ahead-facing-change/" class="">https://www.ietf.org/blog/2017/05/looking-ahead-facing-change/</a><div class=""><br class=""></div><div class="">Alissa Cooper</div><div class="">IETF Chair<br class=""><div class=""><br class=""></div><div class=""><br class=""></div></div></body></html>
--Apple-Mail=_9995F830-0C42-4505-8577-6B1C3021AAD4--


From nobody Tue May  9 11:31:02 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 6B0F212EAD8; Tue,  9 May 2017 11:31:01 -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: i2nsf@ietf.org, ietf@ietf.org, draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org
Subject: Genart telechat review of draft-ietf-i2nsf-problem-and-use-cases-15
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149435466138.10025.5501829638513159288@ietfa.amsl.com>
Date: Tue, 09 May 2017 11:31:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/keGjPk16RBvU3FOE-xKmGFDcu0U>
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, 09 May 2017 18:31:01 -0000

Reviewer: Dale Worley
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.

Document:  draft-ietf-i2nsf-problem-and-use-cases-15
Reviewer:  Dale R. Worley
Review Date:  2017-05-09
IETF LC End Date:  2017-03-22
IESG Telechat date:  2017-05-11

Summary:

       This draft is basically ready for publication, but has nits
       that should be fixed before publication.

There is one remaining nit:

2.  Terminology

   Security Service Provider:    A provider of security services to
the
      customers (end-users or enterprises) using NSF equipment
purchased
      from vendors or created by the service provider.

Per my discussion with the authors, the intended style is to not
specifically capitalize the term "security service provider".  Hence,
this entry headword should be "Security service provider".

[END]



From nobody Tue May  9 12:01:36 2017
Return-Path: <chair@ietf.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 4026412EAF5 for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 12:01:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.189
X-Spam-Level: 
X-Spam-Status: No, score=-0.189 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_50=0.8, HTML_MESSAGE=0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DwMsgTw8sysU for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 12:01:31 -0700 (PDT)
Received: from [IPv6:2001:420:c0c8:1003::4e5] (unknown [IPv6:2001:420:c0c8:1003::4e5]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 7B4D112EAFC for <ietf@ietf.org>; Tue,  9 May 2017 12:01:20 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2BD27EF9-5EF4-4CE4-9013-557E93861E64"
Reply-To: IETF Discussion <ietf@ietf.org>
Subject: Registration for remote participation
Date: Tue, 9 May 2017 12:01:19 -0700
Message-Id: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
To: IETF Discussion <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ARWs2NaG1mOh2a6In4hgTtfH9vI>
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, 09 May 2017 19:01:34 -0000

--Apple-Mail=_2BD27EF9-5EF4-4CE4-9013-557E93861E64
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

For remote participants at IETF meetings, registration is currently =
optional. Remote participants may join a session at an IETF meeting by =
entering any name or pseudonym of their choice into the current form =
used for logging in to MeetEcho.

The IESG is soliciting community feedback on a proposal to require =
registration for remote participants at IETF meetings. The objective of =
requiring registration for real-time remote participation is to provide =
better data to the IETF community and leadership about the size and =
make-up of the remote participant base. As remote participation grows, =
having more reliable remote participation data will allow the service to =
be better tailored to those using it and the community as a whole, and =
will help us understand the potential impact of remote participation on =
in-person participation. We understand that even with required =
registration the data collected will not be perfect, complete, or =
unspoofable, but we believe it would provide a more credible basis for =
analysis than the data available today.

The proposal is as follows:

Remote participants would be required to register (for free) by =
providing the information below (* denotes required fields). =
Registration would be mandatory to access MeetEcho sessions in real time =
and to join the remote mic queue during a session.

Title
First / Given Name*
Last / Family Name*
Company / Organization
ISO 3166 Country of Residence*
Email*
Gender
Have you attended an IETF meeting in person before?
Have you attended an IETF meeting remotely before?

Upon registering, participants would be issued a registration ID, just =
as they are today.

To join a session, participants would be asked to input the registration =
ID. The same email-based facility that is currently available to =
retrieve a forgotten registration ID would continue to be available. The =
cookie-based =E2=80=9CRemember me=E2=80=9D option would also still be =
available. The only difference from how login works today is that the =
option to "Join without registration ID" would be removed. Other options =
for authentication (leveraging a user-chosen password or datatracker =
credentials) might be explored further in the future.

Remote participation registration data would be stored and secured by =
AMS and MeetEcho just as it is currently today. As is the case now, no =
registration or login would be required to access MeetEcho recordings, =
audio recordings, YouTube videos, or jabber rooms. And no changes are =
being proposed as to the handling of virtual blue sheets.

We'd like to hear from the community about this proposal. Please send =
comments to ietf@ietf.org <mailto:ietf@ietf.org>, or exceptionally to =
iesg@ietf.org <mailto:iesg@ietf.org>, preferably by May 30, 2017.

Thanks,
The IESG



--Apple-Mail=_2BD27EF9-5EF4-4CE4-9013-557E93861E64
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""><div class=3D"">For remote participants at =
IETF meetings, registration is currently optional. Remote participants =
may join a session at an IETF meeting by entering any name or pseudonym =
of their choice into the current form used for logging in to =
MeetEcho.</div><div class=3D""><br class=3D""></div><div class=3D"">The =
IESG is soliciting community feedback on a proposal to require =
registration for remote participants at IETF meetings. The objective of =
requiring registration for real-time remote participation is to provide =
better data to the IETF community and leadership about the size and =
make-up of the remote participant base. As remote participation grows, =
having more reliable remote participation data will allow the service to =
be better tailored to those using it and the community as a whole, and =
will help us understand the potential impact of remote participation on =
in-person participation. We understand that even with required =
registration the data collected will not be perfect, complete, or =
unspoofable, but we believe it would provide a more credible basis for =
analysis than the data available today.</div><div class=3D""><br =
class=3D""></div><div class=3D"">The proposal is as follows:</div><div =
class=3D""><br class=3D""></div><div class=3D"">Remote participants =
would be required to register (for free) by providing the information =
below (* denotes required fields). Registration would be mandatory to =
access MeetEcho sessions in real time and to join the remote mic queue =
during a session.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Title</div><div class=3D"">First / Given Name*</div><div =
class=3D"">Last / Family Name*</div><div class=3D"">Company / =
Organization</div><div class=3D"">ISO 3166 Country of =
Residence*</div><div class=3D"">Email*</div><div =
class=3D"">Gender</div><div class=3D"">Have you attended an IETF meeting =
in person before?</div><div class=3D"">Have you attended an IETF meeting =
remotely before?</div><div class=3D""><br class=3D""></div><div =
class=3D"">Upon registering, participants would be issued a registration =
ID, just as they are today.</div><div class=3D""><br class=3D""></div><div=
 class=3D"">To join a session, participants would be asked to input the =
registration ID. The same email-based facility that is currently =
available to retrieve a forgotten registration ID would continue to be =
available. The cookie-based =E2=80=9CRemember me=E2=80=9D option would =
also still be available. The only difference from how login works today =
is that the option to "Join without registration ID" would be removed. =
Other options for authentication (leveraging a user-chosen password or =
datatracker credentials) might be explored further in the =
future.</div><div class=3D""><br class=3D""></div><div class=3D"">Remote =
participation registration data would be stored and secured by AMS and =
MeetEcho just as it is currently today. As is the case now, no =
registration or login would be required to access MeetEcho recordings, =
audio recordings, YouTube videos, or jabber rooms. And no changes are =
being proposed as to the handling of virtual blue sheets.</div><div =
class=3D""><br class=3D""></div><div class=3D"">We'd like to hear from =
the community about this proposal. Please send comments to&nbsp;<a =
href=3D"mailto:ietf@ietf.org" class=3D"">ietf@ietf.org</a>, or =
exceptionally to&nbsp;<a href=3D"mailto:iesg@ietf.org" =
class=3D"">iesg@ietf.org</a>, preferably by May 30, =
2017.</div></div><div class=3D""><br class=3D""></div><div =
class=3D"">Thanks,</div><div class=3D"">The IESG</div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_2BD27EF9-5EF4-4CE4-9013-557E93861E64--


From nobody Tue May  9 13:08:56 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
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 E0A1212EAFA for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 13:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level: 
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_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=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fJx4H0MKmazo for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 13:08:52 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 879AF129687 for <ietf@ietf.org>; Tue,  9 May 2017 13:08:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id E42C6BE7C for <ietf@ietf.org>; Tue,  9 May 2017 21:08:49 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CagcbFtAjdF3 for <ietf@ietf.org>; Tue,  9 May 2017 21:08:48 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id B10F1BDCC for <ietf@ietf.org>; Tue,  9 May 2017 21:08:47 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1494360528; bh=oDIvnS0XpitLQWiwF6wramDit38SVJxZ1fcTkRWl+fM=; h=Subject:To:References:From:Date:In-Reply-To:From; b=TTBX0Jhdjjr3HyRPEI6ikSVKhXMyDpjvqHPti+0wG95q++/u8UKBS6blaebN7OEMP dwaNkuSDKpt4UWDlSh+kouBIV4ZV6TqIXPFxPv7Do1RmPdtUnLd6RTYLKdCOchS3IU TSjqM2XJpDIk8HBhQUf6VX3wcReAZZB8EkLIxwCk=
Subject: Re: Registration for remote participation
To: IETF Discussion <ietf@ietf.org>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <c1f0f773-4842-e413-e6df-dcbf27b94235@cs.tcd.ie>
Date: Tue, 9 May 2017 21:08:46 +0100
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: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="o0e7PQu7EHj7QrVKRfDWmxCKEtaVXAh2I"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZABIqq3Tu5XZixepnt4oXa0QoTU>
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, 09 May 2017 20:08:55 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--o0e7PQu7EHj7QrVKRfDWmxCKEtaVXAh2I
Content-Type: multipart/mixed; boundary="P1fNmfaF1W48R4tC2kREmkxAn9OGm3FVu";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: IETF Discussion <ietf@ietf.org>
Message-ID: <c1f0f773-4842-e413-e6df-dcbf27b94235@cs.tcd.ie>
Subject: Re: Registration for remote participation
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
In-Reply-To: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>

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


No major objection but a few minor comments:-

- I'd be happier if there was a re-iteration that we're not going
to charge remote folks until the remote input experience is much
better and the community have agreed to such charging.
- I think there ought be some ack that this policy (if applied)
may be tee-ing up charging remote folks, as something that might
be needed depending on how the remove/on-site ratios evolve. (It
seemed odd to me that charging was not mentioned.)
- IIRC, there were a couple of times in the 2 meetings when I was
remote where I needed to get in to meetecho a 2nd time with a
different ID. While that particular bug may be fixed (or maybe
was on my side, not meetecho's) it'd be a shame if folks could
not do that kind of thing. I'm not sure how that'd best be handled.

Cheers,
S.

On 09/05/17 20:01, IETF Chair wrote:
> For remote participants at IETF meetings, registration is currently opt=
ional. Remote participants may join a session at an IETF meeting by enter=
ing any name or pseudonym of their choice into the current form used for =
logging in to MeetEcho.
>=20
> The IESG is soliciting community feedback on a proposal to require regi=
stration for remote participants at IETF meetings. The objective of requi=
ring registration for real-time remote participation is to provide better=
 data to the IETF community and leadership about the size and make-up of =
the remote participant base. As remote participation grows, having more r=
eliable remote participation data will allow the service to be better tai=
lored to those using it and the community as a whole, and will help us un=
derstand the potential impact of remote participation on in-person partic=
ipation. We understand that even with required registration the data coll=
ected will not be perfect, complete, or unspoofable, but we believe it wo=
uld provide a more credible basis for analysis than the data available to=
day.
>=20
> The proposal is as follows:
>=20
> Remote participants would be required to register (for free) by providi=
ng the information below (* denotes required fields). Registration would =
be mandatory to access MeetEcho sessions in real time and to join the rem=
ote mic queue during a session.
>=20
> Title
> First / Given Name*
> Last / Family Name*
> Company / Organization
> ISO 3166 Country of Residence*
> Email*
> Gender
> Have you attended an IETF meeting in person before?
> Have you attended an IETF meeting remotely before?
>=20
> Upon registering, participants would be issued a registration ID, just =
as they are today.
>=20
> To join a session, participants would be asked to input the registratio=
n ID. The same email-based facility that is currently available to retrie=
ve a forgotten registration ID would continue to be available. The cookie=
-based =E2=80=9CRemember me=E2=80=9D option would also still be available=
=2E The only difference from how login works today is that the option to =
"Join without registration ID" would be removed. Other options for authen=
tication (leveraging a user-chosen password or datatracker credentials) m=
ight be explored further in the future.
>=20
> Remote participation registration data would be stored and secured by A=
MS and MeetEcho just as it is currently today. As is the case now, no reg=
istration or login would be required to access MeetEcho recordings, audio=
 recordings, YouTube videos, or jabber rooms. And no changes are being pr=
oposed as to the handling of virtual blue sheets.
>=20
> We'd like to hear from the community about this proposal. Please send c=
omments to ietf@ietf.org <mailto:ietf@ietf.org>, or exceptionally to iesg=
@ietf.org <mailto:iesg@ietf.org>, preferably by May 30, 2017.
>=20
> Thanks,
> The IESG
>=20
>=20
>=20


--P1fNmfaF1W48R4tC2kREmkxAn9OGm3FVu--

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

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

iQEcBAEBCAAGBQJZEiHPAAoJEC88hzaAX42iBWUH/A5r9oQM6MYEAVzgWdEnsnt1
7Pl8FgvyVsCGWMhCC0W2bv+xyV/RA/01/Xos2Nq9tCsXnp1tN5zia99phiEMpNHJ
iFXSoReeglzfaiCvQNW5QuULpUxv1MfJxwR4z/HubEoG2afiYq+C3Sll5d8oT4eA
jo0zt1QiD6mIdostwiMY+ehm+narjXYe2Q7MiUuBSjCnmmjKHrwdRKl4H4/HyuH4
T+NKfoK+NbjuvRd0m376uuKp9fS04Jm0OrDH1mQ7oARThwzyBD6A7HWYqbqQ89v/
Rxeuy/WGBOb3lksaigTjFGLmh1npiyio2TyusAqayylenGkrcaylGkDr3RTuZLk=
=SsQ/
-----END PGP SIGNATURE-----

--o0e7PQu7EHj7QrVKRfDWmxCKEtaVXAh2I--


From nobody Tue May  9 13:31:08 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 BCF3912EB1B for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 13:31:04 -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 iHMZPxWE-fD5 for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 13:31:02 -0700 (PDT)
Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::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 5EF64127871 for <ietf@ietf.org>; Tue,  9 May 2017 13:31:02 -0700 (PDT)
Received: by mail-qt0-x231.google.com with SMTP id j29so11189800qtj.1 for <ietf@ietf.org>; Tue, 09 May 2017 13:31:02 -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=PF+sUZzKUtJY/zQUSWAT6uxcvx4r0UeNgYV7cnHL1HU=; b=Eu//YAsGDcOInQtZlh4ijOxtw5abK8ETzEwBMy9cPm3FN+Mwy9MZH/KV5oos8Qls+N 6zONEXndOx7RDqIn5M1UA4zHHuUk8pQu/O2TUjlSYXcaIg66uHCFKR66mZNyExg2UaZS 8PjZTqcxl4FFbCybaf9RYqChKZXQU9OLrBmuFFvVllo4GUJmnWXhZV1zMe7s2m6pD4i0 mq5yYVXxmldIykSa8lpk1uRWroi8UsyagdiTZhN3EimhLpmyYDq+QKEUdCSxNyZyQg0+ LTEbjLKOhcIIs1d8p8VCJvvbK7qFda2Kx9vEsd9EDdHAJRFPNJBrEuW+O3F8I9gfN9RH Q9Yg==
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=PF+sUZzKUtJY/zQUSWAT6uxcvx4r0UeNgYV7cnHL1HU=; b=F3vimDW4kIsmQssJsbUF/jQd/xOcZPvQf+/j+A7moetQVK5dEZQ0dvYb8MACwiIJVc wtEjhlkdIdb/X5ephIK0YflH5BVsW489sY/JRUsdFfc7UiIM7t9DoeC7m3dC7jAiQGb7 iXIxtt8A07zfIiu2yVWHCBH4m1bT5O2+ZOJ9kbmAQM/aa2pA0P2SsLiD+hwR6dvKG7iP cxRUnP0WUaZ2qvQ2S1MnZiLp0NPaXrZqJYTibaaDnoIV/sYRiK4NrLiqH3od2WmaJF/Y dGS7y2Z0ScRfDB1bS+9qzUrdYRDokvxv3M/rMLshf9GAmZLtWgKkFq5StVvHTxJ2fTnN 4PZQ==
X-Gm-Message-State: AODbwcAdElKuRdd548RlJS2HQV9Cq/L9nx9tIUzPnbqjzEQtdruTkN1T j0S3ou2Tpxb3yonlluYQPeAcrtsNG8XG
X-Received: by 10.200.39.100 with SMTP id h33mr2144586qth.280.1494361861276; Tue, 09 May 2017 13:31:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.63.45 with HTTP; Tue, 9 May 2017 13:30:30 -0700 (PDT)
In-Reply-To: <c1f0f773-4842-e413-e6df-dcbf27b94235@cs.tcd.ie>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <c1f0f773-4842-e413-e6df-dcbf27b94235@cs.tcd.ie>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 9 May 2017 13:30:30 -0700
Message-ID: <CA+9kkMAEtMXQ0MVXWX3nTcmi1oCsMq8JcdNPJqLTU1gM2nz74Q@mail.gmail.com>
Subject: Re: Registration for remote participation
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a11403a52e848a7054f1d3be8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/c5I12otj0tU97HH1eYQh8Y_vryY>
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, 09 May 2017 20:31:05 -0000

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

Hi Stephen,

On Tue, May 9, 2017 at 1:08 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
> No major objection but a few minor comments:-
>
> - I'd be happier if there was a re-iteration that we're not going
> to charge remote folks until the remote input experience is much
> better and the community have agreed to such charging.
> - I think there ought be some ack that this policy (if applied)
> may be tee-ing up charging remote folks, as something that might
> be needed depending on how the remove/on-site ratios evolve. (It
> seemed odd to me that charging was not mentioned.)
>


As someone who argued against mentioning registration fees when Alissa
shared a draft, you can at least partially blame me for the oddity.  I
still don't think it belongs in this message, because what we face at the
moment is data so noisy that we can't tell how many people we're serving at
all nor who and where they are.  Because we can't tell who we're serving,
we can't tell whether the service is fit for the purpose very easily.

If they are primarily folks in the hotel, who can't be in two rooms at
once, we have one set of issues; if they are primarily folks at the end of
low bandwidth, high RTT paths to the venue, we have a very different set of
issues.  We also don't know reliably whether we have a small coterie of
very dedicated remote participants or a wide smattering of folks dipping
their toes in for a session or two.

We need that data first.

Once we have it, there may be many things in the set of ways to support the
service that come to light; since those might be fund raising from external
parties rather than charging, I don't think we ought to anticipate that
stage at this one.

Hope that makes sense,

Ted




> - IIRC, there were a couple of times in the 2 meetings when I was
> remote where I needed to get in to meetecho a 2nd time with a
> different ID. While that particular bug may be fixed (or maybe
> was on my side, not meetecho's) it'd be a shame if folks could
> not do that kind of thing. I'm not sure how that'd best be handled.
>
> Cheers,
> S.
>
> On 09/05/17 20:01, IETF Chair wrote:
> > For remote participants at IETF meetings, registration is currently
> optional. Remote participants may join a session at an IETF meeting by
> entering any name or pseudonym of their choice into the current form used
> for logging in to MeetEcho.
> >
> > The IESG is soliciting community feedback on a proposal to require
> registration for remote participants at IETF meetings. The objective of
> requiring registration for real-time remote participation is to provide
> better data to the IETF community and leadership about the size and make-=
up
> of the remote participant base. As remote participation grows, having mor=
e
> reliable remote participation data will allow the service to be better
> tailored to those using it and the community as a whole, and will help us
> understand the potential impact of remote participation on in-person
> participation. We understand that even with required registration the dat=
a
> collected will not be perfect, complete, or unspoofable, but we believe i=
t
> would provide a more credible basis for analysis than the data available
> today.
> >
> > The proposal is as follows:
> >
> > Remote participants would be required to register (for free) by
> providing the information below (* denotes required fields). Registration
> would be mandatory to access MeetEcho sessions in real time and to join t=
he
> remote mic queue during a session.
> >
> > Title
> > First / Given Name*
> > Last / Family Name*
> > Company / Organization
> > ISO 3166 Country of Residence*
> > Email*
> > Gender
> > Have you attended an IETF meeting in person before?
> > Have you attended an IETF meeting remotely before?
> >
> > Upon registering, participants would be issued a registration ID, just
> as they are today.
> >
> > To join a session, participants would be asked to input the registratio=
n
> ID. The same email-based facility that is currently available to retrieve=
 a
> forgotten registration ID would continue to be available. The cookie-base=
d
> =E2=80=9CRemember me=E2=80=9D option would also still be available. The o=
nly difference
> from how login works today is that the option to "Join without registrati=
on
> ID" would be removed. Other options for authentication (leveraging a
> user-chosen password or datatracker credentials) might be explored furthe=
r
> in the future.
> >
> > Remote participation registration data would be stored and secured by
> AMS and MeetEcho just as it is currently today. As is the case now, no
> registration or login would be required to access MeetEcho recordings,
> audio recordings, YouTube videos, or jabber rooms. And no changes are bei=
ng
> proposed as to the handling of virtual blue sheets.
> >
> > We'd like to hear from the community about this proposal. Please send
> comments to ietf@ietf.org <mailto:ietf@ietf.org>, or exceptionally to
> iesg@ietf.org <mailto:iesg@ietf.org>, preferably by May 30, 2017.
> >
> > Thanks,
> > The IESG
> >
> >
> >
>
>

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

<div dir=3D"ltr"><div>Hi Stephen,<br></div><div class=3D"gmail_extra"><br><=
div class=3D"gmail_quote">On Tue, May 9, 2017 at 1:08 PM, Stephen Farrell <=
span dir=3D"ltr">&lt;<a href=3D"mailto:stephen.farrell@cs.tcd.ie" target=3D=
"_blank">stephen.farrell@cs.tcd.ie</a>&gt;</span> wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><br>
No major objection but a few minor comments:-<br>
<br>
- I&#39;d be happier if there was a re-iteration that we&#39;re not going<b=
r>
to charge remote folks until the remote input experience is much<br>
better and the community have agreed to such charging.<br>
- I think there ought be some ack that this policy (if applied)<br>
may be tee-ing up charging remote folks, as something that might<br>
be needed depending on how the remove/on-site ratios evolve. (It<br>
seemed odd to me that charging was not mentioned.)<br></blockquote><div><br=
><br>As someone who argued against mentioning=20
registration fees when Alissa shared a draft, you can at least partially
 blame me for the oddity.=C2=A0 I still don&#39;t think it belongs in this =
message, because what we face at the moment is data so noisy that we can&#3=
9;t tell how many people we&#39;re serving at all nor who and where they ar=
e.=C2=A0 Because we can&#39;t tell who we&#39;re serving, we can&#39;t tell=
 whether the service is fit for the purpose very easily.<br><br>If they are=
 primarily folks in the hotel, who can&#39;t be in two rooms at once, we ha=
ve one set of issues; if they are primarily folks at the end of low bandwid=
th, high RTT paths to the venue, we have a very different set of issues.=C2=
=A0 We also don&#39;t know reliably whether we have a small coterie of very=
 dedicated remote participants or a wide smattering of folks dipping their =
toes in for a session or two.=C2=A0 <br></div><div><br></div><div>We need t=
hat data first.=C2=A0 <br><br>Once we have it, there may be many things in =
the set of ways to support the service that come to light; since those migh=
t be fund raising from external parties rather than charging, I don&#39;t t=
hink we ought to anticipate that stage at this one.<br><br></div><div>Hope =
that makes sense,<br><br></div><div>Ted<br></div><div><br></div><div>=C2=A0=
<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">
- IIRC, there were a couple of times in the 2 meetings when I was<br>
remote where I needed to get in to meetecho a 2nd time with a<br>
different ID. While that particular bug may be fixed (or maybe<br>
was on my side, not meetecho&#39;s) it&#39;d be a shame if folks could<br>
not do that kind of thing. I&#39;m not sure how that&#39;d best be handled.=
<br>
<br>
Cheers,<br>
S.<br>
<span class=3D"gmail-"><br>
On 09/05/17 20:01, IETF Chair wrote:<br>
&gt; For remote participants at IETF meetings, registration is currently op=
tional. Remote participants may join a session at an IETF meeting by enteri=
ng any name or pseudonym of their choice into the current form used for log=
ging in to MeetEcho.<br>
&gt;<br>
&gt; The IESG is soliciting community feedback on a proposal to require reg=
istration for remote participants at IETF meetings. The objective of requir=
ing registration for real-time remote participation is to provide better da=
ta to the IETF community and leadership about the size and make-up of the r=
emote participant base. As remote participation grows, having more reliable=
 remote participation data will allow the service to be better tailored to =
those using it and the community as a whole, and will help us understand th=
e potential impact of remote participation on in-person participation. We u=
nderstand that even with required registration the data collected will not =
be perfect, complete, or unspoofable, but we believe it would provide a mor=
e credible basis for analysis than the data available today.<br>
&gt;<br>
&gt; The proposal is as follows:<br>
&gt;<br>
&gt; Remote participants would be required to register (for free) by provid=
ing the information below (* denotes required fields). Registration would b=
e mandatory to access MeetEcho sessions in real time and to join the remote=
 mic queue during a session.<br>
&gt;<br>
&gt; Title<br>
&gt; First / Given Name*<br>
&gt; Last / Family Name*<br>
&gt; Company / Organization<br>
&gt; ISO 3166 Country of Residence*<br>
&gt; Email*<br>
&gt; Gender<br>
&gt; Have you attended an IETF meeting in person before?<br>
&gt; Have you attended an IETF meeting remotely before?<br>
&gt;<br>
&gt; Upon registering, participants would be issued a registration ID, just=
 as they are today.<br>
&gt;<br>
&gt; To join a session, participants would be asked to input the registrati=
on ID. The same email-based facility that is currently available to retriev=
e a forgotten registration ID would continue to be available. The cookie-ba=
sed =E2=80=9CRemember me=E2=80=9D option would also still be available. The=
 only difference from how login works today is that the option to &quot;Joi=
n without registration ID&quot; would be removed. Other options for authent=
ication (leveraging a user-chosen password or datatracker credentials) migh=
t be explored further in the future.<br>
&gt;<br>
&gt; Remote participation registration data would be stored and secured by =
AMS and MeetEcho just as it is currently today. As is the case now, no regi=
stration or login would be required to access MeetEcho recordings, audio re=
cordings, YouTube videos, or jabber rooms. And no changes are being propose=
d as to the handling of virtual blue sheets.<br>
&gt;<br>
</span>&gt; We&#39;d like to hear from the community about this proposal. P=
lease send comments to <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> &=
lt;mailto:<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;, or except=
ionally to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> &lt;mailto:<a=
 href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>&gt;, preferably by May 30,=
 2017.<br>
&gt;<br>
&gt; Thanks,<br>
&gt; The IESG<br>
&gt;<br>
&gt;<br>
&gt;<br>
<br>
</blockquote></div><br></div></div>

--001a11403a52e848a7054f1d3be8--


From nobody Tue May  9 13:47:00 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
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 2E85212EB39 for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 13:46:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level: 
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_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=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A7JpznWGZKgF for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 13:46:56 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3447F129A8E for <ietf@ietf.org>; Tue,  9 May 2017 13:46:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id AE423BE5B; Tue,  9 May 2017 21:46:53 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ACXBhTsKwGPw; Tue,  9 May 2017 21:46:52 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 003F4BE47; Tue,  9 May 2017 21:46:51 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1494362812; bh=bhwSthnjQuXjcEpGJXLxjUh8i5CfSsffa2EHEn6dqhQ=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=mzXMDweCmBAg7z0QzWuTflK6cvIOHi4X7ER3KjSCVQCswW+zX78CGhxh4cOKK4sUW kBZCADee4e976yy8Kf9WRmKiAXSx07OHThEMMs8gU4hhMWBU1D8KquMWEtv/JYyAqg cgvDp5rRPVDZZ/GTQU4A5uUdOVJuOSbH1mMU2oy8=
Subject: Re: Registration for remote participation
To: Ted Hardie <ted.ietf@gmail.com>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <c1f0f773-4842-e413-e6df-dcbf27b94235@cs.tcd.ie> <CA+9kkMAEtMXQ0MVXWX3nTcmi1oCsMq8JcdNPJqLTU1gM2nz74Q@mail.gmail.com>
Cc: IETF Discussion <ietf@ietf.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <955fecb4-95b2-ffd4-6acf-23edd66947bc@cs.tcd.ie>
Date: Tue, 9 May 2017 21:46:51 +0100
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: <CA+9kkMAEtMXQ0MVXWX3nTcmi1oCsMq8JcdNPJqLTU1gM2nz74Q@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="dPmTakCDfsUBctjf5ReoI7fldN6wFsNO5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Vc73atoPS3lPhk4qTQ9RtUbCjIU>
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, 09 May 2017 20:46:58 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--dPmTakCDfsUBctjf5ReoI7fldN6wFsNO5
Content-Type: multipart/mixed; boundary="DvmWvvNB8u7brSWnd9eVgg6S01p40FnQK";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Ted Hardie <ted.ietf@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>
Message-ID: <955fecb4-95b2-ffd4-6acf-23edd66947bc@cs.tcd.ie>
Subject: Re: Registration for remote participation
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
 <c1f0f773-4842-e413-e6df-dcbf27b94235@cs.tcd.ie>
 <CA+9kkMAEtMXQ0MVXWX3nTcmi1oCsMq8JcdNPJqLTU1gM2nz74Q@mail.gmail.com>
In-Reply-To: <CA+9kkMAEtMXQ0MVXWX3nTcmi1oCsMq8JcdNPJqLTU1gM2nz74Q@mail.gmail.com>

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



On 09/05/17 21:30, Ted Hardie wrote:
> We need that data first.

I agree that getting that data is a good idea and that registering
seems a not horrible mechanism in this case.

>=20
> Once we have it, there may be many things in the set of ways to support=
 the
> service that come to light; since those might be fund raising from exte=
rnal
> parties rather than charging, I don't think we ought to anticipate that=

> stage at this one.
>=20
> Hope that makes sense,

I guess. OTOH, the first thing I thought when reading the message
was "huh, why no mention of the obvious potential for charging?"
So it might have been better to explicitly say that this is not a
bait and switch, even though I'm perfectly sure it is not that:-)

Cheers,
S.


--DvmWvvNB8u7brSWnd9eVgg6S01p40FnQK--

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

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

iQEcBAEBCAAGBQJZEiq7AAoJEC88hzaAX42iiWsIAJB+SulxjyjgrS3/ydO6iIyD
Qf+hBx+l9IZsesodnRPqOfs3lalM4Y23OTwW/CCXONIpRVLOpzO51vO/q8/9dqus
KPuQjEDLiZxnpE83aFbGdPDMgPNAVj0eqU+CoiUrX13NnNjnhVzIC4YGqwZPRXf/
7tmdTfhgDuppeGAMOjAnRtNmgPJ+MUyxvl6qlyhp7piS5h8ckcgrck6GLJbAnB85
J+73Ku1alK3eCqfsZN6p5CRvO/CeHbW76UbXKy90IKAKJalD6qOEZKwBxROLG5qX
VdWoLScnpV79gWFGyk4+nKhi/+dF5BxLMl1kilZIunTU82koFd8JYtuGRf+zZd0=
=yFr4
-----END PGP SIGNATURE-----

--dPmTakCDfsUBctjf5ReoI7fldN6wFsNO5--


From nobody Tue May  9 14:07:26 2017
Return-Path: <alissa@cooperw.in>
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 3E9381292CE for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 14:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=K6c1uJJ9; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Q8hNweG5
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rtCQhA6_9GSk for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 14:07:24 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4001D129C6F for <ietf@ietf.org>; Tue,  9 May 2017 13:59:24 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id A3EAC20756 for <ietf@ietf.org>; Tue,  9 May 2017 16:59:23 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Tue, 09 May 2017 16:59:23 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:date:from:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=VvY/iYCNrluQH8QmY6SL3Cd7D6Gfr9cF0i/EeFdlgUs=; b=K6c1uJJ9 ObMIyrxZWT9CTfzjDVP/Z9kgSL2CD+whUSBkzBXQi+uYOhKogITJGU7FLcCLXt+f jCFkwwFl5CEU2TdExb+7/jSUR6qeQafmMwN3yXAYF31tkqtz4u/1Bk8Ag8mLnGC1 f+WwTsadhEwLo0mgzZmgj5xccobGkwRH/5+ps3/d2NNsPzjwNmsaKeP6kjs5KgL/ KM1nSOi3zhKKjKLlpbyOn2oeVFVktZeGK8SpeBnkW+HvlVC9Sk1/Ep2x7ovAqCTa VOvPNyVaKoivNPnF24z0AnU/Hz9CVqlHKkxUFpk4QhFIwSXu4YZvpAKOqMP7CQZG 4WVxau1UvdZsvg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:references:subject:to:x-me-sender:x-me-sender :x-sasl-enc:x-sasl-enc; s=fm1; bh=VvY/iYCNrluQH8QmY6SL3Cd7D6Gfr9 cF0i/EeFdlgUs=; b=Q8hNweG50KBxi1NAiB+ANYVDm7y7vDN/LmymBda2CNgtLJ Fcc54yAcjxj/+VJjZWsgyTxoP/8qpJj9+wQHS81zrUfE0Bl1qqxUPbZ8LhIV7boM 4rOw4qRq4MY3hR+K/MuLlZ9vvQP596ee0Z8rOeY8DlXrmo6YoRPFcxu7yDTWy8Zq PRZnlkY1inBWdhViT1If4WSHHohHPomfR1uHlAgCI5zX5FK0V0/udbUhM75i3Xjy JfkoPbNFGrTpIZuK59P0RYoqjHMi/herPrZfgysaSPEgkYFsiFTliwTRUH2sUy5w 7UEfBMEXikpog2aQ2l9mUQMDD45bQI40vRKvwPYA==
X-ME-Sender: <xms:qy0SWc5jMBTIR6quPCkuI4nk4HpDYmONBuDecKFMwhdKkr4r8D4uFQ>
X-Sasl-enc: 6xebiQfGpfjiwayBgrjlTLQzR/06QvjhmIq8w59D9e0P 1494363563
Received: from [10.24.41.93] (unknown [128.107.241.167]) by mail.messagingengine.com (Postfix) with ESMTPA id 4048A7E2E3 for <ietf@ietf.org>; Tue,  9 May 2017 16:59:23 -0400 (EDT)
From: Alissa Cooper <alissa@cooperw.in>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D96FE0FF-4CDD-4AAF-9B8A-0A10E66F1CCD"
Subject: Fwd: [Iasa20] Call for volunteers: IASA 2.0 design team
Date: Tue, 9 May 2017 13:59:22 -0700
References: <76E736E8-E7F5-45D4-ABA3-3E1766450865@cooperw.in>
To: IETF Discussion <ietf@ietf.org>
Message-Id: <B29E607B-60DD-4883-8345-742EFF619712@cooperw.in>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kQ7QM6bfGQYoaYHYNlKJikmx19c>
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, 09 May 2017 21:07:25 -0000

--Apple-Mail=_D96FE0FF-4CDD-4AAF-9B8A-0A10E66F1CCD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

FYI

> Begin forwarded message:
>=20
> From: Alissa Cooper <alissa@cooperw.in>
> Subject: [Iasa20] Call for volunteers: IASA 2.0 design team
> Date: May 9, 2017 at 1:56:50 PM PDT
> To: iasa20@ietf.org
>=20
> I think the community is at a point in the IASA 2.0 discussions where =
we are ready to form a design team to start evaluating options for the =
path forward. We have a good articulation of the set of problems we are =
facing in draft-hall-iasa20-workshops-report and =
draft-daigle-iasa-retrospective. We have some sense of the outcome =
properties that people are looking for here, based on list discussion. =
So I'd like to task a design team to go examine potential solutions to =
the problem set that fit the outcome properties, and come back to the =
community with recommended solutions. The scope of the solutions to be =
explored would include:
>=20
> - Structural and organizational changes, both externally (with ISOC =
and contractors) and internally (within the IAOC and subcommittees)
> - Changes to personnel resources, both volunteer and paid
> - Transparency changes
>=20
> For now, changes to the funding model would be out of scope to the =
extent they fall outside the categories above, although the design =
team's work should be informed by the prior discussion of funding =
challenges. The IAOC sponsorship committee is currently in the process =
of getting off the ground and I think it would make sense to have some =
of that discussion start there before merging it back in with the =
administrative discussion. And I think the administrative problems are =
articulated well enough for a team to get going with that focus.
>=20
> My hope is that the design team would have something (even an interim =
something) ready for community discussion around the time frame of IETF =
99. =46rom there we can figure out what a logical next step would be.
>=20
> If you=E2=80=99re interested in volunteering and willing to dedicate =
time to this work over the next several months, please send me email =
off-list by May 17, 2017 and I=E2=80=99ll sort out the team composition.=20=

>=20
> Thanks,
> Alissa
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20


--Apple-Mail=_D96FE0FF-4CDD-4AAF-9B8A-0A10E66F1CCD
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"">FYI<br class=3D""><div><br class=3D""><blockquote type=3D"cite"=
 class=3D""><div class=3D"">Begin forwarded message:</div><br =
class=3D"Apple-interchange-newline"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span=
 style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">From: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">Alissa Cooper &lt;<a =
href=3D"mailto:alissa@cooperw.in" class=3D"">alissa@cooperw.in</a>&gt;<br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Subject: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><b class=3D"">[Iasa20] Call for =
volunteers: IASA 2.0 design team</b><br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Date: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">May 9, 2017 at 1:56:50 PM =
PDT<br class=3D""></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span=
 style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">To: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><a =
href=3D"mailto:iasa20@ietf.org" class=3D"">iasa20@ietf.org</a><br =
class=3D""></span></div><br class=3D""><div class=3D""><div class=3D"">I =
think the community is at a point in the IASA 2.0 discussions where we =
are ready to form a design team to start evaluating options for the path =
forward. We have a good articulation of the set of problems we are =
facing in draft-hall-iasa20-workshops-report and =
draft-daigle-iasa-retrospective. We have some sense of the outcome =
properties that people are looking for here, based on list discussion. =
So I'd like to task a design team to go examine potential solutions to =
the problem set that fit the outcome properties, and come back to the =
community with recommended solutions. The scope of the solutions to be =
explored would include:<br class=3D""><br class=3D"">- Structural and =
organizational changes, both externally (with ISOC and contractors) and =
internally (within the IAOC and subcommittees)<br class=3D"">- Changes =
to personnel resources, both volunteer and paid<br class=3D"">- =
Transparency changes<br class=3D""><br class=3D"">For now, changes to =
the funding model would be out of scope to the extent they fall outside =
the categories above, although the design team's work should be informed =
by the prior discussion of funding challenges. The IAOC sponsorship =
committee is currently in the process of getting off the ground and I =
think it would make sense to have some of that discussion start there =
before merging it back in with the administrative discussion. And I =
think the administrative problems are articulated well enough for a team =
to get going with that focus.<br class=3D""><br class=3D"">My hope is =
that the design team would have something (even an interim something) =
ready for community discussion around the time frame of IETF 99. =46rom =
there we can figure out what a logical next step would be.<br =
class=3D""><br class=3D"">If you=E2=80=99re interested in volunteering =
and willing to dedicate time to this work over the next several months, =
please send me email off-list by May 17, 2017 and I=E2=80=99ll sort out =
the team composition. <br class=3D""><br class=3D"">Thanks,<br =
class=3D"">Alissa<br =
class=3D"">_______________________________________________<br =
class=3D"">iasa20 mailing list<br class=3D""><a =
href=3D"mailto:iasa20@ietf.org" class=3D"">iasa20@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/iasa20<br =
class=3D""></div></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_D96FE0FF-4CDD-4AAF-9B8A-0A10E66F1CCD--


From nobody Tue May  9 14:22:41 2017
Return-Path: <jari.arkko@piuha.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 3DBF312956C for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 14:22:40 -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, RP_MATCHES_RCVD=-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 fsOT0Q7dblHZ for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 14:22:37 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:1829::130]) by ietfa.amsl.com (Postfix) with ESMTP id 65EA012955F for <ietf@ietf.org>; Tue,  9 May 2017 14:22:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 50F962CFB5 for <ietf@ietf.org>; Wed, 10 May 2017 00:22:35 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uzmQusrqCxdh for <ietf@ietf.org>; Wed, 10 May 2017 00:22:34 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTP id 13A972CC9B for <ietf@ietf.org>; Wed, 10 May 2017 00:22:28 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Content-Type: multipart/signed; boundary="Apple-Mail=_B5EF4EBD-35D3-457D-9ED1-09892549C65A"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Registration for remote participation
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
Date: Wed, 10 May 2017 00:22:28 +0300
Message-Id: <A296FCD4-B00B-47A8-BDCF-295144F49696@piuha.net>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vNaTUAFpPbpnNsavg8SNZ4c0cGc>
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, 09 May 2017 21:22:40 -0000

--Apple-Mail=_B5EF4EBD-35D3-457D-9ED1-09892549C65A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

+1 for better data collection. We do need it.

As for other future charging developments brought up by Stephen, those =
are perhaps a point to be discussed in the later. For sure the potential =
for changing the model should be acknowledged. But, I have no reason to =
doubt that IETF=92s community=92s wishes wouldn=92t be driving whatever =
direction remote participation may develop into.

Jari


--Apple-Mail=_B5EF4EBD-35D3-457D-9ED1-09892549C65A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIcBAEBCgAGBQJZEjMUAAoJEM80gCTQU46q/KoP/A32zyPz2ncjcbw0TtIacTTk
Y3lNKqQlqG0dWL75ip7EndQL4b8R6yelKXgQu/gGG0osKxj8rNqDRu19D3UqD11r
EL2jv+S8NbK7C+jDQoTfLph4z5EXJDulV7pfytfZ3SgQoOG26iFQoIjHIUvlyItq
nVfQGku+IpXgh0hY3dUp/WqVgww0ygovbe01swfkr76upEiu9pvD8uJSkUFyw65J
/PG0AL5z4Am+dU0Lf/QjhGDtcdyJz23BhIGDqvaHFgpXUm+WDxOYBLOR5QQZt9rc
bfFqnuO5u1cskUYmFDipdC73GhElQtf2eds8A0MS1RI1fw9hxIeZ8ZQx+JibHP4c
ny/wGXJ6j3iT5NGEbTLQsyWndDXLhlTuxCIAjdpz0HiqYQ21ti1JMcXj9pvlIy4m
EWNdw10hPh2//JDMruhfo2RN/11jSM64UEIK3Ont7fBo1RhGo6cQ1OKx+x4Oi1mQ
1NrsjGTtIPMTlpn3NmawEWq4rqmAJ9fossbs1TUCqVdewDzMkZ3dOxfUqChbl8lw
NKBhk73mAgy1iBAeCKlfgGaA5x13kCs/IlsIUYcehHvDuyah7Iq7o5P7bccF5C/1
IvFiqShv3sg9nifmAx/6ly2EZNH9F2qDyVzmvUKgobb9QPj+CH92ExN+vc8hTfEy
KTy4trxstGShHp697j50
=gcQ/
-----END PGP SIGNATURE-----

--Apple-Mail=_B5EF4EBD-35D3-457D-9ED1-09892549C65A--


From nobody Tue May  9 14:30:56 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 2066F129A9C; Tue,  9 May 2017 14:30:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.703
X-Spam-Level: 
X-Spam-Status: No, score=-0.703 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 6x7EUvCv7wvd; Tue,  9 May 2017 14:30:45 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (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 58C12127977; Tue,  9 May 2017 14:30:45 -0700 (PDT)
Received: from [192.168.1.14] (unknown [124.189.96.43]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 435BF22E2B7; Tue,  9 May 2017 17:30:37 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [art] Artart last call review of draft-ietf-core-coap-tcp-tls-07
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <5E5238DC-B835-4BDF-B50D-8D594A46C4D4@tzi.org>
Date: Wed, 10 May 2017 07:30:35 +1000
Cc: art@ietf.org, draft-ietf-core-coap-tcp-tls.all@ietf.org, ietf@ietf.org, core@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <767F913A-586B-42A2-B021-F9AC5C478702@mnot.net>
References: <149179722452.3118.982908107963516290@ietfa.amsl.com> <5E5238DC-B835-4BDF-B50D-8D594A46C4D4@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/y2XCwbfI-mbh-KqSUyYTqQ6DmRw>
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, 09 May 2017 21:30:48 -0000

> On 10 Apr 2017, at 7:46 pm, Carsten Bormann <cabo@tzi.org> wrote:
>=20
>> Section 7.4 shows how to convert a "coap+ws://" URI into a "wss://"
>> URI, using a well-known URI in the "wss" scheme. However, "wss" is =
not
>> defined to use well-known URIs, so this is an invalid use.=20
>=20
> This incorrect use of RFC 5785 is indeed embarrassing.  More about =
that later.

To close this loop -- the change in -08 isn't sufficiently prominent =
IME; while the general nature of the change is listed in the Abstract, =
the actual normative text is very hard to find. Given that this is a =
pretty fundamental change in the operation of a URI scheme, I'd think it =
at least deserves its own section, if not a separate document.

Cheers,

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





From nobody Tue May  9 15:06:37 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 E8D0C12EB67 for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 15:06:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 H9556YrI6wbl for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 15:06:34 -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 16A4A12EB69 for <ietf@ietf.org>; Tue,  9 May 2017 15:06:34 -0700 (PDT)
Received: by mail-wr0-x22f.google.com with SMTP id z52so18389509wrc.2 for <ietf@ietf.org>; Tue, 09 May 2017 15:06:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=Q7ZpZbg9/9B1ZqTQlTD8Kt+FMJxkH7Hk/G83IC4+V/Y=; b=jIPRc39+u9WjZ96m26nTXKyceQRrGpi0T2Fv0d/sbQZd73lAqHyQ8Std6Nb3qFrR6r LUhqob70Y/SX+jxoS/ykTP3JBhOAnsVj0ugcmFgld1wia8v7qiZo6YWmro/7eb+87D/3 Y65p6y974u67gdypMbOa1gpXcrFVOhv1FEVzrB1GnDUcOlJRARmgaT3gVHMCkvevWnI+ NRGGBpKFpQPrF/QOJc+zGsT50h6zIzZVaddf8xH8xEsi4Zi9+TekFnRYnJw0Y73uIG+M r5wjFkLSSkpPElbt2c2IZNbhfTR/v++XeB3cf0S6Juiu1wHWspLDkZLElMoVhMkLjFe9 CH1A==
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 :subject:date:references:to:in-reply-to:message-id; bh=Q7ZpZbg9/9B1ZqTQlTD8Kt+FMJxkH7Hk/G83IC4+V/Y=; b=b9WLlkJamGXPmWoN2w+0SxXL8POoyqW8112MeVQRWxltogBRkj+8rlrBZgQneeuk/T QHmI+JykltvyrcK9CqH56V8PwW05tjf78AyEgZy7MOWLmWmm/STMg+Rq5CkPizSPULbw MTKiM5yJw7k5rgIMSyMhnslR8c00siKfJ2V2Hjs1qO46IhrJUkLgrM3rnURlM420d335 5P1jb1Ipg0I8IOj9Z5/NDXyHnQyBGK/T1UJ2UZdI+TDYKuPvqAfTQDTpYa4SBudASvjH rgc3R15l8SpaDwNHSyFqG8hYxE0OyeA3SFjhVlhZrKOi22UYft0lBmbuO16eHks8ZsTP 8h+g==
X-Gm-Message-State: AODbwcBQrnS0kRBh5WPgWTyEBKWUvWizTEKHgmu1BJvl0P2gADGgXFxT xhO5VGSIAi7lhfQOq2k=
X-Received: by 10.80.165.105 with SMTP id z38mr1669831edb.60.1494367592369; Tue, 09 May 2017 15:06:32 -0700 (PDT)
Received: from [192.168.1.18] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id b25sm1390892edc.58.2017.05.09.15.06.31 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 May 2017 15:06:31 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Registration for remote participation
Date: Wed, 10 May 2017 01:06:29 +0300
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
To: IETF Discussion <ietf@ietf.org>
In-Reply-To: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
Message-Id: <9121E962-B74F-4ADB-83E3-DD966B7352CB@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/F6SjsG23Eq4azc2SCXCNtHjJMn4>
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, 09 May 2017 22:06:36 -0000

In general, this looks fine to me.  I don=E2=80=99t believe any of the =
questions are particularly invasive, and I can see the utility of each =
of them (except Title, but that=E2=80=99s a cultural thing).

A few remarks inline

On 9 May 2017, at 22:01, IETF Chair <chair@ietf.org> wrote:

> Remote participants would be required to register (for free) by =
providing the information below (* denotes required fields). =
Registration would be mandatory to access MeetEcho sessions in real time =
and to join the remote mic queue during a session.
>=20
> Title
> First / Given Name*
> Last / Family Name*
> Company / Organization
> ISO 3166 Country of Residence*
> Email*
> Gender
> Have you attended an IETF meeting in person before?
> Have you attended an IETF meeting remotely before?

The last two questions seem to be about gathering statistics (as is the =
country of residence). I=E2=80=99m wondering if it wouldn=E2=80=99t make =
sense to add a question about why the participant is remote (too much =
travel, too much money, avoids going to country X for whatever reason).

> Upon registering, participants would be issued a registration ID, just =
as they are today.
>=20
> To join a session, participants would be asked to input the =
registration ID. The same email-based facility that is currently =
available to retrieve a forgotten registration ID would continue to be =
available. The cookie-based =E2=80=9CRemember me=E2=80=9D option would =
also still be available. The only difference from how login works today =
is that the option to "Join without registration ID" would be removed.

Does this mean that unregistered people would not be able to =
listen/view?  I=E2=80=99m fine with cutting off *participation*, but =
even before Meetecho we=E2=80=99ve had a live (audio) stream from the =
room. I wouldn=E2=80=99t want to lose that.  Recordings are good, but by =
the time you listen to a recording, the conversation may have moved on.

> If they are primarily folks in the hotel, who can't be in two rooms at =
once, we have one set of issues; if they are primarily folks at the end =
of low bandwidth, high RTT paths to the venue, we have a very different =
set of issues.  We also don't know reliably whether we have a small =
coterie of very dedicated remote participants or a wide smattering of =
folks dipping their toes in for a session or two. =20

I=E2=80=99m not sure you=E2=80=99d be collecting enough data for that. =
Specifically the country of residence is not enough.  It=E2=80=99s not =
so much that the US is high bandwidth and Russia is low bandwidth. =
It=E2=80=99s more that New York, Moscow, and San Francisco get high =
bandwidth, while Orem, UT and Donetsk might get a lot less.

Yoav



From nobody Tue May  9 15:30:06 2017
Return-Path: <farmer@umn.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 774D8127419 for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 15:30:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.601
X-Spam-Level: 
X-Spam-Status: No, score=-1.601 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xbj1LwZLmuuA for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 15:30:03 -0700 (PDT)
Received: from mta-p7.oit.umn.edu (mta-p7.oit.umn.edu [134.84.196.207]) (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 22CF412702E for <ietf@ietf.org>; Tue,  9 May 2017 15:30:02 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p7.oit.umn.edu (Postfix) with ESMTP id 68C866A0 for <ietf@ietf.org>; Tue,  9 May 2017 22:30:02 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p7.oit.umn.edu ([127.0.0.1]) by localhost (mta-p7.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O-IDt4YbPAkr for <ietf@ietf.org>; Tue,  9 May 2017 17:30:02 -0500 (CDT)
Received: from mail-ua0-f197.google.com (mail-ua0-f197.google.com [209.85.217.197]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p7.oit.umn.edu (Postfix) with ESMTPS id 2FFF16F6 for <ietf@ietf.org>; Tue,  9 May 2017 17:30:02 -0500 (CDT)
Received: by mail-ua0-f197.google.com with SMTP id g49so7788715uaa.3 for <ietf@ietf.org>; Tue, 09 May 2017 15:30:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=9AWD7VRTOONYUhMlk33SCHbdL39jN163WmHFJeRxvSY=; b=In39AjDd6RQnINvuhUEcBLncuQ1YIVt8Ed9fYx1fEGV5n6C2xshUn2pMzjkmCQcdWM zVD4gAX2oO5d67/oiHAxWiaSL64QWqMEdV6b4riA9YpX3PvnYbBPhx2VljHEG+BTrW5C osQ+FL0TggEWCgpGHHJ4qnRtdvuUzffmWgzcaVPvsgJL3ldjXxhcUqS7oNkUxLYUkqKC kPtYi4ioqB4cPksLr2wAFixfO0SS75AXMrLipQ+T/IXJb1hGi7KG/bghnEgap6Udmf0O BcoMDXP3eeJLZRFZJni6n5p1N+VQMLunNuipulIsOAj3Y/knoo1ZIg0rdc0SOUki/p3h BOsw==
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=9AWD7VRTOONYUhMlk33SCHbdL39jN163WmHFJeRxvSY=; b=OX2Qk1D0ShrummRSjPhtbJouIz4cDZammvlTi9FY+gjlXjGtKZa0dwhF9AxTa7Vi7k 3Ws2asE8sL02cxcXjIqHtM6IlLY/VuxB+gIeb7/JwJI6uqHNrR5ShCuYPX4rYKlbNd0n CwpjpLagY21bLxrKb72cV6oB4b0HGuOfz8lDhqp61WlsR6+xH9d3oEFU9H2J+Bq5PKx6 XMOeLcE0fXy0hKKD8Y228etT7PNBlbXR/hJkOdMI6wje163Uv38FBSIQrGBQ3bo+kFV4 blfZ+rNmTvK6qyShj4Y8ilv4iNsZ8r6plSVf/bCh70UVWNnwaBx7rKL2WNXZqqZt2Fgt IE5w==
X-Gm-Message-State: AODbwcCP2v5fMvbSxdm0jJW3kQaQsLfpcWZQkul7nzjzahHB6l5JGVm4 ucAliIgt/Edn/fn4+v+/msIO2T2iPylj4QGBeccToF+vs36MjW/phYPJWHGslAyD5ukESKhi/tc MTsj3z8ZakvGVl20=
X-Received: by 10.31.99.67 with SMTP id x64mr1118388vkb.24.1494369001581; Tue, 09 May 2017 15:30:01 -0700 (PDT)
X-Received: by 10.31.99.67 with SMTP id x64mr1118379vkb.24.1494369001313; Tue, 09 May 2017 15:30:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.44.137 with HTTP; Tue, 9 May 2017 15:30:00 -0700 (PDT)
In-Reply-To: <CA+9kkMAEtMXQ0MVXWX3nTcmi1oCsMq8JcdNPJqLTU1gM2nz74Q@mail.gmail.com>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <c1f0f773-4842-e413-e6df-dcbf27b94235@cs.tcd.ie> <CA+9kkMAEtMXQ0MVXWX3nTcmi1oCsMq8JcdNPJqLTU1gM2nz74Q@mail.gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Tue, 9 May 2017 17:30:00 -0500
Message-ID: <CAN-Dau1sMbQ02_Ek9+yU-XUeHK3uK7z74FGzpW8zXoZLL6-LoQ@mail.gmail.com>
Subject: Re: Registration for remote participation
To: Ted Hardie <ted.ietf@gmail.com>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c07b1187ce3d4054f1ee578
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ewg5teAD0auOSbIMEzQVlQcdSa0>
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, 09 May 2017 22:30:05 -0000

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

On Tue, May 9, 2017 at 3:30 PM, Ted Hardie <ted.ietf@gmail.com> wrote:
...

> As someone who argued against mentioning registration fees when Alissa
> shared a draft, you can at least partially blame me for the oddity.  I
> still don't think it belongs in this message, because what we face at the
> moment is data so noisy that we can't tell how many people we're serving at
> all nor who and where they are.  Because we can't tell who we're serving,
> we can't tell whether the service is fit for the purpose very easily.
>

Personally, I feel it indirectly and appropriately mentions fees, it says;
"Remote participants would be required to register (for free)"


> If they are primarily folks in the hotel, who can't be in two rooms at
> once, we have one set of issues; if they are primarily folks at the end of
> low bandwidth, high RTT paths to the venue, we have a very different set of
> issues.  We also don't know reliably whether we have a small coterie of
> very dedicated remote participants or a wide smattering of folks dipping
> their toes in for a session or two.
>

You mention the "be in two rooms at once" use case, but given the proposed
information to be requested for registration, how would you capture that
use case?  Maybe you should ask that directly, like; "Are you also
attending the meeting in person?"

Country of residence is asked for, but it sounds like you really want to
know where they will be viewing from, not where they live.  For some set of
use cases they will be aligned, but others they won't.

There is another important use case, similar to "be in two rooms at once",
that is a temporary need to leave the meeting site, such as to receive
medical treatment for chronic conditions or simply just other business in
the meeting city.  As someone who has recently began needing treatment
while traveling. You frequently have little choice over when a treatment
slot is made available to you, usually you have to take what they can give
you.  Good remote participation options, make this less burdensome.

Thanks

Once we have it, there may be many things in the set of ways to support the
> service that come to light; since those might be fund raising from external
> parties rather than charging, I don't think we ought to anticipate that
> stage at this one.
>
> Hope that makes sense,
>
> Ted
>
...

> > The proposal is as follows:
>> >
>> > Remote participants would be required to register (for free) by
>> providing the information below (* denotes required fields). Registration
>> would be mandatory to access MeetEcho sessions in real time and to join the
>> remote mic queue during a session.
>> >
>> > Title
>> > First / Given Name*
>> > Last / Family Name*
>> > Company / Organization
>> > ISO 3166 Country of Residence*
>> > Email*
>> > Gender
>> > Have you attended an IETF meeting in person before?
>> > Have you attended an IETF meeting remotely before?
>> >
>> > Upon registering, participants would be issued a registration ID, just
>> as they are today.
>
>


-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

--94eb2c07b1187ce3d4054f1ee578
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, May 9, 2017 at 3:30 PM, Ted Hardie <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:ted.ietf@gmail.com" target=3D"_blank">ted.ietf@gmail.com</a>&gt=
;</span> wrote:</div><div class=3D"gmail_quote">...<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><=
div class=3D"gmail_quote"><div>As someone who argued against mentioning=20
registration fees when Alissa shared a draft, you can at least partially
 blame me for the oddity.=C2=A0 I still don&#39;t think it belongs in this =
message, because what we face at the moment is data so noisy that we can&#3=
9;t tell how many people we&#39;re serving at all nor who and where they ar=
e.=C2=A0 Because we can&#39;t tell who we&#39;re serving, we can&#39;t tell=
 whether the service is fit for the purpose very easily.<br></div></div></d=
iv></div></blockquote><div><br></div><div>Personally, I feel it indirectly =
and appropriately mentions fees, it says; &quot;Remote participants would b=
e required to register (for free)&quot;</div><div>=C2=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_e=
xtra"><div class=3D"gmail_quote"><div>If they are primarily folks in the ho=
tel, who can&#39;t be in two rooms at once, we have one set of issues; if t=
hey are primarily folks at the end of low bandwidth, high RTT paths to the =
venue, we have a very different set of issues.=C2=A0 We also don&#39;t know=
 reliably whether we have a small coterie of very dedicated remote particip=
ants or a wide smattering of folks dipping their toes in for a session or t=
wo. =C2=A0</div></div></div></div></blockquote><div><br></div><div>You ment=
ion the &quot;be in two rooms at once&quot; use case, but given the propose=
d information to be requested for registration, how would you capture that =
use case?=C2=A0 Maybe you should ask that directly, like; &quot;Are you als=
o attending the meeting in person?&quot;=C2=A0</div><div><br></div><div>Cou=
ntry of residence is asked for, but it sounds like you really want to know =
where they will be viewing from, not where they live.=C2=A0 For some set of=
 use cases they will be aligned, but others they won&#39;t.</div><div><br><=
/div><div>There is another important use case, similar to &quot;be in two r=
ooms at once&quot;, that is a temporary need to leave the meeting site, suc=
h as to receive medical treatment for chronic conditions or simply just oth=
er business in the meeting city.=C2=A0 As someone who has recently began ne=
eding treatment while traveling. You frequently have little choice over whe=
n a treatment slot is made available to you, usually you have to take what =
they can give you.=C2=A0 Good remote participation options, make this less =
burdensome. =C2=A0</div><div><br></div><div>Thanks</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"><div dir=3D"ltr"><div class=
=3D"gmail_extra"><div class=3D"gmail_quote"><div>Once we have it, there may=
 be many things in the set of ways to support the service that come to ligh=
t; since those might be fund raising from external parties rather than char=
ging, I don&#39;t think we ought to anticipate that stage at this one.<br><=
br></div><div>Hope that makes sense,<br><br></div><div>Ted</div></div></div=
></div></blockquote><div>... =C2=A0</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"g=
mail_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"><span class=
=3D"gmail-m_6889222258744882922gmail-">
&gt; The proposal is as follows:<br>
&gt;<br>
&gt; Remote participants would be required to register (for free) by provid=
ing the information below (* denotes required fields). Registration would b=
e mandatory to access MeetEcho sessions in real time and to join the remote=
 mic queue during a session.<br>
&gt;<br>
&gt; Title<br>
&gt; First / Given Name*<br>
&gt; Last / Family Name*<br>
&gt; Company / Organization<br>
&gt; ISO 3166 Country of Residence*<br>
&gt; Email*<br>
&gt; Gender<br>
&gt; Have you attended an IETF meeting in person before?<br>
&gt; Have you attended an IETF meeting remotely before?<br>
&gt;<br>
&gt; Upon registering, participants would be issued a registration ID, just=
 as they are today.</span></blockquote></div></div></div>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br>David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0=C2=A0 <a href=3D"mailto:Email%3Afarmer@umn.edu" target=3D"_blank">Email=
:farmer@umn.edu</a><br>Networking &amp; Telecommunication Services<br>Offic=
e of Information Technology<br>University of Minnesota=C2=A0=C2=A0 <br>2218=
 University Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: 612-626-0815<br>Minnea=
polis, MN 55414-3029=C2=A0=C2=A0 Cell: 612-812-9952<br>=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </div>
</div></div>

--94eb2c07b1187ce3d4054f1ee578--


From nobody Tue May  9 15:47:01 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 982801294E9 for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 15:47:00 -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 JGy1GimXFBkS for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 15:46:58 -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 A09BD129562 for <ietf@ietf.org>; Tue,  9 May 2017 15:46:58 -0700 (PDT)
Received: by mail-qk0-x229.google.com with SMTP id a72so14096402qkj.2 for <ietf@ietf.org>; Tue, 09 May 2017 15:46: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=BGWTrCVjn27ohjuxfquTh4I7Vom/xhc9npv6LBcH3BQ=; b=XJkEaQYogiD748BB1gg97o259igYZCIezpUpphlBub7ISoqs2PwAdUncT8hinW9nKP H0PqDligRVKxmfk/LaAjgoO9UKo29/TYj5j91XyZ3waQEnNhayEoKF52MbLQgStR9uTQ hRTrkeVTPwgfOJB9uFVNyVpNY+ZNptKpTnNnZ+N/4pWUJ1HmS6zkifK5rd+6Fh8xjcxL PJq4Z8jDZuZrSG7Dd6pdBjEQDxrgkVlGQYE7eFioxASep5c+gWFZSbi8c29QYI+eMaNl c0vrqF8YQJ/L2MppC1sojGtIQgC9GX0YHZDspsAA0dXpofuj2sXl8RRo/zUa14PG7+F9 zBhw==
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=BGWTrCVjn27ohjuxfquTh4I7Vom/xhc9npv6LBcH3BQ=; b=bk6q4AyYGy89Qp0JvB06gIvmpprn1hLwuoG+l8RtHHYLuSNjGVWyirR4uk+iAscVyo Dk/9yStC0Z8JR/NWq9YqJFZLBilkNdu15ySfBKPw1GN5avJyIxA6iHlkYbK5itoBHx/a dOqaOWQB9sNDvQlzHCmXW5iqWRgdsX2W6G5u8I9HsYJwvosjqawPJtDCQGFT3z/HA3TN pLeqlF91IwRSuwn+8PsBiZJNsq1AY9A/djl8515FM2+MZNZ2NoMQETqmHL1t5WxjX1IL 3TNoGfbArVU6R/N+ViG89IKr5mleJ7Er6nZJVgj1P33ZYhxq0CvRLoQVJreClD24ztFU 4Ibw==
X-Gm-Message-State: AODbwcDLJAEQLQccxd4Sc7h+sjUDkgaFNuBOUM0NWICx7WkSW4Rnjads ytyC3CGYauVfORsOfknkko/zFgDB0Q==
X-Received: by 10.55.137.7 with SMTP id l7mr2861326qkd.122.1494370017645; Tue, 09 May 2017 15:46:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.63.45 with HTTP; Tue, 9 May 2017 15:46:27 -0700 (PDT)
In-Reply-To: <CAN-Dau1sMbQ02_Ek9+yU-XUeHK3uK7z74FGzpW8zXoZLL6-LoQ@mail.gmail.com>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <c1f0f773-4842-e413-e6df-dcbf27b94235@cs.tcd.ie> <CA+9kkMAEtMXQ0MVXWX3nTcmi1oCsMq8JcdNPJqLTU1gM2nz74Q@mail.gmail.com> <CAN-Dau1sMbQ02_Ek9+yU-XUeHK3uK7z74FGzpW8zXoZLL6-LoQ@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 9 May 2017 15:46:27 -0700
Message-ID: <CA+9kkMD5fZoYX4B+MGGBn2Ossdtfh8vh_4uOyukAFGNvkpWHXg@mail.gmail.com>
Subject: Re: Registration for remote participation
To: David Farmer <farmer@umn.edu>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c072ec0109bc6054f1f22cf
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3WEX4Q6P1hu7VDD3rj64ZpygsV0>
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, 09 May 2017 22:47:01 -0000

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

On Tue, May 9, 2017 at 3:30 PM, David Farmer <farmer@umn.edu> wrote:

>
> If they are primarily folks in the hotel, who can't be in two rooms at
>> once, we have one set of issues; if they are primarily folks at the end of
>> low bandwidth, high RTT paths to the venue, we have a very different set of
>> issues.  We also don't know reliably whether we have a small coterie of
>> very dedicated remote participants or a wide smattering of folks dipping
>> their toes in for a session or two.
>>
>
> You mention the "be in two rooms at once" use case, but given the proposed
> information to be requested for registration, how would you capture that
> use case?  Maybe you should ask that directly, like; "Are you also
> attending the meeting in person?"
>

You can identify that by noting that the registration ID used to
participate using the remote tools was that of a user who registered to be
on site. If they picked up their badge, you can then determine that they
were on site.  You can't distinguish someone watching from a hotel room
from someone watching from a different meeting room this way, though.


>
> Country of residence is asked for, but it sounds like you really want to
> know where they will be viewing from, not where they live.  For some set of
> use cases they will be aligned, but others they won't.
>
> There is another important use case, similar to "be in two rooms at once",
> that is a temporary need to leave the meeting site, such as to receive
> medical treatment for chronic conditions or simply just other business in
> the meeting city.  As someone who has recently began needing treatment
> while traveling. You frequently have little choice over when a treatment
> slot is made available to you, usually you have to take what they can give
> you.  Good remote participation options, make this less burdensome.
>
> Thanks
>
> regards,

Ted


> Once we have it, there may be many things in the set of ways to support
>> the service that come to light; since those might be fund raising from
>> external parties rather than charging, I don't think we ought to anticipate
>> that stage at this one.
>>
>> Hope that makes sense,
>>
>> Ted
>>
> ...
>
>> > The proposal is as follows:
>>> >
>>> > Remote participants would be required to register (for free) by
>>> providing the information below (* denotes required fields). Registration
>>> would be mandatory to access MeetEcho sessions in real time and to join the
>>> remote mic queue during a session.
>>> >
>>> > Title
>>> > First / Given Name*
>>> > Last / Family Name*
>>> > Company / Organization
>>> > ISO 3166 Country of Residence*
>>> > Email*
>>> > Gender
>>> > Have you attended an IETF meeting in person before?
>>> > Have you attended an IETF meeting remotely before?
>>> >
>>> > Upon registering, participants would be issued a registration ID, just
>>> as they are today.
>>
>>
>
>
> --
> ===============================================
> David Farmer               Email:farmer@umn.edu
> Networking & Telecommunication Services
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE        Phone: 612-626-0815 <(612)%20626-0815>
> Minneapolis, MN 55414-3029   Cell: 612-812-9952 <(612)%20812-9952>
> ===============================================
>

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

<div dir=3D"ltr">On Tue, May 9, 2017 at 3:30 PM, David Farmer <span dir=3D"=
ltr">&lt;<a href=3D"mailto:farmer@umn.edu" target=3D"_blank">farmer@umn.edu=
</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_qu=
ote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><br><div class=3D"gmai=
l_extra"><div class=3D"gmail_quote"><span class=3D""><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><di=
v class=3D"gmail_quote"><div>If they are primarily folks in the hotel, who =
can&#39;t be in two rooms at once, we have one set of issues; if they are p=
rimarily folks at the end of low bandwidth, high RTT paths to the venue, we=
 have a very different set of issues.=C2=A0 We also don&#39;t know reliably=
 whether we have a small coterie of very dedicated remote participants or a=
 wide smattering of folks dipping their toes in for a session or two. =C2=
=A0</div></div></div></div></blockquote><div><br></div></span><div>You ment=
ion the &quot;be in two rooms at once&quot; use case, but given the propose=
d information to be requested for registration, how would you capture that =
use case?=C2=A0 Maybe you should ask that directly, like; &quot;Are you als=
o attending the meeting in person?&quot;</div></div></div></div></blockquot=
e><div><br></div><div>You can identify that by noting that the registration=
 ID used to participate using the remote tools was that of a user who regis=
tered to be on site. If they picked up their badge, you can then determine =
that they were on site.=C2=A0 You can&#39;t distinguish someone watching fr=
om a hotel room from someone watching from a different meeting room this wa=
y, though.<br><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"><di=
v class=3D"gmail_extra"><div class=3D"gmail_quote"><div>=C2=A0</div><div><b=
r></div><div>Country of residence is asked for, but it sounds like you real=
ly want to know where they will be viewing from, not where they live.=C2=A0=
 For some set of use cases they will be aligned, but others they won&#39;t.=
</div><div><br></div><div>There is another important use case, similar to &=
quot;be in two rooms at once&quot;, that is a temporary need to leave the m=
eeting site, such as to receive medical treatment for chronic conditions or=
 simply just other business in the meeting city.=C2=A0 As someone who has r=
ecently began needing treatment while traveling. You frequently have little=
 choice over when a treatment slot is made available to you, usually you ha=
ve to take what they can give you.=C2=A0 Good remote participation options,=
 make this less burdensome. =C2=A0</div><div><br></div><div>Thanks</div><sp=
an class=3D""><div><br></div></span></div></div></div></blockquote>regards,=
<br><br></div><div class=3D"gmail_quote">Ted<br></div><div class=3D"gmail_q=
uote"><div>=C2=A0</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"><span class=3D""><div></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><div>Once we have it, ther=
e may be many things in the set of ways to support the service that come to=
 light; since those might be fund raising from external parties rather than=
 charging, I don&#39;t think we ought to anticipate that stage at this one.=
<br><br></div><div>Hope that makes sense,<br><br></div><div>Ted</div></div>=
</div></div></blockquote></span><div>... =C2=A0</div><span class=3D""><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:=
1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D=
"gmail_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);pa=
dding-left:1ex"><span class=3D"m_-448144559827838440gmail-m_688922225874488=
2922gmail-">
&gt; The proposal is as follows:<br>
&gt;<br>
&gt; Remote participants would be required to register (for free) by provid=
ing the information below (* denotes required fields). Registration would b=
e mandatory to access MeetEcho sessions in real time and to join the remote=
 mic queue during a session.<br>
&gt;<br>
&gt; Title<br>
&gt; First / Given Name*<br>
&gt; Last / Family Name*<br>
&gt; Company / Organization<br>
&gt; ISO 3166 Country of Residence*<br>
&gt; Email*<br>
&gt; Gender<br>
&gt; Have you attended an IETF meeting in person before?<br>
&gt; Have you attended an IETF meeting remotely before?<br>
&gt;<br>
&gt; Upon registering, participants would be issued a registration ID, just=
 as they are today.</span></blockquote></div></div></div>
</blockquote></span></div><span class=3D"HOEnZb"><font color=3D"#888888"><b=
r><br clear=3D"all"><div><br></div>-- <br><div class=3D"m_-4481445598278384=
40gmail_signature">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D<br>David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0=C2=A0 <a href=3D"mailto:Email%3Afarmer@umn.edu" target=3D"_blank">E=
mail:farmer@umn.edu</a><br>Networking &amp; Telecommunication Services<br>O=
ffice of Information Technology<br>University of Minnesota=C2=A0=C2=A0 <br>=
2218 University Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: <a href=3D"tel:(61=
2)%20626-0815" value=3D"+16126260815" target=3D"_blank">612-626-0815</a><br=
>Minneapolis, MN 55414-3029=C2=A0=C2=A0 Cell: <a href=3D"tel:(612)%20812-99=
52" value=3D"+16128129952" target=3D"_blank">612-812-9952</a><br>=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </div>
</font></span></div></div>
</blockquote></div><br></div></div>

--94eb2c072ec0109bc6054f1f22cf--


From nobody Tue May  9 15:48:53 2017
Return-Path: <ietf@jiaziyi.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 239221294E9; Tue,  9 May 2017 15:48:51 -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=jiaziyi.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 9TTvAtv8wAYd; Tue,  9 May 2017 15:48:49 -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 5ACB3124BFA; Tue,  9 May 2017 15:48:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1494370125;  s=jiazi; d=jiaziyi.com; i=ietf@jiaziyi.com; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To; l=7754; bh=cJ5Tp6yh2KVb3tuApafOh15RjUTU1NpII5ipqqBbTdk=; b=DZoaVHppMuG1066LTGpbjTfpGsKUtwSI7+swjYtu9aATi+uk4otW42vkWqlr9Axo X69aeJsJ/jGGd2e8oPpAwZzWXl9/XYezOhHve04B7hL+oKeM6lVr4siFpwGK45RVPJW EOu2HWtmhscnYRcGJGB4nEYXBhvaigWSi5bKXCDU=
Received: from [192.168.1.101] (230.248.86.88.rdns.comcable.net [88.86.248.230]) by mx.zohomail.com with SMTPS id 1494370125111762.8919372899151; Tue, 9 May 2017 15:48:45 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [manet] Last Call: <draft-ietf-manet-olsrv2-multipath-12.txt> (Multi-path Extension for the Optimized Link State Routing Protocol version 2 (OLSRv2)) to Experimental RFC
From: Jiazi Yi <ietf@jiaziyi.com>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6330DE9@GLKXM0003v.GREENLNK.net>
Date: Wed, 10 May 2017 00:48:42 +0200
Cc: "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>, "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multipath@ietf.org" <draft-ietf-manet-olsrv2-multipath@ietf.org>,  "manet-chairs@ietf.org" <manet-chairs@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9096512E-3473-473A-B6F1-37CBDD82A0F4@jiaziyi.com>
References: <149272508088.22258.8263343290438640855.idtracker@ietfa.amsl.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6330DE9@GLKXM0003v.GREENLNK.net>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
X-Mailer: Apple Mail (2.3273)
X-ZohoMailClient: External
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WpjGvpiQmC5aacSig4_iHd8j9yc>
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, 09 May 2017 22:48:51 -0000

Hi Chris,=20

Thanks a lot for the comments! Please check our reply inline:=20

> On 9 May 2017, at 12:13, Dearlove, Christopher (UK) =
<chris.dearlove@baesystems.com> wrote:
>=20
> A few comments on this draft.
>=20
> IPv6 specifies complete source routing. But this specification can =
only consider what happens within the MANET. So for a packet from =
somewhere in the MANET to somewhere well outside the MANET, the packet =
must be source routed to the gateway between MANET and rest of Internet, =
and not source routed after that. This I think should be explicitly =
mentioned. Whether that is considered compliant with IPv6 I leave to =
others.

Good point. We added some text at the end of section 8.4" Datagram =
Processing at the MP-OLSRv2 Originator"

>=20
> 7.1 SR_addr would better say "originator" address rather than =
"network" address. (That makes it an address without a netmask, see RFC =
7181.)

fixed.=20

>=20
> 8.1 This is suggesting creating TC messages that have on neighbour =
addresses but have only a SOURCE_ROUTE TLV. This is not the design I =
would have suggested as consistent with how I would expect an extension =
to OLSRv2 to do things. We need to consider two kinds of routers: those =
sending TC messages anyway, those that (other than this extension) do =
not. In the former case you could just add the SOURCE_ROUTE TLV to those =
TC messages it sends. Then that information is maintained up to date. =
Routers that don't usually send TC messages could send TC messages with =
just that TLV. But then there's an issue over validity time. A parameter =
SR_HOLD_TIME_MULTIPLIER is introduced. There's no need for that - you =
can simply incorporate that into the validity time recorded in the =
message. That avoids a need to handle the two cases of routers =
differently. There is then an oddity that you get some routers sending =
TC messages with normal validity times and addresses, and some that can =
be sent less frequently with no addresses and longer validity times. But =
that's suspect - note that it's not done in OLSRv2 for attached networks =
(another reason to send TC messages although no neighbours need =
reporting). That's because longer intervals make reacting to new routers =
joining (and network reassembly after fragmentation) slow.
> Rather a better design would simply be to add SOURCE_ROUTE TLV to =
normal TC messages. When sending TC messages for just that reason, that =
could be just the usual case, but you could allow as an option in this =
case to send less frequently with validity time increased accordingly. =
When not using that option, once a router needs to send a TC message, it =
could then decide to report neighbours, increasing the topology =
distributed and allowing more routes, this also being an option.
>=20

IIRC, we had a long discussion on this issue and produced the current =
text.=20
The purpose is to identify the routers that don=E2=80=99t send TC =
messages but support source routing. To avoid unnecessary TC flooding, =
the interval is much longer than the normal TC interval.=20
The normal TC messages (generated based on RFC7181) always have a =
SOURCE_ROUTE TLV. But if we use the same validity time for both RFC7181 =
normal TC processing and MP-OLSRv2 SR_ROUTE TLV processing, the valid =
time in the SR-OLSRv2 Router Set would be much shorter than expected. A =
possible case is that, the router stops sending normal TC messages, the =
corresponding entry in the SR-OLSRv2 Router set will soon expire.=20
Therefore, I think it=E2=80=99s reasonable to make use of the =
SR_HOLD_TIME_MULTIPLIER to distinguish the valid time of normal TC =
message information and SR_ROUTE information.=20


> 8.3 second bullet. You should here (and possibly elsewhere) exclude =
routers with routing willingness zero.

>=20
> 8.3 there seems to be an inconsistency. When operating proactively and =
no multiple routes, drop the packet, but reactively use standard =
routing. The latter seems more appropriate in the former case also.
>=20
> 9 CUTOFF_RATIO. Insists of strictly, but as defined earlier, may be >=3D=
 1`.

All fixed.=20

Thanks again for the valuable comments!

best

Jiazi

>=20
> --=20
> Christopher Dearlove
> Senior Principal Engineer
> BAE Systems Applied Intelligence Laboratories
> =
__________________________________________________________________________=

>=20
> T:  +44 3300 467500  |  E: chris.dearlove@baesystems.com
>=20
> BAE Systems Applied Intelligence, Chelmsford Technology Park, Great =
Baddow, Chelmsford, Essex CM2 8HN.
> www.baesystems.com/ai
> BAE Systems Applied Intelligence Limited
> Registered in England & Wales No: 01337451
> Registered Office: Surrey Research Park, Guildford, Surrey, GU2 7YP
>=20
>=20
> -----Original Message-----
> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of The IESG
> Sent: 20 April 2017 22:51
> To: IETF-Announce
> Cc: manet@ietf.org; draft-ietf-manet-olsrv2-multipath@ietf.org; =
manet-chairs@ietf.org
> Subject: [manet] Last Call: <draft-ietf-manet-olsrv2-multipath-12.txt> =
(Multi-path Extension for the Optimized Link State Routing Protocol =
version 2 (OLSRv2)) to Experimental RFC
>=20
> ----------------------! WARNING ! ---------------------- This message =
originates from outside our organisation, either from an external =
partner or from the internet.
> Consider carefully whether you should click on any links, open any =
attachments or reply.
> Follow the 'Report Suspicious Emails' link on IT matters for =
instructions on reporting suspicious email messages.
> --------------------------------------------------------
>=20
> *** WARNING ***
> EXTERNAL EMAIL -- This message originates from outside our =
organization.
>=20
>=20
> The IESG has received a request from the Mobile Ad-hoc Networks WG
> (manet) to consider the following document:
> - 'Multi-path Extension for the Optimized Link State Routing Protocol
>   version 2 (OLSRv2)'
>  <draft-ietf-manet-olsrv2-multipath-12.txt> as Experimental RFC
>=20
> The IESG plans to make a decision in the next few weeks, and solicits =
final comments on this action. Please send substantive comments to the =
ietf@ietf.org mailing lists by 2017-05-04. Exceptionally, comments may =
be sent to iesg@ietf.org instead. In either case, please retain the =
beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>   This document specifies a multi-path extension for the Optimized =
Link
>   State Routing Protocol version 2 (OLSRv2) to discover multiple
>   disjoint paths, so as to improve reliability of the OLSRv2 protocol.
>   The interoperability with OLSRv2 is retained.
>=20
>=20
>=20
>=20
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-multipath/
>=20
> IESG discussion can be tracked via
> =
https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-multipath/ballot/=

>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
>=20
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>=20
>=20
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
>=20



From nobody Tue May  9 15:50:04 2017
Return-Path: <lberger@labn.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 88C1012EB5C for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 15:50:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.501
X-Spam-Level: 
X-Spam-Status: No, score=-1.501 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.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 mrt094FuINZe for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 15:50:02 -0700 (PDT)
Received: from gproxy3.mail.unifiedlayer.com (gproxy3-pub.mail.unifiedlayer.com [69.89.30.42]) (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 57D811294E9 for <ietf@ietf.org>; Tue,  9 May 2017 15:50:02 -0700 (PDT)
Received: from cmgw4 (unknown [10.0.90.85]) by gproxy3.mail.unifiedlayer.com (Postfix) with ESMTP id D1252402F5 for <ietf@ietf.org>; Tue,  9 May 2017 16:50:01 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw4 with  id JNpy1v00A2SSUrH01Nq1Kh; Tue, 09 May 2017 16:50:01 -0600
X-Authority-Analysis: v=2.2 cv=QdwWhoTv c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10 a=tJ8p9aeEuA8A:10 a=Aiam34JAnM70mF3S6d4A:9 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc: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=4RDYltEwCvg4IEKV7fMpxmuyS/uGkUsFch3n4PTVmIU=; b=hnhUo7tg8e0aa+Mq5WK75Ut21I Fkhx+Kss9QcOjNM+8oSIOaqZiDcxGlkbUYJGXAuD2FXQ5HoJHP08aX+w5AKJuM4aXtx21fr7AedZn 6AP0ihkZLfjQzMIVK1cBJuEpr;
Received: from pool-100-15-84-20.washdc.fios.verizon.net ([100.15.84.20]:56022 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <lberger@labn.net>) id 1d8Dx8-00045E-0D for ietf@ietf.org; Tue, 09 May 2017 16:49:58 -0600
Subject: Re: Registration for remote participation
To: IETF Discussion <ietf@ietf.org>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <9121E962-B74F-4ADB-83E3-DD966B7352CB@gmail.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <9631d940-7208-8c31-0df8-d7a344ff92cf@labn.net>
Date: Tue, 9 May 2017 18:49:56 -0400
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: <9121E962-B74F-4ADB-83E3-DD966B7352CB@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 100.15.84.20
X-Exim-ID: 1d8Dx8-00045E-0D
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-100-15-84-20.washdc.fios.verizon.net ([IPv6:::1]) [100.15.84.20]:56022
X-Source-Auth: lberger@labn.net
X-Email-Count: 1
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XIKLN7k8lo-cZnIZ_TnGxly1eo8>
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, 09 May 2017 22:50:03 -0000

On 5/9/2017 6:06 PM, Yoav Nir wrote:
>> To join a session, participants would be asked to input the registration ID. The same email-based facility that is currently available to retrieve a forgotten registration ID would continue to be available. The cookie-based “Remember me” option would also still be available. The only difference from how login works today is that the option to "Join without registration ID" would be removed.
> Does this mean that unregistered people would not be able to listen/view?  I’m fine with cutting off *participation*, but even before Meetecho we’ve had a live (audio) stream from the room. I wouldn’t want to lose that.  
+1 - I think continuing to provide unregistered live streaming is
important.  I am sensitive that there is a real cost to this,
particularly if usage increases. Perhaps we can shift this to a youtube
live stream to handle the fanout. 
 
> Recordings are good, but by the time you listen to a recording, the conversation may have moved on.
>
>> If they are primarily folks in the hotel, who can't be in two rooms at once, we have one set of issues; 
I also hope we don't loose the live audio only stream -- I regularly use
this while at the meeting to deal with the 2/3 room at once problem.  Of
course, if no one else uses it -- I loose...

Lou
(no hats)


From nobody Tue May  9 15:54:35 2017
Return-Path: <ietf@jiaziyi.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 78C3612EAE2; Tue,  9 May 2017 15:54:16 -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=jiaziyi.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 8oB-ipFGCeDN; Tue,  9 May 2017 15:54:15 -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 21076124B0A; Tue,  9 May 2017 15:54:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1494370448;  s=jiazi; d=jiaziyi.com; i=ietf@jiaziyi.com; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To; l=1359; bh=Bzue9mViNgdVB7Uz9WuBYlUb1OYFB5imytMOYWW0LZQ=; b=g57wIac15mW3hxxkQU3nTfe7YVFrLEtQJNnpEwu40cAaZn6lPM/p6FSgAugMJGg/ XL6Iw2vY9Tqi723KjaXF1jE/XrZ7IqYX7Ud4f4DQXyXqY5me5CCGorLTbxErnihcGyA dJWZONCmwXnGwldbip+5gGQ8GbcVsEUzKz1LltkI=
Received: from [192.168.1.101] (230.248.86.88.rdns.comcable.net [88.86.248.230]) by mx.zohomail.com with SMTPS id 149437044828451.717761972135236; Tue, 9 May 2017 15:54:08 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Intdir telechat review of draft-ietf-manet-olsrv2-multipath-12
From: Jiazi Yi <ietf@jiaziyi.com>
In-Reply-To: <149431964538.10555.11264594833770083998@ietfa.amsl.com>
Date: Wed, 10 May 2017 00:54:06 +0200
Cc: int-dir@ietf.org, manet@ietf.org, ietf@ietf.org, draft-ietf-manet-olsrv2-multipath.all@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <11D61838-1EE5-475B-BCBA-B4DC1D6C5BB4@jiaziyi.com>
References: <149431964538.10555.11264594833770083998@ietfa.amsl.com>
To: Zhen Cao <zhencao.ietf@gmail.com>
X-Mailer: Apple Mail (2.3273)
X-ZohoMailClient: External
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/r6yvsJExhBWy-72TMfYNvDCrPLw>
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, 09 May 2017 22:54:17 -0000

Dear Zhen, 

Thanks very much for your review. 
We will update the draft based on the comments and submit a new revision. 

best

Jiazi

> On 9 May 2017, at 10:47, Zhen Cao <zhencao.ietf@gmail.com> wrote:
> 
> Reviewer: Zhen Cao
> Review result: Ready with Issues
> 
> I am an assigned INT directorate reviewer for this draft. These
> comments were written primarily for the benefit of the Internet Area
> Directors. Document editors and shepherds should treat these comments
> just like they would treat comments from any other IETF contributors
> and resolve them along with any other Last Call comments that have
> been received. For more details of the INT directorate, see
> <http://www.ietf.org/iesg/directorate.html>.
> 
> I believe this document is ready to publish almost as it is. 
> 
> One issue I found during my review lies in Sec. 8.4 where IPv4 loose
> source routing being discussed.  To avoid unnecessary fragmentation, I
> am suggesting the following wording change: 
> 
> S/  If the length of the path (n) is greater than MAX_SRC_HOPS
>      (Section 5), only the "key" routers in the path are kept...
> /  If the length of the path (n) is greater than MAX_SRC_HOPS 
>      (Section 5), or the adding of source routing header exceeds the
> path MTU, 
> only the "key" routers in the path are kept...
> 
> Cheers,
> Zhen
> 
> 
> 



From nobody Tue May  9 15:56:13 2017
Return-Path: <ietf@jiaziyi.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 25B3212EB91; Tue,  9 May 2017 15:56:10 -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=jiaziyi.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 5cGON3-7FbAd; Tue,  9 May 2017 15:56:07 -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 8A6DA12EB85; Tue,  9 May 2017 15:56:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1494370563;  s=jiazi; d=jiaziyi.com; i=ietf@jiaziyi.com; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To; l=8654; bh=nIEekBq1mpm+wA/3wpnGCkAb8jTZnnvgpEHsZL9xmXE=; b=qrnkKyr+d4UbZOd7xJrGGAA5P8bfg6uUSgUhKnpbOQXM8G3jowkAjdWR5nrP9Pnb gBo0nMvnbEBOMLhxEn02lnGXlfrj81XmVX1+x4sDUf4etffDOpn6rhaPV5O0BWA15jb zxubAMc94BglF21FkSUI1fWtuRSzrjAz09WuLqfs=
Received: from [192.168.1.101] (230.248.86.88.rdns.comcable.net [88.86.248.230]) by mx.zohomail.com with SMTPS id 1494370563128979.4849807958168; Tue, 9 May 2017 15:56:03 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [manet] Genart last call review of draft-ietf-manet-olsrv2-multipath-12
From: Jiazi Yi <ietf@jiaziyi.com>
In-Reply-To: <149395525273.6861.14988459288524802803@ietfa.amsl.com>
Date: Wed, 10 May 2017 00:56:00 +0200
Cc: gen-art@ietf.org, manet@ietf.org, ietf@ietf.org, draft-ietf-manet-olsrv2-multipath.all@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <82811D33-9B17-4C32-B045-D8685B9C3C58@jiaziyi.com>
References: <149395525273.6861.14988459288524802803@ietfa.amsl.com>
To: Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.3273)
X-ZohoMailClient: External
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/il8P39-V50gfSXrmbWod3zREpCg>
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, 09 May 2017 22:56:10 -0000

Dear Peter, 

Thanks very much for the detailed comments. 
We have updated the draft and will make a new submission soon. 

cheers

Jiazi

> On 5 May 2017, at 05:34, Peter Yee <peter@akayla.com> wrote:
> 
> Reviewer: Peter Yee
> 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-manet-olsrv2-multipath-12
> Reviewer: Peter Yee
> Review Date: 2017-05-04
> IETF LC End Date: 2017-05-04
> IESG Telechat date: 2017-05-11
> 
> Summary: This Experimental draft is ready with nits.  The draft
> specifies an interoperable, multipath extension to OLSRv2.  Other than
> the nits, I find the draft to be a fine experiment to help determine
> how well OLSRv2 can be improved by allowing multiple, disjoint paths
> between nodes.
> 
> Major issues: None
> 
> Minor issues: None
> 
> Nits/editorial comments: 
> 
> General:
> 
> I'd suggesting changing occurrences of "multi-path" to "multipath" for
> consistency with prior works, including the primary work by the same
> authors [ADHOC11].
> 
> Consider changing "Multi-path Dijkstra Algorithm" to "multipath
> Dijkstra's algorithm".  In any case, use the name consistently - it
> varies throughout the document.
> 
> Change "Round-Robin" (and variations in capitalization) to
> "round-robin" throughout the document.
> 
> Stick to one capitalization form for "MP-OLSRv2 Routing Process".
> 
> Section 10 was not reviewed because it contains RFC Editor
> instructions to delete it.
> 
> Specific:
> 
> Page 3, section 1, 2nd paragraph, last sentence: append a comma after
> "reliability".
> 
> Page 3, section 1, 3rd paragraph, 1st sentence: delete the leading
> "The".  Insert "the "before "Multi-path Dijkstra".  [See general
> comment about hyphenating multi-path].
> 
> Page, section 1.1, 4th bullet item: delete the second "the".
> 
> Page 4, 1st full paragraph, 2nd sentence: change "Standard" to
> "Standards".  Delete comma after "Track".
> 
> Page 4, 2nd bullet item, 3rd sentence: change "setting" to "applying".
> (This is an aesthetics comment - take it or leave it.)
> 
> Page 4, 4th bullet item, 3rd sentence: expand acronym "MPR" on first
> usage and in general do so for all acronyms that would not be
> immediately obvious to a large audience.
> 
> Page 4, 5th bullet item, 4th sentence: delete "the" before "loose".
> 
> Page 4, 6th bullet, 3rd sentence: append "parts" after "following".
> 
> Page 6, section 3, 1st paragraph, 2nd sentence: delete both commas.
> 
> Page 6, section 3, 2nd paragraph, 2nd sentence: delete "the" before
> "information".  Insert "a" before "DiffServ".  Change "Code Point" to
> codepoint.  [RFC 2474 only refers to these a "Code Point" in specific
> names, but otherwise uses the generic form "codepoint".
> 
> Page 6, section 3, 3rd paragraph, 1st sentence: insert "a" before
> "new".
> 
> Page 6, section 3, 3rd paragraph, 3rd sentence: insert "the" before
> "loose".
> 
> Page 7, section 4, 3rd bullet item: insert "the" before "shortest".
> 
> Page 8, partial paragraph at top: change "as" to "using the".
> 
> Page 8, section 5.1, SR_TC_INTERVAL definition: change "a" to "an".
> 
> Page 8, section 5.1, SR_HOLD_TIME_MULTIPLIER definition:  change
> "minimal" to "minimum".  Change "a" to "an" unless that acronym is
> spoken like a word and not spelled out.
> 
> Page 8, section 6, 2nd sentence: delete comma after "datagram".
> 
> Page 9, section 6.1, 1st sentence: insert "the" before "MP-OLSRv2".  
> 
> Page 9, section 6.1.1, 1st paragraph, 1st sentence: change
> "signalling" to "signaling".  [Other words in the document tend to
> suggest that the American spellings are being used rather than British
> forms.]
> 
> Page 9, section 6.2.1, 1st sentence: insert "the" before "loose".
> 
> Page 10, section 7.1, 1st paragraph, 2nd sentence: delete the comma. 
> Insert "the" before each of "MP-OLSRv2" and "OLSRv2".
> 
> Page 11, section 8, 2nd sentence: insert "the" before "topology".
> 
> Page 11, section 8, 3rd sentence: change "between" to "from the".
> 
> Page 11, section 8.1, 2nd paragraph, 2nd sentence: insert "the" before
> "SR_TC_INTERVAL".
> 
> Page 11, section 8.1, 2nd paragraph, 3rd sentence: delete "The".
> 
> Page 11, section 8.1, 2nd paragraph, 5th sentence: insert "the" before
> "SOURCE_ROUTE TLV".
> 
> Page 12, section 8.3, 1st bullet item: change "possiblity" to
> "possibility".
> 
> Page 12, section 8.3, 2nd bullet item, 2nd sentence: perhaps change
> "Or else" to "Otherwise".
> 
> Page 12, section 8.4, 1st paragraph: insert "a" before "DiffServ". 
> Change "Code Point" to "codepoint".
> 
> Page 13, 1st paragraph, last sentence: insert "the" before "OLSRv2".
> 
> Page 13, 3rd paragraph, 2nd sentence: insert "the" before "format".
> 
> Page 13, the paragraph: insert "the" before "following".
> 
> Page 13, last paragraph, 2nd sentence: insert "the" before "outer" and
> "source".
> 
> Page 14, section 8.5.1, 1st paragraph after the 1st set of bullet
> items: insert "the" before "SR-OLSRv2".
> 
> Page 14, section 8.5.1, 2nd paragraph after the 1st set of bullet
> items, 3rd sentence: insert "the" before "OLSRv2".
> 
> Page 14, section 8.5.1, 2nd paragraph after the 1st set of bullet
> items, 4th sentence: change "much" to "many".
> 
> Page 14, section 8.5.1, 3rd paragraph after the 1st set of bullet
> items: shouldn't this be up to "NUMBER_OF_PATHS" rather than always
> "NUMBER_OF_PATHS" paths that are created?  Meaning that it's possible
> the algorithm will not have sufficient disjoint paths to choose from
> in some (probably degenerate) cases?  Delete the second comma in the
> sentence.
> 
> Page 14, section 8.5.1, 2nd set of bullet items, 2nd bullet item, 1st
> sentence: change "A" to "An".
> 
> Page 14, section 8.5.1, 2nd set of bullet items, 2nd bullet item, 2nd
> sentence: insert "the" before "Multi-path".
> 
> Page 14, section 8.5.2, 1st sentence: insert "the" before
> "Multi-path".
> 
> Page 15, 1st full paragraph, 1st sentence: change the second
> occurrence of "Dijkstra" to "Dijkstra's".
> 
> Page 15, 2nd bullet item, 2nd sentence: change "is" to "does".
> 
> Page 15, 1st paragraph after bullet items, 3rd sentence: change
> "vetex" to "vertex".
> 
> Page 15, 1st paragraph after figure, 2nd sentence: change "of" to
> "for".
> 
> Page 16, 1st sentence: change "Dijkstra" to "Dijkstra's".
> 
> Page 16, 1st paragraph after numbered list: insert "the" before
> "Multi-path".
> 
> Page 16, section 8.6, 1st paragraph, last sentence: insert "whether"
> before "the set".
> 
> Page 16, section 9, 1st sentence: change "guideline" to "guidelines".
> 
> Page 16, section 9, 2nd sentence: delete the comma after "certain".
> 
> Page 17, "if id<fe<fp" bullet item: would it make more sense to use "a
> greater" instead of "more"?
> 
> Page 19, section 11, 2nd paragraph, 1st sentence: change "Process" to
> "Processes".
> 
> Page 19, section 11, 2nd paragraph, 2nd sentence: delete "be".
> 
> Page 19, section 11, 3rd paragraph: append "with" after "As".
> 
> Page 19, section 11, 4th paragraph, 1st sentence: insert "The" before
> "MP-OLSRv2".
> 
> Page 19, section 11, 4th paragraph, 2nd sentence: insert "the" before
> "source".
> 
> Page 20, 1st paragraph, 4th sentence: should "ancient" be "the
> oldest"?
> 
> Page 20, 1st paragraph, 5th sentence: delete comma after "that". 
> Insert "a" before "large".  Maybe change "initiates" to "sends". 
> Delete the comma after "which".
> 
> Page 24, 1st paragraph after Figure 2, 1st sentence:  insert "the"
> before "name".  Change "name" to "names".
> 
> Page 24, 1st paragraph after Figure 2, 2nd sentence: change
> "parenthesis" to "parentheses".
> 
> Page 24, 3rd paragraph after Figure 2, 3rd sentence: while I
> understand "punishment", that term hasn't been used previously and
> might be confusing.  A variant occurs elsewhere in the document. 
> Consider explaining what you mean by punishment.
> 
> Page 24, 2nd paragraph after Figure 3, 1st sentence: change "path" to
> "paths".  Append "in order" after "paths".
> 
> Page 24, 3rd paragraph after Figure 3, 2nd sentence: change
> "undesired" to "undesirable".
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet



From nobody Tue May  9 21:31:24 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 332DD12EAB2; Tue,  9 May 2017 21:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level: 
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 mE7caBuZxXjE; Tue,  9 May 2017 21:31:12 -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 9204A1205F1; Tue,  9 May 2017 21:31:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v4A4V8ZY025040; Wed, 10 May 2017 06:31:09 +0200 (CEST)
Received: from [192.168.217.124] (p5DC7F3A7.dip0.t-ipconnect.de [93.199.243.167]) (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 3wN3G45Wt8zDHmm; Wed, 10 May 2017 06:31:08 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [art] Artart last call review of draft-ietf-core-coap-tcp-tls-07
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <767F913A-586B-42A2-B021-F9AC5C478702@mnot.net>
Date: Wed, 10 May 2017 06:31:07 +0200
Cc: art@ietf.org, draft-ietf-core-coap-tcp-tls.all@ietf.org, ietf@ietf.org, core@ietf.org
X-Mao-Original-Outgoing-Id: 516083467.066919-e7cf67f9e5bffe784973075c0e683012
Content-Transfer-Encoding: quoted-printable
Message-Id: <2D57FF92-3A56-43BC-A815-27801E31F770@tzi.org>
References: <149179722452.3118.982908107963516290@ietfa.amsl.com> <5E5238DC-B835-4BDF-B50D-8D594A46C4D4@tzi.org> <767F913A-586B-42A2-B021-F9AC5C478702@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OwqQuIXK3g9_HIfzxTxI1yJieJc>
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, 10 May 2017 04:31:15 -0000

> On May 9, 2017, at 23:30, Mark Nottingham <mnot@mnot.net> wrote:
>=20
> To close this loop -- the change in -08 isn't sufficiently prominent =
IME; while the general nature of the change is listed in the Abstract, =
the actual normative text is very hard to find.

Certainly, let=E2=80=99s see what the IESG decides here.

> Given that this is a pretty fundamental change in the operation of a =
URI scheme, I'd think it at least deserves its own section, if not a =
separate document.

I don=E2=80=99t agree that this is such a fundamental change here =E2=80=94=
 the /.well-known name space in the URI already was special (by the fact =
that ws URIs are mapped to http URIs, which do have /.well-known =
reserved already).

But that doesn=E2=80=99t matter, we should find the best editorial way =
to document making the well-known URI concept available to WebSocket =
URIs.

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


From nobody Tue May  9 22:21:06 2017
Return-Path: <bob.hinden@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 D440E127201 for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 22:21:04 -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, 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 ZR34kzv94u_o for <ietf@ietfa.amsl.com>; Tue,  9 May 2017 22:21:03 -0700 (PDT)
Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::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 A1A3A127136 for <ietf@ietf.org>; Tue,  9 May 2017 22:21:02 -0700 (PDT)
Received: by mail-wr0-x229.google.com with SMTP id z52so26910775wrc.2 for <ietf@ietf.org>; Tue, 09 May 2017 22:21:02 -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=iekJBcejjZp4eIEuDEyUhs0vTREgmQEoPrwf5+C2mTU=; b=Xu+dDHoES961aHjL0LeKkbnS+UcYWjewhBLG9ZxuwWvcW4Y7folw7iWtZrh5H7ntCK oeEGFt5DuC4riYWTIAqoRR9V8Q3nvlXrYKnLufuuLD9Ay538YbQrgNatTt+pYmpM0qBw bqRCNcqT/Iv79dd/yC4PYsVNpXaJfo6+QWd3bYkTohdSzfqk8zwMHQRjTrSwkMnYLDnv vSDtutX1nPIRX4VmobDIrMZ64pWbL7Dove0uznjLQMZ+D4aQXflV9k5Rd9jHEDzIG/r1 /E4kb5TVOffIDvgUvW31nL1UI63sGAtNEcP/o41AwDgBsze3jFYMVUPtfBpd0iZ1o8zA Ytng==
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=iekJBcejjZp4eIEuDEyUhs0vTREgmQEoPrwf5+C2mTU=; b=ZhC2yvc+Cu0vLAl/us5KzkBUe19fEn8HZXDYTcqC3ya9BotFlABLrcNc/txT0o0x9I da+WCk/12QN5IIQicaGwHTCzZ/0oMaeQTckGsOyyjg3tgtIRaruUM4MQpmS3cUBeQ1uE ADRV0VfZdW3xleYF0AUCin7BEWdnrZQjkNFkoihRfBY3YzXg4h0XhV/cgSIpVK0lF66Q GbZFswpgRRnJZALlL7OforS1l9pIGt6fjqtMLfddPDdMK5Bl4w3gZiDzu4fRcF8LcZog pLxJXM+w77y9ifLo4RWsFWwjbc6dM5yqT8VhlqceAh/btLwU+dJ3b6JOQ0u0KSysLz+G uf2w==
X-Gm-Message-State: AODbwcCP7XNVFfqxwidAnxC8f7rln6yENcm7AzczsPOF+ufSHXTD+fvN Ah+Xlh53HQ2/xvCwpabP/w==
X-Received: by 10.223.138.250 with SMTP id z55mr2201923wrz.50.1494393660946; Tue, 09 May 2017 22:21:00 -0700 (PDT)
Received: from [10.0.0.124] (bzq-79-180-161-157.red.bezeqint.net. [79.180.161.157]) by smtp.gmail.com with ESMTPSA id i24sm1304132wrc.40.2017.05.09.22.20.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 May 2017 22:21:00 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <82C753BB-C89C-4039-8A08-0615067777C0@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_6463A540-946E-4BDE-8368-618BE4ABEC35"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Registration for remote participation
Date: Wed, 10 May 2017 08:20:56 +0300
In-Reply-To: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
Cc: Bob Hinden <bob.hinden@gmail.com>
To: IETF <ietf@ietf.org>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SXrrdMZXgxRkZQb0GTXWsfNXAxs>
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, 10 May 2017 05:21:05 -0000

--Apple-Mail=_6463A540-946E-4BDE-8368-618BE4ABEC35
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I support this.  I agree it is useful to collect this data, and think =
it=E2=80=99s important to know who is participating in the IETF =
standards process.

I will resit nitpicking as others are doing that just fine :-)

Bob

> On May 9, 2017, at 10:01 PM, IETF Chair <chair@ietf.org> wrote:
>=20
> For remote participants at IETF meetings, registration is currently =
optional. Remote participants may join a session at an IETF meeting by =
entering any name or pseudonym of their choice into the current form =
used for logging in to MeetEcho.
>=20
> The IESG is soliciting community feedback on a proposal to require =
registration for remote participants at IETF meetings. The objective of =
requiring registration for real-time remote participation is to provide =
better data to the IETF community and leadership about the size and =
make-up of the remote participant base. As remote participation grows, =
having more reliable remote participation data will allow the service to =
be better tailored to those using it and the community as a whole, and =
will help us understand the potential impact of remote participation on =
in-person participation. We understand that even with required =
registration the data collected will not be perfect, complete, or =
unspoofable, but we believe it would provide a more credible basis for =
analysis than the data available today.
>=20
> The proposal is as follows:
>=20
> Remote participants would be required to register (for free) by =
providing the information below (* denotes required fields). =
Registration would be mandatory to access MeetEcho sessions in real time =
and to join the remote mic queue during a session.
>=20
> Title
> First / Given Name*
> Last / Family Name*
> Company / Organization
> ISO 3166 Country of Residence*
> Email*
> Gender
> Have you attended an IETF meeting in person before?
> Have you attended an IETF meeting remotely before?
>=20
> Upon registering, participants would be issued a registration ID, just =
as they are today.
>=20
> To join a session, participants would be asked to input the =
registration ID. The same email-based facility that is currently =
available to retrieve a forgotten registration ID would continue to be =
available. The cookie-based =E2=80=9CRemember me=E2=80=9D option would =
also still be available. The only difference from how login works today =
is that the option to "Join without registration ID" would be removed. =
Other options for authentication (leveraging a user-chosen password or =
datatracker credentials) might be explored further in the future.
>=20
> Remote participation registration data would be stored and secured by =
AMS and MeetEcho just as it is currently today. As is the case now, no =
registration or login would be required to access MeetEcho recordings, =
audio recordings, YouTube videos, or jabber rooms. And no changes are =
being proposed as to the handling of virtual blue sheets.
>=20
> We'd like to hear from the community about this proposal. Please send =
comments to ietf@ietf.org, or exceptionally to iesg@ietf.org, preferably =
by May 30, 2017.
>=20
> Thanks,
> The IESG
>=20
>=20


--Apple-Mail=_6463A540-946E-4BDE-8368-618BE4ABEC35
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQEcBAEBCgAGBQJZEqM5AAoJEK7rdBF357uoQyMH/jNoURZ8AfvAqr/wlZbUwAKh
ZqxP/Nwr3tWtasYF+MWm/jBgYGsz/k2R32UD2xhNvU0JVyrZR+t6pPfQFaLft+wo
LsmAz3vJciQSyVgR8Ai2AeVoJY2ItblqTqYaUIdImy+7XUqkalh4as1Ers2y128F
k6zJYpQtJOA9ZvmpXdzy5UN+QdAHNwLLukBtVHbVSMAKNVBJnbZdyWZ8vkQ/7Y0V
9NGkrxxiap//dvruYgEwIxM3TpTSUUJHN3Mt73d78YlYFaDpH/ptypxxutHge3zD
Bq135vE5mMW6AR5O7uALOlOxECgxSDoWxlTCBHmg2N/+AgEzQqFuEVbDtZYRzEk=
=4a26
-----END PGP SIGNATURE-----

--Apple-Mail=_6463A540-946E-4BDE-8368-618BE4ABEC35--


From nobody Tue May  9 23:03:04 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 C0D7412955F; Tue,  9 May 2017 23:03:01 -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: draft-ietf-netmod-yang-model-classification.all@ietf.org, ietf@ietf.org, netmod@ietf.org
Subject: Genart last call review of draft-ietf-netmod-yang-model-classification-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149439618175.1801.10155387201501790876@ietfa.amsl.com>
Date: Tue, 09 May 2017 23:03:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/plg7MDgWubuCgGzz8jYEI_hHyNU>
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, 10 May 2017 06:03:02 -0000

Reviewer: Pete Resnick
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 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-netmod-yang-model-classification-??
Reviewer: Pete Resnick
Review Date: 2017-05-09
IETF LC End Date: 2017-05-14
IESG Telechat date: Not scheduled for a telechat

Summary: Ready with Minor Issues/Nits

To an outsider like me, this seems like a useful document and it was
an interesting read. The document could use a serious edit for grammar
and typos. A few specific comments below.

Major issues: None.

Minor issues:

In section 2.1, paragraphs 4 and 5 mention "speed". The speed of what?
Development of the module? It's not clear from the text.

In section 3.1, it says:

                          While there is no formal definition of what
   construes an SDO, a common feature is that they publish
   specifications along specific processes with content that reflects
   some sort of membership consensus.  The specifications are
developed
   for wide use among the membership or for audiences beyond that.
   
First of all, s/construes/constitutes. But aside from that, it's not
at all clear to me that a common feature is "membership consensus".
For example, we don't have membership, and many other organizations
use voting and not consensus. Perhaps replace the above with something
simpler like:

                          Most SDOs create specifications according
to
   a formal process in order to produce a standard that is useful for
   their constituencies.

Nits/editorial comments:

In the Abstract and section 3.1, you use "standards-defining
organization" for SDO. I've never heard that phrase used before.
Elsewhere in the document, you use "standards development
organization", which is the phrase I've always seen used. I suggest
you change to that in both places.

Throughout the document, you say things like, "the authors believe" or
"we assume". This is a WG consensus document. While I generally think
that using these terms is bad form in a WG document, saying "the
authors believe" almost sounds like the authors believe it, but the WG
might not. If the authors and the WG believe XYZ, don't say "the
authors believe XYZ" or "we believe XYZ"; just say "XYZ", or at least
use the passive voice. So:

Section 1:

OLD
   The intent of this document is to provide a taxonomy to simplify
   human communication around YANG modules.  The authors acknowledge
   that the classification boundaries are at times blurry, but
believe
   that this document should provide a robust starting point as the
YANG
   community gains further experience with designing and deploying
   modules.  To be more explicit, the authors believe that the
   classification criteria will change over time.
NEW
   The intent of this document is to provide a taxonomy to simplify
   human communication around YANG modules.  While the classification
   boundaries are at times blurry, this document should provide a
robust
   starting point as the YANG community gains further experience with
   designing and deploying modules.  To be more explicit, it is
expected
   that the classification criteria will change over time.
END

Section 2:

OLD
                                                     For the purpose
of
   this document we assume that both approaches (bottom-up and
top-down)
   will be used as they both provide benefits that appeal to
different
   groups.
NEW
                                                     This document
   considers both bottom-up and top-down approaches as they are both
used
   and they each provide benefits that appeal to different groups.
END

Section 2.1:

OLD
                                                     For the purpose
of
   this document we will use the term "orchestrator" to describe a
   system implementing such a process.
NEW
                                                     For the purpose
of
   this document, the term "orchestrator" is used to describe a
system
   implementing such a process.


Section 2.2:

OLD
   Although the [RFC7950], [RFC7950] doesn't explain the relationship
of
   the terms '(YANG) data model' and '(YANG) module', the authors
   understand there is a 1:1 relationship between a data model and a
   YANG module, but a data model may also be expressed using a
   collection of YANG modules (and submodules).

(This one's not even grammatical. Here's my best guess as to what you
meant)

NEW
   Although [RFC7950] doesn't explain the relationship between the
terms
   '(YANG) data model' and '(YANG) module', there is a 1:1
relationship
   between a data model and a YANG module. However, a data model may
   also be expressed using a collection of YANG modules (and
submodules).
   
That's it for all of the "author" and "we" items. One other nit:

3.2 s/augmented into/added into. I don't think you can "augment into"
something.



From nobody Wed May 10 02:34:06 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 142951252BA; Wed, 10 May 2017 02:33:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.126
X-Spam-Level: 
X-Spam-Status: No, score=-6.126 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, RDNS_NONE=0.793, 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 s5z0nkf5o-3X; Wed, 10 May 2017 02:33:56 -0700 (PDT)
Received: from ukmta1.baesystems.com (unknown [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 6EC301243FE; Wed, 10 May 2017 02:33:55 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.38,318,1491260400"; d="scan'208";a="181844680"
Received: from unknown (HELO baemasmds016.greenlnk.net) ([10.15.207.101]) by ukmta1.baesystems.com with ESMTP; 10 May 2017 10:33:19 +0100
X-IronPort-AV: E=Sophos;i="5.38,318,1491260400"; d="scan'208";a="170669235"
Received: from glkxh0004v.greenlnk.net ([10.109.2.35]) by baemasmds016.greenlnk.net with ESMTP; 10 May 2017 10:33:01 +0100
Received: from GLKXM0003V.GREENLNK.net ([169.254.4.172]) by GLKXH0004V.GREENLNK.net ([10.109.2.35]) with mapi id 14.03.0248.002; Wed, 10 May 2017 10:33:00 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Jiazi Yi <ietf@jiaziyi.com>
CC: "ietf@ietf.org" <ietf@ietf.org>, "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multipath@ietf.org" <draft-ietf-manet-olsrv2-multipath@ietf.org>, "manet-chairs@ietf.org" <manet-chairs@ietf.org>
Subject: RE: [manet] Last Call: <draft-ietf-manet-olsrv2-multipath-12.txt> (Multi-path Extension for the Optimized Link State Routing Protocol version 2 (OLSRv2)) to Experimental RFC
Thread-Topic: [manet] Last Call: <draft-ietf-manet-olsrv2-multipath-12.txt> (Multi-path Extension for the Optimized Link State Routing Protocol version 2 (OLSRv2)) to Experimental RFC
Thread-Index: AQHSuiCA8lo3GCHD2k6nFUb/R8wgmaHr37cAgADIFACAAL4IgA==
Date: Wed, 10 May 2017 09:33:00 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6331192@GLKXM0003v.GREENLNK.net>
References: <149272508088.22258.8263343290438640855.idtracker@ietfa.amsl.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6330DE9@GLKXM0003v.GREENLNK.net> <9096512E-3473-473A-B6F1-37CBDD82A0F4@jiaziyi.com>
In-Reply-To: <9096512E-3473-473A-B6F1-37CBDD82A0F4@jiaziyi.com>
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"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/p82JDF6xu_dzntCNXAIB5Vl8eeo>
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, 10 May 2017 09:33:59 -0000

QWRkaXRpb25hbCBjb21tZW50cyA+Pj4gYmVsb3cuIFdoYXQgSSdtIHByb3Bvc2luZyAoc3BlbGxl
ZCBvdXQgYSBiaXQgbW9yZSkgaXMgYWxsIHdpbiwgYW5kIHJlbW92ZXMgcHJvYmxlbXMgd2l0aCB0
aGUgY3VycmVudCBkZXNpZ24uIEkgdGhpbmsgdGhpcyBpcyBhIG11c3QgZG8uDQoNCi0tIA0KQ2hy
aXN0b3BoZXIgRGVhcmxvdmUNClNlbmlvciBQcmluY2lwYWwgRW5naW5lZXINCkJBRSBTeXN0ZW1z
IEFwcGxpZWQgSW50ZWxsaWdlbmNlIExhYm9yYXRvcmllcw0KX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCg0K
VDogwqArNDQgMzMwMCA0Njc1MDAgwqB8IMKgRTogY2hyaXMuZGVhcmxvdmVAYmFlc3lzdGVtcy5j
b20NCg0KQkFFIFN5c3RlbXMgQXBwbGllZCBJbnRlbGxpZ2VuY2UsIENoZWxtc2ZvcmQgVGVjaG5v
bG9neSBQYXJrLCBHcmVhdCBCYWRkb3csIENoZWxtc2ZvcmQsIEVzc2V4IENNMiA4SE4uDQp3d3cu
YmFlc3lzdGVtcy5jb20vYWkNCkJBRSBTeXN0ZW1zIEFwcGxpZWQgSW50ZWxsaWdlbmNlIExpbWl0
ZWQNClJlZ2lzdGVyZWQgaW4gRW5nbGFuZCAmIFdhbGVzIE5vOiAwMTMzNzQ1MQ0KUmVnaXN0ZXJl
ZCBPZmZpY2U6IFN1cnJleSBSZXNlYXJjaCBQYXJrLCBHdWlsZGZvcmQsIFN1cnJleSwgR1UyIDdZ
UA0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBKaWF6aSBZaSBbbWFpbHRv
OmlldGZAamlheml5aS5jb21dIA0KU2VudDogMDkgTWF5IDIwMTcgMjM6NDkNClRvOiBEZWFybG92
ZSwgQ2hyaXN0b3BoZXIgKFVLKQ0KQ2M6IGlldGZAaWV0Zi5vcmc7IElFVEYtQW5ub3VuY2U7IG1h
bmV0QGlldGYub3JnOyBkcmFmdC1pZXRmLW1hbmV0LW9sc3J2Mi1tdWx0aXBhdGhAaWV0Zi5vcmc7
IG1hbmV0LWNoYWlyc0BpZXRmLm9yZw0KU3ViamVjdDogUmU6IFttYW5ldF0gTGFzdCBDYWxsOiA8
ZHJhZnQtaWV0Zi1tYW5ldC1vbHNydjItbXVsdGlwYXRoLTEyLnR4dD4gKE11bHRpLXBhdGggRXh0
ZW5zaW9uIGZvciB0aGUgT3B0aW1pemVkIExpbmsgU3RhdGUgUm91dGluZyBQcm90b2NvbCB2ZXJz
aW9uIDIgKE9MU1J2MikpIHRvIEV4cGVyaW1lbnRhbCBSRkMNCg0KLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLSEgV0FSTklORyAhIC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0gVGhpcyBtZXNzYWdlIG9yaWdp
bmF0ZXMgZnJvbSBvdXRzaWRlIG91ciBvcmdhbmlzYXRpb24sIGVpdGhlciBmcm9tIGFuIGV4dGVy
bmFsIHBhcnRuZXIgb3IgZnJvbSB0aGUgaW50ZXJuZXQuDQpDb25zaWRlciBjYXJlZnVsbHkgd2hl
dGhlciB5b3Ugc2hvdWxkIGNsaWNrIG9uIGFueSBsaW5rcywgb3BlbiBhbnkgYXR0YWNobWVudHMg
b3IgcmVwbHkuDQpGb2xsb3cgdGhlICdSZXBvcnQgU3VzcGljaW91cyBFbWFpbHMnIGxpbmsgb24g
SVQgbWF0dGVycyBmb3IgaW5zdHJ1Y3Rpb25zIG9uIHJlcG9ydGluZyBzdXNwaWNpb3VzIGVtYWls
IG1lc3NhZ2VzLg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0NCg0KSGkgQ2hyaXMsIA0KDQpUaGFua3MgYSBsb3QgZm9yIHRoZSBjb21tZW50
cyEgUGxlYXNlIGNoZWNrIG91ciByZXBseSBpbmxpbmU6IA0KDQo+IE9uIDkgTWF5IDIwMTcsIGF0
IDEyOjEzLCBEZWFybG92ZSwgQ2hyaXN0b3BoZXIgKFVLKSA8Y2hyaXMuZGVhcmxvdmVAYmFlc3lz
dGVtcy5jb20+IHdyb3RlOg0KPiANCj4gQSBmZXcgY29tbWVudHMgb24gdGhpcyBkcmFmdC4NCj4g
DQo+IElQdjYgc3BlY2lmaWVzIGNvbXBsZXRlIHNvdXJjZSByb3V0aW5nLiBCdXQgdGhpcyBzcGVj
aWZpY2F0aW9uIGNhbiBvbmx5IGNvbnNpZGVyIHdoYXQgaGFwcGVucyB3aXRoaW4gdGhlIE1BTkVU
LiBTbyBmb3IgYSBwYWNrZXQgZnJvbSBzb21ld2hlcmUgaW4gdGhlIE1BTkVUIHRvIHNvbWV3aGVy
ZSB3ZWxsIG91dHNpZGUgdGhlIE1BTkVULCB0aGUgcGFja2V0IG11c3QgYmUgc291cmNlIHJvdXRl
ZCB0byB0aGUgZ2F0ZXdheSBiZXR3ZWVuIE1BTkVUIGFuZCByZXN0IG9mIEludGVybmV0LCBhbmQg
bm90IHNvdXJjZSByb3V0ZWQgYWZ0ZXIgdGhhdC4gVGhpcyBJIHRoaW5rIHNob3VsZCBiZSBleHBs
aWNpdGx5IG1lbnRpb25lZC4gV2hldGhlciB0aGF0IGlzIGNvbnNpZGVyZWQgY29tcGxpYW50IHdp
dGggSVB2NiBJIGxlYXZlIHRvIG90aGVycy4NCg0KR29vZCBwb2ludC4gV2UgYWRkZWQgc29tZSB0
ZXh0IGF0IHRoZSBlbmQgb2Ygc2VjdGlvbiA4LjQiIERhdGFncmFtIFByb2Nlc3NpbmcgYXQgdGhl
IE1QLU9MU1J2MiBPcmlnaW5hdG9yIg0KDQo+IA0KPiA3LjEgU1JfYWRkciB3b3VsZCBiZXR0ZXIg
c2F5ICJvcmlnaW5hdG9yIiBhZGRyZXNzIHJhdGhlciB0aGFuIA0KPiAibmV0d29yayIgYWRkcmVz
cy4gKFRoYXQgbWFrZXMgaXQgYW4gYWRkcmVzcyB3aXRob3V0IGEgbmV0bWFzaywgc2VlIA0KPiBS
RkMgNzE4MS4pDQoNCmZpeGVkLiANCg0KPiANCj4gOC4xIFRoaXMgaXMgc3VnZ2VzdGluZyBjcmVh
dGluZyBUQyBtZXNzYWdlcyB0aGF0IGhhdmUgb24gbmVpZ2hib3VyIGFkZHJlc3NlcyBidXQgaGF2
ZSBvbmx5IGEgU09VUkNFX1JPVVRFIFRMVi4gVGhpcyBpcyBub3QgdGhlIGRlc2lnbiBJIHdvdWxk
IGhhdmUgc3VnZ2VzdGVkIGFzIGNvbnNpc3RlbnQgd2l0aCBob3cgSSB3b3VsZCBleHBlY3QgYW4g
ZXh0ZW5zaW9uIHRvIE9MU1J2MiB0byBkbyB0aGluZ3MuIFdlIG5lZWQgdG8gY29uc2lkZXIgdHdv
IGtpbmRzIG9mIHJvdXRlcnM6IHRob3NlIHNlbmRpbmcgVEMgbWVzc2FnZXMgYW55d2F5LCB0aG9z
ZSB0aGF0IChvdGhlciB0aGFuIHRoaXMgZXh0ZW5zaW9uKSBkbyBub3QuIEluIHRoZSBmb3JtZXIg
Y2FzZSB5b3UgY291bGQganVzdCBhZGQgdGhlIFNPVVJDRV9ST1VURSBUTFYgdG8gdGhvc2UgVEMg
bWVzc2FnZXMgaXQgc2VuZHMuIFRoZW4gdGhhdCBpbmZvcm1hdGlvbiBpcyBtYWludGFpbmVkIHVw
IHRvIGRhdGUuIFJvdXRlcnMgdGhhdCBkb24ndCB1c3VhbGx5IHNlbmQgVEMgbWVzc2FnZXMgY291
bGQgc2VuZCBUQyBtZXNzYWdlcyB3aXRoIGp1c3QgdGhhdCBUTFYuIEJ1dCB0aGVuIHRoZXJlJ3Mg
YW4gaXNzdWUgb3ZlciB2YWxpZGl0eSB0aW1lLiBBIHBhcmFtZXRlciBTUl9IT0xEX1RJTUVfTVVM
VElQTElFUiBpcyBpbnRyb2R1Y2VkLiBUaGVyZSdzIG5vIG5lZWQgZm9yIHRoYXQgLSB5b3UgY2Fu
IHNpbXBseSBpbmNvcnBvcmF0ZSB0aGF0IGludG8gdGhlIHZhbGlkaXR5IHRpbWUgcmVjb3JkZWQg
aW4gdGhlIG1lc3NhZ2UuIFRoYXQgYXZvaWRzIGEgbmVlZCB0byBoYW5kbGUgdGhlIHR3byBjYXNl
cyBvZiByb3V0ZXJzIGRpZmZlcmVudGx5LiBUaGVyZSBpcyB0aGVuIGFuIG9kZGl0eSB0aGF0IHlv
dSBnZXQgc29tZSByb3V0ZXJzIHNlbmRpbmcgVEMgbWVzc2FnZXMgd2l0aCBub3JtYWwgdmFsaWRp
dHkgdGltZXMgYW5kIGFkZHJlc3NlcywgYW5kIHNvbWUgdGhhdCBjYW4gYmUgc2VudCBsZXNzIGZy
ZXF1ZW50bHkgd2l0aCBubyBhZGRyZXNzZXMgYW5kIGxvbmdlciB2YWxpZGl0eSB0aW1lcy4gQnV0
IHRoYXQncyBzdXNwZWN0IC0gbm90ZSB0aGF0IGl0J3Mgbm90IGRvbmUgaW4gT0xTUnYyIGZvciBh
dHRhY2hlZCBuZXR3b3JrcyAoYW5vdGhlciByZWFzb24gdG8gc2VuZCBUQyBtZXNzYWdlcyBhbHRo
b3VnaCBubyBuZWlnaGJvdXJzIG5lZWQgcmVwb3J0aW5nKS4gVGhhdCdzIGJlY2F1c2UgbG9uZ2Vy
IGludGVydmFscyBtYWtlIHJlYWN0aW5nIHRvIG5ldyByb3V0ZXJzIGpvaW5pbmcgKGFuZCBuZXR3
b3JrIHJlYXNzZW1ibHkgYWZ0ZXIgZnJhZ21lbnRhdGlvbikgc2xvdy4NCj4gUmF0aGVyIGEgYmV0
dGVyIGRlc2lnbiB3b3VsZCBzaW1wbHkgYmUgdG8gYWRkIFNPVVJDRV9ST1VURSBUTFYgdG8gbm9y
bWFsIFRDIG1lc3NhZ2VzLiBXaGVuIHNlbmRpbmcgVEMgbWVzc2FnZXMgZm9yIGp1c3QgdGhhdCBy
ZWFzb24sIHRoYXQgY291bGQgYmUganVzdCB0aGUgdXN1YWwgY2FzZSwgYnV0IHlvdSBjb3VsZCBh
bGxvdyBhcyBhbiBvcHRpb24gaW4gdGhpcyBjYXNlIHRvIHNlbmQgbGVzcyBmcmVxdWVudGx5IHdp
dGggdmFsaWRpdHkgdGltZSBpbmNyZWFzZWQgYWNjb3JkaW5nbHkuIFdoZW4gbm90IHVzaW5nIHRo
YXQgb3B0aW9uLCBvbmNlIGEgcm91dGVyIG5lZWRzIHRvIHNlbmQgYSBUQyBtZXNzYWdlLCBpdCBj
b3VsZCB0aGVuIGRlY2lkZSB0byByZXBvcnQgbmVpZ2hib3VycywgaW5jcmVhc2luZyB0aGUgdG9w
b2xvZ3kgZGlzdHJpYnV0ZWQgYW5kIGFsbG93aW5nIG1vcmUgcm91dGVzLCB0aGlzIGFsc28gYmVp
bmcgYW4gb3B0aW9uLg0KPiANCg0KSUlSQywgd2UgaGFkIGEgbG9uZyBkaXNjdXNzaW9uIG9uIHRo
aXMgaXNzdWUgYW5kIHByb2R1Y2VkIHRoZSBjdXJyZW50IHRleHQuIA0KVGhlIHB1cnBvc2UgaXMg
dG8gaWRlbnRpZnkgdGhlIHJvdXRlcnMgdGhhdCBkb27igJl0IHNlbmQgVEMgbWVzc2FnZXMgYnV0
IHN1cHBvcnQgc291cmNlIHJvdXRpbmcuIFRvIGF2b2lkIHVubmVjZXNzYXJ5IFRDIGZsb29kaW5n
LCB0aGUgaW50ZXJ2YWwgaXMgbXVjaCBsb25nZXIgdGhhbiB0aGUgbm9ybWFsIFRDIGludGVydmFs
LiANClRoZSBub3JtYWwgVEMgbWVzc2FnZXMgKGdlbmVyYXRlZCBiYXNlZCBvbiBSRkM3MTgxKSBh
bHdheXMgaGF2ZSBhIFNPVVJDRV9ST1VURSBUTFYuIEJ1dCBpZiB3ZSB1c2UgdGhlIHNhbWUgdmFs
aWRpdHkgdGltZSBmb3IgYm90aCBSRkM3MTgxIG5vcm1hbCBUQyBwcm9jZXNzaW5nIGFuZCBNUC1P
TFNSdjIgU1JfUk9VVEUgVExWIHByb2Nlc3NpbmcsIHRoZSB2YWxpZCB0aW1lIGluIHRoZSBTUi1P
TFNSdjIgUm91dGVyIFNldCB3b3VsZCBiZSBtdWNoIHNob3J0ZXIgdGhhbiBleHBlY3RlZC4gQSBw
b3NzaWJsZSBjYXNlIGlzIHRoYXQsIHRoZSByb3V0ZXIgc3RvcHMgc2VuZGluZyBub3JtYWwgVEMg
bWVzc2FnZXMsIHRoZSBjb3JyZXNwb25kaW5nIGVudHJ5IGluIHRoZSBTUi1PTFNSdjIgUm91dGVy
IHNldCB3aWxsIHNvb24gZXhwaXJlLiANClRoZXJlZm9yZSwgSSB0aGluayBpdOKAmXMgcmVhc29u
YWJsZSB0byBtYWtlIHVzZSBvZiB0aGUgU1JfSE9MRF9USU1FX01VTFRJUExJRVIgdG8gZGlzdGlu
Z3Vpc2ggdGhlIHZhbGlkIHRpbWUgb2Ygbm9ybWFsIFRDIG1lc3NhZ2UgaW5mb3JtYXRpb24gYW5k
IFNSX1JPVVRFIGluZm9ybWF0aW9uLiANCg0KPj4+IEkgZG9uJ3QgYWdyZWUsIGFuZCBJIHRoaW5r
IHdoYXQgeW91IGFyZSBzdWdnZXN0aW5nIGludHJvZHVjZXMgYSBwcm9ibGVtIGFuZCB1bm5lY2Vz
c2FyeSBvdmVyaGVhZC4NCg0KPj4+IFRoZSBwcm9ibGVtIGlzIHRoYXQgZXZlcnl3aGVyZSBpbiBP
TFNSdjIgd2UgYXJlIGNhcmVmdWwgdG8gZW5zdXJlIHRoYXQgcGFyYW1ldGVycyBjYW4gYmUgaW5k
ZXBlbmRlbnRseSBzZXQsIGFuZCB0aGF0IHJvdXRlcnMgZG9uJ3QgbmVlZCB0byBjb29yZGluYXRl
IHRvIGludGVyb3BlcmF0ZS4gKFRoZXkgbWF5IGRvIGJldHRlciBpZiB0aGV5IGRvLCBidXQgdGhh
dCdzIGEgcmVmaW5lbWVudC4pIEhlcmUgeW91IGFyZSB1c2luZyBhbiBTUl9IT0xEX1RJTUVfTVVM
VElQTElFUiB0aGF0IHRoZSByZWNlaXZlciBoYXMgdG8ga25vdyBpcyB3aGF0IHRoZSBzZW5kZXIg
aW50ZW5kcy4gQW5kIGl0J3MgdW5uZWNlc3NhcnkuIElmIGFsbCB0aGF0J3MgaW4gdGhlIFRDIG1l
c3NhZ2UgaXMgdGhlIFNPVVJDRV9ST1VURSBUTFYsIHlvdSBjYW4ganVzdCBnaXZlIHRoYXQgYSBs
b25nZXIgdmFsaWRpdHkgdGltZSwgYmVjYXVzZSB0aGUgb25seSB0aGluZyB0aGF0IHZhbGlkaXR5
IHRpbWUgd2lsbCBpbXBhY3Qgb24gaXMgdGhlIHNvdXJjZSByb3V0aW5nIHN0YXR1cy4gSWYgdGhl
IHJvdXRlciBpcyBhbHNvIHNlbmRpbmcgbm9ybWFsIFRDIG1lc3NhZ2VzIGFuZCB5b3Ugc2VuZCBz
ZXBhcmF0ZSBTT1VSQ0VfUk9VVEUgVExWIFRDIG1lc3NhZ2VzIHRoZW4gdGhhdCB3b3VsZCBzdGls
bCBiZSBzby4gQnV0IHRoYXQncyBpbmVmZmljaWVudCwgYmVjYXVzZSBpZiB0aGUgcm91dGVyIGlz
IGFscmVhZHkgc2VuZGluZyBUQyBtZXNzYWdlcywgd2h5IHNlbmQgc2VwYXJhdGUgb25lcyB3aXRo
IGFkZGVkIG92ZXJoZWFkLCB3aGVuIHlvdSBjYW4gcHV0IHRoZSBTT1VSQ0VfUk9VVEUgVExWIGlu
IHRoZSBzYW1lIFRDIG1lc3NhZ2U/IFRoYXQgd291bGQgdGhlbiAod2l0aG91dCBTUl9IT0xEX1RJ
TUVfTVVMVElQTElFUiwgYnV0IHRoYXQncyBhIGdvb2QgdGhpbmcgYmVjYXVzZSBTUl9IT0xEX1RJ
TUVfTVVMVElQTElFUiBpcyBub3QgZ29vZCkgZ2l2ZSBhIHNob3J0ZXIgdmFsaWRpdHkgdGltZSB0
byB0aGUgU09VUkNFX1JPVVRFIFRMViwgYnV0IHRoYXQncyBmaW5lLCBiZWNhdXNlIHRoYXQgcm91
dGVyIHdpbGwgYmUgc2VuZGluZyBtb3JlIFRDIG1lc3NhZ2VzIHdpdGhpbiB0aGF0IHRpbWVzY2Fs
ZSBhbnl3YXkuIEZ1cnRoZXJtb3JlLCB0aGlzIGFsc28gYWxsb3dzIHRoZSByb3V0ZXIgdGhhdCdz
IHNlbmRpbmcgVEMgbWVzc2FnZXMgbW9yZSBmcmVxdWVudGx5IHRvIHByb3ZpZGUgaXRzIGluZm9y
bWF0aW9uIG1vcmUgcmVzcG9uc2l2ZWx5IGluIHRoZSBjYXNlcyBvZiBub2RlcyBqb2luaW5nIGFu
ZCBuZXR3b3JrcyByZWFzc2VtYmxpbmcuDQoNCj4+PiBUaGF0IGdpdmVzIHR3byBiZWhhdmlvdXJz
OiByb3V0ZXJzIHNlbmRpbmcgVEMgbWVzc2FnZXMgYW55d2F5LCBqdXN0IGFkZCBhIFNPVVJDRV9S
T1VURSBUTFYsIGFuZCByb3V0ZXJzIG5vdCBzZW5kaW5nIFRDIG1lc3NhZ2VzIG90aGVyd2lzZSwg
anVzdCBpbmNsdWRlIGEgU09VUkNFX1JPVVRFIFRMViBhbmQgc2V0IHRoZSB2YWxpZGl0eSB0aW1l
IGFjY29yZGluZyB0byB3aGF0IHNjaGVkdWxlIHRoYXQgcm91dGVyIGNob29zZXMgdG8gdXNlIC0g
d2hpY2ggY2FuIGJlIGF0IHRoZSBzYW1lIHJhdGUgYXMgdGhlIG90aGVyIHJvdXRlcnMsIG9yIGF0
IGEgc2xvd2VyIHJvdXRlLCBvciAoYSBuZXcgY2FwYWJpbGl0eSB5b3UgZG9uJ3QgaGF2ZSkgc2xv
d2x5LCBleGNlcHQgaWYgeW91IGxlYXJuIG9mIHRoZSBleGlzdGVuY2Ugb2YgYSBuZXcgcm91dGVy
IGluIHRoZSBuZXR3b3JrIHlvdSBjYW4gc2VuZCBvbmUgb3IgbW9yZSByZXNwb25zaXZlIFNPVVJD
RV9ST1VURSBUTFYgb25seSBUTFZzIHRvIGVuYWJsZSB0aGF0IG5ldyByb3V0ZXIgKG9yIHJvdXRl
cnMpIHRvIGxlYXJuIG9mIHRoZSBzb3VyY2Ugcm91dGluZyBxdWlja2VyLg0KDQo+Pj4gSXQncyBh
bGwgd2luOiBjb21iaW5pbmcgbWVzc2FnZXMsIHNvdXJjZSBzZXQgY29udHJvbCwgYWJpbGl0eSB0
byBkbyBtb3JlIGNsZXZlciB0aGluZ3MgaWYgeW91IHdhbnQgdG8uIChZb3UgY291bGQgcHJvYmFi
bHkgIGV2ZW4gc3RpbGwgc2VuZCBzZXBhcmF0ZSBUQyBtZXNzYWdlcyB3aXRoIGEgU09VUkNFX1JP
VVRFIFRMViB3aGVuIGFsc28gc2VuZGluZyBub3JtYWwgVEMgbWVzc2FnZXMgaWYgeW91IHJlYWxs
eSB3YW50ZWQgdG8sIGFzIGFuIG9wdGlvbiBJIGNhbid0IHNlZSB3YW50aW5nIHRvIHVzZSAtIGFs
dGhvdWdoIGl0IG1pZ2h0IGludHJvZHVjZSBhIG1pbm9yIHByb2JsZW0gdGhhdCBJIGhhdmVuJ3Qg
d29ya2VkIHRocm91Z2ggdGhlIE9MU1J2MiBzcGVjaWZpY2F0aW9uIHRvIGNoZWNrLCBiZWNhdXNl
IGl0J3MgdW5uZWNlc3NhcnkuKQ0KDQo+Pj4gVGhlIHBvaW50IGlzIHRoYXQgd2hhdCBJIHN1Z2dl
c3QgY2FuIGdhaW4gZXZlcnl0aGluZyB5b3UgZG8sIGFuZCBhbGxvdyBtb3JlLCBwbHVzIG5vdCBi
cmVha2luZyBleHBlY3RlZCBPTFNSdjIgYmVoYXZpb3VyLg0KDQo+IDguMyBzZWNvbmQgYnVsbGV0
LiBZb3Ugc2hvdWxkIGhlcmUgKGFuZCBwb3NzaWJseSBlbHNld2hlcmUpIGV4Y2x1ZGUgcm91dGVy
cyB3aXRoIHJvdXRpbmcgd2lsbGluZ25lc3MgemVyby4NCg0KPiANCj4gOC4zIHRoZXJlIHNlZW1z
IHRvIGJlIGFuIGluY29uc2lzdGVuY3kuIFdoZW4gb3BlcmF0aW5nIHByb2FjdGl2ZWx5IGFuZCBu
byBtdWx0aXBsZSByb3V0ZXMsIGRyb3AgdGhlIHBhY2tldCwgYnV0IHJlYWN0aXZlbHkgdXNlIHN0
YW5kYXJkIHJvdXRpbmcuIFRoZSBsYXR0ZXIgc2VlbXMgbW9yZSBhcHByb3ByaWF0ZSBpbiB0aGUg
Zm9ybWVyIGNhc2UgYWxzby4NCj4gDQo+IDkgQ1VUT0ZGX1JBVElPLiBJbnNpc3RzIG9mIHN0cmlj
dGx5LCBidXQgYXMgZGVmaW5lZCBlYXJsaWVyLCBtYXkgYmUgPj0gMWAuDQoNCkFsbCBmaXhlZC4g
DQoNClRoYW5rcyBhZ2FpbiBmb3IgdGhlIHZhbHVhYmxlIGNvbW1lbnRzIQ0KDQpiZXN0DQoNCkpp
YXppDQoNCj4gDQo+IC0tDQo+IENocmlzdG9waGVyIERlYXJsb3ZlDQo+IFNlbmlvciBQcmluY2lw
YWwgRW5naW5lZXINCj4gQkFFIFN5c3RlbXMgQXBwbGllZCBJbnRlbGxpZ2VuY2UgTGFib3JhdG9y
aWVzIA0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQo+IF9fX18NCj4gDQo+IFQ6ICArNDQgMzMwMCA0Njc1MDAg
IHwgIEU6IGNocmlzLmRlYXJsb3ZlQGJhZXN5c3RlbXMuY29tDQo+IA0KPiBCQUUgU3lzdGVtcyBB
cHBsaWVkIEludGVsbGlnZW5jZSwgQ2hlbG1zZm9yZCBUZWNobm9sb2d5IFBhcmssIEdyZWF0IEJh
ZGRvdywgQ2hlbG1zZm9yZCwgRXNzZXggQ00yIDhITi4NCj4gd3d3LmJhZXN5c3RlbXMuY29tL2Fp
DQo+IEJBRSBTeXN0ZW1zIEFwcGxpZWQgSW50ZWxsaWdlbmNlIExpbWl0ZWQgUmVnaXN0ZXJlZCBp
biBFbmdsYW5kICYgV2FsZXMgDQo+IE5vOiAwMTMzNzQ1MSBSZWdpc3RlcmVkIE9mZmljZTogU3Vy
cmV5IFJlc2VhcmNoIFBhcmssIEd1aWxkZm9yZCwgDQo+IFN1cnJleSwgR1UyIDdZUA0KPiANCj4g
DQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IG1hbmV0IFttYWlsdG86bWFu
ZXQtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFRoZSBJRVNHDQo+IFNlbnQ6IDIwIEFw
cmlsIDIwMTcgMjI6NTENCj4gVG86IElFVEYtQW5ub3VuY2UNCj4gQ2M6IG1hbmV0QGlldGYub3Jn
OyBkcmFmdC1pZXRmLW1hbmV0LW9sc3J2Mi1tdWx0aXBhdGhAaWV0Zi5vcmc7IA0KPiBtYW5ldC1j
aGFpcnNAaWV0Zi5vcmcNCj4gU3ViamVjdDogW21hbmV0XSBMYXN0IENhbGw6IDxkcmFmdC1pZXRm
LW1hbmV0LW9sc3J2Mi1tdWx0aXBhdGgtMTIudHh0PiANCj4gKE11bHRpLXBhdGggRXh0ZW5zaW9u
IGZvciB0aGUgT3B0aW1pemVkIExpbmsgU3RhdGUgUm91dGluZyBQcm90b2NvbCANCj4gdmVyc2lv
biAyIChPTFNSdjIpKSB0byBFeHBlcmltZW50YWwgUkZDDQo+IA0KPiAtLS0tLS0tLS0tLS0tLS0t
LS0tLS0tISBXQVJOSU5HICEgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSBUaGlzIG1lc3NhZ2Ugb3Jp
Z2luYXRlcyBmcm9tIG91dHNpZGUgb3VyIG9yZ2FuaXNhdGlvbiwgZWl0aGVyIGZyb20gYW4gZXh0
ZXJuYWwgcGFydG5lciBvciBmcm9tIHRoZSBpbnRlcm5ldC4NCj4gQ29uc2lkZXIgY2FyZWZ1bGx5
IHdoZXRoZXIgeW91IHNob3VsZCBjbGljayBvbiBhbnkgbGlua3MsIG9wZW4gYW55IGF0dGFjaG1l
bnRzIG9yIHJlcGx5Lg0KPiBGb2xsb3cgdGhlICdSZXBvcnQgU3VzcGljaW91cyBFbWFpbHMnIGxp
bmsgb24gSVQgbWF0dGVycyBmb3IgaW5zdHJ1Y3Rpb25zIG9uIHJlcG9ydGluZyBzdXNwaWNpb3Vz
IGVtYWlsIG1lc3NhZ2VzLg0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiANCj4gKioqIFdBUk5JTkcgKioqDQo+IEVYVEVSTkFMIEVN
QUlMIC0tIFRoaXMgbWVzc2FnZSBvcmlnaW5hdGVzIGZyb20gb3V0c2lkZSBvdXIgb3JnYW5pemF0
aW9uLg0KPiANCj4gDQo+IFRoZSBJRVNHIGhhcyByZWNlaXZlZCBhIHJlcXVlc3QgZnJvbSB0aGUg
TW9iaWxlIEFkLWhvYyBOZXR3b3JrcyBXRw0KPiAobWFuZXQpIHRvIGNvbnNpZGVyIHRoZSBmb2xs
b3dpbmcgZG9jdW1lbnQ6DQo+IC0gJ011bHRpLXBhdGggRXh0ZW5zaW9uIGZvciB0aGUgT3B0aW1p
emVkIExpbmsgU3RhdGUgUm91dGluZyBQcm90b2NvbA0KPiAgIHZlcnNpb24gMiAoT0xTUnYyKScN
Cj4gIDxkcmFmdC1pZXRmLW1hbmV0LW9sc3J2Mi1tdWx0aXBhdGgtMTIudHh0PiBhcyBFeHBlcmlt
ZW50YWwgUkZDDQo+IA0KPiBUaGUgSUVTRyBwbGFucyB0byBtYWtlIGEgZGVjaXNpb24gaW4gdGhl
IG5leHQgZmV3IHdlZWtzLCBhbmQgc29saWNpdHMgZmluYWwgY29tbWVudHMgb24gdGhpcyBhY3Rp
b24uIFBsZWFzZSBzZW5kIHN1YnN0YW50aXZlIGNvbW1lbnRzIHRvIHRoZSBpZXRmQGlldGYub3Jn
IG1haWxpbmcgbGlzdHMgYnkgMjAxNy0wNS0wNC4gRXhjZXB0aW9uYWxseSwgY29tbWVudHMgbWF5
IGJlIHNlbnQgdG8gaWVzZ0BpZXRmLm9yZyBpbnN0ZWFkLiBJbiBlaXRoZXIgY2FzZSwgcGxlYXNl
IHJldGFpbiB0aGUgYmVnaW5uaW5nIG9mIHRoZSBTdWJqZWN0IGxpbmUgdG8gYWxsb3cgYXV0b21h
dGVkIHNvcnRpbmcuDQo+IA0KPiBBYnN0cmFjdA0KPiANCj4gDQo+ICAgVGhpcyBkb2N1bWVudCBz
cGVjaWZpZXMgYSBtdWx0aS1wYXRoIGV4dGVuc2lvbiBmb3IgdGhlIE9wdGltaXplZCBMaW5rDQo+
ICAgU3RhdGUgUm91dGluZyBQcm90b2NvbCB2ZXJzaW9uIDIgKE9MU1J2MikgdG8gZGlzY292ZXIg
bXVsdGlwbGUNCj4gICBkaXNqb2ludCBwYXRocywgc28gYXMgdG8gaW1wcm92ZSByZWxpYWJpbGl0
eSBvZiB0aGUgT0xTUnYyIHByb3RvY29sLg0KPiAgIFRoZSBpbnRlcm9wZXJhYmlsaXR5IHdpdGgg
T0xTUnYyIGlzIHJldGFpbmVkLg0KPiANCj4gDQo+IA0KPiANCj4gVGhlIGZpbGUgY2FuIGJlIG9i
dGFpbmVkIHZpYQ0KPiBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRm
LW1hbmV0LW9sc3J2Mi1tdWx0aXBhdGgvDQo+IA0KPiBJRVNHIGRpc2N1c3Npb24gY2FuIGJlIHRy
YWNrZWQgdmlhDQo+IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYt
bWFuZXQtb2xzcnYyLW11bHRpcGF0aC9iYWwNCj4gbG90Lw0KPiANCj4gDQo+IE5vIElQUiBkZWNs
YXJhdGlvbnMgaGF2ZSBiZWVuIHN1Ym1pdHRlZCBkaXJlY3RseSBvbiB0aGlzIEktRC4NCj4gDQo+
IA0KPiANCj4gDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fDQo+IG1hbmV0IG1haWxpbmcgbGlzdA0KPiBtYW5ldEBpZXRmLm9yZw0KPiBodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21hbmV0DQo+IA0KPiANCj4gKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioN
Cj4gVGhpcyBlbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGFyZSBjb25maWRlbnRpYWwgdG8gdGhl
IGludGVuZGVkIA0KPiByZWNpcGllbnQgYW5kIG1heSBhbHNvIGJlIHByaXZpbGVnZWQuIElmIHlv
dSBhcmUgbm90IHRoZSBpbnRlbmRlZCANCj4gcmVjaXBpZW50IHBsZWFzZSBkZWxldGUgaXQgZnJv
bSB5b3VyIHN5c3RlbSBhbmQgbm90aWZ5IHRoZSBzZW5kZXIuDQo+IFlvdSBzaG91bGQgbm90IGNv
cHkgaXQgb3IgdXNlIGl0IGZvciBhbnkgcHVycG9zZSBub3IgZGlzY2xvc2Ugb3IgDQo+IGRpc3Ry
aWJ1dGUgaXRzIGNvbnRlbnRzIHRvIGFueSBvdGhlciBwZXJzb24uDQo+ICoqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqDQo+
IA0KDQoNCg==


From nobody Wed May 10 05:41:19 2017
Return-Path: <ietf@jiaziyi.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 34D89129423; Wed, 10 May 2017 05:41:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Level: 
X-Spam-Status: No, score=-2.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_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=jiaziyi.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 OWAdAhhi0b8G; Wed, 10 May 2017 05:41:06 -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 B4278126DFB; Wed, 10 May 2017 05:41:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1494420062;  s=jiazi; d=jiaziyi.com; i=ietf@jiaziyi.com; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References; l=68805; bh=pFsjUVy51QkluRZLisUECPt+Vcpd01JEttGel8Unjhw=; b=flHvQY3EmpsHn/f4T3SxDFBBAo2iWFrpk+ohCkcEQkm3p6KQprbk5yHeMMdQ9KyR D1KgNzR4dMzAr89SQxjvvzSq3ks7eyjnHWFwUU767LqTXtkiwgBNZDboc3jsJVm3P3m LBcyQUxw/OqVB7SRlm+MQaV/0DU4Yh5P0mlh9PzA=
Received: from [129.104.72.106] (129.104.72.106 [129.104.72.106]) by mx.zohomail.com with SMTPS id 1494420062336240.46827593410194; Wed, 10 May 2017 05:41:02 -0700 (PDT)
From: Jiazi Yi <ietf@jiaziyi.com>
Message-Id: <03E51133-21B1-45EE-8888-52D251667891@jiaziyi.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4BD8F23A-41E1-49F4-B7A6-D52C72BFF50B"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [manet] Last Call: <draft-ietf-manet-olsrv2-multipath-12.txt> (Multi-path Extension for the Optimized Link State Routing Protocol version 2 (OLSRv2)) to Experimental RFC
Date: Wed, 10 May 2017 14:40:59 +0200
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6331192@GLKXM0003v.GREENLNK.net>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multipath@ietf.org" <draft-ietf-manet-olsrv2-multipath@ietf.org>,  "manet-chairs@ietf.org" <manet-chairs@ietf.org>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
References: <149272508088.22258.8263343290438640855.idtracker@ietfa.amsl.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6330DE9@GLKXM0003v.GREENLNK.net> <9096512E-3473-473A-B6F1-37CBDD82A0F4@jiaziyi.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6331192@GLKXM0003v.GREENLNK.net>
X-Mailer: Apple Mail (2.3273)
X-ZohoMailClient: External
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Igd9R-6Kj4ozM9vB2mPS94UlfIg>
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, 10 May 2017 12:41:09 -0000

--Apple-Mail=_4BD8F23A-41E1-49F4-B7A6-D52C72BFF50B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Chris,=20

OK, it makes sense. So the policy will be:

	- the SOURCE_ROUTE TLV won=E2=80=99t have any value
	- Every TC message originated by the source-route supported =
routers will have a SOURCE_ROUTE TLV
	- The TC message not containing any neighbour address will have =
a longer validity time compared to OLSRv2 normal TC messages.=20

best

Jiazi


> On 10 May 2017, at 11:33, Dearlove, Christopher (UK) =
<chris.dearlove@baesystems.com> wrote:
>=20
> Additional comments >>> below. What I'm proposing (spelled out a bit =
more) is all win, and removes problems with the current design. I think =
this is a must do.
>=20
> --=20
> Christopher Dearlove
> Senior Principal Engineer
> BAE Systems Applied Intelligence Laboratories
> =
__________________________________________________________________________=

>=20
> T:  +44 3300 467500  |  E: chris.dearlove@baesystems.com =
<mailto:chris.dearlove@baesystems.com>
>=20
> BAE Systems Applied Intelligence, Chelmsford Technology Park, Great =
Baddow, Chelmsford, Essex CM2 8HN.
> www.baesystems.com/ai <http://www.baesystems.com/ai>
> BAE Systems Applied Intelligence Limited
> Registered in England & Wales No: 01337451
> Registered Office: Surrey Research Park, Guildford, Surrey, GU2 7YP
>=20
>=20
> -----Original Message-----
> From: Jiazi Yi [mailto:ietf@jiaziyi.com <mailto:ietf@jiaziyi.com>]=20
> Sent: 09 May 2017 23:49
> To: Dearlove, Christopher (UK)
> Cc: ietf@ietf.org <mailto:ietf@ietf.org>; IETF-Announce; =
manet@ietf.org <mailto:manet@ietf.org>; =
draft-ietf-manet-olsrv2-multipath@ietf.org =
<mailto:draft-ietf-manet-olsrv2-multipath@ietf.org>; =
manet-chairs@ietf.org <mailto:manet-chairs@ietf.org>
> Subject: Re: [manet] Last Call: =
<draft-ietf-manet-olsrv2-multipath-12.txt> (Multi-path Extension for the =
Optimized Link State Routing Protocol version 2 (OLSRv2)) to =
Experimental RFC
>=20
> ----------------------! WARNING ! ---------------------- This message =
originates from outside our organisation, either from an external =
partner or from the internet.
> Consider carefully whether you should click on any links, open any =
attachments or reply.
> Follow the 'Report Suspicious Emails' link on IT matters for =
instructions on reporting suspicious email messages.
> --------------------------------------------------------
>=20
> Hi Chris,=20
>=20
> Thanks a lot for the comments! Please check our reply inline:=20
>=20
>> On 9 May 2017, at 12:13, Dearlove, Christopher (UK) =
<chris.dearlove@baesystems.com> wrote:
>>=20
>> A few comments on this draft.
>>=20
>> IPv6 specifies complete source routing. But this specification can =
only consider what happens within the MANET. So for a packet from =
somewhere in the MANET to somewhere well outside the MANET, the packet =
must be source routed to the gateway between MANET and rest of Internet, =
and not source routed after that. This I think should be explicitly =
mentioned. Whether that is considered compliant with IPv6 I leave to =
others.
>=20
> Good point. We added some text at the end of section 8.4" Datagram =
Processing at the MP-OLSRv2 Originator"
>=20
>>=20
>> 7.1 SR_addr would better say "originator" address rather than=20
>> "network" address. (That makes it an address without a netmask, see=20=

>> RFC 7181.)
>=20
> fixed.=20
>=20
>>=20
>> 8.1 This is suggesting creating TC messages that have on neighbour =
addresses but have only a SOURCE_ROUTE TLV. This is not the design I =
would have suggested as consistent with how I would expect an extension =
to OLSRv2 to do things. We need to consider two kinds of routers: those =
sending TC messages anyway, those that (other than this extension) do =
not. In the former case you could just add the SOURCE_ROUTE TLV to those =
TC messages it sends. Then that information is maintained up to date. =
Routers that don't usually send TC messages could send TC messages with =
just that TLV. But then there's an issue over validity time. A parameter =
SR_HOLD_TIME_MULTIPLIER is introduced. There's no need for that - you =
can simply incorporate that into the validity time recorded in the =
message. That avoids a need to handle the two cases of routers =
differently. There is then an oddity that you get some routers sending =
TC messages with normal validity times and addresses, and some that can =
be sent less frequently with no addresses and longer validity times. But =
that's suspect - note that it's not done in OLSRv2 for attached networks =
(another reason to send TC messages although no neighbours need =
reporting). That's because longer intervals make reacting to new routers =
joining (and network reassembly after fragmentation) slow.
>> Rather a better design would simply be to add SOURCE_ROUTE TLV to =
normal TC messages. When sending TC messages for just that reason, that =
could be just the usual case, but you could allow as an option in this =
case to send less frequently with validity time increased accordingly. =
When not using that option, once a router needs to send a TC message, it =
could then decide to report neighbours, increasing the topology =
distributed and allowing more routes, this also being an option.
>>=20
>=20
> IIRC, we had a long discussion on this issue and produced the current =
text.=20
> The purpose is to identify the routers that don=E2=80=99t send TC =
messages but support source routing. To avoid unnecessary TC flooding, =
the interval is much longer than the normal TC interval.=20
> The normal TC messages (generated based on RFC7181) always have a =
SOURCE_ROUTE TLV. But if we use the same validity time for both RFC7181 =
normal TC processing and MP-OLSRv2 SR_ROUTE TLV processing, the valid =
time in the SR-OLSRv2 Router Set would be much shorter than expected. A =
possible case is that, the router stops sending normal TC messages, the =
corresponding entry in the SR-OLSRv2 Router set will soon expire.=20
> Therefore, I think it=E2=80=99s reasonable to make use of the =
SR_HOLD_TIME_MULTIPLIER to distinguish the valid time of normal TC =
message information and SR_ROUTE information.=20
>=20
>>>> I don't agree, and I think what you are suggesting introduces a =
problem and unnecessary overhead.
>=20
>>>> The problem is that everywhere in OLSRv2 we are careful to ensure =
that parameters can be independently set, and that routers don't need to =
coordinate to interoperate. (They may do better if they do, but that's a =
refinement.) Here you are using an SR_HOLD_TIME_MULTIPLIER that the =
receiver has to know is what the sender intends. And it's unnecessary. =
If all that's in the TC message is the SOURCE_ROUTE TLV, you can just =
give that a longer validity time, because the only thing that validity =
time will impact on is the source routing status. If the router is also =
sending normal TC messages and you send separate SOURCE_ROUTE TLV TC =
messages then that would still be so. But that's inefficient, because if =
the router is already sending TC messages, why send separate ones with =
added overhead, when you can put the SOURCE_ROUTE TLV in the same TC =
message? That would then (without SR_HOLD_TIME_MULTIPLIER, but that's a =
good thing because SR_HOLD_TIME_MULTIPLIER is not good) give a shorter =
validity time to the SOURCE_ROUTE TLV, but that's fine, because that =
router will be sending more TC messages within that timescale anyway. =
Furthermore, this also allows the router that's sending TC messages more =
frequently to provide its information more responsively in the cases of =
nodes joining and networks reassembling.
>=20
>>>> That gives two behaviours: routers sending TC messages anyway, just =
add a SOURCE_ROUTE TLV, and routers not sending TC messages otherwise, =
just include a SOURCE_ROUTE TLV and set the validity time according to =
what schedule that router chooses to use - which can be at the same rate =
as the other routers, or at a slower route, or (a new capability you =
don't have) slowly, except if you learn of the existence of a new router =
in the network you can send one or more responsive SOURCE_ROUTE TLV only =
TLVs to enable that new router (or routers) to learn of the source =
routing quicker.
>=20
>>>> It's all win: combining messages, source set control, ability to do =
more clever things if you want to. (You could probably  even still send =
separate TC messages with a SOURCE_ROUTE TLV when also sending normal TC =
messages if you really wanted to, as an option I can't see wanting to =
use - although it might introduce a minor problem that I haven't worked =
through the OLSRv2 specification to check, because it's unnecessary.)
>=20
>>>> The point is that what I suggest can gain everything you do, and =
allow more, plus not breaking expected OLSRv2 behaviour.
>=20
>> 8.3 second bullet. You should here (and possibly elsewhere) exclude =
routers with routing willingness zero.
>=20
>>=20
>> 8.3 there seems to be an inconsistency. When operating proactively =
and no multiple routes, drop the packet, but reactively use standard =
routing. The latter seems more appropriate in the former case also.
>>=20
>> 9 CUTOFF_RATIO. Insists of strictly, but as defined earlier, may be =
>=3D 1`.
>=20
> All fixed.=20
>=20
> Thanks again for the valuable comments!
>=20
> best
>=20
> Jiazi
>=20
>>=20
>> --
>> Christopher Dearlove
>> Senior Principal Engineer
>> BAE Systems Applied Intelligence Laboratories=20
>> =
______________________________________________________________________
>> ____
>>=20
>> T:  +44 3300 467500  |  E: chris.dearlove@baesystems.com
>>=20
>> BAE Systems Applied Intelligence, Chelmsford Technology Park, Great =
Baddow, Chelmsford, Essex CM2 8HN.
>> www.baesystems.com/ai
>> BAE Systems Applied Intelligence Limited Registered in England & =
Wales=20
>> No: 01337451 Registered Office: Surrey Research Park, Guildford,=20
>> Surrey, GU2 7YP
>>=20
>>=20
>> -----Original Message-----
>> From: manet [mailto:manet-bounces@ietf.org] On Behalf Of The IESG
>> Sent: 20 April 2017 22:51
>> To: IETF-Announce
>> Cc: manet@ietf.org; draft-ietf-manet-olsrv2-multipath@ietf.org;=20
>> manet-chairs@ietf.org
>> Subject: [manet] Last Call: =
<draft-ietf-manet-olsrv2-multipath-12.txt>=20
>> (Multi-path Extension for the Optimized Link State Routing Protocol=20=

>> version 2 (OLSRv2)) to Experimental RFC
>>=20
>> ----------------------! WARNING ! ---------------------- This message =
originates from outside our organisation, either from an external =
partner or from the internet.
>> Consider carefully whether you should click on any links, open any =
attachments or reply.
>> Follow the 'Report Suspicious Emails' link on IT matters for =
instructions on reporting suspicious email messages.
>> --------------------------------------------------------
>>=20
>> *** WARNING ***
>> EXTERNAL EMAIL -- This message originates from outside our =
organization.
>>=20
>>=20
>> The IESG has received a request from the Mobile Ad-hoc Networks WG
>> (manet) to consider the following document:
>> - 'Multi-path Extension for the Optimized Link State Routing Protocol
>>  version 2 (OLSRv2)'
>> <draft-ietf-manet-olsrv2-multipath-12.txt> as Experimental RFC
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits =
final comments on this action. Please send substantive comments to the =
ietf@ietf.org mailing lists by 2017-05-04. Exceptionally, comments may =
be sent to iesg@ietf.org instead. In either case, please retain the =
beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>=20
>>  This document specifies a multi-path extension for the Optimized =
Link
>>  State Routing Protocol version 2 (OLSRv2) to discover multiple
>>  disjoint paths, so as to improve reliability of the OLSRv2 protocol.
>>  The interoperability with OLSRv2 is retained.
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-multipath/
>>=20
>> IESG discussion can be tracked via
>> =
https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-multipath/bal
>> lot/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>>=20
>>=20
>> ********************************************************************
>> This email and any attachments are confidential to the intended=20
>> recipient and may also be privileged. If you are not the intended=20
>> recipient please delete it from your system and notify the sender.
>> You should not copy it or use it for any purpose nor disclose or=20
>> distribute its contents to any other person.
>> ********************************************************************


--Apple-Mail=_4BD8F23A-41E1-49F4-B7A6-D52C72BFF50B
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"">Hi Chris,&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">OK, it makes sense. So the policy will =
be:</div><div class=3D""><br class=3D""></div><div class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>- the =
SOURCE_ROUTE TLV won=E2=80=99t have any value</div><div class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>- Every =
TC message originated by the source-route supported routers will have a =
SOURCE_ROUTE TLV</div><div class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>- The TC message not containing =
any neighbour address will have a longer validity time compared to =
OLSRv2 normal TC messages.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">best</div><div class=3D""><br =
class=3D""></div><div class=3D"">Jiazi</div><div class=3D""><br =
class=3D""></div><br class=3D""><div><blockquote type=3D"cite" =
class=3D""><div class=3D"">On 10 May 2017, at 11:33, Dearlove, =
Christopher (UK) &lt;<a href=3D"mailto:chris.dearlove@baesystems.com" =
class=3D"">chris.dearlove@baesystems.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">Additional comments &gt;&gt;&gt; =
below. What I'm proposing (spelled out a bit more) is all win, and =
removes problems with the current design. I think this is a must =
do.</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">--<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Christopher Dearlove</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Senior Principal Engineer</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">BAE Systems Applied Intelligence =
Laboratories</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" =
class=3D"">_______________________________________________________________=
___________</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">T: &nbsp;+44 3300 467500 &nbsp;| =
&nbsp;E:<span class=3D"Apple-converted-space">&nbsp;</span></span><a =
href=3D"mailto:chris.dearlove@baesystems.com" style=3D"font-family: =
Helvetica; font-size: 12px; 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"">chris.dearlove@baesystems.com</a><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">BAE Systems Applied Intelligence, Chelmsford =
Technology Park, Great Baddow, Chelmsford, Essex CM2 8HN.</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><a =
href=3D"http://www.baesystems.com/ai" style=3D"font-family: Helvetica; =
font-size: 12px; 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"">www.baesystems.com/ai</a><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">BAE Systems Applied Intelligence =
Limited</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">Registered in England &amp; Wales No: =
01337451</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">Registered Office: Surrey Research Park, =
Guildford, Surrey, GU2 7YP</span><br style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br=
 style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">-----Original Message-----</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">From: Jiazi Yi [</span><a =
href=3D"mailto:ietf@jiaziyi.com" style=3D"font-family: Helvetica; =
font-size: 12px; 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"">mailto:ietf@jiaziyi.com</a><span style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">]<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Sent: 09 May 2017 23:49</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">To: Dearlove, Christopher (UK)</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Cc:<span =
class=3D"Apple-converted-space">&nbsp;</span></span><a =
href=3D"mailto:ietf@ietf.org" style=3D"font-family: Helvetica; =
font-size: 12px; 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"">ietf@ietf.org</a><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">; IETF-Announce;<span =
class=3D"Apple-converted-space">&nbsp;</span></span><a =
href=3D"mailto:manet@ietf.org" style=3D"font-family: Helvetica; =
font-size: 12px; 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"">manet@ietf.org</a><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">;<span =
class=3D"Apple-converted-space">&nbsp;</span></span><a =
href=3D"mailto:draft-ietf-manet-olsrv2-multipath@ietf.org" =
style=3D"font-family: Helvetica; font-size: 12px; 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"">draft-ietf-manet-olsrv2-multipath@ietf.org</a><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">;<span =
class=3D"Apple-converted-space">&nbsp;</span></span><a =
href=3D"mailto:manet-chairs@ietf.org" style=3D"font-family: Helvetica; =
font-size: 12px; 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"">manet-chairs@ietf.org</a><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Subject: Re: [manet] Last Call: =
&lt;draft-ietf-manet-olsrv2-multipath-12.txt&gt; (Multi-path Extension =
for the Optimized Link State Routing Protocol version 2 (OLSRv2)) to =
Experimental RFC</span><br style=3D"font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">----------------------! WARNING =
! ---------------------- This message originates from outside our =
organisation, either from an external partner or from the =
internet.</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">Consider carefully whether you should =
click on any links, open any attachments or reply.</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Follow the 'Report Suspicious Emails' link on IT =
matters for instructions on reporting suspicious email =
messages.</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" =
class=3D"">--------------------------------------------------------</span>=
<br style=3D"font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">Hi Chris,<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br=
 style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Thanks a lot for the comments! Please check our =
reply inline:<span class=3D"Apple-converted-space">&nbsp;</span></span><br=
 style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br=
 style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; 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"">On 9 May 2017, at 12:13, =
Dearlove, Christopher (UK) &lt;<a =
href=3D"mailto:chris.dearlove@baesystems.com" =
class=3D"">chris.dearlove@baesystems.com</a>&gt; wrote:<br class=3D""><br =
class=3D"">A few comments on this draft.<br class=3D""><br class=3D"">IPv6=
 specifies complete source routing. But this specification can only =
consider what happens within the MANET. So for a packet from somewhere =
in the MANET to somewhere well outside the MANET, the packet must be =
source routed to the gateway between MANET and rest of Internet, and not =
source routed after that. This I think should be explicitly mentioned. =
Whether that is considered compliant with IPv6 I leave to others.<br =
class=3D""></blockquote><br style=3D"font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">Good point. We added some text at the end =
of section 8.4" Datagram Processing at the MP-OLSRv2 =
Originator"</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><blockquote=
 type=3D"cite" style=3D"font-family: Helvetica; font-size: 12px; =
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""><br class=3D"">7.1 SR_addr =
would better say "originator" address rather than<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D"">"network" =
address. (That makes it an address without a netmask, see<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D"">RFC =
7181.)<br class=3D""></blockquote><br style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">fixed.<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br=
 style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; 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""><br class=3D"">8.1 This is =
suggesting creating TC messages that have on neighbour addresses but =
have only a SOURCE_ROUTE TLV. This is not the design I would have =
suggested as consistent with how I would expect an extension to OLSRv2 =
to do things. We need to consider two kinds of routers: those sending TC =
messages anyway, those that (other than this extension) do not. In the =
former case you could just add the SOURCE_ROUTE TLV to those TC messages =
it sends. Then that information is maintained up to date. Routers that =
don't usually send TC messages could send TC messages with just that =
TLV. But then there's an issue over validity time. A parameter =
SR_HOLD_TIME_MULTIPLIER is introduced. There's no need for that - you =
can simply incorporate that into the validity time recorded in the =
message. That avoids a need to handle the two cases of routers =
differently. There is then an oddity that you get some routers sending =
TC messages with normal validity times and addresses, and some that can =
be sent less frequently with no addresses and longer validity times. But =
that's suspect - note that it's not done in OLSRv2 for attached networks =
(another reason to send TC messages although no neighbours need =
reporting). That's because longer intervals make reacting to new routers =
joining (and network reassembly after fragmentation) slow.<br =
class=3D"">Rather a better design would simply be to add SOURCE_ROUTE =
TLV to normal TC messages. When sending TC messages for just that =
reason, that could be just the usual case, but you could allow as an =
option in this case to send less frequently with validity time increased =
accordingly. When not using that option, once a router needs to send a =
TC message, it could then decide to report neighbours, increasing the =
topology distributed and allowing more routes, this also being an =
option.<br class=3D""><br class=3D""></blockquote><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">IIRC, we had a long discussion on this issue and =
produced the current text.<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">The purpose is to identify the routers that =
don=E2=80=99t send TC messages but support source routing. To avoid =
unnecessary TC flooding, the interval is much longer than the normal TC =
interval.<span class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">The normal TC messages (generated based on =
RFC7181) always have a SOURCE_ROUTE TLV. But if we use the same validity =
time for both RFC7181 normal TC processing and MP-OLSRv2 SR_ROUTE TLV =
processing, the valid time in the SR-OLSRv2 Router Set would be much =
shorter than expected. A possible case is that, the router stops sending =
normal TC messages, the corresponding entry in the SR-OLSRv2 Router set =
will soon expire.<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Therefore, I think it=E2=80=99s reasonable to =
make use of the SR_HOLD_TIME_MULTIPLIER to distinguish the valid time of =
normal TC message information and SR_ROUTE information.<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br=
 style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; 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""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite" class=3D"">I don't agree, and I =
think what you are suggesting introduces a problem and unnecessary =
overhead.<br class=3D""></blockquote></blockquote></blockquote><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; 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""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite" class=3D"">The problem is that =
everywhere in OLSRv2 we are careful to ensure that parameters can be =
independently set, and that routers don't need to coordinate to =
interoperate. (They may do better if they do, but that's a refinement.) =
Here you are using an SR_HOLD_TIME_MULTIPLIER that the receiver has to =
know is what the sender intends. And it's unnecessary. If all that's in =
the TC message is the SOURCE_ROUTE TLV, you can just give that a longer =
validity time, because the only thing that validity time will impact on =
is the source routing status. If the router is also sending normal TC =
messages and you send separate SOURCE_ROUTE TLV TC messages then that =
would still be so. But that's inefficient, because if the router is =
already sending TC messages, why send separate ones with added overhead, =
when you can put the SOURCE_ROUTE TLV in the same TC message? That would =
then (without SR_HOLD_TIME_MULTIPLIER, but that's a good thing because =
SR_HOLD_TIME_MULTIPLIER is not good) give a shorter validity time to the =
SOURCE_ROUTE TLV, but that's fine, because that router will be sending =
more TC messages within that timescale anyway. Furthermore, this also =
allows the router that's sending TC messages more frequently to provide =
its information more responsively in the cases of nodes joining and =
networks reassembling.<br =
class=3D""></blockquote></blockquote></blockquote><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; 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""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite" class=3D"">That gives two =
behaviours: routers sending TC messages anyway, just add a SOURCE_ROUTE =
TLV, and routers not sending TC messages otherwise, just include a =
SOURCE_ROUTE TLV and set the validity time according to what schedule =
that router chooses to use - which can be at the same rate as the other =
routers, or at a slower route, or (a new capability you don't have) =
slowly, except if you learn of the existence of a new router in the =
network you can send one or more responsive SOURCE_ROUTE TLV only TLVs =
to enable that new router (or routers) to learn of the source routing =
quicker.<br class=3D""></blockquote></blockquote></blockquote><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; 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""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite" class=3D"">It's all win: combining =
messages, source set control, ability to do more clever things if you =
want to. (You could probably &nbsp;even still send separate TC messages =
with a SOURCE_ROUTE TLV when also sending normal TC messages if you =
really wanted to, as an option I can't see wanting to use - although it =
might introduce a minor problem that I haven't worked through the OLSRv2 =
specification to check, because it's unnecessary.)<br =
class=3D""></blockquote></blockquote></blockquote><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; 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""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite" class=3D"">The point is that what I =
suggest can gain everything you do, and allow more, plus not breaking =
expected OLSRv2 behaviour.<br =
class=3D""></blockquote></blockquote></blockquote><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; 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"">8.3 second bullet. You =
should here (and possibly elsewhere) exclude routers with routing =
willingness zero.<br class=3D""></blockquote><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><blockquote=
 type=3D"cite" style=3D"font-family: Helvetica; font-size: 12px; =
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""><br class=3D"">8.3 there =
seems to be an inconsistency. When operating proactively and no multiple =
routes, drop the packet, but reactively use standard routing. The latter =
seems more appropriate in the former case also.<br class=3D""><br =
class=3D"">9 CUTOFF_RATIO. Insists of strictly, but as defined earlier, =
may be &gt;=3D 1`.<br class=3D""></blockquote><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">All fixed.<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br=
 style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Thanks again for the valuable =
comments!</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">best</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br=
 style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Jiazi</span><br style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; 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""><br class=3D"">--<br =
class=3D"">Christopher Dearlove<br class=3D"">Senior Principal =
Engineer<br class=3D"">BAE Systems Applied Intelligence =
Laboratories<span class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D"">_______________________________________________________________=
_______<br class=3D"">____<br class=3D""><br class=3D"">T: &nbsp;+44 =
3300 467500 &nbsp;| &nbsp;E: <a =
href=3D"mailto:chris.dearlove@baesystems.com" =
class=3D"">chris.dearlove@baesystems.com</a><br class=3D""><br =
class=3D"">BAE Systems Applied Intelligence, Chelmsford Technology Park, =
Great Baddow, Chelmsford, Essex CM2 8HN.<br class=3D""><a =
href=3D"http://www.baesystems.com/ai" =
class=3D"">www.baesystems.com/ai</a><br class=3D"">BAE Systems Applied =
Intelligence Limited Registered in England &amp; Wales<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D"">No: 01337451 =
Registered Office: Surrey Research Park, Guildford,<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D"">Surrey, GU2 =
7YP<br class=3D""><br class=3D""><br class=3D"">-----Original =
Message-----<br class=3D"">From: manet [mailto:manet-bounces@ietf.org] =
On Behalf Of The IESG<br class=3D"">Sent: 20 April 2017 22:51<br =
class=3D"">To: IETF-Announce<br class=3D"">Cc: manet@ietf.org; =
draft-ietf-manet-olsrv2-multipath@ietf.org;<span =
class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D"">manet-chairs@ietf.org<br class=3D"">Subject: [manet] Last =
Call: &lt;draft-ietf-manet-olsrv2-multipath-12.txt&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D"">(Multi-path =
Extension for the Optimized Link State Routing Protocol<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D"">version 2 =
(OLSRv2)) to Experimental RFC<br class=3D""><br =
class=3D"">----------------------! WARNING ! ---------------------- This =
message originates from outside our organisation, either from an =
external partner or from the internet.<br class=3D"">Consider carefully =
whether you should click on any links, open any attachments or reply.<br =
class=3D"">Follow the 'Report Suspicious Emails' link on IT matters for =
instructions on reporting suspicious email messages.<br =
class=3D"">--------------------------------------------------------<br =
class=3D""><br class=3D"">*** WARNING ***<br class=3D"">EXTERNAL EMAIL =
-- This message originates from outside our organization.<br =
class=3D""><br class=3D""><br class=3D"">The IESG has received a request =
from the Mobile Ad-hoc Networks WG<br class=3D"">(manet) to consider the =
following document:<br class=3D"">- 'Multi-path Extension for the =
Optimized Link State Routing Protocol<br class=3D"">&nbsp;version 2 =
(OLSRv2)'<br class=3D"">&lt;draft-ietf-manet-olsrv2-multipath-12.txt&gt; =
as Experimental RFC<br class=3D""><br class=3D"">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-05-04. 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.<br class=3D""><br =
class=3D"">Abstract<br class=3D""><br class=3D""><br class=3D"">&nbsp;This=
 document specifies a multi-path extension for the Optimized Link<br =
class=3D"">&nbsp;State Routing Protocol version 2 (OLSRv2) to discover =
multiple<br class=3D"">&nbsp;disjoint paths, so as to improve =
reliability of the OLSRv2 protocol.<br class=3D"">&nbsp;The =
interoperability with OLSRv2 is retained.<br class=3D""><br class=3D""><br=
 class=3D""><br class=3D""><br class=3D"">The file can be obtained =
via<br =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-multip=
ath/<br class=3D""><br class=3D"">IESG discussion can be tracked via<br =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-multip=
ath/bal<br class=3D"">lot/<br class=3D""><br class=3D""><br class=3D"">No =
IPR declarations have been submitted directly on this I-D.<br =
class=3D""><br class=3D""><br class=3D""><br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">manet mailing list<br class=3D"">manet@ietf.org<br =
class=3D"">https://www.ietf.org/mailman/listinfo/manet<br class=3D""><br =
class=3D""><br =
class=3D"">***************************************************************=
*****<br class=3D"">This email and any attachments are confidential to =
the intended<span class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D"">recipient and may also be privileged. If you are not the =
intended<span class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D"">recipient please delete it from your system and notify the =
sender.<br class=3D"">You should not copy it or use it for any purpose =
nor disclose or<span class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D"">distribute its contents to any other person.<br =
class=3D"">***************************************************************=
*****</blockquote></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_4BD8F23A-41E1-49F4-B7A6-D52C72BFF50B--


From nobody Wed May 10 05:51:02 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 66B68128CFF for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 05:51:01 -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, RP_MATCHES_RCVD=-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 IN5_SFYDbGe7 for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 05:50:59 -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 94CFA127868 for <ietf@ietf.org>; Wed, 10 May 2017 05:50:59 -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 1d8R50-000NcA-5t; Wed, 10 May 2017 08:50:58 -0400
Date: Wed, 10 May 2017 08:50:52 -0400
From: John C Klensin <john-ietf@jck.com>
To: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
Subject: Re: Registration for remote participation
Message-ID: <7D148F612B0A8241B214B9D7@PSB>
In-Reply-To: <82C753BB-C89C-4039-8A08-0615067777C0@gmail.com>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <82C753BB-C89C-4039-8A08-0615067777C0@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/Jn3xElLN5YIe1VNcYAJKoqqcsQQ>
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, 10 May 2017 12:51:01 -0000

Concur with Bob on both points.  I continue to believe that we
should allow people to anonymously observe/ lurk and to review
archives and stored videos registration but, as soon as someone
starts participating by, e.g., asking questions or making other
Contributions, it is important that they take responsibility for
being involved and possibly influencing decisions and that we
know who they are.

I favor at least a nominal registration fee for the same reason
-- not because I see it as an important revenue source (a rather
different discussion0 but because it helps eliminate Donald Duck
registrations.

    john


--On Wednesday, May 10, 2017 08:20 +0300 Bob Hinden
<bob.hinden@gmail.com> wrote:

> I support this.  I agree it is useful to collect this data,
> and think it's important to know who is participating in the
> IETF standards process.
> 
> I will resit nitpicking as others are doing that just fine :-)





From nobody Wed May 10 05:54:23 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 E056F12943A; Wed, 10 May 2017 05:54:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.125
X-Spam-Level: 
X-Spam-Status: No, score=-6.125 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RDNS_NONE=0.793, 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 uoRsQiPlSrAu; Wed, 10 May 2017 05:54:17 -0700 (PDT)
Received: from ukmta2.baesystems.com (unknown [20.133.0.56]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95B591293E4; Wed, 10 May 2017 05:54:15 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="5.38,319,1491260400"; d="scan'208,217"; a="62020819"
Received: from unknown (HELO baemasmds016.greenlnk.net) ([10.15.207.101]) by ukmta2.baesystems.com with ESMTP; 10 May 2017 13:54:13 +0100
X-IronPort-AV: E=Sophos;i="5.38,319,1491260400";  d="scan'208,217";a="170716979"
Received: from glkxh0003v.greenlnk.net ([10.109.2.34]) by baemasmds016.greenlnk.net with ESMTP; 10 May 2017 13:53:55 +0100
Received: from GLKXM0003V.GREENLNK.net ([169.254.4.172]) by GLKXH0003V.GREENLNK.net ([10.109.2.34]) with mapi id 14.03.0248.002; Wed, 10 May 2017 13:53:55 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Jiazi Yi <ietf@jiaziyi.com>
CC: "ietf@ietf.org" <ietf@ietf.org>, "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-olsrv2-multipath@ietf.org" <draft-ietf-manet-olsrv2-multipath@ietf.org>, "manet-chairs@ietf.org" <manet-chairs@ietf.org>
Subject: RE: [manet] Last Call: <draft-ietf-manet-olsrv2-multipath-12.txt> (Multi-path Extension for the Optimized Link State Routing Protocol version 2 (OLSRv2)) to Experimental RFC
Thread-Topic: [manet] Last Call: <draft-ietf-manet-olsrv2-multipath-12.txt> (Multi-path Extension for the Optimized Link State Routing Protocol version 2 (OLSRv2)) to Experimental RFC
Thread-Index: AQHSuiCA8lo3GCHD2k6nFUb/R8wgmaHr37cAgADIFACAAL4IgIAAKoKAgAAUKTA=
Date: Wed, 10 May 2017 12:53:55 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE633147C@GLKXM0003v.GREENLNK.net>
References: <149272508088.22258.8263343290438640855.idtracker@ietfa.amsl.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6330DE9@GLKXM0003v.GREENLNK.net> <9096512E-3473-473A-B6F1-37CBDD82A0F4@jiaziyi.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE6331192@GLKXM0003v.GREENLNK.net> <03E51133-21B1-45EE-8888-52D251667891@jiaziyi.com>
In-Reply-To: <03E51133-21B1-45EE-8888-52D251667891@jiaziyi.com>
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: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30DE633147CGLKXM0003vGREEN_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/o-_66F61qU1OgYwpIn1JXpGWxVc>
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, 10 May 2017 12:54:21 -0000

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

SSB0aGluayBwb2ludCAzIHNob3VsZCBiZSDigJxtYXnigJ0gcmF0aGVyIHRoYW4g4oCcd2lsbOKA
nSwgYnV0IG90aGVyd2lzZSBnb29kLg0KDQotLQ0KQ2hyaXN0b3BoZXIgRGVhcmxvdmUNClNlbmlv
ciBQcmluY2lwYWwgRW5naW5lZXINCkJBRSBTeXN0ZW1zIEFwcGxpZWQgSW50ZWxsaWdlbmNlIExh
Ym9yYXRvcmllcw0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCg0KVDogICs0NCAzMzAwIDQ2NzUwMCAgfCAg
RTogY2hyaXMuZGVhcmxvdmVAYmFlc3lzdGVtcy5jb208bWFpbHRvOmNocmlzLmRlYXJsb3ZlQGJh
ZXN5c3RlbXMuY29tPg0KDQpCQUUgU3lzdGVtcyBBcHBsaWVkIEludGVsbGlnZW5jZSwgQ2hlbG1z
Zm9yZCBUZWNobm9sb2d5IFBhcmssIEdyZWF0IEJhZGRvdywgQ2hlbG1zZm9yZCwgRXNzZXggQ00y
IDhITi4NCnd3dy5iYWVzeXN0ZW1zLmNvbS9haTxodHRwOi8vd3d3LmJhZXN5c3RlbXMuY29tL2Fp
Pg0KQkFFIFN5c3RlbXMgQXBwbGllZCBJbnRlbGxpZ2VuY2UgTGltaXRlZA0KUmVnaXN0ZXJlZCBp
biBFbmdsYW5kICYgV2FsZXMgTm86IDAxMzM3NDUxDQpSZWdpc3RlcmVkIE9mZmljZTogU3VycmV5
IFJlc2VhcmNoIFBhcmssIEd1aWxkZm9yZCwgU3VycmV5LCBHVTIgN1lQDQoNCkZyb206IEppYXpp
IFlpIFttYWlsdG86aWV0ZkBqaWF6aXlpLmNvbV0NClNlbnQ6IDEwIE1heSAyMDE3IDEzOjQxDQpU
bzogRGVhcmxvdmUsIENocmlzdG9waGVyIChVSykNCkNjOiBpZXRmQGlldGYub3JnOyBtYW5ldEBp
ZXRmLm9yZzsgZHJhZnQtaWV0Zi1tYW5ldC1vbHNydjItbXVsdGlwYXRoQGlldGYub3JnOyBtYW5l
dC1jaGFpcnNAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbbWFuZXRdIExhc3QgQ2FsbDogPGRyYWZ0
LWlldGYtbWFuZXQtb2xzcnYyLW11bHRpcGF0aC0xMi50eHQ+IChNdWx0aS1wYXRoIEV4dGVuc2lv
biBmb3IgdGhlIE9wdGltaXplZCBMaW5rIFN0YXRlIFJvdXRpbmcgUHJvdG9jb2wgdmVyc2lvbiAy
IChPTFNSdjIpKSB0byBFeHBlcmltZW50YWwgUkZDDQoNCg0KKioqIFdBUk5JTkcgKioqDQpUaGlz
IG1lc3NhZ2Ugb3JpZ2luYXRlcyBmcm9tIG91dHNpZGUgb3VyIG9yZ2FuaXNhdGlvbiwgZWl0aGVy
IGZyb20gYW4gZXh0ZXJuYWwgcGFydG5lciBvciB0aGUgaW50ZXJuZXQuDQpDb25zaWRlciBjYXJl
ZnVsbHkgd2hldGhlciB5b3Ugc2hvdWxkIGNsaWNrIG9uIGFueSBsaW5rcywgb3BlbiBhbnkgYXR0
YWNobWVudHMgb3IgcmVwbHkuDQpGb3IgaW5mb3JtYXRpb24gcmVnYXJkaW5nIFJlZCBGbGFncyB0
aGF0IHlvdSBjYW4gbG9vayBvdXQgZm9yIGluIGVtYWlscyB5b3UgcmVjZWl2ZSwgY2xpY2sgaGVy
ZTxodHRwOi8vd3Mtc2l0ZXMuZW50LmJhZXN5c3RlbXMuY29tL3NpdGVzL0hPU0VDU3Rkc0xpYnJh
cnkvU3RhbmRhcmRzTGlicmFyeS9FdmVyeW9uZS9SZWQlMjBGbGFncy5wZGY+Lg0KSWYgeW91IGZl
ZWwgdGhlIGVtYWlsIGlzIHN1c3BpY2lvdXMsIHBsZWFzZSBmb2xsb3cgdGhpcyBwcm9jZXNzPGh0
dHA6Ly93cy1zaXRlcy5lbnQuYmFlc3lzdGVtcy5jb20vc2l0ZXMvSE9TRUNTdGRzTGlicmFyeS9T
dGFuZGFyZHNMaWJyYXJ5L0V2ZXJ5b25lL0RlYWxpbmclMjBXaXRoJTIwU3VzcGljaW91cyUyMEVt
YWlscy5wZGY+Lg0KSGkgQ2hyaXMsDQoNCk9LLCBpdCBtYWtlcyBzZW5zZS4gU28gdGhlIHBvbGlj
eSB3aWxsIGJlOg0KDQogICAgICAgICAgICAtIHRoZSBTT1VSQ0VfUk9VVEUgVExWIHdvbuKAmXQg
aGF2ZSBhbnkgdmFsdWUNCiAgICAgICAgICAgIC0gRXZlcnkgVEMgbWVzc2FnZSBvcmlnaW5hdGVk
IGJ5IHRoZSBzb3VyY2Utcm91dGUgc3VwcG9ydGVkIHJvdXRlcnMgd2lsbCBoYXZlIGEgU09VUkNF
X1JPVVRFIFRMVg0KICAgICAgICAgICAgLSBUaGUgVEMgbWVzc2FnZSBub3QgY29udGFpbmluZyBh
bnkgbmVpZ2hib3VyIGFkZHJlc3Mgd2lsbCBoYXZlIGEgbG9uZ2VyIHZhbGlkaXR5IHRpbWUgY29t
cGFyZWQgdG8gT0xTUnYyIG5vcm1hbCBUQyBtZXNzYWdlcy4NCg0KYmVzdA0KDQpKaWF6aQ0KDQoN
Ck9uIDEwIE1heSAyMDE3LCBhdCAxMTozMywgRGVhcmxvdmUsIENocmlzdG9waGVyIChVSykgPGNo
cmlzLmRlYXJsb3ZlQGJhZXN5c3RlbXMuY29tPG1haWx0bzpjaHJpcy5kZWFybG92ZUBiYWVzeXN0
ZW1zLmNvbT4+IHdyb3RlOg0KDQpBZGRpdGlvbmFsIGNvbW1lbnRzID4+PiBiZWxvdy4gV2hhdCBJ
J20gcHJvcG9zaW5nIChzcGVsbGVkIG91dCBhIGJpdCBtb3JlKSBpcyBhbGwgd2luLCBhbmQgcmVt
b3ZlcyBwcm9ibGVtcyB3aXRoIHRoZSBjdXJyZW50IGRlc2lnbi4gSSB0aGluayB0aGlzIGlzIGEg
bXVzdCBkby4NCg0KLS0NCkNocmlzdG9waGVyIERlYXJsb3ZlDQpTZW5pb3IgUHJpbmNpcGFsIEVu
Z2luZWVyDQpCQUUgU3lzdGVtcyBBcHBsaWVkIEludGVsbGlnZW5jZSBMYWJvcmF0b3JpZXMNCl9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fDQoNClQ6ICArNDQgMzMwMCA0Njc1MDAgIHwgIEU6IGNocmlzLmRlYXJs
b3ZlQGJhZXN5c3RlbXMuY29tPG1haWx0bzpjaHJpcy5kZWFybG92ZUBiYWVzeXN0ZW1zLmNvbT4N
Cg0KQkFFIFN5c3RlbXMgQXBwbGllZCBJbnRlbGxpZ2VuY2UsIENoZWxtc2ZvcmQgVGVjaG5vbG9n
eSBQYXJrLCBHcmVhdCBCYWRkb3csIENoZWxtc2ZvcmQsIEVzc2V4IENNMiA4SE4uDQp3d3cuYmFl
c3lzdGVtcy5jb20vYWk8aHR0cDovL3d3dy5iYWVzeXN0ZW1zLmNvbS9haT4NCkJBRSBTeXN0ZW1z
IEFwcGxpZWQgSW50ZWxsaWdlbmNlIExpbWl0ZWQNClJlZ2lzdGVyZWQgaW4gRW5nbGFuZCAmIFdh
bGVzIE5vOiAwMTMzNzQ1MQ0KUmVnaXN0ZXJlZCBPZmZpY2U6IFN1cnJleSBSZXNlYXJjaCBQYXJr
LCBHdWlsZGZvcmQsIFN1cnJleSwgR1UyIDdZUA0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0t
LS0tDQpGcm9tOiBKaWF6aSBZaSBbbWFpbHRvOmlldGZAamlheml5aS5jb21dDQpTZW50OiAwOSBN
YXkgMjAxNyAyMzo0OQ0KVG86IERlYXJsb3ZlLCBDaHJpc3RvcGhlciAoVUspDQpDYzogaWV0ZkBp
ZXRmLm9yZzxtYWlsdG86aWV0ZkBpZXRmLm9yZz47IElFVEYtQW5ub3VuY2U7IG1hbmV0QGlldGYu
b3JnPG1haWx0bzptYW5ldEBpZXRmLm9yZz47IGRyYWZ0LWlldGYtbWFuZXQtb2xzcnYyLW11bHRp
cGF0aEBpZXRmLm9yZzxtYWlsdG86ZHJhZnQtaWV0Zi1tYW5ldC1vbHNydjItbXVsdGlwYXRoQGll
dGYub3JnPjsgbWFuZXQtY2hhaXJzQGlldGYub3JnPG1haWx0bzptYW5ldC1jaGFpcnNAaWV0Zi5v
cmc+DQpTdWJqZWN0OiBSZTogW21hbmV0XSBMYXN0IENhbGw6IDxkcmFmdC1pZXRmLW1hbmV0LW9s
c3J2Mi1tdWx0aXBhdGgtMTIudHh0PiAoTXVsdGktcGF0aCBFeHRlbnNpb24gZm9yIHRoZSBPcHRp
bWl6ZWQgTGluayBTdGF0ZSBSb3V0aW5nIFByb3RvY29sIHZlcnNpb24gMiAoT0xTUnYyKSkgdG8g
RXhwZXJpbWVudGFsIFJGQw0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tISBXQVJOSU5HICEgLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLSBUaGlzIG1lc3NhZ2Ugb3JpZ2luYXRlcyBmcm9tIG91dHNpZGUg
b3VyIG9yZ2FuaXNhdGlvbiwgZWl0aGVyIGZyb20gYW4gZXh0ZXJuYWwgcGFydG5lciBvciBmcm9t
IHRoZSBpbnRlcm5ldC4NCkNvbnNpZGVyIGNhcmVmdWxseSB3aGV0aGVyIHlvdSBzaG91bGQgY2xp
Y2sgb24gYW55IGxpbmtzLCBvcGVuIGFueSBhdHRhY2htZW50cyBvciByZXBseS4NCkZvbGxvdyB0
aGUgJ1JlcG9ydCBTdXNwaWNpb3VzIEVtYWlscycgbGluayBvbiBJVCBtYXR0ZXJzIGZvciBpbnN0
cnVjdGlvbnMgb24gcmVwb3J0aW5nIHN1c3BpY2lvdXMgZW1haWwgbWVzc2FnZXMuDQotLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQpIaSBD
aHJpcywNCg0KVGhhbmtzIGEgbG90IGZvciB0aGUgY29tbWVudHMhIFBsZWFzZSBjaGVjayBvdXIg
cmVwbHkgaW5saW5lOg0KDQoNCk9uIDkgTWF5IDIwMTcsIGF0IDEyOjEzLCBEZWFybG92ZSwgQ2hy
aXN0b3BoZXIgKFVLKSA8Y2hyaXMuZGVhcmxvdmVAYmFlc3lzdGVtcy5jb208bWFpbHRvOmNocmlz
LmRlYXJsb3ZlQGJhZXN5c3RlbXMuY29tPj4gd3JvdGU6DQoNCkEgZmV3IGNvbW1lbnRzIG9uIHRo
aXMgZHJhZnQuDQoNCklQdjYgc3BlY2lmaWVzIGNvbXBsZXRlIHNvdXJjZSByb3V0aW5nLiBCdXQg
dGhpcyBzcGVjaWZpY2F0aW9uIGNhbiBvbmx5IGNvbnNpZGVyIHdoYXQgaGFwcGVucyB3aXRoaW4g
dGhlIE1BTkVULiBTbyBmb3IgYSBwYWNrZXQgZnJvbSBzb21ld2hlcmUgaW4gdGhlIE1BTkVUIHRv
IHNvbWV3aGVyZSB3ZWxsIG91dHNpZGUgdGhlIE1BTkVULCB0aGUgcGFja2V0IG11c3QgYmUgc291
cmNlIHJvdXRlZCB0byB0aGUgZ2F0ZXdheSBiZXR3ZWVuIE1BTkVUIGFuZCByZXN0IG9mIEludGVy
bmV0LCBhbmQgbm90IHNvdXJjZSByb3V0ZWQgYWZ0ZXIgdGhhdC4gVGhpcyBJIHRoaW5rIHNob3Vs
ZCBiZSBleHBsaWNpdGx5IG1lbnRpb25lZC4gV2hldGhlciB0aGF0IGlzIGNvbnNpZGVyZWQgY29t
cGxpYW50IHdpdGggSVB2NiBJIGxlYXZlIHRvIG90aGVycy4NCg0KR29vZCBwb2ludC4gV2UgYWRk
ZWQgc29tZSB0ZXh0IGF0IHRoZSBlbmQgb2Ygc2VjdGlvbiA4LjQiIERhdGFncmFtIFByb2Nlc3Np
bmcgYXQgdGhlIE1QLU9MU1J2MiBPcmlnaW5hdG9yIg0KDQoNCg0KNy4xIFNSX2FkZHIgd291bGQg
YmV0dGVyIHNheSAib3JpZ2luYXRvciIgYWRkcmVzcyByYXRoZXIgdGhhbg0KIm5ldHdvcmsiIGFk
ZHJlc3MuIChUaGF0IG1ha2VzIGl0IGFuIGFkZHJlc3Mgd2l0aG91dCBhIG5ldG1hc2ssIHNlZQ0K
UkZDIDcxODEuKQ0KDQpmaXhlZC4NCg0KDQoNCjguMSBUaGlzIGlzIHN1Z2dlc3RpbmcgY3JlYXRp
bmcgVEMgbWVzc2FnZXMgdGhhdCBoYXZlIG9uIG5laWdoYm91ciBhZGRyZXNzZXMgYnV0IGhhdmUg
b25seSBhIFNPVVJDRV9ST1VURSBUTFYuIFRoaXMgaXMgbm90IHRoZSBkZXNpZ24gSSB3b3VsZCBo
YXZlIHN1Z2dlc3RlZCBhcyBjb25zaXN0ZW50IHdpdGggaG93IEkgd291bGQgZXhwZWN0IGFuIGV4
dGVuc2lvbiB0byBPTFNSdjIgdG8gZG8gdGhpbmdzLiBXZSBuZWVkIHRvIGNvbnNpZGVyIHR3byBr
aW5kcyBvZiByb3V0ZXJzOiB0aG9zZSBzZW5kaW5nIFRDIG1lc3NhZ2VzIGFueXdheSwgdGhvc2Ug
dGhhdCAob3RoZXIgdGhhbiB0aGlzIGV4dGVuc2lvbikgZG8gbm90LiBJbiB0aGUgZm9ybWVyIGNh
c2UgeW91IGNvdWxkIGp1c3QgYWRkIHRoZSBTT1VSQ0VfUk9VVEUgVExWIHRvIHRob3NlIFRDIG1l
c3NhZ2VzIGl0IHNlbmRzLiBUaGVuIHRoYXQgaW5mb3JtYXRpb24gaXMgbWFpbnRhaW5lZCB1cCB0
byBkYXRlLiBSb3V0ZXJzIHRoYXQgZG9uJ3QgdXN1YWxseSBzZW5kIFRDIG1lc3NhZ2VzIGNvdWxk
IHNlbmQgVEMgbWVzc2FnZXMgd2l0aCBqdXN0IHRoYXQgVExWLiBCdXQgdGhlbiB0aGVyZSdzIGFu
IGlzc3VlIG92ZXIgdmFsaWRpdHkgdGltZS4gQSBwYXJhbWV0ZXIgU1JfSE9MRF9USU1FX01VTFRJ
UExJRVIgaXMgaW50cm9kdWNlZC4gVGhlcmUncyBubyBuZWVkIGZvciB0aGF0IC0geW91IGNhbiBz
aW1wbHkgaW5jb3Jwb3JhdGUgdGhhdCBpbnRvIHRoZSB2YWxpZGl0eSB0aW1lIHJlY29yZGVkIGlu
IHRoZSBtZXNzYWdlLiBUaGF0IGF2b2lkcyBhIG5lZWQgdG8gaGFuZGxlIHRoZSB0d28gY2FzZXMg
b2Ygcm91dGVycyBkaWZmZXJlbnRseS4gVGhlcmUgaXMgdGhlbiBhbiBvZGRpdHkgdGhhdCB5b3Ug
Z2V0IHNvbWUgcm91dGVycyBzZW5kaW5nIFRDIG1lc3NhZ2VzIHdpdGggbm9ybWFsIHZhbGlkaXR5
IHRpbWVzIGFuZCBhZGRyZXNzZXMsIGFuZCBzb21lIHRoYXQgY2FuIGJlIHNlbnQgbGVzcyBmcmVx
dWVudGx5IHdpdGggbm8gYWRkcmVzc2VzIGFuZCBsb25nZXIgdmFsaWRpdHkgdGltZXMuIEJ1dCB0
aGF0J3Mgc3VzcGVjdCAtIG5vdGUgdGhhdCBpdCdzIG5vdCBkb25lIGluIE9MU1J2MiBmb3IgYXR0
YWNoZWQgbmV0d29ya3MgKGFub3RoZXIgcmVhc29uIHRvIHNlbmQgVEMgbWVzc2FnZXMgYWx0aG91
Z2ggbm8gbmVpZ2hib3VycyBuZWVkIHJlcG9ydGluZykuIFRoYXQncyBiZWNhdXNlIGxvbmdlciBp
bnRlcnZhbHMgbWFrZSByZWFjdGluZyB0byBuZXcgcm91dGVycyBqb2luaW5nIChhbmQgbmV0d29y
ayByZWFzc2VtYmx5IGFmdGVyIGZyYWdtZW50YXRpb24pIHNsb3cuDQpSYXRoZXIgYSBiZXR0ZXIg
ZGVzaWduIHdvdWxkIHNpbXBseSBiZSB0byBhZGQgU09VUkNFX1JPVVRFIFRMViB0byBub3JtYWwg
VEMgbWVzc2FnZXMuIFdoZW4gc2VuZGluZyBUQyBtZXNzYWdlcyBmb3IganVzdCB0aGF0IHJlYXNv
biwgdGhhdCBjb3VsZCBiZSBqdXN0IHRoZSB1c3VhbCBjYXNlLCBidXQgeW91IGNvdWxkIGFsbG93
IGFzIGFuIG9wdGlvbiBpbiB0aGlzIGNhc2UgdG8gc2VuZCBsZXNzIGZyZXF1ZW50bHkgd2l0aCB2
YWxpZGl0eSB0aW1lIGluY3JlYXNlZCBhY2NvcmRpbmdseS4gV2hlbiBub3QgdXNpbmcgdGhhdCBv
cHRpb24sIG9uY2UgYSByb3V0ZXIgbmVlZHMgdG8gc2VuZCBhIFRDIG1lc3NhZ2UsIGl0IGNvdWxk
IHRoZW4gZGVjaWRlIHRvIHJlcG9ydCBuZWlnaGJvdXJzLCBpbmNyZWFzaW5nIHRoZSB0b3BvbG9n
eSBkaXN0cmlidXRlZCBhbmQgYWxsb3dpbmcgbW9yZSByb3V0ZXMsIHRoaXMgYWxzbyBiZWluZyBh
biBvcHRpb24uDQoNCklJUkMsIHdlIGhhZCBhIGxvbmcgZGlzY3Vzc2lvbiBvbiB0aGlzIGlzc3Vl
IGFuZCBwcm9kdWNlZCB0aGUgY3VycmVudCB0ZXh0Lg0KVGhlIHB1cnBvc2UgaXMgdG8gaWRlbnRp
ZnkgdGhlIHJvdXRlcnMgdGhhdCBkb27igJl0IHNlbmQgVEMgbWVzc2FnZXMgYnV0IHN1cHBvcnQg
c291cmNlIHJvdXRpbmcuIFRvIGF2b2lkIHVubmVjZXNzYXJ5IFRDIGZsb29kaW5nLCB0aGUgaW50
ZXJ2YWwgaXMgbXVjaCBsb25nZXIgdGhhbiB0aGUgbm9ybWFsIFRDIGludGVydmFsLg0KVGhlIG5v
cm1hbCBUQyBtZXNzYWdlcyAoZ2VuZXJhdGVkIGJhc2VkIG9uIFJGQzcxODEpIGFsd2F5cyBoYXZl
IGEgU09VUkNFX1JPVVRFIFRMVi4gQnV0IGlmIHdlIHVzZSB0aGUgc2FtZSB2YWxpZGl0eSB0aW1l
IGZvciBib3RoIFJGQzcxODEgbm9ybWFsIFRDIHByb2Nlc3NpbmcgYW5kIE1QLU9MU1J2MiBTUl9S
T1VURSBUTFYgcHJvY2Vzc2luZywgdGhlIHZhbGlkIHRpbWUgaW4gdGhlIFNSLU9MU1J2MiBSb3V0
ZXIgU2V0IHdvdWxkIGJlIG11Y2ggc2hvcnRlciB0aGFuIGV4cGVjdGVkLiBBIHBvc3NpYmxlIGNh
c2UgaXMgdGhhdCwgdGhlIHJvdXRlciBzdG9wcyBzZW5kaW5nIG5vcm1hbCBUQyBtZXNzYWdlcywg
dGhlIGNvcnJlc3BvbmRpbmcgZW50cnkgaW4gdGhlIFNSLU9MU1J2MiBSb3V0ZXIgc2V0IHdpbGwg
c29vbiBleHBpcmUuDQpUaGVyZWZvcmUsIEkgdGhpbmsgaXTigJlzIHJlYXNvbmFibGUgdG8gbWFr
ZSB1c2Ugb2YgdGhlIFNSX0hPTERfVElNRV9NVUxUSVBMSUVSIHRvIGRpc3Rpbmd1aXNoIHRoZSB2
YWxpZCB0aW1lIG9mIG5vcm1hbCBUQyBtZXNzYWdlIGluZm9ybWF0aW9uIGFuZCBTUl9ST1VURSBp
bmZvcm1hdGlvbi4NCg0KDQpJIGRvbid0IGFncmVlLCBhbmQgSSB0aGluayB3aGF0IHlvdSBhcmUg
c3VnZ2VzdGluZyBpbnRyb2R1Y2VzIGEgcHJvYmxlbSBhbmQgdW5uZWNlc3Nhcnkgb3ZlcmhlYWQu
DQoNCg0KVGhlIHByb2JsZW0gaXMgdGhhdCBldmVyeXdoZXJlIGluIE9MU1J2MiB3ZSBhcmUgY2Fy
ZWZ1bCB0byBlbnN1cmUgdGhhdCBwYXJhbWV0ZXJzIGNhbiBiZSBpbmRlcGVuZGVudGx5IHNldCwg
YW5kIHRoYXQgcm91dGVycyBkb24ndCBuZWVkIHRvIGNvb3JkaW5hdGUgdG8gaW50ZXJvcGVyYXRl
LiAoVGhleSBtYXkgZG8gYmV0dGVyIGlmIHRoZXkgZG8sIGJ1dCB0aGF0J3MgYSByZWZpbmVtZW50
LikgSGVyZSB5b3UgYXJlIHVzaW5nIGFuIFNSX0hPTERfVElNRV9NVUxUSVBMSUVSIHRoYXQgdGhl
IHJlY2VpdmVyIGhhcyB0byBrbm93IGlzIHdoYXQgdGhlIHNlbmRlciBpbnRlbmRzLiBBbmQgaXQn
cyB1bm5lY2Vzc2FyeS4gSWYgYWxsIHRoYXQncyBpbiB0aGUgVEMgbWVzc2FnZSBpcyB0aGUgU09V
UkNFX1JPVVRFIFRMViwgeW91IGNhbiBqdXN0IGdpdmUgdGhhdCBhIGxvbmdlciB2YWxpZGl0eSB0
aW1lLCBiZWNhdXNlIHRoZSBvbmx5IHRoaW5nIHRoYXQgdmFsaWRpdHkgdGltZSB3aWxsIGltcGFj
dCBvbiBpcyB0aGUgc291cmNlIHJvdXRpbmcgc3RhdHVzLiBJZiB0aGUgcm91dGVyIGlzIGFsc28g
c2VuZGluZyBub3JtYWwgVEMgbWVzc2FnZXMgYW5kIHlvdSBzZW5kIHNlcGFyYXRlIFNPVVJDRV9S
T1VURSBUTFYgVEMgbWVzc2FnZXMgdGhlbiB0aGF0IHdvdWxkIHN0aWxsIGJlIHNvLiBCdXQgdGhh
dCdzIGluZWZmaWNpZW50LCBiZWNhdXNlIGlmIHRoZSByb3V0ZXIgaXMgYWxyZWFkeSBzZW5kaW5n
IFRDIG1lc3NhZ2VzLCB3aHkgc2VuZCBzZXBhcmF0ZSBvbmVzIHdpdGggYWRkZWQgb3ZlcmhlYWQs
IHdoZW4geW91IGNhbiBwdXQgdGhlIFNPVVJDRV9ST1VURSBUTFYgaW4gdGhlIHNhbWUgVEMgbWVz
c2FnZT8gVGhhdCB3b3VsZCB0aGVuICh3aXRob3V0IFNSX0hPTERfVElNRV9NVUxUSVBMSUVSLCBi
dXQgdGhhdCdzIGEgZ29vZCB0aGluZyBiZWNhdXNlIFNSX0hPTERfVElNRV9NVUxUSVBMSUVSIGlz
IG5vdCBnb29kKSBnaXZlIGEgc2hvcnRlciB2YWxpZGl0eSB0aW1lIHRvIHRoZSBTT1VSQ0VfUk9V
VEUgVExWLCBidXQgdGhhdCdzIGZpbmUsIGJlY2F1c2UgdGhhdCByb3V0ZXIgd2lsbCBiZSBzZW5k
aW5nIG1vcmUgVEMgbWVzc2FnZXMgd2l0aGluIHRoYXQgdGltZXNjYWxlIGFueXdheS4gRnVydGhl
cm1vcmUsIHRoaXMgYWxzbyBhbGxvd3MgdGhlIHJvdXRlciB0aGF0J3Mgc2VuZGluZyBUQyBtZXNz
YWdlcyBtb3JlIGZyZXF1ZW50bHkgdG8gcHJvdmlkZSBpdHMgaW5mb3JtYXRpb24gbW9yZSByZXNw
b25zaXZlbHkgaW4gdGhlIGNhc2VzIG9mIG5vZGVzIGpvaW5pbmcgYW5kIG5ldHdvcmtzIHJlYXNz
ZW1ibGluZy4NCg0KDQpUaGF0IGdpdmVzIHR3byBiZWhhdmlvdXJzOiByb3V0ZXJzIHNlbmRpbmcg
VEMgbWVzc2FnZXMgYW55d2F5LCBqdXN0IGFkZCBhIFNPVVJDRV9ST1VURSBUTFYsIGFuZCByb3V0
ZXJzIG5vdCBzZW5kaW5nIFRDIG1lc3NhZ2VzIG90aGVyd2lzZSwganVzdCBpbmNsdWRlIGEgU09V
UkNFX1JPVVRFIFRMViBhbmQgc2V0IHRoZSB2YWxpZGl0eSB0aW1lIGFjY29yZGluZyB0byB3aGF0
IHNjaGVkdWxlIHRoYXQgcm91dGVyIGNob29zZXMgdG8gdXNlIC0gd2hpY2ggY2FuIGJlIGF0IHRo
ZSBzYW1lIHJhdGUgYXMgdGhlIG90aGVyIHJvdXRlcnMsIG9yIGF0IGEgc2xvd2VyIHJvdXRlLCBv
ciAoYSBuZXcgY2FwYWJpbGl0eSB5b3UgZG9uJ3QgaGF2ZSkgc2xvd2x5LCBleGNlcHQgaWYgeW91
IGxlYXJuIG9mIHRoZSBleGlzdGVuY2Ugb2YgYSBuZXcgcm91dGVyIGluIHRoZSBuZXR3b3JrIHlv
dSBjYW4gc2VuZCBvbmUgb3IgbW9yZSByZXNwb25zaXZlIFNPVVJDRV9ST1VURSBUTFYgb25seSBU
TFZzIHRvIGVuYWJsZSB0aGF0IG5ldyByb3V0ZXIgKG9yIHJvdXRlcnMpIHRvIGxlYXJuIG9mIHRo
ZSBzb3VyY2Ugcm91dGluZyBxdWlja2VyLg0KDQoNCkl0J3MgYWxsIHdpbjogY29tYmluaW5nIG1l
c3NhZ2VzLCBzb3VyY2Ugc2V0IGNvbnRyb2wsIGFiaWxpdHkgdG8gZG8gbW9yZSBjbGV2ZXIgdGhp
bmdzIGlmIHlvdSB3YW50IHRvLiAoWW91IGNvdWxkIHByb2JhYmx5ICBldmVuIHN0aWxsIHNlbmQg
c2VwYXJhdGUgVEMgbWVzc2FnZXMgd2l0aCBhIFNPVVJDRV9ST1VURSBUTFYgd2hlbiBhbHNvIHNl
bmRpbmcgbm9ybWFsIFRDIG1lc3NhZ2VzIGlmIHlvdSByZWFsbHkgd2FudGVkIHRvLCBhcyBhbiBv
cHRpb24gSSBjYW4ndCBzZWUgd2FudGluZyB0byB1c2UgLSBhbHRob3VnaCBpdCBtaWdodCBpbnRy
b2R1Y2UgYSBtaW5vciBwcm9ibGVtIHRoYXQgSSBoYXZlbid0IHdvcmtlZCB0aHJvdWdoIHRoZSBP
TFNSdjIgc3BlY2lmaWNhdGlvbiB0byBjaGVjaywgYmVjYXVzZSBpdCdzIHVubmVjZXNzYXJ5LikN
Cg0KDQpUaGUgcG9pbnQgaXMgdGhhdCB3aGF0IEkgc3VnZ2VzdCBjYW4gZ2FpbiBldmVyeXRoaW5n
IHlvdSBkbywgYW5kIGFsbG93IG1vcmUsIHBsdXMgbm90IGJyZWFraW5nIGV4cGVjdGVkIE9MU1J2
MiBiZWhhdmlvdXIuDQoNCg0KOC4zIHNlY29uZCBidWxsZXQuIFlvdSBzaG91bGQgaGVyZSAoYW5k
IHBvc3NpYmx5IGVsc2V3aGVyZSkgZXhjbHVkZSByb3V0ZXJzIHdpdGggcm91dGluZyB3aWxsaW5n
bmVzcyB6ZXJvLg0KDQoNCg0KOC4zIHRoZXJlIHNlZW1zIHRvIGJlIGFuIGluY29uc2lzdGVuY3ku
IFdoZW4gb3BlcmF0aW5nIHByb2FjdGl2ZWx5IGFuZCBubyBtdWx0aXBsZSByb3V0ZXMsIGRyb3Ag
dGhlIHBhY2tldCwgYnV0IHJlYWN0aXZlbHkgdXNlIHN0YW5kYXJkIHJvdXRpbmcuIFRoZSBsYXR0
ZXIgc2VlbXMgbW9yZSBhcHByb3ByaWF0ZSBpbiB0aGUgZm9ybWVyIGNhc2UgYWxzby4NCg0KOSBD
VVRPRkZfUkFUSU8uIEluc2lzdHMgb2Ygc3RyaWN0bHksIGJ1dCBhcyBkZWZpbmVkIGVhcmxpZXIs
IG1heSBiZSA+PSAxYC4NCg0KQWxsIGZpeGVkLg0KDQpUaGFua3MgYWdhaW4gZm9yIHRoZSB2YWx1
YWJsZSBjb21tZW50cyENCg0KYmVzdA0KDQpKaWF6aQ0KDQoNCg0KLS0NCkNocmlzdG9waGVyIERl
YXJsb3ZlDQpTZW5pb3IgUHJpbmNpcGFsIEVuZ2luZWVyDQpCQUUgU3lzdGVtcyBBcHBsaWVkIElu
dGVsbGlnZW5jZSBMYWJvcmF0b3JpZXMNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCl9fX18NCg0KVDogICs0NCAz
MzAwIDQ2NzUwMCAgfCAgRTogY2hyaXMuZGVhcmxvdmVAYmFlc3lzdGVtcy5jb208bWFpbHRvOmNo
cmlzLmRlYXJsb3ZlQGJhZXN5c3RlbXMuY29tPg0KDQpCQUUgU3lzdGVtcyBBcHBsaWVkIEludGVs
bGlnZW5jZSwgQ2hlbG1zZm9yZCBUZWNobm9sb2d5IFBhcmssIEdyZWF0IEJhZGRvdywgQ2hlbG1z
Zm9yZCwgRXNzZXggQ00yIDhITi4NCnd3dy5iYWVzeXN0ZW1zLmNvbS9haTxodHRwOi8vd3d3LmJh
ZXN5c3RlbXMuY29tL2FpPg0KQkFFIFN5c3RlbXMgQXBwbGllZCBJbnRlbGxpZ2VuY2UgTGltaXRl
ZCBSZWdpc3RlcmVkIGluIEVuZ2xhbmQgJiBXYWxlcw0KTm86IDAxMzM3NDUxIFJlZ2lzdGVyZWQg
T2ZmaWNlOiBTdXJyZXkgUmVzZWFyY2ggUGFyaywgR3VpbGRmb3JkLA0KU3VycmV5LCBHVTIgN1lQ
DQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IG1hbmV0IFttYWlsdG86bWFu
ZXQtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFRoZSBJRVNHDQpTZW50OiAyMCBBcHJp
bCAyMDE3IDIyOjUxDQpUbzogSUVURi1Bbm5vdW5jZQ0KQ2M6IG1hbmV0QGlldGYub3JnPG1haWx0
bzptYW5ldEBpZXRmLm9yZz47IGRyYWZ0LWlldGYtbWFuZXQtb2xzcnYyLW11bHRpcGF0aEBpZXRm
Lm9yZzxtYWlsdG86ZHJhZnQtaWV0Zi1tYW5ldC1vbHNydjItbXVsdGlwYXRoQGlldGYub3JnPjsN
Cm1hbmV0LWNoYWlyc0BpZXRmLm9yZzxtYWlsdG86bWFuZXQtY2hhaXJzQGlldGYub3JnPg0KU3Vi
amVjdDogW21hbmV0XSBMYXN0IENhbGw6IDxkcmFmdC1pZXRmLW1hbmV0LW9sc3J2Mi1tdWx0aXBh
dGgtMTIudHh0Pg0KKE11bHRpLXBhdGggRXh0ZW5zaW9uIGZvciB0aGUgT3B0aW1pemVkIExpbmsg
U3RhdGUgUm91dGluZyBQcm90b2NvbA0KdmVyc2lvbiAyIChPTFNSdjIpKSB0byBFeHBlcmltZW50
YWwgUkZDDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0hIFdBUk5JTkcgISAtLS0tLS0tLS0tLS0t
LS0tLS0tLS0tIFRoaXMgbWVzc2FnZSBvcmlnaW5hdGVzIGZyb20gb3V0c2lkZSBvdXIgb3JnYW5p
c2F0aW9uLCBlaXRoZXIgZnJvbSBhbiBleHRlcm5hbCBwYXJ0bmVyIG9yIGZyb20gdGhlIGludGVy
bmV0Lg0KQ29uc2lkZXIgY2FyZWZ1bGx5IHdoZXRoZXIgeW91IHNob3VsZCBjbGljayBvbiBhbnkg
bGlua3MsIG9wZW4gYW55IGF0dGFjaG1lbnRzIG9yIHJlcGx5Lg0KRm9sbG93IHRoZSAnUmVwb3J0
IFN1c3BpY2lvdXMgRW1haWxzJyBsaW5rIG9uIElUIG1hdHRlcnMgZm9yIGluc3RydWN0aW9ucyBv
biByZXBvcnRpbmcgc3VzcGljaW91cyBlbWFpbCBtZXNzYWdlcy4NCi0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCioqKiBXQVJOSU5HICoq
Kg0KRVhURVJOQUwgRU1BSUwgLS0gVGhpcyBtZXNzYWdlIG9yaWdpbmF0ZXMgZnJvbSBvdXRzaWRl
IG91ciBvcmdhbml6YXRpb24uDQoNCg0KVGhlIElFU0cgaGFzIHJlY2VpdmVkIGEgcmVxdWVzdCBm
cm9tIHRoZSBNb2JpbGUgQWQtaG9jIE5ldHdvcmtzIFdHDQoobWFuZXQpIHRvIGNvbnNpZGVyIHRo
ZSBmb2xsb3dpbmcgZG9jdW1lbnQ6DQotICdNdWx0aS1wYXRoIEV4dGVuc2lvbiBmb3IgdGhlIE9w
dGltaXplZCBMaW5rIFN0YXRlIFJvdXRpbmcgUHJvdG9jb2wNCiB2ZXJzaW9uIDIgKE9MU1J2Mikn
DQo8ZHJhZnQtaWV0Zi1tYW5ldC1vbHNydjItbXVsdGlwYXRoLTEyLnR4dD4gYXMgRXhwZXJpbWVu
dGFsIFJGQw0KDQpUaGUgSUVTRyBwbGFucyB0byBtYWtlIGEgZGVjaXNpb24gaW4gdGhlIG5leHQg
ZmV3IHdlZWtzLCBhbmQgc29saWNpdHMgZmluYWwgY29tbWVudHMgb24gdGhpcyBhY3Rpb24uIFBs
ZWFzZSBzZW5kIHN1YnN0YW50aXZlIGNvbW1lbnRzIHRvIHRoZSBpZXRmQGlldGYub3JnPG1haWx0
bzppZXRmQGlldGYub3JnPiBtYWlsaW5nIGxpc3RzIGJ5IDIwMTctMDUtMDQuIEV4Y2VwdGlvbmFs
bHksIGNvbW1lbnRzIG1heSBiZSBzZW50IHRvIGllc2dAaWV0Zi5vcmc8bWFpbHRvOmllc2dAaWV0
Zi5vcmc+IGluc3RlYWQuIEluIGVpdGhlciBjYXNlLCBwbGVhc2UgcmV0YWluIHRoZSBiZWdpbm5p
bmcgb2YgdGhlIFN1YmplY3QgbGluZSB0byBhbGxvdyBhdXRvbWF0ZWQgc29ydGluZy4NCg0KQWJz
dHJhY3QNCg0KDQogVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgYSBtdWx0aS1wYXRoIGV4dGVuc2lv
biBmb3IgdGhlIE9wdGltaXplZCBMaW5rDQogU3RhdGUgUm91dGluZyBQcm90b2NvbCB2ZXJzaW9u
IDIgKE9MU1J2MikgdG8gZGlzY292ZXIgbXVsdGlwbGUNCiBkaXNqb2ludCBwYXRocywgc28gYXMg
dG8gaW1wcm92ZSByZWxpYWJpbGl0eSBvZiB0aGUgT0xTUnYyIHByb3RvY29sLg0KIFRoZSBpbnRl
cm9wZXJhYmlsaXR5IHdpdGggT0xTUnYyIGlzIHJldGFpbmVkLg0KDQoNCg0KDQpUaGUgZmlsZSBj
YW4gYmUgb2J0YWluZWQgdmlhDQpodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFm
dC1pZXRmLW1hbmV0LW9sc3J2Mi1tdWx0aXBhdGgvDQoNCklFU0cgZGlzY3Vzc2lvbiBjYW4gYmUg
dHJhY2tlZCB2aWENCmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYt
bWFuZXQtb2xzcnYyLW11bHRpcGF0aC9iYWwNCmxvdC8NCg0KDQpObyBJUFIgZGVjbGFyYXRpb25z
IGhhdmUgYmVlbiBzdWJtaXR0ZWQgZGlyZWN0bHkgb24gdGhpcyBJLUQuDQoNCg0KDQoNCl9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQptYW5ldCBtYWlsaW5n
IGxpc3QNCm1hbmV0QGlldGYub3JnPG1haWx0bzptYW5ldEBpZXRmLm9yZz4NCmh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWFuZXQNCg0KDQoqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKg0KVGhpcyBl
bWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGFyZSBjb25maWRlbnRpYWwgdG8gdGhlIGludGVuZGVk
DQpyZWNpcGllbnQgYW5kIG1heSBhbHNvIGJlIHByaXZpbGVnZWQuIElmIHlvdSBhcmUgbm90IHRo
ZSBpbnRlbmRlZA0KcmVjaXBpZW50IHBsZWFzZSBkZWxldGUgaXQgZnJvbSB5b3VyIHN5c3RlbSBh
bmQgbm90aWZ5IHRoZSBzZW5kZXIuDQpZb3Ugc2hvdWxkIG5vdCBjb3B5IGl0IG9yIHVzZSBpdCBm
b3IgYW55IHB1cnBvc2Ugbm9yIGRpc2Nsb3NlIG9yDQpkaXN0cmlidXRlIGl0cyBjb250ZW50cyB0
byBhbnkgb3RoZXIgcGVyc29uLg0KKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioNCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5v
c2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5N
c29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1h
cmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJU
aW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXtt
c28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5k
ZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5
bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxp
bmU7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0YXRlLCBkaXYuTXNvQWNldGF0ZQ0KCXttc28t
c3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkJhbGxvb24gVGV4dCBDaGFyIjsN
CgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6OC4wcHQ7
DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO30NCnNwYW4uYXBwbGUtdGFiLXNw
YW4NCgl7bXNvLXN0eWxlLW5hbWU6YXBwbGUtdGFiLXNwYW47fQ0Kc3Bhbi5hcHBsZS1jb252ZXJ0
ZWQtc3BhY2UNCgl7bXNvLXN0eWxlLW5hbWU6YXBwbGUtY29udmVydGVkLXNwYWNlO30NCnNwYW4u
QmFsbG9vblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJCYWxsb29uIFRleHQgQ2hhciI7DQoJ
bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxsb29uIFRleHQiOw0K
CWZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLkVtYWlsU3R5bGUyMw0K
CXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
InNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0
eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2Vj
dGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIu
MHB0IDcyLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0t
Pjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0
PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUg
bXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4
dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4N
CjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLUdCIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4N
CjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+SSB0aGluayBwb2ludCAzIHNob3Vs
ZCBiZSDigJxtYXnigJ0gcmF0aGVyIHRoYW4g4oCcd2lsbOKAnSwgYnV0IG90aGVyd2lzZSBnb29k
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIu
MHB0Ij48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMwMDdFN0UiPi0tDQo8bzpw
PjwvbzpwPjwvc3Bhbj48L2I+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdp
bi1ib3R0b206MTIuMHB0Ij48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZh
bWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMwMDdF
N0UiPkNocmlzdG9waGVyIERlYXJsb3ZlPGJyPg0KU2VuaW9yIFByaW5jaXBhbCBFbmdpbmVlcjxi
cj4NCkJBRSBTeXN0ZW1zIEFwcGxpZWQgSW50ZWxsaWdlbmNlIExhYm9yYXRvcmllczxicj4NCjwv
c3Bhbj48L2I+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojQkVCRUJFIj5fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXzxicj4NCjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo4LjBw
dDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2Nv
bG9yOiMwMDAwN0UiPjxicj4NCjwvc3Bhbj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjguMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6IzdEN0Q3RCI+VDwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo4LjBwdDtmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiM3
RDdEN0QiPjogJm5ic3A7JiM0Mzs0NCAzMzAwIDQ2NzUwMCAmbmJzcDt8ICZuYnNwOzxiPkU6DQo8
L2I+PGEgaHJlZj0ibWFpbHRvOmNocmlzLmRlYXJsb3ZlQGJhZXN5c3RlbXMuY29tIj5jaHJpcy5k
ZWFybG92ZUBiYWVzeXN0ZW1zLmNvbTwvYT48YnI+DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZTo4LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMwMDAwN0UiPjxicj4NCjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjguMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDs7Y29sb3I6IzNBOEI5MiI+QkFFIFN5c3RlbXMgQXBwbGllZCBJbnRlbGxpZ2VuY2UsIENoZWxt
c2ZvcmQgVGVjaG5vbG9neSBQYXJrLCBHcmVhdCBCYWRkb3csIENoZWxtc2ZvcmQsIEVzc2V4IENN
MiA4SE4uPGJyPg0KPGEgaHJlZj0iaHR0cDovL3d3dy5iYWVzeXN0ZW1zLmNvbS9haSI+PHNwYW4g
c3R5bGU9ImNvbG9yOiMzQThCOTIiPnd3dy5iYWVzeXN0ZW1zLmNvbS9haTwvc3Bhbj48L2E+PG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZTo4LjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOiMzQThCOTIiPkJBRSBTeXN0ZW1zIEFwcGxpZWQgSW50ZWxsaWdlbmNl
IExpbWl0ZWQ8YnI+DQpSZWdpc3RlcmVkIGluIEVuZ2xhbmQgJmFtcDsgV2FsZXMgTm86IDAxMzM3
NDUxPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1h
cmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjguMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzNBOEI5
MiI+UmVnaXN0ZXJlZCBPZmZpY2U6IFN1cnJleSBSZXNlYXJjaCBQYXJrLCBHdWlsZGZvcmQsIFN1
cnJleSwgR1UyIDdZUDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTti
b3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSI+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQt
c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2Vy
aWYmcXVvdDsiPkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQt
c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2Vy
aWYmcXVvdDsiPiBKaWF6aSBZaSBbbWFpbHRvOmlldGZAamlheml5aS5jb21dDQo8YnI+DQo8Yj5T
ZW50OjwvYj4gMTAgTWF5IDIwMTcgMTM6NDE8YnI+DQo8Yj5Ubzo8L2I+IERlYXJsb3ZlLCBDaHJp
c3RvcGhlciAoVUspPGJyPg0KPGI+Q2M6PC9iPiBpZXRmQGlldGYub3JnOyBtYW5ldEBpZXRmLm9y
ZzsgZHJhZnQtaWV0Zi1tYW5ldC1vbHNydjItbXVsdGlwYXRoQGlldGYub3JnOyBtYW5ldC1jaGFp
cnNAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFttYW5ldF0gTGFzdCBDYWxsOiAm
bHQ7ZHJhZnQtaWV0Zi1tYW5ldC1vbHNydjItbXVsdGlwYXRoLTEyLnR4dCZndDsgKE11bHRpLXBh
dGggRXh0ZW5zaW9uIGZvciB0aGUgT3B0aW1pemVkIExpbmsgU3RhdGUgUm91dGluZyBQcm90b2Nv
bCB2ZXJzaW9uIDIgKE9MU1J2MikpIHRvIEV4cGVyaW1lbnRhbCBSRkM8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6c29saWQgYmxhY2sgMS4wcHQ7cGFkZGluZzoy
LjBwdCAyLjBwdCAyLjBwdCAyLjBwdCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBhbGlnbj0iY2Vu
dGVyIiBzdHlsZT0idGV4dC1hbGlnbjpjZW50ZXI7YmFja2dyb3VuZDp3aGl0ZSI+PHNwYW4gc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBhbGlnbj0iY2VudGVyIiBzdHlsZT0idGV4dC1hbGlnbjpjZW50ZXI7YmFj
a2dyb3VuZDp3aGl0ZSI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxNS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMzMzOTcy
Ij4qKiogV0FSTklORyAqKio8bzpwPjwvbzpwPjwvc3Bhbj48L2I+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgYWxpZ249ImNlbnRlciIgc3R5bGU9Im1hcmdpbi1ib3R0
b206MTIuMHB0O3RleHQtYWxpZ246Y2VudGVyO2JhY2tncm91bmQ6d2hpdGUiPg0KPGVtPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzMzMzk3MiI+VGhpcyBtZXNzYWdlIG9yaWdpbmF0
ZXMgZnJvbSBvdXRzaWRlIG91ciBvcmdhbmlzYXRpb24sIGVpdGhlciBmcm9tIGFuIGV4dGVybmFs
IHBhcnRuZXIgb3IgdGhlIGludGVybmV0Ljwvc3Bhbj48L2VtPjxpPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2Vy
aWYmcXVvdDs7Y29sb3I6IzMzMzk3MiI+PGJyPg0KPGVtPjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Db25zaWRlciBjYXJl
ZnVsbHkgd2hldGhlciB5b3Ugc2hvdWxkIGNsaWNrIG9uIGFueSBsaW5rcywgb3BlbiBhbnkgYXR0
YWNobWVudHMgb3IgcmVwbHkuPC9zcGFuPjwvZW0+PGJyPg0KPGVtPjxzcGFuIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gb3IgaW5m
b3JtYXRpb24gcmVnYXJkaW5nIDwvc3Bhbj4NCjwvZW0+PC9zcGFuPjwvaT48c3Ryb25nPjxpPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6cmVkIj5SZWQgRmxhZ3M8L3NwYW4+PC9pPjwv
c3Ryb25nPjxlbT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVv
dDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMzMzM5NzIiPiB0aGF0
IHlvdSBjYW4gbG9vayBvdXQgZm9yIGluIGVtYWlscyB5b3UgcmVjZWl2ZSwNCiBjbGljayA8YSBo
cmVmPSJodHRwOi8vd3Mtc2l0ZXMuZW50LmJhZXN5c3RlbXMuY29tL3NpdGVzL0hPU0VDU3Rkc0xp
YnJhcnkvU3RhbmRhcmRzTGlicmFyeS9FdmVyeW9uZS9SZWQlMjBGbGFncy5wZGYiPg0KaGVyZTwv
YT4uPC9zcGFuPjwvZW0+PGk+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMzMzOTcy
Ij48YnI+DQo8ZW0+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDsiPklmIHlvdSBmZWVsIHRoZSBlbWFpbCBpcyBzdXNwaWNpb3Vz
LCBwbGVhc2UgZm9sbG93DQo8YSBocmVmPSJodHRwOi8vd3Mtc2l0ZXMuZW50LmJhZXN5c3RlbXMu
Y29tL3NpdGVzL0hPU0VDU3Rkc0xpYnJhcnkvU3RhbmRhcmRzTGlicmFyeS9FdmVyeW9uZS9EZWFs
aW5nJTIwV2l0aCUyMFN1c3BpY2lvdXMlMjBFbWFpbHMucGRmIj4NCnRoaXMgcHJvY2VzczwvYT4u
PC9zcGFuPjwvZW0+PC9zcGFuPjwvaT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMz
MzM5NzIiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+SGkgQ2hyaXMsJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9LLCBpdCBtYWtlcyBzZW5zZS4gU28gdGhl
IHBvbGljeSB3aWxsIGJlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBjbGFzcz0iYXBwbGUtdGFiLXNwYW4iPiZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8L3Nw
YW4+LSB0aGUgU09VUkNFX1JPVVRFIFRMViB3b27igJl0IGhhdmUgYW55IHZhbHVlPG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBjbGFzcz0i
YXBwbGUtdGFiLXNwYW4iPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8L3NwYW4+LSBFdmVyeSBUQyBtZXNzYWdlIG9yaWdp
bmF0ZWQgYnkgdGhlIHNvdXJjZS1yb3V0ZSBzdXBwb3J0ZWQgcm91dGVycyB3aWxsIGhhdmUgYSBT
T1VSQ0VfUk9VVEUgVExWPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBjbGFzcz0iYXBwbGUtdGFiLXNwYW4iPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8L3NwYW4+
LSBUaGUgVEMgbWVzc2FnZSBub3QgY29udGFpbmluZyBhbnkgbmVpZ2hib3VyIGFkZHJlc3Mgd2ls
bCBoYXZlIGEgbG9uZ2VyIHZhbGlkaXR5IHRpbWUgY29tcGFyZWQgdG8gT0xTUnYyIG5vcm1hbCBU
QyBtZXNzYWdlcy4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+YmVzdDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5KaWF6aTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0
eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPk9uIDEwIE1heSAyMDE3LCBhdCAxMTozMywgRGVhcmxvdmUsIENocmlz
dG9waGVyIChVSykgJmx0OzxhIGhyZWY9Im1haWx0bzpjaHJpcy5kZWFybG92ZUBiYWVzeXN0ZW1z
LmNvbSI+Y2hyaXMuZGVhcmxvdmVAYmFlc3lzdGVtcy5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5
LjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90OyI+QWRkaXRpb25hbCBjb21tZW50cyAmZ3Q7Jmd0OyZndDsgYmVsb3cuIFdoYXQgSSdtIHBy
b3Bvc2luZyAoc3BlbGxlZCBvdXQgYSBiaXQgbW9yZSkgaXMgYWxsIHdpbiwgYW5kIHJlbW92ZXMg
cHJvYmxlbXMgd2l0aCB0aGUgY3VycmVudCBkZXNpZ24uIEkgdGhpbmsgdGhpcyBpcyBhIG11c3Qg
ZG8uPGJyPg0KPGJyPg0KLS08c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJz
cDs8L3NwYW4+PGJyPg0KQ2hyaXN0b3BoZXIgRGVhcmxvdmU8YnI+DQpTZW5pb3IgUHJpbmNpcGFs
IEVuZ2luZWVyPGJyPg0KQkFFIFN5c3RlbXMgQXBwbGllZCBJbnRlbGxpZ2VuY2UgTGFib3JhdG9y
aWVzPGJyPg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQo8YnI+DQpUOiAmbmJzcDsmIzQzOzQ0IDMz
MDAgNDY3NTAwICZuYnNwO3wgJm5ic3A7RTo8c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNw
YWNlIj4mbmJzcDs8L3NwYW4+PC9zcGFuPjxhIGhyZWY9Im1haWx0bzpjaHJpcy5kZWFybG92ZUBi
YWVzeXN0ZW1zLmNvbSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTom
cXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+Y2hyaXMuZGVhcmxv
dmVAYmFlc3lzdGVtcy5jb208L3NwYW4+PC9hPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsi
Pjxicj4NCjxicj4NCkJBRSBTeXN0ZW1zIEFwcGxpZWQgSW50ZWxsaWdlbmNlLCBDaGVsbXNmb3Jk
IFRlY2hub2xvZ3kgUGFyaywgR3JlYXQgQmFkZG93LCBDaGVsbXNmb3JkLCBFc3NleCBDTTIgOEhO
Ljxicj4NCjwvc3Bhbj48YSBocmVmPSJodHRwOi8vd3d3LmJhZXN5c3RlbXMuY29tL2FpIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij53d3cuYmFlc3lzdGVtcy5jb20vYWk8L3NwYW4+PC9h
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNh
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxicj4NCkJBRSBTeXN0ZW1zIEFwcGxpZWQg
SW50ZWxsaWdlbmNlIExpbWl0ZWQ8YnI+DQpSZWdpc3RlcmVkIGluIEVuZ2xhbmQgJmFtcDsgV2Fs
ZXMgTm86IDAxMzM3NDUxPGJyPg0KUmVnaXN0ZXJlZCBPZmZpY2U6IFN1cnJleSBSZXNlYXJjaCBQ
YXJrLCBHdWlsZGZvcmQsIFN1cnJleSwgR1UyIDdZUDxicj4NCjxicj4NCjxicj4NCi0tLS0tT3Jp
Z2luYWwgTWVzc2FnZS0tLS0tPGJyPg0KRnJvbTogSmlhemkgWWkgWzwvc3Bhbj48YSBocmVmPSJt
YWlsdG86aWV0ZkBqaWF6aXlpLmNvbSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250
LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+bWFp
bHRvOmlldGZAamlheml5aS5jb208L3NwYW4+PC9hPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDsiPl08c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PGJy
Pg0KU2VudDogMDkgTWF5IDIwMTcgMjM6NDk8YnI+DQpUbzogRGVhcmxvdmUsIENocmlzdG9waGVy
IChVSyk8YnI+DQpDYzo8c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8
L3NwYW4+PC9zcGFuPjxhIGhyZWY9Im1haWx0bzppZXRmQGlldGYub3JnIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7Ij5pZXRmQGlldGYub3JnPC9zcGFuPjwvYT48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7Ij47IElFVEYtQW5ub3VuY2U7PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRl
ZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjwvc3Bhbj48YSBocmVmPSJtYWlsdG86bWFuZXRAaWV0Zi5v
cmciPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0
aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPm1hbmV0QGlldGYub3JnPC9zcGFuPjwv
YT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGlj
YSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij47PHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZl
cnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjwvc3Bhbj48YSBocmVmPSJtYWlsdG86ZHJhZnQtaWV0
Zi1tYW5ldC1vbHNydjItbXVsdGlwYXRoQGlldGYub3JnIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7Ij5kcmFmdC1pZXRmLW1hbmV0LW9sc3J2Mi1tdWx0aXBhdGhAaWV0Zi5vcmc8L3NwYW4+
PC9hPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0
aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjs8c3BhbiBjbGFzcz0iYXBwbGUtY29u
dmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PC9zcGFuPjxhIGhyZWY9Im1haWx0bzptYW5ldC1j
aGFpcnNAaWV0Zi5vcmciPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPm1hbmV0LWNoYWly
c0BpZXRmLm9yZzwvc3Bhbj48L2E+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZh
bWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PGJyPg0K
U3ViamVjdDogUmU6IFttYW5ldF0gTGFzdCBDYWxsOiAmbHQ7ZHJhZnQtaWV0Zi1tYW5ldC1vbHNy
djItbXVsdGlwYXRoLTEyLnR4dCZndDsgKE11bHRpLXBhdGggRXh0ZW5zaW9uIGZvciB0aGUgT3B0
aW1pemVkIExpbmsgU3RhdGUgUm91dGluZyBQcm90b2NvbCB2ZXJzaW9uIDIgKE9MU1J2MikpIHRv
IEV4cGVyaW1lbnRhbCBSRkM8YnI+DQo8YnI+DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tISBXQVJO
SU5HICEgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSBUaGlzIG1lc3NhZ2Ugb3JpZ2luYXRlcyBmcm9t
IG91dHNpZGUgb3VyIG9yZ2FuaXNhdGlvbiwgZWl0aGVyIGZyb20gYW4gZXh0ZXJuYWwgcGFydG5l
ciBvciBmcm9tIHRoZSBpbnRlcm5ldC48YnI+DQpDb25zaWRlciBjYXJlZnVsbHkgd2hldGhlciB5
b3Ugc2hvdWxkIGNsaWNrIG9uIGFueSBsaW5rcywgb3BlbiBhbnkgYXR0YWNobWVudHMgb3IgcmVw
bHkuPGJyPg0KRm9sbG93IHRoZSAnUmVwb3J0IFN1c3BpY2lvdXMgRW1haWxzJyBsaW5rIG9uIElU
IG1hdHRlcnMgZm9yIGluc3RydWN0aW9ucyBvbiByZXBvcnRpbmcgc3VzcGljaW91cyBlbWFpbCBt
ZXNzYWdlcy48YnI+DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLTxicj4NCjxicj4NCkhpIENocmlzLDxzcGFuIGNsYXNzPSJhcHBsZS1jb252
ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48YnI+DQo8YnI+DQpUaGFua3MgYSBsb3QgZm9yIHRo
ZSBjb21tZW50cyEgUGxlYXNlIGNoZWNrIG91ciByZXBseSBpbmxpbmU6PHNwYW4gY2xhc3M9ImFw
cGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjxicj4NCjxiciBzdHlsZT0iZm9udC12
YXJpYW50LWNhcHM6IG5vcm1hbDt0ZXh0LWFsaWduOnN0YXJ0Oy13ZWJraXQtdGV4dC1zdHJva2Ut
d2lkdGg6IDBweDt3b3JkLXNwYWNpbmc6MHB4Ij4NCjxicj4NCjwvc3Bhbj48bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPk9u
IDkgTWF5IDIwMTcsIGF0IDEyOjEzLCBEZWFybG92ZSwgQ2hyaXN0b3BoZXIgKFVLKSAmbHQ7PGEg
aHJlZj0ibWFpbHRvOmNocmlzLmRlYXJsb3ZlQGJhZXN5c3RlbXMuY29tIj5jaHJpcy5kZWFybG92
ZUBiYWVzeXN0ZW1zLmNvbTwvYT4mZ3Q7IHdyb3RlOjxicj4NCjxicj4NCkEgZmV3IGNvbW1lbnRz
IG9uIHRoaXMgZHJhZnQuPGJyPg0KPGJyPg0KSVB2NiBzcGVjaWZpZXMgY29tcGxldGUgc291cmNl
IHJvdXRpbmcuIEJ1dCB0aGlzIHNwZWNpZmljYXRpb24gY2FuIG9ubHkgY29uc2lkZXIgd2hhdCBo
YXBwZW5zIHdpdGhpbiB0aGUgTUFORVQuIFNvIGZvciBhIHBhY2tldCBmcm9tIHNvbWV3aGVyZSBp
biB0aGUgTUFORVQgdG8gc29tZXdoZXJlIHdlbGwgb3V0c2lkZSB0aGUgTUFORVQsIHRoZSBwYWNr
ZXQgbXVzdCBiZSBzb3VyY2Ugcm91dGVkIHRvIHRoZSBnYXRld2F5IGJldHdlZW4gTUFORVQgYW5k
DQogcmVzdCBvZiBJbnRlcm5ldCwgYW5kIG5vdCBzb3VyY2Ugcm91dGVkIGFmdGVyIHRoYXQuIFRo
aXMgSSB0aGluayBzaG91bGQgYmUgZXhwbGljaXRseSBtZW50aW9uZWQuIFdoZXRoZXIgdGhhdCBp
cyBjb25zaWRlcmVkIGNvbXBsaWFudCB3aXRoIElQdjYgSSBsZWF2ZSB0byBvdGhlcnMuPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1z
ZXJpZiZxdW90OyI+PGJyPg0KR29vZCBwb2ludC4gV2UgYWRkZWQgc29tZSB0ZXh0IGF0IHRoZSBl
bmQgb2Ygc2VjdGlvbiA4LjQmcXVvdDsgRGF0YWdyYW0gUHJvY2Vzc2luZyBhdCB0aGUgTVAtT0xT
UnYyIE9yaWdpbmF0b3ImcXVvdDs8YnI+DQo8YnIgc3R5bGU9ImZvbnQtdmFyaWFudC1jYXBzOiBu
b3JtYWw7dGV4dC1hbGlnbjpzdGFydDstd2Via2l0LXRleHQtc3Ryb2tlLXdpZHRoOiAwcHg7d29y
ZC1zcGFjaW5nOjBweCI+DQo8YnI+DQo8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48YnI+DQo3LjEgU1JfYWRk
ciB3b3VsZCBiZXR0ZXIgc2F5ICZxdW90O29yaWdpbmF0b3ImcXVvdDsgYWRkcmVzcyByYXRoZXIg
dGhhbjxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48YnI+
DQomcXVvdDtuZXR3b3JrJnF1b3Q7IGFkZHJlc3MuIChUaGF0IG1ha2VzIGl0IGFuIGFkZHJlc3Mg
d2l0aG91dCBhIG5ldG1hc2ssIHNlZTxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2Ui
PiZuYnNwOzwvc3Bhbj48YnI+DQpSRkMgNzE4MS4pPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWls
eTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PGJyPg0KZml4
ZWQuPHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjxicj4N
CjxiciBzdHlsZT0iZm9udC12YXJpYW50LWNhcHM6IG5vcm1hbDt0ZXh0LWFsaWduOnN0YXJ0Oy13
ZWJraXQtdGV4dC1zdHJva2Utd2lkdGg6IDBweDt3b3JkLXNwYWNpbmc6MHB4Ij4NCjxicj4NCjwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4t
Ym90dG9tOjEyLjBwdCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTom
cXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PGJyPg0KOC4xIFRo
aXMgaXMgc3VnZ2VzdGluZyBjcmVhdGluZyBUQyBtZXNzYWdlcyB0aGF0IGhhdmUgb24gbmVpZ2hi
b3VyIGFkZHJlc3NlcyBidXQgaGF2ZSBvbmx5IGEgU09VUkNFX1JPVVRFIFRMVi4gVGhpcyBpcyBu
b3QgdGhlIGRlc2lnbiBJIHdvdWxkIGhhdmUgc3VnZ2VzdGVkIGFzIGNvbnNpc3RlbnQgd2l0aCBo
b3cgSSB3b3VsZCBleHBlY3QgYW4gZXh0ZW5zaW9uIHRvIE9MU1J2MiB0byBkbyB0aGluZ3MuIFdl
IG5lZWQgdG8gY29uc2lkZXIgdHdvIGtpbmRzDQogb2Ygcm91dGVyczogdGhvc2Ugc2VuZGluZyBU
QyBtZXNzYWdlcyBhbnl3YXksIHRob3NlIHRoYXQgKG90aGVyIHRoYW4gdGhpcyBleHRlbnNpb24p
IGRvIG5vdC4gSW4gdGhlIGZvcm1lciBjYXNlIHlvdSBjb3VsZCBqdXN0IGFkZCB0aGUgU09VUkNF
X1JPVVRFIFRMViB0byB0aG9zZSBUQyBtZXNzYWdlcyBpdCBzZW5kcy4gVGhlbiB0aGF0IGluZm9y
bWF0aW9uIGlzIG1haW50YWluZWQgdXAgdG8gZGF0ZS4gUm91dGVycyB0aGF0IGRvbid0IHVzdWFs
bHkNCiBzZW5kIFRDIG1lc3NhZ2VzIGNvdWxkIHNlbmQgVEMgbWVzc2FnZXMgd2l0aCBqdXN0IHRo
YXQgVExWLiBCdXQgdGhlbiB0aGVyZSdzIGFuIGlzc3VlIG92ZXIgdmFsaWRpdHkgdGltZS4gQSBw
YXJhbWV0ZXIgU1JfSE9MRF9USU1FX01VTFRJUExJRVIgaXMgaW50cm9kdWNlZC4gVGhlcmUncyBu
byBuZWVkIGZvciB0aGF0IC0geW91IGNhbiBzaW1wbHkgaW5jb3Jwb3JhdGUgdGhhdCBpbnRvIHRo
ZSB2YWxpZGl0eSB0aW1lIHJlY29yZGVkIGluIHRoZSBtZXNzYWdlLg0KIFRoYXQgYXZvaWRzIGEg
bmVlZCB0byBoYW5kbGUgdGhlIHR3byBjYXNlcyBvZiByb3V0ZXJzIGRpZmZlcmVudGx5LiBUaGVy
ZSBpcyB0aGVuIGFuIG9kZGl0eSB0aGF0IHlvdSBnZXQgc29tZSByb3V0ZXJzIHNlbmRpbmcgVEMg
bWVzc2FnZXMgd2l0aCBub3JtYWwgdmFsaWRpdHkgdGltZXMgYW5kIGFkZHJlc3NlcywgYW5kIHNv
bWUgdGhhdCBjYW4gYmUgc2VudCBsZXNzIGZyZXF1ZW50bHkgd2l0aCBubyBhZGRyZXNzZXMgYW5k
IGxvbmdlciB2YWxpZGl0eQ0KIHRpbWVzLiBCdXQgdGhhdCdzIHN1c3BlY3QgLSBub3RlIHRoYXQg
aXQncyBub3QgZG9uZSBpbiBPTFNSdjIgZm9yIGF0dGFjaGVkIG5ldHdvcmtzIChhbm90aGVyIHJl
YXNvbiB0byBzZW5kIFRDIG1lc3NhZ2VzIGFsdGhvdWdoIG5vIG5laWdoYm91cnMgbmVlZCByZXBv
cnRpbmcpLiBUaGF0J3MgYmVjYXVzZSBsb25nZXIgaW50ZXJ2YWxzIG1ha2UgcmVhY3RpbmcgdG8g
bmV3IHJvdXRlcnMgam9pbmluZyAoYW5kIG5ldHdvcmsgcmVhc3NlbWJseSBhZnRlcg0KIGZyYWdt
ZW50YXRpb24pIHNsb3cuPGJyPg0KUmF0aGVyIGEgYmV0dGVyIGRlc2lnbiB3b3VsZCBzaW1wbHkg
YmUgdG8gYWRkIFNPVVJDRV9ST1VURSBUTFYgdG8gbm9ybWFsIFRDIG1lc3NhZ2VzLiBXaGVuIHNl
bmRpbmcgVEMgbWVzc2FnZXMgZm9yIGp1c3QgdGhhdCByZWFzb24sIHRoYXQgY291bGQgYmUganVz
dCB0aGUgdXN1YWwgY2FzZSwgYnV0IHlvdSBjb3VsZCBhbGxvdyBhcyBhbiBvcHRpb24gaW4gdGhp
cyBjYXNlIHRvIHNlbmQgbGVzcyBmcmVxdWVudGx5IHdpdGggdmFsaWRpdHkgdGltZQ0KIGluY3Jl
YXNlZCBhY2NvcmRpbmdseS4gV2hlbiBub3QgdXNpbmcgdGhhdCBvcHRpb24sIG9uY2UgYSByb3V0
ZXIgbmVlZHMgdG8gc2VuZCBhIFRDIG1lc3NhZ2UsIGl0IGNvdWxkIHRoZW4gZGVjaWRlIHRvIHJl
cG9ydCBuZWlnaGJvdXJzLCBpbmNyZWFzaW5nIHRoZSB0b3BvbG9neSBkaXN0cmlidXRlZCBhbmQg
YWxsb3dpbmcgbW9yZSByb3V0ZXMsIHRoaXMgYWxzbyBiZWluZyBhbiBvcHRpb24uPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90OyI+PGJyPg0KSUlSQywgd2UgaGFkIGEgbG9uZyBkaXNjdXNzaW9uIG9uIHRoaXMgaXNz
dWUgYW5kIHByb2R1Y2VkIHRoZSBjdXJyZW50IHRleHQuPHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZl
cnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjxicj4NClRoZSBwdXJwb3NlIGlzIHRvIGlkZW50aWZ5
IHRoZSByb3V0ZXJzIHRoYXQgZG9u4oCZdCBzZW5kIFRDIG1lc3NhZ2VzIGJ1dCBzdXBwb3J0IHNv
dXJjZSByb3V0aW5nLiBUbyBhdm9pZCB1bm5lY2Vzc2FyeSBUQyBmbG9vZGluZywgdGhlIGludGVy
dmFsIGlzIG11Y2ggbG9uZ2VyIHRoYW4gdGhlIG5vcm1hbCBUQyBpbnRlcnZhbC48c3BhbiBjbGFz
cz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PGJyPg0KVGhlIG5vcm1hbCBU
QyBtZXNzYWdlcyAoZ2VuZXJhdGVkIGJhc2VkIG9uIFJGQzcxODEpIGFsd2F5cyBoYXZlIGEgU09V
UkNFX1JPVVRFIFRMVi4gQnV0IGlmIHdlIHVzZSB0aGUgc2FtZSB2YWxpZGl0eSB0aW1lIGZvciBi
b3RoIFJGQzcxODEgbm9ybWFsIFRDIHByb2Nlc3NpbmcgYW5kIE1QLU9MU1J2MiBTUl9ST1VURSBU
TFYgcHJvY2Vzc2luZywgdGhlIHZhbGlkIHRpbWUgaW4gdGhlIFNSLU9MU1J2MiBSb3V0ZXIgU2V0
IHdvdWxkIGJlIG11Y2ggc2hvcnRlcg0KIHRoYW4gZXhwZWN0ZWQuIEEgcG9zc2libGUgY2FzZSBp
cyB0aGF0LCB0aGUgcm91dGVyIHN0b3BzIHNlbmRpbmcgbm9ybWFsIFRDIG1lc3NhZ2VzLCB0aGUg
Y29ycmVzcG9uZGluZyBlbnRyeSBpbiB0aGUgU1ItT0xTUnYyIFJvdXRlciBzZXQgd2lsbCBzb29u
IGV4cGlyZS48c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+
PGJyPg0KVGhlcmVmb3JlLCBJIHRoaW5rIGl04oCZcyByZWFzb25hYmxlIHRvIG1ha2UgdXNlIG9m
IHRoZSBTUl9IT0xEX1RJTUVfTVVMVElQTElFUiB0byBkaXN0aW5ndWlzaCB0aGUgdmFsaWQgdGlt
ZSBvZiBub3JtYWwgVEMgbWVzc2FnZSBpbmZvcm1hdGlvbiBhbmQgU1JfUk9VVEUgaW5mb3JtYXRp
b24uPHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjxicj4N
CjxiciBzdHlsZT0iZm9udC12YXJpYW50LWNhcHM6IG5vcm1hbDt0ZXh0LWFsaWduOnN0YXJ0Oy13
ZWJraXQtdGV4dC1zdHJva2Utd2lkdGg6IDBweDt3b3JkLXNwYWNpbmc6MHB4Ij4NCjxicj4NCjwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0
O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4w
cHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7Ij5JIGRvbid0IGFncmVlLCBhbmQgSSB0aGluayB3aGF0IHlvdSBh
cmUgc3VnZ2VzdGluZyBpbnRyb2R1Y2VzIGEgcHJvYmxlbSBhbmQgdW5uZWNlc3Nhcnkgb3Zlcmhl
YWQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9ibG9ja3F1b3RlPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZh
bWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PGJyIHN0
eWxlPSJmb250LXZhcmlhbnQtY2Fwczogbm9ybWFsO3RleHQtYWxpZ246c3RhcnQ7LXdlYmtpdC10
ZXh0LXN0cm9rZS13aWR0aDogMHB4O3dvcmQtc3BhY2luZzowcHgiPg0KPGJyPg0KPC9zcGFuPjxv
OnA+PC9vOnA+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2lu
LWJvdHRvbTo1LjBwdCI+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJn
aW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDsiPlRoZSBwcm9ibGVtIGlzIHRoYXQgZXZlcnl3aGVyZSBpbiBPTFNSdjIgd2Ug
YXJlIGNhcmVmdWwgdG8gZW5zdXJlIHRoYXQgcGFyYW1ldGVycyBjYW4gYmUgaW5kZXBlbmRlbnRs
eSBzZXQsIGFuZCB0aGF0IHJvdXRlcnMgZG9uJ3QgbmVlZCB0byBjb29yZGluYXRlIHRvIGludGVy
b3BlcmF0ZS4gKFRoZXkNCiBtYXkgZG8gYmV0dGVyIGlmIHRoZXkgZG8sIGJ1dCB0aGF0J3MgYSBy
ZWZpbmVtZW50LikgSGVyZSB5b3UgYXJlIHVzaW5nIGFuIFNSX0hPTERfVElNRV9NVUxUSVBMSUVS
IHRoYXQgdGhlIHJlY2VpdmVyIGhhcyB0byBrbm93IGlzIHdoYXQgdGhlIHNlbmRlciBpbnRlbmRz
LiBBbmQgaXQncyB1bm5lY2Vzc2FyeS4gSWYgYWxsIHRoYXQncyBpbiB0aGUgVEMgbWVzc2FnZSBp
cyB0aGUgU09VUkNFX1JPVVRFIFRMViwgeW91IGNhbiBqdXN0IGdpdmUgdGhhdA0KIGEgbG9uZ2Vy
IHZhbGlkaXR5IHRpbWUsIGJlY2F1c2UgdGhlIG9ubHkgdGhpbmcgdGhhdCB2YWxpZGl0eSB0aW1l
IHdpbGwgaW1wYWN0IG9uIGlzIHRoZSBzb3VyY2Ugcm91dGluZyBzdGF0dXMuIElmIHRoZSByb3V0
ZXIgaXMgYWxzbyBzZW5kaW5nIG5vcm1hbCBUQyBtZXNzYWdlcyBhbmQgeW91IHNlbmQgc2VwYXJh
dGUgU09VUkNFX1JPVVRFIFRMViBUQyBtZXNzYWdlcyB0aGVuIHRoYXQgd291bGQgc3RpbGwgYmUg
c28uIEJ1dCB0aGF0J3MgaW5lZmZpY2llbnQsDQogYmVjYXVzZSBpZiB0aGUgcm91dGVyIGlzIGFs
cmVhZHkgc2VuZGluZyBUQyBtZXNzYWdlcywgd2h5IHNlbmQgc2VwYXJhdGUgb25lcyB3aXRoIGFk
ZGVkIG92ZXJoZWFkLCB3aGVuIHlvdSBjYW4gcHV0IHRoZSBTT1VSQ0VfUk9VVEUgVExWIGluIHRo
ZSBzYW1lIFRDIG1lc3NhZ2U/IFRoYXQgd291bGQgdGhlbiAod2l0aG91dCBTUl9IT0xEX1RJTUVf
TVVMVElQTElFUiwgYnV0IHRoYXQncyBhIGdvb2QgdGhpbmcgYmVjYXVzZSBTUl9IT0xEX1RJTUVf
TVVMVElQTElFUg0KIGlzIG5vdCBnb29kKSBnaXZlIGEgc2hvcnRlciB2YWxpZGl0eSB0aW1lIHRv
IHRoZSBTT1VSQ0VfUk9VVEUgVExWLCBidXQgdGhhdCdzIGZpbmUsIGJlY2F1c2UgdGhhdCByb3V0
ZXIgd2lsbCBiZSBzZW5kaW5nIG1vcmUgVEMgbWVzc2FnZXMgd2l0aGluIHRoYXQgdGltZXNjYWxl
IGFueXdheS4gRnVydGhlcm1vcmUsIHRoaXMgYWxzbyBhbGxvd3MgdGhlIHJvdXRlciB0aGF0J3Mg
c2VuZGluZyBUQyBtZXNzYWdlcyBtb3JlIGZyZXF1ZW50bHkgdG8gcHJvdmlkZQ0KIGl0cyBpbmZv
cm1hdGlvbiBtb3JlIHJlc3BvbnNpdmVseSBpbiB0aGUgY2FzZXMgb2Ygbm9kZXMgam9pbmluZyBh
bmQgbmV0d29ya3MgcmVhc3NlbWJsaW5nLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvYmxvY2tx
dW90ZT4NCjwvYmxvY2txdW90ZT4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDsiPjxiciBzdHlsZT0iZm9udC12YXJpYW50LWNhcHM6IG5vcm1hbDt0ZXh0
LWFsaWduOnN0YXJ0Oy13ZWJraXQtdGV4dC1zdHJva2Utd2lkdGg6IDBweDt3b3JkLXNwYWNpbmc6
MHB4Ij4NCjxicj4NCjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJt
YXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGJsb2NrcXVvdGUgc3R5bGU9
Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZl
dGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5UaGF0IGdpdmVzIHR3byBiZWhhdmlv
dXJzOiByb3V0ZXJzIHNlbmRpbmcgVEMgbWVzc2FnZXMgYW55d2F5LCBqdXN0IGFkZCBhIFNPVVJD
RV9ST1VURSBUTFYsIGFuZCByb3V0ZXJzIG5vdCBzZW5kaW5nIFRDIG1lc3NhZ2VzIG90aGVyd2lz
ZSwganVzdCBpbmNsdWRlIGEgU09VUkNFX1JPVVRFIFRMVg0KIGFuZCBzZXQgdGhlIHZhbGlkaXR5
IHRpbWUgYWNjb3JkaW5nIHRvIHdoYXQgc2NoZWR1bGUgdGhhdCByb3V0ZXIgY2hvb3NlcyB0byB1
c2UgLSB3aGljaCBjYW4gYmUgYXQgdGhlIHNhbWUgcmF0ZSBhcyB0aGUgb3RoZXIgcm91dGVycywg
b3IgYXQgYSBzbG93ZXIgcm91dGUsIG9yIChhIG5ldyBjYXBhYmlsaXR5IHlvdSBkb24ndCBoYXZl
KSBzbG93bHksIGV4Y2VwdCBpZiB5b3UgbGVhcm4gb2YgdGhlIGV4aXN0ZW5jZSBvZiBhIG5ldyBy
b3V0ZXIgaW4NCiB0aGUgbmV0d29yayB5b3UgY2FuIHNlbmQgb25lIG9yIG1vcmUgcmVzcG9uc2l2
ZSBTT1VSQ0VfUk9VVEUgVExWIG9ubHkgVExWcyB0byBlbmFibGUgdGhhdCBuZXcgcm91dGVyIChv
ciByb3V0ZXJzKSB0byBsZWFybiBvZiB0aGUgc291cmNlIHJvdXRpbmcgcXVpY2tlci48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Jsb2NrcXVvdGU+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48YnIgc3R5bGU9ImZvbnQt
dmFyaWFudC1jYXBzOiBub3JtYWw7dGV4dC1hbGlnbjpzdGFydDstd2Via2l0LXRleHQtc3Ryb2tl
LXdpZHRoOiAwcHg7d29yZC1zcGFjaW5nOjBweCI+DQo8YnI+DQo8L3NwYW4+PG86cD48L286cD48
L3A+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUu
MHB0Ij4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206
NS4wcHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBw
dDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
OyI+SXQncyBhbGwgd2luOiBjb21iaW5pbmcgbWVzc2FnZXMsIHNvdXJjZSBzZXQgY29udHJvbCwg
YWJpbGl0eSB0byBkbyBtb3JlIGNsZXZlciB0aGluZ3MgaWYgeW91IHdhbnQgdG8uIChZb3UgY291
bGQgcHJvYmFibHkgJm5ic3A7ZXZlbiBzdGlsbCBzZW5kIHNlcGFyYXRlIFRDIG1lc3NhZ2VzIHdp
dGggYSBTT1VSQ0VfUk9VVEUNCiBUTFYgd2hlbiBhbHNvIHNlbmRpbmcgbm9ybWFsIFRDIG1lc3Nh
Z2VzIGlmIHlvdSByZWFsbHkgd2FudGVkIHRvLCBhcyBhbiBvcHRpb24gSSBjYW4ndCBzZWUgd2Fu
dGluZyB0byB1c2UgLSBhbHRob3VnaCBpdCBtaWdodCBpbnRyb2R1Y2UgYSBtaW5vciBwcm9ibGVt
IHRoYXQgSSBoYXZlbid0IHdvcmtlZCB0aHJvdWdoIHRoZSBPTFNSdjIgc3BlY2lmaWNhdGlvbiB0
byBjaGVjaywgYmVjYXVzZSBpdCdzIHVubmVjZXNzYXJ5Lik8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Jsb2NrcXVvdGU+DQo8L2Jsb2NrcXVvdGU+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48YnIgc3R5bGU9ImZvbnQtdmFyaWFudC1jYXBzOiBu
b3JtYWw7dGV4dC1hbGlnbjpzdGFydDstd2Via2l0LXRleHQtc3Ryb2tlLXdpZHRoOiAwcHg7d29y
ZC1zcGFjaW5nOjBweCI+DQo8YnI+DQo8L3NwYW4+PG86cD48L286cD48L3A+DQo8YmxvY2txdW90
ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxibG9ja3F1
b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTom
cXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+VGhlIHBvaW50IGlz
IHRoYXQgd2hhdCBJIHN1Z2dlc3QgY2FuIGdhaW4gZXZlcnl0aGluZyB5b3UgZG8sIGFuZCBhbGxv
dyBtb3JlLCBwbHVzIG5vdCBicmVha2luZyBleHBlY3RlZCBPTFNSdjIgYmVoYXZpb3VyLjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvYmxvY2txdW90ZT4NCjwvYmxvY2txdW90ZT4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxiciBzdHlsZT0iZm9u
dC12YXJpYW50LWNhcHM6IG5vcm1hbDt0ZXh0LWFsaWduOnN0YXJ0Oy13ZWJraXQtdGV4dC1zdHJv
a2Utd2lkdGg6IDBweDt3b3JkLXNwYWNpbmc6MHB4Ij4NCjxicj4NCjwvc3Bhbj48bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsi
PjguMyBzZWNvbmQgYnVsbGV0LiBZb3Ugc2hvdWxkIGhlcmUgKGFuZCBwb3NzaWJseSBlbHNld2hl
cmUpIGV4Y2x1ZGUgcm91dGVycyB3aXRoIHJvdXRpbmcgd2lsbGluZ25lc3MgemVyby48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7Ij48YnIgc3R5bGU9ImZvbnQtdmFyaWFudC1jYXBzOiBub3JtYWw7dGV4dC1hbGln
bjpzdGFydDstd2Via2l0LXRleHQtc3Ryb2tlLXdpZHRoOiAwcHg7d29yZC1zcGFjaW5nOjBweCI+
DQo8YnI+DQo8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48YnI+DQo4LjMgdGhlcmUgc2VlbXMgdG8gYmUgYW4g
aW5jb25zaXN0ZW5jeS4gV2hlbiBvcGVyYXRpbmcgcHJvYWN0aXZlbHkgYW5kIG5vIG11bHRpcGxl
IHJvdXRlcywgZHJvcCB0aGUgcGFja2V0LCBidXQgcmVhY3RpdmVseSB1c2Ugc3RhbmRhcmQgcm91
dGluZy4gVGhlIGxhdHRlciBzZWVtcyBtb3JlIGFwcHJvcHJpYXRlIGluIHRoZSBmb3JtZXIgY2Fz
ZSBhbHNvLjxicj4NCjxicj4NCjkgQ1VUT0ZGX1JBVElPLiBJbnNpc3RzIG9mIHN0cmljdGx5LCBi
dXQgYXMgZGVmaW5lZCBlYXJsaWVyLCBtYXkgYmUgJmd0Oz0gMWAuPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtm
b250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+
PGJyPg0KQWxsIGZpeGVkLjxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNw
Ozwvc3Bhbj48YnI+DQo8YnI+DQpUaGFua3MgYWdhaW4gZm9yIHRoZSB2YWx1YWJsZSBjb21tZW50
cyE8YnI+DQo8YnI+DQpiZXN0PGJyPg0KPGJyPg0KSmlhemk8YnI+DQo8YnIgc3R5bGU9ImZvbnQt
dmFyaWFudC1jYXBzOiBub3JtYWw7dGV4dC1hbGlnbjpzdGFydDstd2Via2l0LXRleHQtc3Ryb2tl
LXdpZHRoOiAwcHg7d29yZC1zcGFjaW5nOjBweCI+DQo8YnI+DQo8L3NwYW4+PG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48
YnI+DQotLTxicj4NCkNocmlzdG9waGVyIERlYXJsb3ZlPGJyPg0KU2VuaW9yIFByaW5jaXBhbCBF
bmdpbmVlcjxicj4NCkJBRSBTeXN0ZW1zIEFwcGxpZWQgSW50ZWxsaWdlbmNlIExhYm9yYXRvcmll
czxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48YnI+DQpf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fPGJyPg0KX19fXzxicj4NCjxicj4NClQ6ICZuYnNwOyYjNDM7NDQgMzMwMCA0
Njc1MDAgJm5ic3A7fCAmbmJzcDtFOiA8YSBocmVmPSJtYWlsdG86Y2hyaXMuZGVhcmxvdmVAYmFl
c3lzdGVtcy5jb20iPmNocmlzLmRlYXJsb3ZlQGJhZXN5c3RlbXMuY29tPC9hPjxicj4NCjxicj4N
CkJBRSBTeXN0ZW1zIEFwcGxpZWQgSW50ZWxsaWdlbmNlLCBDaGVsbXNmb3JkIFRlY2hub2xvZ3kg
UGFyaywgR3JlYXQgQmFkZG93LCBDaGVsbXNmb3JkLCBFc3NleCBDTTIgOEhOLjxicj4NCjxhIGhy
ZWY9Imh0dHA6Ly93d3cuYmFlc3lzdGVtcy5jb20vYWkiPnd3dy5iYWVzeXN0ZW1zLmNvbS9haTwv
YT48YnI+DQpCQUUgU3lzdGVtcyBBcHBsaWVkIEludGVsbGlnZW5jZSBMaW1pdGVkIFJlZ2lzdGVy
ZWQgaW4gRW5nbGFuZCAmYW1wOyBXYWxlczxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3Bh
Y2UiPiZuYnNwOzwvc3Bhbj48YnI+DQpObzogMDEzMzc0NTEgUmVnaXN0ZXJlZCBPZmZpY2U6IFN1
cnJleSBSZXNlYXJjaCBQYXJrLCBHdWlsZGZvcmQsPHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRl
ZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjxicj4NClN1cnJleSwgR1UyIDdZUDxicj4NCjxicj4NCjxi
cj4NCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPGJyPg0KRnJvbTogbWFuZXQgWzxhIGhyZWY9
Im1haWx0bzptYW5ldC1ib3VuY2VzQGlldGYub3JnIj5tYWlsdG86bWFuZXQtYm91bmNlc0BpZXRm
Lm9yZzwvYT5dIE9uIEJlaGFsZiBPZiBUaGUgSUVTRzxicj4NClNlbnQ6IDIwIEFwcmlsIDIwMTcg
MjI6NTE8YnI+DQpUbzogSUVURi1Bbm5vdW5jZTxicj4NCkNjOiA8YSBocmVmPSJtYWlsdG86bWFu
ZXRAaWV0Zi5vcmciPm1hbmV0QGlldGYub3JnPC9hPjsgPGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWll
dGYtbWFuZXQtb2xzcnYyLW11bHRpcGF0aEBpZXRmLm9yZyI+DQpkcmFmdC1pZXRmLW1hbmV0LW9s
c3J2Mi1tdWx0aXBhdGhAaWV0Zi5vcmc8L2E+OzxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQt
c3BhY2UiPiZuYnNwOzwvc3Bhbj48YnI+DQo8YSBocmVmPSJtYWlsdG86bWFuZXQtY2hhaXJzQGll
dGYub3JnIj5tYW5ldC1jaGFpcnNAaWV0Zi5vcmc8L2E+PGJyPg0KU3ViamVjdDogW21hbmV0XSBM
YXN0IENhbGw6ICZsdDtkcmFmdC1pZXRmLW1hbmV0LW9sc3J2Mi1tdWx0aXBhdGgtMTIudHh0Jmd0
OzxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48YnI+DQoo
TXVsdGktcGF0aCBFeHRlbnNpb24gZm9yIHRoZSBPcHRpbWl6ZWQgTGluayBTdGF0ZSBSb3V0aW5n
IFByb3RvY29sPHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFu
Pjxicj4NCnZlcnNpb24gMiAoT0xTUnYyKSkgdG8gRXhwZXJpbWVudGFsIFJGQzxicj4NCjxicj4N
Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0hIFdBUk5JTkcgISAtLS0tLS0tLS0tLS0tLS0tLS0tLS0t
IFRoaXMgbWVzc2FnZSBvcmlnaW5hdGVzIGZyb20gb3V0c2lkZSBvdXIgb3JnYW5pc2F0aW9uLCBl
aXRoZXIgZnJvbSBhbiBleHRlcm5hbCBwYXJ0bmVyIG9yIGZyb20gdGhlIGludGVybmV0Ljxicj4N
CkNvbnNpZGVyIGNhcmVmdWxseSB3aGV0aGVyIHlvdSBzaG91bGQgY2xpY2sgb24gYW55IGxpbmtz
LCBvcGVuIGFueSBhdHRhY2htZW50cyBvciByZXBseS48YnI+DQpGb2xsb3cgdGhlICdSZXBvcnQg
U3VzcGljaW91cyBFbWFpbHMnIGxpbmsgb24gSVQgbWF0dGVycyBmb3IgaW5zdHJ1Y3Rpb25zIG9u
IHJlcG9ydGluZyBzdXNwaWNpb3VzIGVtYWlsIG1lc3NhZ2VzLjxicj4NCi0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPGJyPg0KPGJyPg0KKioq
IFdBUk5JTkcgKioqPGJyPg0KRVhURVJOQUwgRU1BSUwgLS0gVGhpcyBtZXNzYWdlIG9yaWdpbmF0
ZXMgZnJvbSBvdXRzaWRlIG91ciBvcmdhbml6YXRpb24uPGJyPg0KPGJyPg0KPGJyPg0KVGhlIElF
U0cgaGFzIHJlY2VpdmVkIGEgcmVxdWVzdCBmcm9tIHRoZSBNb2JpbGUgQWQtaG9jIE5ldHdvcmtz
IFdHPGJyPg0KKG1hbmV0KSB0byBjb25zaWRlciB0aGUgZm9sbG93aW5nIGRvY3VtZW50Ojxicj4N
Ci0gJ011bHRpLXBhdGggRXh0ZW5zaW9uIGZvciB0aGUgT3B0aW1pemVkIExpbmsgU3RhdGUgUm91
dGluZyBQcm90b2NvbDxicj4NCiZuYnNwO3ZlcnNpb24gMiAoT0xTUnYyKSc8YnI+DQombHQ7ZHJh
ZnQtaWV0Zi1tYW5ldC1vbHNydjItbXVsdGlwYXRoLTEyLnR4dCZndDsgYXMgRXhwZXJpbWVudGFs
IFJGQzxicj4NCjxicj4NClRoZSBJRVNHIHBsYW5zIHRvIG1ha2UgYSBkZWNpc2lvbiBpbiB0aGUg
bmV4dCBmZXcgd2Vla3MsIGFuZCBzb2xpY2l0cyBmaW5hbCBjb21tZW50cyBvbiB0aGlzIGFjdGlv
bi4gUGxlYXNlIHNlbmQgc3Vic3RhbnRpdmUgY29tbWVudHMgdG8gdGhlDQo8YSBocmVmPSJtYWls
dG86aWV0ZkBpZXRmLm9yZyI+aWV0ZkBpZXRmLm9yZzwvYT4gbWFpbGluZyBsaXN0cyBieSAyMDE3
LTA1LTA0LiBFeGNlcHRpb25hbGx5LCBjb21tZW50cyBtYXkgYmUgc2VudCB0bw0KPGEgaHJlZj0i
bWFpbHRvOmllc2dAaWV0Zi5vcmciPmllc2dAaWV0Zi5vcmc8L2E+IGluc3RlYWQuIEluIGVpdGhl
ciBjYXNlLCBwbGVhc2UgcmV0YWluIHRoZSBiZWdpbm5pbmcgb2YgdGhlIFN1YmplY3QgbGluZSB0
byBhbGxvdyBhdXRvbWF0ZWQgc29ydGluZy48YnI+DQo8YnI+DQpBYnN0cmFjdDxicj4NCjxicj4N
Cjxicj4NCiZuYnNwO1RoaXMgZG9jdW1lbnQgc3BlY2lmaWVzIGEgbXVsdGktcGF0aCBleHRlbnNp
b24gZm9yIHRoZSBPcHRpbWl6ZWQgTGluazxicj4NCiZuYnNwO1N0YXRlIFJvdXRpbmcgUHJvdG9j
b2wgdmVyc2lvbiAyIChPTFNSdjIpIHRvIGRpc2NvdmVyIG11bHRpcGxlPGJyPg0KJm5ic3A7ZGlz
am9pbnQgcGF0aHMsIHNvIGFzIHRvIGltcHJvdmUgcmVsaWFiaWxpdHkgb2YgdGhlIE9MU1J2MiBw
cm90b2NvbC48YnI+DQombmJzcDtUaGUgaW50ZXJvcGVyYWJpbGl0eSB3aXRoIE9MU1J2MiBpcyBy
ZXRhaW5lZC48YnI+DQo8YnI+DQo8YnI+DQo8YnI+DQo8YnI+DQpUaGUgZmlsZSBjYW4gYmUgb2J0
YWluZWQgdmlhPGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2Mv
ZHJhZnQtaWV0Zi1tYW5ldC1vbHNydjItbXVsdGlwYXRoLyI+aHR0cHM6Ly9kYXRhdHJhY2tlci5p
ZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1tYW5ldC1vbHNydjItbXVsdGlwYXRoLzwvYT48YnI+DQo8
YnI+DQpJRVNHIGRpc2N1c3Npb24gY2FuIGJlIHRyYWNrZWQgdmlhPGJyPg0KPGEgaHJlZj0iaHR0
cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1tYW5ldC1vbHNydjItbXVs
dGlwYXRoL2JhbCI+aHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1t
YW5ldC1vbHNydjItbXVsdGlwYXRoL2JhbDwvYT48YnI+DQpsb3QvPGJyPg0KPGJyPg0KPGJyPg0K
Tm8gSVBSIGRlY2xhcmF0aW9ucyBoYXZlIGJlZW4gc3VibWl0dGVkIGRpcmVjdGx5IG9uIHRoaXMg
SS1ELjxicj4NCjxicj4NCjxicj4NCjxicj4NCjxicj4NCl9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KbWFuZXQgbWFpbGluZyBsaXN0PGJyPg0KPGEg
aHJlZj0ibWFpbHRvOm1hbmV0QGlldGYub3JnIj5tYW5ldEBpZXRmLm9yZzwvYT48YnI+DQo8YSBo
cmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21hbmV0Ij5odHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21hbmV0PC9hPjxicj4NCjxicj4NCjxicj4N
CioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqPGJyPg0KVGhpcyBlbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGFyZSBjb25m
aWRlbnRpYWwgdG8gdGhlIGludGVuZGVkPHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRlZC1zcGFj
ZSI+Jm5ic3A7PC9zcGFuPjxicj4NCnJlY2lwaWVudCBhbmQgbWF5IGFsc28gYmUgcHJpdmlsZWdl
ZC4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkPHNwYW4gY2xhc3M9ImFwcGxlLWNvbnZlcnRl
ZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjxicj4NCnJlY2lwaWVudCBwbGVhc2UgZGVsZXRlIGl0IGZy
b20geW91ciBzeXN0ZW0gYW5kIG5vdGlmeSB0aGUgc2VuZGVyLjxicj4NCllvdSBzaG91bGQgbm90
IGNvcHkgaXQgb3IgdXNlIGl0IGZvciBhbnkgcHVycG9zZSBub3IgZGlzY2xvc2Ugb3I8c3BhbiBj
bGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PGJyPg0KZGlzdHJpYnV0
ZSBpdHMgY29udGVudHMgdG8gYW55IG90aGVyIHBlcnNvbi48YnI+DQoqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9o
dG1sPg0K

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30DE633147CGLKXM0003vGREEN_--


From nobody Wed May 10 07:29:41 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 71522126CF6 for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 07:29:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_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 jEINWvA01VrX for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 07:29:37 -0700 (PDT)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::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 565AE129B65 for <ietf@ietf.org>; Wed, 10 May 2017 07:29:35 -0700 (PDT)
Received: by mail-wm0-x231.google.com with SMTP id u65so24120821wmu.1 for <ietf@ietf.org>; Wed, 10 May 2017 07:29:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:message-id:mime-version:thread-index :content-language; bh=Rx6IMmRlzTxlDoR8Gx3nPpHpxryJYs7acNCfUAMsqH8=; b=Ru5Cc28bgouVm6pQf0rO+++mgstXf4FbG//0lUGhGDSXVmH5tWjqJ8itfoMXVuutCs qmxjNoYaPAaQlIbougTUj0ArfJeZmxCTbnpjJZn9N95f2WbXVvXBO9WWOVQKGRmf43VM FCBIuaBEJDF986QiNmdrAHihU35eJRZ9pDkvf4/SBWWPp9AmN/ViR2uflA2vJ9sZjBKc aJPZoTMw/GYpKXPdAkWqpM70SD02MbSgyN8MyCQnUincZY08/cfjnThJxVCEmza7nNDW wCNItE3whAhAOUeppfRIlKrEbuqMCQGHYtzicI8p69WpublNDQHVvapnO9VMRi7Bj20K Y/Yw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :thread-index:content-language; bh=Rx6IMmRlzTxlDoR8Gx3nPpHpxryJYs7acNCfUAMsqH8=; b=QDpTv7Hlx5FHc6r9+kC/M+HNLXFAKYYUxtnK5vp4sTDJ7oCJMPzHezrUGdwAzows6Q /jSowhkS4TpsvDiOuw4E5Ll72DWOIQ00ReYMSCidu6LyzHzeRrJt9hzp0tYYgR1BsSuG Zpun+e3eJQ3CR8AoJW3dwJWP7qcpUtzCvvjoBYdpI05pm5OOYgl5b0TmDpfc+iaV9VzR aZhHAl+ZRsF8yMWOV5NvoVNsB9GHZiQ//22Y5WhsdArM3wHru/8hvDpUnEOHfmEaHhSc AQ9BEypnHMQtJbSZJy5obPk5U4E4KiETi4zN5B4BbrkKVDTL3kW0JbKHMiLu53oB0Fjz q6gQ==
X-Gm-Message-State: AODbwcADQSBdnwxnJThHCvG4AeOdj7BnONpPN3Zel0Cu5N8MtAHO8p8r jfa0WV160fzpswcT
X-Received: by 10.28.28.206 with SMTP id c197mr1277595wmc.59.1494426573572; Wed, 10 May 2017 07:29:33 -0700 (PDT)
Received: from DESKTOPFLHJVQJ (p57A77749.dip0.t-ipconnect.de. [87.167.119.73]) by smtp.gmail.com with ESMTPSA id w136sm15183987wmd.0.2017.05.10.07.29.32 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 May 2017 07:29:32 -0700 (PDT)
From: "Mehmet Ersue" <mersue@gmail.com>
To: <ietf@ietf.org>
Subject: IETF #100 Hotel Rate
Date: Wed, 10 May 2017 16:29:32 +0200
Message-ID: <012d01d2c999$d7adda40$87098ec0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_012E_01D2C9AA.9B37BBB0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdLJmZH4wtiCdawXQ5mNltfnQQeiNw==
Content-Language: de
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6sWdbNVRGvhLh9cAUCO55v1CdUk>
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, 10 May 2017 14:29:40 -0000

This is a multipart message in MIME format.

------=_NextPart_000_012E_01D2C9AA.9B37BBB0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

The Raffles Hotel Singapore (indicated as the meeting hotel for IETF #100)
is really nice.

I just looked at the room rates.

 

Daily room rate between Nov 11-18:  

>From $462.67, including tax (10% SC, 7% GST): $541,32

20% off, Prepay and nonrefundable:  

>From $370.13, including tax (10% SC, 7% GST): $433,05

 

Out of curiosity, I wonder how much the IETF rate is going to be.

Even if we get 50% off I assume it'll be difficult to pay.

Regards,

Mehmet

 


------=_NextPart_000_012E_01D2C9AA.9B37BBB0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><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:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	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=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal><span style=3D'color:#0000CC'>The Raffles Hotel =
Singapore (indicated as the meeting hotel for IETF #100) is really =
nice.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#0000CC'>I just looked at the room =
rates.<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'>Daily room rate between =
Nov 11-18:&nbsp; <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#0000CC'>From $462.67, including tax (10% SC, 7% GST): =
$541,32<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#0000CC'>20% off, Prepay and nonrefundable:&nbsp; =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#0000CC'>From $370.13, including tax (10% SC, 7% GST): =
$433,05<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'>Out of curiosity, I =
wonder how much the IETF rate is going to be.<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#0000CC'>Even if we get 50% off I =
assume it&#8217;ll be difficult to pay.<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#0000CC'> =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#0000CC'>Regards,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#0000CC'>Mehmet<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_012E_01D2C9AA.9B37BBB0--


From nobody Wed May 10 08:02:37 2017
Return-Path: <aretana@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 E921A129BCB for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 08:02:31 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 HdBubtBgaseM for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 08:02:30 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A28E127698 for <ietf@ietf.org>; Wed, 10 May 2017 08:02:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4014; q=dns/txt; s=iport; t=1494428550; x=1495638150; h=from:to:subject:date:message-id:mime-version; bh=lUT9p0Z4YisPOhE5QhsfEwOCnh7htBqZPcQ8ZBvOANs=; b=blBQUiSDwwoZ/VnRo3PsQHeSnnlzi3yNysrXXX9aYOKVjhPyPMdOVAhB bsGyD/0uGwGTyw4qqVKxzZU90kgWeNgFFSGiag9Gv9QsobPRGDnnZfV3q 4y2NuJptqhAHP2BLN7YG7bn9eEExXjxr0tdB63oPN5pucH4PRxBB44cel A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BMAgDJKhNZ/5ldJa1dGwEBAQMBAQEJA?= =?us-ascii?q?QEBgm5nYoETg2KKGJE2kFuFOIIPLIYUhGY/GAECAQEBAQEBAWsohT9oAQw+AgQ?= =?us-ascii?q?wJwQBijMOsmeCJiuKSAEBAQEBAQEBAQEBAQEBAQEBAQEBARgFhl+CCQuKVi+CM?= =?us-ascii?q?QWJS40khxsBkxqCBIFhjgaIf4tDAR84gQpwFVgBhmKJAoENAQEB?=
X-IronPort-AV: E=Sophos;i="5.38,319,1491264000";  d="scan'208,217";a="424331660"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 May 2017 15:02:29 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v4AF2TZx010010 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 10 May 2017 15:02:29 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 10 May 2017 10:02:28 -0500
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1210.000; Wed, 10 May 2017 10:02:28 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "ietf@ietf.org" <ietf@ietf.org>, "routing-dicussion@ietf.org" <routing-dicussion@ietf.org>
Subject: Routing Area Update after IETF 98 (blog)
Thread-Topic: Routing Area Update after IETF 98 (blog)
Thread-Index: AQHSyZ5xYZr+VGvdWUCZ+67cofMjSQ==
Date: Wed, 10 May 2017 15:02:28 +0000
Message-ID: <087B6537-9854-439E-97ED-1572D69877A5@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1f.0.170216
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.15.4]
Content-Type: multipart/alternative; boundary="_000_087B65379854439E97ED1572D69877A5ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KInNNq0EqkXIQtu6qp8mHVyHUD0>
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, 10 May 2017 15:02:32 -0000

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

SGVsbG8hDQoNCkFzIFJvdXRpbmcgQXJlYSBEaXJlY3RvcnMsIHdlIGhhdmUgbm93IG1hZGUgaXQg
YSBoYWJpdCB0byBzaGFyZSBzb21lIG9mIG91ciB0aG91Z2h0cyBhZnRlciBlYWNoIElFVEYgbWVl
dGluZy4gIFdlIGp1c3QgcG9zdGVkIGEgc2hvcnQgc3VtbWFyeSBvZiBzb21lIG9mIHRoZSBoaWdo
bGlnaHRzIGZyb20gdGhlIHJlY2VudCBvbmUgaW4gQ2hpY2Fnby4NCg0KaHR0cHM6Ly93d3cuaWV0
Zi5vcmcvYmxvZy8yMDE3LzA1L3JvdXRpbmctYXJlYS11cGRhdGUtYWZ0ZXItaWV0Zi05OC8NCg0K
DQpBbGlhLCBBbHZhcm8sIERlYm9yYWgNCg0K

--_000_087B65379854439E97ED1572D69877A5ciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <3DB7A9F7D3A553459E43DA3EC710A577@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iVGl0bGUiIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPSJLZXl3b3JkcyIgY29udGVu
dD0iIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUg
KGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0
IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ
cGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8N
CnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsN
CgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWls
eTpDYWxpYnJpO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFu
LkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1jb21wb3NlOw0KCWZvbnQt
ZmFtaWx5OkNhbGlicmk7DQoJY29sb3I6d2luZG93dGV4dDsNCglmb250LXdlaWdodDpub3JtYWw7
DQoJZm9udC1zdHlsZTpub3JtYWw7fQ0Kc3Bhbi5tc29JbnMNCgl7bXNvLXN0eWxlLXR5cGU6ZXhw
b3J0LW9ubHk7DQoJbXNvLXN0eWxlLW5hbWU6IiI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGlu
ZTsNCgljb2xvcjp0ZWFsO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9y
dC1vbmx5Ow0KCWZvbnQtZmFtaWx5OkNhbGlicmk7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3Np
emU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYu
V29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+DQo8L2hlYWQ+
DQo8Ym9keSBiZ2NvbG9yPSJ3aGl0ZSIgbGFuZz0iRU4tVVMiIGxpbms9IiMwNTYzQzEiIHZsaW5r
PSIjOTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5IZWxsbyE8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QXMgUm91dGluZyBBcmVhIERpcmVj
dG9ycywgd2UgaGF2ZSBub3cgbWFkZSBpdCBhIGhhYml0IHRvIHNoYXJlIHNvbWUgb2Ygb3VyIHRo
b3VnaHRzIGFmdGVyIGVhY2ggSUVURiBtZWV0aW5nLiZuYnNwOyBXZSBqdXN0IHBvc3RlZCBhIHNo
b3J0IHN1bW1hcnkgb2Ygc29tZSBvZiB0aGUgaGlnaGxpZ2h0cyBmcm9tIHRoZSByZWNlbnQgb25l
IGluIENoaWNhZ28uPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxhIGhyZWY9Imh0dHBzOi8vd3d3
LmlldGYub3JnL2Jsb2cvMjAxNy8wNS9yb3V0aW5nLWFyZWEtdXBkYXRlLWFmdGVyLWlldGYtOTgv
Ij5odHRwczovL3d3dy5pZXRmLm9yZy9ibG9nLzIwMTcvMDUvcm91dGluZy1hcmVhLXVwZGF0ZS1h
ZnRlci1pZXRmLTk4LzwvYT4NCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFsaWEsIEFsdmFybywgRGVib3JhaDxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9o
dG1sPg0K

--_000_087B65379854439E97ED1572D69877A5ciscocom_--


From nobody Wed May 10 08:13:10 2017
Return-Path: <ocl@gih.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 1AB25127B60 for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 08:13:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  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 (1024-bit key) header.d=gih.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 5umkKFM4C67k for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 08:13:07 -0700 (PDT)
Received: from waikiki.gih.co.uk (salsa.gih.co.uk [194.33.63.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41C6A1273B1 for <ietf@ietf.org>; Wed, 10 May 2017 08:13:07 -0700 (PDT)
Received: from waikiki.gih.co.uk (localhost [IPv6:::1]) by waikiki.gih.co.uk (Postfix) with ESMTP id 5D5D6320203; Wed, 10 May 2017 16:13:05 +0100 (BST)
DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=gih.co.uk; h=subject:to :references:from:message-id:date:mime-version:in-reply-to :content-type; s=mahalo1; bh=7ys+C1UZ7lSrrK/YYksCWBCJYtU=; b=NQz 1Y+PZJdqcfc5P82QuHefs2bH+1dAgnb30nofg1RvA0FbE0kX6ImoWcQFnXV55n4e xbgf8G6LNlHN3pMBIdplapjaKd9kG9QFyg7EUtH3MuumUBSKF2eXO2aJByt005dU fqTkfzZGXGQFNYIpCS8H7yRtMkYQ2zxlBA1VBGJg=
Received: from [192.168.1.153] (unknown [2.28.112.224]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by waikiki.gih.co.uk (Postfix) with ESMTPSA id AA1D3320201; Wed, 10 May 2017 16:13:04 +0100 (BST)
Subject: Re: IETF #100 Hotel Rate
To: Mehmet Ersue <mersue@gmail.com>, ietf@ietf.org
References: <012d01d2c999$d7adda40$87098ec0$@gmail.com>
From: =?UTF-8?Q?Olivier_MJ_Cr=c3=a9pin-Leblond?= <ocl@gih.com>
Message-ID: <51f9d3d1-6c5c-102d-d76d-ea0d35433921@gih.com>
Date: Wed, 10 May 2017 16:13:05 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0
MIME-Version: 1.0
In-Reply-To: <012d01d2c999$d7adda40$87098ec0$@gmail.com>
Content-Type: multipart/alternative; boundary="------------843291DE6B94156ED52FA2A1"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/i-7_fZjBLNLTGTSLC_zV0uM2c6M>
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, 10 May 2017 15:13:09 -0000

This is a multi-part message in MIME format.
--------------843291DE6B94156ED52FA2A1
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Unlikely to be the Raffles hotel itself. I guess the conference is at
the Raffles City convention centre which has 2 hotels: the Fairmont &
the Swisshotel. Rates are lower than the super luxurious Raffles itself,
which is just across the road.
Kindest regards,

Olivier

On 10/05/2017 15:29, Mehmet Ersue wrote:
>
> The Raffles Hotel Singapore (indicated as the meeting hotel for IETF
> #100) is really nice.
>
> I just looked at the room rates.
>
> =20
>
> Daily room rate between Nov 11-18:=20
>
> From $462.67, including tax (10% SC, 7% GST): $541,32
>
> 20% off, Prepay and nonrefundable:=20
>
> From $370.13, including tax (10% SC, 7% GST): $433,05
>
> =20
>
> Out of curiosity, I wonder how much the IETF rate is going to be.
>
> Even if we get 50% off I assume it=92ll be difficult to pay.
>
> Regards,
>
> Mehmet
>
> =20
>


--------------843291DE6B94156ED52FA2A1
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html;
      charset=3Dwindows-1252">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    Unlikely to be the Raffles hotel itself. I guess the conference is
    at the Raffles City convention centre which has 2 hotels: the
    Fairmont &amp; the Swisshotel. Rates are lower than the super
    luxurious Raffles itself, which is just across the road.<br>
    Kindest regards,<br>
    <br>
    Olivier<br>
    <br>
    <div class=3D"moz-cite-prefix">On 10/05/2017 15:29, Mehmet Ersue
      wrote:<br>
    </div>
    <blockquote type=3D"cite"
      cite=3D"mid:012d01d2c999$d7adda40$87098ec0$@gmail.com">
      <meta http-equiv=3D"Content-Type" content=3D"text/html;
        charset=3Dwindows-1252">
      <meta name=3D"Generator" 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:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	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]-->
      <div class=3D"WordSection1">
        <p class=3D"MsoNormal"><span style=3D"color:#0000CC">The Raffles
            Hotel Singapore (indicated as the meeting hotel for IETF
            #100) is really nice.<o:p></o:p></span></p>
        <p class=3D"MsoNormal"><span style=3D"color:#0000CC">I just looke=
d
            at the room rates.<o:p></o:p></span></p>
        <p class=3D"MsoNormal"><span style=3D"color:#0000CC"><o:p>=A0</o:=
p></span></p>
        <p class=3D"MsoNormal"><span style=3D"color:#0000CC">Daily room r=
ate
            between Nov 11-18:=A0 <o:p></o:p></span></p>
        <p class=3D"MsoNormal"><span style=3D"color:#0000CC">From $462.67=
,
            including tax (10% SC, 7% GST): $541,32<o:p></o:p></span></p>
        <p class=3D"MsoNormal"><span style=3D"color:#0000CC">20% off, Pre=
pay
            and nonrefundable:=A0 <o:p></o:p></span></p>
        <p class=3D"MsoNormal"><span style=3D"color:#0000CC">From $370.13=
,
            including tax (10% SC, 7% GST): $433,05<o:p></o:p></span></p>
        <p class=3D"MsoNormal"><span style=3D"color:#0000CC"><o:p>=A0</o:=
p></span></p>
        <p class=3D"MsoNormal"><span style=3D"color:#0000CC">Out of
            curiosity, I wonder how much the IETF rate is going to be.<o:=
p></o:p></span></p>
        <p class=3D"MsoNormal"><span style=3D"color:#0000CC">Even if we g=
et
            50% off I assume it=92ll be difficult to pay.<o:p></o:p></spa=
n></p>
        <p class=3D"MsoNormal"><span style=3D"color:#0000CC"> <o:p></o:p>=
</span></p>
        <p class=3D"MsoNormal"><span style=3D"color:#0000CC">Regards,<o:p=
></o:p></span></p>
        <p class=3D"MsoNormal"><span style=3D"color:#0000CC">Mehmet<o:p><=
/o:p></span></p>
        <p class=3D"MsoNormal"><o:p>=A0</o:p></p>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------843291DE6B94156ED52FA2A1--


From nobody Wed May 10 08:13:42 2017
Return-Path: <alexandre.mendes-ex@solvay.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 E829C126E3A for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 01:13:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.101
X-Spam-Level: 
X-Spam-Status: No, score=0.101 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=solvay-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 G-BMk-DtGyYY for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 01:13:54 -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 0F713126D46 for <ietf@ietf.org>; Wed, 10 May 2017 01:13:53 -0700 (PDT)
Received: by mail-lf0-x22d.google.com with SMTP id h4so15320499lfj.3 for <ietf@ietf.org>; Wed, 10 May 2017 01:13:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=solvay-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=dlPnULOKw/Sc8CRct2JD6mCTvrPL0/g2rwJ3ixLZ9j4=; b=pgaWjijOx3DrUxFhxx8zbsr3Tly3yQHXmUeEagyEF4GQ4mDioWQGbnKryTM+eTxzpW kE4eSeZ6AZp8zYml/hhy4ZS1v03fZore15mpMay1dUIgQuNB0guQfZ1gZ4egDrn1pbSo WPhDNn3rJ9znMPo1OszlTh3LkpswzaHbjBUBDiked2Vi3xEuoUeObDlC+Qfc58XWsftt ZT4ndyun98th6frzixC6DuEh4LkX/UEgdnN4JKdW8dvucp/tVSaVUyLnsT/pEowpvghJ pFOfsGOOzH+GRx0Jr3L5vMwbVoPyQXORma5j60ObpHwn93UJN/tqSbPCPUjg6qOIQq3+ FLsg==
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=dlPnULOKw/Sc8CRct2JD6mCTvrPL0/g2rwJ3ixLZ9j4=; b=hTHBSIAJMPY0NwTLe280FwUmvtFGug4lXB2Jlv4DDBN3b+F9AvB4sbtuErieu4nHZX +uvJYV9pzqFH4m2uIO8hD+73L2xphuIFgSevG+aYA7LNNGIq1MF8QyPXfB8zq8BnzvK2 89Ae93EUCDriZz8SXJqrZAkF3GlD8JQ8W312Nu8cRdk3JguApIHpUnAb7XdGpsFzV9Zb EpWNvRjVPavacn+PuzZ4n9cm/0VoPdLbt3tjLlvd3kXWQKvY9inbfJ4FIxboh6LRreWg XCl1zeaCP0bxHYqcx19n8i0zIuybw1+GWfSj5GRmpQBkKddBpzhFS+PLi1K936AiB4xE Xg8Q==
X-Gm-Message-State: AODbwcDNUsQdWpH4EywlBAKUXrJ0onuOcrcLN4JszZo1LEP9xPTJlwlI UgXHmipXkjViJZONxtevWcUKwasJDwvZ9DQsJynPIIRX6JQhh2PsX2x9bq5nmGvPUQbHorFxswJ ldPIXpg==
X-Received: by 10.46.5.82 with SMTP id 79mr2140057ljf.95.1494404031762; Wed, 10 May 2017 01:13:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.21.27 with HTTP; Wed, 10 May 2017 01:13:51 -0700 (PDT)
From: "Mendes-ex, Alexandre" <alexandre.mendes-ex@solvay.com>
Date: Wed, 10 May 2017 09:13:51 +0100
Message-ID: <CAJmz+VWBgsnFu67OFR8yiVsuzW0Tz3Y29UViZz0cmikjfjakvw@mail.gmail.com>
Subject: Seeking help for SCIM 1.1 Implementation with Salesforce
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=001a1148e6f07734e1054f270de4
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yV0xoYt2VwZuZUaTe3jOlWYyeCw>
X-Mailman-Approved-At: Wed, 10 May 2017 08:13:40 -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: Wed, 10 May 2017 08:13:56 -0000

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

Hello,

My name is Alexandre Mendes and I am currently trying to implement User
Provisioning between 2 Salesforce orgs using the SCIM 1.1 connector.
After encountering some difficulties I am unable to solve I am trying to
find someone who could possibly shed some light in the situation.

As the website www.simplecloud.info only indicates that SCIM is developed
under the IEFT and unsure of which contact email would the indicated for my
case I firstly decided to contact the general information email, which then
indicated me this address.
I apologize if this was not the correct address for such a situation and I
hope you will be able to point me in the right direction.

Thank you for your attention.

Best Regards,
Alexandre Mendes

-- 


*This message and any attachments is intended for the named addressee(s) 
only and may contain information that is privileged and/or confidential. If 
you receive this message in error, please delete it and immediately notify 
the sender. Any copying, dissemination or disclosure, either whole or 
partial, by a person who is not the named addressee is prohibited. We use 
virus scanning software but disclaim any liability for viruses or other 
devices which remain in this message or any 
attachments.*******************************Ce message, ainsi que toute 
piece jointe, est exclusivement adresse au(x) destinataire(s) nomme(s) et 
peut contenir des informations confidentielles. Si vous recevez ce message 
par erreur, merci de le detruire et d'en avertir immediatement l'emetteur. 
Toute copie, transmission ou divulgation, integrale ou partielle, par une 
personne qui n'est pas nommee comme destinataire est interdite. Nous 
utilisons un logiciel anti-virus mais nous denions toute responsabilite au 
cas ou des virus, ou tout autre procede, seraient contenus dans ce message 
ou toute piece jointe.*

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

<div dir=3D"ltr"><span style=3D"font-size:12.8px">Hello,</span><div style=
=3D"font-size:12.8px"><br></div><div style=3D"font-size:12.8px">My name is =
Alexandre Mendes and I am currently trying to implement User Provisioning b=
etween 2 Salesforce orgs using the SCIM 1.1 connector.=C2=A0</div><div styl=
e=3D"font-size:12.8px">After encountering some difficulties I am unable to =
solve I am trying to find someone who could possibly shed some light in the=
 situation.</div><div style=3D"font-size:12.8px"><br></div><div style=3D"fo=
nt-size:12.8px">As the website=C2=A0<a href=3D"http://www.simplecloud.info/=
" target=3D"_blank">www.simplecloud.info</a>=C2=A0<wbr>only indicates that =
SCIM is developed under the IEFT and unsure of which contact email would th=
e indicated for my case I firstly decided to contact the general informatio=
n email, which then indicated me this address.</div><div style=3D"font-size=
:12.8px">I apologize if this was not the correct address for such a situati=
on and I hope you will be able to point me in the right direction.</div><di=
v style=3D"font-size:12.8px"><br></div><div style=3D"font-size:12.8px">Than=
k you for your attention.</div><div style=3D"font-size:12.8px"><br></div><d=
iv style=3D"font-size:12.8px">Best Regards,</div><div style=3D"font-size:12=
.8px">Alexandre Mendes</div></div>

<br>
<b style=3D"font-weight:normal"><font face=3D"Arial" size=3D"1"><span style=
=3D"color:rgb(102,102,102);background-color:rgb(255,255,255);vertical-align=
:baseline;white-space:pre-wrap">This message and any attachments is intende=
d for the named addressee(s) only and may contain information that is privi=
leged and/or confidential. If you receive this message in error, please del=
ete it and immediately notify the sender. Any copying, dissemination or dis=
closure, either whole or partial, by a person who is not the named addresse=
e is prohibited. We use virus scanning software but disclaim any liability =
for viruses or other devices which remain in this message or any attachment=
s.</span><br><span style=3D"color:rgb(102,102,102);background-color:rgb(255=
,255,255);vertical-align:baseline;white-space:pre-wrap">*******************=
***********<WBR>*</span><br><span style=3D"color:rgb(102,102,102);backgroun=
d-color:rgb(255,255,255);vertical-align:baseline;white-space:pre-wrap">Ce m=
essage, ainsi que toute piece jointe, est exclusivement adresse au(x) desti=
nataire(s) nomme(s) et peut contenir des informations confidentielles. Si v=
ous recevez ce message par erreur, merci de le detruire et d&#39;en avertir=
 immediatement l&#39;emetteur. Toute copie, transmission ou divulgation, in=
tegrale ou partielle, par une personne qui n&#39;est pas nommee comme desti=
nataire est interdite. Nous utilisons un logiciel anti-virus mais nous deni=
ons toute</span><span style=3D"background-color:rgb(255,255,255);vertical-a=
lign:baseline">=C2=A0</span><span style=3D"color:rgb(102,102,102);backgroun=
d-color:rgb(255,255,255);vertical-align:baseline;white-space:pre-wrap">resp=
onsabilite au cas ou des virus, ou tout autre procede, seraient contenus da=
ns ce message ou toute piece jointe.</span></font></b>
--001a1148e6f07734e1054f270de4--


From nobody Wed May 10 08:40:48 2017
Return-Path: <jefftant.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 99C3F129C06 for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 08:40:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 tVl7jb7u0Ckg for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 08:40:37 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::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 C43831294A1 for <ietf@ietf.org>; Wed, 10 May 2017 08:40:37 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id e64so17743686pfd.1 for <ietf@ietf.org>; Wed, 10 May 2017 08:40:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=k++lFeu8YzB+yGOd8ShmdxvWjD0vagr/06Y8dtqV3VA=; b=beWlqDCve6OGDKdry7fRv2NpLx7JXMYDWhO2UsEfgIZ3sQIm0iQj8gdRMNsqsNaHYK lRP2sJYT1ULnOCA1iotabyraAXOJ0aHbuXf93tpL8CUt1bWSOo/mwzHcuh0WkRUvRWY2 wg3K1E/ol/D8sMxxgFsMQS3E1ybrs48QHx5HwIt/OBPGLWKx4YyTOEYuCCIz1/h4saES eDnWuxLy+iQcWQgKdRU7vHI2HrxEXjgKz4TUUBiyvpPp7PsDhWPRY3c03yMrOkN3D9Qd J2r+bjCEFViZhDeLvqArFairxAPQRjlMAJAt01iWqwtX8nBfmb7WqT+84yZFeHfcPaV8 eTQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=k++lFeu8YzB+yGOd8ShmdxvWjD0vagr/06Y8dtqV3VA=; b=QWFdsq9MK9PzH/ZGrp727+ArX0ay7QfwH8SJsPGEHx6wuAdkOpZiNWaKKVEdFXpsr8 Arg1+rerGQCm3F7SrcuT4wiKWc34WCE6k6b+js2fBqy/QIPX28sz7dIitXq6FG+mu7bQ 7uGQ/tP14gHcezwpPsRwKnlEj3dU2Mh5iNVfh1PI18YltQX2OvtdVmGXx0SvitJNN+R1 uz/gks0nQ50GWlitDyB89qDPLPmgWjT2Car/3/6WPEpkwSEfd0dkETwRcW6DCtAQh+xc wM3Ukwzmgv2fdAHQkACPNFbL6VE2rHJf2f74vcO2c16Mwn+j96x9Eu+zFQ4YfChTT0fq 3BdA==
X-Gm-Message-State: AODbwcAI/6HtRj/ZVa/KD11TXeEzLFiXJUp7fxvTR2x/jXG+ArRJAbIR F9FrwdjV8m8lCj66c9g=
X-Received: by 10.98.157.83 with SMTP id i80mr6945988pfd.166.1494430837410; Wed, 10 May 2017 08:40:37 -0700 (PDT)
Received: from [192.168.1.7] ([76.126.247.72]) by smtp.gmail.com with ESMTPSA id i63sm6293755pgc.26.2017.05.10.08.40.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 May 2017 08:40:36 -0700 (PDT)
Content-Type: text/plain; charset=windows-1251
Mime-Version: 1.0 (1.0)
Subject: Re: Registration for remote participation
From: Jeff Tantsura <jefftant.ietf@gmail.com>
X-Mailer: iPhone Mail (14E304)
In-Reply-To: <A296FCD4-B00B-47A8-BDCF-295144F49696@piuha.net>
Date: Wed, 10 May 2017 08:40:35 -0700
Cc: IETF Discussion <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <43AD13CE-1263-4AE9-BFDB-F8E18EF853F6@gmail.com>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <A296FCD4-B00B-47A8-BDCF-295144F49696@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lu1cw9nSkPaVJV9H8QTNioeBa58>
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, 10 May 2017 15:40:46 -0000

+1
None of the questions asked are in invasive, while helping us to better unde=
rstand remote participation dynamics.
I also think adding few questions about "why remote" would help us in the fu=
ture to make better choices when it comes to organization.

Regards,
Jeff

> On May 9, 2017, at 14:22, Jari Arkko <jari.arkko@piuha.net> wrote:
>=20
> +1 for better data collection. We do need it.
>=20
> As for other future charging developments brought up by Stephen, those are=
 perhaps a point to be discussed in the later. For sure the potential for ch=
anging the model should be acknowledged. But, I have no reason to doubt that=
 IETF=92s community=92s wishes wouldn=92t be driving whatever direction remo=
te participation may develop into.
>=20
> Jari
>=20


From nobody Wed May 10 09:37:31 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 7BF4212E037 for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 09:37:29 -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 amwRSjkal8Q8 for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 09:37:27 -0700 (PDT)
Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::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 50E8F129C60 for <ietf@ietf.org>; Wed, 10 May 2017 09:37:25 -0700 (PDT)
Received: by mail-qt0-x22b.google.com with SMTP id n4so905396qte.2 for <ietf@ietf.org>; Wed, 10 May 2017 09:37: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=APL5s3Drctu/Yfi3rnPhYt/5d3dO3YMCxUIMsPST4+s=; b=ETOuPyDy6AQqFYOsYvSNhFrisaHXTmmBLpP5mTcetpNISMXwCJQcecP0xbkLjwN8ru yFVT0OZL4sR37c4jkZag/rnvqhK1a+eeSrWqqSJpFXmvQAGJl2ngwU2gGT77HyGjzYjr sOSMbMG5g6DNdIK5qSQAoBI4UgVt3LZEiT9R5Vf3jfT3aEdtrXAxCuK7PMt4Zbe4Q/lB 6RKHHaS7+Np8d0onhp6PO+7lkRHEk8Xettlbses3074ReJ1R2PBPxB6Y1g57sYF4ZfdA ZyJh+cZArUjjqnjJ0urXuy1KW4KD2qSGju0slHnx67EMoIiN3tVDBT2KvIJmoVfDEaEY ogYQ==
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=APL5s3Drctu/Yfi3rnPhYt/5d3dO3YMCxUIMsPST4+s=; b=XcVInAgHfEcO+yavx5UsYK1Y8o+e/bW7awPjkc9Shgz0R2+dlgHRV2/Io7orCD+mAO /YGsCg75BuYuqRztprePL2yfpEv9L0qnhIfSGtUaQ/d21+g4B7/cx7SKNH+Rh56ZiZnq YBOk5K0iIt+/KePY/sLCgL63h3UH9unl8y5OsewBaTCgaHJI4NYxF1M1iouZigLKi//c h1Ykatsq7fNw2Rmxobz80UrPvpegsLZYvlGQZwtodKfHOhP5JdPAQZNTnlhUNwDefvns 27akaiaW59TGV5NtZ89RnWHxdVyBPceFnVG9OObF6jkTHr/3hwwb2EZRpA5uJmHzzItt btoQ==
X-Gm-Message-State: AODbwcACtZBzhA56ovFg3fDHnsxBr0ejYgrwwFsZR9IHtCH4gknmUEMx 2KfR+RqdZO4P1IcXsPZxrcD6Y887Ig==
X-Received: by 10.237.62.115 with SMTP id m48mr7258962qtf.179.1494434243803; Wed, 10 May 2017 09:37:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.63.45 with HTTP; Wed, 10 May 2017 09:36:53 -0700 (PDT)
In-Reply-To: <CAJmz+VWBgsnFu67OFR8yiVsuzW0Tz3Y29UViZz0cmikjfjakvw@mail.gmail.com>
References: <CAJmz+VWBgsnFu67OFR8yiVsuzW0Tz3Y29UViZz0cmikjfjakvw@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 10 May 2017 09:36:53 -0700
Message-ID: <CA+9kkMDd_e91V9n1KqaASha8czqC51aN02b3_oKEtNxUeRkTdA@mail.gmail.com>
Subject: Re: Seeking help for SCIM 1.1 Implementation with Salesforce
To: "Mendes-ex, Alexandre" <alexandre.mendes-ex@solvay.com>
Cc: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a1140c9a63dfcee054f2e1649
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oBe831VT2xzw8GwSuvIN5ILgHsA>
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, 10 May 2017 16:37:29 -0000

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

Howdy,

I believed you missed the "specifications" section of the simplecloud.info
website, which shows the relevant RFCs:


   - RFC7643 - SCIM: Core Schema <https://tools.ietf.org/html/rfc7643>

   The Core Schema provides a platform-neutral schema and extension model
   for representing users and groups.
   - RFC7644 - SCIM: Protocol <https://tools.ietf.org/html/rfc7644>

   The SCIM Protocol is an application-level, REST protocol for
   provisioning and managing identity data on the web.
   - RFC7642 - SCIM: Definitions, Overview, Concepts, and Requirements
   <https://tools.ietf.org/html/rfc7642>

   This document lists the user scenarios and use cases of System for
   Cross-domain Identity Management (SCIM).

The working group which produced the specifications has concluded, but I
believe the mailing list, scim@ietf.org,  <scim@ietf.org>is still available.

regards,

Ted

On Wed, May 10, 2017 at 1:13 AM, Mendes-ex, Alexandre <
alexandre.mendes-ex@solvay.com> wrote:

> Hello,
>
> My name is Alexandre Mendes and I am currently trying to implement User
> Provisioning between 2 Salesforce orgs using the SCIM 1.1 connector.
> After encountering some difficulties I am unable to solve I am trying to
> find someone who could possibly shed some light in the situation.
>
> As the website www.simplecloud.info only indicates that SCIM is developed
> under the IEFT and unsure of which contact email would the indicated for my
> case I firstly decided to contact the general information email, which then
> indicated me this address.
> I apologize if this was not the correct address for such a situation and I
> hope you will be able to point me in the right direction.
>
> Thank you for your attention.
>
> Best Regards,
> Alexandre Mendes
>
>
>
> *This message and any attachments is intended for the named addressee(s)
> only and may contain information that is privileged and/or confidential. If
> you receive this message in error, please delete it and immediately notify
> the sender. Any copying, dissemination or disclosure, either whole or
> partial, by a person who is not the named addressee is prohibited. We use
> virus scanning software but disclaim any liability for viruses or other
> devices which remain in this message or any
> attachments.*******************************Ce message, ainsi que toute
> piece jointe, est exclusivement adresse au(x) destinataire(s) nomme(s) et
> peut contenir des informations confidentielles. Si vous recevez ce message
> par erreur, merci de le detruire et d'en avertir immediatement l'emetteur.
> Toute copie, transmission ou divulgation, integrale ou partielle, par une
> personne qui n'est pas nommee comme destinataire est interdite. Nous
> utilisons un logiciel anti-virus mais nous denions toute responsabilite au
> cas ou des virus, ou tout autre procede, seraient contenus dans ce message
> ou toute piece jointe.*

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

<div dir=3D"ltr"><div>Howdy,<br><br></div>I believed you missed the &quot;s=
pecifications&quot; section of the <a href=3D"http://simplecloud.info" targ=
et=3D"_blank">simplecloud.info</a> website, which shows the relevant RFCs:<=
br><br><ul><li>
                    <a href=3D"https://tools.ietf.org/html/rfc7643" target=
=3D"_blank">RFC7643 - SCIM: Core Schema</a>
                    <p class=3D"m_802143544723731358gmail-text">
                      The Core Schema provides a platform-neutral schema an=
d extension model for representing users and groups.
                    </p>
                  </li><li>
                    <a href=3D"https://tools.ietf.org/html/rfc7644" target=
=3D"_blank">RFC7644 - SCIM: Protocol</a>
                    <p class=3D"m_802143544723731358gmail-text">
                      The SCIM Protocol is an application-level, REST=20
protocol for provisioning and managing identity data on the web.
                    </p>
                  </li><li>
                    <a href=3D"https://tools.ietf.org/html/rfc7642" target=
=3D"_blank">RFC7642 - SCIM: Definitions, Overview, Concepts, and Requiremen=
ts</a>
                    <p class=3D"m_802143544723731358gmail-text">
                       This document lists the user scenarios and use=20
cases of System for Cross-domain Identity Management (SCIM).
                    </p>
                  </li></ul>
                <p class=3D"m_802143544723731358gmail-text">The working gro=
up which produced the specifications has concluded, but I believe the maili=
ng list, <a href=3D"mailto:scim@ietf.org" target=3D"_blank">scim@ietf.org,=
=C2=A0 </a>is still available.</p><p class=3D"m_802143544723731358gmail-tex=
t">regards,</p><p class=3D"m_802143544723731358gmail-text">Ted<br></p></div=
><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, May 10, =
2017 at 1:13 AM, Mendes-ex, Alexandre <span dir=3D"ltr">&lt;<a href=3D"mail=
to:alexandre.mendes-ex@solvay.com" target=3D"_blank">alexandre.mendes-ex@so=
lvay.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"><div dir=
=3D"ltr"><span style=3D"font-size:12.8px">Hello,</span><div style=3D"font-s=
ize:12.8px"><br></div><div style=3D"font-size:12.8px">My name is Alexandre =
Mendes and I am currently trying to implement User Provisioning between 2 S=
alesforce orgs using the SCIM 1.1 connector.=C2=A0</div><div style=3D"font-=
size:12.8px">After encountering some difficulties I am unable to solve I am=
 trying to find someone who could possibly shed some light in the situation=
.</div><div style=3D"font-size:12.8px"><br></div><div style=3D"font-size:12=
.8px">As the website=C2=A0<a href=3D"http://www.simplecloud.info/" target=
=3D"_blank">www.simplecloud.info</a>=C2=A0o<wbr>nly indicates that SCIM is =
developed under the IEFT and unsure of which contact email would the indica=
ted for my case I firstly decided to contact the general information email,=
 which then indicated me this address.</div><div style=3D"font-size:12.8px"=
>I apologize if this was not the correct address for such a situation and I=
 hope you will be able to point me in the right direction.</div><div style=
=3D"font-size:12.8px"><br></div><div style=3D"font-size:12.8px">Thank you f=
or your attention.</div><div style=3D"font-size:12.8px"><br></div><div styl=
e=3D"font-size:12.8px">Best Regards,</div><div style=3D"font-size:12.8px">A=
lexandre Mendes</div></div>

<br>
<b style=3D"font-weight:normal"><font size=3D"1" face=3D"Arial"><span style=
=3D"color:rgb(102,102,102);background-color:rgb(255,255,255);vertical-align=
:baseline;white-space:pre-wrap">This message and any attachments is intende=
d for the named addressee(s) only and may contain information that is privi=
leged and/or confidential. If you receive this message in error, please del=
ete it and immediately notify the sender. Any copying, dissemination or dis=
closure, either whole or partial, by a person who is not the named addresse=
e is prohibited. We use virus scanning software but disclaim any liability =
for viruses or other devices which remain in this message or any attachment=
s.</span><br><span style=3D"color:rgb(102,102,102);background-color:rgb(255=
,255,255);vertical-align:baseline;white-space:pre-wrap">*******************=
***********<wbr>*</span><br><span style=3D"color:rgb(102,102,102);backgroun=
d-color:rgb(255,255,255);vertical-align:baseline;white-space:pre-wrap">Ce m=
essage, ainsi que toute piece jointe, est exclusivement adresse au(x) desti=
nataire(s) nomme(s) et peut contenir des informations confidentielles. Si v=
ous recevez ce message par erreur, merci de le detruire et d&#39;en avertir=
 immediatement l&#39;emetteur. Toute copie, transmission ou divulgation, in=
tegrale ou partielle, par une personne qui n&#39;est pas nommee comme desti=
nataire est interdite. Nous utilisons un logiciel anti-virus mais nous deni=
ons toute</span><span style=3D"background-color:rgb(255,255,255);vertical-a=
lign:baseline">=C2=A0</span><span style=3D"color:rgb(102,102,102);backgroun=
d-color:rgb(255,255,255);vertical-align:baseline;white-space:pre-wrap">resp=
onsabilite au cas ou des virus, ou tout autre procede, seraient contenus da=
ns ce message ou toute piece jointe.</span></font></b></blockquote></div><b=
r></div>

--001a1140c9a63dfcee054f2e1649--


From nobody Wed May 10 09:58:33 2017
Return-Path: <johnl@iecc.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 2351E1294D8 for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 09:58:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.581
X-Spam-Level: *
X-Spam-Status: No, score=1.581 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HEADER_FROM_DIFFERENT_DOMAINS=0.001, PP_MIME_FAKE_ASCII_TEXT=0.001, RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.779, 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 i0K1BEQHAs6E for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 09:58:30 -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 EC05112945B for <ietf@ietf.org>; Wed, 10 May 2017 09:58:29 -0700 (PDT)
Received: (qmail 29843 invoked by uid 100); 10 May 2017 16:58:28 -0000
Delivered-To: reroute list-iecc-lists-ietf-ietf@johnlevine.com
Date: 10 May 2017 16:58:28 +0000
Message-ID: <oevgrk$ms6$1@gal.iecc.com>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IETF #100 Hotel Rate
Organization: Taughannock Networks, Trumansburg NY
References: <012d01d2c999$d7adda40$87098ec0$@gmail.com><012d01d2c999$d7adda40$87098ec0$@gmail.com> <51f9d3d1-6c5c-102d-d76d-ea0d35433921@gih.com>
Cleverness: some
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: johnl@aryv.qy (John L)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/g9EZIrYax3263D36lblf2m0Dfa4>
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, 10 May 2017 16:58:31 -0000

In article <51f9d3d1-6c5c-102d-d76d-ea0d35433921@gih.com>,
Olivier MJ Crépin-Leblond <ocl@gih.com> wrote:
>-=-=-=-=-=-
>Unlikely to be the Raffles hotel itself. I guess the conference is at
>the Raffles City convention centre which has 2 hotels: the Fairmont &
>the Swisshotel. Rates are lower than the super luxurious Raffles itself,
>which is just across the road.

Right, that's where ICANN met a few years ago.  The Fairmont and
Swissotel are directly connected to the conference centre.  I don't
recall what the rates were but they weren't out of line with other
Fairmont and Swissotels where we've met.

I do recommend making the trip across the road to Long's Bar in the
Raffles hotel for the original Singapore Sling.

R's,
John


From nobody Wed May 10 10:12:04 2017
Return-Path: <chair@ietf.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 017FB1294D4 for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 10:12:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.001
X-Spam-Level: 
X-Spam-Status: No, score=-1.001 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_40=-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 S28wO5CMOerw for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 10:12:02 -0700 (PDT)
Received: from [IPv6:2001:420:c0c8:1001::20d] (unknown [IPv6:2001:420:c0c8:1001::20d]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 14EC0126D85 for <ietf@ietf.org>; Wed, 10 May 2017 10:12:02 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Changes to sergeants-at-arms
Message-Id: <7BD5EE6A-5ECF-4EBE-8386-4FF631296749@ietf.org>
Date: Wed, 10 May 2017 10:12:00 -0700
To: IETF Discussion <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hT4ceKcPtGzUeq9ndKdhU9YxJNI>
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, 10 May 2017 17:12:03 -0000

RFC 3005 establishes the charter for the IETF discussion list. It =
provides for the IETF Chair to appoint sergeants-at-arms to help manage =
inappropriate or abusive postings to this list.

For many years, Jordi Palet and Ted Ts=E2=80=99o have been serving as =
sergeants-at-arms. With an eye towards giving new folks an opportunity =
to experience the role, Jordi and Ted are rotating out of this role. Ben =
Kaduk and Matt Miller have agreed to serve as new sergeants-at-arms.

Please join me in thanking Jordi and Ted for their dedicated service to =
the IETF and to keeping this list running smoothly! And please welcome =
Ben and Matt into the role.

Alissa Cooper
IETF Chair=


From nobody Wed May 10 10:56:13 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 CB35212E049 for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 10:56:12 -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, 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 SWsPLjgdXzJD for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 10:56:11 -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 0EF8E12DDD2 for <ietf@ietf.org>; Wed, 10 May 2017 10:56:10 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 9D3252009E; Wed, 10 May 2017 14:22:29 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9D72A636E0; Wed, 10 May 2017 13:56:09 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: David Farmer <farmer@umn.edu>
cc: Ted Hardie <ted.ietf@gmail.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: Registration for remote participation
In-Reply-To: <CAN-Dau1sMbQ02_Ek9+yU-XUeHK3uK7z74FGzpW8zXoZLL6-LoQ@mail.gmail.com>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <c1f0f773-4842-e413-e6df-dcbf27b94235@cs.tcd.ie> <CA+9kkMAEtMXQ0MVXWX3nTcmi1oCsMq8JcdNPJqLTU1gM2nz74Q@mail.gmail.com> <CAN-Dau1sMbQ02_Ek9+yU-XUeHK3uK7z74FGzpW8zXoZLL6-LoQ@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, 10 May 2017 13:56:09 -0400
Message-ID: <27237.1494438969@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/m-jp79ZSH4L2DqNCSJh0bzawjZA>
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, 10 May 2017 17:56:13 -0000

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


David Farmer <farmer@umn.edu> wrote:
    > Country of residence is asked for, but it sounds like you really want
    > to know where they will be viewing from, not where they live. For some
    > set of use cases they will be aligned, but others they won't.

I think we want country of resident to understand if the travel costs were a
factor.   I think we also want to know their country of citizenship, because
passport/visa issues are also relevant.
I also think we want an IPv4 and IPv6 AS traceroute to their host at the
time of registration.  We also need a log of how many sessions they got to.
In some cases people will register, and then either not attend any sessions
for some reason, or fail to actually connect.

We need to survey people afterwards, and asking the country/visa/etc. issues
afterwards would be better, as would capturing output from something like
ipv6-test.com.

    > There is another important use case, similar to "be in two rooms at
    > once", that is a temporary need to leave the meeting site, such as to
    > receive medical treatment for chronic conditions or simply just other
    > business in the meeting city. As someone who has recently began

I connected to the 11am Friday CORE meeting from the airport departure
lounge at IETF98.  I just couldn't stay longer on Friday and still return in
time for my wife's birthday.  (She has celebrated at least five birthdays
*AT* IETF...)

    > needing treatment while traveling. You frequently have little choice
    > over when a treatment slot is made available to you, usually you have
    > to take what they can give you. Good remote participation options,
    > make this less burdensome.

Good point.
It also might be good if meetecho let us join two meetings at the same time.
(It actually works to open two tabs, although the audio is hard for the brain
to demux...)

--
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+93Q3WUFAlkTVDkACgkQgItw+93Q
3WVf1wf+PSmoCWK/nkZpi5kT2LpJywkvQjPdiqYopFWqcokVZOGFlQoqlTs5D4Hq
5AFqV9fNoYr+qhv83zuRVuA5AEY0uIxPI6ReXj5+Vxd2nxl3WpG6SNVGhaZCrQ0r
DIjBVvPcmx61+wsT/Qi7KYMo76h3r1TcLJq0EwhTHf5ayypB3Iy/fkTgoXGNOg/w
n/cnSfw6tUb7JifK/tHkjaDbxyJgM7KZHpjeWsPWFjB/Id62eW1cpfsA6OX9VJdo
Kpvpj1RAPuPgDVYuTJZkXn6f9g/x1kW0WVFknrwCt6qBMvOu0b7dSqi7KCDAk/41
ctjGbFsK0W1wwADSEJRStl/o1BGE/g==
=NTNd
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed May 10 11:04:16 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 F2C7B129BAC for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 11:04:14 -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, 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 xtEnaNP3ajz2 for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 11:04:13 -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 6B3DD129473 for <ietf@ietf.org>; Wed, 10 May 2017 11:04:13 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id A0D552009E for <ietf@ietf.org>; Wed, 10 May 2017 14:30:32 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 95C54636E0 for <ietf@ietf.org>; Wed, 10 May 2017 14:04:12 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: Registration for remote participation
In-Reply-To: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
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, 10 May 2017 14:04:12 -0400
Message-ID: <29052.1494439452@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gdUZstKozBxgPgjzVnUZTuQ8wk8>
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, 10 May 2017 18:04:15 -0000

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


IETF Chair <chair@ietf.org> wrote:
    > Title
    > First / Given Name*
    > Last / Family Name*
    > Company / Organization
    > ISO 3166 Country of Residence*
    > Email*
    > Gender
    > Have you attended an IETF meeting in person before?
    > Have you attended an IETF meeting remotely before?

    > Upon registering, participants would be issued a registration ID, just
    > as they are today.

Are we validating the email address in some way?
If we are not, I don't see the point of the *-required in any of those places.

    > Remote participation registration data would be stored and secured by
    > AMS and MeetEcho just as it is currently today. As is the case now, no
    > registration or login would be required to access MeetEcho recordings,
    > audio recordings, YouTube videos, or jabber rooms. And no changes are
    > being proposed as to the handling of virtual blue sheets.

I suggest:
  1) Add me to the attendeeXX list.

  2) I think we have another list which is more announce and less discuss,
     but I can't recall it, they should be added to it as well.

  3) It would be nice if they they could be asked at registration time which
     WG they will attend (no commitment!), and if this information could be
     relayed to WG chairs.

  4) ask them if we can collect anonymized performance data and
     site/path/latency/jitter information.

I would also love it the meetecho tool could optionally capture
ipv6-test.com-like information during the session.  Maybe the webrtc people
could also tell us how to capture what kind of RTP sessions were required to
be created.  In the after-survey, we need to ask them if they had to do
anything special to participate. For instance:
       a) did they go into the "office" in order to have enough bandwidth?
       b) did they stay *away* from office in order to avoid restrictive firewalls?

Finally, to echo Klensin, I think that we should retain the ability to lurk
anonymously.

--
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+93Q3WUFAlkTVhwACgkQgItw+93Q
3WVOSgf/dsGkyah0K7hvgk6QqG/Wn8QhWfSQRJiejhuKPydc3weKnQAui4LeNpab
hKdS12ZJaBamfZ+Np3zeXCr3WxSBLS/BKuq9M8obaq6OaVg7rvZePt7TJcynS/wU
sZH9W19SHLK7ooPuT1QX9EKNwV4lpShU9kGKyKon/R6YW9vfCOsW3zY9+y3hxRAo
rQY1F8wIUxpuEI0OfEJj4m1tlRz6HkLGyUJbQdctTySWr1evJh78myf3sTUsGqws
UJWbZ33IYfGlizdanvN7oP0KoBO0dCeR5AbB9Fjicr42kfOqN0iXLEbrsgbyycmW
SKRnrXsmlHbfFPXacxXs2g2bbW2DPA==
=ukhg
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed May 10 11:32:08 2017
Return-Path: <vijay.gurbani@nokia.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 A250312E858; Wed, 10 May 2017 11:31:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Vijay Gurbani <vijay.gurbani@nokia.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-avtcore-rfc5285-bis.all@ietf.org, ietf@ietf.org, avt@ietf.org
Subject: Genart last call review of draft-ietf-avtcore-rfc5285-bis-11
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149444109463.16649.17140517108290058073@ietfa.amsl.com>
Date: Wed, 10 May 2017 11:31:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aCiARnfnflyZKav1S8baHjDeu3M>
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, 10 May 2017 18:31:35 -0000

Reviewer: Vijay Gurbani
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-avtcore-rfc5285-bis-11
Reviewer: Vijay Gurbani
Review Date: 2017-05-10
IETF LC End Date: 2017-04-20
IESG Telechat date: Not scheduled for a telechat

Summary: Ready with nits.

Major issues: 0

Minor issues: 0

Nits/editorial comments: 
- S5: s/An example (this is only an example), where/An example where/
  (I suspect that the reader will get the idea that this is only an
   example.  There are a couple of occurrence of this in S5.)

- S6: s/When doing SDP Offer/When engaging in SDP Offer/

Thanks!



From nobody Wed May 10 12:47:26 2017
Return-Path: <stewe@stewe.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 887BA12EA94 for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 12:47:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.701
X-Spam-Level: 
X-Spam-Status: No, score=-4.701 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_H2=-2.8, SPF_HELO_PASS=-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=steweorg.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 kdzCnsQsb9zz for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 12:47:22 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0104.outbound.protection.outlook.com [104.47.36.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD40E128AB0 for <ietf@ietf.org>; Wed, 10 May 2017 12:47:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=steweorg.onmicrosoft.com; s=selector1-stewe-org; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=tDzGdqDGBmzq37Fr4cZqWR30wf37nWgV4wbdjdFiQJM=; b=cCXhiiqauSH21bP6bt3k1u5nLtjiJau4M3H/OBQ0WSOo1GIc1TshXhO6i+Iq40+81fphvvdozN7SmDNUejVCdYjhV8M1CERmytSnY/PEAWQEHUQHnnbAOJgZNILqdEEo1k4gYDo8NyXbrzasqFbayW45tJzagITFgLXN+tXw9II=
Received: from CY1PR17MB0693.namprd17.prod.outlook.com (10.164.217.5) by CY1PR17MB0696.namprd17.prod.outlook.com (10.164.217.8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1084.16; Wed, 10 May 2017 19:47:20 +0000
Received: from CY1PR17MB0693.namprd17.prod.outlook.com ([10.164.217.5]) by CY1PR17MB0693.namprd17.prod.outlook.com ([10.164.217.5]) with mapi id 15.01.1084.017; Wed, 10 May 2017 19:47:20 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion <ietf@ietf.org>
Subject: Re: Registration for remote participation
Thread-Topic: Registration for remote participation
Thread-Index: AQHSyPa0kEKm1WpyAUugVHquNJkgB6Ht3boA//+nd4A=
Date: Wed, 10 May 2017 19:47:20 +0000
Message-ID: <F4BF8089-0E62-4B3D-AE97-1F5ACC4196BC@stewe.org>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <29052.1494439452@obiwan.sandelman.ca>
In-Reply-To: <29052.1494439452@obiwan.sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: sandelman.ca; dkim=none (message not signed) header.d=none;sandelman.ca; dmarc=none action=none header.from=stewe.org;
x-originating-ip: [50.174.30.183]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY1PR17MB0696; 7:FP8C7Sp60aS6KSWjngr3ChiZwKtcV7Gk/4BvhyCjofI3Oo/IgSjUFkqJCyCUo8mFryh9ZpCPAVjI4XY7+pqkePG7DTKHVpC219JZGjN17Lsam56BtkK9fAezr+eM9JFkT3+WJ5HCb73YI4Xmr/BltQIvROvMmEQyE8c6sKYIu+6YMHsugM2jtmD0jNKlZCxusc5lnZb8rsz9BlEyq/RVvTHNBVCi/mDTvPaUYpt4LAwxkXOSmRUr2cuJx/4D28UF00z0zuYGz9Gpz/HSMYzkcw1og4XioxdRILZw0oQd9BfN/02r++vGWDDGjh6YuZCdx0Ao/JgQGFnD/5+TOsqP7Q==
x-ms-office365-filtering-correlation-id: 5b0d7f15-11c2-4bec-0fec-08d497dd5f10
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075); SRVR:CY1PR17MB0696; 
x-microsoft-antispam-prvs: <CY1PR17MB0696BD470A14DCA06AA53CE1AEEC0@CY1PR17MB0696.namprd17.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(6041248)(20161123558100)(20161123560025)(2016111802025)(201703131423075)(201703061421075)(20161123555025)(20161123564025)(20161123562025)(6043046)(6072148); SRVR:CY1PR17MB0696; BCL:0; PCL:0; RULEID:; SRVR:CY1PR17MB0696; 
x-forefront-prvs: 03030B9493
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39450400003)(39400400002)(24454002)(508600001)(305945005)(8936002)(7736002)(5660300001)(3480700004)(3280700002)(53936002)(122556002)(83716003)(82746002)(8676002)(3660700001)(6436002)(81166006)(6486002)(77096006)(6512007)(6506006)(99286003)(229853002)(38730400002)(25786009)(36756003)(2900100001)(2906002)(86362001)(3846002)(33656002)(102836003)(2950100002)(6116002)(66066001)(50986999)(54356999)(76176999)(189998001)(53546009)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR17MB0696; H:CY1PR17MB0693.namprd17.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <E93098AC59ADCA45866343393A736022@namprd17.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 May 2017 19:47:20.3287 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 865fc51c-5fae-4322-98ef-0121a85df0b6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR17MB0696
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z-rJjjNIqp5zqYxKtVBDf-hPRns>
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, 10 May 2017 19:47:25 -0000

SGksDQpUd28gSVBSLW1vdGl2YXRlZCB0aGluZ3MgaW5saW5lOg0KDQoNCg0KT24gNS8xMC8xNywg
MTE6MDQsICJpZXRmIG9uIGJlaGFsZiBvZiBNaWNoYWVsIFJpY2hhcmRzb24iIDxpZXRmLWJvdW5j
ZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIG1jcitpZXRmQHNhbmRlbG1hbi5jYT4gd3JvdGU6DQoN
Cj4NCj5JRVRGIENoYWlyIDxjaGFpckBpZXRmLm9yZz4gd3JvdGU6DQo+ICAgID4gVGl0bGUNCj4g
ICAgPiBGaXJzdCAvIEdpdmVuIE5hbWUqDQo+ICAgID4gTGFzdCAvIEZhbWlseSBOYW1lKg0KPiAg
ICA+IENvbXBhbnkgLyBPcmdhbml6YXRpb24NCj4gICAgPiBJU08gMzE2NiBDb3VudHJ5IG9mIFJl
c2lkZW5jZSoNCj4gICAgPiBFbWFpbCoNCj4gICAgPiBHZW5kZXINCj4gICAgPiBIYXZlIHlvdSBh
dHRlbmRlZCBhbiBJRVRGIG1lZXRpbmcgaW4gcGVyc29uIGJlZm9yZT8NCj4gICAgPiBIYXZlIHlv
dSBhdHRlbmRlZCBhbiBJRVRGIG1lZXRpbmcgcmVtb3RlbHkgYmVmb3JlPw0KPg0KPiAgICA+IFVw
b24gcmVnaXN0ZXJpbmcsIHBhcnRpY2lwYW50cyB3b3VsZCBiZSBpc3N1ZWQgYSByZWdpc3RyYXRp
b24gSUQsIGp1c3QNCj4gICAgPiBhcyB0aGV5IGFyZSB0b2RheS4NCj4NCj5BcmUgd2UgdmFsaWRh
dGluZyB0aGUgZW1haWwgYWRkcmVzcyBpbiBzb21lIHdheT8NCj5JZiB3ZSBhcmUgbm90LCBJIGRv
bid0IHNlZSB0aGUgcG9pbnQgb2YgdGhlICotcmVxdWlyZWQgaW4gYW55IG9mIHRob3NlIHBsYWNl
cy4NCg0KDQpJ4oCZbSBpbiBmYXZvciBvZiB2YWxpZGF0aW5nIHRoZSBhZGRyZXNzLCBmb3IgZXhh
bXBsZSBieSBzZW5kaW5nIHNvbWUgZm9ybSBvZiBjcmVkZW50aWFsIHRvIGl0OyB3aXRob3V0IHRo
ZSBjcmVkZW50aWFsLCBvbmx5IGxpc3RlbmluZy9yZWFkaW5nIGFjY2VzcyBpcyBncmFudGVkLiAg
RG9lc27igJl0IGhhdmUgdG8gYmUgYnVsbGV0LXByb29mLCBidXQgdXNpbmcgZXhhbXBsZUBleGFt
cGxlLmNvbSBzaG91bGRu4oCZdCB3b3JrLiAgVGhpcyBpcyBvYnZpb3VzbHkgaW4gb3JkZXIgdG8g
b2J0YWluIG9uZSBzZW1pLXRyYWNlYWJsZSByZWNvcmQgb2YgdGhlIHBhcnRpY2lwYW50Lg0KPg0K
PiAgICA+IFJlbW90ZSBwYXJ0aWNpcGF0aW9uIHJlZ2lzdHJhdGlvbiBkYXRhIHdvdWxkIGJlIHN0
b3JlZCBhbmQgc2VjdXJlZCBieQ0KPiAgICA+IEFNUyBhbmQgTWVldEVjaG8ganVzdCBhcyBpdCBp
cyBjdXJyZW50bHkgdG9kYXkuIEFzIGlzIHRoZSBjYXNlIG5vdywgbm8NCj4gICAgPiByZWdpc3Ry
YXRpb24gb3IgbG9naW4gd291bGQgYmUgcmVxdWlyZWQgdG8gYWNjZXNzIE1lZXRFY2hvIHJlY29y
ZGluZ3MsDQo+ICAgID4gYXVkaW8gcmVjb3JkaW5ncywgWW91VHViZSB2aWRlb3MsIG9yIGphYmJl
ciByb29tcy4gQW5kIG5vIGNoYW5nZXMgYXJlDQo+ICAgID4gYmVpbmcgcHJvcG9zZWQgYXMgdG8g
dGhlIGhhbmRsaW5nIG9mIHZpcnR1YWwgYmx1ZSBzaGVldHMuDQo+DQo+SSBzdWdnZXN0Og0KPiAg
MSkgQWRkIG1lIHRvIHRoZSBhdHRlbmRlZVhYIGxpc3QuDQo+DQo+ICAyKSBJIHRoaW5rIHdlIGhh
dmUgYW5vdGhlciBsaXN0IHdoaWNoIGlzIG1vcmUgYW5ub3VuY2UgYW5kIGxlc3MgZGlzY3VzcywN
Cj4gICAgIGJ1dCBJIGNhbid0IHJlY2FsbCBpdCwgdGhleSBzaG91bGQgYmUgYWRkZWQgdG8gaXQg
YXMgd2VsbC4NCj4NCj4gIDMpIEl0IHdvdWxkIGJlIG5pY2UgaWYgdGhleSB0aGV5IGNvdWxkIGJl
IGFza2VkIGF0IHJlZ2lzdHJhdGlvbiB0aW1lIHdoaWNoDQo+ICAgICBXRyB0aGV5IHdpbGwgYXR0
ZW5kIChubyBjb21taXRtZW50ISksIGFuZCBpZiB0aGlzIGluZm9ybWF0aW9uIGNvdWxkIGJlDQo+
ICAgICByZWxheWVkIHRvIFdHIGNoYWlycy4NCj4NCj4gIDQpIGFzayB0aGVtIGlmIHdlIGNhbiBj
b2xsZWN0IGFub255bWl6ZWQgcGVyZm9ybWFuY2UgZGF0YSBhbmQNCj4gICAgIHNpdGUvcGF0aC9s
YXRlbmN5L2ppdHRlciBpbmZvcm1hdGlvbi4NCg0KQW5kIDUpIGNsaWNrLXRocm91Z2ggb2YgdGhl
IE5vdGUgV2VsbCAodW5sZXNzIHRoYXTigJlzIGRvbmUgaW4gc29tZSBvdGhlciBwaGFzZSBvZiB0
aGUgcmVtb3RlIHBhcnRpY2lwYXRpb24sIGxpa2Ugd2hlbiBzaWduaW5nLWluIHRvIG1lZXRlY2hv
KS4gIEFnYWluIGZvci0tSSBob3BlIG9idmlvdXMtLUlQUiByZWxhdGVkIHJlYXNvbnMuDQoNClN0
ZXBoYW4NCg0KWy4uLl0NCj4NCj4NCj4NCj4NCg==


From nobody Wed May 10 13:21:57 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 676D512EAAC for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 13:21:56 -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, RP_MATCHES_RCVD=-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 Ivj2GH1G0xtI for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 13:21:54 -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 45A1212EAA7 for <ietf@ietf.org>; Wed, 10 May 2017 13:21:54 -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 1d8Y7M-000OMp-S3; Wed, 10 May 2017 16:21:52 -0400
Date: Wed, 10 May 2017 16:21:46 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion <ietf@ietf.org>
Subject: Re: Registration for remote participation
Message-ID: <B2B236B5CDB82EFDBED9923E@PSB>
In-Reply-To: <29052.1494439452@obiwan.sandelman.ca>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <29052.1494439452@obiwan.sandelman.ca>
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/BLZ-IfIWKuB4vpqbz8Bi9yme6Ho>
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, 10 May 2017 20:21:56 -0000

--On Wednesday, May 10, 2017 14:04 -0400 Michael Richardson
<mcr+ietf@sandelman.ca> wrote:

>...
> Are we validating the email address in some way?
> If we are not, I don't see the point of the *-required in any
> of those places.
>...

Michael (and others),

I'm happy to let the IESG manage this rather than getting into
an orgy of nit-picking and micro-managing, but I think there are
at least two separate reasons for wanting remote participants to
register and that, which the desired information may overlap,
confusing the two is probably not helpful.  The two are:

(1) For reasons related to IPR policy and issues (including the
"Note Well", but remember it is a summary of policies and
pointer to them, not the policies themselves) and in case
questions arise as to who or what is influencing IETF decisions,
we just need to know who is making Contributions and
influencing, or trying to influence, the IETF.  For that
purpose, I believe the information we should be collecting from
remote participants and the mechanisms used to validate that
information should be as nearly identical to the information
obtained from registrants for on-site attendance.  

As I've said earlier, I prefer that we make at least a nominal
charge as part of the verification process.  I also prefer that
we encourage registration in advance of the meeting, possibly
even providing a reduced fee for advanced registration (as we do
for conventional registrations).  I also believe that this is
"one person, one registration" and that separate registrations
for use of the in-person facilities (presumably including access
to cookies) and remote ones are neither desirable nor
appropriate.

Especially if remote registrations are going to continue to be
free and the forms offered when one first tries to access
Meetecho as a participant during a given meeting, the number of
questions asked should be kept to a minimum to avoid forcing
would-be participants in a session to spend any more time than
absolutely necessary filling out forms rather than contribution.

(2) Almost independent of the above, there are lots of reasons
to try to obtain demographic or opinion information from remote
participants.  Information of that type might help to inform
decisions about meeting locations, reasons why people are
participating remotely rather than attending meetings in person,
etc.  If we are not concerned about poll-stuffing, that
information might reasonably be collected anonymously.
Certainly the incentives for being able to identify and
authenticate a participant are different from those above.  It
can also be collected rather more at leisure, including using
post-meeting surveys similar to the used for registrants in the
past.

Again, I'm happy to let the IESG (assisted by staff and the IAOC
as they deem appropriate) sort out the details, but several
recent comments imply that some of the reasons for registering
remote participants are getting confused.

Finally, apologies for singing this song again, but, if we are
going to encourage remote participation hubs in which people
come together at a remote location to participate in (and
contribute to) an IETF meeting going on at the same time, we'd
best be really sure that registration and identification rules
for such participants are clear, consistent, and integrated with
whatever tools are relevant.

best,
   john



From nobody Wed May 10 14:28:10 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 DD2C012EAD7 for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 14:28:08 -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 zIplQoXtUnTu for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 14:28:07 -0700 (PDT)
Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5076512EAD5 for <ietf@ietf.org>; Wed, 10 May 2017 14:28:07 -0700 (PDT)
Received: by mail-wm0-x242.google.com with SMTP id v4so2643848wmb.2 for <ietf@ietf.org>; Wed, 10 May 2017 14:28:07 -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=4Eeg7s8t6bOGFqKfaUfaDqOtCHXuRr6i/zqbY+Ps8ho=; b=cUFEyp5M8GU0vVB+aw9i12iDjS1f015KjDTjzV3SpLs8xsGqjnntycMADCXf8BMbX3 5OLo/+HaAv27sQxghWEssa7ygqq0hd2To9StO6gBMP429iXw904nmo+RKipaU8ldewN3 4kSBD/0Cbx0WmUGnMHGLUhEJtLDWCR14Z9vlJoYdLH/7njqE80XotiXeziHmVhTLYElD +MIKc1PfQgwAUuooJgxGF4LzOLPQvFUKHNt9haKyPhJaOrlKJuvne3PO9Id+1SViJc8I ZeSOjLxrX/shi3gkcLZkaUI2OxBQDgmBaDPQ07eqbLMFeZyhHJSIqR6Jz5v/6goD8if0 57hg==
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=4Eeg7s8t6bOGFqKfaUfaDqOtCHXuRr6i/zqbY+Ps8ho=; b=ovxYFZY6aC6I0U6nnY+kBuO/5WZgjy48aCEylMoHS0q/robPtDSMFN6PDDJQYQ/GVi 6y+NBsCHlYyshmTmbu5RoZ2azHoz2rVeLl64zoFrXTDacWFIfEcH0F+Mn2xlnVLZ49++ Z9uHhLDElbGcpGnA4RVaTLxNoydFL6r/cJSD0Ms232A/Zn2HliqSOdgtEgi1I8BmxCDY j+XH56MGAdGFLChUtCpT2NCkSyNKl49W0DDTGKWsYyXI5rUmKWePrFDsx/SR4lQemCG9 w2XJrX3fq1OGK6S8WoxF9N99Fvgxh8Jy2dV2Uen87DLG7flPMKtVe7qjp85359NaqpRr gB6A==
X-Gm-Message-State: AODbwcCLzJkJQNxLbLNfDSo7bUAJX18BydMs6ctCGagrOmtrZWPJMPbj IKoBabh5P6FEnw==
X-Received: by 10.80.176.198 with SMTP id j64mr5664149edd.168.1494451685898; Wed, 10 May 2017 14:28:05 -0700 (PDT)
Received: from [192.168.1.18] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id m9sm52782edm.62.2017.05.10.14.28.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 May 2017 14:28:05 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <63BCEF0D-E6FC-4E10-A4B2-3E4CC122B9A6@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_625DA43C-FF90-4D9A-87B1-AA997F10527B"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Registration for remote participation
Date: Thu, 11 May 2017 00:28:02 +0300
In-Reply-To: <7D148F612B0A8241B214B9D7@PSB>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
To: John C Klensin <john-ietf@jck.com>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <82C753BB-C89C-4039-8A08-0615067777C0@gmail.com> <7D148F612B0A8241B214B9D7@PSB>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nFxZ4NJYOMRBzmPBDN6dnJA-p5Y>
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, 10 May 2017 21:28:09 -0000

--Apple-Mail=_625DA43C-FF90-4D9A-87B1-AA997F10527B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 10 May 2017, at 15:50, John C Klensin <john-ietf@jck.com> wrote:
>=20
> I favor at least a nominal registration fee for the same reason
> -- not because I see it as an important revenue source (a rather
> different discussion0 but because it helps eliminate Donald Duck
> registrations.

How does a fee eliminate Donald Duck registrations?  There=E2=80=99s =
nothing preventing me from registering *now* for the Prague physical =
meeting as Donald Duck as long as my $700 are good.

Yoav


--Apple-Mail=_625DA43C-FF90-4D9A-87B1-AA997F10527B
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-----

iQEcBAEBCgAGBQJZE4XjAAoJELhJCxUKWMyZ0H0IALp8q3QnevC5MrZ33GRZKfRL
jPLQbqvBy07hXl5AJ8IM8mnIQhcAqpwim7OtaxoMajSC5kDCboF0cUu4pc4Rn4+H
wqQg7q4vb3rPgM0LRIJfUPhkUusjbmki5Ng5Ehc9kxkrOWTLTi9OSSWKUgsdDOSi
OmUYDFANlvUjgq00QeOSiTYaFG9o9r4eQaJ57HfFt1IQyFKPJIM4DkgQE863aVvX
lJsAJa1L2mi/OIGCcoAhiOFNfIJx1Om0Lvq4F9ZttLn649DxxxREb8MaWEl0CqmM
cyV71TNs5v1xgfDu5QigGczh+ndpUHRzfz5EcmNC3nfMCQqLzYjFwXOSE8XnIsI=
=6nfr
-----END PGP SIGNATURE-----

--Apple-Mail=_625DA43C-FF90-4D9A-87B1-AA997F10527B--


From nobody Wed May 10 17:46:59 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 DAAA312EA56 for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 17:46:57 -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_40=-0.001, RP_MATCHES_RCVD=-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 XF57heDPAfMt for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 17:46:56 -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 AA929129687 for <ietf@ietf.org>; Wed, 10 May 2017 17:46:56 -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 1d8cFr-000Oop-0z; Wed, 10 May 2017 20:46:55 -0400
Date: Wed, 10 May 2017 20:46:48 -0400
From: John C Klensin <john-ietf@jck.com>
To: Yoav Nir <ynir.ietf@gmail.com>
cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
Subject: Re: Registration for remote participation
Message-ID: <F02ABABE3D62B99B29AB9A9C@PSB>
In-Reply-To: <63BCEF0D-E6FC-4E10-A4B2-3E4CC122B9A6@gmail.com>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <82C753BB-C89C-4039-8A08-0615067777C0@gmail.com> <7D148F612B0A8241B214B9D7@PSB> <63BCEF0D-E6FC-4E10-A4B2-3E4CC122B9A6@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/Rgeg8QwN7qMnpZW761JDpSu9Kug>
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, 11 May 2017 00:46:58 -0000

--On Thursday, May 11, 2017 00:28 +0300 Yoav Nir
<ynir.ietf@gmail.com> wrote:

>> On 10 May 2017, at 15:50, John C Klensin <john-ietf@jck.com>
>> wrote:
>> 
>> I favor at least a nominal registration fee for the same
>> reason -- not because I see it as an important revenue source
>> (a rather different discussion0 but because it helps
>> eliminate Donald Duck registrations.
> 
> How does a fee eliminate Donald Duck registrations?  There's
> nothing preventing me from registering *now* for the Prague
> physical meeting as Donald Duck as long as my $700 are good.

Unless things have changed since I was paying active attention,
most registrations, especially those in advance of a meeting,
are paid with credit cards.   If you can get a credit card in
the name of M. Duck, more power to you, but I suggest the effort
required to do that would at least mostly separate those who
have read reasons to want to participate under aliases from
those who were merely being difficult on principle or who were
suffering from an excess of self-indulgent cuteness.

A different way to say the same thing is that, especially with
remote participants, a requirement for strong authentication of
all participants is probably impossible or nearly so.  That
doesn't mean we should avoid making a reasonable best effort and
I believe that requiring some registration payment, even a small
one, is both a useful part of such an effort and a way of
encouraging a modicum of additional seriousness.

YMMD.
    john




From nobody Wed May 10 18:15:18 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 560ED129508; Wed, 10 May 2017 18:15:16 -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: draft-ietf-pals-p2mp-pw.all@ietf.org, ietf@ietf.org, pals@ietf.org
Subject: Rtgdir last call review of draft-ietf-pals-p2mp-pw-02
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149446531632.16715.2861233468294466753@ietfa.amsl.com>
Date: Wed, 10 May 2017 18:15:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nU3FDPgSiIhQ5kJZqZhBXLvrZlk>
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, 11 May 2017 01:15:16 -0000

Reviewer: Patrice Brissette
Review result: Has Issues

[Resending to RTG-DIR]

Hello, 
I have been selected as the Routing Directorate reviewer for this
draft. The Routing Directorate seeks to review all routing or
routing-related drafts as they pass through IETF last call and IESG
review, and sometimes on special request. The purpose of the review is
to provide assistance to the Routing ADs. For more information about
the Routing Directorate, please see
http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir 
Although these comments are primarily for the use of the Routing ADs,
it would be helpful if you could consider them along with any other
IETF Last Call comments that you receive, and strive to resolve them
through discussion or by updating the draft. 
 
Document: draft-ietf-pals-p2mp-pw-02.txt
Reviewer: Patrice Brissette
Review Date: May 10, 2017
IETF LC End Date: May 12, 2017
Intended Status: Standard Track 
Summary: 
•	I have some minor concerns about this document that I think should
be resolved before publication. 
 
Comments: 
•	Please supply an overview of the draft quality and readability. 
•	Include anything else that you think will be helpful toward
understanding your review. 
Major Issues: 
•	"No major issues found." 
Minor Issues:
•	Technically, I think the draft is completed. However, it doesn’t
flow very well. Information is all over. I suggest the authors to
review the layout/flow of the document. 
 
Here are my “detailed” comments:
 
Abstract — What is the plus value on that draft? No clear
 
Many Long sentences in the text. very hard to understand and follow.
Syntax to be improved.
 
Introduction
Typo : “A reference model or a P2MP PW is depicted in Figure 1 below”
 
“In this document, we specify a method of signaling P2MP
   PW using LDP.” —> suggest to move it from intro to abstract 
 
Also, make sure the 3rd person is used. Try to a void “we” usage
 
May I suggest to have a requirement section. Requirements are all over
the document.
 
“   In case of mLDP, a Leaf-PE can decide to join the P2MP LSP at any
   time; whereas in the case of RSVP-TE, the P2MP LSP is set up by
the
   R-PE, generally at the initial service provisioning time. It
should
   be noted that local policy can override any decision to join, add
or
   prune existing or new L-PE(s) from the tree. In any case, the PW
   setup can ignore these differences, and simply assume that the
P2MP
   PSN LSP is available when needed
“
Quite complex to follow. Missing to “why” / explanation.
 
“The LDP liberal label retention mode is used“
Another requirement… is that a MAY, SHOULD, MUST?
 
“In this case, a PW status message with status
   code of 0x00000008 (Local PSN-facing PW (ingress) Receive Fault)
MUST
   also be sent to the R-PE“ 
How? The L-PE fails to join the P2MP PSN LSP.
 
Section 2.2
“   Note that since the LDP label mapping message is only sent by the
R-
   PE to all the L-PEs, it is not possible to negotiate any interface
   parameters.“
Why is that note there? Is that already been mentioned previously.
Fig.4 must  be moved to proper in the text OR create 2 subsection in
2.2
 
“As such, PW status negotiation procedure
   described in [RFC4447bis] is not applicable to P2MP PW. A node
MUST
   NOT claim to be  P2MP PW capable by sending a LDP P2MP PW
Capability
   TLV  if it is not also capable of handling PW status“
 
Should a node send LDP P2MP PW Capability TLV or not? Not well explain

 
There is some reference to LSR in the text where the major part use
the wording “node”.
 
Nits: 
N/A
 
Regards,
Patrice Brissette





From nobody Wed May 10 21:03:11 2017
Return-Path: <johnl@iecc.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 63676127ABE for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 21:03:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.58
X-Spam-Level: *
X-Spam-Status: No, score=1.58 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HEADER_FROM_DIFFERENT_DOMAINS=0.001, PP_MIME_FAKE_ASCII_TEXT=0.001, RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.779] 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 iUq62_K4TrJ2 for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 21:03:07 -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 3AE56129564 for <ietf@ietf.org>; Wed, 10 May 2017 21:03:06 -0700 (PDT)
Received: (qmail 21174 invoked by uid 100); 11 May 2017 04:03:04 -0000
Delivered-To: reroute list-iecc-lists-ietf-ietf@johnlevine.com
Date: 11 May 2017 04:03:04 +0000
Message-ID: <of0npo$1q03$1@gal.iecc.com>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Registration for remote participation
Organization: Taughannock Networks, Trumansburg NY
References: <7D148F612B0A8241B214B9D7@PSB><82C753BB-C89C-4039-8A08-0615067777C0@gmail.com> <7D148F612B0A8241B214B9D7@PSB> <63BCEF0D-E6FC-4E10-A4B2-3E4CC122B9A6@gmail.com>
Cleverness: some
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: johnl@aryv.qy (John L)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5XztY7-V_K88Sh6YNvffa9gQiNc>
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, 11 May 2017 04:03:08 -0000

In article <63BCEF0D-E6FC-4E10-A4B2-3E4CC122B9A6@gmail.com>,
Yoav Nir  <ynir.ietf@gmail.com> wrote:
>How does a fee eliminate Donald Duck registrations?  There’s nothing preventing me from registering *now* for
>the Prague physical meeting as Donald Duck as long as my $700 are good.

I believe that the assumption is that few people are likely to waste
$700 each on multiple fake registrations.

Also, if the identity of the person becomes an issue, the credit card
used to pay is an excellent key to use.

R's,
John



 


From nobody Wed May 10 22:19:32 2017
Return-Path: <swmike@swm.pp.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 DD99112EB5F for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 22:19:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.403
X-Spam-Level: 
X-Spam-Status: No, score=-2.403 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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=swm.pp.se
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ETb2GSK8Bfqp for <ietf@ietfa.amsl.com>; Wed, 10 May 2017 22:19:18 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (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 E2ECC128BC8 for <ietf@ietf.org>; Wed, 10 May 2017 22:19:17 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 943E0A3; Thu, 11 May 2017 07:19:14 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1494479954; bh=x0KeOk/wFGmznhUtR6emBG91laokiF00gMEm334y+cA=; h=Date:From:To:Subject:In-Reply-To:References:From; b=AovFiYdRMQW7JP9vvTHCuEZJYIvckI8JueNkoAqhs27FCPnruGvJMjSVuZMulO6aW +81b5yhp8BHi1jjH8aS1bwwkS23D4XVhI/RD3j+7PTzKE/C4GyadUmmEe/SpDx13Eu p2fge7IFGEHgoVXMwYXVQ8mZzfMQpsVw2Qy12cs4=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 7B876A2 for <ietf@ietf.org>; Thu, 11 May 2017 07:19:14 +0200 (CEST)
Date: Thu, 11 May 2017 07:19:14 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: Registration for remote participation
In-Reply-To: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
Message-ID: <alpine.DEB.2.02.1705110714230.30304@uplift.swm.pp.se>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ldDJRGth5S53LD1w9vu_EE3dSQI>
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, 11 May 2017 05:19:20 -0000

On Tue, 9 May 2017, IETF Chair wrote:

> only difference from how login works today is that the option to "Join 
> without registration ID" would be removed. Other options for

The few times I have tried to use my registration ID to join a session, I 
failed to get it working, and I had to revert to use the clickbox to join 
without registration ID. So if remote participation is going to require 
this ID, this needs to be "bulletproof". The "remember me" button also 
needs to work across the entire week, preferrably so I don't even have to 
put in the registration ID more than once for the entire week (cookies 
etc).

Perhaps we could have one IETF where there is encouragement for everybody 
to test this functionality and make sure all cases of it not working is 
reported to the NOC and fault found? So basically a "dress rehearsal".

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Wed May 10 23:29:36 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 79F26128CD5; Wed, 10 May 2017 23:29:20 -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: mpls@ietf.org, draft-ietf-mpls-tp-aps-updates.all@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-ietf-mpls-tp-aps-updates-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149448416047.16649.7655814250953782130@ietfa.amsl.com>
Date: Wed, 10 May 2017 23:29:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9UCFXe-PvZFElDWUayPRZmFSWmc>
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, 11 May 2017 06:29:21 -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 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-mpls-tp-aps-updates-??
Reviewer: Roni Even
Review Date: 2017-05-10
IETF LC End Date: 2017-05-19
IESG Telechat date: 2017-05-25

Summary:

The document is ready for publication as a standard track RFC

Major issues:

Minor issues:

Nits/editorial comments: 



From nobody Wed May 10 23:36:13 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 6D12C12EB6B; Wed, 10 May 2017 23:36:11 -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 MgA26NVqvZar; Wed, 10 May 2017 23:36:09 -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 E3EF11294C9; Wed, 10 May 2017 23:36:08 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml702-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DGJ67418; Thu, 11 May 2017 06:36:07 +0000 (GMT)
Received: from DGGEMM405-HUB.china.huawei.com (10.3.20.213) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 11 May 2017 07:36:06 +0100
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.129]) by DGGEMM405-HUB.china.huawei.com ([10.3.20.213]) with mapi id 14.03.0301.000; Thu, 11 May 2017 14:35:29 +0800
From: Roni Even <roni.even@huawei.com>
To: Vijay Gurbani <vijay.gurbani@nokia.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-avtcore-rfc5285-bis.all@ietf.org" <draft-ietf-avtcore-rfc5285-bis.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "avt@ietf.org" <avt@ietf.org>
Subject: RE: Genart last call review of draft-ietf-avtcore-rfc5285-bis-11
Thread-Topic: Genart last call review of draft-ietf-avtcore-rfc5285-bis-11
Thread-Index: AQHSybusAgiMxyxhxEqffNR8CJU4tqHurcGQ
Date: Thu, 11 May 2017 06:35:28 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD7BF765@DGGEMM506-MBX.china.huawei.com>
References: <149444109463.16649.17140517108290058073@ietfa.amsl.com>
In-Reply-To: <149444109463.16649.17140517108290058073@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.201.202]
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.0A020205.59140657.009D, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.3.129, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 6ac0c70b92c2b8c557b7d4b8131b346b
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sY8xJR0hHL1PvCGphYMh5tFilOo>
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, 11 May 2017 06:36:11 -0000

SGkgVmlqYXksDQpUaGFua3MsIEkgd2lsbCBmaXggdGhlc2UgdHdvIG5pdHMNClJvbmkNCg0KPiAt
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBWaWpheSBHdXJiYW5pIFttYWlsdG86
dmlqYXkuZ3VyYmFuaUBub2tpYS5jb21dDQo+IFNlbnQ6INeZ15XXncKg15MgMTAg157XkNeZIDIw
MTcgMjE6MzINCj4gVG86IGdlbi1hcnRAaWV0Zi5vcmcNCj4gQ2M6IGRyYWZ0LWlldGYtYXZ0Y29y
ZS1yZmM1Mjg1LWJpcy5hbGxAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmc7IGF2dEBpZXRmLm9yZw0K
PiBTdWJqZWN0OiBHZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLWF2dGNvcmUt
cmZjNTI4NS1iaXMtMTENCj4gDQo+IFJldmlld2VyOiBWaWpheSBHdXJiYW5pDQo+IFJldmlldyBy
ZXN1bHQ6IFJlYWR5IHdpdGggTml0cw0KPiANCj4gSSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCBy
ZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gVGhlIEdlbmVyYWwgQXJlYSBSZXZpZXcNCj4gVGVhbSAo
R2VuLUFSVCkgcmV2aWV3cyBhbGwgSUVURiBkb2N1bWVudHMgYmVpbmcgcHJvY2Vzc2VkIGJ5IHRo
ZSBJRVNHIGZvcg0KPiB0aGUgSUVURiBDaGFpci4gIFBsZWFzZSB0cmVhdCB0aGVzZSBjb21tZW50
cyBqdXN0IGxpa2UgYW55IG90aGVyIGxhc3QgY2FsbA0KPiBjb21tZW50cy4NCj4gDQo+IEZvciBt
b3JlIGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQNCj4gDQo+IDxodHRwczovL3Ry
YWMuaWV0Zi5vcmcvdHJhYy9nZW4vd2lraS9HZW5BcnRmYXE+Lg0KPiANCj4gRG9jdW1lbnQ6IGRy
YWZ0LWlldGYtYXZ0Y29yZS1yZmM1Mjg1LWJpcy0xMQ0KPiBSZXZpZXdlcjogVmlqYXkgR3VyYmFu
aQ0KPiBSZXZpZXcgRGF0ZTogMjAxNy0wNS0xMA0KPiBJRVRGIExDIEVuZCBEYXRlOiAyMDE3LTA0
LTIwDQo+IElFU0cgVGVsZWNoYXQgZGF0ZTogTm90IHNjaGVkdWxlZCBmb3IgYSB0ZWxlY2hhdA0K
PiANCj4gU3VtbWFyeTogUmVhZHkgd2l0aCBuaXRzLg0KPiANCj4gTWFqb3IgaXNzdWVzOiAwDQo+
IA0KPiBNaW5vciBpc3N1ZXM6IDANCj4gDQo+IE5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOg0KPiAt
IFM1OiBzL0FuIGV4YW1wbGUgKHRoaXMgaXMgb25seSBhbiBleGFtcGxlKSwgd2hlcmUvQW4gZXhh
bXBsZSB3aGVyZS8NCj4gICAoSSBzdXNwZWN0IHRoYXQgdGhlIHJlYWRlciB3aWxsIGdldCB0aGUg
aWRlYSB0aGF0IHRoaXMgaXMgb25seSBhbg0KPiAgICBleGFtcGxlLiAgVGhlcmUgYXJlIGEgY291
cGxlIG9mIG9jY3VycmVuY2Ugb2YgdGhpcyBpbiBTNS4pDQo+IA0KPiAtIFM2OiBzL1doZW4gZG9p
bmcgU0RQIE9mZmVyL1doZW4gZW5nYWdpbmcgaW4gU0RQIE9mZmVyLw0KPiANCj4gVGhhbmtzIQ0K
PiANCg0K


From nobody Thu May 11 00:18:15 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 951E6128D6F for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 00:18:14 -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 5QDtl7zeat3o for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 00:18:13 -0700 (PDT)
Received: from mail-wr0-x241.google.com (mail-wr0-x241.google.com [IPv6:2a00:1450:400c:c0c::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 EEA1A127BA3 for <ietf@ietf.org>; Thu, 11 May 2017 00:18:12 -0700 (PDT)
Received: by mail-wr0-x241.google.com with SMTP id w50so2184973wrc.0 for <ietf@ietf.org>; Thu, 11 May 2017 00:18:12 -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=MAakrrovMt433fssmiQpSjFu5pIJlAdhGtvHRVvvesI=; b=c5M1LZ39xB4PcnUyJA7cni9BA0V97wtQeyI0DUqa6Afg/mYHHJLRQ/Wqb//tUveazh R+RKW1p1JBs8ZnrzW+eeG/+MoDolf1B8TSQijf7twQFGOf4Wu6Igyyxx5mk62ROxWj6j do1GBxX+x+qqexh3B92JKt692h4/bYv46VCo3F0lZaARns4vu6Ttu7AaNvIuofCk8+ha QdmNczmz43VfxnQOm+CvJckgKwdfXQ6GsXTgWgW0EGsCijtqIYYVgp1CIUPzVmaaA+m7 WGuqQPp0o57r85moGc/HJPO56q2hE1u2Fkxpe6bRiRzPz3+cCVxjVyCb+RXvbJyPOknU sEDA==
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=MAakrrovMt433fssmiQpSjFu5pIJlAdhGtvHRVvvesI=; b=YILrysmQsolM7t0tLG90ebFkHGacskzR55M0eDDaalQPCIjvGk2pXdCZOENTKheqto qkM22T8JMODJbtCjhCqS0dq+QJSPnLzrqnX1Iz+JJw+c3s53yK7KB0mWGJYKGn4h0+fo S/e/4eNJQjQ1D9wUuKolTQhfcxVJ1x+uoTZyxy8A7YdrLxiGA+JwaQqoMX8s5bN0jUW8 xzDqahjerpBO7ifZqES0a1RcxDnF9MNs2BTbYz26MqIPqLDVq6lNKbncKxNFaIdo8A3i PpzS3nij4zE+gDR0lxIo3eV1rXvLdoZH4WswQCXWLRZL3imPLnf85TLGuQBrawWM47G3 oKUg==
X-Gm-Message-State: AODbwcCzcs2Ka7lQYIZsTQv4ZUsgQoRGGG930zlcc49WaqAsTg2p2tC2 S7rOS0hwwhz1FUL0uTI=
X-Received: by 10.223.176.84 with SMTP id g20mr6943147wra.172.1494487091472; Thu, 11 May 2017 00:18:11 -0700 (PDT)
Received: from [172.24.228.70] (dyn32-131.checkpoint.com. [194.29.32.131]) by smtp.gmail.com with ESMTPSA id l1sm869238wrl.15.2017.05.11.00.18.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 May 2017 00:18:10 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <27E63309-8D6F-4C85-AFB1-6A0A97579E22@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_E2A3BBC7-438A-4FFC-9CE6-7D3C3A6409CA"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Registration for remote participation
Date: Thu, 11 May 2017 10:18:05 +0300
In-Reply-To: <F02ABABE3D62B99B29AB9A9C@PSB>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
To: John C Klensin <john-ietf@jck.com>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <82C753BB-C89C-4039-8A08-0615067777C0@gmail.com> <7D148F612B0A8241B214B9D7@PSB> <63BCEF0D-E6FC-4E10-A4B2-3E4CC122B9A6@gmail.com> <F02ABABE3D62B99B29AB9A9C@PSB>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uM1-qGz2KJtdX-AUNh2pdzXUftQ>
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, 11 May 2017 07:18:15 -0000

--Apple-Mail=_E2A3BBC7-438A-4FFC-9CE6-7D3C3A6409CA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 11 May 2017, at 3:46, John C Klensin <john-ietf@jck.com> wrote:
>=20
>=20
>=20
> --On Thursday, May 11, 2017 00:28 +0300 Yoav Nir
> <ynir.ietf@gmail.com> wrote:
>=20
>>> On 10 May 2017, at 15:50, John C Klensin <john-ietf@jck.com>
>>> wrote:
>>>=20
>>> I favor at least a nominal registration fee for the same
>>> reason -- not because I see it as an important revenue source
>>> (a rather different discussion0 but because it helps
>>> eliminate Donald Duck registrations.
>>=20
>> How does a fee eliminate Donald Duck registrations?  There's
>> nothing preventing me from registering *now* for the Prague
>> physical meeting as Donald Duck as long as my $700 are good.
>=20
> Unless things have changed since I was paying active attention,
> most registrations, especially those in advance of a meeting,
> are paid with credit cards.   If you can get a credit card in
> the name of M. Duck, more power to you,

I don=E2=80=99t know if things have changed, but bank transfers are also =
accepted. And I usually have my employer=E2=80=99s credit card pay for =
the meeting, so my name is nowhere on that.

But being able to trace participants to their true identity is one =
thing. Having their true names appear in blue sheets or Jabber windows =
is, I think, important for us and one of the points of this exercise.

Yoav

--Apple-Mail=_E2A3BBC7-438A-4FFC-9CE6-7D3C3A6409CA
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-----

iQEcBAEBCgAGBQJZFBAuAAoJELhJCxUKWMyZOKUIAL0/AbzuhCnffxUXDv6jGA0q
y5tP+fjI1A+yPcUiZV2Jg071QPqujrjkktM3DEKavSngjYpc8VOhCON94c7NaYdv
iT03Lh5G5AP3Rz+9SDHrQfzatEeKDXoU/8KxUyRRoUkat2GnSlhj3OK0LcdaXVuG
P6lscSqyqlMIey1dltN/3uDjH3RtO8asEcQndic044vi8zbJw8B6ps5PPG+gRHP6
knftHpvXLRQ8edUrUnuKCdI0WzUO4ARbeG3hqJyV+LG4yknJ4eunfcpIp2O4aLyi
w4wsLrWh1pJvWJv/zRtVzap6BKG6C/+V/BuYzl4viX35OvgdwxGaSGhs2lx27gk=
=7e9O
-----END PGP SIGNATURE-----

--Apple-Mail=_E2A3BBC7-438A-4FFC-9CE6-7D3C3A6409CA--


From nobody Thu May 11 00:26:47 2017
Return-Path: <robmgl@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 0F4AD129AA3; Thu, 11 May 2017 00:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 VsobZLhloFCC; Thu, 11 May 2017 00:26:42 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 508E2129666; Thu, 11 May 2017 00:26:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17694; q=dns/txt; s=iport; t=1494487602; x=1495697202; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=iPucKD3XmJKf8gV3oF2uYyec2Lx8bzqga5ZMgG3FDqA=; b=FfBpqoAD+qsUl4jOfIEzlqYHmjfitMXHXW6HuslDK3twvQmei6zKnRQD TIIubBiCxhu5FII467DFZ5zIfEZm4W9LZs37ECojJ4yzMl4paU5GpQL6y XytXKOhi4RJYGiMX31DdugDInvfKqcCYn0EnZKjWa/Oeg6w04JJWU1ivQ Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DkAAAg4xNZ/4ENJK1TChkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYMqK2KBDAeDYooYkViIJY1Pgg8shXgCGoRoPxgBAgEBAQEBAQF?= =?us-ascii?q?rKIUVAQEBAQMOFRExBg4MBAIBCBEBAgEBAQMCERIDAgICHxEUAQIGCAIEAQ0FC?= =?us-ascii?q?BOJbQMVDrFRgiaHMA2DOAEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgQuHMQGDG4J?= =?us-ascii?q?UgWcOQBmCU4JgBZAihjeGdjsBhxuDNYN3hEqCDYU7hQKFKoh/gi6EZ4QuAR84g?= =?us-ascii?q?QpwFUaEdhyBY3aIDIENAQEB?=
X-IronPort-AV: E=Sophos;i="5.38,322,1491264000"; d="scan'208";a="25936985"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 May 2017 07:26:41 +0000
Received: from XCH-RCD-009.cisco.com (xch-rcd-009.cisco.com [173.37.102.19]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v4B7Qfe5011892 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 11 May 2017 07:26:41 GMT
Received: from xch-rcd-009.cisco.com (173.37.102.19) by XCH-RCD-009.cisco.com (173.37.102.19) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 11 May 2017 02:26:40 -0500
Received: from xch-rcd-009.cisco.com ([173.37.102.19]) by XCH-RCD-009.cisco.com ([173.37.102.19]) with mapi id 15.00.1210.000; Thu, 11 May 2017 02:26:40 -0500
From: "Roberta Maglione (robmgl)" <robmgl@cisco.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "spring@ietf.org" <spring@ietf.org>, "draft-ietf-spring-ipv6-use-cases.all@ietf.org" <draft-ietf-spring-ipv6-use-cases.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Genart last call review of draft-ietf-spring-ipv6-use-cases-10
Thread-Topic: Genart last call review of draft-ietf-spring-ipv6-use-cases-10
Thread-Index: AQHSw2VAyXPj3jfsxU2lEYHPpiixaaHux9KQ
Date: Thu, 11 May 2017 07:26:40 +0000
Message-ID: <0feaa4ed02d448a88d720113bf1814ce@XCH-RCD-009.cisco.com>
References: <149374426742.21414.16408814015665498739@ietfa.amsl.com>
In-Reply-To: <149374426742.21414.16408814015665498739@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.60.123.211]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XywD9Wxvxqzfg_t6_7prmf15y_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: Thu, 11 May 2017 07:26:45 -0000

SGVsbG8gU3Rld2FydCwNClRoYW5rcyBmb3IgeW91ciByZXZpZXcgYW5kIGNvbW1lbnRzLg0KV2Ug
d2lsbCB1cGRhdGUgdGhlIGRyYWZ0IGFuZCBmb2N1cyBvbiB0aGUgdXNlIGNhc2Ugd2hlcmUgdGhl
IGlwdjYgZGF0YXBsYW5lIGlzIHVzZWQgd2l0aG91dCBhbnkgcHJlc2VuY2Ugb2YgbXBscy4gVGhp
cyBhZGRyZXNzZXMgdGhlIHJlcXVpcmVtZW50cyBleHByZXNzZWQgYnkgaXB2NiBuZXR3b3JrIHdo
ZXJlLCBieSBkZXNpZ24gcG9saWN5LCBtcGxzIGRhdGFwbGFuZSBpcyBub3QgdXNlZC4NCg0KUmVn
YXJkcw0KUm9iZXJ0YQ0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBTdGV3
YXJ0IEJyeWFudCBbbWFpbHRvOnN0ZXdhcnQuYnJ5YW50QGdtYWlsLmNvbV0gDQpTZW50OiBUdWVz
ZGF5LCBNYXkgMiwgMjAxNyA2OjU4IFBNDQpUbzogZ2VuLWFydEBpZXRmLm9yZw0KQ2M6IHNwcmlu
Z0BpZXRmLm9yZzsgZHJhZnQtaWV0Zi1zcHJpbmctaXB2Ni11c2UtY2FzZXMuYWxsQGlldGYub3Jn
OyBpZXRmQGlldGYub3JnDQpTdWJqZWN0OiBHZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFm
dC1pZXRmLXNwcmluZy1pcHY2LXVzZS1jYXNlcy0xMA0KDQpSZXZpZXdlcjogU3Rld2FydCBCcnlh
bnQNClJldmlldyByZXN1bHQ6IE5vdCBSZWFkeQ0KDQpJIGFtIHRoZSBhc3NpZ25lZCBHZW4tQVJU
IHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBUaGUgR2VuZXJhbCBBcmVhIFJldmlldyBUZWFtIChH
ZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQgYnkgdGhl
IElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLiAgUGxlYXNlIHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1
c3QgbGlrZSBhbnkgb3RoZXIgbGFzdCBjYWxsIGNvbW1lbnRzLg0KDQpGb3IgbW9yZSBpbmZvcm1h
dGlvbiwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0DQoNCjxodHRwczovL3RyYWMuaWV0Zi5vcmcvdHJh
Yy9nZW4vd2lraS9HZW5BcnRmYXE+Lg0KDQpEb2N1bWVudDogZHJhZnQtaWV0Zi1zcHJpbmctaXB2
Ni11c2UtY2FzZXMtPz8NClJldmlld2VyOiBTdGV3YXJ0IEJyeWFudA0KUmV2aWV3IERhdGU6IDIw
MTctMDUtMDINCklFVEYgTEMgRW5kIERhdGU6IDIwMTctMDUtMDQNCklFU0cgVGVsZWNoYXQgZGF0
ZTogTm90IHNjaGVkdWxlZCBmb3IgYSB0ZWxlY2hhdA0KDQpTdW1tYXJ5Og0KDQpJIGhhdmUgYSBu
dW1iZXIgb2YgY29uY2VybnMgYWJvdXQgdGhpcyBkcmFmdCwgd2hpY2ggSSBkZXRhaWwgYmVsb3cu
DQoNCkEgc2lnbmlmaWNhbnQgcGFydCBvZiB0aGUganVzdGlmaWNhdGlvbiBzZWVtcyB0byBldm9s
dmUgYXJvdW5kIHRoZSBpbmFiaWxpdHkgb2YgTVBMUyB0byBmdW5jdGlvbiBpbiBhbiBJUHY2IG9u
bHkgbmV0d29yay4gVGhpcyBpcyBzb21ldGhpbmcgdGhhdCB0aGUgTVBMUyBXRyBzaG91bGQgcHJv
dmlkZSBleHBlcnQgaW5wdXQgb24uDQoNCk1ham9yIGlzc3VlczoNCiAgIEluIGFkZGl0aW9uIHRo
ZXJlIGFyZSBjYXNlcyB3aGVyZSB0aGUgb3BlcmF0b3JzIGNvdWxkIGhhdmUgbWFkZSB0aGUNCiAg
IGRlc2lnbiBjaG9pY2UgdG8gZGlzYWJsZSBJUHY0LCBmb3IgZWFzZSBvZiBtYW5hZ2VtZW50IGFu
ZCBzY2FsZQ0KICAgKHJldHVybiB0byBzaW5nbGUtc3RhY2spIG9yIGR1ZSB0byBhbiBhZGRyZXNz
IGNvbnN0cmFpbnQsIGZvciBleGFtcGxlDQogICBiZWNhdXNlIHRoZXkgZG8gbm90IHBvc3Nlc3Mg
ZW5vdWdoIElQdjQgYWRkcmVzc2VzIHJlc291cmNlcyB0byBudW1iZXINCiAgIGFsbCB0aGUgZW5k
cG9pbnRzIGFuZCBvdGhlciBuZXR3b3JrIGVsZW1lbnRzIG9uIHdoaWNoIHRoZXkgZGVzaXJlIHRv
DQogICBydW4gTVBMUy4NCg0KU0I+IEJ1dCBhcyBJIHNob3cgYmVsb3cgTVBMUyBXRyBlaXRoZXIg
aGFzIGZpeGVkIHRoaXMgb3IgaXMgdmVyeQ0KY2xvc2UNClNCPiB0byBmaXhpbmcgdGhpcywgc28g
SSBkb24ndCBzZWUgaG93IHlvdSBjYW4ganVzdGlmeSBkZXNpZ25pbmcgYSBtYWpvciANClNCPiBt
b2RpZmljYXRpb24gdG8gdGhlIElQdjYgZGF0YXBsYW5lIG9uIHRoZSBiYXNpcyBvZiB0aGUgYWJv
dmUNCg0KU0I+IHN0YXRlbWVudC4NCg0KPT09PT09PT09PT09PT09DQoNCiAgIEluIHN1Y2ggc2Nl
bmFyaW8gdGhlIHN1cHBvcnQgZm9yIE1QTFMgb3BlcmF0aW9ucyBvbiBhbiBJUHY2LW9ubHkNCiAg
IG5ldHdvcmsgd291bGQgYmUgcmVxdWlyZWQuICBIb3dldmVyIHRvZGF5J3MgSVB2Ni1vbmx5IG5l
dHdvcmtzIGFyZQ0KICAgbm90IGZ1bGx5IGNhcGFibGUgb2Ygc3VwcG9ydGluZyBNUExTLiAgVGhl
cmUgaXMgb25nb2luZyB3b3JrIGluIHRoZQ0KICAgTVBMUyBXb3JraW5nIEdyb3VwLCBkZXNjcmli
ZWQgaW4gW1JGQzc0MzldIHRvIGlkZW50aWZ5IGdhcHMgdGhhdCBtdXN0DQogICBiZSBhZGRyZXNz
ZWQgaW4gb3JkZXIgdG8gYWxsb3cgTVBMUy1yZWxhdGVkIHByb3RvY29scyBhbmQNCiAgIGFwcGxp
Y2F0aW9ucyB0byBiZSB1c2VkIHdpdGggSVB2Ni1vbmx5IG5ldHdvcmtzLiAgDQoNClNCPiBUaGF0
IGRyYWZ0IHdhcyBwdWJsaXNoZWQgdHdvIHllYXJzIGFnby4gQW4gUkZDIHdhcyBwdWJsaXNoZWQg
dG8gDQpTQj4gYWRkcmVzcyB0aGUgTERQIGdhcCBtaWQgMjAxNi4gUkZDNzUwNiBmaXhlZCB0aGUg
UkFPIGluIEFwcmlsDQoyMDE1LA0KU0I+IE1JQnMgYXJlIGJlaW5nIHJlcGxhY2VkIGJ5IFlBTkcu
IEkgYW0gbm90IHN1cmUgeW91IG5lZWQgR01QTFMsIEwyVlBOIA0KU0I+IG9yIEwzVlBOIGluIHRo
ZSBhcHBsaWNhdGlvbiB5b3UgY2l0ZS4NClNCPg0KU0I+IEkgdGhpbmsgYSBtb3JlIHVwIHRvIGRh
dGUgZXZhbHVhdGlvbiBvZiB0aGUgYWJpbGl0eSBvZiBNUExTIHRvIHJ1biANClNCPiBpbiBhbiBJ
UHY2IG5ldHdvcmsgaXMgbmVlZGVkLg0KU0I+DQpTQj4gQWRkaXRpb25hbGx5IGlmIHlvdSBhcmUg
dGFsa2luZyBNUExTLVNSIHRoZW4gdGhlIHNob3J0ZmFsbCBpcyANClNCPiBkaWZmZXJlbnQgc3Rp
bGwgYmVjYXVzZSB5b3UgcmVseSBvbiB0aGUgU1IgZXh0ZW5zaW9ucyB0byB0aGUgSUdQcyANClNC
PiBhbmQgbm90IHRoZSBjbGFzc2ljIE1QTFMgc2lnbmFsbGluZyBwcm90b2NvbHMuDQoNCj09PT09
PT09PT09PQ0KDQogICAyLiAgVGhlcmUgaXMgYSBzdHJpY3QgbGFjayBvZiBhbiBNUExTIGRhdGFw
bGFuZSBpbiBhIHBvcnRpb24gb2YgdGhlDQogICAgICAgZW5kIHRvIGVuZCBwYXRoDQoNClNCPiBJ
dCBpcyBub3QgdGhlIGxhY2sgb2YgTVBMUyBpbiBhIHBvcnRpb24gb2YgdGhlIG5ldHdvcmssIHNp
bmNlIHlvdSANClNCPiBjYW4gdHVubmVsIE1QTFMgb3ZlciBJUC4gVGhlIGNvbnN0cmFpbnQgYXBw
bGllcyB3aGVuIHlvdSBuZWVkIHRha2UgDQpTQj4gYW4gTVBMUyBhY3Rpb24gYXQgbm9kZSB0aGF0
IGRvZXMgbm90IGhhdmUgTVBMUyBmb3J3YXJkaW5nDQpsb2dpYy4NClNCPiBJIHdvbmRlciBob3cg
Y29tbW9uIHRoaXMgaXMgaW4gcHJhY3Rpc2UgZ2l2ZW4gdGhhdCBJIHVuZGVyc3RhbmQNCnRoYXQg
DQpTQj4gb3RoZXIgd29yayBpbiBJUHY2IFNSIGlzIGRyaXZpbmcgdG93YXJkcyBjb252aW5jaW5n
IHBlb3BsZSB0aGF0IHRoZSANClNCPiBudW1iZXIgb2YgYWN0dWFsIFNSIGFjdGlvbnMgb24gYSBw
YXRoIGlzIHRpbnkuDQoNCiAgIDQuICBUaGVyZSBpcyBhIG5lZWQgdG8gY29ubmVjdCBtaWxsaW9u
cyBvZiBhZGRyZXNzYWJsZSBzZWdtZW50DQogICAgICAgZW5kcG9pbnRzLCB0aHVzIGhpZ2ggcm91
dGluZyBzY2FsYWJpbGl0eSBpcyBhIHJlcXVpcmVtZW50LiANCklQdjYNCiAgICAgICBhZGRyZXNz
ZXMgYXJlIGluaGVyZW50bHkgc3VtbWFyaXphYmxlOiBhIHZlcnkgbGFyZ2Ugb3BlcmF0b3INCiAg
ICAgICBjb3VsZCBzY2FsZSBieSBzdW1tYXJpemluZyBJUHY2IHN1Ym5ldHMgYXQgdmFyaW91cyBp
bnRlcm5hbA0KICAgICAgIGJvdW5kYXJpZXMuICBUaGlzIGlzIHZlcnkgc2ltcGxlIGFuZCBpcyBh
IGJhc2ljIHByb3BlcnR5IG9mIElQDQogICAgICAgcm91dGluZy4gIE1QTFMgbm9kZSBzZWdtZW50
cyBhcmUgbm90IHN1bW1hcml6YWJsZS4gIFRvIHJlYWNoIHRoZQ0KICAgICAgIHNhbWUgc2NhbGUs
IGFuIG9wZXJhdG9yIHdvdWxkIG5lZWQgdG8gaW50cm9kdWNlIGFkZGl0aW9uYWwNCiAgICAgICBj
b21wbGV4aXR5LCBzdWNoIGFzIG1lY2hhbmlzbXMga25vd24gd2l0aCB0aGUgaW5kdXN0cnkgdGVy
bQ0KICAgICAgIFNlYW1sZXNzIE1QTFMgW0ktRC5pZXRmLW1wbHMtc2VhbWxlc3MtbXBsc10uDQoN
ClNCPiBBcyBmYXIgYXMgSSBjYW4gc2VlIHRoYXQgZHJhZnQgaGFzIGRpZWQsIGluZGVlZCBpdCBk
aWVkIGluIDIwMTQuDQpTQj4gQXNzdW1pbmcgaXQgaGFzIG5vdCBiZSByZS1pbmNhcm5hdGVkIGlu
IGFub3RoZXIgbmFtZSwgdGhpcyBjYWxscyANClNCPiBpbnRvIHF1ZXN0aW9uIHRoZSB2YWxpZGl0
eSBvZiB0aGUgdXNlIGNhc2UuDQpTQj4NClNCPiBJIHRoaW5rIHRvIGNvbXBhcmUgYXBwbGVzIHdp
dGggYXBwbGVzIGhlcmUsIHdlIG5lZWQgdG8gdGFrZSBhIGxvb2sgDQpTQj4gYXQgc3BlY2lmaWMg
ZXhhbXBsZXMgdG8gdmVyaWZ5IHRoYXQgdGhlIHNjYWxpbmcgY29uY2Vybg0KYXJpc2VzLg0KU0I+
IEFzIHBhcnQgb2YgdGhhdCB3ZSBuZWVkIHRvIGNvbnNpZGVyIHdoZXRoZXIgdGhlIGludHJpbnNp
Yw0KaGllcmFyY2h5DQpTQj4gTVBMUywgYW5kIHRoZSBhdmFpbGFiaWxpdHkgb2YgTVBMUyBjb250
ZXh0IGxhYmVscyBhZGRyZXNzZXMgdGhlDQppc3N1ZS4NCg0KU0I+IEFzIGZhciBhcyBJIGNhbiBz
ZWUgdGhhdCBkcmFmdCBoYXMgZGllZCwgaW5kZWVkIGl0IGRpZWQgaW4gMjAxNC4NClNCPiBBc3N1
bWluZyBpdCBoYXMgbm90IGJlIHJlLWluY2FybmF0ZWQgaW4gYW5vdGhlciBuYW1lLCB0aGlzIGNh
bGxzIA0KU0I+IGludG8gcXVlc3Rpb24gdGhlIHZhbGlkaXR5IG9mIHRoZSB1c2UgY2FzZS4NClNC
Pg0KU0I+IEkgdGhpbmsgdG8gY29tcGFyZSBhcHBsZXMgd2l0aCBhcHBsZXMgaGVyZSwgd2UgbmVl
ZCB0byB0YWtlIGEgbG9vayANClNCPiBhdCBzcGVjaWZpYyBleGFtcGxlcyB0byB2ZXJpZnkgdGhh
dCB0aGUgc2NhbGluZyBjb25jZXJuDQphcmlzZXMuDQpTQj4gQXMgcGFydCBvZiB0aGF0IHdlIG5l
ZWQgdG8gY29uc2lkZXIgd2hldGhlciB0aGUgaW50cmluc2ljDQpoaWVyYXJjaHkNClNCPiBNUExT
LCBhbmQgdGhlIGF2YWlsYWJpbGl0eSBvZiBNUExTIGNvbnRleHQgbGFiZWxzIGFkZHJlc3NlcyB0
aGUNCmlzc3VlLg0KDQogICBJbiBhbnkgZW52aXJvbm1lbnQgd2l0aCByZXF1aXJlbWVudHMgc3Vj
aCBhcyB0aG9zZSBsaXN0ZWQgYWJvdmUsIGFuDQogICBJUHY2IGRhdGEgcGxhbmUgDQoNClNCPiBO
bywgYW4gSVB2NiBkYXRhcGxhbmUgZXh0ZW5kZWQgdG8gaW5jbHVkZSBzb3VyY2Ugcm91dGluZw0K
Y2FwYWJpbGl0eQ0KU0I+IC4uLiBZb3UgZG8gbm90IGdldCB0aGlzIHRocm91Z2ggYW4gb2ZmIHRo
ZSBzaGVsZiBJUHY2IGRhdGFwbGFuZSANClNCPiBvdGhlciB0aGFuIHBlcmhhcHMgTVBMUy9JUHY2
Lg0KU0I+IC4uLiBhbmQgd2Ugc2hvdWxkIG5vdCBiZWxpdHRsZSB0aGUgZGlmZmljdWx0eSBvZiBk
b2luZyB0aGUNCnByb3Bvc2VkDQpTQj4gU1J2NiBleHRlbnNpb25zLCBub3QgYWxsIGgvdyBjYW4g
ZWFzaWx5IGRvIGl0LCBhbmQgYSBsb3Qgb2YgaC93DQpjYW4gDQpTQj4gb25seSBpbnRyb2R1Y2Ug
YSB0aW55IG51bWJlciBvZiBzZWdtZW50cy4NCg0KICAgcHJvdmlkZXMgYSBwb3dlcmZ1bCBjb21i
aW5hdGlvbiBvZiBjYXBhYmlsaXRpZXMgZm9yIGENCiAgIG5ldHdvcmsgb3BlcmF0b3IgdG8gcmVh
bGl6ZSBiZW5lZml0cyBpbiBleHBsaWNpdCByb3V0aW5nLCBwcm90ZWN0aW9uDQogICBhbmQgcmVz
dG9yYXRpb24sIGhpZ2ggcm91dGluZyBzY2FsYWJpbGl0eSwgdHJhZmZpYyBlbmdpbmVlcmluZywN
CiAgIHNlcnZpY2UgY2hhaW5pbmcsIHNlcnZpY2UgZGlmZmVyZW50aWF0aW9uIGFuZCBhcHBsaWNh
dGlvbiBmbGV4aWJpbGl0eQ0KICAgdmlhIHByb2dyYW1tYWJpbGl0eS4NCg0KU0I+IFRoZXJlIGlz
IGEgYml0IG9mIGFuICh1bmV4cGxhaW5lZCkgbGVhcCBmcm9tIHRoZSBpbnRyb2R1Y3Rpb24gb2YN
ClNCPiBJUHY2IHRvIHRoZSBhYm92ZSBzZXQgb2YgdXNlIGNhc2VzLg0KDQo9PT09PT09PT09PT0N
Cg0KICAgVGhlIHVzZSBjYXNlcyBkZXNjcmliZWQgaW4gdGhlIHNlY3Rpb24gZG8gbm90IGNvbnN0
aXR1dGUgYW4NCiAgIGV4aGF1c3RpdmUgbGlzdCBvZiBhbGwgdGhlIHBvc3NpYmxlIHNjZW5hcmlv
czsgdGhpcyBzZWN0aW9uIG9ubHkNCiAgIGluY2x1ZGVzIHNvbWUgb2YgdGhlIG1vc3QgY29tbW9u
IGVudmlzaW9uZWQgZGVwbG95bWVudCBtb2RlbHMgZm9yDQogICBJUHY2IFNlZ21lbnQgUm91dGlu
Zy4gIEluIGFkZGl0aW9uIHRvIHRoZSB1c2UgY2FzZXMgZGVzY3JpYmVkIGluIHRoaXMNCiAgIGRv
Y3VtZW50IHRoZSBzcHJpbmcgYXJjaGl0ZWN0dXJlIHNob3VsZCBiZSBhYmxlIHRvIGJlIGFwcGxp
ZWQgdG8gYWxsDQogICB0aGUgdXNlIGNhc2VzIGRlc2NyaWJlZCBpbiBbUkZDNzg1NV0gZm9yIHRo
ZSBzcHJpbmcgTVBMUyBkYXRhIHBsYW5lLA0KICAgd2hlbiBhbiBJUHY2IGRhdGEgcGxhbmUgaXMg
cHJlc2VudC4NCg0KU0I+IFRoZSBzZWNvbmQgc2VudGVuY2UgcmVkdWNlcyB0byB0aGUgbmVlZCB0
byBtYWtlIE1QTFMgd29yayBpbiBhbiBJUHY2IA0KU0I+IGVudmlyb25tZW50Lg0KDQo9PT09PT09
PT09DQoNCiAgIFRoZSBhYmlsaXR5IHRvIHN0ZWVyIHRyYWZmaWMgdG8gYW4gYXBwcm9wcmlhdGUg
ZWdyZXNzIG9yIHV0aWxpemUgYQ0KICAgc3BlY2lmaWMgdHlwZSBvZiBtZWRpYSAoZS5nLiwgbG93
LXBvd2VyLCBXSUZJLCB3aXJlZCwgZmVtdG8tY2VsbCwNCiAgIGJsdWV0b290aCwgTU9DQSwgSG9t
ZVBsdWcsIGV0Yy4pIHdpdGhpbiB0aGUgaG9tZSBpdHNlbGYgYXJlIG9idmlvdXMNCiAgIGNhc2Vz
IHdoaWNoIG1heSBiZSBvZiBpbnRlcmVzdCB0byBhbiBhcHBsaWNhdGlvbiBydW5uaW5nIHdpdGhp
biBhDQogICBob21lIG5ldHdvcmsuDQoNClNCPiBTbyB0aGUgaW50ZXJlc3RpbmcgdGhpbmcgaGVy
ZSBpcyB0aGF0IHRvIHNldCB1cCBhIFNSIHlvdSBub3JtYWxseSANClNCPiBuZWVkIHRvIGtub3cg
dGhlIHRvcG9sb2d5IHNvIHlvdSBjYW4gcGxhbiB0aGUgcGF0aCwgYnV0IGhvbWVuZXQgDQpTQj4g
Y2hvc2UgYSBkaXN0YW5jZSB2ZWN0b3IgcHJvdG9jb2wsIHdoaWNoIGlzIGEgcHJvdG9jb2wgZ2Vu
cmUgdGhhdCANClNCPiBub3JtYWxseSBkb2VzIG5vdCB1bmRlcnN0YW5kIHRoZSB0b3BvbG9neS4N
Cg0KPT09PT09PT0NCg0KICAgSW5mb3JtYXRpb24gaW5jbHVkZWQgaW4gdGhlIHNwcmluZyBoZWFk
ZXIsIHdoZXRoZXIgaW1wb3NlZCBieSB0aGUNCiAgIGVuZC1ob3N0IGl0c2VsZiwgYSBjdXN0b21l
ciBlZGdlIHJvdXRlciwgb3Igd2l0aGluIHRoZSBhY2Nlc3MgbmV0d29yaw0KICAgb2YgdGhlIElT
UCwgbWF5IGJlIG9mIHVzZSBhdCB0aGUgZmFyIGVuZHMgb2YgdGhlIGRhdGEgY29tbXVuaWNhdGlv
bg0KICAgYXMgd2VsbC4gIEZvciBleGFtcGxlLCBhbiBhcHBsaWNhdGlvbiBydW5uaW5nIG9uIGFu
IGVuZC1ob3N0IHdpdGgNCiAgIGFwcGxpY2F0aW9uLXN1cHBvcnQgaW4gYSBkYXRhIGNlbnRlciBj
YW4gdXRpbGl6ZSB0aGUgc3ByaW5nIGhlYWRlciBhcw0KICAgYSBjaGFubmVsIHRvIGluY2x1ZGUg
aW5mb3JtYXRpb24gdGhhdCBhZmZlY3RzIGl0cyB0cmVhdG1lbnQgd2l0aGluDQogICB0aGUgZGF0
YSBjZW50ZXIgaXRzZWxmLCBhbGxvd2luZyBmb3IgYXBwbGljYXRpb24tbGV2ZWwgc3RlZXJpbmcg
YW5kDQogICBsb2FkLWJhbGFuY2luZyB3aXRob3V0IHJlbHlpbmcgdXBvbiBpbXBsaWNpdCBhcHBs
aWNhdGlvbg0KICAgY2xhc3NpZmljYXRpb24gdGVjaG5pcXVlcyBhdCB0aGUgZGF0YS1jZW50ZXIg
ZWRnZS4gIEZ1cnRoZXIsIGFzIG1vcmUNCiAgIGFuZCBtb3JlIGFwcGxpY2F0aW9uIHRyYWZmaWMg
aXMgZW5jcnlwdGVkLCB0aGUgYWJpbGl0eSB0byBleHRyYWN0DQogICAoYW5kIGluY2x1ZGUgaW4g
dGhlIHNwcmluZyBoZWFkZXIpIGp1c3QgZW5vdWdoIGluZm9ybWF0aW9uIHRvIGVuYWJsZQ0KICAg
dGhlIG5ldHdvcmsgYW5kIGRhdGEgY2VudGVyIHRvIGxvYWQtYmFsYW5jZSBhbmQgc3RlZXIgdHJh
ZmZpYw0KICAgYXBwcm9wcmlhdGVseSBiZWNvbWVzIG1vcmUgYW5kIG1vcmUgaW1wb3J0YW50Lg0K
DQpTQj4gSG93ZXZlciB0aGVyZSBpcyBhIHRydXN0IGlzc3VlIHdpdGggc2hhcmluZyBpbmZvcm1h
dGlvbiBpbiB0aGlzDQp3YXkNClNCPiBhbmQgaXQgd2FzIGEgYnJlYWNoIG9mIHRydXN0IHRoYXQg
Y2F1c2VkIHRoZSBzb3VyY2Ugcm91dGluZw0KZmVhdHVyZSANClNCPiB0byBiZSByZW1vdmVkIGZy
b20gSVB2NiBpbiB0aGUgZmlyc3QgcGxhY2UuDQpTQj4NClNCPiBGb3IgdGhpcyB0byBiZSBhIHZh
bGlkIHVzZSBjYXNlIEkgdGhpbmsgeW91IG5lZWQgdG8gYWRkcmVzcyB0aGUgDQpTQj4gdHJ1c3Qg
YW5kIHNlY3VyaXR5IGlzc3VlcyB0byBleHBsYWluIHdoeSB0aGV5IGFyZSBubyBsb25nZXINCnJl
bGV2YW50DQpTQj4gb3IgbWFrZSBpdCBjbGVhciB0aGF0IHRoZXkgbmVlZCB0byBiZSBhZGRyZXNz
ZWQuDQoNCj09PT09PT09DQoNCiAgIFRoZSBuZWVkIHRvIHNldHVwIGEgc291cmNlLWJhc2VkIHBh
dGgsIGdvaW5nIHRocm91Z2ggc29tZSBzcGVjaWZpYw0KICAgbWlkZGxlL2ludGVybWVkaWF0ZSBw
b2ludHMgaW4gdGhlIG5ldHdvcmsgbWF5IGJlIHJlbGF0ZWQgdG8gZGlmZmVyZW50DQogICByZXF1
aXJlbWVudHM6DQoNClNCPiBUaGVyZSBuZWVkcyB0byBiZSBzb21lIGRpc2N1c3Npb24gb24gdGhl
IHRydXN0IG1vZGVsIGhlcmUgYW5kIGF0dGFjayANClNCPiB2ZWN0b3JzIGFzc29jaWF0ZWQgd2l0
aCB0aGlzIHByb3Bvc2FsLg0KDQo9PT09PT09PT09DQoNCiAgIFRoaXMgZG9jdW1lbnQgcHJlc2Vu
dHMgdXNlIGNhc2VzIHRvIGJlIGNvbnNpZGVyZWQgYnkgdGhlIHNwcmluZw0KICAgYXJjaGl0ZWN0
dXJlIGFuZCBwb3RlbnRpYWwgSVB2NiBleHRlbnNpb25zLiAgQXMgc3VjaCwgaXQgZG9lcyBub3QN
CiAgIGludHJvZHVjZSBhbnkgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMuICBIb3dldmVyLCB0aGVy
ZSBhcmUgYSBudW1iZXINCiAgIG9mIHNlY3VyaXR5IGNvbmNlcm5zIHdpdGggc291cmNlIHJvdXRp
bmcgYXQgdGhlIElQIGxheWVyIFtSRkM1MDk1XS4NCiAgIEl0IGlzIGV4cGVjdGVkIHRoYXQgYW55
IHNvbHV0aW9uIHRoYXQgYWRkcmVzc2VzIHRoZXNlIHVzZSBjYXNlcyB0bw0KICAgYWxzbyBhZGRy
ZXNzIGFueSBzZWN1cml0eSBjb25jZXJucy4NCg0KU0I+IEl0IGlzIG5vdCBjbGVhciB0aGF0IHRo
ZSBpbnRyb2R1Y3Rpb24gb2YgdGhpcyB0ZWNobm9sb2d5IHRvIHRoZXNlIA0KU0I+IGFwcGxpY2F0
aW9ucyBkb2VzIG5vdCBpbnRyb2R1Y2UgYSBzb2x1dGlvbnMgYWdub3N0aWMgaW5jcmVhc2UgaW4g
DQpTQj4gc2VjdXJpdHkgcmlzay4NClNCPiANCg0KTWlub3IgaXNzdWVzOg0KDQogICBUaGUgb2Jq
ZWN0aXZlIG9mIHRoaXMgZG9jdW1lbnQgaXMgdG8gaWxsdXN0cmF0ZSBzb21lIHVzZSBjYXNlcyB0
aGF0DQogICBuZWVkIHRvIGJlIHRha2VuIGludG8gYWNjb3VudCBieSB0aGUgU291cmNlIFBhY2tl
dCBSb3V0aW5nIGluDQogICBOZXR3b3JraW5nIChTUFJJTkcpIGFyY2hpdGVjdHVyZSBpbiB0aGUg
Y29udGV4dCBvZiBhbiBJUHY2DQogICBlbnZpcm9ubWVudC4NCg0KU0I+IEl0IGlzIHVuY2xlYXIg
d2hldGhlciBpdCBpcyBmZWVkaW5nIHRoZSBTUiBhcmNoaXRlY3R1cmUgKHdoaWNoIGlzIA0KU0I+
IGN1cnJlbnRseSBpbiBBRCBldmFsdWF0aW9uKSBvciB0aGUgU1J2NiBkZXNpZ24uDQpTQj4NClNC
PiBJdCBzZWVtcyBhIGJpdCBsYXRlIHRvIGJlIHByb2dyZXNzaW5nIHRoaXMgaWYgaXQgaXMgYSBy
ZXF1aXJlbWVudCBvbiANClNCPiB0aGUgYXJjaGl0ZWN0dXJlLg0KDQo9PT09PT09PT09PT09PT09
DQoNCiAgIFNvdXJjZSBQYWNrZXQgUm91dGluZyBpbiBOZXR3b3JraW5nIChTUFJJTkcpIGFyY2hp
dGVjdHVyZSBsZXZlcmFnZXMNCiAgIHRoZSBzb3VyY2Ugcm91dGluZyBwYXJhZGlnbS4gIEFuIGlu
Z3Jlc3Mgbm9kZSBzdGVlcnMgYSBwYWNrZXQgdGhyb3VnaA0KICAgYSBjb250cm9sbGVkIHNldCBv
ZiBpbnN0cnVjdGlvbnMsIGNhbGxlZCBzZWdtZW50cywgYnkgcHJlcGVuZGluZyB0aGUNCiAgIHBh
Y2tldCB3aXRoIFNQUklORyBoZWFkZXIuICANCg0KU0I+IFRoYXQgaXMgd2hhdCBJIHRoaW5rIGl0
IHNob3VsZCBkbywgYnV0IHRoYXQgaXMgbm90IHRoZSBkZXNpZ24NCmRpcmVjdGlvbg0KU0I+IG9m
IHRoZSBjdXJyZW50IElQdjYgcHJvcG9zYWwuIFRoZSBkZXNpZ24gb2YgcmVjb3JkIG1vZGlmaWVz
IHRoZQ0KU0I+IElQdjYgaGVhZGVyLg0KDQo9PT09PT09PT09DQoNCiAgIEluIHRvZGF5J3MgbmV0
d29ya3MsIHNvdXJjZSByb3V0aW5nIGlzIHR5cGljYWxseSBhY2NvbXBsaXNoZWQgYnkNCiAgIGVu
Y2Fwc3VsYXRpbmcgSVAgcGFja2V0cyBpbiBNUExTIExTUHMgdGhhdCBhcmUgc2lnbmFsZWQgdmlh
IFJTVlAtVEUuDQoNClNCPiBUaGVyZSBpcyBhbiBpbnRlcmVzdGluZyBxdWVzdGlvbiBhcyB0byB3
aGV0aGVyIFJTVlAtVEUgaXMgYSBzb3VyY2UgDQpTQj4gcm91dGluZyBwYXJhZHlnbSBvciBzaW1w
bHkgYW4gZXhwbGljaXQgcm91dGluZyBwYXJhZHlnbS4NClNCPiBTb3VyY2Ugcm91dGluZyBpcyBt
b3JlIGNvbW1vbmx5IGFzc29jaWF0ZWQgd2l0aCBhIHJvdXRlIGltcG9zZWQgb24gYSANClNCPiBw
YWNrZXQgcmF0aGVyIHRoYW4gdGhlIGlkZW50aWZ5IG9mIGEgcm91dGUgYmVpbmcgaW1wb3NlZCBv
biBhIA0KU0I+IHBhY2tldC4NCg0KICAgMy4gIFRoZXJlIGlzIGEgbmVlZCBvciBkZXNpcmUgdG8g
cmVtb3ZlIHJvdXRpbmcgc3RhdGUgZnJvbSBhbnkgbm9kZQ0KICAgICAgIG90aGVyIHRoYW4gdGhl
IHNvdXJjZSwgc3VjaCB0aGF0IHRoZSBzb3VyY2UgaXMgdGhlIG9ubHkgbm9kZSB0aGF0DQogICAg
ICAga25vd3MgYW5kIHdpbGwga25vdyB0aGUgcGF0aCBhIHBhY2tldCB3aWxsIHRha2UsIGEgcHJp
b3JpDQoNClNCPiBUaGF0IGlzIGEgU1IgZ29hbCwgbm90IGEgZ29hbCBzcGVjaWZpYyB0byBJUHY2
DQoNCj09PT09PT09PT0NCg0KICAgQSBzcHJpbmcgZW5hYmxlZCBob21lIHByb3ZpZGVzIHRoZSBh
YmlsaXR5IHRvIHN0ZWVyIHRyYWZmaWMgaW50byBhDQogICBzcGVjaWZpYyBwYXRoIGZyb20gZW5k
LWhvc3RzIGluIHRoZSBob21lLCBvciBmcm9tIGEgY3VzdG9tZXIgZWRnZQ0KICAgcm91dGVyIGlu
IHRoZSBob21lLiAgDQoNClNCPiBXaGVyZSBkb2VzIEJhYmVsIGZpdCBpbnRvIHRoaXM/IElzbid0
IHRoZSBwdXJwb3NlIG9mIEJhYmVsIHRvIGRvIA0KU0I+IHRoaXMgaW4gYSBzdGFuZGFyZCBJUHY2
IGRhdGFwbGFuZT8NCg0KPT09PT09PT09DQoNCiAgIFNvbWUgRGF0YSBDZW50ZXIgb3BlcmF0b3Jz
IGFyZSB0cmFuc2l0aW9uaW5nIHRoZWlyIERhdGEgQ2VudGVyDQogICBpbmZyYXN0cnVjdHVyZSBm
cm9tIElQdjQgdG8gbmF0aXZlIElQdjYgb25seSwgaW4gb3JkZXIgdG8gY29wZSB3aXRoDQogICBJ
UHY0IGFkZHJlc3MgZGVwbGV0aW9uIGFuZCB0byBhY2hpZXZlIGxhcmdlciBzY2FsZS4gIEluIHN1
Y2gNCiAgIGVudmlyb25tZW50LCBzb3VyY2Ugcm91dGluZyAodGhyb3VnaCBTZWdtZW50IFJvdXRp
bmcgSVB2NikgY2FuIGJlDQogICB1c2VkIHRvIHN0ZWVyIHRyYWZmaWMgYWNyb3NzIHNwZWNpZmlj
IHBhdGhzIHRocm91Z2ggdGhlIG5ldHdvcmsuIA0KDQpTQj4gSSBkbyBub3Qgc2VlIGhvdyB0aGUg
Zmlyc3Qgc2VudGVuY2UgbGVhZHMgdG8gdGhlIHNlY29uZC4NCg0KPT09PT09PT09PQ0KDQogICBJ
biBhbiBlbnZpcm9ubWVudCwgd2hlcmUgZWFjaCBzaW5nbGUgY2FjaGUgc3lzdGVtIGNhbiBiZSB1
bmlxdWVseQ0KICAgaWRlbnRpZmllZCBieSBpdHMgb3duIElQdjYgYWRkcmVzcywgYSBsaXN0IGNv
bnRhaW5pbmcgYSBzZXF1ZW5jZSBvZg0KICAgdGhlIGNhY2hlcyBpbiBhIGhpZXJhcmNoeSBjYW4g
YmUgYnVpbHQuICBBdCBlYWNoIG5vZGUgKGNhY2hlKSBpbiB0aGUNCiAgIGxpc3QsIHRoZSBwcmVz
ZW5jZSBvZiB0aGUgcmVxdWVzdGVkIGNvbnRlbnQgaWYgY2hlY2tlZC4gIElmIHRoZQ0KICAgcmVx
dWVzdGVkIGNvbnRlbnQgaXMgZm91bmQgYXQgdGhlIGNhY2hlIChjYWNoZSBoaXRzIHNjZW5hcmlv
KSB0aGUNCiAgIHNlcXVlbmNlIGVuZHMsIGV2ZW4gaWYgdGhlcmUgYXJlIG1vcmUgbm9kZXMgaW4g
dGhlIGxpc3Q7IG90aGVyd2lzZQ0KICAgbmV4dCBlbGVtZW50IGluIHRoZSBsaXN0IChuZXh0IG5v
ZGUvY2FjaGUpIGlzIGV4YW1pbmVkLg0KDQpTQj4gVGhpcyBuZWVkcyBzb21lIGRpc2N1c3Npb24g
b24gdGhlIGFsdGVybmF0aXZlIGFwcHJvYWNoZXM6DQpTQj4gZm9yIGV4YW1wbGUgc2VydmljZSBm
dW5jdGlvbiBjaGFpbmluZyBhbmQgYW4gSUNOIG92ZXJsYXkuDQoNCk5pdHMvZWRpdG9yaWFsIGNv
bW1lbnRzOiANCiAgIFRoZXJlZm9yZSwgdGhlcmUgYXJlIHNjZW5hcmlvcyB3aGVyZSBpdCBtYXkg
YmUgcG9zc2libGUgdG8gcnVuDQpJUHY2DQogICBvbiB0b3Agb2YgTVBMUywgYW5kIGFzIHN1Y2gs
IHRoZSBNUExTIFNlZ21lbnQgUm91dGluZyBhcmNoaXRlY3R1cmUNCg0KU0I+IEkgdGhpbmsgdGhh
dCBpcyBhIGRlc2lnbiByYXRoZXIgdGhhbiBhbiBhcmNoaXRlY3R1cmUuDQoNCj09PT09PT09PT09
PT0NCg0KICAgVGhpcyBpcyBhbiBhbm90aGVyDQogICBleGFtcGxlIG9mIHNjZW5hcmlvIHdoZXJl
IGEgc29sdXRpb24gcmVseWluZyBvbiBJUHY2IHdpdGhvdXQNCiAgIHJlcXVpcmluZyB0aGUgdXNl
IG9mIE1QTFMgY291bGQgcmVwcmVzZW50IGEgdmFsaWQgb3B0aW9uIHRvIHNvbHZlIHRoZQ0KICAg
cHJvYmxlbSBhbmQgbWVldCBvcGVyYXRvcnMnIHJlcXVpcmVtZW50cy4NCg0KU0I+ICJjb3VsZCIg
aXMgbm90IGEgcGFydGljdWxhcmx5IHN0cm9uZyBqdXN0aWZpY2F0aW9uLg0KDQo=


From nobody Thu May 11 04:06:10 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 D696212EBC0; Thu, 11 May 2017 04:05:50 -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: draft-ietf-bmwg-vswitch-opnfv.all@ietf.org, ietf@ietf.org, bmwg@ietf.org,  dromasca@gmail.com
Subject: Genart last call review of draft-ietf-bmwg-vswitch-opnfv-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149450075072.16690.14546662616864459158@ietfa.amsl.com>
Date: Thu, 11 May 2017 04:05:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JwQWwiXLQ9V4OXzfNPB-ZMMhMa4>
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, 11 May 2017 11:05:51 -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-bmwg-vswitch-opnfv-??
Reviewer: Dan Romascanu
Review Date: 2017-05-11
IETF LC End Date: 2017-05-15
IESG Telechat date: Not scheduled for a telechat

Summary:

Almost Ready. 

This document describes describes the progress of the Open Platform
for NFV (OPNFV) project on virtual switch performance "VSPERF". That
project reuses the BMWG framework and specifications to benchmark
virtual switches implemented in general-purpose hardware. Some
differences with the benchmarking of specialized HW platforms are
identified and they may become work items for BMWG in the future. It's
a well written and clear document, but I have reservations about it
being published as an RFC, and I cannot find coverage for it in the WG
charter. I also have concerns that parts of the methodology used by
OPNFV break the BMWG principles, especially repeatability and
'black-box', and this is not clear enough articulated in the document.
 

Major issues:

1. It is not clear to me why this document needs to be published as an
RFC. The introduction says: 'This memo describes the progress of the
Open Platform for NFV (OPNFV) project on virtual switch performance
"VSPERF".  This project intends to build on the current and completed
work of the Benchmarking Methodology Working Group in IETF, by
referencing existing literature.' Why should the WG and the IESG
invest resources in publishing this, why an I-D or an Independent
Stream RFC is not sufficient? The WG charter says something about:
'VNF and Related Infrastructure Benchmarking: Benchmarking
Methodologies have reliably characterized many physical devices. This
work item extends and enhances the methods to virtual network
functions (VNF) and their unique supporting infrastructure. A first
deliverable from this activity will be a document that considers the
new benchmarking space to ensure that common issues are recognized
from the start, using background materials from industry and SDOs
(e.g., IETF, ETSI NFV).'. I do not believe that this document covers
the intent of the charter, as it focused on one organization only. 

2. In section 3 there 'repeatability' is mentioned, while
acknowledging that in a virtual environment there is no guarantee and
actually no way to know what other applications are being run.
Measuring parameters as the ones listed in 3.3 provides just part of
the answer, and they are internal parameters to the SUT. Also, the
different deployment scenarios in section 4 require different
configurations for the SUT, thus breaking the 'black-box' principle. I
believe that there is a need for a more clear explanation of why BMWG
specifications are appropriate and how comparison can be made while
repeatability cannot be ensured, and measurements are dependent upon
parameters internal to the SUT. 

Minor issues:

1. Some of the tests mentioned in Section 4 have no prior or in
progress work in the IETF: Control Path and Datapath Coupling Tests,
Noisy Neighbour Tests, characterization of acceleration technologies.
If new work is needed / proposed to be added for the BMWG scope and
framework it would be useful for BMWG to list these separately. 


Nits/editorial comments: 

1. What is called 'Deployment scenarios' from VS perspective in
Section 4 describe in fact different configurations of the SUT in BMWG
terms. It seems better to separate this second part of section 4 in a
separate section. If it belongs to an existing section it rather
belongs in 3 than in 4. 




From nobody Thu May 11 04:11:28 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 E66F612EC61; Thu, 11 May 2017 04:11:15 -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: draft-ietf-bmwg-vswitch-opnfv.all@ietf.org, ietf@ietf.org, bmwg@ietf.org,  dromasca@gmail.com
Subject: Opsdir last call review of draft-ietf-bmwg-vswitch-opnfv-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149450107581.16728.18142473358782662679@ietfa.amsl.com>
Date: Thu, 11 May 2017 04:11:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xrv21Z5gRkUhFGRb17AIvgUqTtw>
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, 11 May 2017 11:11:16 -0000

Reviewer: Dan Romascanu
Review result: Has Issues

This document describes describes the progress of the Open Platform
for NFV (OPNFV) project on virtual switch performance "VSPERF". That
project reuses the BMWG framework and specifications to benchmark
virtual switches implemented in general-purpose hardware. Some
differences with the benchmarking of specialized HW platforms are
identified and they may become work items for BMWG in the future. It's
a well written and clear document, but I have reservations about it
being published as an RFC, and I cannot find coverage for it in the WG
charter. I also have concerns that parts of the methodology used by
OPNFV break the BMWG principles, especially repeatability and
'black-box', and this is not clear enough articulated in the document.
 As I was assigned both OPS-DIR and Gen-ART reviews for this document,
I detailed the concerns in my Gen-ART review, they seem to belong
better there. 

>From an OPS-DIR perspective this document has no issues. If the
concerns in section 6 are addressed and caution is taken to isolate
the SUTs and benchmarking environments from the Internet or
operational intranets, there is no operational impact. If approved it
would be a useful tool for operators to get some information about how
benchmarking of OPNFV project products are being designed. 




From nobody Thu May 11 04:19:01 2017
Return-Path: <tore@fud.no>
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 5CC32126DED; Thu, 11 May 2017 04:18:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.798
X-Spam-Level: 
X-Spam-Status: No, score=0.798 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 OEfotGmLtbDB; Thu, 11 May 2017 04:18:51 -0700 (PDT)
Received: from mail.fud.no (mail.fud.no [IPv6:2a02:c0:4f0:bb02:f816:3eff:fed3:8342]) (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 AC63F12EBF6; Thu, 11 May 2017 04:16:53 -0700 (PDT)
Received: from [2a02:c0:2:1:1194:17:0:1029] (port=53692 helo=echo.ms.redpill-linpro.com) by mail.fud.no with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from <tore@fud.no>) id 1d8m5L-0004nc-DY; Thu, 11 May 2017 11:16:43 +0000
Date: Thu, 11 May 2017 13:16:42 +0200
From: Tore Anderson <tore@fud.no>
To: Joe Clarke <jclarke@cisco.com>
Cc: <ops-dir@ietf.org>, v6ops@ietf.org, ietf@ietf.org, draft-ietf-v6ops-v4v6-xlat-prefix.all@ietf.org
Subject: Re: Opsdir early review of draft-ietf-v6ops-v4v6-xlat-prefix-00
Message-ID: <20170511131642.1f408832@echo.ms.redpill-linpro.com>
In-Reply-To: <149373185172.9923.9255526962045750289@ietfa.amsl.com>
References: <149373185172.9923.9255526962045750289@ietfa.amsl.com>
X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-redhat-linux-gnu)
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/kOMs0VPJ9g0mxoSUXteVHfIpA7w>
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, 11 May 2017 11:18:53 -0000

Hi Joe, and thank you very much for your review. See in-line for my
comments.

* Joe Clarke <jclarke@cisco.com>

> You set out to define WKP as _the_ well-known prefix.  For the most
> part you adhere to this language in the draft.  However, in section 3,
> you state (highlighting added by me):
>=20
> Also, because the WKP is a /96, an operator preferring to use _a WKP_
> over an NSP can only do so for only one of his IPv4/IPv6 translation
> mechanisms.  All others must necessarily use an NSP.

Good catch! I changed =C2=ABa WKP=C2=BB to =C2=ABthe WKP=C2=BB.

> And then in section 5:
>=20
> When 64:ff9b:1::/48 or a more-specific prefix is used with the
> [RFC6052] algorithm, it is considered to be a Network-Specific
> Prefix.
>=20
> I believe what you're saying is that while you define 64:ff9b:1::/48
> as a WKP in _this_ draft, respective to RFC6052, it is an NSP.=20
> However, the combination of text in both sections was a bit confusing
> to me, and perhaps it would be useful to clarify your use of terms.

Actually I'm trying to not imply anywhere that 64:ff9b:1::/48 is a/the
=C2=ABWKP=C2=BB (although the previous point you brought up was a failure i=
n that
regard). The WKP is defined to be exactly 64:ff9b::/96 by RFC6052, and
I do not want to cause any ambiguity here.

I rewrote the paragraph in question as follows:

      Note that 64:ff9b:1::/48 (or any more-specific prefix) is distinct fr=
om
      the WKP 64:ff9b::/96. Therefore, the restrictions on the use of the W=
KP
      described in Section 3.1 of <xref target=3D"RFC6052"/> do not apply t=
o the
      use of 64:ff9b:1::/48.

Is that better?

> In Section 3, you state:
>=20
> Since the WKP 64:ff9b::/96 was reserved by [RFC6052], several new
> IPv4/IPv6 translation mechanisms have been defined by the IETF
>=20
> I think it would be useful to mention some of these new translation
> mechanisms as non-normative references, and if need be, show an
> example of interoperability.

How about: =C2=ABSince the WKP 64:ff9b::/96 was reserved by [RFC6052],
several new IPv4/IPv6 translation mechanisms have been defined by the
IETF, such as [RFC6146] and [RFC7915].=C2=BB ?

These two mechanisms do not interoperate at all, so they need different
translation prefixes if they're to be deployed in the same network.

> NITS:
>=20
> In your Abstract, you mention RFC6890, but this does not appear to be
> an xref to it, and it should be.

As mentioned by others, the idnits tool complains about xrefs in the
abstract. In any case I've just dropped the Updates on 6890 completely.

> In Section 4.1 you state:
>=20
> OLD:
> The second criterion is that the prefix length chosen is is a
> multiple of 16.  This ensures the prefix ends on a colon boundary
> when representing it in text, easing operator interaction with it.
>=20
> NEW:
> The second criterion is that the prefix length chosen is a
> multiple of 16.  This ensures the prefix ends on a colon boundary
> when representing it in text, easing operator interaction with it.
>=20
> (Removed a redundant "is".)

Fixed, thanks!

> In Section 4.1 again:
>=20
> OLD:
> The [RFC6052] algorithm specifies IPv4/IPv6 translation prefixes as
> short as /32.  In order to facilitate multiple instances of
> translation mechanisms using /32s, while at the same time aligning on
> a 16-bit boundary, it would be necessary to reserve a /16.  Doing so
> was however considered as too wasteful by the IPv6 Operations working
> group.
>=20
> NEW:
> The [RFC6052] algorithm specifies IPv4/IPv6 translation prefixes as
> short as /32.  In order to facilitate multiple instances of
> translation mechanisms using /32s, while at the same time aligning on
> a 16-bit boundary, it would be necessary to reserve a /16.  Doing so,
> however, was considered too wasteful by the IPv6 Operations working
> group.

Fixed, thanks!

> In Section 6:
>=20
> OLD:
> The Stateless IP/ICMP Translation algorithm [RFC7915] is one well-
> known algorithm that can operate in a checksum-neutral manner, when
> using the [RFC6052] algorithm for all of its address translations.
> However, in order to attain checksum neutrality is imperative that
> the translation prefix is chosen carefully.  Specifically, in order
> for a 96-bit [RFC6052] prefix to be checksum neutral, all the six
> 16-bit words in the prefix must add up to a multiple of 0xffff.
>=20
> NEW:
> The Stateless IP/ICMP Translation algorithm [RFC7915] is one well-
> known algorithm that can operate in a checksum-neutral manner, when
> using the [RFC6052] algorithm for all of its address translations.
> However, in order to attain checksum neutrality it is imperative that
> the translation prefix is chosen carefully.  Specifically, in order
> for a 96-bit [RFC6052] prefix to be checksum neutral, all the six
> 16-bit words in the prefix must add up to a multiple of 0xffff.
>=20
> (Added a missing "it".)

Fixed, thanks!

Tore


From nobody Thu May 11 04:24:10 2017
Return-Path: <tore@fud.no>
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 53B9912EBD6; Thu, 11 May 2017 04:24:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 47yhldYiOAMf; Thu, 11 May 2017 04:24:06 -0700 (PDT)
Received: from mail.fud.no (mail.fud.no [IPv6:2a02:c0:4f0:bb02:f816:3eff:fed3:8342]) (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 E29B4129789; Thu, 11 May 2017 04:22:01 -0700 (PDT)
Received: from [2a02:c0:2:1:1194:17:0:1029] (port=53752 helo=echo.ms.redpill-linpro.com) by mail.fud.no with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from <tore@fud.no>) id 1d8mAM-0004oD-Hi; Thu, 11 May 2017 11:21:54 +0000
Date: Thu, 11 May 2017 13:21:53 +0200
From: Tore Anderson <tore@fud.no>
To: David Farmer <farmer@umn.edu>
Cc: Fred Baker <fredbaker.ietf@gmail.com>, V6 Ops List <v6ops@ietf.org>, draft-ietf-v6ops-v4v6-xlat-prefix.all@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>
Subject: Re: [v6ops] Opsdir early review of draft-ietf-v6ops-v4v6-xlat-prefix-00
Message-ID: <20170511132153.269fd1d7@echo.ms.redpill-linpro.com>
In-Reply-To: <CAN-Dau0dVSL7cAZs2YWHpeU8rpU76bn00-7XiS2Rj+eOAOCS4A@mail.gmail.com>
References: <149373185172.9923.9255526962045750289@ietfa.amsl.com> <7789CECA-165C-417F-B485-03A154327AC1@gmail.com> <CAN-Dau0dVSL7cAZs2YWHpeU8rpU76bn00-7XiS2Rj+eOAOCS4A@mail.gmail.com>
X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JFx7rJJvzXr_MGTn_et5Rqfm_Gk>
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, 11 May 2017 11:24:07 -0000

Hi David,

> Prompted by this review, I reread the document and found what I think are a
> couple additional typos.
> 
> Section 4.2, Prefix Value, compares two options: 64:ff9a:ffff:ffff::/48 and
> 64:ff9b:1::/48. However in the fifth paragraph of the section, I believe
> there are two errant references to 64:ff9b:1::/96, that should instead
> be 64:ff9b:1::/48,
> unless I'm misunderstanding the intent of the paragraph.

You're absolutely right. Fixed. Thank you!

Tore


From nobody Thu May 11 05:18:03 2017
Return-Path: <ajs@anvilwalrusden.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 E08EC12EBB3 for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 05:18:01 -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, DKIM_SIGNED=0.1, DKIM_VALID=-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=yitter.info header.b=Vu/MlDli; dkim=pass (1024-bit key) header.d=yitter.info header.b=AcCxxz5t
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l4ZmhVc7PoE2 for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 05:17:59 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E2D412EC49 for <ietf@ietf.org>; Thu, 11 May 2017 05:15:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id AD46EBB834 for <ietf@ietf.org>; Thu, 11 May 2017 12:15:01 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1494504901; bh=J+93/DCxsNJQVnB4lAIlxzdRM4CW9Pic5/CG70vxRTE=; h=Date:From:To:Subject:References:In-Reply-To:From; b=Vu/MlDli2jzcn0rtGv/ZaOyzkyf5WaLPTIjY0+vYHjdNx3HxfFYp1EYXzUaDihTjJ 8x5bffT1E/KthABaFFEhKXx20KVOcUvANFi/FvIOSsEqJ6CWyixa479VWlYi8G9qzr HoysQeBvx83kKDz3E1Lc4m5q0gBVf0w1cGd7iMB8=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m8EcyXyB_3Tr for <ietf@ietf.org>; Thu, 11 May 2017 12:14:59 +0000 (UTC)
Date: Thu, 11 May 2017 08:14:58 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1494504899; bh=J+93/DCxsNJQVnB4lAIlxzdRM4CW9Pic5/CG70vxRTE=; h=Date:From:To:Subject:References:In-Reply-To:From; b=AcCxxz5tXZ4qxuDK4glOoz8CnznZFEZt09PyGancVXzTM5PSTdUaGP6tCjbSjCuQ2 PzDUJqRbPmxUr1PrXOlxGUulGfQHNEdxF8KUQBoORchV25w48039hUqgHJMJTwA60p OSYVIdEYJHkPWj1DxifPKpkTMstfQKpABDI9XbLc=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Registration for remote participation
Message-ID: <20170511121458.v62px5wrbh47zf3j@mx4.yitter.info>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <29052.1494439452@obiwan.sandelman.ca> <F4BF8089-0E62-4B3D-AE97-1F5ACC4196BC@stewe.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <F4BF8089-0E62-4B3D-AE97-1F5ACC4196BC@stewe.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IEfCI-tfOCqCJAvnr24FW1c3RYE>
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, 11 May 2017 12:18:02 -0000

On Wed, May 10, 2017 at 07:47:20PM +0000, Stephan Wenger wrote:
> 
> I’m in favor of validating the address, for example by sending some form of credential to it; without the credential, only listening/reading access is granted.  Doesn’t have to be bullet-proof, but using example@example.com shouldn’t work.  This is obviously in order to obtain one semi-traceable record of the participant.
> >

We don't do that for in-person participants, because we no longer even
collect the email address on the blue sheets.  (We do it for meeting
registration, of course, but we don't have a way to pair that with
participation in any given part of the meeting, so the IPR issue is
harder to argue by analogy here.)
 
> And 5) click-through of the Note Well (unless that’s done in some other phase of the remote participation, like when signing-in to meetecho).  Again for--I hope obvious--IPR related reasons.
> 

We _certainly_ don't do that for in-person meetings.  We put the Note
Well up and assume that anyone who is in the room and who makes a
Contribution in any way is aware of it.  Joining the meeting virtually
has the same property, no?

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Thu May 11 07:12:30 2017
Return-Path: <Italo.Busi@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 6030B1314C5; Thu, 11 May 2017 07:12:13 -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 PFFeE1pe30VQ; Thu, 11 May 2017 07:12: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 BF28E129AC7; Thu, 11 May 2017 07:05:52 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML712-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DMS65534; Thu, 11 May 2017 14:05:47 +0000 (GMT)
Received: from LHREML504-MBS.china.huawei.com ([10.201.109.59]) by LHREML712-CAH.china.huawei.com ([10.201.108.35]) with mapi id 14.03.0301.000;  Thu, 11 May 2017 15:05:43 +0100
From: Italo Busi <Italo.Busi@huawei.com>
To: "ietf@ietf.org" <ietf@ietf.org>
CC: "mpls@ietf.org" <mpls@ietf.org>, "draft-ietf-mpls-tp-shared-ring-protection@ietf.org" <draft-ietf-mpls-tp-shared-ring-protection@ietf.org>
Subject: RE: Last Call: <draft-ietf-mpls-tp-shared-ring-protection-05.txt> (Shared-Ring protection (MSRP) mechanism for ring topology) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-mpls-tp-shared-ring-protection-05.txt> (Shared-Ring protection (MSRP) mechanism for ring topology) to Proposed Standard
Thread-Index: AQHSwFHT6RfRe34k+0+8cXprdYx99aHvEoSQ
Date: Thu, 11 May 2017 14:05:42 +0000
Message-ID: <91E3A1BD737FDF4FA14118387FF6766B157346F2@lhreml504-mbs>
References: <149339519935.2881.8322243003635696392.idtracker@ietfa.amsl.com>
In-Reply-To: <149339519935.2881.8322243003635696392.idtracker@ietfa.amsl.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.46.243.209]
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.0A020205.59146FBC.02BE, 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: 2308c4b72cc3415953b99e51bfb7d306
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hyJmmV-v_PpNfcoePAK2ZBsyrro>
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, 11 May 2017 14:12:14 -0000

SSB0aGluayB0aGUgZHJhZnQgaXMgcmVhZHkgdG8gYmUgcHVibGlzaGVkLg0KDQpJIGhhdmUgcmVj
ZW50bHkgZGlzY3Vzc2VkIHdpdGggc29tZSBhdXRob3JzIG9mIHRoZSBkcmFmdCBzb21lIHF1ZXN0
aW9ucyBmb3IgY2xhcmlmaWNhdGlvbiBhbmQgaXQgbWlnaHQgYmUgd29ydGh3aGlsZSBjb25zaWRl
cmluZyBtaW5vciB0ZXh0IGNoYW5nZXMgcHJvcG9zZWQgYmVsb3cgdG8gZnVydGhlciBpbXByb3Zl
IHRleHQgY2xhcml0eS4NCg0KMSkgU2VjdGlvbiA0LjMuMS4yIGFuZCA0LjMuMi4yDQoNClRoZSB0
ZXh0IGRlc2NyaWJpbmcgZWdyZXNzIG5vZGUgZmFpbHVyZXMgaW1wbHkgdGhhdCwgYWxzbyBpbiBj
YXNlIG9mIHdyYXBwaW5nIGFuZCBzaG9ydC13cmFwcGluZywgdGhlIGluZ3Jlc3Mgbm9kZSwgd2hl
biBub3RpZmllZCAoYnkgUlBTKSBhYm91dCBlZ3Jlc3Mgbm9kZSBmYWlsdXJlLCB3aWxsIG5vdCBz
ZW5kIHRyYWZmaWMgdG8gZWl0aGVyIHRoZSB3b3JraW5nIG9yIHRoZSBwcm90ZWN0aW9uIHR1bm5l
bCAobGlrZSBpdCBkb2VzIHdpdGggc3RlZXJpbmcgcHJvdGVjdGlvbikuIEl0IG1pZ2h0IGJlIHdv
cnRod2hpbGUgYWRkaW5nIHNvbWUgZXhwbGljaXQgdGV4dA0KDQpPTEQgVEVYVCAoU2VjdGlvbiA0
LjMuMS4yKQ0KICAgSW4gb25lIHNwZWNpYWwgY2FzZSB3aGVyZSBub2RlIEQgZmFpbHMsIGFsbCB0
aGUgcmluZyB0dW5uZWxzIHdpdGgNCiAgIG5vZGUgRCBhcyBlZ3Jlc3Mgd2lsbCBiZWNvbWUgdW51
c2FibGUuIEhvd2V2ZXIsIGJlZm9yZSB0aGUgZmFpbHVyZQ0KICAgbG9jYXRpb24gaW5mb3JtYXRp
b24gaXMgcHJvcGFnYXRlZCB0byBhbGwgdGhlIHJpbmcgbm9kZXMsIHRoZQ0KICAgd3JhcHBpbmcg
cHJvdGVjdGlvbiBtZWNoYW5pc20gbWF5IGNhdXNlIHRlbXBvcmFyeSB0cmFmZmljIGxvb3A6DQoN
Ck5FVyBURVhUIChTZWN0aW9uIDQuMy4xLjIpDQogICBJbiBvbmUgc3BlY2lhbCBjYXNlIHdoZXJl
IG5vZGUgRCBmYWlscywgYWxsIHRoZSByaW5nIHR1bm5lbHMgd2l0aA0KICAgbm9kZSBEIGFzIGVn
cmVzcyB3aWxsIGJlY29tZSB1bnVzYWJsZS4gVGhlIGluZ3Jlc3Mgbm9kZSB3aWxsIHVwZGF0ZSBp
dHMgcmluZyBtYXAgYWNjb3JkaW5nIHRvIHJlY2VpdmVkIFJQUyBtZXNzYWdlcyBhbmQgZGV0ZXJt
aW5lIHRoYXQgdGhlIGVncmVzcyBub2RlIGlzIG5vdCByZWFjaGFibGUgdGh1cyBpdCB3aWxsIG5v
dCBzZW5kIHRyYWZmaWMgdG8gZWl0aGVyIHRoZSB3b3JraW5nIG9yIHRoZSBwcm90ZWN0aW9uIHR1
bm5lbC4gSG93ZXZlciwgYmVmb3JlIHRoZSBmYWlsdXJlDQogICBsb2NhdGlvbiBpbmZvcm1hdGlv
biBpcyBwcm9wYWdhdGVkIHRvIGFsbCB0aGUgcmluZyBub2RlcywgdGhlDQogICB3cmFwcGluZyBw
cm90ZWN0aW9uIG1lY2hhbmlzbSBtYXkgY2F1c2UgdGVtcG9yYXJ5IHRyYWZmaWMgbG9vcDoNCg0K
T0xEIFRFWFQgKFNlY3Rpb24gNC4zLjIuMikNCiAgIDwuLi4+IFdoZW4gbm9kZSBEDQogICBmYWls
cywgdHJhZmZpYyBvZiBMU1AxIGNhbm5vdCBiZSBwcm90ZWN0ZWQgYnkgYW55IHJpbmcgdHVubmVs
cyB3aGljaA0KICAgdXNlIG5vZGUgRCBhcyB0aGUgZWdyZXNzIG5vZGUuICBIb3dldmVyLCBiZWZv
cmUgdGhlIGZhaWx1cmUgbG9jYXRpb24NCiAgIGluZm9ybWF0aW9uIGlzIHByb3BhZ2F0ZWQgdG8g
YWxsIHRoZSByaW5nIG5vZGVzIHVzaW5nIHRoZSBSUFMNCiAgIHByb3RvY29sLCBub2RlIEMgc3dp
dGNoZXMgYWxsIHRoZSB0cmFmZmljIG9uIHRoZSB3b3JraW5nIHJpbmcgdHVubmVsIA0KICAgPC4u
Lj4NCg0KTkVXIFRFWFQgKFNlY3Rpb24gNC4zLjIuMikNCiAgIDwuLi4+IFdoZW4gbm9kZSBEDQog
ICBmYWlscywgdHJhZmZpYyBvZiBMU1AxIGNhbm5vdCBiZSBwcm90ZWN0ZWQgYnkgYW55IHJpbmcg
dHVubmVscyB3aGljaA0KICAgdXNlIG5vZGUgRCBhcyB0aGUgZWdyZXNzIG5vZGUuIFRoZSBpbmdy
ZXNzIG5vZGUgd2lsbCB1cGRhdGUgaXRzIHJpbmcgbWFwIGFjY29yZGluZyB0byByZWNlaXZlZCBS
UFMgbWVzc2FnZXMgYW5kIGRldGVybWluZSB0aGF0IHRoZSBlZ3Jlc3Mgbm9kZSBpcyBub3QgcmVh
Y2hhYmxlIHRodXMgaXQgd2lsbCBub3Qgc2VuZCB0cmFmZmljIHRvIGVpdGhlciB0aGUgd29ya2lu
ZyBvciB0aGUgcHJvdGVjdGlvbiB0dW5uZWwuIEhvd2V2ZXIsIGJlZm9yZSB0aGUgZmFpbHVyZSBs
b2NhdGlvbg0KICAgaW5mb3JtYXRpb24gaXMgcHJvcGFnYXRlZCB0byBhbGwgdGhlIHJpbmcgbm9k
ZXMgdXNpbmcgdGhlIFJQUw0KICAgcHJvdG9jb2wsIG5vZGUgQyBzd2l0Y2hlcyBhbGwgdGhlIHRy
YWZmaWMgb24gdGhlIHdvcmtpbmcgcmluZyB0dW5uZWwgDQogICA8Li4uPg0KDQoyKSAgU2VjdGlv
biA0LjMuMg0KDQpXaXRoIHNob3J0LXdyYXBwaW5nIHRoZSB0d28gdHJhZmZpYyBkaXJlY3Rpb25z
IG9mIHByb3RlY3RlZCBMU1BzIGFyZSBubyBsb25nZXIgY28tcm91dGVkIHVuZGVyIHByb3RlY3Rp
b24gc3dpdGNoaW5nIGNvbmRpdGlvbnMuIFRoaXMgc2hvdWxkIGJlIG1lbnRpb25lZC4NCg0KT0xE
IFRFWFQNCiAgIFdpdGggc2hvcnQgd3JhcHBpbmcgcHJvdGVjdGlvbiwgZGF0YSB0cmFmZmljIHN3
aXRjaGluZyBpcyBleGVjdXRlZA0KICAgb25seSBhdCB0aGUgbm9kZSB1cHN0cmVhbSB0byB0aGUg
ZmFpbHVyZSwgYW5kIGRhdGEgdHJhZmZpYyBsZWF2ZXMgdGhlDQogICByaW5nIGluIHRoZSBwcm90
ZWN0aW9uIHJpbmcgdHVubmVsIGF0IHRoZSBlZ3Jlc3Mgbm9kZS4gIFRoaXMgc2NoZW1lDQogICBj
YW4gcmVkdWNlIHRoZSBhZGRpdGlvbmFsIGxhdGVuY3kgYW5kIGJhbmR3aWR0aCBjb25zdW1wdGlv
biB3aGVuDQogICB0cmFmZmljIGlzIHN3aXRjaGVkIHRvIHRoZSBwcm90ZWN0aW9uIHBhdGguDQoN
Ck5FVyBURVhUDQogICBXaXRoIHNob3J0IHdyYXBwaW5nIHByb3RlY3Rpb24sIGRhdGEgdHJhZmZp
YyBzd2l0Y2hpbmcgaXMgZXhlY3V0ZWQNCiAgIG9ubHkgYXQgdGhlIG5vZGUgdXBzdHJlYW0gdG8g
dGhlIGZhaWx1cmUsIGFuZCBkYXRhIHRyYWZmaWMgbGVhdmVzIHRoZQ0KICAgcmluZyBpbiB0aGUg
cHJvdGVjdGlvbiByaW5nIHR1bm5lbCBhdCB0aGUgZWdyZXNzIG5vZGUuICBUaGlzIHNjaGVtZQ0K
ICAgY2FuIHJlZHVjZSB0aGUgYWRkaXRpb25hbCBsYXRlbmN5IGFuZCBiYW5kd2lkdGggY29uc3Vt
cHRpb24gd2hlbg0KICAgdHJhZmZpYyBpcyBzd2l0Y2hlZCB0byB0aGUgcHJvdGVjdGlvbiBwYXRo
LiBIb3dldmVyIHRoZSB0d28gZGlyZWN0aW9ucyBvZiBhIHByb3RlY3RlZCBiaWRpcmVjdGlvbmFs
IExTUCBhcmUgbm8gbG9uZ2VyIGNvLXJvdXRlZCB1bmRlciBwcm90ZWN0aW9uIHN3aXRjaGluZyBj
b25kaXRpb25zLg0KDQozKSBTZWN0aW9uIDQuMy4yDQoNClRoZSBkaWZmZXJlbmNlIGJldHdlZW4g
d3JhcHBpbmcgYW5kIHNob3J0LXdyYXBwaW5nIGlzIGluIHRoZSB3YXkgcHJvdGVjdGlvbiB0dW5u
ZWwgaXMgY29uZmlndXJlZC4NCg0KT0xEIFRFWFQNCiAgIEluIHRoZSB0cmFkaXRpb25hbCB3cmFw
cGluZyBzb2x1dGlvbiwgaW4gbm9ybWFsIHN0YXRlIHRoZSBwcm90ZWN0aW9uDQogICByaW5nIHR1
bm5lbCBpcyBhIGNsb3NlZCByaW5nLCB3aGlsZSBpbiB0aGUgc2hvcnQgd3JhcHBpbmcgc29sdXRp
b24sDQogICB0aGUgcHJvdGVjdGlvbiByaW5nIHR1bm5lbCBpcyBlbmRlZCBhdCB0aGUgZWdyZXNz
IG5vZGUsIHdoaWNoIGlzDQogICBzaW1pbGFyIHRvIHRoZSB3b3JraW5nIHJpbmcgdHVubmVsLg0K
DQpORVcgVEVYVA0KICAgSW4gdGhlIHRyYWRpdGlvbmFsIHdyYXBwaW5nIHNvbHV0aW9uLCB0aGUg
cHJvdGVjdGlvbg0KICAgcmluZyB0dW5uZWwgaXMgY29uZmlndXJlZCBhcyBhIGNsb3NlZCByaW5n
LCB3aGlsZSBpbiB0aGUgc2hvcnQgd3JhcHBpbmcgc29sdXRpb24sDQogICB0aGUgcHJvdGVjdGlv
biByaW5nIHR1bm5lbCBpcyBjb25maWd1cmVkIGFzIGVuZGVkIGF0IHRoZSBlZ3Jlc3Mgbm9kZSwg
d2hpY2ggaXMNCiAgIHNpbWlsYXIgdG8gdGhlIHdvcmtpbmcgcmluZyB0dW5uZWwuDQoNClRoYW5r
cywgSXRhbG8NCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IFRoZSBJRVNHIFtt
YWlsdG86aWVzZy1zZWNyZXRhcnlAaWV0Zi5vcmddIA0KU2VudDogc2FiYXRvIDI5IGFwcmlsZSAy
MDE3IDAwOjAwDQpUbzogSUVURi1Bbm5vdW5jZQ0KQ2M6IG1wbHNAaWV0Zi5vcmc7IGRiMzU0NkBh
dHQuY29tOyBtcGxzLWNoYWlyc0BpZXRmLm9yZzsgZHJhZnQtaWV0Zi1tcGxzLXRwLXNoYXJlZC1y
aW5nLXByb3RlY3Rpb25AaWV0Zi5vcmc7IEVyaWMgR3JheTsgRXJpYy5HcmF5QEVyaWNzc29uLmNv
bQ0KU3ViamVjdDogTGFzdCBDYWxsOiA8ZHJhZnQtaWV0Zi1tcGxzLXRwLXNoYXJlZC1yaW5nLXBy
b3RlY3Rpb24tMDUudHh0PiAoU2hhcmVkLVJpbmcgcHJvdGVjdGlvbiAoTVNSUCkgbWVjaGFuaXNt
IGZvciByaW5nIHRvcG9sb2d5KSB0byBQcm9wb3NlZCBTdGFuZGFyZA0KDQoNClRoZSBJRVNHIGhh
cyByZWNlaXZlZCBhIHJlcXVlc3QgZnJvbSB0aGUgTXVsdGlwcm90b2NvbCBMYWJlbCBTd2l0Y2hp
bmcgV0cNCihtcGxzKSB0byBjb25zaWRlciB0aGUgZm9sbG93aW5nIGRvY3VtZW50Og0KLSAnU2hh
cmVkLVJpbmcgcHJvdGVjdGlvbiAoTVNSUCkgbWVjaGFuaXNtIGZvciByaW5nIHRvcG9sb2d5Jw0K
ICA8ZHJhZnQtaWV0Zi1tcGxzLXRwLXNoYXJlZC1yaW5nLXByb3RlY3Rpb24tMDUudHh0PiBhcyBQ
cm9wb3NlZCBTdGFuZGFyZA0KDQpUaGUgSUVTRyBwbGFucyB0byBtYWtlIGEgZGVjaXNpb24gaW4g
dGhlIG5leHQgZmV3IHdlZWtzLCBhbmQgc29saWNpdHMgZmluYWwgY29tbWVudHMgb24gdGhpcyBh
Y3Rpb24uIFBsZWFzZSBzZW5kIHN1YnN0YW50aXZlIGNvbW1lbnRzIHRvIHRoZSBpZXRmQGlldGYu
b3JnIG1haWxpbmcgbGlzdHMgYnkgMjAxNy0wNS0xMi4gRXhjZXB0aW9uYWxseSwgY29tbWVudHMg
bWF5IGJlIHNlbnQgdG8gaWVzZ0BpZXRmLm9yZyBpbnN0ZWFkLiBJbiBlaXRoZXIgY2FzZSwgcGxl
YXNlIHJldGFpbiB0aGUgYmVnaW5uaW5nIG9mIHRoZSBTdWJqZWN0IGxpbmUgdG8gYWxsb3cgYXV0
b21hdGVkIHNvcnRpbmcuDQoNCkFic3RyYWN0DQoNCg0KICAgVGhpcyBkb2N1bWVudCBkZXNjcmli
ZXMgcmVxdWlyZW1lbnRzLCBhcmNoaXRlY3R1cmUgYW5kIHNvbHV0aW9ucyBmb3INCiAgIE1QTFMt
VFAgU2hhcmVkIFJpbmcgUHJvdGVjdGlvbiAoTVNSUCkgaW4gYSByaW5nIHRvcG9sb2d5IGZvciBw
b2ludC0NCiAgIHRvLXBvaW50IChQMlApIHNlcnZpY2VzLiAgVGhlIE1TUlAgbWVjaGFuaXNtIGlz
IGRlc2NyaWJlZCB0byBtZWV0IHRoZQ0KICAgcmluZyBwcm90ZWN0aW9uIHJlcXVpcmVtZW50cyBh
cyBkZXNjcmliZWQgaW4gUkZDIDU2NTQuICBUaGlzIGRvY3VtZW50DQogICBkZWZpbmVzIHRoZSBS
aW5nIFByb3RlY3Rpb24gU3dpdGNoIChSUFMpIFByb3RvY29sIHRoYXQgaXMgdXNlZCB0bw0KICAg
Y29vcmRpbmF0ZSB0aGUgcHJvdGVjdGlvbiBiZWhhdmlvciBvZiB0aGUgbm9kZXMgb24gTVBMUyBy
aW5nLg0KDQoNCg0KDQoNClRoZSBmaWxlIGNhbiBiZSBvYnRhaW5lZCB2aWENCmh0dHBzOi8vZGF0
YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtbXBscy10cC1zaGFyZWQtcmluZy1wcm90
ZWN0aW9uLw0KDQpJRVNHIGRpc2N1c3Npb24gY2FuIGJlIHRyYWNrZWQgdmlhDQpodHRwczovL2Rh
dGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLW1wbHMtdHAtc2hhcmVkLXJpbmctcHJv
dGVjdGlvbi9iYWxsb3QvDQoNClRoZSBmb2xsb3dpbmcgSVBSIERlY2xhcmF0aW9ucyBtYXkgYmUg
cmVsYXRlZCB0byB0aGlzIEktRDoNCg0KICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9p
cHIvMjY4MC8NCiAgIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvaXByLzI2ODEvDQogICBo
dHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2lwci8yNjgyLw0KICAgaHR0cHM6Ly9kYXRhdHJh
Y2tlci5pZXRmLm9yZy9pcHIvMjY4My8NCg0KDQoNCg0KDQoNCg==


From nobody Thu May 11 07:34: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 CF7C2129AC4 for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 07:34:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 pRC_nMuMixgQ for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 07:34: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 6E49312EC97 for <ietf@ietf.org>; Thu, 11 May 2017 07:27:47 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id B2289E1AB; Thu, 11 May 2017 10:54:09 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B4832636BB; Thu, 11 May 2017 10:27:46 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: John C Klensin <john-ietf@jck.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: Registration for remote participation
In-Reply-To: <B2B236B5CDB82EFDBED9923E@PSB>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <29052.1494439452@obiwan.sandelman.ca> <B2B236B5CDB82EFDBED9923E@PSB>
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, 11 May 2017 10:27:46 -0400
Message-ID: <15237.1494512866@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BiAKyphRTri33i8kCnC_124POvw>
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, 11 May 2017 14:34:04 -0000

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


John C Klensin <john-ietf@jck.com> wrote:
    > --On Wednesday, May 10, 2017 14:04 -0400 Michael Richardson
    > <mcr+ietf@sandelman.ca> wrote:

    >> ...
    >> Are we validating the email address in some way?
    >> If we are not, I don't see the point of the *-required in any
    >> of those places.
    >> ...

    > Michael (and others),

    > I'm happy to let the IESG manage this rather than getting into
    > an orgy of nit-picking and micro-managing, but I think there are
    > at least two separate reasons for wanting remote participants to
    > register and that, which the desired information may overlap,

I'm not arguing against registration, but rather, I want to consciously
say that we are validating the registration!
I'd be quite happy to register via the datatracker, for instance.  A great
use for OAUTH2.

I agree with all your other points.


--
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+93Q3WUFAlkUdOIACgkQgItw+93Q
3WUh5Af/QpeXFck8TzyUfZaJxMRMauSzzmi0dbAxz4EJIb3uew8zUo3iGMxWAHGH
5E4W4xGJBZVpsLMkXjoXqkGcpHSqOqhfaJTFVREOUPLb3hhO2WOTACceNj+oIiyl
190TsbN6HKyTPbpWZLB+2/8BkldKIFpsSpNJ3khOc9q4T58dzHSYChfoc0MmU6ZS
LG93bbHpxO4vIS9k1BNnb4PSQN5dZ74Ow0yZkj7porWR+qK/jHoqtRJn/za6AloQ
NNGepnbS7rUHNtpmtb3RXLDWrtQrl3mnys9FMCz4MxiPRguhl+tlo8wEysmqMGX1
nkR/9jk/TkHN8aeB2lM2mLAiaSEK0g==
=39Tb
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu May 11 10:06:31 2017
Return-Path: <acmorton@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 3D24D12948E; Thu, 11 May 2017 10:06:10 -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 J8J-RD_U1eNV; Thu, 11 May 2017 10:06:07 -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 CF8CA12EBAE; Thu, 11 May 2017 10:01:10 -0700 (PDT)
Received: from pps.filterd (m0049295.ppops.net [127.0.0.1]) by m0049295.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v4BGuWhv004428; Thu, 11 May 2017 13:01:08 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049295.ppops.net-00191d01. with ESMTP id 2acrmw7df8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 11 May 2017 13:01:07 -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 v4BH12Ks024014; Thu, 11 May 2017 13:01:05 -0400
Received: from mlpi408.sfdc.sbc.com (mlpi408.sfdc.sbc.com [130.9.128.240]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v4BH0h80022033 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 11 May 2017 13:00:57 -0400
Received: from clpi183.sldc.sbc.com (clpi183.sldc.sbc.com [135.41.1.46]) by mlpi408.sfdc.sbc.com (RSA Interceptor); Thu, 11 May 2017 17:00:29 GMT
Received: from sldc.sbc.com (localhost [127.0.0.1]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id v4BH0Ssq007091; Thu, 11 May 2017 12:00:29 -0500
Received: from mail-azure.research.att.com (mail-azure.research.att.com [135.207.255.18]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id v4BH0L1n006154; Thu, 11 May 2017 12:00:21 -0500
Received: from exchange.research.att.com (njmtcas2.research.att.com [135.207.255.47]) by mail-azure.research.att.com (Postfix) with ESMTP id A3FE3E08B7; Thu, 11 May 2017 13:00:20 -0400 (EDT)
Received: from njmtexg4.research.att.com ([fe80::8cd:baa3:219e:5bd4]) by njmtcas2.research.att.com ([fe80::d550:ec84:f872:cad9%15]) with mapi id 14.03.0319.002; Thu, 11 May 2017 13:00:20 -0400
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: Dan Romascanu <dromasca@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-bmwg-vswitch-opnfv.all@ietf.org" <draft-ietf-bmwg-vswitch-opnfv.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "bmwg@ietf.org" <bmwg@ietf.org>
Subject: RE: Genart last call review of draft-ietf-bmwg-vswitch-opnfv-03
Thread-Topic: Genart last call review of draft-ietf-bmwg-vswitch-opnfv-03
Thread-Index: AQHSykaQpvZtcVQqDEiJ+tr7bcWy3KHvK1EQ
Date: Thu, 11 May 2017 17:00:20 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF25F9B072@njmtexg4.research.att.com>
References: <149450075072.16690.14546662616864459158@ietfa.amsl.com>
In-Reply-To: <149450075072.16690.14546662616864459158@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.214.90]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-05-11_13:, , 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-1703280000 definitions=main-1705110087
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8Z3WOpRbUR_k3j7Pyduk251iJcM>
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, 11 May 2017 17:06:10 -0000

SGkgRGFuLA0KcGxlYXNlIHNlZSByZXBsaWVzLCBbQUNNXSwgYmVsb3cuDQoNCj4gLS0tLS1Pcmln
aW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogRGFuIFJvbWFzY2FudSBbbWFpbHRvOmRyb21hc2Nh
QGdtYWlsLmNvbV0NCj4gU2VudDogVGh1cnNkYXksIE1heSAxMSwgMjAxNyA3OjA2IEFNDQo+IFRv
OiBnZW4tYXJ0QGlldGYub3JnDQo+IENjOiBkcmFmdC1pZXRmLWJtd2ctdnN3aXRjaC1vcG5mdi5h
bGxAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmc7DQo+IGJtd2dAaWV0Zi5vcmc7IGRyb21hc2NhQGdt
YWlsLmNvbQ0KPiBTdWJqZWN0OiBHZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRm
LWJtd2ctdnN3aXRjaC1vcG5mdi0wMw0KPiANCj4gUmV2aWV3ZXI6IERhbiBSb21hc2NhbnUNCj4g
UmV2aWV3IHJlc3VsdDogQWxtb3N0IFJlYWR5DQo+IA0KPiBJIGFtIHRoZSBhc3NpZ25lZCBHZW4t
QVJUIHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBUaGUgR2VuZXJhbCBBcmVhDQo+IFJldmlldyBU
ZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQN
Cj4gYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLiAgUGxlYXNlIHRyZWF0IHRoZXNlIGNv
bW1lbnRzIGp1c3QNCj4gbGlrZSBhbnkgb3RoZXIgbGFzdCBjYWxsIGNvbW1lbnRzLg0KPiANCj4g
Rm9yIG1vcmUgaW5mb3JtYXRpb24sIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPiANCj4gPGh0dHBz
Oi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRwcy0NCj4gM0FfX3RyYWMu
aWV0Zi5vcmdfdHJhY19nZW5fd2lraV9HZW5BcnRmYXEmZD1Ed0lDYVEmYz1MRllaLQ0KPiBvOV9I
VU1lTVRTUWljdmpJZyZyPU9mc1N1OGtUSWx0VnlEMW9MNzJjQncmbT1OVFZsTEJOLQ0KPiBMM3U5
ekdQSG1fQ05WY1hXN19PR1g4XzE4Q3RhQWFsWmluMCZzPTJIci0NCj4gZGhLYURISWd1WTdXOTd6
MzNSbEtqcVBEdG1vWW1NMi1qV3JiUy1vJmU9ID4uDQo+IA0KPiBEb2N1bWVudDogZHJhZnQtaWV0
Zi1ibXdnLXZzd2l0Y2gtb3BuZnYtMDMNCj4gUmV2aWV3ZXI6IERhbiBSb21hc2NhbnUNCj4gUmV2
aWV3IERhdGU6IDIwMTctMDUtMTENCj4gSUVURiBMQyBFbmQgRGF0ZTogMjAxNy0wNS0xNQ0KPiBJ
RVNHIFRlbGVjaGF0IGRhdGU6IE5vdCBzY2hlZHVsZWQgZm9yIGEgdGVsZWNoYXQNCj4gDQo+IFN1
bW1hcnk6DQo+IA0KPiBBbG1vc3QgUmVhZHkuDQo+IA0KPiBUaGlzIGRvY3VtZW50IGRlc2NyaWJl
cyBkZXNjcmliZXMgdGhlIHByb2dyZXNzIG9mIHRoZSBPcGVuIFBsYXRmb3JtDQo+IGZvciBORlYg
KE9QTkZWKSBwcm9qZWN0IG9uIHZpcnR1YWwgc3dpdGNoIHBlcmZvcm1hbmNlICJWU1BFUkYiLiBU
aGF0DQo+IHByb2plY3QgcmV1c2VzIHRoZSBCTVdHIGZyYW1ld29yayBhbmQgc3BlY2lmaWNhdGlv
bnMgdG8gYmVuY2htYXJrDQo+IHZpcnR1YWwgc3dpdGNoZXMgaW1wbGVtZW50ZWQgaW4gZ2VuZXJh
bC1wdXJwb3NlIGhhcmR3YXJlLiBTb21lDQo+IGRpZmZlcmVuY2VzIHdpdGggdGhlIGJlbmNobWFy
a2luZyBvZiBzcGVjaWFsaXplZCBIVyBwbGF0Zm9ybXMgYXJlDQo+IGlkZW50aWZpZWQgYW5kIHRo
ZXkgbWF5IGJlY29tZSB3b3JrIGl0ZW1zIGZvciBCTVdHIGluIHRoZSBmdXR1cmUuIEl0J3MNCj4g
YSB3ZWxsIHdyaXR0ZW4gYW5kIGNsZWFyIGRvY3VtZW50LCBidXQgSSBoYXZlIHJlc2VydmF0aW9u
cyBhYm91dCBpdA0KPiBiZWluZyBwdWJsaXNoZWQgYXMgYW4gUkZDLCBhbmQgSSBjYW5ub3QgZmlu
ZCBjb3ZlcmFnZSBmb3IgaXQgaW4gdGhlIFdHDQo+IGNoYXJ0ZXIuIEkgYWxzbyBoYXZlIGNvbmNl
cm5zIHRoYXQgcGFydHMgb2YgdGhlIG1ldGhvZG9sb2d5IHVzZWQgYnkNCj4gT1BORlYgYnJlYWsg
dGhlIEJNV0cgcHJpbmNpcGxlcywgZXNwZWNpYWxseSByZXBlYXRhYmlsaXR5IGFuZA0KPiAnYmxh
Y2stYm94JywgYW5kIHRoaXMgaXMgbm90IGNsZWFyIGVub3VnaCBhcnRpY3VsYXRlZCBpbiB0aGUg
ZG9jdW1lbnQuDQpbQUNNXSANCk9rLCBsZXQncyBhZGRyZXNzIHlvdXIgc3BlY2lmaWMgaXNzdWVz
LCBhbmQgY29tZSBiYWNrIHRvIHlvdXIgcmVzZXJ2YXRpb25zLg0KDQo+IA0KPiANCj4gTWFqb3Ig
aXNzdWVzOg0KPiANCj4gMS4gSXQgaXMgbm90IGNsZWFyIHRvIG1lIHdoeSB0aGlzIGRvY3VtZW50
IG5lZWRzIHRvIGJlIHB1Ymxpc2hlZCBhcyBhbg0KPiBSRkMuIFRoZSBpbnRyb2R1Y3Rpb24gc2F5
czogJ1RoaXMgbWVtbyBkZXNjcmliZXMgdGhlIHByb2dyZXNzIG9mIHRoZQ0KPiBPcGVuIFBsYXRm
b3JtIGZvciBORlYgKE9QTkZWKSBwcm9qZWN0IG9uIHZpcnR1YWwgc3dpdGNoIHBlcmZvcm1hbmNl
DQo+ICJWU1BFUkYiLiAgVGhpcyBwcm9qZWN0IGludGVuZHMgdG8gYnVpbGQgb24gdGhlIGN1cnJl
bnQgYW5kIGNvbXBsZXRlZA0KPiB3b3JrIG9mIHRoZSBCZW5jaG1hcmtpbmcgTWV0aG9kb2xvZ3kg
V29ya2luZyBHcm91cCBpbiBJRVRGLCBieQ0KPiByZWZlcmVuY2luZyBleGlzdGluZyBsaXRlcmF0
dXJlLicgV2h5IHNob3VsZCB0aGUgV0cgYW5kIHRoZSBJRVNHDQo+IGludmVzdCByZXNvdXJjZXMg
aW4gcHVibGlzaGluZyB0aGlzLCB3aHkgYW4gSS1EIG9yIGFuIEluZGVwZW5kZW50DQo+IFN0cmVh
bSBSRkMgaXMgbm90IHN1ZmZpY2llbnQ/IA0KW0FDTV0gDQpUaGUgV0cgY29uc2lkZXJlZCBhbmQg
ZGlzY3Vzc2VkIHRoaXMgZG9jdW1lbnQgb3ZlciAzIHJldmlzaW9ucw0KYW5kIGEgeWVhciBvZiB0
aW1lIGJlZm9yZSByZWFjaGluZyBjb25zZW5zdXMgdG8gZGV2ZWxvcCBpdCBmdXJ0aGVyDQphcyBh
IGNoYXJ0ZXJlZCBpdGVtLCBzbyB0aGlzIGRlY2lzaW9uIHdhcyBub3QgdGFrZW4gbGlnaHRseS4N
ClNlZSBtb3JlIGJlbG93Lg0KDQo+IFRoZSBXRyBjaGFydGVyIHNheXMgc29tZXRoaW5nIGFib3V0
Og0KPiAnVk5GIGFuZCBSZWxhdGVkIEluZnJhc3RydWN0dXJlIEJlbmNobWFya2luZzogQmVuY2ht
YXJraW5nDQo+IE1ldGhvZG9sb2dpZXMgaGF2ZSByZWxpYWJseSBjaGFyYWN0ZXJpemVkIG1hbnkg
cGh5c2ljYWwgZGV2aWNlcy4gVGhpcw0KPiB3b3JrIGl0ZW0gZXh0ZW5kcyBhbmQgZW5oYW5jZXMg
dGhlIG1ldGhvZHMgdG8gdmlydHVhbCBuZXR3b3JrDQo+IGZ1bmN0aW9ucyAoVk5GKSBhbmQgdGhl
aXIgdW5pcXVlIHN1cHBvcnRpbmcgaW5mcmFzdHJ1Y3R1cmUuIEEgZmlyc3QNCj4gZGVsaXZlcmFi
bGUgZnJvbSB0aGlzIGFjdGl2aXR5IHdpbGwgYmUgYSBkb2N1bWVudCB0aGF0IGNvbnNpZGVycyB0
aGUNCj4gbmV3IGJlbmNobWFya2luZyBzcGFjZSB0byBlbnN1cmUgdGhhdCBjb21tb24gaXNzdWVz
IGFyZSByZWNvZ25pemVkDQo+IGZyb20gdGhlIHN0YXJ0LCB1c2luZyBiYWNrZ3JvdW5kIG1hdGVy
aWFscyBmcm9tIGluZHVzdHJ5IGFuZCBTRE9zDQo+IChlLmcuLCBJRVRGLCBFVFNJIE5GVikuJy4g
SSBkbyBub3QgYmVsaWV2ZSB0aGF0IHRoaXMgZG9jdW1lbnQgY292ZXJzDQo+IHRoZSBpbnRlbnQg
b2YgdGhlIGNoYXJ0ZXIsIGFzIGl0IGZvY3VzZWQgb24gb25lIG9yZ2FuaXphdGlvbiBvbmx5Lg0K
W0FDTV0gDQpJJ20gc29ycnksIGJ1dCBoZXJlIHlvdSBhcmUgbWlzdGFrZW4uIFRoZSBkb2N1bWVu
dCB0aGF0IHNhdGlzZmllZA0KdGhlICJmaXJzdCBkZWxpdmVyYWJsZSAuLi4gZG9jdW1lbnQgdGhh
dCBjb25zaWRlcnMgdGhlIG5ldyBiZW5jaG1hcmtpbmcgc3BhY2UiDQppczogaHR0cHM6Ly90b29s
cy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtYm13Zy12aXJ0dWFsLW5ldC0wNQ0KdGl0bGVkOiBD
b25zaWRlcmF0aW9ucyBmb3IgQmVuY2htYXJraW5nIFZpcnR1YWwgTmV0d29yayBGdW5jdGlvbnMg
YW5kIFRoZWlyIEluZnJhc3RydWN0dXJlDQp3aGljaCBoYXMgYmVlbiBzdWJtaXR0ZWQgdG8gSUVT
RyBhbmQgYXBwcm92ZWQgZm9yIHB1YmxpY2F0aW9uLg0KRnVydGhlciwgdGhlIGN1cnJlbnQgZHJh
ZnQgKGRyYWZ0LWlldGYtYm13Zy12c3dpdGNoLW9wbmZ2LTAzKQ0KcmVmZXJlbmNlcyB0aGUgYXBw
cm92ZWQgIkNvbnNpZGVyYXRpb25zIiBkcmFmdCBpbiBTZWN0aW9uIDMNCihhcyBkb2VzIGFsbW9z
dCBldmVyeSByZWxhdGVkIEluZHVzdHJ5IHNwZWMgSSdtIGF3YXJlIG9mKS4NCg0KVGhlIEJNV0cg
Q2hhcnRlciBjb250aW51ZXM6DQogIEJlbmNobWFya3MgZm9yIHBsYXRmb3JtIGNhcGFjaXR5IGFu
ZCBwZXJmb3JtYW5jZSBjaGFyYWN0ZXJpc3RpY3Mgb2YNCiAgdmlydHVhbCByb3V0ZXJzLCBzd2l0
Y2hlcywgYW5kIHJlbGF0ZWQgY29tcG9uZW50cyB3aWxsIGZvbGxvdywgaW5jbHVkaW5nDQogIGNv
bXBhcmlzb25zIGJldHdlZW4gcGh5c2ljYWwgYW5kIHZpcnR1YWwgbmV0d29yayBmdW5jdGlvbnMu
IEluIG1hbnkgY2FzZXMsDQogIHRoZSB0cmFkaXRpb25hbCBiZW5jaG1hcmtzIHNob3VsZCBiZSBh
cHBsaWNhYmxlIHRvIFZORnMsIGJ1dCB0aGUgbGFiDQogIHNldC11cHMsIGNvbmZpZ3VyYXRpb25z
LCBhbmQgbWVhc3VyZW1lbnQgbWV0aG9kcyB3aWxsIGxpa2VseSBuZWVkIHRvDQogIGJlIHJldmlz
ZWQgb3IgZW5oYW5jZWQuDQoNClRoaXMgZHJhZnQgY29uc3RpdHV0ZXMgb25lIG9mIHNldmVyYWwg
Zm9sbG93LW9uIGVmZm9ydHMsIGFwcHJvYWNoaW5nIA0KdGhlIHByb2JsZW0gZXhhY3RseSBhcyB3
ZSBkZXNjcmliZWQgaW4gdGhlIGxhc3Qgc2VudGVuY2UgYWJvdmUuDQoNCkFuIGFzcGVjdCBvZiBJ
bmR1c3RyeSBjb2xsYWJvcmF0aW9uIHRoYXQgd2UgZGlkIG5vdCBhbnRpY2lwYXRlIGluIHRoZSAN
CkJNV0cgQ2hhcnRlciBpcyBvdXIgY3VycmVudCBpbnRlcmFjdGlvbnMgd2l0aCBPcGVuIFNvdXJj
ZSBDb21tdW5pdGllcy4NClRoZSBjdXJyZW50IENoYXJ0ZXIgd2FzIGFwcHJvdmVkIGluIEp1bmUg
MjAxNCwgdGhlbiBPUE5GViB3YXMgZm91bmRlZCANCm9uIFNlcHRlbWJlciAzMCwgMjAxNCBbMF0g
YW5kIHRoZSBWU1BFUkYgUHJvamVjdCB3YXMgY3JlYXRlZCBvbg0KRGVjIDE2LCAyMDE0LCBzbyB3
ZSBkaWQgbm90IGFudGljaXBhdGUgZXh0ZW5zaXZlIGNvbGxhYm9yYXRpb24gb24NCnRoaXMgYW5k
IG90aGVyIGJlbmNobWFya2luZyB0b3BpY3MuIA0KDQoNCg0KPiANCj4gMi4gSW4gc2VjdGlvbiAz
IHRoZXJlICdyZXBlYXRhYmlsaXR5JyBpcyBtZW50aW9uZWQsIHdoaWxlDQo+IGFja25vd2xlZGdp
bmcgdGhhdCBpbiBhIHZpcnR1YWwgZW52aXJvbm1lbnQgdGhlcmUgaXMgbm8gZ3VhcmFudGVlIGFu
ZA0KPiBhY3R1YWxseSBubyB3YXkgdG8ga25vdyB3aGF0IG90aGVyIGFwcGxpY2F0aW9ucyBhcmUg
YmVpbmcgcnVuLg0KW0FDTV0gDQpTZWU6DQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJh
ZnQtaWV0Zi1ibXdnLXZpcnR1YWwtbmV0LTA1I3NlY3Rpb24tMy40DQoNClRoZXJlIGFyZSBjZXJ0
YWlubHkgd2F5cyB0byBhc3Nlc3MgdGhlIGN1cnJlbnQgc2V0IG9mIHByb2Nlc3Nlcw0KYXQgYSBw
YXJ0aWN1bGFyIHRpbWUuIFRoZSBTb2Z0d2FyZSBjb25maWd1cmF0aW9uIHBhcmFtZXRlcnMgaW4N
ClNlY3Rpb24gMy4zIGFyZSBpbnRlbmRlZCB0byBjYXB0dXJlIHRoaXMgYXNwZWN0IGFzIHBhcnQg
b2Ygc2V0LXVwLg0KQXQgdGhlIHNhbWUgdGltZSwgdGhlcmUgd2lsbCBiZSBjaGFsbGVuZ2VzIHRv
IGFzc2VzcyB0aGUgRFVUDQpwZXJmb3JtYW5jZSB3aGVuIHJlc291cmNlcyBhcmUgZnVsbHkgc2hh
cmVkLCBhbmQgbmV3IHRlc3RpbmcNCnN0cmF0ZWdpZXMgd2lsbCBiZSBuZWVkZWQ6DQpodHRwczov
L3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1ibXdnLXZpcnR1YWwtbmV0LTA1I3NlY3Rp
b24tMy4zDQoNCg0KPiBNZWFzdXJpbmcgcGFyYW1ldGVycyBhcyB0aGUgb25lcyBsaXN0ZWQgaW4g
My4zIHByb3ZpZGVzIGp1c3QgcGFydCBvZg0KPiB0aGUgYW5zd2VyLCBhbmQgdGhleSBhcmUgaW50
ZXJuYWwgcGFyYW1ldGVycyB0byB0aGUgU1VULiANCltBQ01dIA0KWWVzLCBrbm93aW5nIHRoZSB0
ZXN0ZWQgY29uZmlndXJhdGlvbiBpcyBhIGNyaXRpY2FsIHBpbGxhciANCnN1cHBvcnRpbmcgcmVw
ZWF0YWJpbGl0eSAodGhlc2UgaXRlbXMgYXJlIG5vdCBtZWFzdXJlZCwgYnV0IGNvbmZpZ3VyZWQp
LA0KYW5kIHdoeSB3ZSBwcm92aWRlZCB0aGlzIHNlY3Rpb24uDQoNCj4gQWxzbywgdGhlDQo+IGRp
ZmZlcmVudCBkZXBsb3ltZW50IHNjZW5hcmlvcyBpbiBzZWN0aW9uIDQgcmVxdWlyZSBkaWZmZXJl
bnQNCj4gY29uZmlndXJhdGlvbnMgZm9yIHRoZSBTVVQsIHRodXMgYnJlYWtpbmcgdGhlICdibGFj
ay1ib3gnIHByaW5jaXBsZS4NCltBQ01dIA0KU3BlY2lmeWluZyBEVVQgY29uZmlndXJhdGlvbiBk
b2VzIG5vdCBicmVhayBhbnkgcGFydCBvZiB0aGUgDQpibGFjay1ib3ggcHJpbmNpcGxlLCB3aGlj
aCBlc3RhYmxpc2hlcyB0aGF0IGJlbmNobWFyayBtZWFzdXJlbWVudHMNCndpbGwgYmUgYmFzZWQg
b24gZXh0ZXJuYWxseSBvYnNlcnZhYmxlIHBoZW5vbWVuYS4gU2VlOg0KaHR0cHM6Ly90b29scy5p
ZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtYm13Zy12aXJ0dWFsLW5ldC0wNSNzZWN0aW9uLTQuMg0K
DQpQcmV2aW91cyBCTVdHIFJGQ3MgaGF2ZSBpZGVudGlmaWVkIHRoZSBjcml0aWNhbCBjb25maWd1
cmF0aW9uDQpwYXJhbWV0ZXJzIG9mIHRoZSBEVVQsIHN1Y2ggYXMgdGhlIG51bWJlciBhbmQgdHlw
ZSBvZiANCm5ldHdvcmsgaW50ZXJmYWNlcywgdGhlIGFycmFuZ2VtZW50IG9mIERVVHMgaW4gYSBT
VVQsIGV0Yy4NCg0KPiBJIGJlbGlldmUgdGhhdCB0aGVyZSBpcyBhIG5lZWQgZm9yIGEgbW9yZSBj
bGVhciBleHBsYW5hdGlvbiBvZiB3aHkgQk1XRw0KPiBzcGVjaWZpY2F0aW9ucyBhcmUgYXBwcm9w
cmlhdGUgYW5kIGhvdyBjb21wYXJpc29uIGNhbiBiZSBtYWRlIHdoaWxlDQo+IHJlcGVhdGFiaWxp
dHkgY2Fubm90IGJlIGVuc3VyZWQsIGFuZCBtZWFzdXJlbWVudHMgYXJlIGRlcGVuZGVudCB1cG9u
DQo+IHBhcmFtZXRlcnMgaW50ZXJuYWwgdG8gdGhlIFNVVC4NCltBQ01dIA0KSSBiZWxpZXZlIHRo
YXQgZHJhZnQtaWV0Zi1ibXdnLXZpcnR1YWwtbmV0LTA1IGFscmVhZHkgDQppbmRpY2F0ZXMgd2h5
IHRoZSBleGlzdGluZyBCTVdHIFJGQ3MgYXJlIGEgcmVhc29uYWJsZSANCnN0YXJ0aW5nIHBsYWNl
IGZvciBORlYgYmVuY2htYXJrcywgaW4gcGFydCBiZWNhdXNlIA0Kd2Ugd2FudCB0byBtZWFzdXJl
IHRoZSBzYW1lIGJlbmNobWFya3Mgb2YgcGh5c2ljYWwgDQpuZXR3b3JrIGZ1bmN0aW9ucyBpbiBt
YW55IGNhc2VzLiBTZWUNCmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWJt
d2ctdmlydHVhbC1uZXQtMDUjc2VjdGlvbi00LjENCg0KUmVwZWF0YWJpbGl0eSBpcyBhIGdvYWwg
b2YgYWxsIGV4cGVyaW1lbnRzLCBhbmQgd2UgdW5kZXJzdGFuZA0KdGhhdCB0aGVyZSBpcyBtb3Jl
IHdvcmsgdG8gZG8gaW4gdGhpcyByZWdhcmQsIGJ1dCB3aGF0DQp3ZSBrbm93IG5vdyAoZG9jdW1l
bnRlZCBpbiB0aGlzIGRyYWZ0KSBzaG91bGQNCmJlIGEgdmFsdWFibGUgY29udHJpYnV0aW9uIHRv
IHRoZSBJbmR1c3RyeS4NCg0KDQo+IA0KPiBNaW5vciBpc3N1ZXM6DQo+IA0KPiAxLiBTb21lIG9m
IHRoZSB0ZXN0cyBtZW50aW9uZWQgaW4gU2VjdGlvbiA0IGhhdmUgbm8gcHJpb3Igb3IgaW4NCj4g
cHJvZ3Jlc3Mgd29yayBpbiB0aGUgSUVURjogQ29udHJvbCBQYXRoIGFuZCBEYXRhcGF0aCBDb3Vw
bGluZyBUZXN0cywNCj4gTm9pc3kgTmVpZ2hib3VyIFRlc3RzLCBjaGFyYWN0ZXJpemF0aW9uIG9m
IGFjY2VsZXJhdGlvbiB0ZWNobm9sb2dpZXMuDQpbQUNNXSANCkknbSBzb3JyeSwgYnV0IHRoYXQn
cyBub3QgYW4gYWNjdXJhdGUgcG9ydHJheWFsIG9mIEJNV0cncyBsaXRlcmF0dXJlLg0KDQpodHRw
czovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNjQxMyBleGFtaW5lZCBDb250cm9sIFBsYW5lL0Rh
dGFwbGFuZSANCmludGVyYWN0aW9ucywgZm9yIGV4YW1wbGUuDQoNCmh0dHBzOi8vdG9vbHMuaWV0
Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWJtd2ctdmlydHVhbC1uZXQtMDUjc2VjdGlvbi0zLjMNCml0
ZW0gMiBzcGVjaWZpY2FsbHkgaW5jbHVkZWQgTm9pc3kgTmVpZ2hib3VyIGFtb25nIHRoZSBuZXcg
DQp0ZXN0aW5nIHN0cmF0ZWdpZXMuDQoNCkV2ZXJ5IG5ldHdvcmsgaW50ZXJmYWNlIHdpdGggYW4g
QVNJQyBpcyBhbiBleGFtcGxlIG9mIGFjY2VsZXJhdGlvbiwNCm9uZSB0aGF0IHdlJ3ZlIGNoYXJh
Y3Rlcml6ZWQgaW4gcGh5c2ljYWwgbmV0d29yayBkZXZpY2VzIGZvciB5ZWFycy4NCg0KPiBJZiBu
ZXcgd29yayBpcyBuZWVkZWQgLyBwcm9wb3NlZCB0byBiZSBhZGRlZCBmb3IgdGhlIEJNV0cgc2Nv
cGUgYW5kDQo+IGZyYW1ld29yayBpdCB3b3VsZCBiZSB1c2VmdWwgZm9yIEJNV0cgdG8gbGlzdCB0
aGVzZSBzZXBhcmF0ZWx5Lg0KPiANCj4gDQo+IE5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOg0KPiAN
Cj4gMS4gV2hhdCBpcyBjYWxsZWQgJ0RlcGxveW1lbnQgc2NlbmFyaW9zJyBmcm9tIFZTIHBlcnNw
ZWN0aXZlIGluDQo+IFNlY3Rpb24gNCBkZXNjcmliZSBpbiBmYWN0IGRpZmZlcmVudCBjb25maWd1
cmF0aW9ucyBvZiB0aGUgU1VUIGluIEJNV0cNCj4gdGVybXMuIEl0IHNlZW1zIGJldHRlciB0byBz
ZXBhcmF0ZSB0aGlzIHNlY29uZCBwYXJ0IG9mIHNlY3Rpb24gNCBpbiBhDQo+IHNlcGFyYXRlIHNl
Y3Rpb24uIElmIGl0IGJlbG9uZ3MgdG8gYW4gZXhpc3Rpbmcgc2VjdGlvbiBpdCByYXRoZXINCj4g
YmVsb25ncyBpbiAzIHRoYW4gaW4gNC4NCj4gDQpbQUNNXSANClNlY3Rpb24gMyBpcyBtb3JlIGFi
b3V0IGV4dGVuZGluZyB0aGUgY29uZmlndXJhdGlvbiBndWlkYW5jZQ0KZnJvbSBodHRwczovL3Rv
b2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1ibXdnLXZpcnR1YWwtbmV0LTA1I3NlY3Rpb24t
My4yDQoNClNlY3Rpb24gNCBzdW1tYXJpemVzIHRoZSBWU1BFUkYgTGV2ZWwgVGVzdCBEZXNpZ24g
ZG9jdW1lbnQsDQpvZiB3aGljaCB0aGVzZSBkZXBsb3ltZW50IHNjZW5hcmlvcyBhcmUgYSBrZXkg
cGFydC4NCg0KdGhhbmtzIGZvciB5b3VyIGNvbW1lbnRzOyBob3BlZnVsbHkgdGhpcyBkZXRhaWxl
ZCByZXBseQ0Kd2lsbCByZWR1Y2UgeW91ciByZXNlcnZhdGlvbnMgYWJvdXQgcHVibGljYXRpb24u
DQoNCkFsDQooZm9yIHRoZSBjby1hdXRob3JzKQ0KDQpbMF0gaHR0cHM6Ly93d3cub3BuZnYub3Jn
L2Fubm91bmNlbWVudHMvMjAxNC8wOS8zMC90ZWxlY29tLWluZHVzdHJ5LWFuZC12ZW5kb3JzLXVu
aXRlLXRvLWJ1aWxkLWNvbW1vbi1vcGVuLXBsYXRmb3JtLXRvLWFjY2VsZXJhdGUtbmV0d29yay1m
dW5jdGlvbnMtdmlydHVhbGl6YXRpb24NCg0K


From nobody Thu May 11 10:07:17 2017
Return-Path: <acmorton@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 8C6B012EC7D; Thu, 11 May 2017 10:07:08 -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 gy4xGUQsdAja; Thu, 11 May 2017 10:07:06 -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 C9DC412EB94; Thu, 11 May 2017 10:01:24 -0700 (PDT)
Received: from pps.filterd (m0048589.ppops.net [127.0.0.1]) by m0048589.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v4BGu7H6005916; Thu, 11 May 2017 13:01:22 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0048589.ppops.net-00191d01. with ESMTP id 2act58m503-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 11 May 2017 13:01: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 v4BH1EXJ025187; Thu, 11 May 2017 13:01:20 -0400
Received: from mlpi408.sfdc.sbc.com (mlpi408.sfdc.sbc.com [130.9.128.240]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v4BH0rmS022964 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 11 May 2017 13:01:11 -0400
Received: from clpi183.sldc.sbc.com (clpi183.sldc.sbc.com [135.41.1.46]) by mlpi408.sfdc.sbc.com (RSA Interceptor); Thu, 11 May 2017 17:00:37 GMT
Received: from sldc.sbc.com (localhost [127.0.0.1]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id v4BH0ZSM007719; Thu, 11 May 2017 12:00:37 -0500
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.178.11]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id v4BH0TN3007110; Thu, 11 May 2017 12:00:29 -0500
Received: from exchange.research.att.com (njmtcas2.research.att.com [135.207.255.47]) by mail-blue.research.att.com (Postfix) with ESMTP id B82A8F0486; Thu, 11 May 2017 13:00:28 -0400 (EDT)
Received: from njmtexg4.research.att.com ([fe80::8cd:baa3:219e:5bd4]) by njmtcas2.research.att.com ([fe80::d550:ec84:f872:cad9%15]) with mapi id 14.03.0319.002; Thu, 11 May 2017 13:00:28 -0400
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: Dan Romascanu <dromasca@gmail.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
CC: "draft-ietf-bmwg-vswitch-opnfv.all@ietf.org" <draft-ietf-bmwg-vswitch-opnfv.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "bmwg@ietf.org" <bmwg@ietf.org>
Subject: RE: Opsdir last call review of draft-ietf-bmwg-vswitch-opnfv-03
Thread-Topic: Opsdir last call review of draft-ietf-bmwg-vswitch-opnfv-03
Thread-Index: AQHSykdUS/fJfaxnyEyPSoOu45aoKqHvWyeQ
Date: Thu, 11 May 2017 17:00:27 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF25F9B079@njmtexg4.research.att.com>
References: <149450107581.16728.18142473358782662679@ietfa.amsl.com>
In-Reply-To: <149450107581.16728.18142473358782662679@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.214.90]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-05-11_13:, , 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-1703280000 definitions=main-1705110087
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nGrW9Bt3QiZoQAP3KiXbcKAPpI0>
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, 11 May 2017 17:07:09 -0000

RGFuLCBwcm92aWRpbmcgeW91ciBHZW4tQVJUIGNvbW1lbnRzIGFuZCByZXBseSBiZWxvdy4NCg0K
PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBEYW4gUm9tYXNjYW51IFttYWls
dG86ZHJvbWFzY2FAZ21haWwuY29tXQ0KPiBTZW50OiBUaHVyc2RheSwgTWF5IDExLCAyMDE3IDc6
MTEgQU0NCj4gVG86IG9wcy1kaXJAaWV0Zi5vcmcNCj4gQ2M6IGRyYWZ0LWlldGYtYm13Zy12c3dp
dGNoLW9wbmZ2LmFsbEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzsNCj4gYm13Z0BpZXRmLm9yZzsg
ZHJvbWFzY2FAZ21haWwuY29tDQo+IFN1YmplY3Q6IE9wc2RpciBsYXN0IGNhbGwgcmV2aWV3IG9m
IGRyYWZ0LWlldGYtYm13Zy12c3dpdGNoLW9wbmZ2LTAzDQo+IA0KPiBSZXZpZXdlcjogRGFuIFJv
bWFzY2FudQ0KPiBSZXZpZXcgcmVzdWx0OiBIYXMgSXNzdWVzDQo+IA0KPiBUaGlzIGRvY3VtZW50
IGRlc2NyaWJlcyBkZXNjcmliZXMgdGhlIHByb2dyZXNzIG9mIHRoZSBPcGVuIFBsYXRmb3JtDQo+
IGZvciBORlYgKE9QTkZWKSBwcm9qZWN0IG9uIHZpcnR1YWwgc3dpdGNoIHBlcmZvcm1hbmNlICJW
U1BFUkYiLiBUaGF0DQo+IHByb2plY3QgcmV1c2VzIHRoZSBCTVdHIGZyYW1ld29yayBhbmQgc3Bl
Y2lmaWNhdGlvbnMgdG8gYmVuY2htYXJrDQo+IHZpcnR1YWwgc3dpdGNoZXMgaW1wbGVtZW50ZWQg
aW4gZ2VuZXJhbC1wdXJwb3NlIGhhcmR3YXJlLiBTb21lDQo+IGRpZmZlcmVuY2VzIHdpdGggdGhl
IGJlbmNobWFya2luZyBvZiBzcGVjaWFsaXplZCBIVyBwbGF0Zm9ybXMgYXJlDQo+IGlkZW50aWZp
ZWQgYW5kIHRoZXkgbWF5IGJlY29tZSB3b3JrIGl0ZW1zIGZvciBCTVdHIGluIHRoZSBmdXR1cmUu
IEl0J3MNCj4gYSB3ZWxsIHdyaXR0ZW4gYW5kIGNsZWFyIGRvY3VtZW50LCBidXQgSSBoYXZlIHJl
c2VydmF0aW9ucyBhYm91dCBpdA0KPiBiZWluZyBwdWJsaXNoZWQgYXMgYW4gUkZDLCBhbmQgSSBj
YW5ub3QgZmluZCBjb3ZlcmFnZSBmb3IgaXQgaW4gdGhlIFdHDQo+IGNoYXJ0ZXIuIEkgYWxzbyBo
YXZlIGNvbmNlcm5zIHRoYXQgcGFydHMgb2YgdGhlIG1ldGhvZG9sb2d5IHVzZWQgYnkNCj4gT1BO
RlYgYnJlYWsgdGhlIEJNV0cgcHJpbmNpcGxlcywgZXNwZWNpYWxseSByZXBlYXRhYmlsaXR5IGFu
ZA0KPiAnYmxhY2stYm94JywgYW5kIHRoaXMgaXMgbm90IGNsZWFyIGVub3VnaCBhcnRpY3VsYXRl
ZCBpbiB0aGUgZG9jdW1lbnQuDQo+ICBBcyBJIHdhcyBhc3NpZ25lZCBib3RoIE9QUy1ESVIgYW5k
IEdlbi1BUlQgcmV2aWV3cyBmb3IgdGhpcyBkb2N1bWVudCwNCj4gSSBkZXRhaWxlZCB0aGUgY29u
Y2VybnMgaW4gbXkgR2VuLUFSVCByZXZpZXcsIHRoZXkgc2VlbSB0byBiZWxvbmcNCj4gYmV0dGVy
IHRoZXJlLg0KPiANCj4gPkZyb20gYW4gT1BTLURJUiBwZXJzcGVjdGl2ZSB0aGlzIGRvY3VtZW50
IGhhcyBubyBpc3N1ZXMuIElmIHRoZQ0KPiBjb25jZXJucyBpbiBzZWN0aW9uIDYgYXJlIGFkZHJl
c3NlZCBhbmQgY2F1dGlvbiBpcyB0YWtlbiB0byBpc29sYXRlDQo+IHRoZSBTVVRzIGFuZCBiZW5j
aG1hcmtpbmcgZW52aXJvbm1lbnRzIGZyb20gdGhlIEludGVybmV0IG9yDQo+IG9wZXJhdGlvbmFs
IGludHJhbmV0cywgdGhlcmUgaXMgbm8gb3BlcmF0aW9uYWwgaW1wYWN0LiBJZiBhcHByb3ZlZCBp
dA0KPiB3b3VsZCBiZSBhIHVzZWZ1bCB0b29sIGZvciBvcGVyYXRvcnMgdG8gZ2V0IHNvbWUgaW5m
b3JtYXRpb24gYWJvdXQgaG93DQo+IGJlbmNobWFya2luZyBvZiBPUE5GViBwcm9qZWN0IHByb2R1
Y3RzIGFyZSBiZWluZyBkZXNpZ25lZC4NCj4gDQo+IA0KLT0tPS09LT0tPS09LT0tPS09LT0tPS09
LQ0KIA0KSGkgRGFuLA0KcGxlYXNlIHNlZSByZXBsaWVzLCBbQUNNXSwgYmVsb3cuDQoNCj4gLS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogRGFuIFJvbWFzY2FudSBbbWFpbHRvOmRy
b21hc2NhQGdtYWlsLmNvbV0NCj4gU2VudDogVGh1cnNkYXksIE1heSAxMSwgMjAxNyA3OjA2IEFN
DQo+IFRvOiBnZW4tYXJ0QGlldGYub3JnDQo+IENjOiBkcmFmdC1pZXRmLWJtd2ctdnN3aXRjaC1v
cG5mdi5hbGxAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmc7DQo+IGJtd2dAaWV0Zi5vcmc7IGRyb21h
c2NhQGdtYWlsLmNvbQ0KPiBTdWJqZWN0OiBHZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFm
dC1pZXRmLWJtd2ctdnN3aXRjaC1vcG5mdi0wMw0KPiANCj4gUmV2aWV3ZXI6IERhbiBSb21hc2Nh
bnUNCj4gUmV2aWV3IHJlc3VsdDogQWxtb3N0IFJlYWR5DQo+IA0KPiBJIGFtIHRoZSBhc3NpZ25l
ZCBHZW4tQVJUIHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBUaGUgR2VuZXJhbCBBcmVhDQo+IFJl
dmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBwcm9j
ZXNzZWQNCj4gYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLiAgUGxlYXNlIHRyZWF0IHRo
ZXNlIGNvbW1lbnRzIGp1c3QNCj4gbGlrZSBhbnkgb3RoZXIgbGFzdCBjYWxsIGNvbW1lbnRzLg0K
PiANCj4gRm9yIG1vcmUgaW5mb3JtYXRpb24sIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPiANCj4g
PGh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRwcy0NCj4gM0Ff
X3RyYWMuaWV0Zi5vcmdfdHJhY19nZW5fd2lraV9HZW5BcnRmYXEmZD1Ed0lDYVEmYz1MRllaLQ0K
PiBvOV9IVU1lTVRTUWljdmpJZyZyPU9mc1N1OGtUSWx0VnlEMW9MNzJjQncmbT1OVFZsTEJOLQ0K
PiBMM3U5ekdQSG1fQ05WY1hXN19PR1g4XzE4Q3RhQWFsWmluMCZzPTJIci0NCj4gZGhLYURISWd1
WTdXOTd6MzNSbEtqcVBEdG1vWW1NMi1qV3JiUy1vJmU9ID4uDQo+IA0KPiBEb2N1bWVudDogZHJh
ZnQtaWV0Zi1ibXdnLXZzd2l0Y2gtb3BuZnYtMDMNCj4gUmV2aWV3ZXI6IERhbiBSb21hc2NhbnUN
Cj4gUmV2aWV3IERhdGU6IDIwMTctMDUtMTENCj4gSUVURiBMQyBFbmQgRGF0ZTogMjAxNy0wNS0x
NQ0KPiBJRVNHIFRlbGVjaGF0IGRhdGU6IE5vdCBzY2hlZHVsZWQgZm9yIGEgdGVsZWNoYXQNCj4g
DQo+IFN1bW1hcnk6DQo+IA0KPiBBbG1vc3QgUmVhZHkuDQo+IA0KPiBUaGlzIGRvY3VtZW50IGRl
c2NyaWJlcyBkZXNjcmliZXMgdGhlIHByb2dyZXNzIG9mIHRoZSBPcGVuIFBsYXRmb3JtDQo+IGZv
ciBORlYgKE9QTkZWKSBwcm9qZWN0IG9uIHZpcnR1YWwgc3dpdGNoIHBlcmZvcm1hbmNlICJWU1BF
UkYiLiBUaGF0DQo+IHByb2plY3QgcmV1c2VzIHRoZSBCTVdHIGZyYW1ld29yayBhbmQgc3BlY2lm
aWNhdGlvbnMgdG8gYmVuY2htYXJrDQo+IHZpcnR1YWwgc3dpdGNoZXMgaW1wbGVtZW50ZWQgaW4g
Z2VuZXJhbC1wdXJwb3NlIGhhcmR3YXJlLiBTb21lDQo+IGRpZmZlcmVuY2VzIHdpdGggdGhlIGJl
bmNobWFya2luZyBvZiBzcGVjaWFsaXplZCBIVyBwbGF0Zm9ybXMgYXJlDQo+IGlkZW50aWZpZWQg
YW5kIHRoZXkgbWF5IGJlY29tZSB3b3JrIGl0ZW1zIGZvciBCTVdHIGluIHRoZSBmdXR1cmUuIEl0
J3MNCj4gYSB3ZWxsIHdyaXR0ZW4gYW5kIGNsZWFyIGRvY3VtZW50LCBidXQgSSBoYXZlIHJlc2Vy
dmF0aW9ucyBhYm91dCBpdA0KPiBiZWluZyBwdWJsaXNoZWQgYXMgYW4gUkZDLCBhbmQgSSBjYW5u
b3QgZmluZCBjb3ZlcmFnZSBmb3IgaXQgaW4gdGhlIFdHDQo+IGNoYXJ0ZXIuIEkgYWxzbyBoYXZl
IGNvbmNlcm5zIHRoYXQgcGFydHMgb2YgdGhlIG1ldGhvZG9sb2d5IHVzZWQgYnkNCj4gT1BORlYg
YnJlYWsgdGhlIEJNV0cgcHJpbmNpcGxlcywgZXNwZWNpYWxseSByZXBlYXRhYmlsaXR5IGFuZA0K
PiAnYmxhY2stYm94JywgYW5kIHRoaXMgaXMgbm90IGNsZWFyIGVub3VnaCBhcnRpY3VsYXRlZCBp
biB0aGUgZG9jdW1lbnQuDQpbQUNNXSANCk9rLCBsZXQncyBhZGRyZXNzIHlvdXIgc3BlY2lmaWMg
aXNzdWVzLCBhbmQgY29tZSBiYWNrIHRvIHlvdXIgcmVzZXJ2YXRpb25zLg0KDQo+IA0KPiANCj4g
TWFqb3IgaXNzdWVzOg0KPiANCj4gMS4gSXQgaXMgbm90IGNsZWFyIHRvIG1lIHdoeSB0aGlzIGRv
Y3VtZW50IG5lZWRzIHRvIGJlIHB1Ymxpc2hlZCBhcyBhbg0KPiBSRkMuIFRoZSBpbnRyb2R1Y3Rp
b24gc2F5czogJ1RoaXMgbWVtbyBkZXNjcmliZXMgdGhlIHByb2dyZXNzIG9mIHRoZQ0KPiBPcGVu
IFBsYXRmb3JtIGZvciBORlYgKE9QTkZWKSBwcm9qZWN0IG9uIHZpcnR1YWwgc3dpdGNoIHBlcmZv
cm1hbmNlDQo+ICJWU1BFUkYiLiAgVGhpcyBwcm9qZWN0IGludGVuZHMgdG8gYnVpbGQgb24gdGhl
IGN1cnJlbnQgYW5kIGNvbXBsZXRlZA0KPiB3b3JrIG9mIHRoZSBCZW5jaG1hcmtpbmcgTWV0aG9k
b2xvZ3kgV29ya2luZyBHcm91cCBpbiBJRVRGLCBieQ0KPiByZWZlcmVuY2luZyBleGlzdGluZyBs
aXRlcmF0dXJlLicgV2h5IHNob3VsZCB0aGUgV0cgYW5kIHRoZSBJRVNHDQo+IGludmVzdCByZXNv
dXJjZXMgaW4gcHVibGlzaGluZyB0aGlzLCB3aHkgYW4gSS1EIG9yIGFuIEluZGVwZW5kZW50DQo+
IFN0cmVhbSBSRkMgaXMgbm90IHN1ZmZpY2llbnQ/IA0KW0FDTV0gDQpUaGUgV0cgY29uc2lkZXJl
ZCBhbmQgZGlzY3Vzc2VkIHRoaXMgZG9jdW1lbnQgb3ZlciAzIHJldmlzaW9ucw0KYW5kIGEgeWVh
ciBvZiB0aW1lIGJlZm9yZSByZWFjaGluZyBjb25zZW5zdXMgdG8gZGV2ZWxvcCBpdCBmdXJ0aGVy
DQphcyBhIGNoYXJ0ZXJlZCBpdGVtLCBzbyB0aGlzIGRlY2lzaW9uIHdhcyBub3QgdGFrZW4gbGln
aHRseS4NClNlZSBtb3JlIGJlbG93Lg0KDQo+IFRoZSBXRyBjaGFydGVyIHNheXMgc29tZXRoaW5n
IGFib3V0Og0KPiAnVk5GIGFuZCBSZWxhdGVkIEluZnJhc3RydWN0dXJlIEJlbmNobWFya2luZzog
QmVuY2htYXJraW5nDQo+IE1ldGhvZG9sb2dpZXMgaGF2ZSByZWxpYWJseSBjaGFyYWN0ZXJpemVk
IG1hbnkgcGh5c2ljYWwgZGV2aWNlcy4gVGhpcw0KPiB3b3JrIGl0ZW0gZXh0ZW5kcyBhbmQgZW5o
YW5jZXMgdGhlIG1ldGhvZHMgdG8gdmlydHVhbCBuZXR3b3JrDQo+IGZ1bmN0aW9ucyAoVk5GKSBh
bmQgdGhlaXIgdW5pcXVlIHN1cHBvcnRpbmcgaW5mcmFzdHJ1Y3R1cmUuIEEgZmlyc3QNCj4gZGVs
aXZlcmFibGUgZnJvbSB0aGlzIGFjdGl2aXR5IHdpbGwgYmUgYSBkb2N1bWVudCB0aGF0IGNvbnNp
ZGVycyB0aGUNCj4gbmV3IGJlbmNobWFya2luZyBzcGFjZSB0byBlbnN1cmUgdGhhdCBjb21tb24g
aXNzdWVzIGFyZSByZWNvZ25pemVkDQo+IGZyb20gdGhlIHN0YXJ0LCB1c2luZyBiYWNrZ3JvdW5k
IG1hdGVyaWFscyBmcm9tIGluZHVzdHJ5IGFuZCBTRE9zDQo+IChlLmcuLCBJRVRGLCBFVFNJIE5G
VikuJy4gSSBkbyBub3QgYmVsaWV2ZSB0aGF0IHRoaXMgZG9jdW1lbnQgY292ZXJzDQo+IHRoZSBp
bnRlbnQgb2YgdGhlIGNoYXJ0ZXIsIGFzIGl0IGZvY3VzZWQgb24gb25lIG9yZ2FuaXphdGlvbiBv
bmx5Lg0KW0FDTV0gDQpJJ20gc29ycnksIGJ1dCBoZXJlIHlvdSBhcmUgbWlzdGFrZW4uIFRoZSBk
b2N1bWVudCB0aGF0IHNhdGlzZmllZA0KdGhlICJmaXJzdCBkZWxpdmVyYWJsZSAuLi4gZG9jdW1l
bnQgdGhhdCBjb25zaWRlcnMgdGhlIG5ldyBiZW5jaG1hcmtpbmcgc3BhY2UiDQppczogaHR0cHM6
Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtYm13Zy12aXJ0dWFsLW5ldC0wNQ0KdGl0
bGVkOiBDb25zaWRlcmF0aW9ucyBmb3IgQmVuY2htYXJraW5nIFZpcnR1YWwgTmV0d29yayBGdW5j
dGlvbnMgYW5kIFRoZWlyIEluZnJhc3RydWN0dXJlDQp3aGljaCBoYXMgYmVlbiBzdWJtaXR0ZWQg
dG8gSUVTRyBhbmQgYXBwcm92ZWQgZm9yIHB1YmxpY2F0aW9uLg0KRnVydGhlciwgdGhlIGN1cnJl
bnQgZHJhZnQgKGRyYWZ0LWlldGYtYm13Zy12c3dpdGNoLW9wbmZ2LTAzKQ0KcmVmZXJlbmNlcyB0
aGUgYXBwcm92ZWQgIkNvbnNpZGVyYXRpb25zIiBkcmFmdCBpbiBTZWN0aW9uIDMNCihhcyBkb2Vz
IGFsbW9zdCBldmVyeSByZWxhdGVkIEluZHVzdHJ5IHNwZWMgSSdtIGF3YXJlIG9mKS4NCg0KVGhl
IEJNV0cgQ2hhcnRlciBjb250aW51ZXM6DQogIEJlbmNobWFya3MgZm9yIHBsYXRmb3JtIGNhcGFj
aXR5IGFuZCBwZXJmb3JtYW5jZSBjaGFyYWN0ZXJpc3RpY3Mgb2YNCiAgdmlydHVhbCByb3V0ZXJz
LCBzd2l0Y2hlcywgYW5kIHJlbGF0ZWQgY29tcG9uZW50cyB3aWxsIGZvbGxvdywgaW5jbHVkaW5n
DQogIGNvbXBhcmlzb25zIGJldHdlZW4gcGh5c2ljYWwgYW5kIHZpcnR1YWwgbmV0d29yayBmdW5j
dGlvbnMuIEluIG1hbnkgY2FzZXMsDQogIHRoZSB0cmFkaXRpb25hbCBiZW5jaG1hcmtzIHNob3Vs
ZCBiZSBhcHBsaWNhYmxlIHRvIFZORnMsIGJ1dCB0aGUgbGFiDQogIHNldC11cHMsIGNvbmZpZ3Vy
YXRpb25zLCBhbmQgbWVhc3VyZW1lbnQgbWV0aG9kcyB3aWxsIGxpa2VseSBuZWVkIHRvDQogIGJl
IHJldmlzZWQgb3IgZW5oYW5jZWQuDQoNClRoaXMgZHJhZnQgY29uc3RpdHV0ZXMgb25lIG9mIHNl
dmVyYWwgZm9sbG93LW9uIGVmZm9ydHMsIGFwcHJvYWNoaW5nIA0KdGhlIHByb2JsZW0gZXhhY3Rs
eSBhcyB3ZSBkZXNjcmliZWQgaW4gdGhlIGxhc3Qgc2VudGVuY2UgYWJvdmUuDQoNCkFuIGFzcGVj
dCBvZiBJbmR1c3RyeSBjb2xsYWJvcmF0aW9uIHRoYXQgd2UgZGlkIG5vdCBhbnRpY2lwYXRlIGlu
IHRoZSANCkJNV0cgQ2hhcnRlciBpcyBvdXIgY3VycmVudCBpbnRlcmFjdGlvbnMgd2l0aCBPcGVu
IFNvdXJjZSBDb21tdW5pdGllcy4NClRoZSBjdXJyZW50IENoYXJ0ZXIgd2FzIGFwcHJvdmVkIGlu
IEp1bmUgMjAxNCwgdGhlbiBPUE5GViB3YXMgZm91bmRlZCANCm9uIFNlcHRlbWJlciAzMCwgMjAx
NCBbMF0gYW5kIHRoZSBWU1BFUkYgUHJvamVjdCB3YXMgY3JlYXRlZCBvbg0KRGVjIDE2LCAyMDE0
LCBzbyB3ZSBkaWQgbm90IGFudGljaXBhdGUgZXh0ZW5zaXZlIGNvbGxhYm9yYXRpb24gb24NCnRo
aXMgYW5kIG90aGVyIGJlbmNobWFya2luZyB0b3BpY3MuIA0KDQoNCg0KPiANCj4gMi4gSW4gc2Vj
dGlvbiAzIHRoZXJlICdyZXBlYXRhYmlsaXR5JyBpcyBtZW50aW9uZWQsIHdoaWxlDQo+IGFja25v
d2xlZGdpbmcgdGhhdCBpbiBhIHZpcnR1YWwgZW52aXJvbm1lbnQgdGhlcmUgaXMgbm8gZ3VhcmFu
dGVlIGFuZA0KPiBhY3R1YWxseSBubyB3YXkgdG8ga25vdyB3aGF0IG90aGVyIGFwcGxpY2F0aW9u
cyBhcmUgYmVpbmcgcnVuLg0KW0FDTV0gDQpTZWU6DQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0
bWwvZHJhZnQtaWV0Zi1ibXdnLXZpcnR1YWwtbmV0LTA1I3NlY3Rpb24tMy40DQoNClRoZXJlIGFy
ZSBjZXJ0YWlubHkgd2F5cyB0byBhc3Nlc3MgdGhlIGN1cnJlbnQgc2V0IG9mIHByb2Nlc3Nlcw0K
YXQgYSBwYXJ0aWN1bGFyIHRpbWUuIFRoZSBTb2Z0d2FyZSBjb25maWd1cmF0aW9uIHBhcmFtZXRl
cnMgaW4NClNlY3Rpb24gMy4zIGFyZSBpbnRlbmRlZCB0byBjYXB0dXJlIHRoaXMgYXNwZWN0IGFz
IHBhcnQgb2Ygc2V0LXVwLg0KQXQgdGhlIHNhbWUgdGltZSwgdGhlcmUgd2lsbCBiZSBjaGFsbGVu
Z2VzIHRvIGFzc2VzcyB0aGUgRFVUDQpwZXJmb3JtYW5jZSB3aGVuIHJlc291cmNlcyBhcmUgZnVs
bHkgc2hhcmVkLCBhbmQgbmV3IHRlc3RpbmcNCnN0cmF0ZWdpZXMgd2lsbCBiZSBuZWVkZWQ6DQpo
dHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1ibXdnLXZpcnR1YWwtbmV0LTA1
I3NlY3Rpb24tMy4zDQoNCg0KPiBNZWFzdXJpbmcgcGFyYW1ldGVycyBhcyB0aGUgb25lcyBsaXN0
ZWQgaW4gMy4zIHByb3ZpZGVzIGp1c3QgcGFydCBvZg0KPiB0aGUgYW5zd2VyLCBhbmQgdGhleSBh
cmUgaW50ZXJuYWwgcGFyYW1ldGVycyB0byB0aGUgU1VULiANCltBQ01dIA0KWWVzLCBrbm93aW5n
IHRoZSB0ZXN0ZWQgY29uZmlndXJhdGlvbiBpcyBhIGNyaXRpY2FsIHBpbGxhciANCnN1cHBvcnRp
bmcgcmVwZWF0YWJpbGl0eSAodGhlc2UgaXRlbXMgYXJlIG5vdCBtZWFzdXJlZCwgYnV0IGNvbmZp
Z3VyZWQpLA0KYW5kIHdoeSB3ZSBwcm92aWRlZCB0aGlzIHNlY3Rpb24uDQoNCj4gQWxzbywgdGhl
DQo+IGRpZmZlcmVudCBkZXBsb3ltZW50IHNjZW5hcmlvcyBpbiBzZWN0aW9uIDQgcmVxdWlyZSBk
aWZmZXJlbnQNCj4gY29uZmlndXJhdGlvbnMgZm9yIHRoZSBTVVQsIHRodXMgYnJlYWtpbmcgdGhl
ICdibGFjay1ib3gnIHByaW5jaXBsZS4NCltBQ01dIA0KU3BlY2lmeWluZyBEVVQgY29uZmlndXJh
dGlvbiBkb2VzIG5vdCBicmVhayBhbnkgcGFydCBvZiB0aGUgDQpibGFjay1ib3ggcHJpbmNpcGxl
LCB3aGljaCBlc3RhYmxpc2hlcyB0aGF0IGJlbmNobWFyayBtZWFzdXJlbWVudHMNCndpbGwgYmUg
YmFzZWQgb24gZXh0ZXJuYWxseSBvYnNlcnZhYmxlIHBoZW5vbWVuYS4gU2VlOg0KaHR0cHM6Ly90
b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtYm13Zy12aXJ0dWFsLW5ldC0wNSNzZWN0aW9u
LTQuMg0KDQpQcmV2aW91cyBCTVdHIFJGQ3MgaGF2ZSBpZGVudGlmaWVkIHRoZSBjcml0aWNhbCBj
b25maWd1cmF0aW9uDQpwYXJhbWV0ZXJzIG9mIHRoZSBEVVQsIHN1Y2ggYXMgdGhlIG51bWJlciBh
bmQgdHlwZSBvZiANCm5ldHdvcmsgaW50ZXJmYWNlcywgdGhlIGFycmFuZ2VtZW50IG9mIERVVHMg
aW4gYSBTVVQsIGV0Yy4NCg0KPiBJIGJlbGlldmUgdGhhdCB0aGVyZSBpcyBhIG5lZWQgZm9yIGEg
bW9yZSBjbGVhciBleHBsYW5hdGlvbiBvZiB3aHkgQk1XRw0KPiBzcGVjaWZpY2F0aW9ucyBhcmUg
YXBwcm9wcmlhdGUgYW5kIGhvdyBjb21wYXJpc29uIGNhbiBiZSBtYWRlIHdoaWxlDQo+IHJlcGVh
dGFiaWxpdHkgY2Fubm90IGJlIGVuc3VyZWQsIGFuZCBtZWFzdXJlbWVudHMgYXJlIGRlcGVuZGVu
dCB1cG9uDQo+IHBhcmFtZXRlcnMgaW50ZXJuYWwgdG8gdGhlIFNVVC4NCltBQ01dIA0KSSBiZWxp
ZXZlIHRoYXQgZHJhZnQtaWV0Zi1ibXdnLXZpcnR1YWwtbmV0LTA1IGFscmVhZHkgDQppbmRpY2F0
ZXMgd2h5IHRoZSBleGlzdGluZyBCTVdHIFJGQ3MgYXJlIGEgcmVhc29uYWJsZSANCnN0YXJ0aW5n
IHBsYWNlIGZvciBORlYgYmVuY2htYXJrcywgaW4gcGFydCBiZWNhdXNlIA0Kd2Ugd2FudCB0byBt
ZWFzdXJlIHRoZSBzYW1lIGJlbmNobWFya3Mgb2YgcGh5c2ljYWwgDQpuZXR3b3JrIGZ1bmN0aW9u
cyBpbiBtYW55IGNhc2VzLiBTZWUNCmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1p
ZXRmLWJtd2ctdmlydHVhbC1uZXQtMDUjc2VjdGlvbi00LjENCg0KUmVwZWF0YWJpbGl0eSBpcyBh
IGdvYWwgb2YgYWxsIGV4cGVyaW1lbnRzLCBhbmQgd2UgdW5kZXJzdGFuZA0KdGhhdCB0aGVyZSBp
cyBtb3JlIHdvcmsgdG8gZG8gaW4gdGhpcyByZWdhcmQsIGJ1dCB3aGF0DQp3ZSBrbm93IG5vdyAo
ZG9jdW1lbnRlZCBpbiB0aGlzIGRyYWZ0KSBzaG91bGQNCmJlIGEgdmFsdWFibGUgY29udHJpYnV0
aW9uIHRvIHRoZSBJbmR1c3RyeS4NCg0KDQo+IA0KPiBNaW5vciBpc3N1ZXM6DQo+IA0KPiAxLiBT
b21lIG9mIHRoZSB0ZXN0cyBtZW50aW9uZWQgaW4gU2VjdGlvbiA0IGhhdmUgbm8gcHJpb3Igb3Ig
aW4NCj4gcHJvZ3Jlc3Mgd29yayBpbiB0aGUgSUVURjogQ29udHJvbCBQYXRoIGFuZCBEYXRhcGF0
aCBDb3VwbGluZyBUZXN0cywNCj4gTm9pc3kgTmVpZ2hib3VyIFRlc3RzLCBjaGFyYWN0ZXJpemF0
aW9uIG9mIGFjY2VsZXJhdGlvbiB0ZWNobm9sb2dpZXMuDQpbQUNNXSANCkknbSBzb3JyeSwgYnV0
IHRoYXQncyBub3QgYW4gYWNjdXJhdGUgcG9ydHJheWFsIG9mIEJNV0cncyBsaXRlcmF0dXJlLg0K
DQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNjQxMyBleGFtaW5lZCBDb250cm9sIFBs
YW5lL0RhdGFwbGFuZSANCmludGVyYWN0aW9ucywgZm9yIGV4YW1wbGUuDQoNCmh0dHBzOi8vdG9v
bHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWJtd2ctdmlydHVhbC1uZXQtMDUjc2VjdGlvbi0z
LjMNCml0ZW0gMiBzcGVjaWZpY2FsbHkgaW5jbHVkZWQgTm9pc3kgTmVpZ2hib3VyIGFtb25nIHRo
ZSBuZXcgDQp0ZXN0aW5nIHN0cmF0ZWdpZXMuDQoNCkV2ZXJ5IG5ldHdvcmsgaW50ZXJmYWNlIHdp
dGggYW4gQVNJQyBpcyBhbiBleGFtcGxlIG9mIGFjY2VsZXJhdGlvbiwNCm9uZSB0aGF0IHdlJ3Zl
IGNoYXJhY3Rlcml6ZWQgaW4gcGh5c2ljYWwgbmV0d29yayBkZXZpY2VzIGZvciB5ZWFycy4NCg0K
PiBJZiBuZXcgd29yayBpcyBuZWVkZWQgLyBwcm9wb3NlZCB0byBiZSBhZGRlZCBmb3IgdGhlIEJN
V0cgc2NvcGUgYW5kDQo+IGZyYW1ld29yayBpdCB3b3VsZCBiZSB1c2VmdWwgZm9yIEJNV0cgdG8g
bGlzdCB0aGVzZSBzZXBhcmF0ZWx5Lg0KPiANCj4gDQo+IE5pdHMvZWRpdG9yaWFsIGNvbW1lbnRz
Og0KPiANCj4gMS4gV2hhdCBpcyBjYWxsZWQgJ0RlcGxveW1lbnQgc2NlbmFyaW9zJyBmcm9tIFZT
IHBlcnNwZWN0aXZlIGluDQo+IFNlY3Rpb24gNCBkZXNjcmliZSBpbiBmYWN0IGRpZmZlcmVudCBj
b25maWd1cmF0aW9ucyBvZiB0aGUgU1VUIGluIEJNV0cNCj4gdGVybXMuIEl0IHNlZW1zIGJldHRl
ciB0byBzZXBhcmF0ZSB0aGlzIHNlY29uZCBwYXJ0IG9mIHNlY3Rpb24gNCBpbiBhDQo+IHNlcGFy
YXRlIHNlY3Rpb24uIElmIGl0IGJlbG9uZ3MgdG8gYW4gZXhpc3Rpbmcgc2VjdGlvbiBpdCByYXRo
ZXINCj4gYmVsb25ncyBpbiAzIHRoYW4gaW4gNC4NCj4gDQpbQUNNXSANClNlY3Rpb24gMyBpcyBt
b3JlIGFib3V0IGV4dGVuZGluZyB0aGUgY29uZmlndXJhdGlvbiBndWlkYW5jZQ0KZnJvbSBodHRw
czovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1ibXdnLXZpcnR1YWwtbmV0LTA1I3Nl
Y3Rpb24tMy4yDQoNClNlY3Rpb24gNCBzdW1tYXJpemVzIHRoZSBWU1BFUkYgTGV2ZWwgVGVzdCBE
ZXNpZ24gZG9jdW1lbnQsDQpvZiB3aGljaCB0aGVzZSBkZXBsb3ltZW50IHNjZW5hcmlvcyBhcmUg
YSBrZXkgcGFydC4NCg0KdGhhbmtzIGZvciB5b3VyIGNvbW1lbnRzOyBob3BlZnVsbHkgdGhpcyBk
ZXRhaWxlZCByZXBseQ0Kd2lsbCByZWR1Y2UgeW91ciByZXNlcnZhdGlvbnMgYWJvdXQgcHVibGlj
YXRpb24uDQoNCkFsDQooZm9yIHRoZSBjby1hdXRob3JzKQ0KDQpbMF0gaHR0cHM6Ly93d3cub3Bu
ZnYub3JnL2Fubm91bmNlbWVudHMvMjAxNC8wOS8zMC90ZWxlY29tLWluZHVzdHJ5LWFuZC12ZW5k
b3JzLXVuaXRlLXRvLWJ1aWxkLWNvbW1vbi1vcGVuLXBsYXRmb3JtLXRvLWFjY2VsZXJhdGUtbmV0
d29yay1mdW5jdGlvbnMtdmlydHVhbGl6YXRpb24NCg==


From nobody Thu May 11 10:18:19 2017
Return-Path: <jclarke@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 E9DA013144E; Thu, 11 May 2017 10:18:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 LBv4dVwwiXnk; Thu, 11 May 2017 10:18:15 -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 44015129B84; Thu, 11 May 2017 10:13:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1747; q=dns/txt; s=iport; t=1494522793; x=1495732393; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=Wh1VPyjsGml3rxZ8GRBQQKBqkw2eioriHRPujgzWpZ8=; b=Bi9VEd8IkJr56HYGN04zwhujZJm/zyJ92cGP2hTvw2gU6sy36VucMKX3 /7QaJesuxJeW1yLWVfSPIUF+Q8e7Be6+2Zq3zWq1KwvfnaqdhlljtPVDy gkrkT2YC7ihG0CF88ffgdp6ujTB9EHE6q7+clT0wbBoH4AtDjacNv6QqO s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DaAgBXmxRZ/5NdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1WFV5tRIXKVAoIPhiQChQ1AFwECAQEBAQEBAWsohRUBAQEBAgE?= =?us-ascii?q?jDwFGEAsYAgImAgJXBg0IAQGKFgixUYImincBAQEBAQEBAQEBAQEBAQEBASGBC?= =?us-ascii?q?4VUgV4rC4IxNId1gmABBJZvhxuTG4sChmmUQyABNoEKTyEVh1ckiRIBAQE?=
X-IronPort-AV: E=Sophos;i="5.38,325,1491264000"; d="scan'208";a="241986267"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 May 2017 17:13:12 +0000
Received: from [10.82.250.3] (rtp-vpn6-513.cisco.com [10.82.250.3]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id v4BHDABw017783; Thu, 11 May 2017 17:13:12 GMT
Subject: Re: Opsdir early review of draft-ietf-v6ops-v4v6-xlat-prefix-00
To: Tore Anderson <tore@fud.no>
Cc: ops-dir@ietf.org, v6ops@ietf.org, ietf@ietf.org, draft-ietf-v6ops-v4v6-xlat-prefix.all@ietf.org
References: <149373185172.9923.9255526962045750289@ietfa.amsl.com> <20170511131642.1f408832@echo.ms.redpill-linpro.com>
From: Joe Clarke <jclarke@cisco.com>
Organization: Cisco
Message-ID: <9d92e7bd-5b55-fb1f-5572-b69b6507ee7c@cisco.com>
Date: Thu, 11 May 2017 13:13:10 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.0
MIME-Version: 1.0
In-Reply-To: <20170511131642.1f408832@echo.ms.redpill-linpro.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dSPuPV3ne2vPytNOEW4ZOesdr7g>
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, 11 May 2017 17:18:17 -0000

On 5/11/17 07:16, Tore Anderson wrote:
> Actually I'm trying to not imply anywhere that 64:ff9b:1::/48 is a/the
> «WKP» (although the previous point you brought up was a failure in that
> regard). The WKP is defined to be exactly 64:ff9b::/96 by RFC6052, and
> I do not want to cause any ambiguity here.
> 
> I rewrote the paragraph in question as follows:
> 
>       Note that 64:ff9b:1::/48 (or any more-specific prefix) is distinct from
>       the WKP 64:ff9b::/96. Therefore, the restrictions on the use of the WKP
>       described in Section 3.1 of <xref target="RFC6052"/> do not apply to the
>       use of 64:ff9b:1::/48.
> 
> Is that better?

Yes, I think that text plus the previous clarification is good.

> 
>> In Section 3, you state:
>>
>> Since the WKP 64:ff9b::/96 was reserved by [RFC6052], several new
>> IPv4/IPv6 translation mechanisms have been defined by the IETF
>>
>> I think it would be useful to mention some of these new translation
>> mechanisms as non-normative references, and if need be, show an
>> example of interoperability.
> 
> How about: «Since the WKP 64:ff9b::/96 was reserved by [RFC6052],
> several new IPv4/IPv6 translation mechanisms have been defined by the
> IETF, such as [RFC6146] and [RFC7915].» ?
> 
> These two mechanisms do not interoperate at all, so they need different
> translation prefixes if they're to be deployed in the same network.

That works.

> 
>> NITS:
>>
>> In your Abstract, you mention RFC6890, but this does not appear to be
>> an xref to it, and it should be.
> 
> As mentioned by others, the idnits tool complains about xrefs in the
> abstract. In any case I've just dropped the Updates on 6890 completely.

Thanks.

Joe


From nobody Thu May 11 10:25:44 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 0D47212EBC1 for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 10:25:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 RvBNEsaR-liH for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 10:25:41 -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 EDA3512EBA3 for <ietf@ietf.org>; Thu, 11 May 2017 10:19:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 48FAC300563 for <ietf@ietf.org>; Thu, 11 May 2017 13:19:54 -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 My14QRMt1HHb for <ietf@ietf.org>; Thu, 11 May 2017 13:19:53 -0400 (EDT)
Received: from new-host-6.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 0737630042E; Thu, 11 May 2017 13:19:52 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Registration for remote participation
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20170511121458.v62px5wrbh47zf3j@mx4.yitter.info>
Date: Thu, 11 May 2017 13:19:52 -0400
Cc: IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7BEFAC6-25C3-4907-A764-A9EF8FB90238@vigilsec.com>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <29052.1494439452@obiwan.sandelman.ca> <F4BF8089-0E62-4B3D-AE97-1F5ACC4196BC@stewe.org> <20170511121458.v62px5wrbh47zf3j@mx4.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IJuFlbWThhjibsoreyax7g14Vq4>
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, 11 May 2017 17:25:43 -0000

> On May 11, 2017, at 8:14 AM, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:
>=20
> On Wed, May 10, 2017 at 07:47:20PM +0000, Stephan Wenger wrote:
>>=20
>> I=E2=80=99m in favor of validating the address, for example by =
sending some form of credential to it; without the credential, only =
listening/reading access is granted.  Doesn=E2=80=99t have to be =
bullet-proof, but using example@example.com shouldn=E2=80=99t work.  =
This is obviously in order to obtain one semi-traceable record of the =
participant.
>>>=20
>=20
> We don't do that for in-person participants, because we no longer even
> collect the email address on the blue sheets.  (We do it for meeting
> registration, of course, but we don't have a way to pair that with
> participation in any given part of the meeting, so the IPR issue is
> harder to argue by analogy here.)

Collecting an email address as part of the registration process does not =
mean that the email address needs to appear in the proceedings.

Russ


From nobody Thu May 11 10:40:19 2017
Return-Path: <stewe@stewe.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 F0F1D12951E for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 10:40:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.702
X-Spam-Level: 
X-Spam-Status: No, score=-4.702 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_H2=-2.8, SPF_HELO_PASS=-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=steweorg.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 DQIBLvG3AN1D for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 10:40:15 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0131.outbound.protection.outlook.com [104.47.33.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 1FE02129411 for <ietf@ietf.org>; Thu, 11 May 2017 10:35:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=steweorg.onmicrosoft.com; s=selector1-stewe-org; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=qWUS26TVlmbvcE9ARuGGETUr8KO08/YXB3TibXuVk9U=; b=A3HPrVa4nfYftWc07TWBO5VrtP1QzJlCxyzkZWeffFQkb2wJUncBLQsmqPladfrbtK5a0sQXDBevCZV8vnkdqUp+aAT5bO4ILQbkFX5hnIDOc0d7WAgE34W6ArdhZdqUFi+BKsBPrLxYlaQrV4SHCcPotWvwtxIp9WW8ChIZxCE=
Received: from CY1PR17MB0693.namprd17.prod.outlook.com (10.164.217.5) by CY1PR17MB0696.namprd17.prod.outlook.com (10.164.217.8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1084.16; Thu, 11 May 2017 17:35:24 +0000
Received: from CY1PR17MB0693.namprd17.prod.outlook.com ([10.164.217.5]) by CY1PR17MB0693.namprd17.prod.outlook.com ([10.164.217.5]) with mapi id 15.01.1084.020; Thu, 11 May 2017 17:35:24 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Registration for remote participation
Thread-Topic: Registration for remote participation
Thread-Index: AQHSyPa0kEKm1WpyAUugVHquNJkgB6Ht3boA//+nd4CAAYlLAP//5C2A
Date: Thu, 11 May 2017 17:35:24 +0000
Message-ID: <C860EF0F-25C0-413D-90F8-0A19437F0B46@stewe.org>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <29052.1494439452@obiwan.sandelman.ca> <F4BF8089-0E62-4B3D-AE97-1F5ACC4196BC@stewe.org> <20170511121458.v62px5wrbh47zf3j@mx4.yitter.info>
In-Reply-To: <20170511121458.v62px5wrbh47zf3j@mx4.yitter.info>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: anvilwalrusden.com; dkim=none (message not signed) header.d=none;anvilwalrusden.com; dmarc=none action=none header.from=stewe.org;
x-originating-ip: [50.174.30.183]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY1PR17MB0696; 7:96STadq1NOuUNmr891LKFBX1W0m5JwzF7080Zkg7rjr10qlURj30fzjd3PIZl1w3hm38//NZfz2We9sofMww1V6kHbDjjp38VNJeHdrci1PPNB33KT3KCJ2QbZgEWR/w8W1DZS9LAZ3Hm6uGAtdd5x/+0NXLHHVVvgdD0S3KoGzkwEyrRVxrrWDV9DByU1+VdxE8SGPw3npyFBjXMWHDcnscLYB+gRy2JYeu8fbIgg7wBqOKCXrHkwuKKVvD0aZiYGmkQY9k9G0n8IcyblACJjReKm2+/OF/TrwdbB8T/kVveHmQqUkLjL40Z6IqLacHRQ9ygY1YwzmSFF8kI0bvlQ==
x-ms-office365-filtering-correlation-id: 8812cc13-3cc4-4b8b-47f4-08d498941b17
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075); SRVR:CY1PR17MB0696; 
x-microsoft-antispam-prvs: <CY1PR17MB06965012B7EE28EEC1A7F2FCAEED0@CY1PR17MB0696.namprd17.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(6041248)(20161123564025)(2016111802025)(20161123555025)(20161123562025)(20161123560025)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6043046)(6072148); SRVR:CY1PR17MB0696; BCL:0; PCL:0; RULEID:; SRVR:CY1PR17MB0696; 
x-forefront-prvs: 0304E36CA3
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39450400003)(39400400002)(39830400002)(39410400002)(24454002)(25786009)(99286003)(53546009)(86362001)(122556002)(2501003)(38730400002)(102836003)(3846002)(6116002)(6246003)(66066001)(36756003)(189998001)(478600001)(53936002)(6436002)(76176999)(50986999)(54356999)(33656002)(93886004)(5660300001)(82746002)(6506006)(8936002)(3480700004)(229853002)(83716003)(2950100002)(7736002)(305945005)(3280700002)(81166006)(2906002)(8676002)(77096006)(2900100001)(3660700001)(6486002)(19840200001)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR17MB0696; H:CY1PR17MB0693.namprd17.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <14DD1D5B6FD8A842830B83CB87E0969E@namprd17.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 May 2017 17:35:24.1768 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 865fc51c-5fae-4322-98ef-0121a85df0b6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR17MB0696
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PEKGgnsLD-Wr6mSOqARrCaYS_0U>
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, 11 May 2017 17:40:17 -0000

SGkgQW5kcmV3LCBwbGVhc2Ugc2VlIGlubGluZS4NCg0KDQoNCg0KT24gNS8xMS8xNywgMDU6MTQs
ICJpZXRmIG9uIGJlaGFsZiBvZiBBbmRyZXcgU3VsbGl2YW4iIDxpZXRmLWJvdW5jZXNAaWV0Zi5v
cmcgb24gYmVoYWxmIG9mIGFqc0BhbnZpbHdhbHJ1c2Rlbi5jb20+IHdyb3RlOg0KDQo+T24gV2Vk
LCBNYXkgMTAsIDIwMTcgYXQgMDc6NDc6MjBQTSArMDAwMCwgU3RlcGhhbiBXZW5nZXIgd3JvdGU6
DQo+PiANCj4+IEnigJltIGluIGZhdm9yIG9mIHZhbGlkYXRpbmcgdGhlIGFkZHJlc3MsIGZvciBl
eGFtcGxlIGJ5IHNlbmRpbmcgc29tZSBmb3JtIG9mIGNyZWRlbnRpYWwgdG8gaXQ7IHdpdGhvdXQg
dGhlIGNyZWRlbnRpYWwsIG9ubHkgbGlzdGVuaW5nL3JlYWRpbmcgYWNjZXNzIGlzIGdyYW50ZWQu
ICBEb2VzbuKAmXQgaGF2ZSB0byBiZSBidWxsZXQtcHJvb2YsIGJ1dCB1c2luZyBleGFtcGxlQGV4
YW1wbGUuY29tIHNob3VsZG7igJl0IHdvcmsuICBUaGlzIGlzIG9idmlvdXNseSBpbiBvcmRlciB0
byBvYnRhaW4gb25lIHNlbWktdHJhY2VhYmxlIHJlY29yZCBvZiB0aGUgcGFydGljaXBhbnQuDQo+
PiA+DQo+DQo+V2UgZG9uJ3QgZG8gdGhhdCBmb3IgaW4tcGVyc29uIHBhcnRpY2lwYW50cywgYmVj
YXVzZSB3ZSBubyBsb25nZXIgZXZlbg0KPmNvbGxlY3QgdGhlIGVtYWlsIGFkZHJlc3Mgb24gdGhl
IGJsdWUgc2hlZXRzLiAgKFdlIGRvIGl0IGZvciBtZWV0aW5nDQo+cmVnaXN0cmF0aW9uLCBvZiBj
b3Vyc2UsIGJ1dCB3ZSBkb24ndCBoYXZlIGEgd2F5IHRvIHBhaXIgdGhhdCB3aXRoDQo+cGFydGlj
aXBhdGlvbiBpbiBhbnkgZ2l2ZW4gcGFydCBvZiB0aGUgbWVldGluZywgc28gdGhlIElQUiBpc3N1
ZSBpcw0KPmhhcmRlciB0byBhcmd1ZSBieSBhbmFsb2d5IGhlcmUuKQ0KDQpUaGUgcXVlc3Rpb24g
aXMgbm90IHdoZXRoZXIgd2UgY29sbGVjdCBlbWFpbCBhZGRyZXNzZXMuICBUaGUgcXVlc3Rpb24g
aXMgd2hldGhlciB3ZSBjb2xsZWN0IHRoZSBpZGVudGlmaWNhdGlvbiBvZiB0aGUgaW5kaXZpZHVh
bCBhbmQgaXRzIGVtcGxveWVyLCBib3RoZXIgd2l0aCByZWFzb25hYmxlIGNlcnRhaW50eS4gIElJ
UkMsIG9uZSByZWFzb24gZm9yIHRoZSBjaGFuZ2UgZnJvbSBlbWFpbCBhZGRyZXNzIHRvIGNvbXBh
bnkgbmFtZSB3YXMgbWFkZSBiZWNhdXNlLCB0b2RheSwgbWFueSBwZW9wbGUgdXNlIG5vbi1lbXBs
b3llciBlbWFpbCBmb3IgSUVURiB3b3JrIGV2ZW4gaWYgdGhleSBkbyB0aGUgd29yayBtb3N0bHkg
b24gYmVoYWxmIG9mIHRoZWlyIGVtcGxveWVyIGFuZCBhcyBwYXJ0IG9mIHRoZWlyIGpvYiwgYW5k
IHRyYWNraW5nIGRvd24gdGhlIHBhcnRpY2lwYW504oCZcyBlbXBsb3llciBmcm9tIHRoZSBlbWFp
bCBhZGRyZXNzIGZvciB0aGluZ3MgbGlrZSBOb25jb20gZWxpZ2liaWxpdHkgYW5kIGFsc28gSVBS
IHJlbGF0ZWQgaXNzdWVzIGRpZG7igJl0IHdvcmsgYW55bW9yZSAoaWYgaXQgZXZlciBkaWQpLiAg
KHRoZXJlIHdlcmUgYWxzbyBvdGhlciBtb3RpdmF0aW9ucywgaW5jbHVkaW5nIHRoZSBoYW5keSBj
cmVhdGlvbiBvZiBhIFNQQU0gbGlzdCBmcm9tIElFVEYgYXJjaGl2YWwgbWF0ZXJpYWwgc3VjaCBh
cyB0aGUgcHJvY2VlZGluZ3MpLg0KDQpGb3IgYW4gaW4tcGVyc29uIG1lZXRpbmcsIHdlIChvciBh
IGNvdXJ0KSBoYXZlIG1hbnkgd2F5cyB0byBpZGVudGlmeSBhIHBlcnNvbiB3aG8gaW5mbHVlbmNl
cyB0aGUgZGVjaXNpb24gcHJvY2Vzcy4gIEZvciBhbiBleHRlcm5hbCBwZXJzb24sIGVzcGVjaWFs
bHkgd2hlbiB0aGVyZSBpcyBubyB2aWRlbywgd2UgYXJlIG1vcmUgbGltaXRlZC4gIEEgbm9uLXZl
cmlmaWVkIGVtYWlsIGFkZHJlc3MgaXMgY2VydGFpbmx5IGVhc2llciB0byBmYWtlIHRoYW4gdGhl
IHJlY29sbGVjdGlvbiBvZiBhIHJvb21mdWwgb2YgcGVvcGxlIGR1cmluZyBhIHBoeXNpY2FsIG1l
ZXRpbmcuDQoNCj4gDQo+PiBBbmQgNSkgY2xpY2stdGhyb3VnaCBvZiB0aGUgTm90ZSBXZWxsICh1
bmxlc3MgdGhhdOKAmXMgZG9uZSBpbiBzb21lIG90aGVyIHBoYXNlIG9mIHRoZSByZW1vdGUgcGFy
dGljaXBhdGlvbiwgbGlrZSB3aGVuIHNpZ25pbmctaW4gdG8gbWVldGVjaG8pLiAgQWdhaW4gZm9y
LS1JIGhvcGUgb2J2aW91cy0tSVBSIHJlbGF0ZWQgcmVhc29ucy4NCj4+IA0KPg0KPldlIF9jZXJ0
YWlubHlfIGRvbid0IGRvIHRoYXQgZm9yIGluLXBlcnNvbiBtZWV0aW5ncy4gIFdlIHB1dCB0aGUg
Tm90ZQ0KPldlbGwgdXAgYW5kIGFzc3VtZSB0aGF0IGFueW9uZSB3aG8gaXMgaW4gdGhlIHJvb20g
YW5kIHdobyBtYWtlcyBhDQo+Q29udHJpYnV0aW9uIGluIGFueSB3YXkgaXMgYXdhcmUgb2YgaXQu
ICBKb2luaW5nIHRoZSBtZWV0aW5nIHZpcnR1YWxseQ0KPmhhcyB0aGUgc2FtZSBwcm9wZXJ0eSwg
bm8/DQoNCkFjdHVhbGx5LCBOby4gIEluIGFuIGluLXBlcnNvbiBtZWV0aW5nLCB0aGUgaHVyZGxl
IG9mIG1pc3NpbmcgYSBub3RlIHdlbGwgaXMgcHJldHR5IGhpZ2guICBXaGVuIHlvdSBhcmUgYXQg
YSBwaHlzaWNhbCBtZWV0aW5nIGFuZCBnZXQgYm9tYmFyZGVkIHdpdGggYSBOb3RlIFdlbGwgbm90
IG9ubHkgZHVyaW5nIHJlZ2lzdHJhdGlvbiB0aW1lLCBidXQgYWxzbyBkYWlseSBzZXZlcmFsIHRp
bWVzIGF0IHRoZSBiZWdpbiBvZiBXRyBzZXNzaW9ucywgeW91IGFuZCB5b3VyIGxhd3llciB3b3Vs
ZCBoYXZlIGEgaGFyZCB0aW1lIHRvIGFyZ3VlIHRoYXQgeW91IHdlcmUgbm90IGF3YXJlIG9mIGl0
IChhbmQgdGhlcmVmb3JlIHBlcmhhcHMgZnJlZSBvZiBjZXJ0YWluIG9ibGlnYXRpb25zIHlvdSBv
dGhlcndpc2UgaGF2ZSBwZXIgcG9saWN5KS4gIE9UT0gsIGFzc3VtaW5nIG5vIGNsaWNrLXRocm91
Z2ggb3Igc2ltaWxhciwgYSBnb29kIGxhd3llciBjb3VsZCBjb25jZWl2YWJseSBtYWtlIHRoZSBj
YXNlIHRoYXQgaGlzIGNsaWVudCB3YXMgbm90IGF3YXJlIG9mIHRoZSBOb3RlIFdlbGwgYW5kIGFz
c29jaWF0ZWQgcG9saWN5IHdoZW4gaW5mbHVlbmNpbmcgYW4gSUVURiBkZWNpc2lvbiBwcm9jZXNz
IG9mIGEgY2VydGFpbiBkb2N1bWVudCwgZXNwZWNpYWxseSBpZiB0aGF0IHBlcnNvbiBpcyBub3Qg
YW4gSUVURiByZWd1bGFyIGFuZCBkaWFscyBpbiBvbmx5IGZvciBvbmUgV0cgc2Vzc2lvbiAoYW5k
IHBlcmhhcHMgYSBiaXQgbGF0ZSB0byB0aGF0KS4gIFRoZW4sIHRoZSBnb29kIGxhd3llciBjb3Vs
ZCBjb25jZWl2YWJseSBhcmd1ZSB0aGF0IGNlcnRhaW4gb2JsaWdhdGlvbnMgKHN1Y2ggYXMgdGhl
IG9ibGlnYXRpb24gdG8gZGlzY2xvc2UgcGF0ZW50cykgd2VyZSBub3Qga25vd24gdG8gdGhhdCBj
bGllbnQgb2YgaGlzLiAgQW5kIGZpbmFsbHksIHRoZSBsYXd5ZXIgY291bGQgYXJndWUgdGhhdCwg
dGhlcmVmb3JlLCB0aGUgb2JsaWdhdGlvbnMgZG8gbm90IGFwcGx5LiAgKE5vdGUgdGhhdCBJIGRp
ZG7igJl0IGluY2x1ZGUgdGhlIHdvcmQg4oCcc3VjY2Vzc2Z1bOKAnSBpbiB0aGUgbGFzdCBzZW50
ZW5jZS4pDQoNClRoZXJlIGhhcyBiZWVuIG9uZSBmYWlybHkgcHJvbWluZW50IGNhc2Ugd2hlcmUg
YSBjb21wYW55IGNob29zZSB0byBzZW5kIHVuZGVyY292ZXIgcGFydGljaXBhbnRzIHRvIHN0YW5k
YXJkcyBtZWV0aW5ncywgaW4gb3JkZXIgdG8gKHNvIHRoZSBjb3VydCBmb3VuZCBJSVJDKSBjaXJj
dW12ZW50IG9ibGlnYXRpb25zIGJ5IHRoZSBzdGFuZGFyZHMgY29tbWl0dGVlLiAgV2Ugc2hvdWxk
IG5vdCBmYWNpbGl0YXRlIHN1Y2ggYmVoYXZpb3IuICBUaGF0IGNhc2UgYW5kIG91cnMgYXJlIG5v
dCBkaXJlY3RseSBjb21wYXJhYmxlLCBidXQgSU1PIG5vdCBkaXNzaW1pbGFyIGluIHRoZWlyIG5h
dHVyZS4NCg0KU3RlcGhhbg0KPg0KPkENCj4NCj4tLSANCj5BbmRyZXcgU3VsbGl2YW4NCj5hanNA
YW52aWx3YWxydXNkZW4uY29tDQo+DQo=


From nobody Thu May 11 10:43:28 2017
Return-Path: <dhc@dcrocker.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 15A7B13145A for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 10:43:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.908
X-Spam-Level: 
X-Spam-Status: No, score=0.908 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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=dcrocker.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 L92JsYJv7hrd for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 10:43:24 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.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 38C29129B98 for <ietf@ietf.org>; Thu, 11 May 2017 10:38:27 -0700 (PDT)
Received: from [10.37.39.100] (dncc-208-115-90-243.smartcity.com [208.115.90.243]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v4BHeqhP014329 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 11 May 2017 10:40:53 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1494524453; bh=crr/PtVfO2eohUGCsPFgnYx/B1Io/e1JbF80qFEjDVo=; h=Subject:To:Cc:References:Reply-To:From:Date:In-Reply-To:From; b=ltIwc9+7GA8gGdgMsbIdAML49KGK1dPddLejUnjZv4qoGBS2erdmYRCz2dnBcJLpI xD/ojINu1rUsLgZQy1Akef1tuxedMDbDIAvIo4AglK0/LVwGmdVoALAIB1vUKHI3VH Beuv0PK4vn4rZXx1DXIqPCw5amJ96kruuhnbvg7s=
Subject: Re: Registration for remote participation
To: Russ Housley <housley@vigilsec.com>, Andrew Sullivan <ajs@anvilwalrusden.com>
Cc: IETF <ietf@ietf.org>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <29052.1494439452@obiwan.sandelman.ca> <F4BF8089-0E62-4B3D-AE97-1F5ACC4196BC@stewe.org> <20170511121458.v62px5wrbh47zf3j@mx4.yitter.info> <F7BEFAC6-25C3-4907-A764-A9EF8FB90238@vigilsec.com>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <6c137e8d-d76b-fe8b-2ab7-64c806d1e98e@dcrocker.net>
Date: Thu, 11 May 2017 11:38:15 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0
MIME-Version: 1.0
In-Reply-To: <F7BEFAC6-25C3-4907-A764-A9EF8FB90238@vigilsec.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/M5FRtvv3uSE_5MV5g-k2wgsOXG0>
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, 11 May 2017 17:43:26 -0000

On 5/11/2017 11:19 AM, Russ Housley wrote:
>> We don't do that for in-person participants, because we no longer even
>> collect the email address on the blue sheets.  (
...
> Collecting an email address as part of the registration process does not mean that the email address needs to appear in the proceedings.

IETF f2f meetings do not even enforce the 'requirement' that one have 
registered.  Anyone /can/ walk in and sit in any of the meeting rooms. 
So the act and fact of registration is by community trust.

And as noted, one can write whatever one wants on the blue sheet.

To the extent that remote participation should approximate what is done 
for f2f, registration should give access, but there should be a 
separate, open-form 'blue sheet' step for the user to complete.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Thu May 11 11:23:09 2017
Return-Path: <julian.reschke@gmx.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 4E05E129B14; Thu, 11 May 2017 11:23:08 -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, 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 zsjTV-5NkuoM; Thu, 11 May 2017 11:23:04 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 A686813145D; Thu, 11 May 2017 11:16:58 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.111.224]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MW9TR-1dXOkY3cWv-00XNWQ; Thu, 11 May 2017 20:16:56 +0200
To: ietf@ietf.org
Cc: draft-nottingham-rfc5988bis@ietf.org
From: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: Last Call: <draft-nottingham-rfc5988bis-05.txt> (Web Linking) to Proposed Standard
Message-ID: <588716b3-161c-62ac-e5a9-a04c86f13e86@gmx.de>
Date: Thu, 11 May 2017 20:16:54 +0200
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; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:ewQl+Z6M2YpIopC7tlLabegpvY2kwa7PjO3OWYsIkN+qUaAz3JD bP6BR2uFOQ6WOqyQREgsw9c9t5e1JU6Sg5nOKohBeM5pjpXJK0GtrPeovT2t8pL8or7szUl nkX/xmhEaG0CMTS3uc9rUR1UfsbqZoQZeVOgDSzgFPIE5J7HeEsf54mDJLq2acoVa5ekYhw Az3j4LlsTrgSgGChZk28A==
X-UI-Out-Filterresults: notjunk:1;V01:K0:TjSj1I28BBI=:Sv22zGpfcEZvU+5e1Usn5g LYP9KmKykZI6nPDN2ucxGgsHFk27t6tCteznLxiwS03SXjwKEegxobuyv5ooTDbSEU0CFwZpN BwdT6ZVNz2XU+XwhK0lK+LyfAhB8DcwNEl3J+h4+K7MAiM2KUMMrTcIrpzODVICVvcAQdxtgu 9lWNNhzoitgI5iuYEFZUh4UmkvyqyOhNnFq6guND84UCUS+EGkyTltEi4NsxQ8nxsUshvCA3G RUkSvFoYcD5JRnE6yvGU4P+oqlHo1y4g7x79KCDzczFvYjhIdcDUbAXov8zyqpWDZvsMF5/6t Asi+93eYZ8TaT81SpeKnLvm9S49Jx/uwdcdD88rCZlvJmg3zuqFGlelFqkroNcydPt0veXech F1wMhqS3AI9/3QtMjd30Z18ETOQGHl9eUHD0HMiSHwOjxrnkhhoPtbKRukoqX4qnnwnwF7Jz1 fhL+kqEWuGn41j7coU1/zmEob0hp911fdKIxaP3lrpimyDJ00Gsj6dggS8r/0idbIRewlnuzg 9jnerWvKR/G7IQLTQ4vDnzDc0kAxItCr3tnHU9JuPUX7OXi4CgdpwLq0v92os5XQmth21E8Wx 2v0OIaHhI97C7OWuZpio3qsZS5eaQsOJjzqdeUWTedtgAsLYemENXJJ93eCHGdc5ev34ZiAoY Tk9hLOiUpmXfc5l+a8wnOrVXKe8aAqeuk7jtansSM5WMjF+nyTCbpkuuiCzCDIaSza6YWNaPm +jLbgKHcv6ZXMQT6GmDEGbasngwn/dlOZRgRVTqbQaNA77cikOJc0nOWvbwy+Ds2IYfIeLPe5 P6QI1Nt
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ey30QAyPv8tDkrJoSOjL1hnvaTw>
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, 11 May 2017 18:23:08 -0000

Here's my feedback, mainly editorial nits...:

    Additionally, the following rules are included from [RFC3986]: URI
    and URI-Reference; from [RFC6838]: type-name and subtype-name; from
    [W3C.CR-css3-mediaqueries-20090915]: media_query_list; and from
    [RFC5646]: Language-Tag.

That doesn't work, as "_" is not a legal ABNF character.

2.  Links

    In this specification, a link is a typed connection between two
    resources, and is comprised of:

    o  A _link context_,

    o  a _link relation type_ (Section 2.1),

    o  a _link target_, and

    o  optionally, _target attributes_ (Section 2.2).

It might be good to add forward references for "link context" and "link 
target" as well.

    Finally, links are consumed by _link applications_. Generally, an
    application will define the link relation type(s) it uses, along with
    the serialisation(s) that they might occur within.  For example, the
    application "Web browsing" looks for the "stylesheet" link relation
    type in the HTML link serialisation, whereas the application
    "AtomPub" uses the "edit" and "edit-media" link relations.

Actually, one popular browser also looks for the stylesheet link 
relation in the "Link" header field...

    Relation types are not to be confused with media types [RFC6838];

Media types are defined in RFC 2046; RFC 6838 is mainly about media type 
registrations.

    they do not identify the format of the representation that results
    when the link is dereferenced.  Rather, they only describe how the
    current context is related to another resource.

    o  *Reference*: Reference to the document that specifies the link
       relation type, preferably including a URI that can be used to
       retrieve a copy of the document.  An indication of the relevant
       section(s) MAY also be included, but is not required.

s/MAY/can/

    Note that relation types can be registered by third parties
    (including the Expert(s)), if the Expert(s) determine that an
    unregistered relation type is widely deployed and not likely to be
    registered in a timely manner.

maybe s/registered/registed otherwise/?

2.1.1.2.  Registration Request Processing

    Relation types are registered on the advice of a Designated Expert
    (appointed by the IESG or their delegate), with a Specification
    Required (using terminology from [RFC5226]).

s/[RFC5226]/Section 4.1 of [RFC5226]/


2.2.  Target Attributes

    This specification does not attempt to coordinate the name of target
    attributes, their cardinality or use.  Serialisations SHOULD
    coordinate their target attributes to avoid conflicts in semantics or
    syntax.

I'm not sure who's the audience for this SHOULD, and how to implement 
it. For instance, shouldn't this spec do this for the header field 
serialization?

3.  Link Serialisation in HTTP Headers

s/Headers/Header fields/

    This specification defines the link-params "rel", "anchor", "rev",
    "hreflang", "media", "title", "title*", and "type"; see Section 3.2,
    Section 3.3 and Section 3.4.

s/Section 3.2, Section 3.3 and Section 3.4/Sections 3.2, 3.3, and 3.4/

3.1.  Link Target

    Each link-value conveys one target IRI as a URI-Reference (after
    conversion to one, if necessary; see [RFC3987], Section 3.1) inside
    angle brackets ("<>").  If the URI-Reference is relative, parsers
    MUST resolve it as per [RFC3986], Section 5.  Note that any base IRI
    from the message's content is not applied.

Maybe s/base IRI from the message's content/base IRI appearing inside 
the message's content/

3.2.  Link Context

    By default, the context of a link conveyed in the Link header field
    is identity of the representation it is associated with, as defined
    in [RFC7231], Section 3.1.4.1, serialised as a URI.

Broken sentence: "is identity".

    The ABNF for the "anchor" parameter's value is:

      URI-Reference

s/URI-Reference/URI-Reference; Section 4.1 of [RFC3986]/

    Note that depending on HTTP status code and response headers, the
    link context might be "anonymous" (i.e., no link context is
    available).  For example, this is the case on a 404 response to a GET
    request.

I understand this is identical in RFC 5988, but where does this actually 
come from? It basically restricts use of anchor-less link header fields 
2xx responses, right?

3.3.  Relation Type

    The ABNF for the "rel" and "rev" parameters' values is:

      relation-type *( 1*SP relation-type )

    where:

      relation-type  = reg-rel-type | ext-rel-type

Finally I can use this link https://www.youtube.com/watch?v=LbK-g8tKnoc 
in LC feedback!

      reg-rel-type   = LOALPHA *( LOALPHA | DIGIT | "." | "-" )
      ext-rel-type   = URI

s/URI/URI; Section 3 of [RFC3986]/

    Note that extension relation types are REQUIRED to be absolute URIs
    in Link headers, and MUST be quoted if they contain a semicolon (";")

s/headers/header fields/

    or comma (",") (as these characters are used as delimiters in the
    header field itself).

There are more characters legal in URIs but illegal in token -- so maybe 
phrasing it like this can cause confusion. Maybe "MUST be quoted when 
they contain characters not allowed in tokens, such as ...."?

3.4.1.  Serialisation-Defined Attributes

    The ABNF for the "type" parameter's value is:

      type-name "/" subtype-name

(maybe point to https://tools.ietf.org/html/rfc6838#section-4.2 here)


3.5.  Link Header Field Examples

Maybe add an example for multiple Link header field instances in a 
single message?


4.1.  Link HTTP Header Field Registration

    Header field: Link
    Applicable protocol: http
    Status: standard
    Author/change controller:
        IETF  (iesg@ietf.org)
        Internet Engineering Task Force
    Specification document(s):
        [RFC&rfc.number;]

s/[RFC&rfc.number;]/this document/


4.2.  Link Relation Type Registry

    Each published document will be at a URL mutually agreed to by IANA
    and the Expert(s), and IANA will set HTTP response headers on them as
    (reasonably) requested by the Expert(s).

Wow. Does IANA know that we want to configure their web server?


5.  Security Considerations

    Link applications ought to consider the attack vectors opened by
    automatically following, trusting, or otherwise using links gathered
    from HTTP headers.  In particular, Link header fields that use the

s/headers/header fields/

    "anchor" parameter to associate a link's context with another
    resource are to be treated with due caution.

    The Link header field makes extensive use of IRIs and URIs.  See
    [RFC3987] for security considerations relating to IRIs.  See
    [RFC3986] for security considerations relating to URIs.  See
    [RFC7230] for security considerations relating to HTTP headers.

s/headers/header fields/

7.1.  Normative References

    [W3C.CR-css3-mediaqueries-20090915]
               Lie, H., Celik, T., Glazman, D., and A. Kesteren, "Media
               Queries", World Wide Web Consortium CR CR-css3-
               mediaqueries-20090915, September 2009,
               <http://www.w3.org/TR/2009/CR-css3-mediaqueries-20090915>.

Need to update to 
<https://www.w3.org/TR/2012/REC-css3-mediaqueries-20120619/>.

    [W3C.REC-html5-20141028]
               Hickson, I., Berjon, R., Faulkner, S., Leithead, T.,
               Navara, E., O&#039;Connor, T., and S. Pfeiffer, "HTML5",
               World Wide Web Consortium Recommendation REC-
               html5-20141028, October 2014,
               <http://www.w3.org/TR/2014/REC-html5-20141028>.

Broken escape in author name.


A.1.  Link Serialisation in HTML

    HTML5 ([W3C.REC-html5-20141028]) Section 4.8 defines modern HTML

"Section 4.8 of HTML5"

    links.  That document links to the Microformats Wiki as a registry;
    over time, the IANA registry ought to mirror its contents, and
    ideally eventually replace it (although that depends on the HTML
    community).


Appendix B.  Algorithm for Parsing Link Headers

    Given a HTTP header field-value "field_value" as a string assuming
    ASCII encoding, the following algorithm can be used to parse it into
    the model described by this specification:

This part is a bit scary -- I don't know how to review it. It might be 
better to have code in an actual programming language, and a set of 
tests for it.

    1.  Let "links" be an empty list.

    2.  Create "link_strings" by splitting "field_value" on ","
        characters, excepting "," characters within quoted strings as per

I have my doubts that people will be able to translate it into actually 
correct code. To detect whether something is inside a quoted-string 
essentially requires running a parser; the prose here suggests that this 
is not necessary.

It also should mention that there might be multiple instances of 
field_value.


From nobody Thu May 11 11:57:44 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 DE194129442; Thu, 11 May 2017 11:57:33 -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 d_c3en6yA7-B; Thu, 11 May 2017 11:57:30 -0700 (PDT)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::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 B0439129C06; Thu, 11 May 2017 11:52:19 -0700 (PDT)
Received: by mail-qk0-x236.google.com with SMTP id u75so30270897qka.3; Thu, 11 May 2017 11:52: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 :cc; bh=a825Gq36ZloTLXauiOQKs0SQrIYAc8wiRvoC+9B5vwc=; b=f3JWHKenhTfBoQX7KkdsTgKZQl2u7XxiKLRBSiAhWJp148bpsIVueQMmV+kHioH0GJ dNV3pp5QXXTyMRAwQHBRfn7v8FxCOS5Ln9mqs187vRkPbgYVaGLs8x7xB37ye4B1JZ/M ByrNtJ0SwdyBfBjniWnKk4cMrhVJD57NRWWOdpEOemulX9Vs/NR1UJ+6aHfpxlXv6GS0 sky+8mAzHEitdfmEoX8ZTaapMxEV6YhO8Dg0N953DI8So8KRm3wCv5QYNAMh+EQwNY9d 5cr2j/AdVnEK5t0/VdXZSmF3NCZGc4qc7z2yCOVcr+8v38tjgGJ299NtfKQI61ow5dVP hzUQ==
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=a825Gq36ZloTLXauiOQKs0SQrIYAc8wiRvoC+9B5vwc=; b=NJMry+pgJkDtfyFe8OI0dEIN/SJohvYwURUEbRTB28fTZs13veIkgGRhFLWTUCsumu FW0TxpT11IXEl0sw3xXW8H+a6ZbIHNIa5WR2lQLx4nM9th6lfHj3J5+0A55LWSRYkOvJ wULCdtg7h2SUnRIfNPSDJ8xVvA70T84IxXpZod1i3dNdJiIU5UUnJKomL7UPQ2MWk3Uf RIaZ86opwIxmbPoGXOMqZjukYoA0WYUcem0T+NFQokx3/eK+tEpvaHhwCmx1ZPVd1MgF wyfHXpyyjimC/zS99y+xEum92YJ7LLgFvIsXB8JL0Et9TA95LZwjUI+O76k5wgZSVfOV pQww==
X-Gm-Message-State: AODbwcBO24YIK4QOQbj2bmDU1Lnb/9P1zzARPZoIwznLLWAp4Jc3vd1n 3AZpyPBU+jozfosNfW+z0TBpugwjTEG0
X-Received: by 10.55.43.144 with SMTP id r16mr256684qkr.213.1494528738801; Thu, 11 May 2017 11:52:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.19.39 with HTTP; Thu, 11 May 2017 11:52:18 -0700 (PDT)
In-Reply-To: <4D7F4AD313D3FC43A053B309F97543CF25F9B072@njmtexg4.research.att.com>
References: <149450075072.16690.14546662616864459158@ietfa.amsl.com> <4D7F4AD313D3FC43A053B309F97543CF25F9B072@njmtexg4.research.att.com>
From: Dan Romascanu <dromasca@gmail.com>
Date: Thu, 11 May 2017 21:52:18 +0300
Message-ID: <CAFgnS4UAfMe5L7k=zwCqfUjgz14ArBpTE_bz675dCf0_Jk21fg@mail.gmail.com>
Subject: Re: Genart last call review of draft-ietf-bmwg-vswitch-opnfv-03
To: "MORTON, ALFRED C (AL)" <acmorton@att.com>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>,  "draft-ietf-bmwg-vswitch-opnfv.all@ietf.org" <draft-ietf-bmwg-vswitch-opnfv.all@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>, "bmwg@ietf.org" <bmwg@ietf.org>
Content-Type: multipart/alternative; boundary=001a11471648953f5e054f4416ef
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FOHSZD132NkmgJESrDjO8ePVnBg>
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, 11 May 2017 18:57:34 -0000

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

Hi,

Please see in-line.

Regards,

Dan


On Thu, May 11, 2017 at 8:00 PM, MORTON, ALFRED C (AL) <acmorton@att.com>
wrote:

> Hi Dan,
> please see replies, [ACM], below.
>
> > -----Original Message-----
> > From: Dan Romascanu [mailto:dromasca@gmail.com]
> > Sent: Thursday, May 11, 2017 7:06 AM
> > To: gen-art@ietf.org
> > Cc: draft-ietf-bmwg-vswitch-opnfv.all@ietf.org; ietf@ietf.org;
> > bmwg@ietf.org; dromasca@gmail.com
> > Subject: Genart last call review of draft-ietf-bmwg-vswitch-opnfv-03
> >
> > 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://urldefense.proofpoint.com/v2/url?u=https-
> > 3A__trac.ietf.org_trac_gen_wiki_GenArtfaq&d=DwICaQ&c=LFYZ-
> > o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=NTVlLBN-
> > L3u9zGPHm_CNVcXW7_OGX8_18CtaAalZin0&s=2Hr-
> > dhKaDHIguY7W97z33RlKjqPDtmoYmM2-jWrbS-o&e= >.
> >
> > Document: draft-ietf-bmwg-vswitch-opnfv-03
> > Reviewer: Dan Romascanu
> > Review Date: 2017-05-11
> > IETF LC End Date: 2017-05-15
> > IESG Telechat date: Not scheduled for a telechat
> >
> > Summary:
> >
> > Almost Ready.
> >
> > This document describes describes the progress of the Open Platform
> > for NFV (OPNFV) project on virtual switch performance "VSPERF". That
> > project reuses the BMWG framework and specifications to benchmark
> > virtual switches implemented in general-purpose hardware. Some
> > differences with the benchmarking of specialized HW platforms are
> > identified and they may become work items for BMWG in the future. It's
> > a well written and clear document, but I have reservations about it
> > being published as an RFC, and I cannot find coverage for it in the WG
> > charter. I also have concerns that parts of the methodology used by
> > OPNFV break the BMWG principles, especially repeatability and
> > 'black-box', and this is not clear enough articulated in the document.
> [ACM]
> Ok, let's address your specific issues, and come back to your reservations.
>
> >
> >
> > Major issues:
> >
> > 1. It is not clear to me why this document needs to be published as an
> > RFC. The introduction says: 'This memo describes the progress of the
> > Open Platform for NFV (OPNFV) project on virtual switch performance
> > "VSPERF".  This project intends to build on the current and completed
> > work of the Benchmarking Methodology Working Group in IETF, by
> > referencing existing literature.' Why should the WG and the IESG
> > invest resources in publishing this, why an I-D or an Independent
> > Stream RFC is not sufficient?
> [ACM]
> The WG considered and discussed this document over 3 revisions
> and a year of time before reaching consensus to develop it further
> as a chartered item, so this decision was not taken lightly.
> See more below.
>
> > The WG charter says something about:
> > 'VNF and Related Infrastructure Benchmarking: Benchmarking
> > Methodologies have reliably characterized many physical devices. This
> > work item extends and enhances the methods to virtual network
> > functions (VNF) and their unique supporting infrastructure. A first
> > deliverable from this activity will be a document that considers the
> > new benchmarking space to ensure that common issues are recognized
> > from the start, using background materials from industry and SDOs
> > (e.g., IETF, ETSI NFV).'. I do not believe that this document covers
> > the intent of the charter, as it focused on one organization only.
> [ACM]
> I'm sorry, but here you are mistaken. The document that satisfied
> the "first deliverable ... document that considers the new benchmarking
> space"
> is: https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05
> titled: Considerations for Benchmarking Virtual Network Functions and
> Their Infrastructure
> which has been submitted to IESG and approved for publication.
> Further, the current draft (draft-ietf-bmwg-vswitch-opnfv-03)
> references the approved "Considerations" draft in Section 3
> (as does almost every related Industry spec I'm aware of).
>
> The BMWG Charter continues:
>   Benchmarks for platform capacity and performance characteristics of
>   virtual routers, switches, and related components will follow, including
>   comparisons between physical and virtual network functions. In many
> cases,
>   the traditional benchmarks should be applicable to VNFs, but the lab
>   set-ups, configurations, and measurement methods will likely need to
>   be revised or enhanced.
>
> This draft constitutes one of several follow-on efforts, approaching
> the problem exactly as we described in the last sentence above.
>

How? What last sentence?

Is it:

'In many cases,
  the traditional benchmarks should be applicable to VNFs, but the lab
  set-ups, configurations, and measurement methods will likely need to
  be revised or enhanced.'

How does this document approach this problem? If there is a need to revise
or enhance existing BMWG work, what is needed is specific revisions of
documents. This informational document only documents work in one external
organization. I have reservations that this is a WG task to advance this
document, and of the IESG to approve it. Why can't it stand as an I-D until
the WG decides whatever work needs to be undertaken (if any) to meet the
OPNFV needs? Or if they with to have an RFC, why can't it be Independent
Stream?

Will the WG write similar documents for all (or several) other
organizations that implement VNFs one way or another? Should it?


> An aspect of Industry collaboration that we did not anticipate in the
> BMWG Charter is our current interactions with Open Source Communities.
> The current Charter was approved in June 2014, then OPNFV was founded
> on September 30, 2014 [0] and the VSPERF Project was created on
> Dec 16, 2014, so we did not anticipate extensive collaboration on
> this and other benchmarking topics.
>
>
>
> >
> > 2. In section 3 there 'repeatability' is mentioned, while
> > acknowledging that in a virtual environment there is no guarantee and
> > actually no way to know what other applications are being run.
> [ACM]
> See:
> https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#section-3.4
>
> There are certainly ways to assess the current set of processes
> at a particular time. The Software configuration parameters in
> Section 3.3 are intended to capture this aspect as part of set-up.
> At the same time, there will be challenges to assess the DUT
> performance when resources are fully shared, and new testing
> strategies will be needed:
> https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#section-3.3
>
>
> > Measuring parameters as the ones listed in 3.3 provides just part of
> > the answer, and they are internal parameters to the SUT.
> [ACM]
> Yes, knowing the tested configuration is a critical pillar
> supporting repeatability (these items are not measured, but configured),
> and why we provided this section.
>
> > Also, the
> > different deployment scenarios in section 4 require different
> > configurations for the SUT, thus breaking the 'black-box' principle.
> [ACM]
> Specifying DUT configuration does not break any part of the
> black-box principle, which establishes that benchmark measurements
> will be based on externally observable phenomena. See:
> https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#section-4.2
>
> Previous BMWG RFCs have identified the critical configuration
> parameters of the DUT, such as the number and type of
> network interfaces, the arrangement of DUTs in a SUT, etc.
>

I may have not been clear enough. The document talks about repeatability
and about comparing benchmarks with the ones of specialized HW
implementations. Then it goes into a long but still partial list of factors
that can influence the benchmarking, the majority of them depend on the HW
and SW measurements and parameters of the internal systems. How can this be
compared with a number of small and indeed externally observable
configuration parameters like the number and type of network interfaces.
This is several degrees of magnitude apart in complexity.

>
> > I believe that there is a need for a more clear explanation of why BMWG
> > specifications are appropriate and how comparison can be made while
> > repeatability cannot be ensured, and measurements are dependent upon
> > parameters internal to the SUT.
> [ACM]
> I believe that draft-ietf-bmwg-virtual-net-05 already
> indicates why the existing BMWG RFCs are a reasonable
> starting place for NFV benchmarks, in part because
> we want to measure the same benchmarks of physical
> network functions in many cases. See
> https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#section-4.1
>
> Repeatability is a goal of all experiments, and we understand
> that there is more work to do in this regard, but what
> we know now (documented in this draft) should
> be a valuable contribution to the Industry.
>
>
Measuring the same benchmarks is a good goal. I believe that the claim of
repeatability needs to be better argued.


>
> >
> > Minor issues:
> >
> > 1. Some of the tests mentioned in Section 4 have no prior or in
> > progress work in the IETF: Control Path and Datapath Coupling Tests,
> > Noisy Neighbour Tests, characterization of acceleration technologies.
> [ACM]
> I'm sorry, but that's not an accurate portrayal of BMWG's literature.
>
> https://tools.ietf.org/html/rfc6413 examined Control Plane/Dataplane
> interactions, for example.
>
> https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#section-3.3
> item 2 specifically included Noisy Neighbour among the new
> testing strategies.
>
>
Please provide references for each in text.


> Every network interface with an ASIC is an example of acceleration,
> one that we've characterized in physical network devices for years.
>
>
Yes, but we do not deal here with externally observable interfaces only,
and if the characterization of the acceleration technologies matters than
you need a way to express it (where can we find it in existing BMWG work?
new work?)


> > If new work is needed / proposed to be added for the BMWG scope and
> > framework it would be useful for BMWG to list these separately.
> >
> >
> > Nits/editorial comments:
> >
> > 1. What is called 'Deployment scenarios' from VS perspective in
> > Section 4 describe in fact different configurations of the SUT in BMWG
> > terms. It seems better to separate this second part of section 4 in a
> > separate section. If it belongs to an existing section it rather
> > belongs in 3 than in 4.
> >
> [ACM]
> Section 3 is more about extending the configuration guidance
> from https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-
> 05#section-3.2
>
> Section 4 summarizes the VSPERF Level Test Design document,
> of which these deployment scenarios are a key part.
>

Yes, but this seams to belong to configurations of SUTs, even if they are
called 'Deployment scenarios' in OPNFV-speak, and they impact
repeatibility.


>
> thanks for your comments; hopefully this detailed reply
> will reduce your reservations about publication.
>
> Al
> (for the co-authors)
>
> [0] https://www.opnfv.org/announcements/2014/09/30/
> telecom-industry-and-vendors-unite-to-build-common-open-
> platform-to-accelerate-network-functions-virtualization
>
>

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

<div dir=3D"ltr"><div><div><div>Hi, <br><br></div>Please see in-line. <br><=
br></div>Regards,<br><br></div>Dan<br><br><div><div><div><div class=3D"gmai=
l_extra"><br><div class=3D"gmail_quote">On Thu, May 11, 2017 at 8:00 PM, MO=
RTON, ALFRED C (AL) <span dir=3D"ltr">&lt;<a href=3D"mailto:acmorton@att.co=
m" target=3D"_blank">acmorton@att.com</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">Hi Dan,<br>
please see replies, [ACM], below.<br>
<span class=3D"gmail-"><br>
&gt; -----Original Message-----<br>
&gt; From: Dan Romascanu [mailto:<a href=3D"mailto:dromasca@gmail.com">drom=
asca@gmail.com</a>]<br>
&gt; Sent: Thursday, May 11, 2017 7:06 AM<br>
&gt; To: <a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br>
&gt; Cc: <a href=3D"mailto:draft-ietf-bmwg-vswitch-opnfv.all@ietf.org">draf=
t-ietf-bmwg-vswitch-opnfv.<wbr>all@ietf.org</a>; <a href=3D"mailto:ietf@iet=
f.org">ietf@ietf.org</a>;<br>
&gt; <a href=3D"mailto:bmwg@ietf.org">bmwg@ietf.org</a>; <a href=3D"mailto:=
dromasca@gmail.com">dromasca@gmail.com</a><br>
&gt; Subject: Genart last call review of draft-ietf-bmwg-vswitch-opnfv-<wbr=
>03<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>
</span>&gt; &lt;<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhtt=
ps-" rel=3D"noreferrer" target=3D"_blank">https://urldefense.<wbr>proofpoin=
t.com/v2/url?u=3Dhttps-</a><br>
&gt; 3A__trac.ietf.org_trac_gen_<wbr>wiki_GenArtfaq&amp;d=3DDwICaQ&amp;c=3D=
<wbr>LFYZ-<br>
&gt; o9_HUMeMTSQicvjIg&amp;r=3D<wbr>OfsSu8kTIltVyD1oL72cBw&amp;m=3D<wbr>NTV=
lLBN-<br>
&gt; L3u9zGPHm_CNVcXW7_OGX8_<wbr>18CtaAalZin0&amp;s=3D2Hr-<br>
&gt; dhKaDHIguY7W97z33RlKjqPDtmoYmM<wbr>2-jWrbS-o&amp;e=3D &gt;.<br>
&gt;<br>
&gt; Document: draft-ietf-bmwg-vswitch-opnfv-<wbr>03<br>
<span class=3D"gmail-">&gt; Reviewer: Dan Romascanu<br>
&gt; Review Date: 2017-05-11<br>
&gt; IETF LC End Date: 2017-05-15<br>
&gt; IESG Telechat date: Not scheduled for a telechat<br>
&gt;<br>
&gt; Summary:<br>
&gt;<br>
&gt; Almost Ready.<br>
&gt;<br>
&gt; This document describes describes the progress of the Open Platform<br=
>
&gt; for NFV (OPNFV) project on virtual switch performance &quot;VSPERF&quo=
t;. That<br>
&gt; project reuses the BMWG framework and specifications to benchmark<br>
&gt; virtual switches implemented in general-purpose hardware. Some<br>
&gt; differences with the benchmarking of specialized HW platforms are<br>
&gt; identified and they may become work items for BMWG in the future. It&#=
39;s<br>
&gt; a well written and clear document, but I have reservations about it<br=
>
&gt; being published as an RFC, and I cannot find coverage for it in the WG=
<br>
&gt; charter. I also have concerns that parts of the methodology used by<br=
>
&gt; OPNFV break the BMWG principles, especially repeatability and<br>
&gt; &#39;black-box&#39;, and this is not clear enough articulated in the d=
ocument.<br>
</span>[ACM]<br>
Ok, let&#39;s address your specific issues, and come back to your reservati=
ons.<br>
<span class=3D"gmail-"><br>
&gt;<br>
&gt;<br>
&gt; Major issues:<br>
&gt;<br>
&gt; 1. It is not clear to me why this document needs to be published as an=
<br>
&gt; RFC. The introduction says: &#39;This memo describes the progress of t=
he<br>
&gt; Open Platform for NFV (OPNFV) project on virtual switch performance<br=
>
&gt; &quot;VSPERF&quot;.=C2=A0 This project intends to build on the current=
 and completed<br>
&gt; work of the Benchmarking Methodology Working Group in IETF, by<br>
&gt; referencing existing literature.&#39; Why should the WG and the IESG<b=
r>
&gt; invest resources in publishing this, why an I-D or an Independent<br>
&gt; Stream RFC is not sufficient?<br>
</span>[ACM]<br>
The WG considered and discussed this document over 3 revisions<br>
and a year of time before reaching consensus to develop it further<br>
as a chartered item, so this decision was not taken lightly.<br>
See more below.<br>
<span class=3D"gmail-"><br>
&gt; The WG charter says something about:<br>
&gt; &#39;VNF and Related Infrastructure Benchmarking: Benchmarking<br>
&gt; Methodologies have reliably characterized many physical devices. This<=
br>
&gt; work item extends and enhances the methods to virtual network<br>
&gt; functions (VNF) and their unique supporting infrastructure. A first<br=
>
&gt; deliverable from this activity will be a document that considers the<b=
r>
&gt; new benchmarking space to ensure that common issues are recognized<br>
&gt; from the start, using background materials from industry and SDOs<br>
&gt; (e.g., IETF, ETSI NFV).&#39;. I do not believe that this document cove=
rs<br>
&gt; the intent of the charter, as it focused on one organization only.<br>
</span>[ACM]<br>
I&#39;m sorry, but here you are mistaken. The document that satisfied<br>
the &quot;first deliverable ... document that considers the new benchmarkin=
g space&quot;<br>
is: <a href=3D"https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05" =
rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>draft=
-ietf-bmwg-virtual-net-05</a><br>
titled: Considerations for Benchmarking Virtual Network Functions and Their=
 Infrastructure<br>
which has been submitted to IESG and approved for publication.<br>
Further, the current draft (draft-ietf-bmwg-vswitch-<wbr>opnfv-03)<br>
references the approved &quot;Considerations&quot; draft in Section 3<br>
(as does almost every related Industry spec I&#39;m aware of).<br>
<br>
The BMWG Charter continues:<br>
=C2=A0 Benchmarks for platform capacity and performance characteristics of<=
br>
=C2=A0 virtual routers, switches, and related components will follow, inclu=
ding<br>
=C2=A0 comparisons between physical and virtual network functions. In many =
cases,<br>
=C2=A0 the traditional benchmarks should be applicable to VNFs, but the lab=
<br>
=C2=A0 set-ups, configurations, and measurement methods will likely need to=
<br>
=C2=A0 be revised or enhanced.<br>
<br>
This draft constitutes one of several follow-on efforts, approaching<br>
the problem exactly as we described in the last sentence above.<br></blockq=
uote><div><br></div><div>How? What last sentence? <br><br></div><div>Is it:=
 <br></div><div><br>&#39;In many cases,<br>
=C2=A0 the traditional benchmarks should be applicable to VNFs, but the lab=
<br>
=C2=A0 set-ups, configurations, and measurement methods will likely need to=
<br>
=C2=A0 be revised or enhanced.&#39;<br><br></div><div>How does this documen=
t approach this problem? If there is a need to revise or enhance existing B=
MWG work, what is needed is specific revisions of documents. This informati=
onal document only documents work in one external organization. I have rese=
rvations that this is a WG task to advance this document, and of the IESG t=
o approve it. Why can&#39;t it stand as an I-D until the WG decides whateve=
r work needs to be undertaken (if any) to meet the OPNFV needs? Or if they =
with to have an RFC, why can&#39;t it be Independent Stream? <br><br></div>=
<div>Will the WG write similar documents for all (or several) other organiz=
ations that implement VNFs one way or another? Should it?<br></div><div><br=
> </div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
An aspect of Industry collaboration that we did not anticipate in the<br>
BMWG Charter is our current interactions with Open Source Communities.<br>
The current Charter was approved in June 2014, then OPNFV was founded<br>
on September 30, 2014 [0] and the VSPERF Project was created on<br>
Dec 16, 2014, so we did not anticipate extensive collaboration on<br>
this and other benchmarking topics.<br>
<span class=3D"gmail-"><br>
<br>
<br>
&gt;<br>
&gt; 2. In section 3 there &#39;repeatability&#39; is mentioned, while<br>
&gt; acknowledging that in a virtual environment there is no guarantee and<=
br>
&gt; actually no way to know what other applications are being run.<br>
</span>[ACM]<br>
See:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#secti=
on-3.4" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<w=
br>draft-ietf-bmwg-virtual-net-<wbr>05#section-3.4</a><br>
<br>
There are certainly ways to assess the current set of processes<br>
at a particular time. The Software configuration parameters in<br>
Section 3.3 are intended to capture this aspect as part of set-up.<br>
At the same time, there will be challenges to assess the DUT<br>
performance when resources are fully shared, and new testing<br>
strategies will be needed:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#secti=
on-3.3" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<w=
br>draft-ietf-bmwg-virtual-net-<wbr>05#section-3.3</a><br>
<span class=3D"gmail-"><br>
<br>
&gt; Measuring parameters as the ones listed in 3.3 provides just part of<b=
r>
&gt; the answer, and they are internal parameters to the SUT.<br>
</span>[ACM]<br>
Yes, knowing the tested configuration is a critical pillar<br>
supporting repeatability (these items are not measured, but configured),<br=
>
and why we provided this section.<br>
<span class=3D"gmail-"><br>
&gt; Also, the<br>
&gt; different deployment scenarios in section 4 require different<br>
&gt; configurations for the SUT, thus breaking the &#39;black-box&#39; prin=
ciple.<br>
</span>[ACM]<br>
Specifying DUT configuration does not break any part of the<br>
black-box principle, which establishes that benchmark measurements<br>
will be based on externally observable phenomena. See:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#secti=
on-4.2" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<w=
br>draft-ietf-bmwg-virtual-net-<wbr>05#section-4.2</a><br>
<br>
Previous BMWG RFCs have identified the critical configuration<br>
parameters of the DUT, such as the number and type of<br>
network interfaces, the arrangement of DUTs in a SUT, etc.<br></blockquote>=
<div><br></div><div>I may have not been clear enough. The document talks ab=
out repeatability and about comparing benchmarks with the ones of specializ=
ed HW implementations. Then it goes into a long but still partial list of f=
actors that can influence the benchmarking, the majority of them depend on =
the HW and SW measurements and parameters of the internal systems. How can =
this be compared with a number of small and indeed externally observable co=
nfiguration parameters like the number and type of network interfaces. This=
 is several degrees of magnitude apart in complexity.=C2=A0 <br></div><bloc=
kquote 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-"><br>
&gt; I believe that there is a need for a more clear explanation of why BMW=
G<br>
&gt; specifications are appropriate and how comparison can be made while<br=
>
&gt; repeatability cannot be ensured, and measurements are dependent upon<b=
r>
&gt; parameters internal to the SUT.<br>
</span>[ACM]<br>
I believe that draft-ietf-bmwg-virtual-net-05 already<br>
indicates why the existing BMWG RFCs are a reasonable<br>
starting place for NFV benchmarks, in part because<br>
we want to measure the same benchmarks of physical<br>
network functions in many cases. See<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#secti=
on-4.1" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<w=
br>draft-ietf-bmwg-virtual-net-<wbr>05#section-4.1</a><br>
<br>
Repeatability is a goal of all experiments, and we understand<br>
that there is more work to do in this regard, but what<br>
we know now (documented in this draft) should<br>
be a valuable contribution to the Industry.<br>
<span class=3D"gmail-"><br></span></blockquote><div><br></div><div>Measurin=
g the same benchmarks is a good goal. I believe that the claim of repeatabi=
lity needs to be better argued. <br>=C2=A0<br></div><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"><span class=3D"gmail-">
<br>
&gt;<br>
&gt; Minor issues:<br>
&gt;<br>
&gt; 1. Some of the tests mentioned in Section 4 have no prior or in<br>
&gt; progress work in the IETF: Control Path and Datapath Coupling Tests,<b=
r>
&gt; Noisy Neighbour Tests, characterization of acceleration technologies.<=
br>
</span>[ACM]<br>
I&#39;m sorry, but that&#39;s not an accurate portrayal of BMWG&#39;s liter=
ature.<br>
<br>
<a href=3D"https://tools.ietf.org/html/rfc6413" rel=3D"noreferrer" target=
=3D"_blank">https://tools.ietf.org/html/<wbr>rfc6413</a> examined Control P=
lane/Dataplane<br>
interactions, for example.<br>
<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#secti=
on-3.3" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<w=
br>draft-ietf-bmwg-virtual-net-<wbr>05#section-3.3</a><br>
item 2 specifically included Noisy Neighbour among the new<br>
testing strategies.<br>
<br></blockquote><div><br></div><div>Please provide references for each in =
text. <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"=
>
Every network interface with an ASIC is an example of acceleration,<br>
one that we&#39;ve characterized in physical network devices for years.<br>
<span class=3D"gmail-"><br></span></blockquote><div><br></div><div>Yes, but=
 we do not deal here with externally observable interfaces only, and if the=
 characterization of the acceleration technologies matters than you need a =
way to express it (where can we find it in existing BMWG work? new work?)<b=
r>=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"><span c=
lass=3D"gmail-">
&gt; If new work is needed / proposed to be added for the BMWG scope and<br=
>
&gt; framework it would be useful for BMWG to list these separately.<br>
&gt;<br>
&gt;<br>
&gt; Nits/editorial comments:<br>
&gt;<br>
&gt; 1. What is called &#39;Deployment scenarios&#39; from VS perspective i=
n<br>
&gt; Section 4 describe in fact different configurations of the SUT in BMWG=
<br>
&gt; terms. It seems better to separate this second part of section 4 in a<=
br>
&gt; separate section. If it belongs to an existing section it rather<br>
&gt; belongs in 3 than in 4.<br>
&gt;<br>
</span>[ACM]<br>
Section 3 is more about extending the configuration guidance<br>
from <a href=3D"https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#=
section-3.2" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/ht=
ml/<wbr>draft-ietf-bmwg-virtual-net-<wbr>05#section-3.2</a><br>
<br>
Section 4 summarizes the VSPERF Level Test Design document,<br>
of which these deployment scenarios are a key part.<br></blockquote><div><b=
r></div><div>Yes, but this seams to belong to configurations of SUTs, even =
if they are called &#39;Deployment scenarios&#39; in OPNFV-speak, and they =
impact repeatibility. <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>
thanks for your comments; hopefully this detailed reply<br>
will reduce your reservations about publication.<br>
<br>
Al<br>
(for the co-authors)<br>
<br>
[0] <a href=3D"https://www.opnfv.org/announcements/2014/09/30/telecom-indus=
try-and-vendors-unite-to-build-common-open-platform-to-accelerate-network-f=
unctions-virtualization" rel=3D"noreferrer" target=3D"_blank">https://www.o=
pnfv.org/<wbr>announcements/2014/09/30/<wbr>telecom-industry-and-vendors-<w=
br>unite-to-build-common-open-<wbr>platform-to-accelerate-<wbr>network-func=
tions-<wbr>virtualization</a><br>
<br>
</blockquote></div><br></div></div></div></div></div>

--001a11471648953f5e054f4416ef--


From nobody Thu May 11 15:33:05 2017
Return-Path: <housley@vigilsec.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 116DC1292AE; Thu, 11 May 2017 15:33:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Russ Housley <housley@vigilsec.com>
To: <secdir@ietf.org>
Cc: draft-ietf-pals-vpls-pim-snooping.all@ietf.org, ietf@ietf.org, pals@ietf.org
Subject: Secdir last call review of draft-ietf-pals-vpls-pim-snooping-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149454198305.16624.16060763979327626869@ietfa.amsl.com>
Date: Thu, 11 May 2017 15:33:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5MThHU8i0CrXWvHloA3zBdhSUQc>
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, 11 May 2017 22:33:03 -0000

Reviewer: Russ Housley
Review result: Has Nits

I 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 authors, document editors, and WG chairs should
treat these comments just like any other IETF Last Call comments.

Document: draft-ietf-pals-vpls-pim-snooping-05
Reviewer: Russ Housley
Review Date: 2016-05-11
IETF LC End Date: 2017-05-19
IESG Telechat date: Unknown

Summary: Has Nits

I did not review the state machines in detail.  I assume that others
that are far more familiar with PIM have done s detailed review of
them.


No Major Concerns


Minor Concerns

Section 1 says:

   In that case, the PW related concept/procedures are not
   applicable and that's all.

I am not sure what you are trying to tell the implementer.
Please clarify.

Section 1.3 includes: "rpt : Rendezvous Point", and Section 2.3
includes: "Rendezvous Points (RP)".  Please pick one and use it
throughout.

In Section 2.2, please add a reference for the "split-horizon rule
for mesh PWs" or add a pointer to the section where it is discussed
further in this document.

A better heading for Section 2.3.2 would be "IPv4 and IPv6".


Nits

Please change the language that makes reference to other "draft",
such
as: "As stated in the VPLS Multicast Requirements draft ...".  This
wording leads to changes by the RFC Editor, so it is better to use a
word like "document".

Please change "J/P messages" to "Join/Prune messages" throughout the
document.

The document uses both "learned" and "learnt".  If there is a
difference
to the reader, it was too subtle for me to figure out.  If they are
the
same, please pick one.

In Section 1.1, rewording would add clarity:

   Depending on how the control messages are handled
   (transparently flooded, selectively forwarded, aggregated), the
   procedure/process may be called Snooping or proxy in different
   contexts.

I suggest:

   Depending on whether the control messages are
   transparently flooded, selectively forwarded, or aggregated, the
   processing may be called Snooping or proxy in different contexts.

Section 2.3 says:

   However, the PE does not need to have any routing tables like as
   required in PIM multicast routing.

Please correct.  I think you are trying to say:

   However, the PE does not need any routing tables like those
   required in PIM multicast routing.

Section 4.2.1 says:

   Note that the differences apply only to PIM Join/Prune messages. 
PIM
   Hello messages are snooped and flooded in all cases.

Wouldn't it be more clear to consume the same number of lines and add
this information to the table.

In Section 2.7 the document uses PIM-BIDIR and BIDIR-PIM, and they
seem
have the same meaning.  Please pick one.



From nobody Thu May 11 16:09:55 2017
Return-Path: <rsk@gsp.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 020B912951F for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 16:09:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.501
X-Spam-Level: 
X-Spam-Status: No, score=-1.501 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 QjEYmSu0W6e0 for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 16:09:52 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 301F912953B for <ietf@ietf.org>; Thu, 11 May 2017 16:05:28 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id v4BN5QqS019776 for <ietf@ietf.org>; Thu, 11 May 2017 19:05:26 -0400 (EDT)
Date: Thu, 11 May 2017 19:05:26 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: Registration for remote participation
Message-ID: <20170511230526.GA9893@gsp.org>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <29052.1494439452@obiwan.sandelman.ca> <F4BF8089-0E62-4B3D-AE97-1F5ACC4196BC@stewe.org> <20170511121458.v62px5wrbh47zf3j@mx4.yitter.info> <C860EF0F-25C0-413D-90F8-0A19437F0B46@stewe.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C860EF0F-25C0-413D-90F8-0A19437F0B46@stewe.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/afl15NJE_zzWI37cX4myMXGWmXQ>
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, 11 May 2017 23:09:54 -0000

On Thu, May 11, 2017 at 05:35:24PM +0000, Stephan Wenger wrote:
> (there were also other motivations, including the handy creation of
> a SPAM list from IETF archival material such as the proceedings).

I'm trying to stay out of the rest of this, but let me add two notes
at this point.

First, the proper term is "spam".  "SPAM" is a product of the Hormel
Corporation and has nothing to do with email.  "Spam" is not an acronym
and it is incorrect to present it in all-caps.

Second, there is no point whatsoever in worrying about whether spammers
will acquire addresses from such a list: they already have them, for
a value of "them" somewhere in 9 or 10 digits.  (And any newly-created
ones will be in their hands soon enough, via a variety of methods which
would take many pages to describe.)

---rsk


From nobody Thu May 11 17:20:47 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
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 8F357129C51 for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 17:20:45 -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=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TBrpUTkIRPXd for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 17:20:42 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23FF512EC5F for <ietf@ietf.org>; Thu, 11 May 2017 17:15:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 99451BE2D; Fri, 12 May 2017 01:15:46 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qf9iq2Hzb5Hw; Fri, 12 May 2017 01:15:45 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 0602DBDD0; Fri, 12 May 2017 01:15:45 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1494548145; bh=UPFfnZ1l1LfcMiSkQd/KFPrYGiyC+XCFiWq0C92QXbg=; h=Subject:To:References:From:Date:In-Reply-To:From; b=h8MQ3Vf2qlMU0/goGiZtxzfySYLU/HGmzPalz5iA4WQIiAN3KlTmSvP6DZFTzDX7K EUe767PLRfysOU4qi4ClH3VdRddL4GYAWxEcD9RWDaadusAnUybhq2W6QATjBVZ4Nd XxXdtT6z2e/5kVaQ108MaZBWq2d6Xwpf+/rhQb2o=
Subject: Re: Registration for remote participation
To: Stephan Wenger <stewe@stewe.org>, Andrew Sullivan <ajs@anvilwalrusden.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <29052.1494439452@obiwan.sandelman.ca> <F4BF8089-0E62-4B3D-AE97-1F5ACC4196BC@stewe.org> <20170511121458.v62px5wrbh47zf3j@mx4.yitter.info> <C860EF0F-25C0-413D-90F8-0A19437F0B46@stewe.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <1b639d16-f7de-0de0-78cd-8b8522af8bb0@cs.tcd.ie>
Date: Fri, 12 May 2017 01:15:44 +0100
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: <C860EF0F-25C0-413D-90F8-0A19437F0B46@stewe.org>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="TNgpCBj7VVdvQL3GG2wak580RGAlSoNHl"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/60cek3Q6JXJnjhWtPEbeNuXTdNI>
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, 12 May 2017 00:20:46 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--TNgpCBj7VVdvQL3GG2wak580RGAlSoNHl
Content-Type: multipart/mixed; boundary="2gOgcVsGwtM6AAuo5gobEk8KtFu8BWIdi";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Stephan Wenger <stewe@stewe.org>, Andrew Sullivan
 <ajs@anvilwalrusden.com>, "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <1b639d16-f7de-0de0-78cd-8b8522af8bb0@cs.tcd.ie>
Subject: Re: Registration for remote participation
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
 <29052.1494439452@obiwan.sandelman.ca>
 <F4BF8089-0E62-4B3D-AE97-1F5ACC4196BC@stewe.org>
 <20170511121458.v62px5wrbh47zf3j@mx4.yitter.info>
 <C860EF0F-25C0-413D-90F8-0A19437F0B46@stewe.org>
In-Reply-To: <C860EF0F-25C0-413D-90F8-0A19437F0B46@stewe.org>

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


FWIW, I personally consider almost all so-called IPR in the IETF's
space to be BS, so I am entirely happy that we ignore such issues to
the fullest possible extent. (While recognising that we do have to
pretend to respect some of that nonsense, sadly.)

I am also personally unhappy when we pander to the pretence that
the relevant output of entities like the USPTO are "inventions."
I base my attitude on my personal perception that a very high five
nines of supposedly relevant patent claims that I have read are
just crap. I do not ask that anyone else (dis)agrees with me.

So, yes, some IETF participants do need to pay attention to that
gibberish, and I'm ok with living with their being impaired in
that manner, but only to the extent that that is a necessary evil.

IOW, let's prefer usability to idiocy.

S.

On 11/05/17 18:35, Stephan Wenger wrote:
> Hi Andrew, please see inline.
>=20
>=20
>=20
>=20
> On 5/11/17, 05:14, "ietf on behalf of Andrew Sullivan" <ietf-bounces@ie=
tf.org on behalf of ajs@anvilwalrusden.com> wrote:
>=20
>> On Wed, May 10, 2017 at 07:47:20PM +0000, Stephan Wenger wrote:
>>>
>>> I=C3=A2=E2=82=AC=E2=84=A2m in favor of validating the address, for ex=
ample by sending some form of credential to it; without the credential, o=
nly listening/reading access is granted.  Doesn=C3=A2=E2=82=AC=E2=84=A2t =
have to be bullet-proof, but using example@example.com shouldn=C3=A2=E2=82=
=AC=E2=84=A2t work.  This is obviously in order to obtain one semi-tracea=
ble record of the participant.
>>>>
>>
>> We don't do that for in-person participants, because we no longer even=

>> collect the email address on the blue sheets.  (We do it for meeting
>> registration, of course, but we don't have a way to pair that with
>> participation in any given part of the meeting, so the IPR issue is
>> harder to argue by analogy here.)
>=20
> The question is not whether we collect email addresses.  The question i=
s whether we collect the identification of the individual and its employe=
r, bother with reasonable certainty.  IIRC, one reason for the change fro=
m email address to company name was made because, today, many people use =
non-employer email for IETF work even if they do the work mostly on behal=
f of their employer and as part of their job, and tracking down the parti=
cipant=C3=A2=E2=82=AC=E2=84=A2s employer from the email address for thing=
s like Noncom eligibility and also IPR related issues didn=C3=A2=E2=82=AC=
=E2=84=A2t work anymore (if it ever did).  (there were also other motivat=
ions, including the handy creation of a SPAM list from IETF archival mate=
rial such as the proceedings).
>=20
> For an in-person meeting, we (or a court) have many ways to identify a =
person who influences the decision process.  For an external person, espe=
cially when there is no video, we are more limited.  A non-verified email=
 address is certainly easier to fake than the recollection of a roomful o=
f people during a physical meeting.
>=20
>>
>>> And 5) click-through of the Note Well (unless that=C3=A2=E2=82=AC=E2=84=
=A2s done in some other phase of the remote participation, like when sign=
ing-in to meetecho).  Again for--I hope obvious--IPR related reasons.
>>>
>>
>> We _certainly_ don't do that for in-person meetings.  We put the Note
>> Well up and assume that anyone who is in the room and who makes a
>> Contribution in any way is aware of it.  Joining the meeting virtually=

>> has the same property, no?
>=20
> Actually, No.  In an in-person meeting, the hurdle of missing a note we=
ll is pretty high.  When you are at a physical meeting and get bombarded =
with a Note Well not only during registration time, but also daily severa=
l times at the begin of WG sessions, you and your lawyer would have a har=
d time to argue that you were not aware of it (and therefore perhaps free=
 of certain obligations you otherwise have per policy).  OTOH, assuming n=
o click-through or similar, a good lawyer could conceivably make the case=
 that his client was not aware of the Note Well and associated policy whe=
n influencing an IETF decision process of a certain document, especially =
if that person is not an IETF regular and dials in only for one WG sessio=
n (and perhaps a bit late to that).  Then, the good lawyer could conceiva=
bly argue that certain obligations (such as the obligation to disclose pa=
tents) were not known to that client of his.  And finally, the lawyer cou=
ld argue that, therefore, the obligations do not apply.  (Note that I did=
n=C3=A2=E2=82=AC=E2=84=A2t include the word =C3=A2=E2=82=AC=C5=93successf=
ul=C3=A2=E2=82=AC=C2=9D in the last sentence.)
>=20
> There has been one fairly prominent case where a company choose to send=
 undercover participants to standards meetings, in order to (so the court=
 found IIRC) circumvent obligations by the standards committee.  We shoul=
d not facilitate such behavior.  That case and ours are not directly comp=
arable, but IMO not dissimilar in their nature.
>=20
> Stephan
>>
>> A
>>
>> --=20
>> Andrew Sullivan
>> ajs@anvilwalrusden.com
>>


--2gOgcVsGwtM6AAuo5gobEk8KtFu8BWIdi--

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

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

iQEcBAEBCAAGBQJZFP6wAAoJEC88hzaAX42iET4H/iUMK1i4amaFpitZ9aKj8crx
ouhrwHnkyfFHwcWwldio7nkA3TFjdvQEX0qYqb0oZMli5px7wVw1z9iZHErbjXc7
StiKEVIiDj9dAHBUXz+u7OrMznlwYl/eqCXI/8Us/1wCDulBcOs3EQCaF/7ypeyW
j9UN5tGPNl/IT9c+sQaurrj6XH6Iap/XQHOtcNaGP2CFzJwmJKY+xcvdbDj4lecE
6m1m4+4DAONPnvTApJA7umqpYVmSA90SY1/0W+hGOSqxLnWGpotVTgBw6h0htM/M
1hxG/vGNnhnveZQ6htZPPuBj/Ib10RZy1uQvalL8S3wYH+aP5Io21xeFEdD/loc=
=6Ywu
-----END PGP SIGNATURE-----

--TNgpCBj7VVdvQL3GG2wak580RGAlSoNHl--


From nobody Thu May 11 21:58:53 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 A3D12128CB9 for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 21:58:52 -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, 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 kM0D7IZd_cTV for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 21:58:50 -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 302DA129434 for <ietf@ietf.org>; Thu, 11 May 2017 21:53:18 -0700 (PDT)
Received: from pps.filterd (m0098394.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v4C4nRvk049043 for <ietf@ietf.org>; Fri, 12 May 2017 00:53:13 -0400
Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) by mx0a-001b2d01.pphosted.com with ESMTP id 2acpt0h7bj-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 12 May 2017 00:53:12 -0400
Received: from localhost by e31.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 11 May 2017 22:53:12 -0600
Received: from b03cxnp08028.gho.boulder.ibm.com (9.17.130.20) by e31.co.us.ibm.com (192.168.1.131) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 11 May 2017 22:53:09 -0600
Received: from b03ledav004.gho.boulder.ibm.com (b03ledav004.gho.boulder.ibm.com [9.17.130.235]) by b03cxnp08028.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v4C4r9wZ10223948 for <ietf@ietf.org>; Thu, 11 May 2017 21:53:09 -0700
Received: from b03ledav004.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 308CB78038 for <ietf@ietf.org>; Thu, 11 May 2017 22:53:09 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b03ledav004.gho.boulder.ibm.com (Postfix) with ESMTPS id 087467803F for <ietf@ietf.org>; Thu, 11 May 2017 22:53:08 -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 v4C4r7O7032676 for <ietf@ietf.org>; Fri, 12 May 2017 00:53:07 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v4C4r6Zj032659 for ietf@ietf.org; Fri, 12 May 2017 00:53:06 -0400
From: narten@us.ibm.com
Date: Fri, 12 May 2017 00:53:06 -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: 17051204-8235-0000-0000-00000B7AA458
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00007049; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000211; SDB=6.00859344; UDB=6.00425959; IPR=6.00638923;  BA=6.00005345; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00015421; XFM=3.00000015; UTC=2017-05-12 04:53:10
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17051204-8236-0000-0000-00003BC4D669
Message-Id: <201705120453.v4C4r6Zj032659@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-05-12_01:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=99 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1705120094
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0AcnVFhECOKlhY8OBnAvx6NVZpc>
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, 12 May 2017 04:58:53 -0000

Total of 109 messages in the last 7 days.
 
script run at: Fri May 12 00:53:06 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  5.50% |    6 |  7.13% |   103592 | robert@raszuk.net
  3.67% |    4 |  7.70% |   111906 | ietf@jiaziyi.com
  2.75% |    3 |  6.79% |    98680 | chris.dearlove@baesystems.com
  4.59% |    5 |  4.52% |    65668 | job@ntt.net
  2.75% |    3 |  4.62% |    67205 | nishida@sfc.wide.ad.jp
  2.75% |    3 |  3.59% |    52164 | ted.ietf@gmail.com
  2.75% |    3 |  3.47% |    50396 | dromasca@gmail.com
  1.83% |    2 |  4.22% |    61280 | weigengyu@bupt.edu.cn
  1.83% |    2 |  4.00% |    58132 | xuxiaohu@huawei.com
  2.75% |    3 |  2.41% |    35065 | stephen.farrell@cs.tcd.ie
  2.75% |    3 |  2.31% |    33555 | bob.hinden@gmail.com
  2.75% |    3 |  2.01% |    29248 | ynir.ietf@gmail.com
  2.75% |    3 |  1.75% |    25489 | mcr+ietf@sandelman.ca
  2.75% |    3 |  1.74% |    25360 | chair@ietf.org
  2.75% |    3 |  1.63% |    23752 | john-ietf@jck.com
  2.75% |    3 |  1.62% |    23574 | stewart.bryant@gmail.com
  1.83% |    2 |  2.51% |    36462 | acmorton@att.com
  1.83% |    2 |  1.72% |    24961 | stewe@stewe.org
  1.83% |    2 |  1.40% |    20281 | cabo@tzi.org
  1.83% |    2 |  1.37% |    19893 | warren@kumari.net
  1.83% |    2 |  1.35% |    19617 | enkechen@cisco.com
  1.83% |    2 |  1.27% |    18409 | jclarke@cisco.com
  1.83% |    2 |  1.23% |    17899 | ietf@kuehlewind.net
  1.83% |    2 |  1.20% |    17471 | tore@fud.no
  0.92% |    1 |  2.02% |    29347 | spencerdawkins.ietf@gmail.com
  1.83% |    2 |  1.03% |    14996 | housley@vigilsec.com
  1.83% |    2 |  0.88% |    12739 | johnl@taugh.com
  0.92% |    1 |  1.50% |    21795 | shitanshu_shah@hotmail.com
  0.92% |    1 |  1.43% |    20727 | robmgl@cisco.com
  0.92% |    1 |  1.21% |    17559 | farmer@umn.edu
  0.92% |    1 |  1.08% |    15719 | julian.reschke@gmx.de
  0.92% |    1 |  1.03% |    14905 | alissa@cooperw.in
  0.92% |    1 |  0.88% |    12726 | italo.busi@huawei.com
  0.92% |    1 |  0.86% |    12488 | alexandre.mendes-ex@solvay.com
  0.92% |    1 |  0.80% |    11605 | aretana@cisco.com
  0.92% |    1 |  0.79% |    11413 | ocl@gih.com
  0.92% |    1 |  0.78% |    11305 | mersue@gmail.com
  0.92% |    1 |  0.77% |    11159 | narten@us.ibm.com
  0.92% |    1 |  0.76% |    11021 | jheitz@cisco.com
  0.92% |    1 |  0.70% |    10168 | townsley@cisco.com
  0.92% |    1 |  0.68% |     9948 | lear@cisco.com
  0.92% |    1 |  0.68% |     9923 | presnick@qti.qualcomm.com
  0.92% |    1 |  0.66% |     9529 | martin.thomson@gmail.com
  0.92% |    1 |  0.63% |     9173 | lberger@labn.net
  0.92% |    1 |  0.60% |     8653 | sprevidi@cisco.com
  0.92% |    1 |  0.58% |     8424 | jefftant.ietf@gmail.com
  0.92% |    1 |  0.57% |     8349 | amy.yemin@huawei.com
  0.92% |    1 |  0.57% |     8322 | roni.even@huawei.com
  0.92% |    1 |  0.56% |     8094 | ajs@anvilwalrusden.com
  0.92% |    1 |  0.55% |     8014 | daniel.migault@ericsson.com
  0.92% |    1 |  0.54% |     7919 | jari.arkko@piuha.net
  0.92% |    1 |  0.52% |     7614 | dhc@dcrocker.net
  0.92% |    1 |  0.51% |     7431 | touch@isi.edu
  0.92% |    1 |  0.50% |     7229 | swmike@swm.pp.se
  0.92% |    1 |  0.49% |     7093 | randy@psg.com
  0.92% |    1 |  0.47% |     6806 | mnot@mnot.net
  0.92% |    1 |  0.47% |     6801 | adam@nostrum.com
  0.92% |    1 |  0.46% |     6699 | rsk@gsp.org
  0.92% |    1 |  0.40% |     5818 | zhencao.ietf@gmail.com
  0.92% |    1 |  0.40% |     5816 | worley@ariadne.com
  0.92% |    1 |  0.39% |     5677 | vijay.gurbani@nokia.com
  0.92% |    1 |  0.37% |     5417 | ron.even.tlv@gmail.com
  0.92% |    1 |  0.35% |     5058 | j.schoenwaelder@jacobs-university.de
--------+------+--------+----------+------------------------
100.00% |  109 |100.00% |  1453538 | Total


From nobody Thu May 11 22:12:18 2017
Return-Path: <chengweiqiang@chinamobile.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 42963129C39; Thu, 11 May 2017 22:12:09 -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, RP_MATCHES_RCVD=-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 ONsnIxQXbCqZ; Thu, 11 May 2017 22:12:06 -0700 (PDT)
Received: from cmccmta2.chinamobile.com (cmccmta2.chinamobile.com [221.176.66.80]) by ietfa.amsl.com (Postfix) with ESMTP id 80B5B129C37; Thu, 11 May 2017 22:06:59 -0700 (PDT)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.3]) by rmmx-syy-dmz-app07-12007 (RichMail) with SMTP id 2ee7591542ece97-328ec; Fri, 12 May 2017 13:06:53 +0800 (CST)
X-RM-TRANSID: 2ee7591542ece97-328ec
X-RM-SPAM-FLAG: 00000000
Received: from cmcc (unknown[10.2.51.63]) by rmsmtp-syy-appsvr02-12002 (RichMail) with SMTP id 2ee2591542ecd15-51d50; Fri, 12 May 2017 13:06:52 +0800 (CST)
X-RM-TRANSID: 2ee2591542ecd15-51d50
From: "Weiqiang Cheng" <chengweiqiang@chinamobile.com>
To: "'Italo Busi'" <Italo.Busi@huawei.com>, <ietf@ietf.org>
Cc: <mpls@ietf.org>, <draft-ietf-mpls-tp-shared-ring-protection@ietf.org>
References: <149339519935.2881.8322243003635696392.idtracker@ietfa.amsl.com> <91E3A1BD737FDF4FA14118387FF6766B157346F2@lhreml504-mbs>
In-Reply-To: <91E3A1BD737FDF4FA14118387FF6766B157346F2@lhreml504-mbs>
Subject: Re: Last Call: <draft-ietf-mpls-tp-shared-ring-protection-05.txt> (Shared-Ring protection (MSRP) mechanism for ring topology) to Proposed Standard
Date: Fri, 12 May 2017 13:06:58 +0800
Message-ID: <003801d2cadd$955a6c40$c00f44c0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHSwFHT6RfRe34k+0+8cXprdYx99aHvEoSQgAEmtiA=
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/p3h-z0lCOBssbqaMklKioDCKrmM>
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, 12 May 2017 05:12:09 -0000

Hi Italo,
Thank you very much for your detailed review and valuable comments.
We authors will make some modifications based on your comments.

B.R.
Weiqiang Cheng

-----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6-----
=E5=8F=91=E4=BB=B6=E4=BA=BA: Italo Busi [mailto:Italo.Busi@huawei.com]=20
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2017=E5=B9=B45=E6=9C=8811=E6=97=A5 =
22:06
=E6=94=B6=E4=BB=B6=E4=BA=BA: ietf@ietf.org
=E6=8A=84=E9=80=81: mpls@ietf.org; =
draft-ietf-mpls-tp-shared-ring-protection@ietf.org
=E4=B8=BB=E9=A2=98: RE: Last Call: =
<draft-ietf-mpls-tp-shared-ring-protection-05.txt> (Shared-Ring =
protection (MSRP) mechanism for ring topology) to Proposed Standard

I think the draft is ready to be published.

I have recently discussed with some authors of the draft some questions =
for clarification and it might be worthwhile considering minor text =
changes proposed below to further improve text clarity.

1) Section 4.3.1.2 and 4.3.2.2

The text describing egress node failures imply that, also in case of =
wrapping and short-wrapping, the ingress node, when notified (by RPS) =
about egress node failure, will not send traffic to either the working =
or the protection tunnel (like it does with steering protection). It =
might be worthwhile adding some explicit text

OLD TEXT (Section 4.3.1.2)
   In one special case where node D fails, all the ring tunnels with
   node D as egress will become unusable. However, before the failure
   location information is propagated to all the ring nodes, the
   wrapping protection mechanism may cause temporary traffic loop:

NEW TEXT (Section 4.3.1.2)
   In one special case where node D fails, all the ring tunnels with
   node D as egress will become unusable. The ingress node will update =
its ring map according to received RPS messages and determine that the =
egress node is not reachable thus it will not send traffic to either the =
working or the protection tunnel. However, before the failure
   location information is propagated to all the ring nodes, the
   wrapping protection mechanism may cause temporary traffic loop:

OLD TEXT (Section 4.3.2.2)
   <...> When node D
   fails, traffic of LSP1 cannot be protected by any ring tunnels which
   use node D as the egress node.  However, before the failure location
   information is propagated to all the ring nodes using the RPS
   protocol, node C switches all the traffic on the working ring tunnel=20
   <...>

NEW TEXT (Section 4.3.2.2)
   <...> When node D
   fails, traffic of LSP1 cannot be protected by any ring tunnels which
   use node D as the egress node. The ingress node will update its ring =
map according to received RPS messages and determine that the egress =
node is not reachable thus it will not send traffic to either the =
working or the protection tunnel. However, before the failure location
   information is propagated to all the ring nodes using the RPS
   protocol, node C switches all the traffic on the working ring tunnel=20
   <...>

2)  Section 4.3.2

With short-wrapping the two traffic directions of protected LSPs are no =
longer co-routed under protection switching conditions. This should be =
mentioned.

OLD TEXT
   With short wrapping protection, data traffic switching is executed
   only at the node upstream to the failure, and data traffic leaves the
   ring in the protection ring tunnel at the egress node.  This scheme
   can reduce the additional latency and bandwidth consumption when
   traffic is switched to the protection path.

NEW TEXT
   With short wrapping protection, data traffic switching is executed
   only at the node upstream to the failure, and data traffic leaves the
   ring in the protection ring tunnel at the egress node.  This scheme
   can reduce the additional latency and bandwidth consumption when
   traffic is switched to the protection path. However the two =
directions of a protected bidirectional LSP are no longer co-routed =
under protection switching conditions.

3) Section 4.3.2

The difference between wrapping and short-wrapping is in the way =
protection tunnel is configured.

OLD TEXT
   In the traditional wrapping solution, in normal state the protection
   ring tunnel is a closed ring, while in the short wrapping solution,
   the protection ring tunnel is ended at the egress node, which is
   similar to the working ring tunnel.

NEW TEXT
   In the traditional wrapping solution, the protection
   ring tunnel is configured as a closed ring, while in the short =
wrapping solution,
   the protection ring tunnel is configured as ended at the egress node, =
which is
   similar to the working ring tunnel.

Thanks, Italo

-----Original Message-----
From: The IESG [mailto:iesg-secretary@ietf.org]=20
Sent: sabato 29 aprile 2017 00:00
To: IETF-Announce
Cc: mpls@ietf.org; db3546@att.com; mpls-chairs@ietf.org; =
draft-ietf-mpls-tp-shared-ring-protection@ietf.org; Eric Gray; =
Eric.Gray@Ericsson.com
Subject: Last Call: <draft-ietf-mpls-tp-shared-ring-protection-05.txt> =
(Shared-Ring protection (MSRP) mechanism for ring topology) to Proposed =
Standard


The IESG has received a request from the Multiprotocol Label Switching =
WG
(mpls) to consider the following document:
- 'Shared-Ring protection (MSRP) mechanism for ring topology'
  <draft-ietf-mpls-tp-shared-ring-protection-05.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-05-12. Exceptionally, comments may =
be sent to iesg@ietf.org instead. In either case, please retain the =
beginning of the Subject line to allow automated sorting.

Abstract


   This document describes requirements, architecture and solutions for
   MPLS-TP Shared Ring Protection (MSRP) in a ring topology for point-
   to-point (P2P) services.  The MSRP mechanism is described to meet the
   ring protection requirements as described in RFC 5654.  This document
   defines the Ring Protection Switch (RPS) Protocol that is used to
   coordinate the protection behavior of the nodes on MPLS ring.





The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-mpls-tp-shared-ring-protectio=
n/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-mpls-tp-shared-ring-protectio=
n/ballot/

The following IPR Declarations may be related to this I-D:

   https://datatracker.ietf.org/ipr/2680/
   https://datatracker.ietf.org/ipr/2681/
   https://datatracker.ietf.org/ipr/2682/
   https://datatracker.ietf.org/ipr/2683/










From nobody Thu May 11 23:23:35 2017
Return-Path: <cts@etri.re.kr>
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 EAC9D1286B1; Thu, 11 May 2017 23:23: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, 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 iXwVn8cW3Amf; Thu, 11 May 2017 23:23:29 -0700 (PDT)
Received: from smtpeg.etri.re.kr (smtpeg1.etri.re.kr [129.254.27.141]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F71612EA7F; Thu, 11 May 2017 23:19:00 -0700 (PDT)
Received: from SMTP1.etri.info (129.254.28.71) by SMTPEG1.etri.info (129.254.27.141) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 12 May 2017 15:18:58 +0900
Received: from SMTP5.etri.info ([169.254.5.137]) by SMTP1.etri.info ([10.2.6.30]) with mapi id 14.03.0319.002; Fri, 12 May 2017 15:18:57 +0900
From: =?ks_c_5601-1987?B?waTFwr3E?= <cts@etri.re.kr>
To: "ietf@ietf.org" <ietf@ietf.org>
CC: "mpls@ietf.org" <mpls@ietf.org>, "draft-ietf-mpls-tp-shared-ring-protection@ietf.org" <draft-ietf-mpls-tp-shared-ring-protection@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-shared-ring-protection-05.txt> (Shared-Ring protection (MSRP) mechanism for ring topology) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-tp-shared-ring-protection-05.txt> (Shared-Ring protection (MSRP) mechanism for ring topology) to Proposed Standard
Thread-Index: AQHSwDiELaN/BQQqsk29ttW8LV5UxaHwOl/w
Date: Fri, 12 May 2017 06:18:55 +0000
Message-ID: <AD98114A73E97041A2EDDCC3F3D10B0373E84540@SMTP5.etri.info>
References: <149339519935.2881.8322243003635696392.idtracker@ietfa.amsl.com>
In-Reply-To: <149339519935.2881.8322243003635696392.idtracker@ietfa.amsl.com>
Accept-Language: en-US, ko-KR
Content-Language: ko-KR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.254.73.86]
Content-Type: text/plain; charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/te8rRniw3VWttRbhnOMkCdG8MAU>
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, 12 May 2017 06:23:33 -0000

RGVhciBhdXRob3JzLA0KDQpJIGhhdmUgdHdvIGNvbW1lbnRzIG9uIHRoaXMgZHJhZnQuDQoNCjEp
IFNlY3Rpb24gNC40LjEgKGxhc3QgdHdvIHBhcmFncmFwaHMgYWJvdmUgRmlndXJlIDExKQ0KDQpG
b2xsb3dpbmcgdHdvIHNlbnRlbmNlcyBhcmUgZHVwbGljYXRlZCBpbiB0aGUgbGFzdCB0d28gcGFy
YWdyYXBocyBhYm92ZSBGaWd1cmUgMTEuDQoNCkZpZ3VyZSAxMSBzaG93cyB0aGUgdG9wb2xvZ3kg
b2Ygc2luZ2xlLW5vZGUgaW50ZXJjb25uZWN0ZWQNCnJpbmdzLiBOb2RlIEMgaXMgdGhlIGludGVy
Y29ubmVjdGlvbiBub2RlIGJldHdlZW4gUmluZzEgYW5kDQpSaW5nMi4NCg0KUHJvcG9zZWQgY2hh
bmdlOiBkZWxldGUgdGhlIGxhc3QgcGFyYWdyYXBoLg0KDQoNCjIpIFNlY3Rpb24gNS4xLjQuMiAo
M3JkIHBhcmFncmFwaCBmcm9tIHRoZSBib3R0b20pDQoNClRoZSBsYXN0IHR3byBidWxsZXQgaXRl
bXMgY29ycmVzcG9uZCB0byBjb25kaXRpb25zIHdoaWNoIHRyaWdnZXIgc3RhdGUgdHJhbnNpdGlv
biBmcm9tIHRoZSBTd2l0Y2hpbmcgc3RhdGUgdG8gdGhlIElkbGUgc3RhdGUuIEhvd2V2ZXIsIGN1
cnJlbnQgdGV4dCBhYm92ZSB0aG9zZSBidWxsZXQgaXRlbXMgaXMgZGVzY3JpYmluZyBhZHZlcnNl
bHkuDQoNClByb3Bvc2VkIGNoYW5nZTogDQoNCk9MRCBURVhUDQpJbiBvbmUgb2YgdGhlIGZvbGxv
d2luZyBjb25kaXRpb25zLCB0cmFuc2l0aW9uIGZyb20gdGhlIElkbGUgc3RhdGUgdG8NCnRoZSBT
d2l0Y2hpbmcgc3RhdGUgTVVTVCBiZSB0cmlnZ2VyZWQ6DQoNCk5FVyBURVhUDQpJbiBvbmUgb2Yg
dGhlIGZvbGxvd2luZyBjb25kaXRpb25zLCB0cmFuc2l0aW9uIGZyb20gdGhlIFN3aXRjaGluZyBz
dGF0ZSB0bw0KdGhlIElkbGUgc3RhdGUgTVVTVCBiZSB0cmlnZ2VyZWQ6DQoNCkJlc3QgcmVnYXJk
cywNClRhZXNpaw0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBtcGxzIFtt
YWlsdG86bXBscy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgVGhlIElFU0cNClNlbnQ6
IFNhdHVyZGF5LCBBcHJpbCAyOSwgMjAxNyAxOjAwIEFNDQpUbzogSUVURi1Bbm5vdW5jZQ0KQ2M6
IG1wbHNAaWV0Zi5vcmc7IGRyYWZ0LWlldGYtbXBscy10cC1zaGFyZWQtcmluZy1wcm90ZWN0aW9u
QGlldGYub3JnOyBtcGxzLWNoYWlyc0BpZXRmLm9yZw0KU3ViamVjdDogW21wbHNdIExhc3QgQ2Fs
bDogPGRyYWZ0LWlldGYtbXBscy10cC1zaGFyZWQtcmluZy1wcm90ZWN0aW9uLTA1LnR4dD4gKFNo
YXJlZC1SaW5nIHByb3RlY3Rpb24gKE1TUlApIG1lY2hhbmlzbSBmb3IgcmluZyB0b3BvbG9neSkg
dG8gUHJvcG9zZWQgU3RhbmRhcmQNCg0KDQpUaGUgSUVTRyBoYXMgcmVjZWl2ZWQgYSByZXF1ZXN0
IGZyb20gdGhlIE11bHRpcHJvdG9jb2wgTGFiZWwgU3dpdGNoaW5nIFdHDQoobXBscykgdG8gY29u
c2lkZXIgdGhlIGZvbGxvd2luZyBkb2N1bWVudDoNCi0gJ1NoYXJlZC1SaW5nIHByb3RlY3Rpb24g
KE1TUlApIG1lY2hhbmlzbSBmb3IgcmluZyB0b3BvbG9neScNCiAgPGRyYWZ0LWlldGYtbXBscy10
cC1zaGFyZWQtcmluZy1wcm90ZWN0aW9uLTA1LnR4dD4gYXMgUHJvcG9zZWQgU3RhbmRhcmQNCg0K
VGhlIElFU0cgcGxhbnMgdG8gbWFrZSBhIGRlY2lzaW9uIGluIHRoZSBuZXh0IGZldyB3ZWVrcywg
YW5kIHNvbGljaXRzIGZpbmFsIGNvbW1lbnRzIG9uIHRoaXMgYWN0aW9uLiBQbGVhc2Ugc2VuZCBz
dWJzdGFudGl2ZSBjb21tZW50cyB0byB0aGUgaWV0ZkBpZXRmLm9yZyBtYWlsaW5nIGxpc3RzIGJ5
IDIwMTctMDUtMTIuIEV4Y2VwdGlvbmFsbHksIGNvbW1lbnRzIG1heSBiZSBzZW50IHRvIGllc2dA
aWV0Zi5vcmcgaW5zdGVhZC4gSW4gZWl0aGVyIGNhc2UsIHBsZWFzZSByZXRhaW4gdGhlIGJlZ2lu
bmluZyBvZiB0aGUgU3ViamVjdCBsaW5lIHRvIGFsbG93IGF1dG9tYXRlZCBzb3J0aW5nLg0KDQpB
YnN0cmFjdA0KDQoNCiAgIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIHJlcXVpcmVtZW50cywgYXJj
aGl0ZWN0dXJlIGFuZCBzb2x1dGlvbnMgZm9yDQogICBNUExTLVRQIFNoYXJlZCBSaW5nIFByb3Rl
Y3Rpb24gKE1TUlApIGluIGEgcmluZyB0b3BvbG9neSBmb3IgcG9pbnQtDQogICB0by1wb2ludCAo
UDJQKSBzZXJ2aWNlcy4gIFRoZSBNU1JQIG1lY2hhbmlzbSBpcyBkZXNjcmliZWQgdG8gbWVldCB0
aGUNCiAgIHJpbmcgcHJvdGVjdGlvbiByZXF1aXJlbWVudHMgYXMgZGVzY3JpYmVkIGluIFJGQyA1
NjU0LiAgVGhpcyBkb2N1bWVudA0KICAgZGVmaW5lcyB0aGUgUmluZyBQcm90ZWN0aW9uIFN3aXRj
aCAoUlBTKSBQcm90b2NvbCB0aGF0IGlzIHVzZWQgdG8NCiAgIGNvb3JkaW5hdGUgdGhlIHByb3Rl
Y3Rpb24gYmVoYXZpb3Igb2YgdGhlIG5vZGVzIG9uIE1QTFMgcmluZy4NCg0KDQoNCg0KDQpUaGUg
ZmlsZSBjYW4gYmUgb2J0YWluZWQgdmlhDQpodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2Rv
Yy9kcmFmdC1pZXRmLW1wbHMtdHAtc2hhcmVkLXJpbmctcHJvdGVjdGlvbi8NCg0KSUVTRyBkaXNj
dXNzaW9uIGNhbiBiZSB0cmFja2VkIHZpYQ0KaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9k
b2MvZHJhZnQtaWV0Zi1tcGxzLXRwLXNoYXJlZC1yaW5nLXByb3RlY3Rpb24vYmFsbG90Lw0KDQpU
aGUgZm9sbG93aW5nIElQUiBEZWNsYXJhdGlvbnMgbWF5IGJlIHJlbGF0ZWQgdG8gdGhpcyBJLUQ6
DQoNCiAgIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvaXByLzI2ODAvDQogICBodHRwczov
L2RhdGF0cmFja2VyLmlldGYub3JnL2lwci8yNjgxLw0KICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5p
ZXRmLm9yZy9pcHIvMjY4Mi8NCiAgIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvaXByLzI2
ODMvDQoNCg0KDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCm1wbHMgbWFpbGluZyBsaXN0DQptcGxzQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL21wbHMNCg==


From nobody Thu May 11 23:56: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 E4207129C6F for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 23:56:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.802
X-Spam-Level: 
X-Spam-Status: No, score=-11.802 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 hPv275NCXhQl for <ietf@ietfa.amsl.com>; Thu, 11 May 2017 23:56:51 -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 CBCAC12E043 for <ietf@ietf.org>; Thu, 11 May 2017 23:52:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2792; q=dns/txt; s=iport; t=1494571931; x=1495781531; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=eViKl1gQ20CMN1+TrgYwHYOjecqodWFNCngGUKeqA2Y=; b=JTR7tTcqRmVsRjKjaH2cGJc9Q/QeAH4SlVedQdMdJVAHbW0WGKiyphZJ YtdfLt0FaMVuSc6Ud+AJXnJ8uLzssy6W0UCHnNxpw1bvlp6eWIr+2X39U u3pMzcB/6ox5mMggChh6KANLpfGnD6i13l4qLa+hv7Y0r7rl/T5+rrlfa w=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DjAAB1WhVZ/xbLJq1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBhDeBDINrihhzkGmVdIIPBx2GAAKFUxgBAgEBAQEBAQFrKIUWAQU?= =?us-ascii?q?jZgsYFRUCAlcGAQwGAgEBih+vAoImgUeJMAEBAQEBAQQBAQEBAQEBEg+IaIJwh?= =?us-ascii?q?DQSAVuCU4JgAQSQIo1ohA2CFHuLf4JZiCmGaZRDHzh/Cy8gCBkVHIchPjaGMA0?= =?us-ascii?q?XB4IQAQEB?=
X-IronPort-AV: E=Sophos;i="5.38,328,1491264000";  d="asc'?scan'208";a="654644552"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 May 2017 06:52:09 +0000
Received: from [10.61.230.114] ([10.61.230.114]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v4C6q96s027003; Fri, 12 May 2017 06:52:09 GMT
Subject: Re: Registration for remote participation
To: Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion <ietf@ietf.org>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <29052.1494439452@obiwan.sandelman.ca>
From: Eliot Lear <lear@cisco.com>
Message-ID: <20b21b8a-a803-fa36-1ce7-b5c7f4c67503@cisco.com>
Date: Fri, 12 May 2017 08:52:08 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <29052.1494439452@obiwan.sandelman.ca>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="03fmXgNOBmUiCJKsDSdGjurvfhtDLs8HN"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OGf65BT4zDVslGHvurXX2C1BMjQ>
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, 12 May 2017 06:56:54 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--03fmXgNOBmUiCJKsDSdGjurvfhtDLs8HN
Content-Type: multipart/mixed; boundary="ethNiSrplSxSiS0MfjuMuQBLbrOGOS7cx";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>,
 IETF Discussion <ietf@ietf.org>
Message-ID: <20b21b8a-a803-fa36-1ce7-b5c7f4c67503@cisco.com>
Subject: Re: Registration for remote participation
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
 <29052.1494439452@obiwan.sandelman.ca>
In-Reply-To: <29052.1494439452@obiwan.sandelman.ca>

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



On 5/10/17 8:04 PM, Michael Richardson wrote:
> IETF Chair <chair@ietf.org> wrote:
>     > Title
>     > First / Given Name*
>     > Last / Family Name*
>     > Company / Organization
>     > ISO 3166 Country of Residence*
>     > Email*
>     > Gender
>     > Have you attended an IETF meeting in person before?
>     > Have you attended an IETF meeting remotely before?
>
>     > Upon registering, participants would be issued a registration ID,=
 just
>     > as they are today.
>
> Are we validating the email address in some way?
> If we are not, I don't see the point of the *-required in any of those =
places.

Regardless of motivation here, if the tools team were to use our
ietf.org logins for registration one of the benefits of that would be
that many fields could be filled in for us, albeit editable (some of us
need that for tee shirt size, regrettably),  both for in person and
remote participation.=20

There is a downside: the secretariat would have to secure that
information.  Personally I think we should offer that as an option as an
exercise to demonstrate how privacy can be done properly, so that we are
eating our own dog food.  The minimum, though, would be a validated IETF
account.  I don't think that's a high bar.

Eliot



--ethNiSrplSxSiS0MfjuMuQBLbrOGOS7cx--

--03fmXgNOBmUiCJKsDSdGjurvfhtDLs8HN
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

iQEcBAEBCAAGBQJZFVuZAAoJEIe2a0bZ0nozij0H/RV+sE/sgk45ULI1D3SdRiAg
zAlEA3hGIFqDlsj6tw0McMJocZu7O0qim/rV6bIswsSFOiYL9LrYgK00FW4RHvP1
Ymb8vEsmJNalPlO9C/DZsByr8FyLTQS/L44KeILIy6jqRGDYx4yHrdGPa6BZsseE
ss0SxNRNiszadVtz9AL6mXvEjbhxMI7taP8nYeUt0KLjzxq2UKexJjoQ0kIUwQLi
ILIYxSWU5x3g+K4cNZNPsxOK9J3v4gAmzFlRXIPW159+E0eeWIrDJaQMPw/mi4jU
xstXv5O6KoqKVCSbgvrv/WP/cN+xmYP2hEJlWpLVLEJDSOrflrjSvCEf7x+lXeU=
=qQ+1
-----END PGP SIGNATURE-----

--03fmXgNOBmUiCJKsDSdGjurvfhtDLs8HN--


From nobody Fri May 12 01:49:59 2017
Return-Path: <huubatwork@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 628061293F5; Fri, 12 May 2017 01:49:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qSxgoPPxspoC; Fri, 12 May 2017 01:49:55 -0700 (PDT)
Received: from mail-wr0-x241.google.com (mail-wr0-x241.google.com [IPv6:2a00:1450:400c:c0c::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 67CFE1294EE; Fri, 12 May 2017 01:44:59 -0700 (PDT)
Received: by mail-wr0-x241.google.com with SMTP id g12so6667248wrg.2; Fri, 12 May 2017 01:44:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=reply-to:subject:references:to:cc:from:message-id :disposition-notification-to:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=zA4+xFcN3Y5xzlgwWHtiX4AW2ohHaxXilAE9v98kyzo=; b=AgILdqA04wj7WFkrcGmk9KlwGwgvqIROySWVh3fL2S2HtaCOJSdx5h7KM+AV23DVL5 4LlKo76lFaQ09WsbkjztDIzVsdWYuNwRWSqzRFrwrQVUUtdoMqT6RQyaD1c4j2XK3Opb ZACqvBLuS8uqn8okLH5OANlQMCscKh7+ifJHma0ySovik8SwqlUYtHoUCj6LHkkJgOz3 Idg4F8VgkXDOHxzJh4UBhWxm8ae+G/oCmCm0BHuuNZT3T+aBJZtwC8djdJhGXAXFE7rx 8wg9rsfXmcwXd57kiWYTN6nnC4Baff4Lta5xIRSw3SMsJezipDJ6pD/jcJptzFCn1k9H w78Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:reply-to:subject:references:to:cc:from :message-id:disposition-notification-to:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=zA4+xFcN3Y5xzlgwWHtiX4AW2ohHaxXilAE9v98kyzo=; b=egHn0t/FmE14WEUo31F9Ax1g7jH1YYSdKq7fMUxUQwJ2JhSIKj3/TcFx+M1kOkFi/7 jMFOZoQn4wzXAB0NmU49Z/z2LJj9R5MgxDS3nO6M+clL/YL+KIbJ3IXkpsuQ0CNGdn8a zkUo0MkN1UtIJqDe8+cmsUPP77dNps6nwXgMic6gTMorqvBmSnRf06UUqeS/i/Zn7vG/ Nq6C5YADXlJqhjWoIlrMK6DdOXq29ug9mS7m5EZ6lc+hPRWc6ZZqqeXbnE48tDlGUBqB FvAfO9B5elH3AXNW99R1NO7szuJSJ+XvWLq9uIdTqMW2L3744RjyUPTvkla0c2ahDSFD 0VNg==
X-Gm-Message-State: AODbwcDBoxIEWNaVA59NAqpvpAZf/l+p6jaktY7V4a9Acngv5p1ChquG QprL3AE7RT+5iGUS
X-Received: by 10.80.140.203 with SMTP id r11mr2241576edr.18.1494578697642; Fri, 12 May 2017 01:44:57 -0700 (PDT)
Received: from McAsterix.local ([92.109.37.136]) by smtp.gmail.com with ESMTPSA id t17sm861288edh.1.2017.05.12.01.44.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 May 2017 01:44:52 -0700 (PDT)
Reply-To: huubatwork@gmail.com
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-shared-ring-protection-05.txt> (Shared-Ring protection (MSRP) mechanism for ring topology) to Proposed Standard
References: <149339519935.2881.8322243003635696392.idtracker@ietfa.amsl.com> <AD98114A73E97041A2EDDCC3F3D10B0373E84540@SMTP5.etri.info>
To: =?UTF-8?B?7KCV7YOc7Iud?= <cts@etri.re.kr>, "ietf@ietf.org" <ietf@ietf.org>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "draft-ietf-mpls-tp-shared-ring-protection@ietf.org" <draft-ietf-mpls-tp-shared-ring-protection@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>
From: Huub van Helvoort <huubatwork@gmail.com>
Message-ID: <7af362b9-17da-8d57-421c-d45ad07ab154@gmail.com>
Date: Fri, 12 May 2017 10:45:06 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <AD98114A73E97041A2EDDCC3F3D10B0373E84540@SMTP5.etri.info>
Content-Type: text/plain; charset=euc-kr; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/m_rFansAMPxtUZ7L7xWKExNE5WA>
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, 12 May 2017 08:49:57 -0000

Hello Taesik,

Thank you very much for reviewing the draft in detail
and for your valid comments.

We, the authors of the draft, will incorporate your comments.

Best regards, Huub.


---------
> Dear authors,
>
> I have two comments on this draft.
>
> 1) Section 4.4.1 (last two paragraphs above Figure 11)
>
> Following two sentences are duplicated in the last two paragraphs above Figure 11.
>
> Figure 11 shows the topology of single-node interconnected
> rings. Node C is the interconnection node between Ring1 and
> Ring2.
>
> Proposed change: delete the last paragraph.
>
>
> 2) Section 5.1.4.2 (3rd paragraph from the bottom)
>
> The last two bullet items correspond to conditions which trigger state transition from the Switching state to the Idle state. However, current text above those bullet items is describing adversely.
>
> Proposed change:
>
> OLD TEXT
> In one of the following conditions, transition from the Idle state to
> the Switching state MUST be triggered:
>
> NEW TEXT
> In one of the following conditions, transition from the Switching state to
> the Idle state MUST be triggered:
>
> Best regards,
> Taesik
>
>
> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of The IESG
> Sent: Saturday, April 29, 2017 1:00 AM
> To: IETF-Announce
> Cc: mpls@ietf.org; draft-ietf-mpls-tp-shared-ring-protection@ietf.org; mpls-chairs@ietf.org
> Subject: [mpls] Last Call: <draft-ietf-mpls-tp-shared-ring-protection-05.txt> (Shared-Ring protection (MSRP) mechanism for ring topology) to Proposed Standard
>
>
> The IESG has received a request from the Multiprotocol Label Switching WG
> (mpls) to consider the following document:
> - 'Shared-Ring protection (MSRP) mechanism for ring topology'
>    <draft-ietf-mpls-tp-shared-ring-protection-05.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-05-12. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document describes requirements, architecture and solutions for
>     MPLS-TP Shared Ring Protection (MSRP) in a ring topology for point-
>     to-point (P2P) services.  The MSRP mechanism is described to meet the
>     ring protection requirements as described in RFC 5654.  This document
>     defines the Ring Protection Switch (RPS) Protocol that is used to
>     coordinate the protection behavior of the nodes on MPLS ring.
>
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-mpls-tp-shared-ring-protection/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-mpls-tp-shared-ring-protection/ballot/
>
> The following IPR Declarations may be related to this I-D:
>
>     https://datatracker.ietf.org/ipr/2680/
>     https://datatracker.ietf.org/ipr/2681/
>     https://datatracker.ietf.org/ipr/2682/
>     https://datatracker.ietf.org/ipr/2683/
>
>
>
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


-- 
================================================================
Always remember that you are unique...just like everyone else...


From nobody Fri May 12 03:15:16 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 85A3E124234 for <ietf@ietfa.amsl.com>; Fri, 12 May 2017 03:15:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.599
X-Spam-Level: 
X-Spam-Status: No, score=-0.599 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 7kAUUIGGp3Do for <ietf@ietfa.amsl.com>; Fri, 12 May 2017 03:15:12 -0700 (PDT)
Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::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 5DE6A124BE8 for <ietf@ietf.org>; Fri, 12 May 2017 03:02:02 -0700 (PDT)
Received: by mail-wm0-x243.google.com with SMTP id y10so12790249wmh.0 for <ietf@ietf.org>; Fri, 12 May 2017 03:02:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-transfer-encoding:thread-index:content-language; bh=oQnKCKkJLrNlAZX4xJNMgmBx/EW0GihaikuU56lorcQ=; b=ahOXurkqNyp9mNz8UxJkThqFe56a8n5RG9QEgJ05Ua91KA8MUJsre5dSM8CMCMuJXW OuxYm8ovh8EXYG+eW3YtQiyy27XdZV2Jw/MEWkJd/a8llE+5DcHRhJxHTMX2wQ9KKkN6 NTT/t6hFCwhLFUkV63zZrT9/PzQyp+TtQmgJ1EuitTwhOYHxw9FKdtw58da9/498z1qI SR8gf1fhVMhbgjYo+VKUn/bU1+bXLF6Bnn/iEBQqgumrIjzmuxBDyAUGonp40iDsLUSc uI4QW4ci9TxEj6Ezar7lMHfcu4fz5R5R+logu/lZxyrOsXISQi56Zlkxyfd8d84yVIST Wv/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=oQnKCKkJLrNlAZX4xJNMgmBx/EW0GihaikuU56lorcQ=; b=k45TYGQ/CozCw8ZCxW8hQEjPMdK2SOcAPAq6PFxxhBU3jZEQaZs+/XJczk/moktDWp B9DoKfQYQCRYXkO7H51tyMZLybfJnHUKZnRietBcFlkSBxjfQYtoH7WJLV36onbIojrQ 2Ml04OC+J/i0hw7SmLeotZkaDnlWMfydh7UX6/7hf1fwSO3+btsKZHi6u+80ZHYH2eHE iAM+3jNfaifk63D3UIbppwXnZ8nJlbmI2FWgZkhzbQGVZTHg8OQw1DHITXDBbMzBYgga OfW7QekPlD4vVq2dTVckFPG/zY23NZmQwLh8Wj9NScB9hWKBNIbjwqiigKTLTIvYZxAw rS4A==
X-Gm-Message-State: AODbwcBf55B14qmdM1GP04BcsRzgpBllZLeBZ6lXHf1vu9FjOOTWYTe3 kIJPRPQj5wTS0YzY
X-Received: by 10.28.159.145 with SMTP id i139mr2050601wme.29.1494583320673; Fri, 12 May 2017 03:02:00 -0700 (PDT)
Received: from DESKTOPFLHJVQJ (p57A77DB8.dip0.t-ipconnect.de. [87.167.125.184]) by smtp.gmail.com with ESMTPSA id s75sm3685402wmd.3.2017.05.12.03.01.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 May 2017 03:02:00 -0700 (PDT)
From: "Mehmet Ersue" <mersue@gmail.com>
To: "'John Levine'" <johnl@taugh.com>, <ietf@ietf.org>
References: <012d01d2c999$d7adda40$87098ec0$@gmail.com><012d01d2c999$d7adda40$87098ec0$@gmail.com> <51f9d3d1-6c5c-102d-d76d-ea0d35433921@gih.com> <oevgrk$ms6$1@gal.iecc.com>
In-Reply-To: <oevgrk$ms6$1@gal.iecc.com>
Subject: RE: IETF #100 Hotel Rate
Date: Fri, 12 May 2017 12:02:00 +0200
Message-ID: <008301d2cb06$cc9736b0$65c5a410$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGODeFiUhNaXCmtjMiThoVgxtasTgGODeFiAXnT95YCE3P7QKJRFmkA
Content-Language: de
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HgyLt7E4Y3EpO2P6Lv2oOUzFFjE>
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, 12 May 2017 10:15:16 -0000

It's good there are options.
However, the meeting page indicates that Raffles is the main hotel.

https://www.ietf.org/meeting/100/index.html

Mehmet

> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of John Levine
> Sent: Wednesday, May 10, 2017 6:58 PM
> To: ietf@ietf.org
> Subject: Re: IETF #100 Hotel Rate
>=20
> In article <51f9d3d1-6c5c-102d-d76d-ea0d35433921@gih.com>,
> Olivier MJ Cr=C3=A9pin-Leblond <ocl@gih.com> wrote:
> >-=3D-=3D-=3D-=3D-=3D-
> >Unlikely to be the Raffles hotel itself. I guess the conference is at
> >the Raffles City convention centre which has 2 hotels: the Fairmont &
> >the Swisshotel. Rates are lower than the super luxurious Raffles
> >itself, which is just across the road.
>=20
> Right, that's where ICANN met a few years ago.  The Fairmont and =
Swissotel
> are directly connected to the conference centre.  I don't recall what =
the
rates
> were but they weren't out of line with other Fairmont and Swissotels =
where
> we've met.
>=20
> I do recommend making the trip across the road to Long's Bar in the
Raffles
> hotel for the original Singapore Sling.
>=20
> R's,
> John



From nobody Fri May 12 08:28:44 2017
Return-Path: <olejacobsen@me.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 50A8712941D for <ietf@ietfa.amsl.com>; Fri, 12 May 2017 08:28:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 (2048-bit key) header.d=me.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 ayvY2yiZtjm1 for <ietf@ietfa.amsl.com>; Fri, 12 May 2017 08:28:41 -0700 (PDT)
Received: from pv42p55im-ztdg10051601.me.com (pv42p55im-ztdg10051601.me.com [17.139.148.156]) (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 9BB1612EC80 for <ietf@ietf.org>; Fri, 12 May 2017 08:23:49 -0700 (PDT)
Received: from process-dkim-sign-daemon.pv42p55im-ztdg10051601.me.com by pv42p55im-ztdg10051601.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OPU00800IQJ2100@pv42p55im-ztdg10051601.me.com> for ietf@ietf.org; Fri, 12 May 2017 15:23:49 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1494602628; bh=qMrwZfIEVFlbGreyXHlaWo7J5vz8MwzdtholWaBcoVI=; h=Content-type:From:MIME-version:Subject:Message-id:Date:To; b=V5ZEt+14InIcNjm7btVjOU8hr+XmD45IUMtLYMS01TETjUBb/4vRE5mDcXHRP1R8u t7V2ZxF+lN1BZzEvNZKr/DzNNQoAmqiU5XTcLHEus6oblnWrZ9dKNGILzXrxZeFrEC q8aY5yeFx5rA2YVVtJljM+xWY0PbR6woIqM1aMP4EMWirmLTUGMgghG2iPVYbutDbf ZAuKfQxOj+3ZCORR/pQjArO6DHsynZfymoxOMfCgXKW6yVEd9ABy9BpRWi+r6LrQ/P Hd4ZzgQT17bs+JSL2Ao9IWvENe3jS+1KXXUtdeLOqjuaeZTFwWhQGrsJh6LPv20Hgo 6IDFDcVz0srBQ==
Received: from icloud.com ([127.0.0.1]) by pv42p55im-ztdg10051601.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OPU00CRVIRFRX40@pv42p55im-ztdg10051601.me.com> for ietf@ietf.org; Fri, 12 May 2017 15:23:48 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-05-12_08:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=1 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1705120290
Content-transfer-encoding: 7bit
Content-type: multipart/alternative; boundary=Apple-Mail-CF5CF535-46F4-427D-A263-9A8BC93BE187
From: Ole Jacobsen <olejacobsen@me.com>
MIME-version: 1.0 (1.0)
Subject: Raffles Convention Center Singapore for IETF 100
Message-id: <BF311943-F2E1-495A-95C2-1F2201073846@me.com>
Date: Fri, 12 May 2017 17:23:39 +0200
To: ietf@ietf.org
X-Mailer: iPhone Mail (14E304)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dxNwB0Wp9FXkxtIbnqFhpFbGC34>
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, 12 May 2017 15:28:42 -0000

--Apple-Mail-CF5CF535-46F4-427D-A263-9A8BC93BE187
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

The hotels and the rates will be
published along with the other typical meeting information as is
normally done.  In this case the information is expected to be available
during the Prague meeting in July, and registration would open shortly there=
after
The venue hotel is NOT the Raffles hotel with those high rates that were quo=
ted.


Ole J. Jacobsen
Editor & Publisher
The Internet Protocol Journal
Cell: +1 415 370-4628
T-Mobile: +1 415 889-9821
http://protocoljournal.org

Sent from my iPhone=

--Apple-Mail-CF5CF535-46F4-427D-A263-9A8BC93BE187
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><span></span></div><div><meta http-equ=
iv=3D"content-type" content=3D"text/html; charset=3Dutf-8"><div><span></span=
></div><div><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"><div><span style=3D"background-color: rgba(255, 255, 255, 0);">The ho=
tels and the rates will be<br>published along with the other typical meeting=
 information as is<br>normally done. &nbsp;In this case the information is e=
xpected to be available<br>during the Prague meeting in July, and registrati=
on would open shortly thereafter</span><br>The venue hotel is NOT the Raffle=
s hotel with those high rates that were quoted.</div><div><br></div><div><br=
><div><div style=3D"font-family: UICTFontTextStyleBody; font-size: 18px; -we=
bkit-text-size-adjust: auto;">Ole J. Jacobsen</div><div style=3D"font-family=
: UICTFontTextStyleBody; font-size: 18px; -webkit-text-size-adjust: auto;">E=
ditor &amp; Publisher</div><div style=3D"font-family: UICTFontTextStyleBody;=
 font-size: 18px; -webkit-text-size-adjust: auto;">The Internet Protocol Jou=
rnal</div><div style=3D"font-family: UICTFontTextStyleBody; font-size: 18px;=
 -webkit-text-size-adjust: auto;">Cell: +1 415 370-4628</div><div style=3D"f=
ont-family: UICTFontTextStyleBody; font-size: 18px; -webkit-text-size-adjust=
: auto;">T-Mobile: +1 415 889-9821</div></div><div style=3D"font-family: UIC=
TFontTextStyleBody; font-size: 18px; -webkit-text-size-adjust: auto;"><a hre=
f=3D"http://protocoljournal.org">http://protocoljournal.org</a></div><div><b=
r></div>Sent from my iPhone</div></div></div></body></html>=

--Apple-Mail-CF5CF535-46F4-427D-A263-9A8BC93BE187--


From nobody Fri May 12 09:02:06 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 A1C2E1298BA for <ietf@ietf.org>; Fri, 12 May 2017 09:02:03 -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@ietf.org>
Subject: IETF WebEx Account Patch Applied Tonight
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <149460492365.13394.1057617802177377917.idtracker@ietfa.amsl.com>
Date: Fri, 12 May 2017 09:02:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/n7J5UJkGYiNDzq7oILyo77ASQiw>
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, 12 May 2017 16:02:04 -0000

As many of you use the IETF WebEx account for IETF virtual meetings, we thought it important to let you know that tonight, Friday May 12, 2017 between 7:00 PM and 11:59 PM PDT (GMT-7), Cisco will be applying an Emergency Patch to the WebEx Meeting Center. 

Please note that after the patch has been applied to ietf.webex.com, you will receive the new version of the WebEx meeting client upon entering a session for the first time.

IETF Secretariat


From nobody Fri May 12 13:37:38 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 5ED3A131445; Fri, 12 May 2017 13:37:31 -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: <art@ietf.org>
Cc: ietf@ietf.org, draft-ietf-nfsv4-versioning.all@ietf.org, nfsv4@ietf.org
Subject: Artart last call review of draft-ietf-nfsv4-versioning-09
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149462145126.13443.7366912235626631179@ietfa.amsl.com>
Date: Fri, 12 May 2017 13:37:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Tz3zMw-5B7e7Bk5wifzoaX4vgvY>
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, 12 May 2017 20:37:32 -0000

Reviewer: Matthew Miller
Review result: Ready with Issues

Document: draft-ietf-nfsv4-versioning-09
IETF LC End Date: 2017-05-12
IESG Telechat date: 2017-05-25

This document provides guidance for dealing with extensions
and versioning in NFSv4, including how and when to update
minor versions.

This document is mostly ready.  Some of the grammatical choices
make for a more difficult read; the most obvious ones to me are
nits below.

Major issues:

NONE

Minor issues:

NONE

Nits/editorial comments:

* For the bullet points in this document, some end in periods and
some don't.  I recommend the authors choose one and update
accordingly.

* In section 1. "Introduction", the last sentence is very clumsy.
The Gen-ART review already points this out, and provides what I think
is a good suggested change.

* In section 4.4.2 "Establishing Interoperability", the phrase
"client
would uses" should be "client uses"

* In section 5.2 "Behavioral Changes", the following sentence is
difficult parse:

   """
   One class of behavioral change involves changes in the set of
errors
   to be returned in the event of various errors.
   """

I think the following has the same meaning:

   """
   One class of behavior change involves changes in the set of errors
   to be returned when various failure conditions occur.
   """

That's not tremendously better, but I think it's a little easier to
wrap one's mind around.

* In the title for Section 9.3 "XDR Corrections to REQUIRED
features",
"Features" should be capitalized.

* In Section 9.3 "XDR Corrections to REQUIRED features", the word
"correct" should be "corrected" in the sentence "Such clients would
only
be capable of interoperating with servers that supported the correct
version."



From nobody Fri May 12 14:17:12 2017
Return-Path: <pmcmanus@mozilla.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 3B7291314BB; Fri, 12 May 2017 14:17:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.734
X-Spam-Level: 
X-Spam-Status: No, score=-0.734 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_HELO_PASS=-0.001, 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 hLr7m4rT1McK; Fri, 12 May 2017 14:17:01 -0700 (PDT)
Received: from linode64.ducksong.com (linode6only.ducksong.com [IPv6:2600:3c02::f03c:91ff:fe6e:e8da]) by ietfa.amsl.com (Postfix) with ESMTP id 0C359126DED; Fri, 12 May 2017 14:12:55 -0700 (PDT)
Received: from mail-qt0-f177.google.com (mail-qt0-f177.google.com [209.85.216.177]) by linode64.ducksong.com (Postfix) with ESMTPSA id 5AC0F3A0A2; Fri, 12 May 2017 17:12:53 -0400 (EDT)
Received: by mail-qt0-f177.google.com with SMTP id f55so9305115qta.3; Fri, 12 May 2017 14:12:53 -0700 (PDT)
X-Gm-Message-State: AODbwcBBxmndEuK8IDt6M4QYOtlV+mMbdjmctDRyNMnps/ZG8lbs8KYR kM+Atot/8MDE8wfBgeFzJbgFqLBcXA==
X-Received: by 10.200.40.193 with SMTP id j1mr6158200qtj.186.1494623573075; Fri, 12 May 2017 14:12:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.178.74 with HTTP; Fri, 12 May 2017 14:12:52 -0700 (PDT)
In-Reply-To: <2D57FF92-3A56-43BC-A815-27801E31F770@tzi.org>
References: <149179722452.3118.982908107963516290@ietfa.amsl.com> <5E5238DC-B835-4BDF-B50D-8D594A46C4D4@tzi.org> <767F913A-586B-42A2-B021-F9AC5C478702@mnot.net> <2D57FF92-3A56-43BC-A815-27801E31F770@tzi.org>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Fri, 12 May 2017 17:12:52 -0400
X-Gmail-Original-Message-ID: <CAOdDvNppxEj4NoTcE5_LvcnK80zxRdFjgwepCdNs0N2E+-00HQ@mail.gmail.com>
Message-ID: <CAOdDvNppxEj4NoTcE5_LvcnK80zxRdFjgwepCdNs0N2E+-00HQ@mail.gmail.com>
Subject: Re: [art] Artart last call review of draft-ietf-core-coap-tcp-tls-07
To: Carsten Bormann <cabo@tzi.org>
Cc: Mark Nottingham <mnot@mnot.net>, art@ietf.org, draft-ietf-core-coap-tcp-tls.all@ietf.org,  IETF Discussion Mailing List <ietf@ietf.org>, core@ietf.org
Content-Type: multipart/alternative; boundary="001a11406bf6257010054f5a2b50"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-AthVLgVOs55ewALN6-l1h6HkQ4>
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, 12 May 2017 21:17:04 -0000

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

I have a few thoughts on this draft too.

6455-Websockets was a point in time solution for a problem that was solved
later and better by HTTP/2 (RFC 7540) with the introduction of parallelism,
multiplexing, and non 1:1 bi-directional message capabilities (which 6455
only solves 1/3 of).. 6455 is now considered historical and legacy cruft by
many. I don't know of anyone that would think that if 6455 did not exist it
should be introduced into today's ecosystem. (we would still want a
dev-facing interface doing some of the same things as websockets at a js
layer, but it would not be implemented on the wire 6455 style.)

If the motivation of the websockets-coap binding is to deal with
bi-directional problems better than HTTP/1, the answer to me seems to be to
use HTTP/2 (and maybe an extension of the existing http mapping) rather
than building a parallel system of gateways, proxies, and tunnels on top of
6455. It is unfortunate enough (perhaps unavoidable?) that we have a
parallel stack of constrained protocols without building a gatewaying
system between them rooted in legacy baggage.

The draft as much as acknowledges this with some not totally convincing
handwaving (that is not meant pejoratively - I've been known to hand wave
:))

Although HTTP/2 could also potentially address these requirements,
there would be
   additional costs and delays introduced by such a transition.
   Currently, there are also fewer HTTP/2 implementations available for
   constrained devices in comparison to CoAP.

The aspects of the proposed solution that would seem to pose the largest
challenges for constrained devices, (tcp and tls) are also present in
wss:// as well - which begs the question of whether this is designing a
nominally constrained-device ecosystem actually for
not-so-badly-constrained gateways and they should be using our primary
security, application, and transport standards directly. This parallel
stack has to end somewhere, right?

also, if you stay within the semantics of http, but require 7540 or its
successors for reasons of performance, you will pick up quic for free when
we get there - which is just a specific instance of the general argument
with forking standards.

lastly I think the security considerations (both in that section and
elsewhere) could use some work.

The purpose of websockets-6455 is to deploy a mechanism, consistent with
the web security model, for non-privileged javascript to be able to
communicate using communication patterns that do not fit into the HTTP/1
request/reply pattern well. To be consistent with that security model a
websockets end point needs to opt into doing websockets, potentially doing
a particular sub-protocol, and be expecting this request to have been
triggered by a particular Origin.

The net effect is to prohibit random javascript from the web from spraying
around arbitrary TCP streams behind every user agent's firewall, or
otherwise generating arbitrary botnets (beyond what is allowed by SOP
anyhow).

The coap-tcp-tls-websockets forward-proxy model builds an arbitrary gateway
from websockets to coap based on proxy-uri and would seem to run afoul of
the security model by spraying arbitrary coap around instead of arbitrary
tcp :).. Reverse proxy models, being locked down to particular origins,
work better.

(and as a final nit the websocket handshake examples do not have an Origin
request header as required by 6455 for browsers, and I think browsers are
in scope of this document - but thinking and talking about Origin is a key
part of when websockets is and is not appropriate.).

-Patrick



On Wed, May 10, 2017 at 12:31 AM, Carsten Bormann <cabo@tzi.org> wrote:

>
> > On May 9, 2017, at 23:30, Mark Nottingham <mnot@mnot.net> wrote:
> >
> > To close this loop -- the change in -08 isn't sufficiently prominent
> IME; while the general nature of the change is listed in the Abstract, th=
e
> actual normative text is very hard to find.
>
> Certainly, let=E2=80=99s see what the IESG decides here.
>
> > Given that this is a pretty fundamental change in the operation of a UR=
I
> scheme, I'd think it at least deserves its own section, if not a separate
> document.
>
> I don=E2=80=99t agree that this is such a fundamental change here =E2=80=
=94 the
> /.well-known name space in the URI already was special (by the fact that =
ws
> URIs are mapped to http URIs, which do have /.well-known reserved already=
).
>
> But that doesn=E2=80=99t matter, we should find the best editorial way to=
 document
> making the well-known URI concept available to WebSocket URIs.
>
> Gr=C3=BC=C3=9Fe, Carsten
>
>

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

<div dir=3D"ltr"><div>I have a few thoughts on this draft too.<br></div><di=
v><br></div><div>6455-Websockets was a point in time solution for a problem=
 that was solved later and better by HTTP/2 (RFC 7540) with the introductio=
n of parallelism, multiplexing, and non 1:1 bi-directional message capabili=
ties (which 6455 only solves 1/3 of).. 6455 is now considered historical an=
d legacy cruft by many. I don&#39;t know of anyone that would think that if=
 6455 did not exist it should be introduced into today&#39;s ecosystem. (we=
 would still want a dev-facing interface doing some of the same things as w=
ebsockets at a js layer, but it would not be implemented on the wire 6455 s=
tyle.)<br></div><div><br></div><div>If the motivation of the websockets-coa=
p binding is to deal with bi-directional problems better than HTTP/1, the a=
nswer to me seems to be to use HTTP/2 (and maybe an extension of the existi=
ng http mapping) rather than building a parallel system of gateways, proxie=
s, and tunnels on top of 6455. It is unfortunate enough (perhaps unavoidabl=
e?) that we have a parallel stack of constrained protocols without building=
 a gatewaying system between them rooted in legacy baggage.<br></div><div><=
br></div><div>The draft as much as acknowledges this with some not totally =
convincing handwaving (that is not meant pejoratively - I&#39;ve been known=
 to hand wave :))<br></div><div><pre class=3D"gmail-newpage">Although HTTP/=
2 could also potentially address these requirements, there would be
   additional costs and delays introduced by such a transition.
   Currently, there are also fewer HTTP/2 implementations available for
   constrained devices in comparison to CoAP.</pre></div><div></div><div> T=
he aspects of the proposed solution that would seem to pose the largest cha=
llenges for constrained devices, (tcp and tls) are also present in wss:// a=
s well - which begs the question of whether this is designing a nominally c=
onstrained-device ecosystem actually for not-so-badly-constrained gateways =
and they should be using our primary security, application, and transport s=
tandards directly. This parallel stack has to end somewhere, right?<br></di=
v><div><br></div><div>also, if you stay within the semantics of http, but r=
equire 7540 or its successors for reasons of performance, you will pick up =
quic for free when we get there - which is just a specific instance of the =
general argument with forking standards.</div><div><br></div><div>lastly I =
think the security considerations (both in that section and elsewhere) coul=
d use some work.</div><div><br></div><div><div>The purpose of websockets-64=
55 is to deploy a mechanism, consistent
 with the web security model, for non-privileged javascript to be able=20
to communicate using communication patterns that do not fit into the=20
HTTP/1 request/reply pattern well. To be consistent with that security=20
model a websockets end point needs to opt into doing websockets,=20
potentially doing a particular sub-protocol, and be expecting this=20
request to have been triggered by a particular Origin.</div><div><br></div>=
<div>The
 net effect is to prohibit random javascript from the web from spraying=20
around arbitrary TCP streams behind every user agent&#39;s firewall, or=20
otherwise generating arbitrary botnets (beyond what is allowed by SOP=20
anyhow).<br></div><div><br></div><div>The coap-tcp-tls-websockets=20
forward-proxy model builds an arbitrary gateway from websockets to coap=20
based on proxy-uri and would seem to run afoul of the security model by=20
spraying arbitrary coap around instead of arbitrary tcp :).. Reverse=20
proxy models, being locked down to particular origins, work better.</div><d=
iv><br></div><div>(and as
 a final nit the websocket handshake examples do not have an Origin request=
=20
header as required by 6455 for browsers, and I think browsers are in=20
scope of this document - but thinking and talking about Origin is a key par=
t of when websockets is and is not appropriate.).</div></div><div><br></div=
><div>-Patrick</div><div><br></div><div><br></div></div><div class=3D"gmail=
_extra"><br><div class=3D"gmail_quote">On Wed, May 10, 2017 at 12:31 AM, Ca=
rsten 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"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><span class=3D""><br>
&gt; On May 9, 2017, at 23:30, Mark Nottingham &lt;<a href=3D"mailto:mnot@m=
not.net">mnot@mnot.net</a>&gt; wrote:<br>
&gt;<br>
&gt; To close this loop -- the change in -08 isn&#39;t sufficiently promine=
nt IME; while the general nature of the change is listed in the Abstract, t=
he actual normative text is very hard to find.<br>
<br>
</span>Certainly, let=E2=80=99s see what the IESG decides here.<br>
<span class=3D""><br>
&gt; Given that this is a pretty fundamental change in the operation of a U=
RI scheme, I&#39;d think it at least deserves its own section, if not a sep=
arate document.<br>
<br>
</span>I don=E2=80=99t agree that this is such a fundamental change here =
=E2=80=94 the /.well-known name space in the URI already was special (by th=
e fact that ws URIs are mapped to http URIs, which do have /.well-known res=
erved already).<br>
<br>
But that doesn=E2=80=99t matter, we should find the best editorial way to d=
ocument making the well-known URI concept available to WebSocket URIs.<br>
<br>
Gr=C3=BC=C3=9Fe, Carsten<br>
<br>
</blockquote></div><br></div>

--001a11406bf6257010054f5a2b50--


From nobody Fri May 12 16:09:01 2017
Return-Path: <oritl@microsoft.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 33439131496; Fri, 12 May 2017 16:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level: 
X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-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=microsoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v2zFRFJ-zc-z; Fri, 12 May 2017 16:08:51 -0700 (PDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0097.outbound.protection.outlook.com [104.47.40.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E599A12EC83; Fri, 12 May 2017 16:05:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=A+dyErgFM1oZcJ35L/evqZnyyDEZrchENOTfuyFbSAY=; b=KdxDittLv22cDMaObhVlTxtptpQEB9i0VMIFOh6H7TgbzXcZZHw1jUmzIFgKtI/kOz/2fh15ea0EJmyQuXx7tb0aDhABGYeptjt+djMGOqHmLX3ZmEeYNZ+XHsxoisbIeueRbqoZTLnfG0imXNHWvC+VcHguv17M5tBhvH4Trt8=
Received: from CY1PR0301MB2122.namprd03.prod.outlook.com (10.164.2.156) by CY1PR0301MB2124.namprd03.prod.outlook.com (10.164.2.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1084.16; Fri, 12 May 2017 23:05:18 +0000
Received: from CY1PR0301MB2122.namprd03.prod.outlook.com ([10.164.2.156]) by CY1PR0301MB2122.namprd03.prod.outlook.com ([10.164.2.156]) with mapi id 15.01.1084.022; Fri, 12 May 2017 23:05:17 +0000
From: Orit Levin <oritl@microsoft.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-calext-caldav-attachments.all@tools.ietf.org" <draft-ietf-calext-caldav-attachments.all@tools.ietf.org>
Subject: Gen-ART Last Call review of draft-ietf-calext-caldav-attachments-02
Thread-Topic: Gen-ART Last Call review of draft-ietf-calext-caldav-attachments-02
Thread-Index: AdLLcmgbqXfPTnnvRVagW4WBZNOBOQ==
Date: Fri, 12 May 2017 23:05:17 +0000
Message-ID: <CY1PR0301MB2122EF13B247A2A22EC637C4ADE20@CY1PR0301MB2122.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:4::47b]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY1PR0301MB2124; 7:BVPk3Xs2XzgXWOqFX0W0J1PGoJRoWMt1cQiJDFEbmPYkBBABuKCzQom6BJZ4nElSvmKeqYaOEgAMzvfcZgmXkvF6D14NvhOu7hVwbReEY9xzHnuOMBhWvHGRAOlaoQs5tuBaNjqJub99keQ7U/fti+NVgNY5ERqYwdMyfgIcyALPcySypmu3jC9qql1+IyXRlVsgKaIfvyS3QZMsRT8aGQBnMo3vnMx7AJvSwvLdMRCTOHwaC8XhXUqvzh8G1qALj10MXQzVMVkVhgmBxUq+/gmqUrhSoDl6WWWsbUN9nI3TFuT/c0MGr0T2Un/KMYK1KTCQR5L3G00ZHvGq7GWXt/XvJCNRm22mO3xlmKT5j/U=
x-ms-office365-filtering-correlation-id: 00a43afd-569c-49d0-44cf-08d4998b5b75
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081)(201702281549075); SRVR:CY1PR0301MB2124; 
x-microsoft-antispam-prvs: <CY1PR0301MB2124BD88C3CC7AE5E05ED2FAADE20@CY1PR0301MB2124.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(6055026)(61426038)(61427038)(6041248)(20161123560025)(20161123558100)(20161123564025)(20161123555025)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6072148); SRVR:CY1PR0301MB2124; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0301MB2124; 
x-forefront-prvs: 0305463112
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39400400002)(39840400002)(39860400002)(39410400002)(39850400002)(39450400003)(377424004)(199003)(189002)(81166006)(77096006)(9686003)(8676002)(606005)(236005)(55016002)(8990500004)(10090500001)(2900100001)(86612001)(3660700001)(54906002)(6506006)(5640700003)(33656002)(25786009)(54896002)(122556002)(99286003)(6306002)(5005710100001)(2351001)(3280700002)(189998001)(5660300001)(6436002)(50986999)(54356999)(6916009)(53936002)(110136004)(8936002)(10290500003)(2906002)(7736002)(74316002)(38730400002)(102836003)(86362001)(790700001)(6116002)(7906003)(4326008)(2501003)(7696004)(230783001)(478600001)(5630700001); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0301MB2124; H:CY1PR0301MB2122.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CY1PR0301MB2122EF13B247A2A22EC637C4ADE20CY1PR0301MB2122_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 May 2017 23:05:17.8397 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0301MB2124
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2hUe00IoPG1iBK-l102fswuKq4M>
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, 12 May 2017 23:08:53 -0000

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

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 t=
he IETF Chair.  Please treat these comments just like any other last call c=
omments.



For more information, please see the FAQ at



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



Document: draft-ietf-isis-mi-bis-02

Reviewer: Orit Levin

Review Date: 2017-04-06

IETF LC End Date: 2017-05-14

IESG Telechat date:



Summary: This draft is ready for publication.
The document is very well organized and clearly written. My only comment or=
 question is related to backwards compatibility and mixed systems.
Is there a possibility that all or some of the clients do not support the n=
ew functionality?
Is there a possibility that a server doesn't support the new functionality?
If the answer to one of these questions is yes, how is it being dealt with =
by the SW? How would it affect human experience?

Thanks,
Orit.

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">I am the assigned Gen-ART reviewer for this draft=
. The General Area Review Team (Gen-ART) reviews all IETF documents being p=
rocessed by the IESG for the IETF Chair.&nbsp; Please treat these comments =
just like any other last call comments.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">For more information, please see the FAQ at<o:p><=
/o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&lt;<a href=3D"http://wiki.tools.ietf.org/area/ge=
n/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArt=
faq</a>&gt;.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Document: draft-ietf-isis-mi-bis-02<o:p></o:p></p=
>
<p class=3D"MsoPlainText">Reviewer: Orit Levin<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 2017-04-06<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 2017-05-14<o:p></o:p></p>
<p class=3D"MsoPlainText">IESG Telechat date: <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary: This draft is ready for publication.<o:p=
></o:p></p>
<p class=3D"MsoNormal">The document is very well organized and clearly writ=
ten. My only comment or question is related to backwards compatibility and =
mixed systems.
<o:p></o:p></p>
<p class=3D"MsoNormal">Is there a possibility that all or some of the clien=
ts do not support the new functionality?
<o:p></o:p></p>
<p class=3D"MsoNormal">Is there a possibility that a server doesn&#8217;t s=
upport the new functionality?
<o:p></o:p></p>
<p class=3D"MsoNormal">If the answer to one of these questions is yes, how =
is it being dealt with by the SW? How would it affect human experience?<o:p=
></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal">Orit.<o:p></o:p></p>
</div>
</body>
</html>

--_000_CY1PR0301MB2122EF13B247A2A22EC637C4ADE20CY1PR0301MB2122_--


From nobody Sat May 13 06:28:46 2017
Return-Path: <davenoveck@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 56C961270A3; Sat, 13 May 2017 06:28: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, 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 DUruH1c0tder; Sat, 13 May 2017 06:28:42 -0700 (PDT)
Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::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 B6E2C126C7A; Sat, 13 May 2017 06:26:46 -0700 (PDT)
Received: by mail-it0-x229.google.com with SMTP id c15so23696914ith.0; Sat, 13 May 2017 06:26: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=YZY8iA6bLd3FmN+jqpzi3k+Xr4N8TsPjinEHKdLnDjM=; b=s6lJ61VNCyaH+k/x0KTiLqTo1ZuWnagQlxqF7LMubJgM2J5nVAFzzLWOvsu5iU7D/u st1rkeFNsdRz4M/mn/AwU/zb4i9pVb3SoqfAYB3HJoKFJRfGjbtXJkqywcjQMtNbTk54 A8mPK6E/JE2yw6VxB7COoVbOaeIgg/eOjftTtgf5whhqDZx4Odj9CofwcGcb1RJ89a0K Q8KhFqBAHF9LNH3wPKPJB/7wHbl81zuwZBZExworvyem7WwrZbtWMnshS7Sq/PcMn4nu S6/wr5E2TRbBeV2yPpBPyyCukGzeSRVfe0MlsVgAHUha8TI8x5uTyrBnGnid1CLbipHE 0hIA==
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=YZY8iA6bLd3FmN+jqpzi3k+Xr4N8TsPjinEHKdLnDjM=; b=eh20JcLPF6zK5XwNTvEKZkCZwAYnuNDDiU9639IoaazkDh2aVIVFkDWmjreN75gCjx ekj246UFNhNDrnMJEsDeIaIN4HOAwSmikj+7BM/PsFLWt90Z9rFuo3fdzORAwcEWwiDO m9SJf+M6HFyl4x+adlIKWjjQ2GFb5gCdhiXbyXklIvugRPhJ0ftwk8o15noXBcAbgatO PLO3DhdFsw0/26n/mriv568caxqOgLDiFPalyL0diRld7llm20jrnSW/Jevgm0YIVih1 JKkqDcUXeWq6s75ndt/Gi5FgaNx0un2cAL1r3toYXid0ItBW1UQnM1Yb6Wzj5KhWNIWy RF+Q==
X-Gm-Message-State: AODbwcCvotIIduCvWOpq7SNwsG+p2sX0FLvCOl+0I6j+zZWYsIm94PKj gYjPU/6YJe8Id8xVza7I4kXYC8xeHg==
X-Received: by 10.36.108.147 with SMTP id w141mr9090415itb.57.1494682006002; Sat, 13 May 2017 06:26:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.20.75 with HTTP; Sat, 13 May 2017 06:26:45 -0700 (PDT)
In-Reply-To: <149462145126.13443.7366912235626631179@ietfa.amsl.com>
References: <149462145126.13443.7366912235626631179@ietfa.amsl.com>
From: David Noveck <davenoveck@gmail.com>
Date: Sat, 13 May 2017 09:26:45 -0400
Message-ID: <CADaq8jctpRi95B97LdTb7TZ_4oib0i56ArPym95h8R4eBDwVtg@mail.gmail.com>
Subject: Re: Artart last call review of draft-ietf-nfsv4-versioning-09
To: Matthew Miller <linuxwolf+ietf@outer-planes.net>
Cc: art@ietf.org, ietf@ietf.org, draft-ietf-nfsv4-versioning.all@ietf.org,  "nfsv4@ietf.org" <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="001a114417aa052965054f67c626"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9xHPjCeq0CJkl8RD8UB9iqLrK6o>
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, 13 May 2017 13:28:44 -0000

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

Thanks for the review.

> * For the bullet points in this document, some end in periods and
> some don't.  I recommend the authors choose one and update
> accordingly.

Will update those without periods.

> * In section 1. "Introduction", the last sentence is very clumsy.
> The Gen-ART review already points this out, and provides what I think
> is a good suggested change.

It has been updated.

> * In section 4.4.2 "Establishing Interoperability", the phrase
> "client
> would uses" should be "client uses"

Will fix.

> * In section 5.2 "Behavioral Changes", the following sentence is
> difficult parse:

...

> I think the following has the same meaning:
>
>   """
>   One class of behavior change involves changes in the set of errors
>   to be returned when various failure conditions occur.
>   """
>
> That's not tremendously better, but I think it's a little easier to
> wrap one's mind around.

Will change.

> * In the title for Section 9.3 "XDR Corrections to REQUIRED
> features",
> "Features" should be capitalized.

Will fix.

> * In Section 9.3 "XDR Corrections to REQUIRED features", the word
> "correct" should be "corrected" in the sentence "Such clients would
> only
> be capable of interoperating with servers that supported the correct
> version."

Will fix.


On Fri, May 12, 2017 at 4:37 PM, Matthew Miller <
linuxwolf+ietf@outer-planes.net> wrote:

> Reviewer: Matthew Miller
> Review result: Ready with Issues
>
> Document: draft-ietf-nfsv4-versioning-09
> IETF LC End Date: 2017-05-12
> IESG Telechat date: 2017-05-25
>
> This document provides guidance for dealing with extensions
> and versioning in NFSv4, including how and when to update
> minor versions.
>
> This document is mostly ready.  Some of the grammatical choices
> make for a more difficult read; the most obvious ones to me are
> nits below.
>
> Major issues:
>
> NONE
>
> Minor issues:
>
> NONE
>
> Nits/editorial comments:
>
> * For the bullet points in this document, some end in periods and
> some don't.  I recommend the authors choose one and update
> accordingly.
>
> * In section 1. "Introduction", the last sentence is very clumsy.
> The Gen-ART review already points this out, and provides what I think
> is a good suggested change.
>
> * In section 4.4.2 "Establishing Interoperability", the phrase
> "client
> would uses" should be "client uses"
>
> * In section 5.2 "Behavioral Changes", the following sentence is
> difficult parse:
>
>    """
>    One class of behavioral change involves changes in the set of
> errors
>    to be returned in the event of various errors.
>    """
>
> I think the following has the same meaning:
>
>    """
>    One class of behavior change involves changes in the set of errors
>    to be returned when various failure conditions occur.
>    """
>
> That's not tremendously better, but I think it's a little easier to
> wrap one's mind around.
>
> * In the title for Section 9.3 "XDR Corrections to REQUIRED
> features",
> "Features" should be capitalized.
>
> * In Section 9.3 "XDR Corrections to REQUIRED features", the word
> "correct" should be "corrected" in the sentence "Such clients would
> only
> be capable of interoperating with servers that supported the correct
> version."
>
>
>

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

<div dir=3D"ltr">Thanks for the review.<div><br></div><div><span style=3D"f=
ont-size:16px">&gt; * For the bullet points in this document, some end in p=
eriods and</span><br style=3D"font-size:16px"><span style=3D"font-size:16px=
">&gt; some don&#39;t.=C2=A0 I recommend the authors choose one and update<=
/span><br style=3D"font-size:16px"><span style=3D"font-size:16px">&gt; acco=
rdingly.</span><br></div><div><span style=3D"font-size:16px"><br></span></d=
iv><div><span style=3D"font-size:16px">Will update those without periods.</=
span></div><div><span style=3D"font-size:16px"><br></span></div><div><span =
style=3D"font-size:16px">&gt; * In section 1. &quot;Introduction&quot;, the=
 last sentence is very clumsy.</span></div><span style=3D"font-size:16px">&=
gt; The Gen-ART review already points this out, and provides what I think</=
span><br style=3D"font-size:16px"><span style=3D"font-size:16px">&gt; is a =
good suggested change.</span><div><span style=3D"font-size:16px"><br></span=
></div><div><span style=3D"font-size:16px">It has been updated.</span></div=
><div><span style=3D"font-size:16px"><br></span></div><div><span style=3D"f=
ont-size:16px">&gt; * In section 4.4.2 &quot;Establishing Interoperability&=
quot;, the phrase</span><br style=3D"font-size:16px"><span style=3D"font-si=
ze:16px">&gt; &quot;client</span><br style=3D"font-size:16px"><span style=
=3D"font-size:16px">&gt; would uses&quot; should be &quot;client uses&quot;=
</span><span style=3D"font-size:16px"><br></span></div><div><span style=3D"=
font-size:16px"><br></span></div><div><span style=3D"font-size:16px">Will f=
ix.</span></div><div><span style=3D"font-size:16px"><br></span></div><div><=
span style=3D"font-size:16px">&gt; * In section 5.2 &quot;Behavioral Change=
s&quot;, the following sentence is</span></div><span style=3D"font-size:16p=
x">&gt; difficult parse:</span><div><br style=3D"font-size:16px">...<br sty=
le=3D"font-size:16px"><span style=3D"font-size:16px">=C2=A0 =C2=A0</span><b=
r style=3D"font-size:16px"><span style=3D"font-size:16px">&gt; I think the =
following has the same meaning:</span><br style=3D"font-size:16px">&gt;<br =
style=3D"font-size:16px"><span style=3D"font-size:16px">&gt; =C2=A0 &quot;&=
quot;&quot;</span><br style=3D"font-size:16px"><span style=3D"font-size:16p=
x">&gt; =C2=A0 One class of behavior change involves changes in the set of =
errors</span><br style=3D"font-size:16px"><span style=3D"font-size:16px">&g=
t; =C2=A0 to be returned when various failure conditions occur.</span><br s=
tyle=3D"font-size:16px"><span style=3D"font-size:16px">&gt; =C2=A0 &quot;&q=
uot;&quot;</span><br style=3D"font-size:16px">&gt;<br style=3D"font-size:16=
px"><span style=3D"font-size:16px">&gt; That&#39;s not tremendously better,=
 but I think it&#39;s a little easier to</span><br style=3D"font-size:16px"=
><span style=3D"font-size:16px">&gt; wrap one&#39;s mind around.</span></di=
v><div><br></div><div>Will change.</div><div><br></div><div><span style=3D"=
font-size:16px">&gt; * In the title for Section 9.3 &quot;XDR Corrections t=
o REQUIRED</span><br style=3D"font-size:16px"><span style=3D"font-size:16px=
">&gt; features&quot;,</span><br style=3D"font-size:16px"><span style=3D"fo=
nt-size:16px">&gt; &quot;Features&quot; should be capitalized.</span><br st=
yle=3D"font-size:16px"><br>Will fix.</div><div><br><span style=3D"font-size=
:16px">&gt; * In Section 9.3 &quot;XDR Corrections to REQUIRED features&quo=
t;, the word</span><br style=3D"font-size:16px"><span style=3D"font-size:16=
px">&gt; &quot;correct&quot; should be &quot;corrected&quot; in the sentenc=
e &quot;Such clients would</span><br style=3D"font-size:16px"><span style=
=3D"font-size:16px">&gt; only</span><br style=3D"font-size:16px"><span styl=
e=3D"font-size:16px">&gt; be capable of interoperating with servers that su=
pported the correct</span><br style=3D"font-size:16px"><span style=3D"font-=
size:16px">&gt; version.&quot;</span><br></div><div><span style=3D"font-siz=
e:16px"><br></span></div><div><span style=3D"font-size:16px">Will fix.</spa=
n></div><div><div><div><span style=3D"font-size:16px"><br></span></div></di=
v></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On =
Fri, May 12, 2017 at 4:37 PM, Matthew Miller <span dir=3D"ltr">&lt;<a href=
=3D"mailto:linuxwolf+ietf@outer-planes.net" target=3D"_blank">linuxwolf+iet=
f@outer-planes.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
Reviewer: Matthew Miller<br>
Review result: Ready with Issues<br>
<br>
Document: draft-ietf-nfsv4-versioning-09<br>
IETF LC End Date: 2017-05-12<br>
IESG Telechat date: 2017-05-25<br>
<br>
This document provides guidance for dealing with extensions<br>
and versioning in NFSv4, including how and when to update<br>
minor versions.<br>
<br>
This document is mostly ready.=C2=A0 Some of the grammatical choices<br>
make for a more difficult read; the most obvious ones to me are<br>
nits below.<br>
<br>
Major issues:<br>
<br>
NONE<br>
<br>
Minor issues:<br>
<br>
NONE<br>
<br>
Nits/editorial comments:<br>
<br>
* For the bullet points in this document, some end in periods and<br>
some don&#39;t.=C2=A0 I recommend the authors choose one and update<br>
accordingly.<br>
<br>
* In section 1. &quot;Introduction&quot;, the last sentence is very clumsy.=
<br>
The Gen-ART review already points this out, and provides what I think<br>
is a good suggested change.<br>
<br>
* In section 4.4.2 &quot;Establishing Interoperability&quot;, the phrase<br=
>
&quot;client<br>
would uses&quot; should be &quot;client uses&quot;<br>
<br>
* In section 5.2 &quot;Behavioral Changes&quot;, the following sentence is<=
br>
difficult parse:<br>
<br>
=C2=A0 =C2=A0&quot;&quot;&quot;<br>
=C2=A0 =C2=A0One class of behavioral change involves changes in the set of<=
br>
errors<br>
=C2=A0 =C2=A0to be returned in the event of various errors.<br>
=C2=A0 =C2=A0&quot;&quot;&quot;<br>
<br>
I think the following has the same meaning:<br>
<br>
=C2=A0 =C2=A0&quot;&quot;&quot;<br>
=C2=A0 =C2=A0One class of behavior change involves changes in the set of er=
rors<br>
=C2=A0 =C2=A0to be returned when various failure conditions occur.<br>
=C2=A0 =C2=A0&quot;&quot;&quot;<br>
<br>
That&#39;s not tremendously better, but I think it&#39;s a little easier to=
<br>
wrap one&#39;s mind around.<br>
<br>
* In the title for Section 9.3 &quot;XDR Corrections to REQUIRED<br>
features&quot;,<br>
&quot;Features&quot; should be capitalized.<br>
<br>
* In Section 9.3 &quot;XDR Corrections to REQUIRED features&quot;, the word=
<br>
&quot;correct&quot; should be &quot;corrected&quot; in the sentence &quot;S=
uch clients would<br>
only<br>
be capable of interoperating with servers that supported the correct<br>
version.&quot;<br>
<br>
<br>
</blockquote></div><br></div>

--001a114417aa052965054f67c626--


From nobody Sun May 14 00:37:09 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 E404B129451; Sun, 14 May 2017 00:37:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 kk_3xS60Janc; Sun, 14 May 2017 00:37:03 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (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 982131200FC; Sun, 14 May 2017 00:35:46 -0700 (PDT)
Received: from [192.168.1.18] (unknown [124.189.96.43]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 7556722E255; Sun, 14 May 2017 03:35:40 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Last Call: <draft-nottingham-rfc5988bis-05.txt> (Web Linking) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <588716b3-161c-62ac-e5a9-a04c86f13e86@gmx.de>
Date: Sun, 14 May 2017 17:35:36 +1000
Cc: ietf@ietf.org, draft-nottingham-rfc5988bis@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <704BC987-1ED0-4E59-A803-0B4013A86F03@mnot.net>
References: <588716b3-161c-62ac-e5a9-a04c86f13e86@gmx.de>
To: "Julian F. Reschke" <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/okHdFc-VjH_jAUqLZJ_L5s6h5K4>
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, 14 May 2017 07:37:07 -0000

Thanks for the feedback, Julian. I've incorporated into source; =
responses below where necessary.


> On 12 May 2017, at 4:16 am, Julian Reschke <julian.reschke@gmx.de> =
wrote:
>=20
> Here's my feedback, mainly editorial nits...:
>=20
>   Additionally, the following rules are included from [RFC3986]: URI
>   and URI-Reference; from [RFC6838]: type-name and subtype-name; from
>   [W3C.CR-css3-mediaqueries-20090915]: media_query_list; and from
>   [RFC5646]: Language-Tag.
>=20
> That doesn't work, as "_" is not a legal ABNF character.
>=20
> 2.  Links
>=20
>   In this specification, a link is a typed connection between two
>   resources, and is comprised of:
>=20
>   o  A _link context_,
>=20
>   o  a _link relation type_ (Section 2.1),
>=20
>   o  a _link target_, and
>=20
>   o  optionally, _target attributes_ (Section 2.2).
>=20
> It might be good to add forward references for "link context" and =
"link target" as well.

Context and target are explained directly below the list; they don't =
have their own sections in the generic model.


>   Finally, links are consumed by _link applications_. Generally, an
>   application will define the link relation type(s) it uses, along =
with
>   the serialisation(s) that they might occur within.  For example, the
>   application "Web browsing" looks for the "stylesheet" link relation
>   type in the HTML link serialisation, whereas the application
>   "AtomPub" uses the "edit" and "edit-media" link relations.
>=20
> Actually, one popular browser also looks for the stylesheet link =
relation in the "Link" header field...

True, but that's not specified behaviour, AIUI.


>   Relation types are not to be confused with media types [RFC6838];
>=20
> Media types are defined in RFC 2046; RFC 6838 is mainly about media =
type registrations.
>=20
>   they do not identify the format of the representation that results
>   when the link is dereferenced.  Rather, they only describe how the
>   current context is related to another resource.
>=20
>   o  *Reference*: Reference to the document that specifies the link
>      relation type, preferably including a URI that can be used to
>      retrieve a copy of the document.  An indication of the relevant
>      section(s) MAY also be included, but is not required.
>=20
> s/MAY/can/
>=20
>   Note that relation types can be registered by third parties
>   (including the Expert(s)), if the Expert(s) determine that an
>   unregistered relation type is widely deployed and not likely to be
>   registered in a timely manner.
>=20
> maybe s/registered/registed otherwise/?

I did "...not likely to be registered in a timely manner otherwise."


> 2.1.1.2.  Registration Request Processing
>=20
>   Relation types are registered on the advice of a Designated Expert
>   (appointed by the IESG or their delegate), with a Specification
>   Required (using terminology from [RFC5226]).
>=20
> s/[RFC5226]/Section 4.1 of [RFC5226]/
>=20
>=20
> 2.2.  Target Attributes
>=20
>   This specification does not attempt to coordinate the name of target
>   attributes, their cardinality or use.  Serialisations SHOULD
>   coordinate their target attributes to avoid conflicts in semantics =
or
>   syntax.
>=20
> I'm not sure who's the audience for this SHOULD, and how to implement =
it. For instance, shouldn't this spec do this for the header field =
serialization?

The audience is people creating or maintaining serialisations; I've =
clarified the language.

The header field serialisation has, effectively; it was designed to be =
compatible with existing serialisations (HTML first, with Atom =
succeeding it, since Link pre-dated it, even though it wasn't =
specified).


> 3.  Link Serialisation in HTTP Headers
>=20
> s/Headers/Header fields/
>=20
>   This specification defines the link-params "rel", "anchor", "rev",
>   "hreflang", "media", "title", "title*", and "type"; see Section 3.2,
>   Section 3.3 and Section 3.4.
>=20
> s/Section 3.2, Section 3.3 and Section 3.4/Sections 3.2, 3.3, and 3.4/

That's hard to automate; I think we can fix that at the RFC editor =
stage.


> 3.1.  Link Target
>=20
>   Each link-value conveys one target IRI as a URI-Reference (after
>   conversion to one, if necessary; see [RFC3987], Section 3.1) inside
>   angle brackets ("<>").  If the URI-Reference is relative, parsers
>   MUST resolve it as per [RFC3986], Section 5.  Note that any base IRI
>   from the message's content is not applied.
>=20
> Maybe s/base IRI from the message's content/base IRI appearing inside =
the message's content/
>=20
> 3.2.  Link Context
>=20
>   By default, the context of a link conveyed in the Link header field
>   is identity of the representation it is associated with, as defined
>   in [RFC7231], Section 3.1.4.1, serialised as a URI.
>=20
> Broken sentence: "is identity".
>=20
>   The ABNF for the "anchor" parameter's value is:
>=20
>     URI-Reference
>=20
> s/URI-Reference/URI-Reference; Section 4.1 of [RFC3986]/
>=20
>   Note that depending on HTTP status code and response headers, the
>   link context might be "anonymous" (i.e., no link context is
>   available).  For example, this is the case on a 404 response to a =
GET
>   request.
>=20
> I understand this is identical in RFC 5988, but where does this =
actually come from? It basically restricts use of anchor-less link =
header fields 2xx responses, right?

<http://httpwg.org/specs/rfc7231.html#identifying.payload>, referenced =
just a few paragraphs earlier.


> 3.3.  Relation Type
>=20
>   The ABNF for the "rel" and "rev" parameters' values is:
>=20
>     relation-type *( 1*SP relation-type )
>=20
>   where:
>=20
>     relation-type  =3D reg-rel-type | ext-rel-type
>=20
> Finally I can use this link =
https://www.youtube.com/watch?v=3DLbK-g8tKnoc in LC feedback!

Source:
  https://github.com/mnot/I-D/issues/33#issuecomment-260825416

Do you have any further suggestions?


>     reg-rel-type   =3D LOALPHA *( LOALPHA | DIGIT | "." | "-" )
>     ext-rel-type   =3D URI
>=20
> s/URI/URI; Section 3 of [RFC3986]/
>=20
>   Note that extension relation types are REQUIRED to be absolute URIs
>   in Link headers, and MUST be quoted if they contain a semicolon =
(";")
>=20
> s/headers/header fields/
>=20
>   or comma (",") (as these characters are used as delimiters in the
>   header field itself).
>=20
> There are more characters legal in URIs but illegal in token -- so =
maybe phrasing it like this can cause confusion. Maybe "MUST be quoted =
when they contain characters not allowed in tokens, such as ...."?
>=20
> 3.4.1.  Serialisation-Defined Attributes
>=20
>   The ABNF for the "type" parameter's value is:
>=20
>     type-name "/" subtype-name
>=20
> (maybe point to https://tools.ietf.org/html/rfc6838#section-4.2 here)
>=20
> 3.5.  Link Header Field Examples
>=20
> Maybe add an example for multiple Link header field instances in a =
single message?
>=20
> 4.1.  Link HTTP Header Field Registration
>=20
>   Header field: Link
>   Applicable protocol: http
>   Status: standard
>   Author/change controller:
>       IETF  (iesg@ietf.org)
>       Internet Engineering Task Force
>   Specification document(s):
>       [RFC&rfc.number;]
>=20
> s/[RFC&rfc.number;]/this document/
>=20
>=20
> 4.2.  Link Relation Type Registry
>=20
>   Each published document will be at a URL mutually agreed to by IANA
>   and the Expert(s), and IANA will set HTTP response headers on them =
as
>   (reasonably) requested by the Expert(s).
>=20
> Wow. Does IANA know that we want to configure their web server?

We're talking about it. Data, metadata -- what's the difference?


> 5.  Security Considerations
>=20
>   Link applications ought to consider the attack vectors opened by
>   automatically following, trusting, or otherwise using links gathered
>   from HTTP headers.  In particular, Link header fields that use the
>=20
> s/headers/header fields/
>=20
>   "anchor" parameter to associate a link's context with another
>   resource are to be treated with due caution.
>=20
>   The Link header field makes extensive use of IRIs and URIs.  See
>   [RFC3987] for security considerations relating to IRIs.  See
>   [RFC3986] for security considerations relating to URIs.  See
>   [RFC7230] for security considerations relating to HTTP headers.
>=20
> s/headers/header fields/
>=20
> 7.1.  Normative References
>=20
>   [W3C.CR-css3-mediaqueries-20090915]
>              Lie, H., Celik, T., Glazman, D., and A. Kesteren, "Media
>              Queries", World Wide Web Consortium CR CR-css3-
>              mediaqueries-20090915, September 2009,
>              =
<http://www.w3.org/TR/2009/CR-css3-mediaqueries-20090915>.
>=20
> Need to update to =
<https://www.w3.org/TR/2012/REC-css3-mediaqueries-20120619/>.
>=20
>   [W3C.REC-html5-20141028]
>              Hickson, I., Berjon, R., Faulkner, S., Leithead, T.,
>              Navara, E., O&#039;Connor, T., and S. Pfeiffer, "HTML5",
>              World Wide Web Consortium Recommendation REC-
>              html5-20141028, October 2014,
>              <http://www.w3.org/TR/2014/REC-html5-20141028>.
>=20
> Broken escape in author name.

Hmm.


> A.1.  Link Serialisation in HTML
>=20
>   HTML5 ([W3C.REC-html5-20141028]) Section 4.8 defines modern HTML
>=20
> "Section 4.8 of HTML5"
>=20
>   links.  That document links to the Microformats Wiki as a registry;
>   over time, the IANA registry ought to mirror its contents, and
>   ideally eventually replace it (although that depends on the HTML
>   community).
>=20
>=20
> Appendix B.  Algorithm for Parsing Link Headers
>=20
>   Given a HTTP header field-value "field_value" as a string assuming
>   ASCII encoding, the following algorithm can be used to parse it into
>   the model described by this specification:
>=20
> This part is a bit scary -- I don't know how to review it. It might be =
better to have code in an actual programming language, and a set of =
tests for it.

That's not current practice for the intended audience, and shipping code =
makes it more likely that it will be used as a "reference =
implementation." This is marked as explicitly non-normative, and the =
precedence is clear.

It has been reviewed (and improved) by others, FWIW. If we find =
problems, we do have errata.


>   1.  Let "links" be an empty list.
>=20
>   2.  Create "link_strings" by splitting "field_value" on ","
>       characters, excepting "," characters within quoted strings as =
per
>=20
> I have my doubts that people will be able to translate it into =
actually correct code. To detect whether something is inside a =
quoted-string essentially requires running a parser; the prose here =
suggests that this is not necessary.

I reluctantly agree. I'll need to rework the algorithm to address this; =
please stand by.


> It also should mention that there might be multiple instances of =
field_value.

The algorithm is for parsing a single field-value...


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


From nobody Sun May 14 01:04:58 2017
Return-Path: <julian.reschke@gmx.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 4E92C128768; Sun, 14 May 2017 01:04:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.899
X-Spam-Level: 
X-Spam-Status: No, score=-4.899 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, RCVD_IN_SORBS_SPAM=0.5, 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 mE1GL6lDxOYU; Sun, 14 May 2017 01:04:55 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 DC64212944E; Sun, 14 May 2017 01:03:59 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.100.51]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LhOSG-1dnbIY2uem-00mYVL; Sun, 14 May 2017 10:03:54 +0200
Subject: Re: Last Call: <draft-nottingham-rfc5988bis-05.txt> (Web Linking) to Proposed Standard
To: Mark Nottingham <mnot@mnot.net>
References: <588716b3-161c-62ac-e5a9-a04c86f13e86@gmx.de> <704BC987-1ED0-4E59-A803-0B4013A86F03@mnot.net>
Cc: ietf@ietf.org, draft-nottingham-rfc5988bis@ietf.org
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <c81eb293-f443-8d61-bd82-b7c2902e4426@gmx.de>
Date: Sun, 14 May 2017 10:03:52 +0200
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: <704BC987-1ED0-4E59-A803-0B4013A86F03@mnot.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:yKkJGvdwQHZQnomle4+hA/Xln4lzMBT3g83h9spDBx+mo0tngY2 fV49Bf/BqVKdSvhzM9jHAqOqXLw2OeBeIHQ1bgZ81u2Ynql7JZwq9QqDB5RdSstwHPzQCAF /TYERozahhe8TaTCx0N481z3PDYhYwmO0CZ/8snn72TxaaFs5Cisjb3ufZWFTLN4WFKiNMR pppR6ignGHri2g/G16CYg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:jCqV7mctFQ8=:oitdA2SQJiVnFbuptlpt9m jaAFjNSFDJ6cd4A3tG4plZd7k2BzXwV3jNaEhtt+u+rZysAuotfDfgXY5wIigp9g2/fU7He9S WgVmV+EDd1Kdfek6/KXi5+xf+qGfv+N3Axdu8G/rcxEg2iW3n0nhm55UaSz2SG0ZRTYHXoK9W hgqMieoqOp50OJCvt18jKO2AZHLrG9u+Z2ovDdoW2j05THfNpAkP3e2hWBprce56LACye4rUr 2y/wdmfAvNsqj5bLx2K12ungBMMr+rYsr6F+GoPtaI6wJMX/UjTmZm04wN4XEvKBYy9ittUcR FuCxv0VGK4tUj81VXnEvr7UmjI0ZDP3ZpWbLXdB2CXwpTlfdHprgYNBSy8kJtecE1KBK1fUlK ux40na+lE2Z0ePejq+J22GZCxaf7ydxt0XZC71HvdGUATYHQR2R+RZ8YMxvDmpO9uSXzGoaX6 4mnKBtyp+I70rCpUv4Ap1JvxQQrQ+WSOjedWfAsrsAuQXaSTbKHQPwHxNEqC2G8a9nr64q0f8 Yl6g70lvZKk/2kkCufxv2gmb9BIA/9/Yn2eyI8gI6SceYBDqUmc1HQ1nn4ftt7lYre/oHktvR sVPPyW5KWx+5BvCtGuMroWqF/1XPfH/UdR9w0SiFLtxktfCXzLAtao/YcEQHe6HMy8MmR0M9F 6AB+Y/A+ZV0RThpchrW2d0f4/ZnSBhExrKxl/nJ3T7FYJsZdtMwnrS/J/wlLAPSBB3j/0EEjf 1wuQzvaUFk4j7GleoZqxjqK/o7uHFDePClwxe0GtIMbX7TgYY1R2WcoRJgP+bN/y02wH8vF21 eO/LKZy
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QfiqaCvS8AcH7DOLyH2Wqk5Yqbs>
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, 14 May 2017 08:04:57 -0000

On 2017-05-14 09:35, Mark Nottingham wrote:
> Thanks for the feedback, Julian. I've incorporated into source; responses below where necessary.
> ...
>> 2.  Links
>>
>>   In this specification, a link is a typed connection between two
>>   resources, and is comprised of:
>>
>>   o  A _link context_,
>>
>>   o  a _link relation type_ (Section 2.1),
>>
>>   o  a _link target_, and
>>
>>   o  optionally, _target attributes_ (Section 2.2).
>>
>> It might be good to add forward references for "link context" and "link target" as well.
>
> Context and target are explained directly below the list; they don't have their own sections in the generic model.

I was going to say: there are sub sections in Section 3 - but yes, they 
are specific to the header field...


>>   Finally, links are consumed by _link applications_. Generally, an
>>   application will define the link relation type(s) it uses, along with
>>   the serialisation(s) that they might occur within.  For example, the
>>   application "Web browsing" looks for the "stylesheet" link relation
>>   type in the HTML link serialisation, whereas the application
>>   "AtomPub" uses the "edit" and "edit-media" link relations.
>>
>> Actually, one popular browser also looks for the stylesheet link relation in the "Link" header field...
>
> True, but that's not specified behaviour, AIUI.

<https://www.w3.org/TR/html5/document-metadata.html#the-link-element>:

"HTTP Link: headers, if supported, must be assumed to come before any 
links in the document, in the order that they were given in the HTTP 
message. These headers are to be processed according to the rules given 
in the relevant specifications. [HTTP] [WEBLINK]"

So this refers to RFC 5988, which delegates to the IANA registry, which 
in turn points back to the HTML spec for the definition of the 
"stylesheet" link relation.

To me this sounds like it is well-defined, just not required ("if 
supported").

>> 3.  Link Serialisation in HTTP Headers
>>
>> s/Headers/Header fields/
>>
>>   This specification defines the link-params "rel", "anchor", "rev",
>>   "hreflang", "media", "title", "title*", and "type"; see Section 3.2,
>>   Section 3.3 and Section 3.4.
>>
>> s/Section 3.2, Section 3.3 and Section 3.4/Sections 3.2, 3.3, and 3.4/
>
> That's hard to automate; I think we can fix that at the RFC editor stage.

(hard to automate with markdown? :-)

>> 3.3.  Relation Type
>>
>>   The ABNF for the "rel" and "rev" parameters' values is:
>>
>>     relation-type *( 1*SP relation-type )
>>
>>   where:
>>
>>     relation-type  = reg-rel-type | ext-rel-type
>>
>> Finally I can use this link https://www.youtube.com/watch?v=LbK-g8tKnoc in LC feedback!
>
> Source:
>   https://github.com/mnot/I-D/issues/33#issuecomment-260825416
>
> Do you have any further suggestions?

Just added to the issue:

-    "_" is not legal in a production name
-    use "/" instead of "|"

>> 4.2.  Link Relation Type Registry
>>
>>   Each published document will be at a URL mutually agreed to by IANA
>>   and the Expert(s), and IANA will set HTTP response headers on them as
>>   (reasonably) requested by the Expert(s).
>>
>> Wow. Does IANA know that we want to configure their web server?
>
> We're talking about it. Data, metadata -- what's the difference?

Operationally?

>> Appendix B.  Algorithm for Parsing Link Headers
>>
>>   Given a HTTP header field-value "field_value" as a string assuming
>>   ASCII encoding, the following algorithm can be used to parse it into
>>   the model described by this specification:
>>
>> This part is a bit scary -- I don't know how to review it. It might be better to have code in an actual programming language, and a set of tests for it.
>
> That's not current practice for the intended audience, and shipping code makes it more likely that it will be used as a "reference implementation." This is marked as explicitly non-normative, and the precedence is clear.
>
> It has been reviewed (and improved) by others, FWIW. If we find problems, we do have errata.
>
>
>>   1.  Let "links" be an empty list.
>>
>>   2.  Create "link_strings" by splitting "field_value" on ","
>>       characters, excepting "," characters within quoted strings as per
>>
>> I have my doubts that people will be able to translate it into actually correct code. To detect whether something is inside a quoted-string essentially requires running a parser; the prose here suggests that this is not necessary.
>
> I reluctantly agree. I'll need to rework the algorithm to address this; please stand by.

The only way to properly split list supporting field values is to parse 
them according to the grammar for the list items; I don't believe in the 
existence of a shortcut that actually works correctly. Suggesting 
otherwise IMHO will lead to broken implementations for certain edge cases.

>> It also should mention that there might be multiple instances of field_value.
>
> The algorithm is for parsing a single field-value...

Yes, but should we tell the audience that they need to parse *all* field 
values, and combine the result?

Best regards, Julian


From nobody Sun May 14 01:46:02 2017
Return-Path: <j.schoenwaelder@jacobs-university.de>
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 0D73C126D73; Sun, 14 May 2017 01:46:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?b?SsO8cmdlbiBTY2jDtm53w6RsZGVy?= <j.schoenwaelder@jacobs-university.de>
To: <ops-dir@ietf.org>
Cc: ietf@ietf.org, draft-ietf-nfsv4-xattrs.all@ietf.org, nfsv4@ietf.org
Subject: Opsdir last call review of draft-ietf-nfsv4-xattrs-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149475155989.2899.8921343359746045233@ietfa.amsl.com>
Date: Sun, 14 May 2017 01:45:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iCyMCQXLgspiArKUD4RnVHNjxUo>
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, 14 May 2017 08:46:00 -0000

Reviewer: Jürgen Schönwälder
Review result: Ready

This was a nice read, a very well written document. I do not see any
operational issues for the Internet resulting from this
specification.
The functionality provided seems to be desirable.

I was a bit surprised to see that numeric values for NFSv4 protocol
extensions etc appear to be somewhat magically managed (section 8.6)
instead of using IANA but this likely has its own history and
reasons.



From nobody Sun May 14 02:16:20 2017
Return-Path: <j.schoenwaelder@jacobs-university.de>
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 4D94B1292D3; Sun, 14 May 2017 02:16:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?b?SsO8cmdlbiBTY2jDtm53w6RsZGVy?= <j.schoenwaelder@jacobs-university.de>
To: <ops-dir@ietf.org>
Cc: mpls@ietf.org, draft-ietf-mpls-tp-aps-updates.all@ietf.org, ietf@ietf.org
Subject: Opsdir last call review of draft-ietf-mpls-tp-aps-updates-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149475337228.2843.4160391987888372254@ietfa.amsl.com>
Date: Sun, 14 May 2017 02:16:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ahhbZsJg5n03jpa6PQoO7yHmFQE>
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, 14 May 2017 09:16:12 -0000

Reviewer: Jürgen Schönwälder
Review result: Ready

The document is about the changes it suggests. Not being an MPLS
geek,
I can't judge the details. That said, from an operational point of
view, fixing ambiguities in specifications is usually a very good
thing.



From nobody Sun May 14 07:24:53 2017
Return-Path: <julian.reschke@gmx.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 4618812932A; Sun, 14 May 2017 07:24:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.899
X-Spam-Level: 
X-Spam-Status: No, score=-4.899 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, RCVD_IN_SORBS_SPAM=0.5, 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 WDFZQ9KGF3LD; Sun, 14 May 2017 07:24:42 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.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 79F961201FA; Sun, 14 May 2017 07:23:57 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.100.51]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M8eAd-1dxDjM0yvL-00wB2G; Sun, 14 May 2017 16:23:55 +0200
To: IETF Discussion <ietf@ietf.org>, art@ietf.org
From: Julian Reschke <julian.reschke@gmx.de>
Subject: ART Area Review for draft-ietf-calext-caldav-attachments-02
Message-ID: <c04f39e2-79d2-ab9d-59ab-26e51d7ab5fc@gmx.de>
Date: Sun, 14 May 2017 16:23:52 +0200
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; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:q1Dk5fbzBRKSa9CB+rFw6/JTwk9Td0BAfmilJFWL9t0cQG4wHhQ M2uOx/6K+uglFCdsSehCJlH/DbScGIQzuJ02GFSDME7GURy7GGFYnTMORio+UoegdupLieJ PWOP5gunn5l0pg7oB7UJnUldjxVcSyjSjFF3R34wZ6j6wy6vdWGoenWVJgaKb3iZTZKe5zv MAjwQUbqlA8j0Pdmyb0Zw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:Mz0PWO78b0g=:0uvJQyjeK6lyx65QF3x9gl BOhjR7pNQOUlJ5lhj7aBHdaTvv8m8sqotLS2hKNrMhjtu8leeBlBxOJzcXnUNdmKByCx7FLsb 6xaXJWukjylIn5fp7H3qaELAaknOKeg1JgmsRHVVxMe5PkNibsOPXtMXkt/rZmBGEoWweQjc4 XgnbDwtcSTTh/52NyPMSBWEmeqcL+5pOKdPCo8zfY9ersQSdgrP/EbnrqwSL8NMAWoPPEgkH3 VN9jsZno4uM5U67OulUWzWmyJEOMuH6Bo5XVGEZEkkcRS3ywwHNdi3pPg19xbzxq2I9UhvnKv et5VkE1V1eEEmLFffJlmIRVOty2BJOuIhke1lW0siHi0POBiu7ByLQ2L/xAtPeoUB/1++P/iJ fWpJy1tJMSqemxgkMF2wDlRh6VDEHEUZzkjNF5Z+qqrSl5V/6Nl2IvXUP3HVisIuZmLrJaLO+ T/vS9303LK9mW9TFMcZW1Pz5ooKJ8QHbrMg5DTCpN7PGi1ByzLgJkvlMabAWqar2JKaL1/PDe pED2HF7hv828e1Wjo1T4G8oTyvSdzrtHsoxFw64J4kxY2MtsUCq+00s3v8xJNi3knirMPC1cb W3022/gsOgLF76bAgm6E8+SjFkCO2yooc0ui97h8mLRTtUAQ2WRXyumYQTnPwUMs2ebNuu+kk 0j0IRjKANIX1QB534edHfk26JrRCsl5KyaZn2/jfDsYonhnh9zOWadduBSxhkkmrbgG4R0a3x QTuSgrFgHFufUOhhuAvBJOs7y1rOqMjjGn/rI91GTSc7v+lJxBG14gngJKGhoQ3+09qQWo6Ow DOy/R2X
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nFZaTVv5rxdtPRbrFH2BOSQtPiM>
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, 14 May 2017 14:24:44 -0000

Reviewer: Julian Reschke
Review result: Not Ready

Document: draft-ietf-calext-caldav-attachments-02
IETF LC End Date: 2017-05-14
IESG Telechat date: 2017-05-25

This document describes attachment handling in CalDAV (WebDAV based 
calendaring).

The mechanism described by this document is essential RPCish, using HTTP 
POST for tunneling. It will work in practice, but it definitively isn't 
state of the art in IETF protocols, in particular in an otherwise 
WebDAV/CalDAV-based ecosystem.

Major issues:

The main issue with this specification is that it

1) models operations on attachments as POST operations, where the actual 
type of operation is specified using a query parameter, instead of using 
the HTTP methods POST, PUT, and DELETE.

2) hardwires specific query strings into the protocol, violating a MUST 
level requirement in BCP 190 (see 
https://tools.ietf.org/html/rfc7320#section-2.4):

    Applications MUST NOT directly specify the syntax of queries, as this
    can cause operational difficulties for deployments that do not
    support a particular form of a query.  For example, a site may wish
    to support an application using "static" files that do not support
    query parameters.

Re 1) this is even called out specifically in Sections 3.8 (update) and 
3.9 (remove), but it's not clear at all why that is the case.

Re 2) Part of the hard-wiring could be avoided by using different HTTP 
methods for the different actions. The other parameters could be made 
discoverable using URIs / URI templates, exposed as WebDAV properties, 
as is the case in RFC 5995.


5.1.  Cal-Managed-ID Response Header Field

This doesn't seem to address the points listed in 
<https://greenbytes.de/tech/webdav/rfc7231.html#considerations.for.new.header.fields> 
(and it wouldn't be needed if the attachment would be modeled as an HTTP 
resource whose values could be reported back in a Location header field 
upon creation).

Minor issues:

3.12.4.  Processing Time

    Clients can expect servers to take a while to respond to POST
    requests that include large attachment bodies.  Servers SHOULD use
    the "102 (Processing)" interim response defined in Section 10.1 of
    [RFC2518] to keep the client connection alive if the POST request
    will take significant time to complete.

While discussing the new code 103 in the HTTP WG, we considered interop 
problems with existing code that doesn't handle 1xx status codes at all, 
or had problems with status codes other than 100. I personally support 
use of new 1xx status codes, but it would be good to hear whether the WG 
considered deployment problems when making this a SHOULD-level requirement.

3.12.5.  Automatic Clean-up by servers

    Servers MAY automatically remove attachment data, for example to
    regain the storage taken by unused attachments, or as the result of a
    virus scanning.  When doing so they SHOULD NOT modify calendar data
    referencing those attachments.  Instead they SHOULD respond with "410
    (Gone)" to any request on the removed attachment URI.

This essentially requires servers to distinguish between resources that 
never have been there, and those which have been there but were removed. 
It's definitively additional work for the server, where it's not clear 
what the benefit for clients is.

6.1.  CALDAV:managed-attachments-server-URL property

This mechanism is really funky. Depending on the presence of this 
property, the authority part of attachment URIs is rewritten or not. 
Depending on its contents, the rewrite is based on yet another default 
or the given value.

It's not clear why all this can't be replaced by a mechanism where 
attachment URIs can be relative references to be resolved against a base 
URI.


Nits/editorial comments:

    In addition, such a server MUST support the "return=representation"
    Prefer header field value [RFC7240] on successful HTTP PUT and POST
    requests targeting existing calendar object resources, by returning
    the new representation of that calendar resource (including its new
    ETag header field value) in the response.

(not specific to this spec, but to the CalDAV ecosystem: the specs rely 
a lot on DAV feature names, but there's no registry - I believe it would 
be good if we added one in a separate spec)

1.  Introduction

    The iCalendar [RFC5545] data format is used to represent calendar
    data and is used with iTIP [RFC5546] to handle scheduling operations
    between calendar users.

    [RFC4791] defines the CalDAV Calendar Access protocol, based on HTTP
    [RFC7230], for accessing calendar data stored on a server.

Maybe also mention RFC 4918 here. RFC 4918 currently isn't referenced at 
all, despite the fact that the specification relies on stuff defined 
over there, such as the "DAV" response header field.



From nobody Sun May 14 10:03:38 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 27AB5120726 for <ietf@ietfa.amsl.com>; Sun, 14 May 2017 10:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.52
X-Spam-Level: 
X-Spam-Status: No, score=-1.52 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 2oSNk1sCZMmr for <ietf@ietfa.amsl.com>; Sun, 14 May 2017 10:03:35 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.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 8433B129AE0 for <ietf@ietf.org>; Sun, 14 May 2017 10:01:30 -0700 (PDT)
X-AuditID: c1b4fb2d-b25ff7000000196b-ed-59188d67fcbd
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id F0.C1.06507.76D88195; Sun, 14 May 2017 19:01:28 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.104]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0339.000; Sun, 14 May 2017 19:01:27 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Mehmet Ersue <mersue@gmail.com>, 'John Levine' <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: IETF #100 Hotel Rate
Thread-Topic: IETF #100 Hotel Rate
Thread-Index: AQGODeFiUhNaXCmtjMiThoVgxtasTgGODeFiAXnT95YCE3P7QKJRFmkAgAOab/A=
Date: Sun, 14 May 2017 17:01:26 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4CBA1A5E@ESESSMB109.ericsson.se>
References: <012d01d2c999$d7adda40$87098ec0$@gmail.com><012d01d2c999$d7adda40$87098ec0$@gmail.com> <51f9d3d1-6c5c-102d-d76d-ea0d35433921@gih.com> <oevgrk$ms6$1@gal.iecc.com> <008301d2cb06$cc9736b0$65c5a410$@gmail.com>
In-Reply-To: <008301d2cb06$cc9736b0$65c5a410$@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrGLMWRmVeSWpSXmKPExsUyM2K7t25Gr0SkwYuX2hbPNs5nsTjds4bJ on3eUyYHZo+ds+6yeyxZ8pPJ496W0ADmKC6blNSczLLUIn27BK6MFX/fsRZc4a7ofruZsYFx D2cXIweHhICJxP/1Wl2MXBxCAkcYJe5+m8sC4SxhlHh1fxoLSBGbgIVE9z9tEFNEIF3id3MJ iCksoCjxcKNXFyMnUFRJ4vnCA8wQtp/Eo/ab7CA2i4CqxInVixlBbF4BX4nGNzdZIabfZZTo 3DmDGWQOJ9D0pqUsIDWMAmIS30+tYQKxmQXEJW49mQ9mSwgISCzZc54ZwhaVePn4HyuErSTR uOQJK0S9nsSNqVPYIGxtiWULXzND7BWUODnzCcsERpFZSMbOQtIyC0nLLCQtCxhZVjGKFqcW F+emGxnrpRZlJhcX5+fp5aWWbGIExsbBLb91dzCufu14iFGAg1GJh/dBo3ikEGtiWXFl7iFG CQ5mJRFe7TKJSCHelMTKqtSi/Pii0pzU4kOM0hwsSuK8DvsuRAgJpCeWpGanphakFsFkmTg4 pRoYnZ/x2NUzGCZee7NZ7XT73bRWDy7tXwqncpWrZ9+syj14Xu/LCpc/X+9sXMJq9+26uVe4 +vTZLT4n/zVEWDf+1LQ7a1ljlWesuLavd+qmxyk9d7N2ay83W8LyKNJnilbhq+dub19pnMtn 7tmw81FmxbNlyl/EO/Yd2KPRZLBnjc/yzXy572eoKLEUZyQaajEXFScCAEHEuEqJAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/armdpL7bUeEa57b5lTY9nDY9uxk>
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, 14 May 2017 17:03:37 -0000

Where does it say that Raffles is the main hotel???

Regards,

Christer

-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Mehmet Ersue
Sent: 12 May 2017 12:02
To: 'John Levine' <johnl@taugh.com>; ietf@ietf.org
Subject: RE: IETF #100 Hotel Rate

It's good there are options.
However, the meeting page indicates that Raffles is the main hotel.

https://www.ietf.org/meeting/100/index.html

Mehmet

> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of John Levine
> Sent: Wednesday, May 10, 2017 6:58 PM
> To: ietf@ietf.org
> Subject: Re: IETF #100 Hotel Rate
>=20
> In article <51f9d3d1-6c5c-102d-d76d-ea0d35433921@gih.com>,
> Olivier MJ Cr=C3=A9pin-Leblond <ocl@gih.com> wrote:
> >-=3D-=3D-=3D-=3D-=3D-
> >Unlikely to be the Raffles hotel itself. I guess the conference is at=20
> >the Raffles City convention centre which has 2 hotels: the Fairmont &=20
> >the Swisshotel. Rates are lower than the super luxurious Raffles=20
> >itself, which is just across the road.
>=20
> Right, that's where ICANN met a few years ago.  The Fairmont and=20
> Swissotel are directly connected to the conference centre.  I don't=20
> recall what the
rates
> were but they weren't out of line with other Fairmont and Swissotels=20
> where we've met.
>=20
> I do recommend making the trip across the road to Long's Bar in the
Raffles
> hotel for the original Singapore Sling.
>=20
> R's,
> John



From nobody Sun May 14 10:06:38 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 8CA44129484 for <ietf@ietfa.amsl.com>; Sun, 14 May 2017 10:06:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.48
X-Spam-Level: *
X-Spam-Status: No, score=1.48 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=HKCg2dhK; dkim=pass (1536-bit key) header.d=taugh.com header.b=LqkOdOQq
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T6CD8U9f-u_J for <ietf@ietfa.amsl.com>; Sun, 14 May 2017 10:06:35 -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 7926612422F for <ietf@ietf.org>; Sun, 14 May 2017 10:04:19 -0700 (PDT)
Received: (qmail 58285 invoked from network); 14 May 2017 17:04:18 -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=e3ab.59188e12.k1705; bh=ELsMo3WoEjNJusQz8Cl5LP1D8NPfOdzq2yPVF9fht5Y=; b=HKCg2dhK9vDb2fafhfjcBUTZfr3dDt9+VUsbNXpZxRsZH854S3H9A6YHbCmljuAV1p7D4SEzno/yCbaYCzlvbdLHpy+pj9cgKRRHoIHGPuaHR4gZniW6VEKAxxT3vIFxHdDGH110GAhL9KEjMC507kcEPPx3v95QvYTKFaY5YvkBfYjuDFh6k9TsRXl2OkyJcKcHMHWskLfNiHuRd6hh6Z8kn94C8qi7eLiOF00vf+dp4OvO0pqxo6JLEogTJOoA
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=e3ab.59188e12.k1705; bh=ELsMo3WoEjNJusQz8Cl5LP1D8NPfOdzq2yPVF9fht5Y=; b=LqkOdOQqezw209Bz6iCI5qsS2efiWV9Aml/v7sYQ8I/7aEWgaYvbaU3q5YSCNjZBmT19MQIUDN/FbH5H/3eq7cd3kwVzTRK6RATBVcP8wzxVOM1E2FqPfCxmYRNQh1WNN1pDY+aBmzqieBD02Kvst8s4/+F5rd9i168xGzjR2a1rvCX7UAjLHM2D+44fpodgv8qTlj+PLBFu4r47G8qabYlppYQ7/eXHnpPckmsNpqcJO93Vv+CQlX+jPxS1+spD
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; 14 May 2017 17:04:18 -0000
Date: 14 May 2017 13:04:17 -0400
Message-ID: <alpine.OSX.2.21.1705141303300.53967@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: IETF #100 Hotel Rate
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4CBA1A5E@ESESSMB109.ericsson.se>
References: <012d01d2c999$d7adda40$87098ec0$@gmail.com><012d01d2c999$d7adda40$87098ec0$@gmail.com> <51f9d3d1-6c5c-102d-d76d-ea0d35433921@gih.com> <oevgrk$ms6$1@gal.iecc.com> <008301d2cb06$cc9736b0$65c5a410$@gmail.com> <7594FB04B1934943A5C02806D1A2204B4CBA1A5E@ESESSMB109.ericsson.se>
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/RMKOP4we-48lX54qxOFKOGthNzQ>
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, 14 May 2017 17:06:36 -0000

> Where does it say that Raffles is the main hotel???

It doesn't any more.  They fixed it to refer to the convention centre 
acress the street.

> https://www.ietf.org/meeting/100/index.html

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Sun May 14 18:47:02 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 4576D12E040; Sun, 14 May 2017 18:47:00 -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=mHzHIU0X; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=q8KPJeqZ
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YBidALcD0VUs; Sun, 14 May 2017 18:46:57 -0700 (PDT)
Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1071212E045; Sun, 14 May 2017 18:42:40 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.nyi.internal (Postfix) with ESMTP id 15C5E8E4; Sun, 14 May 2017 21:42:39 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Sun, 14 May 2017 21:42:39 -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=sOLNk8R1rrCdhD9/D3 Sw3Y76U2WrL3UAaco3orraFZo=; b=mHzHIU0XWm+Ia4iOtCQ61n1L2gr8lJN2jW 6E3hpY/ExZNjHdU9Ah9oUz8OireMiQj34Z0RYTMHDCaSkf7pHovgnqISc1K5yxq6 k+C7gIeYXhPA0WV7Mv47eiuIFNkdPKLOwYqTZFpXlfKmcb8kMXs0O5XDkgT6D/UH MOErWlj/ROBu2gtYULQuxdnUM6SvSoBIwSLbMv8m8rieqyhbXVznZ7Alko4UAX4i iWrIOWp4M7TJ4nuPL+0DmuMbZemrs9mAGftFDstBEBhzVtu2IQi7EdoFi+54ltWG RDf3yOJz27nHM12LNrx6dRnDb8IkME9Mw1kKXsmtWnCPrUXndqIQ==
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=sOLNk8R1rrCdhD9/D3Sw3Y76U2WrL3UAaco3orraFZo=; b=q8KPJeqZ /0XH9P8cSnAvUox7VoEGqQ03D7ErgSqZnahL58zW47mxHvVCNByCooaxMIqY2Xc/ ftXzFaC+JHJ63sIVkoUuPi1Jpgv10/v3zaaJbS5c4l/e4nVVZAbyBV1fKi2oGGdA uL87oAJvkdzC+XOQ7Z85FGwmuf2VvNqBqtvhY3/+5/LsSNGDRG7RuMNnnh27b9fq NdZcJ6RsXokLfzJejSfdlHigHRZzQxaf424/ZeEwQu6O08Wv7oe+HvSui/dGnoLx w4BvCZK7WfPKueH8ZHyMvO+zopT1bGnpO37A5GYr2MUrZRwuEglYWFFBQpRt2Awr iSnBXDmy+SCTiw==
X-ME-Sender: <xms:jgcZWa40qogTm0lI0QawXGpGAOOWMFDEBXl444cdGBuhm6aD9tt3Aw>
X-Sasl-enc: CBzn4QSIwxRatH8e2uNKZxrRDKzOp6t9fWZJa9E3lARd 1494812558
Received: from [192.168.1.18] (cpe-124-189-96-43.gziz1.win.bigpond.net.au [124.189.96.43]) by mail.messagingengine.com (Postfix) with ESMTPA id 8F043241E3; Sun, 14 May 2017 21:42:37 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Last Call: <draft-nottingham-rfc5988bis-05.txt> (Web Linking) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <c81eb293-f443-8d61-bd82-b7c2902e4426@gmx.de>
Date: Mon, 15 May 2017 11:42:34 +1000
Cc: ietf@ietf.org, draft-nottingham-rfc5988bis@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <09EA3303-8F65-4FDE-8303-8C2AD9B8B897@mnot.net>
References: <588716b3-161c-62ac-e5a9-a04c86f13e86@gmx.de> <704BC987-1ED0-4E59-A803-0B4013A86F03@mnot.net> <c81eb293-f443-8d61-bd82-b7c2902e4426@gmx.de>
To: "Julian F. Reschke" <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/01w6MddWQRs9bJ3-fGUyb0yGhEw>
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, 15 May 2017 01:47:00 -0000

On 14 May 2017, at 6:03 pm, Julian Reschke <julian.reschke@gmx.de> =
wrote:

>>> Actually, one popular browser also looks for the stylesheet link =
relation in the "Link" header field...
>>=20
>> True, but that's not specified behaviour, AIUI.
>=20
> <https://www.w3.org/TR/html5/document-metadata.html#the-link-element>:
>=20
> "HTTP Link: headers, if supported, must be assumed to come before any =
links in the document, in the order that they were given in the HTTP =
message. These headers are to be processed according to the rules given =
in the relevant specifications. [HTTP] [WEBLINK]"
>=20
> So this refers to RFC 5988, which delegates to the IANA registry, =
which in turn points back to the HTML spec for the definition of the =
"stylesheet" link relation.
>=20
> To me this sounds like it is well-defined, just not required ("if =
supported").

https://github.com/mnot/I-D/commit/8e3d4c5167e


> Just added to the issue:
>=20
> -    "_" is not legal in a production name
> -    use "/" instead of "|"

Now in the repo, thanks.


>>> 4.2.  Link Relation Type Registry
>>>=20
>>>  Each published document will be at a URL mutually agreed to by IANA
>>>  and the Expert(s), and IANA will set HTTP response headers on them =
as
>>>  (reasonably) requested by the Expert(s).
>>>=20
>>> Wow. Does IANA know that we want to configure their web server?
>>=20
>> We're talking about it. Data, metadata -- what's the difference?
>=20
> Operationally?

We'll see.=20


>>>  1.  Let "links" be an empty list.
>>>=20
>>>  2.  Create "link_strings" by splitting "field_value" on ","
>>>      characters, excepting "," characters within quoted strings as =
per
>>>=20
>>> I have my doubts that people will be able to translate it into =
actually correct code. To detect whether something is inside a =
quoted-string essentially requires running a parser; the prose here =
suggests that this is not necessary.
>>=20
>> I reluctantly agree. I'll need to rework the algorithm to address =
this; please stand by.
>=20
> The only way to properly split list supporting field values is to =
parse them according to the grammar for the list items; I don't believe =
in the existence of a shortcut that actually works correctly. Suggesting =
otherwise IMHO will lead to broken implementations for certain edge =
cases.

+1


>>> It also should mention that there might be multiple instances of =
field_value.
>>=20
>> The algorithm is for parsing a single field-value...
>=20
> Yes, but should we tell the audience that they need to parse *all* =
field values, and combine the result?

OK.


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


From nobody Sun May 14 18:57:38 2017
Return-Path: <sboutros@vmware.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 2F323129B5B; Sun, 14 May 2017 18:57:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.702
X-Spam-Level: 
X-Spam-Status: No, score=-4.702 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_H2=-2.8, SPF_HELO_PASS=-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=onevmw.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 4dZWZuSqtkRz; Sun, 14 May 2017 18:57:19 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0089.outbound.protection.outlook.com [104.47.38.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9CEA129AE5; Sun, 14 May 2017 18:52:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=onevmw.onmicrosoft.com; s=selector1-vmware-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=RWOk1xYyiOJTKiW0py0XDOer/LoE+XRhQE+QDGyTE40=; b=l7IiM/5jcKT7FgKZzy8V4MS3HYD7JUfMPcs/p7Y6l6Sp8a86aO2jIy2aX30Dc2VVTrFi0wyAv/2Ov2+kMxKUF47WRPhqbPsAiVqZBaiQmgByXsaaaPfhfIEPNFc1kNyVDNC8gYpA4sYiU2PHOAJtlLaySvJGPboBgMRa0eXNJhA=
Received: from BN6PR05MB3009.namprd05.prod.outlook.com (10.173.19.15) by BN6PR05MB3011.namprd05.prod.outlook.com (10.173.19.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1101.8; Mon, 15 May 2017 01:52:58 +0000
Received: from BN6PR05MB3009.namprd05.prod.outlook.com ([10.173.19.15]) by BN6PR05MB3009.namprd05.prod.outlook.com ([10.173.19.15]) with mapi id 15.01.1101.011; Mon, 15 May 2017 01:52:58 +0000
From: Sami Boutros <sboutros@vmware.com>
To: Min Ye <amy.yemin@huawei.com>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "Patrice Brissette (pbrisset)" <pbrisset@cisco.com>
CC: "draft-ietf-pals-p2mp-pw.all@ietf.org" <draft-ietf-pals-p2mp-pw.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "pals@ietf.org" <pals@ietf.org>
Subject: Re: Rtgdir last call review of draft-ietf-pals-p2mp-pw-02
Thread-Topic: Rtgdir last call review of draft-ietf-pals-p2mp-pw-02
Thread-Index: AQHSyfQORpr0WT3BYUyvZqID9K0TvaH0MrUA
Date: Mon, 15 May 2017 01:52:57 +0000
Message-ID: <89E173B8-3C03-4B4A-A405-F0442B983D7F@vmware.com>
References: <149446531632.16715.2861233468294466753@ietfa.amsl.com>
In-Reply-To: <149446531632.16715.2861233468294466753@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;huawei.com; dmarc=none action=none header.from=vmware.com;
x-originating-ip: [2601:642:4400:5082:1cdd:82eb:534a:fbec]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR05MB3011; 7:Cwhl6bfeuBZiw2iWhzrUBpJXJt5lWch0JWX7OGo1uFRNyxt1mmNKqdm7+zkjTgP89G+6gUGrM6BgJxEJAHI468kLI5U5Du2bBISfk66MK2HsGbl4jJjCdTI9AiQfESf9Bmmc+v0Pz/DNkhtbFpo8zblG280qiAYbxa73cNwK1s3hi5WqTYBtmn7quKnDlbvbI9sy+NjXCaJjxLSNj3w/gooHaF1gv4jfXAGTjC3HMruToEVZsZofQ6PN6DDFp3wlY5gM19vWB/dpFF+xzG4GIYNrodlaPchKcAamcKijLCKxPOVGhvpmczLnenEnLHDRBz5ss7e9qtocKjzdMiwkHw==; 20:s1WuyayNkDgqzdcC2BBwM4TlOJufxpx+slH/BcmUm+uGzm7hpA3eFD6OePzX8otzhNErkNaDVcU1q37VOk4HRHgtlsurbI0xvBFpOiemcShZRGRZDXXMy0xsLjboz7csZVVjpAkbXYZIMAU+/bCsQmUSUtIs6HIHYY1TJvnIGwc=
x-ms-traffictypediagnostic: BN6PR05MB3011:
x-ms-office365-filtering-correlation-id: abac2988-a78e-4a7b-19a4-08d49b351c9a
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081); SRVR:BN6PR05MB3011; 
x-microsoft-antispam-prvs: <BN6PR05MB30111E7088EA7AC91815406BBEE10@BN6PR05MB3011.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(10436049006162)(50582790962513);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(3002001)(93006095)(93001095)(10201501046)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(20161123555025)(20161123562025)(20161123558100)(20161123560025)(6072148); SRVR:BN6PR05MB3011; BCL:0; PCL:0; RULEID:; SRVR:BN6PR05MB3011; 
x-forefront-prvs: 0308EE423E
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39840400002)(39410400002)(39400400002)(39850400002)(39450400003)(24454002)(37854004)(377454003)(6306002)(122556002)(6512007)(2906002)(189998001)(99286003)(54906002)(478600001)(230783001)(4326008)(38730400002)(6246003)(5660300001)(50986999)(76176999)(54356999)(6116002)(53936002)(102836003)(77096006)(83716003)(7736002)(6506006)(6436002)(8936002)(81166006)(6486002)(33656002)(36756003)(305945005)(82746002)(8676002)(86362001)(2501003)(2900100001)(25786009)(575784001)(3280700002)(2950100002)(3660700001)(53546009); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR05MB3011; H:BN6PR05MB3009.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <EA9BF094B040DA49B8C4F4781DD3D7D7@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: vmware.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 May 2017 01:52:57.9624 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: b39138ca-3cee-4b4a-a4d6-cd83d9dd62f0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR05MB3011
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2R9_Ias_i0LcCF5EPjd5W1gnWYU>
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, 15 May 2017 01:57:22 -0000

SGkgUGF0cmljZSwNCg0KVGhhbmtzIGZvciByZXZpZXdpbmcgdGhlIGRyYWZ0Lg0KDQpQbGVhc2Ug
c2VlIGNvbW1lbnRzIGlubGluZS4NCg0KDQpPbiA1LzEwLzE3LCA2OjE1IFBNLCAiTWluIFllIiA8
YW15LnllbWluQGh1YXdlaS5jb20+IHdyb3RlOg0KDQo+UmV2aWV3ZXI6IFBhdHJpY2UgQnJpc3Nl
dHRlDQo+UmV2aWV3IHJlc3VsdDogSGFzIElzc3Vlcw0KPg0KPltSZXNlbmRpbmcgdG8gUlRHLURJ
Ul0NCj4NCj5IZWxsbywgDQo+SSBoYXZlIGJlZW4gc2VsZWN0ZWQgYXMgdGhlIFJvdXRpbmcgRGly
ZWN0b3JhdGUgcmV2aWV3ZXIgZm9yIHRoaXMNCj5kcmFmdC4gVGhlIFJvdXRpbmcgRGlyZWN0b3Jh
dGUgc2Vla3MgdG8gcmV2aWV3IGFsbCByb3V0aW5nIG9yDQo+cm91dGluZy1yZWxhdGVkIGRyYWZ0
cyBhcyB0aGV5IHBhc3MgdGhyb3VnaCBJRVRGIGxhc3QgY2FsbCBhbmQgSUVTRw0KPnJldmlldywg
YW5kIHNvbWV0aW1lcyBvbiBzcGVjaWFsIHJlcXVlc3QuIFRoZSBwdXJwb3NlIG9mIHRoZSByZXZp
ZXcgaXMNCj50byBwcm92aWRlIGFzc2lzdGFuY2UgdG8gdGhlIFJvdXRpbmcgQURzLiBGb3IgbW9y
ZSBpbmZvcm1hdGlvbiBhYm91dA0KPnRoZSBSb3V0aW5nIERpcmVjdG9yYXRlLCBwbGVhc2Ugc2Vl
DQo+aHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91PWh0dHAtM0FfX3Ry
YWMudG9vbHMuaWV0Zi5vcmdfYXJlYV9ydGdfdHJhY193aWtpX1J0Z0RpciZkPUR3SURhUSZjPXVp
bGFLOTBENFRPVm9INThKTlhSZ1Emcj1JVnpjVFJMUWRwdGEwOEwwYl95MnpEa3F2d0poUktNQ0Fi
WC0ySy1MVjk4Jm09TVdJWGZlN0VfZ0Z3V1pGcnNWUHBOVGE2RVFpbUNHRngtRzNzSWpNTGJNZyZz
PXRBM051bVFFUkhFUnVZRFlBMENDcHJxMzZfX01IR0xmWlUzRThZeXB2VmcmZT0gIA0KPkFsdGhv
dWdoIHRoZXNlIGNvbW1lbnRzIGFyZSBwcmltYXJpbHkgZm9yIHRoZSB1c2Ugb2YgdGhlIFJvdXRp
bmcgQURzLA0KPml0IHdvdWxkIGJlIGhlbHBmdWwgaWYgeW91IGNvdWxkIGNvbnNpZGVyIHRoZW0g
YWxvbmcgd2l0aCBhbnkgb3RoZXINCj5JRVRGIExhc3QgQ2FsbCBjb21tZW50cyB0aGF0IHlvdSBy
ZWNlaXZlLCBhbmQgc3RyaXZlIHRvIHJlc29sdmUgdGhlbQ0KPnRocm91Z2ggZGlzY3Vzc2lvbiBv
ciBieSB1cGRhdGluZyB0aGUgZHJhZnQuIA0KPiANCj5Eb2N1bWVudDogZHJhZnQtaWV0Zi1wYWxz
LXAybXAtcHctMDIudHh0DQo+UmV2aWV3ZXI6IFBhdHJpY2UgQnJpc3NldHRlDQo+UmV2aWV3IERh
dGU6IE1heSAxMCwgMjAxNw0KPklFVEYgTEMgRW5kIERhdGU6IE1heSAxMiwgMjAxNw0KPkludGVu
ZGVkIFN0YXR1czogU3RhbmRhcmQgVHJhY2sgDQo+U3VtbWFyeTogDQo+4oCiCUkgaGF2ZSBzb21l
IG1pbm9yIGNvbmNlcm5zIGFib3V0IHRoaXMgZG9jdW1lbnQgdGhhdCBJIHRoaW5rIHNob3VsZA0K
PmJlIHJlc29sdmVkIGJlZm9yZSBwdWJsaWNhdGlvbi4gDQo+IA0KPkNvbW1lbnRzOiANCj7igKIJ
UGxlYXNlIHN1cHBseSBhbiBvdmVydmlldyBvZiB0aGUgZHJhZnQgcXVhbGl0eSBhbmQgcmVhZGFi
aWxpdHkuIA0KPuKAoglJbmNsdWRlIGFueXRoaW5nIGVsc2UgdGhhdCB5b3UgdGhpbmsgd2lsbCBi
ZSBoZWxwZnVsIHRvd2FyZA0KPnVuZGVyc3RhbmRpbmcgeW91ciByZXZpZXcuIA0KPk1ham9yIElz
c3VlczogDQo+4oCiCSJObyBtYWpvciBpc3N1ZXMgZm91bmQuIiANCj5NaW5vciBJc3N1ZXM6DQo+
4oCiCVRlY2huaWNhbGx5LCBJIHRoaW5rIHRoZSBkcmFmdCBpcyBjb21wbGV0ZWQuIEhvd2V2ZXIs
IGl0IGRvZXNu4oCZdA0KPmZsb3cgdmVyeSB3ZWxsLiBJbmZvcm1hdGlvbiBpcyBhbGwgb3Zlci4g
SSBzdWdnZXN0IHRoZSBhdXRob3JzIHRvDQo+cmV2aWV3IHRoZSBsYXlvdXQvZmxvdyBvZiB0aGUg
ZG9jdW1lbnQuIA0KPiANCj5IZXJlIGFyZSBteSDigJxkZXRhaWxlZOKAnSBjb21tZW50czoNCj4g
DQo+QWJzdHJhY3Qg4oCUIFdoYXQgaXMgdGhlIHBsdXMgdmFsdWUgb24gdGhhdCBkcmFmdD8gTm8g
Y2xlYXINCj4gDQo+TWFueSBMb25nIHNlbnRlbmNlcyBpbiB0aGUgdGV4dC4gdmVyeSBoYXJkIHRv
IHVuZGVyc3RhbmQgYW5kIGZvbGxvdy4NCj5TeW50YXggdG8gYmUgaW1wcm92ZWQuDQoNCg0KSSB3
ZW50IG92ZXIgdGhlIGFic3RyYWN0LCBJIGRpZG7igJl0IHNlZSBhbnkgbG9uZyBzZW50ZW5jZXMu
IE5vdCBzdXJlIA0KV2hhdCB0byBpbXByb3ZlPyBDYW4geW91IGJlIHNwZWNpZmljPw0KDQoNCj4g
DQo+SW50cm9kdWN0aW9uDQo+VHlwbyA6IOKAnEEgcmVmZXJlbmNlIG1vZGVsIG9yIGEgUDJNUCBQ
VyBpcyBkZXBpY3RlZCBpbiBGaWd1cmUgMSBiZWxvd+KAnQ0KPiANCj7igJxJbiB0aGlzIGRvY3Vt
ZW50LCB3ZSBzcGVjaWZ5IGEgbWV0aG9kIG9mIHNpZ25hbGluZyBQMk1QDQo+ICAgUFcgdXNpbmcg
TERQLuKAnSDigJQ+IHN1Z2dlc3QgdG8gbW92ZSBpdCBmcm9tIGludHJvIHRvIGFic3RyYWN0DQoN
Ck5vdCBzdXJlIGlmIHdlIGNhbiByZWZlcmVuY2UgYSBmaWd1cmUgaW4gdGhlIGFic3RyYWN0LiBU
aGUgYWJzdHJhY3QNCkFscmVhZHkgbWVudGlvbiB0aGF0IHRoZSBzZWNvbmQgc2VudGVuY2UuDQoN
Cj4gDQo+IA0KPkFsc28sIG1ha2Ugc3VyZSB0aGUgM3JkIHBlcnNvbiBpcyB1c2VkLiBUcnkgdG8g
YSB2b2lkIOKAnHdl4oCdIHVzYWdlDQoNCkFncmVlZCwgSSB3aWxsIHJlbW92ZSBhbGwgdXNhZ2Ug
b2Yg4oCcd2XigJ0gaW4gdGhlIGRvY3VtZW50Lg0KDQo+IA0KPk1heSBJIHN1Z2dlc3QgdG8gaGF2
ZSBhIHJlcXVpcmVtZW50IHNlY3Rpb24uIFJlcXVpcmVtZW50cyBhcmUgYWxsIG92ZXINCj50aGUg
ZG9jdW1lbnQuDQoNClRoZXJlIGlzIGFscmVhZHkgYW4gUkZDIGZvciB0aGF0LiBbUkZDNzMzOF0g
ICBGLiBKb3VuYXksIGV0LiBhbCwgDQoiUmVxdWlyZW1lbnRzIGZvciBQb2ludCB0byBNdWx0aXBv
aW50IFBzZXVkb3dpcmUiLCBSRkM3MzM4LCBTZXB0ZW1iZXIgMjAxNC4NCg0KVGhpcyBzb2x1dGlv
biBkb2N1bWVudCBhZGRyZXNzZXMgdGhlIHJlcXVpcmVtZW50cy4NCg0KPiANCj7igJwgICBJbiBj
YXNlIG9mIG1MRFAsIGEgTGVhZi1QRSBjYW4gZGVjaWRlIHRvIGpvaW4gdGhlIFAyTVAgTFNQIGF0
IGFueQ0KPiAgIHRpbWU7IHdoZXJlYXMgaW4gdGhlIGNhc2Ugb2YgUlNWUC1URSwgdGhlIFAyTVAg
TFNQIGlzIHNldCB1cCBieQ0KPnRoZQ0KPiAgIFItUEUsIGdlbmVyYWxseSBhdCB0aGUgaW5pdGlh
bCBzZXJ2aWNlIHByb3Zpc2lvbmluZyB0aW1lLiBJdA0KPnNob3VsZA0KPiAgIGJlIG5vdGVkIHRo
YXQgbG9jYWwgcG9saWN5IGNhbiBvdmVycmlkZSBhbnkgZGVjaXNpb24gdG8gam9pbiwgYWRkDQo+
b3INCj4gICBwcnVuZSBleGlzdGluZyBvciBuZXcgTC1QRShzKSBmcm9tIHRoZSB0cmVlLiBJbiBh
bnkgY2FzZSwgdGhlIFBXDQo+ICAgc2V0dXAgY2FuIGlnbm9yZSB0aGVzZSBkaWZmZXJlbmNlcywg
YW5kIHNpbXBseSBhc3N1bWUgdGhhdCB0aGUNCj5QMk1QDQo+ICAgUFNOIExTUCBpcyBhdmFpbGFi
bGUgd2hlbiBuZWVkZWQNCj7igJwNCj5RdWl0ZSBjb21wbGV4IHRvIGZvbGxvdy4gTWlzc2luZyB0
byDigJx3aHnigJ0gLyBleHBsYW5hdGlvbi4NCg0KU3VyZSBJIGNhbiBjbGFyaWZ5IHRoaXMgYSBs
aXR0bGUgbW9yZSwgd2lsbCByZW1vdmUgc29tZSBzZW50ZW5jZXMgDQpUaGF0IG1ha2UgaXQgY29u
ZnVzaW5nLCB3ZSBhcmUgc2ltcGx5IGhlcmUgZGlmZmVyZW50aWF0aW5nIG1MRFAgTFNQIGZyb20N
CnAybXAgTFNQIHcvIFJTVlAtVEUgYW5kIHNheWluZyB0aGF0IFBXIHNldHVwIGlzIGFnbm9zdGlj
IG9mIHRoZSB0cmFuc3BvcnQgDQpwMm1wIExTUCBzZXR1cC4NCg0KPiANCj7igJxUaGUgTERQIGxp
YmVyYWwgbGFiZWwgcmV0ZW50aW9uIG1vZGUgaXMgdXNlZOKAnA0KPkFub3RoZXIgcmVxdWlyZW1l
bnTigKYgaXMgdGhhdCBhIE1BWSwgU0hPVUxELCBNVVNUPw0KDQpJIHdpbGwgY2hhbmdlIGl0IHRv
IGEgTVVTVC4NCg0KPiANCj7igJxJbiB0aGlzIGNhc2UsIGEgUFcgc3RhdHVzIG1lc3NhZ2Ugd2l0
aCBzdGF0dXMNCj4gICBjb2RlIG9mIDB4MDAwMDAwMDggKExvY2FsIFBTTi1mYWNpbmcgUFcgKGlu
Z3Jlc3MpIFJlY2VpdmUgRmF1bHQpDQo+TVVTVA0KPiAgIGFsc28gYmUgc2VudCB0byB0aGUgUi1Q
ReKAnA0KPiANCj5Ib3c/IFRoZSBMLVBFIGZhaWxzIHRvIGpvaW4gdGhlIFAyTVAgUFNOIExTUC4N
Cg0KQ29ycmVjdCB0aGUgTC1QRSBoYXZlIHRvIHNpZ25hbCB0aGlzIGZhaWx1cmUgdG8gdGhlIHJv
b3QgUEUuDQoNCj4gDQo+U2VjdGlvbiAyLjINCj7igJwgICBOb3RlIHRoYXQgc2luY2UgdGhlIExE
UCBsYWJlbCBtYXBwaW5nIG1lc3NhZ2UgaXMgb25seSBzZW50IGJ5IHRoZQ0KPlItDQo+ICAgUEUg
dG8gYWxsIHRoZSBMLVBFcywgaXQgaXMgbm90IHBvc3NpYmxlIHRvIG5lZ290aWF0ZSBhbnkgaW50
ZXJmYWNlDQo+ICAgcGFyYW1ldGVycy7igJwNCj5XaHkgaXMgdGhhdCBub3RlIHRoZXJlPyBJcyB0
aGF0IGFscmVhZHkgYmVlbiBtZW50aW9uZWQgcHJldmlvdXNseS4NCg0KVGhpcyBpcyB0aGUgb25s
eSByZWZlcmVuY2UgaW4gdGhlIGRvY3VtZW50Lg0KDQo+RmlnLjQgbXVzdCAgYmUgbW92ZWQgdG8g
cHJvcGVyIGluIHRoZSB0ZXh0IE9SIGNyZWF0ZSAyIHN1YnNlY3Rpb24gaW4NCj4yLjINCg0KU29y
cnkgZGlkbuKAmXQgZ2V0IHdoYXQgeW91IG1lYW4gaGVyZT8gQ2FuIHlvdSBlbGFib3JhdGU/DQoN
Cj4gDQo+4oCcQXMgc3VjaCwgUFcgc3RhdHVzIG5lZ290aWF0aW9uIHByb2NlZHVyZQ0KPiAgIGRl
c2NyaWJlZCBpbiBbUkZDNDQ0N2Jpc10gaXMgbm90IGFwcGxpY2FibGUgdG8gUDJNUCBQVy4gQSBu
b2RlDQo+TVVTVA0KPiAgIE5PVCBjbGFpbSB0byBiZSAgUDJNUCBQVyBjYXBhYmxlIGJ5IHNlbmRp
bmcgYSBMRFAgUDJNUCBQVw0KPkNhcGFiaWxpdHkNCj4gICBUTFYgIGlmIGl0IGlzIG5vdCBhbHNv
IGNhcGFibGUgb2YgaGFuZGxpbmcgUFcgc3RhdHVz4oCcDQo+IA0KPlNob3VsZCBhIG5vZGUgc2Vu
ZCBMRFAgUDJNUCBQVyBDYXBhYmlsaXR5IFRMViBvciBub3Q/IE5vdCB3ZWxsIGV4cGxhaW4NCg0K
V2hhdCBpcyBzYWlkIGhlcmUsIHRoYXQgeW91IGNhbuKAmXQgYmUgUDJNUCBQVyBjYXBhYmxlIHdp
dGhvdXQgYmVpbmcgUFcgc3RhdHVzIGNhcGFibGUuDQpOb3Qgc3VyZSBob3cgdG8gbWFrZSBpdCBj
bGVhcmVyLg0KDQo+DQo+IA0KPlRoZXJlIGlzIHNvbWUgcmVmZXJlbmNlIHRvIExTUiBpbiB0aGUg
dGV4dCB3aGVyZSB0aGUgbWFqb3IgcGFydCB1c2UNCj50aGUgd29yZGluZyDigJxub2Rl4oCdLg0K
DQpJIHdpbGwgbWFrZSBhbGwgY29uc2lzdGVudCwgYW5kIHVzZSBMU1IgaW5zdGVhZCBvZiBub2Rl
Lg0KDQpUaGFua3MsDQoNClNhbWkNCj4gDQo+Tml0czogDQo+Ti9BDQo+IA0KPlJlZ2FyZHMsDQo+
UGF0cmljZSBCcmlzc2V0dGUNCj4NCj4NCj4NCj4NCg==


From nobody Sun May 14 21:43:25 2017
Return-Path: <julian.reschke@gmx.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 006D712EABD; Sun, 14 May 2017 21:43:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.501
X-Spam-Level: 
X-Spam-Status: No, score=-3.501 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, 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 bMTbef670DkH; Sun, 14 May 2017 21:43:22 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 9BCE0129469; Sun, 14 May 2017 21:38:40 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.120.200]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LhTjQ-1dno7v43qi-00mZhq; Mon, 15 May 2017 06:38:36 +0200
Subject: Re: Last Call: <draft-nottingham-rfc5988bis-05.txt> (Web Linking) to Proposed Standard
To: Mark Nottingham <mnot@mnot.net>
References: <588716b3-161c-62ac-e5a9-a04c86f13e86@gmx.de> <704BC987-1ED0-4E59-A803-0B4013A86F03@mnot.net> <c81eb293-f443-8d61-bd82-b7c2902e4426@gmx.de> <09EA3303-8F65-4FDE-8303-8C2AD9B8B897@mnot.net>
Cc: ietf@ietf.org, draft-nottingham-rfc5988bis@ietf.org
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <56d569af-f6a2-067d-29cd-43a4dd133182@gmx.de>
Date: Mon, 15 May 2017 06:38:34 +0200
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: <09EA3303-8F65-4FDE-8303-8C2AD9B8B897@mnot.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:rt0RoWOSTfKGBXKVdS0qgG1uITx046zN0TCKsQ9m3saEadyI7A+ yaht1Kn1SirFs9Q2SIr4JDmA/RUkGNGxNEw9tosR/+IvdZ1Df9dVa9eZuK8NclKrl5HkHL+ FYbPogxcxdTFOAQLw2lu2aiB8/etN1y2rDHoJbkjOr/yhSYgfgabtWmSMtMeUVuoxsUGuUR gc0GrXtiRRxojWaMi4EUQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:CgreIBzShqM=:IE5fAtD7NnZY6Ci9Pj6AqW M1V5bMTb5PoqkTx3+agSgqrBtrixZH8MCtKZOog100t5SOjB/zCDnw+EfUp6Lhi9QzvAwDJtn ON0PAMH7FSMIrQVfKL+ZbFfvAKpwTQX2yrLgm8ZITB5DLRr2zfaE8tl7/4YvdKQCD5VO7AE9p 94qkuYFrqN801h355V4a7v1YvJUBluEBEOaHUg5ymXgf5BxLEYGyuTEE1k8QEQ5Zo+b+0uCHM HKnt1f11iW7ttsAFsCmwF7mXXG+5oyZr3QjGLYzxjnsDnyAco8QGHIMuh8kbrehC9IyaqpNLA CjJ0uB/+r48MAQLrOFn/iI27PEt824ngHLYsXninAxcvg30moAeTOAU5sC5h1mYN2VgYdaYoU YLrPRFp0XaouZoxsyP+LE2Z2dl8Mtz+QbuwbMxSs4kvzQEvzdKyl9MiySAtT89pAmvruZx0WL o9qK8wR4iemXIPwpPdJPim7zCWhuHSrUft89KMLjNIDaMAWq+JAoCb0WwVVRISUvf4VFjkUxP +d6cdFZHKVCFTNfvOF1lbXXrT9OfQY1LP+ixTAt8Q86MADNoxFoP9SA37JYpQVwTMYyqGInVK eO7+dYOhM1Sy6ty/GVCBp6ZhdJ0mBeaN/S+GZw1c7KFfrVs9BnY8/89/AKcqDS/akxwhBR1Z5 9xRh5kYe6/Ik47XwH93B+5HTcrfEuit1BIsiNrzCoy6VFSsg/ew8G2VfRZ3ffg5YrSYS93w1z wyaJmw8riOfXjtjL7YgN+eujejdRPJA8GX7FagNaDIQFj+eynISQxbaCvhTFIzLAWPFbSr6YC 5VptCJA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aVw5oG3j8yShjaaMIlDALOrYOj4>
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, 15 May 2017 04:43:24 -0000

On 2017-05-15 03:42, Mark Nottingham wrote:
> On 14 May 2017, at 6:03 pm, Julian Reschke <julian.reschke@gmx.de> wrote:
>
>>>> Actually, one popular browser also looks for the stylesheet link relation in the "Link" header field...
>>>
>>> True, but that's not specified behaviour, AIUI.
>>
>> <https://www.w3.org/TR/html5/document-metadata.html#the-link-element>:
>>
>> "HTTP Link: headers, if supported, must be assumed to come before any links in the document, in the order that they were given in the HTTP message. These headers are to be processed according to the rules given in the relevant specifications. [HTTP] [WEBLINK]"
>>
>> So this refers to RFC 5988, which delegates to the IANA registry, which in turn points back to the HTML spec for the definition of the "stylesheet" link relation.
>>
>> To me this sounds like it is well-defined, just not required ("if supported").
>
> https://github.com/mnot/I-D/commit/8e3d4c5167e

+1


 > ...

Best regards, Julian


From nobody Mon May 15 03:46:38 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 EE7D0126E64; Mon, 15 May 2017 03:46:35 -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: draft-ietf-tls-ecdhe-psk-aead.all@ietf.org, ietf@ietf.org, tls@ietf.org, dromasca@gmail.com
Subject: Genart last call review of draft-ietf-tls-ecdhe-psk-aead-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149484519593.2843.448630358757818654@ietfa.amsl.com>
Date: Mon, 15 May 2017 03:46:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jJ9HYfGTQE7ylG-CIezpHSgRewc>
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, 15 May 2017 10:46:36 -0000

Reviewer: Dan Romascanu
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 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-tls-ecdhe-psk-aead-??
Reviewer: Dan Romascanu
Review Date: 2017-05-15
IETF LC End Date: 2017-05-18
IESG Telechat date: 2017-05-25

Summary:

This is a straight-forward and clear document that defines several new
cipher suites for the Transport Layer Security (TLS) protocol version
1.2 and higher, based on the Ephemeral Elliptic Curve Diffie-Hellman
with Pre-Shared Key (ECDHE_PSK) key exchange together with the
Authenticated Encryption with Associated Data (AEAD) algorithms
AES-GCM and AES-CCM. The document is well written and I appreciate the
effort to clarify in the Introduction the context, what was missing,
and why the document is necessary. The document is Ready, there is one
issue about support for TLS version 1.3 and higher that may need some
text clarification. 

Major issues:

Minor issues:

Section 4 ('Applicable TLS Versions') describes in details how the
cipher suites defined in the document make use of the authenticated
encryption with additional data (AEAD) defined in TLS 1.2 [RFC5246]
and DTLS 1.2 [RFC6347]. About TLS 1.3 it just says: 

' TLS 1.3 and above version, negotiate and support these cipher suites
in a different way.'

This may raise some concerns as 'in a different way' is ambiguous,
especially compared to the details included for TLS 1.2. Moreover, TLS
1.3 is still work-in-progress, and I believe that this document when
approved needs to wait for TLS 1.3 to be approved for publication.
Will anything change, or need to be added? Some better clarification
text would help IMO. 

Nits/editorial comments: 



From nobody Mon May 15 06:19:19 2017
Return-Path: <john@jlc.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 8809712941C for <ietf@ietfa.amsl.com>; Mon, 15 May 2017 06:19:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.501
X-Spam-Level: 
X-Spam-Status: No, score=-1.501 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 9JLAKHcUsR23 for <ietf@ietfa.amsl.com>; Mon, 15 May 2017 06:19:17 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id ED47F129B25 for <ietf@ietf.org>; Mon, 15 May 2017 06:12:57 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 6945690A197; Mon, 15 May 2017 09:12:40 -0400 (EDT)
Date: Mon, 15 May 2017 09:12:40 -0400
From: John Leslie <john@jlc.net>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: Registration for remote participation
Message-ID: <20170515131240.GR56980@verdi>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2V-MJYwfIxq1YxsFlZZDA2q4EeQ>
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, 15 May 2017 13:19:18 -0000

IETF Chair <chair@ietf.org> wrote:
> 
> The IESG is soliciting community feedback on a proposal to require
> registration for remote participants at IETF meetings...
> 
> Registration would be mandatory to access MeetEcho sessions in real
> time and to join the remote mic queue during a session...
> 
> Upon registering, participants would be issued a registration ID, just
> as they are today.
> 
> To join a session, participants would be asked to input the
> registration ID.

   These "registration IDs" are hard to remember. That's why I joined so
many sessions "without rugistration ID".

> The same email-based facility that is currently available to retrieve
> a forgotten registration ID would continue to be available.

   This is not practical unless you allow joining enough before the start
of session to complete the process.

> The cookie-based ???Remember me??? option would also still be available.

   Would you believe some of us avoid cookies?

> Other options for authentication (leveraging a user-chosen password or
> datatracker credentials) might be explored further in the future.

   I strongly advise considering them before disallowing registration
without registration ID.

--
John Leslie <john@jlc.net>


From nobody Mon May 15 06:25:30 2017
Return-Path: <john@jlc.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 1CADE12EB2F for <ietf@ietfa.amsl.com>; Mon, 15 May 2017 06:25:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.302
X-Spam-Level: 
X-Spam-Status: No, score=-2.302 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 tVUfunCf8Wfd for <ietf@ietfa.amsl.com>; Mon, 15 May 2017 06:25:25 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 4024F12EB30 for <ietf@ietf.org>; Mon, 15 May 2017 06:18:42 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 9907290A26B; Mon, 15 May 2017 09:18:41 -0400 (EDT)
Date: Mon, 15 May 2017 09:18:41 -0400
From: John Leslie <john@jlc.net>
To: Ted Hardie <ted.ietf@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: Registration for remote participation
Message-ID: <20170515131841.GS56980@verdi>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <c1f0f773-4842-e413-e6df-dcbf27b94235@cs.tcd.ie> <CA+9kkMAEtMXQ0MVXWX3nTcmi1oCsMq8JcdNPJqLTU1gM2nz74Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+9kkMAEtMXQ0MVXWX3nTcmi1oCsMq8JcdNPJqLTU1gM2nz74Q@mail.gmail.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6_V-ZERQjWBpABaQWa9ujsu5BGw>
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, 15 May 2017 13:25:28 -0000

Ted Hardie <ted.ietf@gmail.com> wrote:
> ...
> 
> We need that data first.

   There really-should be ways to get it without asking folks to change
the way they access remote participation.

   It would seem to me that providing the name under which you registered
would be sufficient...

--
John Leslie <john@jlc.net>


From nobody Mon May 15 07:09:25 2017
Return-Path: <murch@andrew.cmu.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 E4C01129AEB; Mon, 15 May 2017 07:09:22 -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, RP_MATCHES_RCVD=-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 o1iAHhScTzlE; Mon, 15 May 2017 07:09:20 -0700 (PDT)
Received: from smtp.andrew.cmu.edu (SMTP.ANDREW.CMU.EDU [128.2.105.202]) (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 54C7912EAB9; Mon, 15 May 2017 07:03:31 -0700 (PDT)
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) (user=murch mech=PLAIN (0 bits)) by smtp.andrew.cmu.edu (8.15.2/8.15.2) with ESMTPSA id v4FE3P6L032523 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 15 May 2017 10:03:26 -0400
Subject: Re: [art] ART Area Review for draft-ietf-calext-caldav-attachments-02
To: Julian Reschke <julian.reschke@gmx.de>, IETF Discussion <ietf@ietf.org>, art@ietf.org
References: <c04f39e2-79d2-ab9d-59ab-26e51d7ab5fc@gmx.de>
From: Ken Murchison <murch@andrew.cmu.edu>
Organization: Carnegie Mellon University
Message-ID: <81613220-989b-ca78-fe56-0ac7b19e7ce6@andrew.cmu.edu>
Date: Mon, 15 May 2017 10:03:25 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <c04f39e2-79d2-ab9d-59ab-26e51d7ab5fc@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-PMX-Version: 6.3.0.2556906, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.5.15.135416
X-SMTP-Spam-Clean: 33% ( SXL_IP_DYNAMIC 3, TO_IN_SUBJECT 0.5, HTML_00_01 0.05, HTML_00_10 0.05, BODY_SIZE_4000_4999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, FROM_EDU_TLD 0, IN_REP_TO 0, LEGITIMATE_SIGNS 0, MSG_THREAD 0, RDNS_GENERIC_POOLED 0, RDNS_POOLED 0, RDNS_RESIDENTIAL 0, RDNS_SUSP 0, RDNS_SUSP_GENERIC 0, RDNS_SUSP_SPECIFIC 0, REFERENCES 0, URI_WITH_PATH_ONLY 0,  __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __HAS_FROM 0, __HAS_MSGID 0, __HTTPS_URI 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0,  __MIME_TEXT_P 0, __MIME_TEXT_P1 0, __MIME_VERSION 0, __MOZILLA_USER_AGENT 0, __MULTIPLE_URI_TEXT 0, __NO_HTML_TAG_RAW 0, __PHISH_SPEAR_STRUCTURE_1 0, __RDNS_POOLED_1 0, __REFERENCES 0, __SANE_MSGID 0, __SUBJ_ALPHA_NEGATE 0, __TO_IN_SUBJECT2 0, __TO_MALFORMED_2 0, __TO_NAME 0, __TO_NAME_DIFF_FROM_ACC 0, __TO_REAL_NAMES 0, __URI_IN_BODY 0, __URI_NOT_IMG 0, __URI_NO_MAILTO 0, __URI_NO_WWW 0, __URI_NS , __URI_WITH_PATH 0, __USER_AGENT 0)
X-SMTP-Spam-Score: 33%
X-Scanned-By: MIMEDefang 2.78 on 128.2.105.202
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8U7iJQzVoihl9pt0HR9-DVUcrTY>
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, 15 May 2017 14:09:23 -0000

Hi Julian,

Thanks for the review.  Comments inline.


On 05/14/2017 10:23 AM, Julian Reschke wrote:
> Reviewer: Julian Reschke
> Review result: Not Ready
>
> Document: draft-ietf-calext-caldav-attachments-02
> IETF LC End Date: 2017-05-14
> IESG Telechat date: 2017-05-25
>
> This document describes attachment handling in CalDAV (WebDAV based 
> calendaring).
>
> The mechanism described by this document is essential RPCish, using 
> HTTP POST for tunneling. It will work in practice, but it definitively 
> isn't state of the art in IETF protocols, in particular in an 
> otherwise WebDAV/CalDAV-based ecosystem.
>
> Major issues:
>
> The main issue with this specification is that it
>
> 1) models operations on attachments as POST operations, where the 
> actual type of operation is specified using a query parameter, instead 
> of using the HTTP methods POST, PUT, and DELETE.

The resource being acted upon is an actual calendar resource, which is 
already in place.  The attachments are meta-data associated with one or 
more calendar resources, which is why a POST is used on the calendar 
resource to manipulate an attachment.  Can you explain how you would 
envision different HTTP methods be used to add/update/delete an 
attachment associated with a calendar resource?

> 2) hardwires specific query strings into the protocol, violating a 
> MUST level requirement in BCP 190 (see 
> https://tools.ietf.org/html/rfc7320#section-2.4):
>
>    Applications MUST NOT directly specify the syntax of queries, as this
>    can cause operational difficulties for deployments that do not
>    support a particular form of a query.  For example, a site may wish
>    to support an application using "static" files that do not support
>    query parameters.

Which part(s) of the query syntax MUST not be specified?  The entire 
thing?  Just the keywords?  Did RFC 7808 get this wrong, or is URI 
templating ok?


> Re 1) this is even called out specifically in Sections 3.8 (update) 
> and 3.9 (remove), but it's not clear at all why that is the case.
>
> Re 2) Part of the hard-wiring could be avoided by using different HTTP 
> methods for the different actions. The other parameters could be made 
> discoverable using URIs / URI templates, exposed as WebDAV properties, 
> as is the case in RFC 5995.

As above, can you explain how different HTTP methods would be used where 
the target of the add/update/remove operation is an existing calendar 
resource?



> 5.1. Cal-Managed-ID Response Header Field
>
> This doesn't seem to address the points listed in 
> <https://greenbytes.de/tech/webdav/rfc7231.html#considerations.for.new.header.fields> 
> (and it wouldn't be needed if the attachment would be modeled as an 
> HTTP resource whose values could be reported back in a Location header 
> field upon creation).

Can parameters be added to a Location header field (it doesn't appear 
so), or are you suggesting that the managed-id value be encoded in the 
URI-reference value?



>
> Minor issues:
>
> 3.12.4.  Processing Time
>
>    Clients can expect servers to take a while to respond to POST
>    requests that include large attachment bodies.  Servers SHOULD use
>    the "102 (Processing)" interim response defined in Section 10.1 of
>    [RFC2518] to keep the client connection alive if the POST request
>    will take significant time to complete.
>
> While discussing the new code 103 in the HTTP WG, we considered 
> interop problems with existing code that doesn't handle 1xx status 
> codes at all, or had problems with status codes other than 100. I 
> personally support use of new 1xx status codes, but it would be good 
> to hear whether the WG considered deployment problems when making this 
> a SHOULD-level requirement.

Existing implementations of this CalDAV extension all seem to handle 1xx 
status codes.


-- 
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University


From nobody Mon May 15 07:24:27 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 04A7C12EAB3 for <ietf@ietfa.amsl.com>; Mon, 15 May 2017 07:24:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 qMUy-ZuXIvPO for <ietf@ietfa.amsl.com>; Mon, 15 May 2017 07:24:24 -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 57846124BFA for <ietf@ietf.org>; Mon, 15 May 2017 07:18:45 -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 094EC3493C3; Mon, 15 May 2017 14:18:43 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id D3ADB160072; Mon, 15 May 2017 14:18:42 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id BFFB4160071; Mon, 15 May 2017 14:18: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 WARXzvQfzXHc; Mon, 15 May 2017 14:18: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 81E6B160041; Mon, 15 May 2017 14:18:42 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id C95CD6EB9E9A; Tue, 16 May 2017 00:18:39 +1000 (AEST)
To: John Leslie <john@jlc.net>
Cc: IETF Discussion <ietf@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <20170515131240.GR56980@verdi>
Subject: Re: Registration for remote participation
In-reply-to: Your message of "Mon, 15 May 2017 09:12:40 -0400." <20170515131240.GR56980@verdi>
Date: Tue, 16 May 2017 00:18:39 +1000
Message-Id: <20170515141839.C95CD6EB9E9A@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1Ntq5ytv6UJZS20QoCKAuYxSInc>
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, 15 May 2017 14:24:27 -0000

In message <20170515131240.GR56980@verdi>, John Leslie writes:
> IETF Chair <chair@ietf.org> wrote:
> > 
> > The IESG is soliciting community feedback on a proposal to require
> > registration for remote participants at IETF meetings...
> > 
> > Registration would be mandatory to access MeetEcho sessions in real
> > time and to join the remote mic queue during a session...
> > 
> > Upon registering, participants would be issued a registration ID, just
> > as they are today.
> > 
> > To join a session, participants would be asked to input the
> > registration ID.
> 
>    These "registration IDs" are hard to remember. That's why I joined so
> many sessions "without rugistration ID".

When you need to registration ID to participate you will record it,
look it in the registration email or recover it.

	IETF 97 confirmation for Mr. Mark P Andrews

	Registration Type: Remote Participant 

	Your registration number is 97XXXXXXXX 

 
> > The same email-based facility that is currently available to retrieve
> > a forgotten registration ID would continue to be available.
> 
>    This is not practical unless you allow joining enough before the start
> of session to complete the process.

The session are open well before the workig group actually starts.
 
> > The cookie-based ???Remember me??? option would also still be available.
> 
>    Would you believe some of us avoid cookies?
> 
> > Other options for authentication (leveraging a user-chosen password or
> > datatracker credentials) might be explored further in the future.
> 
>    I strongly advise considering them before disallowing registration
> without registration ID.
> 
> --
> John Leslie <john@jlc.net>
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Mon May 15 09:07:42 2017
Return-Path: <pbrisset@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 6D1F51267BB; Mon, 15 May 2017 09:07:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 1gB4q-rwcgry; Mon, 15 May 2017 09:07:19 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AD43128B44; Mon, 15 May 2017 09:02:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10002; q=dns/txt; s=iport; t=1494864173; x=1496073773; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=FL8OFKAHzotlCcZDZHUgjlMnRNJ5pUaqfRfvOMVqLQQ=; b=XBs+BiiaR7nmft5OmaNMPS9QRBr7OVIlRioeATcI12jJE0kkH3Yu0uZj 4J8zp7Pr7qUsLF6KSomCIqWdnD+NoP5J/we956pMO0G7rp4OoWtB0GXM0 /oZ/qJHeMPUxW5728pOuEPz4RQLHVFbch1CY4Oyp5AXk/b6PEoflwEjaJ o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BFAQCH0BlZ/4YNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1VigQwHg2SKGJE+IZV1gg8ohXwCGoUWPxgBAgEBAQEBAQFrKIU?= =?us-ascii?q?ZBiMREzIQAgEGAg4GBgImAgICMBUQAgQBDQUbigiOep1ggiaDP4cMAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBHYELhVSBXQErC4JlhGMHECECglgvgjEBBJZvhxsBhxu?= =?us-ascii?q?Lf4IEVYRmg2aGRoY0jg4BHziBCnAVWAGEZByBY3aHUoENAQEB?=
X-IronPort-AV: E=Sophos;i="5.38,345,1491264000"; d="scan'208";a="424589387"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 15 May 2017 16:02:52 +0000
Received: from XCH-RTP-007.cisco.com (xch-rtp-007.cisco.com [64.101.220.147]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id v4FG2pL4006023 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 15 May 2017 16:02:52 GMT
Received: from xch-rtp-009.cisco.com (64.101.220.149) by XCH-RTP-007.cisco.com (64.101.220.147) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 15 May 2017 12:02:51 -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.1210.000; Mon, 15 May 2017 12:02:51 -0400
From: "Patrice Brissette (pbrisset)" <pbrisset@cisco.com>
To: Sami Boutros <sboutros@vmware.com>, Min Ye <amy.yemin@huawei.com>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>
CC: "draft-ietf-pals-p2mp-pw.all@ietf.org" <draft-ietf-pals-p2mp-pw.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "pals@ietf.org" <pals@ietf.org>
Subject: Re: Rtgdir last call review of draft-ietf-pals-p2mp-pw-02
Thread-Topic: Rtgdir last call review of draft-ietf-pals-p2mp-pw-02
Thread-Index: AQHSzZS0GfuQJeqMNUWBoX3pZMCpIw==
Date: Mon, 15 May 2017 16:02:51 +0000
Message-ID: <B220B877-8FC1-4296-925A-2580DD3C796F@cisco.com>
References: <149446531632.16715.2861233468294466753@ietfa.amsl.com> <89E173B8-3C03-4B4A-A405-F0442B983D7F@vmware.com>
In-Reply-To: <89E173B8-3C03-4B4A-A405-F0442B983D7F@vmware.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.21.0.170409
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.221.176]
Content-Type: text/plain; charset="utf-8"
Content-ID: <22C5271AC015914A98A7AE7582165054@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RnYaZthmTLPMQxhOuoKjyDu9ZLg>
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, 15 May 2017 16:07:22 -0000

SGV5IFNhbWksDQoNClBsZWFzZSBzZWUgYmVsb3cuIExvb2sgZm9yIDxQYXRyaWNlPg0KDQpSZWdh
cmRzLA0KUGF0cmljZSBCcmlzc2V0dGUNCg0KT24gMjAxNy0wNS0xNCwgOTo1MiBQTSwgIlNhbWkg
Qm91dHJvcyIgPHNib3V0cm9zQHZtd2FyZS5jb20+IHdyb3RlOg0KDQogICAgSGkgUGF0cmljZSwN
CiAgICANCiAgICBUaGFua3MgZm9yIHJldmlld2luZyB0aGUgZHJhZnQuDQogICAgDQogICAgUGxl
YXNlIHNlZSBjb21tZW50cyBpbmxpbmUuDQogICAgDQogICAgDQogICAgT24gNS8xMC8xNywgNjox
NSBQTSwgIk1pbiBZZSIgPGFteS55ZW1pbkBodWF3ZWkuY29tPiB3cm90ZToNCiAgICANCiAgICA+
UmV2aWV3ZXI6IFBhdHJpY2UgQnJpc3NldHRlDQogICAgPlJldmlldyByZXN1bHQ6IEhhcyBJc3N1
ZXMNCiAgICA+DQogICAgPltSZXNlbmRpbmcgdG8gUlRHLURJUl0NCiAgICA+DQogICAgPkhlbGxv
LCANCiAgICA+SSBoYXZlIGJlZW4gc2VsZWN0ZWQgYXMgdGhlIFJvdXRpbmcgRGlyZWN0b3JhdGUg
cmV2aWV3ZXIgZm9yIHRoaXMNCiAgICA+ZHJhZnQuIFRoZSBSb3V0aW5nIERpcmVjdG9yYXRlIHNl
ZWtzIHRvIHJldmlldyBhbGwgcm91dGluZyBvcg0KICAgID5yb3V0aW5nLXJlbGF0ZWQgZHJhZnRz
IGFzIHRoZXkgcGFzcyB0aHJvdWdoIElFVEYgbGFzdCBjYWxsIGFuZCBJRVNHDQogICAgPnJldmll
dywgYW5kIHNvbWV0aW1lcyBvbiBzcGVjaWFsIHJlcXVlc3QuIFRoZSBwdXJwb3NlIG9mIHRoZSBy
ZXZpZXcgaXMNCiAgICA+dG8gcHJvdmlkZSBhc3Npc3RhbmNlIHRvIHRoZSBSb3V0aW5nIEFEcy4g
Rm9yIG1vcmUgaW5mb3JtYXRpb24gYWJvdXQNCiAgICA+dGhlIFJvdXRpbmcgRGlyZWN0b3JhdGUs
IHBsZWFzZSBzZWUNCiAgICA+aHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3Vy
bD91PWh0dHAtM0FfX3RyYWMudG9vbHMuaWV0Zi5vcmdfYXJlYV9ydGdfdHJhY193aWtpX1J0Z0Rp
ciZkPUR3SURhUSZjPXVpbGFLOTBENFRPVm9INThKTlhSZ1Emcj1JVnpjVFJMUWRwdGEwOEwwYl95
MnpEa3F2d0poUktNQ0FiWC0ySy1MVjk4Jm09TVdJWGZlN0VfZ0Z3V1pGcnNWUHBOVGE2RVFpbUNH
RngtRzNzSWpNTGJNZyZzPXRBM051bVFFUkhFUnVZRFlBMENDcHJxMzZfX01IR0xmWlUzRThZeXB2
VmcmZT0gIA0KICAgID5BbHRob3VnaCB0aGVzZSBjb21tZW50cyBhcmUgcHJpbWFyaWx5IGZvciB0
aGUgdXNlIG9mIHRoZSBSb3V0aW5nIEFEcywNCiAgICA+aXQgd291bGQgYmUgaGVscGZ1bCBpZiB5
b3UgY291bGQgY29uc2lkZXIgdGhlbSBhbG9uZyB3aXRoIGFueSBvdGhlcg0KICAgID5JRVRGIExh
c3QgQ2FsbCBjb21tZW50cyB0aGF0IHlvdSByZWNlaXZlLCBhbmQgc3RyaXZlIHRvIHJlc29sdmUg
dGhlbQ0KICAgID50aHJvdWdoIGRpc2N1c3Npb24gb3IgYnkgdXBkYXRpbmcgdGhlIGRyYWZ0LiAN
CiAgICA+IA0KICAgID5Eb2N1bWVudDogZHJhZnQtaWV0Zi1wYWxzLXAybXAtcHctMDIudHh0DQog
ICAgPlJldmlld2VyOiBQYXRyaWNlIEJyaXNzZXR0ZQ0KICAgID5SZXZpZXcgRGF0ZTogTWF5IDEw
LCAyMDE3DQogICAgPklFVEYgTEMgRW5kIERhdGU6IE1heSAxMiwgMjAxNw0KICAgID5JbnRlbmRl
ZCBTdGF0dXM6IFN0YW5kYXJkIFRyYWNrIA0KICAgID5TdW1tYXJ5OiANCiAgICA+4oCiCUkgaGF2
ZSBzb21lIG1pbm9yIGNvbmNlcm5zIGFib3V0IHRoaXMgZG9jdW1lbnQgdGhhdCBJIHRoaW5rIHNo
b3VsZA0KICAgID5iZSByZXNvbHZlZCBiZWZvcmUgcHVibGljYXRpb24uIA0KICAgID4gDQogICAg
PkNvbW1lbnRzOiANCiAgICA+4oCiCVBsZWFzZSBzdXBwbHkgYW4gb3ZlcnZpZXcgb2YgdGhlIGRy
YWZ0IHF1YWxpdHkgYW5kIHJlYWRhYmlsaXR5LiANCiAgICA+4oCiCUluY2x1ZGUgYW55dGhpbmcg
ZWxzZSB0aGF0IHlvdSB0aGluayB3aWxsIGJlIGhlbHBmdWwgdG93YXJkDQogICAgPnVuZGVyc3Rh
bmRpbmcgeW91ciByZXZpZXcuIA0KICAgID5NYWpvciBJc3N1ZXM6IA0KICAgID7igKIJIk5vIG1h
am9yIGlzc3VlcyBmb3VuZC4iIA0KICAgID5NaW5vciBJc3N1ZXM6DQogICAgPuKAoglUZWNobmlj
YWxseSwgSSB0aGluayB0aGUgZHJhZnQgaXMgY29tcGxldGVkLiBIb3dldmVyLCBpdCBkb2VzbuKA
mXQNCiAgICA+ZmxvdyB2ZXJ5IHdlbGwuIEluZm9ybWF0aW9uIGlzIGFsbCBvdmVyLiBJIHN1Z2dl
c3QgdGhlIGF1dGhvcnMgdG8NCiAgICA+cmV2aWV3IHRoZSBsYXlvdXQvZmxvdyBvZiB0aGUgZG9j
dW1lbnQuIA0KICAgID4gDQogICAgPkhlcmUgYXJlIG15IOKAnGRldGFpbGVk4oCdIGNvbW1lbnRz
Og0KICAgID4gDQogICAgPkFic3RyYWN0IOKAlCBXaGF0IGlzIHRoZSBwbHVzIHZhbHVlIG9uIHRo
YXQgZHJhZnQ/IE5vIGNsZWFyDQogICAgPiANCiAgICA+TWFueSBMb25nIHNlbnRlbmNlcyBpbiB0
aGUgdGV4dC4gdmVyeSBoYXJkIHRvIHVuZGVyc3RhbmQgYW5kIGZvbGxvdy4NCiAgICA+U3ludGF4
IHRvIGJlIGltcHJvdmVkLg0KDQo8UGF0cmljZT4gVGhpcyBjb21tZW50IGlzIHJlZ2FyZGluZyB0
aGUgZHJhZnQgaW4gZ2VuZXJhbC4gSXQgZG9lc27igJl0IGZsb3cgd2VsbC4gWW91IG5lZWQgdG8g
cmVhZCBpdCBtb3JlIHRoYW4gb25jZSB0byBzZWUgdGhlIG92ZXJhbGwgcGljdHVyZS4gSXQgbWln
aHQganVzdCBiZSB0byByZXNodWZmbGUgc29tZSBzZWN0aW9ucy4NCiAgICANCiAgICANCiAgICBJ
IHdlbnQgb3ZlciB0aGUgYWJzdHJhY3QsIEkgZGlkbuKAmXQgc2VlIGFueSBsb25nIHNlbnRlbmNl
cy4gTm90IHN1cmUgDQogICAgV2hhdCB0byBpbXByb3ZlPyBDYW4geW91IGJlIHNwZWNpZmljPw0K
ICAgIA0KICAgIA0KICAgID4gDQogICAgPkludHJvZHVjdGlvbg0KICAgID5UeXBvIDog4oCcQSBy
ZWZlcmVuY2UgbW9kZWwgb3IgYSBQMk1QIFBXIGlzIGRlcGljdGVkIGluIEZpZ3VyZSAxIGJlbG93
4oCdDQogICAgPiANCiAgICA+4oCcSW4gdGhpcyBkb2N1bWVudCwgd2Ugc3BlY2lmeSBhIG1ldGhv
ZCBvZiBzaWduYWxpbmcgUDJNUA0KICAgID4gICBQVyB1c2luZyBMRFAu4oCdIOKAlD4gc3VnZ2Vz
dCB0byBtb3ZlIGl0IGZyb20gaW50cm8gdG8gYWJzdHJhY3QNCiAgICANCiAgICBOb3Qgc3VyZSBp
ZiB3ZSBjYW4gcmVmZXJlbmNlIGEgZmlndXJlIGluIHRoZSBhYnN0cmFjdC4gVGhlIGFic3RyYWN0
DQogICAgQWxyZWFkeSBtZW50aW9uIHRoYXQgdGhlIHNlY29uZCBzZW50ZW5jZS4NCg0KPFBhdHJp
Y2U+IFRoaXMgaXMgTk9UIGEgZmlndXJlIGJ1dCByYXRoZXIgdGhlIGV4cGxhbmF0aW9uLiBUaGF0
IGxpbmUgbWFrZXMgdGhlIGRvY3VtZW50IHZlcnkgY2xlYXIuIEl0IGp1c3QgbmVlZCB0byBiZSBz
cGVsbGVkIG91dC4g4oCcc3BlY2lmeSBhIG1ldGhvZCBvZiBzaWduYWxpbmcgUDJNUCBQVyB1c2lu
ZyBMRFDigJ0uDQoNCiAgICA+IA0KICAgID4gDQogICAgPkFsc28sIG1ha2Ugc3VyZSB0aGUgM3Jk
IHBlcnNvbiBpcyB1c2VkLiBUcnkgdG8gYSB2b2lkIOKAnHdl4oCdIHVzYWdlDQogICAgDQogICAg
QWdyZWVkLCBJIHdpbGwgcmVtb3ZlIGFsbCB1c2FnZSBvZiDigJx3ZeKAnSBpbiB0aGUgZG9jdW1l
bnQuDQogICAgDQogICAgPiANCiAgICA+TWF5IEkgc3VnZ2VzdCB0byBoYXZlIGEgcmVxdWlyZW1l
bnQgc2VjdGlvbi4gUmVxdWlyZW1lbnRzIGFyZSBhbGwgb3Zlcg0KICAgID50aGUgZG9jdW1lbnQu
DQogICAgDQogICAgVGhlcmUgaXMgYWxyZWFkeSBhbiBSRkMgZm9yIHRoYXQuIFtSRkM3MzM4XSAg
IEYuIEpvdW5heSwgZXQuIGFsLCANCiAgICAiUmVxdWlyZW1lbnRzIGZvciBQb2ludCB0byBNdWx0
aXBvaW50IFBzZXVkb3dpcmUiLCBSRkM3MzM4LCBTZXB0ZW1iZXIgMjAxNC4NCiAgICANCiAgICBU
aGlzIHNvbHV0aW9uIGRvY3VtZW50IGFkZHJlc3NlcyB0aGUgcmVxdWlyZW1lbnRzLg0KDQo8UGF0
cmljZT4gWW91ciBkb2N1bWVudCBlbmhhbmNlcyB0aGF0IGJhc2VkIFJGQyBieSBwcm92aWRpbmcg
bW9yZSDigJxNVVNU4oCdLCDigJxTSE9VTETigJ0sIGV0Yy4gDQpUaGV5IGFyZSBhbGwgb3ZlciB0
aGUgZG9jLiBUbyBtYWtlIGl0IGNsZWFyLCBncm91cGluZyB0aGVtIGluIGEgc2VjdGlvbiBtYXkg
aGVscC4gQW5vdGhlciBpZGVhIGlzIHRvIGhhdmUgUmVxdWlyZW1lbnQgc3ViLXNlY3Rpb25zIHBl
ciB0b3BpYy4NCg0KICAgIA0KICAgID4gDQogICAgPuKAnCAgIEluIGNhc2Ugb2YgbUxEUCwgYSBM
ZWFmLVBFIGNhbiBkZWNpZGUgdG8gam9pbiB0aGUgUDJNUCBMU1AgYXQgYW55DQogICAgPiAgIHRp
bWU7IHdoZXJlYXMgaW4gdGhlIGNhc2Ugb2YgUlNWUC1URSwgdGhlIFAyTVAgTFNQIGlzIHNldCB1
cCBieQ0KICAgID50aGUNCiAgICA+ICAgUi1QRSwgZ2VuZXJhbGx5IGF0IHRoZSBpbml0aWFsIHNl
cnZpY2UgcHJvdmlzaW9uaW5nIHRpbWUuIEl0DQogICAgPnNob3VsZA0KICAgID4gICBiZSBub3Rl
ZCB0aGF0IGxvY2FsIHBvbGljeSBjYW4gb3ZlcnJpZGUgYW55IGRlY2lzaW9uIHRvIGpvaW4sIGFk
ZA0KICAgID5vcg0KICAgID4gICBwcnVuZSBleGlzdGluZyBvciBuZXcgTC1QRShzKSBmcm9tIHRo
ZSB0cmVlLiBJbiBhbnkgY2FzZSwgdGhlIFBXDQogICAgPiAgIHNldHVwIGNhbiBpZ25vcmUgdGhl
c2UgZGlmZmVyZW5jZXMsIGFuZCBzaW1wbHkgYXNzdW1lIHRoYXQgdGhlDQogICAgPlAyTVANCiAg
ICA+ICAgUFNOIExTUCBpcyBhdmFpbGFibGUgd2hlbiBuZWVkZWQNCiAgICA+4oCcDQogICAgPlF1
aXRlIGNvbXBsZXggdG8gZm9sbG93LiBNaXNzaW5nIHRvIOKAnHdoeeKAnSAvIGV4cGxhbmF0aW9u
Lg0KICAgIA0KICAgIFN1cmUgSSBjYW4gY2xhcmlmeSB0aGlzIGEgbGl0dGxlIG1vcmUsIHdpbGwg
cmVtb3ZlIHNvbWUgc2VudGVuY2VzIA0KICAgIFRoYXQgbWFrZSBpdCBjb25mdXNpbmcsIHdlIGFy
ZSBzaW1wbHkgaGVyZSBkaWZmZXJlbnRpYXRpbmcgbUxEUCBMU1AgZnJvbQ0KICAgIHAybXAgTFNQ
IHcvIFJTVlAtVEUgYW5kIHNheWluZyB0aGF0IFBXIHNldHVwIGlzIGFnbm9zdGljIG9mIHRoZSB0
cmFuc3BvcnQgDQogICAgcDJtcCBMU1Agc2V0dXAuDQogICAgDQogICAgPiANCiAgICA+4oCcVGhl
IExEUCBsaWJlcmFsIGxhYmVsIHJldGVudGlvbiBtb2RlIGlzIHVzZWTigJwNCiAgICA+QW5vdGhl
ciByZXF1aXJlbWVudOKApiBpcyB0aGF0IGEgTUFZLCBTSE9VTEQsIE1VU1Q/DQogICAgDQogICAg
SSB3aWxsIGNoYW5nZSBpdCB0byBhIE1VU1QuDQogICAgDQogICAgPiANCiAgICA+4oCcSW4gdGhp
cyBjYXNlLCBhIFBXIHN0YXR1cyBtZXNzYWdlIHdpdGggc3RhdHVzDQogICAgPiAgIGNvZGUgb2Yg
MHgwMDAwMDAwOCAoTG9jYWwgUFNOLWZhY2luZyBQVyAoaW5ncmVzcykgUmVjZWl2ZSBGYXVsdCkN
CiAgICA+TVVTVA0KICAgID4gICBhbHNvIGJlIHNlbnQgdG8gdGhlIFItUEXigJwNCiAgICA+IA0K
ICAgID5Ib3c/IFRoZSBMLVBFIGZhaWxzIHRvIGpvaW4gdGhlIFAyTVAgUFNOIExTUC4NCiAgICAN
CiAgICBDb3JyZWN0IHRoZSBMLVBFIGhhdmUgdG8gc2lnbmFsIHRoaXMgZmFpbHVyZSB0byB0aGUg
cm9vdCBQRS4NCg0KPFBhdHJpY2U+IHF1ZXN0aW9uIHJlbWFpbnMsIGhvdz8gSWYgTC1QRSBmYWls
cyB0byBqb2luIHRoZSBMU1AsIFBXIHdpbGwgYmUgZG93bi4gSG93IGNhbiBpdCBzaWduYWxzIHRo
ZSBmYWlsdXJlIHRvIHJvb3QgUEU/DQogICAgDQogICAgPiANCiAgICA+U2VjdGlvbiAyLjINCiAg
ICA+4oCcICAgTm90ZSB0aGF0IHNpbmNlIHRoZSBMRFAgbGFiZWwgbWFwcGluZyBtZXNzYWdlIGlz
IG9ubHkgc2VudCBieSB0aGUNCiAgICA+Ui0NCiAgICA+ICAgUEUgdG8gYWxsIHRoZSBMLVBFcywg
aXQgaXMgbm90IHBvc3NpYmxlIHRvIG5lZ290aWF0ZSBhbnkgaW50ZXJmYWNlDQogICAgPiAgIHBh
cmFtZXRlcnMu4oCcDQogICAgPldoeSBpcyB0aGF0IG5vdGUgdGhlcmU/IElzIHRoYXQgYWxyZWFk
eSBiZWVuIG1lbnRpb25lZCBwcmV2aW91c2x5Lg0KICAgIA0KICAgIFRoaXMgaXMgdGhlIG9ubHkg
cmVmZXJlbmNlIGluIHRoZSBkb2N1bWVudC4NCg0KPFBhdHJpY2U+IEZvcmdvdCBteSB0aG91Z2h0
cyBvbiB0aGF0IG9uZS4NCiAgICANCiAgICA+RmlnLjQgbXVzdCAgYmUgbW92ZWQgdG8gcHJvcGVy
IGluIHRoZSB0ZXh0IE9SIGNyZWF0ZSAyIHN1YnNlY3Rpb24gaW4NCiAgICA+Mi4yDQogICAgDQog
ICAgU29ycnkgZGlkbuKAmXQgZ2V0IHdoYXQgeW91IG1lYW4gaGVyZT8gQ2FuIHlvdSBlbGFib3Jh
dGU/DQoNCjxQYXRyaWNlPiBTb3JyeSDigKZMZXQgbWUgdHJ5IGFnYWluLiDigJxQMlAgUFcgRG93
bnN0cmVhbSBGRUMgRWxlbWVudOKAnS4gSSB0aGluayB5b3Ugc2hvdWxkIGhhdmUgYSBzZWN0aW9u
IGp1c3Qgb24gdGhhdCB0b3BpYy4gQWN0dWFsbHksIG1heWJlIHlvdSBjYW4gY3JlYXRlIGEgc3Vi
c2VjdGlvbiBmb3IgZWFjaCBkaWZmZXJlbnQgRkVDIGV4cGxhaW5lZCBpbiB0aGUgZG9jdW1lbnQu
IA0KICAgIA0KICAgID4gDQogICAgPuKAnEFzIHN1Y2gsIFBXIHN0YXR1cyBuZWdvdGlhdGlvbiBw
cm9jZWR1cmUNCiAgICA+ICAgZGVzY3JpYmVkIGluIFtSRkM0NDQ3YmlzXSBpcyBub3QgYXBwbGlj
YWJsZSB0byBQMk1QIFBXLiBBIG5vZGUNCiAgICA+TVVTVA0KICAgID4gICBOT1QgY2xhaW0gdG8g
YmUgIFAyTVAgUFcgY2FwYWJsZSBieSBzZW5kaW5nIGEgTERQIFAyTVAgUFcNCiAgICA+Q2FwYWJp
bGl0eQ0KICAgID4gICBUTFYgIGlmIGl0IGlzIG5vdCBhbHNvIGNhcGFibGUgb2YgaGFuZGxpbmcg
UFcgc3RhdHVz4oCcDQogICAgPiANCiAgICA+U2hvdWxkIGEgbm9kZSBzZW5kIExEUCBQMk1QIFBX
IENhcGFiaWxpdHkgVExWIG9yIG5vdD8gTm90IHdlbGwgZXhwbGFpbg0KICAgIA0KICAgIFdoYXQg
aXMgc2FpZCBoZXJlLCB0aGF0IHlvdSBjYW7igJl0IGJlIFAyTVAgUFcgY2FwYWJsZSB3aXRob3V0
IGJlaW5nIFBXIHN0YXR1cyBjYXBhYmxlLg0KICAgIE5vdCBzdXJlIGhvdyB0byBtYWtlIGl0IGNs
ZWFyZXIuDQoNCjxQYXRyaWNlPiByaWdodOKApiBJIG11c3QgaGF2ZSBiZWVuIHRpcmVkLiBUb28g
bWFueSBOT1QgDQogICAgDQogICAgPg0KICAgID4gDQogICAgPlRoZXJlIGlzIHNvbWUgcmVmZXJl
bmNlIHRvIExTUiBpbiB0aGUgdGV4dCB3aGVyZSB0aGUgbWFqb3IgcGFydCB1c2UNCiAgICA+dGhl
IHdvcmRpbmcg4oCcbm9kZeKAnS4NCiAgICANCiAgICBJIHdpbGwgbWFrZSBhbGwgY29uc2lzdGVu
dCwgYW5kIHVzZSBMU1IgaW5zdGVhZCBvZiBub2RlLg0KICAgIA0KICAgIFRoYW5rcywNCiAgICAN
CiAgICBTYW1pDQogICAgPiANCiAgICA+Tml0czogDQogICAgPk4vQQ0KICAgID4gDQogICAgPlJl
Z2FyZHMsDQogICAgPlBhdHJpY2UgQnJpc3NldHRlDQogICAgPg0KICAgID4NCiAgICA+DQogICAg
Pg0KICAgIA0KDQo=


From nobody Mon May 15 09:09:42 2017
Return-Path: <julian.reschke@gmx.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 E41AE12EAC6; Mon, 15 May 2017 09:09:40 -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, 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 2dcfzZW0ltGn; Mon, 15 May 2017 09:09:39 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 73EAE12EAC1; Mon, 15 May 2017 09:04:42 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.120.200]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MSdRI-1dblX92eSC-00RbhZ; Mon, 15 May 2017 18:04:31 +0200
Subject: Re: [art] ART Area Review for draft-ietf-calext-caldav-attachments-02
To: Ken Murchison <murch@andrew.cmu.edu>, IETF Discussion <ietf@ietf.org>, art@ietf.org
References: <c04f39e2-79d2-ab9d-59ab-26e51d7ab5fc@gmx.de> <81613220-989b-ca78-fe56-0ac7b19e7ce6@andrew.cmu.edu>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <b2a4924d-c7c9-b40b-484f-9fab48bfe5de@gmx.de>
Date: Mon, 15 May 2017 18:04:28 +0200
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: <81613220-989b-ca78-fe56-0ac7b19e7ce6@andrew.cmu.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:n/iUtHBhmkiQmU1oJS98CwbDX2IFXcMEh6e8+EZw0cb9BF/Ju11 p/y29Nt+LgQ+IMW/gmKmxmoxv2m2J/7PRv1Nmx8SzYUkShqN1JimVJn1WFcLHssYktmQGGc BweUazeMCw+67lKi+jmTFMZ3SOMqXBVEb7zswu650wCRrBK3V41OJv4hNVNJffWmuOvCFkv BzizMnmh4V8bTqx+LtW3A==
X-UI-Out-Filterresults: notjunk:1;V01:K0:49s4ZXwvPek=:ffhbn/sr94+FoQ7xDhqIpr cgYMLiCv6ldpDaREMpxTOx/HBFWFf3u4GM586eCq30c4m8tnuRlsje0nY+9MiELFhVbIp51H1 WPE2uwMLXcg4mE6oUgA8IpoxKRc4bkYcwOciAagmHPoMqFj/x7kpTBeI2c2viLOj5N3r/eqHc U3k5qkVByBGNZzYZIQ+2k/KTKjv3b5nKzQS9ALY4nM7TAkxk/kpLF2pPecmnT1uU4tRNXfpze r7dEOL/lfyT84phuLh0kWbAlB7lc+Jxo1qnBtZT2S338ej+twpuiP8Em5AYSPzgveogFwoooW vBLbxqfHjvGZ/o55EoP6TSPxenYYWID75qQzOQYUCfTWU6dv6FLozQrMztfkYWYwBmtlVhPuw qVH8RIVJdlMtUkcsa5ok3YQQ5DfgVYWF6vLgCEmdZn2cl3WOr8p8d6GosdpAi3PWJnqAnHS9J EHYC9IKdO2TgyjfL2DlMmCnE4BR+ttf5O/S6UbEtOZvCx27bIOvEbmb4wXAy8Zc4tr65DolrJ rBAObbjkzKKgvwRjnFpNlI9J4WUmGuN+dysA27aI/hU8ET3ytvb2tjsiYrwci3CVG/03Z0yTv CxP4xt+lhRkabMhdEev+uIXCyUSsoc7ulwxYvCKueHpgxYwPrNWxcwXOLW0g66PUCG0I+FSIf j+mCZ37luMK3URH9HLF8p8K+/aPbFZLmK72Tww/YcDBmE988/OK0s+XfMR5c4/iLobmYpLc+3 PjRdtrna3BBuJsu2JlAjPHDPWMjckpp55USlSc0k9EiNU2mecFq+hePij1ML5wgwik0GtTv2N M6V4bJ4
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vHulvhNCf0_0lDUIrxV3mMhUw44>
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, 15 May 2017 16:09:41 -0000

On 2017-05-15 16:03, Ken Murchison wrote:
> Hi Julian,
>
> Thanks for the review.  Comments inline.
>
>
> On 05/14/2017 10:23 AM, Julian Reschke wrote:
>> Reviewer: Julian Reschke
>> Review result: Not Ready
>>
>> Document: draft-ietf-calext-caldav-attachments-02
>> IETF LC End Date: 2017-05-14
>> IESG Telechat date: 2017-05-25
>>
>> This document describes attachment handling in CalDAV (WebDAV based
>> calendaring).
>>
>> The mechanism described by this document is essential RPCish, using
>> HTTP POST for tunneling. It will work in practice, but it definitively
>> isn't state of the art in IETF protocols, in particular in an
>> otherwise WebDAV/CalDAV-based ecosystem.
>>
>> Major issues:
>>
>> The main issue with this specification is that it
>>
>> 1) models operations on attachments as POST operations, where the
>> actual type of operation is specified using a query parameter, instead
>> of using the HTTP methods POST, PUT, and DELETE.
>
> The resource being acted upon is an actual calendar resource, which is
> already in place.  The attachments are meta-data associated with one or

Only for creation of the attachment. Once is has been created, it should 
have its own URI, and the usual HTTP methods should be applicable.

> more calendar resources, which is why a POST is used on the calendar
> resource to manipulate an attachment.  Can you explain how you would
> envision different HTTP methods be used to add/update/delete an
> attachment associated with a calendar resource?

For adding, I would define an HTTP resource that can be posted to. It 
could be discovered through a WebDAV property.

>> 2) hardwires specific query strings into the protocol, violating a
>> MUST level requirement in BCP 190 (see
>> https://tools.ietf.org/html/rfc7320#section-2.4):
>>
>>    Applications MUST NOT directly specify the syntax of queries, as this
>>    can cause operational difficulties for deployments that do not
>>    support a particular form of a query.  For example, a site may wish
>>    to support an application using "static" files that do not support
>>    query parameters.
>
> Which part(s) of the query syntax MUST not be specified?  The entire
> thing?  Just the keywords?  Did RFC 7808 get this wrong, or is URI
> templating ok?

I'm not familiar with 7808. URI templates are superior than hardwiring 
everything for sure. We just shouldn't enforce specific URI templates - 
the server should be able to specify them, clients would need to 
discover them.


>> Re 1) this is even called out specifically in Sections 3.8 (update)
>> and 3.9 (remove), but it's not clear at all why that is the case.
>>
>> Re 2) Part of the hard-wiring could be avoided by using different HTTP
>> methods for the different actions. The other parameters could be made
>> discoverable using URIs / URI templates, exposed as WebDAV properties,
>> as is the case in RFC 5995.
>
> As above, can you explain how different HTTP methods would be used where
> the target of the add/update/remove operation is an existing calendar
> resource?
> ...

(see above)

>> 5.1. Cal-Managed-ID Response Header Field
>>
>> This doesn't seem to address the points listed in
>> <https://greenbytes.de/tech/webdav/rfc7231.html#considerations.for.new.header.fields>
>> (and it wouldn't be needed if the attachment would be modeled as an
>> HTTP resource whose values could be reported back in a Location header
>> field upon creation).
>
> Can parameters be added to a Location header field (it doesn't appear
> so), or are you suggesting that the managed-id value be encoded in the
> URI-reference value?

I suggest that the attachment *is* a HTTP resource, thus has it's own URI.

>> Minor issues:
>>
>> 3.12.4.  Processing Time
>>
>>    Clients can expect servers to take a while to respond to POST
>>    requests that include large attachment bodies.  Servers SHOULD use
>>    the "102 (Processing)" interim response defined in Section 10.1 of
>>    [RFC2518] to keep the client connection alive if the POST request
>>    will take significant time to complete.
>>
>> While discussing the new code 103 in the HTTP WG, we considered
>> interop problems with existing code that doesn't handle 1xx status
>> codes at all, or had problems with status codes other than 100. I
>> personally support use of new 1xx status codes, but it would be good
>> to hear whether the WG considered deployment problems when making this
>> a SHOULD-level requirement.
>
> Existing implementations of this CalDAV extension all seem to handle 1xx
> status codes.

I'm more concerned about HTTP libraries and intermediaries. See, for 
instance, <http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8170305>.

Best regards, Julian


From nobody Mon May 15 16:42:05 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 E9D21129BE0; Mon, 15 May 2017 16:41:51 -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-oauth-native-apps.all@ietf.org, ietf@ietf.org, oauth@ietf.org
Subject: Genart last call review of draft-ietf-oauth-native-apps-10
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149489171188.11868.13336890952697460283@ietfa.amsl.com>
Date: Mon, 15 May 2017 16:41:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/H9NaDYeuQMgkvGFPp0QZvIaa3QY>
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, 15 May 2017 23:41:52 -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-oauth-native-apps-10
Reviewer: Elwyn Davies
Review Date: 2017-05-15
IETF LC End Date: 2017-05-16
IESG Telechat date: 2017-05-25

Summary: Almost ready.  A couple of simple minor issues could do with
addressing.

Major issues:
None.

Minor issues:
s3: "browser":  The browser that acts as the Oauth user-agent is
conflated with the user's choice of default browser.  Firstly this is
not something that is discussed in RFC 6749.  Secondly, the concept of
'default browser' would normally be thought of by users as the browser
that is used to display the content associated with hyperlinks rather
than providing Oauth services.  I suggest that the implication in the
body of the draft that 'the browser' is the user selected or system
selected default browser needs to be at least discussed explicitly
rather than buried in the terminology definitions in s3.  I wonder
whether ths connection is something that should be made by a separate
OS setting or a setting in each native app rather than conflated with
the default browser.  The term "designated browser" might be useful.
In all cases there might be secuity implications if a bad actor could
subvert the designated browser setting.

s8.1, Requirement of use of PKCE in some cases:  This strict
requirement really needs to be introduced in the body of the
discussion rather than buried in the seurity considerations.

Nits/editorial comments: 

General: s/i.e./i.e.,/ (3 places)

Title and Abstract: s/apps/applications/g  (uses before we get to
terminology in s3)

s1, para 1:  Suggest the following to make it clear that the
definition is in RFC 6749 rather than here.
OLD:
 The OAuth 2.0 [RFC6749] authorization framework documents two
approaches in Section 9 for native apps to interact with the
authorization endpoint: an embedded user-agent, and an external user-
agent.
NEW:
The OAuth 2.0 [RFC6749] authorization framework defines "native
applications" in Section 9 of RFC 6749 (see also Section 3 below) and
documents two approaches by whch they can interact with the
authorization endpoint: an embedded user-agent, and an external
user-agent. 
END 

s1, para 2: s/apps/applications/(2places) .  For second case: s/native
apps/native applications (shortened to "native apps" or just "apps"
hereafter)/

s3, "native app": s/app/application/g in the definition.  After that
in the document "[native] app" is fine except for the definitions
mentioned in the next comment. Worth repeating the link to Section 9
of RFC 6749.

s3, All definitions after "app"; s/app/application/g in the
definitions as these are not restricted to (native) apps as defined
here.

s3, "embedded user-agent": s/modify/modifyng/

s4, last para: s/emcompasses/encompasses/

s4, last para: s/inter-process/inter-app/ (since this term is
defined)

s4, last para: Might be worth pointing to the 'SHOULD' about client
type assumptions in s2.1 of RFC 6749 withe reference to servers that
do make assumptions.

s4.1, para below figure 1: s/system browser/browser/ (or maybe
"designated browser").

s5, paras 1 and  2: Reword to clarify and remove 'we gain' usage (not
allowed in RFCs):
OLD:
   Just as URIs are used for OAuth 2.0 [RFC6749] on the web to
initiate
   the authorization request and return the authorization response to
   the requesting website, URIs can be used by native apps to
initiate
   the authorization request in the device's browser and return the
   response to the requesting native app.

   By applying the same principles from the web to native apps, we
gain
   benefits seen on the web, like the usability of a single sign-on
   session and the security of a separate authentication context.  It
   also reduces the implementation complexity by reusing similar
flows
   as the web, and increases interoperability by relying on
standards-
   based web flows that are not specific to a particular platform.
NEW:
   Just as URIs are used for OAuth 2.0 [RFC6749] in the HTTP protocol
on the web to initiate
   the authorization request and return the authorization response to
   the requesting website, URIs can be used by native apps to
initiate
   the authorization request in the device's browser and return the
   response to the requesting native app.

   By extending the techniques from the web to native apps, the
   benefits gained in the web context will also be reaped when using 
   OAuth with native apps; benefits include the usability of a single
sign-on
   session and the security of a separate authentication context.  Use
of
   the techniques also reduces implementation complexity by reusing
similar flows
   to those employed on the web, and increases interoperability by
relying on standards-
   based web flows that are not specific to a particular platform.
END

s5, para 3: Suggest prefixing this para with: "To conform to this best
practise," - the MUST is not derived from RFC 6749.

s7.1, last para: s/URI like it/URI as it/; s/like normal/as it would
normally/

s7.2, next to last para:
OLD:
Due to this reason, they SHOULD be used over the other redirect
choices for native apps where possible.
NEW:
For this reason, they SHOULD be used in preference to the other
redirect options for native apps where possible.
END

s7.2, last para: s/it REQUIRED/it is REQUIRED/

s8.1, para 2: Need to expand acronym PKCE at first use (currently
expanded in para 4).

s8.1, para 4: s/sends data/send data/

s8.2: It would be more consistent with RFC 6749 to refer to "Implicit
Flow" as "Implicit Grant authorization flow" at least for the title
and first occurrence.   The second and third occurrences in para 1
should s/Implicit Flow/implicit flow/ for consistency with para 2.

s8.2, para 2: s/code flow/Authorization Code Grant flow/

s8.3, last para: Is a reminder to choose the 'right' type of IP
literal (IPv4 or v6) desirable?  Doing an address lookup on
"localhost" presumably tells you which one to use! [perhaps?]

s8.7, para 4: s/like/such as/

s8.8; need to expand CSRF (Cross Site Request Forgery) and maybe
explain a it how CSRGF and the cross-app case are related




From nobody Mon May 15 19:39:38 2017
Return-Path: <john@jlc.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 663DC12422F for <ietf@ietfa.amsl.com>; Mon, 15 May 2017 19:39:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Level: 
X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 B46plIhtyZvA for <ietf@ietfa.amsl.com>; Mon, 15 May 2017 19:39:35 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 382E71294B7 for <ietf@ietf.org>; Mon, 15 May 2017 19:36:41 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 336CF9097F8; Mon, 15 May 2017 22:36:41 -0400 (EDT)
Date: Mon, 15 May 2017 22:36:41 -0400
From: John Leslie <john@jlc.net>
To: Mark Andrews <marka@isc.org>
Cc: John Leslie <john@jlc.net>, IETF Discussion <ietf@ietf.org>
Subject: Re: Registration for remote participation
Message-ID: <20170516023641.GV56980@verdi>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <20170515131240.GR56980@verdi> <20170515141839.C95CD6EB9E9A@rock.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170515141839.C95CD6EB9E9A@rock.dv.isc.org>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3yiEX64vOdrjIdCibKbb4kd374I>
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, 16 May 2017 02:39:37 -0000

Mark Andrews <marka@isc.org> wrote:
> In message <20170515131240.GR56980@verdi>, John Leslie writes:
>> IETF Chair <chair@ietf.org> wrote:
>>> 
>>> To join a session, participants would be asked to input the
>>> registration ID.
>> 
>> These "registration IDs" are hard to remember. That's why I joined so
>> many sessions "without rugistration ID".
> 
> When you need to registration ID to participate you will
> record it,

   Post-it note on the screen, no doubt...

> look it in the registration email

   Often there are 100 spams I haven't finished dealing with...

> or recover it.

   How?

> 	IETF 97 confirmation for Mr. Mark P Andrews
> 	Registration Type: Remote Participant 
> 	Your registration number is 97XXXXXXXX 

   I suppose that's "easy enough" assuming I've found the email (on the
same computer I'm using for remote attendance) and can cut&paste. I must
be getting too old to participate in IETF weeks if I ever fail...

>>> The same email-based facility that is currently available to retrieve
>>> a forgotten registration ID would continue to be available.

   Believe it or not, I haven't used that recently...

>> This is not practical unless you allow joining enough before the start
>> of session to complete the process.
> 
> The session are open well before the workig group actually starts.

   I've found that time to be variable: sometimes less than two minutes...

>>> The cookie-based ???Remember me??? option would also still be available.
>> 
>>    Would you believe some of us avoid cookies?

   (Of course, I never avoid the physical cookies when I'm physically
present!)

>>> Other options for authentication (leveraging a user-chosen password or
>>> datatracker credentials) might be explored further in the future.
>> 
>> I strongly advise considering them before disallowing registration
>> without registration ID.

BTW, it's not unusual (for me, anyway) to join different sessions from
different computers, not all of which will have all the cookies.

   If you really want to make it harder to join an individual session
(or re-join after a MeetEcho glitch, for that matter), I probably
can't stop you; but I won't consider it a reasonable trade-off for
collecting some information you've already collected that same day.

   Perhaps you'll find volunteers to man the help-lines for folks having
trouble joining sessions...

--
John Leslie <john@jlc.net>


From nobody Mon May 15 19:40:14 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 61111129B02 for <ietf@ietfa.amsl.com>; Mon, 15 May 2017 19:40:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.821
X-Spam-Level: 
X-Spam-Status: No, score=-0.821 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=B0L0+iid; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=PWIK+APF
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9W2qvEmktkSb for <ietf@ietfa.amsl.com>; Mon, 15 May 2017 19:40:09 -0700 (PDT)
Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F3E912EB0C for <ietf@ietf.org>; Mon, 15 May 2017 19:37:12 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.nyi.internal (Postfix) with ESMTP id CB34D1013; Mon, 15 May 2017 22:37:11 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Mon, 15 May 2017 22:37:11 -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=bNYDG4rCMQEMUzxJfZ PfRW8b59un3zCXgdIuuIKE+CY=; b=B0L0+iidDtl556GNj8lTfoVLWeIMSiqjG7 lLK6ljDVRNMnu3pTQ7Wsv0RAYIh5moFx+8uRDXxGi+fYZtp7e6zNr2s1PFMXo+6c z3l7KFDgMlhHSTLOPO0aUIJLtqy7eaJ/vPIzCpuerJgCUMHFqbLyv9yTKT9wpwFz cMaY0X+GSoJNNrXZzEcolnB1XjG8l/F54Z95H1Sl0i1ZDx1TwRhItXohugZUNtLS xMn+rASdmUzx/xdEoFIrJm2x/JET/YO4bSVUxoTPkqkwXG41ONzdjlqaMhcsc4W1 9PQfVAWAEGyWvNejsYv4DxkSDvAtuUhftprLWxAOO5z3+8KcXMDA==
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=bNYDG4rCMQEMUzxJfZPfRW8b59un3zCXgdIuuIKE+CY=; b=PWIK+APF VIuzPisQ5g7WQS5qJIAHz/PLesstJ6/Ch7FERYFUEP/3n1hmIiWFOOmdGdnG0Frx 5rO/uzKFeNF0hfVo/fdlQnYcJVFnGPoNdJ0tcR79pqhdyewBAgkV4mHh3uIAnYWG r+NO6pBCqm1e/4DywscVFETa7qDmk1RW1+WitOQgQKhavuugPXOTy4+Et3gxZpiN Qphioc4Vano83SJ3HYXs5YBBPV6o5ledBdQuCf0rYPhWJI6Lx0EDlmPQQFUJUAF1 Skr8hI7nQSh8jxwnyHUFytjIzO01xfNo32rtcCIJjJJKr0bGlJ6kIhXaPx+W3c4W Rb6ciSY+WpjYug==
X-ME-Sender: <xms:12UaWQgHljDCSVHeDlI-zRhnGySIxxaiWCbBuQ9ZI02IFruijXUflA>
X-Sasl-enc: DfccsY0LWlpsNBfGTxIHMJqGCY9OActNUz9IJpU5BUn/ 1494902230
Received: from [192.168.1.18] (cpe-124-189-96-43.gziz1.win.bigpond.net.au [124.189.96.43]) by mail.messagingengine.com (Postfix) with ESMTPA id 6E859249CC; Mon, 15 May 2017 22:37:10 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Last Call: <draft-nottingham-rfc5988bis-05.txt> (Web Linking) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <09EA3303-8F65-4FDE-8303-8C2AD9B8B897@mnot.net>
Date: Tue, 16 May 2017 12:37:06 +1000
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <280366F3-ECDA-44A2-820A-33FD5965EAFD@mnot.net>
References: <588716b3-161c-62ac-e5a9-a04c86f13e86@gmx.de> <704BC987-1ED0-4E59-A803-0B4013A86F03@mnot.net> <c81eb293-f443-8d61-bd82-b7c2902e4426@gmx.de> <09EA3303-8F65-4FDE-8303-8C2AD9B8B897@mnot.net>
To: "Julian F. Reschke" <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lZ_sd4h9mm6poWb9lxVtTMHznoU>
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, 16 May 2017 02:40:12 -0000

> On 15 May 2017, at 11:42 am, Mark Nottingham <mnot@mnot.net> wrote:
>=20
>>>>=20
>>>> 1.  Let "links" be an empty list.
>>>>=20
>>>> 2.  Create "link_strings" by splitting "field_value" on ","
>>>>     characters, excepting "," characters within quoted strings as =
per
>>>>=20
>>>> I have my doubts that people will be able to translate it into =
actually correct code. To detect whether something is inside a =
quoted-string essentially requires running a parser; the prose here =
suggests that this is not necessary.
>>>=20
>>> I reluctantly agree. I'll need to rework the algorithm to address =
this; please stand by.
>>=20
>> The only way to properly split list supporting field values is to =
parse them according to the grammar for the list items; I don't believe =
in the existence of a shortcut that actually works correctly. Suggesting =
otherwise IMHO will lead to broken implementations for certain edge =
cases.
>=20
> +1
>=20
>=20
>>>> It also should mention that there might be multiple instances of =
field_value.
>>>=20
>>> The algorithm is for parsing a single field-value...
>>=20
>> Yes, but should we tell the audience that they need to parse *all* =
field values, and combine the result?
>=20
> OK.

This is what I currently have:
  https://gist.github.com/mnot/2fb569e7303dbcdde8b27cb7a404a648

I need to get some more eyeballs onto it to make sure it's correct (or =
at least reasonable). Reviews appreciated.=20

Cheers,


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


From nobody Mon May 15 23:37:15 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 66D1D12EB5B; Mon, 15 May 2017 23:37:13 -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 4fFGe3KOTwkH; Mon, 15 May 2017 23:37:11 -0700 (PDT)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40C17129B16; Mon, 15 May 2017 23:34:07 -0700 (PDT)
Received: by mail-oi0-x22a.google.com with SMTP id h4so13566805oib.3; Mon, 15 May 2017 23:34: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=Y+sMk1WeIPkGlEWtiLenezqkzrtjt+ltbLeQWGFNyvE=; b=HwabV3LAsS/u8Kyxonye4aKd5doQ1eh/OWe44+FJTMugNtIchvcCJIfh8Am9Sj/YDy ObiKwGiclwntItL8f1b0kHDoo/bS7WI1eD54hvCna6+9p4TvqS10e9JihSMRyldtT1B+ 24xLxJhFAKPky9ZgvdeuP5eQEctg8wLw9Zdn+pG4fJXnNg3cLo+nP5PxgtpXsNsWesSl 99OkJj5YisjZEyU5uLeY+E32PRx/nZJcA63wSx7DLjNDrj7k03+cmrxAVL6F75QOa2Pn 68WAUpxye5aepbMFH2I4eUQZ8I86YQeU3rChGRuXxlDFT434+B/CLBUo3uesT7KszF/v aB/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=Y+sMk1WeIPkGlEWtiLenezqkzrtjt+ltbLeQWGFNyvE=; b=of2fm8VJ998qV7mBhAbr+upBuRiJ6wLMzuFMOBmgTZ3qPP+euqMOxTNwnn69kGhnch fVa0dHsVFOyKvRUlF5dzG8BVXUsOFq1mCHK+pB+I4dg1T8n6HtFaFQpdOx7qE+XUThLj sgv1GooxvKlsZFrdghJBz8Uk3efyWdYpjnIwdkf65qDDiAktNdw+WWT+iZMzQQV4oc6b iku8HvOZ/dtsYOLt3s/BSkAycYcu4XcoNgA+/jfPI/gHlF4lw6pbxjeqBMXJnT6NuN3g jIyjGUMMmeihp10PecbIoIf4iDu+K0wU8wXvzKpx0yWnBMSrK41mN9SiXcJ1SMpQQsP6 IpXg==
X-Gm-Message-State: AODbwcAZG+ct3n7O4Ar7L9XttgVxFiETR7LURUOzwv1lGckw06Uy77Bs ZLAVSPMbz5+yrUdSmFyZpTUWXErnLg==
X-Received: by 10.202.77.73 with SMTP id a70mr934615oib.126.1494916446681; Mon, 15 May 2017 23:34:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.231.132 with HTTP; Mon, 15 May 2017 23:33:46 -0700 (PDT)
In-Reply-To: <149454198305.16624.16060763979327626869@ietfa.amsl.com>
References: <149454198305.16624.16060763979327626869@ietfa.amsl.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Tue, 16 May 2017 14:33:46 +0800
Message-ID: <CAA=duU2ZnMTSR-Rcsm+7XEE_xBWrnUVMOg=4RhpFfvde6M+CvA@mail.gmail.com>
Subject: Re: Secdir last call review of draft-ietf-pals-vpls-pim-snooping-05
To: Russ Housley <housley@vigilsec.com>
Cc: secdir@ietf.org, draft-ietf-pals-vpls-pim-snooping.all@ietf.org,  IETF Discussion <ietf@ietf.org>, "pals@ietf.org" <pals@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c17d42c60417054f9e5b66"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3VzgMXBfn6PLG8-1xqbTZxYQPaM>
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, 16 May 2017 06:37:13 -0000

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

Russ,

Thanks for your review!

Cheers,
Andy

On Fri, May 12, 2017 at 6:33 AM, Russ Housley <housley@vigilsec.com> wrote:

> Reviewer: Russ Housley
> Review result: Has Nits
>
> I 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 authors, document editors, and WG chairs should
> treat these comments just like any other IETF Last Call comments.
>
> Document: draft-ietf-pals-vpls-pim-snooping-05
> Reviewer: Russ Housley
> Review Date: 2016-05-11
> IETF LC End Date: 2017-05-19
> IESG Telechat date: Unknown
>
> Summary: Has Nits
>
> I did not review the state machines in detail.  I assume that others
> that are far more familiar with PIM have done s detailed review of
> them.
>
>
> No Major Concerns
>
>
> Minor Concerns
>
> Section 1 says:
>
>    In that case, the PW related concept/procedures are not
>    applicable and that's all.
>
> I am not sure what you are trying to tell the implementer.
> Please clarify.
>
> Section 1.3 includes: "rpt : Rendezvous Point", and Section 2.3
> includes: "Rendezvous Points (RP)".  Please pick one and use it
> throughout.
>
> In Section 2.2, please add a reference for the "split-horizon rule
> for mesh PWs" or add a pointer to the section where it is discussed
> further in this document.
>
> A better heading for Section 2.3.2 would be "IPv4 and IPv6".
>
>
> Nits
>
> Please change the language that makes reference to other "draft",
> such
> as: "As stated in the VPLS Multicast Requirements draft ...".  This
> wording leads to changes by the RFC Editor, so it is better to use a
> word like "document".
>
> Please change "J/P messages" to "Join/Prune messages" throughout the
> document.
>
> The document uses both "learned" and "learnt".  If there is a
> difference
> to the reader, it was too subtle for me to figure out.  If they are
> the
> same, please pick one.
>
> In Section 1.1, rewording would add clarity:
>
>    Depending on how the control messages are handled
>    (transparently flooded, selectively forwarded, aggregated), the
>    procedure/process may be called Snooping or proxy in different
>    contexts.
>
> I suggest:
>
>    Depending on whether the control messages are
>    transparently flooded, selectively forwarded, or aggregated, the
>    processing may be called Snooping or proxy in different contexts.
>
> Section 2.3 says:
>
>    However, the PE does not need to have any routing tables like as
>    required in PIM multicast routing.
>
> Please correct.  I think you are trying to say:
>
>    However, the PE does not need any routing tables like those
>    required in PIM multicast routing.
>
> Section 4.2.1 says:
>
>    Note that the differences apply only to PIM Join/Prune messages.
> PIM
>    Hello messages are snooped and flooded in all cases.
>
> Wouldn't it be more clear to consume the same number of lines and add
> this information to the table.
>
> In Section 2.7 the document uses PIM-BIDIR and BIDIR-PIM, and they
> seem
> have the same meaning.  Please pick one.
>
>
>

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

<div dir=3D"ltr">Russ,<div><br></div><div>Thanks for your review!</div><div=
><br></div><div>Cheers,</div><div>Andy</div></div><div class=3D"gmail_extra=
"><br><div class=3D"gmail_quote">On Fri, May 12, 2017 at 6:33 AM, Russ Hous=
ley <span dir=3D"ltr">&lt;<a href=3D"mailto:housley@vigilsec.com" target=3D=
"_blank">housley@vigilsec.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">Reviewer: Russ Housley<br>
Review result: Has Nits<br>
<br>
I reviewed this document as part of the Security Directorate&#39;s<br>
ongoing<br>
effort to review all IETF documents being processed by the IESG.<br>
These<br>
comments were written primarily for the benefit of the Security Area<br>
Directors.=C2=A0 Document authors, document editors, and WG chairs should<b=
r>
treat these comments just like any other IETF Last Call comments.<br>
<br>
Document: draft-ietf-pals-vpls-pim-<wbr>snooping-05<br>
Reviewer: Russ Housley<br>
Review Date: 2016-05-11<br>
IETF LC End Date: 2017-05-19<br>
IESG Telechat date: Unknown<br>
<br>
Summary: Has Nits<br>
<br>
I did not review the state machines in detail.=C2=A0 I assume that others<b=
r>
that are far more familiar with PIM have done s detailed review of<br>
them.<br>
<br>
<br>
No Major Concerns<br>
<br>
<br>
Minor Concerns<br>
<br>
Section 1 says:<br>
<br>
=C2=A0 =C2=A0In that case, the PW related concept/procedures are not<br>
=C2=A0 =C2=A0applicable and that&#39;s all.<br>
<br>
I am not sure what you are trying to tell the implementer.<br>
Please clarify.<br>
<br>
Section 1.3 includes: &quot;rpt : Rendezvous Point&quot;, and Section 2.3<b=
r>
includes: &quot;Rendezvous Points (RP)&quot;.=C2=A0 Please pick one and use=
 it<br>
throughout.<br>
<br>
In Section 2.2, please add a reference for the &quot;split-horizon rule<br>
for mesh PWs&quot; or add a pointer to the section where it is discussed<br=
>
further in this document.<br>
<br>
A better heading for Section 2.3.2 would be &quot;IPv4 and IPv6&quot;.<br>
<br>
<br>
Nits<br>
<br>
Please change the language that makes reference to other &quot;draft&quot;,=
<br>
such<br>
as: &quot;As stated in the VPLS Multicast Requirements draft ...&quot;.=C2=
=A0 This<br>
wording leads to changes by the RFC Editor, so it is better to use a<br>
word like &quot;document&quot;.<br>
<br>
Please change &quot;J/P messages&quot; to &quot;Join/Prune messages&quot; t=
hroughout the<br>
document.<br>
<br>
The document uses both &quot;learned&quot; and &quot;learnt&quot;.=C2=A0 If=
 there is a<br>
difference<br>
to the reader, it was too subtle for me to figure out.=C2=A0 If they are<br=
>
the<br>
same, please pick one.<br>
<br>
In Section 1.1, rewording would add clarity:<br>
<br>
=C2=A0 =C2=A0Depending on how the control messages are handled<br>
=C2=A0 =C2=A0(transparently flooded, selectively forwarded, aggregated), th=
e<br>
=C2=A0 =C2=A0procedure/process may be called Snooping or proxy in different=
<br>
=C2=A0 =C2=A0contexts.<br>
<br>
I suggest:<br>
<br>
=C2=A0 =C2=A0Depending on whether the control messages are<br>
=C2=A0 =C2=A0transparently flooded, selectively forwarded, or aggregated, t=
he<br>
=C2=A0 =C2=A0processing may be called Snooping or proxy in different contex=
ts.<br>
<br>
Section 2.3 says:<br>
<br>
=C2=A0 =C2=A0However, the PE does not need to have any routing tables like =
as<br>
=C2=A0 =C2=A0required in PIM multicast routing.<br>
<br>
Please correct.=C2=A0 I think you are trying to say:<br>
<br>
=C2=A0 =C2=A0However, the PE does not need any routing tables like those<br=
>
=C2=A0 =C2=A0required in PIM multicast routing.<br>
<br>
Section 4.2.1 says:<br>
<br>
=C2=A0 =C2=A0Note that the differences apply only to PIM Join/Prune message=
s.<br>
PIM<br>
=C2=A0 =C2=A0Hello messages are snooped and flooded in all cases.<br>
<br>
Wouldn&#39;t it be more clear to consume the same number of lines and add<b=
r>
this information to the table.<br>
<br>
In Section 2.7 the document uses PIM-BIDIR and BIDIR-PIM, and they<br>
seem<br>
have the same meaning.=C2=A0 Please pick one.<br>
<br>
<br>
</blockquote></div><br></div>

--001a11c17d42c60417054f9e5b66--


From nobody Tue May 16 05:38:01 2017
Return-Path: <bwietf@bwijnen.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 7818412EB41; Tue, 16 May 2017 05:37:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Bert Wijnen <bwietf@bwijnen.net>
To: <yang-doctors@ietf.org>
Cc: draft-ietf-netconf-yang-push.all@ietf.org, ietf@ietf.org, netconf@ietf.org
Subject: Yangdoctors early review of draft-ietf-netconf-yang-push-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149493827145.11944.9758454721784881844@ietfa.amsl.com>
Date: Tue, 16 May 2017 05:37:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8mjlASwLK6aWsAI4KAnRRkwaXpk>
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, 16 May 2017 12:37:52 -0000

Reviewer: Bert Wijnen
Review result: On the Right Track


- last para of sect 3.5.
  This seems to me to make it difficult to create interoperable
  implementations. Or is there a way for a client to figure out what
  is or is not support, other than tryal and error?
- page 41:    

     /* YANG Parser Pyang crashing on the following syntax below

  So does the definition get skipped? Or what needs to happen here?

Consistency

- last bullet on page 7 talks about "YANG subtrees". I do not see that
term
  in netconf or yang documents. Those just talk about "subtrees".
Maybe I am
  not looking good enough?
- top of page 8 I see the words "xpath", "Xpath" and "XPath"
  is there a difference?

Nits

- you may want to check the reference/citation occurrences of
[subscribe]
  at several places it points to
     draft-ietf-netconf-yang-push-06#ref-subscribe
  whereas I think it intends to point to the [subscribe] in the
  normative references section
- first bullet on page 5:
     Enhancements to filters. Specifically the filter MUST at identify
at
     least one targeted yang
   s/at//  -- the first "at" seems superfluous
   plus, you are using capitalized MUST with out reference/citation
of
   RFC2119
- page 36:

    leaf dependency {
      type sn:subscription-id;
      description
        "Provides the Subscription ID of a parent subscription which
         has absolute priority should that parent have push updates
         ready to egress the publisher. In other words, there should
be
         no streaming of objects from the current subscription if of
         the parent has something ready to push.";
      reference
        "RFC-7540, section 5.3.1";
    }

     s/if of/if/ ??


From nobody Tue May 16 13:58:47 2017
Return-Path: <evoit@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 61AF512EC09; Tue, 16 May 2017 13:58:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 P-64R987PfFi; Tue, 16 May 2017 13:58:36 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AE2912EC73; Tue, 16 May 2017 13:53:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4500; q=dns/txt; s=iport; t=1494968039; x=1496177639; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=u2slkq/JndUfMd8dB7pcp2EIYxCVCe/w3dh7G9tdRS0=; b=fiqIIZRbmzlkrI9Px9Zh5X8clh89Ep43s/M1uIDTEyNS4D8KcMHTQKgw Lvip1mccs5lkrXLRmGO8fAR0l3uYKdZ8fFN7Jo55+7ycepurLa7n6aoIV uf1Y5fRfInJ8FgXo/K+pqUeZ7MfpBoaw09rnz+qNKHA/4wOrwkK5vio/j Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AyAQCbZRtZ/4UNJK1SChoBAQEBAgEBA?= =?us-ascii?q?QEIAQEBAYNVYoETg2WKGJFklXWCDy6FdgIahTU/GAECAQEBAQEBAWsohRgBAQE?= =?us-ascii?q?BAgEjEUUFCwIBCA4HBQIIAR0CAgIwFRACBAENDYoTCA6sSIImiwEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEYBYELhVSBXoMbhDuDOoJBHwWeCgGHG4t2kXSUQgEfOIE?= =?us-ascii?q?KcBWFPRyBY3uHMYENAQEB?=
X-IronPort-AV: E=Sophos;i="5.38,350,1491264000"; d="scan'208";a="246189445"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 16 May 2017 20:53:58 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id v4GKrwJk000798 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 16 May 2017 20:53:58 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 16 May 2017 16:53:57 -0400
Received: from xch-rtp-013.cisco.com ([64.101.220.153]) by XCH-RTP-013.cisco.com ([64.101.220.153]) with mapi id 15.00.1210.000; Tue, 16 May 2017 16:53:57 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Bert Wijnen <bwietf@bwijnen.net>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
CC: "draft-ietf-netconf-yang-push.all@ietf.org" <draft-ietf-netconf-yang-push.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>, "Waltermire, David A. (Fed)" <david.waltermire@nist.gov>
Subject: RE: Yangdoctors early review of draft-ietf-netconf-yang-push-06
Thread-Topic: Yangdoctors early review of draft-ietf-netconf-yang-push-06
Thread-Index: AQHSzkE9C/OO0NmevUiBbCVmGdSZbKH3ao5w
Date: Tue, 16 May 2017 20:53:57 +0000
Message-ID: <c955ae937b4142ac949c6f7876c40cc0@XCH-RTP-013.cisco.com>
References: <149493827145.11944.9758454721784881844@ietfa.amsl.com>
In-Reply-To: <149493827145.11944.9758454721784881844@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.56.228]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EojKjHQwYMSozWMfgwB2PDP2YGY>
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, 16 May 2017 20:58:39 -0000

SGkgQmVydCwNCg0KVGhhbmtzIHZlcnkgbXVjaCBmb3IgdGhlIHJldmlldy4gIFNvbWUgdGhvdWdo
dHMgaW4tbGluZS4uLg0KDQo+IEZyb206IEJlcnQgV2lqbmVuLCBNYXkgMTYsIDIwMTcgODozOCBB
TQ0KPiANCj4gUmV2aWV3ZXI6IEJlcnQgV2lqbmVuDQo+IFJldmlldyByZXN1bHQ6IE9uIHRoZSBS
aWdodCBUcmFjaw0KPiANCj4gDQo+IC0gbGFzdCBwYXJhIG9mIHNlY3QgMy41Lg0KPiAgIFRoaXMg
c2VlbXMgdG8gbWUgdG8gbWFrZSBpdCBkaWZmaWN1bHQgdG8gY3JlYXRlIGludGVyb3BlcmFibGUN
Cj4gICBpbXBsZW1lbnRhdGlvbnMuIE9yIGlzIHRoZXJlIGEgd2F5IGZvciBhIGNsaWVudCB0byBm
aWd1cmUgb3V0IHdoYXQNCj4gICBpcyBvciBpcyBub3Qgc3VwcG9ydCwgb3RoZXIgdGhhbiB0cnlh
bCBhbmQgZXJyb3I/DQoNCk1pbmltYWwgWFBBVEggc3ludGF4IHN1cHBvcnQgaXMgcmVhbGx5IGEg
c3Vic2NyaXB0aW9uIGluZGVwZW5kZW50IGlzc3VlLiAgQXQgdGhpcyB0aW1lLCBJIGFtIG5vdCBh
d2FyZSBvZiBhbnlvbmUgYXR0ZW1wdGluZyB0byBjb25zdHJhaW4gd2hpY2ggWFBBVEggY2FwYWJp
bGl0aWVzIHNob3VsZCBiZSB0aGUgbWluaW11bSBzZXQgZm9yIHRoZSBpbmR1c3RyeS4gIE9uZSBv
ZiB0aGUgcmVhc29ucyBpcyB0aGF0IGdvaW5nIHdpdGggYSBtaW5pbXVtIGNvbW1vbiBkZW5vbWlu
YXRvciBmb3IgYSBoaWdoIHZvbHVtZSBpbmZvcm1hdGlvbiBzZXQgIChsaWtlIHJvdXRpbmcgY2hh
bmdlcykgbWlnaHQgY29uc3RyYWluIHRoZSBhdmFpbGFiaWxpdHkgb2YgbG93IHZvbHVtZSwgaGln
aCB2YWx1ZSBmaWx0ZXJzIChsaWtlIGNvbmZpZ3VyYXRpb24gY2hhbmdlcykuICAgICBJIHdvdWxk
IHZlcnkgbXVjaCB3ZWxjb21lIHNvbWVvbmUgd2hvIHdhbnRlZCB0byBhdHRlbXB0IHdvcmsgaW4g
dGhpcyBhcmVhLiAgIEFzIERhdmlkIFdhbHRlcm1pcmUgc2FpZCB0byBtZSBvbiB0aGlzIHRvcGlj
IHRvZGF5LCBpdCBtaWdodCBiZSBwb3NzaWJsZSB0byBpZGVudGlmeSBhIG1pbmltdW0gWFBBVEgg
ZmlsdGVyIGNhcGFiaWxpdHkgc2V0IGZvciB2YXJpb3VzIHJvbGVzIGluIHRoZSBuZXR3b3JrIGVs
ZW1lbnQuICBCdXQgdGhpcyBpcyBub24tdHJpdmlhbCB3b3JrLg0KDQpGb3Igbm93LCBJIGFtIGFz
c3VtaW5nIGFueSB2ZW5kb3Igd2lsbCBiZSBhYmxlIHRvIGFydGljdWxhdGUgd2hhdCB0aGUgc3lu
dGF4IGNhcGFiaWxpdGllcyBhcmUgZm9yIHRoZWlyIHBsYXRmb3Jtcy4gIEFuZCB0aGV5IGNhbiBk
byBvdXRzaWRlIHRoZSBzdGFuZGFyZHMgYXJlbmEuICBBIGdvb2Qgd2F5IHRvIGRvIHRoaXMgd291
bGQgYmUgdG8gcHJlLXBvcHVsYXRlIGV4YW1wbGUgZmlsdGVycyBpbiB0aGUgImZpbHRlcnMiIG9i
amVjdHMuIA0KDQo+IC0gcGFnZSA0MToNCj4gDQo+ICAgICAgLyogWUFORyBQYXJzZXIgUHlhbmcg
Y3Jhc2hpbmcgb24gdGhlIGZvbGxvd2luZyBzeW50YXggYmVsb3cNCj4gDQo+ICAgU28gZG9lcyB0
aGUgZGVmaW5pdGlvbiBnZXQgc2tpcHBlZD8gT3Igd2hhdCBuZWVkcyB0byBoYXBwZW4gaGVyZT8N
Cg0KVGhlcmUgaXMgYSBjb21pbmcgaW4gcHlhbmcgMS43LjIgd2hpY2ggZml4ZXMgdGhlIGJ1Zy4u
LiAgICAgDQpodHRwczovL2dpdGh1Yi5jb20vbWJqNDY2OC9weWFuZy9pc3N1ZXMvMzAwIA0KDQpT
ZWUNCmh0dHBzOi8vZ2l0aHViLmNvbS9tYmo0NjY4L3B5YW5nL2NvbW1pdC9iODkxY2MzZGQzYTQ1
NDdmOWVkZGQ4Mzg4MmU5ODcyYmMyMDY2YzZkIA0KDQpBbGwgd2UgbmVlZCB0byBkbyBpcyBhd2Fp
dCB0aGUgbmV3IHZlcnNpb24uDQoNCj4gQ29uc2lzdGVuY3kNCj4gDQo+IC0gbGFzdCBidWxsZXQg
b24gcGFnZSA3IHRhbGtzIGFib3V0ICJZQU5HIHN1YnRyZWVzIi4gSSBkbyBub3Qgc2VlIHRoYXQg
dGVybQ0KPiAgIGluIG5ldGNvbmYgb3IgeWFuZyBkb2N1bWVudHMuIFRob3NlIGp1c3QgdGFsayBh
Ym91dCAic3VidHJlZXMiLg0KPiBNYXliZSBJIGFtDQo+ICAgbm90IGxvb2tpbmcgZ29vZCBlbm91
Z2g/DQoNCldpbGwgcmVtb3ZlIHRoZSB3b3JkIFlBTkcNCg0KPiAtIHRvcCBvZiBwYWdlIDggSSBz
ZWUgdGhlIHdvcmRzICJ4cGF0aCIsICJYcGF0aCIgYW5kICJYUGF0aCINCj4gICBpcyB0aGVyZSBh
IGRpZmZlcmVuY2U/DQoNCk5vLiAgV2lsbCBmaXguDQogDQo+IE5pdHMNCg0KTmljZSBjYXRjaGVz
LiAgV2lsbCBmaXggdGhlIGl0ZW1zIGJlbG93Lg0KDQpFcmljDQoNCj4gLSB5b3UgbWF5IHdhbnQg
dG8gY2hlY2sgdGhlIHJlZmVyZW5jZS9jaXRhdGlvbiBvY2N1cnJlbmNlcyBvZiBbc3Vic2NyaWJl
XQ0KPiAgIGF0IHNldmVyYWwgcGxhY2VzIGl0IHBvaW50cyB0bw0KPiAgICAgIGRyYWZ0LWlldGYt
bmV0Y29uZi15YW5nLXB1c2gtMDYjcmVmLXN1YnNjcmliZQ0KPiAgIHdoZXJlYXMgSSB0aGluayBp
dCBpbnRlbmRzIHRvIHBvaW50IHRvIHRoZSBbc3Vic2NyaWJlXSBpbiB0aGUNCj4gICBub3JtYXRp
dmUgcmVmZXJlbmNlcyBzZWN0aW9uDQo+IC0gZmlyc3QgYnVsbGV0IG9uIHBhZ2UgNToNCj4gICAg
ICBFbmhhbmNlbWVudHMgdG8gZmlsdGVycy4gU3BlY2lmaWNhbGx5IHRoZSBmaWx0ZXIgTVVTVCBh
dCBpZGVudGlmeSBhdA0KPiAgICAgIGxlYXN0IG9uZSB0YXJnZXRlZCB5YW5nDQo+ICAgIHMvYXQv
LyAgLS0gdGhlIGZpcnN0ICJhdCIgc2VlbXMgc3VwZXJmbHVvdXMNCj4gICAgcGx1cywgeW91IGFy
ZSB1c2luZyBjYXBpdGFsaXplZCBNVVNUIHdpdGggb3V0IHJlZmVyZW5jZS9jaXRhdGlvbiBvZg0K
PiAgICBSRkMyMTE5DQo+IC0gcGFnZSAzNjoNCj4gDQo+ICAgICBsZWFmIGRlcGVuZGVuY3kgew0K
PiAgICAgICB0eXBlIHNuOnN1YnNjcmlwdGlvbi1pZDsNCj4gICAgICAgZGVzY3JpcHRpb24NCj4g
ICAgICAgICAiUHJvdmlkZXMgdGhlIFN1YnNjcmlwdGlvbiBJRCBvZiBhIHBhcmVudCBzdWJzY3Jp
cHRpb24gd2hpY2gNCj4gICAgICAgICAgaGFzIGFic29sdXRlIHByaW9yaXR5IHNob3VsZCB0aGF0
IHBhcmVudCBoYXZlIHB1c2ggdXBkYXRlcw0KPiAgICAgICAgICByZWFkeSB0byBlZ3Jlc3MgdGhl
IHB1Ymxpc2hlci4gSW4gb3RoZXIgd29yZHMsIHRoZXJlIHNob3VsZCBiZQ0KPiAgICAgICAgICBu
byBzdHJlYW1pbmcgb2Ygb2JqZWN0cyBmcm9tIHRoZSBjdXJyZW50IHN1YnNjcmlwdGlvbiBpZiBv
Zg0KPiAgICAgICAgICB0aGUgcGFyZW50IGhhcyBzb21ldGhpbmcgcmVhZHkgdG8gcHVzaC4iOw0K
PiAgICAgICByZWZlcmVuY2UNCj4gICAgICAgICAiUkZDLTc1NDAsIHNlY3Rpb24gNS4zLjEiOw0K
PiAgICAgfQ0KPiANCj4gICAgICBzL2lmIG9mL2lmLyA/Pw0KDQo=


From nobody Tue May 16 14:26:09 2017
Return-Path: <andy@yumaworks.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 5EB2A128E19 for <ietf@ietfa.amsl.com>; Tue, 16 May 2017 14:25:53 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-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 KxLxEPxBIDoz for <ietf@ietfa.amsl.com>; Tue, 16 May 2017 14:25:51 -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 E73B91300E8 for <ietf@ietf.org>; Tue, 16 May 2017 14:21:00 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id d127so132839899wmf.0 for <ietf@ietf.org>; Tue, 16 May 2017 14:21:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QJBPGGScf4Hl/T9vJnxyao+xYgIba6mCsemEPpFz1mg=; b=AQzBt5tMELZZjuX422uXmLoc/MTudaXKMe8He29SzDGGF+gxLlE+oC5OKpz4KCpfbV jyzS+2AVi95md7G/H+FQ9gQTJn5F6tLJuc5OPfilE9vG1FkbnlG2q32nR7syZhLxTHlC KeKK3aF//kh9p79zN2Fay/qtF33djeFMR3Yoz3xetFcToeuWffpeL9rO3gdlV/V7Vz+S sc6ZDqKaMMrTIyp1yeUagcQ2sS4aN//K6Vq/6GtlkLD6acBnhthnhzqalgglcgO/vEmy eB/+ehLNeLFJnv94jI/ZZKdk7HRItWxaaJOCWY3XkksCzSnEmr1Bbo0ODBNgWG8VpaHM BMXQ==
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=QJBPGGScf4Hl/T9vJnxyao+xYgIba6mCsemEPpFz1mg=; b=MDvoX8yWG+Tto8GzY/xfJR0Pnz4ZoarXCZAQPgL7FzZWOPEVyutUn1w3uVDIGDCOSH mIp5SCkOfGU/Bu0BF5N0OZMSMv49XIF18eKq1QjvJYpsc7OagX8J5r4hc5XH8rvSTr95 pLvEjYG/SRTwGdxP34qvRrv80m/qfO/kJAeR3JW+kCbs8E8fkP6cYzWnWr0koeWSNs/i m/LZkWZ17uUgqPUuLMWW1h2cys2sr6g3dF6Iv/DYwwvAS9H2qdJDBJbWdKAkybOxBwB3 9LnDxGnkC6M1YMFxadCqxyz4HuKuFlsaroyOBiDykH1MxHouCi3BolmRliz15+Ur4i/P i4Kw==
X-Gm-Message-State: AODbwcB8eycu5ykljbFVyubw3wuhGLT1HzMdsnCdAVMP1ttAHnulz/Uz t9T5I7JW20Boys79OU7lbNXhjtLfGktH
X-Received: by 10.28.142.70 with SMTP id q67mr308055wmd.99.1494969659375; Tue, 16 May 2017 14:20:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.155.2 with HTTP; Tue, 16 May 2017 14:20:58 -0700 (PDT)
In-Reply-To: <c955ae937b4142ac949c6f7876c40cc0@XCH-RTP-013.cisco.com>
References: <149493827145.11944.9758454721784881844@ietfa.amsl.com> <c955ae937b4142ac949c6f7876c40cc0@XCH-RTP-013.cisco.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Tue, 16 May 2017 14:20:58 -0700
Message-ID: <CABCOCHQg9vPCKdmbqbzWf2CM86b0LBS-XM9jARcbCpNDixAkPg@mail.gmail.com>
Subject: Re: Yangdoctors early review of draft-ietf-netconf-yang-push-06
To: "Eric Voit (evoit)" <evoit@cisco.com>
Cc: Bert Wijnen <bwietf@bwijnen.net>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>,  "draft-ietf-netconf-yang-push.all@ietf.org" <draft-ietf-netconf-yang-push.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>,  "netconf@ietf.org" <netconf@ietf.org>, "Waltermire, David A. (Fed)" <david.waltermire@nist.gov>
Content-Type: multipart/alternative; boundary="001a114429847f6ee5054faabf09"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ty2ZNjkNxy580kyV0tCL-QRd7IY>
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, 16 May 2017 21:25:53 -0000

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

On Tue, May 16, 2017 at 1:53 PM, Eric Voit (evoit) <evoit@cisco.com> wrote:

> Hi Bert,
>
> Thanks very much for the review.  Some thoughts in-line...
>
> > From: Bert Wijnen, May 16, 2017 8:38 AM
> >
> > Reviewer: Bert Wijnen
> > Review result: On the Right Track
> >
> >
> > - last para of sect 3.5.
> >   This seems to me to make it difficult to create interoperable
> >   implementations. Or is there a way for a client to figure out what
> >   is or is not support, other than tryal and error?
>
> Minimal XPATH syntax support is really a subscription independent issue.
> At this time, I am not aware of anyone attempting to constrain which XPATH
> capabilities should be the minimum set for the industry.  One of the
> reasons is that going with a minimum common denominator for a high volume
> information set  (like routing changes) might constrain the availability of
> low volume, high value filters (like configuration changes).     I would
> very much welcome someone who wanted to attempt work in this area.   As
> David Waltermire said to me on this topic today, it might be possible to
> identify a minimum XPATH filter capability set for various roles in the
> network element.  But this is non-trivial work.
>
> For now, I am assuming any vendor will be able to articulate what the
> syntax capabilities are for their platforms.  And they can do outside the
> standards arena.  A good way to do this would be to pre-populate example
> filters in the "filters" objects.
>
>

This is not going to be interoperable or easy to debug to find out what a
vendor supports.
Sec 3.5, para 3 & 4 about XPath implementations should be replaced. The
text should say a node-set result
MUST be generated or the result is the empty node-set.
Some XPath constructs SHOULD be avoided, as specified in sec 4.5 of RFC
6087.

Filters need to be well-defined so clients can actually use them.
The same syntax as a NETCONF <get> XPath filter should be used here.
New filters  should be defined if they are really needed.


Andy

> - page 41:
> >
> >      /* YANG Parser Pyang crashing on the following syntax below
> >
> >   So does the definition get skipped? Or what needs to happen here?
>
> There is a coming in pyang 1.7.2 which fixes the bug...
> https://github.com/mbj4668/pyang/issues/300
>
> See
> https://github.com/mbj4668/pyang/commit/b891cc3dd3a4547f9eddd83882e987
> 2bc2066c6d
>
> All we need to do is await the new version.
>
> > Consistency
> >
> > - last bullet on page 7 talks about "YANG subtrees". I do not see that
> term
> >   in netconf or yang documents. Those just talk about "subtrees".
> > Maybe I am
> >   not looking good enough?
>
> Will remove the word YANG
>
> > - top of page 8 I see the words "xpath", "Xpath" and "XPath"
> >   is there a difference?
>
> No.  Will fix.
>
> > Nits
>
> Nice catches.  Will fix the items below.
>
> Eric
>
> > - you may want to check the reference/citation occurrences of [subscribe]
> >   at several places it points to
> >      draft-ietf-netconf-yang-push-06#ref-subscribe
> >   whereas I think it intends to point to the [subscribe] in the
> >   normative references section
> > - first bullet on page 5:
> >      Enhancements to filters. Specifically the filter MUST at identify at
> >      least one targeted yang
> >    s/at//  -- the first "at" seems superfluous
> >    plus, you are using capitalized MUST with out reference/citation of
> >    RFC2119
> > - page 36:
> >
> >     leaf dependency {
> >       type sn:subscription-id;
> >       description
> >         "Provides the Subscription ID of a parent subscription which
> >          has absolute priority should that parent have push updates
> >          ready to egress the publisher. In other words, there should be
> >          no streaming of objects from the current subscription if of
> >          the parent has something ready to push.";
> >       reference
> >         "RFC-7540, section 5.3.1";
> >     }
> >
> >      s/if of/if/ ??
>
>

--001a114429847f6ee5054faabf09
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, May 16, 2017 at 1:53 PM, Eric Voit (evoit) <span dir=3D"ltr">&l=
t;<a href=3D"mailto:evoit@cisco.com" target=3D"_blank">evoit@cisco.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">Hi Bert,<br>
<br>
Thanks very much for the review.=C2=A0 Some thoughts in-line...<br>
<br>
&gt; From: Bert Wijnen, May 16, 2017 8:38 AM<br>
&gt;<br>
&gt; Reviewer: Bert Wijnen<br>
&gt; Review result: On the Right Track<br>
&gt;<br>
&gt;<br>
&gt; - last para of sect 3.5.<br>
&gt;=C2=A0 =C2=A0This seems to me to make it difficult to create interopera=
ble<br>
&gt;=C2=A0 =C2=A0implementations. Or is there a way for a client to figure =
out what<br>
&gt;=C2=A0 =C2=A0is or is not support, other than tryal and error?<br>
<br>
Minimal XPATH syntax support is really a subscription independent issue.=C2=
=A0 At this time, I am not aware of anyone attempting to constrain which XP=
ATH capabilities should be the minimum set for the industry.=C2=A0 One of t=
he reasons is that going with a minimum common denominator for a high volum=
e information set=C2=A0 (like routing changes) might constrain the availabi=
lity of low volume, high value filters (like configuration changes).=C2=A0 =
=C2=A0 =C2=A0I would very much welcome someone who wanted to attempt work i=
n this area.=C2=A0 =C2=A0As David Waltermire said to me on this topic today=
, it might be possible to identify a minimum XPATH filter capability set fo=
r various roles in the network element.=C2=A0 But this is non-trivial work.=
<br>
<br>
For now, I am assuming any vendor will be able to articulate what the synta=
x capabilities are for their platforms.=C2=A0 And they can do outside the s=
tandards arena.=C2=A0 A good way to do this would be to pre-populate exampl=
e filters in the &quot;filters&quot; objects.<br>
<br></blockquote><div><br></div><div><br></div><div>This is not going to be=
 interoperable or easy to debug to find out what a vendor supports.</div><d=
iv>Sec 3.5, para 3 &amp; 4 about XPath implementations should be replaced. =
The text should say a node-set result</div><div>MUST be generated or the re=
sult is the empty node-set.</div><div>Some XPath constructs SHOULD be avoid=
ed, as specified in sec 4.5 of RFC 6087.<br></div><div><br></div><div>Filte=
rs need to be well-defined so clients can actually use them.</div><div>The =
same syntax as a NETCONF &lt;get&gt; XPath filter should be used here.</div=
><div>New filters =C2=A0should be defined if they are really needed.</div><=
div><br></div><div><br></div><div>Andy</div><div><br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">
&gt; - page 41:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 /* YANG Parser Pyang crashing on the following syn=
tax below<br>
&gt;<br>
&gt;=C2=A0 =C2=A0So does the definition get skipped? Or what needs to happe=
n here?<br>
<br>
There is a coming in pyang 1.7.2 which fixes the bug...<br>
<a href=3D"https://github.com/mbj4668/pyang/issues/300" rel=3D"noreferrer" =
target=3D"_blank">https://github.com/mbj4668/<wbr>pyang/issues/300</a><br>
<br>
See<br>
<a href=3D"https://github.com/mbj4668/pyang/commit/b891cc3dd3a4547f9eddd838=
82e9872bc2066c6d" rel=3D"noreferrer" target=3D"_blank">https://github.com/m=
bj4668/<wbr>pyang/commit/<wbr>b891cc3dd3a4547f9eddd83882e987<wbr>2bc2066c6d=
</a><br>
<br>
All we need to do is await the new version.<br>
<br>
&gt; Consistency<br>
&gt;<br>
&gt; - last bullet on page 7 talks about &quot;YANG subtrees&quot;. I do no=
t see that term<br>
&gt;=C2=A0 =C2=A0in netconf or yang documents. Those just talk about &quot;=
subtrees&quot;.<br>
&gt; Maybe I am<br>
&gt;=C2=A0 =C2=A0not looking good enough?<br>
<br>
Will remove the word YANG<br>
<br>
&gt; - top of page 8 I see the words &quot;xpath&quot;, &quot;Xpath&quot; a=
nd &quot;XPath&quot;<br>
&gt;=C2=A0 =C2=A0is there a difference?<br>
<br>
No.=C2=A0 Will fix.<br>
<br>
&gt; Nits<br>
<br>
Nice catches.=C2=A0 Will fix the items below.<br>
<br>
Eric<br>
<br>
&gt; - you may want to check the reference/citation occurrences of [subscri=
be]<br>
&gt;=C2=A0 =C2=A0at several places it points to<br>
&gt;=C2=A0 =C2=A0 =C2=A0 draft-ietf-netconf-yang-push-<wbr>06#ref-subscribe=
<br>
&gt;=C2=A0 =C2=A0whereas I think it intends to point to the [subscribe] in =
the<br>
&gt;=C2=A0 =C2=A0normative references section<br>
&gt; - first bullet on page 5:<br>
&gt;=C2=A0 =C2=A0 =C2=A0 Enhancements to filters. Specifically the filter M=
UST at identify at<br>
&gt;=C2=A0 =C2=A0 =C2=A0 least one targeted yang<br>
&gt;=C2=A0 =C2=A0 s/at//=C2=A0 -- the first &quot;at&quot; seems superfluou=
s<br>
&gt;=C2=A0 =C2=A0 plus, you are using capitalized MUST with out reference/c=
itation of<br>
&gt;=C2=A0 =C2=A0 RFC2119<br>
&gt; - page 36:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0leaf dependency {<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0type sn:subscription-id;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0description<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;Provides the Subscription ID of=
 a parent subscription which<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 has absolute priority should that pa=
rent have push updates<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ready to egress the publisher. In ot=
her words, there should be<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 no streaming of objects from the cur=
rent subscription if of<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 the parent has something ready to pu=
sh.&quot;;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0reference<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;RFC-7540, section 5.3.1&quot;;<=
br>
&gt;=C2=A0 =C2=A0 =C2=A0}<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 s/if of/if/ ??<br>
<br>
</blockquote></div><br></div></div>

--001a114429847f6ee5054faabf09--


From nobody Tue May 16 14:34:12 2017
Return-Path: <evoit@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 8104E12955A; Tue, 16 May 2017 14:34:00 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 XDuiikG3DFSm; Tue, 16 May 2017 14:33:57 -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 027D112EC3E; Tue, 16 May 2017 14:28:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20176; q=dns/txt; s=iport; t=1494970140; x=1496179740; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=zWJRNjwrhVo83kizFbBsSvCtnFkB/d5bHqTBhcvlPMg=; b=Fnbp08OnLDQFhd+xKoWmhEJ8vQiwK7KsFtxU4bHlueDCDxlULMwuBN72 HK5tZCU68iPlMxObn+whpulnpEYaIZeJKu51HA7WS23ayk0brES+7MmqG OgWp/P7R36kxCqVPPL6uAXCXR/lmV8tsxC+i5oTgNRiwsheOV60KRPLvT Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CHAwAPbhtZ/4QNJK1SChkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYJuZ2KBDAeDZYoYkWSQPYU4gg8uhTw6AhqFNT8YAQIBAQEBAQE?= =?us-ascii?q?BayiFGAEBAQECASMKTAULAgEIFQ8BGgMCAgIwFBECBA4FCIoTCA6sRIImiwYBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAQEYBYZfgV6DG4Q7XoJcgkEfBZ4KAYcbi3aRdJR?= =?us-ascii?q?CAR84gQpwFYU9HIFjdgWHMYENAQEB?=
X-IronPort-AV: E=Sophos;i="5.38,350,1491264000";  d="scan'208,217";a="422426281"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 16 May 2017 21:28:59 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v4GLSwX6012034 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 16 May 2017 21:28:59 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 16 May 2017 17:28:58 -0400
Received: from xch-rtp-013.cisco.com ([64.101.220.153]) by XCH-RTP-013.cisco.com ([64.101.220.153]) with mapi id 15.00.1210.000; Tue, 16 May 2017 17:28:58 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Andy Bierman <andy@yumaworks.com>
CC: Bert Wijnen <bwietf@bwijnen.net>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>, "draft-ietf-netconf-yang-push.all@ietf.org" <draft-ietf-netconf-yang-push.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>, "Waltermire, David A. (Fed)" <david.waltermire@nist.gov>
Subject: RE: Yangdoctors early review of draft-ietf-netconf-yang-push-06
Thread-Topic: Yangdoctors early review of draft-ietf-netconf-yang-push-06
Thread-Index: AQHSzkE9C/OO0NmevUiBbCVmGdSZbKH3ao5wgABQnAD//725UA==
Date: Tue, 16 May 2017 21:28:57 +0000
Message-ID: <df333dcd802a427dabdebbb506d550a0@XCH-RTP-013.cisco.com>
References: <149493827145.11944.9758454721784881844@ietfa.amsl.com> <c955ae937b4142ac949c6f7876c40cc0@XCH-RTP-013.cisco.com> <CABCOCHQg9vPCKdmbqbzWf2CM86b0LBS-XM9jARcbCpNDixAkPg@mail.gmail.com>
In-Reply-To: <CABCOCHQg9vPCKdmbqbzWf2CM86b0LBS-XM9jARcbCpNDixAkPg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.56.228]
Content-Type: multipart/alternative; boundary="_000_df333dcd802a427dabdebbb506d550a0XCHRTP013ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/M-DLQoJW8iqnzGoz5Eew1GdPpvA>
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, 16 May 2017 21:34:01 -0000

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

RnJvbTogQW5keSBCaWVybWFuLCBNYXkgMTYsIDIwMTcgNToyMSBQTQ0KDQpPbiBUdWUsIE1heSAx
NiwgMjAxNyBhdCAxOjUzIFBNLCBFcmljIFZvaXQgKGV2b2l0KSA8ZXZvaXRAY2lzY28uY29tPG1h
aWx0bzpldm9pdEBjaXNjby5jb20+PiB3cm90ZToNCkhpIEJlcnQsDQoNClRoYW5rcyB2ZXJ5IG11
Y2ggZm9yIHRoZSByZXZpZXcuICBTb21lIHRob3VnaHRzIGluLWxpbmUuLi4NCg0KPiBGcm9tOiBC
ZXJ0IFdpam5lbiwgTWF5IDE2LCAyMDE3IDg6MzggQU0NCj4NCj4gUmV2aWV3ZXI6IEJlcnQgV2lq
bmVuDQo+IFJldmlldyByZXN1bHQ6IE9uIHRoZSBSaWdodCBUcmFjaw0KPg0KPg0KPiAtIGxhc3Qg
cGFyYSBvZiBzZWN0IDMuNS4NCj4gICBUaGlzIHNlZW1zIHRvIG1lIHRvIG1ha2UgaXQgZGlmZmlj
dWx0IHRvIGNyZWF0ZSBpbnRlcm9wZXJhYmxlDQo+ICAgaW1wbGVtZW50YXRpb25zLiBPciBpcyB0
aGVyZSBhIHdheSBmb3IgYSBjbGllbnQgdG8gZmlndXJlIG91dCB3aGF0DQo+ICAgaXMgb3IgaXMg
bm90IHN1cHBvcnQsIG90aGVyIHRoYW4gdHJ5YWwgYW5kIGVycm9yPw0KDQpNaW5pbWFsIFhQQVRI
IHN5bnRheCBzdXBwb3J0IGlzIHJlYWxseSBhIHN1YnNjcmlwdGlvbiBpbmRlcGVuZGVudCBpc3N1
ZS4gIEF0IHRoaXMgdGltZSwgSSBhbSBub3QgYXdhcmUgb2YgYW55b25lIGF0dGVtcHRpbmcgdG8g
Y29uc3RyYWluIHdoaWNoIFhQQVRIIGNhcGFiaWxpdGllcyBzaG91bGQgYmUgdGhlIG1pbmltdW0g
c2V0IGZvciB0aGUgaW5kdXN0cnkuICBPbmUgb2YgdGhlIHJlYXNvbnMgaXMgdGhhdCBnb2luZyB3
aXRoIGEgbWluaW11bSBjb21tb24gZGVub21pbmF0b3IgZm9yIGEgaGlnaCB2b2x1bWUgaW5mb3Jt
YXRpb24gc2V0ICAobGlrZSByb3V0aW5nIGNoYW5nZXMpIG1pZ2h0IGNvbnN0cmFpbiB0aGUgYXZh
aWxhYmlsaXR5IG9mIGxvdyB2b2x1bWUsIGhpZ2ggdmFsdWUgZmlsdGVycyAobGlrZSBjb25maWd1
cmF0aW9uIGNoYW5nZXMpLiAgICAgSSB3b3VsZCB2ZXJ5IG11Y2ggd2VsY29tZSBzb21lb25lIHdo
byB3YW50ZWQgdG8gYXR0ZW1wdCB3b3JrIGluIHRoaXMgYXJlYS4gICBBcyBEYXZpZCBXYWx0ZXJt
aXJlIHNhaWQgdG8gbWUgb24gdGhpcyB0b3BpYyB0b2RheSwgaXQgbWlnaHQgYmUgcG9zc2libGUg
dG8gaWRlbnRpZnkgYSBtaW5pbXVtIFhQQVRIIGZpbHRlciBjYXBhYmlsaXR5IHNldCBmb3IgdmFy
aW91cyByb2xlcyBpbiB0aGUgbmV0d29yayBlbGVtZW50LiAgQnV0IHRoaXMgaXMgbm9uLXRyaXZp
YWwgd29yay4NCg0KRm9yIG5vdywgSSBhbSBhc3N1bWluZyBhbnkgdmVuZG9yIHdpbGwgYmUgYWJs
ZSB0byBhcnRpY3VsYXRlIHdoYXQgdGhlIHN5bnRheCBjYXBhYmlsaXRpZXMgYXJlIGZvciB0aGVp
ciBwbGF0Zm9ybXMuICBBbmQgdGhleSBjYW4gZG8gb3V0c2lkZSB0aGUgc3RhbmRhcmRzIGFyZW5h
LiAgQSBnb29kIHdheSB0byBkbyB0aGlzIHdvdWxkIGJlIHRvIHByZS1wb3B1bGF0ZSBleGFtcGxl
IGZpbHRlcnMgaW4gdGhlICJmaWx0ZXJzIiBvYmplY3RzLg0KVGhpcyBpcyBub3QgZ29pbmcgdG8g
YmUgaW50ZXJvcGVyYWJsZSBvciBlYXN5IHRvIGRlYnVnIHRvIGZpbmQgb3V0IHdoYXQgYSB2ZW5k
b3Igc3VwcG9ydHMuDQpTZWMgMy41LCBwYXJhIDMgJiA0IGFib3V0IFhQYXRoIGltcGxlbWVudGF0
aW9ucyBzaG91bGQgYmUgcmVwbGFjZWQuIFRoZSB0ZXh0IHNob3VsZCBzYXkgYSBub2RlLXNldCBy
ZXN1bHQNCk1VU1QgYmUgZ2VuZXJhdGVkIG9yIHRoZSByZXN1bHQgaXMgdGhlIGVtcHR5IG5vZGUt
c2V0Lg0KU29tZSBYUGF0aCBjb25zdHJ1Y3RzIFNIT1VMRCBiZSBhdm9pZGVkLCBhcyBzcGVjaWZp
ZWQgaW4gc2VjIDQuNSBvZiBSRkMgNjA4Ny4NCg0KPGV2b2l0PiBtYWtlcyBzZW5zZS4gIFRoZSBy
ZWZlcmVuY2UgdG8gUkZDIDYwODcgaXMgYSBnb29kIG9uZQ0KDQpGaWx0ZXJzIG5lZWQgdG8gYmUg
d2VsbC1kZWZpbmVkIHNvIGNsaWVudHMgY2FuIGFjdHVhbGx5IHVzZSB0aGVtLg0KVGhlIHNhbWUg
c3ludGF4IGFzIGEgTkVUQ09ORiA8Z2V0PiBYUGF0aCBmaWx0ZXIgc2hvdWxkIGJlIHVzZWQgaGVy
ZS4NCg0KPGV2b2l0PiBZZXMuICBXZSBhbHdheXMgYXJlIGFpbWluZyB3aXRoIGVxdWl2YWxlbmNl
IHRvIDxnZXQ+DQoNCk5ldyBmaWx0ZXJzICBzaG91bGQgYmUgZGVmaW5lZCBpZiB0aGV5IGFyZSBy
ZWFsbHkgbmVlZGVkLg0KDQo8ZXZvaXQ+IE92ZXIgdGltZSwgbmV3IGZpbHRlciB0eXBlcyBjYW4g
YmUgYXVnbWVudGVkIGluIGFzIGlkZW50aXRpZXMuICBBZ2FpbiwgPGdldD4gZXF1aXZhbGVuY2Ug
aXMgdGhlIGdvYWwuICBDZXJ0YWlubHkgYWRkaW5nIHRoZW0gaW50byB0aGUgbW9kZWwgaGVyZSBp
cyB0aGUgZWFzeSBwYXJ0IHZzIGRpbWVuc2lvbmluZyB3aGF0IGEgcGxhdGZvcm0gY2FuIHN1cHBv
cnQuDQoNCkVyaWMNCg0KQW5keQ0KDQo+IC0gcGFnZSA0MToNCj4NCj4gICAgICAvKiBZQU5HIFBh
cnNlciBQeWFuZyBjcmFzaGluZyBvbiB0aGUgZm9sbG93aW5nIHN5bnRheCBiZWxvdw0KPg0KPiAg
IFNvIGRvZXMgdGhlIGRlZmluaXRpb24gZ2V0IHNraXBwZWQ/IE9yIHdoYXQgbmVlZHMgdG8gaGFw
cGVuIGhlcmU/DQoNClRoZXJlIGlzIGEgY29taW5nIGluIHB5YW5nIDEuNy4yIHdoaWNoIGZpeGVz
IHRoZSBidWcuLi4NCmh0dHBzOi8vZ2l0aHViLmNvbS9tYmo0NjY4L3B5YW5nL2lzc3Vlcy8zMDAN
Cg0KU2VlDQpodHRwczovL2dpdGh1Yi5jb20vbWJqNDY2OC9weWFuZy9jb21taXQvYjg5MWNjM2Rk
M2E0NTQ3ZjllZGRkODM4ODJlOTg3MmJjMjA2NmM2ZA0KDQpBbGwgd2UgbmVlZCB0byBkbyBpcyBh
d2FpdCB0aGUgbmV3IHZlcnNpb24uDQoNCj4gQ29uc2lzdGVuY3kNCj4NCj4gLSBsYXN0IGJ1bGxl
dCBvbiBwYWdlIDcgdGFsa3MgYWJvdXQgIllBTkcgc3VidHJlZXMiLiBJIGRvIG5vdCBzZWUgdGhh
dCB0ZXJtDQo+ICAgaW4gbmV0Y29uZiBvciB5YW5nIGRvY3VtZW50cy4gVGhvc2UganVzdCB0YWxr
IGFib3V0ICJzdWJ0cmVlcyIuDQo+IE1heWJlIEkgYW0NCj4gICBub3QgbG9va2luZyBnb29kIGVu
b3VnaD8NCg0KV2lsbCByZW1vdmUgdGhlIHdvcmQgWUFORw0KDQo+IC0gdG9wIG9mIHBhZ2UgOCBJ
IHNlZSB0aGUgd29yZHMgInhwYXRoIiwgIlhwYXRoIiBhbmQgIlhQYXRoIg0KPiAgIGlzIHRoZXJl
IGEgZGlmZmVyZW5jZT8NCg0KTm8uICBXaWxsIGZpeC4NCg0KPiBOaXRzDQoNCk5pY2UgY2F0Y2hl
cy4gIFdpbGwgZml4IHRoZSBpdGVtcyBiZWxvdy4NCg0KRXJpYw0KDQo+IC0geW91IG1heSB3YW50
IHRvIGNoZWNrIHRoZSByZWZlcmVuY2UvY2l0YXRpb24gb2NjdXJyZW5jZXMgb2YgW3N1YnNjcmli
ZV0NCj4gICBhdCBzZXZlcmFsIHBsYWNlcyBpdCBwb2ludHMgdG8NCj4gICAgICBkcmFmdC1pZXRm
LW5ldGNvbmYteWFuZy1wdXNoLTA2I3JlZi1zdWJzY3JpYmUNCj4gICB3aGVyZWFzIEkgdGhpbmsg
aXQgaW50ZW5kcyB0byBwb2ludCB0byB0aGUgW3N1YnNjcmliZV0gaW4gdGhlDQo+ICAgbm9ybWF0
aXZlIHJlZmVyZW5jZXMgc2VjdGlvbg0KPiAtIGZpcnN0IGJ1bGxldCBvbiBwYWdlIDU6DQo+ICAg
ICAgRW5oYW5jZW1lbnRzIHRvIGZpbHRlcnMuIFNwZWNpZmljYWxseSB0aGUgZmlsdGVyIE1VU1Qg
YXQgaWRlbnRpZnkgYXQNCj4gICAgICBsZWFzdCBvbmUgdGFyZ2V0ZWQgeWFuZw0KPiAgICBzL2F0
Ly8gIC0tIHRoZSBmaXJzdCAiYXQiIHNlZW1zIHN1cGVyZmx1b3VzDQo+ICAgIHBsdXMsIHlvdSBh
cmUgdXNpbmcgY2FwaXRhbGl6ZWQgTVVTVCB3aXRoIG91dCByZWZlcmVuY2UvY2l0YXRpb24gb2YN
Cj4gICAgUkZDMjExOQ0KPiAtIHBhZ2UgMzY6DQo+DQo+ICAgICBsZWFmIGRlcGVuZGVuY3kgew0K
PiAgICAgICB0eXBlIHNuOnN1YnNjcmlwdGlvbi1pZDsNCj4gICAgICAgZGVzY3JpcHRpb24NCj4g
ICAgICAgICAiUHJvdmlkZXMgdGhlIFN1YnNjcmlwdGlvbiBJRCBvZiBhIHBhcmVudCBzdWJzY3Jp
cHRpb24gd2hpY2gNCj4gICAgICAgICAgaGFzIGFic29sdXRlIHByaW9yaXR5IHNob3VsZCB0aGF0
IHBhcmVudCBoYXZlIHB1c2ggdXBkYXRlcw0KPiAgICAgICAgICByZWFkeSB0byBlZ3Jlc3MgdGhl
IHB1Ymxpc2hlci4gSW4gb3RoZXIgd29yZHMsIHRoZXJlIHNob3VsZCBiZQ0KPiAgICAgICAgICBu
byBzdHJlYW1pbmcgb2Ygb2JqZWN0cyBmcm9tIHRoZSBjdXJyZW50IHN1YnNjcmlwdGlvbiBpZiBv
Zg0KPiAgICAgICAgICB0aGUgcGFyZW50IGhhcyBzb21ldGhpbmcgcmVhZHkgdG8gcHVzaC4iOw0K
PiAgICAgICByZWZlcmVuY2UNCj4gICAgICAgICAiUkZDLTc1NDAsIHNlY3Rpb24gNS4zLjEiOw0K
PiAgICAgfQ0KPg0KPiAgICAgIHMvaWYgb2YvaWYvID8/DQoNCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLm1zb25vcm1hbDAsIGxpLm1z
b25vcm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCglt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTIuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE4
DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
IixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0
eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7
fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBp
biAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rp
b24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1
bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEt
LVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzpp
ZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtl
bmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0i
cHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8ZGl2IHN0eWxlPSJib3JkZXI6
bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4w
cHQiPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWYiPkZyb206PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiBBbmR5IEJpZXJtYW4sIE1heSAx
NiwgMjAxNyA1OjIxIFBNPGJyPg0KPGJyPg0KPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIFR1ZSwgTWF5IDE2LCAyMDE3IGF0IDE6NTMgUE0sIEVy
aWMgVm9pdCAoZXZvaXQpICZsdDs8YSBocmVmPSJtYWlsdG86ZXZvaXRAY2lzY28uY29tIiB0YXJn
ZXQ9Il9ibGFuayI+ZXZvaXRAY2lzY28uY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+
DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0ND
QyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdp
bi1yaWdodDowaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDowaW47bWFyZ2luLXJpZ2h0OjBpbjttYXJnaW4tYm90dG9tOjEyLjBwdDttYXJnaW4tbGVm
dDoxNi44cHQiPg0KSGkgQmVydCw8YnI+DQo8YnI+DQpUaGFua3MgdmVyeSBtdWNoIGZvciB0aGUg
cmV2aWV3LiZuYnNwOyBTb21lIHRob3VnaHRzIGluLWxpbmUuLi48YnI+DQo8YnI+DQomZ3Q7IEZy
b206IEJlcnQgV2lqbmVuLCBNYXkgMTYsIDIwMTcgODozOCBBTTxicj4NCiZndDs8YnI+DQomZ3Q7
IFJldmlld2VyOiBCZXJ0IFdpam5lbjxicj4NCiZndDsgUmV2aWV3IHJlc3VsdDogT24gdGhlIFJp
Z2h0IFRyYWNrPGJyPg0KJmd0Ozxicj4NCiZndDs8YnI+DQomZ3Q7IC0gbGFzdCBwYXJhIG9mIHNl
Y3QgMy41Ljxicj4NCiZndDsmbmJzcDsgJm5ic3A7VGhpcyBzZWVtcyB0byBtZSB0byBtYWtlIGl0
IGRpZmZpY3VsdCB0byBjcmVhdGUgaW50ZXJvcGVyYWJsZTxicj4NCiZndDsmbmJzcDsgJm5ic3A7
aW1wbGVtZW50YXRpb25zLiBPciBpcyB0aGVyZSBhIHdheSBmb3IgYSBjbGllbnQgdG8gZmlndXJl
IG91dCB3aGF0PGJyPg0KJmd0OyZuYnNwOyAmbmJzcDtpcyBvciBpcyBub3Qgc3VwcG9ydCwgb3Ro
ZXIgdGhhbiB0cnlhbCBhbmQgZXJyb3I/PGJyPg0KPGJyPg0KTWluaW1hbCBYUEFUSCBzeW50YXgg
c3VwcG9ydCBpcyByZWFsbHkgYSBzdWJzY3JpcHRpb24gaW5kZXBlbmRlbnQgaXNzdWUuJm5ic3A7
IEF0IHRoaXMgdGltZSwgSSBhbSBub3QgYXdhcmUgb2YgYW55b25lIGF0dGVtcHRpbmcgdG8gY29u
c3RyYWluIHdoaWNoIFhQQVRIIGNhcGFiaWxpdGllcyBzaG91bGQgYmUgdGhlIG1pbmltdW0gc2V0
IGZvciB0aGUgaW5kdXN0cnkuJm5ic3A7IE9uZSBvZiB0aGUgcmVhc29ucyBpcyB0aGF0IGdvaW5n
IHdpdGggYSBtaW5pbXVtIGNvbW1vbg0KIGRlbm9taW5hdG9yIGZvciBhIGhpZ2ggdm9sdW1lIGlu
Zm9ybWF0aW9uIHNldCZuYnNwOyAobGlrZSByb3V0aW5nIGNoYW5nZXMpIG1pZ2h0IGNvbnN0cmFp
biB0aGUgYXZhaWxhYmlsaXR5IG9mIGxvdyB2b2x1bWUsIGhpZ2ggdmFsdWUgZmlsdGVycyAobGlr
ZSBjb25maWd1cmF0aW9uIGNoYW5nZXMpLiZuYnNwOyAmbmJzcDsgJm5ic3A7SSB3b3VsZCB2ZXJ5
IG11Y2ggd2VsY29tZSBzb21lb25lIHdobyB3YW50ZWQgdG8gYXR0ZW1wdCB3b3JrIGluIHRoaXMg
YXJlYS4mbmJzcDsgJm5ic3A7QXMgRGF2aWQNCiBXYWx0ZXJtaXJlIHNhaWQgdG8gbWUgb24gdGhp
cyB0b3BpYyB0b2RheSwgaXQgbWlnaHQgYmUgcG9zc2libGUgdG8gaWRlbnRpZnkgYSBtaW5pbXVt
IFhQQVRIIGZpbHRlciBjYXBhYmlsaXR5IHNldCBmb3IgdmFyaW91cyByb2xlcyBpbiB0aGUgbmV0
d29yayBlbGVtZW50LiZuYnNwOyBCdXQgdGhpcyBpcyBub24tdHJpdmlhbCB3b3JrLjxicj4NCjxi
cj4NCkZvciBub3csIEkgYW0gYXNzdW1pbmcgYW55IHZlbmRvciB3aWxsIGJlIGFibGUgdG8gYXJ0
aWN1bGF0ZSB3aGF0IHRoZSBzeW50YXggY2FwYWJpbGl0aWVzIGFyZSBmb3IgdGhlaXIgcGxhdGZv
cm1zLiZuYnNwOyBBbmQgdGhleSBjYW4gZG8gb3V0c2lkZSB0aGUgc3RhbmRhcmRzIGFyZW5hLiZu
YnNwOyBBIGdvb2Qgd2F5IHRvIGRvIHRoaXMgd291bGQgYmUgdG8gcHJlLXBvcHVsYXRlIGV4YW1w
bGUgZmlsdGVycyBpbiB0aGUgJnF1b3Q7ZmlsdGVycyZxdW90OyBvYmplY3RzLjxzcGFuIHN0eWxl
PSJjb2xvcjojMUY0OTdEIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhpcyBpcyBub3QgZ29pbmcgdG8gYmUgaW50ZXJv
cGVyYWJsZSBvciBlYXN5IHRvIGRlYnVnIHRvIGZpbmQgb3V0IHdoYXQgYSB2ZW5kb3Igc3VwcG9y
dHMuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5T
ZWMgMy41LCBwYXJhIDMgJmFtcDsgNCBhYm91dCBYUGF0aCBpbXBsZW1lbnRhdGlvbnMgc2hvdWxk
IGJlIHJlcGxhY2VkLiBUaGUgdGV4dCBzaG91bGQgc2F5IGEgbm9kZS1zZXQgcmVzdWx0PG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5NVVNUIGJlIGdl
bmVyYXRlZCBvciB0aGUgcmVzdWx0IGlzIHRoZSBlbXB0eSBub2RlLXNldC48bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlNvbWUgWFBhdGggY29uc3Ry
dWN0cyBTSE9VTEQgYmUgYXZvaWRlZCwgYXMgc3BlY2lmaWVkIGluIHNlYyA0LjUgb2YgUkZDIDYw
ODcuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPiZsdDtldm9pdCZndDsgbWFr
ZXMgc2Vuc2UuJm5ic3A7IFRoZSByZWZlcmVuY2UgdG8gUkZDIDYwODcgaXMgYSBnb29kIG9uZTxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+RmlsdGVycyBuZWVkIHRvIGJlIHdlbGwtZGVmaW5lZCBzbyBjbGllbnRzIGNhbiBhY3R1YWxs
eSB1c2UgdGhlbS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPlRoZSBzYW1lIHN5bnRheCBhcyBhIE5FVENPTkYgJmx0O2dldCZndDsgWFBhdGggZmls
dGVyIHNob3VsZCBiZSB1c2VkIGhlcmUuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5
N0QiPiZsdDtldm9pdCZndDsgWWVzLiZuYnNwOyBXZSBhbHdheXMgYXJlIGFpbWluZyB3aXRoIGVx
dWl2YWxlbmNlIHRvICZsdDtnZXQmZ3Q7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk5ldyBm
aWx0ZXJzICZuYnNwO3Nob3VsZCBiZSBkZWZpbmVkIGlmIHRoZXkgYXJlIHJlYWxseSBuZWVkZWQu
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPiZsdDtldm9p
dCZndDsgT3ZlciB0aW1lLCBuZXcgZmlsdGVyIHR5cGVzIGNhbiBiZSBhdWdtZW50ZWQgaW4gYXMg
aWRlbnRpdGllcy4mbmJzcDsgQWdhaW4sICZsdDtnZXQmZ3Q7IGVxdWl2YWxlbmNlIGlzIHRoZSBn
b2FsLiZuYnNwOyBDZXJ0YWlubHkgYWRkaW5nIHRoZW0gaW50byB0aGUgbW9kZWwgaGVyZSBpcyB0
aGUNCiBlYXN5IHBhcnQgdnMgZGltZW5zaW9uaW5nIHdoYXQgYSBwbGF0Zm9ybSBjYW4gc3VwcG9y
dC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMt
c2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPkVyaWM8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFu
ZHk8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYu
MHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij4mZ3Q7IC0gcGFnZSA0MTo8YnI+DQom
Z3Q7PGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7IC8qIFlBTkcgUGFyc2VyIFB5YW5nIGNy
YXNoaW5nIG9uIHRoZSBmb2xsb3dpbmcgc3ludGF4IGJlbG93PGJyPg0KJmd0Ozxicj4NCiZndDsm
bmJzcDsgJm5ic3A7U28gZG9lcyB0aGUgZGVmaW5pdGlvbiBnZXQgc2tpcHBlZD8gT3Igd2hhdCBu
ZWVkcyB0byBoYXBwZW4gaGVyZT88YnI+DQo8YnI+DQpUaGVyZSBpcyBhIGNvbWluZyBpbiBweWFu
ZyAxLjcuMiB3aGljaCBmaXhlcyB0aGUgYnVnLi4uPGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly9naXRo
dWIuY29tL21iajQ2NjgvcHlhbmcvaXNzdWVzLzMwMCIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8v
Z2l0aHViLmNvbS9tYmo0NjY4L3B5YW5nL2lzc3Vlcy8zMDA8L2E+PGJyPg0KPGJyPg0KU2VlPGJy
Pg0KPGEgaHJlZj0iaHR0cHM6Ly9naXRodWIuY29tL21iajQ2NjgvcHlhbmcvY29tbWl0L2I4OTFj
YzNkZDNhNDU0N2Y5ZWRkZDgzODgyZTk4NzJiYzIwNjZjNmQiIHRhcmdldD0iX2JsYW5rIj5odHRw
czovL2dpdGh1Yi5jb20vbWJqNDY2OC9weWFuZy9jb21taXQvYjg5MWNjM2RkM2E0NTQ3ZjllZGRk
ODM4ODJlOTg3MmJjMjA2NmM2ZDwvYT48YnI+DQo8YnI+DQpBbGwgd2UgbmVlZCB0byBkbyBpcyBh
d2FpdCB0aGUgbmV3IHZlcnNpb24uPGJyPg0KPGJyPg0KJmd0OyBDb25zaXN0ZW5jeTxicj4NCiZn
dDs8YnI+DQomZ3Q7IC0gbGFzdCBidWxsZXQgb24gcGFnZSA3IHRhbGtzIGFib3V0ICZxdW90O1lB
Tkcgc3VidHJlZXMmcXVvdDsuIEkgZG8gbm90IHNlZSB0aGF0IHRlcm08YnI+DQomZ3Q7Jm5ic3A7
ICZuYnNwO2luIG5ldGNvbmYgb3IgeWFuZyBkb2N1bWVudHMuIFRob3NlIGp1c3QgdGFsayBhYm91
dCAmcXVvdDtzdWJ0cmVlcyZxdW90Oy48YnI+DQomZ3Q7IE1heWJlIEkgYW08YnI+DQomZ3Q7Jm5i
c3A7ICZuYnNwO25vdCBsb29raW5nIGdvb2QgZW5vdWdoPzxicj4NCjxicj4NCldpbGwgcmVtb3Zl
IHRoZSB3b3JkIFlBTkc8YnI+DQo8YnI+DQomZ3Q7IC0gdG9wIG9mIHBhZ2UgOCBJIHNlZSB0aGUg
d29yZHMgJnF1b3Q7eHBhdGgmcXVvdDssICZxdW90O1hwYXRoJnF1b3Q7IGFuZCAmcXVvdDtYUGF0
aCZxdW90Ozxicj4NCiZndDsmbmJzcDsgJm5ic3A7aXMgdGhlcmUgYSBkaWZmZXJlbmNlPzxicj4N
Cjxicj4NCk5vLiZuYnNwOyBXaWxsIGZpeC48YnI+DQo8YnI+DQomZ3Q7IE5pdHM8YnI+DQo8YnI+
DQpOaWNlIGNhdGNoZXMuJm5ic3A7IFdpbGwgZml4IHRoZSBpdGVtcyBiZWxvdy48YnI+DQo8YnI+
DQpFcmljPGJyPg0KPGJyPg0KJmd0OyAtIHlvdSBtYXkgd2FudCB0byBjaGVjayB0aGUgcmVmZXJl
bmNlL2NpdGF0aW9uIG9jY3VycmVuY2VzIG9mIFtzdWJzY3JpYmVdPGJyPg0KJmd0OyZuYnNwOyAm
bmJzcDthdCBzZXZlcmFsIHBsYWNlcyBpdCBwb2ludHMgdG88YnI+DQomZ3Q7Jm5ic3A7ICZuYnNw
OyAmbmJzcDsgZHJhZnQtaWV0Zi1uZXRjb25mLXlhbmctcHVzaC0wNiNyZWYtc3Vic2NyaWJlPGJy
Pg0KJmd0OyZuYnNwOyAmbmJzcDt3aGVyZWFzIEkgdGhpbmsgaXQgaW50ZW5kcyB0byBwb2ludCB0
byB0aGUgW3N1YnNjcmliZV0gaW4gdGhlPGJyPg0KJmd0OyZuYnNwOyAmbmJzcDtub3JtYXRpdmUg
cmVmZXJlbmNlcyBzZWN0aW9uPGJyPg0KJmd0OyAtIGZpcnN0IGJ1bGxldCBvbiBwYWdlIDU6PGJy
Pg0KJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7IEVuaGFuY2VtZW50cyB0byBmaWx0ZXJzLiBTcGVj
aWZpY2FsbHkgdGhlIGZpbHRlciBNVVNUIGF0IGlkZW50aWZ5IGF0PGJyPg0KJmd0OyZuYnNwOyAm
bmJzcDsgJm5ic3A7IGxlYXN0IG9uZSB0YXJnZXRlZCB5YW5nPGJyPg0KJmd0OyZuYnNwOyAmbmJz
cDsgcy9hdC8vJm5ic3A7IC0tIHRoZSBmaXJzdCAmcXVvdDthdCZxdW90OyBzZWVtcyBzdXBlcmZs
dW91czxicj4NCiZndDsmbmJzcDsgJm5ic3A7IHBsdXMsIHlvdSBhcmUgdXNpbmcgY2FwaXRhbGl6
ZWQgTVVTVCB3aXRoIG91dCByZWZlcmVuY2UvY2l0YXRpb24gb2Y8YnI+DQomZ3Q7Jm5ic3A7ICZu
YnNwOyBSRkMyMTE5PGJyPg0KJmd0OyAtIHBhZ2UgMzY6PGJyPg0KJmd0Ozxicj4NCiZndDsmbmJz
cDsgJm5ic3A7ICZuYnNwO2xlYWYgZGVwZW5kZW5jeSB7PGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwO3R5cGUgc246c3Vic2NyaXB0aW9uLWlkOzxicj4NCiZndDsmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDtkZXNjcmlwdGlvbjxicj4NCiZndDsmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7JnF1b3Q7UHJvdmlkZXMgdGhlIFN1YnNjcmlwdGlvbiBJRCBvZiBhIHBh
cmVudCBzdWJzY3JpcHRpb24gd2hpY2g8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyBoYXMgYWJzb2x1dGUgcHJpb3JpdHkgc2hvdWxkIHRoYXQgcGFyZW50IGhhdmUg
cHVzaCB1cGRhdGVzPGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
cmVhZHkgdG8gZWdyZXNzIHRoZSBwdWJsaXNoZXIuIEluIG90aGVyIHdvcmRzLCB0aGVyZSBzaG91
bGQgYmU8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBubyBzdHJl
YW1pbmcgb2Ygb2JqZWN0cyBmcm9tIHRoZSBjdXJyZW50IHN1YnNjcmlwdGlvbiBpZiBvZjxicj4N
CiZndDsmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHRoZSBwYXJlbnQgaGFzIHNv
bWV0aGluZyByZWFkeSB0byBwdXNoLiZxdW90Ozs8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7cmVmZXJlbmNlPGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsmcXVvdDtSRkMtNzU0MCwgc2VjdGlvbiA1LjMuMSZxdW90Ozs8YnI+DQomZ3Q7Jm5ic3A7
ICZuYnNwOyAmbmJzcDt9PGJyPg0KJmd0Ozxicj4NCiZndDsmbmJzcDsgJm5ic3A7ICZuYnNwOyBz
L2lmIG9mL2lmLyA/PzxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_df333dcd802a427dabdebbb506d550a0XCHRTP013ciscocom_--


From nobody Tue May 16 18:02:42 2017
Return-Path: <huitema@huitema.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 0045213147C; Tue, 16 May 2017 18:02:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Christian Huitema <huitema@huitema.net>
To: <secdir@ietf.org>
Cc: mpls@ietf.org, draft-ietf-mpls-tp-aps-updates.all@ietf.org, ietf@ietf.org
Subject: Secdir last call review of draft-ietf-mpls-tp-aps-updates-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149498296095.6616.14922755167741082096@ietfa.amsl.com>
Date: Tue, 16 May 2017 18:02:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HZr8zmcaWKlCUPCHizTrxKlKLIc>
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, 17 May 2017 01:02:41 -0000

Reviewer: Christian Huitema
Review result: Ready

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.

This document is: Ready.

This document, draft-ietf-mpls-tp-aps-updates-03, describes a set of
fixes to the MPLS Transport Profile (MPLS-TP) Linear Protection
defined in RFC 6378. Linear Protection is meant to provide rapid and
simple protection switching. MPLS-TP allows end-points in a "protected
domain" to coordinate when the traffic shall be sent on the normal
path, or switched to the pre-established protection path. The protocol
was updated in RFC 7271. The current document updates RFC 7271. It
adds a better definition for the initialization of the protocol state,
and defines a limited set of changes in the state machine. 

The security sections states that "No specific security issue is
raised in addition to those ones already documented in [RFC7271].  It
may be noted that tightening the description of initializing behavior
may help to protect networks from re-start attack." I agree with that
assessment.
 


From nobody Wed May 17 02:22:28 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 D2C8112EABC; Wed, 17 May 2017 02:22:18 -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: ospf@ietf.org, ietf@ietf.org, draft-ietf-ospf-ospfv3-lsa-extend.all@ietf.org
Subject: Rtgdir early review of draft-ietf-ospf-ospfv3-lsa-extend-14
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149501293882.6715.9441857001639471954@ietfa.amsl.com>
Date: Wed, 17 May 2017 02:22:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MmX0q9r1zBNVNoBjQz7AuZm_s9A>
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, 17 May 2017 09:22:19 -0000

Reviewer: IJsbrand Wijnands
Review result: Has Issues

Hi All,

I have been selected to do a routing directorate QA review of this
draft.
https://www.ietf.org/id/draft-ietf-ospf-ospfv3-lsa-extend-14.txt

Summary: 

This draft proposes a new addressing (TLV) format to more easily allow

additional information to be added as part of a particular LSA. 
Overall, well written, easy to understand what the objective is for
this draft.

Comments and Questions:

This looks like a pretty radical change to the OSPFv3 spec. I would 
almost argue to call it OSPFv4..

Its very unfortunate there are no ‘reserved’ fields in RFC5340 that 
would allow you keep the existing LSA’s format and have some way to 
extend it differently. The TLV approach look good, I can’t see a
better 
way to achieve the goal.

Minor Issues and Nits:
none.

Thx,

Ice.



From nobody Wed May 17 03:46:40 2017
Return-Path: <julian.reschke@gmx.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 AFF4A12EAC2 for <ietf@ietfa.amsl.com>; Wed, 17 May 2017 03:46:38 -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_50=0.8, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, 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 uaE66L94DnXE for <ietf@ietfa.amsl.com>; Wed, 17 May 2017 03:46:37 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.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 AD67512EB1A for <ietf@ietf.org>; Wed, 17 May 2017 03:41:44 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.117.158]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LkOaJ-1ditZY3FtL-00cPFl; Wed, 17 May 2017 12:41:39 +0200
Subject: Re: Last Call: <draft-nottingham-rfc5988bis-05.txt> (Web Linking) to Proposed Standard
To: Mark Nottingham <mnot@mnot.net>
References: <588716b3-161c-62ac-e5a9-a04c86f13e86@gmx.de> <704BC987-1ED0-4E59-A803-0B4013A86F03@mnot.net> <c81eb293-f443-8d61-bd82-b7c2902e4426@gmx.de> <09EA3303-8F65-4FDE-8303-8C2AD9B8B897@mnot.net> <280366F3-ECDA-44A2-820A-33FD5965EAFD@mnot.net>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <5b94ecb4-b317-38ec-aa10-dc166faac5d0@gmx.de>
Date: Wed, 17 May 2017 12:41:37 +0200
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: <280366F3-ECDA-44A2-820A-33FD5965EAFD@mnot.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:35TXMMsXrFjcRmvSA4PhCZNjZggjkm2etxO4RTH7dQNc+u755QT 5EWIKyUMt+CDskUE+iLnN6lvw9r5F5Y1xI9wyP+CcNH0PmpV1lESxnv1JhVhGFgr7Y9ykyH SabmF7eLNi+/1pmYACq5PO+nU0Lst29AeAOUP+9J4lqJHUxqj0Cx4G4yFBn2wM75ldm9iPo 5ceOiQYNRxiGQ33dgMnaw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:BBUVuGFYQEo=:TvLcST5BQlN7YpB2+qRmUT vC1dWs4f18anDmEil4ABmZSHp7+FmYOUY3Q4vkSWu0T+SyscVIS+zg85EtopvUwj54ZPKp7w+ /vjLnjQd5S7JiWCBkCAugEiDkQ8FMGHFPxUgPcUuhB7E6HyYwBRGrNWQTJofWLioS4Ceujpfx rDL2nhBahe/0DLeyuq/edHhvVexavmxEtoLOnX2aqSmgS3je7vGz6M80hzwj3GPv0Q673KVqC 175JOCdENtPN0gdrRS9sr+oRc0fFwOUIhoBDihMGw2AQeyZf6h4vDqxo1meN+CVAZDAyaIHmJ Pp6SQ99c4KeVR1lX8wYLlt9n/SlOyvXDaAlLsXVjdLIgZynnyDPawE49MRI61rZGpQPdc7hp3 161VYuFO82rZp7ersNMvUeiGOLz7Ku8RBH0UyOj0B+vhPqsx+H6337rakppewNn6QNudge7c3 71r5EDUY1Poq4k57o/uELreCWhZrUId++dbnV+w2h+cmeKeWYtOTkbyl5Yg9Xg7+xnCBLNyHs QYlKucVBNydSKBKCKgp0bd2c3kd3I99LMnFtVM2FyUBtWKiew8C0uk+JAG4iJmpGP/I2TixTK eyYay7L234cw1uZ7G3+mN0M3dhGl60m2bxwEWGzb7GUyO6lVAfhDo8Opny2MW8id5w78sFJf3 UlDSVFnUTnF5fV4+XD6gmpaTUWLoB4yxL7uKmHtgM2bKc+csO161MJ0XVi0eGQKF9qHS4K5Ud u45pf0XA/uGkLJJs2vYjfZ4QK9en2tIwOZXO5MIZw9kFw3dEc3Z1KMdRbLuWIUWmuyBZ04pkh Y35vGDx
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/I_UPWOi_Sm_Sg8AYe8KziAsOWyg>
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, 17 May 2017 10:46:39 -0000

On 2017-05-16 04:37, Mark Nottingham wrote:
> ...
> This is what I currently have:
>   https://gist.github.com/mnot/2fb569e7303dbcdde8b27cb7a404a648
>
> I need to get some more eyeballs onto it to make sure it's correct (or at least reasonable). Reviews appreciated.
> ...

I think this goes into the right direction; it's mostly a parser based 
on a relaxed ABNF transformed to prose (which makes me wonder whether 
there's a tool to be written here :-).

Other comments:

1)  "... If it is not present, context_string is the identity of the 
representation carrying the Link header ..." - similar prose is 
elsewhere in the spec - what is "the identity of a representation"?????

2) "Consume the contents up to but not including the first DQUOTE 
character that is not preceded by a "" character" - I assume there's a 
backslash missing here. That said: doesn't work, because it would fail 
for an input such as: "\\" - here, the DQUOTE is preceded by backslash, 
but it's not part of the quoted-pair.

Best regards, Julian


From nobody Wed May 17 05:12:25 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 4ADC612422F; Wed, 17 May 2017 05:12:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 hukVHWzVWVzf; Wed, 17 May 2017 05:12:07 -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 709E5126C23; Wed, 17 May 2017 05:07:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1442; q=dns/txt; s=iport; t=1495022825; x=1496232425; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Kfrsg8wpAuTwoxaYgXd3EZ/kLMgDSvAhV6u32SUBwd4=; b=CrhUgxJ3OfjX2ejGDhc4utPIVeDXVz/ZiutO4A4AtGbN+L3nEjdemC6H jztaSSI4fgFx3c7sIwUniHW/6Xzd8AbF+D4OR4NyprnxlpW6uK7SX/rRT EPS5KKPPqtIKJgeZBYTBc0PQkUa1CTDfVZz34EnCxrOOaA6woBhgRQJFF w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AHAQBEPBxZ/5BdJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1VigQwHg2aKGKdbgg8shXgCGoVAPxgBAgEBAQEBAQFrKIUZBiM?= =?us-ascii?q?RRRACAQgODAImAgICMBUQAgQBDQWKIw6tGIImiwcBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEYBYELik2HdYJgAQSeEAGTGpFtlEUBHziBCnAVhzx2AYdagQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.38,354,1491264000"; d="scan'208";a="424735363"
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; 17 May 2017 12:07:04 +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 v4HC73UB023271 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 17 May 2017 12:07:04 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; Wed, 17 May 2017 08:07:03 -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; Wed, 17 May 2017 08:07:03 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Min Ye <amy.yemin@huawei.com>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>
CC: "ospf@ietf.org" <ospf@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-ospf-ospfv3-lsa-extend.all@ietf.org" <draft-ietf-ospf-ospfv3-lsa-extend.all@ietf.org>
Subject: Re: Rtgdir early review of draft-ietf-ospf-ospfv3-lsa-extend-14
Thread-Topic: Rtgdir early review of draft-ietf-ospf-ospfv3-lsa-extend-14
Thread-Index: AQHSzu8WdJCLcbGHPk6KfFYvglZsraH4bkGA
Date: Wed, 17 May 2017 12:07:03 +0000
Message-ID: <D541B500.AF34E%acee@cisco.com>
References: <149501293882.6715.9441857001639471954@ietfa.amsl.com>
In-Reply-To: <149501293882.6715.9441857001639471954@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.196]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E9A9EA8FBE58504CAF82A26B9C2BB31D@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lURTrxOO6xFaQWVS3zfG2N4nRVE>
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, 17 May 2017 12:12:09 -0000

SGkgTWluICwNCg0KT24gNS8xNy8xNywgNToyMiBBTSwgIk1pbiBZZSIgPGFteS55ZW1pbkBodWF3
ZWkuY29tPiB3cm90ZToNCg0KPlJldmlld2VyOiBJSnNicmFuZCBXaWpuYW5kcw0KPlJldmlldyBy
ZXN1bHQ6IEhhcyBJc3N1ZXMNCg0KSSB0aGluayB0aGUgcmVzdWx0IGlzIOKAnE5vIElzc3Vlc+KA
nS4NCg0KVGhhbmtzLA0KQWNlZQ0KPg0KPkhpIEFsbCwNCj4NCj5JIGhhdmUgYmVlbiBzZWxlY3Rl
ZCB0byBkbyBhIHJvdXRpbmcgZGlyZWN0b3JhdGUgUUEgcmV2aWV3IG9mIHRoaXMNCj5kcmFmdC4N
Cj5odHRwczovL3d3dy5pZXRmLm9yZy9pZC9kcmFmdC1pZXRmLW9zcGYtb3NwZnYzLWxzYS1leHRl
bmQtMTQudHh0DQo+DQo+U3VtbWFyeTogDQo+DQo+VGhpcyBkcmFmdCBwcm9wb3NlcyBhIG5ldyBh
ZGRyZXNzaW5nIChUTFYpIGZvcm1hdCB0byBtb3JlIGVhc2lseSBhbGxvdw0KPg0KPmFkZGl0aW9u
YWwgaW5mb3JtYXRpb24gdG8gYmUgYWRkZWQgYXMgcGFydCBvZiBhIHBhcnRpY3VsYXIgTFNBLg0K
Pk92ZXJhbGwsIHdlbGwgd3JpdHRlbiwgZWFzeSB0byB1bmRlcnN0YW5kIHdoYXQgdGhlIG9iamVj
dGl2ZSBpcyBmb3INCj50aGlzIGRyYWZ0Lg0KPg0KPkNvbW1lbnRzIGFuZCBRdWVzdGlvbnM6DQo+
DQo+VGhpcyBsb29rcyBsaWtlIGEgcHJldHR5IHJhZGljYWwgY2hhbmdlIHRvIHRoZSBPU1BGdjMg
c3BlYy4gSSB3b3VsZA0KPmFsbW9zdCBhcmd1ZSB0byBjYWxsIGl0IE9TUEZ2NC4uDQo+DQo+SXRz
IHZlcnkgdW5mb3J0dW5hdGUgdGhlcmUgYXJlIG5vIOKAmHJlc2VydmVk4oCZIGZpZWxkcyBpbiBS
RkM1MzQwIHRoYXQNCj53b3VsZCBhbGxvdyB5b3Uga2VlcCB0aGUgZXhpc3RpbmcgTFNB4oCZcyBm
b3JtYXQgYW5kIGhhdmUgc29tZSB3YXkgdG8NCj5leHRlbmQgaXQgZGlmZmVyZW50bHkuIFRoZSBU
TFYgYXBwcm9hY2ggbG9vayBnb29kLCBJIGNhbuKAmXQgc2VlIGENCj5iZXR0ZXIgDQo+d2F5IHRv
IGFjaGlldmUgdGhlIGdvYWwuDQo+DQo+TWlub3IgSXNzdWVzIGFuZCBOaXRzOg0KPm5vbmUuDQo+
DQo+VGh4LA0KPg0KPkljZS4NCj4NCj4NCg0K


From nobody Wed May 17 06:07:11 2017
Return-Path: <murch@andrew.cmu.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 31EF012EB53; Wed, 17 May 2017 06:07:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.501
X-Spam-Level: 
X-Spam-Status: No, score=-1.501 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 Ymnj9aZWULZR; Wed, 17 May 2017 06:07:07 -0700 (PDT)
Received: from smtp.andrew.cmu.edu (SMTP.ANDREW.CMU.EDU [128.2.105.202]) (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 775791294B7; Wed, 17 May 2017 06:07:07 -0700 (PDT)
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) (user=murch mech=PLAIN (0 bits)) by smtp.andrew.cmu.edu (8.15.2/8.15.2) with ESMTPSA id v4HD723i019793 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 May 2017 09:07:03 -0400
Subject: Re: [art] ART Area Review for draft-ietf-calext-caldav-attachments-02
To: Julian Reschke <julian.reschke@gmx.de>, IETF Discussion <ietf@ietf.org>, art@ietf.org
References: <c04f39e2-79d2-ab9d-59ab-26e51d7ab5fc@gmx.de> <81613220-989b-ca78-fe56-0ac7b19e7ce6@andrew.cmu.edu> <b2a4924d-c7c9-b40b-484f-9fab48bfe5de@gmx.de>
From: Ken Murchison <murch@andrew.cmu.edu>
Organization: Carnegie Mellon University
Message-ID: <a603f3de-2d96-6f86-e0c3-3e0a4884a185@andrew.cmu.edu>
Date: Wed, 17 May 2017 09:07:02 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <b2a4924d-c7c9-b40b-484f-9fab48bfe5de@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-PMX-Version: 6.3.0.2556906, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.5.17.125716
X-SMTP-Spam-Clean: 33% ( SXL_IP_DYNAMIC 3, TO_IN_SUBJECT 0.5, HTML_00_01 0.05, HTML_00_10 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, FROM_EDU_TLD 0, IN_REP_TO 0, LEGITIMATE_SIGNS 0, MSG_THREAD 0, NO_CTA_URI_FOUND 0, NO_URI_FOUND 0, NO_URI_HTTPS 0, RDNS_GENERIC_POOLED 0, RDNS_POOLED 0, RDNS_RESIDENTIAL 0, RDNS_SUSP 0, RDNS_SUSP_GENERIC 0, RDNS_SUSP_SPECIFIC 0, REFERENCES 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __HAS_FROM 0, __HAS_MSGID 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_TEXT_P 0, __MIME_TEXT_P1 0, __MIME_VERSION 0, __MOZILLA_USER_AGENT 0, __NO_HTML_TAG_RAW 0, __PHISH_SPEAR_STRUCTURE_1 0, __RDNS_POOLED_1 0, __REFERENCES 0, __SANE_MSGID 0, __SUBJ_ALPHA_NEGATE 0, __TO_IN_SUBJECT2 0, __TO_MALFORMED_2 0, __TO_NAME 0, __TO_NAME_DIFF_FROM_ACC 0, __TO_REAL_NAMES 0,  __USER_AGENT 0)
X-SMTP-Spam-Score: 33%
X-Scanned-By: MIMEDefang 2.78 on 128.2.105.202
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-7bgpv7XVrC-Whp2SiWYHZuv_8Q>
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, 17 May 2017 13:07:09 -0000

On 05/15/2017 12:04 PM, Julian Reschke wrote:
> On 2017-05-15 16:03, Ken Murchison wrote:
>> Hi Julian,
>>
>> Thanks for the review.  Comments inline.
>>
>>
>> On 05/14/2017 10:23 AM, Julian Reschke wrote:
>>> Reviewer: Julian Reschke
>>> Review result: Not Ready
>>>
>>> Document: draft-ietf-calext-caldav-attachments-02
>>> IETF LC End Date: 2017-05-14
>>> IESG Telechat date: 2017-05-25
>>>
>>> This document describes attachment handling in CalDAV (WebDAV based
>>> calendaring).
>>>
>>> The mechanism described by this document is essential RPCish, using
>>> HTTP POST for tunneling. It will work in practice, but it definitively
>>> isn't state of the art in IETF protocols, in particular in an
>>> otherwise WebDAV/CalDAV-based ecosystem.
>>>
>>> Major issues:
>>>
>>> The main issue with this specification is that it
>>>
>>> 1) models operations on attachments as POST operations, where the
>>> actual type of operation is specified using a query parameter, instead
>>> of using the HTTP methods POST, PUT, and DELETE.
>>
>> The resource being acted upon is an actual calendar resource, which is
>> already in place.  The attachments are meta-data associated with one or
>
> Only for creation of the attachment. Once is has been created, it 
> should have its own URI, and the usual HTTP methods should be applicable.

Using HTTP methods directly on the attachment URI makes things more 
difficult because the calendar resource(s) referencing the attachment 
also need to be updated.  This would have to be done either as a 
side-effect of the PUT/DELETE on the attachment, or as a separate PUT 
(and separate round-trips) on the resource(s).  The desire was to avoid 
doing either one of these, which is why a POST on the calendar resource 
was chosen as the method to add/update/delete an attachment from a 
calendar resource.



>> more calendar resources, which is why a POST is used on the calendar
>> resource to manipulate an attachment.  Can you explain how you would
>> envision different HTTP methods be used to add/update/delete an
>> attachment associated with a calendar resource?
>
> For adding, I would define an HTTP resource that can be posted to. It 
> could be discovered through a WebDAV property.

We could certainly define a template or series of templates for 
add/update/delete and expose them as WebDAV properties.


-- 
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University


From nobody Wed May 17 06:14:56 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 2078F129BA8; Wed, 17 May 2017 06:14:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 IOU2rbt_vqWk; Wed, 17 May 2017 06:14:44 -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 D6FF0129478; Wed, 17 May 2017 06:14:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5801; q=dns/txt; s=iport; t=1495026884; x=1496236484; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=/fADXs/yfgxTZTiut3FKe8vYxggIr5YCY7OMfugQb+U=; b=HkdowfrHokzZHyv1hx+l6Yb+1fpYlyQzvSZM+iOMZiRw1lnj7sFZVFpU 2o660Wvlx8Fbt8zGBllRFIfrfOQ/StxM2QJBvSjpRi/e1XZTD899iDhAU kE8amdeoWSommR4E7HBUxLB0LyAC2q+/TVqKV2YJoeb7kyRuQxkmI6MCs g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BIAQCRSxxZ/5hdJa1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBg1VihHmKGJFFIXKVA4IPLoV2AoVaPxgBAgEBAQEBAQFrKIUZBiMVNAY?= =?us-ascii?q?HEAsOBgYCERUCAlcGAQwIAQEQig8OrROCJosIAQEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?RoFgQuFVIFeKwuCMTSDIYIBglOCYAEEnhCHHIM1iEqCBIU8g0MjhkeMFogwHzi?= =?us-ascii?q?BCi8gCBkVh1gkhnCCGhQBAQE?=
X-IronPort-AV: E=Sophos;i="5.38,354,1491264000"; d="scan'208";a="424764137"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 May 2017 13:14:42 +0000
Received: from [10.82.217.158] (rtp-vpn3-412.cisco.com [10.82.217.158]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v4HDEg9K029140; Wed, 17 May 2017 13:14:42 GMT
Subject: Re: Genart last call review of draft-ietf-netmod-yang-model-classification-06
To: Pete Resnick <presnick@qti.qualcomm.com>, gen-art@ietf.org
Cc: draft-ietf-netmod-yang-model-classification.all@ietf.org, ietf@ietf.org, netmod@ietf.org
References: <149439618175.1801.10155387201501790876@ietfa.amsl.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <8f002f0c-fea3-7a4b-9250-1e870f423d86@cisco.com>
Date: Wed, 17 May 2017 09:14:40 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0
MIME-Version: 1.0
In-Reply-To: <149439618175.1801.10155387201501790876@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_MS_PDERmSQiq4IW60liwxeUsak>
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, 17 May 2017 13:14:46 -0000

Thanks Pete,

Version 7 has been posted.
All your feedback has been taken into account.
https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-yang-model-classification-07

Regards, Benoit
> Reviewer: Pete Resnick
> 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 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-netmod-yang-model-classification-??
> Reviewer: Pete Resnick
> Review Date: 2017-05-09
> IETF LC End Date: 2017-05-14
> IESG Telechat date: Not scheduled for a telechat
>
> Summary: Ready with Minor Issues/Nits
>
> To an outsider like me, this seems like a useful document and it was
> an interesting read. The document could use a serious edit for grammar
> and typos. A few specific comments below.
>
> Major issues: None.
>
> Minor issues:
>
> In section 2.1, paragraphs 4 and 5 mention "speed". The speed of what?
> Development of the module? It's not clear from the text.
>
> In section 3.1, it says:
>
>                            While there is no formal definition of what
>     construes an SDO, a common feature is that they publish
>     specifications along specific processes with content that reflects
>     some sort of membership consensus.  The specifications are
> developed
>     for wide use among the membership or for audiences beyond that.
>     
> First of all, s/construes/constitutes. But aside from that, it's not
> at all clear to me that a common feature is "membership consensus".
> For example, we don't have membership, and many other organizations
> use voting and not consensus. Perhaps replace the above with something
> simpler like:
>
>                            Most SDOs create specifications according
> to
>     a formal process in order to produce a standard that is useful for
>     their constituencies.
>
> Nits/editorial comments:
>
> In the Abstract and section 3.1, you use "standards-defining
> organization" for SDO. I've never heard that phrase used before.
> Elsewhere in the document, you use "standards development
> organization", which is the phrase I've always seen used. I suggest
> you change to that in both places.
>
> Throughout the document, you say things like, "the authors believe" or
> "we assume". This is a WG consensus document. While I generally think
> that using these terms is bad form in a WG document, saying "the
> authors believe" almost sounds like the authors believe it, but the WG
> might not. If the authors and the WG believe XYZ, don't say "the
> authors believe XYZ" or "we believe XYZ"; just say "XYZ", or at least
> use the passive voice. So:
>
> Section 1:
>
> OLD
>     The intent of this document is to provide a taxonomy to simplify
>     human communication around YANG modules.  The authors acknowledge
>     that the classification boundaries are at times blurry, but
> believe
>     that this document should provide a robust starting point as the
> YANG
>     community gains further experience with designing and deploying
>     modules.  To be more explicit, the authors believe that the
>     classification criteria will change over time.
> NEW
>     The intent of this document is to provide a taxonomy to simplify
>     human communication around YANG modules.  While the classification
>     boundaries are at times blurry, this document should provide a
> robust
>     starting point as the YANG community gains further experience with
>     designing and deploying modules.  To be more explicit, it is
> expected
>     that the classification criteria will change over time.
> END
>
> Section 2:
>
> OLD
>                                                       For the purpose
> of
>     this document we assume that both approaches (bottom-up and
> top-down)
>     will be used as they both provide benefits that appeal to
> different
>     groups.
> NEW
>                                                       This document
>     considers both bottom-up and top-down approaches as they are both
> used
>     and they each provide benefits that appeal to different groups.
> END
>
> Section 2.1:
>
> OLD
>                                                       For the purpose
> of
>     this document we will use the term "orchestrator" to describe a
>     system implementing such a process.
> NEW
>                                                       For the purpose
> of
>     this document, the term "orchestrator" is used to describe a
> system
>     implementing such a process.
>
>
> Section 2.2:
>
> OLD
>     Although the [RFC7950], [RFC7950] doesn't explain the relationship
> of
>     the terms '(YANG) data model' and '(YANG) module', the authors
>     understand there is a 1:1 relationship between a data model and a
>     YANG module, but a data model may also be expressed using a
>     collection of YANG modules (and submodules).
>
> (This one's not even grammatical. Here's my best guess as to what you
> meant)
>
> NEW
>     Although [RFC7950] doesn't explain the relationship between the
> terms
>     '(YANG) data model' and '(YANG) module', there is a 1:1
> relationship
>     between a data model and a YANG module. However, a data model may
>     also be expressed using a collection of YANG modules (and
> submodules).
>     
> That's it for all of the "author" and "we" items. One other nit:
>
> 3.2 s/augmented into/added into. I don't think you can "augment into"
> something.
>
>
> .
>


From nobody Wed May 17 06:16:51 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 1797D12EB6A; Wed, 17 May 2017 06:16:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 7_bEX7yGsNYt; Wed, 17 May 2017 06:16:40 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 372DB1286B1; Wed, 17 May 2017 06:16:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13172; q=dns/txt; s=iport; t=1495026970; x=1496236570; h=subject:from:to:cc:references:message-id:date: mime-version:in-reply-to; bh=YqQr9H+6b19XX/n5Q2rnpL9mSr+OWSEkW0bhQpSZzuA=; b=gU1LGvO9HUZDTH9XegidQKfrfq2oIr3dLHEaq1uxBFFnUTnIUaYv2nkX A0Hg6yk9OxjmG6MmvgWhlffA15T86EY73ysLdHciZM6VTZ+M3WyHT+EnZ RkBilVN/MyJ3T9h7/zeiZJTNhnWWRQkfYNYL3eKdLqUf7ztooiuo0nm8Y E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CWAQCGTBxZ/51dJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1VigQyDbYoYkUUhkD2FOIIPIQEMgkCCbEoChVo/GAECAQEBAQE?= =?us-ascii?q?BAWsohRkBAQEDAQEhSwQHEAkCGCMHAgInHxEGAQwGAgEBih8OjzqdYIImK4pcA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAQEBGAWGX4FeKwuCZYMhhFSCYAEElnOHHYcci3+?= =?us-ascii?q?CBIU8g0OGaowWiDAfOIEKLyAIGRVGhSyBZiQ2iGgBAQE?=
X-IronPort-AV: E=Sophos; i="5.38,354,1491264000"; d="scan'208,217"; a="28504252"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 May 2017 13:16:09 +0000
Received: from [10.82.217.158] (rtp-vpn3-412.cisco.com [10.82.217.158]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id v4HDG8GI002304; Wed, 17 May 2017 13:16:08 GMT
Subject: Re: [netmod] Last Call: <draft-ietf-netmod-yang-model-classification-06.txt> (YANG Module Classification) to Informational RFC
From: Benoit Claise <bclaise@cisco.com>
To: Jonathan Hansford <jonathan@hansfords.net>, IETF-Announce <ietf-announce@ietf.org>, ietf@ietf.org
Cc: netmod-chairs@ietf.org, warren@kumari.net, draft-ietf-netmod-yang-model-classification@ietf.org, netmod@ietf.org
References: <149360589744.9906.9498469901914786081.idtracker@ietfa.amsl.com> <46a76c75-fd04-4134-9a97-26d1567963d7@Spark> <d7e4de44-60be-54ad-4727-16b05ebe7a4b@cisco.com>
Message-ID: <6fd6d841-e5f9-c304-9616-032eb5b41923@cisco.com>
Date: Wed, 17 May 2017 09:16:07 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0
MIME-Version: 1.0
In-Reply-To: <d7e4de44-60be-54ad-4727-16b05ebe7a4b@cisco.com>
Content-Type: multipart/alternative; boundary="------------54C72DA6F31C6A8834376396"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W0pZdtYZQdi_IGdluwaQiEegsTI>
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, 17 May 2017 13:16:43 -0000

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

Hi Jonathan,

See 
https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-yang-model-classification-07 
for the applied changes.
The sentence is section 2.2 has been removed: it was too hard to parse 
(and was not strictly needed for this draft).

Regards, Benoit
> Thanks Jonathan,
>
> See in line.
>
>> I have no substantive comments, but have noticed, among other things, 
>> a few somewhat inconsequential typos that could nevertheless impact 
>> readability, particularly for those for whom English is a second 
>> language:
>> • Page 3, penultimate bullet: s/by network operator/by a network operator
>> • Why is figure 1 on page 5 when it is first referenced at the top of 
>> page 4?
>> • Section 2.1, second paragraph (2 typos): s/peole or extarnal/people 
>> or external
>> • Section 2.1, last paragraph: I don't understand the second sentence 
>> that starts: “Although it provides information …”
>> • Section 2.2, second paragraph: i don't understand the first 
>> sentence that starts: “Although the [RFC7950], [RFC7950] …”
> I guess this should be:
>     Although YANG [RFC7950 <https://tools.ietf.org/html/rfc7950>] doesn't explain the relationship of
>     the terms '(YANG) data model' and '(YANG) module', the authors
>     understand there is a 1:1 relationship between a data model and a
>     YANG module, but a data model may also be expressed using a
>     collection of YANG modules (and submodules).  The module provides a
>     coherent data model representation of the software environment
>     consisting of the operating system and applications running on the
>     device.  The decomposition, ordering, and execution of changes to the
>     operating system and application configuration is the task of the
>     agent that implements the module.
> Re-reading this paragraph, its logical place is in the terminology 
> section 1.1, next to data model and module definitions.
>
> Regards, Benoit
>> • Section 3.3, second paragraph: s/include ability/include the ability
>> • Section 6: small point but I believe the second acknowledgement 
>> should be me(!), “Jonathan Hansford”, not “David”
>>
>> Jonathan
>>
>> =O)
>>
>>
>> On 1 May 2017, 03:32 +0100, The IESG <iesg-secretary@ietf.org>, wrote:
>>>
>>> The IESG has received a request from the NETCONF Data Modeling Language
>>> WG (netmod) to consider the following document:
>>> - 'YANG Module Classification'
>>> <draft-ietf-netmod-yang-model-classification-06.txt> as Informational
>>> RFC
>>>
>>> The IESG plans to make a decision in the next few weeks, and solicits
>>> final comments on this action. Please send substantive comments to the
>>> ietf@ietf.org mailing lists by 2017-05-14. 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 YANG data modeling language is currently being considered for a
>>> wide variety of applications throughout the networking industry at
>>> large. Many standards-defining organizations (SDOs), open source
>>> software projects, vendors and users are using YANG to develop and
>>> publish YANG modules for a wide variety of applications. At the same
>>> time, there is currently no well-known terminology to categorize
>>> various types of YANG modules.
>>>
>>> A consistent terminology would help with the categorization of YANG
>>> modules, assist in the analysis of the YANG data modeling efforts in
>>> the IETF and other organizations, and bring clarity to the YANG-
>>> related discussions between the different groups.
>>>
>>> This document describes a set of concepts and associated terms to
>>> support consistent classification of YANG modules.
>>>
>>>
>>>
>>>
>>> The file can be obtained via
>>> https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classification/
>>>
>>> IESG discussion can be tracked via
>>> https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classification/ballot/
>>>
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> netmod mailing list
>>> netmod@ietf.org
>>> https://www.ietf.org/mailman/listinfo/netmod
>
>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod


--------------54C72DA6F31C6A8834376396
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">Hi Jonathan,<br>
      <br>
      See
<a class="moz-txt-link-freetext" href="https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-yang-model-classification-07">https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-yang-model-classification-07</a>
      for the applied changes.<br>
      The sentence is section 2.2 has been removed: it was too hard to
      parse (and was not strictly needed for this draft).<br>
      <br>
      Regards, Benoit<br>
    </div>
    <blockquote type="cite"
      cite="mid:d7e4de44-60be-54ad-4727-16b05ebe7a4b@cisco.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div class="moz-cite-prefix">Thanks Jonathan,<br>
        <br>
        See in line.<br>
        <br>
      </div>
      <blockquote cite="mid:46a76c75-fd04-4134-9a97-26d1567963d7@Spark"
        type="cite">
        <title></title>
        <div name="messageBodySection">I have no substantive comments,
          but have noticed, among other things, a few somewhat
          inconsequential typos that could nevertheless impact
          readability, particularly for those for whom English is a
          second language:<br>
          • Page 3, penultimate bullet: s/by network operator/by a
          network operator<br>
          • Why is figure 1 on page 5 when it is first referenced at the
          top of page 4?<br>
          • Section 2.1, second paragraph (2 typos): s/peole or
          extarnal/people or external<br>
          • Section 2.1, last paragraph: I don't understand the second
          sentence that starts: “Although it provides information …”<br>
          • Section 2.2, second paragraph: i don't understand the first
          sentence that starts: “Although the [RFC7950], [RFC7950] …”</div>
      </blockquote>
      I guess this should be:<br>
      <pre class="newpage">   Although YANG [<a href="https://tools.ietf.org/html/rfc7950" title="&quot;The YANG 1.1 Data Modeling Language&quot;" moz-do-not-send="true">RFC7950</a>] doesn't explain the relationship of
   the terms '(YANG) data model' and '(YANG) module', the authors
   understand there is a 1:1 relationship between a data model and a
   YANG module, but a data model may also be expressed using a
   collection of YANG modules (and submodules).  The module provides a
   coherent data model representation of the software environment
   consisting of the operating system and applications running on the
   device.  The decomposition, ordering, and execution of changes to the
   operating system and application configuration is the task of the
   agent that implements the module.
</pre>
      Re-reading this paragraph, its logical place is in the terminology
      section 1.1, next to data model and module definitions.<br>
      <br>
      Regards, Benoit<br>
      <blockquote cite="mid:46a76c75-fd04-4134-9a97-26d1567963d7@Spark"
        type="cite">
        <div name="messageBodySection"> • Section 3.3, second paragraph:
          s/include ability/include the ability<br>
          • Section 6: small point but I believe the second
          acknowledgement should be me(!), “Jonathan Hansford”, not
          “David”</div>
        <div name="messageSignatureSection"><br>
          Jonathan<br>
          <br>
          =O)</div>
        <div name="messageReplySection"><br>
          <div name="messageReplySection"><br>
            On 1 May 2017, 03:32 +0100, The IESG <a
              class="moz-txt-link-rfc2396E"
              href="mailto:iesg-secretary@ietf.org"
              moz-do-not-send="true">&lt;iesg-secretary@ietf.org&gt;</a>,
            wrote:<br>
            <blockquote type="cite"><br>
              The IESG has received a request from the NETCONF Data
              Modeling Language<br>
              WG (netmod) to consider the following document:<br>
              - 'YANG Module Classification'<br>
              &lt;draft-ietf-netmod-yang-model-classification-06.txt&gt;
              as Informational<br>
              RFC<br>
              <br>
              The IESG plans to make a decision in the next few weeks,
              and solicits<br>
              final comments on this action. Please send substantive
              comments to the<br>
              <a class="moz-txt-link-abbreviated"
                href="mailto:ietf@ietf.org" moz-do-not-send="true">ietf@ietf.org</a>
              mailing lists by 2017-05-14. Exceptionally, comments may
              be<br>
              sent to <a class="moz-txt-link-abbreviated"
                href="mailto:iesg@ietf.org" moz-do-not-send="true">iesg@ietf.org</a>
              instead. In either case, please retain the<br>
              beginning of the Subject line to allow automated sorting.<br>
              <br>
              Abstract<br>
              <br>
              <br>
              The YANG data modeling language is currently being
              considered for a<br>
              wide variety of applications throughout the networking
              industry at<br>
              large. Many standards-defining organizations (SDOs), open
              source<br>
              software projects, vendors and users are using YANG to
              develop and<br>
              publish YANG modules for a wide variety of applications.
              At the same<br>
              time, there is currently no well-known terminology to
              categorize<br>
              various types of YANG modules.<br>
              <br>
              A consistent terminology would help with the
              categorization of YANG<br>
              modules, assist in the analysis of the YANG data modeling
              efforts in<br>
              the IETF and other organizations, and bring clarity to the
              YANG-<br>
              related discussions between the different groups.<br>
              <br>
              This document describes a set of concepts and associated
              terms to<br>
              support consistent classification of YANG modules.<br>
              <br>
              <br>
              <br>
              <br>
              The file can be obtained via<br>
              <a class="moz-txt-link-freetext"
href="https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classification/"
                moz-do-not-send="true">https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classification/</a><br>
              <br>
              IESG discussion can be tracked via<br>
              <a class="moz-txt-link-freetext"
href="https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classification/ballot/"
                moz-do-not-send="true">https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classification/ballot/</a><br>
              <br>
              <br>
              No IPR declarations have been submitted directly on this
              I-D.<br>
              <br>
              <br>
              <br>
              <br>
              _______________________________________________<br>
              netmod mailing list<br>
              <a class="moz-txt-link-abbreviated"
                href="mailto:netmod@ietf.org" moz-do-not-send="true">netmod@ietf.org</a><br>
              <a class="moz-txt-link-freetext"
                href="https://www.ietf.org/mailman/listinfo/netmod"
                moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/netmod</a><br>
            </blockquote>
          </div>
        </div>
      </blockquote>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
netmod mailing list
<a class="moz-txt-link-abbreviated" href="mailto:netmod@ietf.org">netmod@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/netmod">https://www.ietf.org/mailman/listinfo/netmod</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------54C72DA6F31C6A8834376396--


From nobody Wed May 17 06:57:32 2017
Return-Path: <cyrus@daboo.name>
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 5423412EB33; Wed, 17 May 2017 06:57:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.797
X-Spam-Level: 
X-Spam-Status: No, score=0.797 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 M6VyhUatB5Be; Wed, 17 May 2017 06:57:28 -0700 (PDT)
Received: from daboo.name (daboo.name [173.13.55.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 08D2012EC7A; Wed, 17 May 2017 06:51:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id F0B4C6D53789; Wed, 17 May 2017 09:51:21 -0400 (EDT)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7QOO5RxFFuiv; Wed, 17 May 2017 09:51:21 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.44.178.52]) by daboo.name (Postfix) with ESMTPSA id C0D276D5377E; Wed, 17 May 2017 09:51:20 -0400 (EDT)
Date: Wed, 17 May 2017 09:51:19 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Ken Murchison <murch@andrew.cmu.edu>, Julian Reschke <julian.reschke@gmx.de>, IETF Discussion <ietf@ietf.org>, art@ietf.org
Subject: Re: [art] ART Area Review for draft-ietf-calext-caldav-attachments-02
Message-ID: <5A6C244B4A6B876F82606F31@caldav.corp.apple.com>
In-Reply-To: <a603f3de-2d96-6f86-e0c3-3e0a4884a185@andrew.cmu.edu>
References: <c04f39e2-79d2-ab9d-59ab-26e51d7ab5fc@gmx.de> <81613220-989b-ca78-fe56-0ac7b19e7ce6@andrew.cmu.edu> <b2a4924d-c7c9-b40b-484f-9fab48bfe5de@gmx.de> <a603f3de-2d96-6f86-e0c3-3e0a4884a185@andrew.cmu.edu>
X-Mailer: Mulberry/4.1.0b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=625
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5-Lqz8h0q1_y_-wF9fzoxYwwNRo>
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, 17 May 2017 13:57:31 -0000

Hi Ken,

--On May 17, 2017 at 9:07:02 AM -0400 Ken Murchison <murch@andrew.cmu.edu> 
wrote:

>> For adding, I would define an HTTP resource that can be posted to. It
>> could be discovered through a WebDAV property.
>
> We could certainly define a template or series of templates for
> add/update/delete and expose them as WebDAV properties.
>

I would be OK with adding that, provided we also include an Appendix that 
describes what currently shipping implementations do - basically what is 
coded into the current spec. i.e., the template allows the same form of 
query param based URIs as we have today.

-- 
Cyrus Daboo


From nobody Wed May 17 07:00:03 2017
Return-Path: <cyrus@daboo.name>
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 528C5129BCE; Wed, 17 May 2017 06:59:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.004
X-Spam-Level: 
X-Spam-Status: No, score=-0.004 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 ZgetMk6RsFwh; Wed, 17 May 2017 06:59:52 -0700 (PDT)
Received: from daboo.name (daboo.name [173.13.55.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 D9FB3128656; Wed, 17 May 2017 06:53:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 210C86D53811; Wed, 17 May 2017 09:53:47 -0400 (EDT)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tBeP1xenGJ55; Wed, 17 May 2017 09:53:46 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.44.178.52]) by daboo.name (Postfix) with ESMTPSA id 1D9ED6D53802; Wed, 17 May 2017 09:53:46 -0400 (EDT)
Date: Wed, 17 May 2017 09:53:44 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Ken Murchison <murch@andrew.cmu.edu>, Julian Reschke <julian.reschke@gmx.de>, IETF Discussion <ietf@ietf.org>, art@ietf.org
Subject: Re: [art] ART Area Review for draft-ietf-calext-caldav-attachments-02
Message-ID: <D109686063172A99C2FDEFC9@caldav.corp.apple.com>
In-Reply-To: <a603f3de-2d96-6f86-e0c3-3e0a4884a185@andrew.cmu.edu>
References: <c04f39e2-79d2-ab9d-59ab-26e51d7ab5fc@gmx.de> <81613220-989b-ca78-fe56-0ac7b19e7ce6@andrew.cmu.edu> <b2a4924d-c7c9-b40b-484f-9fab48bfe5de@gmx.de> <a603f3de-2d96-6f86-e0c3-3e0a4884a185@andrew.cmu.edu>
X-Mailer: Mulberry/4.1.0b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=1174
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4_Li_B_ZA6EOyrd0yu1Wm9E-HW4>
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, 17 May 2017 13:59:54 -0000

Hi Ken,

--On May 17, 2017 at 9:07:02 AM -0400 Ken Murchison <murch@andrew.cmu.edu> 
wrote:

>> Only for creation of the attachment. Once is has been created, it
>> should have its own URI, and the usual HTTP methods should be applicable.
>
> Using HTTP methods directly on the attachment URI makes things more
> difficult because the calendar resource(s) referencing the attachment
> also need to be updated.  This would have to be done either as a
> side-effect of the PUT/DELETE on the attachment, or as a separate PUT
> (and separate round-trips) on the resource(s).  The desire was to avoid
> doing either one of these, which is why a POST on the calendar resource
> was chosen as the method to add/update/delete an attachment from a
> calendar resource.

One tricky aspect here is that calendar servers may not "host" the 
attachments themselves - i.e., they could use a separate "drop box" service 
to store the resources. In that case it is important that changes to the 
attachments are always managed through the calendar server so that it can 
alert clients via changes to the calendar data whenever an attachment is 
added, changed, or removed.

-- 
Cyrus Daboo


From nobody Wed May 17 07:06:09 2017
Return-Path: <julian.reschke@gmx.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 73034129418; Wed, 17 May 2017 07:06:08 -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_50=0.8, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, 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 dJEDtbprdtcT; Wed, 17 May 2017 07:06:02 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 ADD96124281; Wed, 17 May 2017 06:58:10 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.117.158]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Lwoiq-1e45352cEC-016RvB; Wed, 17 May 2017 15:58:03 +0200
Subject: Re: [art] ART Area Review for draft-ietf-calext-caldav-attachments-02
To: Ken Murchison <murch@andrew.cmu.edu>, IETF Discussion <ietf@ietf.org>, art@ietf.org
References: <c04f39e2-79d2-ab9d-59ab-26e51d7ab5fc@gmx.de> <81613220-989b-ca78-fe56-0ac7b19e7ce6@andrew.cmu.edu> <b2a4924d-c7c9-b40b-484f-9fab48bfe5de@gmx.de> <a603f3de-2d96-6f86-e0c3-3e0a4884a185@andrew.cmu.edu>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <7bcfecea-3a89-978c-9e1b-edf9aac5dd44@gmx.de>
Date: Wed, 17 May 2017 15:58:00 +0200
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: <a603f3de-2d96-6f86-e0c3-3e0a4884a185@andrew.cmu.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:w6GTVvb1P50+BbhIgQc9idkKIq+GaHaSg7av9cY3+/lIykUj/2r vXNsT7+0USymC6z4xGuP+9snrxaev3FiyA/eKrJyUHXHzuqCugmYrFxi08DWTrJ/U6jEPB2 u3u26aS9wxwswMatDAu92s0hvQirex94q+e8OY1CPwX+KAcm/g6GdTunouvsykum/cAIhOL JQ0EVyS67AR9BQdO+OVrQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:MwWTpvXgYYw=:Kc50tQ9aKrXyRdwtW3e/h6 jZsn92p8Z6fzFDp+7sKGlbPeObFlMBANDJkmcpidDi/t6/btSuIi5+mJUt27rx/ns77p1/20p gN38NqrT00rJ0A24PZ1Y20wZklygbd7erjPtsBROrVCDON46hv3WJZXteN2CprgS47EGKI+cA nrYKuPpLbXh+1UyyzO3emTbEZZ6UF3licBSp8BiSubxlcQbszaAFJ6wViLrGm3Ev2GF5S102T ni+5Qi2XmsVTo3sIL22qSMmqAsXoAj9ZvO34C3bqs0AQX+HNsA4jeS8CCKMm6ToYcAR+8hRtt 131bn1kDpiSU7LBkkfH8doSqZV9WFNLG2FbFt7RyUjwj21fbLqkdZFR7ZE9bwAjokqODXKIN1 66iUpsqBKeJ8D7c6/V5J2/fU5YPEjBvlCcIMA5voBo29PcJrbtYEFkqvsj2B+rgsYj0TVJhe4 axcXwqWpBzhvCv3Kf009c0A7H0rw0nu0Byfcc0qfSd1GzJV4TtJyVi86GlvW4JQTbTVKXDzvF edeRXipijKtwG4cORkKTk7zotHn1tGepzxOaTymoOb7V+59eQnZoCevy4XjZ9u43w/tl3jllj tuRZgDOmFZxR3c0BstU1E7EQG89fYaop3W7X2A48/11PuYxE6QoAXcmnOX2pFrJghkHcYfv8o vhvfvcmW9yDv+CxcyXixWCC9BMGjfZxyi2+74vUvt3NjUAEle0ceg7KkgikjiGf9HqY+ZPYDU JYYOzxsTRIcY6c3DGof2M2YrVVLfPY//xxYehSnwSCt9r4A5lwXpNjwsUX2m0IG3JuEOPlM2w 9h1dvWn
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9lpeWzjalYub5C_7Re7WvtjQQDw>
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, 17 May 2017 14:06:08 -0000

On 2017-05-17 15:07, Ken Murchison wrote:
> ...
>> Only for creation of the attachment. Once is has been created, it
>> should have its own URI, and the usual HTTP methods should be applicable.
>
> Using HTTP methods directly on the attachment URI makes things more
> difficult because the calendar resource(s) referencing the attachment
> also need to be updated.  This would have to be done either as a
> side-effect of the PUT/DELETE on the attachment, or as a separate PUT
> (and separate round-trips) on the resource(s).  The desire was to avoid
> doing either one of these, which is why a POST on the calendar resource
> was chosen as the method to add/update/delete an attachment from a
> calendar resource.

But the POST is *not* on the calendar resource, but on the calendar 
resource + query parameters, which, from HTTP's point of view is a 
different resource already.

Furthermore, what URIs are used is orthogonal to the question of which 
methods to use.

Why is

   POST /calendar-entry?action=remove&attachment=xyz

easier to process than

   DELETE /calendar-entry?attachment=xyz

or

   DELETE /calendar-entry/attachments/xyz

?

> ...

Best regards, Julian


From nobody Wed May 17 07:10:19 2017
Return-Path: <julian.reschke@gmx.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 2C84F129537; Wed, 17 May 2017 07:10:11 -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_50=0.8, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, 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 yrdb2EgAro7M; Wed, 17 May 2017 07:10:10 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.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 4D7EB12EBBD; Wed, 17 May 2017 07:01:45 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.117.158]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MXZw6-1dWNjz11hG-00WY5i; Wed, 17 May 2017 16:01:29 +0200
Subject: Re: [art] ART Area Review for draft-ietf-calext-caldav-attachments-02
To: Cyrus Daboo <cyrus@daboo.name>, Ken Murchison <murch@andrew.cmu.edu>, IETF Discussion <ietf@ietf.org>, art@ietf.org
References: <c04f39e2-79d2-ab9d-59ab-26e51d7ab5fc@gmx.de> <81613220-989b-ca78-fe56-0ac7b19e7ce6@andrew.cmu.edu> <b2a4924d-c7c9-b40b-484f-9fab48bfe5de@gmx.de> <a603f3de-2d96-6f86-e0c3-3e0a4884a185@andrew.cmu.edu> <D109686063172A99C2FDEFC9@caldav.corp.apple.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <ffeb5967-a0ff-c0cc-0140-d6c42fc4ec23@gmx.de>
Date: Wed, 17 May 2017 16:01:20 +0200
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: <D109686063172A99C2FDEFC9@caldav.corp.apple.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:Sk8ZU+ZN4nmfIWLo8PmVmC++wsVKMHckaY/9IhmOWsdaXzGtl5L nKsg7bre4vuobywgm9lr+nNZFbIa2k2JGi/1y0aO+ZYmXc0iIZoObXbjtbozdMpB+mqyD3x m8sPu7Ne0grghandgNz+YgplMJLQ85xqrz8IFz6Y4Y2wu199yOF7dED7HDaC3F/k7I0N3zy AYLfWDkX89lPBpwRvmWOQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:0G5DnqNmknM=:g6DXoFbtgjidE+tbRerKYd DENIAuq8rQeJ/1XuoNhVtvTi4o4RH5tGfxaLJ8q83ju93T+x5LKZWfNEm5fScOcdKbzyqJLgX YMvh8mFUsSvYUDehT4PrnFBWl7WaLKrY/7VypOVraF5QmWI3BF24B4R73ona5MxG9uxY06Ri8 pMFKIgpEDjgM+dK74Af2zen2zc5+7gcy/IdJEu7v03d9CbyjwdpmGNScesiXL8Dp9d+8hcdub MyolTjoqpj0icSRCd8CupMByYldWwqA6CVZ73LHhNKuSatH0L0Q8KfeHmFPiS2Dna9aa+bgxw XmkgSi4p91CKqvs9sL/bZyWNxEnNj5/4UbXsVQqDnB6UvN7leqR0KyBSJ/ILZD2HsxvPXkNyA sFjQLIthVx9+x6CSksKEqSphWCCohGFUZ7/vuno4pReZ7qR+DWaEKf2rEsepyABVTbnrO39og JxaEkFyvvhToaVbaBFPr1l5a0yravgwG1U4ytX319OnpE4CinyXAhYeKjbJ6w1Am2y4rtQSHN K+OU+Lsb8HLFtZuOmSt86tCUoC8a5RA7MI7g3AJOJDzAeFbrkd0ZMPKYtztGwrEK4dyiIJFsH 5otV0x5kwQNLxaArWV9tZ3Jc5c1XesQxbgCRM98dKppDNUa37AHo1xAAaNCl3tHwfO4UZATbY oqO3d+mDynV0yEn4QF7a2eeDtIHaHfOXU9i2so5eMB9QMr0UEUg1fhOepni98uWG8dRn1t9rT GVvgiZKfNSsXJFk/Yr1lMjVPoLOLsGwGMp5hVAwsvIwQ8I83TnjxxDukszmsF8XCJ/hpDnveD bCFeKq3
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8XnQSAnkUQcnHmitWUijvzdbju4>
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, 17 May 2017 14:10:11 -0000

On 2017-05-17 15:53, Cyrus Daboo wrote:
>> Using HTTP methods directly on the attachment URI makes things more
>> difficult because the calendar resource(s) referencing the attachment
>> also need to be updated.  This would have to be done either as a
>> side-effect of the PUT/DELETE on the attachment, or as a separate PUT
>> (and separate round-trips) on the resource(s).  The desire was to avoid
>> doing either one of these, which is why a POST on the calendar resource
>> was chosen as the method to add/update/delete an attachment from a
>> calendar resource.
>
> One tricky aspect here is that calendar servers may not "host" the
> attachments themselves - i.e., they could use a separate "drop box"
> service to store the resources. In that case it is important that
> changes to the attachments are always managed through the calendar
> server so that it can alert clients via changes to the calendar data
> whenever an attachment is added, changed, or removed.

Again, that's an implementation detail. Just because the calendar server 
stores attachments somewhere else doesn't mean it has to expose those URIs.

Best regards, Julian



From nobody Wed May 17 18:34:47 2017
Return-Path: <amy.yemin@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 BA7F9129461; Wed, 17 May 2017 18:34:31 -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, 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 YqLnq8j1cTD1; Wed, 17 May 2017 18:34: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 977B9129455; Wed, 17 May 2017 18:34:28 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DNG38751; Thu, 18 May 2017 01:34:26 +0000 (GMT)
Received: from DGGEML405-HUB.china.huawei.com (10.3.17.49) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 18 May 2017 02:34:25 +0100
Received: from DGGEML509-MBX.china.huawei.com ([169.254.1.14]) by dggeml405-hub.china.huawei.com ([10.3.17.49]) with mapi id 14.03.0301.000; Thu, 18 May 2017 09:34:20 +0800
From: "Yemin (Amy)" <amy.yemin@huawei.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>
CC: "ospf@ietf.org" <ospf@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-ospf-ospfv3-lsa-extend.all@ietf.org" <draft-ietf-ospf-ospfv3-lsa-extend.all@ietf.org>
Subject: RE: Rtgdir early review of draft-ietf-ospf-ospfv3-lsa-extend-14
Thread-Topic: Rtgdir early review of draft-ietf-ospf-ospfv3-lsa-extend-14
Thread-Index: AQHSzwYeJ6QO1mB4GE+TPaqcTtLKAaH5Ty+A
Date: Thu, 18 May 2017 01:34:20 +0000
Message-ID: <9C5FD3EFA72E1740A3D41BADDE0B461FC6BA7F39@dggeml509-mbx.china.huawei.com>
References: <149501293882.6715.9441857001639471954@ietfa.amsl.com> <D541B500.AF34E%acee@cisco.com>
In-Reply-To: <D541B500.AF34E%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.169.31.176]
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.0A020205.591CFA23.0007, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.1.14, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: d43c34b6ff31f284a66ccc5f19666669
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fzLl8tfv5c9NdHxaf8X2JC5z5m0>
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, 18 May 2017 01:34:32 -0000

SGkgQWNlZSwgDQoNClRoYW5rcyBmb3IgY29ycmVjdGlvbi4gSSB1cGRhdGVkIHRoZSByZXN1bHQg
YXMgIlJlYWR5Ii4gDQoNCkJSLA0KQW15DQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpG
cm9tOiBBY2VlIExpbmRlbSAoYWNlZSkgW21haWx0bzphY2VlQGNpc2NvLmNvbV0gDQpTZW50OiBX
ZWRuZXNkYXksIE1heSAxNywgMjAxNyA4OjA3IFBNDQpUbzogWWVtaW4gKEFteSkgPGFteS55ZW1p
bkBodWF3ZWkuY29tPjsgcnRnLWRpckBpZXRmLm9yZw0KQ2M6IG9zcGZAaWV0Zi5vcmc7IGlldGZA
aWV0Zi5vcmc7IGRyYWZ0LWlldGYtb3NwZi1vc3BmdjMtbHNhLWV4dGVuZC5hbGxAaWV0Zi5vcmcN
ClN1YmplY3Q6IFJlOiBSdGdkaXIgZWFybHkgcmV2aWV3IG9mIGRyYWZ0LWlldGYtb3NwZi1vc3Bm
djMtbHNhLWV4dGVuZC0xNA0KDQpIaSBNaW4gLA0KDQpPbiA1LzE3LzE3LCA1OjIyIEFNLCAiTWlu
IFllIiA8YW15LnllbWluQGh1YXdlaS5jb20+IHdyb3RlOg0KDQo+UmV2aWV3ZXI6IElKc2JyYW5k
IFdpam5hbmRzDQo+UmV2aWV3IHJlc3VsdDogSGFzIElzc3Vlcw0KDQpJIHRoaW5rIHRoZSByZXN1
bHQgaXMg4oCcTm8gSXNzdWVz4oCdLg0KDQpUaGFua3MsDQpBY2VlDQo+DQo+SGkgQWxsLA0KPg0K
PkkgaGF2ZSBiZWVuIHNlbGVjdGVkIHRvIGRvIGEgcm91dGluZyBkaXJlY3RvcmF0ZSBRQSByZXZp
ZXcgb2YgdGhpcyANCj5kcmFmdC4NCj5odHRwczovL3d3dy5pZXRmLm9yZy9pZC9kcmFmdC1pZXRm
LW9zcGYtb3NwZnYzLWxzYS1leHRlbmQtMTQudHh0DQo+DQo+U3VtbWFyeTogDQo+DQo+VGhpcyBk
cmFmdCBwcm9wb3NlcyBhIG5ldyBhZGRyZXNzaW5nIChUTFYpIGZvcm1hdCB0byBtb3JlIGVhc2ls
eSBhbGxvdw0KPg0KPmFkZGl0aW9uYWwgaW5mb3JtYXRpb24gdG8gYmUgYWRkZWQgYXMgcGFydCBv
ZiBhIHBhcnRpY3VsYXIgTFNBLg0KPk92ZXJhbGwsIHdlbGwgd3JpdHRlbiwgZWFzeSB0byB1bmRl
cnN0YW5kIHdoYXQgdGhlIG9iamVjdGl2ZSBpcyBmb3IgDQo+dGhpcyBkcmFmdC4NCj4NCj5Db21t
ZW50cyBhbmQgUXVlc3Rpb25zOg0KPg0KPlRoaXMgbG9va3MgbGlrZSBhIHByZXR0eSByYWRpY2Fs
IGNoYW5nZSB0byB0aGUgT1NQRnYzIHNwZWMuIEkgd291bGQgDQo+YWxtb3N0IGFyZ3VlIHRvIGNh
bGwgaXQgT1NQRnY0Li4NCj4NCj5JdHMgdmVyeSB1bmZvcnR1bmF0ZSB0aGVyZSBhcmUgbm8g4oCY
cmVzZXJ2ZWTigJkgZmllbGRzIGluIFJGQzUzNDAgdGhhdCANCj53b3VsZCBhbGxvdyB5b3Uga2Vl
cCB0aGUgZXhpc3RpbmcgTFNB4oCZcyBmb3JtYXQgYW5kIGhhdmUgc29tZSB3YXkgdG8gDQo+ZXh0
ZW5kIGl0IGRpZmZlcmVudGx5LiBUaGUgVExWIGFwcHJvYWNoIGxvb2sgZ29vZCwgSSBjYW7igJl0
IHNlZSBhIGJldHRlciANCj53YXkgdG8gYWNoaWV2ZSB0aGUgZ29hbC4NCj4NCj5NaW5vciBJc3N1
ZXMgYW5kIE5pdHM6DQo+bm9uZS4NCj4NCj5UaHgsDQo+DQo+SWNlLg0KPg0KPg0KDQo=


From nobody Wed May 17 20:26:45 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 780D612EB84 for <ietf@ietfa.amsl.com>; Wed, 17 May 2017 20:26:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=lB0MyGD1; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=sC4gYB01
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ssmnwsgweSw0 for <ietf@ietfa.amsl.com>; Wed, 17 May 2017 20:26:41 -0700 (PDT)
Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0B74129AD8 for <ietf@ietf.org>; Wed, 17 May 2017 20:22:15 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.nyi.internal (Postfix) with ESMTP id 26828CC; Wed, 17 May 2017 23:22:15 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Wed, 17 May 2017 23:22:15 -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=XF0n6QMHhD7Zl9VqBB IbfsM8+0EdBmuUodeoZhKUSO0=; b=lB0MyGD1vfkYCdKINmW6m8QSLg70A73sJl LQVDkbth2/BMzJwd8a790PpIGVMnQd1JpwlFoQGLrWWxK952IejUoERZNo71tbqh BQ7fWvvEn+n2e8/xUILIHsveA41X0q0c0ukxagxPBxNvQeOT8qGgHENk3xQ8CPUu wOWG+625HS5io4dAeom9UB6cesU4vkYSfyScGdMJFAqRL3wp0Npf+xs1IR5zIEiF T1TYlGquOtKUTSTABsmxVbYPBr3ha+wN9mDbecWaIsQ+PSY701nKZTCTT+Saer0W gHigSx67oGSDpQP+waKuwkcQ1oSUQGgjiYVLm/zFWT7HnPJBcPZw==
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=XF0n6QMHhD7Zl9VqBBIbfsM8+0EdBmuUodeoZhKUSO0=; b=sC4gYB01 I2TAESGyGNqxYpLHixEmYLUmc9VuaFt3lep71bEPJGKZHCM56ytGY2w85IGZnz9W 7lhEAjdYP07oEsX38QDUdZ3bWMisTqS4IHpiHwvz61hvkUP4NkXcTqum8Qitx1GT mcoyJVC5v+m56a2PpFb19YvSTnLOYSa6uJhwnyJFQgygJPJJGincKBSkw9tCD/c6 fk5k3JyHAy4YcvZMELSoEYrrVf8JmoqFd0R3WWW6j9V/tP+53MM9XEoyZarzyh/0 75D1q2YUz0OXMHOc0Rn1C4t7/+etytzYMTeALTiyBo2txKwUBM1helRqRQ8ooqHv lLtz80EXOlftHA==
X-ME-Sender: <xms:ZhMdWa8yZPZ3et6scR7FJeKnZ5c19qowAaJB76DX29_fMzTGchajQg>
X-Sasl-enc: +2CupAqt+MRAyVic+jrCy1INvVGnKghFu5c1eGqsXxnL 1495077734
Received: from [192.168.1.18] (cpe-124-188-19-231.hdbq1.win.bigpond.net.au [124.188.19.231]) by mail.messagingengine.com (Postfix) with ESMTPA id E4CE3247F0; Wed, 17 May 2017 23:22:13 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Last Call: <draft-nottingham-rfc5988bis-05.txt> (Web Linking) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <5b94ecb4-b317-38ec-aa10-dc166faac5d0@gmx.de>
Date: Thu, 18 May 2017 13:22:10 +1000
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <77A93621-A2F2-4D15-AE00-EFB6CBDD5C3E@mnot.net>
References: <588716b3-161c-62ac-e5a9-a04c86f13e86@gmx.de> <704BC987-1ED0-4E59-A803-0B4013A86F03@mnot.net> <c81eb293-f443-8d61-bd82-b7c2902e4426@gmx.de> <09EA3303-8F65-4FDE-8303-8C2AD9B8B897@mnot.net> <280366F3-ECDA-44A2-820A-33FD5965EAFD@mnot.net> <5b94ecb4-b317-38ec-aa10-dc166faac5d0@gmx.de>
To: "Julian F. Reschke" <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/I5NNv6Gkbq8lZbYDm4ZYiWtbdM8>
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, 18 May 2017 03:26:43 -0000

> On 17 May 2017, at 8:41 pm, Julian Reschke <julian.reschke@gmx.de> =
wrote:
>=20
> On 2017-05-16 04:37, Mark Nottingham wrote:
>> ...
>> This is what I currently have:
>>  https://gist.github.com/mnot/2fb569e7303dbcdde8b27cb7a404a648
>>=20
>> I need to get some more eyeballs onto it to make sure it's correct =
(or at least reasonable). Reviews appreciated.
>> ...
>=20
> I think this goes into the right direction; it's mostly a parser based =
on a relaxed ABNF transformed to prose (which makes me wonder whether =
there's a tool to be written here :-).
>=20
> Other comments:
>=20
> 1)  "... If it is not present, context_string is the identity of the =
representation carrying the Link header ..." - similar prose is =
elsewhere in the spec - what is "the identity of a representation"?????

See the linked reference. Would it be better to use "URL" instead of =
"identity"?


> 2) "Consume the contents up to but not including the first DQUOTE =
character that is not preceded by a "" character" - I assume there's a =
backslash missing here. That said: doesn't work, because it would fail =
for an input such as: "\\" - here, the DQUOTE is preceded by backslash, =
but it's not part of the quoted-pair.

I've updated to address this.

Thanks,


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


From nobody Wed May 17 22:07:41 2017
Return-Path: <julian.reschke@gmx.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 83DF81294B3 for <ietf@ietfa.amsl.com>; Wed, 17 May 2017 22:07:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.5
X-Spam-Level: 
X-Spam-Status: No, score=-3.5 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FREEMAIL_FROM=0.001, 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 n8BuP1YV6zXc for <ietf@ietfa.amsl.com>; Wed, 17 May 2017 22:07:37 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 185A1129ABE for <ietf@ietf.org>; Wed, 17 May 2017 22:02:36 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.121.200]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MOCSm-1d5jwK1t5A-005Vx6; Thu, 18 May 2017 07:02:32 +0200
Subject: Re: Last Call: <draft-nottingham-rfc5988bis-05.txt> (Web Linking) to Proposed Standard
To: Mark Nottingham <mnot@mnot.net>
References: <588716b3-161c-62ac-e5a9-a04c86f13e86@gmx.de> <704BC987-1ED0-4E59-A803-0B4013A86F03@mnot.net> <c81eb293-f443-8d61-bd82-b7c2902e4426@gmx.de> <09EA3303-8F65-4FDE-8303-8C2AD9B8B897@mnot.net> <280366F3-ECDA-44A2-820A-33FD5965EAFD@mnot.net> <5b94ecb4-b317-38ec-aa10-dc166faac5d0@gmx.de> <77A93621-A2F2-4D15-AE00-EFB6CBDD5C3E@mnot.net>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <9f065b23-59bc-fb1d-6d2d-434d0253475c@gmx.de>
Date: Thu, 18 May 2017 07:02:29 +0200
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: <77A93621-A2F2-4D15-AE00-EFB6CBDD5C3E@mnot.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:UAv/HrBaVe5CFo6G9nfXYT/Qv+zLPFBZgkooYG7On4+2QJ2zSX0 D1PlcSKiPxKKS/MVgPZTAqt4hHuhQBkFj9Wdl172y9t3o+UMx/xEzJtx+BDYyZBaoy+57Op B5sqHcPF3J/omvtdpXpBMdKhm3b/I40TBabBLbptHGqP3vHpNJHeue0o7f6ckD+g4K1s2Ym VxIl5Yf0k5pEvDLVSMlAg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:VtNblVgslwU=:qcgbsChUkQp8A/2T+JY0HN V1pJbZqq4XLGnk+dBIYFtkQHvMp8I2GTVSjdxrkl/RIupFUTUvtxOARLvZp9vHzi+DFMtkqbH M/PTZmEEZuytPhAioFrnBZ21d2NnGww/eDvDSP4hUJQHdq1eDQkLLjo4PSBzYF3e7XX8J7kbK YARKE8BTysN2OiPNf4Mi9xB0pcEhnQCh9+/baE4lD5Vqvc7FRKdo8zyzRAaBoTTX/rOcdW3vH LouL4JvJskCxbJKGwHZ5oD8X2BB0+bFQC6xacBGHGh89xbua3WykwA1O/UWeyHuRpbnoITXnP xuHfiJwgPHPvRjcPfPf1x1qw60LL85s9DcsFl+VyoLL/a/U9Szx8B9XO0JzKTOaT5bwJaQEAg 1qDW/nq+PmApdw5R/iiQsl9EWhTLEZD3FjXMIffm67mK31xiw7lG/13JXsGi3DIHXTY9ry5Ly caOdJzJtn81RDDrXHkMUwSUKOdrzsxXKGPehcoDnaEAIxye3/soyrvK1I3aePiT0PzSJibDHO Gd3p+50cY7OeZsY2WYWQWr2mreWSDrS+jvAPUMvlSDR+tWBlzzFlBP/Gtmj//ShHFhzCJi6ed Fz5RC0T/c5e1t5NC7h6l0SHBjBGsKG5hN9ZqC8uDjh53yYX8STdo5cB9MAu+MmqI0M4Ydql0x cmd2J25RS/kXz54TmNF+CnOKNcAMut9YAFp/zUdzNDwhkrv+7upmSNwG2HDKRmRQ/N73cz4Yn CQnx6swBjc3xU602DGyOFXMWjW2QkTRNTeQVOBYAYLITRowiFrh9Gf73j+ObxU/U3Zz14srPm XO2odI8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/f2pBUIyVmcRYcntMOiZe8D5j6lk>
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, 18 May 2017 05:07:39 -0000

On 2017-05-18 05:22, Mark Nottingham wrote:
>
>> On 17 May 2017, at 8:41 pm, Julian Reschke <julian.reschke@gmx.de> wrote:
>>
>> On 2017-05-16 04:37, Mark Nottingham wrote:
>>> ...
>>> This is what I currently have:
>>>  https://gist.github.com/mnot/2fb569e7303dbcdde8b27cb7a404a648
>>>
>>> I need to get some more eyeballs onto it to make sure it's correct (or at least reasonable). Reviews appreciated.
>>> ...
>>
>> I think this goes into the right direction; it's mostly a parser based on a relaxed ABNF transformed to prose (which makes me wonder whether there's a tool to be written here :-).
>>
>> Other comments:
>>
>> 1)  "... If it is not present, context_string is the identity of the representation carrying the Link header ..." - similar prose is elsewhere in the spec - what is "the identity of a representation"?????
>
> See the linked reference. Would it be better to use "URL" instead of "identity"?

URL (or URI).

>> 2) "Consume the contents up to but not including the first DQUOTE character that is not preceded by a "" character" - I assume there's a backslash missing here. That said: doesn't work, because it would fail for an input such as: "\\" - here, the DQUOTE is preceded by backslash, but it's not part of the quoted-pair.
>
> I've updated to address this.

Goes into the right direction, but doesn't seem to be correct yet:

> 4. While input has content:
>
>     i. If the first character is a backslash ("\"):
>
>         1. Discard the first character.
>
>         2. If there is no more input, return output.
>
>         3. Else, consume the first character and append it to output.
>
>     ii. Else, if the first character is DQUOTE, discard it and return output.

There seems to be missing a step between (i) and (ii) for non-quoted-pairs.

Best regards, Julian


From nobody Wed May 17 23:30:13 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 60BDB12EBBD for <ietf@ietfa.amsl.com>; Wed, 17 May 2017 23:30:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=amdN20/7; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=aM9u33/a
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8tnXqefcPqxD for <ietf@ietfa.amsl.com>; Wed, 17 May 2017 23:30:09 -0700 (PDT)
Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1349B12947F for <ietf@ietf.org>; Wed, 17 May 2017 23:25:20 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.nyi.internal (Postfix) with ESMTP id 776DDEE6; Thu, 18 May 2017 02:25:19 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Thu, 18 May 2017 02:25:19 -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=koTB8/UNgLJG44jk80 n+beFiAtkr/MNn3nnfafFZe4U=; b=amdN20/72sYJ7ooPebCghHAkug/hZpFuO4 ANrS0RIBwAhb9dZBQBpauFvfFDECHPbkTNFgzodg+QBzvSKIMFGgHGvC4fKDn121 K98ySJiGhaXx7gWFlsuC8RWSN8ETdWfmNwaZXWOWzTAmEW9/tvx+TsRYo9P/xjud YoTaJeH1sXrjowFRzeyJ2AvQBxb+71Q04dTciquSmHqOky30jv9vG5Mkcm10Ru0w Os1DNfvUpL766T796dnANahk3wS/1nyFk+BRCAjqMGF+z/IhYNzKDfNZIJhgJsuE s11kA7t21XFTOr0eWcnPk35i+NFZfbXaPpYDzfZdV8DohimQkXTg==
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=koTB8/UNgLJG44jk80n+beFiAtkr/MNn3nnfafFZe4U=; b=aM9u33/a Jwuni1qhm1/aIQQy3CzxFWJf5VgQkj1ciUSVEkUjs+MKQhQ70htK4LqCjzi6eOoV RyPPqCOArJHvCJLOxJ0LxvnNUJK48F1Cw277PO1Rvo4j/16aRQMHtmiBo9jtD6zU drgS01cJg7bhBmvG54K6BHP43KBMvo9hePSzoQtLFHg6cjx2p7N0FGD0Jevg+7NB xS4OLP0eemYNVogPJsMtzs1NZNTEwHWWwP4uJn/HYhzg9LeBS9W2asdFuBgJIK9L CdQmegBhAk3e70ToOUVt/TS6xxtPCTvmR+LDohbl9n/amPXmiypii8Os+in6HrUO YBU7hDJpsyVt1g==
X-ME-Sender: <xms:Tj4dWec0tA323EK-OIVcbHxbQL3bNmDoVCqYuYeLyW6pOlRiRt-93g>
X-Sasl-enc: ityMd+1x35Q+u9vIUNV93B0AoeFfdIwWuCJE3+MH6SpK 1495088718
Received: from [192.168.1.18] (cpe-124-188-19-231.hdbq1.win.bigpond.net.au [124.188.19.231]) by mail.messagingengine.com (Postfix) with ESMTPA id 851277E6E5; Thu, 18 May 2017 02:25:17 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Last Call: <draft-nottingham-rfc5988bis-05.txt> (Web Linking) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <9f065b23-59bc-fb1d-6d2d-434d0253475c@gmx.de>
Date: Thu, 18 May 2017 16:25:16 +1000
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7BB9FE83-8009-405C-8F0B-CA867061DD24@mnot.net>
References: <588716b3-161c-62ac-e5a9-a04c86f13e86@gmx.de> <704BC987-1ED0-4E59-A803-0B4013A86F03@mnot.net> <c81eb293-f443-8d61-bd82-b7c2902e4426@gmx.de> <09EA3303-8F65-4FDE-8303-8C2AD9B8B897@mnot.net> <280366F3-ECDA-44A2-820A-33FD5965EAFD@mnot.net> <5b94ecb4-b317-38ec-aa10-dc166faac5d0@gmx.de> <77A93621-A2F2-4D15-AE00-EFB6CBDD5C3E@mnot.net> <9f065b23-59bc-fb1d-6d2d-434d0253475c@gmx.de>
To: "Julian F. Reschke" <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9LfLra7zB3nx7UcOZPC1YViZdyY>
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, 18 May 2017 06:30:12 -0000

See changes:
  https://github.com/mnot/I-D/commit/143403a2e7e37

In situ:
  https://mnot.github.io/I-D/rfc5988bis/


> On 18 May 2017, at 3:02 pm, Julian Reschke <julian.reschke@gmx.de> =
wrote:
>=20
> On 2017-05-18 05:22, Mark Nottingham wrote:
>>=20
>>> On 17 May 2017, at 8:41 pm, Julian Reschke <julian.reschke@gmx.de> =
wrote:
>>>=20
>>> On 2017-05-16 04:37, Mark Nottingham wrote:
>>>> ...
>>>> This is what I currently have:
>>>> https://gist.github.com/mnot/2fb569e7303dbcdde8b27cb7a404a648
>>>>=20
>>>> I need to get some more eyeballs onto it to make sure it's correct =
(or at least reasonable). Reviews appreciated.
>>>> ...
>>>=20
>>> I think this goes into the right direction; it's mostly a parser =
based on a relaxed ABNF transformed to prose (which makes me wonder =
whether there's a tool to be written here :-).
>>>=20
>>> Other comments:
>>>=20
>>> 1)  "... If it is not present, context_string is the identity of the =
representation carrying the Link header ..." - similar prose is =
elsewhere in the spec - what is "the identity of a representation"?????
>>=20
>> See the linked reference. Would it be better to use "URL" instead of =
"identity"?
>=20
> URL (or URI).
>=20
>>> 2) "Consume the contents up to but not including the first DQUOTE =
character that is not preceded by a "" character" - I assume there's a =
backslash missing here. That said: doesn't work, because it would fail =
for an input such as: "\\" - here, the DQUOTE is preceded by backslash, =
but it's not part of the quoted-pair.
>>=20
>> I've updated to address this.
>=20
> Goes into the right direction, but doesn't seem to be correct yet:
>=20
>> 4. While input has content:
>>=20
>>    i. If the first character is a backslash ("\"):
>>=20
>>        1. Discard the first character.
>>=20
>>        2. If there is no more input, return output.
>>=20
>>        3. Else, consume the first character and append it to output.
>>=20
>>    ii. Else, if the first character is DQUOTE, discard it and return =
output.
>=20
> There seems to be missing a step between (i) and (ii) for =
non-quoted-pairs.
>=20
> Best regards, Julian

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


From nobody Thu May 18 05:43:49 2017
Return-Path: <alissa@cooperw.in>
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 712CB129C5A for <ietf@ietfa.amsl.com>; Thu, 18 May 2017 05:43:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.02
X-Spam-Level: 
X-Spam-Status: No, score=-0.02 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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 (2048-bit key) header.d=cooperw.in header.b=BoMeNlH1; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=C2um/30c
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NkjNCi6jcvio for <ietf@ietfa.amsl.com>; Thu, 18 May 2017 05:43:44 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD960129C59 for <ietf@ietf.org>; Thu, 18 May 2017 05:38:45 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 02BA821C33 for <ietf@ietf.org>; Thu, 18 May 2017 08:38:45 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Thu, 18 May 2017 08:38:45 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= 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=XKC9t9sx/P9R27stW4 V6EDWj6D/NS9hpiMLz48jIj0M=; b=BoMeNlH1tl/HlpeyvAVe8C+jLCQZDQf+0E g/pd9OJ9m9NfVv5E3nl3cpcJ7+vbYTeLCXmAje+7fvPVcylzor+MFtDVejtp9tJr Mnge6gkRICqCwq2R/L89Ps6NrXAAGYhsuhPX4Zs8WDZpRcFF0RqWaSBdlAHqHI4E BTy2RV/80HYGS/qid4IMdv+FR+QE8Ps4spYKGjrSgN3sZzvbgI0yypqT0gOj9Dwv qkqmxyaYtuOt3hbWIoyz5Ulz/3v5geEM4bHPj7h7CgrJj0S+/KdEkXAIeURMFXxL /p1nCFLVQNXz6pvphuAqeNFZuubmeHAfeXFnj8DKVeJjqQzr2Zmg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=XKC9t9sx/P9R27stW4V6EDWj6D/NS9hpiMLz48jIj0M=; b=C2um/30c GRfCsbAOHV7367xtJtYafUxHVTAYmO4vXvEFo+FXef9TDGCswlqyf7XHmvOQ94MV +77t8Uin8ZuwsGw2lH2xf2ZtpLDAHAxzy70UCSxwzw75guLXR2IVRB/jZUtf4G2f Ohy5TksPXeYZ9kw3w+y1x2Zv6YD9REzCWQfuiWKtMbxhYP1kWMi9hKj2yiTHCnvQ TAuAkJYE78VCNax2o0+tOvhBeVwLG+GH0ULX2t4RYX47vMepRQwX/LF+tBo9h2H7 lArbkxQvz33vdRBNYmStz/17Yzar4nnw6HUJIXOuH0p+BBuo/76LTmu1MVG5Dfs2 /Y0ZC1OGA8aHjQ==
X-ME-Sender: <xms:1JUdWUNpwvFLa1lAKwOiiOB1KIJAfsbsojeSGXqnwUB8cv5VrRDDVg>
X-Sasl-enc: ItRKMiHLOKjkDgL2eT35O04HenUg3MIq4uKU3JxZbKl0 1495111124
Received: from rtp-vpn2-1797.cisco.com (unknown [173.38.117.72]) by mail.messagingengine.com (Postfix) with ESMTPA id AD1587E7E6 for <ietf@ietf.org>; Thu, 18 May 2017 08:38:44 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Registration for remote participation
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
Date: Thu, 18 May 2017 08:38:44 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2E6EBACA-1C5C-4E61-A5BA-664F4DA42D35@cooperw.in>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RTnJuy0lej1-5TiGcZtWWPgXE6o>
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, 18 May 2017 12:43:46 -0000

Thanks all for the feedback on this proposal thus far. I wanted to =
provide a couple of reactions:

- No changes are being proposed regarding live audio streams. These =
would continue to be available to anyone without registration.

- The feedback about other information to solicit or questions to ask of =
registrants is much appreciated. I'll make sure the IESG, IAOC, =
secretariat, and MeetEcho team review the suggestions so we can refine =
the questions on the registration form and perhaps also the post-meeting =
survey. We should probably do this regardless of whether registration is =
required or not.

- In the data that MeetEcho already collects, they distinguish between =
those who join a session while connected to the IETF meeting network and =
everyone else. This doesn't capture all of the cases mentioned in the =
thread (e.g., joining from another location nearby the meeting), but it =
does cover some.

- Regarding charging, it's possible that we could think about charging =
for remote registration in the future. Or not. Or getting it sponsored, =
or changing the in-person meeting fee, or changing nothing ... basically =
it is as Jari said, perhaps a discussion for the future. But from my =
perspective the important things would be: (1) community discussion of =
any proposed changes, (2) understanding the remote participant user =
base, the motivations for charging or not charging, and the expected =
outcome of any proposed changes, and (3) having confidence in any system =
we have in place that is predicated on charging (e.g., we don't want =
people to feel that they are being cheated out of their registration fee =
because the system is easily circumventable).

- We could potentially do email validation, although for the purposes of =
getting more accurate data I'm not sure it adds a lot of value. My sense =
is that the noise in our current data set arises from people inputting =
different variations of their name when they join without a registration =
ID. I don't think people are deliberately trying to skew the data, so I =
wouldn't anticipate that if we require registration that people will =
register with multiple different email addresses in order to obtain =
multiple registration IDs, regardless of whether we validate the email =
addresses. Or, if they are looking to do Donald Duck registrations for =
an IPR-related purpose, they could still obtain two registration IDs by =
registering with two different email addresses that both validate. But I =
completely agree that leveraging datatracker logins could be quite =
useful going forward.=20

- Everyone who registers for a meeting, whether it be in-person or =
remote, is already presented with the Note Well and asked to acknowledge =
it as the first step in the registration process (see =
https://ietf.org/meeting/register.html and =
https://ietf.org/meeting/remote-registration.html).

- The data that we can currently collect can be quite noisy, which is =
why we are suggesting to make a slight change in the trade-off between =
ease-of-access and data quality. For example, at IETF 98, we counted =
about twice as many unique remote attendees (based on names entered) as =
registered remote attendees.

Alissa






From nobody Thu May 18 09:15: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 F22D212AF77; Thu, 18 May 2017 09:15:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.301
X-Spam-Level: 
X-Spam-Status: No, score=0.301 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 O_KNYoNl0MAl; Thu, 18 May 2017 09:15:19 -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 4A712129AF1; Thu, 18 May 2017 09:10:03 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id b204so60209487oii.1; Thu, 18 May 2017 09:10:03 -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=xMSMYPjx9hnV07u+1cxjiqByA+D/cXAoGT3KL2CFMMg=; b=LdO5nTp/zUxAo2MVsA2uLRgV2/a6UJG/oB7sWcdOneAamKGNM96zeCWDZwMwEde9Sr 4T/TnxnhcbMYFbnoPx99TCPKgFlISfXc6C+XTU+pcb9UdgNQ6jNAT7v6Htq1NyYqGcUX BLcgx0Xh+UkIgiQ1iJgmdN/hVLYVSPa5nUIJ87Vkx08XGawE/FPduqThJadzo2Az2ONK 0iiD0KwvwdpZBs+9VTnX4bW6RmqFHTL5A6PKS7qOvqQvmTeb/YNYq9MCS88Oq4Sd2Rbp 3zSsIiBPTUiRd1b1M5RFrfRoIyhXj8q0aKWFPZsA0kUvQJYamWaHnqRaDnfKfshTPOmi 1Pfw==
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=xMSMYPjx9hnV07u+1cxjiqByA+D/cXAoGT3KL2CFMMg=; b=CvpQAdgT7tw6GeFypIc0XJ+6rmUFhWRpDwwbuIvqXpG2vz81sBenCcspEo+aOGyecT clqoab8+xpBbEkr8PzIKVp924EYWN+DhMn25JyLHIP7Gij8iWkiEjwr3CxNN9IMM6pCf EZkaOVcZs2Tr+hw0oW2iJkTmTDlAW+K7Y6pcv3xJQ8awrsLp6UIjYVJhluRgKc1nRCWk 106mvYCFLVR2QKttOopU/uEkF7pvtw0LUW0teewE8dJKZ/AidZ3rURQTCHJXb4Ed9Myi hwKVsYF5+uLNpOxhwLQWLa84KhMzaFtUITxYJFqDvy5S7mb3rfw9X+RZ7P1lnc82vpaB yfqA==
X-Gm-Message-State: AODbwcAcfGdIOysaaBt5pcUspACT6SGhP+XF7ovIYokH79Zk/BbCIKYo r479vSBS80D36JZ0g0drOUNstbFapwiA
X-Received: by 10.157.25.25 with SMTP id j25mr2908327ota.112.1495123802441; Thu, 18 May 2017 09:10:02 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.17.34 with HTTP; Thu, 18 May 2017 09:10:01 -0700 (PDT)
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 18 May 2017 12:10:01 -0400
X-Google-Sender-Auth: qyYwXBZ4yh373lKGMsoFIZLSomY
Message-ID: <CAMm+Lwh+E+BsATQmmX6ccJou-sz1XNtFHxQZikohYCeT0qkfdQ@mail.gmail.com>
Subject: SECDIR Review of draft-ietf-nfsv4-umask-03
To: "secdir@ietf.org" <secdir@ietf.org>, draft-ietf-nfsv4-umask.all@ietf.org,  IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f4030435b94823ce08054fcea385"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hzhAqzjsgICe3t_XsDgwM5a-bic>
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, 18 May 2017 16:15:22 -0000

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

Reviewer:
=E2=80=8BPhillip Hallam-Baker

Review result:
=E2=80=8BOK but...=E2=80=8B


I 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 authors, document editors, and WG chairs should
treat these comments just like any other IETF Last Call comments.

Document: Review of draft-ietf-nfsv4-umask-03
Reviewer:
=E2=80=8BPhillip Hallam-Baker



Review result:
=E2=80=8BOK but...=E2=80=8B


This particular draft looks OK to me. Aligning the semantics of NFS with
the semantics of the file system seems to me to be absolutely the way to go
forward. I am not sufficiently experienced in the semantics of NFS or Unix
as deployed to be able to offer an opinion on whether the draft achieves
that. However it appears that the author does.

=E2=80=8BWhat is problematic here is that the Security Considerations in th=
e draft
are essentially relying on those in rfc7530 which are woefully inadequate
given the critical role of NFS in Internet security. They are not so much a
security plan as a collection of random thoughts jotted down in haphazard
fashion.=E2=80=8B

There is clearly no coherent model of what NFS security should achieve,
what the threats are, what controls are deployed to control them. Also note
that the main reason this review is late is that I have been dealing with
issues arising from WannaCry which used an SMB:1 exploit. Re-reading
RFC7530 in the light of that experience gives me grave concern.

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

<div dir=3D"ltr"><span style=3D"font-size:12.8px">Reviewer:=C2=A0</span><di=
v class=3D"gmail_default" style=3D"display:inline">=E2=80=8BPhillip Hallam-=
Baker</div><br style=3D"font-size:12.8px"><span style=3D"font-size:12.8px">=
Review result:=C2=A0<div class=3D"gmail_default" style=3D"font-size:small;d=
isplay:inline">=E2=80=8BOK but...=E2=80=8B</div></span><br style=3D"font-si=
ze:12.8px"><br style=3D"font-size:12.8px"><span style=3D"font-size:12.8px">=
I reviewed this document as part of the Security Directorate&#39;s</span><b=
r style=3D"font-size:12.8px"><span style=3D"font-size:12.8px">ongoing</span=
><br style=3D"font-size:12.8px"><span style=3D"font-size:12.8px">effort to =
review all IETF documents being processed by the IESG.</span><br style=3D"f=
ont-size:12.8px"><span style=3D"font-size:12.8px">These</span><br style=3D"=
font-size:12.8px"><span style=3D"font-size:12.8px">comments were written pr=
imarily for the benefit of the Security Area</span><br style=3D"font-size:1=
2.8px"><span style=3D"font-size:12.8px">Directors.=C2=A0 Document authors, =
document editors, and WG chairs should</span><br style=3D"font-size:12.8px"=
><span style=3D"font-size:12.8px">treat these comments just like any other =
IETF Last Call comments.</span><br style=3D"font-size:12.8px"><br style=3D"=
font-size:12.8px"><span style=3D"font-size:12.8px">Document:=C2=A0Review of=
 draft-ietf-nfsv4-umask-03</span><br style=3D"font-size:12.8px"><span style=
=3D"font-size:12.8px">Reviewer: <div class=3D"gmail_default" style=3D"font-=
size:small;display:inline">=E2=80=8BPhillip Hallam-Baker</div></span><br st=
yle=3D"font-size:12.8px"><br style=3D"font-size:12.8px"><br style=3D"font-s=
ize:12.8px"><span style=3D"font-size:12.8px">Review result:=C2=A0</span><di=
v class=3D"gmail_default" style=3D"display:inline">=E2=80=8BOK but...=E2=80=
=8B</div><br><div><div class=3D"gmail_default" style=3D"display:inline"><br=
></div></div><div><div class=3D"gmail_default" style=3D"display:inline">Thi=
s particular draft looks OK to me. Aligning the semantics of NFS with the s=
emantics of the file system seems to me to be absolutely the way to go forw=
ard. I am not sufficiently experienced in the semantics of NFS or Unix as d=
eployed to be able to offer an opinion on whether the draft achieves that. =
However it appears that the author does.</div></div><div><div class=3D"gmai=
l_default" style=3D"display:inline"><br></div></div><div><div class=3D"gmai=
l_default" style=3D"font-size:small">=E2=80=8BWhat is problematic here is t=
hat the Security Considerations in the draft are essentially relying on tho=
se in rfc7530 which are woefully inadequate given the critical role of NFS =
in Internet security. They are not so much a security plan as a collection =
of random thoughts jotted down in haphazard fashion.=E2=80=8B</div><br></di=
v><div><div class=3D"gmail_default" style=3D"display:inline">There is clear=
ly no coherent model of what NFS security should achieve, what the threats =
are, what controls are deployed to control them. Also note that the main re=
ason this review is late is that I have been dealing with issues arising fr=
om WannaCry which used an SMB:1 exploit. Re-reading RFC7530 in the light of=
 that experience gives me grave concern.</div></div><div><div class=3D"gmai=
l_default" style=3D"display:inline"><br></div></div></div>

--f4030435b94823ce08054fcea385--


From nobody Thu May 18 09:31:27 2017
Return-Path: <sboutros@vmware.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 CD550126CC4; Thu, 18 May 2017 09:31:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level: 
X-Spam-Status: No, score=-1.922 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_HELO_PASS=-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=onevmw.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 af_rNrZxSs2D; Thu, 18 May 2017 09:31:04 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0057.outbound.protection.outlook.com [104.47.41.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DCD5129C3E; Thu, 18 May 2017 09:25:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=onevmw.onmicrosoft.com; s=selector1-vmware-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=3Vk34UJKaTdeo6YAvTTVnw4JJaLy2/3fm5gtZMlc4Sg=; b=h6RJdZNyQa9urgr2bZ4VStfwbXySMXOywWi31zqhIQTPnx1PrUR0a18jL6kgfFcUUABFzFyRNIIFjsfEECL28eyl30AvXhJovgySpBLaUTWMJtNAkPNp9B3KPnj2w8KGtTpjmRazfz+ib7qOm9bShayAQPf3fFpPqisai9XwR9w=
Received: from BN6PR05MB3009.namprd05.prod.outlook.com (10.173.19.15) by BN6PR05MB3010.namprd05.prod.outlook.com (10.173.19.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1101.8; Thu, 18 May 2017 16:25:46 +0000
Received: from BN6PR05MB3009.namprd05.prod.outlook.com ([10.173.19.15]) by BN6PR05MB3009.namprd05.prod.outlook.com ([10.173.19.15]) with mapi id 15.01.1101.019; Thu, 18 May 2017 16:25:46 +0000
From: Sami Boutros <sboutros@vmware.com>
To: "Patrice Brissette (pbrisset)" <pbrisset@cisco.com>, Min Ye <amy.yemin@huawei.com>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>
CC: "draft-ietf-pals-p2mp-pw.all@ietf.org" <draft-ietf-pals-p2mp-pw.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "pals@ietf.org" <pals@ietf.org>
Subject: Re: Rtgdir last call review of draft-ietf-pals-p2mp-pw-02
Thread-Topic: Rtgdir last call review of draft-ietf-pals-p2mp-pw-02
Thread-Index: AQHSyfQORpr0WT3BYUyvZqID9K0TvaH0MrUAgAFiy4CABEgMgA==
Date: Thu, 18 May 2017 16:25:46 +0000
Message-ID: <A6B8B7CD-9E63-4800-9DC0-E8DAA67C6FE0@vmware.com>
References: <149446531632.16715.2861233468294466753@ietfa.amsl.com> <89E173B8-3C03-4B4A-A405-F0442B983D7F@vmware.com> <B220B877-8FC1-4296-925A-2580DD3C796F@cisco.com>
In-Reply-To: <B220B877-8FC1-4296-925A-2580DD3C796F@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;cisco.com; dmarc=none action=none header.from=vmware.com;
x-originating-ip: [208.91.2.2]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR05MB3010; 7:p3G7c27fv2HW9VF1Nj39IH6ONgm30DrPtjoB66cjDNtvlUEE62VVhpDCrHii1uJ0e/q7yz4CM0Ep5G3IahqEEW54Kd3H3F2tjElj4RZLE1xECgcqqPuGeUoqIAze2tFGX/MKfbKbB0fUf9Z5AItuylUffMJKj5b6DLhXhb8bDzJQ98yujAvV67mSTj53/HTFYCV591k9Y/rTNa4lSJSPC7OTS+Hkb5TuIrqx9iiEbvkV/PoNvLYnriT7BGj0Pk3TucHP6Sys5uJtsK4W9isZCFp955KMyb6DRghmcw4KFsRRdmWBGF2tQ5PDL9+7Dfu5fPCdUelkTwdn5iNksRQfVA==; 20:kwuH5bDDO8OS5fBd04TeqNK3hVGVdWTM89kwkGFfBcfqiibvtIej1m74XB4DtAD6FRhgmchEWFMOTNDoI8efAQhyxiaaXXF2hOojS2q/oLSEzIMZCeFbJ/4op64PCGG4OgfpQtbYDNB4ZIOPo4kwMl+e2miAuwjLvXSsaWFG4VM=
x-ms-traffictypediagnostic: BN6PR05MB3010:
x-ms-office365-filtering-correlation-id: 1c04e125-ab0c-4dce-5752-08d49e0a89be
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081)(201702281549075); SRVR:BN6PR05MB3010; 
x-microsoft-antispam-prvs: <BN6PR05MB3010650EC3EB982FC7F0A315BEE40@BN6PR05MB3010.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700036)(100105000095)(100000701036)(100105300095)(100000702036)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(100000703036)(100105400095)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123564025)(20161123558100)(20161123555025)(20161123560025)(6072148)(100000704036)(100105200095)(100000705036)(100105500095); SRVR:BN6PR05MB3010; BCL:0; PCL:0; RULEID:(100000800036)(100110000095)(100000801036)(100110300095)(100000802036)(100110100095)(100000803036)(100110400095)(100000804036)(100110200095)(100000805036)(100110500095); SRVR:BN6PR05MB3010; 
x-forefront-prvs: 0311124FA9
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39400400002)(39850400002)(39840400002)(39860400002)(39450400003)(37854004)(230783001)(50986999)(8936002)(54356999)(76176999)(3280700002)(3660700001)(2906002)(53936002)(6512007)(38730400002)(6246003)(6436002)(54906002)(99286003)(6506006)(478600001)(4326008)(122556002)(305945005)(7736002)(66066001)(5660300001)(2501003)(189998001)(6486002)(77096006)(25786009)(2950100002)(33656002)(229853002)(8676002)(102836003)(3846002)(86362001)(36756003)(6116002)(81166006); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR05MB3010; H:BN6PR05MB3009.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <55499143E1A7AB48ADF46AEA31CB72AD@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: vmware.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 May 2017 16:25:46.2335 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: b39138ca-3cee-4b4a-a4d6-cd83d9dd62f0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR05MB3010
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DFTvBwZRrwvR7ZEs5UBj4PeMNHs>
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, 18 May 2017 16:31:07 -0000

SGkgUGF0cmljZSwNCg0KDQoNCg0KUGxlYXNlIHNlZSBjb21tZW50cyBpbmxpbmUuDQoNCj4gICAg
PiANCj4gICAgPkhlcmUgYXJlIG15IOKAnGRldGFpbGVk4oCdIGNvbW1lbnRzOg0KPiAgICA+IA0K
PiAgICA+QWJzdHJhY3Qg4oCUIFdoYXQgaXMgdGhlIHBsdXMgdmFsdWUgb24gdGhhdCBkcmFmdD8g
Tm8gY2xlYXINCj4gICAgPiANCj4gICAgPk1hbnkgTG9uZyBzZW50ZW5jZXMgaW4gdGhlIHRleHQu
IHZlcnkgaGFyZCB0byB1bmRlcnN0YW5kIGFuZCBmb2xsb3cuDQo+ICAgID5TeW50YXggdG8gYmUg
aW1wcm92ZWQuDQo+DQo+PFBhdHJpY2U+IFRoaXMgY29tbWVudCBpcyByZWdhcmRpbmcgdGhlIGRy
YWZ0IGluIGdlbmVyYWwuIEl0IGRvZXNu4oCZdCBmbG93IHdlbGwuIFlvdSBuZWVkIHRvIHJlYWQg
aXQgbW9yZSB0aGFuIG9uY2UgdG8gc2VlIHRoZSBvdmVyYWxsIHBpY3R1cmUuIEl0IG1pZ2h0IGp1
c3QgYmUgdG8gcmVzaHVmZmxlIHNvbWUgc2VjdGlvbnMuDQo+ICAgIA0KDQpTdXJlIHdpbGwgbG9v
ayBpbnRvIHRoYXQuDQoNCj4gICAgDQo+ICAgIEkgd2VudCBvdmVyIHRoZSBhYnN0cmFjdCwgSSBk
aWRu4oCZdCBzZWUgYW55IGxvbmcgc2VudGVuY2VzLiBOb3Qgc3VyZSANCj4gICAgV2hhdCB0byBp
bXByb3ZlPyBDYW4geW91IGJlIHNwZWNpZmljPw0KPiAgICANCj4gICAgDQo+ICAgID4gDQo+ICAg
ID5JbnRyb2R1Y3Rpb24NCj4gICAgPlR5cG8gOiDigJxBIHJlZmVyZW5jZSBtb2RlbCBvciBhIFAy
TVAgUFcgaXMgZGVwaWN0ZWQgaW4gRmlndXJlIDEgYmVsb3figJ0NCj4gICAgPiANCj4gICAgPuKA
nEluIHRoaXMgZG9jdW1lbnQsIHdlIHNwZWNpZnkgYSBtZXRob2Qgb2Ygc2lnbmFsaW5nIFAyTVAN
Cj4gICAgPiAgIFBXIHVzaW5nIExEUC7igJ0g4oCUPiBzdWdnZXN0IHRvIG1vdmUgaXQgZnJvbSBp
bnRybyB0byBhYnN0cmFjdA0KPiAgICANCj4gICAgTm90IHN1cmUgaWYgd2UgY2FuIHJlZmVyZW5j
ZSBhIGZpZ3VyZSBpbiB0aGUgYWJzdHJhY3QuIFRoZSBhYnN0cmFjdA0KPiAgICBBbHJlYWR5IG1l
bnRpb24gdGhhdCB0aGUgc2Vjb25kIHNlbnRlbmNlLg0KPg0KPjxQYXRyaWNlPiBUaGlzIGlzIE5P
VCBhIGZpZ3VyZSBidXQgcmF0aGVyIHRoZSBleHBsYW5hdGlvbi4gVGhhdCBsaW5lIG1ha2VzIHRo
ZSBkb2N1bWVudCB2ZXJ5IGNsZWFyLiBJdCBqdXN0IG5lZWQgdG8gYmUgc3BlbGxlZCBvdXQuIOKA
nHNwZWNpZnkgYSBtZXRob2Qgb2Ygc2lnbmFsaW5nIFAyTVAgUFcgdXNpbmcgTERQ4oCdLg0KDQpU
aGlzIGlzIGV4YWN0bHkgd2hhdCB3ZSBoYXZlIGluIHRoZSBhYnN0cmFjdCBmaXJzdCBzZW50ZW5j
ZSDigJxUaGlzIGRvY3VtZW50IHNwZWNpZmllcyBhIG1lY2hhbmlzbSB0byBzaWduYWwgUG9pbnQt
dG8tTXVsdGlwb2ludA0KICAgKFAyTVApIFBzZXVkb3dpcmVzIChQVykgdHJlZSB1c2luZyBMRFAu
4oCdDQogDQo+DQo+ICAgID4gDQo+ICAgID4gDQo+ICAgID5BbHNvLCBtYWtlIHN1cmUgdGhlIDNy
ZCBwZXJzb24gaXMgdXNlZC4gVHJ5IHRvIGEgdm9pZCDigJx3ZeKAnSB1c2FnZQ0KPiAgICANCj4g
ICAgQWdyZWVkLCBJIHdpbGwgcmVtb3ZlIGFsbCB1c2FnZSBvZiDigJx3ZeKAnSBpbiB0aGUgZG9j
dW1lbnQuDQo+ICAgIA0KPiAgICA+IA0KPiAgICA+TWF5IEkgc3VnZ2VzdCB0byBoYXZlIGEgcmVx
dWlyZW1lbnQgc2VjdGlvbi4gUmVxdWlyZW1lbnRzIGFyZSBhbGwgb3Zlcg0KPiAgICA+dGhlIGRv
Y3VtZW50Lg0KPiAgICANCj4gICAgVGhlcmUgaXMgYWxyZWFkeSBhbiBSRkMgZm9yIHRoYXQuIFtS
RkM3MzM4XSAgIEYuIEpvdW5heSwgZXQuIGFsLCANCj4gICAgIlJlcXVpcmVtZW50cyBmb3IgUG9p
bnQgdG8gTXVsdGlwb2ludCBQc2V1ZG93aXJlIiwgUkZDNzMzOCwgU2VwdGVtYmVyIDIwMTQuDQo+
ICAgIA0KPiAgICBUaGlzIHNvbHV0aW9uIGRvY3VtZW50IGFkZHJlc3NlcyB0aGUgcmVxdWlyZW1l
bnRzLg0KPg0KPjxQYXRyaWNlPiBZb3VyIGRvY3VtZW50IGVuaGFuY2VzIHRoYXQgYmFzZWQgUkZD
IGJ5IHByb3ZpZGluZyBtb3JlIOKAnE1VU1TigJ0sIOKAnFNIT1VMROKAnSwgZXRjLiANCj5UaGV5
IGFyZSBhbGwgb3ZlciB0aGUgZG9jLiBUbyBtYWtlIGl0IGNsZWFyLCBncm91cGluZyB0aGVtIGlu
IGEgc2VjdGlvbiBtYXkgaGVscC4gQW5vdGhlciBpZGVhIGlzIHRvIGhhdmUgUmVxdWlyZW1lbnQg
c3ViLXNlY3Rpb25zIHBlciB0b3BpYy4NCg0KSXQgc2VlbXMgdGhhdCB0aGlzIGlzIHRoZSBzYW1l
IGFzIHlvdXIgZG9jdW1lbnQgZmxvdyBjb21tZW50IGFib3ZlLCBJIHdpbGwgbG9vayBpbnRvIHRo
YXQuDQoNCj4NCj4gICAgDQo+ICAgID4gDQo+ICAgID7igJwgICBJbiBjYXNlIG9mIG1MRFAsIGEg
TGVhZi1QRSBjYW4gZGVjaWRlIHRvIGpvaW4gdGhlIFAyTVAgTFNQIGF0IGFueQ0KPiAgICA+ICAg
dGltZTsgd2hlcmVhcyBpbiB0aGUgY2FzZSBvZiBSU1ZQLVRFLCB0aGUgUDJNUCBMU1AgaXMgc2V0
IHVwIGJ5DQo+ICAgID50aGUNCj4gICAgPiAgIFItUEUsIGdlbmVyYWxseSBhdCB0aGUgaW5pdGlh
bCBzZXJ2aWNlIHByb3Zpc2lvbmluZyB0aW1lLiBJdA0KPiAgICA+c2hvdWxkDQo+ICAgID4gICBi
ZSBub3RlZCB0aGF0IGxvY2FsIHBvbGljeSBjYW4gb3ZlcnJpZGUgYW55IGRlY2lzaW9uIHRvIGpv
aW4sIGFkZA0KPiAgICA+b3INCj4gICAgPiAgIHBydW5lIGV4aXN0aW5nIG9yIG5ldyBMLVBFKHMp
IGZyb20gdGhlIHRyZWUuIEluIGFueSBjYXNlLCB0aGUgUFcNCj4gICAgPiAgIHNldHVwIGNhbiBp
Z25vcmUgdGhlc2UgZGlmZmVyZW5jZXMsIGFuZCBzaW1wbHkgYXNzdW1lIHRoYXQgdGhlDQo+ICAg
ID5QMk1QDQo+ICAgID4gICBQU04gTFNQIGlzIGF2YWlsYWJsZSB3aGVuIG5lZWRlZA0KPiAgICA+
4oCcDQo+ICAgID5RdWl0ZSBjb21wbGV4IHRvIGZvbGxvdy4gTWlzc2luZyB0byDigJx3aHnigJ0g
LyBleHBsYW5hdGlvbi4NCj4gICAgDQo+ICAgIFN1cmUgSSBjYW4gY2xhcmlmeSB0aGlzIGEgbGl0
dGxlIG1vcmUsIHdpbGwgcmVtb3ZlIHNvbWUgc2VudGVuY2VzIA0KPiAgICBUaGF0IG1ha2UgaXQg
Y29uZnVzaW5nLCB3ZSBhcmUgc2ltcGx5IGhlcmUgZGlmZmVyZW50aWF0aW5nIG1MRFAgTFNQIGZy
b20NCj4gICAgcDJtcCBMU1Agdy8gUlNWUC1URSBhbmQgc2F5aW5nIHRoYXQgUFcgc2V0dXAgaXMg
YWdub3N0aWMgb2YgdGhlIHRyYW5zcG9ydCANCj4gICAgcDJtcCBMU1Agc2V0dXAuDQo+ICAgIA0K
PiAgICA+IA0KPiAgICA+4oCcVGhlIExEUCBsaWJlcmFsIGxhYmVsIHJldGVudGlvbiBtb2RlIGlz
IHVzZWTigJwNCj4gICAgPkFub3RoZXIgcmVxdWlyZW1lbnTigKYgaXMgdGhhdCBhIE1BWSwgU0hP
VUxELCBNVVNUPw0KPiAgICANCj4gICAgSSB3aWxsIGNoYW5nZSBpdCB0byBhIE1VU1QuDQo+ICAg
IA0KPiAgICA+IA0KPiAgICA+4oCcSW4gdGhpcyBjYXNlLCBhIFBXIHN0YXR1cyBtZXNzYWdlIHdp
dGggc3RhdHVzDQo+ICAgID4gICBjb2RlIG9mIDB4MDAwMDAwMDggKExvY2FsIFBTTi1mYWNpbmcg
UFcgKGluZ3Jlc3MpIFJlY2VpdmUgRmF1bHQpDQo+ICAgID5NVVNUDQo+ICAgID4gICBhbHNvIGJl
IHNlbnQgdG8gdGhlIFItUEXigJwNCj4gICAgPiANCj4gICAgPkhvdz8gVGhlIEwtUEUgZmFpbHMg
dG8gam9pbiB0aGUgUDJNUCBQU04gTFNQLg0KPiAgICANCj4gICAgQ29ycmVjdCB0aGUgTC1QRSBo
YXZlIHRvIHNpZ25hbCB0aGlzIGZhaWx1cmUgdG8gdGhlIHJvb3QgUEUuDQo+DQo+PFBhdHJpY2U+
IHF1ZXN0aW9uIHJlbWFpbnMsIGhvdz8gSWYgTC1QRSBmYWlscyB0byBqb2luIHRoZSBMU1AsIFBX
IHdpbGwgYmUgZG93bi4gSG93IGNhbiBpdCBzaWduYWxzIHRoZSBmYWlsdXJlIHRvIHJvb3QgUEU/
DQo+ICAgIA0KDQpMLVBFIHdpbGwgdXNlIHRoZSBQVyBzdGF0dXMgbWVzc2FnZSwgdG8gc2lnbmFs
IHRvIHJvb3QgUEUgdGhpcyBpcyB3aGF0IHRoZSB0ZXh0IGlzIHNheWluZy4NCg0KPiAgICA+IA0K
PiAgICA+U2VjdGlvbiAyLjINCj4gICAgPuKAnCAgIE5vdGUgdGhhdCBzaW5jZSB0aGUgTERQIGxh
YmVsIG1hcHBpbmcgbWVzc2FnZSBpcyBvbmx5IHNlbnQgYnkgdGhlDQo+ICAgID5SLQ0KPiAgICA+
ICAgUEUgdG8gYWxsIHRoZSBMLVBFcywgaXQgaXMgbm90IHBvc3NpYmxlIHRvIG5lZ290aWF0ZSBh
bnkgaW50ZXJmYWNlDQo+ICAgID4gICBwYXJhbWV0ZXJzLuKAnA0KPiAgICA+V2h5IGlzIHRoYXQg
bm90ZSB0aGVyZT8gSXMgdGhhdCBhbHJlYWR5IGJlZW4gbWVudGlvbmVkIHByZXZpb3VzbHkuDQo+
ICAgIA0KPiAgICBUaGlzIGlzIHRoZSBvbmx5IHJlZmVyZW5jZSBpbiB0aGUgZG9jdW1lbnQuDQo+
DQo+PFBhdHJpY2U+IEZvcmdvdCBteSB0aG91Z2h0cyBvbiB0aGF0IG9uZS4NCj4gICAgDQo+ICAg
ID5GaWcuNCBtdXN0ICBiZSBtb3ZlZCB0byBwcm9wZXIgaW4gdGhlIHRleHQgT1IgY3JlYXRlIDIg
c3Vic2VjdGlvbiBpbg0KPiAgICA+Mi4yDQo+ICAgIA0KPiAgICBTb3JyeSBkaWRu4oCZdCBnZXQg
d2hhdCB5b3UgbWVhbiBoZXJlPyBDYW4geW91IGVsYWJvcmF0ZT8NCj4NCj48UGF0cmljZT4gU29y
cnkg4oCmTGV0IG1lIHRyeSBhZ2Fpbi4g4oCcUDJQIFBXIERvd25zdHJlYW0gRkVDIEVsZW1lbnTi
gJ0uIEkgdGhpbmsgeW91IHNob3VsZCBoYXZlIGEgc2VjdGlvbiBqdXN0IG9uIHRoYXQgdG9waWMu
IEFjdHVhbGx5LCBtYXliZSB5b3UgY2FuIGNyZWF0ZSBhIHN1YnNlY3Rpb24gZm9yIGVhY2ggZGlm
ZmVyZW50IEZFQyBleHBsYWluZWQgaW4gdGhlIGRvY3VtZW50LiANCj4gICAgDQoNCk9rLCBJIHdp
bGwgYWRkIHN1YnNlY3Rpb25zIGZvciBEb3duc3RyZWFtIGFuZCBVcHN0cmVhbS4NCg0KVGhhbmtz
LA0KDQpTYW1pDQo+ICAgID4gDQo+ICAgID7igJxBcyBzdWNoLCBQVyBzdGF0dXMgbmVnb3RpYXRp
b24gcHJvY2VkdXJlDQo+ICAgID4gICBkZXNjcmliZWQgaW4gW1JGQzQ0NDdiaXNdIGlzIG5vdCBh
cHBsaWNhYmxlIHRvIFAyTVAgUFcuIEEgbm9kZQ0KPiAgICA+TVVTVA0KPiAgICA+ICAgTk9UIGNs
YWltIHRvIGJlICBQMk1QIFBXIGNhcGFibGUgYnkgc2VuZGluZyBhIExEUCBQMk1QIFBXDQo+ICAg
ID5DYXBhYmlsaXR5DQo+ICAgID4gICBUTFYgIGlmIGl0IGlzIG5vdCBhbHNvIGNhcGFibGUgb2Yg
aGFuZGxpbmcgUFcgc3RhdHVz4oCcDQo+ICAgID4gDQo+ICAgID5TaG91bGQgYSBub2RlIHNlbmQg
TERQIFAyTVAgUFcgQ2FwYWJpbGl0eSBUTFYgb3Igbm90PyBOb3Qgd2VsbCBleHBsYWluDQo+ICAg
IA0KPiAgICBXaGF0IGlzIHNhaWQgaGVyZSwgdGhhdCB5b3UgY2Fu4oCZdCBiZSBQMk1QIFBXIGNh
cGFibGUgd2l0aG91dCBiZWluZyBQVyBzdGF0dXMgY2FwYWJsZS4NCj4gICAgTm90IHN1cmUgaG93
IHRvIG1ha2UgaXQgY2xlYXJlci4NCj4NCj48UGF0cmljZT4gcmlnaHTigKYgSSBtdXN0IGhhdmUg
YmVlbiB0aXJlZC4gVG9vIG1hbnkgTk9UIA0KPiAgICANCj4gICAgPg0KPiAgICA+IA0KPiAgICA+
VGhlcmUgaXMgc29tZSByZWZlcmVuY2UgdG8gTFNSIGluIHRoZSB0ZXh0IHdoZXJlIHRoZSBtYWpv
ciBwYXJ0IHVzZQ0KPiAgICA+dGhlIHdvcmRpbmcg4oCcbm9kZeKAnS4NCj4gICAgDQo+ICAgIEkg
d2lsbCBtYWtlIGFsbCBjb25zaXN0ZW50LCBhbmQgdXNlIExTUiBpbnN0ZWFkIG9mIG5vZGUuDQo+
ICAgIA0KPiAgICBUaGFua3MsDQo+ICAgIA0KPiAgICBTYW1pDQo+ICAgID4gDQo+ICAgID5OaXRz
OiANCj4gICAgPk4vQQ0KPiAgICA+IA0KPiAgICA+UmVnYXJkcywNCj4gICAgPlBhdHJpY2UgQnJp
c3NldHRlDQo+ICAgID4NCj4gICAgPg0KPiAgICA+DQo+ICAgID4NCj4gICAgDQo+DQo=


From nobody Thu May 18 10:50:09 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 6AA82129B53; Thu, 18 May 2017 10:50:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32qQ9BFtPnn6; Thu, 18 May 2017 10:49:59 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (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 6E2AC129C51; Thu, 18 May 2017 10:44:28 -0700 (PDT)
X-AuditID: c6180641-361ff700000037f2-91-591d971b2e2a
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usplmg21.ericsson.net (Symantec Mail Security) with SMTP id 3D.19.14322.B179D195; Thu, 18 May 2017 14:44:14 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.03.0319.002; Thu, 18 May 2017 13:44:24 -0400
From: Daniel Migault <daniel.migault@ericsson.com>
To: Dan Romascanu <dromasca@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-tls-ecdhe-psk-aead.all@ietf.org" <draft-ietf-tls-ecdhe-psk-aead.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "tls@ietf.org" <tls@ietf.org>
Subject: RE: Genart last call review of draft-ietf-tls-ecdhe-psk-aead-03
Thread-Topic: Genart last call review of draft-ietf-tls-ecdhe-psk-aead-03
Thread-Index: AQHSzWiJWERoq289gk+axe0Pcf3PPqH6RMuw
Date: Thu, 18 May 2017 17:44:24 +0000
Message-ID: <2DD56D786E600F45AC6BDE7DA4E8A8C118BDB690@eusaamb107.ericsson.se>
References: <149484519593.2843.448630358757818654@ietfa.amsl.com>
In-Reply-To: <149484519593.2843.448630358757818654@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.10]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDLMWRmVeSWpSXmKPExsUyuXRPiK7cdNlIgyu3rSzeLNvEZNH4WMvi 6qvPLBbPNs5nsfh0vovRgdVj56y77B5LlvxkCmCK4rJJSc3JLEst0rdL4Mq4cPwKW8EC5YqP 18+wNzCuUepi5OCQEDCRePXSsYuRi0NI4CijxOk9HawQznJGiZ7jD9i6GDk52ASMJNoO9bOD 2CICvhLXT09iByliFljIKNG+aAIzSEJYwENi9/M2qCJPiVMtx5ggbCOJR2+/gtksAqoSK/7/ YgSxeYEGLbu/GiwuJOAoce3MMlYQm1PASWLb/NdgixkFxCS+n1oDVsMsIC5x68l8MFtCQEBi yZ7zzBC2qMTLx/9YIWwliUlLz7GCfMYsoCmxfpc+RKuixJTuh+wQawUlTs58wjKBUXQWkqmz EDpmIemYhaRjASPLKkaO0uKCnNx0I8NNjMA4OSbB5riDcW+v5yFGAQ5GJR7e7i7ZSCHWxLLi ytxDjBIczEoivF/OAYV4UxIrq1KL8uOLSnNSiw8xSnOwKInzviu/ECEkkJ5YkpqdmlqQWgST ZeLglGpglGQpfavM+f9vZGwto0Rz0dTKAtkZFnOnLej061senP3GzIJ3o5POw2VzNm5hTZu2 XmTFhBdqG9fmbn99padTsjD2w5SVd846buI+zMO1NK0sci6zQZMEy9MC21Ua5zWXH+rPZOfg PKd2Nzte3Omf2k7V6aznfyhleR7telc2ie03R8Shf/P3K7EUZyQaajEXFScCAAaWn0GPAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VNF65i_bPX3KdtWrxcBO18Shlho>
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, 18 May 2017 17:50:01 -0000

SGkgRGFuLCANCg0KVGhhbmsgeW91IGZvciB5b3VyIHJldmlld3MgYW5kIGNvbW1lbnRzLiBJIGJl
bGlldmUgdGhlIGZvbGxvd2luZyB0ZXh0IHByb3ZpZGVzIG1vcmUgZXhwbGFuYXRpb24gb24gaG93
IHRoZSBwcm92aWRlZCBjaXBoZXIgc3VpdGVzIGFyZSBuZWdvdGlhdGVkIGJ5IFRMUzEuMyBhcyB3
ZWxsIGFzIHdoeSBwb2ludCBjb2RlcyBkZWZpbmVkIGluIHRoZSBkb2N1bWVudCBkb2VzIG5vdCBh
cHBseSB0byBUTFMxLjMuIEZlZWwgZnJlZSB0byBsZXQgbWUga25vdyBpZiB0aGF0IGFkZHJlc3Mg
eW91ciBjb25jZXJuIGFuZCBJIGNhbiBwdWJsaXNoIHZlcnNpb24gMDQgd2l0aCB0aGUgdGV4dCBi
ZWxvdy4NCg0KVW5saWtlIFRMUzEuMiwgVExTMS4zIHNlcGFyYXRlcyBhdXRoZW50aWNhdGlvbiBh
bmQgY2lwaGVyIHN1aXRlIG5lZ290aWF0aW9uIDx4cmVmIHRhcmdldD0iSS1ELmlldGYtdGxzLXRs
czEzIi8+IFNlY3Rpb24gMS4yLiBUTFMxLjMgc3VwcG9ydHMgUFNLIHdpdGggRUNESEUga2V5IGV4
Y2hhbmdlIGFuZCB0aGUgY2lwaGVyIHN1aXRlcyBUTFNfQUVTXzEyOF9HQ01fU0hBMjU2LCBUTFNf
QUVTXzI1Nl9HQ01fU0hBMzg0LCBUTFNfQUVTXzEyOF9DQ01fOF9TSEEyNTYgYW5kICBUTFNfQUVT
XzEyOF9DQ01fU0hBMjU2IGFyZSBwYXJ0IG9mIHRoZSBzcGVjaWZpY2F0aW9uLiBBcyBhIHJlc3Vs
dCwgVExTIDEuMyBhbmQgaGlnaGVyIHZlcnNpb25zLCBuZWdvdGlhdGUgYW5kIHN1cHBvcnQgdGhl
c2UgY2lwaGVyIHN1aXRlcyBpbiBhIGRpZmZlcmVudCB3YXkuDQoNCkkgYW0gbm90IHN1cmUgd2Ug
IGhhdmUgdG8gd2FpdCBmb3IgdGhlIHB1YmxpY2F0aW9uIG9mIFRMUzEuMyBhcyBjaGFuZ2VzIG9u
IFRMUzEuMyBhcmUgdW5saWtlbHkgdG8gaW1wYWN0IHRoZSBjb2RlIHBvaW50IGFzc2lnbmVkLiBI
b3dldmVyLCB3ZSBjdXJyZW50bHkgaGF2ZSBUTFMxLjMgYXMgYSBub3JtYXRpdmUgcmVmZXJlbmNl
LiANCg0KWW91cnMsIA0KRGFuaWVsDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTog
RGFuIFJvbWFzY2FudSBbbWFpbHRvOmRyb21hc2NhQGdtYWlsLmNvbV0gDQpTZW50OiBNb25kYXks
IE1heSAxNSwgMjAxNyA2OjQ3IEFNDQpUbzogZ2VuLWFydEBpZXRmLm9yZw0KQ2M6IGRyYWZ0LWll
dGYtdGxzLWVjZGhlLXBzay1hZWFkLmFsbEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzsgdGxzQGll
dGYub3JnOyBkcm9tYXNjYUBnbWFpbC5jb20NClN1YmplY3Q6IEdlbmFydCBsYXN0IGNhbGwgcmV2
aWV3IG9mIGRyYWZ0LWlldGYtdGxzLWVjZGhlLXBzay1hZWFkLTAzDQoNClJldmlld2VyOiBEYW4g
Um9tYXNjYW51DQpSZXZpZXcgcmVzdWx0OiBSZWFkeSB3aXRoIElzc3Vlcw0KDQpJIGFtIHRoZSBh
c3NpZ25lZCBHZW4tQVJUIHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBUaGUgR2VuZXJhbCBBcmVh
IFJldmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBw
cm9jZXNzZWQgYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLiAgUGxlYXNlIHRyZWF0IHRo
ZXNlIGNvbW1lbnRzIGp1c3QgbGlrZSBhbnkgb3RoZXIgbGFzdCBjYWxsIGNvbW1lbnRzLg0KDQpG
b3IgbW9yZSBpbmZvcm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0DQoNCjxodHRwczovL3Ry
YWMuaWV0Zi5vcmcvdHJhYy9nZW4vd2lraS9HZW5BcnRmYXE+Lg0KDQpEb2N1bWVudDogZHJhZnQt
aWV0Zi10bHMtZWNkaGUtcHNrLWFlYWQtPz8NClJldmlld2VyOiBEYW4gUm9tYXNjYW51DQpSZXZp
ZXcgRGF0ZTogMjAxNy0wNS0xNQ0KSUVURiBMQyBFbmQgRGF0ZTogMjAxNy0wNS0xOA0KSUVTRyBU
ZWxlY2hhdCBkYXRlOiAyMDE3LTA1LTI1DQoNClN1bW1hcnk6DQoNClRoaXMgaXMgYSBzdHJhaWdo
dC1mb3J3YXJkIGFuZCBjbGVhciBkb2N1bWVudCB0aGF0IGRlZmluZXMgc2V2ZXJhbCBuZXcgY2lw
aGVyIHN1aXRlcyBmb3IgdGhlIFRyYW5zcG9ydCBMYXllciBTZWN1cml0eSAoVExTKSBwcm90b2Nv
bCB2ZXJzaW9uDQoxLjIgYW5kIGhpZ2hlciwgYmFzZWQgb24gdGhlIEVwaGVtZXJhbCBFbGxpcHRp
YyBDdXJ2ZSBEaWZmaWUtSGVsbG1hbiB3aXRoIFByZS1TaGFyZWQgS2V5IChFQ0RIRV9QU0spIGtl
eSBleGNoYW5nZSB0b2dldGhlciB3aXRoIHRoZSBBdXRoZW50aWNhdGVkIEVuY3J5cHRpb24gd2l0
aCBBc3NvY2lhdGVkIERhdGEgKEFFQUQpIGFsZ29yaXRobXMgQUVTLUdDTSBhbmQgQUVTLUNDTS4g
VGhlIGRvY3VtZW50IGlzIHdlbGwgd3JpdHRlbiBhbmQgSSBhcHByZWNpYXRlIHRoZSBlZmZvcnQg
dG8gY2xhcmlmeSBpbiB0aGUgSW50cm9kdWN0aW9uIHRoZSBjb250ZXh0LCB3aGF0IHdhcyBtaXNz
aW5nLCBhbmQgd2h5IHRoZSBkb2N1bWVudCBpcyBuZWNlc3NhcnkuIFRoZSBkb2N1bWVudCBpcyBS
ZWFkeSwgdGhlcmUgaXMgb25lIGlzc3VlIGFib3V0IHN1cHBvcnQgZm9yIFRMUyB2ZXJzaW9uIDEu
MyBhbmQgaGlnaGVyIHRoYXQgbWF5IG5lZWQgc29tZSB0ZXh0IGNsYXJpZmljYXRpb24uIA0KDQpN
YWpvciBpc3N1ZXM6DQoNCk1pbm9yIGlzc3VlczoNCg0KU2VjdGlvbiA0ICgnQXBwbGljYWJsZSBU
TFMgVmVyc2lvbnMnKSBkZXNjcmliZXMgaW4gZGV0YWlscyBob3cgdGhlIGNpcGhlciBzdWl0ZXMg
ZGVmaW5lZCBpbiB0aGUgZG9jdW1lbnQgbWFrZSB1c2Ugb2YgdGhlIGF1dGhlbnRpY2F0ZWQgZW5j
cnlwdGlvbiB3aXRoIGFkZGl0aW9uYWwgZGF0YSAoQUVBRCkgZGVmaW5lZCBpbiBUTFMgMS4yIFtS
RkM1MjQ2XSBhbmQgRFRMUyAxLjIgW1JGQzYzNDddLiBBYm91dCBUTFMgMS4zIGl0IGp1c3Qgc2F5
czogDQoNCicgVExTIDEuMyBhbmQgYWJvdmUgdmVyc2lvbiwgbmVnb3RpYXRlIGFuZCBzdXBwb3J0
IHRoZXNlIGNpcGhlciBzdWl0ZXMgaW4gYSBkaWZmZXJlbnQgd2F5LicNCg0KVGhpcyBtYXkgcmFp
c2Ugc29tZSBjb25jZXJucyBhcyAnaW4gYSBkaWZmZXJlbnQgd2F5JyBpcyBhbWJpZ3VvdXMsIGVz
cGVjaWFsbHkgY29tcGFyZWQgdG8gdGhlIGRldGFpbHMgaW5jbHVkZWQgZm9yIFRMUyAxLjIuIE1v
cmVvdmVyLCBUTFMNCjEuMyBpcyBzdGlsbCB3b3JrLWluLXByb2dyZXNzLCBhbmQgSSBiZWxpZXZl
IHRoYXQgdGhpcyBkb2N1bWVudCB3aGVuIGFwcHJvdmVkIG5lZWRzIHRvIHdhaXQgZm9yIFRMUyAx
LjMgdG8gYmUgYXBwcm92ZWQgZm9yIHB1YmxpY2F0aW9uLg0KV2lsbCBhbnl0aGluZyBjaGFuZ2Us
IG9yIG5lZWQgdG8gYmUgYWRkZWQ/IFNvbWUgYmV0dGVyIGNsYXJpZmljYXRpb24gdGV4dCB3b3Vs
ZCBoZWxwIElNTy4gDQoNCk5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOiANCg0KDQo=


From nobody Thu May 18 10:51:57 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 7737F12EBD1; Thu, 18 May 2017 10:51:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Juj8Cf_H5uGh; Thu, 18 May 2017 10:51:46 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (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 7189F1292F4; Thu, 18 May 2017 10:45:42 -0700 (PDT)
X-AuditID: c6180641-379ff700000037f2-c5-591d976674fc
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usplmg21.ericsson.net (Symantec Mail Security) with SMTP id A8.29.14322.6679D195; Thu, 18 May 2017 14:45:28 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0339.000; Thu, 18 May 2017 13:45:38 -0400
From: Daniel Migault <daniel.migault@ericsson.com>
To: Simon Friedberger <simon.tls@a-oben.org>, "ietf@ietf.org" <ietf@ietf.org>
CC: "tls@ietf.org" <tls@ietf.org>
Subject: RE: [TLS] Last Call: <draft-ietf-tls-ecdhe-psk-aead-03.txt> (ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transport Layer Security (TLS)) to Proposed Standard
Thread-Topic: [TLS] Last Call: <draft-ietf-tls-ecdhe-psk-aead-03.txt> (ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transport Layer Security (TLS)) to Proposed Standard
Thread-Index: AQHSxPVA+HUpnSSi3UucXiEEFjZ+saHk/FmAgBVW5mA=
Date: Thu, 18 May 2017 17:45:38 +0000
Message-ID: <2DD56D786E600F45AC6BDE7DA4E8A8C118BDB69D@eusaamb107.ericsson.se>
References: <149391606578.6842.3727373203321848879.idtracker@ietfa.amsl.com> <4373f972-bf9b-4dbe-1b59-7f51846831f3@a-oben.org>
In-Reply-To: <4373f972-bf9b-4dbe-1b59-7f51846831f3@a-oben.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrGLMWRmVeSWpSXmKPExsUyuXRPgm7GdNlIg6f/VC2ebZzPYnFt8nIW i0/nuxgdmD2mrZvL6LFkyU+mAKYoLpuU1JzMstQifbsEroxTG/tYCk6KVpz9foq9gfGsYBcj B4eEgInErkaHLkYuDiGBo4wS35tmsUA4yxklZv/5zNbFyMnBJmAk0Xaonx3EFhHwlTj6dj2Y zSygKPH+0jywBmGBzYwSL5/dZwRxRAS2MEocOnKPEaLDSuLsuodgHSwCqhKXb3ezgti8QJNW NExmhljXwCjRNfMVO8hNnAJ2Es0HA0FqGAXEJL6fWsMEsU1c4taT+WC2hICAxJI955khbFGJ l4//sULYShKTlp5jhajXkViw+xMbhK0tsWzha2aIvYISJ2c+YZnAKDoLydhZSFpmIWmZhaRl ASPLKkaO0uKCnNx0I8NNjMDYOCbB5riDcW+v5yFGAQ5GJR7e7i7ZSCHWxLLiytxDjBIczEoi vF/OAYV4UxIrq1KL8uOLSnNSiw8xSnOwKInzviu/ECEkkJ5YkpqdmlqQWgSTZeLglGpgnCHf sHirhd3OfXzLin7YrG8Kttv96/a+2pDntQ0h3EebphYbT01i3vSu8UH1bbFnBzRUq9J2Jgj5 FzFuPtKYP7llrfMXl9Bu7Y7S7gP8156GMh81v7/30iS1I4G1KWeXXdl12Gj/ndSyw94nVgd9 Wb5+zc+ioq9bJyX85mKZ5nil0fZxzbpSFyWW4oxEQy3mouJEAJvw01mJAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BL5dMEHdnQYUieqCtVEDKkvurBs>
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, 18 May 2017 17:51:49 -0000

Hi Simon,=20

Thank you for the review. I believe we have addressed your comments in our =
version 04. Please see my comments inline.=20

Yours,=20
Daniel

-----Original Message-----
From: TLS [mailto:tls-bounces@ietf.org] On Behalf Of Simon Friedberger
Sent: Thursday, May 04, 2017 5:59 PM
To: ietf@ietf.org
Cc: tls@ietf.org
Subject: Re: [TLS] Last Call: <draft-ietf-tls-ecdhe-psk-aead-03.txt> (ECDHE=
_PSK with AES-GCM and AES-CCM Cipher Suites for Transport Layer Security (T=
LS)) to Proposed Standard

Nits:

	RFC 4279 reference is missing.
MGLT: It seems the reference is mentioned in the current version in the Nor=
mative reference as well  as in the introduction at line 127,  in section 3=
 line 143. In case you meant another reference, please let us know.=20



	"TLS 1.3 and above version, " should probably be "TLS 1.3 and above" or "T=
LS 1.3 and higher versions"
MGLT: Changed to "TLS 1.3 and higher versions"

On 04/05/17 18:41, The IESG wrote:
> The IESG has received a request from the Transport Layer Security WG
> (tls) to consider the following document:
> - 'ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transport Layer
>    Security (TLS)'
>   <draft-ietf-tls-ecdhe-psk-aead-03.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits=20
> final comments on this action. Please send substantive comments to the=20
> ietf@ietf.org mailing lists by 2017-05-18. Exceptionally, comments may=20
> be sent to iesg@ietf.org instead. In either case, please retain the=20
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    This document defines several new cipher suites for the Transport
>    Layer Security (TLS) protocol.  The cipher suites are all based on
>    the Ephemeral Elliptic Curve Diffie-Hellman with Pre-Shared Key
>    (ECDHE_PSK) key exchange together with the Authenticated Encryption
>    with Associated Data (AEAD) algorithms AES-GCM and AES-CCM.  PSK
>    provides light and efficient authentication, ECDHE provides perfect
>    forward secrecy, and AES-GCM and AES-CCM provides encryption and
>    integrity protection.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-tls-ecdhe-psk-aead/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-tls-ecdhe-psk-aead/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls

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


From nobody Thu May 18 12:50:31 2017
Return-Path: <pbrisset@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 1003E128C83; Thu, 18 May 2017 12:50:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 4-GjIC5AG_R2; Thu, 18 May 2017 12:50:17 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9F3412AF77; Thu, 18 May 2017 12:44:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8950; q=dns/txt; s=iport; t=1495136684; x=1496346284; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=eIjz4mhvCv6EoZ80P0EWfsl6NRUGCjH8TuUhFYx8zNI=; b=EicyQeXCYMLvUappcK3juUPhMOIPGJg2mPFSromGJP2Wo3cwfENluR3y MYBjDnGT0n8dhfvgQwRL/ypfZjX4ETMlrarlE+jmeUh4teLd/OE+ZAHus TKOrrwKc7xYDYgOY/8SdUyJ3j6MGRElSTeRGxH/dDxVRiGX5EcGHHye/z c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DWAABY+R1Z/49dJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1WBbgeDZooYkW6VdoIPhiQCGoVWPxgBAgEBAQEBAQFrKIUZAQQ?= =?us-ascii?q?BIxETMhACAQYCDgwCJgICAjAVEAIEAQ0FG4oACJFKnWCCJoM/h1oBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEdgQuFVIFdASuCcIRjBxAjglgvgjEBBJZ0hx8BkxqCBIU?= =?us-ascii?q?8g2eGR5RFAR84gQpwFVgBhGQcgWN2hyWBDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.38,359,1491264000"; d="scan'208";a="428314725"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 May 2017 19:44:23 +0000
Received: from XCH-RTP-008.cisco.com (xch-rtp-008.cisco.com [64.101.220.148]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v4IJiNf2006966 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 18 May 2017 19:44:23 GMT
Received: from xch-rtp-009.cisco.com (64.101.220.149) by XCH-RTP-008.cisco.com (64.101.220.148) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 18 May 2017 15:44:22 -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.1210.000; Thu, 18 May 2017 15:44:22 -0400
From: "Patrice Brissette (pbrisset)" <pbrisset@cisco.com>
To: Sami Boutros <sboutros@vmware.com>, Min Ye <amy.yemin@huawei.com>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>
CC: "draft-ietf-pals-p2mp-pw.all@ietf.org" <draft-ietf-pals-p2mp-pw.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "pals@ietf.org" <pals@ietf.org>
Subject: Re: Rtgdir last call review of draft-ietf-pals-p2mp-pw-02
Thread-Topic: Rtgdir last call review of draft-ietf-pals-p2mp-pw-02
Thread-Index: AQHSzZS0GfuQJeqMNUWBoX3pZMCpIw==
Date: Thu, 18 May 2017 19:44:22 +0000
Message-ID: <7BB57E2E-ED82-46A1-887B-91B088799FBD@cisco.com>
References: <149446531632.16715.2861233468294466753@ietfa.amsl.com> <89E173B8-3C03-4B4A-A405-F0442B983D7F@vmware.com> <B220B877-8FC1-4296-925A-2580DD3C796F@cisco.com> <A6B8B7CD-9E63-4800-9DC0-E8DAA67C6FE0@vmware.com>
In-Reply-To: <A6B8B7CD-9E63-4800-9DC0-E8DAA67C6FE0@vmware.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.21.0.170409
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.215.212]
Content-Type: text/plain; charset="utf-8"
Content-ID: <8AFB87E434798C4DB6376C37FEE4C646@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6EwrbNHC8DGxE0VXgeFLlR7TeAc>
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, 18 May 2017 19:50:21 -0000

VGhhbmsgU2FtaQ0KDQpSZWdhcmRzLA0KUGF0cmljZSBCcmlzc2V0dGUNCg0KT24gMjAxNy0wNS0x
OCwgMTI6MjUgUE0sICJTYW1pIEJvdXRyb3MiIDxzYm91dHJvc0B2bXdhcmUuY29tPiB3cm90ZToN
Cg0KICAgIEhpIFBhdHJpY2UsDQogICAgDQogICAgDQogICAgDQogICAgDQogICAgUGxlYXNlIHNl
ZSBjb21tZW50cyBpbmxpbmUuDQogICAgDQogICAgPiAgICA+IA0KICAgID4gICAgPkhlcmUgYXJl
IG15IOKAnGRldGFpbGVk4oCdIGNvbW1lbnRzOg0KICAgID4gICAgPiANCiAgICA+ICAgID5BYnN0
cmFjdCDigJQgV2hhdCBpcyB0aGUgcGx1cyB2YWx1ZSBvbiB0aGF0IGRyYWZ0PyBObyBjbGVhcg0K
ICAgID4gICAgPiANCiAgICA+ICAgID5NYW55IExvbmcgc2VudGVuY2VzIGluIHRoZSB0ZXh0LiB2
ZXJ5IGhhcmQgdG8gdW5kZXJzdGFuZCBhbmQgZm9sbG93Lg0KICAgID4gICAgPlN5bnRheCB0byBi
ZSBpbXByb3ZlZC4NCiAgICA+DQogICAgPjxQYXRyaWNlPiBUaGlzIGNvbW1lbnQgaXMgcmVnYXJk
aW5nIHRoZSBkcmFmdCBpbiBnZW5lcmFsLiBJdCBkb2VzbuKAmXQgZmxvdyB3ZWxsLiBZb3UgbmVl
ZCB0byByZWFkIGl0IG1vcmUgdGhhbiBvbmNlIHRvIHNlZSB0aGUgb3ZlcmFsbCBwaWN0dXJlLiBJ
dCBtaWdodCBqdXN0IGJlIHRvIHJlc2h1ZmZsZSBzb21lIHNlY3Rpb25zLg0KICAgID4gICAgDQog
ICAgDQogICAgU3VyZSB3aWxsIGxvb2sgaW50byB0aGF0Lg0KICAgIA0KICAgID4gICAgDQogICAg
PiAgICBJIHdlbnQgb3ZlciB0aGUgYWJzdHJhY3QsIEkgZGlkbuKAmXQgc2VlIGFueSBsb25nIHNl
bnRlbmNlcy4gTm90IHN1cmUgDQogICAgPiAgICBXaGF0IHRvIGltcHJvdmU/IENhbiB5b3UgYmUg
c3BlY2lmaWM/DQogICAgPiAgICANCiAgICA+ICAgIA0KICAgID4gICAgPiANCiAgICA+ICAgID5J
bnRyb2R1Y3Rpb24NCiAgICA+ICAgID5UeXBvIDog4oCcQSByZWZlcmVuY2UgbW9kZWwgb3IgYSBQ
Mk1QIFBXIGlzIGRlcGljdGVkIGluIEZpZ3VyZSAxIGJlbG934oCdDQogICAgPiAgICA+IA0KICAg
ID4gICAgPuKAnEluIHRoaXMgZG9jdW1lbnQsIHdlIHNwZWNpZnkgYSBtZXRob2Qgb2Ygc2lnbmFs
aW5nIFAyTVANCiAgICA+ICAgID4gICBQVyB1c2luZyBMRFAu4oCdIOKAlD4gc3VnZ2VzdCB0byBt
b3ZlIGl0IGZyb20gaW50cm8gdG8gYWJzdHJhY3QNCiAgICA+ICAgIA0KICAgID4gICAgTm90IHN1
cmUgaWYgd2UgY2FuIHJlZmVyZW5jZSBhIGZpZ3VyZSBpbiB0aGUgYWJzdHJhY3QuIFRoZSBhYnN0
cmFjdA0KICAgID4gICAgQWxyZWFkeSBtZW50aW9uIHRoYXQgdGhlIHNlY29uZCBzZW50ZW5jZS4N
CiAgICA+DQogICAgPjxQYXRyaWNlPiBUaGlzIGlzIE5PVCBhIGZpZ3VyZSBidXQgcmF0aGVyIHRo
ZSBleHBsYW5hdGlvbi4gVGhhdCBsaW5lIG1ha2VzIHRoZSBkb2N1bWVudCB2ZXJ5IGNsZWFyLiBJ
dCBqdXN0IG5lZWQgdG8gYmUgc3BlbGxlZCBvdXQuIOKAnHNwZWNpZnkgYSBtZXRob2Qgb2Ygc2ln
bmFsaW5nIFAyTVAgUFcgdXNpbmcgTERQ4oCdLg0KICAgIA0KICAgIFRoaXMgaXMgZXhhY3RseSB3
aGF0IHdlIGhhdmUgaW4gdGhlIGFic3RyYWN0IGZpcnN0IHNlbnRlbmNlIOKAnFRoaXMgZG9jdW1l
bnQgc3BlY2lmaWVzIGEgbWVjaGFuaXNtIHRvIHNpZ25hbCBQb2ludC10by1NdWx0aXBvaW50DQog
ICAgICAgKFAyTVApIFBzZXVkb3dpcmVzIChQVykgdHJlZSB1c2luZyBMRFAu4oCdDQogICAgIA0K
ICAgID4NCiAgICA+ICAgID4gDQogICAgPiAgICA+IA0KICAgID4gICAgPkFsc28sIG1ha2Ugc3Vy
ZSB0aGUgM3JkIHBlcnNvbiBpcyB1c2VkLiBUcnkgdG8gYSB2b2lkIOKAnHdl4oCdIHVzYWdlDQog
ICAgPiAgICANCiAgICA+ICAgIEFncmVlZCwgSSB3aWxsIHJlbW92ZSBhbGwgdXNhZ2Ugb2Yg4oCc
d2XigJ0gaW4gdGhlIGRvY3VtZW50Lg0KICAgID4gICAgDQogICAgPiAgICA+IA0KICAgID4gICAg
Pk1heSBJIHN1Z2dlc3QgdG8gaGF2ZSBhIHJlcXVpcmVtZW50IHNlY3Rpb24uIFJlcXVpcmVtZW50
cyBhcmUgYWxsIG92ZXINCiAgICA+ICAgID50aGUgZG9jdW1lbnQuDQogICAgPiAgICANCiAgICA+
ICAgIFRoZXJlIGlzIGFscmVhZHkgYW4gUkZDIGZvciB0aGF0LiBbUkZDNzMzOF0gICBGLiBKb3Vu
YXksIGV0LiBhbCwgDQogICAgPiAgICAiUmVxdWlyZW1lbnRzIGZvciBQb2ludCB0byBNdWx0aXBv
aW50IFBzZXVkb3dpcmUiLCBSRkM3MzM4LCBTZXB0ZW1iZXIgMjAxNC4NCiAgICA+ICAgIA0KICAg
ID4gICAgVGhpcyBzb2x1dGlvbiBkb2N1bWVudCBhZGRyZXNzZXMgdGhlIHJlcXVpcmVtZW50cy4N
CiAgICA+DQogICAgPjxQYXRyaWNlPiBZb3VyIGRvY3VtZW50IGVuaGFuY2VzIHRoYXQgYmFzZWQg
UkZDIGJ5IHByb3ZpZGluZyBtb3JlIOKAnE1VU1TigJ0sIOKAnFNIT1VMROKAnSwgZXRjLiANCiAg
ICA+VGhleSBhcmUgYWxsIG92ZXIgdGhlIGRvYy4gVG8gbWFrZSBpdCBjbGVhciwgZ3JvdXBpbmcg
dGhlbSBpbiBhIHNlY3Rpb24gbWF5IGhlbHAuIEFub3RoZXIgaWRlYSBpcyB0byBoYXZlIFJlcXVp
cmVtZW50IHN1Yi1zZWN0aW9ucyBwZXIgdG9waWMuDQogICAgDQogICAgSXQgc2VlbXMgdGhhdCB0
aGlzIGlzIHRoZSBzYW1lIGFzIHlvdXIgZG9jdW1lbnQgZmxvdyBjb21tZW50IGFib3ZlLCBJIHdp
bGwgbG9vayBpbnRvIHRoYXQuDQogICAgDQogICAgPg0KICAgID4gICAgDQogICAgPiAgICA+IA0K
ICAgID4gICAgPuKAnCAgIEluIGNhc2Ugb2YgbUxEUCwgYSBMZWFmLVBFIGNhbiBkZWNpZGUgdG8g
am9pbiB0aGUgUDJNUCBMU1AgYXQgYW55DQogICAgPiAgICA+ICAgdGltZTsgd2hlcmVhcyBpbiB0
aGUgY2FzZSBvZiBSU1ZQLVRFLCB0aGUgUDJNUCBMU1AgaXMgc2V0IHVwIGJ5DQogICAgPiAgICA+
dGhlDQogICAgPiAgICA+ICAgUi1QRSwgZ2VuZXJhbGx5IGF0IHRoZSBpbml0aWFsIHNlcnZpY2Ug
cHJvdmlzaW9uaW5nIHRpbWUuIEl0DQogICAgPiAgICA+c2hvdWxkDQogICAgPiAgICA+ICAgYmUg
bm90ZWQgdGhhdCBsb2NhbCBwb2xpY3kgY2FuIG92ZXJyaWRlIGFueSBkZWNpc2lvbiB0byBqb2lu
LCBhZGQNCiAgICA+ICAgID5vcg0KICAgID4gICAgPiAgIHBydW5lIGV4aXN0aW5nIG9yIG5ldyBM
LVBFKHMpIGZyb20gdGhlIHRyZWUuIEluIGFueSBjYXNlLCB0aGUgUFcNCiAgICA+ICAgID4gICBz
ZXR1cCBjYW4gaWdub3JlIHRoZXNlIGRpZmZlcmVuY2VzLCBhbmQgc2ltcGx5IGFzc3VtZSB0aGF0
IHRoZQ0KICAgID4gICAgPlAyTVANCiAgICA+ICAgID4gICBQU04gTFNQIGlzIGF2YWlsYWJsZSB3
aGVuIG5lZWRlZA0KICAgID4gICAgPuKAnA0KICAgID4gICAgPlF1aXRlIGNvbXBsZXggdG8gZm9s
bG93LiBNaXNzaW5nIHRvIOKAnHdoeeKAnSAvIGV4cGxhbmF0aW9uLg0KICAgID4gICAgDQogICAg
PiAgICBTdXJlIEkgY2FuIGNsYXJpZnkgdGhpcyBhIGxpdHRsZSBtb3JlLCB3aWxsIHJlbW92ZSBz
b21lIHNlbnRlbmNlcyANCiAgICA+ICAgIFRoYXQgbWFrZSBpdCBjb25mdXNpbmcsIHdlIGFyZSBz
aW1wbHkgaGVyZSBkaWZmZXJlbnRpYXRpbmcgbUxEUCBMU1AgZnJvbQ0KICAgID4gICAgcDJtcCBM
U1Agdy8gUlNWUC1URSBhbmQgc2F5aW5nIHRoYXQgUFcgc2V0dXAgaXMgYWdub3N0aWMgb2YgdGhl
IHRyYW5zcG9ydCANCiAgICA+ICAgIHAybXAgTFNQIHNldHVwLg0KICAgID4gICAgDQogICAgPiAg
ICA+IA0KICAgID4gICAgPuKAnFRoZSBMRFAgbGliZXJhbCBsYWJlbCByZXRlbnRpb24gbW9kZSBp
cyB1c2Vk4oCcDQogICAgPiAgICA+QW5vdGhlciByZXF1aXJlbWVudOKApiBpcyB0aGF0IGEgTUFZ
LCBTSE9VTEQsIE1VU1Q/DQogICAgPiAgICANCiAgICA+ICAgIEkgd2lsbCBjaGFuZ2UgaXQgdG8g
YSBNVVNULg0KICAgID4gICAgDQogICAgPiAgICA+IA0KICAgID4gICAgPuKAnEluIHRoaXMgY2Fz
ZSwgYSBQVyBzdGF0dXMgbWVzc2FnZSB3aXRoIHN0YXR1cw0KICAgID4gICAgPiAgIGNvZGUgb2Yg
MHgwMDAwMDAwOCAoTG9jYWwgUFNOLWZhY2luZyBQVyAoaW5ncmVzcykgUmVjZWl2ZSBGYXVsdCkN
CiAgICA+ICAgID5NVVNUDQogICAgPiAgICA+ICAgYWxzbyBiZSBzZW50IHRvIHRoZSBSLVBF4oCc
DQogICAgPiAgICA+IA0KICAgID4gICAgPkhvdz8gVGhlIEwtUEUgZmFpbHMgdG8gam9pbiB0aGUg
UDJNUCBQU04gTFNQLg0KICAgID4gICAgDQogICAgPiAgICBDb3JyZWN0IHRoZSBMLVBFIGhhdmUg
dG8gc2lnbmFsIHRoaXMgZmFpbHVyZSB0byB0aGUgcm9vdCBQRS4NCiAgICA+DQogICAgPjxQYXRy
aWNlPiBxdWVzdGlvbiByZW1haW5zLCBob3c/IElmIEwtUEUgZmFpbHMgdG8gam9pbiB0aGUgTFNQ
LCBQVyB3aWxsIGJlIGRvd24uIEhvdyBjYW4gaXQgc2lnbmFscyB0aGUgZmFpbHVyZSB0byByb290
IFBFPw0KICAgID4gICAgDQogICAgDQogICAgTC1QRSB3aWxsIHVzZSB0aGUgUFcgc3RhdHVzIG1l
c3NhZ2UsIHRvIHNpZ25hbCB0byByb290IFBFIHRoaXMgaXMgd2hhdCB0aGUgdGV4dCBpcyBzYXlp
bmcuDQogICAgDQogICAgPiAgICA+IA0KICAgID4gICAgPlNlY3Rpb24gMi4yDQogICAgPiAgICA+
4oCcICAgTm90ZSB0aGF0IHNpbmNlIHRoZSBMRFAgbGFiZWwgbWFwcGluZyBtZXNzYWdlIGlzIG9u
bHkgc2VudCBieSB0aGUNCiAgICA+ICAgID5SLQ0KICAgID4gICAgPiAgIFBFIHRvIGFsbCB0aGUg
TC1QRXMsIGl0IGlzIG5vdCBwb3NzaWJsZSB0byBuZWdvdGlhdGUgYW55IGludGVyZmFjZQ0KICAg
ID4gICAgPiAgIHBhcmFtZXRlcnMu4oCcDQogICAgPiAgICA+V2h5IGlzIHRoYXQgbm90ZSB0aGVy
ZT8gSXMgdGhhdCBhbHJlYWR5IGJlZW4gbWVudGlvbmVkIHByZXZpb3VzbHkuDQogICAgPiAgICAN
CiAgICA+ICAgIFRoaXMgaXMgdGhlIG9ubHkgcmVmZXJlbmNlIGluIHRoZSBkb2N1bWVudC4NCiAg
ICA+DQogICAgPjxQYXRyaWNlPiBGb3Jnb3QgbXkgdGhvdWdodHMgb24gdGhhdCBvbmUuDQogICAg
PiAgICANCiAgICA+ICAgID5GaWcuNCBtdXN0ICBiZSBtb3ZlZCB0byBwcm9wZXIgaW4gdGhlIHRl
eHQgT1IgY3JlYXRlIDIgc3Vic2VjdGlvbiBpbg0KICAgID4gICAgPjIuMg0KICAgID4gICAgDQog
ICAgPiAgICBTb3JyeSBkaWRu4oCZdCBnZXQgd2hhdCB5b3UgbWVhbiBoZXJlPyBDYW4geW91IGVs
YWJvcmF0ZT8NCiAgICA+DQogICAgPjxQYXRyaWNlPiBTb3JyeSDigKZMZXQgbWUgdHJ5IGFnYWlu
LiDigJxQMlAgUFcgRG93bnN0cmVhbSBGRUMgRWxlbWVudOKAnS4gSSB0aGluayB5b3Ugc2hvdWxk
IGhhdmUgYSBzZWN0aW9uIGp1c3Qgb24gdGhhdCB0b3BpYy4gQWN0dWFsbHksIG1heWJlIHlvdSBj
YW4gY3JlYXRlIGEgc3Vic2VjdGlvbiBmb3IgZWFjaCBkaWZmZXJlbnQgRkVDIGV4cGxhaW5lZCBp
biB0aGUgZG9jdW1lbnQuIA0KICAgID4gICAgDQogICAgDQogICAgT2ssIEkgd2lsbCBhZGQgc3Vi
c2VjdGlvbnMgZm9yIERvd25zdHJlYW0gYW5kIFVwc3RyZWFtLg0KICAgIA0KICAgIFRoYW5rcywN
CiAgICANCiAgICBTYW1pDQogICAgPiAgICA+IA0KICAgID4gICAgPuKAnEFzIHN1Y2gsIFBXIHN0
YXR1cyBuZWdvdGlhdGlvbiBwcm9jZWR1cmUNCiAgICA+ICAgID4gICBkZXNjcmliZWQgaW4gW1JG
QzQ0NDdiaXNdIGlzIG5vdCBhcHBsaWNhYmxlIHRvIFAyTVAgUFcuIEEgbm9kZQ0KICAgID4gICAg
Pk1VU1QNCiAgICA+ICAgID4gICBOT1QgY2xhaW0gdG8gYmUgIFAyTVAgUFcgY2FwYWJsZSBieSBz
ZW5kaW5nIGEgTERQIFAyTVAgUFcNCiAgICA+ICAgID5DYXBhYmlsaXR5DQogICAgPiAgICA+ICAg
VExWICBpZiBpdCBpcyBub3QgYWxzbyBjYXBhYmxlIG9mIGhhbmRsaW5nIFBXIHN0YXR1c+KAnA0K
ICAgID4gICAgPiANCiAgICA+ICAgID5TaG91bGQgYSBub2RlIHNlbmQgTERQIFAyTVAgUFcgQ2Fw
YWJpbGl0eSBUTFYgb3Igbm90PyBOb3Qgd2VsbCBleHBsYWluDQogICAgPiAgICANCiAgICA+ICAg
IFdoYXQgaXMgc2FpZCBoZXJlLCB0aGF0IHlvdSBjYW7igJl0IGJlIFAyTVAgUFcgY2FwYWJsZSB3
aXRob3V0IGJlaW5nIFBXIHN0YXR1cyBjYXBhYmxlLg0KICAgID4gICAgTm90IHN1cmUgaG93IHRv
IG1ha2UgaXQgY2xlYXJlci4NCiAgICA+DQogICAgPjxQYXRyaWNlPiByaWdodOKApiBJIG11c3Qg
aGF2ZSBiZWVuIHRpcmVkLiBUb28gbWFueSBOT1QgDQogICAgPiAgICANCiAgICA+ICAgID4NCiAg
ICA+ICAgID4gDQogICAgPiAgICA+VGhlcmUgaXMgc29tZSByZWZlcmVuY2UgdG8gTFNSIGluIHRo
ZSB0ZXh0IHdoZXJlIHRoZSBtYWpvciBwYXJ0IHVzZQ0KICAgID4gICAgPnRoZSB3b3JkaW5nIOKA
nG5vZGXigJ0uDQogICAgPiAgICANCiAgICA+ICAgIEkgd2lsbCBtYWtlIGFsbCBjb25zaXN0ZW50
LCBhbmQgdXNlIExTUiBpbnN0ZWFkIG9mIG5vZGUuDQogICAgPiAgICANCiAgICA+ICAgIFRoYW5r
cywNCiAgICA+ICAgIA0KICAgID4gICAgU2FtaQ0KICAgID4gICAgPiANCiAgICA+ICAgID5OaXRz
OiANCiAgICA+ICAgID5OL0ENCiAgICA+ICAgID4gDQogICAgPiAgICA+UmVnYXJkcywNCiAgICA+
ICAgID5QYXRyaWNlIEJyaXNzZXR0ZQ0KICAgID4gICAgPg0KICAgID4gICAgPg0KICAgID4gICAg
Pg0KICAgID4gICAgPg0KICAgID4gICAgDQogICAgPg0KICAgIA0KDQo=


From nobody Thu May 18 13:54:17 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 7D876129B55; Thu, 18 May 2017 13:54:07 -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 AuFAi7Ey_ya0; Thu, 18 May 2017 13:54:05 -0700 (PDT)
Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::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 BCBB2129BDA; Thu, 18 May 2017 13:48:08 -0700 (PDT)
Received: by mail-qt0-x22e.google.com with SMTP id c13so44357435qtc.1; Thu, 18 May 2017 13:48:08 -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=iMx3OZGOhgrQiAN7fV+Jcg3bGsPXOS4n792xRPXdOsU=; b=XpoYHqBcc/PN0YYBdSf2VDx0a7/t1YgIJjeMbzdmlZQhgSHLxBGTJFO00MqVgHISGd JM4DGPPuIbbxhl4dtZQf1BP9aNrHFh8sUOb/237opM8skoXjuEwKIE+A1pCrzt3R3V0D etCsTwNwF1XMMhB7sKLZXvzptQ9Yfh1Ad0Dd6yAA+4qaA6QP460dqQfo3rs693keYd2Z kLYdcfPPmybwWoDwCNltag81+P1xQKvGes5B5BuRYT3IbTKI3mIFgfxDiJ+GUnoD2Gia hud7zUOE8YzKOBlyb0lrGSBzfR/t6j567u2uOF/c/YwX0pHE1XqyOGPn0tDnjBIkC/Si Tfkw==
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=iMx3OZGOhgrQiAN7fV+Jcg3bGsPXOS4n792xRPXdOsU=; b=p1/AwDtDyfM961KHUs52xmljZ4/KdvNdHb2d0gXAqhGOqwtk6WGATB1683bvMUU4o2 HUCLHWzvyTMpOxd6VA+XZGBym6MurGC9v4ujqY8cHgoTNJs6z72O3dAyDuzqt7CFBc3N cx5yr0DxxbVc9eZUV8o5+KEZ9t7ij9gacMwwwVnAUUaEuQG6d7fWWS/y13f3b/J1lfta IkmJ9aiv9P7d9iO8bOS4I0yc5hiLqRYAl+4g6BN9BSQGIH27OhOcQNVO6WnsdxkEqlSk 10lRTpO7SgDIYA+fq+8j5gBOipsUnq5L1Ar0IP/d0QJ00OQSDr+uUTcNPGiI/E/lV8w+ k7wQ==
X-Gm-Message-State: AODbwcC5lC7eZJzKtNJNUaLxRhJVzecTHTGGpccYTdsrUGOyNiQHgG+2 yyQp4qJ/u3EhQjNGIMHqbGlWar5U6Q==
X-Received: by 10.237.36.3 with SMTP id r3mr6285091qtc.200.1495140487931; Thu, 18 May 2017 13:48:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.31.101 with HTTP; Thu, 18 May 2017 13:48:07 -0700 (PDT)
In-Reply-To: <2DD56D786E600F45AC6BDE7DA4E8A8C118BDB690@eusaamb107.ericsson.se>
References: <149484519593.2843.448630358757818654@ietfa.amsl.com> <2DD56D786E600F45AC6BDE7DA4E8A8C118BDB690@eusaamb107.ericsson.se>
From: Dan Romascanu <dromasca@gmail.com>
Date: Thu, 18 May 2017 23:48:07 +0300
Message-ID: <CAFgnS4XLycJht29ahFnow-qhfKvRYOKOHc-BG_jZm6qA7vgfqw@mail.gmail.com>
Subject: Re: Genart last call review of draft-ietf-tls-ecdhe-psk-aead-03
To: Daniel Migault <daniel.migault@ericsson.com>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>,  "draft-ietf-tls-ecdhe-psk-aead.all@ietf.org" <draft-ietf-tls-ecdhe-psk-aead.all@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>, "tls@ietf.org" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="001a114385c8ac2ac6054fd285ed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QIx9igtuohND0LW-uqxP0_IaMW8>
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, 18 May 2017 20:54:08 -0000

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

Hi Daniel,

Thank you for your response, and for addressing my comment. Yes, the edits
address my concern, this is exactly the kind of clarification text that IMO
was missing. I suggest to publish the revised version as soon as you
address all other comments. The document can be approved by the IESG if
they believe it's ready and will wait in the RFC Editor Queue because of
the dependency on TLS 1.3.

Regards,

Dan


On Thu, May 18, 2017 at 8:44 PM, Daniel Migault <daniel.migault@ericsson.com
> wrote:

> Hi Dan,
>
> Thank you for your reviews and comments. I believe the following text
> provides more explanation on how the provided cipher suites are negotiated
> by TLS1.3 as well as why point codes defined in the document does not apply
> to TLS1.3. Feel free to let me know if that address your concern and I can
> publish version 04 with the text below.
>
> Unlike TLS1.2, TLS1.3 separates authentication and cipher suite
> negotiation <xref target="I-D.ietf-tls-tls13"/> Section 1.2. TLS1.3
> supports PSK with ECDHE key exchange and the cipher suites
> TLS_AES_128_GCM_SHA256, TLS_AES_256_GCM_SHA384, TLS_AES_128_CCM_8_SHA256
> and  TLS_AES_128_CCM_SHA256 are part of the specification. As a result, TLS
> 1.3 and higher versions, negotiate and support these cipher suites in a
> different way.
>
> I am not sure we  have to wait for the publication of TLS1.3 as changes on
> TLS1.3 are unlikely to impact the code point assigned. However, we
> currently have TLS1.3 as a normative reference.
>
> Yours,
> Daniel
> -----Original Message-----
> From: Dan Romascanu [mailto:dromasca@gmail.com]
> Sent: Monday, May 15, 2017 6:47 AM
> To: gen-art@ietf.org
> Cc: draft-ietf-tls-ecdhe-psk-aead.all@ietf.org; ietf@ietf.org;
> tls@ietf.org; dromasca@gmail.com
> Subject: Genart last call review of draft-ietf-tls-ecdhe-psk-aead-03
>
> Reviewer: Dan Romascanu
> 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 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-tls-ecdhe-psk-aead-??
> Reviewer: Dan Romascanu
> Review Date: 2017-05-15
> IETF LC End Date: 2017-05-18
> IESG Telechat date: 2017-05-25
>
> Summary:
>
> This is a straight-forward and clear document that defines several new
> cipher suites for the Transport Layer Security (TLS) protocol version
> 1.2 and higher, based on the Ephemeral Elliptic Curve Diffie-Hellman with
> Pre-Shared Key (ECDHE_PSK) key exchange together with the Authenticated
> Encryption with Associated Data (AEAD) algorithms AES-GCM and AES-CCM. The
> document is well written and I appreciate the effort to clarify in the
> Introduction the context, what was missing, and why the document is
> necessary. The document is Ready, there is one issue about support for TLS
> version 1.3 and higher that may need some text clarification.
>
> Major issues:
>
> Minor issues:
>
> Section 4 ('Applicable TLS Versions') describes in details how the cipher
> suites defined in the document make use of the authenticated encryption
> with additional data (AEAD) defined in TLS 1.2 [RFC5246] and DTLS 1.2
> [RFC6347]. About TLS 1.3 it just says:
>
> ' TLS 1.3 and above version, negotiate and support these cipher suites in
> a different way.'
>
> This may raise some concerns as 'in a different way' is ambiguous,
> especially compared to the details included for TLS 1.2. Moreover, TLS
> 1.3 is still work-in-progress, and I believe that this document when
> approved needs to wait for TLS 1.3 to be approved for publication.
> Will anything change, or need to be added? Some better clarification text
> would help IMO.
>
> Nits/editorial comments:
>
>
>

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

<div dir=3D"ltr"><div><div><div>Hi Daniel, <br><br></div>Thank you for your=
 response, and for addressing my comment. Yes, the edits address my concern=
, this is exactly the kind of clarification text that IMO was missing. I su=
ggest to publish the revised version as soon as you address all other comme=
nts. The document can be approved by the IESG if they believe it&#39;s read=
y and will wait in the RFC Editor Queue because of the dependency on TLS 1.=
3. <br><br></div>Regards,<br><br></div>Dan<br><br></div><div class=3D"gmail=
_extra"><br><div class=3D"gmail_quote">On Thu, May 18, 2017 at 8:44 PM, Dan=
iel Migault <span dir=3D"ltr">&lt;<a href=3D"mailto:daniel.migault@ericsson=
.com" target=3D"_blank">daniel.migault@ericsson.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">Hi Dan,<br>
<br>
Thank you for your reviews and comments. I believe the following text provi=
des more explanation on how the provided cipher suites are negotiated by TL=
S1.3 as well as why point codes defined in the document does not apply to T=
LS1.3. Feel free to let me know if that address your concern and I can publ=
ish version 04 with the text below.<br>
<br>
Unlike TLS1.2, TLS1.3 separates authentication and cipher suite negotiation=
 &lt;xref target=3D&quot;I-D.ietf-tls-tls13&quot;/&gt; Section 1.2. TLS1.3 =
supports PSK with ECDHE key exchange and the cipher suites TLS_AES_128_GCM_=
SHA256, TLS_AES_256_GCM_SHA384, TLS_AES_128_CCM_8_SHA256 and=C2=A0 TLS_AES_=
128_CCM_SHA256 are part of the specification. As a result, TLS 1.3 and high=
er versions, negotiate and support these cipher suites in a different way.<=
br>
<br>
I am not sure we=C2=A0 have to wait for the publication of TLS1.3 as change=
s on TLS1.3 are unlikely to impact the code point assigned. However, we cur=
rently have TLS1.3 as a normative reference.<br>
<br>
Yours,<br>
Daniel<br>
-----Original Message-----<br>
From: Dan Romascanu [mailto:<a href=3D"mailto:dromasca@gmail.com">dromasca@=
gmail.com</a>]<br>
Sent: Monday, May 15, 2017 6:47 AM<br>
To: <a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br>
Cc: <a href=3D"mailto:draft-ietf-tls-ecdhe-psk-aead.all@ietf.org">draft-iet=
f-tls-ecdhe-psk-aead.<wbr>all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.org=
">ietf@ietf.org</a>; <a href=3D"mailto:tls@ietf.org">tls@ietf.org</a>; <a h=
ref=3D"mailto:dromasca@gmail.com">dromasca@gmail.com</a><br>
Subject: Genart last call review of draft-ietf-tls-ecdhe-psk-aead-<wbr>03<b=
r>
<br>
Reviewer: Dan Romascanu<br>
Review result: Ready with Issues<br>
<br>
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 t=
he IETF Chair.=C2=A0 Please treat these comments just like any other last c=
all 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-tls-ecdhe-psk-aead-<wbr>??<br>
Reviewer: Dan Romascanu<br>
Review Date: 2017-05-15<br>
IETF LC End Date: 2017-05-18<br>
IESG Telechat date: 2017-05-25<br>
<br>
Summary:<br>
<br>
This is a straight-forward and clear document that defines several new ciph=
er suites for the Transport Layer Security (TLS) protocol version<br>
1.2 and higher, based on the Ephemeral Elliptic Curve Diffie-Hellman with P=
re-Shared Key (ECDHE_PSK) key exchange together with the Authenticated Encr=
yption with Associated Data (AEAD) algorithms AES-GCM and AES-CCM. The docu=
ment is well written and I appreciate the effort to clarify in the Introduc=
tion the context, what was missing, and why the document is necessary. The =
document is Ready, there is one issue about support for TLS version 1.3 and=
 higher that may need some text clarification.<br>
<br>
Major issues:<br>
<br>
Minor issues:<br>
<br>
Section 4 (&#39;Applicable TLS Versions&#39;) describes in details how the =
cipher suites defined in the document make use of the authenticated encrypt=
ion with additional data (AEAD) defined in TLS 1.2 [RFC5246] and DTLS 1.2 [=
RFC6347]. About TLS 1.3 it just says:<br>
<br>
&#39; TLS 1.3 and above version, negotiate and support these cipher suites =
in a different way.&#39;<br>
<br>
This may raise some concerns as &#39;in a different way&#39; is ambiguous, =
especially compared to the details included for TLS 1.2. Moreover, TLS<br>
1.3 is still work-in-progress, and I believe that this document when approv=
ed needs to wait for TLS 1.3 to be approved for publication.<br>
Will anything change, or need to be added? Some better clarification text w=
ould help IMO.<br>
<br>
Nits/editorial comments:<br>
<br>
<br>
</blockquote></div><br></div>

--001a114385c8ac2ac6054fd285ed--


From nobody Thu May 18 13:58:41 2017
Return-Path: <tjackson@mobileiron.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 6D16B129B9B; Thu, 18 May 2017 13:58:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.69
X-Spam-Level: 
X-Spam-Status: No, score=-4.69 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_H2=-2.8, SPF_HELO_PASS=-0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mobileironinc.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 bBVw_hFjiOHw; Thu, 18 May 2017 13:58:29 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0073.outbound.protection.outlook.com [104.47.33.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FF5B129BCA; Thu, 18 May 2017 13:52:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mobileironinc.onmicrosoft.com; s=selector1-mobileiron-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=8oxQAJSu9obK7Y+tPicIqxRgNSfStrFTPR6+VKWvTuc=; b=X8y17f65MsD05GotmcsFrJm+7KaBtTeTgbRbfP5idHNP79ip/jOKOc8wWTL6wZ91Z0BtdPCtmrf++BEBBxERF/o9weCumPhldwjccs5bCHcWHsMwUNcGpm4FB5ZBCUSmQ1SIFsJwO07FCrwO3cI0neLeRYBAqknINOLsXBMCWuM=
Received: from CY4PR10MB1734.namprd10.prod.outlook.com (10.172.69.9) by CY4PR10MB1734.namprd10.prod.outlook.com (10.172.69.9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1084.16; Thu, 18 May 2017 20:52:05 +0000
Received: from CY4PR10MB1734.namprd10.prod.outlook.com ([10.172.69.9]) by CY4PR10MB1734.namprd10.prod.outlook.com ([10.172.69.9]) with mapi id 15.01.1084.030; Thu, 18 May 2017 20:52:05 +0000
From: Timothy Jackson <tjackson@mobileiron.com>
To: Daniel Migault <daniel.migault@ericsson.com>, Simon Friedberger <simon.tls@a-oben.org>, "ietf@ietf.org" <ietf@ietf.org>
CC: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] Last Call: <draft-ietf-tls-ecdhe-psk-aead-03.txt> (ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transport Layer Security (TLS)) to Proposed Standard
Thread-Topic: [TLS] Last Call: <draft-ietf-tls-ecdhe-psk-aead-03.txt> (ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transport Layer Security (TLS)) to Proposed Standard
Thread-Index: AQHSxPbUkILbHt+MPUCNqbVojoqxB6HkuUiAgBW56AD//769gA==
Date: Thu, 18 May 2017 20:52:04 +0000
Message-ID: <6191522F-FB75-4B74-B7DE-200FEDB3F021@mobileiron.com>
References: <149391606578.6842.3727373203321848879.idtracker@ietfa.amsl.com> <4373f972-bf9b-4dbe-1b59-7f51846831f3@a-oben.org> <2DD56D786E600F45AC6BDE7DA4E8A8C118BDB69D@eusaamb107.ericsson.se>
In-Reply-To: <2DD56D786E600F45AC6BDE7DA4E8A8C118BDB69D@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ericsson.com; dkim=none (message not signed) header.d=none;ericsson.com; dmarc=none action=none header.from=mobileiron.com;
x-originating-ip: [198.61.62.10]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR10MB1734; 7:c2SO4mwpDoTHdnVCqPTFWXKgfdCzBLpNMYEjXd7glqpvBSSYUNwbWVROnQOQPJfOiSJ4RgY88ph5CqyGNB2LCPF8rHcOYDQUQ6U07ftZvG8LpSFYWdpUuXpm69iWD8ErvWRx1k8VqfF7/lhYkdubZBqj26pd2CW74dRgRIqRzsQN4VvCHdelxZ6k/Mrd16sbT60th3q0ZLV9fspAX/lli2I9JU/bDivyi0ab59Pm40XDlJvgGo1UrMxuqaaep9YhlNVQzSfSHOMW8FfOa/YgMI/oQ5Kn5u61n6eE3Q/K7/LcBcd0mEjR2J5IJd2bzGj5pLQ1O2MVbxNPdZAVYl2rDg==
x-ms-office365-filtering-correlation-id: 9f855d22-830f-467c-3b89-08d49e2fbdc4
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081); SRVR:CY4PR10MB1734; 
x-microsoft-antispam-prvs: <CY4PR10MB1734A78770ECEC7F90D0FDEBAAE40@CY4PR10MB1734.namprd10.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(120809045254105)(192374486261705); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(93006095)(93001095)(10201501046)(6041248)(20161123555025)(20161123564025)(20161123558100)(20161123562025)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6072148); SRVR:CY4PR10MB1734; BCL:0; PCL:0; RULEID:; SRVR:CY4PR10MB1734; 
x-forefront-prvs: 0311124FA9
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39400400002)(39850400002)(39840400002)(39450400003)(377454003)(13464003)(24454002)(6246003)(122556002)(8936002)(229853002)(54356999)(25786009)(76176999)(53546009)(50986999)(99286003)(38730400002)(53936002)(2501003)(6512007)(8676002)(5660300001)(81166006)(3280700002)(345774005)(6306002)(305945005)(230783001)(33656002)(2906002)(15650500001)(7736002)(3660700001)(6486002)(6506006)(6436002)(2950100002)(4326008)(36756003)(77096006)(6116002)(3846002)(102836003)(66066001)(966005)(478600001)(86362001)(189998001); DIR:OUT; SFP:1101; SCL:1; SRVR:CY4PR10MB1734; H:CY4PR10MB1734.namprd10.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <40E8A7DF23105A4DA7A1C7603B0FC366@namprd10.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: mobileiron.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 May 2017 20:52:04.7625 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8392379d-8a98-4cb4-8cfe-5e7fa92e4e60
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR10MB1734
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DE7FG3VQcqyotryHX_OXsGBuTVU>
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, 18 May 2017 20:58:32 -0000

T25lIHNtYWxsIG5pdC4NCg0KPiBFQ0RIRSBwcm92aWRlcyBwZXJmZWN0IGZvcndhcmQgc2VjcmVj
eQ0KSSB0aG91Z2h0IHdlIGhhZCBkZWNpZGVkIHRvIGNoYW5nZSDigJxwZXJmZWN0IGZvcndhcmQg
c2VjcmVjeeKAnSB0byBqdXN0IOKAnGZvcndhcmQgc2VjcmVjeeKAnSBzaW5jZSDigJxwZXJmZWN0
4oCdIGlzIHN1Y2ggYSBkaWZmaWN1bHQgc3RhbmRhcmQgdG8gcmVhY2g/DQoNClRpbQ0K4oCUDQpU
aW0gSmFja3NvbiB8IFByb2R1Y3QgU2VjdXJpdHkgQXJjaGl0ZWN0IHwgTW9iaWxlSXJvbiwgSW5j
Lg0KDQpPbiA1LzE4LzE3LCAxMDo0NSBBTSwgIlRMUyBvbiBiZWhhbGYgb2YgRGFuaWVsIE1pZ2F1
bHQiIDx0bHMtYm91bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2YgZGFuaWVsLm1pZ2F1bHRAZXJp
Y3Nzb24uY29tPiB3cm90ZToNCg0KICAgIEhpIFNpbW9uLCANCiAgICANCiAgICBUaGFuayB5b3Ug
Zm9yIHRoZSByZXZpZXcuIEkgYmVsaWV2ZSB3ZSBoYXZlIGFkZHJlc3NlZCB5b3VyIGNvbW1lbnRz
IGluIG91ciB2ZXJzaW9uIDA0LiBQbGVhc2Ugc2VlIG15IGNvbW1lbnRzIGlubGluZS4gDQogICAg
DQogICAgWW91cnMsIA0KICAgIERhbmllbA0KICAgIA0KICAgIC0tLS0tT3JpZ2luYWwgTWVzc2Fn
ZS0tLS0tDQogICAgRnJvbTogVExTIFttYWlsdG86dGxzLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJl
aGFsZiBPZiBTaW1vbiBGcmllZGJlcmdlcg0KICAgIFNlbnQ6IFRodXJzZGF5LCBNYXkgMDQsIDIw
MTcgNTo1OSBQTQ0KICAgIFRvOiBpZXRmQGlldGYub3JnDQogICAgQ2M6IHRsc0BpZXRmLm9yZw0K
ICAgIFN1YmplY3Q6IFJlOiBbVExTXSBMYXN0IENhbGw6IDxkcmFmdC1pZXRmLXRscy1lY2RoZS1w
c2stYWVhZC0wMy50eHQ+IChFQ0RIRV9QU0sgd2l0aCBBRVMtR0NNIGFuZCBBRVMtQ0NNIENpcGhl
ciBTdWl0ZXMgZm9yIFRyYW5zcG9ydCBMYXllciBTZWN1cml0eSAoVExTKSkgdG8gUHJvcG9zZWQg
U3RhbmRhcmQNCiAgICANCiAgICBOaXRzOg0KICAgIA0KICAgIAlSRkMgNDI3OSByZWZlcmVuY2Ug
aXMgbWlzc2luZy4NCiAgICBNR0xUOiBJdCBzZWVtcyB0aGUgcmVmZXJlbmNlIGlzIG1lbnRpb25l
ZCBpbiB0aGUgY3VycmVudCB2ZXJzaW9uIGluIHRoZSBOb3JtYXRpdmUgcmVmZXJlbmNlIGFzIHdl
bGwgIGFzIGluIHRoZSBpbnRyb2R1Y3Rpb24gYXQgbGluZSAxMjcsICBpbiBzZWN0aW9uIDMgbGlu
ZSAxNDMuIEluIGNhc2UgeW91IG1lYW50IGFub3RoZXIgcmVmZXJlbmNlLCBwbGVhc2UgbGV0IHVz
IGtub3cuIA0KICAgIA0KICAgIA0KICAgIA0KICAgIAkiVExTIDEuMyBhbmQgYWJvdmUgdmVyc2lv
biwgIiBzaG91bGQgcHJvYmFibHkgYmUgIlRMUyAxLjMgYW5kIGFib3ZlIiBvciAiVExTIDEuMyBh
bmQgaGlnaGVyIHZlcnNpb25zIg0KICAgIE1HTFQ6IENoYW5nZWQgdG8gIlRMUyAxLjMgYW5kIGhp
Z2hlciB2ZXJzaW9ucyINCiAgICANCiAgICBPbiAwNC8wNS8xNyAxODo0MSwgVGhlIElFU0cgd3Jv
dGU6DQogICAgPiBUaGUgSUVTRyBoYXMgcmVjZWl2ZWQgYSByZXF1ZXN0IGZyb20gdGhlIFRyYW5z
cG9ydCBMYXllciBTZWN1cml0eSBXRw0KICAgID4gKHRscykgdG8gY29uc2lkZXIgdGhlIGZvbGxv
d2luZyBkb2N1bWVudDoNCiAgICA+IC0gJ0VDREhFX1BTSyB3aXRoIEFFUy1HQ00gYW5kIEFFUy1D
Q00gQ2lwaGVyIFN1aXRlcyBmb3IgVHJhbnNwb3J0IExheWVyDQogICAgPiAgICBTZWN1cml0eSAo
VExTKScNCiAgICA+ICAgPGRyYWZ0LWlldGYtdGxzLWVjZGhlLXBzay1hZWFkLTAzLnR4dD4gYXMg
UHJvcG9zZWQgU3RhbmRhcmQNCiAgICA+DQogICAgPiBUaGUgSUVTRyBwbGFucyB0byBtYWtlIGEg
ZGVjaXNpb24gaW4gdGhlIG5leHQgZmV3IHdlZWtzLCBhbmQgc29saWNpdHMgDQogICAgPiBmaW5h
bCBjb21tZW50cyBvbiB0aGlzIGFjdGlvbi4gUGxlYXNlIHNlbmQgc3Vic3RhbnRpdmUgY29tbWVu
dHMgdG8gdGhlIA0KICAgID4gaWV0ZkBpZXRmLm9yZyBtYWlsaW5nIGxpc3RzIGJ5IDIwMTctMDUt
MTguIEV4Y2VwdGlvbmFsbHksIGNvbW1lbnRzIG1heSANCiAgICA+IGJlIHNlbnQgdG8gaWVzZ0Bp
ZXRmLm9yZyBpbnN0ZWFkLiBJbiBlaXRoZXIgY2FzZSwgcGxlYXNlIHJldGFpbiB0aGUgDQogICAg
PiBiZWdpbm5pbmcgb2YgdGhlIFN1YmplY3QgbGluZSB0byBhbGxvdyBhdXRvbWF0ZWQgc29ydGlu
Zy4NCiAgICA+DQogICAgPiBBYnN0cmFjdA0KICAgID4NCiAgICA+DQogICAgPiAgICBUaGlzIGRv
Y3VtZW50IGRlZmluZXMgc2V2ZXJhbCBuZXcgY2lwaGVyIHN1aXRlcyBmb3IgdGhlIFRyYW5zcG9y
dA0KICAgID4gICAgTGF5ZXIgU2VjdXJpdHkgKFRMUykgcHJvdG9jb2wuICBUaGUgY2lwaGVyIHN1
aXRlcyBhcmUgYWxsIGJhc2VkIG9uDQogICAgPiAgICB0aGUgRXBoZW1lcmFsIEVsbGlwdGljIEN1
cnZlIERpZmZpZS1IZWxsbWFuIHdpdGggUHJlLVNoYXJlZCBLZXkNCiAgICA+ICAgIChFQ0RIRV9Q
U0spIGtleSBleGNoYW5nZSB0b2dldGhlciB3aXRoIHRoZSBBdXRoZW50aWNhdGVkIEVuY3J5cHRp
b24NCiAgICA+ICAgIHdpdGggQXNzb2NpYXRlZCBEYXRhIChBRUFEKSBhbGdvcml0aG1zIEFFUy1H
Q00gYW5kIEFFUy1DQ00uICBQU0sNCiAgICA+ICAgIHByb3ZpZGVzIGxpZ2h0IGFuZCBlZmZpY2ll
bnQgYXV0aGVudGljYXRpb24sIEVDREhFIHByb3ZpZGVzIHBlcmZlY3QNCiAgICA+ICAgIGZvcndh
cmQgc2VjcmVjeSwgYW5kIEFFUy1HQ00gYW5kIEFFUy1DQ00gcHJvdmlkZXMgZW5jcnlwdGlvbiBh
bmQNCiAgICA+ICAgIGludGVncml0eSBwcm90ZWN0aW9uLg0KICAgID4NCiAgICA+DQogICAgPg0K
ICAgID4NCiAgICA+IFRoZSBmaWxlIGNhbiBiZSBvYnRhaW5lZCB2aWENCiAgICA+IGh0dHBzOi8v
ZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtdGxzLWVjZGhlLXBzay1hZWFkLw0K
ICAgID4NCiAgICA+IElFU0cgZGlzY3Vzc2lvbiBjYW4gYmUgdHJhY2tlZCB2aWENCiAgICA+IGh0
dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtdGxzLWVjZGhlLXBzay1h
ZWFkL2JhbGxvdC8NCiAgICA+DQogICAgPg0KICAgID4gTm8gSVBSIGRlY2xhcmF0aW9ucyBoYXZl
IGJlZW4gc3VibWl0dGVkIGRpcmVjdGx5IG9uIHRoaXMgSS1ELg0KICAgID4NCiAgICA+DQogICAg
Pg0KICAgID4NCiAgICA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fDQogICAgPiBUTFMgbWFpbGluZyBsaXN0DQogICAgPiBUTFNAaWV0Zi5vcmcNCiAgICA+
IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGxzDQogICAgDQogICAgX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCiAgICBUTFMgbWFp
bGluZyBsaXN0DQogICAgVExTQGlldGYub3JnDQogICAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby90bHMNCiAgICANCiAgICBfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KICAgIFRMUyBtYWlsaW5nIGxpc3QNCiAgICBUTFNAaWV0Zi5v
cmcNCiAgICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Rscw0KICAgIA0K
DQo=


From nobody Thu May 18 14:07:47 2017
Return-Path: <prvs=6311b0b214=uri@ll.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 75037126C23; Thu, 18 May 2017 14:07:45 -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, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 y1-lzxazPlwF; Thu, 18 May 2017 14:07:43 -0700 (PDT)
Received: from llmx2.ll.mit.edu (LLMX2.LL.MIT.EDU [129.55.12.48]) by ietfa.amsl.com (Postfix) with ESMTP id 67FC112EB52; Thu, 18 May 2017 14:01:22 -0700 (PDT)
Received: from LLE2K10-HUB01.mitll.ad.local (LLE2K10-HUB01.mitll.ad.local) by llmx2.ll.mit.edu (unknown) with ESMTP id v4IL13jk046733; Thu, 18 May 2017 17:01:03 -0400
From: "Blumenthal, Uri - 0553 - MITLL" <uri@ll.mit.edu>
To: Timothy Jackson <tjackson@mobileiron.com>
CC: Daniel Migault <daniel.migault@ericsson.com>, Simon Friedberger <simon.tls@a-oben.org>, "ietf@ietf.org" <ietf@ietf.org>, "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] Last Call: <draft-ietf-tls-ecdhe-psk-aead-03.txt> (ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transport Layer Security (TLS)) to Proposed Standard
Thread-Topic: [TLS] Last Call: <draft-ietf-tls-ecdhe-psk-aead-03.txt> (ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transport Layer Security (TLS)) to Proposed Standard
Thread-Index: AQHSxPVWpHIsuShcKEe7pKr8MzTDmKHk/FmAgBW56QCAADQWAIAAAn8A
Date: Thu, 18 May 2017 21:01:02 +0000
Message-ID: <7E11398B-EAEF-4E06-BC6A-6797BA2197AE@ll.mit.edu>
References: <149391606578.6842.3727373203321848879.idtracker@ietfa.amsl.com> <4373f972-bf9b-4dbe-1b59-7f51846831f3@a-oben.org> <2DD56D786E600F45AC6BDE7DA4E8A8C118BDB69D@eusaamb107.ericsson.se> <6191522F-FB75-4B74-B7DE-200FEDB3F021@mobileiron.com>
In-Reply-To: <6191522F-FB75-4B74-B7DE-200FEDB3F021@mobileiron.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Content-Type: multipart/signed; boundary="Apple-Mail-2D23B870-777E-4452-9D5E-0D29511845E5"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-05-18_05:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1705180142
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9D_1UiVKaK6vooiTneM0o3vgYgg>
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, 18 May 2017 21:07:46 -0000

--Apple-Mail-2D23B870-777E-4452-9D5E-0D29511845E5
Content-Type: text/plain;
	charset=windows-1251
Content-Transfer-Encoding: base64

SXQgaXMgYSBtYXRoZW1hdGljYWwgY3J5cHRvZ3JhcGhpYyB0ZXJtLCBhbmQgYXMgc3VjaCBpcyBp
bmNvbnRyb3ZlcnRpYmxlLiANCg0KSSBzYXkgbGVhdmUgaXQgaW4uDQoNClJlZ2FyZHMsDQpVcmkN
Cg0KU2VudCBmcm9tIG15IGlQaG9uZQ0KDQo+IE9uIE1heSAxOCwgMjAxNywgYXQgMTY6NTgsIFRp
bW90aHkgSmFja3NvbiA8dGphY2tzb25AbW9iaWxlaXJvbi5jb20+IHdyb3RlOg0KPiANCj4gT25l
IHNtYWxsIG5pdC4NCj4gDQo+PiBFQ0RIRSBwcm92aWRlcyBwZXJmZWN0IGZvcndhcmQgc2VjcmVj
eQ0KPiBJIHRob3VnaHQgd2UgaGFkIGRlY2lkZWQgdG8gY2hhbmdlIJNwZXJmZWN0IGZvcndhcmQg
c2VjcmVjeZQgdG8ganVzdCCTZm9yd2FyZCBzZWNyZWN5lCBzaW5jZSCTcGVyZmVjdJQgaXMgc3Vj
aCBhIGRpZmZpY3VsdCBzdGFuZGFyZCB0byByZWFjaD8NCj4gDQo+IFRpbQ0KPiCXDQo+IFRpbSBK
YWNrc29uIHwgUHJvZHVjdCBTZWN1cml0eSBBcmNoaXRlY3QgfCBNb2JpbGVJcm9uLCBJbmMuDQo+
IA0KPiBPbiA1LzE4LzE3LCAxMDo0NSBBTSwgIlRMUyBvbiBiZWhhbGYgb2YgRGFuaWVsIE1pZ2F1
bHQiIDx0bHMtYm91bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2YgZGFuaWVsLm1pZ2F1bHRAZXJp
Y3Nzb24uY29tPiB3cm90ZToNCj4gDQo+ICAgIEhpIFNpbW9uLCANCj4gDQo+ICAgIFRoYW5rIHlv
dSBmb3IgdGhlIHJldmlldy4gSSBiZWxpZXZlIHdlIGhhdmUgYWRkcmVzc2VkIHlvdXIgY29tbWVu
dHMgaW4gb3VyIHZlcnNpb24gMDQuIFBsZWFzZSBzZWUgbXkgY29tbWVudHMgaW5saW5lLiANCj4g
DQo+ICAgIFlvdXJzLCANCj4gICAgRGFuaWVsDQo+IA0KPiAgICAtLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KPiAgICBGcm9tOiBUTFMgW21haWx0bzp0bHMtYm91bmNlc0BpZXRmLm9yZ10gT24g
QmVoYWxmIE9mIFNpbW9uIEZyaWVkYmVyZ2VyDQo+ICAgIFNlbnQ6IFRodXJzZGF5LCBNYXkgMDQs
IDIwMTcgNTo1OSBQTQ0KPiAgICBUbzogaWV0ZkBpZXRmLm9yZw0KPiAgICBDYzogdGxzQGlldGYu
b3JnDQo+ICAgIFN1YmplY3Q6IFJlOiBbVExTXSBMYXN0IENhbGw6IDxkcmFmdC1pZXRmLXRscy1l
Y2RoZS1wc2stYWVhZC0wMy50eHQ+IChFQ0RIRV9QU0sgd2l0aCBBRVMtR0NNIGFuZCBBRVMtQ0NN
IENpcGhlciBTdWl0ZXMgZm9yIFRyYW5zcG9ydCBMYXllciBTZWN1cml0eSAoVExTKSkgdG8gUHJv
cG9zZWQgU3RhbmRhcmQNCj4gDQo+ICAgIE5pdHM6DQo+IA0KPiAgICAgICAgUkZDIDQyNzkgcmVm
ZXJlbmNlIGlzIG1pc3NpbmcuDQo+ICAgIE1HTFQ6IEl0IHNlZW1zIHRoZSByZWZlcmVuY2UgaXMg
bWVudGlvbmVkIGluIHRoZSBjdXJyZW50IHZlcnNpb24gaW4gdGhlIE5vcm1hdGl2ZSByZWZlcmVu
Y2UgYXMgd2VsbCAgYXMgaW4gdGhlIGludHJvZHVjdGlvbiBhdCBsaW5lIDEyNywgIGluIHNlY3Rp
b24gMyBsaW5lIDE0My4gSW4gY2FzZSB5b3UgbWVhbnQgYW5vdGhlciByZWZlcmVuY2UsIHBsZWFz
ZSBsZXQgdXMga25vdy4gDQo+IA0KPiANCj4gDQo+ICAgICAgICAiVExTIDEuMyBhbmQgYWJvdmUg
dmVyc2lvbiwgIiBzaG91bGQgcHJvYmFibHkgYmUgIlRMUyAxLjMgYW5kIGFib3ZlIiBvciAiVExT
IDEuMyBhbmQgaGlnaGVyIHZlcnNpb25zIg0KPiAgICBNR0xUOiBDaGFuZ2VkIHRvICJUTFMgMS4z
IGFuZCBoaWdoZXIgdmVyc2lvbnMiDQo+IA0KPj4gICAgT24gMDQvMDUvMTcgMTg6NDEsIFRoZSBJ
RVNHIHdyb3RlOg0KPj4gVGhlIElFU0cgaGFzIHJlY2VpdmVkIGEgcmVxdWVzdCBmcm9tIHRoZSBU
cmFuc3BvcnQgTGF5ZXIgU2VjdXJpdHkgV0cNCj4+ICh0bHMpIHRvIGNvbnNpZGVyIHRoZSBmb2xs
b3dpbmcgZG9jdW1lbnQ6DQo+PiAtICdFQ0RIRV9QU0sgd2l0aCBBRVMtR0NNIGFuZCBBRVMtQ0NN
IENpcGhlciBTdWl0ZXMgZm9yIFRyYW5zcG9ydCBMYXllcg0KPj4gICBTZWN1cml0eSAoVExTKScN
Cj4+ICA8ZHJhZnQtaWV0Zi10bHMtZWNkaGUtcHNrLWFlYWQtMDMudHh0PiBhcyBQcm9wb3NlZCBT
dGFuZGFyZA0KPj4gDQo+PiBUaGUgSUVTRyBwbGFucyB0byBtYWtlIGEgZGVjaXNpb24gaW4gdGhl
IG5leHQgZmV3IHdlZWtzLCBhbmQgc29saWNpdHMgDQo+PiBmaW5hbCBjb21tZW50cyBvbiB0aGlz
IGFjdGlvbi4gUGxlYXNlIHNlbmQgc3Vic3RhbnRpdmUgY29tbWVudHMgdG8gdGhlIA0KPj4gaWV0
ZkBpZXRmLm9yZyBtYWlsaW5nIGxpc3RzIGJ5IDIwMTctMDUtMTguIEV4Y2VwdGlvbmFsbHksIGNv
bW1lbnRzIG1heSANCj4+IGJlIHNlbnQgdG8gaWVzZ0BpZXRmLm9yZyBpbnN0ZWFkLiBJbiBlaXRo
ZXIgY2FzZSwgcGxlYXNlIHJldGFpbiB0aGUgDQo+PiBiZWdpbm5pbmcgb2YgdGhlIFN1YmplY3Qg
bGluZSB0byBhbGxvdyBhdXRvbWF0ZWQgc29ydGluZy4NCj4+IA0KPj4gQWJzdHJhY3QNCj4+IA0K
Pj4gDQo+PiAgIFRoaXMgZG9jdW1lbnQgZGVmaW5lcyBzZXZlcmFsIG5ldyBjaXBoZXIgc3VpdGVz
IGZvciB0aGUgVHJhbnNwb3J0DQo+PiAgIExheWVyIFNlY3VyaXR5IChUTFMpIHByb3RvY29sLiAg
VGhlIGNpcGhlciBzdWl0ZXMgYXJlIGFsbCBiYXNlZCBvbg0KPj4gICB0aGUgRXBoZW1lcmFsIEVs
bGlwdGljIEN1cnZlIERpZmZpZS1IZWxsbWFuIHdpdGggUHJlLVNoYXJlZCBLZXkNCj4+ICAgKEVD
REhFX1BTSykga2V5IGV4Y2hhbmdlIHRvZ2V0aGVyIHdpdGggdGhlIEF1dGhlbnRpY2F0ZWQgRW5j
cnlwdGlvbg0KPj4gICB3aXRoIEFzc29jaWF0ZWQgRGF0YSAoQUVBRCkgYWxnb3JpdGhtcyBBRVMt
R0NNIGFuZCBBRVMtQ0NNLiAgUFNLDQo+PiAgIHByb3ZpZGVzIGxpZ2h0IGFuZCBlZmZpY2llbnQg
YXV0aGVudGljYXRpb24sIEVDREhFIHByb3ZpZGVzIHBlcmZlY3QNCj4+ICAgZm9yd2FyZCBzZWNy
ZWN5LCBhbmQgQUVTLUdDTSBhbmQgQUVTLUNDTSBwcm92aWRlcyBlbmNyeXB0aW9uIGFuZA0KPj4g
ICBpbnRlZ3JpdHkgcHJvdGVjdGlvbi4NCj4+IA0KPj4gDQo+PiANCj4+IA0KPj4gVGhlIGZpbGUg
Y2FuIGJlIG9idGFpbmVkIHZpYQ0KPj4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2Mv
ZHJhZnQtaWV0Zi10bHMtZWNkaGUtcHNrLWFlYWQvDQo+PiANCj4+IElFU0cgZGlzY3Vzc2lvbiBj
YW4gYmUgdHJhY2tlZCB2aWENCj4+IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2Ry
YWZ0LWlldGYtdGxzLWVjZGhlLXBzay1hZWFkL2JhbGxvdC8NCj4+IA0KPj4gDQo+PiBObyBJUFIg
ZGVjbGFyYXRpb25zIGhhdmUgYmVlbiBzdWJtaXR0ZWQgZGlyZWN0bHkgb24gdGhpcyBJLUQuDQo+
PiANCj4+IA0KPj4gDQo+PiANCj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQo+PiBUTFMgbWFpbGluZyBsaXN0DQo+PiBUTFNAaWV0Zi5vcmcNCj4+IGh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGxzDQo+IA0KPiAgICBfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiAgICBUTFMgbWFpbGlu
ZyBsaXN0DQo+ICAgIFRMU0BpZXRmLm9yZw0KPiAgICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL3Rscw0KPiANCj4gICAgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCj4gICAgVExTIG1haWxpbmcgbGlzdA0KPiAgICBUTFNAaWV0Zi5v
cmcNCj4gICAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90bHMNCj4gDQo+
IA0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBU
TFMgbWFpbGluZyBsaXN0DQo+IFRMU0BpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL3Rscw0K
--Apple-Mail-2D23B870-777E-4452-9D5E-0D29511845E5
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINeDCCA4Mw
ggJroAMCAQICAQEwDQYJKoZIhvcNAQEFBQAwVDELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1JVCBM
aW5jb2xuIExhYm9yYXRvcnkxDDAKBgNVBAsTA1BLSTEWMBQGA1UEAxMNTUlUTEwgUm9vdCBDQTAe
Fw0wODA5MjMxMjAwMDBaFw0yOTEyMzEyMzU5NTlaMFQxCzAJBgNVBAYTAlVTMR8wHQYDVQQKExZN
SVQgTGluY29sbiBMYWJvcmF0b3J5MQwwCgYDVQQLEwNQS0kxFjAUBgNVBAMTDU1JVExMIFJvb3Qg
Q0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDFTikXWLImsvmtir9cEAqD3eQJMBMb
sHDQ0YWkQnUDdeyvpQgir3/VUkE6ALAOqtWwArWVHDL+WSsfM+ShuIyvXDONDbxJH/2yDmQByasy
oFhtzfTaq3AIYpnF012ECHadQ4I7XQAylSwI12mKQ9j26RPyWwD56iszhDWtz8vQnoAdGm05Tsi4
MF1mP6101vuC/4YqSevrCP2baxUZrChobsACqGxa9BQz+riH8fkWliXCdUASHYDOGqIb1vCXq4kk
jMn/y5RaV02RXDPUjl9H+8JrGItchbihTJ0G5EpMb56QSjEca4PvfLHkm2xJyJLwdAvagQzy2/5U
AL5qVuqDAgMBAAGjYDBeMA8GA1UdEwEB/wQFMAMBAf8wHQYDVR0OBBYEFGeqes/0Cqa5crWKoNKd
8hDDQ+0pMB8GA1UdIwQYMBaAFGeqes/0Cqa5crWKoNKd8hDDQ+0pMAsGA1UdDwQEAwIBhjANBgkq
hkiG9w0BAQUFAAOCAQEAPhttBWDQeHjYSlhfj8k+Q1Lc5QARZH9iDNlRjVAaL2tBnil9yNTX9Nqg
1Pxjth/RE75702Ib34EOFAf+RCJk5Cj2u/01RvzEO0oJgJp3vMRC1Wxixa68rZcvD8mLWbZ4G+g4
HhFL/ksBZ83Cztb4Na3ZrLN5MLKstKvHtlWAGPM06bRM8iRt+ml3CDG6jsVkvy2z4zbj3YCXzt3d
Vqx69RLWmmtEES6kKGY9O3WGO1qORA6lPgFADM/WVURitbOW/47+Vs/2K6MqlhZx9ipDcUZ/ftgK
+4N656zjGb6eqbKto2w14jwaHdcMjCp/MecuHLhjzRXKo38mPx1/dIr0ADCCBLwwggOkoAMCAQIC
ASkwDQYJKoZIhvcNAQEFBQAwVDELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1JVCBMaW5jb2xuIExh
Ym9yYXRvcnkxDDAKBgNVBAsTA1BLSTEWMBQGA1UEAxMNTUlUTEwgUm9vdCBDQTAeFw0xMzEyMTcw
MDAwMDBaFw0yMDEyMzEyMzU5NTlaMFExCzAJBgNVBAYTAlVTMR8wHQYDVQQKExZNSVQgTGluY29s
biBMYWJvcmF0b3J5MQwwCgYDVQQLEwNQS0kxEzARBgNVBAMTCk1JVExMIENBLTMwggEiMA0GCSqG
SIb3DQEBAQUAA4IBDwAwggEKAoIBAQDaMFJ1bXy25bW03EbqHwHSSpyQVlAAC2gcKS9SlQRfqMW8
F3yZAjncbIthG4CjgdYml7v+LMVc59IkOzpQzmi+8I59eDZsmANiUEL0kNwsEUifSemk671G+mNZ
KLG0LnpyvAnlSzlA923G0p16TksleXagrDfDyWKFSLF49vFZp3WbtkwopqC+b3NPJs/oW6YpHF5g
mNKkHb5wBiOgYYRtJUfLHy7MebrECgEwfFrxvL7IPPwnOTqw/2KKWA/eJdIagICaHIHO+VBDlA01
Y/4Saj2PP+6QqFhUH9XB3G2iq48CqfiJ8MAhoz121vTlzLWBcAVI/dn+JSTHIFllQ5F/AgMBAAGj
ggGaMIIBljASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBTXYGYOe0mNdUwN/c9G3sjHEofK
vzAfBgNVHSMEGDAWgBRnqnrP9AqmuXK1iqDSnfIQw0PtKTAOBgNVHQ8BAf8EBAMCAYYwZgYIKwYB
BQUHAQEEWjBYMC0GCCsGAQUFBzAChiFodHRwOi8vY3JsLmxsLm1pdC5lZHUvZ2V0dG8/TExSQ0Ew
JwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLmxsLm1pdC5lZHUvb2NzcDAzBgNVHR8ELDAqMCigJqAk
hiJodHRwOi8vY3JsLmxsLm1pdC5lZHUvZ2V0Y3JsP0xMUkNBMIGSBgNVHSAEgYowgYcwDQYLKoZI
hvcSAgEDAQYwDQYLKoZIhvcSAgEDAQgwDQYLKoZIhvcSAgEDAQcwDQYLKoZIhvcSAgEDAQkwDQYL
KoZIhvcSAgEDAQowDQYLKoZIhvcSAgEDAQswDQYLKoZIhvcSAgEDAQ4wDQYLKoZIhvcSAgEDAQ8w
DQYLKoZIhvcSAgEDARAwDQYJKoZIhvcNAQEFBQADggEBACx/0cGfvapTtROCTFquMBzuLKeFwMSB
bB7Ngq139IsZJDQOG3MhX8tMLGpQuM534f4dOowlcHz6cefOHKpDjdGycZk4VPlF/M+H3h1v9kne
qXbjgPCUkjvJcEDYORlwQSA5YL1sdysSXNTo2eKBqFJbmh1UmuGYf9eFABwxLvsTkfrbLLErVY8+
BwGKkZWe7XFIdtOId7sOp9ZDa1UwtR/bddiEi5r3iQmxB3iNKHvU1UPR7sXiycCipAwj3wzMNh4s
6SOXMpGzvuv9oyw8ArHqcxo69EvsLLQ+OnnWLaoWRsaZfyh+eHaR6uNNO9En+DbavUxXxFHU+S2M
yw06w98wggUtMIIEFaADAgECAgoadMQgAAAAAK0DMA0GCSqGSIb3DQEBCwUAMFExCzAJBgNVBAYT
AlVTMR8wHQYDVQQKExZNSVQgTGluY29sbiBMYWJvcmF0b3J5MQwwCgYDVQQLEwNQS0kxEzARBgNV
BAMTCk1JVExMIENBLTMwHhcNMTcwMzAxMTgyNTA2WhcNMjAxMjMxMjM1OTU5WjBsMQswCQYDVQQG
EwJVUzEfMB0GA1UEChMWTUlUIExpbmNvbG4gTGFib3JhdG9yeTEPMA0GA1UECxMGUGVvcGxlMSsw
KQYDVQQDEyJCbHVtZW50aGFsLlVyaS41MDAxMDU4NCAoTW9iaWxpdHkpMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEAg+8bBB+jySfGyqx/fL9a596qTeq9fGfYXI2yJEZqLzJazzV1u6oL
ToMnJQ6phCIkQGplPsM+9PpzIcw5nN8GahHPU6FXXT3BSr6/bny4hftGu05y/n/DWWlPkos6PhSN
AB8WG3L+6a3mHcp9yYumPkdtM20+08oiU9S6OhFr6BoFFoeFjKEcFhvvovm9GcRzQ3g1cXHore5p
6umBCLGxZi0cGhBI/7ZyJmJUUo50bAPKdpURqYSsgU7p6GxCgpIcZBUlTxCSliPO/0TqiBMZ857M
F4OcehpG7LuxufD0p+g02uX7Z0aIfYnGHlkm3Y7NgvF6lW2WxCPklqKakb2fuwIDAQABo4IB6jCC
AeYwHQYDVR0OBBYEFPbiFDP71vJBmRLhxtKU/CWESr+tMA4GA1UdDwEB/wQEAwIGwDAfBgNVHSME
GDAWgBTXYGYOe0mNdUwN/c9G3sjHEofKvzAzBgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLmxs
Lm1pdC5lZHUvZ2V0Y3JsL0xMQ0EzMGYGCCsGAQUFBwEBBFowWDAtBggrBgEFBQcwAoYhaHR0cDov
L2NybC5sbC5taXQuZWR1L2dldHRvL0xMQ0EzMCcGCCsGAQUFBzABhhtodHRwOi8vb2NzcC5sbC5t
aXQuZWR1L29jc3AwPQYJKwYBBAGCNxUHBDAwLgYmKwYBBAGCNxUIg4PlHYfsp2aGrYcVg+rwRYW2
oR8dhYHgQIbXxk0CAWQCAQkwLAYDVR0lAQH/BCIwIAYIKwYBBQUHAwQGCisGAQQBgjcKAwwGCCsG
AQUFBwMCMBgGA1UdIAQRMA8wDQYLKoZIhvcSAgEDAQgwQQYDVR0RBDowOIEOdXJpQGxsLm1pdC5l
ZHWgJgYKKwYBBAGCNxQCA6AYDBZVUjIwOTgwQG1pdGxsLmFkLmxvY2FsMC0GCSsGAQQBgjcUAgQg
Hh4ATABMAE0AbwBiAGkAbABlAFMAaQBnAEEAdQB0AGgwDQYJKoZIhvcNAQELBQADggEBADbiZo1D
kfqhBA4LYklB+i49k6dh7L+nDEg3WdeZ/CRZAon9G3hPsUWd5YIsufRpoYUVJABcVos87kXZmkF1
RjH8vLNFOEV8ZVcNxbWC5DiA6dTswIEhXMSHFuyp3tERvu2z6+f9FC4jvZttYyLyirBJC4KwP/AO
Lm42Gn4lLeNrY4Ex8nq2Ah3xjB+QqvpxD2k1aaoR0fWaDxv2ZrdaFR43x2MTkiee+wR1diZ7GA7G
/HyJg9MUukKq23qm6Ys0VJQcJsKU1Q2/TLL99FRRa18ourBvFwJzcllLhTcqnvbawWt6cYEvGIJ9
Dszxz7LQECXI0KrPpM7x32SulMJjt1YxggLJMIICxQIBATBfMFExCzAJBgNVBAYTAlVTMR8wHQYD
VQQKExZNSVQgTGluY29sbiBMYWJvcmF0b3J5MQwwCgYDVQQLEwNQS0kxEzARBgNVBAMTCk1JVExM
IENBLTMCChp0xCAAAAAArQMwCQYFKw4DAhoFAKCCAT8wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEH
ATAcBgkqhkiG9w0BCQUxDxcNMTcwNTE4MjEwMTAwWjAjBgkqhkiG9w0BCQQxFgQUYtsKgimEy8Jl
HkcCr0IFKw7uMA0wbgYJKwYBBAGCNxAEMWEwXzBRMQswCQYDVQQGEwJVUzEfMB0GA1UEChMWTUlU
IExpbmNvbG4gTGFib3JhdG9yeTEMMAoGA1UECxMDUEtJMRMwEQYDVQQDEwpNSVRMTCBDQS0zAgoa
dMQgAAAAAK0DMHAGCyqGSIb3DQEJEAILMWGgXzBRMQswCQYDVQQGEwJVUzEfMB0GA1UEChMWTUlU
IExpbmNvbG4gTGFib3JhdG9yeTEMMAoGA1UECxMDUEtJMRMwEQYDVQQDEwpNSVRMTCBDQS0zAgoa
dMQgAAAAAK0DMA0GCSqGSIb3DQEBAQUABIIBAB2kwrXMmUKJY57OiyUj4tb6JWa1DyWTGT+qSCjG
zmNOFt72HWlFqjTmPYZOkdKVrpkKlindyzfSrK6RHP5C8NE1FneiU89fsLr81fGGfnn/ki1KyOMw
5TeWKsGeQnNeWxmaKzIjKWtrnCUYSWhBsATivdBvIVY9ahIIYf0RpF7+JSwLr+wEi5yZKbleg063
RgTTGffWsKSrBFp7YIjucZ7o/+XAG+KtTPywFCUgz3tMa1OjOtQXxI3koIiVcYNv9N7K1EMjIP7P
vqCbTlq5RlLIc0Si6+Cmp5vfCTPW7wjNbqWirdbmtber2T33WnpXjNjCzuPEOuOjH7qqlq0y/YQA
AAAAAAA=

--Apple-Mail-2D23B870-777E-4452-9D5E-0D29511845E5--


From nobody Thu May 18 14:23:50 2017
Return-Path: <mglt.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 7482D12E3AE; Thu, 18 May 2017 14:23:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level: 
X-Spam-Status: No, score=-1.698 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_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y8fhe8RAN8gH; Thu, 18 May 2017 14:23:38 -0700 (PDT)
Received: from mail-wr0-x236.google.com (mail-wr0-x236.google.com [IPv6:2a00:1450:400c:c0c::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 6931F129AAA; Thu, 18 May 2017 14:17:21 -0700 (PDT)
Received: by mail-wr0-x236.google.com with SMTP id l9so4114961wre.1; Thu, 18 May 2017 14:17:21 -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=7OqtbsefojpFyTwgSkQ90lIBPG28RGomIDhvjYLmEoU=; b=aummM0CiR+Bzp/xGLnKfXNGP7BeCD05D8nFVVpTcG5DrpXlsC2VmEdwYKJzZXJpdds 22F3RdSSM8GheSj1ZE0tY6D1iok8Jnu7jRa9YpEQMTdOEL3IuUs0550X2TkHnk8V0Uif q1GHYAXGPYycFEoWZEH7lqzQ3cusffL/vOoN9G8+txFZXQ2sCWpi5+mQ6aH44gFYD5RR 3s7Lubk4Bx9GCsjwzl1IeGifpSw6u3GjndyGk5WTfhJ4tt2za2Jky8JTJjKLMJQ8ERGf mwB/RT6CL6DDMuL3b+0rqBnGQTX2TDU+9frUMhwCiTFKBkjIVItBiiW9QVKNCoCPKWzO WcKA==
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=7OqtbsefojpFyTwgSkQ90lIBPG28RGomIDhvjYLmEoU=; b=bUm0O9C7kvBhF3UQc67aBYvBXwby+sJ3c/mVI+jUWmg0SV/fPMQ/3Iwdj95FssFA84 QcZWcx1/UnafAk7Ys6rBVssJKYo5YFSr6tqgk9osh5ED/PoCnrxl4cRqkXcEPHIf7vpt BU+0JliYc61R0kMNaa5Gf1zFHTLYEVT0WwWDHr7WH3owKyADe8Iqu6wxjKIb4IltindW mEak8Hl/DyLWHjhelNZX2RIL4b8864WnC2UDwveiHASSeOfEZ7AiKPb/k/AyIKMEWJfm kThfaWJQrpRjHHYgnqBCDyYwntc+beKLG6UG9ju4mLj2AmE5lbKdPZz6KJ9QYb8ou6h7 5W/g==
X-Gm-Message-State: AODbwcAcJ5zzbVG5Lia0Wa+RTvFq4sYWCHto3nrhPlkE3Sg2dp66M1Ox MFEyjpZ0PVpjlyR+7Y31acBAcchwaA==
X-Received: by 10.46.78.9 with SMTP id c9mr1511334ljb.38.1495142239809; Thu, 18 May 2017 14:17:19 -0700 (PDT)
MIME-Version: 1.0
Sender: mglt.ietf@gmail.com
Received: by 10.46.0.14 with HTTP; Thu, 18 May 2017 14:17:19 -0700 (PDT)
In-Reply-To: <7E11398B-EAEF-4E06-BC6A-6797BA2197AE@ll.mit.edu>
References: <149391606578.6842.3727373203321848879.idtracker@ietfa.amsl.com> <4373f972-bf9b-4dbe-1b59-7f51846831f3@a-oben.org> <2DD56D786E600F45AC6BDE7DA4E8A8C118BDB69D@eusaamb107.ericsson.se> <6191522F-FB75-4B74-B7DE-200FEDB3F021@mobileiron.com> <7E11398B-EAEF-4E06-BC6A-6797BA2197AE@ll.mit.edu>
From: Daniel Migault <daniel.migault@ericsson.com>
Date: Thu, 18 May 2017 17:17:19 -0400
X-Google-Sender-Auth: QZPTbJFjfqJzChplbvLjW3HKuxA
Message-ID: <CADZyTkkncvCjpw85AUSwpHON-KLmbJsyYb-hw-EOEV8i3TXRYg@mail.gmail.com>
Subject: Re: [TLS] Last Call: <draft-ietf-tls-ecdhe-psk-aead-03.txt> (ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transport Layer Security (TLS)) to Proposed Standard
To: "Blumenthal, Uri - 0553 - MITLL" <uri@ll.mit.edu>
Cc: Timothy Jackson <tjackson@mobileiron.com>, "ietf@ietf.org" <ietf@ietf.org>, "tls@ietf.org" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="f403045ec30617b6e9054fd2ee7a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sqLd0pgnfREW3yRNXlNa0y8VHsY>
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, 18 May 2017 21:23:41 -0000

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

Hi,

Thanks Tim and Uri for the comment. At least wikipedia considers them as
equivalent. I am fine either way, but leave it  as pfs unless there is a
consensus to change it to forward secrecy. If having fs seems important to
you please let us know asap!

Yours,
Daniel

On Thu, May 18, 2017 at 5:01 PM, Blumenthal, Uri - 0553 - MITLL <
uri@ll.mit.edu> wrote:

> It is a mathematical cryptographic term, and as such is incontrovertible.
>
> I say leave it in.
>
> Regards,
> Uri
>
> Sent from my iPhone
>
> > On May 18, 2017, at 16:58, Timothy Jackson <tjackson@mobileiron.com>
> wrote:
> >
> > One small nit.
> >
> >> ECDHE provides perfect forward secrecy
> > I thought we had decided to change =E2=80=9Cperfect forward secrecy=E2=
=80=9D to just
> =E2=80=9Cforward secrecy=E2=80=9D since =E2=80=9Cperfect=E2=80=9D is such=
 a difficult standard to reach?
> >
> > Tim
> > =E2=80=94
> > Tim Jackson | Product Security Architect | MobileIron, Inc.
> >
> > On 5/18/17, 10:45 AM, "TLS on behalf of Daniel Migault" <
> tls-bounces@ietf.org on behalf of daniel.migault@ericsson.com> wrote:
> >
> >    Hi Simon,
> >
> >    Thank you for the review. I believe we have addressed your comments
> in our version 04. Please see my comments inline.
> >
> >    Yours,
> >    Daniel
> >
> >    -----Original Message-----
> >    From: TLS [mailto:tls-bounces@ietf.org] On Behalf Of Simon
> Friedberger
> >    Sent: Thursday, May 04, 2017 5:59 PM
> >    To: ietf@ietf.org
> >    Cc: tls@ietf.org
> >    Subject: Re: [TLS] Last Call: <draft-ietf-tls-ecdhe-psk-aead-03.txt>
> (ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transport Layer
> Security (TLS)) to Proposed Standard
> >
> >    Nits:
> >
> >        RFC 4279 reference is missing.
> >    MGLT: It seems the reference is mentioned in the current version in
> the Normative reference as well  as in the introduction at line 127,  in
> section 3 line 143. In case you meant another reference, please let us kn=
ow.
> >
> >
> >
> >        "TLS 1.3 and above version, " should probably be "TLS 1.3 and
> above" or "TLS 1.3 and higher versions"
> >    MGLT: Changed to "TLS 1.3 and higher versions"
> >
> >>    On 04/05/17 18:41, The IESG wrote:
> >> The IESG has received a request from the Transport Layer Security WG
> >> (tls) to consider the following document:
> >> - 'ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transport Laye=
r
> >>   Security (TLS)'
> >>  <draft-ietf-tls-ecdhe-psk-aead-03.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-05-18. 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 defines several new cipher suites for the Transport
> >>   Layer Security (TLS) protocol.  The cipher suites are all based on
> >>   the Ephemeral Elliptic Curve Diffie-Hellman with Pre-Shared Key
> >>   (ECDHE_PSK) key exchange together with the Authenticated Encryption
> >>   with Associated Data (AEAD) algorithms AES-GCM and AES-CCM.  PSK
> >>   provides light and efficient authentication, ECDHE provides perfect
> >>   forward secrecy, and AES-GCM and AES-CCM provides encryption and
> >>   integrity protection.
> >>
> >>
> >>
> >>
> >> The file can be obtained via
> >> https://datatracker.ietf.org/doc/draft-ietf-tls-ecdhe-psk-aead/
> >>
> >> IESG discussion can be tracked via
> >> https://datatracker.ietf.org/doc/draft-ietf-tls-ecdhe-psk-aead/ballot/
> >>
> >>
> >> No IPR declarations have been submitted directly on this I-D.
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> TLS mailing list
> >> TLS@ietf.org
> >> https://www.ietf.org/mailman/listinfo/tls
> >
> >    _______________________________________________
> >    TLS mailing list
> >    TLS@ietf.org
> >    https://www.ietf.org/mailman/listinfo/tls
> >
> >    _______________________________________________
> >    TLS mailing list
> >    TLS@ietf.org
> >    https://www.ietf.org/mailman/listinfo/tls
> >
> >
> > _______________________________________________
> > TLS mailing list
> > TLS@ietf.org
> > https://www.ietf.org/mailman/listinfo/tls
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>
>

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

<div dir=3D"ltr"><div><div>Hi, <br><br>Thanks Tim and Uri for the comment. =
At least wikipedia considers them as equivalent. I am fine either way, but =
leave it=C2=A0 as pfs unless there is a consensus to change it to forward s=
ecrecy. If having fs seems important to you please let us know asap!<br><br=
>Yours, <br></div></div>Daniel <br></div><div class=3D"gmail_extra"><br><di=
v class=3D"gmail_quote">On Thu, May 18, 2017 at 5:01 PM, Blumenthal, Uri - =
0553 - MITLL <span dir=3D"ltr">&lt;<a href=3D"mailto:uri@ll.mit.edu" target=
=3D"_blank">uri@ll.mit.edu</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">It is a mathematical cryptographic term, and as such is incontrover=
tible.<br>
<br>
I say leave it in.<br>
<br>
Regards,<br>
Uri<br>
<br>
Sent from my iPhone<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; On May 18, 2017, at 16:58, Timothy Jackson &lt;<a href=3D"mailto:tjack=
son@mobileiron.com">tjackson@mobileiron.com</a>&gt; wrote:<br>
&gt;<br>
&gt; One small nit.<br>
&gt;<br>
&gt;&gt; ECDHE provides perfect forward secrecy<br>
&gt; I thought we had decided to change =E2=80=9Cperfect forward secrecy=E2=
=80=9D to just =E2=80=9Cforward secrecy=E2=80=9D since =E2=80=9Cperfect=E2=
=80=9D is such a difficult standard to reach?<br>
&gt;<br>
&gt; Tim<br>
&gt; =E2=80=94<br>
&gt; Tim Jackson | Product Security Architect | MobileIron, Inc.<br>
&gt;<br>
&gt; On 5/18/17, 10:45 AM, &quot;TLS on behalf of Daniel Migault&quot; &lt;=
<a href=3D"mailto:tls-bounces@ietf.org">tls-bounces@ietf.org</a> on behalf =
of <a href=3D"mailto:daniel.migault@ericsson.com">daniel.migault@ericsson.c=
om</a>&gt; wrote:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Hi Simon,<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Thank you for the review. I believe we have addressed you=
r comments in our version 04. Please see my comments inline.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Yours,<br>
&gt;=C2=A0 =C2=A0 Daniel<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 -----Original Message-----<br>
&gt;=C2=A0 =C2=A0 From: TLS [mailto:<a href=3D"mailto:tls-bounces@ietf.org"=
>tls-bounces@ietf.org</a>] On Behalf Of Simon Friedberger<br>
&gt;=C2=A0 =C2=A0 Sent: Thursday, May 04, 2017 5:59 PM<br>
&gt;=C2=A0 =C2=A0 To: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br=
>
&gt;=C2=A0 =C2=A0 Cc: <a href=3D"mailto:tls@ietf.org">tls@ietf.org</a><br>
&gt;=C2=A0 =C2=A0 Subject: Re: [TLS] Last Call: &lt;draft-ietf-tls-ecdhe-ps=
k-<wbr>aead-03.txt&gt; (ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites fo=
r Transport Layer Security (TLS)) to Proposed Standard<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Nits:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 RFC 4279 reference is missing.<br>
&gt;=C2=A0 =C2=A0 MGLT: It seems the reference is mentioned in the current =
version in the Normative reference as well=C2=A0 as in the introduction at =
line 127,=C2=A0 in section 3 line 143. In case you meant another reference,=
 please let us know.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 &quot;TLS 1.3 and above version, &quot; sho=
uld probably be &quot;TLS 1.3 and above&quot; or &quot;TLS 1.3 and higher v=
ersions&quot;<br>
&gt;=C2=A0 =C2=A0 MGLT: Changed to &quot;TLS 1.3 and higher versions&quot;<=
br>
&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 On 04/05/17 18:41, The IESG wrote:<br>
&gt;&gt; The IESG has received a request from the Transport Layer Security =
WG<br>
&gt;&gt; (tls) to consider the following document:<br>
&gt;&gt; - &#39;ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transp=
ort Layer<br>
&gt;&gt;=C2=A0 =C2=A0Security (TLS)&#39;<br>
&gt;&gt;=C2=A0 &lt;draft-ietf-tls-ecdhe-psk-<wbr>aead-03.txt&gt; as Propose=
d Standard<br>
&gt;&gt;<br>
&gt;&gt; The IESG plans to make a decision in the next few weeks, and solic=
its<br>
&gt;&gt; final comments on this action. Please send substantive comments to=
 the<br>
&gt;&gt; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists b=
y 2017-05-18. Exceptionally, comments may<br>
&gt;&gt; be sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> inst=
ead. In either case, please retain the<br>
&gt;&gt; beginning of the Subject line to allow automated sorting.<br>
&gt;&gt;<br>
&gt;&gt; Abstract<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0This document defines several new cipher suites for th=
e Transport<br>
&gt;&gt;=C2=A0 =C2=A0Layer Security (TLS) protocol.=C2=A0 The cipher suites=
 are all based on<br>
&gt;&gt;=C2=A0 =C2=A0the Ephemeral Elliptic Curve Diffie-Hellman with Pre-S=
hared Key<br>
&gt;&gt;=C2=A0 =C2=A0(ECDHE_PSK) key exchange together with the Authenticat=
ed Encryption<br>
&gt;&gt;=C2=A0 =C2=A0with Associated Data (AEAD) algorithms AES-GCM and AES=
-CCM.=C2=A0 PSK<br>
&gt;&gt;=C2=A0 =C2=A0provides light and efficient authentication, ECDHE pro=
vides perfect<br>
&gt;&gt;=C2=A0 =C2=A0forward secrecy, and AES-GCM and AES-CCM provides encr=
yption and<br>
&gt;&gt;=C2=A0 =C2=A0integrity protection.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; The file can be obtained via<br>
&gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-tls-ecdhe-p=
sk-aead/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org=
/<wbr>doc/draft-ietf-tls-ecdhe-psk-<wbr>aead/</a><br>
&gt;&gt;<br>
&gt;&gt; IESG discussion can be tracked via<br>
&gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-tls-ecdhe-p=
sk-aead/ballot/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.i=
etf.org/<wbr>doc/draft-ietf-tls-ecdhe-psk-<wbr>aead/ballot/</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; No IPR declarations have been submitted directly on this I-D.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; ______________________________<wbr>_________________<br>
&gt;&gt; TLS mailing list<br>
&gt;&gt; <a href=3D"mailto:TLS@ietf.org">TLS@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/tls" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/tls</a>=
<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 ______________________________<wbr>_________________<br>
&gt;=C2=A0 =C2=A0 TLS mailing list<br>
&gt;=C2=A0 =C2=A0 <a href=3D"mailto:TLS@ietf.org">TLS@ietf.org</a><br>
&gt;=C2=A0 =C2=A0 <a href=3D"https://www.ietf.org/mailman/listinfo/tls" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinf=
o/tls</a><br>
&gt;<br>
&gt;=C2=A0 =C2=A0 ______________________________<wbr>_________________<br>
&gt;=C2=A0 =C2=A0 TLS mailing list<br>
&gt;=C2=A0 =C2=A0 <a href=3D"mailto:TLS@ietf.org">TLS@ietf.org</a><br>
&gt;=C2=A0 =C2=A0 <a href=3D"https://www.ietf.org/mailman/listinfo/tls" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinf=
o/tls</a><br>
&gt;<br>
&gt;<br>
&gt; ______________________________<wbr>_________________<br>
&gt; TLS mailing list<br>
&gt; <a href=3D"mailto:TLS@ietf.org">TLS@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/tls" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/tls</a><br>
</div></div><br>______________________________<wbr>_________________<br>
TLS mailing list<br>
<a href=3D"mailto:TLS@ietf.org">TLS@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tls" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/tls</a><br>
<br></blockquote></div><br></div>

--f403045ec30617b6e9054fd2ee7a--


From nobody Thu May 18 14:29:15 2017
Return-Path: <prvs=6311b0b214=uri@ll.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 8CD4512778E; Thu, 18 May 2017 14:29:14 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 sbktBnJ1BXcD; Thu, 18 May 2017 14:29:12 -0700 (PDT)
Received: from llmx2.ll.mit.edu (LLMX2.LL.MIT.EDU [129.55.12.48]) by ietfa.amsl.com (Postfix) with ESMTP id 74219129BE6; Thu, 18 May 2017 14:22:17 -0700 (PDT)
Received: from LLE2K10-HUB01.mitll.ad.local (LLE2K10-HUB01.mitll.ad.local) by llmx2.ll.mit.edu (unknown) with ESMTP id v4ILMFgQ009997; Thu, 18 May 2017 17:22:15 -0400
From: "Blumenthal, Uri - 0553 - MITLL" <uri@ll.mit.edu>
To: Daniel Migault <daniel.migault@ericsson.com>
CC: Timothy Jackson <tjackson@mobileiron.com>, "ietf@ietf.org" <ietf@ietf.org>, "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] Last Call: <draft-ietf-tls-ecdhe-psk-aead-03.txt> (ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transport Layer Security (TLS)) to Proposed Standard
Thread-Topic: [TLS] Last Call: <draft-ietf-tls-ecdhe-psk-aead-03.txt> (ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transport Layer Security (TLS)) to Proposed Standard
Thread-Index: AQHSxPVWpHIsuShcKEe7pKr8MzTDmKHk/FmAgBW56QCAADQWAIAAAn8AgAAEj4CAAAFeAA==
Date: Thu, 18 May 2017 21:22:14 +0000
Message-ID: <B8D07E38-0FD0-44ED-9FA9-E166B56A3A5B@ll.mit.edu>
References: <149391606578.6842.3727373203321848879.idtracker@ietfa.amsl.com> <4373f972-bf9b-4dbe-1b59-7f51846831f3@a-oben.org> <2DD56D786E600F45AC6BDE7DA4E8A8C118BDB69D@eusaamb107.ericsson.se> <6191522F-FB75-4B74-B7DE-200FEDB3F021@mobileiron.com> <7E11398B-EAEF-4E06-BC6A-6797BA2197AE@ll.mit.edu> <CADZyTkkncvCjpw85AUSwpHON-KLmbJsyYb-hw-EOEV8i3TXRYg@mail.gmail.com>
In-Reply-To: <CADZyTkkncvCjpw85AUSwpHON-KLmbJsyYb-hw-EOEV8i3TXRYg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Content-Type: multipart/signed; boundary="Apple-Mail-9DD953CA-CD22-4DA9-A409-550794E10AC7"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-05-18_05:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1705180144
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/F9A2dhqYrXvLw12APi0Arvwgx1M>
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, 18 May 2017 21:29:14 -0000

--Apple-Mail-9DD953CA-CD22-4DA9-A409-550794E10AC7
Content-Type: multipart/alternative;
	boundary=Apple-Mail-E1A62FE4-18C2-428F-BCCF-38DD24A8094C
Content-Transfer-Encoding: 7bit


--Apple-Mail-E1A62FE4-18C2-428F-BCCF-38DD24A8094C
Content-Type: text/plain;
	charset=windows-1251
Content-Transfer-Encoding: base64

SW5zdGVhZCBvZiBvdXIgaW4gYWRkaXRpb24gdG8gdGhlIFdpa2ksIGNoZWNrIHNjaG9sYXJseSBy
ZWZlcmVuY2VzLiBFLmcuLCBJbnRyb2R1Y3Rpb24gdG8gTW9kZXJuIENyeXB0b2dyYXBoeSwgSGFu
ZGJvb2sgb2YgQXBwbGllZCBDcnlwdG9ncmFwaHksIGV0Yy4NCg0KUmVnYXJkcywNClVyaQ0KDQpT
ZW50IGZyb20gbXkgaVBob25lDQoNCj4gT24gTWF5IDE4LCAyMDE3LCBhdCAxNzoxOCwgRGFuaWVs
IE1pZ2F1bHQgPGRhbmllbC5taWdhdWx0QGVyaWNzc29uLmNvbT4gd3JvdGU6DQo+IA0KPiBIaSwg
DQo+IA0KPiBUaGFua3MgVGltIGFuZCBVcmkgZm9yIHRoZSBjb21tZW50LiBBdCBsZWFzdCB3aWtp
cGVkaWEgY29uc2lkZXJzIHRoZW0gYXMgZXF1aXZhbGVudC4gSSBhbSBmaW5lIGVpdGhlciB3YXks
IGJ1dCBsZWF2ZSBpdCAgYXMgcGZzIHVubGVzcyB0aGVyZSBpcyBhIGNvbnNlbnN1cyB0byBjaGFu
Z2UgaXQgdG8gZm9yd2FyZCBzZWNyZWN5LiBJZiBoYXZpbmcgZnMgc2VlbXMgaW1wb3J0YW50IHRv
IHlvdSBwbGVhc2UgbGV0IHVzIGtub3cgYXNhcCENCj4gDQo+IFlvdXJzLCANCj4gRGFuaWVsIA0K
PiANCj4+IE9uIFRodSwgTWF5IDE4LCAyMDE3IGF0IDU6MDEgUE0sIEJsdW1lbnRoYWwsIFVyaSAt
IDA1NTMgLSBNSVRMTCA8dXJpQGxsLm1pdC5lZHU+IHdyb3RlOg0KPj4gSXQgaXMgYSBtYXRoZW1h
dGljYWwgY3J5cHRvZ3JhcGhpYyB0ZXJtLCBhbmQgYXMgc3VjaCBpcyBpbmNvbnRyb3ZlcnRpYmxl
Lg0KPj4gDQo+PiBJIHNheSBsZWF2ZSBpdCBpbi4NCj4+IA0KPj4gUmVnYXJkcywNCj4+IFVyaQ0K
Pj4gDQo+PiBTZW50IGZyb20gbXkgaVBob25lDQo+PiANCj4+ID4gT24gTWF5IDE4LCAyMDE3LCBh
dCAxNjo1OCwgVGltb3RoeSBKYWNrc29uIDx0amFja3NvbkBtb2JpbGVpcm9uLmNvbT4gd3JvdGU6
DQo+PiA+DQo+PiA+IE9uZSBzbWFsbCBuaXQuDQo+PiA+DQo+PiA+PiBFQ0RIRSBwcm92aWRlcyBw
ZXJmZWN0IGZvcndhcmQgc2VjcmVjeQ0KPj4gPiBJIHRob3VnaHQgd2UgaGFkIGRlY2lkZWQgdG8g
Y2hhbmdlIJNwZXJmZWN0IGZvcndhcmQgc2VjcmVjeZQgdG8ganVzdCCTZm9yd2FyZCBzZWNyZWN5
lCBzaW5jZSCTcGVyZmVjdJQgaXMgc3VjaCBhIGRpZmZpY3VsdCBzdGFuZGFyZCB0byByZWFjaD8N
Cj4+ID4NCj4+ID4gVGltDQo+PiA+IJcNCj4+ID4gVGltIEphY2tzb24gfCBQcm9kdWN0IFNlY3Vy
aXR5IEFyY2hpdGVjdCB8IE1vYmlsZUlyb24sIEluYy4NCj4+ID4NCj4+ID4gT24gNS8xOC8xNywg
MTA6NDUgQU0sICJUTFMgb24gYmVoYWxmIG9mIERhbmllbCBNaWdhdWx0IiA8dGxzLWJvdW5jZXNA
aWV0Zi5vcmcgb24gYmVoYWxmIG9mIGRhbmllbC5taWdhdWx0QGVyaWNzc29uLmNvbT4gd3JvdGU6
DQo+PiA+DQo+PiA+ICAgIEhpIFNpbW9uLA0KPj4gPg0KPj4gPiAgICBUaGFuayB5b3UgZm9yIHRo
ZSByZXZpZXcuIEkgYmVsaWV2ZSB3ZSBoYXZlIGFkZHJlc3NlZCB5b3VyIGNvbW1lbnRzIGluIG91
ciB2ZXJzaW9uIDA0LiBQbGVhc2Ugc2VlIG15IGNvbW1lbnRzIGlubGluZS4NCj4+ID4NCj4+ID4g
ICAgWW91cnMsDQo+PiA+ICAgIERhbmllbA0KPj4gPg0KPj4gPiAgICAtLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KPj4gPiAgICBGcm9tOiBUTFMgW21haWx0bzp0bHMtYm91bmNlc0BpZXRmLm9y
Z10gT24gQmVoYWxmIE9mIFNpbW9uIEZyaWVkYmVyZ2VyDQo+PiA+ICAgIFNlbnQ6IFRodXJzZGF5
LCBNYXkgMDQsIDIwMTcgNTo1OSBQTQ0KPj4gPiAgICBUbzogaWV0ZkBpZXRmLm9yZw0KPj4gPiAg
ICBDYzogdGxzQGlldGYub3JnDQo+PiA+ICAgIFN1YmplY3Q6IFJlOiBbVExTXSBMYXN0IENhbGw6
IDxkcmFmdC1pZXRmLXRscy1lY2RoZS1wc2stYWVhZC0wMy50eHQ+IChFQ0RIRV9QU0sgd2l0aCBB
RVMtR0NNIGFuZCBBRVMtQ0NNIENpcGhlciBTdWl0ZXMgZm9yIFRyYW5zcG9ydCBMYXllciBTZWN1
cml0eSAoVExTKSkgdG8gUHJvcG9zZWQgU3RhbmRhcmQNCj4+ID4NCj4+ID4gICAgTml0czoNCj4+
ID4NCj4+ID4gICAgICAgIFJGQyA0Mjc5IHJlZmVyZW5jZSBpcyBtaXNzaW5nLg0KPj4gPiAgICBN
R0xUOiBJdCBzZWVtcyB0aGUgcmVmZXJlbmNlIGlzIG1lbnRpb25lZCBpbiB0aGUgY3VycmVudCB2
ZXJzaW9uIGluIHRoZSBOb3JtYXRpdmUgcmVmZXJlbmNlIGFzIHdlbGwgIGFzIGluIHRoZSBpbnRy
b2R1Y3Rpb24gYXQgbGluZSAxMjcsICBpbiBzZWN0aW9uIDMgbGluZSAxNDMuIEluIGNhc2UgeW91
IG1lYW50IGFub3RoZXIgcmVmZXJlbmNlLCBwbGVhc2UgbGV0IHVzIGtub3cuDQo+PiA+DQo+PiA+
DQo+PiA+DQo+PiA+ICAgICAgICAiVExTIDEuMyBhbmQgYWJvdmUgdmVyc2lvbiwgIiBzaG91bGQg
cHJvYmFibHkgYmUgIlRMUyAxLjMgYW5kIGFib3ZlIiBvciAiVExTIDEuMyBhbmQgaGlnaGVyIHZl
cnNpb25zIg0KPj4gPiAgICBNR0xUOiBDaGFuZ2VkIHRvICJUTFMgMS4zIGFuZCBoaWdoZXIgdmVy
c2lvbnMiDQo+PiA+DQo+PiA+PiAgICBPbiAwNC8wNS8xNyAxODo0MSwgVGhlIElFU0cgd3JvdGU6
DQo+PiA+PiBUaGUgSUVTRyBoYXMgcmVjZWl2ZWQgYSByZXF1ZXN0IGZyb20gdGhlIFRyYW5zcG9y
dCBMYXllciBTZWN1cml0eSBXRw0KPj4gPj4gKHRscykgdG8gY29uc2lkZXIgdGhlIGZvbGxvd2lu
ZyBkb2N1bWVudDoNCj4+ID4+IC0gJ0VDREhFX1BTSyB3aXRoIEFFUy1HQ00gYW5kIEFFUy1DQ00g
Q2lwaGVyIFN1aXRlcyBmb3IgVHJhbnNwb3J0IExheWVyDQo+PiA+PiAgIFNlY3VyaXR5IChUTFMp
Jw0KPj4gPj4gIDxkcmFmdC1pZXRmLXRscy1lY2RoZS1wc2stYWVhZC0wMy50eHQ+IGFzIFByb3Bv
c2VkIFN0YW5kYXJkDQo+PiA+Pg0KPj4gPj4gVGhlIElFU0cgcGxhbnMgdG8gbWFrZSBhIGRlY2lz
aW9uIGluIHRoZSBuZXh0IGZldyB3ZWVrcywgYW5kIHNvbGljaXRzDQo+PiA+PiBmaW5hbCBjb21t
ZW50cyBvbiB0aGlzIGFjdGlvbi4gUGxlYXNlIHNlbmQgc3Vic3RhbnRpdmUgY29tbWVudHMgdG8g
dGhlDQo+PiA+PiBpZXRmQGlldGYub3JnIG1haWxpbmcgbGlzdHMgYnkgMjAxNy0wNS0xOC4gRXhj
ZXB0aW9uYWxseSwgY29tbWVudHMgbWF5DQo+PiA+PiBiZSBzZW50IHRvIGllc2dAaWV0Zi5vcmcg
aW5zdGVhZC4gSW4gZWl0aGVyIGNhc2UsIHBsZWFzZSByZXRhaW4gdGhlDQo+PiA+PiBiZWdpbm5p
bmcgb2YgdGhlIFN1YmplY3QgbGluZSB0byBhbGxvdyBhdXRvbWF0ZWQgc29ydGluZy4NCj4+ID4+
DQo+PiA+PiBBYnN0cmFjdA0KPj4gPj4NCj4+ID4+DQo+PiA+PiAgIFRoaXMgZG9jdW1lbnQgZGVm
aW5lcyBzZXZlcmFsIG5ldyBjaXBoZXIgc3VpdGVzIGZvciB0aGUgVHJhbnNwb3J0DQo+PiA+PiAg
IExheWVyIFNlY3VyaXR5IChUTFMpIHByb3RvY29sLiAgVGhlIGNpcGhlciBzdWl0ZXMgYXJlIGFs
bCBiYXNlZCBvbg0KPj4gPj4gICB0aGUgRXBoZW1lcmFsIEVsbGlwdGljIEN1cnZlIERpZmZpZS1I
ZWxsbWFuIHdpdGggUHJlLVNoYXJlZCBLZXkNCj4+ID4+ICAgKEVDREhFX1BTSykga2V5IGV4Y2hh
bmdlIHRvZ2V0aGVyIHdpdGggdGhlIEF1dGhlbnRpY2F0ZWQgRW5jcnlwdGlvbg0KPj4gPj4gICB3
aXRoIEFzc29jaWF0ZWQgRGF0YSAoQUVBRCkgYWxnb3JpdGhtcyBBRVMtR0NNIGFuZCBBRVMtQ0NN
LiAgUFNLDQo+PiA+PiAgIHByb3ZpZGVzIGxpZ2h0IGFuZCBlZmZpY2llbnQgYXV0aGVudGljYXRp
b24sIEVDREhFIHByb3ZpZGVzIHBlcmZlY3QNCj4+ID4+ICAgZm9yd2FyZCBzZWNyZWN5LCBhbmQg
QUVTLUdDTSBhbmQgQUVTLUNDTSBwcm92aWRlcyBlbmNyeXB0aW9uIGFuZA0KPj4gPj4gICBpbnRl
Z3JpdHkgcHJvdGVjdGlvbi4NCj4+ID4+DQo+PiA+Pg0KPj4gPj4NCj4+ID4+DQo+PiA+PiBUaGUg
ZmlsZSBjYW4gYmUgb2J0YWluZWQgdmlhDQo+PiA+PiBodHRwczovL2RhdGF0cmFja2VyLmlldGYu
b3JnL2RvYy9kcmFmdC1pZXRmLXRscy1lY2RoZS1wc2stYWVhZC8NCj4+ID4+DQo+PiA+PiBJRVNH
IGRpc2N1c3Npb24gY2FuIGJlIHRyYWNrZWQgdmlhDQo+PiA+PiBodHRwczovL2RhdGF0cmFja2Vy
LmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLXRscy1lY2RoZS1wc2stYWVhZC9iYWxsb3QvDQo+PiA+
Pg0KPj4gPj4NCj4+ID4+IE5vIElQUiBkZWNsYXJhdGlvbnMgaGF2ZSBiZWVuIHN1Ym1pdHRlZCBk
aXJlY3RseSBvbiB0aGlzIEktRC4NCj4+ID4+DQo+PiA+Pg0KPj4gPj4NCj4+ID4+DQo+PiA+PiBf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4gPj4gVExT
IG1haWxpbmcgbGlzdA0KPj4gPj4gVExTQGlldGYub3JnDQo+PiA+PiBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Rscw0KPj4gPg0KPj4gPiAgICBfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4gPiAgICBUTFMgbWFpbGluZyBsaXN0
DQo+PiA+ICAgIFRMU0BpZXRmLm9yZw0KPj4gPiAgICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL3Rscw0KPj4gPg0KPj4gPiAgICBfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0KPj4gPiAgICBUTFMgbWFpbGluZyBsaXN0DQo+PiA+ICAg
IFRMU0BpZXRmLm9yZw0KPj4gPiAgICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL3Rscw0KPj4gPg0KPj4gPg0KPj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXw0KPj4gPiBUTFMgbWFpbGluZyBsaXN0DQo+PiA+IFRMU0BpZXRmLm9y
Zw0KPj4gPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Rscw0KPj4gDQo+
PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4gVExT
IG1haWxpbmcgbGlzdA0KPj4gVExTQGlldGYub3JnDQo+PiBodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL3Rscw0KPj4gDQo+IA0K
--Apple-Mail-E1A62FE4-18C2-428F-BCCF-38DD24A8094C
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iY29udGVudC10eXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPjwvaGVhZD48Ym9keSBkaXI9ImF1dG8iPjxkaXY+SW5zdGVh
ZCBvZiBvdXIgaW4gYWRkaXRpb24gdG8gdGhlIFdpa2ksIGNoZWNrIHNjaG9sYXJseSByZWZlcmVu
Y2VzLiBFLmcuLCBJbnRyb2R1Y3Rpb24gdG8gTW9kZXJuIENyeXB0b2dyYXBoeSwgSGFuZGJvb2sg
b2YgQXBwbGllZCBDcnlwdG9ncmFwaHksIGV0Yy48YnI+PGJyPlJlZ2FyZHMsPGRpdj5Vcmk8L2Rp
dj48ZGl2Pjxicj48L2Rpdj48ZGl2PlNlbnQgZnJvbSBteSBpUGhvbmU8L2Rpdj48L2Rpdj48ZGl2
Pjxicj5PbiBNYXkgMTgsIDIwMTcsIGF0IDE3OjE4LCBEYW5pZWwgTWlnYXVsdCAmbHQ7PGEgaHJl
Zj0ibWFpbHRvOmRhbmllbC5taWdhdWx0QGVyaWNzc29uLmNvbSI+ZGFuaWVsLm1pZ2F1bHRAZXJp
Y3Nzb24uY29tPC9hPiZndDsgd3JvdGU6PGJyPjxicj48L2Rpdj48YmxvY2txdW90ZSB0eXBlPSJj
aXRlIj48ZGl2PjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0idGV4dC9o
dG1sOyBjaGFyc2V0PXV0Zi04Ij48ZGl2IGRpcj0ibHRyIj48ZGl2PjxkaXY+SGksIDxicj48YnI+
VGhhbmtzIFRpbSBhbmQgVXJpIGZvciB0aGUgY29tbWVudC4gQXQgbGVhc3Qgd2lraXBlZGlhIGNv
bnNpZGVycyB0aGVtIGFzIGVxdWl2YWxlbnQuIEkgYW0gZmluZSBlaXRoZXIgd2F5LCBidXQgbGVh
dmUgaXQmbmJzcDsgYXMgcGZzIHVubGVzcyB0aGVyZSBpcyBhIGNvbnNlbnN1cyB0byBjaGFuZ2Ug
aXQgdG8gZm9yd2FyZCBzZWNyZWN5LiBJZiBoYXZpbmcgZnMgc2VlbXMgaW1wb3J0YW50IHRvIHlv
dSBwbGVhc2UgbGV0IHVzIGtub3cgYXNhcCE8YnI+PGJyPllvdXJzLCA8YnI+PC9kaXY+PC9kaXY+
RGFuaWVsIDxicj48L2Rpdj48ZGl2IGNsYXNzPSJnbWFpbF9leHRyYSI+PGJyPjxkaXYgY2xhc3M9
ImdtYWlsX3F1b3RlIj5PbiBUaHUsIE1heSAxOCwgMjAxNyBhdCA1OjAxIFBNLCBCbHVtZW50aGFs
LCBVcmkgLSAwNTUzIC0gTUlUTEwgPHNwYW4gZGlyPSJsdHIiPiZsdDs8YSBocmVmPSJtYWlsdG86
dXJpQGxsLm1pdC5lZHUiIHRhcmdldD0iX2JsYW5rIj51cmlAbGwubWl0LmVkdTwvYT4mZ3Q7PC9z
cGFuPiB3cm90ZTo8YnI+PGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0ibWFy
Z2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGluZy1sZWZ0OjFl
eCI+SXQgaXMgYSBtYXRoZW1hdGljYWwgY3J5cHRvZ3JhcGhpYyB0ZXJtLCBhbmQgYXMgc3VjaCBp
cyBpbmNvbnRyb3ZlcnRpYmxlLjxicj4NCjxicj4NCkkgc2F5IGxlYXZlIGl0IGluLjxicj4NCjxi
cj4NClJlZ2FyZHMsPGJyPg0KVXJpPGJyPg0KPGJyPg0KU2VudCBmcm9tIG15IGlQaG9uZTxicj4N
CjxkaXYgY2xhc3M9IkhPRW5aYiI+PGRpdiBjbGFzcz0iaDUiPjxicj4NCiZndDsgT24gTWF5IDE4
LCAyMDE3LCBhdCAxNjo1OCwgVGltb3RoeSBKYWNrc29uICZsdDs8YSBocmVmPSJtYWlsdG86dGph
Y2tzb25AbW9iaWxlaXJvbi5jb20iPnRqYWNrc29uQG1vYmlsZWlyb24uY29tPC9hPiZndDsgd3Jv
dGU6PGJyPg0KJmd0Ozxicj4NCiZndDsgT25lIHNtYWxsIG5pdC48YnI+DQomZ3Q7PGJyPg0KJmd0
OyZndDsgRUNESEUgcHJvdmlkZXMgcGVyZmVjdCBmb3J3YXJkIHNlY3JlY3k8YnI+DQomZ3Q7IEkg
dGhvdWdodCB3ZSBoYWQgZGVjaWRlZCB0byBjaGFuZ2Ug4oCccGVyZmVjdCBmb3J3YXJkIHNlY3Jl
Y3nigJ0gdG8ganVzdCDigJxmb3J3YXJkIHNlY3JlY3nigJ0gc2luY2Ug4oCccGVyZmVjdOKAnSBp
cyBzdWNoIGEgZGlmZmljdWx0IHN0YW5kYXJkIHRvIHJlYWNoPzxicj4NCiZndDs8YnI+DQomZ3Q7
IFRpbTxicj4NCiZndDsg4oCUPGJyPg0KJmd0OyBUaW0gSmFja3NvbiB8IFByb2R1Y3QgU2VjdXJp
dHkgQXJjaGl0ZWN0IHwgTW9iaWxlSXJvbiwgSW5jLjxicj4NCiZndDs8YnI+DQomZ3Q7IE9uIDUv
MTgvMTcsIDEwOjQ1IEFNLCAiVExTIG9uIGJlaGFsZiBvZiBEYW5pZWwgTWlnYXVsdCIgJmx0Ozxh
IGhyZWY9Im1haWx0bzp0bHMtYm91bmNlc0BpZXRmLm9yZyI+dGxzLWJvdW5jZXNAaWV0Zi5vcmc8
L2E+IG9uIGJlaGFsZiBvZiA8YSBocmVmPSJtYWlsdG86ZGFuaWVsLm1pZ2F1bHRAZXJpY3Nzb24u
Y29tIj5kYW5pZWwubWlnYXVsdEBlcmljc3Nvbi5jb208L2E+Jmd0OyB3cm90ZTo8YnI+DQomZ3Q7
PGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgSGkgU2ltb24sPGJyPg0KJmd0Ozxicj4NCiZndDsmbmJz
cDsgJm5ic3A7IFRoYW5rIHlvdSBmb3IgdGhlIHJldmlldy4gSSBiZWxpZXZlIHdlIGhhdmUgYWRk
cmVzc2VkIHlvdXIgY29tbWVudHMgaW4gb3VyIHZlcnNpb24gMDQuIFBsZWFzZSBzZWUgbXkgY29t
bWVudHMgaW5saW5lLjxicj4NCiZndDs8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyBZb3Vycyw8YnI+
DQomZ3Q7Jm5ic3A7ICZuYnNwOyBEYW5pZWw8YnI+DQomZ3Q7PGJyPg0KJmd0OyZuYnNwOyAmbmJz
cDsgLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyBGcm9t
OiBUTFMgW21haWx0bzo8YSBocmVmPSJtYWlsdG86dGxzLWJvdW5jZXNAaWV0Zi5vcmciPnRscy1i
b3VuY2VzQGlldGYub3JnPC9hPl0gT24gQmVoYWxmIE9mIFNpbW9uIEZyaWVkYmVyZ2VyPGJyPg0K
Jmd0OyZuYnNwOyAmbmJzcDsgU2VudDogVGh1cnNkYXksIE1heSAwNCwgMjAxNyA1OjU5IFBNPGJy
Pg0KJmd0OyZuYnNwOyAmbmJzcDsgVG86IDxhIGhyZWY9Im1haWx0bzppZXRmQGlldGYub3JnIj5p
ZXRmQGlldGYub3JnPC9hPjxicj4NCiZndDsmbmJzcDsgJm5ic3A7IENjOiA8YSBocmVmPSJtYWls
dG86dGxzQGlldGYub3JnIj50bHNAaWV0Zi5vcmc8L2E+PGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsg
U3ViamVjdDogUmU6IFtUTFNdIExhc3QgQ2FsbDogJmx0O2RyYWZ0LWlldGYtdGxzLWVjZGhlLXBz
ay08d2JyPmFlYWQtMDMudHh0Jmd0OyAoRUNESEVfUFNLIHdpdGggQUVTLUdDTSBhbmQgQUVTLUND
TSBDaXBoZXIgU3VpdGVzIGZvciBUcmFuc3BvcnQgTGF5ZXIgU2VjdXJpdHkgKFRMUykpIHRvIFBy
b3Bvc2VkIFN0YW5kYXJkPGJyPg0KJmd0Ozxicj4NCiZndDsmbmJzcDsgJm5ic3A7IE5pdHM6PGJy
Pg0KJmd0Ozxicj4NCiZndDsmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgUkZDIDQyNzkgcmVm
ZXJlbmNlIGlzIG1pc3NpbmcuPGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgTUdMVDogSXQgc2VlbXMg
dGhlIHJlZmVyZW5jZSBpcyBtZW50aW9uZWQgaW4gdGhlIGN1cnJlbnQgdmVyc2lvbiBpbiB0aGUg
Tm9ybWF0aXZlIHJlZmVyZW5jZSBhcyB3ZWxsJm5ic3A7IGFzIGluIHRoZSBpbnRyb2R1Y3Rpb24g
YXQgbGluZSAxMjcsJm5ic3A7IGluIHNlY3Rpb24gMyBsaW5lIDE0My4gSW4gY2FzZSB5b3UgbWVh
bnQgYW5vdGhlciByZWZlcmVuY2UsIHBsZWFzZSBsZXQgdXMga25vdy48YnI+DQomZ3Q7PGJyPg0K
Jmd0Ozxicj4NCiZndDs8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICJUTFMg
MS4zIGFuZCBhYm92ZSB2ZXJzaW9uLCAiIHNob3VsZCBwcm9iYWJseSBiZSAiVExTIDEuMyBhbmQg
YWJvdmUiIG9yICJUTFMgMS4zIGFuZCBoaWdoZXIgdmVyc2lvbnMiPGJyPg0KJmd0OyZuYnNwOyAm
bmJzcDsgTUdMVDogQ2hhbmdlZCB0byAiVExTIDEuMyBhbmQgaGlnaGVyIHZlcnNpb25zIjxicj4N
CiZndDs8YnI+DQomZ3Q7Jmd0OyZuYnNwOyAmbmJzcDsgT24gMDQvMDUvMTcgMTg6NDEsIFRoZSBJ
RVNHIHdyb3RlOjxicj4NCiZndDsmZ3Q7IFRoZSBJRVNHIGhhcyByZWNlaXZlZCBhIHJlcXVlc3Qg
ZnJvbSB0aGUgVHJhbnNwb3J0IExheWVyIFNlY3VyaXR5IFdHPGJyPg0KJmd0OyZndDsgKHRscykg
dG8gY29uc2lkZXIgdGhlIGZvbGxvd2luZyBkb2N1bWVudDo8YnI+DQomZ3Q7Jmd0OyAtICdFQ0RI
RV9QU0sgd2l0aCBBRVMtR0NNIGFuZCBBRVMtQ0NNIENpcGhlciBTdWl0ZXMgZm9yIFRyYW5zcG9y
dCBMYXllcjxicj4NCiZndDsmZ3Q7Jm5ic3A7ICZuYnNwO1NlY3VyaXR5IChUTFMpJzxicj4NCiZn
dDsmZ3Q7Jm5ic3A7ICZsdDtkcmFmdC1pZXRmLXRscy1lY2RoZS1wc2stPHdicj5hZWFkLTAzLnR4
dCZndDsgYXMgUHJvcG9zZWQgU3RhbmRhcmQ8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7IFRo
ZSBJRVNHIHBsYW5zIHRvIG1ha2UgYSBkZWNpc2lvbiBpbiB0aGUgbmV4dCBmZXcgd2Vla3MsIGFu
ZCBzb2xpY2l0czxicj4NCiZndDsmZ3Q7IGZpbmFsIGNvbW1lbnRzIG9uIHRoaXMgYWN0aW9uLiBQ
bGVhc2Ugc2VuZCBzdWJzdGFudGl2ZSBjb21tZW50cyB0byB0aGU8YnI+DQomZ3Q7Jmd0OyA8YSBo
cmVmPSJtYWlsdG86aWV0ZkBpZXRmLm9yZyI+aWV0ZkBpZXRmLm9yZzwvYT4gbWFpbGluZyBsaXN0
cyBieSAyMDE3LTA1LTE4LiBFeGNlcHRpb25hbGx5LCBjb21tZW50cyBtYXk8YnI+DQomZ3Q7Jmd0
OyBiZSBzZW50IHRvIDxhIGhyZWY9Im1haWx0bzppZXNnQGlldGYub3JnIj5pZXNnQGlldGYub3Jn
PC9hPiBpbnN0ZWFkLiBJbiBlaXRoZXIgY2FzZSwgcGxlYXNlIHJldGFpbiB0aGU8YnI+DQomZ3Q7
Jmd0OyBiZWdpbm5pbmcgb2YgdGhlIFN1YmplY3QgbGluZSB0byBhbGxvdyBhdXRvbWF0ZWQgc29y
dGluZy48YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7IEFic3RyYWN0PGJyPg0KJmd0OyZndDs8
YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jm5ic3A7ICZuYnNwO1RoaXMgZG9jdW1lbnQgZGVm
aW5lcyBzZXZlcmFsIG5ldyBjaXBoZXIgc3VpdGVzIGZvciB0aGUgVHJhbnNwb3J0PGJyPg0KJmd0
OyZndDsmbmJzcDsgJm5ic3A7TGF5ZXIgU2VjdXJpdHkgKFRMUykgcHJvdG9jb2wuJm5ic3A7IFRo
ZSBjaXBoZXIgc3VpdGVzIGFyZSBhbGwgYmFzZWQgb248YnI+DQomZ3Q7Jmd0OyZuYnNwOyAmbmJz
cDt0aGUgRXBoZW1lcmFsIEVsbGlwdGljIEN1cnZlIERpZmZpZS1IZWxsbWFuIHdpdGggUHJlLVNo
YXJlZCBLZXk8YnI+DQomZ3Q7Jmd0OyZuYnNwOyAmbmJzcDsoRUNESEVfUFNLKSBrZXkgZXhjaGFu
Z2UgdG9nZXRoZXIgd2l0aCB0aGUgQXV0aGVudGljYXRlZCBFbmNyeXB0aW9uPGJyPg0KJmd0OyZn
dDsmbmJzcDsgJm5ic3A7d2l0aCBBc3NvY2lhdGVkIERhdGEgKEFFQUQpIGFsZ29yaXRobXMgQUVT
LUdDTSBhbmQgQUVTLUNDTS4mbmJzcDsgUFNLPGJyPg0KJmd0OyZndDsmbmJzcDsgJm5ic3A7cHJv
dmlkZXMgbGlnaHQgYW5kIGVmZmljaWVudCBhdXRoZW50aWNhdGlvbiwgRUNESEUgcHJvdmlkZXMg
cGVyZmVjdDxicj4NCiZndDsmZ3Q7Jm5ic3A7ICZuYnNwO2ZvcndhcmQgc2VjcmVjeSwgYW5kIEFF
Uy1HQ00gYW5kIEFFUy1DQ00gcHJvdmlkZXMgZW5jcnlwdGlvbiBhbmQ8YnI+DQomZ3Q7Jmd0OyZu
YnNwOyAmbmJzcDtpbnRlZ3JpdHkgcHJvdGVjdGlvbi48YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsm
Z3Q7PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7IFRoZSBmaWxlIGNh
biBiZSBvYnRhaW5lZCB2aWE8YnI+DQomZ3Q7Jmd0OyA8YSBocmVmPSJodHRwczovL2RhdGF0cmFj
a2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLXRscy1lY2RoZS1wc2stYWVhZC8iIHJlbD0ibm9y
ZWZlcnJlciIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvPHdi
cj5kb2MvZHJhZnQtaWV0Zi10bHMtZWNkaGUtcHNrLTx3YnI+YWVhZC88L2E+PGJyPg0KJmd0OyZn
dDs8YnI+DQomZ3Q7Jmd0OyBJRVNHIGRpc2N1c3Npb24gY2FuIGJlIHRyYWNrZWQgdmlhPGJyPg0K
Jmd0OyZndDsgPGEgaHJlZj0iaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQt
aWV0Zi10bHMtZWNkaGUtcHNrLWFlYWQvYmFsbG90LyIgcmVsPSJub3JlZmVycmVyIiB0YXJnZXQ9
Il9ibGFuayI+aHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy88d2JyPmRvYy9kcmFmdC1pZXRm
LXRscy1lY2RoZS1wc2stPHdicj5hZWFkL2JhbGxvdC88L2E+PGJyPg0KJmd0OyZndDs8YnI+DQom
Z3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7IE5vIElQUiBkZWNsYXJhdGlvbnMgaGF2ZSBiZWVuIHN1Ym1p
dHRlZCBkaXJlY3RseSBvbiB0aGlzIEktRC48YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7PGJy
Pg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7IF9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXzx3YnI+X19fX19fX19fX19fX19fX188YnI+DQomZ3Q7Jmd0OyBUTFMgbWFp
bGluZyBsaXN0PGJyPg0KJmd0OyZndDsgPGEgaHJlZj0ibWFpbHRvOlRMU0BpZXRmLm9yZyI+VExT
QGlldGYub3JnPC9hPjxicj4NCiZndDsmZ3Q7IDxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vdGxzIiByZWw9Im5vcmVmZXJyZXIiIHRhcmdldD0iX2JsYW5rIj5o
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuLzx3YnI+bGlzdGluZm8vdGxzPC9hPjxicj4NCiZn
dDs8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX188
d2JyPl9fX19fX19fX19fX19fX19fPGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgVExTIG1haWxpbmcg
bGlzdDxicj4NCiZndDsmbmJzcDsgJm5ic3A7IDxhIGhyZWY9Im1haWx0bzpUTFNAaWV0Zi5vcmci
PlRMU0BpZXRmLm9yZzwvYT48YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyA8YSBocmVmPSJodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RscyIgcmVsPSJub3JlZmVycmVyIiB0YXJn
ZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi88d2JyPmxpc3RpbmZvL3Rs
czwvYT48YnI+DQomZ3Q7PGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fPHdicj5fX19fX19fX19fX19fX19fXzxicj4NCiZndDsmbmJzcDsgJm5ic3A7
IFRMUyBtYWlsaW5nIGxpc3Q8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyA8YSBocmVmPSJtYWlsdG86
VExTQGlldGYub3JnIj5UTFNAaWV0Zi5vcmc8L2E+PGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgPGEg
aHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90bHMiIHJlbD0ibm9y
ZWZlcnJlciIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vPHdi
cj5saXN0aW5mby90bHM8L2E+PGJyPg0KJmd0Ozxicj4NCiZndDs8YnI+DQomZ3Q7IF9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXzx3YnI+X19fX19fX19fX19fX19fX188YnI+DQomZ3Q7IFRM
UyBtYWlsaW5nIGxpc3Q8YnI+DQomZ3Q7IDxhIGhyZWY9Im1haWx0bzpUTFNAaWV0Zi5vcmciPlRM
U0BpZXRmLm9yZzwvYT48YnI+DQomZ3Q7IDxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vdGxzIiByZWw9Im5vcmVmZXJyZXIiIHRhcmdldD0iX2JsYW5rIj5odHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuLzx3YnI+bGlzdGluZm8vdGxzPC9hPjxicj4NCjwvZGl2
PjwvZGl2Pjxicj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188d2JyPl9fX19fX19fX19f
X19fX19fPGJyPg0KVExTIG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzpUTFNAaWV0
Zi5vcmciPlRMU0BpZXRmLm9yZzwvYT48YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL3RscyIgcmVsPSJub3JlZmVycmVyIiB0YXJnZXQ9Il9ibGFuayI+
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi88d2JyPmxpc3RpbmZvL3RsczwvYT48YnI+DQo8
YnI+PC9ibG9ja3F1b3RlPjwvZGl2Pjxicj48L2Rpdj4NCjwvZGl2PjwvYmxvY2txdW90ZT48L2Jv
ZHk+PC9odG1sPg==

--Apple-Mail-E1A62FE4-18C2-428F-BCCF-38DD24A8094C--

--Apple-Mail-9DD953CA-CD22-4DA9-A409-550794E10AC7
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINeDCCA4Mw
ggJroAMCAQICAQEwDQYJKoZIhvcNAQEFBQAwVDELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1JVCBM
aW5jb2xuIExhYm9yYXRvcnkxDDAKBgNVBAsTA1BLSTEWMBQGA1UEAxMNTUlUTEwgUm9vdCBDQTAe
Fw0wODA5MjMxMjAwMDBaFw0yOTEyMzEyMzU5NTlaMFQxCzAJBgNVBAYTAlVTMR8wHQYDVQQKExZN
SVQgTGluY29sbiBMYWJvcmF0b3J5MQwwCgYDVQQLEwNQS0kxFjAUBgNVBAMTDU1JVExMIFJvb3Qg
Q0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDFTikXWLImsvmtir9cEAqD3eQJMBMb
sHDQ0YWkQnUDdeyvpQgir3/VUkE6ALAOqtWwArWVHDL+WSsfM+ShuIyvXDONDbxJH/2yDmQByasy
oFhtzfTaq3AIYpnF012ECHadQ4I7XQAylSwI12mKQ9j26RPyWwD56iszhDWtz8vQnoAdGm05Tsi4
MF1mP6101vuC/4YqSevrCP2baxUZrChobsACqGxa9BQz+riH8fkWliXCdUASHYDOGqIb1vCXq4kk
jMn/y5RaV02RXDPUjl9H+8JrGItchbihTJ0G5EpMb56QSjEca4PvfLHkm2xJyJLwdAvagQzy2/5U
AL5qVuqDAgMBAAGjYDBeMA8GA1UdEwEB/wQFMAMBAf8wHQYDVR0OBBYEFGeqes/0Cqa5crWKoNKd
8hDDQ+0pMB8GA1UdIwQYMBaAFGeqes/0Cqa5crWKoNKd8hDDQ+0pMAsGA1UdDwQEAwIBhjANBgkq
hkiG9w0BAQUFAAOCAQEAPhttBWDQeHjYSlhfj8k+Q1Lc5QARZH9iDNlRjVAaL2tBnil9yNTX9Nqg
1Pxjth/RE75702Ib34EOFAf+RCJk5Cj2u/01RvzEO0oJgJp3vMRC1Wxixa68rZcvD8mLWbZ4G+g4
HhFL/ksBZ83Cztb4Na3ZrLN5MLKstKvHtlWAGPM06bRM8iRt+ml3CDG6jsVkvy2z4zbj3YCXzt3d
Vqx69RLWmmtEES6kKGY9O3WGO1qORA6lPgFADM/WVURitbOW/47+Vs/2K6MqlhZx9ipDcUZ/ftgK
+4N656zjGb6eqbKto2w14jwaHdcMjCp/MecuHLhjzRXKo38mPx1/dIr0ADCCBLwwggOkoAMCAQIC
ASkwDQYJKoZIhvcNAQEFBQAwVDELMAkGA1UEBhMCVVMxHzAdBgNVBAoTFk1JVCBMaW5jb2xuIExh
Ym9yYXRvcnkxDDAKBgNVBAsTA1BLSTEWMBQGA1UEAxMNTUlUTEwgUm9vdCBDQTAeFw0xMzEyMTcw
MDAwMDBaFw0yMDEyMzEyMzU5NTlaMFExCzAJBgNVBAYTAlVTMR8wHQYDVQQKExZNSVQgTGluY29s
biBMYWJvcmF0b3J5MQwwCgYDVQQLEwNQS0kxEzARBgNVBAMTCk1JVExMIENBLTMwggEiMA0GCSqG
SIb3DQEBAQUAA4IBDwAwggEKAoIBAQDaMFJ1bXy25bW03EbqHwHSSpyQVlAAC2gcKS9SlQRfqMW8
F3yZAjncbIthG4CjgdYml7v+LMVc59IkOzpQzmi+8I59eDZsmANiUEL0kNwsEUifSemk671G+mNZ
KLG0LnpyvAnlSzlA923G0p16TksleXagrDfDyWKFSLF49vFZp3WbtkwopqC+b3NPJs/oW6YpHF5g
mNKkHb5wBiOgYYRtJUfLHy7MebrECgEwfFrxvL7IPPwnOTqw/2KKWA/eJdIagICaHIHO+VBDlA01
Y/4Saj2PP+6QqFhUH9XB3G2iq48CqfiJ8MAhoz121vTlzLWBcAVI/dn+JSTHIFllQ5F/AgMBAAGj
ggGaMIIBljASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBTXYGYOe0mNdUwN/c9G3sjHEofK
vzAfBgNVHSMEGDAWgBRnqnrP9AqmuXK1iqDSnfIQw0PtKTAOBgNVHQ8BAf8EBAMCAYYwZgYIKwYB
BQUHAQEEWjBYMC0GCCsGAQUFBzAChiFodHRwOi8vY3JsLmxsLm1pdC5lZHUvZ2V0dG8/TExSQ0Ew
JwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLmxsLm1pdC5lZHUvb2NzcDAzBgNVHR8ELDAqMCigJqAk
hiJodHRwOi8vY3JsLmxsLm1pdC5lZHUvZ2V0Y3JsP0xMUkNBMIGSBgNVHSAEgYowgYcwDQYLKoZI
hvcSAgEDAQYwDQYLKoZIhvcSAgEDAQgwDQYLKoZIhvcSAgEDAQcwDQYLKoZIhvcSAgEDAQkwDQYL
KoZIhvcSAgEDAQowDQYLKoZIhvcSAgEDAQswDQYLKoZIhvcSAgEDAQ4wDQYLKoZIhvcSAgEDAQ8w
DQYLKoZIhvcSAgEDARAwDQYJKoZIhvcNAQEFBQADggEBACx/0cGfvapTtROCTFquMBzuLKeFwMSB
bB7Ngq139IsZJDQOG3MhX8tMLGpQuM534f4dOowlcHz6cefOHKpDjdGycZk4VPlF/M+H3h1v9kne
qXbjgPCUkjvJcEDYORlwQSA5YL1sdysSXNTo2eKBqFJbmh1UmuGYf9eFABwxLvsTkfrbLLErVY8+
BwGKkZWe7XFIdtOId7sOp9ZDa1UwtR/bddiEi5r3iQmxB3iNKHvU1UPR7sXiycCipAwj3wzMNh4s
6SOXMpGzvuv9oyw8ArHqcxo69EvsLLQ+OnnWLaoWRsaZfyh+eHaR6uNNO9En+DbavUxXxFHU+S2M
yw06w98wggUtMIIEFaADAgECAgoadMQgAAAAAK0DMA0GCSqGSIb3DQEBCwUAMFExCzAJBgNVBAYT
AlVTMR8wHQYDVQQKExZNSVQgTGluY29sbiBMYWJvcmF0b3J5MQwwCgYDVQQLEwNQS0kxEzARBgNV
BAMTCk1JVExMIENBLTMwHhcNMTcwMzAxMTgyNTA2WhcNMjAxMjMxMjM1OTU5WjBsMQswCQYDVQQG
EwJVUzEfMB0GA1UEChMWTUlUIExpbmNvbG4gTGFib3JhdG9yeTEPMA0GA1UECxMGUGVvcGxlMSsw
KQYDVQQDEyJCbHVtZW50aGFsLlVyaS41MDAxMDU4NCAoTW9iaWxpdHkpMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEAg+8bBB+jySfGyqx/fL9a596qTeq9fGfYXI2yJEZqLzJazzV1u6oL
ToMnJQ6phCIkQGplPsM+9PpzIcw5nN8GahHPU6FXXT3BSr6/bny4hftGu05y/n/DWWlPkos6PhSN
AB8WG3L+6a3mHcp9yYumPkdtM20+08oiU9S6OhFr6BoFFoeFjKEcFhvvovm9GcRzQ3g1cXHore5p
6umBCLGxZi0cGhBI/7ZyJmJUUo50bAPKdpURqYSsgU7p6GxCgpIcZBUlTxCSliPO/0TqiBMZ857M
F4OcehpG7LuxufD0p+g02uX7Z0aIfYnGHlkm3Y7NgvF6lW2WxCPklqKakb2fuwIDAQABo4IB6jCC
AeYwHQYDVR0OBBYEFPbiFDP71vJBmRLhxtKU/CWESr+tMA4GA1UdDwEB/wQEAwIGwDAfBgNVHSME
GDAWgBTXYGYOe0mNdUwN/c9G3sjHEofKvzAzBgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLmxs
Lm1pdC5lZHUvZ2V0Y3JsL0xMQ0EzMGYGCCsGAQUFBwEBBFowWDAtBggrBgEFBQcwAoYhaHR0cDov
L2NybC5sbC5taXQuZWR1L2dldHRvL0xMQ0EzMCcGCCsGAQUFBzABhhtodHRwOi8vb2NzcC5sbC5t
aXQuZWR1L29jc3AwPQYJKwYBBAGCNxUHBDAwLgYmKwYBBAGCNxUIg4PlHYfsp2aGrYcVg+rwRYW2
oR8dhYHgQIbXxk0CAWQCAQkwLAYDVR0lAQH/BCIwIAYIKwYBBQUHAwQGCisGAQQBgjcKAwwGCCsG
AQUFBwMCMBgGA1UdIAQRMA8wDQYLKoZIhvcSAgEDAQgwQQYDVR0RBDowOIEOdXJpQGxsLm1pdC5l
ZHWgJgYKKwYBBAGCNxQCA6AYDBZVUjIwOTgwQG1pdGxsLmFkLmxvY2FsMC0GCSsGAQQBgjcUAgQg
Hh4ATABMAE0AbwBiAGkAbABlAFMAaQBnAEEAdQB0AGgwDQYJKoZIhvcNAQELBQADggEBADbiZo1D
kfqhBA4LYklB+i49k6dh7L+nDEg3WdeZ/CRZAon9G3hPsUWd5YIsufRpoYUVJABcVos87kXZmkF1
RjH8vLNFOEV8ZVcNxbWC5DiA6dTswIEhXMSHFuyp3tERvu2z6+f9FC4jvZttYyLyirBJC4KwP/AO
Lm42Gn4lLeNrY4Ex8nq2Ah3xjB+QqvpxD2k1aaoR0fWaDxv2ZrdaFR43x2MTkiee+wR1diZ7GA7G
/HyJg9MUukKq23qm6Ys0VJQcJsKU1Q2/TLL99FRRa18ourBvFwJzcllLhTcqnvbawWt6cYEvGIJ9
Dszxz7LQECXI0KrPpM7x32SulMJjt1YxggLJMIICxQIBATBfMFExCzAJBgNVBAYTAlVTMR8wHQYD
VQQKExZNSVQgTGluY29sbiBMYWJvcmF0b3J5MQwwCgYDVQQLEwNQS0kxEzARBgNVBAMTCk1JVExM
IENBLTMCChp0xCAAAAAArQMwCQYFKw4DAhoFAKCCAT8wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEH
ATAcBgkqhkiG9w0BCQUxDxcNMTcwNTE4MjEyMjEyWjAjBgkqhkiG9w0BCQQxFgQU+EidNsFUmp/6
t1GyrIubifx8KjkwbgYJKwYBBAGCNxAEMWEwXzBRMQswCQYDVQQGEwJVUzEfMB0GA1UEChMWTUlU
IExpbmNvbG4gTGFib3JhdG9yeTEMMAoGA1UECxMDUEtJMRMwEQYDVQQDEwpNSVRMTCBDQS0zAgoa
dMQgAAAAAK0DMHAGCyqGSIb3DQEJEAILMWGgXzBRMQswCQYDVQQGEwJVUzEfMB0GA1UEChMWTUlU
IExpbmNvbG4gTGFib3JhdG9yeTEMMAoGA1UECxMDUEtJMRMwEQYDVQQDEwpNSVRMTCBDQS0zAgoa
dMQgAAAAAK0DMA0GCSqGSIb3DQEBAQUABIIBAF8kFMnIQCbE4Y66JhCWKsENmbLjQXCFn2qP1lJR
Go7lO7nz36GZGFo8Q5s0ApdLFMOdvi0Oc6yy5kunnLVOxL84B7WH/mdays3/TVnvczGPGUYRWq3+
GBYsIouydJ6G9NAB33r2yBefdTnlCSpYqjF/Rb2gZomi1ZVnLfKsLqhJVdYrcoZ0dODn/0wXvkE0
UTGGf4wx5Kw8pqLvrLRR68pjwSxnx96znzHKDyRFPe36He302oeAClkzU20VFG4AV0Qk3rLlvjrK
e2ZWY0V3e/ozZZ2tZERgmHyMa2pOU2GsUxTgc4JeNsrH5rEpEtpJfLfMO4OOIEQ2xXpytsddIWEA
AAAAAAA=

--Apple-Mail-9DD953CA-CD22-4DA9-A409-550794E10AC7--


From nobody Thu May 18 14:37:35 2017
Return-Path: <ekr@rtfm.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 C42041200B9 for <ietf@ietfa.amsl.com>; Thu, 18 May 2017 14:37:26 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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=rtfm-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 0dztlvM1xyeJ for <ietf@ietfa.amsl.com>; Thu, 18 May 2017 14:37:24 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002: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 C51BA129400 for <ietf@ietf.org>; Thu, 18 May 2017 14:31:35 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id l14so27197395ywk.1 for <ietf@ietf.org>; Thu, 18 May 2017 14:31:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=jdnzvD99ofr/+13li/sSrYYgPxEBdCIZ2vCVeO//4BM=; b=0uW6s/VkJGm6ufIDHW+DwtdUyPTeQxU+n3ccTPLYqz88jIVMRLWFoIaiKQMN+xKi6Q vKapbN5LMUApwrRQjZtLe4e9HHHoinJTCYB27iuzhOUMrPkI2bZ7kRA7iW9L7VAUl3+v CVIcBeFUta8wNw1o+X4RdZ0KkcL9i1LZBfujnCfgJ2qQLwx0BRmdC3wDRbUSUSMCnv1Z 2IuyuU1AbVnJSic/FZSCe8hANbKq6FAVYXkkzk8UvpnTucvAP05mvyhhwqLxwW6ag+pR gEzkwt1V/wMZIlbgQg0P2JfzrzW2NqKlly1jSu2GIa658dDSHml3boeR+SXtv4pVgvey qScw==
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=jdnzvD99ofr/+13li/sSrYYgPxEBdCIZ2vCVeO//4BM=; b=Yl9RRuiDKtSQUoPfz04Dg1Z9AdygFrKLV2jvQRBGjCOpJJmLJfhOw6Puz9EQyC0JjU 0Dusb0yJjt9rL8C9JYMvbAzyKA4YH4OEL/Sz9varqQGj28b4qeinSUC+yZolJPXHGVRO dwQ2O183ceht4NuwU3B7dmzFcndN1RIozVHkQKWTFVbDfEHIcYaNXpuQFmOD28CwujQB TeOg/cLYDZAs0Ygd2/XkGFjSDP2L/LuHj5xEzPjYfvP1qAntGFvp8YF6mQcRdjbqzD1s stnkR40Sq/MsJooKEJk/xRQdLDdSmJkvOqb3QL+qU3m7tGr5wizcnthgdcKK8pF25eRH /skw==
X-Gm-Message-State: AODbwcBDeG8EI5vDiwLRY5JAxolKr3SiW/6W4GHKvGh/npbbRk6oXOZm vB9iEvaG+iKPmniTxBIF7n2KSOoTsDIv
X-Received: by 10.129.147.134 with SMTP id k128mr5575501ywg.270.1495143095063;  Thu, 18 May 2017 14:31:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.131.150 with HTTP; Thu, 18 May 2017 14:30:54 -0700 (PDT)
In-Reply-To: <CADZyTkkncvCjpw85AUSwpHON-KLmbJsyYb-hw-EOEV8i3TXRYg@mail.gmail.com>
References: <149391606578.6842.3727373203321848879.idtracker@ietfa.amsl.com> <4373f972-bf9b-4dbe-1b59-7f51846831f3@a-oben.org> <2DD56D786E600F45AC6BDE7DA4E8A8C118BDB69D@eusaamb107.ericsson.se> <6191522F-FB75-4B74-B7DE-200FEDB3F021@mobileiron.com> <7E11398B-EAEF-4E06-BC6A-6797BA2197AE@ll.mit.edu> <CADZyTkkncvCjpw85AUSwpHON-KLmbJsyYb-hw-EOEV8i3TXRYg@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 18 May 2017 17:30:54 -0400
Message-ID: <CABcZeBNr-6UbGd+Lt_h2vQaFmB+CdgA=Nz5rzaoRSvSzy7BkDA@mail.gmail.com>
Subject: Re: [TLS] Last Call: <draft-ietf-tls-ecdhe-psk-aead-03.txt> (ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transport Layer Security (TLS)) to Proposed Standard
To: Daniel Migault <daniel.migault@ericsson.com>
Cc: "Blumenthal, Uri - 0553 - MITLL" <uri@ll.mit.edu>, "tls@ietf.org" <tls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c08d3561210e2054fd3212d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-L8ZC9Mbx3kIguh2pfhxySI75zo>
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, 18 May 2017 21:37:27 -0000

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

I don't much care, but we've moved to "forward secrecy" in TLS 1.3.

-Ekr


On Thu, May 18, 2017 at 5:17 PM, Daniel Migault <daniel.migault@ericsson.co=
m
> wrote:

> Hi,
>
> Thanks Tim and Uri for the comment. At least wikipedia considers them as
> equivalent. I am fine either way, but leave it  as pfs unless there is a
> consensus to change it to forward secrecy. If having fs seems important t=
o
> you please let us know asap!
>
> Yours,
> Daniel
>
> On Thu, May 18, 2017 at 5:01 PM, Blumenthal, Uri - 0553 - MITLL <
> uri@ll.mit.edu> wrote:
>
>> It is a mathematical cryptographic term, and as such is incontrovertible=
.
>>
>> I say leave it in.
>>
>> Regards,
>> Uri
>>
>> Sent from my iPhone
>>
>> > On May 18, 2017, at 16:58, Timothy Jackson <tjackson@mobileiron.com>
>> wrote:
>> >
>> > One small nit.
>> >
>> >> ECDHE provides perfect forward secrecy
>> > I thought we had decided to change =E2=80=9Cperfect forward secrecy=E2=
=80=9D to just
>> =E2=80=9Cforward secrecy=E2=80=9D since =E2=80=9Cperfect=E2=80=9D is suc=
h a difficult standard to reach?
>> >
>> > Tim
>> > =E2=80=94
>> > Tim Jackson | Product Security Architect | MobileIron, Inc.
>> >
>> > On 5/18/17, 10:45 AM, "TLS on behalf of Daniel Migault" <
>> tls-bounces@ietf.org on behalf of daniel.migault@ericsson.com> wrote:
>> >
>> >    Hi Simon,
>> >
>> >    Thank you for the review. I believe we have addressed your comments
>> in our version 04. Please see my comments inline.
>> >
>> >    Yours,
>> >    Daniel
>> >
>> >    -----Original Message-----
>> >    From: TLS [mailto:tls-bounces@ietf.org] On Behalf Of Simon
>> Friedberger
>> >    Sent: Thursday, May 04, 2017 5:59 PM
>> >    To: ietf@ietf.org
>> >    Cc: tls@ietf.org
>> >    Subject: Re: [TLS] Last Call: <draft-ietf-tls-ecdhe-psk-aead-03.txt=
>
>> (ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transport Layer
>> Security (TLS)) to Proposed Standard
>> >
>> >    Nits:
>> >
>> >        RFC 4279 reference is missing.
>> >    MGLT: It seems the reference is mentioned in the current version in
>> the Normative reference as well  as in the introduction at line 127,  in
>> section 3 line 143. In case you meant another reference, please let us k=
now.
>> >
>> >
>> >
>> >        "TLS 1.3 and above version, " should probably be "TLS 1.3 and
>> above" or "TLS 1.3 and higher versions"
>> >    MGLT: Changed to "TLS 1.3 and higher versions"
>> >
>> >>    On 04/05/17 18:41, The IESG wrote:
>> >> The IESG has received a request from the Transport Layer Security WG
>> >> (tls) to consider the following document:
>> >> - 'ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transport Lay=
er
>> >>   Security (TLS)'
>> >>  <draft-ietf-tls-ecdhe-psk-aead-03.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 th=
e
>> >> ietf@ietf.org mailing lists by 2017-05-18. Exceptionally, comments ma=
y
>> >> 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 defines several new cipher suites for the Transport
>> >>   Layer Security (TLS) protocol.  The cipher suites are all based on
>> >>   the Ephemeral Elliptic Curve Diffie-Hellman with Pre-Shared Key
>> >>   (ECDHE_PSK) key exchange together with the Authenticated Encryption
>> >>   with Associated Data (AEAD) algorithms AES-GCM and AES-CCM.  PSK
>> >>   provides light and efficient authentication, ECDHE provides perfect
>> >>   forward secrecy, and AES-GCM and AES-CCM provides encryption and
>> >>   integrity protection.
>> >>
>> >>
>> >>
>> >>
>> >> The file can be obtained via
>> >> https://datatracker.ietf.org/doc/draft-ietf-tls-ecdhe-psk-aead/
>> >>
>> >> IESG discussion can be tracked via
>> >> https://datatracker.ietf.org/doc/draft-ietf-tls-ecdhe-psk-aead/ballot=
/
>> >>
>> >>
>> >> No IPR declarations have been submitted directly on this I-D.
>> >>
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> TLS mailing list
>> >> TLS@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/tls
>> >
>> >    _______________________________________________
>> >    TLS mailing list
>> >    TLS@ietf.org
>> >    https://www.ietf.org/mailman/listinfo/tls
>> >
>> >    _______________________________________________
>> >    TLS mailing list
>> >    TLS@ietf.org
>> >    https://www.ietf.org/mailman/listinfo/tls
>> >
>> >
>> > _______________________________________________
>> > TLS mailing list
>> > TLS@ietf.org
>> > https://www.ietf.org/mailman/listinfo/tls
>>
>> _______________________________________________
>> TLS mailing list
>> TLS@ietf.org
>> https://www.ietf.org/mailman/listinfo/tls
>>
>>
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>
>

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

<div dir=3D"ltr">I don&#39;t much care, but we&#39;ve moved to &quot;forwar=
d secrecy&quot; in TLS 1.3.<div><br></div><div>-Ekr</div><div><br></div></d=
iv><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, May 18=
, 2017 at 5:17 PM, Daniel Migault <span dir=3D"ltr">&lt;<a href=3D"mailto:d=
aniel.migault@ericsson.com" target=3D"_blank">daniel.migault@ericsson.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"><div dir=3D"ltr"><di=
v><div>Hi, <br><br>Thanks Tim and Uri for the comment. At least wikipedia c=
onsiders them as equivalent. I am fine either way, but leave it=C2=A0 as pf=
s unless there is a consensus to change it to forward secrecy. If having fs=
 seems important to you please let us know asap!<br><br>Yours, <br></div></=
div>Daniel <br></div><div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"=
gmail_extra"><br><div class=3D"gmail_quote">On Thu, May 18, 2017 at 5:01 PM=
, Blumenthal, Uri - 0553 - MITLL <span dir=3D"ltr">&lt;<a href=3D"mailto:ur=
i@ll.mit.edu" target=3D"_blank">uri@ll.mit.edu</a>&gt;</span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">It is a mathematical cryptographic term, and as=
 such is incontrovertible.<br>
<br>
I say leave it in.<br>
<br>
Regards,<br>
Uri<br>
<br>
Sent from my iPhone<br>
<div class=3D"m_2531415802891281647HOEnZb"><div class=3D"m_2531415802891281=
647h5"><br>
&gt; On May 18, 2017, at 16:58, Timothy Jackson &lt;<a href=3D"mailto:tjack=
son@mobileiron.com" target=3D"_blank">tjackson@mobileiron.com</a>&gt; wrote=
:<br>
&gt;<br>
&gt; One small nit.<br>
&gt;<br>
&gt;&gt; ECDHE provides perfect forward secrecy<br>
&gt; I thought we had decided to change =E2=80=9Cperfect forward secrecy=E2=
=80=9D to just =E2=80=9Cforward secrecy=E2=80=9D since =E2=80=9Cperfect=E2=
=80=9D is such a difficult standard to reach?<br>
&gt;<br>
&gt; Tim<br>
&gt; =E2=80=94<br>
&gt; Tim Jackson | Product Security Architect | MobileIron, Inc.<br>
&gt;<br>
&gt; On 5/18/17, 10:45 AM, &quot;TLS on behalf of Daniel Migault&quot; &lt;=
<a href=3D"mailto:tls-bounces@ietf.org" target=3D"_blank">tls-bounces@ietf.=
org</a> on behalf of <a href=3D"mailto:daniel.migault@ericsson.com" target=
=3D"_blank">daniel.migault@ericsson.com</a>&gt; wrote:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Hi Simon,<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Thank you for the review. I believe we have addressed you=
r comments in our version 04. Please see my comments inline.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Yours,<br>
&gt;=C2=A0 =C2=A0 Daniel<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 -----Original Message-----<br>
&gt;=C2=A0 =C2=A0 From: TLS [mailto:<a href=3D"mailto:tls-bounces@ietf.org"=
 target=3D"_blank">tls-bounces@ietf.org</a>] On Behalf Of Simon Friedberger=
<br>
&gt;=C2=A0 =C2=A0 Sent: Thursday, May 04, 2017 5:59 PM<br>
&gt;=C2=A0 =C2=A0 To: <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ie=
tf@ietf.org</a><br>
&gt;=C2=A0 =C2=A0 Cc: <a href=3D"mailto:tls@ietf.org" target=3D"_blank">tls=
@ietf.org</a><br>
&gt;=C2=A0 =C2=A0 Subject: Re: [TLS] Last Call: &lt;draft-ietf-tls-ecdhe-ps=
k-aead<wbr>-03.txt&gt; (ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites fo=
r Transport Layer Security (TLS)) to Proposed Standard<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Nits:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 RFC 4279 reference is missing.<br>
&gt;=C2=A0 =C2=A0 MGLT: It seems the reference is mentioned in the current =
version in the Normative reference as well=C2=A0 as in the introduction at =
line 127,=C2=A0 in section 3 line 143. In case you meant another reference,=
 please let us know.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 &quot;TLS 1.3 and above version, &quot; sho=
uld probably be &quot;TLS 1.3 and above&quot; or &quot;TLS 1.3 and higher v=
ersions&quot;<br>
&gt;=C2=A0 =C2=A0 MGLT: Changed to &quot;TLS 1.3 and higher versions&quot;<=
br>
&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 On 04/05/17 18:41, The IESG wrote:<br>
&gt;&gt; The IESG has received a request from the Transport Layer Security =
WG<br>
&gt;&gt; (tls) to consider the following document:<br>
&gt;&gt; - &#39;ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for Transp=
ort Layer<br>
&gt;&gt;=C2=A0 =C2=A0Security (TLS)&#39;<br>
&gt;&gt;=C2=A0 &lt;draft-ietf-tls-ecdhe-psk-aead<wbr>-03.txt&gt; as Propose=
d Standard<br>
&gt;&gt;<br>
&gt;&gt; The IESG plans to make a decision in the next few weeks, and solic=
its<br>
&gt;&gt; final comments on this action. Please send substantive comments to=
 the<br>
&gt;&gt; <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</=
a> mailing lists by 2017-05-18. Exceptionally, comments may<br>
&gt;&gt; be sent to <a href=3D"mailto:iesg@ietf.org" target=3D"_blank">iesg=
@ietf.org</a> instead. In either case, please retain the<br>
&gt;&gt; beginning of the Subject line to allow automated sorting.<br>
&gt;&gt;<br>
&gt;&gt; Abstract<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0This document defines several new cipher suites for th=
e Transport<br>
&gt;&gt;=C2=A0 =C2=A0Layer Security (TLS) protocol.=C2=A0 The cipher suites=
 are all based on<br>
&gt;&gt;=C2=A0 =C2=A0the Ephemeral Elliptic Curve Diffie-Hellman with Pre-S=
hared Key<br>
&gt;&gt;=C2=A0 =C2=A0(ECDHE_PSK) key exchange together with the Authenticat=
ed Encryption<br>
&gt;&gt;=C2=A0 =C2=A0with Associated Data (AEAD) algorithms AES-GCM and AES=
-CCM.=C2=A0 PSK<br>
&gt;&gt;=C2=A0 =C2=A0provides light and efficient authentication, ECDHE pro=
vides perfect<br>
&gt;&gt;=C2=A0 =C2=A0forward secrecy, and AES-GCM and AES-CCM provides encr=
yption and<br>
&gt;&gt;=C2=A0 =C2=A0integrity protection.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; The file can be obtained via<br>
&gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-tls-ecdhe-p=
sk-aead/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org=
/d<wbr>oc/draft-ietf-tls-ecdhe-psk-ae<wbr>ad/</a><br>
&gt;&gt;<br>
&gt;&gt; IESG discussion can be tracked via<br>
&gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-tls-ecdhe-p=
sk-aead/ballot/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.i=
etf.org/d<wbr>oc/draft-ietf-tls-ecdhe-psk-ae<wbr>ad/ballot/</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; No IPR declarations have been submitted directly on this I-D.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; ______________________________<wbr>_________________<br>
&gt;&gt; TLS mailing list<br>
&gt;&gt; <a href=3D"mailto:TLS@ietf.org" target=3D"_blank">TLS@ietf.org</a>=
<br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/tls" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/tls</a>=
<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 ______________________________<wbr>_________________<br>
&gt;=C2=A0 =C2=A0 TLS mailing list<br>
&gt;=C2=A0 =C2=A0 <a href=3D"mailto:TLS@ietf.org" target=3D"_blank">TLS@iet=
f.org</a><br>
&gt;=C2=A0 =C2=A0 <a href=3D"https://www.ietf.org/mailman/listinfo/tls" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinf=
o/tls</a><br>
&gt;<br>
&gt;=C2=A0 =C2=A0 ______________________________<wbr>_________________<br>
&gt;=C2=A0 =C2=A0 TLS mailing list<br>
&gt;=C2=A0 =C2=A0 <a href=3D"mailto:TLS@ietf.org" target=3D"_blank">TLS@iet=
f.org</a><br>
&gt;=C2=A0 =C2=A0 <a href=3D"https://www.ietf.org/mailman/listinfo/tls" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinf=
o/tls</a><br>
&gt;<br>
&gt;<br>
&gt; ______________________________<wbr>_________________<br>
&gt; TLS mailing list<br>
&gt; <a href=3D"mailto:TLS@ietf.org" target=3D"_blank">TLS@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/tls" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/tls</a><br>
</div></div><br>______________________________<wbr>_________________<br>
TLS mailing list<br>
<a href=3D"mailto:TLS@ietf.org" target=3D"_blank">TLS@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tls" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/tls</a><br>
<br></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
TLS mailing list<br>
<a href=3D"mailto:TLS@ietf.org">TLS@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tls" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/tls</a><br>
<br></blockquote></div><br></div>

--94eb2c08d3561210e2054fd3212d--


From nobody Thu May 18 21:43:46 2017
Return-Path: <kaduk@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 70A81129C6E; Thu, 18 May 2017 21:43:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.303
X-Spam-Level: 
X-Spam-Status: No, score=-2.303 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, 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 TdrSVNrUSx8o; Thu, 18 May 2017 21:43:21 -0700 (PDT)
Received: from dmz-mailsec-scanner-4.mit.edu (dmz-mailsec-scanner-4.mit.edu [18.9.25.15]) (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 DBABA129C13; Thu, 18 May 2017 21:38:35 -0700 (PDT)
X-AuditID: 1209190f-db7ff70000005284-13-591e76c97452
Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id 4E.26.21124.9C67E195; Fri, 19 May 2017 00:38:34 -0400 (EDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id v4J4cWgl014307; Fri, 19 May 2017 00:38:33 -0400
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v4J4cRQa011042 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 19 May 2017 00:38:31 -0400
Date: Thu, 18 May 2017 23:38:27 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: iesg@ietf.org, secdir@ietf.org, draft-ietf-tls-ecdhe-psk-aead.all@ietf.org
Cc: tls@ietf.org, ietf@ietf.org
Subject: secdir review of draft-ietf-tls-ecdhe-psk-aead-03
Message-ID: <20170519043827.GL39245@kduck.kaduk.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.7.1 (2016-10-04)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrDIsWRmVeSWpSXmKPExsUixG6nrnuqTC7SYP57GYs3yzYxWcz4M5HZ 4tnG+SwWHxY+ZLH4dL6L0YHVY8mSn0wBjFFcNimpOZllqUX6dglcGT0P9rAWfJapWPr7P2MD 41bxLkYODgkBE4lLb1y7GLk4hAQWM0mc3vWUHcLZyCjx4m4rK4RzlUniZNdJIIeTg0VAVWLV 4WvsIDabgIpEQ/dlZhBbRMBPYt2P90wgNrOAvMSidzfBaoQFrCR+bvwDFucF2vZpRRcbhC0o cXLmExaIei2JG/9eMoFcxCwgLbH8HwdIWFRAWeLv4XssExj5ZiHpmIWkYxZCxwJG5lWMsim5 Vbq5iZk5xanJusXJiXl5qUW6Jnq5mSV6qSmlmxhBgcgpyb+DcU6D9yFGAQ5GJR7eBytkI4VY E8uKK3MPMUpyMCmJ8s4IkIsU4kvKT6nMSCzOiC8qzUktPsQowcGsJMIrLgaU401JrKxKLcqH SUlzsCiJ84prNEYICaQnlqRmp6YWpBbBZGU4OJQkeJeVAjUKFqWmp1akZeaUIKSZODhBhvMA Dc8HqeEtLkjMLc5Mh8ifYlSUEue1KAFKCIAkMkrz4HpBiUIie3/NK0ZxoFeEeb1B2nmASQau +xXQYCagwc0PpEEGlyQipKQaGB1b8nfVilR23Fh8536vG9fSB1ev3/FOM/Tvi/9bf+exkMXs F+6TV/FeWuVulP3j4d830Ys3hhuu2/tobdPl2PPSLp0KSs8v2+/6KnBPZHvHlaU3wto23q0K WXRz6pLyd7xn3K5ML5dMWLJpQqx1HZPjA3fu3yx2S5b5mQUm/hNaN43xy+nF254qsRRnJBpq MRcVJwIA6NGlB+8CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YSvDlNFuM4GqHa5Bfh__G4XIfJs>
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, 19 May 2017 04:43:24 -0000

Hi all,

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.

This document is ready with nits.

Essentially, we are filling in a gap in the TLS (< 1.3) ciphersuite
space, thought of as a cross product of key exchange and
cipher+mac/AEAD -- we have some of the combinations (PSK with ECDHE
but no AES-[GC]CM, PSK with AES-GCM but only non-EC DH, etc.) but
not quite this one.

That said, it seems a little silly to only partially fill the gap
(by omitting the AES_256_CCM* cipher suites), even though there is
not currently demand for them.

This document is just assembling pieces that were already specified
elsewhere, so it need not contain much detail itself, which is fine.
That said, I think section 3 should probably state explicitly which
pieces it uses, instead of a vague reference of being "based on RFC
4279".  So, "The ServerKeyExchange and ClientKeyExchange messages
from RFC 5489 for ECDHE_PSK are used, and the premaster secret is
computed in the same manner as for ECDHE_PSK key exchange in RFC
5489."  (I am not sure why RFC 4279 is cited in the current text; it
does not cover ECDHE_PSK.)

The premaster_secret structure so used basically ends up putting the
ECDH output first followed by the static PSK; with the pre-TLS 1.2
PRF, that would give the ECDH shared secret to md5 and the PSK to
sha1, which is perhaps another reason to not use these with pre-1.2
worth mentioning (in addition to the AEAD availability).

The security considerations largely refer to those of the other
documents providing the pieces that are combined together here;
those referenced security considerations sections are more than
adequate here, as this document itself does not really do anything
particularly novel.  That said, if we are going to reiterate the
entropy requirement for PSKs inline, we probably ought to also
reiterate the nonce-reuse considerations for GCM and CCM.  The
relevant constructions help, but there are still ways to mess up and
reuse a nonce when doing crypto in parallel, if I remember the
GCM/TLS document's security considerations correctly.


Some other editorial nits follow.

I see we're already discussing "perfect forward secrecy" vs.
"forward secrecy"; my preference is for just "forward secrecy" (and
I may have been one of the more active voices in causing TLS 1.3 to
switch), but in the grand scheme of things it doesn't really matter.

In section 2, the RFC 7525 reference that "AEAD algorithms [...] are
strongly recommended" is scoped to just (D)TLS, so the text here
should probably also list that qualification.

In section 4, "... make use of the authenticated encryption with
additional data (AEAD) defined in TLS 1.2" seems to make AEAD into
something of a unique object, as opposed to a class of things with
multiple possible instantiations.  I would consider something like
"... (AEAD) concept".

In section 4, "these cipher suites MUST NOT be negotiated in TLS
versions prior to 1.2" should probably clarify that "these" cipher
suites are the new ones specified by this document.

s/Servers,\nwhich/Servers\nthat/

Does the last paragraph of section 5 want a note "RFC Editor please
remove this paragraph"?

Section 6, third paragraph, s/by using short PSK/by using a short
PSK/.  Also, s/by a human and thus/by a human which thus/, maybe?

Last paragraph page 4, comma after "i.e.".


-Ben


From nobody Thu May 18 21:58:34 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 7FB5712EB54 for <ietf@ietfa.amsl.com>; Thu, 18 May 2017 21:58:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.401
X-Spam-Level: 
X-Spam-Status: No, score=-5.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, 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 CIc9QUMpnV2V for <ietf@ietfa.amsl.com>; Thu, 18 May 2017 21:58:26 -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 2DB7A12EB3C for <ietf@ietf.org>; Thu, 18 May 2017 21:53:11 -0700 (PDT)
Received: from pps.filterd (m0098417.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v4J4hj43104492 for <ietf@ietf.org>; Fri, 19 May 2017 00:53:10 -0400
Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.152]) by mx0a-001b2d01.pphosted.com with ESMTP id 2ahssrrkva-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 19 May 2017 00:53:10 -0400
Received: from localhost by e34.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, 18 May 2017 22:53:09 -0600
Received: from b03cxnp07028.gho.boulder.ibm.com (9.17.130.15) by e34.co.us.ibm.com (192.168.1.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 18 May 2017 22:53:08 -0600
Received: from b03ledav006.gho.boulder.ibm.com (b03ledav006.gho.boulder.ibm.com [9.17.130.237]) by b03cxnp07028.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v4J4r8xT14549426 for <ietf@ietf.org>; Thu, 18 May 2017 21:53:08 -0700
Received: from b03ledav006.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 2A277C604A for <ietf@ietf.org>; Thu, 18 May 2017 22:53:08 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b03ledav006.gho.boulder.ibm.com (Postfix) with ESMTPS id 10E44C6037 for <ietf@ietf.org>; Thu, 18 May 2017 22:53:08 -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 v4J4r7ek027277 for <ietf@ietf.org>; Fri, 19 May 2017 00:53:07 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v4J4r6O9027260 for ietf@ietf.org; Fri, 19 May 2017 00:53:06 -0400
From: narten@us.ibm.com
Date: Fri, 19 May 2017 00:53:06 -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: 17051904-0016-0000-0000-000006C60129
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00007083; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000212; SDB=6.00862434; UDB=6.00427910; IPR=6.00642183;  BA=6.00005358; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00015507; XFM=3.00000015; UTC=2017-05-19 04:53:09
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17051904-0017-0000-0000-000039B5AAC3
Message-Id: <201705190453.v4J4r6O9027260@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-05-19_03:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=75 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1705190033
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XZnvFT9aqY5TyO8x8VzFG8t--QY>
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, 19 May 2017 04:58:32 -0000

Total of 64 messages in the last 7 days.
 
script run at: Fri May 19 00:53:06 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 12.50% |    8 | 10.46% |    78003 | julian.reschke@gmx.de
  7.81% |    5 |  7.58% |    56543 | mnot@mnot.net
  4.69% |    3 |  5.46% |    40714 | daniel.migault@ericsson.com
  3.12% |    2 |  6.54% |    48794 | uri@ll.mit.edu
  3.12% |    2 |  5.29% |    39441 | evoit@cisco.com
  3.12% |    2 |  4.46% |    33237 | bclaise@cisco.com
  4.69% |    3 |  2.80% |    20878 | john@jlc.net
  3.12% |    2 |  4.14% |    30911 | sboutros@vmware.com
  3.12% |    2 |  4.03% |    30098 | pbrisset@cisco.com
  3.12% |    2 |  3.12% |    23246 | dromasca@gmail.com
  3.12% |    2 |  2.79% |    20822 | murch@andrew.cmu.edu
  3.12% |    2 |  1.94% |    14454 | cyrus@daboo.name
  3.12% |    2 |  1.88% |    14026 | amy.yemin@huawei.com
  3.12% |    2 |  1.38% |    10329 | j.schoenwaelder@jacobs-university.de
  1.56% |    1 |  2.91% |    21704 | ekr@rtfm.com
  1.56% |    1 |  2.39% |    17841 | andy@yumaworks.com
  1.56% |    1 |  2.37% |    17693 | davenoveck@gmail.com
  1.56% |    1 |  2.26% |    16883 | pmcmanus@mozilla.com
  1.56% |    1 |  2.01% |    14972 | agmalis@gmail.com
  1.56% |    1 |  2.00% |    14901 | oritl@microsoft.com
  1.56% |    1 |  1.81% |    13480 | tjackson@mobileiron.com
  1.56% |    1 |  1.70% |    12670 | chengweiqiang@chinamobile.com
  1.56% |    1 |  1.67% |    12485 | phill@hallambaker.com
  1.56% |    1 |  1.60% |    11966 | narten@us.ibm.com
  1.56% |    1 |  1.54% |    11465 | huubatwork@gmail.com
  1.56% |    1 |  1.51% |    11262 | elwynd@dial.pipex.com
  1.56% |    1 |  1.47% |    10990 | alissa@cooperw.in
  1.56% |    1 |  1.33% |     9932 | lear@cisco.com
  1.56% |    1 |  1.30% |     9667 | olejacobsen@me.com
  1.56% |    1 |  1.27% |     9460 | cts@etri.re.kr
  1.56% |    1 |  1.21% |     9034 | acee@cisco.com
  1.56% |    1 |  1.20% |     8950 | mersue@gmail.com
  1.56% |    1 |  1.18% |     8836 | christer.holmberg@ericsson.com
  1.56% |    1 |  1.13% |     8440 | marka@isc.org
  1.56% |    1 |  1.01% |     7564 | johnl@taugh.com
  1.56% |    1 |  0.87% |     6484 | linuxwolf+ietf@outer-planes.net
  1.56% |    1 |  0.87% |     6481 | bwietf@bwijnen.net
  1.56% |    1 |  0.82% |     6085 | huitema@huitema.net
  1.56% |    1 |  0.69% |     5184 | ietf-secretariat@ietf.org
--------+------+--------+----------+------------------------
100.00% |   64 |100.00% |   745925 | Total


From nobody Fri May 19 00:21:57 2017
Return-Path: <davemgarrett@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 918EA129ADA; Fri, 19 May 2017 00:21:52 -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 L8ieFsHbj3_R; Fri, 19 May 2017 00:21:51 -0700 (PDT)
Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::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 6ACF0127A91; Fri, 19 May 2017 00:16:36 -0700 (PDT)
Received: by mail-qt0-x234.google.com with SMTP id c13so51911702qtc.1; Fri, 19 May 2017 00:16:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-transfer-encoding:message-id; bh=1l6wwkBmmZlH9uo3WF1lXR/upb5w3DhmVxp3H96FKuE=; b=CFImJbKua/vDQNK96rHApq84iAOeHIUZnaZcwkHkBj14ZqF8y5wUjljxV4GhebYG4u Y2mD095XN+5VHGPymg1T/Y59+ErQuJKUvdDc9JdtiHkRe2oNxXiW7gBTlP04G6iCVAXw GyxkheQyUBqWkZvqWEX/zy2Vb/kjsxTqy/k94BCJstWCzSAAceKLoZYYhjZ2kKdP4RSb GtbFPGTP8CBi9UxOrgBbgErHc21RqarB/LyVGjAoCUqQEmFqMjkDcN153HNCQ2EpdR5n alkbnvU6z+hSEbkYM7gEy/RWYew37WVDNg3Y1y2Fxja2wrc41Ub+tbXva7pXQ7Bw07wn ry0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:user-agent:cc:references :in-reply-to:mime-version:content-transfer-encoding:message-id; bh=1l6wwkBmmZlH9uo3WF1lXR/upb5w3DhmVxp3H96FKuE=; b=iAyoaT7C+wAskUFNVLQJZJxw9SFTICp4NV4RcMkZE8+w8SObNW1B9YPPHECwfqus9f h5xS67so4uRBozDGHZBaBTM2Wa2lInLfsGnaYRYtXlJIdK8e1H36pONcOuaCuIjYim9W i2vdh+pNz72MeG1+ilekDAKpqO96+c0Wal5eZ7Z1IAWQsh5p37r4NHKGSJoQkYrLROiP oQ4uYqunQItjMGe547yI4kQAsTTzUd2baBXZzURPEVJ8vM51ZHqOZKvQz2fXgSfH2WCT XN8YkPo3Ql2Ea3WwrGSpb5OGp4AbtH7zv/XpoHkJ/bQaN65/XAF1+BoxFKWVN4eogpXv vrqA==
X-Gm-Message-State: AODbwcCzJz/ZSNp/ezDRdOCVUE3hGnarFT8+qvE+GSsA3Ug7fPUroj1W NzQK/92nM/OhOA2oOrk=
X-Received: by 10.200.56.243 with SMTP id g48mr8729225qtc.79.1495178195474; Fri, 19 May 2017 00:16:35 -0700 (PDT)
Received: from dave-laptop.localnet (pool-71-185-36-197.phlapa.fios.verizon.net. [71.185.36.197]) by smtp.gmail.com with ESMTPSA id o13sm5426365qke.30.2017.05.19.00.16.34 (version=TLS1 cipher=AES128-SHA bits=128/128); Fri, 19 May 2017 00:16:34 -0700 (PDT)
From: Dave Garrett <davemgarrett@gmail.com>
To: tls@ietf.org
Subject: Re: [TLS] secdir review of draft-ietf-tls-ecdhe-psk-aead-03
Date: Fri, 19 May 2017 03:16:32 -0400
User-Agent: KMail/1.13.5 (Linux/2.6.32-74-generic-pae; KDE/4.4.5; i686; ; )
Cc: Benjamin Kaduk <kaduk@mit.edu>, iesg@ietf.org, secdir@ietf.org, draft-ietf-tls-ecdhe-psk-aead.all@ietf.org, ietf@ietf.org
References: <20170519043827.GL39245@kduck.kaduk.org>
In-Reply-To: <20170519043827.GL39245@kduck.kaduk.org>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201705190316.33316.davemgarrett@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eMg4oOZ7h0Yq1_hDBhSRuFp46D8>
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, 19 May 2017 07:21:53 -0000

On Friday, May 19, 2017 12:38:27 am Benjamin Kaduk wrote:
> In section 4, "these cipher suites MUST NOT be negotiated in TLS
> versions prior to 1.2" should probably clarify that "these" cipher
> suites are the new ones specified by this document.

Probably should be: "the cipher suites defined in this document
MUST NOT be negotiated for any version of TLS other than 1.2."

The sentence mentioning TLS 1.3+ could be moved up to right after
and just say: "TLS version 1.3 and later negotiate these features in
a different manner."


Dave


From nobody Fri May 19 01:19:42 2017
Return-Path: <olivier.dornon@nokia.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 34D2312943E; Fri, 19 May 2017 01:19:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.702
X-Spam-Level: 
X-Spam-Status: No, score=-4.702 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_H2=-2.8, SPF_HELO_PASS=-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=nokia.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 GGX8qoZE6mX7; Fri, 19 May 2017 01:19:37 -0700 (PDT)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30117.outbound.protection.outlook.com [40.107.3.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F788128768; Fri, 19 May 2017 01:13:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector1-nokia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=X5PHhpcT6uhInZibK/hwAM47U7E/ajDSSeyvu5WY7AU=; b=r2wK6O/vglCtj2xKOkjHiQ9cvUXrB2zAWyFHhDc8oB70iLdVPz9ZRl+lzv1C8QElteEuGEoM7F1AIswvYwdknCsyQNpJ0DMbsB8OXqqCSIcnn+FFk/qjd+bKPvjLrllLlb/f4zTca4s14iD1K1HzQC6D87TEPcNFExO36BtU6Gs=
Received: from VI1PR07CA0163.eurprd07.prod.outlook.com (10.166.77.11) by DB3PR07MB0586.eurprd07.prod.outlook.com (10.160.46.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1084.7; Fri, 19 May 2017 08:13:55 +0000
Received: from VE1EUR03FT035.eop-EUR03.prod.protection.outlook.com (2a01:111:f400:7e09::200) by VI1PR07CA0163.outlook.office365.com (2603:10a6:802:3e::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1124.5 via Frontend Transport; Fri, 19 May 2017 08:13:55 +0000
Authentication-Results: spf=pass (sender IP is 135.245.241.12) smtp.mailfrom=nokia.com; ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=pass action=none header.from=nokia.com;
Received-SPF: Pass (protection.outlook.com: domain of nokia.com designates 135.245.241.12 as permitted sender) receiver=protection.outlook.com; client-ip=135.245.241.12; helo=fr711usmtp1-o.zeu.alcatel-lucent.com;
Received: from fr711usmtp1-o.zeu.alcatel-lucent.com (135.245.241.12) by VE1EUR03FT035.mail.protection.outlook.com (10.152.18.110) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.1075.5 via Frontend Transport; Fri, 19 May 2017 08:13:54 +0000
Received: from fr711usmtp1.zeu.alcatel-lucent.com (fr711usmtp1-o.zeu.alcatel-lucent.com [135.239.2.135]) by fr711usmtp1-o.zeu.alcatel-lucent.com (GMO-o) with ESMTP id v4J8DiS1004594 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 19 May 2017 08:13:46 GMT
Received: from princess.be.alcatel-lucent.com (bt9870.be.alcatel-lucent.com [138.203.16.150]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id v4J8DLHH004562; Fri, 19 May 2017 08:13:27 GMT
Received: from [138.203.14.165] (cplab165 [138.203.14.165]) by princess.be.alcatel-lucent.com (Postfix) with ESMTP id DE40C1045CB; Fri, 19 May 2017 10:13:20 +0200 (CEST)
Message-ID: <591EA920.5000808@nokia.com>
Date: Fri, 19 May 2017 10:13:20 +0200
From: Olivier Dornon <olivier.dornon@nokia.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>, <secdir@ietf.org>
CC: <draft-ietf-pals-vpls-pim-snooping.all@ietf.org>, <ietf@ietf.org>, <pals@ietf.org>
Subject: Re: Secdir last call review of draft-ietf-pals-vpls-pim-snooping-05
References: <149454198305.16624.16060763979327626869@ietfa.amsl.com>
In-Reply-To: <149454198305.16624.16060763979327626869@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:135.245.241.12; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(39840400002)(39850400002)(39410400002)(39860400002)(39450400003)(39400400002)(2980300002)(438002)(377454003)(43784003)(24454002)(51914003)(377424004)(9170700003)(50986999)(356003)(23676002)(230700001)(87266999)(76176999)(54356999)(305945005)(65816999)(2950100002)(64126003)(4001350100001)(86362001)(5660300001)(6706004)(33656002)(106466001)(478600001)(38730400002)(230783001)(36756003)(4326008)(50466002)(54906002)(53936002)(80316001)(53546009)(229853002)(83506001)(81166006)(6266002)(8676002)(189998001)(8936002)(6246003)(2906002); DIR:OUT; SFP:1102; SCL:1; SRVR:DB3PR07MB0586; H:fr711usmtp1-o.zeu.alcatel-lucent.com; FPR:; SPF:Pass; MLV:sfv; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; VE1EUR03FT035; 1:hJEZSfEjkC+GxNeP+JssmiCz2cRJBM+7UljWJSEMggukTc3F+n14wNevo4a4cIoibLz4brEFE78dlvu8IGl+bMHfUqxfo3BzoRnBA7yqWeuxtuFTbpqPi9vZyPQWPGjoEH5fWw/KiU8vy+M7KXkHpafW7aUzJz6vgBeZugQFBLR1O1xG0fVvTslnVRY9/p40pEFDH7FlES4ZMEbAmeqwMds74pdDazuNLR0y0yyySsvfuhgePqCGhde8koHw10HAzjfEHJAdi+bAssU7uXZ6uGbtLkPt0qILeJO2tO0lKtQS1heJ1raIp9fDGMcjexfM6i+UC2wS38O6ED/QPi528CQ/X7ehjfGrW0gGf9JH3V02eBWgmUoHzXoVWoFbcYFuAbra4OpXJ2msAZTt4QzZKf5evoYkWu/QLE3aUcRW5nMYZsr5qWSEvnQoLzgUqB3ps6a/X7KzDy1ZjqfIEvJlM8lKtxrBeGhWGhkMuukhq/WV4i3cqaZOaNLHEdMISDjXeQuWtK5JSJYVIEyeoY/Ak6QUxsAWW97sarPr3SvI5wM=
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 37f1e689-948f-4b5f-4d29-08d49e8efe21
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(8251501002)(2017030254075)(201703131423075)(201703031133081); SRVR:DB3PR07MB0586; 
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB0586; 3:A36qeFhWKRP3Dr8nEJ/P0bBRqj9qfbbMp6G/e+2hn9eAA3RrTtuQy6YW9Tz8oZ4egE1QOhgk1f2DOuwJkzDplj86EMlkLa/zMliouAU8Jh7Avfr1Cn10TFViysSEphSF35hAp3l24xye9aXRJHcOabOYleH2jMF8ER6O5mSzH0rcDmIk13D2CkyWZ8wodrADnQJOYh5E+zXjbff+KTxBZQL5WoTgK/+pc4Of8FywTXiNfgh41Es7FQ2Qo62EA9ulJddQRJjQloYr8CTZY2N+4Crf576YRCl4kZ7e4+Q8+uNSz4tm13Aw6+5CQEiOOdhsxfV9c3MLld0vavzHnhAmQ9pAFjBUyV9KUduzYAoP/ZLw9VO3mZ5qvmQ4+k1HQvgIXolDQJCrqHBKyxWgP49BxIG7snLz8jCwaHEWWWq1pmWoZRXGQgnH6iuUAbcgX8hU1kxl4kjfSitqg10GWpfMReS4zJoQwGQGk1zGz7um6Wq6ReA8aUNu9weT91DTvvCs
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB0586; 25:YPKmqY9GzoyU1O2DdGdu606i3ViAo9zzVhgdehTrBxOOlVpL9ozcsN8Z/mESYnDfILe1gsvlyTFHSdK+kEmCU/6n9N3YNGsHmX83lr9XZXkQFXSba3PE9svdJ76MrTETjPppSKZ/Gcjf23S958cZMrmtEUF3/6QqzO3b2+aOFt6F3E6sPVZFTKpagZHyAka1bXW6OJkw+I8JOJKOUP/UBmXbbzpGl0l0brwrI7nltNioRKviW1xiREs4P2pfwlra18bkPwbLoDum76uq+U3herFZGL+brnvEw+XwwqTBcjsevP1sWOeHNsnvC1oqOfqBj3/EnaP98y9Uo3n/7twCl73VvIhfgbdj/P3F/FZEajDVrX1ergMduqQDwkriFFz3SXM+e8B1vSdBclF/JORF0b+m16gW9I9OFn9UbfHxjWx5jHGdamYcDajB9aEUNrQDGJ8xuLpUdQ7V6izqY6OfUm5L78WmvSuZ25djfN2gUJg=; 31:NTwH3kv/tMeXloLQICWudGXH7uR/ZDAFD4CB0ZjV03ZU5rYxiV4VcfL9Ld62AtAwZuj/sudHVMMtwb6p9hOKp7bK5lorZrThvU/TlQSAaBA2Je5GYLrTIiS/iXj+kRLQRObLH8krjwi3FBJx4CglAKPggtRuIukdEUzk+MQGBUH2b/9poJh+x2ilaRDpwrFVGowFui5bPQ6e5F9dIpyb1abEdEgM3NEA9HIlpe/An/h93dzzJZF6u74hFZBG88LNNWs+WuR97h8Q4+RAyhLZZA==
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB0586; 20:0yTRwQiMSz7StvRYs4PrcW/4g/z+ME33iDm/9gFQfPRXJVV3m3thtQFJOIa8Bjtew3hNXKXurFakt6BurEAtrIHP+l0P578HJTtDSQxnrhYtRZOlAwmm3piOoSUyyxH61G1q9Gq69HXHezjfaPEEpi+mC5/qeetYj3ZSK8U20Ie1k+rx+yqQnSOGSCYZxTuJ4f4y7+V/KtiO/Vz47J87ubokYt1wb+dFZTPuaz6sWc3gGgwfvdwmPCAa/LKI97ENcA/YWGVfA/iOSQX0+2qvPrY0bvDGg6Za2ACP5y/aO7DXr4/YEQ8FDT6ujpnNzamDMBZ1rGDWec/d8/ve3y/ZWdgLM3Cz2kgX4Hu9hjXSbUo23QVv7+i1vhnfuqvhVxm75gFjiX3dzXeBvrVAu8muORq81bS+I773nI+EG2TVuPVYtHGncrVvCpx0FDOYgoTnVcjx3uNboDW+RPKaHIjqqsmo0yK7sQR8aAwbXZtsRjt00leP+F1/HKGjqa4m2rbcUC3Sp/n6bG+Q+CrXA3oHCPX8MR2dp8xwyOpIGvEW43i4q/mHxP57/GJtcoEWAToAxqlwUu3l1Rv9UuintTAUimhpUK31RC7U1srgq/JJDUw=
X-Microsoft-Antispam-PRVS: <DB3PR07MB05862C20825B2C04245F6A7A8DE50@DB3PR07MB0586.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(192374486261705);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700036)(100105000095)(100000701036)(100105300095)(100000702036)(100105100095)(6040450)(601004)(2401047)(5005006)(13018025)(8121501046)(13016025)(3002001)(100000703036)(100105400095)(10201501046)(93006095)(93004095)(6055026)(6041248)(20161123560025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123562025)(20161123558100)(6072148)(100000704036)(100105200095)(100000705036)(100105500095); SRVR:DB3PR07MB0586; BCL:0; PCL:0; RULEID:(100000800036)(100110000095)(100000801036)(100110300095)(100000802036)(100110100095)(100000803036)(100110400095)(100000804036)(100110200095)(100000805036)(100110500095); SRVR:DB3PR07MB0586; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQjNQUjA3TUIwNTg2OzQ6aVZBQTBiaEk1QUZ4c25ZdXorb3dHbUxpMFUr?= =?utf-8?B?a1FHamZlT0FrdjA1cVJYNWZiYm01VGZEdHNZSVp1TnNxenVTY2l3SStiNmRy?= =?utf-8?B?aHlzb1ordUFvN2FJdldONEJQNCt1M3dvQy9YUmVHM3MwMXpaMlVLd0J0a0lv?= =?utf-8?B?ZnFZU1ZKbVg4V1dkRld6VnM4WUQ0UnRnRDNZOWFlSGdlWDhYenI3dXpjTEZD?= =?utf-8?B?TkY2U0dYckNnaDZvb1BtYnIrRlhSTnlhTG1yY1dqS1RmYXlZM3c0UHB5N1hh?= =?utf-8?B?Z0tpN0NsRWNwNXd6emZDTDc1bkhVekJ6WjUydWdyMTk0aUhuVENWNEl1OEpE?= =?utf-8?B?RmpnMGMrZGdtQkFGRmFpaDVza0FDZHdTRUlqdFZQOEw5ZW5RS2Y4ZTlrZnVR?= =?utf-8?B?WmN6RVZwd0hsYzZoR2daQmloQnYyUWlQdmZjNGw1M0VvMi9QSm5GR21KWTdJ?= =?utf-8?B?ZjJXOHJyaTZIdTQ1bGlidFdTcnFqcmNUU2I0Ly9DdWRURld4SDE4cndaRnFL?= =?utf-8?B?T1BzSmRHdmtaTmU4RXlUcG43NnB4a21Vb1YycTJUakVsMzBUZ3JmWUw0djk0?= =?utf-8?B?MHFmSW8xS3hqTFRYV01Cdm9XYW0xTzREdDVaL2E5MkptVjJFbGVDaGhtV3l6?= =?utf-8?B?dHFDQmRmZHo2OCtVK2FiYXR1UGNLMldQbS93YjVQQkpETEFJZldnajB2N081?= =?utf-8?B?WUcrbzUrNHdsMnJVbk94SVBvTGtjR3Q4T3ZlZVp2Yyt5T3dweURXSUpJOHox?= =?utf-8?B?bkNPSjQ3cEhrQ29JZ3owVWVLZ1FZdUs1d0FIZ1E5M0tpdTh0U2RLeWtwVmlJ?= =?utf-8?B?SWR1bUJ0R1hxMEdLaDYyWXRDMkpGQ2lKcFpRcVdiMTFIMUhOcFJLNGxZbGM1?= =?utf-8?B?VUlJZE5KWDlGeS84SzJkRU9TRE8wSjdWVThFaE9BQnduODZ1RXZxdUxNZWl1?= =?utf-8?B?YndoWThoNE00bEJENStMQTZoVWZrN2ljVmNVMjgydHFsSnJRK0pvNEtscXFE?= =?utf-8?B?Z29iaWRVOUEzbE5aY3V6QVdVWFgycW1DUERYZWo1R0FJNUhVdC9YeUcxblk4?= =?utf-8?B?Ulo2RVRNQjVGeWVnalAyL25SODFsTkorY1k4czdUbzhxV1A3b1dhQkdIbnlr?= =?utf-8?B?SDE2OHZZdHpFMStoWnR4NitHTWVKWGUyUzB5SkdLakw0dlIzVEZMQWNkM3Zx?= =?utf-8?B?UHJLMlZYb2xqeStLU2lLSVRGaEZlS3JKa1lncmtyVmtNTmRsdUtGRzZDZzgw?= =?utf-8?B?SlZ6R0pGR3JKSXpyalFsa3JwSXpKYWtWbUw2REVJemtWTEJpdEtkbmo3Umk2?= =?utf-8?B?eFhXa25ZQ0E4MjJZWVNlSWF1Y0VTMnNuUWN4Q2orRzkycWJ3MldEN3NZb200?= =?utf-8?B?MFBzeU5uaDZQTVhzRFdmdExreEM5bDNqRFNqdVQ5OHJRNnJjOHVnWDVrQVN2?= =?utf-8?B?NWkycnBWbHRWVkcwcU5EOGZQMXdwTFZxdEMwdDhnZUVRTFJ3UjRVMURkUW12?= =?utf-8?B?TmE1VTlWaWVYK2xidHpoT000dlBDTVhJRHJvblFBdkd4WFovclFHaFhNaEhG?= =?utf-8?B?S21SVDkxM1hiVG43VGl0akZ1dFpNaks2cVNWSlFNTFRRcnpEVjdlcWYySXlZ?= =?utf-8?B?TnVhdHM0eTAyNjJndTc0Qkxnbjdsa2c2R0ZkOS8yc0lKSHROczNoMG9HUVY3?= =?utf-8?Q?XRCShn22j7XAw7PYA=3D?=
X-Forefront-PRVS: 031257FE13
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQjNQUjA3TUIwNTg2OzIzOlNINkt5WDFud29paVE0QVBrdnBLbldleFhV?= =?utf-8?B?eksxYlgxSUVlY1lTTWhpeGVXNXUwOTdiQXQ3OFRFUDU2L3E1dnk4K2ZhVDRt?= =?utf-8?B?QkErSk5DaktvYnVFYjRvYlJXbUpwMGZjZEVRY3p1SnZxQ0NOUENVT2swRjZC?= =?utf-8?B?RldVZXF6ZGZ1TDF6d3FCUE9YOXBCbCtZaURhZS96M0V5NEV2elBmMWNPd3FJ?= =?utf-8?B?cTNtdENCZjJOQTVQWFI4K2NaSDdBQ2crSjNvUTlxS1ZOVDRaTkZCTU5sSWNH?= =?utf-8?B?RVhIY2ZDbHF1WEJKdGdxM1Y4YWtramY4L0pnVStCSWY4YWdGdGltaVBncDVq?= =?utf-8?B?U0tvM0piV1c0b0VXWENEVUtUZTZSR3lnKy90MUpyemxFNkl5czNvK0NGZUxX?= =?utf-8?B?SHpFc2ZDRDc4c013M1lDMXhhcENrL21Iei9mZFhJc3hnT1loWko3cnN0MHV5?= =?utf-8?B?R2h1cmpLbHRua21tT0xRdVM4TTBFZWpBTVBUS3NBZDBKZGVWU2J3djh3Si9H?= =?utf-8?B?T3dmSVJLd25Fb2orckN1a01HSC9BNVFNZDgwZkFMRjMwcnRSTDBPSW5YN01X?= =?utf-8?B?cUlBSERUY3BBZDdoUzNydU5SSXNoMXhDOGhudzV4WGIrUzBDQVpsWHZRMWlD?= =?utf-8?B?MXN1VWdXMkNLQXh0NTF5c1dmTFRKdHdCSnhBbUluM3cxR0hQS0ppRTFxQUJX?= =?utf-8?B?elpnVEJiSWZkdVBhRXdiNUV3WHRTNkFPY3A4KzNJVnlzL2ZYSVNCb01PU3Rh?= =?utf-8?B?Q25pbXlJSVV2Rzl5K3kyajlUZytveFgwOFlZcEVnSE9RcVliY202QTlRZWtv?= =?utf-8?B?MWdSVEZYUTVWTE03ZkczR2VoU1F1b2FxbXhmaTFEd2NUeHBDOEtKSDRGZkRT?= =?utf-8?B?U3BwemJSUzQ2QktvNXhNUUs1enB6dzBTL2g0d3BFZFZRdVJRSklxYWErbGpC?= =?utf-8?B?cUhxajJCNGptUytESStWc3JKYXZMUzJRYzdJZ3lFNjJkNmxnUm4zNlZyR3NE?= =?utf-8?B?aEJpbTlRalQvV0xacnRqMEdQTTdwK2NHN2tmWDUyMXZJMDVnUDhNZ3ZmNDFi?= =?utf-8?B?R29VVlZ4Q3FIRy84Myttak4zbEtUMVlLQzFqeGliZzhuMWVNYXlrczJPUGtN?= =?utf-8?B?bWVaVzRPZEZHOTFLZG5jbFlaK0J6WmRWUjN5WlJEKzdnd0Nmcml6VGV1VUZk?= =?utf-8?B?dEs2Y0dyZWVjYmsrSURZOTMwcFQzd3NHbStmS0tVK2c2TEhuc2dweWhiRk5F?= =?utf-8?B?V3ZET2tEeVpFVmgzNDJkYWZuemVZUzNibFZXU1BJNE5FMmJ1bTZNa21qYUJ2?= =?utf-8?B?SHFjckhZVHE0TGVjNit2a1FwTElFa1R1ZUhDVzFhMUE4Z0lYbkJFem1XU1py?= =?utf-8?B?eHRubVE3QXhseFlPMS9jSVpKWlhzSmZRNjhIZHladU5PNE9PbExORlpsV3oz?= =?utf-8?B?K0hwTytZeERFaEdBdTlremRNcU9oRXZINkxqRWxJQ2ZHSTJQZFZITUtkMzc5?= =?utf-8?B?K1R2SzlmTzd6aHZXRHBLZlpsWnN1U1p0ekhUNWovWDdhOENRTXJyMUtQOW83?= =?utf-8?B?ekRCUXFJQ1lLYk9rTE81NXRUVHdMdkhEWGd3eWF4Q1p3dmIveTVwaEhiMkli?= =?utf-8?B?M1QxOTkzMGd5ZXBkTS8rQ25WVjM3aGxXV2VVK09UNm5tZk5pMHVzU0FpNk8w?= =?utf-8?Q?xiXX+20U7UbM7WLEVwPAcy9yac3pv3rIqNNZFfc?=
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB0586; 6:Gd4wrn7J0+roNLsyRqYR8N849QVwXUSaHZhyTfNSqSM574YNfRPw+WZeUg6cnJKS46QjG5FBxO8AK7YHDK38eo9RBfepuyKUYboYOZiQ5y71xI1cMYoRA8E6XnhXeLw/KZ3ruuRQkYS67ekld9iYeEjXfmwyT5WuLC8qLeehWZF15eBLOt3JNRyd1Fp9EUlbC4KtG9mev6vtEkzDgE9U0ZaDwylkAJJ+C0L5nM9XFnMlCK5s7fGbogFxBs7VfWbihVDZoOQCvcU/TfELu2x8jwej2L1/HNO81timgXyKzd2NBtuDOaidEQWEzK0Fe8qvyalMu1yQQYqK6Ox6p7jN5xaV4w5FTQlRGGBDqk02yVUPFJ4M3LnpraLjzX5jqz9aM/6jOi9Y8G+whBRezB925ftnEdFAYMoi1WMRrSGE63BipIDFW+Akx150dPP87YJZJoCEnjZhOgrbDQ/cxQqhWbf3Y49O2Q1qEY654S/KZwj0ZIBILVCibW/niqeXaOksP3ZyHJX8Jq5mNtIx0BPulvHkdKqbaU5a8c/D2MnU7LA=
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB0586; 5:HQx6u7Wru7j0QtoojU56L2/6b8YGOFPH2/pkMD0YNz75RLYNMktuXQSf7eVhq8go9pRoMxH5a1xm3WVg08MJK5jwXt4Hf7uaqmCBFyM5UKUaotoQN79KMAvwyjLaFNilgegyD4aHM2543a7LI8LTUW7b45iovBzUw3rqRs8qmlY3haESfU4dKLx7/3Rm+rsHSt7O0xxJJXVBlZdPT7KezwupczncdANJ9zENa0FIVWgT7tPAQMUmHt0hOoS/sSsT4uM1BStwxYsVLJrm8nZSHbKeS5+CwhW7U6nVipXbx0aeCDOVfQ6QAo5hmo0cfYWa6wCgYj6oGWMnxLIJUy53XgIInrkpev20KiVE7cQOb96ji3ND38ULSo39p/PFlSKjcw+Cq4mdEIufK+9LfC0qrUpFGil24gabq/5F+m1K+kkuYw3xHK+YXSp7ePuNn0J5JmGv8GbSJkHA5X/5f1TYMjr8UsA6eyk5EI/qldHzqMpVQO1bY+xdY5CYd4dH9aog; 24:ev4sjaTi5X+HgmkCDu//OmMrmPgBfLzjf9cgEgeFQTpbgyVw7Qf0lrzP0lpyDbi3EhP7vV91LtEv4LrxA52uAquC/BPPn8J57XpIkjBNDaY=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB0586; 7:FAFe1IW72xfnp7d0zBd2oZYG5YaMZX4c2Xm+dwOQo/s4il3ukyieFw9xL30BmkCKKEV/ujddMvyuVnCbvDQqpWZ723SUQxhA3+5ARyOUwpqXBFNPOo/vyOVqK30La/JwsGX/GiyLEHdghM1/n4BxZO3es+oeawcbfw2Ivgb0HBQj9+rELLIR5LX+HyFrDOqPCb21pgYT1IUPHZuOk3FievJk1Ffu2eatUmPKTJ7g2cx25zMSuu0cklKPKvVhRJeB2hYQ94YnSSAakZnLEUeeeAoWU7LdhIxOyMWobXtaKR0PPC8ad3eqWnL9aEL4NbsD26YFidZ5x8z4SyembyGnEA==
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 19 May 2017 08:13:54.8628 (UTC)
X-MS-Exchange-CrossTenant-Id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=5d471751-9675-428d-917b-70f44f9630b0; Ip=[135.245.241.12];  Helo=[fr711usmtp1-o.zeu.alcatel-lucent.com]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR07MB0586
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Rj1caW1CE7V9Fgb-YN7OiqOzEoA>
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, 19 May 2017 08:19:40 -0000

Russ,

Thanks for the review, I found all of your comments to be legitimate.

I'll upload an updated version in the coming days.

Thanks again,
Olivier.

On 05/12/2017 12:33 AM, Russ Housley wrote:
> Reviewer: Russ Housley
> Review result: Has Nits
>
> I 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 authors, document editors, and WG chairs should
> treat these comments just like any other IETF Last Call comments.
>
> Document: draft-ietf-pals-vpls-pim-snooping-05
> Reviewer: Russ Housley
> Review Date: 2016-05-11
> IETF LC End Date: 2017-05-19
> IESG Telechat date: Unknown
>
> Summary: Has Nits
>
> I did not review the state machines in detail.  I assume that others
> that are far more familiar with PIM have done s detailed review of
> them.
>
>
> No Major Concerns
>
>
> Minor Concerns
>
> Section 1 says:
>
>     In that case, the PW related concept/procedures are not
>     applicable and that's all.
>
> I am not sure what you are trying to tell the implementer.
> Please clarify.
>
> Section 1.3 includes: "rpt : Rendezvous Point", and Section 2.3
> includes: "Rendezvous Points (RP)".  Please pick one and use it
> throughout.
>
> In Section 2.2, please add a reference for the "split-horizon rule
> for mesh PWs" or add a pointer to the section where it is discussed
> further in this document.
>
> A better heading for Section 2.3.2 would be "IPv4 and IPv6".
>
>
> Nits
>
> Please change the language that makes reference to other "draft",
> such
> as: "As stated in the VPLS Multicast Requirements draft ...".  This
> wording leads to changes by the RFC Editor, so it is better to use a
> word like "document".
>
> Please change "J/P messages" to "Join/Prune messages" throughout the
> document.
>
> The document uses both "learned" and "learnt".  If there is a
> difference
> to the reader, it was too subtle for me to figure out.  If they are
> the
> same, please pick one.
>
> In Section 1.1, rewording would add clarity:
>
>     Depending on how the control messages are handled
>     (transparently flooded, selectively forwarded, aggregated), the
>     procedure/process may be called Snooping or proxy in different
>     contexts.
>
> I suggest:
>
>     Depending on whether the control messages are
>     transparently flooded, selectively forwarded, or aggregated, the
>     processing may be called Snooping or proxy in different contexts.
>
> Section 2.3 says:
>
>     However, the PE does not need to have any routing tables like as
>     required in PIM multicast routing.
>
> Please correct.  I think you are trying to say:
>
>     However, the PE does not need any routing tables like those
>     required in PIM multicast routing.
>
> Section 4.2.1 says:
>
>     Note that the differences apply only to PIM Join/Prune messages.
> PIM
>     Hello messages are snooped and flooded in all cases.
>
> Wouldn't it be more clear to consume the same number of lines and add
> this information to the table.
>
> In Section 2.7 the document uses PIM-BIDIR and BIDIR-PIM, and they
> seem
> have the same meaning.  Please pick one.
>
>


From nobody Fri May 19 07:17:17 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 1E01D127599; Fri, 19 May 2017 07:17:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.022
X-Spam-Level: 
X-Spam-Status: No, score=-5.022 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 xcwpNoj3WGy9; Fri, 19 May 2017 07:17:14 -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 76D761274D2; Fri, 19 May 2017 07:17:14 -0700 (PDT)
Received: from mail08.wdf.sap.corp (mail01.sap.corp [194.39.131.53]) (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 3wTqr84pCRz1KKD; Fri, 19 May 2017 16:17:12 +0200 (CEST)
X-purgate-ID: 152705::1495203432-0000521C-43C7610E/0/0
X-purgate-size: 2767
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 mail08.wdf.sap.corp (Postfix) with ESMTP id 3wTqr842gjz2ycn; Fri, 19 May 2017 16:17:12 +0200 (CEST)
Received: by ld9781.wdf.sap.corp (Postfix, from userid 10159) id 84D9A1A6A1; Fri, 19 May 2017 16:17:12 +0200 (CEST)
Subject: Re: [TLS] secdir review of draft-ietf-tls-ecdhe-psk-aead-03
In-Reply-To: <20170519043827.GL39245@kduck.kaduk.org>
To: Benjamin Kaduk <kaduk@mit.edu>
Date: Fri, 19 May 2017 16:17:12 +0200 (CEST)
CC: iesg@ietf.org, secdir@ietf.org,  draft-ietf-tls-ecdhe-psk-aead.all@ietf.org, tls@ietf.org, 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: <20170519141712.84D9A1A6A1@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ueUL2tXwQlzGJEPFwFVlc0egoIw>
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, 19 May 2017 14:17:16 -0000

Benjamin Kaduk wrote:
> 
> Some other editorial nits follow.
> 
> In section 4, "these cipher suites MUST NOT be negotiated in TLS
> versions prior to 1.2" should probably clarify that "these" cipher
> suites are the new ones specified by this document.


This reminds me of the specification goofs in several TLSv1.2-related
documents about AEAD cipher suites which are responsible for the viability
of the POODLE attack and other exploitable fallback hacks.

It would be much preferable to avoid/fix those problems and facilitate
the migration to and use of TLSv1.2 without failing TLS handshakes and
band aids such as TLS_FALLBACK_SCSV


Suggested improvement:

   The cipher suites defined in this document make use of the
   authenticated encryption with additional data (AEAD) defined in TLS
   1.2 [RFC5246] and DTLS 1.2 [RFC6347].  Earlier versions of TLS do not
   have support for AEAD and consequently, these cipher suites MUST NOT
-  be negotiated in TLS versions prior to 1.2.  Clients MUST NOT offer
-  these cipher suites if they do not offer TLS 1.2 or later.  Servers,
-  which select an earlier version of TLS MUST NOT select one of these
-  cipher suites.  A client MUST treat the selection of these cipher
-  suites in combination with a version of TLS that does not support
-  AEAD (i.e., TLS 1.1 or earlier) as an error and generate a fatal
-  'illegal_parameter' TLS alert.
+                                               A client that offers
+  the cipher suites from this document in ClientHello.cipher_suites
+  in combination with (3,1) "TLSv1.0" or (3,2) "TLSv1.1" in
+  ClientHello.client_version MUST support TLSv1.2 and MUST accept
+  the server to negotiate TLSv1.2 for the current session.  If the
+  client does not support TLSv1.2 or is not willing to negotiate TLSv1.2,
+  then this client MUST NOT offer any of these cipher suites with a
+  lower protocol version than (3,3) "TLSv1.2" in ClientHello.client_version.
+  A server receiving a ClientHello and a client_version indicating
+  (3,1) "TLSv1.0" or (3,2) "TLSv1.1" and any of the cipher suites from
+  this document in ClientHello.cipher_suites can safely assume that the
+  client supports TLSv1.2 and is willing to use it.  The server MUST
+  NOT negotiate these cipher suites with TLS protocol versions earlier
+  than TLSv1.2.
+
+  Not requiring clients to indicate their support for TLSv1.2 cipher
+  suites exclusively through ClientHello.client_hello improves the
+  interoperability in the installed base and use of TLSv1.2 AEAD
+  cipher suites without upsetting the installed base of version-intolerant
+  TLS servers, results in more TLS handshakes succeeding and obviates
+  fallback mechanisms.


-Martin


From nobody Fri May 19 07:40:24 2017
Return-Path: <bkaduk@akamai.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 1DB3512871F; Fri, 19 May 2017 07:40:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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=akamai.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 fwjujipgLvp8; Fri, 19 May 2017 07:40:03 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 151D6128616; Fri, 19 May 2017 07:40:02 -0700 (PDT)
Received: from pps.filterd (m0050096.ppops.net [127.0.0.1]) by m0050096.ppops.net-00190b01. (8.16.0.21/8.16.0.21) with SMTP id v4JEREhR018311; Fri, 19 May 2017 15:40:00 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=subject : to : cc : references : from : message-id : date : mime-version : in-reply-to : content-type; s=jan2016.eng; bh=nqaJ2c6f6nzUTZqHFNr++LfBDzLt1Zs6zhERmLXmwnM=; b=LSAimkt9tpudwA5d5o37bA9f3mwKATS8gWHvoVQG4FTxlYFVdEQbA4pMXNrUPVzQgS6d uxxFN3xzFw4TYbThRwtJK7uSUQ5qqdenPSutm0wp7PbjRHjiqG5Z47HJiqbp2m8G0Tgv J6kdGVpnCVm+1L7nNFYRz6Qq7KNetKVIz72O8lTs9Km/AckfMtIxEsZVLUdo0s9Fm4km QzpToK1goxFW+BMwGu+og5qjmmT91YvQq1oXuWKM57g+IEhFB8P+aj/hnV6urMCkR2DC oku68gECkN1USIWddNyGrDr+Kr0h2aO/sm7mDpEf+Fmpk+Uo0CbOjFP75TxVAKckHJdx eA== 
Received: from prod-mail-ppoint2 (a184-51-33-19.deploy.static.akamaitechnologies.com [184.51.33.19] (may be forged)) by m0050096.ppops.net-00190b01. with ESMTP id 2ahya7h2ju-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 19 May 2017 15:39:59 +0100
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.17/8.16.0.17) with SMTP id v4JEPUWZ028856; Fri, 19 May 2017 10:39:59 -0400
Received: from prod-mail-relay10.akamai.com ([172.27.118.251]) by prod-mail-ppoint2.akamai.com with ESMTP id 2adwfugd74-1; Fri, 19 May 2017 10:39:58 -0400
Received: from [172.19.17.86] (bos-lpczi.kendall.corp.akamai.com [172.19.17.86]) by prod-mail-relay10.akamai.com (Postfix) with ESMTP id 37EB01FC72; Fri, 19 May 2017 14:39:58 +0000 (GMT)
Subject: Re: [TLS] secdir review of draft-ietf-tls-ecdhe-psk-aead-03
To: Dave Garrett <davemgarrett@gmail.com>, tls@ietf.org
Cc: draft-ietf-tls-ecdhe-psk-aead.all@ietf.org, secdir@ietf.org, ietf@ietf.org, Benjamin Kaduk <kaduk@mit.edu>, iesg@ietf.org
References: <20170519043827.GL39245@kduck.kaduk.org> <201705190316.33316.davemgarrett@gmail.com>
From: Benjamin Kaduk <bkaduk@akamai.com>
Message-ID: <010db57b-37a9-a543-d33c-cc0dd7a75fcf@akamai.com>
Date: Fri, 19 May 2017 09:39:57 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <201705190316.33316.davemgarrett@gmail.com>
Content-Type: multipart/alternative; boundary="------------4C99548D51EF38DA6C013C38"
Content-Language: en-US
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-05-19_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1705190092
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-05-19_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default 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-1703280000 definitions=main-1705190092
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3wgtzmwisy7mk_yoHGiW8w1e9p0>
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, 19 May 2017 14:40:09 -0000

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

On 05/19/2017 02:16 AM, Dave Garrett wrote:
> On Friday, May 19, 2017 12:38:27 am Benjamin Kaduk wrote:
>> In section 4, "these cipher suites MUST NOT be negotiated in TLS
>> versions prior to 1.2" should probably clarify that "these" cipher
>> suites are the new ones specified by this document.
> Probably should be: "the cipher suites defined in this document
> MUST NOT be negotiated for any version of TLS other than 1.2."
>
> The sentence mentioning TLS 1.3+ could be moved up to right after
> and just say: "TLS version 1.3 and later negotiate these features in
> a different manner."
>
>

That's probably best, yes.  The interaction between this document and
TLS 1.3 is a little weird, and it's not entirely clear to me that this
one needs to say much of anything about TLS 1.3, given that TLS 1.3
changes all the relevant messages and key hierarchy and such.

-Ben

--------------4C99548D51EF38DA6C013C38
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">
    On 05/19/2017 02:16 AM, Dave Garrett wrote:<br>
    <blockquote type="cite"
      cite="mid:201705190316.33316.davemgarrett@gmail.com">
      <pre wrap="">On Friday, May 19, 2017 12:38:27 am Benjamin Kaduk wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">In section 4, "these cipher suites MUST NOT be negotiated in TLS
versions prior to 1.2" should probably clarify that "these" cipher
suites are the new ones specified by this document.
</pre>
      </blockquote>
      <pre wrap="">
Probably should be: "the cipher suites defined in this document
MUST NOT be negotiated for any version of TLS other than 1.2."

The sentence mentioning TLS 1.3+ could be moved up to right after
and just say: "TLS version 1.3 and later negotiate these features in
a different manner."


</pre>
    </blockquote>
    <br>
    That's probably best, yes.  The interaction between this document
    and TLS 1.3 is a little weird, and it's not entirely clear to me
    that this one needs to say much of anything about TLS 1.3, given
    that TLS 1.3 changes all the relevant messages and key hierarchy and
    such.<br>
    <br>
    -Ben<br>
  </body>
</html>

--------------4C99548D51EF38DA6C013C38--


From nobody Fri May 19 08:55:43 2017
Return-Path: <mglt.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 97E901294D8; Fri, 19 May 2017 08:55:41 -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 IePb0rm2HD51; Fri, 19 May 2017 08:55:38 -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 17B04129484; Fri, 19 May 2017 08:55:38 -0700 (PDT)
Received: by mail-lf0-x231.google.com with SMTP id 99so3338356lfu.1; Fri, 19 May 2017 08:55:37 -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=L+plUwKnFmIyg/bdkHFdC9zg9l6zsBn2dNJEtQP4xVY=; b=OSQ+ZqGcE/2bL57NRRhDieKYYUeBNWBBg2E6S6DFYfz88tYyXZEkHZNLBHMdqQ8Jc7 WbZiL65bMIesBTDfh+32SZxazGx3l6THtgI3uNT0GQGpttynE4cfwgpVC5j18jU3Vtxh Yrhz5Z6Umq4h0kNkWr3Rtooxjt7e8bjqlEMDlNEfCZY0QjzW0jGySVCR4ykay0ugoLbX yTj8GaHSJFPnwkuS3XwIWL8plxj3i8JFJSi+sSO1KhfiddfFJhPzZezqrrDtypW70aOh Gmg1SDciTUvf2ld2LAbollaPRQpsm9qDJ/lYnIh48fnSvOeC9tAqMrohd/K2aP5eZJTZ y7Qw==
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=L+plUwKnFmIyg/bdkHFdC9zg9l6zsBn2dNJEtQP4xVY=; b=HQ1nVYAOhArZTa/jmK0GNCKJvCNmOnAseIYcnZAggUSjC4txGl13VOhuqgejQx3i08 PKQ2qZHtKpRfotI+LjeSbvY6YNDicBYm/dapVR8C6uhGWbV/ZkTQUd1rpd0iJRh4xVO6 ftq07ULtpgPPVu4b9Hsmy3Dej6R3br0g/PMlLMHCcVEpYjtDz1WWGKayiq7RKPf1HyG/ vcFM0AHs7vA+qLxE41q30GWUUhgnagMiuQlvdEZ5qdAIi5sDXBGM0Nez/2tDWxCgxtS6 vpUO5CMfZOFIzhHS9ifsEuDj7oevfJZRpjX/cpPwvbQ6vEZNmcD5fAfy2RB6/CxC7KVq be8g==
X-Gm-Message-State: AODbwcCVtqG8TQp6ZCQqObtWF6Meu7zePAcPQd6ysO6TZ4mVRw8uSK+6 7xBGmHTguF4X/SLdnJtv6d7b7JzVW872
X-Received: by 10.25.228.197 with SMTP id x66mr2272178lfi.145.1495209336235; Fri, 19 May 2017 08:55:36 -0700 (PDT)
MIME-Version: 1.0
Sender: mglt.ietf@gmail.com
Received: by 10.46.0.14 with HTTP; Fri, 19 May 2017 08:55:35 -0700 (PDT)
In-Reply-To: <20170519043827.GL39245@kduck.kaduk.org>
References: <20170519043827.GL39245@kduck.kaduk.org>
From: Daniel Migault <daniel.migault@ericsson.com>
Date: Fri, 19 May 2017 11:55:35 -0400
X-Google-Sender-Auth: mkl0vhJtSKd0EsKUTBHbL0a9Xck
Message-ID: <CADZyTkncMTsTQt6C2S+Z0mw+30uc38bfrTSCOvjWRPn_dJkDLQ@mail.gmail.com>
Subject: Re: [TLS] secdir review of draft-ietf-tls-ecdhe-psk-aead-03
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, secdir@ietf.org,  draft-ietf-tls-ecdhe-psk-aead.all@ietf.org, tls <tls@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0e7d8859eec0054fe28dcd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4q0hCP-yU6zI3vVcZPhmpNGL3o8>
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, 19 May 2017 15:55:42 -0000

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

Hi Benjamin,

Thank you for the review. Please find my comments inline and let me know if
you agree with the proposed text. I believe the only point not addressed
concerns the addition of CCM-256 which has been remove after discussion
during the WGLC.

Thanks you for the review,

Yours,
Daniel

On Fri, May 19, 2017 at 12:38 AM, Benjamin Kaduk <kaduk@mit.edu> wrote:

> Hi all,
>
> 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.
>
> This document is ready with nits.
>
> Essentially, we are filling in a gap in the TLS (< 1.3) ciphersuite
> space, thought of as a cross product of key exchange and
> cipher+mac/AEAD -- we have some of the combinations (PSK with ECDHE
> but no AES-[GC]CM, PSK with AES-GCM but only non-EC DH, etc.) but
> not quite this one.
>
> That said, it seems a little silly to only partially fill the gap
> (by omitting the AES_256_CCM* cipher suites), even though there is
> not currently demand for them.
>
> MGLT: TLS_ECDHE_PSK_WITH_AES_256_CCM_8_SHA256 and
TLS_ECDHE_PSK_WITH_AES_256_CCM_SHA384  were mentioned in the 01 and removed
after  the WGLC. [0] The issue was whether or not introducing new ciphers
not supported by TLS1.3. In 01, we though of adding the code point for
TLS1.2 and then specify that TLS1.3 was only implementing a **subset** of
the cipher suites proposed.In case of needs these could still be supported
later by TLS1.3. The consensus seems to not introduce ciphers that would
not be handled by TLS1.3. If the WG decides otherwise, these could still be
added.

[0]
https://mailarchive.ietf.org/arch/msg/tls/M442CwmUMxrYJR8FjCh3h-a69o4/?qid=6e4713be1d71bae6718c6e6e6c4b8007




> This document is just assembling pieces that were already specified
> elsewhere, so it need not contain much detail itself, which is fine.
> That said, I think section 3 should probably state explicitly which
> pieces it uses, instead of a vague reference of being "based on RFC
> 4279".  So, "The ServerKeyExchange and ClientKeyExchange messages
> from RFC 5489 for ECDHE_PSK are used, and the premaster secret is
> computed in the same manner as for ECDHE_PSK key exchange in RFC
> 5489."  (I am not sure why RFC 4279 is cited in the current text; it
> does not cover ECDHE_PSK.)
>

MGLT: I agree we coudl be more explicit, here are the changes I propose. I
believe it address your purpose.

OLD:

Messages and pre-master secret construction in this
document are based on [RFC4279 <https://tools.ietf.org/html/rfc4279>].

NEW:

Messages and pre-master secret construction in this
document are defined in [RFC5489]. The ServerKeyExchange
and ClientKeyExchange messages and premaster secret is
computed as for  the ECDHE_PSK key exchange.


> The premaster_secret structure so used basically ends up putting the
> ECDH output first followed by the static PSK; with the pre-TLS 1.2
> PRF, that would give the ECDH shared secret to md5 and the PSK to
> sha1, which is perhaps another reason to not use these with pre-1.2
> worth mentioning (in addition to the AEAD availability).
>

MGLT: I believe the following text address your concern, however I am
wondering if we are not going beyond the scope of expected considerations.

In addition, it is worth noting that TLS1.0 <xref target="RFC2246"/> and
TL1.2 <xref target="RFC4346"/> splits the premaster in two parts. The PRF
results of mixing the two pseudorandom streams with distinct hash functions
(MD5 and SHA-1) by exclusive-ORing them together. In the case of ECDHE_PSK
authentication, the PSK and pre-master are treated by distinct hash
function with distinct properties. This may introduce vulnerabilities over
the expected security provided by the constructed pre-master. As such
TLS1.0 and TLS1.1 SHOULD NOT be used with ECDHE_PSK.


> The security considerations largely refer to those of the other
> documents providing the pieces that are combined together here;
> those referenced security considerations sections are more than
> adequate here, as this document itself does not really do anything
> particularly novel.  That said, if we are going to reiterate the
> entropy requirement for PSKs inline, we probably ought to also
> reiterate the nonce-reuse considerations for GCM and CCM.  The
> relevant constructions help, but there are still ways to mess up and
> reuse a nonce when doing crypto in parallel, if I remember the
> GCM/TLS document's security considerations correctly.
>

MGLT: I believe the following text address your comments.

 <t>GCM or CCM encryption - even of different clear text - re-using a
nonce with a same key undermines the security of GCM and CCM. As a
result, GCM and CCM MUST only be used with system guaranteeing nonce
uniqueness <xref target="RFC5116"/>.</t>


>
> Some other editorial nits follow.
>
> I see we're already discussing "perfect forward secrecy" vs.
> "forward secrecy"; my preference is for just "forward secrecy" (and
> I may have been one of the more active voices in causing TLS 1.3 to
> switch), but in the grand scheme of things it doesn't really matter.
>
> MGLT: perfect forward secrecy has been removed and replaced by forward
secrecy.


> In section 2, the RFC 7525 reference that "AEAD algorithms [...] are
> strongly recommended" is scoped to just (D)TLS, so the text here
> should probably also list that qualification.
>

MGLT: I believe the following text address your concern:

OLD text:
<t>AEAD algorithms that combine encryption and integrity protection are
strongly recommended for <xref target="RFC7525" /> and non-AEAD algorithms
are forbidden to use in TLS 1.3 <xref target="I-D.ietf-tls-tls13"/>.

NEW text:
<t>AEAD algorithms that combine encryption and integrity protection are
strongly recommended for (D)TLS <xref target="RFC7525" /> and non-AEAD
algorithms
are forbidden to use in TLS 1.3 <xref target="I-D.ietf-tls-tls13"/>.

> In section 4, "... make use of the authenticated encryption with
> additional data (AEAD) defined in TLS 1.2" seems to make AEAD into
> something of a unique object, as opposed to a class of things with
> multiple possible instantiations.  I would consider something like
> "... (AEAD) concept".
>
> In section 4, "these cipher suites MUST NOT be negotiated in TLS
> versions prior to 1.2" should probably clarify that "these" cipher
> suites are the new ones specified by this document.
>
> MGLT: I believe the following text address your comment:

OLD:
these cipher suites MUST NOT be negotiated in TLS  versions prior to 1.2.

NEW:
the cipher suites defined in this document MUST NOT be negotiated in TLS
versions prior to 1.2.

 OLD:
Clients MUST NOT offer these cipher suites

NEW:
Clients MUST NOT offer these cipher suites defined in this document



> s/Servers,\nwhich/Servers\nthat/
>
>
MGLT: Done


> Does the last paragraph of section 5 want a note "RFC Editor please
> remove this paragraph"?
>
> MGLT: Done


> Section 6, third paragraph, s/by using short PSK/by using a short
> PSK/.  Also, s/by a human and thus/by a human which thus/, maybe?
>
> MGLT: Probably ;-) done. thanks.


> Last paragraph page 4, comma after "i.e.".
>

MGLT: Added

>
>
> -Ben
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>

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

<div dir=3D"ltr"><div><div><div><div>Hi Benjamin, <br><br></div>Thank you f=
or the review. Please find my comments inline and let me know if you agree =
with the proposed text. I believe the only point not addressed concerns the=
 addition of CCM-256 which has been remove after discussion during the WGLC=
. <br><br></div>Thanks you for the review,<br><br></div>Yours, <br></div>Da=
niel<br><div><div><div><div class=3D"gmail_extra"><br><div class=3D"gmail_q=
uote">On Fri, May 19, 2017 at 12:38 AM, Benjamin Kaduk <span dir=3D"ltr">&l=
t;<a href=3D"mailto:kaduk@mit.edu" target=3D"_blank">kaduk@mit.edu</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 all,<=
br>
<br>
I have reviewed this document as part of the security directorate&#39;s<br>
ongoing effort to review all IETF documents being processed by the<br>
IESG.=C2=A0 These comments were written primarily for the benefit of the<br=
>
security area directors.=C2=A0 Document editors and WG chairs should<br>
treat these comments just like any other last call comments.<br>
<br>
This document is ready with nits.<br>
<br>
Essentially, we are filling in a gap in the TLS (&lt; 1.3) ciphersuite<br>
space, thought of as a cross product of key exchange and<br>
cipher+mac/AEAD -- we have some of the combinations (PSK with ECDHE<br>
but no AES-[GC]CM, PSK with AES-GCM but only non-EC DH, etc.) but<br>
not quite this one.<br>
<br>
That said, it seems a little silly to only partially fill the gap<br>
(by omitting the AES_256_CCM* cipher suites), even though there is<br>
not currently demand for them.<br>
<br></blockquote><div>MGLT: TLS_ECDHE_PSK_WITH_AES_256_CCM_8_SHA256 and  TL=
S_ECDHE_PSK_WITH_AES_256_CCM_SHA384=C2=A0 were mentioned in the 01 and remo=
ved after=C2=A0 the WGLC. [0] The issue was whether or not introducing new =
ciphers not supported by TLS1.3. In 01, we though of adding the code point =
for TLS1.2 and then specify that TLS1.3 was only implementing a **subset** =
of the cipher suites proposed.In case of needs these could still be support=
ed later by TLS1.3. The consensus seems to not introduce ciphers that would=
 not be handled by TLS1.3. If the WG decides otherwise, these could still b=
e added.=C2=A0 =C2=A0 <br><br>[0] <a href=3D"https://mailarchive.ietf.org/a=
rch/msg/tls/M442CwmUMxrYJR8FjCh3h-a69o4/?qid=3D6e4713be1d71bae6718c6e6e6c4b=
8007">https://mailarchive.ietf.org/arch/msg/tls/M442CwmUMxrYJR8FjCh3h-a69o4=
/?qid=3D6e4713be1d71bae6718c6e6e6c4b8007</a><br><br><br></div><div>=C2=A0</=
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">
This document is just assembling pieces that were already specified<br>
elsewhere, so it need not contain much detail itself, which is fine.<br>
That said, I think section 3 should probably state explicitly which<br>
pieces it uses, instead of a vague reference of being &quot;based on RFC<br=
>
4279&quot;.=C2=A0 So, &quot;The ServerKeyExchange and ClientKeyExchange mes=
sages<br>
from RFC 5489 for ECDHE_PSK are used, and the premaster secret is<br>
computed in the same manner as for ECDHE_PSK key exchange in RFC<br>
5489.&quot;=C2=A0 (I am not sure why RFC 4279 is cited in the current text;=
 it<br>
does not cover ECDHE_PSK.)<br></blockquote><div><br></div><div>MGLT: I agre=
e we coudl be more explicit, here are the changes I propose. I believe it a=
ddress your purpose. <br><br></div><div>OLD:<br><pre class=3D"gmail-newpage=
">Messages and pre-master secret construction in this <br>document are base=
d on [<a href=3D"https://tools.ietf.org/html/rfc4279" title=3D"&quot;Pre-Sh=
ared Key Ciphersuites for Transport Layer Security (TLS)&quot;">RFC4279</a>=
].<br><br></pre></div><div>NEW:<br><pre class=3D"gmail-newpage">Messages an=
d pre-master secret construction in this <br>document are defined in [RFC54=
89]. The ServerKeyExchange<br>and ClientKeyExchange messages and premaster =
secret is <br>computed as for  the ECDHE_PSK key exchange. =C2=A0<br></pre>=
</div><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">
<br>
The premaster_secret structure so used basically ends up putting the<br>
ECDH output first followed by the static PSK; with the pre-TLS 1.2<br>
PRF, that would give the ECDH shared secret to md5 and the PSK to<br>
sha1, which is perhaps another reason to not use these with pre-1.2<br>
worth mentioning (in addition to the AEAD availability).<br></blockquote><d=
iv><br></div><div>MGLT: I believe the following text address your concern, =
however I am wondering if we are not going beyond the scope of expected con=
siderations.=C2=A0 <br><br></div><div>In addition, it is worth noting that =
TLS1.0 &lt;xref target=3D&quot;RFC2246&quot;/&gt; and TL1.2 &lt;xref target=
=3D&quot;RFC4346&quot;/&gt; splits the premaster in two parts. The PRF resu=
lts of mixing the two pseudorandom streams with distinct hash functions (MD=
5 and SHA-1) by exclusive-ORing them together. In the case of ECDHE_PSK aut=
hentication, the PSK and pre-master are treated by distinct hash function w=
ith distinct properties. This may introduce vulnerabilities over the expect=
ed security provided by the constructed pre-master. As such TLS1.0 and TLS1=
.1 SHOULD NOT be used with ECDHE_PSK. </div><div>=C2=A0</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex">
The security considerations largely refer to those of the other<br>
documents providing the pieces that are combined together here;<br>
those referenced security considerations sections are more than<br>
adequate here, as this document itself does not really do anything<br>
particularly novel.=C2=A0 That said, if we are going to reiterate the<br>
entropy requirement for PSKs inline, we probably ought to also<br>
reiterate the nonce-reuse considerations for GCM and CCM.=C2=A0 The<br>
relevant constructions help, but there are still ways to mess up and<br>
reuse a nonce when doing crypto in parallel, if I remember the<br>
GCM/TLS document&#39;s security considerations correctly.<br></blockquote><=
div><br>MGLT: I believe the following text address your comments.<br><br>=
=C2=A0&lt;t&gt;GCM or CCM encryption - even of different clear text - re-us=
ing a <br>nonce with a same key undermines the security of GCM and CCM. As =
a<br>result, GCM and CCM MUST only be used with system guaranteeing nonce<b=
r>uniqueness &lt;xref target=3D&quot;RFC5116&quot;/&gt;.&lt;/t&gt;<br><br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
Some other editorial nits follow.<br>
<br>
I see we&#39;re already discussing &quot;perfect forward secrecy&quot; vs.<=
br>
&quot;forward secrecy&quot;; my preference is for just &quot;forward secrec=
y&quot; (and<br>
I may have been one of the more active voices in causing TLS 1.3 to<br>
switch), but in the grand scheme of things it doesn&#39;t really matter.<br=
>
<br></blockquote><div>MGLT: perfect forward secrecy has been removed and re=
placed by forward secrecy.<br>=C2=A0<br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex">
In section 2, the RFC 7525 reference that &quot;AEAD algorithms [...] are<b=
r>
strongly recommended&quot; is scoped to just (D)TLS, so the text here<br>
should probably also list that qualification.<br></blockquote><div>=C2=A0<b=
r></div><div>MGLT: I believe the following text address your concern:<br><b=
r></div><div>OLD text: <br>&lt;t&gt;AEAD algorithms that combine encryption=
 and integrity protection are<br>strongly recommended for &lt;xref target=
=3D&quot;RFC7525&quot; /&gt; and non-AEAD algorithms<br>are forbidden to us=
e in TLS 1.3 &lt;xref target=3D&quot;I-D.ietf-tls-tls13&quot;/&gt;. <br><br=
></div><div>NEW text:<br>&lt;t&gt;AEAD algorithms that combine encryption a=
nd integrity protection are<br>strongly recommended for (D)TLS &lt;xref tar=
get=3D&quot;RFC7525&quot; /&gt; and non-AEAD algorithms<br>are forbidden to=
 use in TLS 1.3 &lt;xref target=3D&quot;I-D.ietf-tls-tls13&quot;/&gt;. <br>=
</div><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">
In section 4, &quot;... make use of the authenticated encryption with<br>
additional data (AEAD) defined in TLS 1.2&quot; seems to make AEAD into<br>
something of a unique object, as opposed to a class of things with<br>
multiple possible instantiations.=C2=A0 I would consider something like<br>
&quot;... (AEAD) concept&quot;.<br>
<br>
In section 4, &quot;these cipher suites MUST NOT be negotiated in TLS<br>
versions prior to 1.2&quot; should probably clarify that &quot;these&quot; =
cipher<br>
suites are the new ones specified by this document.<br>
<br></blockquote><div>MGLT: I believe the following text address your comme=
nt:<br><br></div><div>OLD:<br>these cipher suites MUST NOT be negotiated in=
 TLS=C2=A0 versions prior to 1.2.<br><br></div><div>NEW:<br>the cipher suit=
es defined in this document MUST NOT be negotiated in TLS <br>versions prio=
r to 1.2.<br><br></div><div>=C2=A0OLD:<br>Clients MUST NOT offer these ciph=
er suites <br><br></div><div>NEW: <br>Clients MUST NOT offer these cipher s=
uites defined in this document <br></div><div><br>=C2=A0 <br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex">
s/Servers,\nwhich/Servers\<wbr>nthat/<br>
<br></blockquote><div><br></div><div>MGLT: Done<br>=C2=A0<br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex">
Does the last paragraph of section 5 want a note &quot;RFC Editor please<br=
>
remove this paragraph&quot;?<br>
<br></blockquote><div>MGLT: Done<br>=C2=A0<br></div><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">
Section 6, third paragraph, s/by using short PSK/by using a short<br>
PSK/.=C2=A0 Also, s/by a human and thus/by a human which thus/, maybe?<br>
<br></blockquote><div>MGLT: Probably ;-) done. thanks.<br>=C2=A0<br></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">
Last paragraph page 4, comma after &quot;i.e.&quot;.<br></blockquote><div><=
br></div><div>MGLT: Added <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>
<br>
-Ben<br>
<br>
______________________________<wbr>_________________<br>
TLS mailing list<br>
<a href=3D"mailto:TLS@ietf.org">TLS@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tls" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/tls</a><br>
</blockquote></div><br></div></div></div></div></div>

--94eb2c0e7d8859eec0054fe28dcd--


From nobody Fri May 19 09:08:04 2017
Return-Path: <mglt.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 27D681294EC; Fri, 19 May 2017 09:07:41 -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 PCfPhlC85vcB; Fri, 19 May 2017 09:07:39 -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 0CB561294A4; Fri, 19 May 2017 09:07:39 -0700 (PDT)
Received: by mail-lf0-x22d.google.com with SMTP id h4so3511215lfj.3; Fri, 19 May 2017 09:07:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=uwHBmfuU4afjEOllwHYg5B3VzGqkeebVf6XvE+EY0gg=; b=PO7WgfJRI5Y2h5a5x+4Z48haRK7enlYhKEX82+icO7n1mXyV5LjnAMlkEKk8fxjSWz 0+jvf7sEfKtlfVuiiTLACjUsvyfQkiXTmfyx9+i+qErhswNaQ3CSyeA1YdCJvI4GU0Zn wasg2WwNIH6Mzx+NFCyywmA/GqQYfgeTmyxyt6E0l+zTHS8W3l+5XXEVLqvL4c535EOJ roVDEwTB/rrT+TjPv6DhSKU5JPNlvdHzK2GHmBa/MLwo7q43n2rQSEf5Ld4TT2Lw5TOt uLsg9L4mTEyeKkZVHW3xCYLxhNToAHy6IsuRNcDProQyaqvlaPHfbyHCzR70vDCTJ4gi C/QA==
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=uwHBmfuU4afjEOllwHYg5B3VzGqkeebVf6XvE+EY0gg=; b=jcE9OllRpEQvmDUK1qHMHPaF4cRWxb6b7K8a6D7knpGDQoYa4hb9bSn7PP2qkPKZhy kPmeVXUU6/krEFWdSXaKRe8AoDZim750iPbRXHyViaesNYSbAHn2rlAYxwQOmdWfGzaN +/KAliemmMBtDD2ZlUu5mJMu0BZM5o8OAejs73kzwic248aUAOGJiBSC5e4mq/JHaLjX UsUM3xy0Vz+3g54RSqIsUy+NobKhahCr9U9CkDo7FFjVzVRxhxs9w9fK8tNwXVwONqCw /Ak15+sViJxy7TzRfa1jNKytQ2mq2fyBMHQXKotof7YHkAlGw4bFGOB8YgxFeifX8tZh CqGQ==
X-Gm-Message-State: AODbwcAQaJZNqMAwWyonSD+mhrlgw3B0A/VEGis8np0z/FzsIfn/ut7C LZhl8xdQk0a+isiKe/At5gS06a1JVw==
X-Received: by 10.25.193.145 with SMTP id r139mr1531754lff.111.1495210057237;  Fri, 19 May 2017 09:07:37 -0700 (PDT)
MIME-Version: 1.0
Sender: mglt.ietf@gmail.com
Received: by 10.46.0.14 with HTTP; Fri, 19 May 2017 09:07:36 -0700 (PDT)
In-Reply-To: <010db57b-37a9-a543-d33c-cc0dd7a75fcf@akamai.com>
References: <20170519043827.GL39245@kduck.kaduk.org> <201705190316.33316.davemgarrett@gmail.com> <010db57b-37a9-a543-d33c-cc0dd7a75fcf@akamai.com>
From: Daniel Migault <daniel.migault@ericsson.com>
Date: Fri, 19 May 2017 12:07:36 -0400
X-Google-Sender-Auth: 9qEQEUqd_BBy51at4x7pj0L4Fqc
Message-ID: <CADZyTknj9HrEW+ZwCgoVvsV3cQMk_m+H9_QGVL6-aO_1OMx5Zw@mail.gmail.com>
Subject: Re: [TLS] secdir review of draft-ietf-tls-ecdhe-psk-aead-03
To: Benjamin Kaduk <bkaduk@akamai.com>
Cc: Dave Garrett <davemgarrett@gmail.com>, tls <tls@ietf.org>, The IESG <iesg@ietf.org>,  Benjamin Kaduk <kaduk@mit.edu>, draft-ietf-tls-ecdhe-psk-aead.all@ietf.org,  "ietf@ietf.org" <ietf@ietf.org>, secdir@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c1a0878538d39054fe2b8a6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KYQz2RrU6KwKKvcRWxeYg5ZtU54>
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, 19 May 2017 16:07:41 -0000

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

Hi Benjamin and Dave,

Thanks for the clarification. Considering also Roman' s and Ben' s comments
the section is built as follow. 1) Limit cipher suites to TLS1.2, 2)
explain how TLS1.3 and higher version negotiate them 3) bring all
explanation foe the previous versions.

Yours,
Daniel

The text is as follows:

<t> The cipher suites defined in this document MUST NOT be negotiated
for any version of (D)TLS other than TLS1.2.</t>

<t> TLS version 1.3 and later negotiate these features in a different
manner. Unlike TLS1.2, TLS1.3 separates authentication and cipher suite
negotiation <xref target="I-D.ietf-tls-tls13"/> Section 1.2. TLS1.3
supports PSK with ECDHE key exchange and the cipher suites
TLS_AES_128_GCM_SHA256, TLS_AES_256_GCM_SHA384, TLS_AES_128_CCM_8_SHA256
and  TLS_AES_128_CCM_SHA256 are part of the specification. As a result,
TLS 1.3 and higher versions, negotiate and support these cipher suites
in a different way. </t>

<t>The cipher suites defined in this document make use of the
authenticated encryption with additional data (AEAD) defined in TLS 1.2
<xref target="RFC5246"/> and DTLS 1.2 <xref target="RFC6347" />.
Earlier versions of TLS do not have support for AEAD and consequently,
the cipher suites defined in this document MUST NOT be negotiated in TLS
versions prior to 1.2.  In addition, it is worth noting that TLS1.0
<xref target="RFC2246"/> and TL1.2 <xref target="RFC4346"/> splits teh
pre-master in two parts. The PRF results of mixing the two pseudorandom
streams with distinct hash functions (MD5 and SHA-1) by exclusive-ORing
them together. In the case of ECDHE_PSK authentication, the PSK and
pre-master are treated by distinct hash function with distinct
properties. This may introduce vulnerabilities over the expected
security provided by the constructed pre-master. As such TLS1.0 and
TLS1.1 SHOULD NOT be used with ECDHE_PSK.  Clients MUST NOT offer these
cipher suites defined in this document if they do not offer TLS 1.2 or
later. Servers that select an earlier version of TLS MUST NOT select one
of these cipher suites. A client MUST treat the selection of these
cipher suites in combination with a version of TLS that does not support
AEAD (i.e., TLS 1.1 or earlier) as an error and generate a fatal
'illegal_parameter' TLS alert.</t>




On Fri, May 19, 2017 at 10:39 AM, Benjamin Kaduk <bkaduk@akamai.com> wrote:

> On 05/19/2017 02:16 AM, Dave Garrett wrote:
>
> On Friday, May 19, 2017 12:38:27 am Benjamin Kaduk wrote:
>
> In section 4, "these cipher suites MUST NOT be negotiated in TLS
> versions prior to 1.2" should probably clarify that "these" cipher
> suites are the new ones specified by this document.
>
> Probably should be: "the cipher suites defined in this document
> MUST NOT be negotiated for any version of TLS other than 1.2."
>
> The sentence mentioning TLS 1.3+ could be moved up to right after
> and just say: "TLS version 1.3 and later negotiate these features in
> a different manner."
>
>
>
>
> That's probably best, yes.  The interaction between this document and TLS
> 1.3 is a little weird, and it's not entirely clear to me that this one
> needs to say much of anything about TLS 1.3, given that TLS 1.3 changes all
> the relevant messages and key hierarchy and such.
>
> -Ben
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>
>

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

<div dir=3D"ltr"><div><div>Hi Benjamin and Dave, <br><br></div>Thanks for t=
he clarification. Considering also Roman&#39; s and Ben&#39; s comments the=
 section is built as follow. 1) Limit cipher suites to TLS1.2, 2) explain h=
ow TLS1.3 and higher version negotiate them 3) bring all explanation foe th=
e previous versions.<br><br></div><div>Yours, <br></div><div>Daniel<br><br>=
</div>The text is as follows:<br><br>&lt;t&gt; The cipher suites defined in=
 this document MUST NOT be negotiated<br>for any version of (D)TLS other th=
an TLS1.2.&lt;/t&gt;<br><br>&lt;t&gt; TLS version 1.3 and later negotiate t=
hese features in a different<br>manner. Unlike TLS1.2, TLS1.3 separates aut=
hentication and cipher suite<br>negotiation &lt;xref target=3D&quot;I-D.iet=
f-tls-tls13&quot;/&gt; Section 1.2. TLS1.3<br>supports PSK with ECDHE key e=
xchange and the cipher suites<br>TLS_AES_128_GCM_SHA256, TLS_AES_256_GCM_SH=
A384, TLS_AES_128_CCM_8_SHA256 <br>and=C2=A0 TLS_AES_128_CCM_SHA256 are par=
t of the specification. As a result,<br>TLS 1.3 and higher versions, negoti=
ate and support these cipher suites<br>in a different way. &lt;/t&gt;<br><b=
r>&lt;t&gt;The cipher suites defined in this document make use of the<br>au=
thenticated encryption with additional data (AEAD) defined in TLS 1.2<br>&l=
t;xref target=3D&quot;RFC5246&quot;/&gt; and DTLS 1.2 &lt;xref target=3D&qu=
ot;RFC6347&quot; /&gt;.<br>Earlier versions of TLS do not have support for =
AEAD and consequently,<br>the cipher suites defined in this document MUST N=
OT be negotiated in TLS<br>versions prior to 1.2.=C2=A0 In addition, it is =
worth noting that TLS1.0<br>&lt;xref target=3D&quot;RFC2246&quot;/&gt; and =
TL1.2 &lt;xref target=3D&quot;RFC4346&quot;/&gt; splits teh<br>pre-master i=
n two parts. The PRF results of mixing the two pseudorandom<br>streams with=
 distinct hash functions (MD5 and SHA-1) by exclusive-ORing<br>them togethe=
r. In the case of ECDHE_PSK authentication, the PSK and<br>pre-master are t=
reated by distinct hash function with distinct<br>properties. This may intr=
oduce vulnerabilities over the expected<br>security provided by the constru=
cted pre-master. As such TLS1.0 and<br>TLS1.1 SHOULD NOT be used with ECDHE=
_PSK.=C2=A0 Clients MUST NOT offer these<br>cipher suites defined in this d=
ocument if they do not offer TLS 1.2 or<br>later. Servers that select an ea=
rlier version of TLS MUST NOT select one<br>of these cipher suites. A clien=
t MUST treat the selection of these<br>cipher suites in combination with a =
version of TLS that does not support<br>AEAD (i.e., TLS 1.1 or earlier) as =
an error and generate a fatal <br>&#39;illegal_parameter&#39; TLS alert.&lt=
;/t&gt;<br><br>=C2=A0 <br><div><div><br><div><div class=3D"gmail_extra"><br=
><div class=3D"gmail_quote">On Fri, May 19, 2017 at 10:39 AM, Benjamin Kadu=
k <span dir=3D"ltr">&lt;<a href=3D"mailto:bkaduk@akamai.com" target=3D"_bla=
nk">bkaduk@akamai.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF"><span class=3D"gmail-">
    On 05/19/2017 02:16 AM, Dave Garrett wrote:<br>
    <blockquote type=3D"cite">
      <pre>On Friday, May 19, 2017 12:38:27 am Benjamin Kaduk wrote:
</pre>
      <blockquote type=3D"cite">
        <pre>In section 4, &quot;these cipher suites MUST NOT be negotiated=
 in TLS
versions prior to 1.2&quot; should probably clarify that &quot;these&quot; =
cipher
suites are the new ones specified by this document.
</pre>
      </blockquote>
      <pre>Probably should be: &quot;the cipher suites defined in this docu=
ment
MUST NOT be negotiated for any version of TLS other than 1.2.&quot;

The sentence mentioning TLS 1.3+ could be moved up to right after
and just say: &quot;TLS version 1.3 and later negotiate these features in
a different manner.&quot;


</pre>
    </blockquote>
    <br></span>
    That&#39;s probably best, yes.=C2=A0 The interaction between this docum=
ent
    and TLS 1.3 is a little weird, and it&#39;s not entirely clear to me
    that this one needs to say much of anything about TLS 1.3, given
    that TLS 1.3 changes all the relevant messages and key hierarchy and
    such.<br>
    <br>
    -Ben<br>
  </div>

<br>______________________________<wbr>_________________<br>
TLS mailing list<br>
<a href=3D"mailto:TLS@ietf.org">TLS@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tls" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/tls</a><br>
<br></blockquote></div><br></div></div></div></div></div>

--94eb2c1a0878538d39054fe2b8a6--


From nobody Fri May 19 09:25:59 2017
Return-Path: <mglt.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 BCFF712955F; Fri, 19 May 2017 09:25:56 -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 R5W5i34hUVr6; Fri, 19 May 2017 09:25:54 -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 A8C441294F3; Fri, 19 May 2017 09:25:53 -0700 (PDT)
Received: by mail-lf0-x232.google.com with SMTP id y126so3711035lfc.2; Fri, 19 May 2017 09:25:53 -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=bE8IPZygLAJ0pGuNryzThjkvrgswGRp2YcsgJ+gq/Rw=; b=iBczSge/YhesrK4a3UJvGU4UHTlmhhzglARpMLvX/+TDV7JuP4sGmK/8hvdcpRMgc7 OTOvCJ/oM5v+JdmmFxGKoL/5ImGrIaC3iKJ2+8QjBQBayrfz1i7FVvrNo0+laugh0ZrZ kOSi8txkxz7IbpMe2RFhaWhtS1nsQ4Er5kDMkCIDLfRiwE/xIEWjaAg2bZoQT3MvNlnb yGondVLxCcJ7ZJqBqYzC9HtzCXf8UA+WGcskSH9cmQ4En9dmJPmBTjCBIg3GiHSxpreM ucJcnwm7smgOIDNwPUtrNW5aJgO0DFn+pBskjGQvAVUBo8Eya9LHTpjKCW71jP78ng0D bBLg==
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=bE8IPZygLAJ0pGuNryzThjkvrgswGRp2YcsgJ+gq/Rw=; b=m/n42gDzlb3okWAzofhnc4nXIMYgO6GB3IxUWBri8M+tnqJRSdTpPvrDsAsPBSeeul ger5hE2H++WEHPhmLjMdJzV4i1EW36a00eDCiHHdoYH/GLYDGfx6wf5y4kPG6GHwc2/o XnGa9GvJb/biZfho8YSVe2MeciDziiQuBs3Fhwo+XuatF/8c0OHYNJcG7eFC0oI1XyqS DLt4KGx1mx1blGiCixHN5MH+EdSpWdDtKtDCmeKGA5Rri8PcGqIjMvBP0u3zjXwMBWwu jX0qjzHMFvGmkhTCtbbZ+cGe1IqQSDfs7dBHL8VdT+Iyc/lU1NbpFI/jh7sdqOC3dalb pcTA==
X-Gm-Message-State: AODbwcCBSP/jpEaaINwznvPwwiGzuoEh5N7VbglxFiplsfTfKGxgUxcO 1ZedHvywuQxWKsRa8SP2+Zmy/gpDdA==
X-Received: by 10.25.229.69 with SMTP id c66mr2783915lfh.102.1495211151786; Fri, 19 May 2017 09:25:51 -0700 (PDT)
MIME-Version: 1.0
Sender: mglt.ietf@gmail.com
Received: by 10.46.0.14 with HTTP; Fri, 19 May 2017 09:25:51 -0700 (PDT)
In-Reply-To: <20170519141712.84D9A1A6A1@ld9781.wdf.sap.corp>
References: <20170519043827.GL39245@kduck.kaduk.org> <20170519141712.84D9A1A6A1@ld9781.wdf.sap.corp>
From: Daniel Migault <daniel.migault@ericsson.com>
Date: Fri, 19 May 2017 12:25:51 -0400
X-Google-Sender-Auth: WPgY13FdGIvJnTffCNRBub0cj_Q
Message-ID: <CADZyTkkU0pyJtoZXmnC6WwPZ_6oQfpYU8Ax77-8WPK4cE1UJ7w@mail.gmail.com>
Subject: Re: [TLS] secdir review of draft-ietf-tls-ecdhe-psk-aead-03
To: mrex@sap.com
Cc: Benjamin Kaduk <kaduk@mit.edu>, tls <tls@ietf.org>,  draft-ietf-tls-ecdhe-psk-aead.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>,  The IESG <iesg@ietf.org>, secdir@ietf.org
Content-Type: multipart/alternative; boundary="001a113c0cb2910d10054fe2f9e6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tCZR-vcOHg4Fl1U_rCGgvZTcCFc>
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, 19 May 2017 16:25:57 -0000

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

Hi Martin,

Thank you for the proposed text. It was very clear and I took it entirely,
just changing s/TLSv1/TLS 1/.

Yours,
Daniel


The current text is as follows:
<section title="Applicable TLS Versions">


<t> The cipher suites defined in this document MUST NOT be negotiated
for any version of (D)TLS other than TLS 1.2.</t>

<t> TLS version 1.3 and later negotiate these features in a different
manner. Unlike TLS 1.2, TLS 1.3 separates authentication and cipher suite
negotiation <xref target="I-D.ietf-tls-tls13"/> Section 1.2. TLS 1.3
supports PSK with ECDHE key exchange and the cipher suites
TLS_AES_128_GCM_SHA256, TLS_AES_256_GCM_SHA384, TLS_AES_128_CCM_8_SHA256
and  TLS_AES_128_CCM_SHA256 are part of the specification. As a result,
TLS 1.3 and higher versions, negotiate and support these cipher suites
in a different way. </t>

<t>The cipher suites defined in this document make use of the
authenticated encryption with additional data (AEAD) defined in TLS 1.2
<xref target="RFC5246"/> and DTLS 1.2 <xref target="RFC6347" />.
Earlier versions of TLS do not have support for AEAD and consequently,
the cipher suites defined in this document MUST NOT be negotiated in TLS
versions prior to 1.2.  In addition, it is worth noting that TLS 1.0
<xref target="RFC2246"/> and TL1.2 <xref target="RFC4346"/> splits the
pre-master in two parts. The PRF results of mixing the two pseudorandom
streams with distinct hash functions (MD5 and SHA-1) by exclusive-ORing
them together. In the case of ECDHE_PSK authentication, the PSK and
pre-master are treated by distinct hash function with distinct
properties. This may introduce vulnerabilities over the expected
security provided by the constructed pre-master. As such TLS 1.0 and
TLS 1.1 SHOULD NOT be used with ECDHE_PSK.</t>

<t>A client that offers the cipher suites from this document in
ClientHello.cipher_suites in combination with (3,1) "TLS 1.0" or (3,2)
"TLS 1.1" in ClientHello.client_version MUST support TLS 1.2 and MUST
accept the server to negotiate TLS 1.2 for the current session.  If the
client does not support TLS 1.2 or is not willing to negotiate TLS 1.2,
then this client MUST NOT offer any of these cipher suites with a lower
protocol version than (3,3) "TLS 1.2" in ClientHello.client_version.</t>

<t>A server receiving a ClientHello and a client_version indicating
(3,1) "TLS 1.0" or (3,2) "TLS 1.1" and any of the cipher suites from
this document in ClientHello.cipher_suites can safely assume that the
client supports TLS 1.2 and is willing to use it. The server MUST NOT
negotiate these cipher suites with TLS protocol versions earlier than
TLS 1.2. Not requiring clients to indicate their support for TLS 1.2
cipher suites exclusively through ClientHello.client_hello improves the
interoperability in the installed base and use of TLS 1.2 AEAD cipher
suites without upsetting the installed base of version-intolerant TLS
servers, results in more TLS handshakes succeeding and obviates fallback
mechanisms.</t>


On Fri, May 19, 2017 at 10:17 AM, Martin Rex <mrex@sap.com> wrote:

> Benjamin Kaduk wrote:
> >
> > Some other editorial nits follow.
> >
> > In section 4, "these cipher suites MUST NOT be negotiated in TLS
> > versions prior to 1.2" should probably clarify that "these" cipher
> > suites are the new ones specified by this document.
>
>
> This reminds me of the specification goofs in several TLSv1.2-related
> documents about AEAD cipher suites which are responsible for the viability
> of the POODLE attack and other exploitable fallback hacks.
>
> It would be much preferable to avoid/fix those problems and facilitate
> the migration to and use of TLSv1.2 without failing TLS handshakes and
> band aids such as TLS_FALLBACK_SCSV
>
>
> Suggested improvement:
>
>    The cipher suites defined in this document make use of the
>    authenticated encryption with additional data (AEAD) defined in TLS
>    1.2 [RFC5246] and DTLS 1.2 [RFC6347].  Earlier versions of TLS do not
>    have support for AEAD and consequently, these cipher suites MUST NOT
> -  be negotiated in TLS versions prior to 1.2.  Clients MUST NOT offer
> -  these cipher suites if they do not offer TLS 1.2 or later.  Servers,
> -  which select an earlier version of TLS MUST NOT select one of these
> -  cipher suites.  A client MUST treat the selection of these cipher
> -  suites in combination with a version of TLS that does not support
> -  AEAD (i.e., TLS 1.1 or earlier) as an error and generate a fatal
> -  'illegal_parameter' TLS alert.
> +                                               A client that offers
> +  the cipher suites from this document in ClientHello.cipher_suites
> +  in combination with (3,1) "TLSv1.0" or (3,2) "TLSv1.1" in
> +  ClientHello.client_version MUST support TLSv1.2 and MUST accept
> +  the server to negotiate TLSv1.2 for the current session.  If the
> +  client does not support TLSv1.2 or is not willing to negotiate TLSv1.2,
> +  then this client MUST NOT offer any of these cipher suites with a
> +  lower protocol version than (3,3) "TLSv1.2" in
> ClientHello.client_version.
> +  A server receiving a ClientHello and a client_version indicating
> +  (3,1) "TLSv1.0" or (3,2) "TLSv1.1" and any of the cipher suites from
> +  this document in ClientHello.cipher_suites can safely assume that the
> +  client supports TLSv1.2 and is willing to use it.  The server MUST
> +  NOT negotiate these cipher suites with TLS protocol versions earlier
> +  than TLSv1.2.
> +
> +  Not requiring clients to indicate their support for TLSv1.2 cipher
> +  suites exclusively through ClientHello.client_hello improves the
> +  interoperability in the installed base and use of TLSv1.2 AEAD
> +  cipher suites without upsetting the installed base of version-intolerant
> +  TLS servers, results in more TLS handshakes succeeding and obviates
> +  fallback mechanisms.
>
>
> -Martin
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>

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

<div dir=3D"ltr"><div><div><div><div>Hi Martin, <br><br></div>Thank you for=
 the proposed text. It was very clear and I took it entirely, just changing=
 s/TLSv1/TLS 1/. <br><br></div>Yours, <br></div>Daniel<br><br><br></div>The=
 current text is as follows:<br>&lt;section title=3D&quot;Applicable TLS Ve=
rsions&quot;&gt;<br><br><br>&lt;t&gt; The cipher suites defined in this doc=
ument MUST NOT be negotiated<br>for any version of (D)TLS other than TLS 1.=
2.&lt;/t&gt;<br><br>&lt;t&gt; TLS version 1.3 and later negotiate these fea=
tures in a different<br>manner. Unlike TLS 1.2, TLS 1.3 separates authentic=
ation and cipher suite<br>negotiation &lt;xref target=3D&quot;I-D.ietf-tls-=
tls13&quot;/&gt; Section 1.2. TLS 1.3<br>supports PSK with ECDHE key exchan=
ge and the cipher suites<br>TLS_AES_128_GCM_SHA256, TLS_AES_256_GCM_SHA384,=
 TLS_AES_128_CCM_8_SHA256<br>and=C2=A0 TLS_AES_128_CCM_SHA256 are part of t=
he specification. As a result,<br>TLS 1.3 and higher versions, negotiate an=
d support these cipher suites<br>in a different way. &lt;/t&gt;<br><br>&lt;=
t&gt;The cipher suites defined in this document make use of the<br>authenti=
cated encryption with additional data (AEAD) defined in TLS 1.2<br>&lt;xref=
 target=3D&quot;RFC5246&quot;/&gt; and DTLS 1.2 &lt;xref target=3D&quot;RFC=
6347&quot; /&gt;.<br>Earlier versions of TLS do not have support for AEAD a=
nd consequently,<br>the cipher suites defined in this document MUST NOT be =
negotiated in TLS<br>versions prior to 1.2.=C2=A0 In addition, it is worth =
noting that TLS 1.0<br>&lt;xref target=3D&quot;RFC2246&quot;/&gt; and TL1.2=
 &lt;xref target=3D&quot;RFC4346&quot;/&gt; splits the<br>pre-master in two=
 parts. The PRF results of mixing the two pseudorandom<br>streams with dist=
inct hash functions (MD5 and SHA-1) by exclusive-ORing<br>them together. In=
 the case of ECDHE_PSK authentication, the PSK and<br>pre-master are treate=
d by distinct hash function with distinct<br>properties. This may introduce=
 vulnerabilities over the expected<br>security provided by the constructed =
pre-master. As such TLS 1.0 and<br>TLS 1.1 SHOULD NOT be used with ECDHE_PS=
K.&lt;/t&gt;<br><br>&lt;t&gt;A client that offers the cipher suites from th=
is document in<br>ClientHello.cipher_suites in combination with (3,1) &quot=
;TLS 1.0&quot; or (3,2)<br>&quot;TLS 1.1&quot; in ClientHello.client_versio=
n MUST support TLS 1.2 and MUST<br>accept the server to negotiate TLS 1.2 f=
or the current session.=C2=A0 If the<br>client does not support TLS 1.2 or =
is not willing to negotiate TLS 1.2,<br>then this client MUST NOT offer any=
 of these cipher suites with a lower<br>protocol version than (3,3) &quot;T=
LS 1.2&quot; in ClientHello.client_version.&lt;/t&gt;<br><br>&lt;t&gt;A ser=
ver receiving a ClientHello and a client_version indicating<br>(3,1) &quot;=
TLS 1.0&quot; or (3,2) &quot;TLS 1.1&quot; and any of the cipher suites fro=
m<br>this document in ClientHello.cipher_suites can safely assume that the<=
br>client supports TLS 1.2 and is willing to use it. The server MUST NOT<br=
>negotiate these cipher suites with TLS protocol versions earlier than<br>T=
LS 1.2. Not requiring clients to indicate their support for TLS 1.2<br>ciph=
er suites exclusively through ClientHello.client_hello improves the<br>inte=
roperability in the installed base and use of TLS 1.2 AEAD cipher<br>suites=
 without upsetting the installed base of version-intolerant TLS<br>servers,=
 results in more TLS handshakes succeeding and obviates fallback<br>mechani=
sms.&lt;/t&gt;<br><br></div><div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">On Fri, May 19, 2017 at 10:17 AM, Martin Rex <span dir=3D"ltr">&=
lt;<a href=3D"mailto:mrex@sap.com" target=3D"_blank">mrex@sap.com</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">Benjamin Ka=
duk wrote:<br>
&gt;<br>
&gt; Some other editorial nits follow.<br>
&gt;<br>
</span><span class=3D"">&gt; In section 4, &quot;these cipher suites MUST N=
OT be negotiated in TLS<br>
&gt; versions prior to 1.2&quot; should probably clarify that &quot;these&q=
uot; cipher<br>
&gt; suites are the new ones specified by this document.<br>
<br>
<br>
</span>This reminds me of the specification goofs in several TLSv1.2-relate=
d<br>
documents about AEAD cipher suites which are responsible for the viability<=
br>
of the POODLE attack and other exploitable fallback hacks.<br>
<br>
It would be much preferable to avoid/fix those problems and facilitate<br>
the migration to and use of TLSv1.2 without failing TLS handshakes and<br>
band aids such as TLS_FALLBACK_SCSV<br>
<br>
<br>
Suggested improvement:<br>
<br>
=C2=A0 =C2=A0The cipher suites defined in this document make use of the<br>
<span class=3D"">=C2=A0 =C2=A0authenticated encryption with additional data=
 (AEAD) defined in TLS<br>
</span>=C2=A0 =C2=A01.2 [RFC5246] and DTLS 1.2 [RFC6347].=C2=A0 Earlier ver=
sions of TLS do not<br>
=C2=A0 =C2=A0have support for AEAD and consequently, these cipher suites MU=
ST NOT<br>
-=C2=A0 be negotiated in TLS versions prior to 1.2.=C2=A0 Clients MUST NOT =
offer<br>
-=C2=A0 these cipher suites if they do not offer TLS 1.2 or later.=C2=A0 Se=
rvers,<br>
-=C2=A0 which select an earlier version of TLS MUST NOT select one of these=
<br>
-=C2=A0 cipher suites.=C2=A0 A client MUST treat the selection of these cip=
her<br>
-=C2=A0 suites in combination with a version of TLS that does not support<b=
r>
-=C2=A0 AEAD (i.e., TLS 1.1 or earlier) as an error and generate a fatal<br=
>
-=C2=A0 &#39;illegal_parameter&#39; TLS alert.<br>
+=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0A client that offers<br>
+=C2=A0 the cipher suites from this document in ClientHello.cipher_suites<b=
r>
+=C2=A0 in combination with (3,1) &quot;TLSv1.0&quot; or (3,2) &quot;TLSv1.=
1&quot; in<br>
+=C2=A0 ClientHello.client_version MUST support TLSv1.2 and MUST accept<br>
+=C2=A0 the server to negotiate TLSv1.2 for the current session.=C2=A0 If t=
he<br>
+=C2=A0 client does not support TLSv1.2 or is not willing to negotiate TLSv=
1.2,<br>
+=C2=A0 then this client MUST NOT offer any of these cipher suites with a<b=
r>
+=C2=A0 lower protocol version than (3,3) &quot;TLSv1.2&quot; in ClientHell=
o.client_version.<br>
+=C2=A0 A server receiving a ClientHello and a client_version indicating<br=
>
+=C2=A0 (3,1) &quot;TLSv1.0&quot; or (3,2) &quot;TLSv1.1&quot; and any of t=
he cipher suites from<br>
+=C2=A0 this document in ClientHello.cipher_suites can safely assume that t=
he<br>
+=C2=A0 client supports TLSv1.2 and is willing to use it.=C2=A0 The server =
MUST<br>
+=C2=A0 NOT negotiate these cipher suites with TLS protocol versions earlie=
r<br>
+=C2=A0 than TLSv1.2.<br>
+<br>
+=C2=A0 Not requiring clients to indicate their support for TLSv1.2 cipher<=
br>
+=C2=A0 suites exclusively through ClientHello.client_hello improves the<br=
>
+=C2=A0 interoperability in the installed base and use of TLSv1.2 AEAD<br>
+=C2=A0 cipher suites without upsetting the installed base of version-intol=
erant<br>
+=C2=A0 TLS servers, results in more TLS handshakes succeeding and obviates=
<br>
+=C2=A0 fallback mechanisms.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
-Martin<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
______________________________<wbr>_________________<br>
TLS mailing list<br>
<a href=3D"mailto:TLS@ietf.org">TLS@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tls" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/tls</a><br>
</div></div></blockquote></div><br></div>

--001a113c0cb2910d10054fe2f9e6--


From nobody Fri May 19 09:27:38 2017
Return-Path: <kaduk@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 61EFA129526; Fri, 19 May 2017 09:27:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 rUKWvGG-H7b0; Fri, 19 May 2017 09:27:34 -0700 (PDT)
Received: from dmz-mailsec-scanner-2.mit.edu (dmz-mailsec-scanner-2.mit.edu [18.9.25.13]) (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 9E4E7129447; Fri, 19 May 2017 09:27:33 -0700 (PDT)
X-AuditID: 1209190d-fd7ff700000023f1-de-591f1cf45586
Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP id B6.96.09201.4FC1F195; Fri, 19 May 2017 12:27:32 -0400 (EDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id v4JGRU5P007560; Fri, 19 May 2017 12:27:31 -0400
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v4JGRPmR013013 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 19 May 2017 12:27:29 -0400
Date: Fri, 19 May 2017 11:27:25 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Daniel Migault <daniel.migault@ericsson.com>
Cc: The IESG <iesg@ietf.org>, secdir@ietf.org, draft-ietf-tls-ecdhe-psk-aead.all@ietf.org, tls <tls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [TLS] secdir review of draft-ietf-tls-ecdhe-psk-aead-03
Message-ID: <20170519162725.GM39245@kduck.kaduk.org>
References: <20170519043827.GL39245@kduck.kaduk.org> <CADZyTkncMTsTQt6C2S+Z0mw+30uc38bfrTSCOvjWRPn_dJkDLQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CADZyTkncMTsTQt6C2S+Z0mw+30uc38bfrTSCOvjWRPn_dJkDLQ@mail.gmail.com>
User-Agent: Mutt/1.7.1 (2016-10-04)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLIsWRmVeSWpSXmKPExsUixCmqrftFRj7SYOEGZYsp0/ewWbxZtonJ YsaficwWzzbOZ7H4sPAhi8Wn812MDmwev75eZfNYsuQnUwBTFJdNSmpOZllqkb5dAlfGnOZP 7AVrHCtONW1gb2BsNeli5OSQEDCRON3/lgnEFhJYzCSxb7EnhL2RUeLXvPQuRi4g+yqTxNpf J1hAEiwCqhLzJh1hBLHZBFQkGrovM4PYIgIGEi8n7GQDsZkFFjBKzPltCGILC7hIrOhbAlbD C7Rs79zdUMuqJY5cmMgGEReUODnzCQtEr5bEjX8vgWo4gGxpieX/OEDCnAKBElM+zAdbKyqg LPH38D2WCYwCs5B0z0LSPQuhewEj8ypG2ZTcKt3cxMyc4tRk3eLkxLy81CJdI73czBK91JTS TYzgUJbk3cH4767XIUYBDkYlHt6EX3KRQqyJZcWVuYcYJTmYlER5HQ8DhfiS8lMqMxKLM+KL SnNSiw8xSnAwK4nwMojKRwrxpiRWVqUW5cOkpDlYlMR5xTUaI4QE0hNLUrNTUwtSi2CyMhwc ShK8G6WBGgWLUtNTK9Iyc0oQ0kwcnCDDeYCGvwOp4S0uSMwtzkyHyJ9iVJQS5z0EkhAASWSU 5sH1glKNRPb+mleM4kCvCPOqAROPEA8wTcF1vwIazAQ0uPmBNMjgkkSElFQDY8GJ5y4qF7be uHe8Qtfk+Pfp166E8p07ey9CUC3v0OfjAr3Xdko82Ph5/2Y534mt9w46znyynOGxl/SUvs2t asd3yc4Q8ddVdUpd0LhJ+viBwxW7dv/zsJmrWLT7emSly/XMcOntIlW23G7ftfau3DSjKK7j 53L2oG0WvSIBP3fWRubOPVQR/FWJpTgj0VCLuag4EQBhJEK1EAMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tspVUnSpqrLcwVA5JqX-95fF7gs>
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, 19 May 2017 16:27:36 -0000

On Fri, May 19, 2017 at 11:55:35AM -0400, Daniel Migault wrote:
> Hi Benjamin,
> 
> Thank you for the review. Please find my comments inline and let me know if
> you agree with the proposed text. I believe the only point not addressed
> concerns the addition of CCM-256 which has been remove after discussion
> during the WGLC.
> 
> Thanks you for the review,
> 
> Yours,
> Daniel
> 
> On Fri, May 19, 2017 at 12:38 AM, Benjamin Kaduk <kaduk@mit.edu> wrote:
> 
> > Hi all,
> >
> > 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.
> >
> > This document is ready with nits.
> >
> > Essentially, we are filling in a gap in the TLS (< 1.3) ciphersuite
> > space, thought of as a cross product of key exchange and
> > cipher+mac/AEAD -- we have some of the combinations (PSK with ECDHE
> > but no AES-[GC]CM, PSK with AES-GCM but only non-EC DH, etc.) but
> > not quite this one.
> >
> > That said, it seems a little silly to only partially fill the gap
> > (by omitting the AES_256_CCM* cipher suites), even though there is
> > not currently demand for them.
> >
> > MGLT: TLS_ECDHE_PSK_WITH_AES_256_CCM_8_SHA256 and
> TLS_ECDHE_PSK_WITH_AES_256_CCM_SHA384  were mentioned in the 01 and removed
> after  the WGLC. [0] The issue was whether or not introducing new ciphers
> not supported by TLS1.3. In 01, we though of adding the code point for
> TLS1.2 and then specify that TLS1.3 was only implementing a **subset** of
> the cipher suites proposed.In case of needs these could still be supported
> later by TLS1.3. The consensus seems to not introduce ciphers that would
> not be handled by TLS1.3. If the WG decides otherwise, these could still be
> added.
> 
> [0]
> https://mailarchive.ietf.org/arch/msg/tls/M442CwmUMxrYJR8FjCh3h-a69o4/?qid=6e4713be1d71bae6718c6e6e6c4b8007

That seems like a reasonable position for the WG to take, given how
close TLS 1.3 is to publication.  (It would also be reasonable to
define the full cross-product for TLS 1.2 only and have TLS 1.3 just
use a subset, but I have no real preference.)

> 
> > This document is just assembling pieces that were already specified
> > elsewhere, so it need not contain much detail itself, which is fine.
> > That said, I think section 3 should probably state explicitly which
> > pieces it uses, instead of a vague reference of being "based on RFC
> > 4279".  So, "The ServerKeyExchange and ClientKeyExchange messages
> > from RFC 5489 for ECDHE_PSK are used, and the premaster secret is
> > computed in the same manner as for ECDHE_PSK key exchange in RFC
> > 5489."  (I am not sure why RFC 4279 is cited in the current text; it
> > does not cover ECDHE_PSK.)
> >
> 
> MGLT: I agree we coudl be more explicit, here are the changes I propose. I
> believe it address your purpose.
> 
> OLD:
> 
> Messages and pre-master secret construction in this
> document are based on [RFC4279 <https://tools.ietf.org/html/rfc4279>].
> 
> NEW:
> 
> Messages and pre-master secret construction in this
> document are defined in [RFC5489]. The ServerKeyExchange
> and ClientKeyExchange messages and premaster secret is
> computed as for  the ECDHE_PSK key exchange.

That basically works for me, though I'd tweak the phrasing slightly
for clarity/grammar:

NEW2:

Messages and pre-master secret construction in this
document are defined in [RFC5489]. The ServerKeyExchange
and ClientKeyExchange messages are used and the premaster secret is
computed as for the ECDHE_PSK key exchange.


> 
> > The premaster_secret structure so used basically ends up putting the
> > ECDH output first followed by the static PSK; with the pre-TLS 1.2
> > PRF, that would give the ECDH shared secret to md5 and the PSK to
> > sha1, which is perhaps another reason to not use these with pre-1.2
> > worth mentioning (in addition to the AEAD availability).
> >
> 
> MGLT: I believe the following text address your concern, however I am
> wondering if we are not going beyond the scope of expected considerations.

It perhaps is and perhaps is not worth mentioning, yes.

> In addition, it is worth noting that TLS1.0 <xref target="RFC2246"/> and
> TL1.2 <xref target="RFC4346"/> splits the premaster in two parts. The PRF
> results of mixing the two pseudorandom streams with distinct hash functions

"results of" is an unusual phrasing; "results from" might be more
familiar.

> (MD5 and SHA-1) by exclusive-ORing them together. In the case of ECDHE_PSK
> authentication, the PSK and pre-master are treated by distinct hash
> function with distinct properties. This may introduce vulnerabilities over
> the expected security provided by the constructed pre-master. As such
> TLS1.0 and TLS1.1 SHOULD NOT be used with ECDHE_PSK.

The general tenor of this text addresses my concern, yes, but feel
free to use editorial discretion and not bother putting it in, if
you don't think it's useful.  (BTW, I think we are still TLS1.0 and
TLS1.1 MUST NOT be used with these ciphersuites, so maybe the SHOULD
NOT in the last sentence is not quite what is intended.)

> 
> > The security considerations largely refer to those of the other
> > documents providing the pieces that are combined together here;
> > those referenced security considerations sections are more than
> > adequate here, as this document itself does not really do anything
> > particularly novel.  That said, if we are going to reiterate the
> > entropy requirement for PSKs inline, we probably ought to also
> > reiterate the nonce-reuse considerations for GCM and CCM.  The
> > relevant constructions help, but there are still ways to mess up and
> > reuse a nonce when doing crypto in parallel, if I remember the
> > GCM/TLS document's security considerations correctly.
> >
> 
> MGLT: I believe the following text address your comments.
> 
>  <t>GCM or CCM encryption - even of different clear text - re-using a
> nonce with a same key undermines the security of GCM and CCM. As a
> result, GCM and CCM MUST only be used with system guaranteeing nonce
> uniqueness <xref target="RFC5116"/>.</t>

Sure, sounds good.  (Grammar nit: "a system".)

> 
> >
> > Some other editorial nits follow.
> >
> 
> > In section 2, the RFC 7525 reference that "AEAD algorithms [...] are
> > strongly recommended" is scoped to just (D)TLS, so the text here
> > should probably also list that qualification.
> >
> 
> MGLT: I believe the following text address your concern:
> 
> OLD text:
> <t>AEAD algorithms that combine encryption and integrity protection are
> strongly recommended for <xref target="RFC7525" /> and non-AEAD algorithms
> are forbidden to use in TLS 1.3 <xref target="I-D.ietf-tls-tls13"/>.
> 
> NEW text:
> <t>AEAD algorithms that combine encryption and integrity protection are
> strongly recommended for (D)TLS <xref target="RFC7525" /> and non-AEAD
> algorithms
> are forbidden to use in TLS 1.3 <xref target="I-D.ietf-tls-tls13"/>.

Yes, thanks.

> > In section 4, "... make use of the authenticated encryption with
> > additional data (AEAD) defined in TLS 1.2" seems to make AEAD into
> > something of a unique object, as opposed to a class of things with
> > multiple possible instantiations.  I would consider something like
> > "... (AEAD) concept".
> >
> > In section 4, "these cipher suites MUST NOT be negotiated in TLS
> > versions prior to 1.2" should probably clarify that "these" cipher
> > suites are the new ones specified by this document.
> >
> > MGLT: I believe the following text address your comment:
> 
> OLD:
> these cipher suites MUST NOT be negotiated in TLS  versions prior to 1.2.
> 
> NEW:
> the cipher suites defined in this document MUST NOT be negotiated in TLS
> versions prior to 1.2.
> 
>  OLD:
> Clients MUST NOT offer these cipher suites
> 
> NEW:
> Clients MUST NOT offer these cipher suites defined in this document

I think I only intended to comment about the first one, but there is
no harm in changing both.  Thanks!


-Ben


From nobody Fri May 19 09:58:47 2017
Return-Path: <mglt.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 159E2129526; Fri, 19 May 2017 09:58:14 -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 YEOmbOLhX0KY; Fri, 19 May 2017 09:58:10 -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 55ED71294F4; Fri, 19 May 2017 09:58:10 -0700 (PDT)
Received: by mail-lf0-x230.google.com with SMTP id 99so4186874lfu.1; Fri, 19 May 2017 09:58:10 -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=+V2BlG7CJ4wjwDCI5HgOPAYPEgdbYUi0drEqepx0PpY=; b=GbUP8NcWDSRJL37PEG3lENkC5o5sqFJGz5ZU0eXFG5i8s9C62XHUXcsNn4cI5OxExJ d97SlGJZCfnO1zDzsb2sYcSN5dLE275JNb2lqCZlCn/tySN5g179k1vLBljS2uCXsTVX zye2rF35ktbC/jQefDZfaABSGc+8NYU6zmznNjcgksl5lIS98BCTXce6jlKic5Xvwt86 wkmTCDXO1yL0cUbu8HLwil0gNYSFV3f+TH1KPM5GtoGIAvclqGGdi6yemYTvshSnvPfX qLJ7DC2Idah65cy0/hRilitcHS+pdCuw5TbTuCl2/AgY3DWyAzggrKGRF9o858tUGMYi H9tg==
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=+V2BlG7CJ4wjwDCI5HgOPAYPEgdbYUi0drEqepx0PpY=; b=HuMMTwJAVABH1Z+DtlrYk6zFcbSZomBlIAxR1ttJlCewDJMllGbK7TUhfG8MrtfCxg wzpyaodv7AkbK3ZrZ4X6w5gDfcgzIpUgowQjB6sz/DfPlU2N2c9M3z+8loNrWjkQFlN5 q7/1+ytbt7cCskkF8ntE4vR/RqUdm/LHR/p1zu3pLpZxThTGzLThws1tz1GBDjIR074F zDmtBrsfr7yS4gUv/yfTadtL58IK2IYxOoe99YeUPVO+DG9f5D4L4zTm7VxwcR+fbBb+ 6VStK2xOt1C/UsaDuxSL5TSXuijlLqWpifSlWCq858zVmzRc8eM7l6WqibY5v+RdCsM2 YflQ==
X-Gm-Message-State: AODbwcBRxwpTAYFV+Ev4iFBYLfpwf0Ib7ogoYG6+SxRKfkTHhkqZ5m+V nlBtL/V+wskUu9dFnwGTp2SAikFITw==
X-Received: by 10.46.69.8 with SMTP id s8mr2564481lja.55.1495213088509; Fri, 19 May 2017 09:58:08 -0700 (PDT)
MIME-Version: 1.0
Sender: mglt.ietf@gmail.com
Received: by 10.46.0.14 with HTTP; Fri, 19 May 2017 09:58:07 -0700 (PDT)
In-Reply-To: <20170519162725.GM39245@kduck.kaduk.org>
References: <20170519043827.GL39245@kduck.kaduk.org> <CADZyTkncMTsTQt6C2S+Z0mw+30uc38bfrTSCOvjWRPn_dJkDLQ@mail.gmail.com> <20170519162725.GM39245@kduck.kaduk.org>
From: Daniel Migault <daniel.migault@ericsson.com>
Date: Fri, 19 May 2017 12:58:07 -0400
X-Google-Sender-Auth: 1raqJXhaY3kI7429EhZs5caQhV8
Message-ID: <CADZyTk=id9bDfi31R+K6hC+ZKzWsjsvo8JbSCzqYGaK_1X1j7Q@mail.gmail.com>
Subject: Re: [TLS] secdir review of draft-ietf-tls-ecdhe-psk-aead-03
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: tls <tls@ietf.org>, draft-ietf-tls-ecdhe-psk-aead.all@ietf.org,  "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>, secdir@ietf.org
Content-Type: multipart/alternative; boundary="001a114b07fe0114c9054fe36d55"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mK4jnmqYukE_VBtjAW6z_34ORo0>
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, 19 May 2017 16:58:14 -0000

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

Thank you,

Your comments have all been addressed. I have one remaining clarification.
In my text the SHOULD NOT was intended to the ECDHE_PSK in general, and not
only for the cipher suites of the draft. In your opinion do we clarify
this, and should we use something else than SHOULD NOT ?

Thanks for the reviews!

Yours,
Daniel

> (MD5 and SHA-1) by exclusive-ORing them together. In the case of ECDHE_PSK
> authentication, the PSK and pre-master are treated by distinct hash
> function with distinct properties. This may introduce vulnerabilities over
> the expected security provided by the constructed pre-master. As such
> TLS1.0 and TLS1.1 SHOULD NOT be used with ECDHE_PSK.

The general tenor of this text addresses my concern, yes, but feel
free to use editorial discretion and not bother putting it in, if
you don't think it's useful.  (BTW, I think we are still TLS1.0 and
TLS1.1 MUST NOT be used with these ciphersuites, so maybe the SHOULD
NOT in the last sentence is not quite what is intended.)

On Fri, May 19, 2017 at 12:27 PM, Benjamin Kaduk <kaduk@mit.edu> wrote:

> On Fri, May 19, 2017 at 11:55:35AM -0400, Daniel Migault wrote:
> > Hi Benjamin,
> >
> > Thank you for the review. Please find my comments inline and let me know
> if
> > you agree with the proposed text. I believe the only point not addressed
> > concerns the addition of CCM-256 which has been remove after discussion
> > during the WGLC.
> >
> > Thanks you for the review,
> >
> > Yours,
> > Daniel
> >
> > On Fri, May 19, 2017 at 12:38 AM, Benjamin Kaduk <kaduk@mit.edu> wrote:
> >
> > > Hi all,
> > >
> > > 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.
> > >
> > > This document is ready with nits.
> > >
> > > Essentially, we are filling in a gap in the TLS (< 1.3) ciphersuite
> > > space, thought of as a cross product of key exchange and
> > > cipher+mac/AEAD -- we have some of the combinations (PSK with ECDHE
> > > but no AES-[GC]CM, PSK with AES-GCM but only non-EC DH, etc.) but
> > > not quite this one.
> > >
> > > That said, it seems a little silly to only partially fill the gap
> > > (by omitting the AES_256_CCM* cipher suites), even though there is
> > > not currently demand for them.
> > >
> > > MGLT: TLS_ECDHE_PSK_WITH_AES_256_CCM_8_SHA256 and
> > TLS_ECDHE_PSK_WITH_AES_256_CCM_SHA384  were mentioned in the 01 and
> removed
> > after  the WGLC. [0] The issue was whether or not introducing new ciphers
> > not supported by TLS1.3. In 01, we though of adding the code point for
> > TLS1.2 and then specify that TLS1.3 was only implementing a **subset** of
> > the cipher suites proposed.In case of needs these could still be
> supported
> > later by TLS1.3. The consensus seems to not introduce ciphers that would
> > not be handled by TLS1.3. If the WG decides otherwise, these could still
> be
> > added.
> >
> > [0]
> > https://mailarchive.ietf.org/arch/msg/tls/M442CwmUMxrYJR8FjCh3h-a69o4/?
> qid=6e4713be1d71bae6718c6e6e6c4b8007
>
> That seems like a reasonable position for the WG to take, given how
> close TLS 1.3 is to publication.  (It would also be reasonable to
> define the full cross-product for TLS 1.2 only and have TLS 1.3 just
> use a subset, but I have no real preference.)
>
> >
> > > This document is just assembling pieces that were already specified
> > > elsewhere, so it need not contain much detail itself, which is fine.
> > > That said, I think section 3 should probably state explicitly which
> > > pieces it uses, instead of a vague reference of being "based on RFC
> > > 4279".  So, "The ServerKeyExchange and ClientKeyExchange messages
> > > from RFC 5489 for ECDHE_PSK are used, and the premaster secret is
> > > computed in the same manner as for ECDHE_PSK key exchange in RFC
> > > 5489."  (I am not sure why RFC 4279 is cited in the current text; it
> > > does not cover ECDHE_PSK.)
> > >
> >
> > MGLT: I agree we coudl be more explicit, here are the changes I propose.
> I
> > believe it address your purpose.
> >
> > OLD:
> >
> > Messages and pre-master secret construction in this
> > document are based on [RFC4279 <https://tools.ietf.org/html/rfc4279>].
> >
> > NEW:
> >
> > Messages and pre-master secret construction in this
> > document are defined in [RFC5489]. The ServerKeyExchange
> > and ClientKeyExchange messages and premaster secret is
> > computed as for  the ECDHE_PSK key exchange.
>
> That basically works for me, though I'd tweak the phrasing slightly
> for clarity/grammar:
>
> NEW2:
>
> Messages and pre-master secret construction in this
> document are defined in [RFC5489]. The ServerKeyExchange
> and ClientKeyExchange messages are used and the premaster secret is
> computed as for the ECDHE_PSK key exchange.
>
>
> >
> > > The premaster_secret structure so used basically ends up putting the
> > > ECDH output first followed by the static PSK; with the pre-TLS 1.2
> > > PRF, that would give the ECDH shared secret to md5 and the PSK to
> > > sha1, which is perhaps another reason to not use these with pre-1.2
> > > worth mentioning (in addition to the AEAD availability).
> > >
> >
> > MGLT: I believe the following text address your concern, however I am
> > wondering if we are not going beyond the scope of expected
> considerations.
>
> It perhaps is and perhaps is not worth mentioning, yes.
>
> > In addition, it is worth noting that TLS1.0 <xref target="RFC2246"/> and
> > TL1.2 <xref target="RFC4346"/> splits the premaster in two parts. The PRF
> > results of mixing the two pseudorandom streams with distinct hash
> functions
>
> "results of" is an unusual phrasing; "results from" might be more
> familiar.
>
> > (MD5 and SHA-1) by exclusive-ORing them together. In the case of
> ECDHE_PSK
> > authentication, the PSK and pre-master are treated by distinct hash
> > function with distinct properties. This may introduce vulnerabilities
> over
> > the expected security provided by the constructed pre-master. As such
> > TLS1.0 and TLS1.1 SHOULD NOT be used with ECDHE_PSK.
>
> The general tenor of this text addresses my concern, yes, but feel
> free to use editorial discretion and not bother putting it in, if
> you don't think it's useful.  (BTW, I think we are still TLS1.0 and
> TLS1.1 MUST NOT be used with these ciphersuites, so maybe the SHOULD
> NOT in the last sentence is not quite what is intended.)
>
> >
> > > The security considerations largely refer to those of the other
> > > documents providing the pieces that are combined together here;
> > > those referenced security considerations sections are more than
> > > adequate here, as this document itself does not really do anything
> > > particularly novel.  That said, if we are going to reiterate the
> > > entropy requirement for PSKs inline, we probably ought to also
> > > reiterate the nonce-reuse considerations for GCM and CCM.  The
> > > relevant constructions help, but there are still ways to mess up and
> > > reuse a nonce when doing crypto in parallel, if I remember the
> > > GCM/TLS document's security considerations correctly.
> > >
> >
> > MGLT: I believe the following text address your comments.
> >
> >  <t>GCM or CCM encryption - even of different clear text - re-using a
> > nonce with a same key undermines the security of GCM and CCM. As a
> > result, GCM and CCM MUST only be used with system guaranteeing nonce
> > uniqueness <xref target="RFC5116"/>.</t>
>
> Sure, sounds good.  (Grammar nit: "a system".)
>
> >
> > >
> > > Some other editorial nits follow.
> > >
> >
> > > In section 2, the RFC 7525 reference that "AEAD algorithms [...] are
> > > strongly recommended" is scoped to just (D)TLS, so the text here
> > > should probably also list that qualification.
> > >
> >
> > MGLT: I believe the following text address your concern:
> >
> > OLD text:
> > <t>AEAD algorithms that combine encryption and integrity protection are
> > strongly recommended for <xref target="RFC7525" /> and non-AEAD
> algorithms
> > are forbidden to use in TLS 1.3 <xref target="I-D.ietf-tls-tls13"/>.
> >
> > NEW text:
> > <t>AEAD algorithms that combine encryption and integrity protection are
> > strongly recommended for (D)TLS <xref target="RFC7525" /> and non-AEAD
> > algorithms
> > are forbidden to use in TLS 1.3 <xref target="I-D.ietf-tls-tls13"/>.
>
> Yes, thanks.
>
> > > In section 4, "... make use of the authenticated encryption with
> > > additional data (AEAD) defined in TLS 1.2" seems to make AEAD into
> > > something of a unique object, as opposed to a class of things with
> > > multiple possible instantiations.  I would consider something like
> > > "... (AEAD) concept".
> > >
> > > In section 4, "these cipher suites MUST NOT be negotiated in TLS
> > > versions prior to 1.2" should probably clarify that "these" cipher
> > > suites are the new ones specified by this document.
> > >
> > > MGLT: I believe the following text address your comment:
> >
> > OLD:
> > these cipher suites MUST NOT be negotiated in TLS  versions prior to 1.2.
> >
> > NEW:
> > the cipher suites defined in this document MUST NOT be negotiated in TLS
> > versions prior to 1.2.
> >
> >  OLD:
> > Clients MUST NOT offer these cipher suites
> >
> > NEW:
> > Clients MUST NOT offer these cipher suites defined in this document
>
> I think I only intended to comment about the first one, but there is
> no harm in changing both.  Thanks!
>
>
> -Ben
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>

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

<div dir=3D"ltr"><div><div><div>Thank you, <br><br></div>Your comments have=
 all been addressed. I have one remaining clarification. In my text the SHO=
ULD NOT was intended to the ECDHE_PSK in general, and not only for the ciph=
er suites of the draft. In your opinion do we clarify this, and should we u=
se something else than SHOULD NOT ?<br><br></div><div>Thanks for the review=
s!<br><br></div>Yours, <br></div>Daniel<br><div><div><br><span class=3D"gma=
il-im">&gt; (MD5 and SHA-1) by exclusive-ORing them together. In the case o=
f ECDHE_PSK<br>
&gt; authentication, the PSK and pre-master are treated by distinct hash<br=
>
&gt; function with distinct properties. This may introduce vulnerabilities =
over<br>
&gt; the expected security provided by the constructed pre-master. As such<=
br>
&gt; TLS1.0 and TLS1.1 SHOULD NOT be used with ECDHE_PSK.<br>
<br>
</span>The general tenor of this text addresses my concern, yes, but feel<b=
r>
free to use editorial discretion and not bother putting it in, if<br>
you don&#39;t think it&#39;s useful.=C2=A0 (BTW, I think we are still TLS1.=
0 and<br>
TLS1.1 MUST NOT be used with these ciphersuites, so maybe the SHOULD<br>
NOT in the last sentence is not quite what is intended.)</div></div></div><=
div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, May 19, 20=
17 at 12:27 PM, Benjamin Kaduk <span dir=3D"ltr">&lt;<a href=3D"mailto:kadu=
k@mit.edu" target=3D"_blank">kaduk@mit.edu</a>&gt;</span> wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5">On Fri, May=
 19, 2017 at 11:55:35AM -0400, Daniel Migault wrote:<br>
&gt; Hi Benjamin,<br>
&gt;<br>
&gt; Thank you for the review. Please find my comments inline and let me kn=
ow if<br>
&gt; you agree with the proposed text. I believe the only point not address=
ed<br>
&gt; concerns the addition of CCM-256 which has been remove after discussio=
n<br>
&gt; during the WGLC.<br>
&gt;<br>
&gt; Thanks you for the review,<br>
&gt;<br>
&gt; Yours,<br>
&gt; Daniel<br>
&gt;<br>
&gt; On Fri, May 19, 2017 at 12:38 AM, Benjamin Kaduk &lt;<a href=3D"mailto=
:kaduk@mit.edu">kaduk@mit.edu</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt; Hi all,<br>
&gt; &gt;<br>
&gt; &gt; I have reviewed this document as part of the security directorate=
&#39;s<br>
&gt; &gt; ongoing effort to review all IETF documents being processed by th=
e<br>
&gt; &gt; IESG.=C2=A0 These comments were written primarily for the benefit=
 of the<br>
&gt; &gt; security area directors.=C2=A0 Document editors and WG chairs sho=
uld<br>
&gt; &gt; treat these comments just like any other last call comments.<br>
&gt; &gt;<br>
&gt; &gt; This document is ready with nits.<br>
&gt; &gt;<br>
&gt; &gt; Essentially, we are filling in a gap in the TLS (&lt; 1.3) cipher=
suite<br>
&gt; &gt; space, thought of as a cross product of key exchange and<br>
&gt; &gt; cipher+mac/AEAD -- we have some of the combinations (PSK with ECD=
HE<br>
&gt; &gt; but no AES-[GC]CM, PSK with AES-GCM but only non-EC DH, etc.) but=
<br>
&gt; &gt; not quite this one.<br>
&gt; &gt;<br>
&gt; &gt; That said, it seems a little silly to only partially fill the gap=
<br>
&gt; &gt; (by omitting the AES_256_CCM* cipher suites), even though there i=
s<br>
&gt; &gt; not currently demand for them.<br>
&gt; &gt;<br>
&gt; &gt; MGLT: TLS_ECDHE_PSK_WITH_AES_256_<wbr>CCM_8_SHA256 and<br>
&gt; TLS_ECDHE_PSK_WITH_AES_256_<wbr>CCM_SHA384=C2=A0 were mentioned in the=
 01 and removed<br>
&gt; after=C2=A0 the WGLC. [0] The issue was whether or not introducing new=
 ciphers<br>
&gt; not supported by TLS1.3. In 01, we though of adding the code point for=
<br>
&gt; TLS1.2 and then specify that TLS1.3 was only implementing a **subset**=
 of<br>
&gt; the cipher suites proposed.In case of needs these could still be suppo=
rted<br>
&gt; later by TLS1.3. The consensus seems to not introduce ciphers that wou=
ld<br>
&gt; not be handled by TLS1.3. If the WG decides otherwise, these could sti=
ll be<br>
&gt; added.<br>
&gt;<br>
&gt; [0]<br>
&gt; <a href=3D"https://mailarchive.ietf.org/arch/msg/tls/M442CwmUMxrYJR8Fj=
Ch3h-a69o4/?qid=3D6e4713be1d71bae6718c6e6e6c4b8007" rel=3D"noreferrer" targ=
et=3D"_blank">https://mailarchive.ietf.org/<wbr>arch/msg/tls/<wbr>M442CwmUM=
xrYJR8FjCh3h-a69o4/?<wbr>qid=3D<wbr>6e4713be1d71bae6718c6e6e6c4b80<wbr>07</=
a><br>
<br>
</div></div>That seems like a reasonable position for the WG to take, given=
 how<br>
close TLS 1.3 is to publication.=C2=A0 (It would also be reasonable to<br>
define the full cross-product for TLS 1.2 only and have TLS 1.3 just<br>
use a subset, but I have no real preference.)<br>
<span class=3D""><br>
&gt;<br>
&gt; &gt; This document is just assembling pieces that were already specifi=
ed<br>
&gt; &gt; elsewhere, so it need not contain much detail itself, which is fi=
ne.<br>
&gt; &gt; That said, I think section 3 should probably state explicitly whi=
ch<br>
&gt; &gt; pieces it uses, instead of a vague reference of being &quot;based=
 on RFC<br>
&gt; &gt; 4279&quot;.=C2=A0 So, &quot;The ServerKeyExchange and ClientKeyEx=
change messages<br>
&gt; &gt; from RFC 5489 for ECDHE_PSK are used, and the premaster secret is=
<br>
&gt; &gt; computed in the same manner as for ECDHE_PSK key exchange in RFC<=
br>
&gt; &gt; 5489.&quot;=C2=A0 (I am not sure why RFC 4279 is cited in the cur=
rent text; it<br>
&gt; &gt; does not cover ECDHE_PSK.)<br>
&gt; &gt;<br>
&gt;<br>
&gt; MGLT: I agree we coudl be more explicit, here are the changes I propos=
e. I<br>
&gt; believe it address your purpose.<br>
&gt;<br>
&gt; OLD:<br>
&gt;<br>
&gt; Messages and pre-master secret construction in this<br>
</span>&gt; document are based on [RFC4279 &lt;<a href=3D"https://tools.iet=
f.org/html/rfc4279" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf=
.org/html/<wbr>rfc4279</a>&gt;].<br>
<span class=3D"">&gt;<br>
&gt; NEW:<br>
&gt;<br>
&gt; Messages and pre-master secret construction in this<br>
&gt; document are defined in [RFC5489]. The ServerKeyExchange<br>
&gt; and ClientKeyExchange messages and premaster secret is<br>
&gt; computed as for=C2=A0 the ECDHE_PSK key exchange.<br>
<br>
</span>That basically works for me, though I&#39;d tweak the phrasing sligh=
tly<br>
for clarity/grammar:<br>
<br>
NEW2:<br>
<span class=3D""><br>
Messages and pre-master secret construction in this<br>
document are defined in [RFC5489]. The ServerKeyExchange<br>
</span>and ClientKeyExchange messages are used and the premaster secret is<=
br>
<span class=3D"">computed as for the ECDHE_PSK key exchange.<br>
<br>
<br>
&gt;<br>
&gt; &gt; The premaster_secret structure so used basically ends up putting =
the<br>
&gt; &gt; ECDH output first followed by the static PSK; with the pre-TLS 1.=
2<br>
&gt; &gt; PRF, that would give the ECDH shared secret to md5 and the PSK to=
<br>
&gt; &gt; sha1, which is perhaps another reason to not use these with pre-1=
.2<br>
&gt; &gt; worth mentioning (in addition to the AEAD availability).<br>
&gt; &gt;<br>
&gt;<br>
&gt; MGLT: I believe the following text address your concern, however I am<=
br>
&gt; wondering if we are not going beyond the scope of expected considerati=
ons.<br>
<br>
</span>It perhaps is and perhaps is not worth mentioning, yes.<br>
<span class=3D""><br>
&gt; In addition, it is worth noting that TLS1.0 &lt;xref target=3D&quot;RF=
C2246&quot;/&gt; and<br>
&gt; TL1.2 &lt;xref target=3D&quot;RFC4346&quot;/&gt; splits the premaster =
in two parts. The PRF<br>
&gt; results of mixing the two pseudorandom streams with distinct hash func=
tions<br>
<br>
</span>&quot;results of&quot; is an unusual phrasing; &quot;results from&qu=
ot; might be more<br>
familiar.<br>
<span class=3D""><br>
&gt; (MD5 and SHA-1) by exclusive-ORing them together. In the case of ECDHE=
_PSK<br>
&gt; authentication, the PSK and pre-master are treated by distinct hash<br=
>
&gt; function with distinct properties. This may introduce vulnerabilities =
over<br>
&gt; the expected security provided by the constructed pre-master. As such<=
br>
&gt; TLS1.0 and TLS1.1 SHOULD NOT be used with ECDHE_PSK.<br>
<br>
</span>The general tenor of this text addresses my concern, yes, but feel<b=
r>
free to use editorial discretion and not bother putting it in, if<br>
you don&#39;t think it&#39;s useful.=C2=A0 (BTW, I think we are still TLS1.=
0 and<br>
TLS1.1 MUST NOT be used with these ciphersuites, so maybe the SHOULD<br>
NOT in the last sentence is not quite what is intended.)<br>
<span class=3D""><br>
&gt;<br>
&gt; &gt; The security considerations largely refer to those of the other<b=
r>
&gt; &gt; documents providing the pieces that are combined together here;<b=
r>
&gt; &gt; those referenced security considerations sections are more than<b=
r>
&gt; &gt; adequate here, as this document itself does not really do anythin=
g<br>
&gt; &gt; particularly novel.=C2=A0 That said, if we are going to reiterate=
 the<br>
&gt; &gt; entropy requirement for PSKs inline, we probably ought to also<br=
>
&gt; &gt; reiterate the nonce-reuse considerations for GCM and CCM.=C2=A0 T=
he<br>
&gt; &gt; relevant constructions help, but there are still ways to mess up =
and<br>
&gt; &gt; reuse a nonce when doing crypto in parallel, if I remember the<br=
>
&gt; &gt; GCM/TLS document&#39;s security considerations correctly.<br>
&gt; &gt;<br>
&gt;<br>
&gt; MGLT: I believe the following text address your comments.<br>
&gt;<br>
&gt;=C2=A0 &lt;t&gt;GCM or CCM encryption - even of different clear text - =
re-using a<br>
&gt; nonce with a same key undermines the security of GCM and CCM. As a<br>
&gt; result, GCM and CCM MUST only be used with system guaranteeing nonce<b=
r>
&gt; uniqueness &lt;xref target=3D&quot;RFC5116&quot;/&gt;.&lt;/t&gt;<br>
<br>
</span>Sure, sounds good.=C2=A0 (Grammar nit: &quot;a system&quot;.)<br>
<span class=3D""><br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; Some other editorial nits follow.<br>
&gt; &gt;<br>
&gt;<br>
</span><span class=3D"">&gt; &gt; In section 2, the RFC 7525 reference that=
 &quot;AEAD algorithms [...] are<br>
&gt; &gt; strongly recommended&quot; is scoped to just (D)TLS, so the text =
here<br>
&gt; &gt; should probably also list that qualification.<br>
&gt; &gt;<br>
&gt;<br>
&gt; MGLT: I believe the following text address your concern:<br>
&gt;<br>
&gt; OLD text:<br>
&gt; &lt;t&gt;AEAD algorithms that combine encryption and integrity protect=
ion are<br>
&gt; strongly recommended for &lt;xref target=3D&quot;RFC7525&quot; /&gt; a=
nd non-AEAD algorithms<br>
&gt; are forbidden to use in TLS 1.3 &lt;xref target=3D&quot;I-D.ietf-tls-t=
ls13&quot;/&gt;.<br>
&gt;<br>
&gt; NEW text:<br>
&gt; &lt;t&gt;AEAD algorithms that combine encryption and integrity protect=
ion are<br>
&gt; strongly recommended for (D)TLS &lt;xref target=3D&quot;RFC7525&quot; =
/&gt; and non-AEAD<br>
&gt; algorithms<br>
&gt; are forbidden to use in TLS 1.3 &lt;xref target=3D&quot;I-D.ietf-tls-t=
ls13&quot;/&gt;.<br>
<br>
</span>Yes, thanks.<br>
<span class=3D""><br>
&gt; &gt; In section 4, &quot;... make use of the authenticated encryption =
with<br>
&gt; &gt; additional data (AEAD) defined in TLS 1.2&quot; seems to make AEA=
D into<br>
&gt; &gt; something of a unique object, as opposed to a class of things wit=
h<br>
&gt; &gt; multiple possible instantiations.=C2=A0 I would consider somethin=
g like<br>
&gt; &gt; &quot;... (AEAD) concept&quot;.<br>
&gt; &gt;<br>
&gt; &gt; In section 4, &quot;these cipher suites MUST NOT be negotiated in=
 TLS<br>
&gt; &gt; versions prior to 1.2&quot; should probably clarify that &quot;th=
ese&quot; cipher<br>
&gt; &gt; suites are the new ones specified by this document.<br>
&gt; &gt;<br>
&gt; &gt; MGLT: I believe the following text address your comment:<br>
&gt;<br>
&gt; OLD:<br>
&gt; these cipher suites MUST NOT be negotiated in TLS=C2=A0 versions prior=
 to 1.2.<br>
&gt;<br>
&gt; NEW:<br>
&gt; the cipher suites defined in this document MUST NOT be negotiated in T=
LS<br>
&gt; versions prior to 1.2.<br>
&gt;<br>
&gt;=C2=A0 OLD:<br>
&gt; Clients MUST NOT offer these cipher suites<br>
&gt;<br>
&gt; NEW:<br>
&gt; Clients MUST NOT offer these cipher suites defined in this document<br=
>
<br>
</span>I think I only intended to comment about the first one, but there is=
<br>
no harm in changing both.=C2=A0 Thanks!<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
-Ben<br>
<br>
______________________________<wbr>_________________<br>
TLS mailing list<br>
<a href=3D"mailto:TLS@ietf.org">TLS@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tls" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/tls</a><br>
</div></div></blockquote></div><br></div>

--001a114b07fe0114c9054fe36d55--


From nobody Fri May 19 11:19:47 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 833E5129687; Fri, 19 May 2017 11:19:34 -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-grow-bgp-reject.all@ietf.org, grow@ietf.org, ietf@ietf.org
Subject: Genart telechat review of draft-ietf-grow-bgp-reject-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149521797450.18806.9588203462855463048@ietfa.amsl.com>
Date: Fri, 19 May 2017 11:19:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FLbEaMgWAa41ZB1SZivbrkMtZeE>
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, 19 May 2017 18:19:34 -0000

Reviewer: Dale Worley
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
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document:  draft-ietf-grow-bgp-reject-07
Reviewer:  Dale R. Worley
Review Date:  2017-05-19
IETF LC End Date:  2017-04-18
IESG Telechat date:  2017-06-08

Summary:  This draft is basically ready for publication, but has nits
that should be fixed before publication.

My knowledge of BGP is quite limited, so I cannot review the
desirability of this solution.  I assume that the routing and
operations community has fully considered that question.

   1. Introduction
			
   BGP routing security issues need to be addressed in order to make
the
   Internet more stable.  Route leaks [RFC7908] are part of the
problem,
   but software defects or operator misconfiguration can contribute
too.
   This document updates [RFC4271] in order to improve the default
level
   of Internet routing security.

This paragraph is a good introduction, but it isn't very cohesive.  I
suggest revising the third sentence to something like:

   This document updates [RFC4271] so that routes are neither
imported
   nor exported unless specifically enabled by configuration, thus
   reducing route leaks, and so improving the default level of
   Internet routing security.

Then again, considering section 5 paragraph 1, perhaps this update
reduces all three causes (route leaks, software defects, and operator
misconfigurations), in which case you could say

   This document updates [RFC4271] so that routes are neither
imported
   nor exported unless specifically enabled by configuration, thus
   reducing the consequences of these problems, and so improving the
   default level of Internet routing security.

--

   BGP speakers following this specification do not use or send
routes
   on EBGP sessions, unless configured to do otherwise.

This sentence seems to be correct as written, but somehow it reads
awkwardly to me.  I think the problem is that "do otherwise" is used,
when the "otherwise" is "do not use ...".  I think it would read more
smoothly to say:

   BGP speakers following this specification do not use or send
routes
   on EBGP sessions, unless specifically configured to do so.

Perhaps the Editor should be consulted about this.

--

   2.  Terminology

   [RFC4271] describes a Policy Information Base (PIB) which contains
   local policies that can be applied to the information in the
Routing
   Information Base (RIB).  This document distinguishes the type of
   policy based on its application.

Here, you want to say "the type of a policy" or "the type of a
particular policy", because "policy" refers to a specific policy
within a set of policies, rather than being a mass noun.

   3. Changes to RFC4271	
				
   This section describes the Updates to [RFC4271] that define the
   default behavior of a BGP speaker when there are no Import or
   Export Policies associated with a particular EBGP session.

Of course, there is no need to capitalize "Updates".

The wording "describes the updates" is awkward.  Really, it lists or
specifies the updates, rather than describing them.  Also, the use of
"updates ... that ..." suggests that there is a larger set of updates
from which "the updates that define the default behavior" are
selected, and that smaller set will be described in this section.
Instead, there are updates, and those updates define the default
behavior.

So I think a better wording is:

   This section updates [RFC4271] to change the default behavior
...".

It's probably worth consulting the Edtior to see if a better wording
is possible.

--

   The following paragraph is added to Section 9.1 (Decision Process)
   after the fifth paragraph ending in "route aggregation and route
   information reduction":

Strictly, this says that there are five paragraphs which end in
"route
aggregation and route information reduction", and the fifth of them
is
being discussed.  The correct wording is 'the fifth paragraph, which
ends in "route aggregation and route information reduction"'.

   The following paragraph is added to Section 9.1.3 (Phase 3: Route
   Dissemination) after the third paragraph ending in "by means of an
   UPDATE message (see 9.2).":

Similarly, this should be 'the third paragraph, which ends in "by
means of an UPDATE message (see 9.2)."'

   5. Security Considerations	

   Permissive default routing policies can result in inadvertent
effects	
   such as route leaks [RFC7908], in general resulting in rerouting
of	
   traffic through an unexpected path.

The word "rerouting" emphasizes that the traffic's route has been
changed, whereas I think the problem you are concerned with is simply
that the traffic is routed through an unexpected path.  That suggests
changing "rerouting" to "routing".

Then again, perhaps routing people always conceptualize an incorrect
route as a change from an expected or correct route, in which case
"rerouting" is the best word to use.

   Appendix A.  Transition Considerations

   It is anticipated that transitioning to a compliant BGP
   implementation will require a process thay may take several years.

You probably want to s/a compliant BGP implementation/compliant BGP
implementations/, unless you are describing the process for an
individual operator, not for all operators collectively.

   A.1. N+1 N+2 Release Strategy	

   An implementer could leverage an approach described as "the N+1
and	
   N+2 release strategy".

I prefer reducing the words within the quotation marks.  (But
probably
it's best to ask the Editor.)  That would give:

   An implementer could leverage an approach described as the "N+1
and	
   N+2" release strategy.

The section title is difficult to understand without context.  I
suggest revising it in a way that parallels the way you use the term
in the text of the section, such as:

   A.1. Using an "N+1 and N+2" Release Strategy	

This conveys the maximum possible amount of information to a reader
(like me) who doesn't know what the "N+1 and N+2" strategy is, namely
that there is a known release strategy with the name "N+1 and N+2",
and that the section describes how to use it in this context (and
hopefully, defines it as well). -- (All of which expectations are
met.)

   "ebgp insecure-mode"

I think that in this phrase, "ebgp insecure" modifies "mode", and so
it would be written "ebgp-insecure mode".  (As opposed to "ebgp"
modifying "insecure mode", in which case it would indeed be written
"ebgp insecure-mode".)

[END]



From nobody Fri May 19 13:04:31 2017
Return-Path: <wdenniss@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 75DED129AB6 for <ietf@ietfa.amsl.com>; Fri, 19 May 2017 13:04:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, 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 G26VcCKEK3fX for <ietf@ietfa.amsl.com>; Fri, 19 May 2017 13:04: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 216E012951C for <ietf@ietf.org>; Fri, 19 May 2017 13:04:06 -0700 (PDT)
Received: by mail-io0-x22f.google.com with SMTP id k91so53773721ioi.1 for <ietf@ietf.org>; Fri, 19 May 2017 13:04:06 -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=DIxZijMyoosEBEnHAb1cHOE1AsjPqASahl8Rbj8RQ4A=; b=eemJyYjZYqgg/TNT9am0JhnOyxmz8/RWKf4TjTavffIoW1fgPndpX0603zHamsvKVh Pvw306xN/jGz74WTbiQDe+qMjU9k7ahJScAbVZxyghVB9Ml4txZ3ufYKAHQ0nsNeCIa1 29zSZLzThrQJ0ucwmR9f2fIsu7/2gZW8SlnnlA2gwFjn6U9nu0SD/u3vniZ4CEdg7LEX Bdt3IXgpfcOa6RXqqqp0w8WvJRZ1zVKCwHmeuzzabEV9rCxYy8rsrB7WSnlIgN5IXjF1 nxLOzF0PgvTeKijy2t5nC53FbEy9/5psT3mjkpcN8+knWsEH218LcCWoJ8O3NLFS/9LB mAJQ==
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=DIxZijMyoosEBEnHAb1cHOE1AsjPqASahl8Rbj8RQ4A=; b=SLcpBLvv0hftRRotTEoIIKyD2YwNKNlyihtM4O0qmG03Hnpi2od6sLNUTCsbPB0YN1 9eVExu2OMMaN6Ki3RAcqmxDUn3QeEGDe+tumHaOs66r65cNnkjPybFkk5I3zm5iGi+JO P8AP/IcGwkVCNINqPtRRbT1yFixmBSaaP5iNqzGkKHueSpFQCuVc9e6gZPavfZCkCIDL EdP1rph+6kVVM//dV3Zz4cUfysXWshEUraTE11LzBuTYoj0Jv7SJNqM0u0rslIbfS2Ab CBEjxgLH086aMIWzdohwawks6F6Ak/ojkgMM5QoSpCwmO2+i82N/Zs0dnNsXBCic3Vj2 BPWQ==
X-Gm-Message-State: AODbwcCaIMIysTO5Y7sNHvdOpLUBZBj4ChrRHkHlF5w0aYy3AkO/Auun Y/WOK8Aeqtk23/5Tx+eulfSSvHeC3d4F
X-Received: by 10.107.25.203 with SMTP id 194mr11591604ioz.182.1495224245104;  Fri, 19 May 2017 13:04:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.35.37 with HTTP; Fri, 19 May 2017 13:03:44 -0700 (PDT)
In-Reply-To: <149489171188.11868.13336890952697460283@ietfa.amsl.com>
References: <149489171188.11868.13336890952697460283@ietfa.amsl.com>
From: William Denniss <wdenniss@google.com>
Date: Fri, 19 May 2017 13:03:44 -0700
Message-ID: <CAAP42hBvma8ZijjQ3+88-pqv7EObHtJcF-cn91zbFhSG9KzFew@mail.gmail.com>
Subject: Re: Genart last call review of draft-ietf-oauth-native-apps-10
To: Elwyn Davies <elwynd@dial.pipex.com>
Cc: gen-art@ietf.org, draft-ietf-oauth-native-apps.all@ietf.org, ietf@ietf.org, "oauth@ietf.org" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="001a113fe2dafe2c0d054fe6056b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jtPerd_jlCih5loBK5gCSJK5uEo>
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, 19 May 2017 20:04:11 -0000

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

Elwyn,

Thank you for your detailed review.

Comments inline, my changes appear in version 11
<https://datatracker.ietf.org/doc/html/draft-ietf-oauth-native-apps-11>.

On Mon, May 15, 2017 at 4:41 PM, Elwyn Davies <elwynd@dial.pipex.com> wrote:

> 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-oauth-native-apps-10
> Reviewer: Elwyn Davies
> Review Date: 2017-05-15
> IETF LC End Date: 2017-05-16
> IESG Telechat date: 2017-05-25
>
> Summary: Almost ready.  A couple of simple minor issues could do with
> addressing.
>
> Major issues:
> None.
>
> Minor issues:
> s3: "browser":  The browser that acts as the Oauth user-agent is
> conflated with the user's choice of default browser.  Firstly this is
> not something that is discussed in RFC 6749.  Secondly, the concept of
> 'default browser' would normally be thought of by users as the browser
> that is used to display the content associated with hyperlinks rather
> than providing Oauth services.  I suggest that the implication in the
> body of the draft that 'the browser' is the user selected or system
> selected default browser needs to be at least discussed explicitly
> rather than buried in the terminology definitions in s3.  I wonder
> whether ths connection is something that should be made by a separate
> OS setting or a setting in each native app rather than conflated with
> the default browser.  The term "designated browser" might be useful.
> In all cases there might be secuity implications if a bad actor could
> subvert the designated browser setting.
>

I reworded the definition, please take another look.

s8.1, Requirement of use of PKCE in some cases:  This strict
> requirement really needs to be introduced in the body of the
> discussion rather than buried in the seurity considerations.
>

I reworked Section 6 to include this requirement there.

Nits/editorial comments:
>
> General: s/i.e./i.e.,/ (3 places)
>

Done.

Title and Abstract: s/apps/applications/g  (uses before we get to
> terminology in s3)
>

After consulting some dictionaries, I'm convinced that app is a bonafide
synonym for application, and not shorthand (even if it started out that
way). So I've reworded our definition, but am otherwise planning to retain
the use of "app". The primary use-case for this BCP are "apps", I believe
replacing this usage would introduce more confusion that it could
potentially solve.

s1, para 1:  Suggest the following to make it clear that the
> definition is in RFC 6749 rather than here.
> OLD:
>  The OAuth 2.0 [RFC6749] authorization framework documents two
> approaches in Section 9 for native apps to interact with the
> authorization endpoint: an embedded user-agent, and an external user-
> agent.
> NEW:
> The OAuth 2.0 [RFC6749] authorization framework defines "native
> applications" in Section 9 of RFC 6749 (see also Section 3 below) and
> documents two approaches by whch they can interact with the
> authorization endpoint: an embedded user-agent, and an external
> user-agent.
> END
>

I feel like this is implied due to the reference to Section 9 of 6749 in
the opening sentence.

s1, para 2: s/apps/applications/(2places) .  For second case: s/native
> apps/native applications (shortened to "native apps" or just "apps"
> hereafter)/
>
> s3, "native app": s/app/application/g in the definition.  After that
> in the document "[native] app" is fine except for the definitions
> mentioned in the next comment. Worth repeating the link to Section 9
> of RFC 6749.
>
> s3, All definitions after "app"; s/app/application/g in the
> definitions as these are not restricted to (native) apps as defined
> here.
>

Per earlier comment.

s3, "embedded user-agent": s/modify/modifyng/
>

Done.

s4, last para: s/emcompasses/encompasses/
>

Done.


> s4, last para: s/inter-process/inter-app/ (since this term is
> defined)
>

Done.


> s4, last para: Might be worth pointing to the 'SHOULD' about client
> type assumptions in s2.1 of RFC 6749 withe reference to servers that
> do make assumptions.
>

This is covered in detail in Section 8.4. I'd like to keep this
introduction light, and not get into the details just yet.  Let me know if
you think 8.4 is inadequate.

s4.1, para below figure 1: s/system browser/browser/ (or maybe
> "designated browser").
>

Reworded.

s5, paras 1 and  2: Reword to clarify and remove 'we gain' usage (not
> allowed in RFCs):
> OLD:
>    Just as URIs are used for OAuth 2.0 [RFC6749] on the web to
> initiate
>    the authorization request and return the authorization response to
>    the requesting website, URIs can be used by native apps to
> initiate
>    the authorization request in the device's browser and return the
>    response to the requesting native app.
>
>    By applying the same principles from the web to native apps, we
> gain
>    benefits seen on the web, like the usability of a single sign-on
>    session and the security of a separate authentication context.  It
>    also reduces the implementation complexity by reusing similar
> flows
>    as the web, and increases interoperability by relying on
> standards-
>    based web flows that are not specific to a particular platform.
> NEW:
>    Just as URIs are used for OAuth 2.0 [RFC6749] in the HTTP protocol
> on the web to initiate
>    the authorization request and return the authorization response to
>    the requesting website, URIs can be used by native apps to
> initiate
>    the authorization request in the device's browser and return the
>    response to the requesting native app.
>
>    By extending the techniques from the web to native apps, the
>    benefits gained in the web context will also be reaped when using
>    OAuth with native apps; benefits include the usability of a single
> sign-on
>    session and the security of a separate authentication context.  Use
> of
>    the techniques also reduces implementation complexity by reusing
> similar flows
>    to those employed on the web, and increases interoperability by
> relying on standards-
>    based web flows that are not specific to a particular platform.
> END
>

Re-worded to remove "we gain", thanks for your suggestion.

s5, para 3: Suggest prefixing this para with: "To conform to this best
> practise," - the MUST is not derived from RFC 6749.
>

Re-worded taking into account this suggestion.

s7.1, last para: s/URI like it/URI as it/; s/like normal/as it would
> normally/
>

Done.


> s7.2, next to last para:
> OLD:
> Due to this reason, they SHOULD be used over the other redirect
> choices for native apps where possible.
> NEW:
> For this reason, they SHOULD be used in preference to the other
> redirect options for native apps where possible.
> END
>

Done.

s7.2, last para: s/it REQUIRED/it is REQUIRED/
>

Done.

s8.1, para 2: Need to expand acronym PKCE at first use (currently
> expanded in para 4).
>

PKCE now defined earlier in the doc.


> s8.1, para 4: s/sends data/send data/
>

Done.

s8.2: It would be more consistent with RFC 6749 to refer to "Implicit
> Flow" as "Implicit Grant authorization flow" at least for the title
> and first occurrence.   The second and third occurrences in para 1
> should s/Implicit Flow/implicit flow/ for consistency with para 2.
>

Done.


> s8.2, para 2: s/code flow/Authorization Code Grant flow/
>

Done.

s8.3, last para: Is a reminder to choose the 'right' type of IP
> literal (IPv4 or v6) desirable?  Doing an address lookup on
> "localhost" presumably tells you which one to use! [perhaps?]
>

Good point, but I think this is an implementation consideration. I've added
a note to 7.3.

s8.7, para 4: s/like/such as/
>

Done.


> s8.8; need to expand CSRF (Cross Site Request Forgery)


Done.


> and maybe
> explain a it how CSRGF and the cross-app case are related
>

Great point, done.

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

<div dir=3D"ltr">Elwyn,<div><br></div><div>Thank you for your detailed revi=
ew.</div><div><br></div><div>Comments inline, my changes appear in <a href=
=3D"https://datatracker.ietf.org/doc/html/draft-ietf-oauth-native-apps-11" =
target=3D"_blank">version 11</a>.<br><div class=3D"gmail_extra"><br><div cl=
ass=3D"gmail_quote">On Mon, May 15, 2017 at 4:41 PM, Elwyn Davies <span dir=
=3D"ltr">&lt;<a href=3D"mailto:elwynd@dial.pipex.com" target=3D"_blank">elw=
ynd@dial.pipex.com</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">Reviewer: Elwyn Davies<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/ge<wbr>n/wiki/GenArtfaq<=
/a>&gt;.<br>
<br>
Document: draft-ietf-oauth-native-apps-1<wbr>0<br>
Reviewer: Elwyn Davies<br>
Review Date: 2017-05-15<br>
IETF LC End Date: 2017-05-16<br>
IESG Telechat date: 2017-05-25<br>
<br>
Summary: Almost ready.=C2=A0 A couple of simple minor issues could do with<=
br>
addressing.<br>
<br>
Major issues:<br>
None.<br>
<br>
Minor issues:<br>
s3: &quot;browser&quot;: =C2=A0The browser that acts as the Oauth user-agen=
t is<br>
conflated with the user&#39;s choice of default browser.=C2=A0 Firstly this=
 is<br>
not something that is discussed in RFC 6749.=C2=A0 Secondly, the concept of=
<br>
&#39;default browser&#39; would normally be thought of by users as the brow=
ser<br>
that is used to display the content associated with hyperlinks rather<br>
than providing Oauth services.=C2=A0 I suggest that the implication in the<=
br>
body of the draft that &#39;the browser&#39; is the user selected or system=
<br>
selected default browser needs to be at least discussed explicitly<br>
rather than buried in the terminology definitions in s3.=C2=A0 I wonder<br>
whether ths connection is something that should be made by a separate<br>
OS setting or a setting in each native app rather than conflated with<br>
the default browser.=C2=A0 The term &quot;designated browser&quot; might be=
 useful.<br>
In all cases there might be secuity implications if a bad actor could<br>
subvert the designated browser setting.<br></blockquote><div><br></div><div=
>I reworded the definition, please take another look.</div><div><br></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">
s8.1, Requirement of use of PKCE in some cases: =C2=A0This strict<br>
requirement really needs to be introduced in the body of the<br>
discussion rather than buried in the seurity considerations.<br></blockquot=
e><div><br></div><div>I reworked Section 6 to include this requirement ther=
e.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Nits/editorial comments:<br>
<br>
General: s/i.e./i.e.,/ (3 places)<br></blockquote><div><br></div><div>Done.=
</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Title and Abstract: s/apps/applications/g =C2=A0(uses before we get to<br>
terminology in s3)<br></blockquote><div><br></div><div>After consulting som=
e dictionaries, I&#39;m convinced that app is a bonafide synonym for applic=
ation, and not shorthand (even if it started out that way). So I&#39;ve rew=
orded our definition, but am otherwise planning to retain the use of &quot;=
app&quot;. The primary use-case for this BCP are &quot;apps&quot;, I believ=
e replacing this usage would introduce more confusion that it could potenti=
ally solve.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex">
s1, para 1: =C2=A0Suggest the following to make it clear that the<br>
definition is in RFC 6749 rather than here.<br>
OLD:<br>
=C2=A0The OAuth 2.0 [RFC6749] authorization framework documents two<br>
approaches in Section 9 for native apps to interact with the<br>
authorization endpoint: an embedded user-agent, and an external user-<br>
agent.<br>
NEW:<br>
The OAuth 2.0 [RFC6749] authorization framework defines &quot;native<br>
applications&quot; in Section 9 of RFC 6749 (see also Section 3 below) and<=
br>
documents two approaches by whch they can interact with the<br>
authorization endpoint: an embedded user-agent, and an external<br>
user-agent.=C2=A0<br>
END=C2=A0<br></blockquote><div><br></div><div>I feel like this is implied d=
ue to the reference to Section 9 of 6749 in the opening sentence.=C2=A0</di=
v><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">s1, para=
 2: s/apps/applications/(2places) .=C2=A0 For second case: s/native<br>
apps/native applications (shortened to &quot;native apps&quot; or just &quo=
t;apps&quot;<br>
hereafter)/<br>
<br>
s3, &quot;native app&quot;: s/app/application/g in the definition.=C2=A0 Af=
ter that<br>
in the document &quot;[native] app&quot; is fine except for the definitions=
<br>
mentioned in the next comment. Worth repeating the link to Section 9<br>
of RFC 6749.<br>
<br>
s3, All definitions after &quot;app&quot;; s/app/application/g in the<br>
definitions as these are not restricted to (native) apps as defined<br>
here.<br></blockquote><div><br></div><div>Per earlier comment.</div><div><b=
r></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">
s3, &quot;embedded user-agent&quot;: s/modify/modifyng/<br></blockquote><di=
v><br></div><div>Done.</div><div><br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex">
s4, last para: s/emcompasses/encompasses/<br></blockquote><div><br></div><d=
iv>Done.</div><div>=C2=A0</div><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">
s4, last para: s/inter-process/inter-app/ (since this term is<br>
defined)<br></blockquote><div><br></div><div>Done.</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">
s4, last para: Might be worth pointing to the &#39;SHOULD&#39; about client=
<br>
type assumptions in s2.1 of RFC 6749 withe reference to servers that<br>
do make assumptions.<br></blockquote><div><br></div><div>This is covered in=
 detail in Section 8.4. I&#39;d like to keep this introduction light, and n=
ot get into the details just yet.=C2=A0 Let me know if you think 8.4 is ina=
dequate.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">
s4.1, para below figure 1: s/system browser/browser/ (or maybe<br>
&quot;designated browser&quot;).<br></blockquote><div><br></div><div>Reword=
ed.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
s5, paras 1 and =C2=A02: Reword to clarify and remove &#39;we gain&#39; usa=
ge (not<br>
allowed in RFCs):<br>
OLD:<br>
=C2=A0 =C2=A0Just as URIs are used for OAuth 2.0 [RFC6749] on the web to<br=
>
initiate<br>
=C2=A0=C2=A0 the authorization request and return the authorization respons=
e to<br>
=C2=A0=C2=A0 the requesting website, URIs can be used by native apps to<br>
initiate<br>
=C2=A0=C2=A0 the authorization request in the device&#39;s browser and retu=
rn the<br>
=C2=A0=C2=A0 response to the requesting native app.<br>
<br>
=C2=A0=C2=A0 By applying the same principles from the web to native apps, w=
e<br>
gain<br>
=C2=A0=C2=A0 benefits seen on the web, like the usability of a single sign-=
on<br>
=C2=A0=C2=A0 session and the security of a separate authentication context.=
=C2=A0 It<br>
=C2=A0=C2=A0 also reduces the implementation complexity by reusing similar<=
br>
flows<br>
=C2=A0=C2=A0 as the web, and increases interoperability by relying on<br>
standards-<br>
=C2=A0=C2=A0 based web flows that are not specific to a particular platform=
.<br>
NEW:<br>
=C2=A0 =C2=A0Just as URIs are used for OAuth 2.0 [RFC6749] in the HTTP prot=
ocol<br>
on the web to initiate<br>
=C2=A0=C2=A0 the authorization request and return the authorization respons=
e to<br>
=C2=A0=C2=A0 the requesting website, URIs can be used by native apps to<br>
initiate<br>
=C2=A0=C2=A0 the authorization request in the device&#39;s browser and retu=
rn the<br>
=C2=A0=C2=A0 response to the requesting native app.<br>
<br>
=C2=A0=C2=A0 By extending the techniques from the web to native apps, the<b=
r>
=C2=A0=C2=A0 benefits gained in the web context will also be reaped when us=
ing=C2=A0<br>
=C2=A0 =C2=A0OAuth with native apps; benefits include the usability of a si=
ngle<br>
sign-on<br>
=C2=A0=C2=A0 session and the security of a separate authentication context.=
=C2=A0 Use<br>
of<br>
=C2=A0 =C2=A0the techniques also reduces implementation complexity by reusi=
ng<br>
similar flows<br>
=C2=A0 =C2=A0to those employed on the web, and increases interoperability b=
y<br>
relying on standards-<br>
=C2=A0=C2=A0 based web flows that are not specific to a particular platform=
.<br>
END<br></blockquote><div><br></div><div>Re-worded to remove &quot;we gain&q=
uot;, thanks for your suggestion.</div><div><br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex">
s5, para 3: Suggest prefixing this para with: &quot;To conform to this best=
<br>
practise,&quot; - the MUST is not derived from RFC 6749.<br></blockquote><d=
iv><br></div><div>Re-worded taking into account this suggestion.</div><div>=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
s7.1, last para: s/URI like it/URI as it/; s/like normal/as it would<br>
normally/<br></blockquote><div><br></div><div>Done.</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">
s7.2, next to last para:<br>
OLD:<br>
Due to this reason, they SHOULD be used over the other redirect<br>
choices for native apps where possible.<br>
NEW:<br>
For this reason, they SHOULD be used in preference to the other<br>
redirect options for native apps where possible.<br>
END<br></blockquote><div><br></div><div>Done.</div><div><br></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">
s7.2, last para: s/it REQUIRED/it is REQUIRED/<br></blockquote><div><br></d=
iv><div>Done.</div><div><br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">
s8.1, para 2: Need to expand acronym PKCE at first use (currently<br>
expanded in para 4).<br></blockquote><div><br></div><div>PKCE now defined e=
arlier in the doc.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex">
s8.1, para 4: s/sends data/send data/<br></blockquote><div><br></div><div>D=
one.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
s8.2: It would be more consistent with RFC 6749 to refer to &quot;Implicit<=
br>
Flow&quot; as &quot;Implicit Grant authorization flow&quot; at least for th=
e title<br>
and first occurrence. =C2=A0 The second and third occurrences in para 1<br>
should s/Implicit Flow/implicit flow/ for consistency with para 2.<br></blo=
ckquote><div><br></div><div>Done.</div><div>=C2=A0<br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">
s8.2, para 2: s/code flow/Authorization Code Grant flow/<br></blockquote><d=
iv><br></div><div>Done.</div><div><br></div><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">
s8.3, last para: Is a reminder to choose the &#39;right&#39; type of IP<br>
literal (IPv4 or v6) desirable?=C2=A0 Doing an address lookup on<br>
&quot;localhost&quot; presumably tells you which one to use! [perhaps?]<br>=
</blockquote><div><br></div><div>Good point, but I think this is an impleme=
ntation consideration. I&#39;ve added a note to 7.3.</div><div><br></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">
s8.7, para 4: s/like/such as/<br></blockquote><div><br></div><div>Done.</di=
v><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
s8.8; need to expand CSRF (Cross Site Request Forgery)</blockquote><div><br=
></div><div>Done.</div><div>=C2=A0</div><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"> and maybe<br>
explain a it how CSRGF and the cross-app case are related<br></blockquote><=
div><br></div><div>Great point, done.</div></div><br></div></div></div>

--001a113fe2dafe2c0d054fe6056b--


From nobody Fri May 19 14:47:28 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 2FB10128961; Fri, 19 May 2017 14:47:14 -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-anima-grasp.all@ietf.org, ietf@ietf.org, anima@ietf.org
Subject: Genart telechat review of draft-ietf-anima-grasp-12
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149523043416.21589.9385334747760332010@ietfa.amsl.com>
Date: Fri, 19 May 2017 14:47:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IKfIYerBCbQSQmWYJCiMpv049_k>
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, 19 May 2017 21:47:14 -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 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-anima-grasp-??
Reviewer: Joel Halpern
Review Date: 2017-05-19
IETF LC End Date: 2017-03-02
IESG Telechat date: 2017-05-25

Summary: This document is still ready for publication as a Proposed
Standard RFC

Major issues: N/A

Minor issues: N/A

Nits/editorial comments:  N/A



From nobody Fri May 19 15:43:40 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 68E1E129B5E; Fri, 19 May 2017 15:43:27 -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: draft-ietf-tls-ecdhe-psk-aead.all@ietf.org, ietf@ietf.org, tls@ietf.org, dromasca@gmail.com
Subject: Genart telechat review of draft-ietf-tls-ecdhe-psk-aead-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149523380739.28567.9584998643479497589@ietfa.amsl.com>
Date: Fri, 19 May 2017 15:43:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wuRUoWvZYWXJqZfEJ2a5u9sd2CI>
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, 19 May 2017 22:43:27 -0000

Reviewer: Dan Romascanu
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-ietf-tls-ecdhe-psk-aead-??
Reviewer: Dan Romascanu
Review Date: 2017-05-19
IETF LC End Date: 2017-05-18
IESG Telechat date: 2017-05-25

Summary:

This is a straight-forward and clear document that defines several new
cipher suites for the Transport Layer Security (TLS) protocol version
1.2 and higher, based on the Ephemeral Elliptic Curve Diffie-Hellman
with Pre-Shared Key (ECDHE_PSK) key exchange together with the
Authenticated Encryption with Associated Data (AEAD) algorithms
AES-GCM and AES-CCM. The document is well written and I appreciate the
effort to clarify in the Introduction the context, what was missing,
and why the document is necessary. One issue raised in my initial
review for draft-03 was addressed, discussed and draft-04 includes
useful clarification text. 

The document is Ready

Major issues:

Minor issues:

Nits/editorial comments: 



From nobody Sun May 21 20:05:19 2017
Return-Path: <wangzitao@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 9EE08129515; Sun, 21 May 2017 20:05:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.82
X-Spam-Level: 
X-Spam-Status: No, score=-2.82 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HTML_MESSAGE=0.001, 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, 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 KiFsNPJH4Ryt; Sun, 21 May 2017 20:05:14 -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 33F95124B0A; Sun, 21 May 2017 20:05:13 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml703-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DHB06537; Mon, 22 May 2017 03:05:11 +0000 (GMT)
Received: from DGGEMM402-HUB.china.huawei.com (10.3.20.210) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 22 May 2017 04:05:09 +0100
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.49]) by DGGEMM402-HUB.china.huawei.com ([10.3.20.210]) with mapi id 14.03.0301.000; Mon, 22 May 2017 11:05:05 +0800
From: wangzitao <wangzitao@huawei.com>
To: "ops-dir@ietf.org" <ops-dir@ietf.org>
CC: "oauth@ietf.org" <oauth@ietf.org>, "draft-ietf-oauth-native-apps.all@ietf.org" <draft-ietf-oauth-native-apps.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: [OPS-DIR] Opsdir telechat review of draft-ietf-oauth-native-apps-10
Thread-Topic: [OPS-DIR] Opsdir telechat review of draft-ietf-oauth-native-apps-10
Thread-Index: AdLSqDVW3BTeNlgFQ6WqlwAw3ux67g==
Date: Mon, 22 May 2017 03:05:04 +0000
Message-ID: <E6BC9BBCBCACC246846FC685F9FF41EA2AE094F0@DGGEMM506-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.136.79.161]
Content-Type: multipart/alternative; boundary="_000_E6BC9BBCBCACC246846FC685F9FF41EA2AE094F0DGGEMM506MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.59225567.00BB, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.3.49, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 01d0af88b641625d75bea2fdc53aa751
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7o6E_5IJmsjXDad_WzkDXezy4YM>
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, 22 May 2017 03:05:18 -0000

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

Reviewer: Zitao Wang (Michael)

Review result: Has Nits



I have reviewed this document as part of the Operational directorate's ongo=
ing effort to review all IETF documents being processed by the IESG.  These=
 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 in=
cluded in AD reviews during the IESG review.  Document editors and WG chair=
s should treat these comments just like any other last call comments.



Document reviewed:  draft-ietf-oauth-native-apps-10



Summary:


OAuth 2.0 authorization requests from native apps should only be made
through external user-agents, primarily the user's browser. This
specification details the security and usability reasons why this is
the case, and how native apps and authorization servers can implement

this best practice.


I think the document is written very clear, except some small nits:

Page 3:     The last sentence of introduction-- "This practice is also know=
n as the AppAuth pattern".

I suggest adding a reference to explain the AppAuth pattern.



Page 3:     Terminology -- "OAuth".

I suggest modifying to: "OAuth"   The Web Authorization (OAuth) protocol.  =
In this document, OAuth refers to OAuth 2.0 [RFC6749].



Page 4:     Terminology -- "web-view"  A web browser UI component.

Does it mean "User Information"?  Suggest expanding this abbreviation.



Page 5:     Figure 1.   Does the browser and authorization endpoint are som=
e kinds of "external user-agent"? Suggest describing it more clearly.


Page   9:   PKCE [RFC7636] details how this limitation can be used to execu=
te a code interception attack (see Figure 1).

Does the Figure 1 means "Figure 1 of RFC7636"?


Page10:     However, as the Implicit Flow cannot be protected by PKCE
Seems here, the reference be omitted.





A run of idnits revealed no errors, flaws. There were 1 warning and 1 comme=
nts though



  =3D=3D There are 1 instance of lines with non-RFC2606-compliant FQDNs in =
the

     document.





  Miscellaneous warnings:

  -------------------------------------------------------------------------=
---



  -- The document date (April 26, 2017) is 14 days in the past.  Is this

     intentional?





  Checking references for intended status: Best Current Practice

  -------------------------------------------------------------------------=
---



     (See RFCs 3967 and 4897 for information about using normative referenc=
es

     to lower-maturity documents in RFCs)



     No issues found here.



     Summary: 0 errors (**), 0 flaws (~~), 1 warning (=3D=3D), 1 comment (-=
-).





_______________________________________________

OPS-DIR mailing list

OPS-DIR@ietf.org<mailto:OPS-DIR@ietf.org>

https://www.ietf.org/mailman/listinfo/ops-dir


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"\7EAF\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML \9884\8BBE\683C\5F0F Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLChar
	{mso-style-name:"HTML \9884\8BBE\683C\5F0F Char";
	mso-style-priority:99;
	mso-style-link:"HTML \9884\8BBE\683C\5F0F";
	font-family:"Courier New";}
span.Char
	{mso-style-name:"\7EAF\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\7EAF\6587\672C;
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">Reviewer: Zitao Wang (Michael)<o:p></o:p></p>
<p class=3D"MsoPlainText">Review result: Has Nits<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I have reviewed this document as part of the Oper=
ational directorate&#8217;s&nbsp;ongoing effort to review all IETF document=
s being processed by the IESG. &nbsp;These&nbsp;comments were written with =
the intent of improving the operational&nbsp;aspects of the
 IETF drafts. Comments that are not addressed in last call may be included =
in AD reviews during the IESG review. &nbsp;Document editors and&nbsp;WG ch=
airs should treat these comments just like any other last call&nbsp;comment=
s.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Document reviewed: &nbsp;draft-ietf-oauth-native-=
apps-10<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary: <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:normal;text-autospace:none">
<span style=3D"font-size:10.5pt;font-family:Consolas">OAuth 2.0 authorizati=
on requests from native apps should only be made<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:normal;text-autospace:none">
<span style=3D"font-size:10.5pt;font-family:Consolas">through external user=
-agents, primarily the user&#8217;s browser. This<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:normal;text-autospace:none">
<span style=3D"font-size:10.5pt;font-family:Consolas">specification details=
 the security and usability reasons why this is<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:normal;text-autospace:none">
<span style=3D"font-size:10.5pt;font-family:Consolas">the case, and how nat=
ive apps and authorization servers can implement<o:p></o:p></span></p>
<p class=3D"MsoPlainText">this best practice.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;line-height:115%;fon=
t-family:Consolas">I think the document is written very clear, except some =
small nits:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><a name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">P=
age 3:</a>&nbsp;&nbsp;&nbsp;&nbsp; The last sentence of introduction-- &#82=
20;This practice is also known as the AppAuth pattern&#8221;.&nbsp;&nbsp;
<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:36.0pt">I=
 suggest adding a reference to explain the AppAuth pattern.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Page 3:&nbsp;&nbsp;&nbsp;&nbsp; Terminology -- &q=
uot;OAuth&quot;.&nbsp; <o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:36.0pt">I=
 suggest modifying to: &quot;OAuth&quot;&nbsp;&nbsp; The Web Authorization =
(OAuth) protocol.&nbsp; In this document, OAuth refers to OAuth 2.0 [RFC674=
9].<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Page 4:&nbsp;&nbsp;&nbsp;&nbsp; Terminology -- &q=
uot;web-view&quot;&nbsp; A web browser UI component.&nbsp;&nbsp;
<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:36.0pt">D=
oes it mean &quot;User Information&quot;?&nbsp; Suggest expanding this abbr=
eviation.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Page 5:&nbsp;&nbsp;&nbsp;&nbsp; Figure 1.&nbsp;&n=
bsp; Does the browser and authorization endpoint are some kinds of &quot;ex=
ternal user-agent&quot;? Suggest describing it more clearly.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:normal;text-autospace:none">
<span style=3D"font-size:10.5pt;font-family:Consolas">Page&nbsp;&nbsp; 9:&n=
bsp;&nbsp; PKCE [RFC7636] details how this limitation can be used to execut=
e a code interception attack (see Figure 1).&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:36.0pt">D=
oes the Figure 1 means &#8220;Figure 1 of RFC7636&#8221;?&nbsp;
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:normal;text-autospace:none">
<span style=3D"font-size:10.5pt;font-family:Consolas">Page10:&nbsp;&nbsp;&n=
bsp;&nbsp; However, as the Implicit Flow cannot be protected by PKCE&nbsp;&=
nbsp;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:0cm;margin-right:0cm;mar=
gin-bottom:0cm;margin-left:36.0pt;margin-bottom:.0001pt;text-indent:36.0pt;=
line-height:normal;text-autospace:none">
<span style=3D"font-size:10.5pt;font-family:Consolas">Seems here, the refer=
ence be omitted.&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<pre><span style=3D"font-size:10.5pt;font-family:Consolas">A run of idnits =
revealed no errors, flaws. There were 1 warning and 1 comments though<o:p><=
/o:p></span></pre>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<pre><span style=3D"color:black">&nbsp; =3D=3D There are 1 instance of line=
s with non-RFC2606-compliant FQDNs in the<o:p></o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nbsp; document.<o:p></o=
:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">&nbsp; Miscellaneous warnings:<o:p></o:p><=
/span></pre>
<pre><span style=3D"color:black">&nbsp; -----------------------------------=
-----------------------------------------<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">&nbsp; -- The document date (April 26, 201=
7) is 14 days in the past.&nbsp; Is this<o:p></o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nbsp; intentional?<o:p>=
</o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">&nbsp; Checking references for intended st=
atus: Best Current Practice<o:p></o:p></span></pre>
<pre><span style=3D"color:black">&nbsp; -----------------------------------=
-----------------------------------------<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nbsp; (See RFCs 3967 an=
d 4897 for information about using normative references<o:p></o:p></span></=
pre>
<pre><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nbsp; to lower-maturity=
 documents in RFCs)<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nbsp; No issues found h=
ere.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nbsp; Summary: 0 errors=
 (**), 0 flaws (~~), 1 warning (=3D=3D), 1 comment (--).</span><span style=
=3D"color:black"><o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<p class=3D"MsoPlainText">_______________________________________________<o=
:p></o:p></p>
<p class=3D"MsoPlainText">OPS-DIR mailing list<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"mailto:OPS-DIR@ietf.org">OPS-DIR@ietf.=
org</a><o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://www.ietf.org/mailman/listinfo/=
ops-dir">https://www.ietf.org/mailman/listinfo/ops-dir</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_E6BC9BBCBCACC246846FC685F9FF41EA2AE094F0DGGEMM506MBXchi_--


From nobody Sun May 21 21:05:05 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 393D912956B; Sun, 21 May 2017 21:05:04 -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-jones-cose-rsa.all@ietf.org, ietf@ietf.org
Subject: Genart telechat review of draft-jones-cose-rsa-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149542590419.3467.434051460088011243@ietfa.amsl.com>
Date: Sun, 21 May 2017 21:05:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PHtSw1OSIOhbsAHNa1hPFqQpCRI>
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, 22 May 2017 04:05:04 -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 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-jones-cose-rsa-??
Reviewer: Roni Even
Review Date: 2017-05-21
IETF LC End Date: 2017-06-15
IESG Telechat date: 2017-06-22

Summary: The document is ready for publication as standard track RFC
with nits

Major issues:

Minor issues:

Nits/editorial comments: 

1. Section 3 first paragraph "can be find" should be "can be found"

2. IANA 5.1  table 1 and 2 missing recommended colum

3. IANA 5.3 table 4 the title is not "value" but "label"





From nobody Mon May 22 04:05:04 2017
Return-Path: <job@instituut.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 91626129BEF for <ietf@ietfa.amsl.com>; Mon, 22 May 2017 04:04:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level: 
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_HTML_ATTACH=0.01, URIBL_BLOCKED=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 5tiY1KxdfvMN for <ietf@ietfa.amsl.com>; Mon, 22 May 2017 04:04:55 -0700 (PDT)
Received: from mail-wm0-f50.google.com (mail-wm0-f50.google.com [74.125.82.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 D999A1241FC for <ietf@ietf.org>; Mon, 22 May 2017 04:04:51 -0700 (PDT)
Received: by mail-wm0-f50.google.com with SMTP id e127so34497735wmg.1 for <ietf@ietf.org>; Mon, 22 May 2017 04:04:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=3KnvXl87mWychKdx5b2VMo6r/hAsJay6i3eW/kh7kF8=; b=E7NeeObuPWj3dVsjZra2fsysW/Yn9fwuambbnpMsUSzR0pNZxVj0eRUQps/ANk4v/e HVoufFP6j2JhlT3SBTThp4PDk9+qkMQ+lFjFBIYVCCXB6D2+3h8A3uEDCymCXatNL6cS tVA9UgCyL1QTvUJ41ZI8Efwfs44DFeJrO5pKm8y/OUmLop5l/PixXJhtwNKo5cEgJn4h ZAThM/2S6z6fAiRzATPBJrYLklZkMXE4BZ/3qILrD96JB32DHSrxPRRMzQ8bhgfbDPX6 lJCJBBjWKEZny4Q4B1yXuPpaKbw9k0HftRqo9FnTasxB0brFGtf0Fvr8yiHlqk9Sqql5 513A==
X-Gm-Message-State: AODbwcCCec+wCTNfpa8m1jLyEePY9H74dQg/UBxgpg/GeFwEEVZ8VNKH DvGQzjt39Kx6lwgf
X-Received: by 10.80.146.71 with SMTP id j7mr17144390eda.17.1495451090038; Mon, 22 May 2017 04:04:50 -0700 (PDT)
Received: from localhost ([2001:67c:208c:10:c1e1:f644:f57b:230a]) by smtp.gmail.com with ESMTPSA id y55sm7874723edb.12.2017.05.22.04.04.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 May 2017 04:04:48 -0700 (PDT)
Date: Mon, 22 May 2017 13:04:48 +0200
From: Job Snijders <job@ntt.net>
To: Dale Worley <worley@ariadne.com>
Cc: gen-art@ietf.org, draft-ietf-grow-bgp-reject.all@ietf.org, grow@ietf.org, ietf@ietf.org
Subject: Re: [GROW] Genart telechat review of draft-ietf-grow-bgp-reject-07
Message-ID: <20170522110448.3obnrbam2who3n5x@hanna.meerval.net>
References: <149521797450.18806.9588203462855463048@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="dt2phjyidgxxemhj"
Content-Disposition: inline
In-Reply-To: <149521797450.18806.9588203462855463048@ietfa.amsl.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: NeoMutt/20170306 (1.8.0)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z_v3eMs2EDixfCtkCWvceUPz0FM>
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, 22 May 2017 11:04:58 -0000

--dt2phjyidgxxemhj
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Dear Dale,

Thank you for your time reviewing this document.

On Fri, May 19, 2017 at 11:19:34AM -0700, Dale Worley wrote:
> Summary:  This draft is basically ready for publication, but has nits
> that should be fixed before publication.
> 
>    1. Introduction
> 			
>    BGP routing security issues need to be addressed in order to make
>    the Internet more stable.  Route leaks [RFC7908] are part of the
>    problem, but software defects or operator misconfiguration can
>    contribute too.  This document updates [RFC4271] in order to
>    improve the default level of Internet routing security.
> 
> This paragraph is a good introduction, but it isn't very cohesive.  I
> suggest revising the third sentence to something like:
> 
>    This document updates [RFC4271] so that routes are neither imported
>    nor exported unless specifically enabled by configuration, thus
>    reducing route leaks, and so improving the default level of
>    Internet routing security.
> 
> Then again, considering section 5 paragraph 1, perhaps this update
> reduces all three causes (route leaks, software defects, and operator
> misconfigurations), in which case you could say
> 
>    This document updates [RFC4271] so that routes are neither imported
>    nor exported unless specifically enabled by configuration, thus
>    reducing the consequences of these problems, and so improving the
>    default level of Internet routing security.

I've accepted the latter suggestion.

> --
> 
>    BGP speakers following this specification do not use or send routes
>    on EBGP sessions, unless configured to do otherwise.
> 
> This sentence seems to be correct as written, but somehow it reads
> awkwardly to me.  I think the problem is that "do otherwise" is used,
> when the "otherwise" is "do not use ...".  I think it would read more
> smoothly to say:
> 
>    BGP speakers following this specification do not use or send routes
>    on EBGP sessions, unless specifically configured to do so.
> 
> Perhaps the Editor should be consulted about this.

I've accepted this suggestion.

> --
> 
>    2.  Terminology
> 
>    [RFC4271] describes a Policy Information Base (PIB) which contains
>    local policies that can be applied to the information in the
>    Routing Information Base (RIB).  This document distinguishes the
>    type of policy based on its application.
> 
> Here, you want to say "the type of a policy" or "the type of a
> particular policy", because "policy" refers to a specific policy
> within a set of policies, rather than being a mass noun.

accepted.

> 
>    3. Changes to RFC4271	
> 				
>    This section describes the Updates to [RFC4271] that define the
>    default behavior of a BGP speaker when there are no Import or
>    Export Policies associated with a particular EBGP session.
> 
> Of course, there is no need to capitalize "Updates".
> 
> The wording "describes the updates" is awkward.  Really, it lists or
> specifies the updates, rather than describing them.  Also, the use of
> "updates ... that ..." suggests that there is a larger set of updates
> from which "the updates that define the default behavior" are
> selected, and that smaller set will be described in this section.
> Instead, there are updates, and those updates define the default
> behavior.
> 
> So I think a better wording is:
> 
>    This section updates [RFC4271] to change the default behavior ...".
> 
> It's probably worth consulting the Edtior to see if a better wording
> is possible.

I suggest: "This section updates <xref target="RFC4271" /> to specify
the default behavior of a BGP speaker when there are no Import or Export
Policies associated with a particular EBGP session."

> --
> 
>    The following paragraph is added to Section 9.1 (Decision Process)
>    after the fifth paragraph ending in "route aggregation and route
>    information reduction":
> 
> Strictly, this says that there are five paragraphs which end in "route
> aggregation and route information reduction", and the fifth of them is
> being discussed.  The correct wording is 'the fifth paragraph, which
> ends in "route aggregation and route information reduction"'.

accepted.

>    The following paragraph is added to Section 9.1.3 (Phase 3: Route
>    Dissemination) after the third paragraph ending in "by means of an
>    UPDATE message (see 9.2).":
> 
> Similarly, this should be 'the third paragraph, which ends in "by
> means of an UPDATE message (see 9.2)."'

accepted.

>    5. Security Considerations	
> 
>    Permissive default routing policies can result in inadvertent
>    effects such as route leaks [RFC7908], in general resulting in
>    rerouting of traffic through an unexpected path.
> 
> The word "rerouting" emphasizes that the traffic's route has been
> changed, whereas I think the problem you are concerned with is simply
> that the traffic is routed through an unexpected path.  That suggests
> changing "rerouting" to "routing".
> 
> Then again, perhaps routing people always conceptualize an incorrect
> route as a change from an expected or correct route, in which case
> "rerouting" is the best word to use.

"routing" is perfectly fine too in this context since we are explicit
about "unexpected paths". Accepted.

>    Appendix A.  Transition Considerations
> 
>    It is anticipated that transitioning to a compliant BGP
>    implementation will require a process thay may take several years.
> 
> You probably want to s/a compliant BGP implementation/compliant BGP
> implementations/, unless you are describing the process for an
> individual operator, not for all operators collectively.

The process refers to the vendors of BGP implementations, not operators.
Given that the appendix is targetted mostly to the vendor audience,
would you have a suggestion within that context?

>    A.1. N+1 N+2 Release Strategy	
> 
>    An implementer could leverage an approach described as "the N+1 and
>    N+2 release strategy".
> 
> I prefer reducing the words within the quotation marks.  (But probably
> it's best to ask the Editor.)  That would give:
> 
>    An implementer could leverage an approach described as the "N+1 and
>    N+2" release strategy.
> 
> The section title is difficult to understand without context.  I
> suggest revising it in a way that parallels the way you use the term
> in the text of the section, such as:
> 
>    A.1. Using an "N+1 and N+2" Release Strategy	
> 
> This conveys the maximum possible amount of information to a reader
> (like me) who doesn't know what the "N+1 and N+2" strategy is, namely
> that there is a known release strategy with the name "N+1 and N+2",
> and that the section describes how to use it in this context (and
> hopefully, defines it as well). -- (All of which expectations are
> met.)

I moved the quotation marks around according to your suggestions.

>    "ebgp insecure-mode"
> 
> I think that in this phrase, "ebgp insecure" modifies "mode", and so
> it would be written "ebgp-insecure mode".  (As opposed to "ebgp"
> modifying "insecure mode", in which case it would indeed be written
> "ebgp insecure-mode".)

The current phrasing aligns with industry standards (for better of for
worse), one should consider the suggestion arbitrary, it is merely a
configuration keyword suggestion and not normative. 

I've attached a -07 -> -08 htmldiff which incorporates your suggestions.
After we covered the 's/a compliant BGP implementation/compliant BGP
implementations/' subtopic, and my co-authors reviewed the proposed
changes, we can proceed to cut & publish a -08.

Kind regards,

Job

--dt2phjyidgxxemhj
Content-Type: text/html; charset=us-ascii
Content-Disposition: attachment; filename="draft-ietf-grow-bgp-reject-08-from-7.diff.html"

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 
<!-- Generated by rfcdiff 1.41: rfcdiff  --> 
<!-- <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional" > -->
<!-- System: Darwin hanna.meerval.net 16.5.0 Darwin Kernel Version 16.5.0: Fri Mar  3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64 --> 
<!-- Using awk: /usr/local/bin/gawk: GNU Awk 4.1.4, API: 1.1 (GNU MPFR 3.1.5, GNU MP 6.1.2) --> 
<!-- Using diff: /usr/bin/diff: diff (GNU diffutils) 2.8.1 --> 
<!-- Using wdiff: /usr/local/bin/wdiff: wdiff (GNU wdiff) 1.2.2 --> 
<html> 
<head> 
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> 
  <meta http-equiv="Content-Style-Type" content="text/css" /> 
  <title>Diff: draft-ietf-grow-bgp-reject-07.txt - draft-ietf-grow-bgp-reject-08.txt</title> 
  <style type="text/css"> 
    body    { margin: 0.4ex; margin-right: auto; } 
    tr      { } 
    td      { white-space: pre; font-family: monospace; vertical-align: top; font-size: 0.86em;} 
    th      { font-size: 0.86em; } 
    .small  { font-size: 0.6em; font-style: italic; font-family: Verdana, Helvetica, sans-serif; } 
    .left   { background-color: #EEE; } 
    .right  { background-color: #FFF; } 
    .diff   { background-color: #CCF; } 
    .lblock { background-color: #BFB; } 
    .rblock { background-color: #FF8; } 
    .insert { background-color: #8FF; } 
    .delete { background-color: #ACF; } 
    .void   { background-color: #FFB; } 
    .cont   { background-color: #EEE; } 
    .linebr { background-color: #AAA; } 
    .lineno { color: red; background-color: #FFF; font-size: 0.7em; text-align: right; padding: 0 2px; } 
    .elipsis{ background-color: #AAA; } 
    .left .cont { background-color: #DDD; } 
    .right .cont { background-color: #EEE; } 
    .lblock .cont { background-color: #9D9; } 
    .rblock .cont { background-color: #DD6; } 
    .insert .cont { background-color: #0DD; } 
    .delete .cont { background-color: #8AD; } 
    .stats, .stats td, .stats th { background-color: #EEE; padding: 2px 0; } 
  </style> 
</head> 
<body > 
  <table border="0" cellpadding="0" cellspacing="0"> 
  <tr bgcolor="orange"><th></th><th>&nbsp;draft-ietf-grow-bgp-reject-07.txt&nbsp;</th><th> </th><th>&nbsp;draft-ietf-grow-bgp-reject-08.txt&nbsp;</th><th></th></tr> 
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Global Routing Operations                                       J. Mauch</td><td> </td><td class="right">Global Routing Operations                                       J. Mauch</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Internet-Draft                                                    Akamai</td><td> </td><td class="right">Internet-Draft                                                    Akamai</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Updates: 4271 (if approved)                                  J. Snijders</td><td> </td><td class="right">Updates: 4271 (if approved)                                  J. Snijders</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Intended status: Standards Track                                     NTT</td><td> </td><td class="right">Intended status: Standards Track                                     NTT</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0001" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">Expires: November <span class="delete">9, 2017 </span>                                    G. Hankins</td><td> </td><td class="rblock">Expires: November <span class="insert">23, 2017</span>                                    G. Hankins</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">                                                                   Nokia</td><td> </td><td class="right">                                                                   Nokia</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0002" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                            <span class="delete"> May 8</span>, 2017</td><td> </td><td class="rblock">                                                            <span class="insert">May 22</span>, 2017</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">        Default EBGP Route Propagation Behavior Without Policies</td><td> </td><td class="right">        Default EBGP Route Propagation Behavior Without Policies</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0003" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">                     draft-ietf-grow-bgp-reject-0<span class="delete">7</span></td><td> </td><td class="rblock">                     draft-ietf-grow-bgp-reject-0<span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Abstract</td><td> </td><td class="right">Abstract</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This document updates RFC4271 by defining the default behavior of a</td><td> </td><td class="right">   This document updates RFC4271 by defining the default behavior of a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   BGP speaker when there is no Import or Export Policy associated with</td><td> </td><td class="right">   BGP speaker when there is no Import or Export Policy associated with</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   an External BGP session.</td><td> </td><td class="right">   an External BGP session.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Requirements Language</td><td> </td><td class="right">Requirements Language</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td> </td><td class="right">   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l2" /><small>skipping to change at</small><em> page 1, line 41</em></th><th> </th><th><a name="part-r2" /><small>skipping to change at</small><em> page 1, line 41</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are working documents of the Internet Engineering</td><td> </td><td class="right">   Internet-Drafts are working documents of the Internet Engineering</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Task Force (IETF).  Note that other groups may also distribute</td><td> </td><td class="right">   Task Force (IETF).  Note that other groups may also distribute</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   working documents as Internet-Drafts.  The list of current Internet-</td><td> </td><td class="right">   working documents as Internet-Drafts.  The list of current Internet-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td> </td><td class="right">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are draft documents valid for a maximum of six months</td><td> </td><td class="right">   Internet-Drafts are draft documents valid for a maximum of six months</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   and may be updated, replaced, or obsoleted by other documents at any</td><td> </td><td class="right">   and may be updated, replaced, or obsoleted by other documents at any</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   time.  It is inappropriate to use Internet-Drafts as reference</td><td> </td><td class="right">   time.  It is inappropriate to use Internet-Drafts as reference</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   material or to cite them other than as "work in progress."</td><td> </td><td class="right">   material or to cite them other than as "work in progress."</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0004" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   This Internet-Draft will expire on November <span class="delete">9</span>, 2017.</td><td> </td><td class="rblock">   This Internet-Draft will expire on November <span class="insert">23</span>, 2017.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Copyright Notice</td><td> </td><td class="right">Copyright Notice</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Copyright (c) 2017 IETF Trust and the persons identified as the</td><td> </td><td class="right">   Copyright (c) 2017 IETF Trust and the persons identified as the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   document authors.  All rights reserved.</td><td> </td><td class="right">   document authors.  All rights reserved.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td> </td><td class="right">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Provisions Relating to IETF Documents</td><td> </td><td class="right">   Provisions Relating to IETF Documents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td> </td><td class="right">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   publication of this document.  Please review these documents</td><td> </td><td class="right">   publication of this document.  Please review these documents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 2, line 25</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 2, line 25</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3</td><td> </td><td class="right">   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   3.  Changes to RFC4271  . . . . . . . . . . . . . . . . . . . . .   3</td><td> </td><td class="right">   3.  Changes to RFC4271  . . . . . . . . . . . . . . . . . . . . .   3</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   4.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4</td><td> </td><td class="right">   4.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4</td><td> </td><td class="right">   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4</td><td> </td><td class="right">   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   4</td><td> </td><td class="right">   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5</td><td> </td><td class="right">   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5</td><td> </td><td class="right">     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5</td><td> </td><td class="right">     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix A.  Transition Considerations  . . . . . . . . . . . . .   5</td><td> </td><td class="right">   Appendix A.  Transition Considerations  . . . . . . . . . . . . .   5</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0005" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">     A.1.  <span class="delete">N+1 N+2 Release Strategy  .</span> . . . . . . . . . . . . . . .   5</td><td> </td><td class="rblock">     A.1.  <span class="insert">"N+1 N+2" Release Strategy </span> . . . . . . . . . . . . . . .   5</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6</td><td> </td><td class="right">   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">1.  Introduction</td><td> </td><td class="right">1.  Introduction</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   BGP routing security issues need to be addressed in order to make the</td><td> </td><td class="right">   BGP routing security issues need to be addressed in order to make the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Internet more stable.  Route leaks [RFC7908] are part of the problem,</td><td> </td><td class="right">   Internet more stable.  Route leaks [RFC7908] are part of the problem,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   but software defects or operator misconfiguration can contribute too.</td><td> </td><td class="right">   but software defects or operator misconfiguration can contribute too.</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0006" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   This document updates [RFC4271] <span class="delete">in order to improve</span> the default level</td><td> </td><td class="rblock">   This document updates [RFC4271] <span class="insert">so that routes are neither imported</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   of Internet routing security.</td><td> </td><td class="rblock"><span class="insert">   nor exported unless specifically enabled by configuration, thus</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   reducing the consequences of these problems, and so improving</span> the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   default level of Internet routing security.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Many deployed BGP speakers send and accept any and all route</td><td> </td><td class="right">   Many deployed BGP speakers send and accept any and all route</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   announcements between their BGP neighbors by default.  This practice</td><td> </td><td class="right">   announcements between their BGP neighbors by default.  This practice</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   dates back to the early days of the Internet, where operators were</td><td> </td><td class="right">   dates back to the early days of the Internet, where operators were</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   permissive in sending routing information to allow all networks to</td><td> </td><td class="right">   permissive in sending routing information to allow all networks to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   reach each other.  As the Internet has become more densely</td><td> </td><td class="right">   reach each other.  As the Internet has become more densely</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   interconnected, the risk of a misbehaving BGP speaker poses</td><td> </td><td class="right">   interconnected, the risk of a misbehaving BGP speaker poses</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   significant risks to Internet routing.</td><td> </td><td class="right">   significant risks to Internet routing.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This specification intends to improve this situation by requiring the</td><td> </td><td class="right">   This specification intends to improve this situation by requiring the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   explicit configuration of both BGP Import and Export Policies for any</td><td> </td><td class="right">   explicit configuration of both BGP Import and Export Policies for any</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   External BGP (EBGP) session such as customers, peers, or</td><td> </td><td class="right">   External BGP (EBGP) session such as customers, peers, or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   confederation boundaries for all enabled address families.  Through</td><td> </td><td class="right">   confederation boundaries for all enabled address families.  Through</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   codification of the aforementioned requirement, operators will</td><td> </td><td class="right">   codification of the aforementioned requirement, operators will</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   benefit from consistent behaviour across different BGP</td><td> </td><td class="right">   benefit from consistent behaviour across different BGP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   implementations.</td><td> </td><td class="right">   implementations.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   BGP speakers following this specification do not use or send routes</td><td> </td><td class="right">   BGP speakers following this specification do not use or send routes</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0007" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   on EBGP sessions, unless <span class="delete">configured to do otherwise</span>.</td><td> </td><td class="rblock">   on EBGP sessions, unless <span class="insert">specifically configured to do so</span>.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">2.  Terminology</td><td> </td><td class="right">2.  Terminology</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC4271] describes a Policy Information Base (PIB) which contains</td><td> </td><td class="right">   [RFC4271] describes a Policy Information Base (PIB) which contains</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   local policies that can be applied to the information in the Routing</td><td> </td><td class="right">   local policies that can be applied to the information in the Routing</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0008" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Information Base (RIB).  This document distinguishes the type of</td><td> </td><td class="rblock">   Information Base (RIB).  This document distinguishes the type of<span class="insert"> a</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   policy based on its application.</td><td> </td><td class="right">   policy based on its application.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Import Policy: a local policy to be applied to the information</td><td> </td><td class="right">   Import Policy: a local policy to be applied to the information</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   contained in the Adj-RIBs-In.  As described in Section 3.2 [RFC4271],</td><td> </td><td class="right">   contained in the Adj-RIBs-In.  As described in Section 3.2 [RFC4271],</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the Adj-RIBs-In contain information learned from other BGP speakers,</td><td> </td><td class="right">   the Adj-RIBs-In contain information learned from other BGP speakers,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   and the application of the Import Policy results in the routes that</td><td> </td><td class="right">   and the application of the Import Policy results in the routes that</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   will be considered in the Decision Process by the local BGP speaker.</td><td> </td><td class="right">   will be considered in the Decision Process by the local BGP speaker.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Export Policy: a local policy to be applied in selecting the</td><td> </td><td class="right">   Export Policy: a local policy to be applied in selecting the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   information contained in the Adj-RIBs-Out.  As described in</td><td> </td><td class="right">   information contained in the Adj-RIBs-Out.  As described in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Section 3.2 [RFC4271], the Adj-RIBs-Out contain information that has</td><td> </td><td class="right">   Section 3.2 [RFC4271], the Adj-RIBs-Out contain information that has</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   been selected for advertisement to other BGP speakers.</td><td> </td><td class="right">   been selected for advertisement to other BGP speakers.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">3.  Changes to RFC4271</td><td> </td><td class="right">3.  Changes to RFC4271</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0009" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   This section <span class="delete">describes the Updates to</span> [RFC4271] <span class="delete">that define</span> the</td><td> </td><td class="rblock">   This section <span class="insert">updates</span> [RFC4271] <span class="insert">to specify</span> the default behavior of a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   default behavior of a BGP speaker when there are no Import or Export</td><td> </td><td class="rblock">   BGP speaker when there are no Import or Export Policies associated</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Policies associated with a particular EBGP session.  A BGP speaker</td><td> </td><td class="rblock">   with a particular EBGP session.  A BGP speaker MAY provide a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   MAY provide a configuration option to deviate from the following</td><td> </td><td class="rblock">   configuration option to deviate from the following updated behaviors.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   updated behaviors.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The following paragraph is added to Section 9.1 (Decision Process)</td><td> </td><td class="right">   The following paragraph is added to Section 9.1 (Decision Process)</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0010" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   after the fifth paragraph<span class="delete"> ending</span> in "route aggregation and route</td><td> </td><td class="rblock">   after the fifth paragraph<span class="insert">, which ends</span> in "route aggregation and route</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   information reduction":</td><td> </td><td class="right">   information reduction":</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Routes contained in an Adj-RIB-In associated with an EBGP peer</td><td> </td><td class="right">      Routes contained in an Adj-RIB-In associated with an EBGP peer</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      SHALL NOT be considered eligible in the Decision Process if no</td><td> </td><td class="right">      SHALL NOT be considered eligible in the Decision Process if no</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      explicit Import Policy has been applied.</td><td> </td><td class="right">      explicit Import Policy has been applied.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The following paragraph is added to Section 9.1.3 (Phase 3: Route</td><td> </td><td class="right">   The following paragraph is added to Section 9.1.3 (Phase 3: Route</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0011" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Dissemination) after the third <span class="delete">paragraph ending</span> in "by means of an</td><td> </td><td class="rblock">   Dissemination) after the third <span class="insert">paragraph, which ends</span> in "by means of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   UPDATE message (see 9.2).":</td><td> </td><td class="rblock">   an UPDATE message (see 9.2).":</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Routes SHALL NOT be added to an Adj-RIB-Out associated with an</td><td> </td><td class="right">      Routes SHALL NOT be added to an Adj-RIB-Out associated with an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      EBGP peer if no explicit Export Policy has been applied.</td><td> </td><td class="right">      EBGP peer if no explicit Export Policy has been applied.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">4.  Acknowledgments</td><td> </td><td class="right">4.  Acknowledgments</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The authors would like to thank the following people for their</td><td> </td><td class="right">   The authors would like to thank the following people for their</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   comments, support and review: Shane Amante, Christopher Morrow,</td><td> </td><td class="right">   comments, support and review: Shane Amante, Christopher Morrow,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Robert Raszuk, Greg Skinner, Adam Chappell, Sriram Kotikalapudi,</td><td> </td><td class="right">   Robert Raszuk, Greg Skinner, Adam Chappell, Sriram Kotikalapudi,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Brian Dickson, Jeffrey Haas, John Heasley, Ignas Bagdonas, Donald</td><td> </td><td class="right">   Brian Dickson, Jeffrey Haas, John Heasley, Ignas Bagdonas, Donald</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0012" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Smith, Dale Worley, Alvaro Retana, <span class="delete">and John Scudder</span>.</td><td> </td><td class="rblock">   Smith, Dale Worley, Alvaro Retana, <span class="insert">John Scudder, and Dale Worley</span>.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.  Security Considerations</td><td> </td><td class="right">5.  Security Considerations</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Permissive default routing policies can result in inadvertent effects</td><td> </td><td class="right">   Permissive default routing policies can result in inadvertent effects</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0013" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   such as route leaks [RFC7908], in general resulting in r<span class="delete">er</span>outing of</td><td> </td><td class="rblock">   such as route leaks [RFC7908], in general resulting in routing of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   traffic through an unexpected path.  While it is possible for an</td><td> </td><td class="right">   traffic through an unexpected path.  While it is possible for an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   operator to use monitoring to detect unexpected flows, there is no</td><td> </td><td class="right">   operator to use monitoring to detect unexpected flows, there is no</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   general framework that can be applied.  These policies also have the</td><td> </td><td class="right">   general framework that can be applied.  These policies also have the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   potential to expose software defects or misconfiguration that could</td><td> </td><td class="right">   potential to expose software defects or misconfiguration that could</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   have unforeseen technical and business impacting effects.</td><td> </td><td class="right">   have unforeseen technical and business impacting effects.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The update to [RFC4271] specified in this document is intended to</td><td> </td><td class="right">   The update to [RFC4271] specified in this document is intended to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   eliminate those inadvertent effects.  Operators must explicitly</td><td> </td><td class="right">   eliminate those inadvertent effects.  Operators must explicitly</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   configure Import and Export Policies to achieve their expected goals.</td><td> </td><td class="right">   configure Import and Export Policies to achieve their expected goals.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   There is of course no protection against a malicious or incorrect</td><td> </td><td class="right">   There is of course no protection against a malicious or incorrect</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 5, line 41</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 5, line 41</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This appendix is non-normative.</td><td> </td><td class="right">   This appendix is non-normative.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   It is anticipated that transitioning to a compliant BGP</td><td> </td><td class="right">   It is anticipated that transitioning to a compliant BGP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   implementation will require a process thay may take several years.</td><td> </td><td class="right">   implementation will require a process thay may take several years.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   It is understood and acknowledged that operators who are taking</td><td> </td><td class="right">   It is understood and acknowledged that operators who are taking</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   advantage of an undefined behavior will always be surprised by</td><td> </td><td class="right">   advantage of an undefined behavior will always be surprised by</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   changes to said behavior.</td><td> </td><td class="right">   changes to said behavior.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0014" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">A.1.  <span class="delete">N+1 N+2</span> Release Strategy</td><td> </td><td class="rblock">A.1.  <span class="insert">"N+1 N+2"</span> Release Strategy</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0015" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   An implementer could leverage an approach described as <span class="delete">"the N+1</span> and</td><td> </td><td class="rblock">   An implementer could leverage an approach described as <span class="insert">the "N+1</span> and</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">N+2</span> release <span class="delete">strategy".</span>  In release N+1, the implementer introduces a</td><td> </td><td class="rblock">   <span class="insert">N+2"</span> release <span class="insert">strategy.</span>  In release N+1, the implementer introduces a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   new default configuration parameter to indicate that the BGP speaker</td><td> </td><td class="right">   new default configuration parameter to indicate that the BGP speaker</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   is operating in "ebgp insecure-mode".  In addition to the</td><td> </td><td class="right">   is operating in "ebgp insecure-mode".  In addition to the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   introduction of the new parameter, an implementer could begin to</td><td> </td><td class="right">   introduction of the new parameter, an implementer could begin to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   display informational warnings to the operator that certain parts of</td><td> </td><td class="right">   display informational warnings to the operator that certain parts of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the configuration are incomplete.  In release N+1, operators of the</td><td> </td><td class="right">   the configuration are incomplete.  In release N+1, operators of the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   BGP implementation become aware that a configurable default exists in</td><td> </td><td class="right">   BGP implementation become aware that a configurable default exists in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the implementation, and can prepare accordingly.  In release N+2 or</td><td> </td><td class="right">   the implementation, and can prepare accordingly.  In release N+2 or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   later, the inverse of the previous default configuration parameter</td><td> </td><td class="right">   later, the inverse of the previous default configuration parameter</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   that was introduced in release N+1 becomes the new default.</td><td> </td><td class="right">   that was introduced in release N+1 becomes the new default.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>

     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 15 change blocks.&nbsp;</a></th></tr>
     <tr class="stats"><td></td><th><i>22 lines changed or deleted</i></th><th><i> </i></th><th><i>23 lines changed or added</i></th><td></td></tr>
     <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.41. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/" >http://tools.ietf.org/tools/rfcdiff/</a> </td></tr>
   </table>
   </body>
   </html>

--dt2phjyidgxxemhj--


From nobody Mon May 22 08:08:34 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 CC80912EB01; Mon, 22 May 2017 08:08:31 -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: draft-ietf-netmod-yang-model-classification.all@ietf.org, ietf@ietf.org, netmod@ietf.org
Subject: Genart telechat review of draft-ietf-netmod-yang-model-classification-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149546571178.4974.504818721239081419@ietfa.amsl.com>
Date: Mon, 22 May 2017 08:08:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nkAHyEle-pgviBQx0P5ws4P2ku8>
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, 22 May 2017 15:08:32 -0000

Reviewer: Pete Resnick
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-ietf-netmod-yang-model-classification-07
Reviewer: Pete Resnick
Review Date: 2017-05-22
IETF LC End Date: 2017-05-14
IESG Telechat date: 2017-06-08

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments: None

Thanks for addressing my comments in the Last Call review.



From nobody Mon May 22 09:19:56 2017
Return-Path: <greg.hankins@nokia.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 912A012EB25; Mon, 22 May 2017 09:19:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.943
X-Spam-Level: 
X-Spam-Status: No, score=-1.943 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665, T_HTML_ATTACH=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 sQR0dWQgVNCt; Mon, 22 May 2017 09:19:35 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BF0012EB23; Mon, 22 May 2017 09:19:35 -0700 (PDT)
Received: from [24.125.34.202] (helo=misfits.twoguys.org) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <greg.hankins@nokia.com>) id 1dCq3R-0000EV-0o; Mon, 22 May 2017 12:19:33 -0400
Received: from misfits.twoguys.org (localhost.twoguys.org [127.0.0.1]) by misfits.twoguys.org (8.14.7/8.12.11) with ESMTP id v4MGJMOp018186; Mon, 22 May 2017 12:19:22 -0400
Received: (from ghankins@localhost) by misfits.twoguys.org (8.14.7/8.14.7/Submit) id v4MGJLAo018185; Mon, 22 May 2017 12:19:21 -0400
X-Authentication-Warning: misfits.twoguys.org: ghankins set sender to greg.hankins@nokia.com using -f
Date: Mon, 22 May 2017 12:19:21 -0400
From: "Hankins, Greg (Nokia - US)" <greg.hankins@nokia.com>
To: Dale Worley <worley@ariadne.com>
Cc: gen-art@ietf.org, draft-ietf-grow-bgp-reject.all@ietf.org, grow@ietf.org,  ietf@ietf.org
Subject: Re: Genart telechat review of draft-ietf-grow-bgp-reject-07
Message-ID: <20170522161921.GA17980@nokia.com>
References: <149521797450.18806.9588203462855463048@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="d6Gm4EdcadzBjdND"
Content-Disposition: inline
In-Reply-To: <149521797450.18806.9588203462855463048@ietfa.amsl.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-ELNK-Trace: 176464c9115cf5b39c7f779228e2f6aeda0071232e20db4d43b7b54aa7f93ff0f989519b717e82d2350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.125.34.202
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W1GoQQz9lxuN-ctPdQV2zbay3zE>
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, 22 May 2017 16:19:40 -0000

--d6Gm4EdcadzBjdND
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Fri, May 19, 2017 at 11:19:34AM -0700, Dale Worley wrote:
>This paragraph is a good introduction, but it isn't very cohesive.  I
>suggest revising the third sentence to something like:
>
>   This document updates [RFC4271] so that routes are neither imported
>   nor exported unless specifically enabled by configuration, thus
>   reducing the consequences of these problems, and so improving the
>   default level of Internet routing security.

Hi Dale, this paragraphs seems wordy now, so I would suggested splitting
sentences as follows:

This document updates [RFC4271] so that routes are neither imported nor
exported unless specifically enabled by configuration.  The solution
reduces the consequences of these problems, and improves the default level
of Internet routing security.

>You probably want to s/a compliant BGP implementation/compliant BGP
>implementations/, unless you are describing the process for an
>individual operator, not for all operators collectively.

As Job said, this was a transition consideration for BGP implementers.

How about this change for clarity:
- old: It is anticipated that transitioning to a compliant BGP implementation
will require a process thay may take several years.
- new: Transitioning to a compliant BGP implementation may require a software
development and release process that can take implementers several years.

I attached a new -07 -> -08 htmldiff that incorporates my edits and
Job's edits.

Greg

--
Greg Hankins <ghankins@mindspring.com>

--d6Gm4EdcadzBjdND
Content-Type: text/html; charset=us-ascii
Content-Disposition: attachment; filename="draft-ietf-grow-bgp-reject-08-from-7.diff.html"

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 
<!-- Generated by rfcdiff 1.41: rfcdiff  --> 
<!-- <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional" > -->
<!-- System: Darwin hanna.meerval.net 16.5.0 Darwin Kernel Version 16.5.0: Fri Mar  3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64 --> 
<!-- Using awk: /usr/local/bin/gawk: GNU Awk 4.1.4, API: 1.1 (GNU MPFR 3.1.5, GNU MP 6.1.2) --> 
<!-- Using diff: /usr/bin/diff: diff (GNU diffutils) 2.8.1 --> 
<!-- Using wdiff: /usr/local/bin/wdiff: wdiff (GNU wdiff) 1.2.2 --> 
<html> 
<head> 
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> 
  <meta http-equiv="Content-Style-Type" content="text/css" /> 
  <title>Diff: draft-ietf-grow-bgp-reject-07.txt - draft-ietf-grow-bgp-reject-08.txt</title> 
  <style type="text/css"> 
    body    { margin: 0.4ex; margin-right: auto; } 
    tr      { } 
    td      { white-space: pre; font-family: monospace; vertical-align: top; font-size: 0.86em;} 
    th      { font-size: 0.86em; } 
    .small  { font-size: 0.6em; font-style: italic; font-family: Verdana, Helvetica, sans-serif; } 
    .left   { background-color: #EEE; } 
    .right  { background-color: #FFF; } 
    .diff   { background-color: #CCF; } 
    .lblock { background-color: #BFB; } 
    .rblock { background-color: #FF8; } 
    .insert { background-color: #8FF; } 
    .delete { background-color: #ACF; } 
    .void   { background-color: #FFB; } 
    .cont   { background-color: #EEE; } 
    .linebr { background-color: #AAA; } 
    .lineno { color: red; background-color: #FFF; font-size: 0.7em; text-align: right; padding: 0 2px; } 
    .elipsis{ background-color: #AAA; } 
    .left .cont { background-color: #DDD; } 
    .right .cont { background-color: #EEE; } 
    .lblock .cont { background-color: #9D9; } 
    .rblock .cont { background-color: #DD6; } 
    .insert .cont { background-color: #0DD; } 
    .delete .cont { background-color: #8AD; } 
    .stats, .stats td, .stats th { background-color: #EEE; padding: 2px 0; } 
  </style> 
</head> 
<body > 
  <table border="0" cellpadding="0" cellspacing="0"> 
  <tr bgcolor="orange"><th></th><th>&nbsp;draft-ietf-grow-bgp-reject-07.txt&nbsp;</th><th> </th><th>&nbsp;draft-ietf-grow-bgp-reject-08.txt&nbsp;</th><th></th></tr> 
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Global Routing Operations                                       J. Mauch</td><td> </td><td class="right">Global Routing Operations                                       J. Mauch</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Internet-Draft                                                    Akamai</td><td> </td><td class="right">Internet-Draft                                                    Akamai</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Updates: 4271 (if approved)                                  J. Snijders</td><td> </td><td class="right">Updates: 4271 (if approved)                                  J. Snijders</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Intended status: Standards Track                                     NTT</td><td> </td><td class="right">Intended status: Standards Track                                     NTT</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0001" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">Expires: November <span class="delete">9, 2017 </span>                                    G. Hankins</td><td> </td><td class="rblock">Expires: November <span class="insert">23, 2017</span>                                    G. Hankins</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">                                                                   Nokia</td><td> </td><td class="right">                                                                   Nokia</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0002" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                            <span class="delete"> May 8</span>, 2017</td><td> </td><td class="rblock">                                                            <span class="insert">May 22</span>, 2017</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">        Default EBGP Route Propagation Behavior Without Policies</td><td> </td><td class="right">        Default EBGP Route Propagation Behavior Without Policies</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0003" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">                     draft-ietf-grow-bgp-reject-0<span class="delete">7</span></td><td> </td><td class="rblock">                     draft-ietf-grow-bgp-reject-0<span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Abstract</td><td> </td><td class="right">Abstract</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This document updates RFC4271 by defining the default behavior of a</td><td> </td><td class="right">   This document updates RFC4271 by defining the default behavior of a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   BGP speaker when there is no Import or Export Policy associated with</td><td> </td><td class="right">   BGP speaker when there is no Import or Export Policy associated with</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   an External BGP session.</td><td> </td><td class="right">   an External BGP session.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Requirements Language</td><td> </td><td class="right">Requirements Language</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td> </td><td class="right">   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l2" /><small>skipping to change at</small><em> page 1, line 41</em></th><th> </th><th><a name="part-r2" /><small>skipping to change at</small><em> page 1, line 41</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are working documents of the Internet Engineering</td><td> </td><td class="right">   Internet-Drafts are working documents of the Internet Engineering</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Task Force (IETF).  Note that other groups may also distribute</td><td> </td><td class="right">   Task Force (IETF).  Note that other groups may also distribute</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   working documents as Internet-Drafts.  The list of current Internet-</td><td> </td><td class="right">   working documents as Internet-Drafts.  The list of current Internet-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td> </td><td class="right">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are draft documents valid for a maximum of six months</td><td> </td><td class="right">   Internet-Drafts are draft documents valid for a maximum of six months</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   and may be updated, replaced, or obsoleted by other documents at any</td><td> </td><td class="right">   and may be updated, replaced, or obsoleted by other documents at any</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   time.  It is inappropriate to use Internet-Drafts as reference</td><td> </td><td class="right">   time.  It is inappropriate to use Internet-Drafts as reference</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   material or to cite them other than as "work in progress."</td><td> </td><td class="right">   material or to cite them other than as "work in progress."</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0004" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   This Internet-Draft will expire on November <span class="delete">9</span>, 2017.</td><td> </td><td class="rblock">   This Internet-Draft will expire on November <span class="insert">23</span>, 2017.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Copyright Notice</td><td> </td><td class="right">Copyright Notice</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Copyright (c) 2017 IETF Trust and the persons identified as the</td><td> </td><td class="right">   Copyright (c) 2017 IETF Trust and the persons identified as the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   document authors.  All rights reserved.</td><td> </td><td class="right">   document authors.  All rights reserved.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td> </td><td class="right">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Provisions Relating to IETF Documents</td><td> </td><td class="right">   Provisions Relating to IETF Documents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td> </td><td class="right">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   publication of this document.  Please review these documents</td><td> </td><td class="right">   publication of this document.  Please review these documents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 2, line 25</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 2, line 25</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3</td><td> </td><td class="right">   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   3.  Changes to RFC4271  . . . . . . . . . . . . . . . . . . . . .   3</td><td> </td><td class="right">   3.  Changes to RFC4271  . . . . . . . . . . . . . . . . . . . . .   3</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   4.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4</td><td> </td><td class="right">   4.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4</td><td> </td><td class="right">   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4</td><td> </td><td class="right">   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   4</td><td> </td><td class="right">   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5</td><td> </td><td class="right">   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5</td><td> </td><td class="right">     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5</td><td> </td><td class="right">     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix A.  Transition Considerations  . . . . . . . . . . . . .   5</td><td> </td><td class="right">   Appendix A.  Transition Considerations  . . . . . . . . . . . . .   5</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0005" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">     A.1.  <span class="delete">N+1 N+2 Release Strategy  .</span> . . . . . . . . . . . . . . .   5</td><td> </td><td class="rblock">     A.1.  <span class="insert">"N+1 N+2" Release Strategy </span> . . . . . . . . . . . . . . .   5</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6</td><td> </td><td class="right">   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">1.  Introduction</td><td> </td><td class="right">1.  Introduction</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   BGP routing security issues need to be addressed in order to make the</td><td> </td><td class="right">   BGP routing security issues need to be addressed in order to make the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Internet more stable.  Route leaks [RFC7908] are part of the problem,</td><td> </td><td class="right">   Internet more stable.  Route leaks [RFC7908] are part of the problem,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   but software defects or operator misconfiguration can contribute too.</td><td> </td><td class="right">   but software defects or operator misconfiguration can contribute too.</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0006" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   This document updates [RFC4271] <span class="delete">in order to improve</span> the default level</td><td> </td><td class="rblock">   This document updates [RFC4271] <span class="insert">so that routes are neither imported</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   of Internet routing security.</td><td> </td><td class="rblock"><span class="insert">   nor exported unless specifically enabled by configuration.  The</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   solution reduces the consequences of these problems, and improves</span> the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   default level of Internet routing security.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Many deployed BGP speakers send and accept any and all route</td><td> </td><td class="right">   Many deployed BGP speakers send and accept any and all route</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   announcements between their BGP neighbors by default.  This practice</td><td> </td><td class="right">   announcements between their BGP neighbors by default.  This practice</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   dates back to the early days of the Internet, where operators were</td><td> </td><td class="right">   dates back to the early days of the Internet, where operators were</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   permissive in sending routing information to allow all networks to</td><td> </td><td class="right">   permissive in sending routing information to allow all networks to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   reach each other.  As the Internet has become more densely</td><td> </td><td class="right">   reach each other.  As the Internet has become more densely</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   interconnected, the risk of a misbehaving BGP speaker poses</td><td> </td><td class="right">   interconnected, the risk of a misbehaving BGP speaker poses</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   significant risks to Internet routing.</td><td> </td><td class="right">   significant risks to Internet routing.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This specification intends to improve this situation by requiring the</td><td> </td><td class="right">   This specification intends to improve this situation by requiring the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   explicit configuration of both BGP Import and Export Policies for any</td><td> </td><td class="right">   explicit configuration of both BGP Import and Export Policies for any</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   External BGP (EBGP) session such as customers, peers, or</td><td> </td><td class="right">   External BGP (EBGP) session such as customers, peers, or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   confederation boundaries for all enabled address families.  Through</td><td> </td><td class="right">   confederation boundaries for all enabled address families.  Through</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   codification of the aforementioned requirement, operators will</td><td> </td><td class="right">   codification of the aforementioned requirement, operators will</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   benefit from consistent behaviour across different BGP</td><td> </td><td class="right">   benefit from consistent behaviour across different BGP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   implementations.</td><td> </td><td class="right">   implementations.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   BGP speakers following this specification do not use or send routes</td><td> </td><td class="right">   BGP speakers following this specification do not use or send routes</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0007" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   on EBGP sessions, unless <span class="delete">configured to do otherwise</span>.</td><td> </td><td class="rblock">   on EBGP sessions, unless <span class="insert">specifically configured to do so</span>.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">2.  Terminology</td><td> </td><td class="right">2.  Terminology</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC4271] describes a Policy Information Base (PIB) which contains</td><td> </td><td class="right">   [RFC4271] describes a Policy Information Base (PIB) which contains</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   local policies that can be applied to the information in the Routing</td><td> </td><td class="right">   local policies that can be applied to the information in the Routing</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0008" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Information Base (RIB).  This document distinguishes the type of</td><td> </td><td class="rblock">   Information Base (RIB).  This document distinguishes the type of<span class="insert"> a</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   policy based on its application.</td><td> </td><td class="right">   policy based on its application.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Import Policy: a local policy to be applied to the information</td><td> </td><td class="right">   Import Policy: a local policy to be applied to the information</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   contained in the Adj-RIBs-In.  As described in Section 3.2 [RFC4271],</td><td> </td><td class="right">   contained in the Adj-RIBs-In.  As described in Section 3.2 [RFC4271],</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the Adj-RIBs-In contain information learned from other BGP speakers,</td><td> </td><td class="right">   the Adj-RIBs-In contain information learned from other BGP speakers,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   and the application of the Import Policy results in the routes that</td><td> </td><td class="right">   and the application of the Import Policy results in the routes that</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   will be considered in the Decision Process by the local BGP speaker.</td><td> </td><td class="right">   will be considered in the Decision Process by the local BGP speaker.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Export Policy: a local policy to be applied in selecting the</td><td> </td><td class="right">   Export Policy: a local policy to be applied in selecting the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   information contained in the Adj-RIBs-Out.  As described in</td><td> </td><td class="right">   information contained in the Adj-RIBs-Out.  As described in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Section 3.2 [RFC4271], the Adj-RIBs-Out contain information that has</td><td> </td><td class="right">   Section 3.2 [RFC4271], the Adj-RIBs-Out contain information that has</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   been selected for advertisement to other BGP speakers.</td><td> </td><td class="right">   been selected for advertisement to other BGP speakers.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">3.  Changes to RFC4271</td><td> </td><td class="right">3.  Changes to RFC4271</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0009" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   This section <span class="delete">describes the Updates to</span> [RFC4271] <span class="delete">that define</span> the</td><td> </td><td class="rblock">   This section <span class="insert">updates</span> [RFC4271] <span class="insert">to specify</span> the default behavior of a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   default behavior of a BGP speaker when there are no Import or Export</td><td> </td><td class="rblock">   BGP speaker when there are no Import or Export Policies associated</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Policies associated with a particular EBGP session.  A BGP speaker</td><td> </td><td class="rblock">   with a particular EBGP session.  A BGP speaker MAY provide a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   MAY provide a configuration option to deviate from the following</td><td> </td><td class="rblock">   configuration option to deviate from the following updated behaviors.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   updated behaviors.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The following paragraph is added to Section 9.1 (Decision Process)</td><td> </td><td class="right">   The following paragraph is added to Section 9.1 (Decision Process)</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0010" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   after the fifth paragraph<span class="delete"> ending</span> in "route aggregation and route</td><td> </td><td class="rblock">   after the fifth paragraph<span class="insert">, which ends</span> in "route aggregation and route</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   information reduction":</td><td> </td><td class="right">   information reduction":</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Routes contained in an Adj-RIB-In associated with an EBGP peer</td><td> </td><td class="right">      Routes contained in an Adj-RIB-In associated with an EBGP peer</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      SHALL NOT be considered eligible in the Decision Process if no</td><td> </td><td class="right">      SHALL NOT be considered eligible in the Decision Process if no</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      explicit Import Policy has been applied.</td><td> </td><td class="right">      explicit Import Policy has been applied.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The following paragraph is added to Section 9.1.3 (Phase 3: Route</td><td> </td><td class="right">   The following paragraph is added to Section 9.1.3 (Phase 3: Route</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0011" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Dissemination) after the third <span class="delete">paragraph ending</span> in "by means of an</td><td> </td><td class="rblock">   Dissemination) after the third <span class="insert">paragraph, which ends</span> in "by means of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   UPDATE message (see 9.2).":</td><td> </td><td class="rblock">   an UPDATE message (see 9.2).":</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      Routes SHALL NOT be added to an Adj-RIB-Out associated with an</td><td> </td><td class="right">      Routes SHALL NOT be added to an Adj-RIB-Out associated with an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      EBGP peer if no explicit Export Policy has been applied.</td><td> </td><td class="right">      EBGP peer if no explicit Export Policy has been applied.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">4.  Acknowledgments</td><td> </td><td class="right">4.  Acknowledgments</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The authors would like to thank the following people for their</td><td> </td><td class="right">   The authors would like to thank the following people for their</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   comments, support and review: Shane Amante, Christopher Morrow,</td><td> </td><td class="right">   comments, support and review: Shane Amante, Christopher Morrow,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Robert Raszuk, Greg Skinner, Adam Chappell, Sriram Kotikalapudi,</td><td> </td><td class="right">   Robert Raszuk, Greg Skinner, Adam Chappell, Sriram Kotikalapudi,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Brian Dickson, Jeffrey Haas, John Heasley, Ignas Bagdonas, Donald</td><td> </td><td class="right">   Brian Dickson, Jeffrey Haas, John Heasley, Ignas Bagdonas, Donald</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0012" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Smith, Dale Worley, Alvaro Retana, <span class="delete">and John Scudder</span>.</td><td> </td><td class="rblock">   Smith, Dale Worley, Alvaro Retana, <span class="insert">John Scudder, and Dale Worley</span>.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.  Security Considerations</td><td> </td><td class="right">5.  Security Considerations</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Permissive default routing policies can result in inadvertent effects</td><td> </td><td class="right">   Permissive default routing policies can result in inadvertent effects</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0013" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   such as route leaks [RFC7908], in general resulting in r<span class="delete">er</span>outing of</td><td> </td><td class="rblock">   such as route leaks [RFC7908], in general resulting in routing of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   traffic through an unexpected path.  While it is possible for an</td><td> </td><td class="right">   traffic through an unexpected path.  While it is possible for an</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   operator to use monitoring to detect unexpected flows, there is no</td><td> </td><td class="right">   operator to use monitoring to detect unexpected flows, there is no</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   general framework that can be applied.  These policies also have the</td><td> </td><td class="right">   general framework that can be applied.  These policies also have the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   potential to expose software defects or misconfiguration that could</td><td> </td><td class="right">   potential to expose software defects or misconfiguration that could</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   have unforeseen technical and business impacting effects.</td><td> </td><td class="right">   have unforeseen technical and business impacting effects.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The update to [RFC4271] specified in this document is intended to</td><td> </td><td class="right">   The update to [RFC4271] specified in this document is intended to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   eliminate those inadvertent effects.  Operators must explicitly</td><td> </td><td class="right">   eliminate those inadvertent effects.  Operators must explicitly</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   configure Import and Export Policies to achieve their expected goals.</td><td> </td><td class="right">   configure Import and Export Policies to achieve their expected goals.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   There is of course no protection against a malicious or incorrect</td><td> </td><td class="right">   There is of course no protection against a malicious or incorrect</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 5, line 34</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 5, line 34</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7908]  Sriram, K., Montgomery, D., McPherson, D., Osterweil, E.,</td><td> </td><td class="right">   [RFC7908]  Sriram, K., Montgomery, D., McPherson, D., Osterweil, E.,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              and B. Dickson, "Problem Definition and Classification of</td><td> </td><td class="right">              and B. Dickson, "Problem Definition and Classification of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              BGP Route Leaks", RFC 7908, DOI 10.17487/RFC7908, June</td><td> </td><td class="right">              BGP Route Leaks", RFC 7908, DOI 10.17487/RFC7908, June</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              2016, &lt;http://www.rfc-editor.org/info/rfc7908&gt;.</td><td> </td><td class="right">              2016, &lt;http://www.rfc-editor.org/info/rfc7908&gt;.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Appendix A.  Transition Considerations</td><td> </td><td class="right">Appendix A.  Transition Considerations</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This appendix is non-normative.</td><td> </td><td class="right">   This appendix is non-normative.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0014" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">It is anticipated that transitioning</span> to a compliant BGP</td><td> </td><td class="rblock">   <span class="insert">Transitioning</span> to a compliant BGP implementation <span class="insert">may</span> require a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   implementation <span class="delete">will</span> require a process <span class="delete">thay may</span> take several years.</td><td> </td><td class="rblock">   <span class="insert">software development and release</span> process <span class="insert">that can</span> take <span class="insert">implementers</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   several years.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   It is understood and acknowledged that operators who are taking</td><td> </td><td class="right">   It is understood and acknowledged that operators who are taking</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   advantage of an undefined behavior will always be surprised by</td><td> </td><td class="right">   advantage of an undefined behavior will always be surprised by</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   changes to said behavior.</td><td> </td><td class="right">   changes to said behavior.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0015" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">A.1.  <span class="delete">N+1 N+2</span> Release Strategy</td><td> </td><td class="rblock">A.1.  <span class="insert">"N+1 N+2"</span> Release Strategy</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0016" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   An implementer could leverage an approach described as <span class="delete">"the N+1</span> and</td><td> </td><td class="rblock">   An implementer could leverage an approach described as <span class="insert">the "N+1</span> and</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">N+2</span> release <span class="delete">strategy".</span>  In release N+1, the implementer introduces a</td><td> </td><td class="rblock">   <span class="insert">N+2"</span> release <span class="insert">strategy.</span>  In release N+1, the implementer introduces a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   new default configuration parameter to indicate that the BGP speaker</td><td> </td><td class="right">   new default configuration parameter to indicate that the BGP speaker</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   is operating in "ebgp insecure-mode".  In addition to the</td><td> </td><td class="right">   is operating in "ebgp insecure-mode".  In addition to the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   introduction of the new parameter, an implementer could begin to</td><td> </td><td class="right">   introduction of the new parameter, an implementer could begin to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   display informational warnings to the operator that certain parts of</td><td> </td><td class="right">   display informational warnings to the operator that certain parts of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the configuration are incomplete.  In release N+1, operators of the</td><td> </td><td class="right">   the configuration are incomplete.  In release N+1, operators of the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   BGP implementation become aware that a configurable default exists in</td><td> </td><td class="right">   BGP implementation become aware that a configurable default exists in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the implementation, and can prepare accordingly.  In release N+2 or</td><td> </td><td class="right">   the implementation, and can prepare accordingly.  In release N+2 or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   later, the inverse of the previous default configuration parameter</td><td> </td><td class="right">   later, the inverse of the previous default configuration parameter</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   that was introduced in release N+1 becomes the new default.</td><td> </td><td class="right">   that was introduced in release N+1 becomes the new default.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>

     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 16 change blocks.&nbsp;</a></th></tr>
     <tr class="stats"><td></td><th><i>24 lines changed or deleted</i></th><th><i> </i></th><th><i>26 lines changed or added</i></th><td></td></tr>
     <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.41. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/" >http://tools.ietf.org/tools/rfcdiff/</a> </td></tr>
   </table>
   </body>
   </html>

--d6Gm4EdcadzBjdND--


From nobody Mon May 22 10:35:52 2017
Return-Path: <kaduk@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 CB0BC12EB31; Mon, 22 May 2017 10:35:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.303
X-Spam-Level: 
X-Spam-Status: No, score=-2.303 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_MED=-2.3, 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 gjJkW-SRmM2z; Mon, 22 May 2017 10:35:43 -0700 (PDT)
Received: from dmz-mailsec-scanner-1.mit.edu (dmz-mailsec-scanner-1.mit.edu [18.9.25.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 2F54B1200ED; Mon, 22 May 2017 10:35:43 -0700 (PDT)
X-AuditID: 1209190c-07dff70000001ef4-ff-5923216d00d9
Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-1.mit.edu (Symantec Messaging Gateway) with SMTP id A1.FB.07924.D6123295; Mon, 22 May 2017 13:35:42 -0400 (EDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id v4MHZei6031223; Mon, 22 May 2017 13:35:40 -0400
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v4MHZZb2025266 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 22 May 2017 13:35:38 -0400
Date: Mon, 22 May 2017 12:35:35 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Daniel Migault <daniel.migault@ericsson.com>
Cc: tls <tls@ietf.org>, draft-ietf-tls-ecdhe-psk-aead.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>, secdir@ietf.org
Subject: Re: [TLS] secdir review of draft-ietf-tls-ecdhe-psk-aead-03
Message-ID: <20170522173534.GT39245@kduck.kaduk.org>
References: <20170519043827.GL39245@kduck.kaduk.org> <CADZyTkncMTsTQt6C2S+Z0mw+30uc38bfrTSCOvjWRPn_dJkDLQ@mail.gmail.com> <20170519162725.GM39245@kduck.kaduk.org> <CADZyTk=id9bDfi31R+K6hC+ZKzWsjsvo8JbSCzqYGaK_1X1j7Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CADZyTk=id9bDfi31R+K6hC+ZKzWsjsvo8JbSCzqYGaK_1X1j7Q@mail.gmail.com>
User-Agent: Mutt/1.7.1 (2016-10-04)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrHIsWRmVeSWpSXmKPExsUixG6nopunqBxpcP8Yq8WU6XvYLN4s28Rk MePPRGaLZxvns1h8WPiQxeLT+S5GBzaPX1+vsnksWfKTKYApissmJTUnsyy1SN8ugSvj748D zAXTOSqeLLnA2sC4na2LkZNDQsBEYmXvW8YuRi4OIYHFTBKTbx9hBEkICWxklJjRVwCRuMok 8WD7dCaQBIuAqsS/W+9YQGw2ARWJhu7LzCC2iICBxMsJO9lAGpgFFjBK7GtqAysSFnCRWNG3 BKyIF2hdz45+qA1vGSU2PqiHiAtKnJz5BKyeWUBL4sa/l0DLOIBsaYnl/zhATE6BQIn76/hB KkQFlCX+Hr7HMoFRYBaS5llImmchNC9gZF7FKJuSW6Wbm5iZU5yarFucnJiXl1qka6iXm1mi l5pSuokRFMyckjw7GM+88TrEKMDBqMTDq/FYKVKINbGsuDL3EKMkB5OSKO/RN0AhvqT8lMqM xOKM+KLSnNTiQ4wSHMxKIrx57MqRQrwpiZVVqUX5MClpDhYlcV4JjcYIIYH0xJLU7NTUgtQi mKwMB4eSBO9kBaBGwaLU9NSKtMycEoQ0EwcnyHAeoOGzQWp4iwsSc4sz0yHypxgVpcR5d4Ak BEASGaV5cL2gZCORvb/mFaM40CvCvGUgVTzARAXX/QpoMBPQYOtn8iCDSxIRUlINjK3n5JZk O9V/1Uyc16yopM53cm3Gju8rp1x86aW/YM6es7tXVxm6s6s+0NtTHdWen6ZwnW3R6ndZK55x GlZwLnddckukpXz6S1ed3U7M0rv33v/+TZ7plczSvV6OqRuZZrYp5J+b5dXKnbnRwEmUhana KiFD0VJ5+p5rV+PzL+7oWpqRsVg8UYmlOCPRUIu5qDgRAHMN/G0RAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8KAObX_gg2o9O87cDww30sWdkEM>
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, 22 May 2017 17:35:45 -0000

Sorry for the slow reply.

On Fri, May 19, 2017 at 12:58:07PM -0400, Daniel Migault wrote:
> Thank you,
> 
> Your comments have all been addressed. I have one remaining clarification.
> In my text the SHOULD NOT was intended to the ECDHE_PSK in general, and not
> only for the cipher suites of the draft. In your opinion do we clarify
> this, and should we use something else than SHOULD NOT ?

It's somewhat awkward, as what we really want to do is Update RFC
5489 to add this prohibition there.  But, that's more process to
jump through and this document is already at a late stage, so I do
not actually propose doing that.  I would be okay saying

  As such, all ECDHE_PSK ciphers, including those defined outside
  this document, SHOULD NOT be negotiated in TLS versions prior to
  1.2.

to match up with the MUST NOT text we have for these new ciphers.
(Taking into account Martin's text that the prohibition is on
negotiating them, but offering them in a ClientHello that also
offers the old version is okay.)

-Ben


From nobody Mon May 22 11:59:26 2017
Return-Path: <murch@andrew.cmu.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 2CFB712878D; Mon, 22 May 2017 11:59:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.501
X-Spam-Level: 
X-Spam-Status: No, score=-1.501 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 UpilocMj7ZWp; Mon, 22 May 2017 11:59:22 -0700 (PDT)
Received: from smtp.andrew.cmu.edu (SMTP.ANDREW.CMU.EDU [128.2.105.202]) (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 985AB126C2F; Mon, 22 May 2017 11:59:22 -0700 (PDT)
Received: from [172.31.24.242] (VPN-172-31-24-242.VPN.CMU.LOCAL [172.31.24.242]) (user=murch mech=PLAIN (0 bits)) by smtp.andrew.cmu.edu (8.15.2/8.15.2) with ESMTPSA id v4MIx7xR050219 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 22 May 2017 14:59:08 -0400
Subject: Re: [art] ART Area Review for draft-ietf-calext-caldav-attachments-02
To: Julian Reschke <julian.reschke@gmx.de>, IETF Discussion <ietf@ietf.org>, art@ietf.org
References: <c04f39e2-79d2-ab9d-59ab-26e51d7ab5fc@gmx.de> <81613220-989b-ca78-fe56-0ac7b19e7ce6@andrew.cmu.edu> <b2a4924d-c7c9-b40b-484f-9fab48bfe5de@gmx.de> <a603f3de-2d96-6f86-e0c3-3e0a4884a185@andrew.cmu.edu> <7bcfecea-3a89-978c-9e1b-edf9aac5dd44@gmx.de>
From: Ken Murchison <murch@andrew.cmu.edu>
Organization: Carnegie Mellon University
Message-ID: <07f64bc5-13f6-62a0-3c04-91c780f69672@andrew.cmu.edu>
Date: Mon, 22 May 2017 14:59:07 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <7bcfecea-3a89-978c-9e1b-edf9aac5dd44@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-PMX-Version: 6.3.0.2556906, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.5.22.185116
X-SMTP-Spam-Clean: 10% ( TO_IN_SUBJECT 0.5, HTML_00_01 0.05, HTML_00_10 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, FROM_EDU_TLD 0, IN_REP_TO 0, LEGITIMATE_SIGNS 0, MSG_THREAD 0, MULTIPLE_REAL_RCPTS 0, NO_CTA_URI_FOUND 0, NO_URI_FOUND 0, NO_URI_HTTPS 0, REFERENCES 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CC_NAME 0, __CC_NAME_DIFF_FROM_ACC 0, __CC_REAL_NAMES 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __HAS_CC_HDR 0, __HAS_FROM 0, __HAS_MSGID 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_TEXT_P 0, __MIME_TEXT_P1 0, __MIME_VERSION 0, __MOZILLA_USER_AGENT 0, __NO_HTML_TAG_RAW 0, __PHISH_SPEAR_STRUCTURE_1 0, __REFERENCES 0, __SANE_MSGID 0, __SUBJ_ALPHA_NEGATE 0, __TO_IN_SUBJECT2 0, __TO_MALFORMED_2 0,  __TO_NAME 0, __TO_NAME_DIFF_FROM_ACC 0, __TO_REAL_NAMES 0, __USER_AGENT 0)
X-SMTP-Spam-Score: 10%
X-Scanned-By: MIMEDefang 2.78 on 128.2.105.202
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rEP7Tb-d0ch3h1MbjJpXUSxC1_U>
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, 22 May 2017 18:59:24 -0000

On 05/17/2017 09:58 AM, Julian Reschke wrote:
> On 2017-05-17 15:07, Ken Murchison wrote:
>> ...
>>> Only for creation of the attachment. Once is has been created, it
>>> should have its own URI, and the usual HTTP methods should be 
>>> applicable.
>>
>> Using HTTP methods directly on the attachment URI makes things more
>> difficult because the calendar resource(s) referencing the attachment
>> also need to be updated.  This would have to be done either as a
>> side-effect of the PUT/DELETE on the attachment, or as a separate PUT
>> (and separate round-trips) on the resource(s).  The desire was to avoid
>> doing either one of these, which is why a POST on the calendar resource
>> was chosen as the method to add/update/delete an attachment from a
>> calendar resource.
>
> But the POST is *not* on the calendar resource, but on the calendar 
> resource + query parameters, which, from HTTP's point of view is a 
> different resource already.
>
> Furthermore, what URIs are used is orthogonal to the question of which 
> methods to use.
>
> Why is
>
>   POST /calendar-entry?action=remove&attachment=xyz
>
> easier to process than
>
>   DELETE /calendar-entry?attachment=xyz
>
> or
>
>   DELETE /calendar-entry/attachments/xyz
>
> ?

The issue here is that a single calendar resource may contain multiple 
events (recurring event with overrides) and a particular attachment may 
be associated with more than one instance of that event.  For this 
reason, we felt it best to use the calendar resource as the gateway to 
the attachments, thus allowing manipulating multiple instances of an 
attachment in a single round-trip.  Also, by preventing clients from 
manipulating attachments directly, a CalDAV server isn't forced to alter 
all calendar resources associated with a particular attachment.

We also have a fairly large number of deployed implementations which we 
do not want to make non-compliant by substantially modifying the 
protocol.  At this point, specifying the use of HTTP methods other than 
POST would indeed make existing implementations non-compliant.

We would definitely like to make this protocol conform to current HTTP 
practice where possible, and would also document where we have strayed 
from existing practice if required to do so.  Do you think we can come 
to some kind of consensus that meets these goals?

-- 
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University


From nobody Mon May 22 12:09:18 2017
Return-Path: <wdenniss@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 5B20D128BC8 for <ietf@ietfa.amsl.com>; Mon, 22 May 2017 12:09:02 -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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 y-6NUG4e7CsG for <ietf@ietfa.amsl.com>; Mon, 22 May 2017 12:09:00 -0700 (PDT)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001: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 F2610128954 for <ietf@ietf.org>; Mon, 22 May 2017 12:08:57 -0700 (PDT)
Received: by mail-io0-x235.google.com with SMTP id o12so87801207iod.3 for <ietf@ietf.org>; Mon, 22 May 2017 12:08:57 -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=qxMxstGIbPVZ8QVipkgAGfsdWIIQHnlpSxYnHq/FX9A=; b=jNTFoWUaszqYLLQvtpFwvnJaHfLnK4kIPDjt+fOU/cU+guO3jj656RhIoZZUTULW9o DK51h0x4pP9zfLHVSpA+pxH3HPyKBt5XiWdqm+Qxo9ySa/Vo8bX1hP3Qd7Sw4mItgOaV uyupFlGemKMsqnKUVebp5IyyYol279ZT2a1SXnQAjxng9KPgoj9pgu4+91Rw5bj/Vjdz 4VaDrIQNNTyHkXai6d87gOcbQNffCUu1fhavazMq0z2PhZ5P8qlDJ7fJQhGQExceStca rxsfJQxLfkaxTiBJWCCK4ESW5Cu2tjN3vp+bAPmcFxpbAZHzcajgd97FXYT5rnSnpWGt ZNLA==
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=qxMxstGIbPVZ8QVipkgAGfsdWIIQHnlpSxYnHq/FX9A=; b=iYTn/hC2qHLrUdd3Wh7T3LhXFFQk0caKWNVamgy4BIrs8cGxjEYA+n4mesnhBDzapC AVRb07VSfKYPlmiSDscGNHfKR7HIy2h1Mt46/0WmFl+DjVo9tkKaiWNhQwBbUStfdheO 0Xephw5Rii3Lf8L64Z9Y9mrvQm9yzuEPeraj0NgZ3cESsrbamnQnbc/YMhurAzEQbVIo J1TjwDi6ZrRpXZpPQFbbgy5ur/t3JdusC0hC3XgkjqlInR+jql7AqhAwr1SaKaGoJ6Xv nHD9NCD+IiKL819M+DGqXo5gQvJ6aYqmz8g3Dn+YAA8dBjKvZrSYiKF+BGsTmN4isA4H RAPA==
X-Gm-Message-State: AODbwcBwMehTCBnntmFVc1QpR3Vzwhw5e/qC0gUbiFDzyHQNNLLFgKX0 bMiIP8LvewZXJY0ZB9ngRr7LLZamj6gb
X-Received: by 10.107.6.27 with SMTP id 27mr23657527iog.53.1495480137083; Mon, 22 May 2017 12:08:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.35.37 with HTTP; Mon, 22 May 2017 12:08:36 -0700 (PDT)
In-Reply-To: <E6BC9BBCBCACC246846FC685F9FF41EA2AE094F0@DGGEMM506-MBX.china.huawei.com>
References: <E6BC9BBCBCACC246846FC685F9FF41EA2AE094F0@DGGEMM506-MBX.china.huawei.com>
From: William Denniss <wdenniss@google.com>
Date: Mon, 22 May 2017 12:08:36 -0700
Message-ID: <CAAP42hBSj3_B48SN3VmQR2Z8qa2Nzpo7wL8FPr18TvmmeLWoyw@mail.gmail.com>
Subject: Re: [OPS-DIR] Opsdir telechat review of draft-ietf-oauth-native-apps-10
To: wangzitao <wangzitao@huawei.com>
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>,  "draft-ietf-oauth-native-apps.all@ietf.org" <draft-ietf-oauth-native-apps.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113ee7d25754640550219a2a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Pk-eMLnMKIvLJsj_4M5I6JPIclk>
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, 22 May 2017 19:09:02 -0000

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

Thanks for your review Zitao!

Version 12 addresses your comments. Detailed responses below:

On Sun, May 21, 2017 at 8:05 PM, wangzitao <wangzitao@huawei.com> wrote:

> Reviewer: Zitao Wang (Michael)
>
> Review result: Has Nits
>
>
>
> I have reviewed this document as part of the Operational
> directorate=E2=80=99s ongoing effort to review all IETF documents being p=
rocessed
> by the IESG.  These comments were written with the intent of improving th=
e
> operational aspects of the IETF drafts. Comments that are not addressed i=
n
> 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 las=
t
> call comments.
>
>
>
> Document reviewed:  draft-ietf-oauth-native-apps-10
>
>
>
> Summary:
>
>
>
> OAuth 2.0 authorization requests from native apps should only be made
>
> through external user-agents, primarily the user=E2=80=99s browser. This
>
> specification details the security and usability reasons why this is
>
> the case, and how native apps and authorization servers can implement
>
> this best practice.
>
>
>
> I think the document is written very clear, except some small nits:
>
> Page 3:     The last sentence of introduction-- =E2=80=9CThis practice is=
 also
> known as the AppAuth pattern=E2=80=9D.
>
> I suggest adding a reference to explain the AppAuth pattern.
>
>
Done


> Page 3:     Terminology -- "OAuth".
>
> I suggest modifying to: "OAuth"   The Web Authorization (OAuth) protocol.
> In this document, OAuth refers to OAuth 2.0 [RFC6749].
>
I went with:
"In this document, OAuth refers to the OAuth 2.0 Authorization Framework
[RFC6749]."

The phrase "Web Authorization (OAuth) protocol" only seems to appear in our
WG Charter, and not general usage
<https://www.google.com/search?q=3Dweb+authorization+protocol>.


> Page 4:     Terminology -- "web-view"  A web browser UI component.
>
> Does it mean "User Information"?  Suggest expanding this abbreviation.
>
>
Done.


> Page 5:     Figure 1.   Does the browser and authorization endpoint are
> some kinds of "external user-agent"? Suggest describing it more clearly.
>

Now states:
"illustrates the interaction of the native app with a browser
        external user-agent to authorize the user. "

Page   9:   PKCE [RFC7636] details how this limitation can be used to
> execute a code interception attack (see Figure 1).
>
> Does the Figure 1 means =E2=80=9CFigure 1 of RFC7636=E2=80=9D?
>

Good catch. I delete the figure reference, since the entire spec talks
about this attack, which is likely sufficient.


>
> Page10:     However, as the Implicit Flow cannot be protected by PKCE
>
> Seems here, the reference be omitted.
>

Added.


> A run of idnits revealed no errors, flaws. There were 1 warning and 1 com=
ments though
>
>
>
>   =3D=3D There are 1 instance of lines with non-RFC2606-compliant FQDNs i=
n the
>
>      document.
>
>
>
>
I ran it myself with verbose output, and got:

tmp/draft-ietf-oauth-native-apps__1_.txt(435): Found possible FQDN
'com.example.app' in position 5; this doesn't match RFC 2606's
suggested ".example" or ".example.(com|org|net)".


We are actually using a RFC2606 domain name here, but in reverse domain
name notation which is causing this warning.

No changes required.


>   Miscellaneous warnings:
>
>   -----------------------------------------------------------------------=
-----
>
>
>
>   -- The document date (April 26, 2017) is 14 days in the past.  Is this
>
>      intentional?
>
>
>
>
>
>   Checking references for intended status: Best Current Practice
>
>   -----------------------------------------------------------------------=
-----
>
>
>
>      (See RFCs 3967 and 4897 for information about using normative refere=
nces
>
>      to lower-maturity documents in RFCs)
>
>
>
>      No issues found here.
>
>
>
>      Summary: 0 errors (**), 0 flaws (~~), 1 warning (=3D=3D), 1 comment =
(--).
>
>
>
>
>
> _______________________________________________
>
> OPS-DIR mailing list
>
> OPS-DIR@ietf.org
>
> https://www.ietf.org/mailman/listinfo/ops-dir
>
>
>

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

<div dir=3D"ltr">Thanks for your review Zitao!<div><br></div><div>Version 1=
2 addresses your comments. Detailed responses below:<br><div class=3D"gmail=
_extra"><br><div class=3D"gmail_quote">On Sun, May 21, 2017 at 8:05 PM, wan=
gzitao <span dir=3D"ltr">&lt;<a href=3D"mailto:wangzitao@huawei.com" target=
=3D"_blank">wangzitao@huawei.com</a>&gt;</span> wrote:<br><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 lang=3D"EN-US">
<div class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-79424819=
56844997469gmail-m_-4518665226251398447WordSection1">
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText">Reviewer: Zitao Wang (Mi=
chael)<u></u><u></u></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText">Review result: Has Nits<=
u></u><u></u></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText">I have reviewed this doc=
ument as part of the Operational directorate=E2=80=99s=C2=A0ongoing effort =
to review all IETF documents being processed by the IESG.=C2=A0 These=C2=A0=
comments were written with the intent of improving the operational=C2=A0asp=
ects of the
 IETF drafts. Comments that are not addressed in last call may be included =
in AD reviews during the IESG review.=C2=A0 Document editors and=C2=A0WG ch=
airs should treat these comments just like any other last call=C2=A0comment=
s.<u></u><u></u></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText">Document reviewed: =C2=
=A0draft-ietf-oauth-native-apps-<wbr>10<u></u><u></u></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText">Summary: <u></u><u></u><=
/p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0.0001pt;line-height:normal">
<span style=3D"font-size:10.5pt;font-family:Consolas">OAuth 2.0 authorizati=
on requests from native apps should only be made<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0.0001pt;line-height:normal">
<span style=3D"font-size:10.5pt;font-family:Consolas">through external user=
-agents, primarily the user=E2=80=99s browser. This<u></u><u></u></span></p=
>
<p class=3D"MsoNormal" style=3D"margin-bottom:0.0001pt;line-height:normal">
<span style=3D"font-size:10.5pt;font-family:Consolas">specification details=
 the security and usability reasons why this is<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0.0001pt;line-height:normal">
<span style=3D"font-size:10.5pt;font-family:Consolas">the case, and how nat=
ive apps and authorization servers can implement<u></u><u></u></span></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText">this best practice.<u></=
u><u></u></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;line-height:115%;fon=
t-family:Consolas">I think the document is written very clear, except some =
small nits:<u></u><u></u></span></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText"><a name=3D"m_-3705660629=
324307280_m_-3603861051619784652_m_-7942481956844997469_m_-4518665226251398=
447_OLE_LINK1"></a><a name=3D"m_-3705660629324307280_m_-3603861051619784652=
_m_-7942481956844997469_m_-4518665226251398447_OLE_LINK2">Page 3:</a>=C2=A0=
=C2=A0=C2=A0=C2=A0 The last sentence of introduction-- =E2=80=9CThis practi=
ce is also known as the AppAuth pattern=E2=80=9D.=C2=A0=C2=A0
<u></u><u></u></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText" style=3D"margin-left:36p=
t;text-indent:36pt">I suggest adding a reference to explain the AppAuth pat=
tern.<u></u><u></u></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText"><u></u></p></div></div><=
/blockquote><div><br></div><div>Done</div><div>=C2=A0</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex"><div lang=3D"EN-US"><div class=3D"m_-3705=
660629324307280gmail-m_-3603861051619784652m_-7942481956844997469gmail-m_-4=
518665226251398447WordSection1">
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText">Page 3:=C2=A0=C2=A0=C2=
=A0=C2=A0 Terminology -- &quot;OAuth&quot;.=C2=A0 <u></u><u></u></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText" style=3D"margin-left:36p=
t;text-indent:36pt">I suggest modifying to: &quot;OAuth&quot;=C2=A0=C2=A0 T=
he Web Authorization (OAuth) protocol.=C2=A0 In this document, OAuth refers=
 to OAuth 2.0 [RFC6749].</p></div></div></blockquote><div>I went with:</div=
><div>&quot;In this document, OAuth refers to the OAuth 2.0 Authorization F=
ramework [RFC6749].&quot;<br></div><div><br></div><div>The phrase &quot;Web=
 Authorization (OAuth) protocol&quot; only seems to appear in our WG Charte=
r, and <a href=3D"https://www.google.com/search?q=3Dweb+authorization+proto=
col" target=3D"_blank">not general usage</a>.</div><div>=C2=A0</div><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"><div lang=3D"EN-US"><div class=
=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-794248195684499746=
9gmail-m_-4518665226251398447WordSection1"><p class=3D"m_-37056606293243072=
80gmail-m_-3603861051619784652m_-7942481956844997469gmail-m_-45186652262513=
98447MsoPlainText"><u></u></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText">Page 4:=C2=A0=C2=A0=C2=
=A0=C2=A0 Terminology -- &quot;web-view&quot;=C2=A0 A web browser UI compon=
ent.=C2=A0=C2=A0
<u></u><u></u></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText" style=3D"margin-left:36p=
t;text-indent:36pt">Does it mean &quot;User Information&quot;?=C2=A0 Sugges=
t expanding this abbreviation.<u></u><u></u></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText"><u></u></p></div></div><=
/blockquote><div><br></div><div>Done.</div><div>=C2=A0</div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-US"><div class=3D"m_-370=
5660629324307280gmail-m_-3603861051619784652m_-7942481956844997469gmail-m_-=
4518665226251398447WordSection1"><p class=3D"m_-3705660629324307280gmail-m_=
-3603861051619784652m_-7942481956844997469gmail-m_-4518665226251398447MsoPl=
ainText"><u></u></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText">Page 5:=C2=A0=C2=A0=C2=
=A0=C2=A0 Figure 1.=C2=A0=C2=A0 Does the browser and authorization endpoint=
 are some kinds of &quot;external user-agent&quot;? Suggest describing it m=
ore clearly.</p></div></div></blockquote><div><br></div><div>Now states:</d=
iv><div>&quot;illustrates the interaction of the native app with a browser<=
/div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 external user-agent to authorize the =
user. &quot;</div><div><br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex"><div lang=3D"EN-US"><div class=3D"m_-3705660629324307280gmail-m_-36=
03861051619784652m_-7942481956844997469gmail-m_-4518665226251398447WordSect=
ion1">
<p class=3D"MsoNormal" style=3D"margin-bottom:0.0001pt;line-height:normal">
<span style=3D"font-size:10.5pt;font-family:Consolas">Page=C2=A0=C2=A0 9:=
=C2=A0=C2=A0 PKCE [RFC7636] details how this limitation can be used to exec=
ute a code interception attack (see Figure 1).=C2=A0=C2=A0=C2=A0
<u></u><u></u></span></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText" style=3D"margin-left:36p=
t;text-indent:36pt">Does the Figure 1 means =E2=80=9CFigure 1 of RFC7636=E2=
=80=9D?=C2=A0</p></div></div></blockquote><div><br></div><div>Good catch. I=
 delete the figure reference, since the entire spec talks about this attack=
, which is likely sufficient.</div><div>=C2=A0</div><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"><div lang=3D"EN-US"><div class=3D"m_-37056606293=
24307280gmail-m_-3603861051619784652m_-7942481956844997469gmail-m_-45186652=
26251398447WordSection1"><p class=3D"m_-3705660629324307280gmail-m_-3603861=
051619784652m_-7942481956844997469gmail-m_-4518665226251398447MsoPlainText"=
 style=3D"margin-left:36pt;text-indent:36pt">
<u></u><u></u></p>
<br>
<p class=3D"MsoNormal" style=3D"margin-bottom:0.0001pt;line-height:normal">
<span style=3D"font-size:10.5pt;font-family:Consolas">Page10:=C2=A0=C2=A0=
=C2=A0=C2=A0 However, as the Implicit Flow cannot be protected by PKCE=C2=
=A0=C2=A0=C2=A0=C2=A0
<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-right:0cm;margin-left:36pt;margin-bo=
ttom:0.0001pt;text-indent:36pt;line-height:normal">
<span style=3D"font-size:10.5pt;font-family:Consolas">Seems here, the refer=
ence be omitted.=C2=A0</span></p></div></div></blockquote><div><br></div><d=
iv>Added.</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-lef=
t:1ex"><div lang=3D"EN-US"><div class=3D"m_-3705660629324307280gmail-m_-360=
3861051619784652m_-7942481956844997469gmail-m_-4518665226251398447WordSecti=
on1">
<pre><span style=3D"font-size:10.5pt;font-family:Consolas">A run of idnits =
revealed no errors, flaws. There were 1 warning and 1 comments though<u></u=
><u></u></span></pre>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText"><u></u>=C2=A0<u></u></p>
<pre><span style=3D"color:black">=C2=A0 =3D=3D There are 1 instance of line=
s with non-RFC2606-compliant FQDNs in the<u></u><u></u></span></pre>
<pre><span style=3D"color:black">=C2=A0=C2=A0=C2=A0=C2=A0 document.<u></u><=
u></u></span></pre>
<pre><span style=3D"color:black"><u></u>=C2=A0</span></pre></div></div></bl=
ockquote><div><br></div><div>I ran it myself with verbose output, and got:<=
/div><div><pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:p=
re-wrap">tmp/draft-ietf-oauth-native-ap<wbr>ps__1_.txt(435): Found possible=
 FQDN &#39;com.example.app&#39; in position 5; this doesn&#39;t match RFC 2=
606&#39;s suggested &quot;.example&quot; or &quot;.example.(com|org|net)&qu=
ot;.</pre></div><div>=C2=A0</div><div>We are actually using a RFC2606 domai=
n name here, but in reverse domain name notation which is causing this warn=
ing.</div><div><br></div><div>No changes required.</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"><div lang=3D"EN-US"><div cl=
ass=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-794248195684499=
7469gmail-m_-4518665226251398447WordSection1"><pre></pre>
<pre><span style=3D"color:black">=C2=A0 Miscellaneous warnings:<u></u><u></=
u></span></pre>
<pre><span style=3D"color:black">=C2=A0 ------------------------------<wbr>=
------------------------------<wbr>----------------<u></u><u></u></span></p=
re>
<pre><span style=3D"color:black"><u></u>=C2=A0<u></u></span></pre>
<pre><span style=3D"color:black">=C2=A0 -- The document date (April 26, 201=
7) is 14 days in the past.=C2=A0 Is this<u></u><u></u></span></pre>
<pre><span style=3D"color:black">=C2=A0=C2=A0=C2=A0=C2=A0 intentional?<u></=
u><u></u></span></pre>
<pre><span style=3D"color:black"><u></u>=C2=A0<u></u></span></pre>
<pre><span style=3D"color:black"><u></u>=C2=A0<u></u></span></pre>
<pre><span style=3D"color:black">=C2=A0 Checking references for intended st=
atus: Best Current Practice<u></u><u></u></span></pre>
<pre><span style=3D"color:black">=C2=A0 ------------------------------<wbr>=
------------------------------<wbr>----------------<u></u><u></u></span></p=
re>
<pre><span style=3D"color:black"><u></u>=C2=A0<u></u></span></pre>
<pre><span style=3D"color:black">=C2=A0=C2=A0=C2=A0=C2=A0 (See RFCs 3967 an=
d 4897 for information about using normative references<u></u><u></u></span=
></pre>
<pre><span style=3D"color:black">=C2=A0=C2=A0=C2=A0=C2=A0 to lower-maturity=
 documents in RFCs)<u></u><u></u></span></pre>
<pre><span style=3D"color:black"><u></u>=C2=A0<u></u></span></pre>
<pre><span style=3D"color:black">=C2=A0=C2=A0=C2=A0=C2=A0 No issues found h=
ere.<u></u><u></u></span></pre>
<pre><span style=3D"color:black"><u></u>=C2=A0<u></u></span></pre>
<pre><span style=3D"color:black">=C2=A0=C2=A0=C2=A0=C2=A0 Summary: 0 errors=
 (**), 0 flaws (~~), 1 warning (=3D=3D), 1 comment (--).</span><span style=
=3D"color:black"><u></u><u></u></span></pre>
<pre><span style=3D"color:black"><u></u>=C2=A0<u></u></span></pre>
<pre><span style=3D"color:black"><u></u>=C2=A0<u></u></span></pre>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText">________________________=
______<wbr>_________________<u></u><u></u></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText">OPS-DIR mailing list<u><=
/u><u></u></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText"><a href=3D"mailto:OPS-DI=
R@ietf.org" target=3D"_blank">OPS-DIR@ietf.org</a><u></u><u></u></p>
<p class=3D"m_-3705660629324307280gmail-m_-3603861051619784652m_-7942481956=
844997469gmail-m_-4518665226251398447MsoPlainText"><a href=3D"https://www.i=
etf.org/mailman/listinfo/ops-dir" target=3D"_blank">https://www.ietf.org/ma=
ilman/l<wbr>istinfo/ops-dir</a><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>

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

--001a113ee7d25754640550219a2a--


From nobody Mon May 22 13:29:30 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 64245128CDB for <ietf@ietfa.amsl.com>; Mon, 22 May 2017 13:29:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.034
X-Spam-Level: 
X-Spam-Status: No, score=-0.034 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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 5Ky01EmYMT4m for <ietf@ietfa.amsl.com>; Mon, 22 May 2017 13:29:17 -0700 (PDT)
Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) (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 E4DB5128D2E for <ietf@ietf.org>; Mon, 22 May 2017 13:29:09 -0700 (PDT)
Received: from resomta-ch2-02v.sys.comcast.net ([69.252.207.98]) by resqmta-ch2-09v.sys.comcast.net with SMTP id CtwLdlJWXQe9cCtwzdHxNV; Mon, 22 May 2017 20:29:09 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-02v.sys.comcast.net with SMTP id CtwxdDfBMgFBHCtwydXxyB; Mon, 22 May 2017 20:29:08 +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 v4MKT6Jn027775; Mon, 22 May 2017 16:29:06 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v4MKT6Qe027772; Mon, 22 May 2017 16:29:06 -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: draft-ietf-grow-bgp-reject.all@ietf.org
Cc: gen-art@ietf.org, grow@ietf.org, ietf@ietf.org
Subject: Re: [GROW] Genart telechat review of draft-ietf-grow-bgp-reject-07
In-Reply-To: <20170522110448.3obnrbam2who3n5x@hanna.meerval.net> (job@ntt.net)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Mon, 22 May 2017 16:29:06 -0400
Message-ID: <87y3topre5.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfAxBBu6rgFrsuUKA/dfrY3rzlEUHyojfmf+F1Vh+nayF4uI4wlQj/VatywxOm9IlzWcjfTuA9a7GhMv4hN/rxCW8DqtsRmvfZiBlIAPr2RjSl70++Cm9 Po46PrWDfJNPutCab6VsjawdR4UmlFRnDEpaRQBxR8ceJs8M6mQXl8mE+yYnpo+XC6YSPS5PhME38j0HSqDuWScvnCG4W5uMdlLNa4pm34ZqfCw0JRIG85XC tfYmbRo99FJYhkPjEPEHeGo2C1m9jo3rydQvvQZrF4c=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/x_KAvpqQTwXrFcZHQ0zF017yT3M>
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, 22 May 2017 20:29:22 -0000

I agree with all the changes that have been discussed, with the
following additional suggestions:

Job Snijders <job@ntt.net> writes:
>>    Appendix A.  Transition Considerations
>> 
>>    It is anticipated that transitioning to a compliant BGP
>>    implementation will require a process thay may take several years.
>> 
>> You probably want to s/a compliant BGP implementation/compliant BGP
>> implementations/, unless you are describing the process for an
>> individual operator, not for all operators collectively.
>
> The process refers to the vendors of BGP implementations, not operators.
> Given that the appendix is targetted mostly to the vendor audience,
> would you have a suggestion within that context?

"Hankins, Greg (Nokia - US)" <greg.hankins@nokia.com> writes:
> How about this change for clarity:
> - old: It is anticipated that transitioning to a compliant BGP implementation
> will require a process thay may take several years.
> - new: Transitioning to a compliant BGP implementation may require a software
> development and release process that can take implementers several years.

I suspect my problems come from not realizing there has been a change of
focus.  (It may be much clearer to routing people.)  So I would suggest
expanding the title of Appendix A to "Transition Considerations for
Vendors of BGP Implementations".

As you point out, in the context of a vendor, the correct wording is "a
compliant BGP implementation".

Even with that change, the change Greg suggests makes sense.  Although
it might be easier to read if the "for an implementor" is brought to the
front of the sentence, where it won't stretch out the flow of the rest
of the sentence.  Something like

    For an implementer, transitioning to a compliant BGP implementation
    may require a software development and release process that can take
    several years.

Perhaps "a software development and release" can be omitted.


"Hankins, Greg (Nokia - US)" <greg.hankins@nokia.com> writes:
> Hi Dale, this paragraphs seems wordy now, so I would suggested splitting
> sentences as follows:
>
> This document updates [RFC4271] so that routes are neither imported nor
> exported unless specifically enabled by configuration.  The solution
> reduces the consequences of these problems, and improves the default level
> of Internet routing security.

In that case, I'd start the second sentence with "This change ..." or
perhaps "This update ..." -- nothing has previously been labeled a
"solution", so the reader has to search a bit to determine the
antecedent.

Dale


From nobody Mon May 22 15:19:48 2017
Return-Path: <fielding@gbiv.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 AB5F11293E4; Mon, 22 May 2017 15:19:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.799
X-Spam-Level: 
X-Spam-Status: No, score=-4.799 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_H2=-2.8, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gbiv.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 8kEkQWFa2iKT; Mon, 22 May 2017 15:19:38 -0700 (PDT)
Received: from homiemail-a124.g.dreamhost.com (sub5.mail.dreamhost.com [208.113.200.129]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CABD81272E1; Mon, 22 May 2017 15:19:38 -0700 (PDT)
Received: from homiemail-a124.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a124.g.dreamhost.com (Postfix) with ESMTP id 3C33560000D00; Mon, 22 May 2017 15:19:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=gbiv.com; bh=Nz05IO1NsBfpXtaFlaWPXuvDnSo=; b=ZgLihgmtrCpKC/VviNR09HBmPn0J ALjXorRrieRDaDJqwskdlPGte5zsdP8gZ6LFnT7qlzoUk4504psaxIWfK9wvxzxb m8UjMShYowoZ9iy+dlEnPDEnDm551TLMAyRf2qnokRcnteqgk2llHYm/Gecmo0oJ OWsUJ0cqCk3UpGw=
Received: from [192.168.1.11] (ip68-228-71-159.oc.oc.cox.net [68.228.71.159]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by homiemail-a124.g.dreamhost.com (Postfix) with ESMTPSA id 1739560001B0A; Mon, 22 May 2017 15:19:38 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: [art] ART Area Review for draft-ietf-calext-caldav-attachments-02
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <07f64bc5-13f6-62a0-3c04-91c780f69672@andrew.cmu.edu>
Date: Mon, 22 May 2017 15:19:37 -0700
Cc: Julian Reschke <julian.reschke@gmx.de>, IETF Discussion <ietf@ietf.org>, art@ietf.org, Cyrus Daboo <cyrus@daboo.name>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4803F47E-B29C-440A-91EA-F0D115208A53@gbiv.com>
References: <c04f39e2-79d2-ab9d-59ab-26e51d7ab5fc@gmx.de> <81613220-989b-ca78-fe56-0ac7b19e7ce6@andrew.cmu.edu> <b2a4924d-c7c9-b40b-484f-9fab48bfe5de@gmx.de> <a603f3de-2d96-6f86-e0c3-3e0a4884a185@andrew.cmu.edu> <7bcfecea-3a89-978c-9e1b-edf9aac5dd44@gmx.de> <07f64bc5-13f6-62a0-3c04-91c780f69672@andrew.cmu.edu>
To: Ken Murchison <murch@andrew.cmu.edu>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PmXfoNYhsBxQ6vRiuMOdNLCd3es>
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, 22 May 2017 22:19:41 -0000

> On May 22, 2017, at 11:59 AM, Ken Murchison <murch@andrew.cmu.edu> =
wrote:
> On 05/17/2017 09:58 AM, Julian Reschke wrote:
>> On 2017-05-17 15:07, Ken Murchison wrote:
>>> ...
>>>> Only for creation of the attachment. Once is has been created, it
>>>> should have its own URI, and the usual HTTP methods should be =
applicable.
>>>=20
>>> Using HTTP methods directly on the attachment URI makes things more
>>> difficult because the calendar resource(s) referencing the =
attachment
>>> also need to be updated.  This would have to be done either as a
>>> side-effect of the PUT/DELETE on the attachment, or as a separate =
PUT
>>> (and separate round-trips) on the resource(s).  The desire was to =
avoid
>>> doing either one of these, which is why a POST on the calendar =
resource
>>> was chosen as the method to add/update/delete an attachment from a
>>> calendar resource.
>>=20
>> But the POST is *not* on the calendar resource, but on the calendar =
resource + query parameters, which, from HTTP's point of view is a =
different resource already.
>>=20
>> Furthermore, what URIs are used is orthogonal to the question of =
which methods to use.
>>=20
>> Why is
>>=20
>>  POST /calendar-entry?action=3Dremove&attachment=3Dxyz
>>=20
>> easier to process than
>>=20
>>  DELETE /calendar-entry?attachment=3Dxyz
>>=20
>> or
>>=20
>>  DELETE /calendar-entry/attachments/xyz
>>=20
>> ?
>=20
> The issue here is that a single calendar resource may contain multiple =
events (recurring event with overrides) and a particular attachment may =
be associated with more than one instance of that event.  For this =
reason, we felt it best to use the calendar resource as the gateway to =
the attachments, thus allowing manipulating multiple instances of an =
attachment in a single round-trip.  Also, by preventing clients from =
manipulating attachments directly, a CalDAV server isn't forced to alter =
all calendar resources associated with a particular attachment.

But that isn't relevant to the choices here.  HTTP is not a filesystem.
A single implementation (e.g., caldav resource) can handle a wide =
variety
of URLs (identified HTTP resources) with all sorts of co-dependencies in
the state represented by those resources.  They are all part of the =
calendar.
The method states the kind of action being made.

Likewise, an identifier for the attachment associated with the calendar =
entry
doesn't have to be the same as the identifiers for interacting with the
attachment directly.  For example, the calendar might provide one =
identifier
for the original attachment, a second for the attachment currently =
applicable
to a given instance of an entry, and a third for updating future =
instances
of that repeating event (i.e., all defined by the server, not the =
protocol).

In any case, one of the cornerstones of caldav practice is that caldav
provides just one interface to an abstract Calendar database normally
accessed via many different protocols/systems.  The Calendar should =
already
be maintaining coherence between entries and attachments, just like it
shouldn't require a new entry be created every time the invitation list
is expanded.

> We also have a fairly large number of deployed implementations which =
we do not want to make non-compliant by substantially modifying the =
protocol.  At this point, specifying the use of HTTP methods other than =
POST would indeed make existing implementations non-compliant.

Specifying method actions within URL query strings is well-known to be
bad practice. However, if you are okay with specifying an IETF protocol
that contains obviously bad practice in its application of HTTP,
a minimum would be to reference section 4.2.1 of RFC7231, where it =
states:

   When a resource is constructed such that parameters within the
   effective request URI have the effect of selecting an action,
   it is the resource owner's responsibility to ensure that the action
   is consistent with the request method semantics. For example, it is
   common for Web-based content editing software to use actions within
   query parameters, such as "page?do=3Ddelete". If the purpose of such =
a
   resource is to perform an unsafe action, then the resource owner MUST
   disable or disallow that action when it is accessed using a safe
   request method. Failure to do so will result in unfortunate side
   effects when automated processes perform a GET on every URI reference
   for the sake of link maintenance, pre-fetching, building a search =
index, etc.

> We would definitely like to make this protocol conform to current HTTP =
practice where possible, and would also document where we have strayed =
from existing practice if required to do so.  Do you think we can come =
to some kind of consensus that meets these goals?
>=20
> --=20
> Kenneth Murchison
> Principal Systems Software Engineer
> Carnegie Mellon University

I honestly don't see how this can be considered an extension of WebDAV
and yet have such a profound misunderstanding of method semantics.
Other applications of HTTP might be expected to work around PUT/DELETE,
but not a WebDAV server.

Likewise, defining a protocol in terms of predefined URL patterns and
specific query components is fundamentally incompatible with REST.

OTOH, it's not the first time this has come up.  HTTP provides plenty
of rope, for good reasons, and these types of choices seem only to
harm those using the rope.  Maybe a future version will just use HTTP.


Cheers,

Roy T. Fielding                     <http://roy.gbiv.com/>
Senior Principal Scientist, Adobe   <https://www.adobe.com/>


From nobody Mon May 22 15:28:32 2017
Return-Path: <greg.hankins@nokia.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 99238128C81; Mon, 22 May 2017 15:28:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.746
X-Spam-Level: 
X-Spam-Status: No, score=0.746 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 HEkaekXHob2F; Mon, 22 May 2017 15:28:14 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C050E1272E1; Mon, 22 May 2017 15:28:13 -0700 (PDT)
Received: from [24.125.34.202] (helo=misfits.twoguys.org) by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <greg.hankins@nokia.com>) id 1dCvoC-0008Jk-3N; Mon, 22 May 2017 18:28:12 -0400
Received: from misfits.twoguys.org (localhost.twoguys.org [127.0.0.1]) by misfits.twoguys.org (8.14.7/8.12.11) with ESMTP id v4MMSBUQ019945; Mon, 22 May 2017 18:28:11 -0400
Received: (from ghankins@localhost) by misfits.twoguys.org (8.14.7/8.14.7/Submit) id v4MMSBtI019944; Mon, 22 May 2017 18:28:11 -0400
X-Authentication-Warning: misfits.twoguys.org: ghankins set sender to greg.hankins@nokia.com using -f
Date: Mon, 22 May 2017 18:28:11 -0400
From: "Hankins, Greg (Nokia - US)" <greg.hankins@nokia.com>
To: "Dale R. Worley" <worley@ariadne.com>
Cc: draft-ietf-grow-bgp-reject.all@ietf.org, gen-art@ietf.org, grow@ietf.org,  ietf@ietf.org
Subject: Re: [GROW] Genart telechat review of draft-ietf-grow-bgp-reject-07
Message-ID: <20170522222811.GA19849@nokia.com>
References: <20170522110448.3obnrbam2who3n5x@hanna.meerval.net> <87y3topre5.fsf@hobgoblin.ariadne.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87y3topre5.fsf@hobgoblin.ariadne.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-ELNK-Trace: 176464c9115cf5b39c7f779228e2f6aeda0071232e20db4db553864b6c9c9b6404df6b5bffd3c947350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.125.34.202
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KGPr2pH9GRPgt58XCAwQXNCIgqE>
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, 22 May 2017 22:28:16 -0000

On Mon, May 22, 2017 at 04:29:06PM -0400, Dale R. Worley wrote:
>I suspect my problems come from not realizing there has been a change of
>focus.  (It may be much clearer to routing people.)  So I would suggest
>expanding the title of Appendix A to "Transition Considerations for
>Vendors of BGP Implementations".

Hi Dale, how about simply "Transition Considerations for BGP Implementers" as
there are many excellent FOSS implementations in addition to implementations
sold by vendors?

>    For an implementer, transitioning to a compliant BGP implementation
>    may require a software development and release process that can take
>    several years.
>
>Perhaps "a software development and release" can be omitted.

Updated: For an implementer, transitioning to a compliant BGP implementation
may require a process that can take several years.

>> This document updates [RFC4271] so that routes are neither imported nor
>> exported unless specifically enabled by configuration.  The solution
>> reduces the consequences of these problems, and improves the default level
>> of Internet routing security.
>
>In that case, I'd start the second sentence with "This change ..." or
>perhaps "This update ..." -- nothing has previously been labeled a
>"solution", so the reader has to search a bit to determine the
>antecedent.

Updated: This change reduces the consequences of these problems, and improves
the default level of Internet routing security.

We'll wait to send a new diff in case there are further comments.

Kind regards,
Greg

--
Greg Hankins <greg.hankins@nokia.com>
Senior Product Manager
IP/Optical Networks, Nokia


From nobody Mon May 22 15:55:18 2017
Return-Path: <eng.khaled.omar@hotmail.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 674B7129409; Mon, 22 May 2017 15:55:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.145
X-Spam-Level: 
X-Spam-Status: No, score=-1.145 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sr9W_mLTQw-1; Mon, 22 May 2017 15:55:08 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-oln040092065054.outbound.protection.outlook.com [40.92.65.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50DF81293EC; Mon, 22 May 2017 15:55:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Fo/Tj07ESbQ/wv8abMIV6piJ4j+FlLcICaG61ZP293Q=; b=srSlMcmBSyTaoSZ6lgdQ8nXBDmKDqG7kBrD1reqaW8u2OogaLovNg4VdYfQTFMxXaZtly3MwxEnIYBwYvWc9tirEnJlupS5Lqu9jgPP4/Wr25tI4xta+w5qEkPjMxRyTSe3av11VoRp60dXVKQ3foHTHAXCPcM2TzWj8zTYvG9Y6KbjsBN17kQ4CAEN5YTITfKQrb3UJsKpWl43K0rbb3qzMaUkQIIhe8c6qcBV4cBHMV1eCYqhizDOMJR6R0LvSVAr/VgIY36uW6r6+cCluXTJSWZZpWH2vg7RSFnlEFCq/aLBhZLvUPScly81esWOQRMVyb2VR7kKXdJ+F+k7oFA==
Received: from HE1EUR01FT052.eop-EUR01.prod.protection.outlook.com (10.152.0.56) by HE1EUR01HT049.eop-EUR01.prod.protection.outlook.com (10.152.0.210) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1075.5; Mon, 22 May 2017 22:55:03 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.0.60) by HE1EUR01FT052.mail.protection.outlook.com (10.152.1.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1075.5 via Frontend Transport; Mon, 22 May 2017 22:55:02 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::a819:bed0:ee53:c0c3]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::a819:bed0:ee53:c0c3%18]) with mapi id 15.01.1101.019; Mon, 22 May 2017 22:55:02 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: "ietf-draft-submission@ietf.org" <ietf-draft-submission@ietf.org>
CC: "int-area@ietf.org" <int-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>,  "intarea-ads@ietf.org" <intarea-ads@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>, IETF Chair <chair@ietf.org>
Subject: IPv10, KRP, and RRP IDs Removal.
Thread-Topic: IPv10, KRP, and RRP IDs Removal.
Thread-Index: AdLTTNVDoZlTmip5SbKkUmpfy2efXw==
Date: Mon, 22 May 2017 22:55:02 +0000
Message-ID: <AM4PR0401MB2241731801FD7F70B2DD246FBDF80@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:3F7AD9629AABC4BAB96DF11CFE7C94F5C89229B18171566CA0BB2BC033C2B488; UpperCasedChecksum:1806E559115941986D4C3F86EA049597C21EBEA61DA4501CD31D8F64AA18A130; SizeAsReceived:8306; Count:43
x-tmn: [rnuJQE62ZtMebF+vxoUJbY73yaLkxIIB]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1EUR01HT049; 5:w2zJDy+85Ra3LGw7qBRSKptMIGNHOk34wcfphYCzaVBQua0Jf21ZA9gShnRtA5akeicGr2olxZ397ZDpfc1PvsN2vPldQTFYz2wZztMHtUKppKv1Qer2RQay71K7EGnnqBT1VPuNrja4cZGlVnJoIw==; 24:wfts/Dg9A/0m133+ooGOeO+RHWQvHNSdpEHCVqZKfUQ1dM4d2W+e94Lhg0hw1l1KMlBDShNbUTuX3AmUi4G2sOYG4iraS6m1hNDkyYPwNqA=; 7:Yh1HGOQCabKCG5whyp3jWjup8ny93sp/iow2Yp0nBlwFxV7bdTJipgaNuZJ5CEO7xwhU/r0r+3msyxIbkXid4OaHrZYg9d6hMCPol3OukvTnXNJX91+DR3c2t9pPI1rssue4qOAg9RNPn08FAmhpqRJzv1sL/cxI71KRLZXPeUic34P1RYqHJSgwM78IrlVrYEwSWWZA2Q+jzVnJqSmHmEBU4eySpF/hwzh5bJG7iSvozIvsXUQoiA3OOKRFXOcRGulVxneziAprSniVB8isuoZxORxEYzTih65mzvERdzrJY+SlhysShAycNVQb+YWZ
x-incomingheadercount: 43
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:HE1EUR01HT049; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 67667bbe-14a2-4822-fc3f-08d4a16594f0
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:HE1EUR01HT049; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:HE1EUR01HT049; BCL:0; PCL:0; RULEID:; SRVR:HE1EUR01HT049; 
x-forefront-prvs: 03152A99FF
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB2241731801FD7F70B2DD246FBDF80AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 May 2017 22:55:02.7681 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1EUR01HT049
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fuuVRHGJ9W19fKr9lFhAft34ob0>
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, 22 May 2017 22:55:10 -0000

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

Hi Jasmine,

As I'm the only author of the following IDs:


1)      Internet Protocol version 10 (IPv10): https://datatracker.ietf.org/=
doc/draft-omar-ipv10/


2)      KHALED Routing Protocol (KRP): https://datatracker.ietf.org/doc/dra=
ft-omar-krp/


3)      Regional Routing Protocol (RRP): https://datatracker.ietf.org/doc/d=
raft-omar-rrp/


Please remove them all from the ietf database or repository.

If the ideas explained on these drafts will be used, discussed or published=
 by the ietf, legal actions will be taken.

Regards,

Khaled Omar

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:973295041;
	mso-list-type:hybrid;
	mso-list-template-ids:2081578066 67698705 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi Jasmine,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As I&#8217;m the only author of the following IDs:<o=
:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">1)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3D"LTR"></span>Internet Protocol version =
10 (IPv10):
<a href=3D"https://datatracker.ietf.org/doc/draft-omar-ipv10/">https://data=
tracker.ietf.org/doc/draft-omar-ipv10/</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">2)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3D"LTR"></span>KHALED Routing Protocol (K=
RP): <a href=3D"https://datatracker.ietf.org/doc/draft-omar-krp/">
https://datatracker.ietf.org/doc/draft-omar-krp/</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">3)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3D"LTR"></span>Regional Routing Protocol =
(RRP): <a href=3D"https://datatracker.ietf.org/doc/draft-omar-rrp/">
https://datatracker.ietf.org/doc/draft-omar-rrp/</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please remove them all from the ietf database or rep=
ository.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">If the ideas explained on these drafts will be used,=
 discussed or published by the ietf, legal actions will be taken.<o:p></o:p=
></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Khaled Omar &nbsp;&nbsp;<o:p></o:p></p>
</div>
</body>
</html>

--_000_AM4PR0401MB2241731801FD7F70B2DD246FBDF80AM4PR0401MB2241_--


From nobody Mon May 22 16:09:27 2017
Return-Path: <eng.khaled.omar@hotmail.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 0051A129439 for <ietf@ietfa.amsl.com>; Mon, 22 May 2017 16:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level: 
X-Spam-Status: No, score=-1.146 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ahWNfpw8hMp for <ietf@ietfa.amsl.com>; Mon, 22 May 2017 16:09:24 -0700 (PDT)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-oln040092072087.outbound.protection.outlook.com [40.92.72.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EE3412940F for <ietf@ietf.org>; Mon, 22 May 2017 16:09:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=XrziXUNT+570LflzYwNTLER3nhKeu4PHztesUAAlatU=; b=YbwiDDZqhNvGf5CkBD+EzW65HTDQNKzX9LGkEG01ry1r7HcdJVfGyQM5Kh7O+4fZQpAmlmlinE2ANdj/+n//KKHIj8xMAC+3I59VtgoNwlLxyBhGxjrFvwxODtHiWAqHUrMpWWa3cDbyz+EaprGp5D4UuyYPHUuHfWjetOJBj8mxJZ+lVVA7NCRn720HNKRi3q/8OrPRh/0z0hhuWsSaUnYN1TfmjVkwtn+S1p7drl/tPvQ18vB9W1up8ytUs3lh8+j3CglJCYNXulpZydqIySpm4+NTBJQsYj1ODbjyyeGHj1foAKBOFKEgthvjKZrI5JRv5+n4Qv6MzrWyD4hrAg==
Received: from AM5EUR03FT042.eop-EUR03.prod.protection.outlook.com (10.152.16.51) by AM5EUR03HT035.eop-EUR03.prod.protection.outlook.com (10.152.17.100) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1075.5; Mon, 22 May 2017 23:09:11 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.16.54) by AM5EUR03FT042.mail.protection.outlook.com (10.152.17.168) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1075.5 via Frontend Transport; Mon, 22 May 2017 23:09:11 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::a819:bed0:ee53:c0c3]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::a819:bed0:ee53:c0c3%18]) with mapi id 15.01.1101.019; Mon, 22 May 2017 23:09:11 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: Ole Jacobsen <olejacobsen@me.com>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: IPv10, KRP, and RRP IDs Removal.
Thread-Topic: IPv10, KRP, and RRP IDs Removal.
Thread-Index: AdLTTNVDoZlTmip5SbKkUmpfy2efXwAAoxMAAAAZZAA=
Date: Mon, 22 May 2017 23:09:11 +0000
Message-ID: <AM4PR0401MB2241ADF8E991BF82170BFBB7BDF80@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <AM4PR0401MB2241731801FD7F70B2DD246FBDF80@AM4PR0401MB2241.eurprd04.prod.outlook.com> <alpine.OSX.2.01.1705221601010.81604@rabdullah.local>
In-Reply-To: <alpine.OSX.2.01.1705221601010.81604@rabdullah.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: me.com; dkim=none (message not signed) header.d=none;me.com; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:7C6BE5EA8D1636B6A7A13B65B7DE41D0180528BBF8E978FB2F043CB5851B40EB; UpperCasedChecksum:967CFCF4D36E0757211EB80BA848F6F0866F75E304942E9EE7B1B4902CCF9308; SizeAsReceived:8317; Count:45
x-tmn: [5i0ceJH/ICNdXnMQQGeqxN5vS0/DykJm]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM5EUR03HT035; 5:jjxnhOxHGPLSzaa1EIs7V3f2CNoZVB8fqoxXerBRzJJrJs5RJxgHW3q0P1uCWBNInhgasq/pi7iNXo+1//WrLixpR8+FtgJGyF45ys+mYq4A+1dt5ItUAUA+W2jscSuQ/yV8juB6DHygMUrjCG9vVA==; 24:IzwyXNbTRLqa6YjEGBF4F6n0UESCt+CjZF/HthshdxRT1/2GJ598fhBKr6tGjAxIk9qHNdPJQwUqBJb5xNDkmQIl1Ga5ExY1btLz6L0hRj0=; 7:7j6oRP7OEkLHd43olWwuj8KtIXCnxwzkXY0WYdnAdLiAtuQYk57B3LC2sFHjlf5N0t5D+IyoCI2rTGMarBagGQNvqGG/DXEPEwqlxYhLOx9laQggGLOAJqYWM5RhRvZ4vqtCwKX+zAgwnR6TIvK3Vax8oMZMEwXUsT86koCovH5wtnybpLZTY1s+BPURXpZbPoqEf4h2o1fKut77wtYUF+sQKDoEJ32Th5BeirWnfQVlQjlbXxkTrgZ5JRcqaQC2ctWX5e22L390b2EymnMBK7KuAHpkYri/LZde2Vy51HDmshzjJOeqrWdKYj9Sxyhh
x-incomingheadercount: 45
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:AM5EUR03HT035; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 55875d48-11c4-4574-bd69-08d4a1678edf
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:AM5EUR03HT035; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:AM5EUR03HT035; BCL:0; PCL:0; RULEID:; SRVR:AM5EUR03HT035; 
x-forefront-prvs: 03152A99FF
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 May 2017 23:09:11.4781 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR03HT035
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bpWxkhKpeSF-spVGvr3ZU7mWjo4>
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, 22 May 2017 23:09:26 -0000

I'm the only author of the listed IDs and they are submitted individually, =
I made this removal request and these IDs must not be stored on the ietf da=
tabase anymore and the ietf representation must not exist after the request=
 date and time which is 23rd of May, 2017 at 1:00 PM GMT+02:00.

-----Original Message-----
From: Ole Jacobsen [mailto:olejacobsen@me.com]=20
Sent: Tuesday, May 23, 2017 1:02 AM
To: Khaled Omar
Subject: Re: IPv10, KRP, and RRP IDs Removal.


You really have no idea how the IETF works, do you?


On Mon, 22 May 2017, Khaled Omar wrote:

> Hi Jasmine,
>=20
> As I'm the only author of the following IDs:
>=20
>=20
> 1) Internet Protocol version 10 (IPv10):=20
> https://datatracker.ietf.org/doc/draft-omar-ipv10/
>=20
>=20
> 2) KHALED Routing Protocol (KRP):=20
> https://datatracker.ietf.org/doc/draft-omar-krp/
>=20
>=20
> 3) Regional Routing Protocol (RRP):=20
> https://datatracker.ietf.org/doc/draft-omar-rrp/
>=20
>=20
> Please remove them all from the ietf database or repository.
>=20
> If the ideas explained on these drafts will be used, discussed or=20
> published by the ietf, legal actions will be taken.
>=20
> Regards,
>=20
> Khaled Omar
>=20


From nobody Mon May 22 17:27:25 2017
Return-Path: <amorris@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 132EC129400 for <ietf@ietfa.amsl.com>; Mon, 22 May 2017 17:27:24 -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, 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 PQYHSbxZK-Ve for <ietf@ietfa.amsl.com>; Mon, 22 May 2017 17:27:22 -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 C66EF12947E for <ietf@ietf.org>; Mon, 22 May 2017 17:27:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 7AD881CA391; Mon, 22 May 2017 17:27:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8gzmZhUZOGxm; Mon, 22 May 2017 17:27:11 -0700 (PDT)
Received: from [10.0.11.159] (unknown [165.117.223.124]) by c8a.amsl.com (Postfix) with ESMTPA id 161AD1CA388; Mon, 22 May 2017 17:27:11 -0700 (PDT)
Subject: Re: IPv10, KRP, and RRP IDs Removal.
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: text/plain; charset=us-ascii
From: Alexa Morris <amorris@amsl.com>
In-Reply-To: <AM4PR0401MB2241ADF8E991BF82170BFBB7BDF80@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Date: Mon, 22 May 2017 20:27:18 -0400
Cc: "Ole J. Jacobsen" <olejacobsen@me.com>, "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sendlaterdate: Mon, 22 May 2017 20:27:18 -0400
Message-Id: <7A539F28-73E3-4CD7-9EA0-7B05AF951CF1@amsl.com>
References: <AM4PR0401MB2241731801FD7F70B2DD246FBDF80@AM4PR0401MB2241.eurprd04.prod.outlook.com> <alpine.OSX.2.01.1705221601010.81604@rabdullah.local> <AM4PR0401MB2241ADF8E991BF82170BFBB7BDF80@AM4PR0401MB2241.eurprd04.prod.outlook.com>
To: Khaled Omar <eng.khaled.omar@hotmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6MDK3CZBtin_veJqNKXcUi5yugg>
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, 23 May 2017 00:27:24 -0000

Khaled,

The IESG has published a statement on this topic. Please see "IESG =
Statement on Removal of an Internet-Draft from the IETF Web Site" at =
https://www.ietf.org/iesg/statement/removal-of-an-internet-draft.html, =
which explains that IESG consensus is required in order to remove an =
Internet Draft from the I-D Repository.

I have forwarded your email to the IESG for their review. Please be =
patient as it will take at least several days for them to review and =
respond to this request.=20

Regards,
Alexa

On May 22, 2017, at 7:09 PM, Khaled Omar <eng.khaled.omar@hotmail.com> =
wrote:

> I'm the only author of the listed IDs and they are submitted =
individually, I made this removal request and these IDs must not be =
stored on the ietf database anymore and the ietf representation must not =
exist after the request date and time which is 23rd of May, 2017 at 1:00 =
PM GMT+02:00.
>=20
> -----Original Message-----
> From: Ole Jacobsen [mailto:olejacobsen@me.com]=20
> Sent: Tuesday, May 23, 2017 1:02 AM
> To: Khaled Omar
> Subject: Re: IPv10, KRP, and RRP IDs Removal.
>=20
>=20
> You really have no idea how the IETF works, do you?
>=20
>=20
> On Mon, 22 May 2017, Khaled Omar wrote:
>=20
>> Hi Jasmine,
>>=20
>> As I'm the only author of the following IDs:
>>=20
>>=20
>> 1) Internet Protocol version 10 (IPv10):=20
>> https://datatracker.ietf.org/doc/draft-omar-ipv10/
>>=20
>>=20
>> 2) KHALED Routing Protocol (KRP):=20
>> https://datatracker.ietf.org/doc/draft-omar-krp/
>>=20
>>=20
>> 3) Regional Routing Protocol (RRP):=20
>> https://datatracker.ietf.org/doc/draft-omar-rrp/
>>=20
>>=20
>> Please remove them all from the ietf database or repository.
>>=20
>> If the ideas explained on these drafts will be used, discussed or=20
>> published by the ietf, legal actions will be taken.
>>=20
>> Regards,
>>=20
>> Khaled Omar
>>=20
>=20

----------
Alexa Morris / Executive Director / IETF
+1.510.492.4001
Email: amorris@amsl.com




From nobody Mon May 22 17:54:11 2017
Return-Path: <eng.khaled.omar@hotmail.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 9F8B6129400 for <ietf@ietfa.amsl.com>; Mon, 22 May 2017 17:54:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.127
X-Spam-Level: 
X-Spam-Status: No, score=-1.127 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YKIM993jDhn1 for <ietf@ietfa.amsl.com>; Mon, 22 May 2017 17:54:08 -0700 (PDT)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-oln040092068071.outbound.protection.outlook.com [40.92.68.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A42D3127843 for <ietf@ietf.org>; Mon, 22 May 2017 17:54:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=C3lM0O+TASRxn1FZ7wzTRsu/V5J8rv7h6fD5lR0zFw4=; b=kuknHuQNElNVDy/5/p1tZB0w+mps6fPWGnzcy8NYXDUjd/zS2ao4keH8jbB7zeKz5BiSuNpgA/DKA38b9gsspDd8pdnuEIz9f6xcyEsykqhrDWtUYsulK44h0WZ8twi06Pq6ESZGofzbe+14O+R/odjj6BhreID8sPLSQbOMmP3EYgmHQFfUwTKGG4592VFoAgddOvUQBiFJo9nQZTGOOioCcpKaqRLlYei0pzBj++R54ai1b9VZCy4HDofGNmNtiEyn8PRAjhnT3c3teKG4eQxYS3DHe2kyEGRz8FdV7S+wbSAL+x3bWUh1y1nGeJmAS3+0xIbJnGOEEK5UpwfpMQ==
Received: from VE1EUR02FT042.eop-EUR02.prod.protection.outlook.com (10.152.12.53) by VE1EUR02HT153.eop-EUR02.prod.protection.outlook.com (10.152.13.169) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1075.5; Tue, 23 May 2017 00:54:05 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.12.54) by VE1EUR02FT042.mail.protection.outlook.com (10.152.13.70) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1075.5 via Frontend Transport; Tue, 23 May 2017 00:54:05 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::a819:bed0:ee53:c0c3]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::a819:bed0:ee53:c0c3%18]) with mapi id 15.01.1101.019; Tue, 23 May 2017 00:54:05 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: Alexa Morris <amorris@amsl.com>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: IPv10, KRP, and RRP IDs Removal.
Thread-Topic: IPv10, KRP, and RRP IDs Removal.
Thread-Index: AdLTTNVDoZlTmip5SbKkUmpfy2efXwAAoxMAAAAZZAAAAuOjAAAAfxvA
Date: Tue, 23 May 2017 00:54:04 +0000
Message-ID: <AM4PR0401MB22412E60AFC1FF8709B194DDBDF90@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <AM4PR0401MB2241731801FD7F70B2DD246FBDF80@AM4PR0401MB2241.eurprd04.prod.outlook.com> <alpine.OSX.2.01.1705221601010.81604@rabdullah.local> <AM4PR0401MB2241ADF8E991BF82170BFBB7BDF80@AM4PR0401MB2241.eurprd04.prod.outlook.com> <7A539F28-73E3-4CD7-9EA0-7B05AF951CF1@amsl.com>
In-Reply-To: <7A539F28-73E3-4CD7-9EA0-7B05AF951CF1@amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: amsl.com; dkim=none (message not signed) header.d=none;amsl.com; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:7256994D2E34C9DE011FB3ACF1EDB94B354D76580E12917448B508D1C31D6417; UpperCasedChecksum:14D5DC52B2EE9E9C2692C5A8D0BD696A8394D698684B3CF7B39614C45EC411F1; SizeAsReceived:8459; Count:45
x-tmn: [BeEwgdhCiULzDTvI9E6AQO7fS+4sO3Nq]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VE1EUR02HT153; 5:7piCi8CTEI4krpEg9N1S/VkQvjyR3wvtck0u9tv29xDLIwnvPE1oCw7jgR1Zk4M+TAMcka5DqT3JlNNMNPfVTqBQjKwtLZln9T3d+rm40Ttnh9Uz8lep/BcX2VCmmsXsBTa1rRRmpuIXC0WRYoewpw==; 24:gB8A63T3vD9QFyAHPnYMCQwWz8ucpX8rc780cF89KZI69ngEUjGsVPnupcB0DJxWukOaDttMfrMmEHbbKB1sg3AZo49jbOLtEJatcvz7SZc=; 7:ofOGHRqLfatca1IQl+OoLiJvgX8LDUxZ2qh9/NSlqg5o2nsT5bLMVGtVa0AVkLYArjQuf6Q4iPhLJNAKLvPWzvJgZeLHuGQspRlVMOqElycl1irclvECnYKSrbpKk/kR0vfNXot7eBAlTqmKEbITzbNHe6Dfd6uTCv8f3PqPOw8VvLlesRvCdpbMFq/9wthXNSmsZkWV1Gw1N1zF6/Q63DW+9vdiD6+Nna6y//UfToS1bgWi3clbRAz5qMqjtmsFYj0MFl63kq8Bn9jVRnLAQqohzTgASbyD+fw+lBl8iC0JQz6cw9ECvqlBPmCHZEgl
x-incomingheadercount: 45
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:VE1EUR02HT153; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: e93e4ce2-cbc8-499b-731f-08d4a176361a
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:VE1EUR02HT153; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:VE1EUR02HT153; BCL:0; PCL:0; RULEID:; SRVR:VE1EUR02HT153; 
x-forefront-prvs: 0316567485
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 May 2017 00:54:04.9836 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1EUR02HT153
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wDKanpQceFfaREtLlr-vVJnqU7k>
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, 23 May 2017 00:54:11 -0000

As mentioned in the provided link:

"Internet-Drafts have no formal status, and are subject to change or remova=
l at any time."

> which explains that IESG consensus is required in order to remove an Inte=
rnet Draft from the I-D Repository.

>From today's date till reaching this consensus for removal, these IDs shoul=
dn't be discussed or published by the ietf on any meeting or any official e=
vent as the contents are not representing the ietf anymore after this date.

I'm waiting for the IESG response ... I hope they can make a decision soon.

"When an I-D is removed from the Public I-D Archive, a copy will be kept in=
 a location accessible by the IETF Secretariat."

This of course doesn't gives the ietf the right of making any usage of thes=
e I-Ds after its removal.



-----Original Message-----
From: Alexa Morris [mailto:amorris@amsl.com]=20
Sent: Tuesday, May 23, 2017 2:27 AM
To: Khaled Omar
Cc: Ole J. Jacobsen; ietf@ietf.org
Subject: Re: IPv10, KRP, and RRP IDs Removal.

Khaled,

The IESG has published a statement on this topic. Please see "IESG Statemen=
t on Removal of an Internet-Draft from the IETF Web Site" at https://www.ie=
tf.org/iesg/statement/removal-of-an-internet-draft.html, which explains tha=
t IESG consensus is required in order to remove an Internet Draft from the =
I-D Repository.

I have forwarded your email to the IESG for their review. Please be patient=
 as it will take at least several days for them to review and respond to th=
is request.=20

Regards,
Alexa

On May 22, 2017, at 7:09 PM, Khaled Omar <eng.khaled.omar@hotmail.com> wrot=
e:

> I'm the only author of the listed IDs and they are submitted individually=
, I made this removal request and these IDs must not be stored on the ietf =
database anymore and the ietf representation must not exist after the reque=
st date and time which is 23rd of May, 2017 at 1:00 PM GMT+02:00.
>=20
> -----Original Message-----
> From: Ole Jacobsen [mailto:olejacobsen@me.com]
> Sent: Tuesday, May 23, 2017 1:02 AM
> To: Khaled Omar
> Subject: Re: IPv10, KRP, and RRP IDs Removal.
>=20
>=20
> You really have no idea how the IETF works, do you?
>=20
>=20
> On Mon, 22 May 2017, Khaled Omar wrote:
>=20
>> Hi Jasmine,
>>=20
>> As I'm the only author of the following IDs:
>>=20
>>=20
>> 1) Internet Protocol version 10 (IPv10):=20
>> https://datatracker.ietf.org/doc/draft-omar-ipv10/
>>=20
>>=20
>> 2) KHALED Routing Protocol (KRP):=20
>> https://datatracker.ietf.org/doc/draft-omar-krp/
>>=20
>>=20
>> 3) Regional Routing Protocol (RRP):=20
>> https://datatracker.ietf.org/doc/draft-omar-rrp/
>>=20
>>=20
>> Please remove them all from the ietf database or repository.
>>=20
>> If the ideas explained on these drafts will be used, discussed or=20
>> published by the ietf, legal actions will be taken.
>>=20
>> Regards,
>>=20
>> Khaled Omar
>>=20
>=20

----------
Alexa Morris / Executive Director / IETF
+1.510.492.4001
Email: amorris@amsl.com




From nobody Mon May 22 18:05:15 2017
Return-Path: <mstjohns@comcast.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 E0A5F1294A2 for <ietf@ietfa.amsl.com>; Mon, 22 May 2017 18:05:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-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=comcast.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 cdcUbpDXeBD2 for <ietf@ietfa.amsl.com>; Mon, 22 May 2017 18:05:08 -0700 (PDT)
Received: from resqmta-po-02v.sys.comcast.net (resqmta-po-02v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:161]) (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 5ECD8127843 for <ietf@ietf.org>; Mon, 22 May 2017 18:05:08 -0700 (PDT)
Received: from resomta-po-07v.sys.comcast.net ([96.114.154.231]) by resqmta-po-02v.sys.comcast.net with SMTP id CyFxdpsmvRJJCCyG3dbb8k; Tue, 23 May 2017 01:05:07 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1495501507; bh=qzaymzGiAIHbGOFhk84Ka/+EKMMPxZ/hstXFciEqnyE=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=l2LIDKNP4v5j+1yZkdhs+og6ATfP3/D41NVHYiYi2FhFAKSeC6tPM4aHhjlbxYwkK zcs4oWQQFowPeXmAWp3zd2v7dJJhEX/zaRK+y99u2AycygMTbvwGNoM8k59TjQDHJM rn32a6q9BIHNSPaL0E0XdU9zkgUbJ8bfCyrYNkJ7aWUAhZbWUfISxDwlm1pO+9UyHb atug+4LiQID1bBKt4wOJIj119rPc3+Z5xRGtEpdadIhzKjGMB37KQf1w/7LKTrcfYQ LNrKGKqeI2Svv017glah85dagQxChWRKYmuRce/hdcujorZdhpuLrHvEXEaxbJN8jB I5J4FkWISCQlw==
Received: from [IPv6:2601:152:4400:a2e0::106f] ([IPv6:2601:152:4400:a2e0::106f]) by resomta-po-07v.sys.comcast.net with SMTP id CyG2dOBpvsPppCyG2d4PLn; Tue, 23 May 2017 01:05:06 +0000
Subject: Re: IPv10, KRP, and RRP IDs Removal.
To: ietf@ietf.org
References: <AM4PR0401MB2241731801FD7F70B2DD246FBDF80@AM4PR0401MB2241.eurprd04.prod.outlook.com> <alpine.OSX.2.01.1705221601010.81604@rabdullah.local> <AM4PR0401MB2241ADF8E991BF82170BFBB7BDF80@AM4PR0401MB2241.eurprd04.prod.outlook.com>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <a2900e2e-ba78-9653-3d5f-45f4cf86f5ed@comcast.net>
Date: Mon, 22 May 2017 21:05:05 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <AM4PR0401MB2241ADF8E991BF82170BFBB7BDF80@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-CMAE-Envelope: MS4wfG636d8DgW3lCzxOjQVH8TAytBqd4dD4vdCCzCgRmaCfYxj+wPOJX35pT4qWZ7l3hInJ6Gp9BO0ivgWeATzM1o/pY0dy2/7B69T4hQFoeaClb+wdWkQ2 F7GNU9Tg80Ny3r7m/9eqgOu/k2a1FRgPOmAJnif4B8x8j/SQOzCqBr2n
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/t8uU-55GDDDjxG-MJisZhCiT_F0>
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, 23 May 2017 01:05:10 -0000

On 5/22/2017 7:09 PM, Khaled Omar wrote:
> I'm the only author of the listed IDs and they are submitted individually, I made this removal request and these IDs must not be stored on the ietf database anymore and the ietf representation must not exist after the request date and time which is 23rd of May, 2017 at 1:00 PM GMT+02:00.

Khaled - upon submitting these IDs you included the standard IETF 
Internet Draft Boiler plate for copyright and licensing.  By doing so, 
you granted the IETF process an unlimited, irrevocable paid up license 
to publish, translate and make derivative works  (and others)  of those 
submissions (see http://trustee.ietf.org/license-info, Trust Legal 
Provisions 5.0 at 2(b) and 3(a).

I am not a lawyer, but removal of the IDs from the ID repository is 
unlikely approaching zero to void the grant of rights you made.  Any 
legal action you take to force the removal is most likely to fail. Your 
specific language of  "If the ideas explained on these drafts will be 
used, discussed or published by the ietf, legal actions will be taken." 
is in conflict with your grant of rights.


  Hence Ole's comment.

Mike

>
> -----Original Message-----
> From: Ole Jacobsen [mailto:olejacobsen@me.com]
> Sent: Tuesday, May 23, 2017 1:02 AM
> To: Khaled Omar
> Subject: Re: IPv10, KRP, and RRP IDs Removal.
>
>
> You really have no idea how the IETF works, do you?
>
>
> On Mon, 22 May 2017, Khaled Omar wrote:
>
>> Hi Jasmine,
>>
>> As I'm the only author of the following IDs:
>>
>>
>> 1) Internet Protocol version 10 (IPv10):
>> https://datatracker.ietf.org/doc/draft-omar-ipv10/
>>
>>
>> 2) KHALED Routing Protocol (KRP):
>> https://datatracker.ietf.org/doc/draft-omar-krp/
>>
>>
>> 3) Regional Routing Protocol (RRP):
>> https://datatracker.ietf.org/doc/draft-omar-rrp/
>>
>>
>> Please remove them all from the ietf database or repository.
>>
>> If the ideas explained on these drafts will be used, discussed or
>> published by the ietf, legal actions will be taken.
>>
>> Regards,
>>
>> Khaled Omar
>>


From nobody Mon May 22 19:51:00 2017
Return-Path: <wangzitao@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 247F2129503; Mon, 22 May 2017 19:50:39 -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, HTML_MESSAGE=0.001, 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 2jGrQvNr14cn; Mon, 22 May 2017 19:50:26 -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 9F8D91294D8; Mon, 22 May 2017 19:50:24 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DNO75742; Tue, 23 May 2017 02:50:22 +0000 (GMT)
Received: from DGGEMM402-HUB.china.huawei.com (10.3.20.210) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 23 May 2017 03:50:21 +0100
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.49]) by DGGEMM402-HUB.china.huawei.com ([10.3.20.210]) with mapi id 14.03.0301.000; Tue, 23 May 2017 10:50:17 +0800
From: wangzitao <wangzitao@huawei.com>
To: William Denniss <wdenniss@google.com>
CC: "ops-dir@ietf.org" <ops-dir@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>,  "draft-ietf-oauth-native-apps.all@ietf.org" <draft-ietf-oauth-native-apps.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [OPS-DIR] Opsdir telechat review of draft-ietf-oauth-native-apps-10
Thread-Topic: [OPS-DIR] Opsdir telechat review of draft-ietf-oauth-native-apps-10
Thread-Index: AdLSqDVW3BTeNlgFQ6WqlwAw3ux67gAQ4yYAACDVwOA=
Date: Tue, 23 May 2017 02:50:17 +0000
Message-ID: <E6BC9BBCBCACC246846FC685F9FF41EA2AE09727@DGGEMM506-MBX.china.huawei.com>
References: <E6BC9BBCBCACC246846FC685F9FF41EA2AE094F0@DGGEMM506-MBX.china.huawei.com> <CAAP42hBSj3_B48SN3VmQR2Z8qa2Nzpo7wL8FPr18TvmmeLWoyw@mail.gmail.com>
In-Reply-To: <CAAP42hBSj3_B48SN3VmQR2Z8qa2Nzpo7wL8FPr18TvmmeLWoyw@mail.gmail.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.136.79.161]
Content-Type: multipart/alternative; boundary="_000_E6BC9BBCBCACC246846FC685F9FF41EA2AE09727DGGEMM506MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.5923A36F.0037, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.3.49, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 19faa7ae4a8c3e6c71edad8340774957
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/g413KJ6y2ZTAwII3WGaUNQUPz2Y>
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, 23 May 2017 02:50:39 -0000

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

Q29vbCEgVGhpcyBjaGFuZ2VzL2V4cGxhaW5zIG1ha2Ugc2Vuc2UgdG8gbWUuDQoNCkJlc3QgUmVn
YXJkcyENCi1NaWNoYWVsDQoNCuWPkeS7tuS6ujogV2lsbGlhbSBEZW5uaXNzIFttYWlsdG86d2Rl
bm5pc3NAZ29vZ2xlLmNvbV0NCuWPkemAgeaXtumXtDogMjAxN+W5tDXmnIgyM+aXpSAzOjA5DQrm
lLbku7bkuro6IHdhbmd6aXRhbw0K5oqE6YCBOiBvcHMtZGlyQGlldGYub3JnOyBvYXV0aEBpZXRm
Lm9yZzsgZHJhZnQtaWV0Zi1vYXV0aC1uYXRpdmUtYXBwcy5hbGxAaWV0Zi5vcmc7IGlldGZAaWV0
Zi5vcmcNCuS4u+mimDogUmU6IFtPUFMtRElSXSBPcHNkaXIgdGVsZWNoYXQgcmV2aWV3IG9mIGRy
YWZ0LWlldGYtb2F1dGgtbmF0aXZlLWFwcHMtMTANCg0KVGhhbmtzIGZvciB5b3VyIHJldmlldyBa
aXRhbyENCg0KVmVyc2lvbiAxMiBhZGRyZXNzZXMgeW91ciBjb21tZW50cy4gRGV0YWlsZWQgcmVz
cG9uc2VzIGJlbG93Og0KDQpPbiBTdW4sIE1heSAyMSwgMjAxNyBhdCA4OjA1IFBNLCB3YW5neml0
YW8gPHdhbmd6aXRhb0BodWF3ZWkuY29tPG1haWx0bzp3YW5neml0YW9AaHVhd2VpLmNvbT4+IHdy
b3RlOg0KDQpSZXZpZXdlcjogWml0YW8gV2FuZyAoTWljaGFlbCkNCg0KUmV2aWV3IHJlc3VsdDog
SGFzIE5pdHMNCg0KDQoNCkkgaGF2ZSByZXZpZXdlZCB0aGlzIGRvY3VtZW50IGFzIHBhcnQgb2Yg
dGhlIE9wZXJhdGlvbmFsIGRpcmVjdG9yYXRl4oCZcyBvbmdvaW5nIGVmZm9ydCB0byByZXZpZXcg
YWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3NlZCBieSB0aGUgSUVTRy4gIFRoZXNlIGNv
bW1lbnRzIHdlcmUgd3JpdHRlbiB3aXRoIHRoZSBpbnRlbnQgb2YgaW1wcm92aW5nIHRoZSBvcGVy
YXRpb25hbCBhc3BlY3RzIG9mIHRoZSBJRVRGIGRyYWZ0cy4gQ29tbWVudHMgdGhhdCBhcmUgbm90
IGFkZHJlc3NlZCBpbiBsYXN0IGNhbGwgbWF5IGJlIGluY2x1ZGVkIGluIEFEIHJldmlld3MgZHVy
aW5nIHRoZSBJRVNHIHJldmlldy4gIERvY3VtZW50IGVkaXRvcnMgYW5kIFdHIGNoYWlycyBzaG91
bGQgdHJlYXQgdGhlc2UgY29tbWVudHMganVzdCBsaWtlIGFueSBvdGhlciBsYXN0IGNhbGwgY29t
bWVudHMuDQoNCg0KDQpEb2N1bWVudCByZXZpZXdlZDogIGRyYWZ0LWlldGYtb2F1dGgtbmF0aXZl
LWFwcHMtMTANCg0KDQoNClN1bW1hcnk6DQoNCg0KT0F1dGggMi4wIGF1dGhvcml6YXRpb24gcmVx
dWVzdHMgZnJvbSBuYXRpdmUgYXBwcyBzaG91bGQgb25seSBiZSBtYWRlDQp0aHJvdWdoIGV4dGVy
bmFsIHVzZXItYWdlbnRzLCBwcmltYXJpbHkgdGhlIHVzZXLigJlzIGJyb3dzZXIuIFRoaXMNCnNw
ZWNpZmljYXRpb24gZGV0YWlscyB0aGUgc2VjdXJpdHkgYW5kIHVzYWJpbGl0eSByZWFzb25zIHdo
eSB0aGlzIGlzDQp0aGUgY2FzZSwgYW5kIGhvdyBuYXRpdmUgYXBwcyBhbmQgYXV0aG9yaXphdGlv
biBzZXJ2ZXJzIGNhbiBpbXBsZW1lbnQNCg0KdGhpcyBiZXN0IHByYWN0aWNlLg0KDQoNCkkgdGhp
bmsgdGhlIGRvY3VtZW50IGlzIHdyaXR0ZW4gdmVyeSBjbGVhciwgZXhjZXB0IHNvbWUgc21hbGwg
bml0czoNCg0KUGFnZSAzOiAgICAgVGhlIGxhc3Qgc2VudGVuY2Ugb2YgaW50cm9kdWN0aW9uLS0g
4oCcVGhpcyBwcmFjdGljZSBpcyBhbHNvIGtub3duIGFzIHRoZSBBcHBBdXRoIHBhdHRlcm7igJ0u
DQoNCkkgc3VnZ2VzdCBhZGRpbmcgYSByZWZlcmVuY2UgdG8gZXhwbGFpbiB0aGUgQXBwQXV0aCBw
YXR0ZXJuLg0KDQpEb25lDQoNCg0KUGFnZSAzOiAgICAgVGVybWlub2xvZ3kgLS0gIk9BdXRoIi4N
Cg0KSSBzdWdnZXN0IG1vZGlmeWluZyB0bzogIk9BdXRoIiAgIFRoZSBXZWIgQXV0aG9yaXphdGlv
biAoT0F1dGgpIHByb3RvY29sLiAgSW4gdGhpcyBkb2N1bWVudCwgT0F1dGggcmVmZXJzIHRvIE9B
dXRoIDIuMCBbUkZDNjc0OV0uDQpJIHdlbnQgd2l0aDoNCiJJbiB0aGlzIGRvY3VtZW50LCBPQXV0
aCByZWZlcnMgdG8gdGhlIE9BdXRoIDIuMCBBdXRob3JpemF0aW9uIEZyYW1ld29yayBbUkZDNjc0
OV0uIg0KDQpUaGUgcGhyYXNlICJXZWIgQXV0aG9yaXphdGlvbiAoT0F1dGgpIHByb3RvY29sIiBv
bmx5IHNlZW1zIHRvIGFwcGVhciBpbiBvdXIgV0cgQ2hhcnRlciwgYW5kIG5vdCBnZW5lcmFsIHVz
YWdlPGh0dHBzOi8vd3d3Lmdvb2dsZS5jb20vc2VhcmNoP3E9d2ViK2F1dGhvcml6YXRpb24rcHJv
dG9jb2w+Lg0KDQoNClBhZ2UgNDogICAgIFRlcm1pbm9sb2d5IC0tICJ3ZWItdmlldyIgIEEgd2Vi
IGJyb3dzZXIgVUkgY29tcG9uZW50Lg0KDQpEb2VzIGl0IG1lYW4gIlVzZXIgSW5mb3JtYXRpb24i
PyAgU3VnZ2VzdCBleHBhbmRpbmcgdGhpcyBhYmJyZXZpYXRpb24uDQoNCkRvbmUuDQoNCg0KUGFn
ZSA1OiAgICAgRmlndXJlIDEuICAgRG9lcyB0aGUgYnJvd3NlciBhbmQgYXV0aG9yaXphdGlvbiBl
bmRwb2ludCBhcmUgc29tZSBraW5kcyBvZiAiZXh0ZXJuYWwgdXNlci1hZ2VudCI/IFN1Z2dlc3Qg
ZGVzY3JpYmluZyBpdCBtb3JlIGNsZWFybHkuDQoNCk5vdyBzdGF0ZXM6DQoiaWxsdXN0cmF0ZXMg
dGhlIGludGVyYWN0aW9uIG9mIHRoZSBuYXRpdmUgYXBwIHdpdGggYSBicm93c2VyDQogICAgICAg
IGV4dGVybmFsIHVzZXItYWdlbnQgdG8gYXV0aG9yaXplIHRoZSB1c2VyLiAiDQoNClBhZ2UgICA5
OiAgIFBLQ0UgW1JGQzc2MzZdIGRldGFpbHMgaG93IHRoaXMgbGltaXRhdGlvbiBjYW4gYmUgdXNl
ZCB0byBleGVjdXRlIGEgY29kZSBpbnRlcmNlcHRpb24gYXR0YWNrIChzZWUgRmlndXJlIDEpLg0K
DQpEb2VzIHRoZSBGaWd1cmUgMSBtZWFucyDigJxGaWd1cmUgMSBvZiBSRkM3NjM24oCdPw0KDQpH
b29kIGNhdGNoLiBJIGRlbGV0ZSB0aGUgZmlndXJlIHJlZmVyZW5jZSwgc2luY2UgdGhlIGVudGly
ZSBzcGVjIHRhbGtzIGFib3V0IHRoaXMgYXR0YWNrLCB3aGljaCBpcyBsaWtlbHkgc3VmZmljaWVu
dC4NCg0KDQpQYWdlMTA6ICAgICBIb3dldmVyLCBhcyB0aGUgSW1wbGljaXQgRmxvdyBjYW5ub3Qg
YmUgcHJvdGVjdGVkIGJ5IFBLQ0UNClNlZW1zIGhlcmUsIHRoZSByZWZlcmVuY2UgYmUgb21pdHRl
ZC4NCg0KQWRkZWQuDQoNCg0KQSBydW4gb2YgaWRuaXRzIHJldmVhbGVkIG5vIGVycm9ycywgZmxh
d3MuIFRoZXJlIHdlcmUgMSB3YXJuaW5nIGFuZCAxIGNvbW1lbnRzIHRob3VnaA0KDQoNCg0KICA9
PSBUaGVyZSBhcmUgMSBpbnN0YW5jZSBvZiBsaW5lcyB3aXRoIG5vbi1SRkMyNjA2LWNvbXBsaWFu
dCBGUUROcyBpbiB0aGUNCg0KICAgICBkb2N1bWVudC4NCg0KDQoNCkkgcmFuIGl0IG15c2VsZiB3
aXRoIHZlcmJvc2Ugb3V0cHV0LCBhbmQgZ290Og0KDQp0bXAvZHJhZnQtaWV0Zi1vYXV0aC1uYXRp
dmUtYXBwc19fMV8udHh0KDQzNSk6IEZvdW5kIHBvc3NpYmxlIEZRRE4gJ2NvbS5leGFtcGxlLmFw
cCcgaW4gcG9zaXRpb24gNTsgdGhpcyBkb2Vzbid0IG1hdGNoIFJGQyAyNjA2J3Mgc3VnZ2VzdGVk
ICIuZXhhbXBsZSIgb3IgIi5leGFtcGxlLihjb218b3JnfG5ldCkiLg0KDQpXZSBhcmUgYWN0dWFs
bHkgdXNpbmcgYSBSRkMyNjA2IGRvbWFpbiBuYW1lIGhlcmUsIGJ1dCBpbiByZXZlcnNlIGRvbWFp
biBuYW1lIG5vdGF0aW9uIHdoaWNoIGlzIGNhdXNpbmcgdGhpcyB3YXJuaW5nLg0KDQpObyBjaGFu
Z2VzIHJlcXVpcmVkLg0KDQoNCiAgTWlzY2VsbGFuZW91cyB3YXJuaW5nczoNCg0KICAtLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tDQoNCg0KDQogIC0tIFRoZSBkb2N1bWVudCBkYXRlIChBcHJpbCAyNiwgMjAx
NykgaXMgMTQgZGF5cyBpbiB0aGUgcGFzdC4gIElzIHRoaXMNCg0KICAgICBpbnRlbnRpb25hbD8N
Cg0KDQoNCg0KDQogIENoZWNraW5nIHJlZmVyZW5jZXMgZm9yIGludGVuZGVkIHN0YXR1czogQmVz
dCBDdXJyZW50IFByYWN0aWNlDQoNCiAgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQoNCg0KICAgICAo
U2VlIFJGQ3MgMzk2NyBhbmQgNDg5NyBmb3IgaW5mb3JtYXRpb24gYWJvdXQgdXNpbmcgbm9ybWF0
aXZlIHJlZmVyZW5jZXMNCg0KICAgICB0byBsb3dlci1tYXR1cml0eSBkb2N1bWVudHMgaW4gUkZD
cykNCg0KDQoNCiAgICAgTm8gaXNzdWVzIGZvdW5kIGhlcmUuDQoNCg0KDQogICAgIFN1bW1hcnk6
IDAgZXJyb3JzICgqKiksIDAgZmxhd3MgKH5+KSwgMSB3YXJuaW5nICg9PSksIDEgY29tbWVudCAo
LS0pLg0KDQoNCg0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fDQoNCk9QUy1ESVIgbWFpbGluZyBsaXN0DQoNCk9QUy1ESVJAaWV0Zi5vcmc8bWFpbHRv
Ok9QUy1ESVJAaWV0Zi5vcmc+DQoNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vb3BzLWRpcg0KDQoNCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
5a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNvbnNvbGFzOw0KCXBh
bm9zZS0xOjIgMTEgNiA5IDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IlxA5a6L5L2TIjsNCglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30NCi8qIFN0eWxlIERl
ZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJ
e21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7
DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQphOmxpbmssIHNwYW4u
TXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRl
eHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0Zv
bGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1k
ZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwcmUNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1z
by1zdHlsZS1saW5rOiJIVE1MIOmihOiuvuagvOW8jyBDaGFyIjsNCgltYXJnaW46MGNtOw0KCW1h
cmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OiJD
b3VyaWVyIE5ldyI7fQ0KcC5tLTM3MDU2NjA2MjkzMjQzMDcyODBnbWFpbC1tLTM2MDM4NjEwNTE2
MTk3ODQ2NTJtLTc5NDI0ODE5NTY4NDQ5OTc0NjlnbWFpbC1tLTQ1MTg2NjUyMjYyNTEzOTg0NDdt
c29wbGFpbnRleHQsIGxpLm0tMzcwNTY2MDYyOTMyNDMwNzI4MGdtYWlsLW0tMzYwMzg2MTA1MTYx
OTc4NDY1Mm0tNzk0MjQ4MTk1Njg0NDk5NzQ2OWdtYWlsLW0tNDUxODY2NTIyNjI1MTM5ODQ0N21z
b3BsYWludGV4dCwgZGl2Lm0tMzcwNTY2MDYyOTMyNDMwNzI4MGdtYWlsLW0tMzYwMzg2MTA1MTYx
OTc4NDY1Mm0tNzk0MjQ4MTk1Njg0NDk5NzQ2OWdtYWlsLW0tNDUxODY2NTIyNjI1MTM5ODQ0N21z
b3BsYWludGV4dA0KCXttc28tc3R5bGUtbmFtZTptXy0zNzA1NjYwNjI5MzI0MzA3MjgwZ21haWwt
bV8tMzYwMzg2MTA1MTYxOTc4NDY1Mm1fLTc5NDI0ODE5NTY4NDQ5OTc0NjlnbWFpbC1tXy00NTE4
NjY1MjI2MjUxMzk4NDQ3bXNvcGxhaW50ZXh0Ow0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0K
CW1hcmdpbi1yaWdodDowY207DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2lu
LWxlZnQ6MGNtOw0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBS
b21hbiIsInNlcmlmIjt9DQpzcGFuLkhUTUxDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJIVE1MIOmi
hOiuvuagvOW8jyBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxp
bms6IkhUTUwg6aKE6K6+5qC85byPIjsNCglmb250LWZhbWlseTpDb25zb2xhczt9DQpzcGFuLkVt
YWlsU3R5bGUyMA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWls
eToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1
bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJ
e3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgOTAuMHB0IDcyLjBwdCA5MC4w
cHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxl
PjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIg
c3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48
eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQi
IGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+
DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNs
YXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkNvb2whIFRoaXMgY2hhbmdlcy9leHBsYWlucyBt
YWtlIHNlbnNlIHRvIG1lLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+QmVzdCBSZWdhcmRzITxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztj
b2xvcjojMUY0OTdEIj4tTWljaGFlbDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXIt
dG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSI+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBsYW5nPSJaSC1DTiIgc3R5bGU9ImZvbnQtc2l6ZTox
MC4wcHQ7Zm9udC1mYW1pbHk65a6L5L2TIj7lj5Hku7bkuro8L3NwYW4+PC9iPjxiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OuWui+S9kyI+Ojwvc3Bhbj48L2I+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk65a6L5L2TIj4gV2lsbGlhbSBE
ZW5uaXNzIFttYWlsdG86d2Rlbm5pc3NAZ29vZ2xlLmNvbV0NCjxicj4NCjxiPjxzcGFuIGxhbmc9
IlpILUNOIj7lj5HpgIHml7bpl7Q8L3NwYW4+OjwvYj4gMjAxNzxzcGFuIGxhbmc9IlpILUNOIj7l
ubQ8L3NwYW4+NTxzcGFuIGxhbmc9IlpILUNOIj7mnIg8L3NwYW4+MjM8c3BhbiBsYW5nPSJaSC1D
TiI+5pelPC9zcGFuPiAzOjA5PGJyPg0KPGI+PHNwYW4gbGFuZz0iWkgtQ04iPuaUtuS7tuS6ujwv
c3Bhbj46PC9iPiB3YW5neml0YW88YnI+DQo8Yj48c3BhbiBsYW5nPSJaSC1DTiI+5oqE6YCBPC9z
cGFuPjo8L2I+IG9wcy1kaXJAaWV0Zi5vcmc7IG9hdXRoQGlldGYub3JnOyBkcmFmdC1pZXRmLW9h
dXRoLW5hdGl2ZS1hcHBzLmFsbEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzxicj4NCjxiPjxzcGFu
IGxhbmc9IlpILUNOIj7kuLvpopg8L3NwYW4+OjwvYj4gUmU6IFtPUFMtRElSXSBPcHNkaXIgdGVs
ZWNoYXQgcmV2aWV3IG9mIGRyYWZ0LWlldGYtb2F1dGgtbmF0aXZlLWFwcHMtMTA8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoYW5rcyBmb3IgeW91ciByZXZp
ZXcgWml0YW8hPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5W
ZXJzaW9uIDEyIGFkZHJlc3NlcyB5b3VyIGNvbW1lbnRzLiBEZXRhaWxlZCByZXNwb25zZXMgYmVs
b3c6PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gU3VuLCBNYXkgMjEs
IDIwMTcgYXQgODowNSBQTSwgd2FuZ3ppdGFvICZsdDs8YSBocmVmPSJtYWlsdG86d2FuZ3ppdGFv
QGh1YXdlaS5jb20iIHRhcmdldD0iX2JsYW5rIj53YW5neml0YW9AaHVhd2VpLmNvbTwvYT4mZ3Q7
IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0ibS0zNzA1NjYw
NjI5MzI0MzA3MjgwZ21haWwtbS0zNjAzODYxMDUxNjE5Nzg0NjUybS03OTQyNDgxOTU2ODQ0OTk3
NDY5Z21haWwtbS00NTE4NjY1MjI2MjUxMzk4NDQ3bXNvcGxhaW50ZXh0Ij4NClJldmlld2VyOiBa
aXRhbyBXYW5nIChNaWNoYWVsKTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Im0tMzcwNTY2MDYy
OTMyNDMwNzI4MGdtYWlsLW0tMzYwMzg2MTA1MTYxOTc4NDY1Mm0tNzk0MjQ4MTk1Njg0NDk5NzQ2
OWdtYWlsLW0tNDUxODY2NTIyNjI1MTM5ODQ0N21zb3BsYWludGV4dCI+DQpSZXZpZXcgcmVzdWx0
OiBIYXMgTml0czxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Im0tMzcwNTY2MDYyOTMyNDMwNzI4
MGdtYWlsLW0tMzYwMzg2MTA1MTYxOTc4NDY1Mm0tNzk0MjQ4MTk1Njg0NDk5NzQ2OWdtYWlsLW0t
NDUxODY2NTIyNjI1MTM5ODQ0N21zb3BsYWludGV4dCI+DQombmJzcDs8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJtLTM3MDU2NjA2MjkzMjQzMDcyODBnbWFpbC1tLTM2MDM4NjEwNTE2MTk3ODQ2
NTJtLTc5NDI0ODE5NTY4NDQ5OTc0NjlnbWFpbC1tLTQ1MTg2NjUyMjYyNTEzOTg0NDdtc29wbGFp
bnRleHQiPg0KSSBoYXZlIHJldmlld2VkIHRoaXMgZG9jdW1lbnQgYXMgcGFydCBvZiB0aGUgT3Bl
cmF0aW9uYWwgZGlyZWN0b3JhdGXigJlzJm5ic3A7b25nb2luZyBlZmZvcnQgdG8gcmV2aWV3IGFs
bCBJRVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQgYnkgdGhlIElFU0cuJm5ic3A7IFRoZXNl
Jm5ic3A7Y29tbWVudHMgd2VyZSB3cml0dGVuIHdpdGggdGhlIGludGVudCBvZiBpbXByb3Zpbmcg
dGhlIG9wZXJhdGlvbmFsJm5ic3A7YXNwZWN0cyBvZiB0aGUgSUVURiBkcmFmdHMuIENvbW1lbnRz
IHRoYXQNCiBhcmUgbm90IGFkZHJlc3NlZCBpbiBsYXN0IGNhbGwgbWF5IGJlIGluY2x1ZGVkIGlu
IEFEIHJldmlld3MgZHVyaW5nIHRoZSBJRVNHIHJldmlldy4mbmJzcDsgRG9jdW1lbnQgZWRpdG9y
cyBhbmQmbmJzcDtXRyBjaGFpcnMgc2hvdWxkIHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1c3QgbGlr
ZSBhbnkgb3RoZXIgbGFzdCBjYWxsJm5ic3A7Y29tbWVudHMuPG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0ibS0zNzA1NjYwNjI5MzI0MzA3MjgwZ21haWwtbS0zNjAzODYxMDUxNjE5Nzg0NjUybS03
OTQyNDgxOTU2ODQ0OTk3NDY5Z21haWwtbS00NTE4NjY1MjI2MjUxMzk4NDQ3bXNvcGxhaW50ZXh0
Ij4NCiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Im0tMzcwNTY2MDYyOTMyNDMwNzI4
MGdtYWlsLW0tMzYwMzg2MTA1MTYxOTc4NDY1Mm0tNzk0MjQ4MTk1Njg0NDk5NzQ2OWdtYWlsLW0t
NDUxODY2NTIyNjI1MTM5ODQ0N21zb3BsYWludGV4dCI+DQpEb2N1bWVudCByZXZpZXdlZDogJm5i
c3A7ZHJhZnQtaWV0Zi1vYXV0aC1uYXRpdmUtYXBwcy0xMDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Im0tMzcwNTY2MDYyOTMyNDMwNzI4MGdtYWlsLW0tMzYwMzg2MTA1MTYxOTc4NDY1Mm0tNzk0
MjQ4MTk1Njg0NDk5NzQ2OWdtYWlsLW0tNDUxODY2NTIyNjI1MTM5ODQ0N21zb3BsYWludGV4dCI+
DQombmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJtLTM3MDU2NjA2MjkzMjQzMDcyODBn
bWFpbC1tLTM2MDM4NjEwNTE2MTk3ODQ2NTJtLTc5NDI0ODE5NTY4NDQ5OTc0NjlnbWFpbC1tLTQ1
MTg2NjUyMjYyNTEzOTg0NDdtc29wbGFpbnRleHQiPg0KU3VtbWFyeTogPG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0ibS0zNzA1NjYwNjI5MzI0MzA3MjgwZ21haWwtbS0zNjAzODYxMDUxNjE5Nzg0
NjUybS03OTQyNDgxOTU2ODQ0OTk3NDY5Z21haWwtbS00NTE4NjY1MjI2MjUxMzk4NDQ3bXNvcGxh
aW50ZXh0Ij4NCiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVw
dDtmb250LWZhbWlseTpDb25zb2xhcyI+T0F1dGggMi4wIGF1dGhvcml6YXRpb24gcmVxdWVzdHMg
ZnJvbSBuYXRpdmUgYXBwcyBzaG91bGQgb25seSBiZSBtYWRlPC9zcGFuPjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTpDb25zb2xhcyI+dGhyb3Vn
aCBleHRlcm5hbCB1c2VyLWFnZW50cywgcHJpbWFyaWx5IHRoZSB1c2Vy4oCZcyBicm93c2VyLiBU
aGlzPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250
LWZhbWlseTpDb25zb2xhcyI+c3BlY2lmaWNhdGlvbiBkZXRhaWxzIHRoZSBzZWN1cml0eSBhbmQg
dXNhYmlsaXR5IHJlYXNvbnMgd2h5IHRoaXMgaXM8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG8iPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzIj50aGUgY2FzZSwgYW5k
IGhvdyBuYXRpdmUgYXBwcyBhbmQgYXV0aG9yaXphdGlvbiBzZXJ2ZXJzIGNhbiBpbXBsZW1lbnQ8
L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0ibS0zNzA1NjYwNjI5MzI0MzA3MjgwZ21h
aWwtbS0zNjAzODYxMDUxNjE5Nzg0NjUybS03OTQyNDgxOTU2ODQ0OTk3NDY5Z21haWwtbS00NTE4
NjY1MjI2MjUxMzk4NDQ3bXNvcGxhaW50ZXh0Ij4NCnRoaXMgYmVzdCBwcmFjdGljZS48bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJtLTM3MDU2NjA2MjkzMjQzMDcyODBnbWFpbC1tLTM2MDM4NjEw
NTE2MTk3ODQ2NTJtLTc5NDI0ODE5NTY4NDQ5OTc0NjlnbWFpbC1tLTQ1MTg2NjUyMjYyNTEzOTg0
NDdtc29wbGFpbnRleHQiPg0KJm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFz
Ij5JIHRoaW5rIHRoZSBkb2N1bWVudCBpcyB3cml0dGVuIHZlcnkgY2xlYXIsIGV4Y2VwdCBzb21l
IHNtYWxsIG5pdHM6PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Im0tMzcwNTY2MDYy
OTMyNDMwNzI4MGdtYWlsLW0tMzYwMzg2MTA1MTYxOTc4NDY1Mm0tNzk0MjQ4MTk1Njg0NDk5NzQ2
OWdtYWlsLW0tNDUxODY2NTIyNjI1MTM5ODQ0N21zb3BsYWludGV4dCI+DQo8YSBuYW1lPSJtXy0z
NzA1NjYwNjI5MzI0MzA3MjgwX21fLTM2MDM4NjEwNTE2MTk3Ij5QYWdlIDM6PC9hPiZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyBUaGUgbGFzdCBzZW50ZW5jZSBvZiBpbnRyb2R1Y3Rpb24tLSDigJxU
aGlzIHByYWN0aWNlIGlzIGFsc28ga25vd24gYXMgdGhlIEFwcEF1dGggcGF0dGVybuKAnS4mbmJz
cDsmbmJzcDsNCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Im0tMzcwNTY2MDYyOTMyNDMwNzI4
MGdtYWlsLW0tMzYwMzg2MTA1MTYxOTc4NDY1Mm0tNzk0MjQ4MTk1Njg0NDk5NzQ2OWdtYWlsLW0t
NDUxODY2NTIyNjI1MTM5ODQ0N21zb3BsYWludGV4dCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBw
dDt0ZXh0LWluZGVudDozNi4wcHQiPg0KSSBzdWdnZXN0IGFkZGluZyBhIHJlZmVyZW5jZSB0byBl
eHBsYWluIHRoZSBBcHBBdXRoIHBhdHRlcm4uPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+RG9uZTxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAj
Q0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7
bWFyZ2luLXJpZ2h0OjBjbSI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJtLTM3MDU2NjA2Mjkz
MjQzMDcyODBnbWFpbC1tLTM2MDM4NjEwNTE2MTk3ODQ2NTJtLTc5NDI0ODE5NTY4NDQ5OTc0Njln
bWFpbC1tLTQ1MTg2NjUyMjYyNTEzOTg0NDdtc29wbGFpbnRleHQiPg0KUGFnZSAzOiZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyBUZXJtaW5vbG9neSAtLSAmcXVvdDtPQXV0aCZxdW90Oy4mbmJzcDsg
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0ibS0zNzA1NjYwNjI5MzI0MzA3MjgwZ21haWwtbS0z
NjAzODYxMDUxNjE5Nzg0NjUybS03OTQyNDgxOTU2ODQ0OTk3NDY5Z21haWwtbS00NTE4NjY1MjI2
MjUxMzk4NDQ3bXNvcGxhaW50ZXh0IiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0O3RleHQtaW5k
ZW50OjM2LjBwdCI+DQpJIHN1Z2dlc3QgbW9kaWZ5aW5nIHRvOiAmcXVvdDtPQXV0aCZxdW90OyZu
YnNwOyZuYnNwOyBUaGUgV2ViIEF1dGhvcml6YXRpb24gKE9BdXRoKSBwcm90b2NvbC4mbmJzcDsg
SW4gdGhpcyBkb2N1bWVudCwgT0F1dGggcmVmZXJzIHRvIE9BdXRoIDIuMCBbUkZDNjc0OV0uPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPkkgd2VudCB3aXRoOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+JnF1b3Q7SW4gdGhpcyBkb2N1bWVudCwgT0F1dGggcmVm
ZXJzIHRvIHRoZSBPQXV0aCAyLjAgQXV0aG9yaXphdGlvbiBGcmFtZXdvcmsgW1JGQzY3NDldLiZx
dW90OzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5UaGUgcGhyYXNlICZxdW90O1dlYiBBdXRob3JpemF0aW9uIChPQXV0aCkgcHJvdG9jb2wmcXVv
dDsgb25seSBzZWVtcyB0byBhcHBlYXIgaW4gb3VyIFdHIENoYXJ0ZXIsIGFuZA0KPGEgaHJlZj0i
aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS9zZWFyY2g/cT13ZWImIzQzO2F1dGhvcml6YXRpb24mIzQz
O3Byb3RvY29sIiB0YXJnZXQ9Il9ibGFuayI+DQpub3QgZ2VuZXJhbCB1c2FnZTwvYT4uPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRl
ci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJn
aW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Im0tMzcwNTY2MDYyOTMyNDMwNzI4MGdtYWlsLW0tMzYwMzg2MTA1MTYxOTc4NDY1Mm0tNzk0MjQ4
MTk1Njg0NDk5NzQ2OWdtYWlsLW0tNDUxODY2NTIyNjI1MTM5ODQ0N21zb3BsYWludGV4dCI+DQpQ
YWdlIDQ6Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IFRlcm1pbm9sb2d5IC0tICZxdW90O3dlYi12
aWV3JnF1b3Q7Jm5ic3A7IEEgd2ViIGJyb3dzZXIgVUkgY29tcG9uZW50LiZuYnNwOyZuYnNwOyA8
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJtLTM3MDU2NjA2MjkzMjQzMDcyODBnbWFpbC1tLTM2
MDM4NjEwNTE2MTk3ODQ2NTJtLTc5NDI0ODE5NTY4NDQ5OTc0NjlnbWFpbC1tLTQ1MTg2NjUyMjYy
NTEzOTg0NDdtc29wbGFpbnRleHQiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQ7dGV4dC1pbmRl
bnQ6MzYuMHB0Ij4NCkRvZXMgaXQgbWVhbiAmcXVvdDtVc2VyIEluZm9ybWF0aW9uJnF1b3Q7PyZu
YnNwOyBTdWdnZXN0IGV4cGFuZGluZyB0aGlzIGFiYnJldmlhdGlvbi48bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5Eb25lLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJi
b3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBj
bSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8ZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJtLTM3MDU2NjA2MjkzMjQzMDcyODBnbWFpbC1tLTM2MDM4NjEwNTE2
MTk3ODQ2NTJtLTc5NDI0ODE5NTY4NDQ5OTc0NjlnbWFpbC1tLTQ1MTg2NjUyMjYyNTEzOTg0NDdt
c29wbGFpbnRleHQiPg0KUGFnZSA1OiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBGaWd1cmUgMS4m
bmJzcDsmbmJzcDsgRG9lcyB0aGUgYnJvd3NlciBhbmQgYXV0aG9yaXphdGlvbiBlbmRwb2ludCBh
cmUgc29tZSBraW5kcyBvZiAmcXVvdDtleHRlcm5hbCB1c2VyLWFnZW50JnF1b3Q7PyBTdWdnZXN0
IGRlc2NyaWJpbmcgaXQgbW9yZSBjbGVhcmx5LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rp
dj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk5vdyBzdGF0
ZXM6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4m
cXVvdDtpbGx1c3RyYXRlcyB0aGUgaW50ZXJhY3Rpb24gb2YgdGhlIG5hdGl2ZSBhcHAgd2l0aCBh
IGJyb3dzZXI8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBleHRlcm5hbCB1c2VyLWFnZW50IHRvIGF1
dGhvcml6ZSB0aGUgdXNlci4gJnF1b3Q7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2Nr
cXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7
cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6
MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWls
eTpDb25zb2xhcyI+UGFnZSZuYnNwOyZuYnNwOyA5OiZuYnNwOyZuYnNwOyBQS0NFIFtSRkM3NjM2
XSBkZXRhaWxzIGhvdyB0aGlzIGxpbWl0YXRpb24gY2FuIGJlIHVzZWQgdG8gZXhlY3V0ZSBhIGNv
ZGUgaW50ZXJjZXB0aW9uIGF0dGFjayAoc2VlIEZpZ3VyZSAxKS4mbmJzcDsmbmJzcDsmbmJzcDsN
Cjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJtLTM3MDU2NjA2MjkzMjQzMDcyODBn
bWFpbC1tLTM2MDM4NjEwNTE2MTk3ODQ2NTJtLTc5NDI0ODE5NTY4NDQ5OTc0NjlnbWFpbC1tLTQ1
MTg2NjUyMjYyNTEzOTg0NDdtc29wbGFpbnRleHQiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQ7
dGV4dC1pbmRlbnQ6MzYuMHB0Ij4NCkRvZXMgdGhlIEZpZ3VyZSAxIG1lYW5zIOKAnEZpZ3VyZSAx
IG9mIFJGQzc2MzbigJ0/Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9i
bG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+R29vZCBjYXRjaC4gSSBk
ZWxldGUgdGhlIGZpZ3VyZSByZWZlcmVuY2UsIHNpbmNlIHRoZSBlbnRpcmUgc3BlYyB0YWxrcyBh
Ym91dCB0aGlzIGF0dGFjaywgd2hpY2ggaXMgbGlrZWx5IHN1ZmZpY2llbnQuPG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0
OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVm
dDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2Zv
bnQtZmFtaWx5OkNvbnNvbGFzIj5QYWdlMTA6Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IEhvd2V2
ZXIsIGFzIHRoZSBJbXBsaWNpdCBGbG93IGNhbm5vdCBiZSBwcm90ZWN0ZWQgYnkgUEtDRSZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21hcmdpbi1sZWZ0OjM2LjBw
dDt0ZXh0LWluZGVudDozNi4wcHQiPg0KPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9u
dC1mYW1pbHk6Q29uc29sYXMiPlNlZW1zIGhlcmUsIHRoZSByZWZlcmVuY2UgYmUgb21pdHRlZC4m
bmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3Rl
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QWRkZWQuPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlk
ICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0Ljhw
dDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPHByZT48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjVwdDtmb250LWZhbWlseTpDb25zb2xhcyI+QSBydW4gb2YgaWRuaXRzIHJldmVh
bGVkIG5vIGVycm9ycywgZmxhd3MuIFRoZXJlIHdlcmUgMSB3YXJuaW5nIGFuZCAxIGNvbW1lbnRz
IHRob3VnaDwvc3Bhbj48bzpwPjwvbzpwPjwvcHJlPg0KPHAgY2xhc3M9Im0tMzcwNTY2MDYyOTMy
NDMwNzI4MGdtYWlsLW0tMzYwMzg2MTA1MTYxOTc4NDY1Mm0tNzk0MjQ4MTk1Njg0NDk5NzQ2OWdt
YWlsLW0tNDUxODY2NTIyNjI1MTM5ODQ0N21zb3BsYWludGV4dCI+DQombmJzcDs8bzpwPjwvbzpw
PjwvcD4NCjxwcmU+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJzcDsgPT0gVGhlcmUgYXJl
IDEgaW5zdGFuY2Ugb2YgbGluZXMgd2l0aCBub24tUkZDMjYwNi1jb21wbGlhbnQgRlFETnMgaW4g
dGhlPC9zcGFuPjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFj
ayI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGRvY3VtZW50Ljwvc3Bhbj48bzpwPjwvbzpwPjwv
cHJlPg0KPHByZT48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPiZuYnNwOzwvc3Bhbj48bzpwPjwv
bzpwPjwvcHJlPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPkkgcmFuIGl0IG15c2VsZiB3aXRoIHZlcmJvc2Ugb3V0cHV0LCBhbmQg
Z290OjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHByZSBzdHlsZT0id29yZC13cmFw
OmJyZWFrLXdvcmQ7d2hpdGUtc3BhY2U6cHJlLXdyYXAiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFj
ayI+dG1wL2RyYWZ0LWlldGYtb2F1dGgtbmF0aXZlLWFwcHNfXzFfLnR4dCg0MzUpOiBGb3VuZCBw
b3NzaWJsZSBGUUROICdjb20uZXhhbXBsZS5hcHAnIGluIHBvc2l0aW9uIDU7IHRoaXMgZG9lc24n
dCBtYXRjaCBSRkMgMjYwNidzIHN1Z2dlc3RlZCAmcXVvdDsuZXhhbXBsZSZxdW90OyBvciAmcXVv
dDsuZXhhbXBsZS4oY29tfG9yZ3xuZXQpJnF1b3Q7LjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5XZSBhcmUgYWN0dWFsbHkgdXNp
bmcgYSBSRkMyNjA2IGRvbWFpbiBuYW1lIGhlcmUsIGJ1dCBpbiByZXZlcnNlIGRvbWFpbiBuYW1l
IG5vdGF0aW9uIHdoaWNoIGlzIGNhdXNpbmcgdGhpcyB3YXJuaW5nLjxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5ObyBjaGFuZ2VzIHJlcXVpcmVk
LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5i
c3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9u
ZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4w
cHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8ZGl2Pg0KPGRpdj4NCjxw
cmU+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJzcDsgTWlzY2VsbGFuZW91cyB3YXJuaW5n
czo8L3NwYW4+PG86cD48L286cD48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNr
Ij4mbmJzcDsgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTwvc3Bhbj48bzpwPjwvbzpwPjwvcHJlPg0KPHBy
ZT48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcHJl
Pg0KPHByZT48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPiZuYnNwOyAtLSBUaGUgZG9jdW1lbnQg
ZGF0ZSAoQXByaWwgMjYsIDIwMTcpIGlzIDE0IGRheXMgaW4gdGhlIHBhc3QuJm5ic3A7IElzIHRo
aXM8L3NwYW4+PG86cD48L286cD48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNr
Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgaW50ZW50aW9uYWw/PC9zcGFuPjxvOnA+PC9vOnA+
PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+Jm5ic3A7PC9zcGFuPjxvOnA+
PC9vOnA+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+Jm5ic3A7PC9zcGFu
PjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+Jm5ic3A7
IENoZWNraW5nIHJlZmVyZW5jZXMgZm9yIGludGVuZGVkIHN0YXR1czogQmVzdCBDdXJyZW50IFBy
YWN0aWNlPC9zcGFuPjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJjb2xvcjpi
bGFjayI+Jm5ic3A7IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08L3NwYW4+PG86cD48L286cD48L3ByZT4N
CjxwcmU+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48
L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsgKFNlZSBSRkNzIDM5NjcgYW5kIDQ4OTcgZm9yIGluZm9ybWF0aW9uIGFib3V0IHVzaW5n
IG5vcm1hdGl2ZSByZWZlcmVuY2VzPC9zcGFuPjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPjxzcGFu
IHN0eWxlPSJjb2xvcjpibGFjayI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHRvIGxvd2VyLW1h
dHVyaXR5IGRvY3VtZW50cyBpbiBSRkNzKTwvc3Bhbj48bzpwPjwvbzpwPjwvcHJlPg0KPHByZT48
c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcHJlPg0K
PHByZT48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBO
byBpc3N1ZXMgZm91bmQgaGVyZS48L3NwYW4+PG86cD48L286cD48L3ByZT4NCjxwcmU+PHNwYW4g
c3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3ByZT4NCjxwcmU+
PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgU3VtbWFy
eTogMCBlcnJvcnMgKCoqKSwgMCBmbGF3cyAofn4pLCAxIHdhcm5pbmcgKD09KSwgMSBjb21tZW50
ICgtLSkuPC9zcGFuPjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJjb2xvcjpi
bGFjayI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJj
b2xvcjpibGFjayI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wcmU+DQo8cCBjbGFzcz0ibS0z
NzA1NjYwNjI5MzI0MzA3MjgwZ21haWwtbS0zNjAzODYxMDUxNjE5Nzg0NjUybS03OTQyNDgxOTU2
ODQ0OTk3NDY5Z21haWwtbS00NTE4NjY1MjI2MjUxMzk4NDQ3bXNvcGxhaW50ZXh0Ij4NCl9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0ibS0zNzA1NjYwNjI5MzI0MzA3MjgwZ21haWwtbS0zNjAzODYxMDUxNjE5Nzg0
NjUybS03OTQyNDgxOTU2ODQ0OTk3NDY5Z21haWwtbS00NTE4NjY1MjI2MjUxMzk4NDQ3bXNvcGxh
aW50ZXh0Ij4NCk9QUy1ESVIgbWFpbGluZyBsaXN0PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
bS0zNzA1NjYwNjI5MzI0MzA3MjgwZ21haWwtbS0zNjAzODYxMDUxNjE5Nzg0NjUybS03OTQyNDgx
OTU2ODQ0OTk3NDY5Z21haWwtbS00NTE4NjY1MjI2MjUxMzk4NDQ3bXNvcGxhaW50ZXh0Ij4NCjxh
IGhyZWY9Im1haWx0bzpPUFMtRElSQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+T1BTLURJUkBp
ZXRmLm9yZzwvYT48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJtLTM3MDU2NjA2MjkzMjQzMDcy
ODBnbWFpbC1tLTM2MDM4NjEwNTE2MTk3ODQ2NTJtLTc5NDI0ODE5NTY4NDQ5OTc0NjlnbWFpbC1t
LTQ1MTg2NjUyMjYyNTEzOTg0NDdtc29wbGFpbnRleHQiPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vcHMtZGlyIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vcHMtZGlyPC9hPjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+
DQo8L2h0bWw+DQo=

--_000_E6BC9BBCBCACC246846FC685F9FF41EA2AE09727DGGEMM506MBXchi_--


From nobody Mon May 22 22:00:13 2017
Return-Path: <kaduk@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 0B18612896F; Mon, 22 May 2017 22:00:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.817
X-Spam-Level: 
X-Spam-Status: No, score=-0.817 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FAKE_REPLY_C=1.486, RCVD_IN_DNSWL_MED=-2.3, 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 AQKKc9s8MDgG; Mon, 22 May 2017 22:00:09 -0700 (PDT)
Received: from dmz-mailsec-scanner-2.mit.edu (dmz-mailsec-scanner-2.mit.edu [18.9.25.13]) (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 687A7126E3A; Mon, 22 May 2017 22:00:09 -0700 (PDT)
X-AuditID: 1209190d-55dff70000000583-45-5923c1d7f65d
Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP id 63.06.01411.7D1C3295; Tue, 23 May 2017 01:00:07 -0400 (EDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id v4N505bg022080; Tue, 23 May 2017 01:00:06 -0400
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v4N500Bs028472 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 23 May 2017 01:00:04 -0400
Date: Tue, 23 May 2017 00:00:00 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Khaled Omar <eng.khaled.omar@hotmail.com>, ietf-secretariat@ietf.org
Cc: ietf@ietf.org
Subject: Re: IPv10, KRP, and RRP IDs Removal.
Message-ID: <20170523050000.GW39245@kduck.kaduk.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AM4PR0401MB2241731801FD7F70B2DD246FBDF80@AM4PR0401MB2241.eurprd04.prod.outlook.com>
User-Agent: Mutt/1.7.1 (2016-10-04)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrIIsWRmVeSWpSXmKPExsUixCmqrHv9oHKkwfG3lhZd27eyWSztbWGx eLZxPosDs8fjnjNsHkuW/GQKYIrisklJzcksSy3St0vgyvgy/ztbwXXeiu+HZjI3MP7l6mLk 5JAQMJFYNKGbtYuRi0NIYDGTxMsn25kgnI2MEi+272KGcK4ySfxdu4wZpIVFQFXiyqPLLCA2 m4CKREP3ZaA4B4eIgIfE60mBIGFmAUGJyX8/M4KEhQV0JU7MigAJ8wIt23hhOTuELShxcuYT FohyLYkb/14ygZQzC0hLLP/HAWJyCiRKLLwuBVIhKqAs8ffwPZYJjPyzkDTPQtI8C6F5ASPz KkbZlNwq3dzEzJzi1GTd4uTEvLzUIl0jvdzMEr3UlNJNjOCQlOTdwfjvrtchRgEORiUeXo3H SpFCrIllxZW5hxglOZiURHn3JChHCvEl5adUZiQWZ8QXleakFh9ilOBgVhLhvbAQKMebklhZ lVqUD5OS5mBREucV12iMEBJITyxJzU5NLUgtgsnKcHAoSfC2HQBqFCxKTU+tSMvMKUFIM3Fw ggznARruD1LDW1yQmFucmQ6RP8WoKCXO+3M/UEIAJJFRmgfXC0oZEtn7a14xigO9IszLBEwg QjzAdAPX/QpoMBPQYOtn8iCDSxIRUlINjD4vbzXFz12idzDu0Yp8Iy4PvoClP++qfZr3suvz rT+bPqmEsrN+0vuXnnC8foqgiOWevcwvHgrl638sUtgftkM4ufNk1vxNhyQYHj/8Osd0avWj 6Ncv+6RlXT/ULTh09svcnn+JHaFnXziazo3k3LpsfYSXVpUp52XmPs/vUexzjJ6mFj7a9k2J pTgj0VCLuag4EQAMGQtc9AIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kFJiyzo_H8H6ZPOgUTAVKQhYqMI>
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, 23 May 2017 05:00:11 -0000

Dear Khaled,

Speaking as sergeant-at-arms,

You were recently placed under a temporary suspension of posting
rights to this list [1], a message that suggested you use that
time to read about the process of submitting and discussing drafts
at the IETF.  It seems that you have not taken advantage of the
opportunity to do so, as you persist in using an overly broad
recipient list when corresponding with the address used for draft
submission, and are attempting to block discussion of technical
issues on a list reserved for such discussions of technical issues.

With my authority as sergeant-at-arms under RFC 3004, I am forced to
request that the secretariat apply an additional restriction of your
posting rights for the period of 60 days, starting immediately.

If you do decide to bring new work to the IETF in the future, we
will expect that you and keep traffic on the IETF mailing
lists focused on discussion of technical issues and in the
appropriate venue(s).

-Ben Kaduk

[1] https://www.ietf.org/mail-archive/web/ietf/current/msg102743.html

On Mon, May 22, 2017 at 10:55:02PM +0000, Khaled Omar wrote:
> Hi Jasmine,
> 
> As I'm the only author of the following IDs:
> 
> 
> 1)      Internet Protocol version 10 (IPv10): https://datatracker.ietf.org/doc/draft-omar-ipv10/
> 
> 
> 2)      KHALED Routing Protocol (KRP): https://datatracker.ietf.org/doc/draft-omar-krp/
> 
> 
> 3)      Regional Routing Protocol (RRP): https://datatracker.ietf.org/doc/draft-omar-rrp/
> 
> 
> Please remove them all from the ietf database or repository.
> 
> If the ideas explained on these drafts will be used, discussed or published by the ietf, legal actions will be taken.
> 
> Regards,
> 
> Khaled Omar


From nobody Tue May 23 02:29:25 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 4B7B2129A8E; Tue, 23 May 2017 02:29:20 -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: draft-ietf-curdle-cms-ecdh-new-curves.all@ietf.org, curdle@ietf.org, ietf@ietf.org
Subject: Opsdir last call review of draft-ietf-curdle-cms-ecdh-new-curves-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149553176028.29418.18414274218431090509@ietfa.amsl.com>
Date: Tue, 23 May 2017 02:29:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uOKxhr5fG2uEQBMvuImRyZ87XGg>
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, 23 May 2017 09:29:20 -0000

Reviewer: Stefan Winter
Review result: Has Nits

Nits: 

* 2.1 starts with "...  based on a one-way hash function described in
ANS X9.63 [X963]." s/ANS/ANSI/

* Chapter 7 defines six OIDs (secg-scheme 11 1...3 and smime-alg
TBD1...3) and also includes the base OIDs under which these new OIDs
are attached (secg-scheme and smime-alg). Those two are not defined in
this document, but the text in chapter 7 suggests so.
Maybe it would be a bit clearer if the text stated explicitly which of
the OIDs in the chapter are NEW, and which ones already exist and are
provided for reference/context.



From nobody Tue May 23 02:47:37 2017
Return-Path: <julian.reschke@gmx.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 7F7CA129420; Tue, 23 May 2017 02:47:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.1
X-Spam-Level: 
X-Spam-Status: No, score=0.1 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  FREEMAIL_FROM=0.001, 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 Ez-lLF0WJO1l; Tue, 23 May 2017 02:47:28 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 AEE8A127286; Tue, 23 May 2017 02:47:27 -0700 (PDT)
Received: from [192.168.1.57] ([217.91.35.233]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MS5xC-1dOlXi2WjK-00TCN0; Tue, 23 May 2017 11:47:08 +0200
Subject: Re: [art] ART Area Review for draft-ietf-calext-caldav-attachments-02
To: Ken Murchison <murch@andrew.cmu.edu>, IETF Discussion <ietf@ietf.org>, art@ietf.org
References: <c04f39e2-79d2-ab9d-59ab-26e51d7ab5fc@gmx.de> <81613220-989b-ca78-fe56-0ac7b19e7ce6@andrew.cmu.edu> <b2a4924d-c7c9-b40b-484f-9fab48bfe5de@gmx.de> <a603f3de-2d96-6f86-e0c3-3e0a4884a185@andrew.cmu.edu> <7bcfecea-3a89-978c-9e1b-edf9aac5dd44@gmx.de> <07f64bc5-13f6-62a0-3c04-91c780f69672@andrew.cmu.edu>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <f7a17043-3738-1157-91e5-a9f863d2aa17@gmx.de>
Date: Tue, 23 May 2017 11:47:04 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <07f64bc5-13f6-62a0-3c04-91c780f69672@andrew.cmu.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:7KNd+yZ1YD/PcZza3Y88SmR+4MYllZbvuDHXsZQ4i2l/3MmcyJw bEcxTvLFaSZQwCKKpRa0ZnjE+LNWcMTv/RwWC1To4vIUgRr3fVpEZE67QaXTMEvfchk+dqW mL8vu2AjWP+x7uVHHazvxVF/F/zHucSWU4V2FU71GYiRhHHX5MPIkbW7x7PIfMbEWRRyf5d hvRDP7zaZ/XSJXbSYw8xQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:pDH/97rXxHQ=:huxfk6W9VCczUBE8q/RuRs g9oBuJpqBNRso3Wi/5gLYF24srbOdKuS3k80AckA48iP6saSdYVX4R4rQIUeUfJdvnK0wlw/1 lAblSSmQFo1WfM8QDVoUd+bMOcEC+8PGTgqtAxxnoYx/DNsHB/E+CnfqxvwHJ7ZSUtJ6sTug4 EKsQgV+/TTpBY8+CzRRhgjoyLRr7PL1m2Bv1iYdoW2PWxth/WFvEbNFMJpZy8okAbQqnTm5wH JIp0sJckXOP1ZGF6DwYzDiTCvoQgdV37M4zGjdtLzrXLj815Cfy5kMdAz+lYnkwjhORC/uHSN nJ94NyY++RxSBhhpUOBIBFh1HvMh/j9QGhY1nLBKFPwPJV4dwHG5sE7zCfOTgoMW9yWhRYASR kMLw2QO51ZRjx74AswEwlQIZK9R4Kp4aE9OQRz93hyGG6O3dlVRp0omztpMCe+K0IHTTx5xRO lKjbbAo4VjiqgRwmPXSfr13vxHFQl0mUIDpDDHW0oAgpTMOpvPzpP4fEzHtS+UNsLmstM4oTP yL8qdnNcc8sf5JBWNv+bHVdC7Qcpn/+Vq0TKaz2sIClUTwm4jOIWD9MY3z0GZNRBkmc5P0UgO B5QzrVPlBEJywuP/g6ixpErilbQms3mOC/Sylun8Ra6OC6Jvy9STZaC35J3cSDziJtAgLURos 7K5YJkiJDw8C7ELHIm373gLR4eKiaXqeY0nMDv4FEctf3NDr9OU8sgjB+t7ew2gYzPl8nZT1n VPDyZ08PyQzotX1/IzgA0LwcthrZje1nn5Mpyic2mcb6uQrJuC58E4ErR0tU9TOgXoD89hHfQ fjNuWXq
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1lx23UuEy11ahEaEWBUR0leVC8A>
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, 23 May 2017 09:47:29 -0000

On 2017-05-22 20:59, Ken Murchison wrote:
> ...
> The issue here is that a single calendar resource may contain multiple 
> events (recurring event with overrides) and a particular attachment may 
> be associated with more than one instance of that event.  For this 
> reason, we felt it best to use the calendar resource as the gateway to 
> the attachments, thus allowing manipulating multiple instances of an 
> attachment in a single round-trip.  Also, by preventing clients from 
> manipulating attachments directly, a CalDAV server isn't forced to alter 
> all calendar resources associated with a particular attachment.
> ...

But that's a detail of how the server implements these resources. I 
still do not understand how the choice of HTTP methods and URI formats 
is relevant for that.

> We also have a fairly large number of deployed implementations which we 
> do not want to make non-compliant by substantially modifying the 
> protocol.  At this point, specifying the use of HTTP methods other than 
> POST would indeed make existing implementations non-compliant.

Yes.

> We would definitely like to make this protocol conform to current HTTP 
> practice where possible, and would also document where we have strayed 
> from existing practice if required to do so.  Do you think we can come 
> to some kind of consensus that meets these goals?

I'm just offering my feedback from an HTTP and web architecture point of 
view. And from that angle, the protocol as specified violates multiple 
best practices, and I would recommend not to publish it on the standards 
track. "Informational" might work, if this is indeed what's implemented, 
and implementers are unwilling to put more work into it...

Best regards, Julian





From nobody Tue May 23 04:55:12 2017
Return-Path: <eng.khaled.omar@hotmail.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 11E03129AEE for <ietf@ietfa.amsl.com>; Tue, 23 May 2017 04:55:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level: 
X-Spam-Status: No, score=-1.146 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XvAavl3g760N for <ietf@ietfa.amsl.com>; Tue, 23 May 2017 04:55:09 -0700 (PDT)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-oln040092072062.outbound.protection.outlook.com [40.92.72.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DD42129AF3 for <ietf@ietf.org>; Tue, 23 May 2017 04:55:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=460YveuGkNJ2IS4w8zfO/tpT54t/oNLfObyNK5i9+uo=; b=nrboIgWDUiGPgmVb5zjPT1WddLVkIZaDJwcqYI2ZPiHf2VRJdZJ/EMJaCMbVthcNFwWU0gG1f+UmhtAuaPPt01Q54xvVyF+Q5sgkJWpRFpjfAkF+ASLV7ooMI4rAJm6lvETK8VpTkbf+r5uito8pNeORxXs0MdpLKj9OgU2LFC633dUsfq3XiMC5sgjSFDld1YCINy9KZVRJWPFG1uhBtuAPh17/h2+4OodQPbo45fnJ2nLYUPR+H+YUzlHl/JmrD+LJIJY38GvpQa/lfDCMW5oyEmc4tRYiYKgyGupq4pQkQ622WC5cz1liNfN2LSmNUGH5YoqEf5dY3xYeS7IVjQ==
Received: from VE1EUR03FT046.eop-EUR03.prod.protection.outlook.com (10.152.18.57) by VE1EUR03HT110.eop-EUR03.prod.protection.outlook.com (10.152.19.189) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1075.5; Tue, 23 May 2017 11:55:07 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.18.56) by VE1EUR03FT046.mail.protection.outlook.com (10.152.19.226) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1075.5 via Frontend Transport; Tue, 23 May 2017 11:55:07 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::a819:bed0:ee53:c0c3]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::a819:bed0:ee53:c0c3%18]) with mapi id 15.01.1101.019; Tue, 23 May 2017 11:55:06 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
CC: ietf <ietf@ietf.org>
Subject: Re: IPv10, KRP, and RRP IDs Removal.
Thread-Topic: IPv10, KRP, and RRP IDs Removal.
Thread-Index: AdLTTNVDoZlTmip5SbKkUmpfy2efXw==
Date: Tue, 23 May 2017 11:55:06 +0000
Message-ID: <AM4PR0401MB2241983F0DC82EE15E67797ABDF90@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <20170523050000.GW39245@kduck.kaduk.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: mit.edu; dkim=none (message not signed) header.d=none;mit.edu; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:3FD1DA84F7EB6CDD203E6FD88639C6947CD8F14B274BF2553522650ECE08550B; UpperCasedChecksum:D4A41DFC57849C0D2BF278FB350443A5E985C775D86CE2B2F0BE9849C578A121; SizeAsReceived:7988; Count:42
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VE1EUR03HT110; 5:z9KoxP5qICI2HlJmALg6kbs50JTB6Gg2SOZ5ojIPaTbJKw8riOH5aLgxOVO8ZBAsrfincxgxi6hqQZ9Nu7IoN6mJoZkJbzODbbcdXSx6j6u+OzB/VGm2ZkjDe6qkt6vWc8YGJ6NwBxzmYD8bB9hjhQ==; 24:uv6Rxci2+18e9oiI1prPfG+IbeTRmGa2dNIu0Isuu9sD31GGKUx5PrmN4+qZ5+9iH8wlYOGnhPXinudPl+RnGXx+hNRBqvhVKj+4XuqpAAQ=; 7:OkltBjE09BMraang4JKN7sAggFcdVW8Zh2wiykJyD3GBPIG3tAONXu1MSCD33FIh/XvESqtjNhCpSsxTaycgvhnmmF1VNUrwsOpFqER+YpDC24hk8F5JZZTcKuG2QT0+IwAZX4txCS8BMmCDoiKtbmdh4ehwLUwqqfaPCmUolL+rpFJlxnklAQJ3xbJiGXLr+2kKgYLi5CUZXwszwB8c2J5ZcBp6EZ/ZEsP2GuJZVeRrCK2pmBAlUw50cUYxs9nowILtDHfidnrEN/AqbcjKk9TaQEMGmD9fC+uo6GfVWjCDf9jdQsA/qvf3pqxCr7zE
x-incomingheadercount: 42
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:VE1EUR03HT110; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 88cf3d43-d0c8-4ade-c8c2-08d4a1d28d66
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:VE1EUR03HT110; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:VE1EUR03HT110; BCL:0; PCL:0; RULEID:; SRVR:VE1EUR03HT110; 
x-forefront-prvs: 0316567485
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB2241983F0DC82EE15E67797ABDF90AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 May 2017 11:55:06.7321 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1EUR03HT110
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PON35nSWigiMtIk8NWeozdENRWw>
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, 23 May 2017 11:55:11 -0000

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

SSBkb24ndCBjYXJlLCBvbmNlIElEcyB3aWxsIGJlIHJlbW92ZWQsIEkgd2lsbCB1bnN1YnNjcmli
ZSBhbmQgd2lsbCBub3Qgc3VibWl0IGFueXRoaW5nIGhlcmUgYWdhaW4uDQoNCg0KLS0tLS0tLS0g
T3JpZ2luYWwgTWVzc2FnZSAtLS0tLS0tLQ0KU3ViamVjdDogUmU6IElQdjEwLCBLUlAsIGFuZCBS
UlAgSURzIFJlbW92YWwuDQpGcm9tOiBCZW5qYW1pbiBLYWR1aw0KVG86IEtoYWxlZCBPbWFyICxp
ZXRmLXNlY3JldGFyaWF0QGlldGYub3JnDQpDQzogaWV0ZkBpZXRmLm9yZw0KDQoNCkRlYXIgS2hh
bGVkLA0KDQpTcGVha2luZyBhcyBzZXJnZWFudC1hdC1hcm1zLA0KDQpZb3Ugd2VyZSByZWNlbnRs
eSBwbGFjZWQgdW5kZXIgYSB0ZW1wb3Jhcnkgc3VzcGVuc2lvbiBvZiBwb3N0aW5nDQpyaWdodHMg
dG8gdGhpcyBsaXN0IFsxXSwgYSBtZXNzYWdlIHRoYXQgc3VnZ2VzdGVkIHlvdSB1c2UgdGhhdA0K
dGltZSB0byByZWFkIGFib3V0IHRoZSBwcm9jZXNzIG9mIHN1Ym1pdHRpbmcgYW5kIGRpc2N1c3Np
bmcgZHJhZnRzDQphdCB0aGUgSUVURi4gSXQgc2VlbXMgdGhhdCB5b3UgaGF2ZSBub3QgdGFrZW4g
YWR2YW50YWdlIG9mIHRoZQ0Kb3Bwb3J0dW5pdHkgdG8gZG8gc28sIGFzIHlvdSBwZXJzaXN0IGlu
IHVzaW5nIGFuIG92ZXJseSBicm9hZA0KcmVjaXBpZW50IGxpc3Qgd2hlbiBjb3JyZXNwb25kaW5n
IHdpdGggdGhlIGFkZHJlc3MgdXNlZCBmb3IgZHJhZnQNCnN1Ym1pc3Npb24sIGFuZCBhcmUgYXR0
ZW1wdGluZyB0byBibG9jayBkaXNjdXNzaW9uIG9mIHRlY2huaWNhbA0KaXNzdWVzIG9uIGEgbGlz
dCByZXNlcnZlZCBmb3Igc3VjaCBkaXNjdXNzaW9ucyBvZiB0ZWNobmljYWwgaXNzdWVzLg0KDQpX
aXRoIG15IGF1dGhvcml0eSBhcyBzZXJnZWFudC1hdC1hcm1zIHVuZGVyIFJGQyAzMDA0LCBJIGFt
IGZvcmNlZCB0bw0KcmVxdWVzdCB0aGF0IHRoZSBzZWNyZXRhcmlhdCBhcHBseSBhbiBhZGRpdGlv
bmFsIHJlc3RyaWN0aW9uIG9mIHlvdXINCnBvc3RpbmcgcmlnaHRzIGZvciB0aGUgcGVyaW9kIG9m
IDYwIGRheXMsIHN0YXJ0aW5nIGltbWVkaWF0ZWx5Lg0KDQpJZiB5b3UgZG8gZGVjaWRlIHRvIGJy
aW5nIG5ldyB3b3JrIHRvIHRoZSBJRVRGIGluIHRoZSBmdXR1cmUsIHdlDQp3aWxsIGV4cGVjdCB0
aGF0IHlvdSBhbmQga2VlcCB0cmFmZmljIG9uIHRoZSBJRVRGIG1haWxpbmcNCmxpc3RzIGZvY3Vz
ZWQgb24gZGlzY3Vzc2lvbiBvZiB0ZWNobmljYWwgaXNzdWVzIGFuZCBpbiB0aGUNCmFwcHJvcHJp
YXRlIHZlbnVlKHMpLg0KDQotQmVuIEthZHVrDQoNClsxXSBodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsLWFyY2hpdmUvd2ViL2lldGYvY3VycmVudC9tc2cxMDI3NDMuaHRtbA0KDQpPbiBNb24sIE1h
eSAyMiwgMjAxNyBhdCAxMDo1NTowMlBNICswMDAwLCBLaGFsZWQgT21hciB3cm90ZToNCj4gSGkg
SmFzbWluZSwNCj4NCj4gQXMgSSdtIHRoZSBvbmx5IGF1dGhvciBvZiB0aGUgZm9sbG93aW5nIElE
czoNCj4NCj4NCj4gMSkgSW50ZXJuZXQgUHJvdG9jb2wgdmVyc2lvbiAxMCAoSVB2MTApOiBodHRw
czovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1vbWFyLWlwdjEwLw0KPg0KPg0KPiAy
KSBLSEFMRUQgUm91dGluZyBQcm90b2NvbCAoS1JQKTogaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRm
Lm9yZy9kb2MvZHJhZnQtb21hci1rcnAvDQo+DQo+DQo+IDMpIFJlZ2lvbmFsIFJvdXRpbmcgUHJv
dG9jb2wgKFJSUCk6IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LW9tYXIt
cnJwLw0KPg0KPg0KPiBQbGVhc2UgcmVtb3ZlIHRoZW0gYWxsIGZyb20gdGhlIGlldGYgZGF0YWJh
c2Ugb3IgcmVwb3NpdG9yeS4NCj4NCj4gSWYgdGhlIGlkZWFzIGV4cGxhaW5lZCBvbiB0aGVzZSBk
cmFmdHMgd2lsbCBiZSB1c2VkLCBkaXNjdXNzZWQgb3IgcHVibGlzaGVkIGJ5IHRoZSBpZXRmLCBs
ZWdhbCBhY3Rpb25zIHdpbGwgYmUgdGFrZW4uDQo+DQo+IFJlZ2FyZHMsDQo+DQo+IEtoYWxlZCBP
bWFyDQo=

--_000_AM4PR0401MB2241983F0DC82EE15E67797ABDF90AM4PR0401MB2241_
Content-Type: text/html; charset="utf-8"
Content-ID: <57CFEA386CF9074EAEE7ED90BB33E8BE@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KSSBkb24ndCBjYXJl
LCBvbmNlIElEcyB3aWxsIGJlIHJlbW92ZWQsIEkgd2lsbCB1bnN1YnNjcmliZSBhbmQgd2lsbCBu
b3Qgc3VibWl0IGFueXRoaW5nIGhlcmUgYWdhaW4uDQo8ZGl2IGNsYXNzPSJxdW90ZSIgc3R5bGU9
ImxpbmUtaGVpZ2h0OiAxLjUiPjxicj4NCjxicj4NCi0tLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2Ug
LS0tLS0tLS08YnI+DQpTdWJqZWN0OiBSZTogSVB2MTAsIEtSUCwgYW5kIFJSUCBJRHMgUmVtb3Zh
bC48YnI+DQpGcm9tOiBCZW5qYW1pbiBLYWR1ayA8a2FkdWtAbWl0LmVkdT48YnI+DQpUbzogS2hh
bGVkIE9tYXIgPGVuZy5raGFsZWQub21hckBob3RtYWlsLmNvbT4saWV0Zi1zZWNyZXRhcmlhdEBp
ZXRmLm9yZzxicj4NCkNDOiBpZXRmQGlldGYub3JnPGJyPg0KPGJyPg0KPGJyIHR5cGU9ImF0dHJp
YnV0aW9uIj4NCjxibG9ja3F1b3RlIGNsYXNzPSJxdW90ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAu
OGV4O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPg0KRGVhciBL
aGFsZWQsPGJyPg0KPGJyPg0KU3BlYWtpbmcgYXMgc2VyZ2VhbnQtYXQtYXJtcyw8YnI+DQo8YnI+
DQpZb3Ugd2VyZSByZWNlbnRseSBwbGFjZWQgdW5kZXIgYSB0ZW1wb3Jhcnkgc3VzcGVuc2lvbiBv
ZiBwb3N0aW5nPGJyPg0KcmlnaHRzIHRvIHRoaXMgbGlzdCBbMV0sIGEgbWVzc2FnZSB0aGF0IHN1
Z2dlc3RlZCB5b3UgdXNlIHRoYXQ8YnI+DQp0aW1lIHRvIHJlYWQgYWJvdXQgdGhlIHByb2Nlc3Mg
b2Ygc3VibWl0dGluZyBhbmQgZGlzY3Vzc2luZyBkcmFmdHM8YnI+DQphdCB0aGUgSUVURi4gSXQg
c2VlbXMgdGhhdCB5b3UgaGF2ZSBub3QgdGFrZW4gYWR2YW50YWdlIG9mIHRoZTxicj4NCm9wcG9y
dHVuaXR5IHRvIGRvIHNvLCBhcyB5b3UgcGVyc2lzdCBpbiB1c2luZyBhbiBvdmVybHkgYnJvYWQ8
YnI+DQpyZWNpcGllbnQgbGlzdCB3aGVuIGNvcnJlc3BvbmRpbmcgd2l0aCB0aGUgYWRkcmVzcyB1
c2VkIGZvciBkcmFmdDxicj4NCnN1Ym1pc3Npb24sIGFuZCBhcmUgYXR0ZW1wdGluZyB0byBibG9j
ayBkaXNjdXNzaW9uIG9mIHRlY2huaWNhbDxicj4NCmlzc3VlcyBvbiBhIGxpc3QgcmVzZXJ2ZWQg
Zm9yIHN1Y2ggZGlzY3Vzc2lvbnMgb2YgdGVjaG5pY2FsIGlzc3Vlcy48YnI+DQo8YnI+DQpXaXRo
IG15IGF1dGhvcml0eSBhcyBzZXJnZWFudC1hdC1hcm1zIHVuZGVyIFJGQyAzMDA0LCBJIGFtIGZv
cmNlZCB0bzxicj4NCnJlcXVlc3QgdGhhdCB0aGUgc2VjcmV0YXJpYXQgYXBwbHkgYW4gYWRkaXRp
b25hbCByZXN0cmljdGlvbiBvZiB5b3VyPGJyPg0KcG9zdGluZyByaWdodHMgZm9yIHRoZSBwZXJp
b2Qgb2YgNjAgZGF5cywgc3RhcnRpbmcgaW1tZWRpYXRlbHkuPGJyPg0KPGJyPg0KSWYgeW91IGRv
IGRlY2lkZSB0byBicmluZyBuZXcgd29yayB0byB0aGUgSUVURiBpbiB0aGUgZnV0dXJlLCB3ZTxi
cj4NCndpbGwgZXhwZWN0IHRoYXQgeW91IGFuZCBrZWVwIHRyYWZmaWMgb24gdGhlIElFVEYgbWFp
bGluZzxicj4NCmxpc3RzIGZvY3VzZWQgb24gZGlzY3Vzc2lvbiBvZiB0ZWNobmljYWwgaXNzdWVz
IGFuZCBpbiB0aGU8YnI+DQphcHByb3ByaWF0ZSB2ZW51ZShzKS48YnI+DQo8YnI+DQotQmVuIEth
ZHVrPGJyPg0KPGJyPg0KWzFdIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIv
aWV0Zi9jdXJyZW50L21zZzEwMjc0My5odG1sPGJyPg0KPGJyPg0KT24gTW9uLCBNYXkgMjIsIDIw
MTcgYXQgMTA6NTU6MDJQTSAmIzQzOzAwMDAsIEtoYWxlZCBPbWFyIHdyb3RlOjxicj4NCiZndDsg
SGkgSmFzbWluZSw8YnI+DQomZ3Q7IDxicj4NCiZndDsgQXMgSSdtIHRoZSBvbmx5IGF1dGhvciBv
ZiB0aGUgZm9sbG93aW5nIElEczo8YnI+DQomZ3Q7IDxicj4NCiZndDsgPGJyPg0KJmd0OyAxKSBJ
bnRlcm5ldCBQcm90b2NvbCB2ZXJzaW9uIDEwIChJUHYxMCk6IGh0dHBzOi8vZGF0YXRyYWNrZXIu
aWV0Zi5vcmcvZG9jL2RyYWZ0LW9tYXItaXB2MTAvPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDxicj4N
CiZndDsgMikgS0hBTEVEIFJvdXRpbmcgUHJvdG9jb2wgKEtSUCk6IGh0dHBzOi8vZGF0YXRyYWNr
ZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LW9tYXIta3JwLzxicj4NCiZndDsgPGJyPg0KJmd0OyA8YnI+
DQomZ3Q7IDMpIFJlZ2lvbmFsIFJvdXRpbmcgUHJvdG9jb2wgKFJSUCk6IGh0dHBzOi8vZGF0YXRy
YWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LW9tYXItcnJwLzxicj4NCiZndDsgPGJyPg0KJmd0OyA8
YnI+DQomZ3Q7IFBsZWFzZSByZW1vdmUgdGhlbSBhbGwgZnJvbSB0aGUgaWV0ZiBkYXRhYmFzZSBv
ciByZXBvc2l0b3J5Ljxicj4NCiZndDsgPGJyPg0KJmd0OyBJZiB0aGUgaWRlYXMgZXhwbGFpbmVk
IG9uIHRoZXNlIGRyYWZ0cyB3aWxsIGJlIHVzZWQsIGRpc2N1c3NlZCBvciBwdWJsaXNoZWQgYnkg
dGhlIGlldGYsIGxlZ2FsIGFjdGlvbnMgd2lsbCBiZSB0YWtlbi48YnI+DQomZ3Q7IDxicj4NCiZn
dDsgUmVnYXJkcyw8YnI+DQomZ3Q7IDxicj4NCiZndDsgS2hhbGVkIE9tYXI8YnI+DQo8L2Jsb2Nr
cXVvdGU+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_AM4PR0401MB2241983F0DC82EE15E67797ABDF90AM4PR0401MB2241_--


From nobody Tue May 23 05:43:33 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 E2D26129B31 for <ietf@ietfa.amsl.com>; Tue, 23 May 2017 05:43:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.782
X-Spam-Level: *
X-Spam-Status: No, score=1.782 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 oT26mDtMUbtq for <ietf@ietfa.amsl.com>; Tue, 23 May 2017 05:43:30 -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 DC941129B29 for <ietf@ietf.org>; Tue, 23 May 2017 05:43:21 -0700 (PDT)
Received: from shogunx (helo=localhost) by sleekfreak.ath.cx with local-esmtp (Exim 4.89) (envelope-from <shogunx@sleekfreak.ath.cx>) id 1dD99f-0002D1-8N; Tue, 23 May 2017 08:43:15 -0400
Date: Tue, 23 May 2017 08:43:14 -0400 (EDT)
From: shogunx@sleekfreak.ath.cx
To: Khaled Omar <eng.khaled.omar@hotmail.com>
cc: Benjamin Kaduk <kaduk@mit.edu>, ietf <ietf@ietf.org>
Subject: Re: IPv10, KRP, and RRP IDs Removal.
In-Reply-To: <AM4PR0401MB2241983F0DC82EE15E67797ABDF90@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Message-ID: <alpine.DEB.2.10.1705230842420.6571@sleekfreak.ath.cx>
References: <20170523050000.GW39245@kduck.kaduk.org> <AM4PR0401MB2241983F0DC82EE15E67797ABDF90@AM4PR0401MB2241.eurprd04.prod.outlook.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/tLz2ILUyaL3-zKqU_lkIxP0hlk0>
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, 23 May 2017 12:43:32 -0000

note well... i lol'd.

On Tue, 23 May 2017, Khaled Omar wrote:

> I don't care, once IDs will be removed, I will unsubscribe and will not
> submit anything here again.
> 
> -------- Original Message --------
> Subject: Re: IPv10, KRP, and RRP IDs Removal.
> From: Benjamin Kaduk
> To: Khaled Omar ,ietf-secretariat@ietf.org
> CC: ietf@ietf.org
> 
>
>       Dear Khaled,
>
>       Speaking as sergeant-at-arms,
>
>       You were recently placed under a temporary suspension of posting
>       rights to this list [1], a message that suggested you use that
>       time to read about the process of submitting and discussing
>       drafts
>       at the IETF. It seems that you have not taken advantage of the
>       opportunity to do so, as you persist in using an overly broad
>       recipient list when corresponding with the address used for
>       draft
>       submission, and are attempting to block discussion of technical
>       issues on a list reserved for such discussions of technical
>       issues.
>
>       With my authority as sergeant-at-arms under RFC 3004, I am
>       forced to
>       request that the secretariat apply an additional restriction of
>       your
>       posting rights for the period of 60 days, starting immediately.
>
>       If you do decide to bring new work to the IETF in the future, we
>       will expect that you and keep traffic on the IETF mailing
>       lists focused on discussion of technical issues and in the
>       appropriate venue(s).
>
>       -Ben Kaduk
>
>       [1]
>       https://www.ietf.org/mail-archive/web/ietf/current/msg102743.html
>
>       On Mon, May 22, 2017 at 10:55:02PM +0000, Khaled Omar wrote:
>       > Hi Jasmine,
>       >
>       > As I'm the only author of the following IDs:
>       >
>       >
>       > 1) Internet Protocol version 10 (IPv10):
>       https://datatracker.ietf.org/doc/draft-omar-ipv10/
>       >
>       >
>       > 2) KHALED Routing Protocol (KRP):
>       https://datatracker.ietf.org/doc/draft-omar-krp/
>       >
>       >
>       > 3) Regional Routing Protocol (RRP):
>       https://datatracker.ietf.org/doc/draft-omar-rrp/
>       >
>       >
>       > Please remove them all from the ietf database or repository.
>       >
>       > If the ideas explained on these drafts will be used, discussed
>       or published by the ietf, legal actions will be taken.
>       >
>       > Regards,
>       >
>       > Khaled Omar
> 
> 
>


From nobody Tue May 23 05:43:40 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 A287B129B34 for <ietf@ietfa.amsl.com>; Tue, 23 May 2017 05:43:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.701
X-Spam-Level: 
X-Spam-Status: No, score=-4.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, 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 N-jYIwpyvF0V for <ietf@ietfa.amsl.com>; Tue, 23 May 2017 05:43:31 -0700 (PDT)
Received: from smtp86.iad3a.emailsrvr.com (smtp86.iad3a.emailsrvr.com [173.203.187.86]) (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 7E92C129B2F for <ietf@ietf.org>; Tue, 23 May 2017 05:43:22 -0700 (PDT)
Received: from smtp35.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp35.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 72CFF591E; Tue, 23 May 2017 08:43:17 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp35.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 886C85BFD;  Tue, 23 May 2017 08:43:16 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [192.168.4.119] ([UNAVAILABLE]. [128.107.241.165]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.12); Tue, 23 May 2017 08:43:17 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: ART last call review of draft-ietf-nfsv4-xattrs-05.txt
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <149360572366.9820.5858645625519856278.idtracker@ietfa.amsl.com>
Date: Tue, 23 May 2017 06:43:15 -0600
Cc: nfsv4-chairs@ietf.org, spencer.shepler@gmail.com, nfsv4@ietf.org, draft-ietf-nfsv4-xattrs@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <3DC61021-5B5E-4C0A-8E99-09F3BCD8F76E@iii.ca>
References: <149360572366.9820.5858645625519856278.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BeFitr3tu-ZHh7EG8R7I4fAO0Vg>
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, 23 May 2017 12:43:33 -0000

This document is easy to understand and I did not see any issues.=20

As a side note, I really wish the IETF had a better way to include code =
in specification than how it is done in this draft.=20


> On Apr 30, 2017, at 8:28 PM, The IESG <iesg-secretary@ietf.org> wrote:
>=20
>=20
> The IESG has received a request from the Network File System Version 4 =
WG
> (nfsv4) to consider the following document:
> - 'File System Extended Attributes in NFSv4'
>  <draft-ietf-nfsv4-xattrs-05.txt> as Proposed Standard
>=20


From nobody Tue May 23 06:28:29 2017
Return-Path: <eng.khaled.omar@hotmail.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 46297129B49 for <ietf@ietfa.amsl.com>; Tue, 23 May 2017 06:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.147
X-Spam-Level: 
X-Spam-Status: No, score=-1.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CPsrFA69vWRY for <ietf@ietfa.amsl.com>; Tue, 23 May 2017 06:28:27 -0700 (PDT)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-oln040092072109.outbound.protection.outlook.com [40.92.72.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 417A7129B2B for <ietf@ietf.org>; Tue, 23 May 2017 06:28:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=vduB6G1YrqqoSnd5KW0L4HHxfiorv7jsIL/dNIDaOkc=; b=kFuih/1E2JUv/5lSSyYNI4NsjvRf1syQrxVOW7lpSw0mmFdTVUgb7xqyncPlJgAZLsZLhWbouJEiopnbqoRUR1GQIA/QnHZJ/5UGJva5sIt5Oo1OOTOHliA9OWLl7hmVkqRqq2RsJqkYNwX/vPTaZLOCU0DL0rS3HGvM1PF8YcYvXy/lHsR4u3HwUZXISj6ynrIelDfWjI2A3jJeYaE4xsbnG61GxFeel3dINQTymj12j2XSLnMRNlrCqdYBFFLhG6h7byHbvk8Or8SjBEoGZv2+r4l59HlIBXxTN92wjO0IqZRivtjuaAIbJdTUCkE52qp62n6lbPp+3neBcfPAGw==
Received: from DB5EUR03FT022.eop-EUR03.prod.protection.outlook.com (10.152.20.53) by DB5EUR03HT239.eop-EUR03.prod.protection.outlook.com (10.152.21.43) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1075.5; Tue, 23 May 2017 13:28:24 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.20.54) by DB5EUR03FT022.mail.protection.outlook.com (10.152.20.171) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1075.5 via Frontend Transport; Tue, 23 May 2017 13:28:24 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::a819:bed0:ee53:c0c3]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::a819:bed0:ee53:c0c3%18]) with mapi id 15.01.1101.019; Tue, 23 May 2017 13:28:24 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: "shogunx@sleekfreak.ath.cx" <shogunx@sleekfreak.ath.cx>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: IPv10, KRP, and RRP IDs Removal.
Thread-Topic: IPv10, KRP, and RRP IDs Removal.
Thread-Index: AdLTTNVDoZlTmip5SbKkUmpfy2efXwAdU9wAAAGE1CA=
Date: Tue, 23 May 2017 13:28:23 +0000
Message-ID: <AM4PR0401MB22415FCBDFC02D4C7E4EE61FBDF90@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <20170523050000.GW39245@kduck.kaduk.org> <AM4PR0401MB2241983F0DC82EE15E67797ABDF90@AM4PR0401MB2241.eurprd04.prod.outlook.com> <alpine.DEB.2.10.1705230842420.6571@sleekfreak.ath.cx>
In-Reply-To: <alpine.DEB.2.10.1705230842420.6571@sleekfreak.ath.cx>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: sleekfreak.ath.cx; dkim=none (message not signed) header.d=none;sleekfreak.ath.cx; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:F48708114F6C6C08C2B957ED1B0A4E81F2ED05AFD819AE0F6BC2F404065237EE; UpperCasedChecksum:43A2D2000AD4E91A25DA633BE7B0EC7A86E6F706DC499E4EC1F3AD7A3940AC2B; SizeAsReceived:8379; Count:45
x-tmn: [l5tRtBpbDzzBPrSO/x3OEsvLx4W1ExgQ]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB5EUR03HT239; 5:aCFQvCh+ZXkYRMOOBeCdjOpAl4AKGrcyhTfW4mejBO0j48caT8aAJHjaQJzTQ6ABORYm80yYU+9GfRw/cq1eBniEvJok/Uqxp/g/j2/wYhOW0GyjYFrqUpcXgwWvSTn6BfRrh/tbj0lR3GxNfk6ubg==; 24:dNJQmIKbPS7kRDqPRihxyXa/1qw3XNP6qrXWILL1TmbjJ5LJM6L7f/I0SgpfFsF7Oltm7vUNHunIAX7hvzlNnGktqpRCty/O1S76P605CMY=; 7:y7JBmBtpYzqwIR9LWJFEKrTSkDBCRmsXh+5Iqo1dEzWrvzAIwDnaE0zks9xdrJT0CY3KW9WUB4hJkMgljfgrN74OeQAa+ZWAaTigImoG6AyUFuLVaOhfKk63tPC4S2Y4j0RgCknHrIb+J+dUafyFnDOa0VvQi+NcAphqXLvPCANGfZ+1p/4qnMXULnOaL47nv0uQwjm7GMAMwaAUi0TgvY8KrrYFpu6FR249KfsSK110Q340uXlHJmcp2HYeWN37VKRVrKAJHg68+n28nJWu/h32GoxqDkrMF7Loq8FvmDh0epIVnT7q6N98kF90ww+P
x-incomingheadercount: 45
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:DB5EUR03HT239; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 10ebd1c4-3b09-43c7-4019-08d4a1df9684
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:DB5EUR03HT239; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:DB5EUR03HT239; BCL:0; PCL:0; RULEID:; SRVR:DB5EUR03HT239; 
x-forefront-prvs: 0316567485
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 May 2017 13:28:23.9269 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5EUR03HT239
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/H-CSmvOYApUTjENxOaHKwKu9XUM>
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, 23 May 2017 13:28:28 -0000

This is a serious official request, if it means nothing for you, stop reply=
ing.

-----Original Message-----
From: shogunx@sleekfreak.ath.cx [mailto:shogunx@sleekfreak.ath.cx]=20
Sent: Tuesday, May 23, 2017 2:43 PM
To: Khaled Omar
Cc: Benjamin Kaduk; ietf
Subject: Re: IPv10, KRP, and RRP IDs Removal.

note well... i lol'd.

On Tue, 23 May 2017, Khaled Omar wrote:

> I don't care, once IDs will be removed, I will unsubscribe and will=20
> not submit anything here again.
>=20
> -------- Original Message --------
> Subject: Re: IPv10, KRP, and RRP IDs Removal.
> From: Benjamin Kaduk
> To: Khaled Omar ,ietf-secretariat@ietf.org
> CC: ietf@ietf.org
>=20
>
>       Dear Khaled,
>
>       Speaking as sergeant-at-arms,
>
>       You were recently placed under a temporary suspension of posting
>       rights to this list [1], a message that suggested you use that
>       time to read about the process of submitting and discussing
>       drafts
>       at the IETF. It seems that you have not taken advantage of the
>       opportunity to do so, as you persist in using an overly broad
>       recipient list when corresponding with the address used for
>       draft
>       submission, and are attempting to block discussion of technical
>       issues on a list reserved for such discussions of technical
>       issues.
>
>       With my authority as sergeant-at-arms under RFC 3004, I am
>       forced to
>       request that the secretariat apply an additional restriction of
>       your
>       posting rights for the period of 60 days, starting immediately.
>
>       If you do decide to bring new work to the IETF in the future, we
>       will expect that you and keep traffic on the IETF mailing
>       lists focused on discussion of technical issues and in the
>       appropriate venue(s).
>
>       -Ben Kaduk
>
>       [1]
>      =20
> https://www.ietf.org/mail-archive/web/ietf/current/msg102743.html
>
>       On Mon, May 22, 2017 at 10:55:02PM +0000, Khaled Omar wrote:
>       > Hi Jasmine,
>       >
>       > As I'm the only author of the following IDs:
>       >
>       >
>       > 1) Internet Protocol version 10 (IPv10):
>       https://datatracker.ietf.org/doc/draft-omar-ipv10/
>       >
>       >
>       > 2) KHALED Routing Protocol (KRP):
>       https://datatracker.ietf.org/doc/draft-omar-krp/
>       >
>       >
>       > 3) Regional Routing Protocol (RRP):
>       https://datatracker.ietf.org/doc/draft-omar-rrp/
>       >
>       >
>       > Please remove them all from the ietf database or repository.
>       >
>       > If the ideas explained on these drafts will be used, discussed
>       or published by the ietf, legal actions will be taken.
>       >
>       > Regards,
>       >
>       > Khaled Omar
>=20
>=20
>


From nobody Tue May 23 06:45:38 2017
Return-Path: <eng.khaled.omar@hotmail.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 A99FC129B5E for <ietf@ietfa.amsl.com>; Tue, 23 May 2017 06:45:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.147
X-Spam-Level: 
X-Spam-Status: No, score=-1.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NoDP8M0U8r-Q for <ietf@ietfa.amsl.com>; Tue, 23 May 2017 06:45:35 -0700 (PDT)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-oln040092071069.outbound.protection.outlook.com [40.92.71.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E6E4129B56 for <ietf@ietf.org>; Tue, 23 May 2017 06:45:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ZOBdvFGPDuL/gNahA0GRxf4zk2egl02wtmLSA9w6Bnw=; b=f3pIsIk5wBB46ZExCuYfW8JpuvZ07/1lN1i1Hvpgoo9Ovuu9T9wWQrqfclTZ0f5IsVH1aAOIowdF1lCbAJ3SQptl0YxgS3kgaCtGXnxzTiFqHnse5OpRa0g4rtGcUZIapOHmpkVUK/bBY69MK/pGqdG77q/kHMZcuT6SWshSPFuWI1V+unRKcYh1DalO+GKftwUsT2I5GML60LddqxA+Bugc8cJctWtoCNmcQ+xqXNqX5yE+cJ7qQVKbh7xmgIO7mv79aWW+9RZJyFiHEDlRoQPLQnnI9nf3tH0DvshpyG7kjKLGagTQmVzdeBCn9uSXfPollqRpRrTM4OQddf3yew==
Received: from AM5EUR03FT025.eop-EUR03.prod.protection.outlook.com (10.152.16.56) by AM5EUR03HT065.eop-EUR03.prod.protection.outlook.com (10.152.17.68) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1075.5; Tue, 23 May 2017 13:45:32 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.16.52) by AM5EUR03FT025.mail.protection.outlook.com (10.152.16.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1075.5 via Frontend Transport; Tue, 23 May 2017 13:45:33 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::a819:bed0:ee53:c0c3]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::a819:bed0:ee53:c0c3%18]) with mapi id 15.01.1101.019; Tue, 23 May 2017 13:45:33 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: FW: IPv10, KRP, and RRP IDs Removal.
Thread-Topic: IPv10, KRP, and RRP IDs Removal.
Thread-Index: AdLTTNVDoZlTmip5SbKkUmpfy2efXwAdU9wAAAGE1CAAAFUHAAAALzVQAAAiV2A=
Date: Tue, 23 May 2017 13:45:32 +0000
Message-ID: <AM4PR0401MB22410069BDA29D0E8FB55ABCBDF90@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <20170523050000.GW39245@kduck.kaduk.org> <AM4PR0401MB2241983F0DC82EE15E67797ABDF90@AM4PR0401MB2241.eurprd04.prod.outlook.com> <alpine.DEB.2.10.1705230842420.6571@sleekfreak.ath.cx> <AM4PR0401MB22415FCBDFC02D4C7E4EE61FBDF90@AM4PR0401MB2241.eurprd04.prod.outlook.com> <alpine.LRH.2.20.999.1705230931450.10183@bofh.nohats.ca> 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:A96F5870F9A97D1EB0E8FD7ED94A31C143E843FF469B0193124ED3A50D3BB96F; UpperCasedChecksum:1CB447FB0E4C446AB9EADCF69147423F98428FCE6F346A640309FE504DF48786; SizeAsReceived:8412; Count:43
x-tmn: [N/kYiiX7H77sge/JYmmL/WVMcRYeZVRJ]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM5EUR03HT065; 5:NdPzUPbWNp51XwrPvcc43nrv91GAstnjMNq271sTadOvBv4smW48D6kz10DvdGQW7LFeHrZfUt8ZnQBNMbf3lQc69enEgElCGtB+QvAXPynVxnOGb3jINEu3g+P2RLzGlwdY7Wz+u6dP13+c+hjAmg==; 24:6emScQyHd5GWxqM6xxKnvQL6AM/tmnnZAz4SonLtsZyMuog5HmLVNIYI6ik2h6hG5s3z9jpxHwjtJNUmLpTSi5+6Or55C+Wrput0GZab3IE=; 7:zrBJw99/CAjmzIlDIQ1q97Tm81M9ohll0AWM9E3FdBmGGwXXF23t0u0pSA3vTHOUWRzy1B8rHyr+pG0psLdzXmiDj+fNvjb832SuqWgeUaarF6Zt1EZ3UPh1yOUSidYzW3PbOSxL1aWOjyP1ojYsQwpiBoaChGdbEybDxMIchxijOTIDZBFmW+dq0YMPTg6brMAxew4umWxP/jyCWW4UPX4VBmNACNs9+dY/xP8bcpSpBxsQnkxkNXY/XW6rFkCtVgn5pgZbyow5gNYhsmy+3O73y1eiFOhrTGptW1oxS8NYlZnThguc/EggwG8Q6yEj
x-incomingheadercount: 43
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:AM5EUR03HT065; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 73952d52-7666-48c1-61c8-08d4a1e1fbdb
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:AM5EUR03HT065; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:AM5EUR03HT065; BCL:0; PCL:0; RULEID:; SRVR:AM5EUR03HT065; 
x-forefront-prvs: 0316567485
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 May 2017 13:45:32.9533 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR03HT065
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eIowEwFsYwJ8I-_73d22y6RzWtU>
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, 23 May 2017 13:45:37 -0000

-----Original Message-----
From: Khaled Omar=20
Sent: Tuesday, May 23, 2017 3:45 PM
To: 'Paul Wouters'
Subject: RE: IPv10, KRP, and RRP IDs Removal.

> Your ideas will never spread if you don't know how to convey them to peop=
le. Blaming people to be unwilling to hear you, and telling others to be qu=
iet if they are critical of your ideas only harms your ideas further.

Leave this only to me, I though the ietf can make a progress with any of th=
ese IDs, but they did not, so it is useless.

> I wish you luck contemplating new ideas and new ways of cooperation.

Thanks, there are many ideas and can be represented anywhere.


-----Original Message-----
From: Paul Wouters [mailto:paul@nohats.ca]
Sent: Tuesday, May 23, 2017 3:36 PM
To: Khaled Omar
Subject: RE: IPv10, KRP, and RRP IDs Removal.

On Tue, 23 May 2017, Khaled Omar wrote:

> This is a serious official request, if it means nothing for you, stop rep=
lying.

Your behaviour is wrong. It violates the rules of our community repeatedly.=
 Which has triggered these kind of responses to you because you ignored man=
y unofficial and a few official warnings.

Your ideas will never spread if you don't know how to convey them to people=
. Blaming people to be unwilling to hear you, and telling others to be quie=
t if they are critical of your ideas only harms your ideas further.

I wish you luck contemplating new ideas and new ways of cooperation.

Paul

> -----Original Message-----
> From: shogunx@sleekfreak.ath.cx [mailto:shogunx@sleekfreak.ath.cx]
> Sent: Tuesday, May 23, 2017 2:43 PM
> To: Khaled Omar
> Cc: Benjamin Kaduk; ietf
> Subject: Re: IPv10, KRP, and RRP IDs Removal.
>
> note well... i lol'd.
>
> On Tue, 23 May 2017, Khaled Omar wrote:
>
>> I don't care, once IDs will be removed, I will unsubscribe and will=20
>> not submit anything here again.
>>
>> -------- Original Message --------
>> Subject: Re: IPv10, KRP, and RRP IDs Removal.
>> From: Benjamin Kaduk
>> To: Khaled Omar ,ietf-secretariat@ietf.org
>> CC: ietf@ietf.org
>>
>>
>>       Dear Khaled,
>>
>>       Speaking as sergeant-at-arms,
>>
>>       You were recently placed under a temporary suspension of posting
>>       rights to this list [1], a message that suggested you use that
>>       time to read about the process of submitting and discussing
>>       drafts
>>       at the IETF. It seems that you have not taken advantage of the
>>       opportunity to do so, as you persist in using an overly broad
>>       recipient list when corresponding with the address used for
>>       draft
>>       submission, and are attempting to block discussion of technical
>>       issues on a list reserved for such discussions of technical
>>       issues.
>>
>>       With my authority as sergeant-at-arms under RFC 3004, I am
>>       forced to
>>       request that the secretariat apply an additional restriction of
>>       your
>>       posting rights for the period of 60 days, starting immediately.
>>
>>       If you do decide to bring new work to the IETF in the future, we
>>       will expect that you and keep traffic on the IETF mailing
>>       lists focused on discussion of technical issues and in the
>>       appropriate venue(s).
>>
>>       -Ben Kaduk
>>
>>       [1]
>>
>> https://www.ietf.org/mail-archive/web/ietf/current/msg102743.html
>>
>>       On Mon, May 22, 2017 at 10:55:02PM +0000, Khaled Omar wrote:
>>      > Hi Jasmine,
>>      >
>>      > As I'm the only author of the following IDs:
>>      >
>>      >
>>      > 1) Internet Protocol version 10 (IPv10):
>>       https://datatracker.ietf.org/doc/draft-omar-ipv10/
>>      >
>>      >
>>      > 2) KHALED Routing Protocol (KRP):
>>       https://datatracker.ietf.org/doc/draft-omar-krp/
>>      >
>>      >
>>      > 3) Regional Routing Protocol (RRP):
>>       https://datatracker.ietf.org/doc/draft-omar-rrp/
>>      >
>>      >
>>      > Please remove them all from the ietf database or repository.
>>      >
>>      > If the ideas explained on these drafts will be used, discussed
>>       or published by the ietf, legal actions will be taken.
>>      >
>>      > Regards,
>>      >
>>      > Khaled Omar
>>
>>
>>
>


From nobody Tue May 23 15:05:01 2017
Return-Path: <mglt.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 65C7512EB49; Tue, 23 May 2017 15:04:59 -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 qjov76PGlap3; Tue, 23 May 2017 15:04:58 -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 012C912EB25; Tue, 23 May 2017 15:04:57 -0700 (PDT)
Received: by mail-lf0-x22c.google.com with SMTP id h4so57645961lfj.3; Tue, 23 May 2017 15:04:57 -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=BcPuDhO1pMmWTz00D2DzmDeckG9yrIFP/RDyuvcpmwU=; b=hk37aTM1gMC9xmHLiM2X1NRjMy1scZR1bHf9D5zFEV6SSSrE+w394A8e9X3OMh3E0I F8KVMl0nGPzN7DnpeXbI7O6hPd9wXgIZBEp81TIkns/d6qsaKrEIXrYgige0mCjFz0CO sqChPjKGzfeU3JxSgdIEJEmKvxjPzxSLWnHaZCqDD6V5IkqsWZqPoRXK4iBbPXNASHco GGbKW20PvPF+UscI92OK4D8SxqNpi08d2wdF74E8SIPFfozWvMuMKo4HTvBhFVQOsvEe WCQxZ2fxGFxW/82Cgv7Pq+/RBsA3JpRHZQYa2QYpeUm7A5m/zLfGgDagmcVLnUg+UvpA tZqA==
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=BcPuDhO1pMmWTz00D2DzmDeckG9yrIFP/RDyuvcpmwU=; b=f3QU4YUL9/a0DaBKhu02KBpWiXCtZAyLS0QH5uiHZMxaay2jrYDFFokepXRN8rf/1R ML1LromVNGH6R/x8hCX5AZl09yxleiTbVIaHhJ2KAD9p6fTM5ctIoRDeCJREBFg8A6qU PZvjbuGKk8dXp+r4uCVQWUUPKRrExd57u1LTjd6KgHKr3CCUS03s+SW/WdVFG7XDHxZj vfJrBWvUQS2jt7GxKFwK5AfMjUOfRQGvc9sd6a7R38+ZOncrZERXAK+swduIkkNbsfrZ Xec2bXgusWTe1X7Ykbq4ZsghsANsZBOoXeIJYCzwUCSWNWAZzkbuRkHNO5JfRgYhF3F4 LVng==
X-Gm-Message-State: AODbwcD9LVtd4OZAxukI0lQNvXLiZx4SSscX+jJIEnI3FrijXuwtI8jA fsiChjAnmE12J36oeGaa99Ep1Rbecg==
X-Received: by 10.46.81.17 with SMTP id f17mr8864653ljb.96.1495577096361; Tue, 23 May 2017 15:04:56 -0700 (PDT)
MIME-Version: 1.0
Sender: mglt.ietf@gmail.com
Received: by 10.46.0.14 with HTTP; Tue, 23 May 2017 15:04:55 -0700 (PDT)
In-Reply-To: <20170522173534.GT39245@kduck.kaduk.org>
References: <20170519043827.GL39245@kduck.kaduk.org> <CADZyTkncMTsTQt6C2S+Z0mw+30uc38bfrTSCOvjWRPn_dJkDLQ@mail.gmail.com> <20170519162725.GM39245@kduck.kaduk.org> <CADZyTk=id9bDfi31R+K6hC+ZKzWsjsvo8JbSCzqYGaK_1X1j7Q@mail.gmail.com> <20170522173534.GT39245@kduck.kaduk.org>
From: Daniel Migault <daniel.migault@ericsson.com>
Date: Tue, 23 May 2017 18:04:55 -0400
X-Google-Sender-Auth: mo_QA4jOMmlD5y2_qXqm4vGR1-M
Message-ID: <CADZyTkn1etMeM4BZ5MYPm4VR-YiFH_yvjNQ6TZEwChrJzvHQUg@mail.gmail.com>
Subject: Re: [TLS] secdir review of draft-ietf-tls-ecdhe-psk-aead-03
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: tls <tls@ietf.org>, draft-ietf-tls-ecdhe-psk-aead.all@ietf.org,  "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>, secdir@ietf.org
Content-Type: multipart/alternative; boundary="f403045ff93c901dac0550382d46"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ja-onrSEDB9I6rBJHv2ZC2fGcVs>
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, 23 May 2017 22:04:59 -0000

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

Thank you for the clarifying text. I have added it on my local copy.
Yours,
Daniel

On Mon, May 22, 2017 at 1:35 PM, Benjamin Kaduk <kaduk@mit.edu> wrote:

> Sorry for the slow reply.
>
> On Fri, May 19, 2017 at 12:58:07PM -0400, Daniel Migault wrote:
> > Thank you,
> >
> > Your comments have all been addressed. I have one remaining
> clarification.
> > In my text the SHOULD NOT was intended to the ECDHE_PSK in general, and
> not
> > only for the cipher suites of the draft. In your opinion do we clarify
> > this, and should we use something else than SHOULD NOT ?
>
> It's somewhat awkward, as what we really want to do is Update RFC
> 5489 to add this prohibition there.  But, that's more process to
> jump through and this document is already at a late stage, so I do
> not actually propose doing that.  I would be okay saying
>
>   As such, all ECDHE_PSK ciphers, including those defined outside
>   this document, SHOULD NOT be negotiated in TLS versions prior to
>   1.2.
>
> to match up with the MUST NOT text we have for these new ciphers.
> (Taking into account Martin's text that the prohibition is on
> negotiating them, but offering them in a ClientHello that also
> offers the old version is okay.)
>
> -Ben
>

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

<div dir=3D"ltr"><div><div>Thank you for the clarifying text. I have added =
it on my local copy. <br></div>Yours, <br></div>Daniel<br></div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, May 22, 2017 at 1:3=
5 PM, Benjamin Kaduk <span dir=3D"ltr">&lt;<a href=3D"mailto:kaduk@mit.edu"=
 target=3D"_blank">kaduk@mit.edu</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">Sorry for the slow reply.<br>
<span class=3D""><br>
On Fri, May 19, 2017 at 12:58:07PM -0400, Daniel Migault wrote:<br>
&gt; Thank you,<br>
&gt;<br>
&gt; Your comments have all been addressed. I have one remaining clarificat=
ion.<br>
&gt; In my text the SHOULD NOT was intended to the ECDHE_PSK in general, an=
d not<br>
&gt; only for the cipher suites of the draft. In your opinion do we clarify=
<br>
&gt; this, and should we use something else than SHOULD NOT ?<br>
<br>
</span>It&#39;s somewhat awkward, as what we really want to do is Update RF=
C<br>
5489 to add this prohibition there.=C2=A0 But, that&#39;s more process to<b=
r>
jump through and this document is already at a late stage, so I do<br>
not actually propose doing that.=C2=A0 I would be okay saying<br>
<br>
=C2=A0 As such, all ECDHE_PSK ciphers, including those defined outside<br>
=C2=A0 this document, SHOULD NOT be negotiated in TLS versions prior to<br>
=C2=A0 1.2.<br>
<br>
to match up with the MUST NOT text we have for these new ciphers.<br>
(Taking into account Martin&#39;s text that the prohibition is on<br>
negotiating them, but offering them in a ClientHello that also<br>
offers the old version is okay.)<br>
<br>
-Ben<br>
</blockquote></div><br></div>

--f403045ff93c901dac0550382d46--


From nobody Tue May 23 16:20:05 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 A03151293FF; Tue, 23 May 2017 16:20:04 -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-oauth-native-apps.all@ietf.org, ietf@ietf.org, oauth@ietf.org
Subject: Genart telechat review of draft-ietf-oauth-native-apps-11
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149558160461.28455.9901952519540975154@ietfa.amsl.com>
Date: Tue, 23 May 2017 16:20:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NTYonTd1n4CxpbA9A2TJqFK_K4Q>
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, 23 May 2017 23:20:05 -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 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-oauth-native-apps-11
Reviewer: Elwyn Davies
Review Date: 2017-05-23
IETF LC End Date: 2017-05-16
IESG Telechat date: 2017-05-25

Summary: (still) Almost ready.  Thanks for the responses to my last
call review of -10 which have addressed several of the comments.  It
seems to me that there still some issues with ensuring the selection
of, and hence the connection to,  the browser providing access to the
authorization services is secure (this was referred to in my previous
review but only (IMO)pary addressed).  This feels like a considerable
problem but I am neither a deep security expert or OAuth expert so I
may be wrong.  My old fogey soul is deeply offended by this new
fangled usage of 'app' which is still in my book an abbreviation, but
I guess I have to bow to the changing times and the acknowledgment
that 'app' is now dignified by an appearance in the OED. >shame<.
 Still, given that RFC 6749 lives on the other side of the
app/application divide, I think that the examples in the abstract and
the beginning of s1 should match with RFC 6749 which uses 'native
application(s).'    There are also a couple more nits that I missed on
the previous pass. [BTW UI is indeed a well-known abbreviation but
given it is only used once it might be worh expanding it.]

I understand that -12 has been submitted but had not been placed in
the public repository as of 9pm  UTC on 2017/05/23 (Tuesday evening my
time).

Major issues:
Possibly 2nd minor issue  is actually major.

Minor issues:
Relationship between (web) browser, (operating) system and user choice
of browser:
The terminology definition of 'browser' in s3:
   "browser" The default application launched by the operating system
to handle "http" 
                      and "https" scheme URI content.
The terminology of 'system browser' used in version 10 of the draft
has been removed but the term 'default application' could still be
interpreted as a system choice.  As far as I know, although some
operating systems have a preinstalled browser which will be the
'default browser', this is a commercial decision and users usually
have the option to install an alternative browser and instruct the OS
to use this as the application used to handle http/https content.  I
suggest that 'user selected application' would be clearer than
'default application'.  In particular Linux installations have no
default application - the user/installer has to separately install a
browser and set it as the default.

Security implications of browser application selection and
activation:
[This could possibly be consdiered as a major issue.]
AFAIK the choice of application that is invoked to handle http/https
content is a user choice made on a per-user configuration that does
not require special privileges.  Typically a browser application will
allow a user to select it as default http/https content when it is
first run by a given user and the choice can be changed at the user's
whim subsequently.  However there is no requirement to involve the
user.  A user-level application could (AFAICS) happily hijack the
configuration and install itself as selected browser without any user
intervention.  Apart from the obvious possibility of DoS, I am not
sufficiently expert in the details of OAuth to know what the
consequences of a bad actor installing a malicious pseudo-browser,
potentially acting as a MiTM or otherwise, might be.  It strikes me
that a user of OAuth might be concerned that the browser acting as
intermediary was what s/he thought it was.

Nits/editorial comments:
Abstract:  'Native apps' needs a reference to Section 9 of RFC 6749.
 I note that there they are (still) called 'native applications'.
 Suggest you postpone introducing the shorthand 'native apps' to
section 1 and indicate that the browser is a web browser. Thus:
OLD:
   OAuth 2.0 authorization requests from native apps should only be
made 
   through external user-agents, primarily the user's browser.  This
   specification details the security and usability reasons why this
is
   the case, and how native apps and authorization servers can
implement
   this best practice.
NEW:
   OAuth 2.0 authorization requests from native applications, as
described 
   in Section 9 of RFC 6749, should only be made through external
user-agents,
   primarily the user's web browser.  This specification details the
security and 
   usability reasons why this is the case, and how native applications
and 
   authorization servers can implement this best practice.
END

s1, para 1: In line with the above: s/native apps/native applications
(hereafter known as 'native apps')/

s1, para 2: s/browser/web browser/

s1, last para: 'AppAuth' needs a reference (a pointer to Appendix B
would provide something suitable I think). 

s3:  Needs a definition for 'redirect URI' pointing to RFC 6749
(possibly to Section 3.1.2 there).

s4.1, Figure 1: Rather nitty but the equivalence of authz and
authorization should be noted.

s7.1: Are there any references that an interested reader could follow
to find more info?

s7.2: Again reference(s) would help.  While the draft writes of
operating systems I can only find one (android). Is this in fact
correct?  Is there an expectation that this will become more generally
implemented?  If not making this a firm requirement is somewhat
dubious.

s7.1 and s7.2: It might be useful to mention that s8.1 describes means
to protect against bad actors installing malicious URI claiming apps.
(And also helps with s7.3 I believe).



From nobody Wed May 24 07:41:51 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 BAE22129B33 for <ietf@ietfa.amsl.com>; Wed, 24 May 2017 07:41:49 -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_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_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 t26OJwsATwSP for <ietf@ietfa.amsl.com>; Wed, 24 May 2017 07:41:48 -0700 (PDT)
Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::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 2788212955A for <ietf@ietf.org>; Wed, 24 May 2017 07:41:48 -0700 (PDT)
Received: by mail-yw0-x232.google.com with SMTP id b68so90187300ywe.3 for <ietf@ietf.org>; Wed, 24 May 2017 07:41: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 :cc; bh=szOqz64XXAHFE9MHYsb9S5Fubc4HQeZdPw9IhieDRf0=; b=RU0VNHnMyH2XhV5DmKb6EsfBtYBHTHZhfgVsLqCLqeaveSb1F5wVVFsKmgNYGwb6jr CNM+pMP7HSclGCNasHufCrwY1BCjtdBM/XjhtsS/0bhRI5U5Q7W56Zq0DVi4OCzq6hgF Pnh06QwT2w368Awwc9uCVw7VYZgDfxkT90kX0IFEi7N94GMfCiV3xlygKaJDvso1SNQU Jxc9uEO3Zkl78bIvEjMHnXeCdlq439niXqHP8nXfgd0xNk7g7B3BMD6aetcviFZQZlls +mBixkVTRYKz1N71+yyqG+vlF6DRr//R0IygDcOmsF/Prilafx5Qt3Fg3apqbrHbwUbX HsOQ==
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=szOqz64XXAHFE9MHYsb9S5Fubc4HQeZdPw9IhieDRf0=; b=YIhkDxDDY8PY4kXi2Xaw+snd51KzO1gcxMjwiUbjf2gcZKI1F5Gx9ISeo5efHPZZG/ QwX7ADldKLVW6WQL9jY6SlX6PpTtpWqU5iunpno+nr27S1LCA/Ck6utja/6mTYg07QJ/ ualGbeAxOKXyi/dTrLRmVbX53hoYM011whfFfIvSJyo5XP3lGdHA2He3KatpzjDzxAcj Ts7sYYZAVLB+K1vl7f1CQT14Q11g3ob8n0Bsi9mWlPPPRgYjH0MVfF5oNhD8huL+rPR9 Huc4YyXE9s8Bqa1EcWxP0GVlt6ZJFu31vJ+LojdWaz4QPRSa/OrkxH3e7vLfvOTxmYhB gq9w==
X-Gm-Message-State: AODbwcBohjcuvsDIyaKr5WyJcVdQuVg0PB08LWjOku2dXhd8bFh/T04Y JLLMezOD+klR1fgETwylWPNnfPDT7w==
X-Received: by 10.129.70.195 with SMTP id t186mr11134066ywa.21.1495636907416;  Wed, 24 May 2017 07:41:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.161.198 with HTTP; Wed, 24 May 2017 07:41:46 -0700 (PDT)
In-Reply-To: <20b21b8a-a803-fa36-1ce7-b5c7f4c67503@cisco.com>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <29052.1494439452@obiwan.sandelman.ca> <20b21b8a-a803-fa36-1ce7-b5c7f4c67503@cisco.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 24 May 2017 10:41:46 -0400
Message-ID: <CAKKJt-cYYWVQ+iKdwoyhH+u-7imauDrP2wKQE_jVVJcxAwF_FA@mail.gmail.com>
Subject: Re: Registration for remote participation
To: Eliot Lear <lear@cisco.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a114c7f149474930550461a35"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QnDRUDL6Js7IBNCwiGAZYYaTXM8>
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, 24 May 2017 14:41:50 -0000

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

I didn't see any response to Eliot's suggestion to use datatracker
credentials for registration, so that (1) we have links to information that
has been previously provided, and (2) we'd have roughly the same level of
verification that we have for anyone who's using the datatracker now.

What are the downsides? I guess Meetecho would need to handle IETF
differently from other customers (who, regrettably, don't use datatracker)?
Are there others?

Spencer


On Fri, May 12, 2017 at 2:52 AM, Eliot Lear <lear@cisco.com> wrote:

>
>
> On 5/10/17 8:04 PM, Michael Richardson wrote:
> > IETF Chair <chair@ietf.org> wrote:
> >     > Title
> >     > First / Given Name*
> >     > Last / Family Name*
> >     > Company / Organization
> >     > ISO 3166 Country of Residence*
> >     > Email*
> >     > Gender
> >     > Have you attended an IETF meeting in person before?
> >     > Have you attended an IETF meeting remotely before?
> >
> >     > Upon registering, participants would be issued a registration ID,
> just
> >     > as they are today.
> >
> > Are we validating the email address in some way?
> > If we are not, I don't see the point of the *-required in any of those
> places.
>
> Regardless of motivation here, if the tools team were to use our
> ietf.org logins for registration one of the benefits of that would be
> that many fields could be filled in for us, albeit editable (some of us
> need that for tee shirt size, regrettably),  both for in person and
> remote participation.
>
> There is a downside: the secretariat would have to secure that
> information.  Personally I think we should offer that as an option as an
> exercise to demonstrate how privacy can be done properly, so that we are
> eating our own dog food.  The minimum, though, would be a validated IETF
> account.  I don't think that's a high bar.
>
> Eliot
>
>
>

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

<div dir=3D"ltr">I didn&#39;t see any response to Eliot&#39;s suggestion to=
 use datatracker credentials for registration, so that (1) we have links to=
 information that has been previously provided, and (2) we&#39;d have rough=
ly the same level of verification that we have for anyone who&#39;s using t=
he datatracker now.<div><br></div><div>What are the downsides? I guess Meet=
echo would need to handle IETF differently from other customers (who, regre=
ttably, don&#39;t use datatracker)? Are there others?</div><div><br></div><=
div>Spencer</div><div><br></div></div><div class=3D"gmail_extra"><br><div c=
lass=3D"gmail_quote">On Fri, May 12, 2017 at 2:52 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"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D=
""><br>
<br>
On 5/10/17 8:04 PM, Michael Richardson wrote:<br>
&gt; IETF Chair &lt;<a href=3D"mailto:chair@ietf.org">chair@ietf.org</a>&gt=
; wrote:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Title<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; First / Given Name*<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Last / Family Name*<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Company / Organization<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; ISO 3166 Country of Residence*<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Email*<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Gender<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Have you attended an IETF meeting in person be=
fore?<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Have you attended an IETF meeting remotely bef=
ore?<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Upon registering, participants would be issued=
 a registration ID, just<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; as they are today.<br>
&gt;<br>
&gt; Are we validating the email address in some way?<br>
&gt; If we are not, I don&#39;t see the point of the *-required in any of t=
hose places.<br>
<br>
</span>Regardless of motivation here, if the tools team were to use our<br>
<a href=3D"http://ietf.org" rel=3D"noreferrer" target=3D"_blank">ietf.org</=
a> logins for registration one of the benefits of that would be<br>
that many fields could be filled in for us, albeit editable (some of us<br>
need that for tee shirt size, regrettably),=C2=A0 both for in person and<br=
>
remote participation.<br>
<br>
There is a downside: the secretariat would have to secure that<br>
information.=C2=A0 Personally I think we should offer that as an option as =
an<br>
exercise to demonstrate how privacy can be done properly, so that we are<br=
>
eating our own dog food.=C2=A0 The minimum, though, would be a validated IE=
TF<br>
account.=C2=A0 I don&#39;t think that&#39;s a high bar.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Eliot<br>
<br>
<br>
</font></span></blockquote></div><br></div>

--001a114c7f149474930550461a35--


From nobody Wed May 24 08:44:24 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 A45D4129406; Wed, 24 May 2017 08:44:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mahesh Jethanandani <mjethanandani@gmail.com>
To: <yang-doctors@ietf.org>
Cc: ietf@ietf.org, teas@ietf.org, draft-ietf-teas-yang-te-topo.all@ietf.org
Subject: Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149564066257.28529.12761629961042171907@ietfa.amsl.com>
Date: Wed, 24 May 2017 08:44:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DIKpHedvrrV49ql5aM0e8nr8SB4>
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, 24 May 2017 15:44:23 -0000

Reviewer: Mahesh Jethanandani
Review result: Ready with Issues

Document reviewed: draft-ietf-teas-yang-te-topo-08

Status: Ready with Issues

I am not an expert in Traffic Engineering. This review is looking at
the draft from a YANG perspective. With that said, I have marked it as
“Ready with Issues” because of some of the points discussed below.

Summary:

This document defines a YANG data model for representing, retrieving
and manipulating TE Topologies. The model serves as a base model that
other technology specific TE Topology models can augment.

Comments:

Almost all the containers in the model are presence containers. Is
there a reason why they have to be presence containers? Note, that
presence containers are containers whose existence itself represents
configuration data. What particular configuration data is each
container representing in itself?

It is difficult to co-relate the diagram with the model itself because
of different terms being used to define different parts of the model.
There is “TE Topology Model” and then there is “Generic TE Topology
Model”. Are these one and the same models? If so, a common term for
both of them would be helpful.

There is extensive use of groupings in the document. However, not all
instances of groupings are used multiple number of times. Where they
are not being repeated, it would be better to move the grouping
directly where the uses statement resides. Case in point the grouping
connectivity-label-restriction-list.

The split between config and state containers does not seem to follow
any particular pattern. It is neither a top level split, as is the
case with existing IETF models, nor do they follow the OpenConfig
style of splitting config and state under each relevant leaf, nor do
they follow the new guidelines as suggested by the new datastore model
draft
(https://tools.ietf.org/html/draft-dsdt-nmda-guidelines-01.html).
Since there recommendation for all new models is to follow the new
datastore guidelines, would suggest that the state containers be
removed and any non-duplicate leafs within state be moved under a
single container. I am told that the change in ietf-te-topology from
the current draft to NMDA style is about 175 lines and for te-types it
is 24 line diff (thanks Robert). As such, the change is not major and
can be done easily. See the diffs at the end of this review.

A pyang compilation of the model with —ietf and —lint option was
clean.

A idnits run of the draft reveals some issues with spacing and
references, but they are parts of the diagram, which confuses idnits.

te-types.diff
—————
507,509c507,509
<   grouping explicit-route-hop_config {
<     description
<       "The explicit route subobject grouping";
---
>   grouping explicit-route-hop {
>     description "Explicit route hop grouping";
> 
595,609d594
<     }
<   }
< 
<   grouping explicit-route-hop {
<     description "Explicit route hop grouping";
<     container config {
<       description
<         "Configuration parameters for the explicit route hop";
<       uses explicit-route-hop_config;
<     }
<     container state {
<       config false;
<       description
<         "State parameters for the explicit route hop";
<       uses explicit-route-hop_config;

te-topology.diff
——————-
264a265
>       config false;
323a325
>       config false;
327a330
>       config false;
357a361
>       config false;
361a366
>       config false;
733,744c738,739
<       container config {
<         description
<           "Configuration data.";
<         uses te-link-config;
<       } // config
<       container state {
<         config false;
<         description
<           "Operational state data.";
<         uses te-link-config;
<         uses te-link-state-derived;
<       } // state
---
>       uses te-link-config;
>       uses te-link-state-derived;
780,781c775,776
<                 path "../../../../../../nw:node[nw:node-id = "
<                   + "current()/../../../../../nt:source/"
---
>                 path "../../../../../nw:node[nw:node-id = "
>                   + "current()/../../../../nt:source/"
792,793c787,788
<                 path "../../../../../../nw:node[nw:node-id = "
<                   + "current()/../../../../../nt:destination/"
---
>                 path "../../../../../nw:node[nw:node-id = "
>                   + "current()/../../../../nt:destination/"
841c836
<         path "../../../../../te/templates/link-template/name";
---
>         path "../../../../te/templates/link-template/name";
1087a1083
>       config false;
1092a1089
>       config false;
1106a1104
>       config false;
1113a1112
>       config false;
1128a1128
>       config false;
1267,1279c1267,1268
<       container config {
<         description
<           "Configuration data.";
<         uses te-node-config;
<       } // config
<       container state {
<         config false;
<         description
<           "Operational state data.";
< 
<         uses te-node-config;
<         uses te-node-state-derived;
<       } // state
---
>       uses te-node-config;
>       uses te-node-state-derived;
1297,1309c1286,1287
<         container config {
<           description
<             "Configuration data.";
<           uses te-node-tunnel-termination-attributes;
<         }
<         container state {
<           config false;
<           description
<             "Operational state data.";
< 
<           uses te-node-tunnel-termination-attributes;
<           uses geolocation-container;
<         } // state
---
>         uses te-node-tunnel-termination-attributes;
>         uses geolocation-container;
1406c1384
<         path "../../../../../te/templates/node-template/name";
---
>         path "../../../../te/templates/node-template/name";
1473,1474c1451
<               path "../../../../../../../nt:termination-point/"+
<                 "nt:tp-id";
---
>               path
"../../../../../../nt:termination-point/nt:tp-id";
1485,1486c1462
<               path "../../../../../../../nt:termination-point/"+
<                 "nt:tp-id";
---
>               path
"../../../../../../nt:termination-point/nt:tp-id";
1577a1554
>       config false;
1583a1561
>       config false;
1595a1574
>       config false;
1738c1717
<             path "../../../../../../nt:termination-point/nt:tp-id";
---
>             path "../../../../../nt:termination-point/nt:tp-id";
1753c1732
<     uses te-types:explicit-route-hop_config;
---
>     uses te-types:explicit-route-hop;
1773,1779c1752,1754
<       container config {
<         description
<           "Configuration data.";
<         uses te-termination-point-config;
<       } // config
<       container state {
<         config false;
---
>       uses interface-switching-capability-list;
>       leaf inter-layer-lock-id {
>         type uint32;
1781,1784c1756,1765
<           "Operational state data.";
<         uses te-termination-point-config;
<         uses geolocation-container;
<       } // state
---
>           "Inter layer lock ID, used for path computation in a TE
>            topology covering multiple layers or multiple regions.";
>         reference
>           "RFC5212: Requirements for GMPLS-Based Multi-Region and
>            Multi-Layer Networks (MRN/MLN).
>            RFC6001: Generalized MPLS (GMPLS) Protocol Extensions
for
>            Multi-Layer and Multi-Region Networks (MLN/MRN).";
>       }
> 
>       uses geolocation-container;
1787,1802d1767
<   grouping te-termination-point-config {
<     description
<       "TE termination point configuration grouping.";
<     uses interface-switching-capability-list;
<     leaf inter-layer-lock-id {
<       type uint32;
<       description
<         "Inter layer lock ID, used for path computation in a TE
<          topology covering multiple layers or multiple regions.";
<       reference
<         "RFC5212: Requirements for GMPLS-Based Multi-Region and
<          Multi-Layer Networks (MRN/MLN).
<          RFC6001: Generalized MPLS (GMPLS) Protocol Extensions
<          for Multi-Layer and Multi-Region Networks (MLN/MRN).";
<     }
<   } // te-termination-point-config
1879,1890c1844,1845
<       container config {
<         description
<           "Configuration data.";
<         uses te-topology-config;
<       } // config
<       container state {
<         config false;
<         description
<           "Operational state data.";
<         uses te-topology-config;
<         uses geolocation-container;
<       } // state
---
>       uses te-topology-config;
>       uses geolocation-container;





From nobody Wed May 24 09:12:00 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 F0600129BA8 for <ietf@ietfa.amsl.com>; Wed, 24 May 2017 09:11:58 -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 4rwnbqpSV7ry for <ietf@ietfa.amsl.com>; Wed, 24 May 2017 09:11:57 -0700 (PDT)
Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::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 BD04812955A for <ietf@ietf.org>; Wed, 24 May 2017 09:11:56 -0700 (PDT)
Received: by mail-wr0-x235.google.com with SMTP id l50so57876222wrc.3 for <ietf@ietf.org>; Wed, 24 May 2017 09:11:56 -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=ymymEolR5D8G5MHO4SOnCVI7C0DKZwRHEdnYkKxnPN0=; b=jPiDZDChbTiAbrDSE54MsBABlR057jADG9HXixrT5NyeW4yFl3olLSa7wf3qMmTUUV 60+V/YTu3g431vxwl7OR07TqgwJqWGR06jWgbASj8akEM67975g8BtDMPdsMOHuVUxdJ YxbtoVYheHEgdN37oyikUL4swWm1fBtMM17+Urpyl/6A0s4HpDfr438Id3mCJwxepMDH gYFHDtT4lq6bR/FbmVH1/hCHlDOv6rubfjcH9hf4byTdJgBNUC0Eldv9xAJoOrLqQ/Yb 7Q49byqm5wX8B5rXRWZldvWcqWRBu9NtoNNGsSYjRtttDnrIiPI9nYkWlOQTnHS7cDsH WOxA==
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=ymymEolR5D8G5MHO4SOnCVI7C0DKZwRHEdnYkKxnPN0=; b=ESf2bOOmmbNlQ7Qg/FOtrrRtCmURJQXNj+MHJm9Z74KuDfuAcx4uLm04UQEJX6K9pa YxUn6lvCutQAPxteeMsJXQ2le2I7/U7uS/Sd3xWNSXGp31+KFwI8IgjBqHaorTowbMmy 0WnXoqiSw4HvrKrt0wwkzgR694YBn+XqWYnKOmDmfGzM/w5tpDCNGmlvtVpDZukamqkJ szPRpgAkxcWXW2LXzBIPCFU6aMmOj/JJ5cGnqAfOPBIRAmDb1EVoOOIYOt91opVtkwcU 9PxA5XPI8y+pKbWXUlEevqEqrZgHicQyDi5oZfTLpMsFVUeRR7Ld6V4JYQ0oqQ8r/g/+ DuMw==
X-Gm-Message-State: AODbwcAWWoySvp2HLY8UBN4KFFsMydXGeEUpYJg/QwS7R/Q3wR7rqI4z mBuBjXXECRswcQ==
X-Received: by 10.223.179.92 with SMTP id k28mr1289105wrd.118.1495642315209; Wed, 24 May 2017 09:11:55 -0700 (PDT)
Received: from [192.168.137.36] ([176.13.229.90]) by smtp.gmail.com with ESMTPSA id a24sm6361757wra.17.2017.05.24.09.11.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 May 2017 09:11:54 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <598238A4-F7B9-4C3A-80A3-FDEEDB5A5A90@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_4C7DA60A-7163-47AD-B142-DE3B01B134F7"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Registration for remote participation
Date: Wed, 24 May 2017 19:11:50 +0300
In-Reply-To: <CAKKJt-cYYWVQ+iKdwoyhH+u-7imauDrP2wKQE_jVVJcxAwF_FA@mail.gmail.com>
Cc: Eliot Lear <lear@cisco.com>, Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion <ietf@ietf.org>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <29052.1494439452@obiwan.sandelman.ca> <20b21b8a-a803-fa36-1ce7-b5c7f4c67503@cisco.com> <CAKKJt-cYYWVQ+iKdwoyhH+u-7imauDrP2wKQE_jVVJcxAwF_FA@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bvG68Rg3O0fcno5e77XrazsHrOs>
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, 24 May 2017 16:11:59 -0000

--Apple-Mail=_4C7DA60A-7163-47AD-B142-DE3B01B134F7
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_729992C1-FE7E-4A38-AEC4-144E26BB7253"


--Apple-Mail=_729992C1-FE7E-4A38-AEC4-144E26BB7253
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

No statistics about this, but there are people who don=E2=80=99t have =
datatracker credentials.

You can do most things, including submitting drafts without datatracker =
credentials.

But as yet another option it works fine.

Yoav

On 24 May 2017, at 17:41, Spencer Dawkins at IETF =
<spencerdawkins.ietf@gmail.com> wrote:

> I didn't see any response to Eliot's suggestion to use datatracker =
credentials for registration, so that (1) we have links to information =
that has been previously provided, and (2) we'd have roughly the same =
level of verification that we have for anyone who's using the =
datatracker now.
>=20
> What are the downsides? I guess Meetecho would need to handle IETF =
differently from other customers (who, regrettably, don't use =
datatracker)? Are there others?
>=20
> Spencer
>=20
>=20
> On Fri, May 12, 2017 at 2:52 AM, Eliot Lear <lear@cisco.com =
<mailto:lear@cisco.com>> wrote:
>=20
>=20
> On 5/10/17 8:04 PM, Michael Richardson wrote:
> > IETF Chair <chair@ietf.org <mailto:chair@ietf.org>> wrote:
> >     > Title
> >     > First / Given Name*
> >     > Last / Family Name*
> >     > Company / Organization
> >     > ISO 3166 Country of Residence*
> >     > Email*
> >     > Gender
> >     > Have you attended an IETF meeting in person before?
> >     > Have you attended an IETF meeting remotely before?
> >
> >     > Upon registering, participants would be issued a registration =
ID, just
> >     > as they are today.
> >
> > Are we validating the email address in some way?
> > If we are not, I don't see the point of the *-required in any of =
those places.
>=20
> Regardless of motivation here, if the tools team were to use our
> ietf.org <http://ietf.org/> logins for registration one of the =
benefits of that would be
> that many fields could be filled in for us, albeit editable (some of =
us
> need that for tee shirt size, regrettably),  both for in person and
> remote participation.
>=20
> There is a downside: the secretariat would have to secure that
> information.  Personally I think we should offer that as an option as =
an
> exercise to demonstrate how privacy can be done properly, so that we =
are
> eating our own dog food.  The minimum, though, would be a validated =
IETF
> account.  I don't think that's a high bar.
>=20
> Eliot
>=20
>=20
>=20


--Apple-Mail=_729992C1-FE7E-4A38-AEC4-144E26BB7253
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"">No statistics about this, but there are people who don=E2=80=99=
t have datatracker credentials.<div class=3D""><br class=3D""></div><div =
class=3D"">You can do most things, including submitting drafts without =
datatracker credentials.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">But as yet another option it works =
fine.&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">Yoav</div><div class=3D""><br class=3D""><div><div =
class=3D"">On 24 May 2017, at 17:41, Spencer Dawkins at IETF &lt;<a =
href=3D"mailto:spencerdawkins.ietf@gmail.com" =
class=3D"">spencerdawkins.ietf@gmail.com</a>&gt; wrote:</div><div =
class=3D""><br class=3D""></div><blockquote type=3D"cite" class=3D""><div =
class=3D""><div dir=3D"ltr" class=3D"">I didn't see any response to =
Eliot's suggestion to use datatracker credentials for registration, so =
that (1) we have links to information that has been previously provided, =
and (2) we'd have roughly the same level of verification that we have =
for anyone who's using the datatracker now.<div class=3D""><br =
class=3D""></div><div class=3D"">What are the downsides? I guess =
Meetecho would need to handle IETF differently from other customers =
(who, regrettably, don't use datatracker)? Are there others?</div><div =
class=3D""><br class=3D""></div><div class=3D"">Spencer</div><div =
class=3D""><br class=3D""></div></div><div class=3D"gmail_extra"><br =
class=3D""><div class=3D"gmail_quote">On Fri, May 12, 2017 at 2:52 AM, =
Eliot Lear <span dir=3D"ltr" class=3D"">&lt;<a =
href=3D"mailto:lear@cisco.com" target=3D"_blank" =
class=3D"">lear@cisco.com</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"><span class=3D""><br class=3D"">
<br class=3D"">
On 5/10/17 8:04 PM, Michael Richardson wrote:<br class=3D"">
&gt; IETF Chair &lt;<a href=3D"mailto:chair@ietf.org" =
class=3D"">chair@ietf.org</a>&gt; wrote:<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp;&gt; Title<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp;&gt; First / Given Name*<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp;&gt; Last / Family Name*<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp;&gt; Company / Organization<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp;&gt; ISO 3166 Country of Residence*<br class=3D"">=

&gt;&nbsp; &nbsp; &nbsp;&gt; Email*<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp;&gt; Gender<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp;&gt; Have you attended an IETF meeting in person =
before?<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp;&gt; Have you attended an IETF meeting remotely =
before?<br class=3D"">
&gt;<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp;&gt; Upon registering, participants would be =
issued a registration ID, just<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp;&gt; as they are today.<br class=3D"">
&gt;<br class=3D"">
&gt; Are we validating the email address in some way?<br class=3D"">
&gt; If we are not, I don't see the point of the *-required in any of =
those places.<br class=3D"">
<br class=3D"">
</span>Regardless of motivation here, if the tools team were to use =
our<br class=3D"">
<a href=3D"http://ietf.org/" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">ietf.org</a> logins for registration one of the benefits of =
that would be<br class=3D"">
that many fields could be filled in for us, albeit editable (some of =
us<br class=3D"">
need that for tee shirt size, regrettably),&nbsp; both for in person =
and<br class=3D"">
remote participation.<br class=3D"">
<br class=3D"">
There is a downside: the secretariat would have to secure that<br =
class=3D"">
information.&nbsp; Personally I think we should offer that as an option =
as an<br class=3D"">
exercise to demonstrate how privacy can be done properly, so that we =
are<br class=3D"">
eating our own dog food.&nbsp; The minimum, though, would be a validated =
IETF<br class=3D"">
account.&nbsp; I don't think that's a high bar.<br class=3D"">
<span class=3D"HOEnZb"><font color=3D"#888888" class=3D""><br class=3D"">
Eliot<br class=3D"">
<br class=3D"">
<br class=3D"">
</font></span></blockquote></div><br class=3D""></div>
</div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_729992C1-FE7E-4A38-AEC4-144E26BB7253--

--Apple-Mail=_4C7DA60A-7163-47AD-B142-DE3B01B134F7
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-----

iQEcBAEBCgAGBQJZJbDGAAoJELhJCxUKWMyZg0UIAM1sAox+WHJ+DqsgFvt8wn8r
in/jW1mS0IzxorLBixkE2xf/QpID7cGyV6flKeE3zyRl5QpptEAcGadXNmk8iPhO
hm0JxFtTLOx4sEG6snqPTO7txzKSaHHpEH2tYQyBsgf/M5pz526qMmMWUI2HxBPj
7WhfdL/QQpZYy+Ab9FYLyZAl6KWBjEeECHe2mXfk6ZnJhsvznEDeS6CmYKpBRe/a
GKl8YWSh/DJaNGrE83Dppr3JhFLOrWxZUtZMaUOBDFBkp0lZzLGjqsIjmGxRBYXa
XClhiC9+gGPANbTRz+qOEfR71RXWjtuwj3tHCElNn5vTldxAvN8Qql/ZeR3Vr2A=
=Ijo0
-----END PGP SIGNATURE-----

--Apple-Mail=_4C7DA60A-7163-47AD-B142-DE3B01B134F7--


From nobody Wed May 24 09:49:26 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 3389D129B6C; Wed, 24 May 2017 09:49:24 -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: draft-nottingham-rfc5988bis.all@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-nottingham-rfc5988bis-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149564456407.28435.714290542306024853@ietfa.amsl.com>
Date: Wed, 24 May 2017 09:49:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U6_pYfIU5jIQV5JmCikDTPQMM0M>
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, 24 May 2017 16:49:24 -0000

Reviewer: Stewart Bryant
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-nottingham-rfc5988bis-??
Reviewer: Stewart Bryant
Review Date: 2017-05-24
IETF LC End Date: 2017-05-26
IESG Telechat date: 2017-06-08

Summary:
This is a well written document, and ready for publication.

I found an IANA consideration a little confusing, but I am sure that
either IANA understand it or will ask for clarification.

Major issues:

Minor issues:
I found the IANA considerations confusing. Specifically it looks like
Section 4.1 refers to 
https://www.iana.org/assignments/message-headers/message-headers.xhtml
although it does not say so in so many words.

Assuming that to be the case the IANA text in section 4.1 (which
copies the text from RFC5688)
does not line up column by column with the text in the registry. I
assume that 
[RFC&rfc.number;] means [This RFC], but do not see where Author/Change
control fits in the 
registry.

Nits/editorial comments: 

In the intro and the abstract the text "a model for indicate the
relationships" is not good grammar.


From nobody Wed May 24 10:34:44 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 87EE3129AEA for <ietf@ietfa.amsl.com>; Wed, 24 May 2017 10:34:42 -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, 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 McqukER20hCp for <ietf@ietfa.amsl.com>; Wed, 24 May 2017 10:34:41 -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 69CD81201F8 for <ietf@ietf.org>; Wed, 24 May 2017 10:34:41 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id DFF5D2009E; Wed, 24 May 2017 13:34:40 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 7D36F6380F; Wed, 24 May 2017 13:34:40 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
cc: Eliot Lear <lear@cisco.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: Registration for remote participation
In-Reply-To: <CAKKJt-cYYWVQ+iKdwoyhH+u-7imauDrP2wKQE_jVVJcxAwF_FA@mail.gmail.com>
References: <C64BEBC3-E6D2-4DA7-9983-06B038221942@ietf.org> <29052.1494439452@obiwan.sandelman.ca> <20b21b8a-a803-fa36-1ce7-b5c7f4c67503@cisco.com> <CAKKJt-cYYWVQ+iKdwoyhH+u-7imauDrP2wKQE_jVVJcxAwF_FA@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, 24 May 2017 13:34:40 -0400
Message-ID: <13415.1495647280@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/u6pQvhSCRWAYjHyGIU0jAumq5Rw>
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, 24 May 2017 17:34:42 -0000

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
    > I didn't see any response to Eliot's suggestion to use datatracker
    > credentials for registration, so that (1) we have links to information
    > that has been previously provided, and (2) we'd have roughly the same
    > level of verification that we have for anyone who's using the
    > datatracker now.

I think that all current DT authentication occurs by database dips (mysql,
port 3306).   To do this nicely, it would have to be OAUTH2, which we do not
have.

    > What are the downsides? I guess Meetecho would need to handle IETF
    > differently from other customers (who, regrettably, don't use
    > datatracker)? Are there others?

If we provided OAUTH2, then there likely would be a much better match.

=2D-=20
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+93Q3WUFAlklxDAACgkQgItw+93Q
3WUydwgAjTrpS0Mb6fo9FI/JpgUGGiF8SIyCNKPE0Gi3GSfGQ1ivMzso2l91XBfr
OxPf2/bro+twVF//Nj/0G3v4ybL6qgBrOJK+n+FlcwviXLgDmYjUbMaaRuoaIpVE
G5f8QzKxyRvGKXq4UdJ1H+Iabbo8wmz1AKNojsqFgEIyE7vCDeeTbtnNhkbk612z
5aqJVOnJvZjHJnMIfjJjuzCIEILPhv3kKau7R4Xk2NPPnBYLqZXojtWRjjuyq9vr
lwvvH64nlwt3GvLe7uiRZUpOnL4MEVcWYdfFZxstOhEyecIu5xCJ8m8hd9bMmOm4
TzscO2WzwZt2LLCuRLopY6AEjrG0iw==
=iur3
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed May 24 15:16:39 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 47AB6126CF9; Wed, 24 May 2017 15:16:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=NWmcw26d; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=oOwwZzwY
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fkX8XCGk8QsQ; Wed, 24 May 2017 15:16:36 -0700 (PDT)
Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94FFE1287A7; Wed, 24 May 2017 15:16:36 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.nyi.internal (Postfix) with ESMTP id BF47FCA6; Wed, 24 May 2017 18:16:35 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Wed, 24 May 2017 18:16:35 -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=cIiZ7g2V4II3vxBXXL +1+dvI3NU+zIMiy6YWmPOSjU8=; b=NWmcw26dQ4+u15vfAtelRrUSYcyT5OGsCN j2arcewjTgU2Atk7Lyff5AzmUcmTx9yntIxBn5CVJZROE984MorTUq5svPvsJIuT zwgOhMc0+6KcW6TL1R7aB2ksx6D8oDTNidHQXr+8ZYKgkHE1zUmR8CtoGA7Jwq8H RsEZjN3I6EqWdy+hIeJ7Cas6H4H28T/RbFyPXi+aeNKBivkv5uvV9L7qvJpe+Wxs V3mBK+G6dNYzrl73aRMHRXO7NyLor9jHhALQrpfa2jsfZsWqujgL2841AP05PiY5 lj+lr64v6RTY0GRkB/gWzWrUK5ERdyMm2fpwf/C4z1GMszPK16Sw==
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=cIiZ7g2V4II3vxBXXL+1+dvI3NU+zIMiy6YWmPOSjU8=; b=oOwwZzwY SDcCUfAOVsACBDctrcek65bd9ltAoe7l1P8dSwHYQ/yRSlWcgZimCJVj5OFOtCny x/pfU369Wb07844Mmj7RooX22E2A0ABflvlSEd4ksOMvGg4suZk8NzhBr7atWMj3 zzz+CtRuqCBaB8kjPgKMbKGtsBxM64caJ2aaVg7QjiK477tX06s/TkfzQDadhPY/ djRkegF1r0IfUqlN65MyuujgGukOIUqeYzbQjmOc5QgQgsfaAjQjTCf+2d0LD6fU miWGtX6zaDCpl/5jn4eJYhWO4Kf9uEp8y6CcPvz87rylGtL19GoApGp8EVaNtRqe ILpnvsQIJazEug==
X-ME-Sender: <xms:QgYmWQmTeNbvict0i2wI51RLlDt36qTKVOvapZrk2qClPNWBoXzIOg>
X-Sasl-enc: a4dPfuHqXik6B/MnVmy50oXeevu1ayiZtoVY1NqIDXqf 1495664194
Received: from frankexeofviews.lan (dtf2586697.lnk.telstra.net [149.135.121.88]) by mail.messagingengine.com (Postfix) with ESMTPA id 4E7917E7A5; Wed, 24 May 2017 18:16:32 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Genart last call review of draft-nottingham-rfc5988bis-05
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <149564456407.28435.714290542306024853@ietfa.amsl.com>
Date: Thu, 25 May 2017 08:16:25 +1000
Cc: gen-art@ietf.org, IETF Discussion Mailing List <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <178E5CCA-3FA4-4AD1-AF6E-CB1E609CB363@mnot.net>
References: <149564456407.28435.714290542306024853@ietfa.amsl.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hzQh3Zz6pshi6ffr0RUrACLhDSs>
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, 24 May 2017 22:16:38 -0000

Hi Stewart,

Thanks for the review. Responses below.

> Minor issues:
> I found the IANA considerations confusing. Specifically it looks like
> Section 4.1 refers to=20
> https://www.iana.org/assignments/message-headers/message-headers.xhtml
> although it does not say so in so many words.

It says=20

> This specification updates the Message Header registry entry for =
"Link" in HTTP [RFC3864] to refer to this document.

Are you suggesting that it be updated to say "Permanent Message Header =
Field Names registry", or something else?


> Assuming that to be the case the IANA text in section 4.1 (which =
copies the text from RFC5688) does not line up column by column with the =
text in the registry. I assume that=20
> [RFC&rfc.number;] means [This RFC],

Yes; already fixed in source.

> but do not see where Author/Change control fits in the registry.

It's required by the registration template in RFC3864.


> Nits/editorial comments:=20
>=20
> In the intro and the abstract the text "a model for indicate the
> relationships" is not good grammar.

Already fixed in source.

Thanks again!


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



From nobody Thu May 25 03:57:30 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 B41F012946B; Thu, 25 May 2017 03:57:16 -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-curdle-cms-ecdh-new-curves.all@ietf.org, curdle@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-ietf-curdle-cms-ecdh-new-curves-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149570983670.8681.5001417855088402577@ietfa.amsl.com>
Date: Thu, 25 May 2017 03:57:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/m2uYIpwvY-9tEAyqo3XgyU0vUeM>
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, 25 May 2017 10:57:17 -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-curdle-cms-ecdh-new-curves-??
Reviewer: Roni Even
Review Date: 2017-05-25
IETF LC End Date: 2017-05-28
IESG Telechat date: Not scheduled for a telechat

Summary:
The document is ready for publication as a standard track RFC

Major issues:

Minor issues:

Nits/editorial comments: 

In general it was easy to read and follow.  Maybe it will be good to
repeat in section 3.2 the definition of KeyAgreeRecipientInfo . This
is done is section 2 for ECC-CMS-SharedInfo but it is not crucial.

1. There is no ToC
2. In section 2.2 fourth paragraph "is used two places" - "in two .."






From nobody Thu May 25 11:51:49 2017
Return-Path: <touch@isi.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 E173912E037; Thu, 25 May 2017 11:51:41 -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_50=0.8, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 6bku3iCcgjRk; Thu, 25 May 2017 11:51:41 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 EA1251293E0; Thu, 25 May 2017 11:51:40 -0700 (PDT)
Received: from [128.9.184.77] ([128.9.184.77]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v4PIpDuT008458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 25 May 2017 11:51:13 -0700 (PDT)
Subject: Re: [art] Artart last call review of draft-ietf-nfsv4-versioning-09
To: Matthew Miller <linuxwolf+ietf@outer-planes.net>, art@ietf.org
Cc: ietf@ietf.org, draft-ietf-nfsv4-versioning.all@ietf.org, nfsv4@ietf.org
References: <149462145126.13443.7366912235626631179@ietfa.amsl.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <d64909ad-b71a-a932-606b-8b974cf68140@isi.edu>
Date: Thu, 25 May 2017 11:51:13 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <149462145126.13443.7366912235626631179@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iMiXSsCpIyS2Y3ij3cNzDOkQ8kc>
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, 25 May 2017 18:51:42 -0000

Hi, all,

I'd like to add one point.

This doc gives guidance on creating minor versions, but never addresses
major versions.

IMO, past variants of NFS have not handled major version changes
appropriately. Each one has been assigned a new port number. This is no
longer recommended practice (see RFC7605, Sec 7.5).

Is this issue addressed in another document?

AFAICT, if (when) NFSv5 is developed, it seems to appear to need another
port number. If that's the case (and I sincerely hope it isn't), it MUST
be the last one assigned to this service.

Joe


From nobody Thu May 25 12:33:18 2017
Return-Path: <davenoveck@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 97127127876; Thu, 25 May 2017 12:33:10 -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 CL6gi7cRHOZW; Thu, 25 May 2017 12:33:09 -0700 (PDT)
Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::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 D6EF1126BF7; Thu, 25 May 2017 12:33:08 -0700 (PDT)
Received: by mail-it0-x230.google.com with SMTP id o5so62383650ith.1; Thu, 25 May 2017 12:33:08 -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=gskXHB8Plylia7vweZIvARanglO8dX5tSPPryRy6K0s=; b=qADyrPAKLpdOSJZSSOVb+Gwmf886GXkmrFV429242s/quP14GU3pvNpMyItpEACjVX uhv19CdQN+oUHoisUkfNq5AFZxpYoWZD7mhu1x5p5N3ijZRWsPv8EnjrAj6vREu6+aTe VPzN9LueYbrNvDcCSX97YOY6TK08XLq+kxESJB/GNGub0gCq7oy+SdJgBOh2ozky2F6s squBfSmavqq7wfB6UPABZTYF+t7BnSYW+s+3dk0iwExtUS+35AKbg8OowVJjaaCtI+b2 Q11hMX2JDaXgxy8baW5/XH+uPMZ6H9Jnn4j4qkNerHy4hDCblvLYKPUKlp0EENAKUjjS Htqg==
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=gskXHB8Plylia7vweZIvARanglO8dX5tSPPryRy6K0s=; b=XsgmbiQiwkQ1su6op3nagWLd2lvEil0c7Po8h2od+bYvpSluQrR5kUhWBPkB/ESHPk 2jVo47rY8CrNrTnTGpyh9gZ52hcSRLEwcOypnUOGpQpZ9AqyzCBp0eAzaKkYXTCcOgdD tuDRvKlUw+WuIBlZicohxmhs9cCwMxlPsqamaiSvh1zqNnQQq43kGnNpUy9qMKdfS8jE 4qqDWekjXcfDjG/eu4TkrjLfkGBpx7wHkDqfKMiWa5ZE8DGBxXTW70gYT81j5Uk+/5qb ErYaMEjy9+g/m1knzBhWdADGZCUj1rERSLDJh9HZWQ2GO4fiqe5oRac1uWa5Itg+av/B Od9A==
X-Gm-Message-State: AODbwcCmec2PjkGSINXU642bJdoDQTgNNHmbfmwN/6mSp6VJ5RL41F13 /ymmO9r+Fmd77ZW6Qpb9EPjv5OypfQ==
X-Received: by 10.36.11.68 with SMTP id 65mr16094591itd.80.1495740788093; Thu, 25 May 2017 12:33:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.4.148 with HTTP; Thu, 25 May 2017 12:33:07 -0700 (PDT)
In-Reply-To: <d64909ad-b71a-a932-606b-8b974cf68140@isi.edu>
References: <149462145126.13443.7366912235626631179@ietfa.amsl.com> <d64909ad-b71a-a932-606b-8b974cf68140@isi.edu>
From: David Noveck <davenoveck@gmail.com>
Date: Thu, 25 May 2017 15:33:07 -0400
Message-ID: <CADaq8jdWgRSqGVt0UBf3sqzp3ivYAW36y1JuNg43HGp5WboKrg@mail.gmail.com>
Subject: Re: [art] Artart last call review of draft-ietf-nfsv4-versioning-09
To: Joe Touch <touch@isi.edu>
Cc: Matthew Miller <linuxwolf+ietf@outer-planes.net>, art@ietf.org, ietf@ietf.org,  draft-ietf-nfsv4-versioning.all@ietf.org, "nfsv4@ietf.org" <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="001a1140c4ee59bfcf05505e4a1f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QWLxDNFUjJYvLdursmkSg23e0mc>
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, 25 May 2017 19:33:11 -0000

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

> This doc gives guidance on creating minor versions, but never addresses
> major versions.

I think we had enough to do addressing minor versions and didn't want to
speculate about a possible v5.  after all, we're the nfsv4 working group
and not the nfsvn working group.


> IMO, past variants of NFS have not handled major version changes
> appropriately. Each one has been assigned a new port number. This is no
> longer recommended practice (see RFC7605, Sec 7.5).


Makes sense.

> Is this issue addressed in another document?

I don't think so.

> AFAICT, if (when) NFSv5 is developed, it seems to appear to need another
> port number.

I don't see why it would.  If there is another Rpc version of the NFS
program,
I don't see why the appropriate negotiation could be defined.  I think
doing\
that would be up to those defining nfsv5.

> If that's the case (and I sincerely hope it isn't), it MUST
> be the last one assigned to this service.

I don't think "MUST" is appropriate in this case but I would say that
assigning
another port would be a DAMN SHAME.

On Thu, May 25, 2017 at 2:51 PM, Joe Touch <touch@isi.edu> wrote:

> Hi, all,
>
> I'd like to add one point.
>
> This doc gives guidance on creating minor versions, but never addresses
> major versions.
>
> IMO, past variants of NFS have not handled major version changes
> appropriately. Each one has been assigned a new port number. This is no
> longer recommended practice (see RFC7605, Sec 7.5).
>
> Is this issue addressed in another document?
>
> AFAICT, if (when) NFSv5 is developed, it seems to appear to need another
> port number. If that's the case (and I sincerely hope it isn't), it MUST
> be the last one assigned to this service.
>
> Joe
>

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

<div dir=3D"ltr"><span style=3D"font-size:12.8px">&gt; This doc gives guida=
nce on creating minor versions, but never addresses</span><br style=3D"font=
-size:12.8px"><span style=3D"font-size:12.8px">&gt; major versions.</span><=
div><br></div><div>I think we had enough to do addressing minor versions an=
d didn&#39;t want to</div><div>speculate about a possible v5. =C2=A0after a=
ll, we&#39;re the nfsv4 working group</div><div>and not the nfsvn working g=
roup.</div><div><br><br style=3D"font-size:12.8px"><span style=3D"font-size=
:12.8px">&gt; IMO, past variants of NFS have not handled major version chan=
ges</span><br style=3D"font-size:12.8px"><span style=3D"font-size:12.8px">&=
gt; appropriately. Each one has been assigned a new port number. This is no=
</span><br style=3D"font-size:12.8px"><span style=3D"font-size:12.8px">&gt;=
 longer recommended practice (see RFC7605, Sec 7.5).</span><br style=3D"fon=
t-size:12.8px"><br><br>Makes sense.</div><div><br><span style=3D"font-size:=
12.8px">&gt; Is this issue addressed in another document?</span><br style=
=3D"font-size:12.8px"><br>I don&#39;t think so.</div><div><br><span style=
=3D"font-size:12.8px">&gt; AFAICT, if (when) NFSv5 is developed, it seems t=
o appear to need another</span><br style=3D"font-size:12.8px"><span style=
=3D"font-size:12.8px">&gt; port number.=C2=A0</span></div><div><span style=
=3D"font-size:12.8px"><br></span></div><div><span style=3D"font-size:12.8px=
">I don&#39;t see why it would.=C2=A0 If there is another Rpc version of th=
e NFS program,</span></div><div><span style=3D"font-size:12.8px">I don&#39;=
t see why the appropriate negotiation could be defined.=C2=A0 I think doing=
\</span></div><div><span style=3D"font-size:12.8px">that would be up to tho=
se defining nfsv5.</span></div><div><span style=3D"font-size:12.8px"><br></=
span></div><div><span style=3D"font-size:12.8px">&gt; If that&#39;s the cas=
e (and I sincerely hope it isn&#39;t), it MUST</span><br style=3D"font-size=
:12.8px"><span style=3D"font-size:12.8px">&gt; be the last one assigned to =
this service.</span><br></div><div><br></div><div>I don&#39;t think &quot;M=
UST&quot; is appropriate in this case but I would say that assigning=C2=A0<=
/div><div>another port would be a DAMN SHAME.</div></div><div class=3D"gmai=
l_extra"><br><div class=3D"gmail_quote">On Thu, May 25, 2017 at 2:51 PM, Jo=
e Touch <span dir=3D"ltr">&lt;<a href=3D"mailto:touch@isi.edu" target=3D"_b=
lank">touch@isi.edu</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"=
>Hi, all,<br>
<br>
I&#39;d like to add one point.<br>
<br>
This doc gives guidance on creating minor versions, but never addresses<br>
major versions.<br>
<br>
IMO, past variants of NFS have not handled major version changes<br>
appropriately. Each one has been assigned a new port number. This is no<br>
longer recommended practice (see RFC7605, Sec 7.5).<br>
<br>
Is this issue addressed in another document?<br>
<br>
AFAICT, if (when) NFSv5 is developed, it seems to appear to need another<br=
>
port number. If that&#39;s the case (and I sincerely hope it isn&#39;t), it=
 MUST<br>
be the last one assigned to this service.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Joe<br>
</font></span></blockquote></div><br></div>

--001a1140c4ee59bfcf05505e4a1f--


From nobody Thu May 25 14:48:19 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 69A16129B82; Thu, 25 May 2017 14:48:17 -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 last call review of draft-ietf-v6ops-unique-ipv6-prefix-per-host-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149574889740.8736.3270119983003121650@ietfa.amsl.com>
Date: Thu, 25 May 2017 14:48:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nep6PInphiI0yCket36axtsgyLk>
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, 25 May 2017 21:48:17 -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-v6ops-unique-ipv6-prefix-per-host-??
Reviewer: Joel Halpern
Review Date: 2017-05-25
IETF LC End Date: 2017-06-06
IESG Telechat date: Not scheduled for a telechat

Summary: This document is ready for publication as an RFC

Major issues: N/A

Minor issues:
     I will leave the decision on the appropriate status of this
document to the IESG.
     I note that sections, for example the third paragraph of section
3, are currently written as if the IETF is recommending this practice,
rather than merely describing how to do this when it is desired. 
Whether this is appropriate is again a call for the members of the
IESG.

Nits/editorial comments: 



From nobody Thu May 25 15:18:18 2017
Return-Path: <touch@isi.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 31DF9127B52; Thu, 25 May 2017 15:18:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.001
X-Spam-Level: 
X-Spam-Status: No, score=-5.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 YEQN_6obsKYx; Thu, 25 May 2017 15:18:15 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (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 C2F31129B21; Thu, 25 May 2017 15:18:15 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id v4PMHhQw019774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 25 May 2017 15:17:57 -0700 (PDT)
Subject: Re: [art] Artart last call review of draft-ietf-nfsv4-versioning-09
To: David Noveck <davenoveck@gmail.com>
Cc: Matthew Miller <linuxwolf+ietf@outer-planes.net>, art@ietf.org, ietf@ietf.org, draft-ietf-nfsv4-versioning.all@ietf.org, "nfsv4@ietf.org" <nfsv4@ietf.org>
References: <149462145126.13443.7366912235626631179@ietfa.amsl.com> <d64909ad-b71a-a932-606b-8b974cf68140@isi.edu> <CADaq8jdWgRSqGVt0UBf3sqzp3ivYAW36y1JuNg43HGp5WboKrg@mail.gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <d10f43d7-d136-d9b9-fcfb-dc78a52e1355@isi.edu>
Date: Thu, 25 May 2017 15:17:43 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <CADaq8jdWgRSqGVt0UBf3sqzp3ivYAW36y1JuNg43HGp5WboKrg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------AC254B0531D11EB8A41583A9"
Content-Language: en-US
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7hbIDxROvMyNz5Au2OcfS3i2iyc>
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, 25 May 2017 22:18:17 -0000

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

Hi, David,

Thanks for the response, and agreed throughout.

Joe


On 5/25/2017 12:33 PM, David Noveck wrote:
> > This doc gives guidance on creating minor versions, but never addresses
> > major versions.
>
> I think we had enough to do addressing minor versions and didn't want to
> speculate about a possible v5.  after all, we're the nfsv4 working group
> and not the nfsvn working group.
>
>
> > IMO, past variants of NFS have not handled major version changes
> > appropriately. Each one has been assigned a new port number. This is no
> > longer recommended practice (see RFC7605, Sec 7.5).
>
>
> Makes sense.
>
> > Is this issue addressed in another document?
>
> I don't think so.
>
> > AFAICT, if (when) NFSv5 is developed, it seems to appear to need another
> > port number. 
>
> I don't see why it would.  If there is another Rpc version of the NFS
> program,
> I don't see why the appropriate negotiation could be defined.  I think
> doing\
> that would be up to those defining nfsv5.
>
> > If that's the case (and I sincerely hope it isn't), it MUST
> > be the last one assigned to this service.
>
> I don't think "MUST" is appropriate in this case but I would say that
> assigning 
> another port would be a DAMN SHAME.
>
> On Thu, May 25, 2017 at 2:51 PM, Joe Touch <touch@isi.edu
> <mailto:touch@isi.edu>> wrote:
>
>     Hi, all,
>
>     I'd like to add one point.
>
>     This doc gives guidance on creating minor versions, but never
>     addresses
>     major versions.
>
>     IMO, past variants of NFS have not handled major version changes
>     appropriately. Each one has been assigned a new port number. This
>     is no
>     longer recommended practice (see RFC7605, Sec 7.5).
>
>     Is this issue addressed in another document?
>
>     AFAICT, if (when) NFSv5 is developed, it seems to appear to need
>     another
>     port number. If that's the case (and I sincerely hope it isn't),
>     it MUST
>     be the last one assigned to this service.
>
>     Joe
>
>


--------------AC254B0531D11EB8A41583A9
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>Hi, David,</p>
    <p>Thanks for the response, and agreed throughout.<br>
    </p>
    <p>Joe<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 5/25/2017 12:33 PM, David Noveck
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CADaq8jdWgRSqGVt0UBf3sqzp3ivYAW36y1JuNg43HGp5WboKrg@mail.gmail.com">
      <div dir="ltr"><span style="font-size:12.8px">&gt; This doc gives
          guidance on creating minor versions, but never addresses</span><br
          style="font-size:12.8px">
        <span style="font-size:12.8px">&gt; major versions.</span>
        <div><br>
        </div>
        <div>I think we had enough to do addressing minor versions and
          didn't want to</div>
        <div>speculate about a possible v5.  after all, we're the nfsv4
          working group</div>
        <div>and not the nfsvn working group.</div>
        <div><br>
          <br style="font-size:12.8px">
          <span style="font-size:12.8px">&gt; IMO, past variants of NFS
            have not handled major version changes</span><br
            style="font-size:12.8px">
          <span style="font-size:12.8px">&gt; appropriately. Each one
            has been assigned a new port number. This is no</span><br
            style="font-size:12.8px">
          <span style="font-size:12.8px">&gt; longer recommended
            practice (see RFC7605, Sec 7.5).</span><br
            style="font-size:12.8px">
          <br>
          <br>
          Makes sense.</div>
        <div><br>
          <span style="font-size:12.8px">&gt; Is this issue addressed in
            another document?</span><br style="font-size:12.8px">
          <br>
          I don't think so.</div>
        <div><br>
          <span style="font-size:12.8px">&gt; AFAICT, if (when) NFSv5 is
            developed, it seems to appear to need another</span><br
            style="font-size:12.8px">
          <span style="font-size:12.8px">&gt; port number. </span></div>
        <div><span style="font-size:12.8px"><br>
          </span></div>
        <div><span style="font-size:12.8px">I don't see why it would. 
            If there is another Rpc version of the NFS program,</span></div>
        <div><span style="font-size:12.8px">I don't see why the
            appropriate negotiation could be defined.  I think doing\</span></div>
        <div><span style="font-size:12.8px">that would be up to those
            defining nfsv5.</span></div>
        <div><span style="font-size:12.8px"><br>
          </span></div>
        <div><span style="font-size:12.8px">&gt; If that's the case (and
            I sincerely hope it isn't), it MUST</span><br
            style="font-size:12.8px">
          <span style="font-size:12.8px">&gt; be the last one assigned
            to this service.</span><br>
        </div>
        <div><br>
        </div>
        <div>I don't think "MUST" is appropriate in this case but I
          would say that assigning </div>
        <div>another port would be a DAMN SHAME.</div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Thu, May 25, 2017 at 2:51 PM, Joe
          Touch <span dir="ltr">&lt;<a href="mailto:touch@isi.edu"
              target="_blank" moz-do-not-send="true">touch@isi.edu</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi, all,<br>
            <br>
            I'd like to add one point.<br>
            <br>
            This doc gives guidance on creating minor versions, but
            never addresses<br>
            major versions.<br>
            <br>
            IMO, past variants of NFS have not handled major version
            changes<br>
            appropriately. Each one has been assigned a new port number.
            This is no<br>
            longer recommended practice (see RFC7605, Sec 7.5).<br>
            <br>
            Is this issue addressed in another document?<br>
            <br>
            AFAICT, if (when) NFSv5 is developed, it seems to appear to
            need another<br>
            port number. If that's the case (and I sincerely hope it
            isn't), it MUST<br>
            be the last one assigned to this service.<br>
            <span class="HOEnZb"><font color="#888888"><br>
                Joe<br>
              </font></span></blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------AC254B0531D11EB8A41583A9--


From nobody Thu May 25 15:43:15 2017
Return-Path: <tom@talpey.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 6DF82129BC8 for <ietf@ietfa.amsl.com>; Thu, 25 May 2017 15:43:13 -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] 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 kPQohl476KYW for <ietf@ietfa.amsl.com>; Thu, 25 May 2017 15:43:12 -0700 (PDT)
Received: from p3plsmtpa09-06.prod.phx3.secureserver.net (p3plsmtpa09-06.prod.phx3.secureserver.net [173.201.193.235]) (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 3E986127B52 for <ietf@ietf.org>; Thu, 25 May 2017 15:43:12 -0700 (PDT)
Received: from [10.137.198.25] ([131.107.147.196]) by :SMTPAUTH: with SMTP id E1QedC8pzqTuIE1QfdErrA; Thu, 25 May 2017 15:40:25 -0700
Subject: Re: [nfsv4] [art] Artart last call review of draft-ietf-nfsv4-versioning-09
To: Joe Touch <touch@isi.edu>, David Noveck <davenoveck@gmail.com>
Cc: art@ietf.org, Matthew Miller <linuxwolf+ietf@outer-planes.net>, ietf@ietf.org, draft-ietf-nfsv4-versioning.all@ietf.org, "nfsv4@ietf.org" <nfsv4@ietf.org>
References: <149462145126.13443.7366912235626631179@ietfa.amsl.com> <d64909ad-b71a-a932-606b-8b974cf68140@isi.edu> <CADaq8jdWgRSqGVt0UBf3sqzp3ivYAW36y1JuNg43HGp5WboKrg@mail.gmail.com> <d10f43d7-d136-d9b9-fcfb-dc78a52e1355@isi.edu>
From: Tom Talpey <tom@talpey.com>
Message-ID: <c3ef20a9-f96e-9b26-330a-138036943db8@talpey.com>
Date: Thu, 25 May 2017 15:40:26 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <d10f43d7-d136-d9b9-fcfb-dc78a52e1355@isi.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfFgqD0Unhil59tIg+xyBVNyA8nfVrdu/pl43zl5VLTnxYXaYTJQ5vHzUmi/HSQwbdd0rzNDK2bJmbO+7bbwkA0NNAlSuQfLhaXOfqpJaEXi/WZPeCKIC koow8ZkNj5G7Hr749yuPzogX6ls5jrMAKQEpql0mnhwcQJf8EwDntULSfGCDVdNM2hWxcikf/PITQTwHZe9V2JK3g8vlECQjgc67gAtQbrZVjzppXkYMDui7 J9frzljPjEUofnPJL1PTsed84xcdYWNSwjK2fI6sWM9ykvymW6fY+IZBAFVfxl5wmrJvqoWefOezkw9P3Gdi868HURw00/tIwYgMiAq04CB1rXJQIdLHt3B9 1jVHu9LdmBOQPiFik+8MoKU3cqff8Q==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/l9kt1hbTReKagRxa4xXZvl-FsLw>
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, 25 May 2017 22:43:13 -0000

On 5/25/2017 3:17 PM, Joe Touch wrote:
> Hi, David,
> 
> Thanks for the response, and agreed throughout.
> 
> Joe
> 
> 
> On 5/25/2017 12:33 PM, David Noveck wrote:
>> > This doc gives guidance on creating minor versions, but never addresses
>> > major versions.
>>
>> I think we had enough to do addressing minor versions and didn't want to
>> speculate about a possible v5.  after all, we're the nfsv4 working group
>> and not the nfsvn working group.
>>
>>
>> > IMO, past variants of NFS have not handled major version changes
>> > appropriately. Each one has been assigned a new port number. This is no
>> > longer recommended practice (see RFC7605, Sec 7.5).

I feel compelled to chime in on this one. NFS has always had a single
assigned port, 2049, which has not changed with major version. In the
NFSv2 days, it was self-assigned by Sun Microsystems, later, in NFSv3,
it was registered with IANA. For both versions, the RPC portmapper was
used by clients to resolve the server port.

In NFSv4, the portmapper is not used, but the port number assignment
did not change. This remains true for all NFSv4 minor versions.

There is one exception - NFS over RDMA received a new port assignment
from IANA, 20049, because the NFSv2 and NFSv3 protocols could not
negotiate the NFS/RDMA listener using legacy portmapping. While the
NFSv4.1+ versions provide a mechanism for that, the static 20049
assignment is still recommended.

Bottom line, the NFS ports are stable and registered, and there is no
need to allocate more, at least as foreseen at this time.

Tom.
>>
>>
>> Makes sense.
>>
>> > Is this issue addressed in another document?
>>
>> I don't think so.
>>
>> > AFAICT, if (when) NFSv5 is developed, it seems to appear to need another
>> > port number. 
>>
>> I don't see why it would. If there is another Rpc version of the NFS 
>> program,
>> I don't see why the appropriate negotiation could be defined.  I think 
>> doing\
>> that would be up to those defining nfsv5.
>>
>> > If that's the case (and I sincerely hope it isn't), it MUST
>> > be the last one assigned to this service.
>>
>> I don't think "MUST" is appropriate in this case but I would say that 
>> assigning
>> another port would be a DAMN SHAME.
>>
>> On Thu, May 25, 2017 at 2:51 PM, Joe Touch <touch@isi.edu 
>> <mailto:touch@isi.edu>> wrote:
>>
>>     Hi, all,
>>
>>     I'd like to add one point.
>>
>>     This doc gives guidance on creating minor versions, but never
>>     addresses
>>     major versions.
>>
>>     IMO, past variants of NFS have not handled major version changes
>>     appropriately. Each one has been assigned a new port number. This
>>     is no
>>     longer recommended practice (see RFC7605, Sec 7.5).
>>
>>     Is this issue addressed in another document?
>>
>>     AFAICT, if (when) NFSv5 is developed, it seems to appear to need
>>     another
>>     port number. If that's the case (and I sincerely hope it isn't),
>>     it MUST
>>     be the last one assigned to this service.
>>
>>     Joe
>>
>>
> 
> 
> 
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4
> 


From nobody Thu May 25 16:12:50 2017
Return-Path: <lorenzo@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 00D351292CE for <ietf@ietfa.amsl.com>; Thu, 25 May 2017 16:12:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.102
X-Spam-Level: 
X-Spam-Status: No, score=-0.102 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, 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 sYoogIBZqpzY for <ietf@ietfa.amsl.com>; Thu, 25 May 2017 16:12:46 -0700 (PDT)
Received: from mail-ua0-x22d.google.com (mail-ua0-x22d.google.com [IPv6:2607:f8b0:400c:c08::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 A2CCD128792 for <ietf@ietf.org>; Thu, 25 May 2017 16:12:46 -0700 (PDT)
Received: by mail-ua0-x22d.google.com with SMTP id y4so117667455uay.2 for <ietf@ietf.org>; Thu, 25 May 2017 16:12:46 -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=Qrv6v4C4KwmDpu4Annv2kJRQBQo6zHdS43tJQm5x3JE=; b=CbjFG55JDSlTie9/wtyXSPNxp9ntcfbQiiVo2ixUm5bkEIphLNnNnP9x7ukGKKfnu8 CduXGlH/BeBEsqix0aT+Q3q4JbGwuvrJWLRm0jipzwkHuOB7R9zfFW01LGNtVb9J7jcn UVpALKquRIiyXBxdnCxBr6HpNY6DxSf6l26/9bkf+QUivuBE3zKx4t+czIBcjd99edPK jgD/Kt4+yHp0CZVQasARv2VTQ/1ZYokKp8B2m/+1wpeCw/TDiRzzSbHiZhkTTNtgukA/ es4axyQ72HUJeTrj2mjKhxYTjDSCUSt9WwPV5gCYMiEZjrcmKs4Q2mhq+nhqH8x/cioo HCaw==
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=Qrv6v4C4KwmDpu4Annv2kJRQBQo6zHdS43tJQm5x3JE=; b=kpOKjRie6VczUcMkdlv7U2W9X8V4LstBHqRoHh8O4+EbHoS9e3pRZYkoeH67x+TvZu 9/BjBa8PqQsuKE/IndY3BwbyIntTyoG+j6uL0v3KeAzdLaRAR03HaBmkfr32gjBbsOsd oSA9Vb8pRWC7Nt9Gaw7v0Z30K9vYHPD/juAVuqjMTJB9OcMxAFX8x6Ap6mjhZfK0fUQI leBYN/komwkpQo1CvqS8NK5xdKTj9AdJiesZ/NtJzsyjaD2PVTs/aNP+x6d+MZPY118C wnEfcn5qpS7MwHV79yseXbvSeEdrkHBlv9C7uiBf8s6Vo2uDjFhNwnv2FLV+syiGV1jO ERMg==
X-Gm-Message-State: AODbwcD1v/Ho29xIke/b83NHnKP+qhXhVIOAoD9J1Rllc5cbhEI06YUz 7Sj3lGHONha4wjmN4tu43yI9KNY1LqrY
X-Received: by 10.176.95.201 with SMTP id g9mr6080035uaj.71.1495753965609; Thu, 25 May 2017 16:12:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.168.138 with HTTP; Thu, 25 May 2017 16:12:25 -0700 (PDT)
In-Reply-To: <149556850339.28443.2716896366216678645.idtracker@ietfa.amsl.com>
References: <149556850339.28443.2716896366216678645.idtracker@ietfa.amsl.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 25 May 2017 16:12:25 -0700
Message-ID: <CAKD1Yr2sd188MB-ogQQbqHkDtf4Q-5d1ZsV2fC+fsoegiMCpFA@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-unique-ipv6-prefix-per-host-03.txt> (Unique IPv6 Prefix Per Host) to Best Current Practice
To: IETF Discussion <ietf@ietf.org>
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>,  draft-ietf-v6ops-unique-ipv6-prefix-per-host.all@ietf.org
Content-Type: multipart/alternative; boundary="089e08204dd8cb05650550615b05"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/E1-afILgP3aY0K9jNfKhrcACIxI>
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, 25 May 2017 23:12:49 -0000

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

On Tue, May 23, 2017 at 12:41 PM, The IESG <iesg-secretary@ietf.org> wrote:

> The IESG has received a request from the IPv6 Operations WG (v6ops) to
> consider the following document:
> - 'Unique IPv6 Prefix Per Host'
>   <draft-ietf-v6ops-unique-ipv6-prefix-per-host-03.txt> as Best Current
> Practice
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.


 I think this is a desirable way to configure public IPv6 network access
and support the publication of this document as BCP. I see a couple issues
that probably need to be resolved before publication:

1. Off-link flag.

   If the UE/
   subscriber desires to send anything external including other UE/
   subscriber devices (assuming device to device communications is
   enabled and supported), then, due to the L-bit set, it SHOULD send
   this traffic to the First Hop Provider Router.

I think the document might need to say what the First Hop Provider Router
needs to do in the case when it the host sends the router a packet for a
destination in the same prefix as the host. (This can happen since L=0.) It
seems that the router could simply turn around and send an NS for that IPv6
address, which would likely just end up going back to the host. Seems like
we might want to avoid that.

2. If this document is to be a BCP, then the RA timers should probably not
be a part of this document. They are over-prescriptive, and they conflict
with the suggestions in RFC 7772, which says:

      In order to limit the amount of power used to receive Router
      Advertisements to, say, 2% of idle power (i.e., to impact idle
      battery life by no more than 2%), the average power budget for
      receiving RAs must be no more than 0.1 mA, or approximately 7 RAs
      per hour.

That argues for an RA interval of > 500 seconds, which is half the power
consumption of the value in this document (300 seconds).

Cheers,
Lorenzo

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, May 23, 2017 at 12:41 PM, The IESG <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:iesg-secretary@ietf.org" target=3D"_blank">iesg-secretary@ietf.org</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">The =
IESG has received a request from the IPv6 Operations WG (v6ops) to<br>
consider the following document:<br>
- &#39;Unique IPv6 Prefix Per Host&#39;<br>
=C2=A0 &lt;draft-ietf-v6ops-unique-ipv6-<wbr>prefix-per-host-03.txt&gt; as =
Best Current<br>
Practice<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action.</blockquote><div><br></div><div>=C2=A0I thin=
k this is a desirable way to configure public IPv6 network access and suppo=
rt the publication of this document as BCP. I see a couple issues that prob=
ably need to be resolved before publication:</div><div><br></div><div>1. Of=
f-link flag.</div><div><br></div><div><div>=C2=A0 =C2=A0If the UE/</div><di=
v>=C2=A0 =C2=A0subscriber desires to send anything external including other=
 UE/</div><div>=C2=A0 =C2=A0subscriber devices (assuming device to device c=
ommunications is</div><div>=C2=A0 =C2=A0enabled and supported), then, due t=
o the L-bit set, it SHOULD send</div><div>=C2=A0 =C2=A0this traffic to the =
First Hop Provider Router.</div></div><div><br></div><div>I think the docum=
ent might need to say what the First Hop Provider Router needs to do in the=
 case when it the host sends the router a packet for a destination in the s=
ame prefix as the host. (This can happen since L=3D0.) It seems that the ro=
uter could simply turn around and send an NS for that IPv6 address, which w=
ould likely just end up going back to the host. Seems like we might want to=
 avoid that.</div><div><br></div><div>2. If this document is to be a BCP, t=
hen the RA timers should probably not be a part of this document. They are =
over-prescriptive, and they conflict with the suggestions in RFC 7772, whic=
h says:</div><div><br></div><div><div>=C2=A0 =C2=A0 =C2=A0 In order to limi=
t the amount of power used to receive Router</div><div>=C2=A0 =C2=A0 =C2=A0=
 Advertisements to, say, 2% of idle power (i.e., to impact idle</div><div>=
=C2=A0 =C2=A0 =C2=A0 battery life by no more than 2%), the average power bu=
dget for</div><div>=C2=A0 =C2=A0 =C2=A0 receiving RAs must be no more than =
0.1 mA, or approximately 7 RAs</div><div>=C2=A0 =C2=A0 =C2=A0 per hour.</di=
v></div><div><br></div><div>That argues for an RA interval of &gt; 500 seco=
nds, which is half the power consumption of the value in this document (300=
 seconds).</div><div><br></div><div>Cheers,</div><div>Lorenzo</div></div></=
div></div>

--089e08204dd8cb05650550615b05--


From nobody Thu May 25 18:02:34 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 5FE76127136 for <ietf@ietfa.amsl.com>; Thu, 25 May 2017 18:02:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.711
X-Spam-Level: 
X-Spam-Status: No, score=0.711 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, 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 6dlaiJOZPqHk for <ietf@ietfa.amsl.com>; Thu, 25 May 2017 18:02:32 -0700 (PDT)
Received: from sonic318-6.consmr.mail.ir2.yahoo.com (sonic318-6.consmr.mail.ir2.yahoo.com [77.238.178.37]) (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 AFC45124E15 for <ietf@ietf.org>; Thu, 25 May 2017 18:02:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048;  t=1495760549; bh=Ra0gy8N7EAU6u466ehPq39TFt02ESXvstYqZoD6SlLc=;  h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject;  b=Nf7ZS84Ssekc9Fsx9a6KckRCFY5aaE2VYNGjzdZYQ2Ij9FKSW9ddSgdCH4VLHdXc2v9//9UkIPD/SmvknAnBrD2SeOMl0u4FVl2YKEifUmotcEySqbkicuJe7kdQhU8LDVcnRD+vME2632cW1IRtil1n8k5rj0P3oQq/2zteRSfNEmL0lCQCz1q8V0avs5CKCCVGjC83HCd6oBafQcUUztfyVuttgkXnxpdqAe+UaHazaKSu057tDhnd8pA4gkiYAKmtGPXpEufrbtW257OZQFpXEj3u0/6wTAQjHbz4eQlViGVQgOWnSk1IVom2weeU7wwD7OPkjpmxhl/w3F9qaQ==
X-YMail-OSG: .RD8SPgVM1nMXC6kEjo2d6lqsCe_hnTZMzBuUjRmR.0xZyImaXt0uH1Cz6lIlnr EBIq5CSc91zPuM4xHQPcDo9N3PIeUoAvbrCzSi.bmC4fFpBrrFyzUPnVILZkHcJ7mn0qv59cohjG nZk_h1REChcYn4V4wkk7hCahs6zjayLlhbM6gA3cU_aYkDovn63sdQ3wGUxG0kidt6UCGNa4sovp 5DDdBcOTYzJej_4ovmj4QoaC4gTV8eg3iDE_B8dAVw5I0U6Mgk_9Z0VSJ2ZxjbNXFJf9Ql09QxfZ weBJcpYmSJQg1CQJqWRkiHOBlLYNsminmzDO_1PKYVRhYKy46OHia8Z4yitF49BHF896YgAGYCrb m57eUj_YCqkOeP8JxR2FsS2cjXK00OsgQQ5ddX8S45kU4x.lhtovxk5RkZqZVsjUNSrOe8iUeaea MZlvL7fNNikB0GuOXM4LVw5pzVt4kEDd7foCmkUXPyzrgIUZAZB.giFSWIbAHssH3Bc8klL8wBcH 661bX6xt.jOa.Xfw63hPiOcDzqlMLjX5cqtanpm3nWaLa95ywTz_ZDw--
Received: from sonic.gate.mail.ne1.yahoo.com by sonic318.consmr.mail.ir2.yahoo.com with HTTP; Fri, 26 May 2017 01:02:29 +0000
Date: Fri, 26 May 2017 01:02:28 +0000 (UTC)
From: Lloyd Wood <lloyd.wood@yahoo.co.uk>
Reply-To: Lloyd Wood <lloyd.wood@yahoo.co.uk>
To: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <646071303.112849.1495760548487@mail.yahoo.com>
In-Reply-To: <AM4PR0401MB22410069BDA29D0E8FB55ABCBDF90@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <20170523050000.GW39245@kduck.kaduk.org> <AM4PR0401MB2241983F0DC82EE15E67797ABDF90@AM4PR0401MB2241.eurprd04.prod.outlook.com> <alpine.DEB.2.10.1705230842420.6571@sleekfreak.ath.cx> <AM4PR0401MB22415FCBDFC02D4C7E4EE61FBDF90@AM4PR0401MB2241.eurprd04.prod.outlook.com> <alpine.LRH.2.20.999.1705230931450.10183@bofh.nohats.ca> <AM4PR0401MB22410069BDA29D0E8FB55ABCBDF90@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Subject: Archived message removal? was Re: IPv10, KRP, and RRP IDs Removal.
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_112848_1864708725.1495760548485"
X-Mailer: WebService/1.1.9726 YahooMailNeo Mozilla/5.0 (Windows NT 6.1; Win64;  x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yNw6RoxiBXq9h_qV9HvVQc6Mgpw>
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, 26 May 2017 01:02:33 -0000

------=_Part_112848_1864708725.1495760548485
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

https://www.ietf.org/mail-archive/web/ietf/current/threads.html#102743

I see in this rather contentious KRP thread that the IETF mail=C2=A0web arc=
hive has several 'Message not available' in place ofmissing messages.
What's happening there?
thanks=C2=A0Lloyd Wood lloyd.wood@yahoo.co.uk http://about.me/lloydwood=C2=
=A0

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

<html><head></head><body><div style=3D"color:#000; background-color:#fff; f=
ont-family:Courier New, courier, monaco, monospace, sans-serif;font-size:16=
px"><div id=3D"yui_3_16_0_ym19_1_1495760451518_2971" dir=3D"ltr"><span id=
=3D"yui_3_16_0_ym19_1_1495760451518_3084"><a href=3D"https://www.ietf.org/m=
ail-archive/web/ietf/current/threads.html#102743" id=3D"yui_3_16_0_ym19_1_1=
495760451518_3083">https://www.ietf.org/mail-archive/web/ietf/current/threa=
ds.html#102743</a><br></span></div><div id=3D"yui_3_16_0_ym19_1_14957604515=
18_2971" dir=3D"ltr"><br></div><div id=3D"yui_3_16_0_ym19_1_1495760451518_2=
971" dir=3D"ltr"><span id=3D"yui_3_16_0_ym19_1_1495760451518_3001">I see in=
 this rather contentious KRP thread that the IETF mail&nbsp;</span></div><d=
iv id=3D"yui_3_16_0_ym19_1_1495760451518_2971" dir=3D"ltr"><span id=3D"yui_=
3_16_0_ym19_1_1495760451518_3005">web archive has several 'Message not avai=
lable' in place of</span></div><div id=3D"yui_3_16_0_ym19_1_1495760451518_2=
971" dir=3D"ltr"><span id=3D"yui_3_16_0_ym19_1_1495760451518_3035">missing =
messages.</span></div><div id=3D"yui_3_16_0_ym19_1_1495760451518_2971" dir=
=3D"ltr"><span><br></span></div><div id=3D"yui_3_16_0_ym19_1_1495760451518_=
2971" dir=3D"ltr"><span id=3D"yui_3_16_0_ym19_1_1495760451518_3082">What's =
happening there?</span></div><div id=3D"yui_3_16_0_ym19_1_1495760451518_297=
1" dir=3D"ltr"><span><br></span></div><div id=3D"yui_3_16_0_ym19_1_14957604=
51518_2971" dir=3D"ltr"><span>thanks</span></div><div></div><div id=3D"yui_=
3_16_0_ym19_1_1495760451518_3008">&nbsp;</div><div class=3D"signature" id=
=3D"yui_3_16_0_ym19_1_1495760451518_3027">Lloyd Wood
 lloyd.wood@yahoo.co.uk
 http://about.me/lloydwood&nbsp;</div><div class=3D"qtdSeparateBR" id=3D"yu=
i_3_16_0_ym19_1_1495760451518_3028"><br><br></div><div class=3D"yahoo_quote=
d" id=3D"yui_3_16_0_ym19_1_1495760451518_3034" style=3D"display: block;">  =
<div style=3D"font-family: Courier New, courier, monaco, monospace, sans-se=
rif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_1495760451518_3033"> <div st=
yle=3D"font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida=
 Grande, Sans-Serif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_149576045151=
8_3032"> <div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1495760451518_3031"> <fon=
t size=3D"2" face=3D"Arial" id=3D"yui_3_16_0_ym19_1_1495760451518_3030"> </=
font></div><div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_149576045=
1518_3041"><br></div> </div> </div>  </div></div></body></html>
------=_Part_112848_1864708725.1495760548485--


From nobody Thu May 25 18:22:40 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 98F8012EAF8 for <ietf@ietfa.amsl.com>; Thu, 25 May 2017 18:22:38 -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, PP_MIME_FAKE_ASCII_TEXT=0.001, 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 3R37OsKpW-UK for <ietf@ietfa.amsl.com>; Thu, 25 May 2017 18:22:37 -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 2E31E12EAFF for <ietf@ietf.org>; Thu, 25 May 2017 18:22:37 -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 565A624AE08; Fri, 26 May 2017 01:21:15 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 495B016003D; Fri, 26 May 2017 01:21:17 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 39022160048; Fri, 26 May 2017 01:21:17 +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 U_ODgXxcC21l; Fri, 26 May 2017 01:21:17 +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 E51A716003D; Fri, 26 May 2017 01:21:16 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id C573879B8334; Fri, 26 May 2017 11:21:12 +1000 (AEST)
To: Lloyd Wood <lloyd.wood@yahoo.co.uk>
Cc: "ietf@ietf.org" <ietf@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <20170523050000.GW39245@kduck.kaduk.org> <AM4PR0401MB2241983F0DC82EE15E67797ABDF90@AM4PR0401MB2241.eurprd04.prod.outlook.com> <alpine.DEB.2.10.1705230842420.6571@sleekfreak.ath.cx> <AM4PR0401MB22415FCBDFC02D4C7E4EE61FBDF90@AM4PR0401MB2241.eurprd04.prod.outlook.com> <alpine.LRH.2.20.999.1705230931450.10183@bofh.nohats.ca> <AM4PR0401MB22410069BDA29D0E8FB55ABCBDF90@AM4PR0401MB2241.eurprd04.prod.outlook.com> <646071303.112849.1495760548487@mail.yahoo.com>
Subject: Re: Archived message removal? was Re: IPv10, KRP, and RRP IDs Removal.
In-reply-to: Your message of "Fri, 26 May 2017 01:02:28 +0000." <646071303.112849.1495760548487@mail.yahoo.com>
Date: Fri, 26 May 2017 11:21:12 +1000
Message-Id: <20170526012112.C573879B8334@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/odNHXJW0rtot_Rv6om2IR-Yw5m4>
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, 26 May 2017 01:22:39 -0000

In message <646071303.112849.1495760548487@mail.yahoo.com>, Lloyd Wood writes:
>
> https://www.ietf.org/mail-archive/web/ietf/current/threads.html#102743
>
> I see in this rather contentious KRP thread that the IETF mail web
> archive has several 'Message not available' in place ofmissing messages.
> What's happening there?

There were replies to private messages that were made public by
Khaled Omar.  The missing messages are those private messages, the
presence of which is visible in the References headers.

> thanks Lloyd Wood lloyd.wood@yahoo.co.uk http://about.me/lloydwood 


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


From nobody Thu May 25 21:53:18 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 476F2126B71 for <ietf@ietfa.amsl.com>; Thu, 25 May 2017 21:53:17 -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, 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 dHMX-0aHeaLK for <ietf@ietfa.amsl.com>; Thu, 25 May 2017 21:53:14 -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 09333126557 for <ietf@ietf.org>; Thu, 25 May 2017 21:53:13 -0700 (PDT)
Received: from pps.filterd (m0098420.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v4Q4mUub022867 for <ietf@ietf.org>; Fri, 26 May 2017 00:53:11 -0400
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) by mx0b-001b2d01.pphosted.com with ESMTP id 2apbh7mb43-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 26 May 2017 00:53:11 -0400
Received: from localhost by e33.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, 25 May 2017 22:53:10 -0600
Received: from b03cxnp07029.gho.boulder.ibm.com (9.17.130.16) by e33.co.us.ibm.com (192.168.1.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 25 May 2017 22:53:08 -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 v4Q4r8vK12779982 for <ietf@ietf.org>; Thu, 25 May 2017 21:53:08 -0700
Received: from b03ledav005.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 72C3FBE03A for <ietf@ietf.org>; Thu, 25 May 2017 22:53:08 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b03ledav005.gho.boulder.ibm.com (Postfix) with ESMTPS id 599D8BE038 for <ietf@ietf.org>; Thu, 25 May 2017 22:53:08 -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 v4Q4r78o015724 for <ietf@ietf.org>; Fri, 26 May 2017 00:53:07 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v4Q4r6n0015707 for ietf@ietf.org; Fri, 26 May 2017 00:53:06 -0400
From: narten@us.ibm.com
Date: Fri, 26 May 2017 00:53:06 -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: 17052604-0008-0000-0000-000007E12973
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00007118; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000212; SDB=6.00865673; UDB=6.00429916; IPR=6.00645534;  BA=6.00005375; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00015585; XFM=3.00000015; UTC=2017-05-26 04:53:09
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17052604-0009-0000-0000-00004251F05A
Message-Id: <201705260453.v4Q4r6n0015707@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-05-26_04:, , 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-1703280000 definitions=main-1705260088
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/x4cQamDDO9g49TB20OrZwQ8ZDQQ>
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, 26 May 2017 04:53:17 -0000

Total of 57 messages in the last 7 days.
 
script run at: Fri May 26 00:53:01 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.77% |    5 | 12.97% |   104994 | daniel.migault@ericsson.com
 10.53% |    6 | 10.21% |    82684 | eng.khaled.omar@hotmail.com
  7.02% |    4 |  5.48% |    44391 | kaduk@mit.edu
  3.51% |    2 |  8.10% |    65569 | greg.hankins@nokia.com
  3.51% |    2 |  7.25% |    58729 | wangzitao@huawei.com
  3.51% |    2 |  7.04% |    57032 | wdenniss@google.com
  1.75% |    1 |  7.64% |    61843 | job@ntt.net
  3.51% |    2 |  2.56% |    20753 | worley@ariadne.com
  3.51% |    2 |  2.44% |    19749 | touch@isi.edu
  3.51% |    2 |  1.41% |    11383 | ron.even.tlv@gmail.com
  3.51% |    2 |  1.40% |    11296 | jmh@joelhalpern.com
  1.75% |    1 |  2.78% |    22520 | olivier.dornon@nokia.com
  1.75% |    1 |  1.95% |    15812 | ynir.ietf@gmail.com
  1.75% |    1 |  1.65% |    13393 | mjethanandani@gmail.com
  1.75% |    1 |  1.56% |    12671 | davenoveck@gmail.com
  1.75% |    1 |  1.55% |    12560 | lorenzo@google.com
  1.75% |    1 |  1.55% |    12549 | fielding@gbiv.com
  1.75% |    1 |  1.54% |    12435 | spencerdawkins.ietf@gmail.com
  1.75% |    1 |  1.35% |    10905 | lloyd.wood@yahoo.co.uk
  1.75% |    1 |  1.33% |    10772 | elwynd@dial.pipex.com
  1.75% |    1 |  1.33% |    10768 | bkaduk@akamai.com
  1.75% |    1 |  1.30% |    10567 | narten@us.ibm.com
  1.75% |    1 |  1.21% |     9780 | tom@talpey.com
  1.75% |    1 |  1.20% |     9707 | murch@andrew.cmu.edu
  1.75% |    1 |  1.14% |     9232 | mstjohns@comcast.net
  1.75% |    1 |  1.14% |     9206 | mrex@sap.com
  1.75% |    1 |  1.11% |     8972 | julian.reschke@gmx.de
  1.75% |    1 |  1.10% |     8937 | mnot@mnot.net
  1.75% |    1 |  1.04% |     8415 | amorris@amsl.com
  1.75% |    1 |  1.03% |     8317 | shogunx@sleekfreak.ath.cx
  1.75% |    1 |  1.00% |     8096 | davemgarrett@gmail.com
  1.75% |    1 |  0.97% |     7885 | mcr+ietf@sandelman.ca
  1.75% |    1 |  0.96% |     7808 | marka@isc.org
  1.75% |    1 |  0.86% |     6942 | fluffy@iii.ca
  1.75% |    1 |  0.76% |     6125 | stewart.bryant@gmail.com
  1.75% |    1 |  0.75% |     6058 | dromasca@gmail.com
  1.75% |    1 |  0.68% |     5490 | presnick@qti.qualcomm.com
  1.75% |    1 |  0.67% |     5395 | stefan.winter@restena.lu
--------+------+--------+----------+------------------------
100.00% |   57 |100.00% |   809740 | Total


From nobody Fri May 26 06:56:21 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 BF63A1295A0; Fri, 26 May 2017 06:56:12 -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 BJYYDOLbekoA; Fri, 26 May 2017 06:56:10 -0700 (PDT)
Received: from mail-yb0-x236.google.com (mail-yb0-x236.google.com [IPv6:2607:f8b0:4002:c09::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 5B329129557; Fri, 26 May 2017 06:56:10 -0700 (PDT)
Received: by mail-yb0-x236.google.com with SMTP id p143so2486582yba.2; Fri, 26 May 2017 06:56:10 -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=QbgESz2P5pihaesDmUyn+g7NyG0lkgY6SPwSrI7In2g=; b=PdILL1YdF7KENgyvat8Fbh8sQuCWIecnZ2TcyzPqVp2vv871UQ8bTZip0MAgG3GqAR imnenKPonQSRQc4XXwXaEbGWrQB2NYqJXnnJsBbVijsqZj9UEO6si6IrEZJAxgulkw9h thSwzTJVU3l4trd0o8MEr7NTUW499zDuXE4MmW6qP9EH25QhqH38vLT5EsTkFWQcKcrW VcbIkqA9m09M678mi22K9G01UC72pxPYGlokYrFfiCS1kC4ZoiEBa+rznPWhLOJlgsF9 71CF8zFkwDmyc/KWyHBuhdYBWEUpGECFpLcBV+hoy+yrkh+Jyvof9Q7YbbA3CSMQZDY3 eRaQ==
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=QbgESz2P5pihaesDmUyn+g7NyG0lkgY6SPwSrI7In2g=; b=LwI/e+R0FIz7JrmhjCjiyXtctNjr0gPI4QrgA4gi7BazX7klVF4ibSYdFPqZCBwv/a DgvwX3hYOM7DAl41mY0LUws9O77zW9w6JKqHN7DKVk4oqIiGE9tUgl7al8dXM1hQk2Uf a5360kzsARpnPhb7RAYNcxx0OBuw4erzw9xyLVelWrFdH9M3PGaLkjr8KQ/zOaL05WDq 3omoaThnPmFw8I9OZhLMBVu9bHakmJQt31louFUmsvvlZdsr0ktXmK8EVkNHoCp4o1QV hf2YYLZgI820ZEUespXee1hDQdOW9f5oMLaQ4yrDx7AIEwy4uNzQJk1YMWkcAjzsvowA 5+Jw==
X-Gm-Message-State: AODbwcCKGzPje4cmUx4ZxrtInXIz6ciawZ5p8khHwiK9UqtJePVU3O06 Yi2IFympVApY5UGcXly7ElJQx0FD1g==
X-Received: by 10.37.15.213 with SMTP id 204mr36918032ybp.127.1495806969674; Fri, 26 May 2017 06:56:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.195.194 with HTTP; Fri, 26 May 2017 06:56:09 -0700 (PDT)
In-Reply-To: <c3ef20a9-f96e-9b26-330a-138036943db8@talpey.com>
References: <149462145126.13443.7366912235626631179@ietfa.amsl.com> <d64909ad-b71a-a932-606b-8b974cf68140@isi.edu> <CADaq8jdWgRSqGVt0UBf3sqzp3ivYAW36y1JuNg43HGp5WboKrg@mail.gmail.com> <d10f43d7-d136-d9b9-fcfb-dc78a52e1355@isi.edu> <c3ef20a9-f96e-9b26-330a-138036943db8@talpey.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 26 May 2017 09:56:09 -0400
Message-ID: <CAKKJt-caHQ0B5bs3F4MghJ2h0BT=+vO52YRcz0uNFtw5hBiNwQ@mail.gmail.com>
Subject: Re: [nfsv4] [art] Artart last call review of draft-ietf-nfsv4-versioning-09
To: Tom Talpey <tom@talpey.com>
Cc: Joe Touch <touch@isi.edu>, David Noveck <davenoveck@gmail.com>, art@ietf.org, Matthew Miller <linuxwolf+ietf@outer-planes.net>, "ietf@ietf.org" <ietf@ietf.org>,  draft-ietf-nfsv4-versioning.all@ietf.org, "nfsv4@ietf.org" <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="001a113f5ae614861805506db374"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-nsMQH9Hu5K9dSvviLvPJD89Lmc>
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, 26 May 2017 13:56:13 -0000

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

Hi, Tom,

On Thu, May 25, 2017 at 6:40 PM, Tom Talpey <tom@talpey.com> wrote:

> On 5/25/2017 3:17 PM, Joe Touch wrote:
>
>> Hi, David,
>>
>> Thanks for the response, and agreed throughout.
>>
>> Joe
>>
>>
>> On 5/25/2017 12:33 PM, David Noveck wrote:
>>
>>> > This doc gives guidance on creating minor versions, but never addresses
>>> > major versions.
>>>
>>> I think we had enough to do addressing minor versions and didn't want to
>>> speculate about a possible v5.  after all, we're the nfsv4 working group
>>> and not the nfsvn working group.
>>>
>>>
>>> > IMO, past variants of NFS have not handled major version changes
>>> > appropriately. Each one has been assigned a new port number. This is no
>>> > longer recommended practice (see RFC7605, Sec 7.5).
>>>
>>
> I feel compelled to chime in on this one. NFS has always had a single
> assigned port, 2049, which has not changed with major version. In the
> NFSv2 days, it was self-assigned by Sun Microsystems, later, in NFSv3,
> it was registered with IANA. For both versions, the RPC portmapper was
> used by clients to resolve the server port.
>
> In NFSv4, the portmapper is not used, but the port number assignment
> did not change. This remains true for all NFSv4 minor versions.
>
> There is one exception - NFS over RDMA received a new port assignment
> from IANA, 20049, because the NFSv2 and NFSv3 protocols could not
> negotiate the NFS/RDMA listener using legacy portmapping. While the
> NFSv4.1+ versions provide a mechanism for that, the static 20049
> assignment is still recommended.
>
> Bottom line, the NFS ports are stable and registered, and there is no
> need to allocate more, at least as foreseen at this time.


Thanks for the history on port allocations, which I lacked, and I'm glad
that your answer is the right answer :-)


> Tom.
>
>>
>>>
>>> Makes sense.
>>>
>>> > Is this issue addressed in another document?
>>>
>>> I don't think so.
>>>
>>> > AFAICT, if (when) NFSv5 is developed, it seems to appear to need
>>> another
>>> > port number.
>>> I don't see why it would. If there is another Rpc version of the NFS
>>> program,
>>> I don't see why the appropriate negotiation could be defined.  I think
>>> doing\
>>> that would be up to those defining nfsv5.
>>>
>>> > If that's the case (and I sincerely hope it isn't), it MUST
>>> > be the last one assigned to this service.
>>>
>>> I don't think "MUST" is appropriate in this case but I would say that
>>> assigning
>>> another port would be a DAMN SHAME.
>>>
>>> On Thu, May 25, 2017 at 2:51 PM, Joe Touch <touch@isi.edu <mailto:
>>> touch@isi.edu>> wrote:
>>>
>>>     Hi, all,
>>>
>>>     I'd like to add one point.
>>>
>>>     This doc gives guidance on creating minor versions, but never
>>>     addresses
>>>     major versions.
>>>
>>>     IMO, past variants of NFS have not handled major version changes
>>>     appropriately. Each one has been assigned a new port number. This
>>>     is no
>>>     longer recommended practice (see RFC7605, Sec 7.5).
>>>
>>>     Is this issue addressed in another document?
>>>
>>>     AFAICT, if (when) NFSv5 is developed, it seems to appear to need
>>>     another
>>>     port number. If that's the case (and I sincerely hope it isn't),
>>>     it MUST
>>>     be the last one assigned to this service.
>>>
>>>     Joe
>>>
>>>
>>>
>>
>>
>> _______________________________________________
>> nfsv4 mailing list
>> nfsv4@ietf.org
>> https://www.ietf.org/mailman/listinfo/nfsv4
>>
>>

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

<div dir=3D"ltr">Hi, Tom,<div class=3D"gmail_extra"><br><div class=3D"gmail=
_quote">On Thu, May 25, 2017 at 6:40 PM, Tom Talpey <span dir=3D"ltr">&lt;<=
a href=3D"mailto:tom@talpey.com" target=3D"_blank">tom@talpey.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"><span class=3D"">On 5/25/201=
7 3:17 PM, Joe Touch wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi, David,<br>
<br>
Thanks for the response, and agreed throughout.<br>
<br>
Joe<br>
<br>
<br>
On 5/25/2017 12:33 PM, David Noveck wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
&gt; This doc gives guidance on creating minor versions, but never addresse=
s<br>
&gt; major versions.<br>
<br>
I think we had enough to do addressing minor versions and didn&#39;t want t=
o<br>
speculate about a possible v5.=C2=A0 after all, we&#39;re the nfsv4 working=
 group<br>
and not the nfsvn working group.<br>
<br>
<br>
&gt; IMO, past variants of NFS have not handled major version changes<br>
&gt; appropriately. Each one has been assigned a new port number. This is n=
o<br>
&gt; longer recommended practice (see RFC7605, Sec 7.5).<br>
</blockquote></blockquote>
<br></span>
I feel compelled to chime in on this one. NFS has always had a single<br>
assigned port, 2049, which has not changed with major version. In the<br>
NFSv2 days, it was self-assigned by Sun Microsystems, later, in NFSv3,<br>
it was registered with IANA. For both versions, the RPC portmapper was<br>
used by clients to resolve the server port.<br>
<br>
In NFSv4, the portmapper is not used, but the port number assignment<br>
did not change. This remains true for all NFSv4 minor versions.<br>
<br>
There is one exception - NFS over RDMA received a new port assignment<br>
from IANA, 20049, because the NFSv2 and NFSv3 protocols could not<br>
negotiate the NFS/RDMA listener using legacy portmapping. While the<br>
NFSv4.1+ versions provide a mechanism for that, the static 20049<br>
assignment is still recommended.<br>
<br>
Bottom line, the NFS ports are stable and registered, and there is no<br>
need to allocate more, at least as foreseen at this time.</blockquote><div>=
<br></div><div>Thanks for the history on port allocations, which I lacked, =
and I&#39;m glad that your answer is the right answer :-)</div><div>=C2=A0<=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">Tom.<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=
=3D"">
<br>
<br>
Makes sense.<br>
<br>
&gt; Is this issue addressed in another document?<br>
<br>
I don&#39;t think so.<br>
<br>
&gt; AFAICT, if (when) NFSv5 is developed, it seems to appear to need anoth=
er<br>
&gt; port number. <br>
I don&#39;t see why it would. If there is another Rpc version of the NFS pr=
ogram,<br>
I don&#39;t see why the appropriate negotiation could be defined.=C2=A0 I t=
hink doing\<br>
that would be up to those defining nfsv5.<br>
<br>
&gt; If that&#39;s the case (and I sincerely hope it isn&#39;t), it MUST<br=
>
&gt; be the last one assigned to this service.<br>
<br>
I don&#39;t think &quot;MUST&quot; is appropriate in this case but I would =
say that assigning<br>
another port would be a DAMN SHAME.<br>
<br></span><span class=3D"">
On Thu, May 25, 2017 at 2:51 PM, Joe Touch &lt;<a href=3D"mailto:touch@isi.=
edu" target=3D"_blank">touch@isi.edu</a> &lt;mailto:<a href=3D"mailto:touch=
@isi.edu" target=3D"_blank">touch@isi.edu</a>&gt;&gt; wrote:<br>
<br>
=C2=A0 =C2=A0 Hi, all,<br>
<br>
=C2=A0 =C2=A0 I&#39;d like to add one point.<br>
<br>
=C2=A0 =C2=A0 This doc gives guidance on creating minor versions, but never=
<br>
=C2=A0 =C2=A0 addresses<br>
=C2=A0 =C2=A0 major versions.<br>
<br>
=C2=A0 =C2=A0 IMO, past variants of NFS have not handled major version chan=
ges<br>
=C2=A0 =C2=A0 appropriately. Each one has been assigned a new port number. =
This<br>
=C2=A0 =C2=A0 is no<br>
=C2=A0 =C2=A0 longer recommended practice (see RFC7605, Sec 7.5).<br>
<br>
=C2=A0 =C2=A0 Is this issue addressed in another document?<br>
<br>
=C2=A0 =C2=A0 AFAICT, if (when) NFSv5 is developed, it seems to appear to n=
eed<br>
=C2=A0 =C2=A0 another<br>
=C2=A0 =C2=A0 port number. If that&#39;s the case (and I sincerely hope it =
isn&#39;t),<br>
=C2=A0 =C2=A0 it MUST<br>
=C2=A0 =C2=A0 be the last one assigned to this service.<br>
<br>
=C2=A0 =C2=A0 Joe<br>
<br>
<br>
</span></blockquote>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
nfsv4 mailing list<br>
<a href=3D"mailto:nfsv4@ietf.org" target=3D"_blank">nfsv4@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/nfsv4" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/nfsv4</a><br>
<br>
</blockquote>
</blockquote></div><br></div></div>

--001a113f5ae614861805506db374--


From nobody Fri May 26 08:03:19 2017
Return-Path: <amorris@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 59438129ABE for <ietf@ietfa.amsl.com>; Fri, 26 May 2017 08:03:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.302
X-Spam-Level: 
X-Spam-Status: No, score=-2.302 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, 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 2ORYZfM7R-cU for <ietf@ietfa.amsl.com>; Fri, 26 May 2017 08:03:17 -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 2E405129544 for <ietf@ietf.org>; Fri, 26 May 2017 08:03:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id CDBD31CA38A; Fri, 26 May 2017 08:03:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bWwbJSgv7_au; Fri, 26 May 2017 08:03:05 -0700 (PDT)
Received: from [10.0.1.66] (c-73-202-53-36.hsd1.ca.comcast.net [73.202.53.36]) by c8a.amsl.com (Postfix) with ESMTPA id A453E1CA388; Fri, 26 May 2017 08:03:05 -0700 (PDT)
Subject: Re: IPv10, KRP, and RRP IDs Removal.
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: text/plain; charset=us-ascii
From: Alexa Morris <amorris@amsl.com>
In-Reply-To: <AM4PR0401MB22412E60AFC1FF8709B194DDBDF90@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Date: Fri, 26 May 2017 08:03:17 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sendlaterdate: Fri, 26 May 2017 08:03:17 -0700
Message-Id: <313AD8B1-7D69-4C8C-A750-97004D26BE34@amsl.com>
References: <AM4PR0401MB2241731801FD7F70B2DD246FBDF80@AM4PR0401MB2241.eurprd04.prod.outlook.com> <alpine.OSX.2.01.1705221601010.81604@rabdullah.local> <AM4PR0401MB2241ADF8E991BF82170BFBB7BDF80@AM4PR0401MB2241.eurprd04.prod.outlook.com> <7A539F28-73E3-4CD7-9EA0-7B05AF951CF1@amsl.com> <AM4PR0401MB22412E60AFC1FF8709B194DDBDF90@AM4PR0401MB2241.eurprd04.prod.outlook.com>
To: Khaled Omar <eng.khaled.omar@hotmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tllVkC8PXR9pv1OsuM53Pg4bLnA>
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, 26 May 2017 15:03:19 -0000

Khaled,

The IESG has reviewed your request and the drafts will not be removed. =
Their response directly below:

---------
Alexa,

The drafts should not be removed. The IESG has not identified any =
unusual circumstances (e.g., mistaken claims of authorship or =
allegations of draft content violating the law) that warrant removal of =
these drafts.

Regards,
The IESG

--------
On May 22, 2017, at 5:54 PM, Khaled Omar <eng.khaled.omar@hotmail.com> =
wrote:

> As mentioned in the provided link:
>=20
> "Internet-Drafts have no formal status, and are subject to change or =
removal at any time."
>=20
>> which explains that IESG consensus is required in order to remove an =
Internet Draft from the I-D Repository.
>=20
> =46rom today's date till reaching this consensus for removal, these =
IDs shouldn't be discussed or published by the ietf on any meeting or =
any official event as the contents are not representing the ietf anymore =
after this date.
>=20
> I'm waiting for the IESG response ... I hope they can make a decision =
soon.
>=20
> "When an I-D is removed from the Public I-D Archive, a copy will be =
kept in a location accessible by the IETF Secretariat."
>=20
> This of course doesn't gives the ietf the right of making any usage of =
these I-Ds after its removal.
>=20
>=20
>=20
> -----Original Message-----
> From: Alexa Morris [mailto:amorris@amsl.com]=20
> Sent: Tuesday, May 23, 2017 2:27 AM
> To: Khaled Omar
> Cc: Ole J. Jacobsen; ietf@ietf.org
> Subject: Re: IPv10, KRP, and RRP IDs Removal.
>=20
> Khaled,
>=20
> The IESG has published a statement on this topic. Please see "IESG =
Statement on Removal of an Internet-Draft from the IETF Web Site" at =
https://www.ietf.org/iesg/statement/removal-of-an-internet-draft.html, =
which explains that IESG consensus is required in order to remove an =
Internet Draft from the I-D Repository.
>=20
> I have forwarded your email to the IESG for their review. Please be =
patient as it will take at least several days for them to review and =
respond to this request.=20
>=20
> Regards,
> Alexa
>=20
> On May 22, 2017, at 7:09 PM, Khaled Omar <eng.khaled.omar@hotmail.com> =
wrote:
>=20
>> I'm the only author of the listed IDs and they are submitted =
individually, I made this removal request and these IDs must not be =
stored on the ietf database anymore and the ietf representation must not =
exist after the request date and time which is 23rd of May, 2017 at 1:00 =
PM GMT+02:00.
>>=20
>> -----Original Message-----
>> From: Ole Jacobsen [mailto:olejacobsen@me.com]
>> Sent: Tuesday, May 23, 2017 1:02 AM
>> To: Khaled Omar
>> Subject: Re: IPv10, KRP, and RRP IDs Removal.
>>=20
>>=20
>> You really have no idea how the IETF works, do you?
>>=20
>>=20
>> On Mon, 22 May 2017, Khaled Omar wrote:
>>=20
>>> Hi Jasmine,
>>>=20
>>> As I'm the only author of the following IDs:
>>>=20
>>>=20
>>> 1) Internet Protocol version 10 (IPv10):=20
>>> https://datatracker.ietf.org/doc/draft-omar-ipv10/
>>>=20
>>>=20
>>> 2) KHALED Routing Protocol (KRP):=20
>>> https://datatracker.ietf.org/doc/draft-omar-krp/
>>>=20
>>>=20
>>> 3) Regional Routing Protocol (RRP):=20
>>> https://datatracker.ietf.org/doc/draft-omar-rrp/
>>>=20
>>>=20
>>> Please remove them all from the ietf database or repository.
>>>=20
>>> If the ideas explained on these drafts will be used, discussed or=20
>>> published by the ietf, legal actions will be taken.
>>>=20
>>> Regards,
>>>=20
>>> Khaled Omar
>>>=20
>>=20
>=20
> ----------
> Alexa Morris / Executive Director / IETF
> +1.510.492.4001
> Email: amorris@amsl.com
>=20
>=20
>=20

----------
Alexa Morris / Executive Director / IETF
+1.510.492.4001
Email: amorris@amsl.com




From nobody Fri May 26 08:39:27 2017
Return-Path: <nomcom-chair-2017@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 1BA76129413; Thu, 25 May 2017 22:25:07 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: NomCom Chair 2017 <nomcom-chair-2017@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: ietf@ietf.org
Subject: NomCom 2017-2018 Call for Volunteers
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <149577630701.8724.2136766192406951320.idtracker@ietfa.amsl.com>
Date: Thu, 25 May 2017 22:25:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iJVfh3HrrvvGnpVpx9ezdtO8bwk>
X-Mailman-Approved-At: Fri, 26 May 2017 08:39:26 -0700
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, 26 May 2017 05:25:07 -0000

The IETF NomCom appoints folks to fill the open slots on the IAOC, the IAB, and the IESG.

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

The details of the operation of the NomCom can be found in RFC 7437 (BCP 10), and RFC 3797 details the selection algorithm.

Volunteers must have attended 3 of the past 5 IETF meetings.  As specified in RFC 7437, that means three out of the five past meetings up to the time this email announcement goes out to start the solicitation of volunteers. The five meetings out of which you must have attended *three* are:

IETF = 94 (Yokohama)      \
       95 (Buenos Aires)   \
       96 (Berlin)          -*** ANY THREE!
       97 (Seoul)          /
       98 (Chicago)       /

You can check your eligibility at: https://www.ietf.org/registration/nomcom.py

If you qualify, please volunteer. Before you decide to volunteer, please remember that anyone appointed to this NomCom will not be considered as a candidate for any of the positions that the 2017 - 2018 NomCom is responsible for filling.

Many people have already volunteered by ticking the box on the IETF 98 registration form. Once these people have been verified as eligible, I will contact all of them shortly. Thank you for volunteering!

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

IAOC:

    Leslie Daigle

IAB:

    Ted Hardie
    Joe Hildebrand
    Lee Howard
    Erik Nordmark
    Martin Thomson
    Brian Trammell

IESG:

    Alia Atlas (RTG)
    Benoit Claise (OPS)
    Suresh Krishnan (INT)
    Mirja Kühlewind (TSV)
    Alexey Melnikov (ART)
    Kathleen Moriarty (SEC) 

All appointments are for 2 years. The ART and Routing areas have 3 ADs and the General area has 1; all other areas have 2 ADs. Thus, all areas have at least one continuing AD.

The primary activity for this NomCom will begin in July 2017 and should be completed in January 2018.  The NomCom will have regularly scheduled conference calls to ensure progress. There will be activities to collect requirements from the community, review candidate questionnaires, review feedback from community members about candidates, and talk to candidates.

While being a NomCom member does require some time commitment it is also a very rewarding experience.

As a member of the NomCom it is very important that you be able to attend IETF 100 (Singapore) to conduct interviews. Being at IETF 99 (Prague) is useful for orientation.  Being at IETF 101 (London) is not essential.

Please volunteer by sending me an email before 23:59 UTC June 26, 2017, as follows:

To: nomcom-chair-2017 at ietf dot org
Subject: NomCom 2017-18 Volunteer

Please include the following information in the email body:

Your Full Name: __________
    // as you write it on the IETF registration form

Current Primary Affiliation:
    // Typically what goes in the Company field
    // in the IETF Registration Form

Emails: _______________
   // All email addresses used to register for the past 5 IETF meetings
   // Preferred email address first

Telephone: _______________________
    // For confirmation if selected

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

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

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

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

Thank you!

Peter Yee
peter at akayla dot com
nomcom-chair-2017 at ietf dot org


From nobody Fri May 26 09:01:17 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 3F3D31296B3; Fri, 26 May 2017 09:00:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level: 
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, 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 OF2CSu1837Mu; Fri, 26 May 2017 09:00:52 -0700 (PDT)
Received: from mail-yb0-x229.google.com (mail-yb0-x229.google.com [IPv6:2607:f8b0:4002: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 A624612EA5A; Fri, 26 May 2017 09:00:52 -0700 (PDT)
Received: by mail-yb0-x229.google.com with SMTP id 130so3303809ybl.3; Fri, 26 May 2017 09:00: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=wwa+S03nNCYOF2RPvOLaLui+JhjJeCZusKEBQtTujRs=; b=sjZvO0AGQXybvwOtI5GjPqqn92o2aXKdrb1HYPSVgsQjENsIIhKjVLolGfzG93NoBd t+t30yUT8BznYMjcLsSFGN38Ptv1hUyIHk48JsgOyDq1P8Pt/B85qizM8UrkYlDcwfAm V7NTpdCA0w/H77k39Vwu5lyw0ml7r9xRZ8oz0f6ba6xCkJ7GMYbTk7bbvDXiYh3mVAAX MeUPnEJcaS2N8ENTjwVGB7S1TQd6BZ7ow/8sNbNu9WikCLFGFMRs49lKRFmjv9g51PP3 sjz0truRQ8M8RUeoUK72yCOudqK7fCdTFMkYwn2jXnfK4dsydIruoTd4o50+jkID3VZx iwPw==
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=wwa+S03nNCYOF2RPvOLaLui+JhjJeCZusKEBQtTujRs=; b=dfj6OL1ly5J67+1HxdWv6IL5kJS+7x569r1eyX1+1jBczT+kxi0lUctMT15ZHIQ4Zh nvDgShZQErPJY+V18qPK/zeS6aann5lFPJU9ivLNFQzjcMCCXMStaiDZTuvs/SrzaBTI l/Ir8pn4bXufbU+lyUFtJvfo1aZ7oA8VO2F5ZoZsBN7nfRwdcJ0OFRoeRE5VEMDbm/EQ dClf729+7g1V02A2V5sFi/yUAVPO1G0P67A6YOLWss2IAfFwYfffmoOgZorRg6LGhYPx y0yjl/YEccQRPSgZc3mGuCXyIvB0bI5JkcTsJ1beEGE4zw2i1wmGsqxXyQEjzol0o6vc oGoA==
X-Gm-Message-State: AODbwcA+fo0gQq2rkzqSqrdPAvj6dBKaEhYXjaByUMKq332Xm5yaoE2A LigLSa40kgh25xb2SKIlqtHEGVb50A==
X-Received: by 10.37.184.10 with SMTP id v10mr32644977ybj.82.1495814451837; Fri, 26 May 2017 09:00:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.195.194 with HTTP; Fri, 26 May 2017 09:00:51 -0700 (PDT)
In-Reply-To: <CAMm+Lwh+E+BsATQmmX6ccJou-sz1XNtFHxQZikohYCeT0qkfdQ@mail.gmail.com>
References: <CAMm+Lwh+E+BsATQmmX6ccJou-sz1XNtFHxQZikohYCeT0qkfdQ@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 26 May 2017 12:00:51 -0400
Message-ID: <CAKKJt-fsJ1UinNiW2LitxVQT4M1YqnFF+1cygU132=bQNgiUnA@mail.gmail.com>
Subject: Re: SECDIR Review of draft-ietf-nfsv4-umask-03
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: "secdir@ietf.org" <secdir@ietf.org>, draft-ietf-nfsv4-umask.all@ietf.org,  IETF Discussion Mailing List <ietf@ietf.org>, NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="089e0822e59c0d5b5e05506f719c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X8naM6WPs2HZoWkRdBa3GGt-dSQ>
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, 26 May 2017 16:00:54 -0000

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

Hi, Phillip,

(adding the NFSv4 working group mailing list, because the issue you raised
in this review is relevant to pretty much all of NFSv4)

On Thu, May 18, 2017 at 12:10 PM, Phillip Hallam-Baker <
phill@hallambaker.com> wrote:

> Reviewer:
> =E2=80=8BPhillip Hallam-Baker
>
> Review result:
> =E2=80=8BOK but...=E2=80=8B
>
>
> I 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 authors, document editors, and WG chairs should
> treat these comments just like any other IETF Last Call comments.
>
> Document: Review of draft-ietf-nfsv4-umask-03
> Reviewer:
> =E2=80=8BPhillip Hallam-Baker
>
>
>
> Review result:
> =E2=80=8BOK but...=E2=80=8B
>
>
> This particular draft looks OK to me. Aligning the semantics of NFS with
> the semantics of the file system seems to me to be absolutely the way to =
go
> forward. I am not sufficiently experienced in the semantics of NFS or Uni=
x
> as deployed to be able to offer an opinion on whether the draft achieves
> that. However it appears that the author does.
>
> =E2=80=8BWhat is problematic here is that the Security Considerations in =
the draft
> are essentially relying on those in rfc7530 which are woefully inadequate
> given the critical role of NFS in Internet security. They are not so much=
 a
> security plan as a collection of random thoughts jotted down in haphazard
> fashion.=E2=80=8B
>
> There is clearly no coherent model of what NFS security should achieve,
> what the threats are, what controls are deployed to control them. Also no=
te
> that the main reason this review is late is that I have been dealing with
> issues arising from WannaCry which used an SMB:1 exploit. Re-reading
> RFC7530 in the light of that experience gives me grave concern.
>

This is very interesting ...

Speaking as the responsible AD, I'm thinking that the right thing to do, is
for me to ask the NFSv4 working group to consider the issue you're raising,
with the high-order bit question being whether it's time to revisit NFS
security. The working group is actively discussing a recharter, likely to
be discussed in Prague, so it's the right time to ask the question.

Given that RFC 7530 is the umbrella RFC for all of NFSv4, I'm thinking
that's the right place to fix anything that needs fixing.

And thanks for your review.

Spencer

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

<div dir=3D"ltr">Hi, Phillip,<div><br></div><div>(adding the NFSv4 working =
group mailing list, because the issue you raised in this review is relevant=
 to pretty much all of NFSv4)<br><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Thu, May 18, 2017 at 12:10 PM, Phillip Hallam-Baker <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:phill@hallambaker.com" target=3D"_blan=
k">phill@hallambaker.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><div dir=3D"ltr"><span style=3D"font-size:12.8px">Reviewer:=C2=A0</sp=
an><div style=3D"display:inline">=E2=80=8BPhillip Hallam-Baker</div><br sty=
le=3D"font-size:12.8px"><span style=3D"font-size:12.8px">Review result:=C2=
=A0<div style=3D"font-size:small;display:inline">=E2=80=8BOK but...=E2=80=
=8B</div></span><br style=3D"font-size:12.8px"><br style=3D"font-size:12.8p=
x"><span style=3D"font-size:12.8px">I reviewed this document as part of the=
 Security Directorate&#39;s</span><br style=3D"font-size:12.8px"><span styl=
e=3D"font-size:12.8px">ongoing</span><br style=3D"font-size:12.8px"><span s=
tyle=3D"font-size:12.8px">effort to review all IETF documents being process=
ed by the IESG.</span><br style=3D"font-size:12.8px"><span style=3D"font-si=
ze:12.8px">These</span><br style=3D"font-size:12.8px"><span style=3D"font-s=
ize:12.8px">comments were written primarily for the benefit of the Security=
 Area</span><br style=3D"font-size:12.8px"><span style=3D"font-size:12.8px"=
>Directors.=C2=A0 Document authors, document editors, and WG chairs should<=
/span><br style=3D"font-size:12.8px"><span style=3D"font-size:12.8px">treat=
 these comments just like any other IETF Last Call comments.</span><br styl=
e=3D"font-size:12.8px"><br style=3D"font-size:12.8px"><span style=3D"font-s=
ize:12.8px">Document:=C2=A0Review of draft-ietf-nfsv4-umask-03</span><br st=
yle=3D"font-size:12.8px"><span style=3D"font-size:12.8px">Reviewer: <div st=
yle=3D"font-size:small;display:inline">=E2=80=8BPhillip Hallam-Baker</div><=
/span><br style=3D"font-size:12.8px"><br style=3D"font-size:12.8px"><br sty=
le=3D"font-size:12.8px"><span style=3D"font-size:12.8px">Review result:=C2=
=A0</span><div style=3D"display:inline">=E2=80=8BOK but...=E2=80=8B</div><b=
r><div><div style=3D"display:inline"><br></div></div><div><div style=3D"dis=
play:inline">This particular draft looks OK to me. Aligning the semantics o=
f NFS with the semantics of the file system seems to me to be absolutely th=
e way to go forward. I am not sufficiently experienced in the semantics of =
NFS or Unix as deployed to be able to offer an opinion on whether the draft=
 achieves that. However it appears that the author does.</div></div><div><d=
iv style=3D"display:inline"><br></div></div><div><div style=3D"font-size:sm=
all">=E2=80=8BWhat is problematic here is that the Security Considerations =
in the draft are essentially relying on those in rfc7530 which are woefully=
 inadequate given the critical role of NFS in Internet security. They are n=
ot so much a security plan as a collection of random thoughts jotted down i=
n haphazard fashion.=E2=80=8B</div><br></div><div><div style=3D"display:inl=
ine">There is clearly no coherent model of what NFS security should achieve=
, what the threats are, what controls are deployed to control them. Also no=
te that the main reason this review is late is that I have been dealing wit=
h issues arising from WannaCry which used an SMB:1 exploit. Re-reading RFC7=
530 in the light of that experience gives me grave concern.</div></div></di=
v></blockquote><div><br></div><div>This is very interesting ...</div><div><=
br></div><div>Speaking as the responsible AD, I&#39;m thinking that the rig=
ht thing to do, is for me to ask the NFSv4 working group to consider the is=
sue you&#39;re raising, with the high-order bit question being whether it&#=
39;s time to revisit NFS security. The working group is actively discussing=
 a recharter, likely to be discussed in Prague, so it&#39;s the right time =
to ask the question.</div><div><br></div><div>Given that RFC 7530 is the um=
brella RFC for all of NFSv4, I&#39;m thinking that&#39;s the right place to=
 fix anything that needs fixing.</div><div><br></div><div>And thanks for yo=
ur review.</div><div><br></div><div>Spencer=C2=A0</div></div></div></div></=
div>

--089e0822e59c0d5b5e05506f719c--


From nobody Fri May 26 11:13:02 2017
Return-Path: <peter@akayla.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 3BE73129B2A for <ietf@ietfa.amsl.com>; Fri, 26 May 2017 11:13:00 -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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mqIslUtWqRgS for <ietf@ietfa.amsl.com>; Fri, 26 May 2017 11:12:58 -0700 (PDT)
Received: from p3plsmtpa09-07.prod.phx3.secureserver.net (p3plsmtpa09-07.prod.phx3.secureserver.net [173.201.193.236]) (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 6FF6F129B05 for <ietf@ietf.org>; Fri, 26 May 2017 11:12:58 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by :SMTPAUTH: with SMTP id EJitdI0z5BTLFEJitdgrBo; Fri, 26 May 2017 11:12:27 -0700
From: "Peter Yee" <peter@akayla.com>
To: <ietf@ietf.org>
References: <149577630701.8724.2136766192406951320.idtracker@ietfa.amsl.com>
In-Reply-To: <149577630701.8724.2136766192406951320.idtracker@ietfa.amsl.com>
Subject: RE: NomCom 2017-2018 Call for Volunteers
Date: Fri, 26 May 2017 11:12:36 -0700
Message-ID: <040701d2d64b$a7721ad0$f6565070$@akayla.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: AQGBYqZ6ydx/+Czzbn1pIuQFJtckQ6Kp0QIA
Content-Language: en-us
X-CMAE-Envelope: MS4wfPe/9BmHpM33m/0RaVzAC1q89/gfCdX6e0NwpTXg9g2enekTticjPms27rlK8onQQx6xYzwWChr9R1vxbLdpt5N2y02zE8nCjGzwgFAgU2wkd6qJ1mqL xFCNFa3IMuEEuG+TQV1iaoWu7H5V2k22HyM=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vsAHhoUq1mBPLsIibkuoSKI7vh4>
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, 26 May 2017 18:13:00 -0000

I will note that I should have included Adam Roach's ART AD position on =
the list of open positions as well.  The 2016-2017 NomCom gave him a =
1-year position to fill out  Alissa Cooper's vacancy when she moved over =
to the IETF Chair position.  The NomCom 2017 page has been updated to =
reflect this being the case and future calls for volunteers will be =
amended as well.

		-Peter

-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of NomCom Chair 2017
Sent: Thursday, May 25, 2017 10:25 PM
To: IETF Announcement List
Cc: ietf@ietf.org
Subject: NomCom 2017-2018 Call for Volunteers

The IETF NomCom appoints folks to fill the open slots on the IAOC, the =
IAB, and the IESG.

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

The details of the operation of the NomCom can be found in RFC 7437 (BCP =
10), and RFC 3797 details the selection algorithm.

Volunteers must have attended 3 of the past 5 IETF meetings.  As =
specified in RFC 7437, that means three out of the five past meetings up =
to the time this email announcement goes out to start the solicitation =
of volunteers. The five meetings out of which you must have attended =
*three* are:

IETF =3D 94 (Yokohama)      \
       95 (Buenos Aires)   \
       96 (Berlin)          -*** ANY THREE!
       97 (Seoul)          /
       98 (Chicago)       /

You can check your eligibility at: =
https://www.ietf.org/registration/nomcom.py

If you qualify, please volunteer. Before you decide to volunteer, please =
remember that anyone appointed to this NomCom will not be considered as =
a candidate for any of the positions that the 2017 - 2018 NomCom is =
responsible for filling.

Many people have already volunteered by ticking the box on the IETF 98 =
registration form. Once these people have been verified as eligible, I =
will contact all of them shortly. Thank you for volunteering!

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

IAOC:

    Leslie Daigle

IAB:

    Ted Hardie
    Joe Hildebrand
    Lee Howard
    Erik Nordmark
    Martin Thomson
    Brian Trammell

IESG:

    Alia Atlas (RTG)
    Benoit Claise (OPS)
    Suresh Krishnan (INT)
    Mirja K=C3=BChlewind (TSV)
    Alexey Melnikov (ART)
    Kathleen Moriarty (SEC)=20

All appointments are for 2 years. The ART and Routing areas have 3 ADs =
and the General area has 1; all other areas have 2 ADs. Thus, all areas =
have at least one continuing AD.

The primary activity for this NomCom will begin in July 2017 and should =
be completed in January 2018.  The NomCom will have regularly scheduled =
conference calls to ensure progress. There will be activities to collect =
requirements from the community, review candidate questionnaires, review =
feedback from community members about candidates, and talk to =
candidates.

While being a NomCom member does require some time commitment it is also =
a very rewarding experience.

As a member of the NomCom it is very important that you be able to =
attend IETF 100 (Singapore) to conduct interviews. Being at IETF 99 =
(Prague) is useful for orientation.  Being at IETF 101 (London) is not =
essential.

Please volunteer by sending me an email before 23:59 UTC June 26, 2017, =
as follows:

To: nomcom-chair-2017 at ietf dot org
Subject: NomCom 2017-18 Volunteer

Please include the following information in the email body:

Your Full Name: __________
    // as you write it on the IETF registration form

Current Primary Affiliation:
    // Typically what goes in the Company field
    // in the IETF Registration Form

Emails: _______________
   // All email addresses used to register for the past 5 IETF meetings
   // Preferred email address first

Telephone: _______________________
    // For confirmation if selected

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

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

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

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

Thank you!

Peter Yee
peter at akayla dot com
nomcom-chair-2017 at ietf dot org



From nobody Fri May 26 12:34:36 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 6AC72129B4C for <ietf@ietfa.amsl.com>; Fri, 26 May 2017 12:34:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=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 Ez1tSw52JTa3 for <ietf@ietfa.amsl.com>; Fri, 26 May 2017 12:34:32 -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 C998A128BA2 for <ietf@ietf.org>; Fri, 26 May 2017 12:34:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 2886D3004AA for <ietf@ietf.org>; Fri, 26 May 2017 15:34:32 -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 qqHO44VuWt5G for <ietf@ietf.org>; Fri, 26 May 2017 15:34:30 -0400 (EDT)
Received: from new-host-6.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 2DC0C30029C; Fri, 26 May 2017 15:34:30 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <2FCD7FC6-1CF6-4B4B-8D2E-6043EC6FE268@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EA2DDDBE-2388-4EAD-832E-E31DE0D1D28D"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Opsdir last call review of draft-ietf-curdle-cms-ecdh-new-curves-07
Date: Fri, 26 May 2017 15:34:29 -0400
In-Reply-To: <149553176028.29418.18414274218431090509@ietfa.amsl.com>
Cc: ops-dir@ietf.org, curdle <curdle@ietf.org>, IETF <ietf@ietf.org>
To: Stefan Winter <stefan.winter@restena.lu>
References: <149553176028.29418.18414274218431090509@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2sPEpSLTnO7tYjsWhDTSSA-e7_8>
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, 26 May 2017 19:34:35 -0000

--Apple-Mail=_EA2DDDBE-2388-4EAD-832E-E31DE0D1D28D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On May 23, 2017, at 5:29 AM, Stefan Winter <stefan.winter@restena.lu> =
wrote:
>=20
> Reviewer: Stefan Winter
> Review result: Has Nits
>=20
> Nits:=20
>=20
> * 2.1 starts with "...  based on a one-way hash function described in
> ANS X9.63 [X963]." s/ANS/ANSI/

The American National Standards Institue (ANSI) is an organization.  See =
https://www.ansi.org/ <https://www.ansi.org/>.

American National Standards (ASN) are documents.  In this case, ANS =
X9.63 is being referenced.

I will expand ANS to American National Standard to avoid future =
confusion.

>=20
> * Chapter 7 defines six OIDs (secg-scheme 11 1...3 and smime-alg
> TBD1...3) and also includes the base OIDs under which these new OIDs
> are attached (secg-scheme and smime-alg). Those two are not defined in
> this document, but the text in chapter 7 suggests so.

Section 7 includes:

      secg-scheme OBJECT IDENTIFIER ::=3D {
        iso(1) identified-organization(3) certicom(132) schemes(1) }

which is followed by 3 OIDs assigned in that arc.


Section 7 also includes:

      smime-alg OBJECT IDENTIFIER ::=3D {
         iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1)
         pkcs-9(9) smime(16) alg(3) }

which is followed by three TBD OID values that need to be assigned by =
IANA once the document is approved.

> Maybe it would be a bit clearer if the text stated explicitly which of
> the OIDs in the chapter are NEW, and which ones already exist and are
> provided for reference/context.

Once IANA makes the three assignments, all of the OID values will appear =
in the RFC.

Russ


--Apple-Mail=_EA2DDDBE-2388-4EAD-832E-E31DE0D1D28D
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 May 23, 2017, at 5:29 AM, Stefan Winter &lt;<a =
href=3D"mailto:stefan.winter@restena.lu" =
class=3D"">stefan.winter@restena.lu</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">Reviewer: Stefan Winter<br class=3D"">Review result: Has =
Nits<br class=3D""><br class=3D"">Nits: <br class=3D""><br class=3D"">* =
2.1 starts with "... &nbsp;based on a one-way hash function described =
in<br class=3D"">ANS X9.63 [X963]." s/ANS/ANSI/<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>The =
American National Standards Institue (ANSI) is an organization. =
&nbsp;See&nbsp;<a href=3D"https://www.ansi.org/" =
class=3D"">https://www.ansi.org/</a>.</div><div><br =
class=3D""></div><div>American National Standards (ASN) are documents. =
&nbsp;In this case, ANS X9.63 is being referenced.</div><div><br =
class=3D""></div><div>I will expand ANS to American National Standard to =
avoid future confusion.</div><div><br class=3D""><blockquote type=3D"cite"=
 class=3D""><div class=3D""><div class=3D""><br class=3D"">* Chapter 7 =
defines six OIDs (secg-scheme 11 1...3 and smime-alg<br =
class=3D"">TBD1...3) and also includes the base OIDs under which these =
new OIDs<br class=3D"">are attached (secg-scheme and smime-alg). Those =
two are not defined in<br class=3D"">this document, but the text in =
chapter 7 suggests so.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>Section 7 includes:</div><div><br =
class=3D""></div><div><div>&nbsp; &nbsp; &nbsp; secg-scheme OBJECT =
IDENTIFIER ::=3D {</div><div>&nbsp; &nbsp; &nbsp; &nbsp; iso(1) =
identified-organization(3) certicom(132) schemes(1) }</div><div><br =
class=3D""></div><div>which is followed by 3 OIDs assigned in that =
arc.</div><div><br class=3D""></div><div><br class=3D""></div><div>Section=
 7 also includes:</div><div><br class=3D""></div><div><div>&nbsp; &nbsp; =
&nbsp; smime-alg OBJECT IDENTIFIER ::=3D {</div><div>&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;iso(1) member-body(2) us(840) rsadsi(113549) =
pkcs(1)</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;pkcs-9(9) smime(16) =
alg(3) }</div><div><br class=3D""></div><div>which is followed by three =
TBD OID values that need to be assigned by IANA once the document is =
approved.</div><div><br class=3D""></div></div><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"">Maybe it would be a bit =
clearer if the text stated explicitly which of<br class=3D"">the OIDs in =
the chapter are NEW, and which ones already exist and are<br =
class=3D"">provided for reference/context.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>Once IANA =
makes the three assignments, all of the OID values will appear in the =
RFC.</div><div><br class=3D""></div><div>Russ</div><div><br =
class=3D""></div></body></html>=

--Apple-Mail=_EA2DDDBE-2388-4EAD-832E-E31DE0D1D28D--


From nobody Fri May 26 13:12:35 2017
Return-Path: <alissa@cooperw.in>
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 B10D1129449 for <ietf@ietfa.amsl.com>; Fri, 26 May 2017 13:12:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.019
X-Spam-Level: 
X-Spam-Status: No, score=-0.019 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_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 (2048-bit key) header.d=cooperw.in header.b=BsUBkYmj; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=W6pGg7MI
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4h7unelpPIdc for <ietf@ietfa.amsl.com>; Fri, 26 May 2017 13:12: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 07EB5124281 for <ietf@ietf.org>; Fri, 26 May 2017 13:12:32 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 6BDC220A3C for <ietf@ietf.org>; Fri, 26 May 2017 16:12:31 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Fri, 26 May 2017 16:12:31 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:date:from:message-id:mime-version:subject:to :x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=Y4OB4C HGfIS6oapnOErAKPCnVsXCghNVoey0UVOBSzI=; b=BsUBkYmjNugZ4njXeH6c8h LWmIQ1EQIXScU+xq2OElbYCoHY36YoX35GL/STBhS90m9BJs0OPo/buEW6uE4feB rz7RdWEDSUz/4CBHNXWvCjYh//XfmZoThYHYJZC7IUy4s4B/tInvRJPWEf05igTd QwL2BUuvshjteDnzRS38QQ3miwSPGAbk2KfgB9W3RlsmgcExMWiXJhKc4yeUF3eL btJ2xJNBOKFXoI166WehBeu0a8RJPalWKOTllqyCcFhM/BvytZo05uw6mTNcFt87 RcnTxCgTAzwpLeKBVVK81w7LKYgJ7GJAELRJy5lIw77Q7jd15zM73XJmNvsuldqQ ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc :x-sasl-enc; s=fm1; bh=Y4OB4CHGfIS6oapnOErAKPCnVsXCghNVoey0UVOBS zI=; b=W6pGg7MIzBrgHzoQC4pSc32NW6kV6MMHe2d+f+nuA0snMJVpBpImrxN/A hYxSp1b1HYNxtir3q0hZUIV4kdY6QiBvJNk52o1co+I/2bONv8Dw+veJAakkArzX kUoeSPqEGKyc6zO68wgyPjL5NMiSIUVPaPQI5tqckRxRwQz7WNUluzecbjRlu4dZ wNm/9fkuqJ/oD5VBrLdh2MjYiJC4QHscB5MRKuR2ikDJW71V8xfqiw1nn9HTmQoZ hvJ6j1x/tAB9Vqo4kXcRrlVAt7J7advUfZg5sqKfL7lYWBs9ey5EssXnuhRinrbr NG6HTVgN3MtfmxED1BJrzEYGrhdiw==
X-ME-Sender: <xms:L4woWeoE0-wfKpEQqzM37IdodGUwtELVl3JzIXVoAQfYMvtF7zqSPw>
X-Sasl-enc: CyAFDPlzwL+PiwYNLzOkKEuqhiE+uAQTiaeO6841FPmH 1495829550
Received: from alcoop-m-mx19.fios-router.home (pool-108-48-166-97.washdc.fios.verizon.net [108.48.166.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 5ED2F241D3 for <ietf@ietf.org>; Fri, 26 May 2017 16:12:30 -0400 (EDT)
From: Alissa Cooper <alissa@cooperw.in>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1EC4A62A-6275-4416-B188-B7DBF7BF8021"
Subject: IESG Retreat
Message-Id: <E04AEAE2-3B09-4747-8B5B-BEFFA24117E1@cooperw.in>
Date: Fri, 26 May 2017 16:12:26 -0400
To: IETF Discussion <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4M9KIv3MUhl7C7TQ4fEPfhgdLBw>
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, 26 May 2017 20:12:34 -0000

--Apple-Mail=_1EC4A62A-6275-4416-B188-B7DBF7BF8021
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

The IESG held its annual retreat last week and I wrote up a short post =
about it: https://www.ietf.org/blog/2017/05/iesg-retreat-3/ =
<https://www.ietf.org/blog/2017/05/iesg-retreat-3/>

Alissa=

--Apple-Mail=_1EC4A62A-6275-4416-B188-B7DBF7BF8021
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="">The IESG held its annual retreat last week and I wrote up a short post about it:&nbsp;<a href="https://www.ietf.org/blog/2017/05/iesg-retreat-3/" class="">https://www.ietf.org/blog/2017/05/iesg-retreat-3/</a><div class=""><br class=""></div><div class="">Alissa</div></body></html>
--Apple-Mail=_1EC4A62A-6275-4416-B188-B7DBF7BF8021--


From nobody Fri May 26 13:24:42 2017
Return-Path: <suresh.krishnan@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 45DA3129449; Fri, 26 May 2017 13:24:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 UeLhbFVtV0iP; Fri, 26 May 2017 13:24:32 -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 610941287A5; Fri, 26 May 2017 13:24:32 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id l74so9442739ywe.2; Fri, 26 May 2017 13:24:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:content-transfer-encoding:mime-version:subject:message-id:date :cc:to; bh=yDhQpxaXNDjoejCEU/XULfWQbpjB9UPTOYNivIti/cg=; b=PYpE9MP/uOxLfIfzPUokABPGSgfwFnEc1bPmk30GgWbSKq/LXMLHvSW9QIQk4WWac3 6RmyMDtKP32CJNbUQc8AzKZPgfTCJMIPrkSQeUreMHQzxM0hWJMWmiLmx4BQ3fztnX3h 3JalOHOEUXeyhe7sacnxivH7ErrXvuU6DhL0Oi9EKmsXSEH3mjoU4x9JrGA51hdvTV9q jQBY3L+0xuiy6wHqT/UHFxPak6xZtlFMKf1XgmpsQb7/qTk0wqNhw1rPQRvYLsp0ZikX f1uwWa/WgIqu6XiLvx1o13685Bwkn77vri1gSHVjtuQ0lIi6qCdOGDBog9cuXKCtD9t5 nkeg==
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 :subject:message-id:date:cc:to; bh=yDhQpxaXNDjoejCEU/XULfWQbpjB9UPTOYNivIti/cg=; b=EikytL2XnU3WhOIBpnkYRF3X4uLaxVSgYyFXQRdlARSouE0BPkFCFQgP8oQ5Wz2MIK f4SYd/eNggtoJXWdmADh4wsReMmaPBgF63AcHed69CRp5MbJDhjASDUXXfvXEJwvzGhH ly1v/5ZifcDjtkcdyrZeEnVwafGt+M+AHpV5SUdGtREOkyoREEtNtNT7JoCjAClS5vYV Zm7hE1yDx0TyVCV3T0YIRR/SqJ4a8sQq1fwRxse/Nw4aUOTyx3wdOeBMsO5Uehytt/Io 252Pc/HZFb/ubNjKLzXE28vGAo3XB/QcgL09bqBFKW9C3A2RuujpMFnKdxUCVTv5h8tL jm+A==
X-Gm-Message-State: AODbwcB3MyYckFsJWkusUEL8lpJua26/vIMRyjwvaahwLZlaTUL4US9S I5A0yV3hskrT4ysngW4=
X-Received: by 10.129.82.195 with SMTP id g186mr3381533ywb.89.1495830271315; Fri, 26 May 2017 13:24:31 -0700 (PDT)
Received: from [10.0.0.2] (45-19-110-76.lightspeed.tukrga.sbcglobal.net. [45.19.110.76]) by smtp.gmail.com with ESMTPSA id k128sm1608400ywb.58.2017.05.26.13.24.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 26 May 2017 13:24:30 -0700 (PDT)
From: Suresh Krishnan <suresh.krishnan@gmail.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: Side meetings experiment at IETF 99
Message-Id: <F93ADBDA-0304-4545-8319-6600898D379E@gmail.com>
Date: Fri, 26 May 2017 16:24:32 -0400
Cc: IESG <iesg@ietf.org>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pf3iqgJIHsC0f984mBC1VE4-mBs>
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, 26 May 2017 20:24:34 -0000

Hi all,
  The IESG has discussed how to improve the path for potential new =
topics to be discussed transparently in the IETF community.  For some =
cross-area topics, it is quite useful to have active conversation among =
a group of people to work on defining the potential work and how it =
interacts with existing efforts.  As the IETF week is quite busy, it can =
be a challenge to arrange these side-meetings to avoid conflicts.  To =
facilitate the scheduling of these conversational side-meetings, the =
IESG has decided to provide a meeting room at IETF 99 in Prague for =
around 30 people, with a U-shaped table, that will be available for =
first-come first-served (FCFS) signup online as soon as the final IETF =
meeting agenda is published.  This experiment will be conducted for IETF =
99 in Prague and will replace AD approval for rooms for side-meetings =
for potential new topics. Proponents of potential new topics are =
reminded that the BoF deadline is June 2; this includes non-WG forming =
BoFs.  The on-site signup FCFS room (seats about 16) will continue to be =
available at IETF 99.

Thanks
Suresh
(on behalf of the IESG)


From nobody Fri May 26 13:24:47 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 26266129449; Fri, 26 May 2017 13:24:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 KxeEirpys1sB; Fri, 26 May 2017 13:24:33 -0700 (PDT)
Received: from mail-pf0-x242.google.com (mail-pf0-x242.google.com [IPv6:2607:f8b0:400e:c00::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81649127ABE; Fri, 26 May 2017 13:24:33 -0700 (PDT)
Received: by mail-pf0-x242.google.com with SMTP id f27so5139132pfe.0; Fri, 26 May 2017 13:24:33 -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=0+15Wnn7qCVXpCaKEserYudgwmMvNsx8/CMe5aHwyU4=; b=GrXuqEAAUNckJ4eYBi3e3Vw+fxl0AdAiesZ2tw16Xjeq34KH41BqR7JIQ7Ivk1fFoH OKZPyWFyDP9xC6jvy4OrlKNPoQWEb0L70LyeodQebqCCmXTt9pMaMvWVbTokmMF1GiBJ IuHa0mBtl/9ejSLRkDQv/AxNJzBRjRAYlxLC3xmCQhqADnazE6+VqrTcyN15vR8LsBSp cDVwrZNkvvncLcI2fet3bPwRjqkrMBqV3HJlliZT0Kur1GjxV0bkAvpVRB6cVMuowxR6 WwIF+xH0KfNv0/zCJ7yOCNE110fubx47dl0sqnnH6J6ZprXqH8+l3hlKtmVLHsiymAd3 N4uQ==
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=0+15Wnn7qCVXpCaKEserYudgwmMvNsx8/CMe5aHwyU4=; b=QK6VwY2PqB44v2X4ab8NWwM+xX8DaBsnSUUT9CZisCI0J717EkDayf8eQDdJVcK+Bf PmPYZB6y5kTcwKcv2WiN1LwDYgd5O7jtyu7m0blCHG2+vPvi58z52OdWlcQIHQKfeRet tqnpiI5iy1L8JepMQiW/y8+OLD0a0At1f1To9YbKJBGqW9I3de9jhhrUf2n8CplXDgyo K0bquQvUKxK13Y1ESBZjXk74uIwaCAOfYqoRUqQJnbxTVHjzZTCli+DTEsW+f0cLd/mE WTDzNUSw2LRDT1Pn76TBaNDBuA7GmmYzv6Lsr7YJsJDM3GIOwljblOf9O0y4ko6E8H32 Vmag==
X-Gm-Message-State: AODbwcCRsQdnkxbrBQxpQhGkcVZhbWbk4sirqnKZ9fDmWfN9ETg9v2/E Tnn2DaQW2sP6vj6u
X-Received: by 10.98.192.143 with SMTP id g15mr4427295pfk.219.1495830272874; Fri, 26 May 2017 13:24:32 -0700 (PDT)
Received: from [192.168.178.21] ([118.149.96.135]) by smtp.gmail.com with ESMTPSA id n22sm3330869pfa.123.2017.05.26.13.24.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 26 May 2017 13:24:32 -0700 (PDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-unique-ipv6-prefix-per-host-03.txt> (Unique IPv6 Prefix Per Host) to Best Current Practice
To: ietf@ietf.org
Cc: v6ops@ietf.org, draft-ietf-v6ops-unique-ipv6-prefix-per-host.all@ietf.org,  v6ops-chairs@ietf.org
References: <149556850339.28443.2716896366216678645.idtracker@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <fa82ceef-7cd6-ab37-aee6-f386266b5c56@gmail.com>
Date: Sat, 27 May 2017 08:24:39 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <149556850339.28443.2716896366216678645.idtracker@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/bQoz3f8MCgNXVDSXKDb-cDkWBaQ>
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, 26 May 2017 20:24:35 -0000

Hi,

I should have noticed this during the v6ops discussions, but I didn't,
sorry.

This draft cites RFC4862 (SLAAC) and mentions Router Advertisements
(without also citing RFC4861, which is possibly a mistake). Those
documents do not specify the subnet prefix length. So the draft
shouldn't assume a particular prefix length either. We all know that
it's usually 64 today, but that doesn't affect the argument made by
the draft. We need consistency with RFC 7608 (BCP 198).

Regards
   Brian Carpenter

On 24/05/2017 07:41, The IESG wrote:
> 
> The IESG has received a request from the IPv6 Operations WG (v6ops)
> to consider the following document: - 'Unique IPv6 Prefix Per Host' 
> <draft-ietf-v6ops-unique-ipv6-prefix-per-host-03.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-06-06.
> 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
> 
> 
> In some IPv6 environments, the need has arisen for hosts to be able 
> to utilize a unique IPv6 prefix, even though the link or media may
> be shared.  Typically hosts (subscribers) on a shared network,
> either wired or wireless, such as Ethernet, WiFi, etc., will acquire
> unique IPv6 addresses from a common IPv6 prefix that is allocated or 
> assigned for use on a specific link.
> 
> In most deployments today, IPv6 address assignment from a single
> IPv6 prefix on a shared network is done by either using IPv6
> stateless address auto-configuration (SLAAC) and/or stateful DHCPv6.
> While this is still viable and operates as designed, there are some
> large scale environments where this concept introduces significant 
> performance challenges and implications, specifically related to
> IPv6 router and neighbor discovery.
> 
> This document outlines an approach utilising existing IPv6 protocols 
> to allow hosts to be assigned a unique IPv6 prefix (instead of a 
> unique IPv6 address from a shared IPv6 prefix).  Benefits of unique 
> IPv6 prefix over a unique IPv6 address from the service provider 
> include improved subscriber isolation and enhanced subscriber 
> management.
> 
> 
> The file can be obtained via 
> https://datatracker.ietf.org/doc/draft-ietf-v6ops-unique-ipv6-prefix-per-host/
>
>  IESG discussion can be tracked via 
> https://datatracker.ietf.org/doc/draft-ietf-v6ops-unique-ipv6-prefix-per-host/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: rfc6106: IPv6 Router Advertisement
> Options for DNS Configuration (Proposed Standard - IETF stream) 
> rfc4941: Privacy Extensions for Stateless Address Autoconfiguration
> in IPv6 (Draft Standard - IETF stream) rfc4862: IPv6 Stateless
> Address Autoconfiguration (Draft Standard - IETF stream) rfc3315:
> Dynamic Host Configuration Protocol for IPv6 (DHCPv6) (Proposed
> Standard - IETF stream)
> 
> 
> 
> _______________________________________________ v6ops mailing list 
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops .
> 


From nobody Fri May 26 13:34:18 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 56493129449; Fri, 26 May 2017 13:34: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, 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 gR0S398RUGfu; Fri, 26 May 2017 13:34:08 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::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 C05BE127ABE; Fri, 26 May 2017 13:34:07 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id b84so3418002wmh.0; Fri, 26 May 2017 13:34:07 -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=9d30YLEbDdWXRUu4RllB7aWm+LL3MBmNzLm0uKBaeL4=; b=hGd2Do/mtSXqmoUVH9R0f6vu0Wn9oZla5LCHAYW0+KxmHC3yryw1NlYsDGPUZS82lu QvT424k63sbX2vhrw4zvV60T1RoBsQu1L4PCPOHpVWAGWfGl2RaZnMvoH9ZhxmmJnunC FPvWUNaY1dT/4ocb0xjOTQl+76bszPb8nAFalgXm7C4td7Raa21xACW+n54YIgY2+VI8 ak2h6T2tnknbtXvISxdfvEP/SJGCdJPSggR66MfuBpGXt6BCXKu/xR2lBpr6pouX9y1v B92idcsex9kwwG0Bk2aH597i8bBflPvLwI+sKksIU1n7gQZxcsFzYYONAVhdcRJ/b1OO HGDQ==
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=9d30YLEbDdWXRUu4RllB7aWm+LL3MBmNzLm0uKBaeL4=; b=sQZAQjDXfNPndUIi3I0IOZScsLiHaEsH1BWuqOAkUeZTwME4UEjQzH6QzuMKQaeh2Q o+CNr708SRNr1kV1jYCV6B8nPoSY/Yklhr3rrUGJLDHoVUlIQo/Z7TEMypZ6IXnOhSiO yhnZRfP/NtYYkyCnokmASorI6IseDO96OXRExqBSI6swJxHijDpiCdHV7tspQ2p4EUAE Kx+r2zQLYIt+TDqx1osBBbPRPlEkKQrarEYuFjm+4nr4v7WzLND71acWO/gvf6plPBlx AatbwnwK/wrL5OowuG7M/tIXt8Nv8Y3B5dnP5xWCFol8l4ccVWwKywv42PYbEgwRAxDM HTyw==
X-Gm-Message-State: AODbwcALHxDhjRneuE2yaWzUQ9U8yeG9FXUavekAul+KX9r6+agQuVAN Zi0ME6QnaYfNLKTqi5c=
X-Received: by 10.28.173.85 with SMTP id w82mr13758787wme.98.1495830846318; Fri, 26 May 2017 13:34:06 -0700 (PDT)
Received: from [192.168.1.18] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id m11sm4002580wmg.34.2017.05.26.13.34.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 26 May 2017 13:34:05 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <571A5927-B330-4A0F-82D4-843AAF46FD3E@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_BBCC1D12-D3D9-4A3D-B9A6-D1BCAB6E9B66"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Side meetings experiment at IETF 99
Date: Fri, 26 May 2017 23:34:02 +0300
In-Reply-To: <F93ADBDA-0304-4545-8319-6600898D379E@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>, IESG <iesg@ietf.org>
To: Suresh Krishnan <suresh.krishnan@gmail.com>
References: <F93ADBDA-0304-4545-8319-6600898D379E@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bSM8R16F2_3v9YgWEko6GlvrXrQ>
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, 26 May 2017 20:34:09 -0000

--Apple-Mail=_BBCC1D12-D3D9-4A3D-B9A6-D1BCAB6E9B66
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi, Suresh.

How is this experiment different from the sign-up room that has been =
available for the last several meetings with a sign-up sheet by the =
door?

I mean, other than making the sign-up online.

Will a sign-up room still be available, or is this experiment replacing =
that?

Thanks

Yoav

> On 26 May 2017, at 23:24, Suresh Krishnan <suresh.krishnan@gmail.com> =
wrote:
>=20
> Hi all,
>  The IESG has discussed how to improve the path for potential new =
topics to be discussed transparently in the IETF community.  For some =
cross-area topics, it is quite useful to have active conversation among =
a group of people to work on defining the potential work and how it =
interacts with existing efforts.  As the IETF week is quite busy, it can =
be a challenge to arrange these side-meetings to avoid conflicts.  To =
facilitate the scheduling of these conversational side-meetings, the =
IESG has decided to provide a meeting room at IETF 99 in Prague for =
around 30 people, with a U-shaped table, that will be available for =
first-come first-served (FCFS) signup online as soon as the final IETF =
meeting agenda is published.  This experiment will be conducted for IETF =
99 in Prague and will replace AD approval for rooms for side-meetings =
for potential new topics. Proponents of potential new topics are =
reminded that the BoF deadline is June 2; this includes non-WG forming =
BoFs.  The on-site signup FCFS room (seats about 16) will continue to be =
available at IETF 99.
>=20
> Thanks
> Suresh
> (on behalf of the IESG)
>=20


--Apple-Mail=_BBCC1D12-D3D9-4A3D-B9A6-D1BCAB6E9B66
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-----

iQEcBAEBCgAGBQJZKJE7AAoJELhJCxUKWMyZyosIAIH8ywYCS4X+4YKlXBKvBOom
7nGxH876JbAhkmRekuxq4AJXROOUdUKsRIxPN4IruQ3iM9FVjrgaTXBSJCtsS+zz
xWzUDFZm8Ds+LMQD0DZqwM/bvutFV79KoHsHLZwrZNuCoLj4T8F+fU+6/QVCOfCs
6iso/i9WP6ylkBrU9fCxYOvfZADAjsXstEHGOPSSed3wKEkGNNyLsqi85vRzaOjo
Jnlw9W34axtK4uPaNtCKDzQOMjuusA/oalZjxoOixj8xQjV9qQXRPUKoAQI3ULTo
bFzXj6VMBC2s6upuj2nJolY6OMPAxFFTTHETuxx4FhxxMFnu/XodsIzss5rqLbo=
=qf3C
-----END PGP SIGNATURE-----

--Apple-Mail=_BBCC1D12-D3D9-4A3D-B9A6-D1BCAB6E9B66--


From nobody Fri May 26 13:38:10 2017
Return-Path: <chair@ietf.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 3C95512954E for <ietf@ietfa.amsl.com>; Fri, 26 May 2017 13:38:09 -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=[ALL_TRUSTED=-1, BAYES_40=-0.001, HTML_MESSAGE=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 xHiNoOrkj7Lw for <ietf@ietfa.amsl.com>; Fri, 26 May 2017 13:38:07 -0700 (PDT)
Received: from alcoop-m-mx19.fios-router.home (pool-108-48-166-97.washdc.fios.verizon.net [108.48.166.97]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 9FF9B129449 for <ietf@ietf.org>; Fri, 26 May 2017 13:38:07 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7A6A1ABE-0D62-46AA-AE57-61A1310B67DE"
Subject: BOF proposals due June 2
Message-Id: <3675C50B-2C41-4483-BEE3-FD509D3FE0F4@ietf.org>
Date: Fri, 26 May 2017 16:38:04 -0400
To: IETF Discussion <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mw66TYvYu4cPhUnhzmy8872L7CM>
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, 26 May 2017 20:38:09 -0000

--Apple-Mail=_7A6A1ABE-0D62-46AA-AE57-61A1310B67DE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I wanted to remind everyone that the deadline for submitting proposals =
for "Birds of a Feather=E2=80=9D (BOF) sessions at IETF 99 is in one =
week: June 2 at 23:59 . Instructions for submitting your proposal are =
available at https://ietf.org/iesg/bof-procedures.html =
<https://ietf.org/iesg/bof-procedures.html>. Please also read =
https://tools.ietf.org/html/rfc5434 =
<https://tools.ietf.org/html/rfc5434>, Considerations for Having a =
Successful Birds-of-a-Feather Session, if you are not familiar with it.

We have a number of ways of bringing new work into the IETF and BOFs are =
just one of them, so please talk to an area director =
(https://ietf.org/iesg/members.html =
<https://ietf.org/iesg/members.html>) about your idea if you=E2=80=99re =
thinking about proposing a BOF.

As the IESG recently noted =
(https://mailarchive.ietf.org/arch/msg/ietf/pf3iqgJIHsC0f984mBC1VE4-mBs =
<https://mailarchive.ietf.org/arch/msg/ietf/pf3iqgJIHsC0f984mBC1VE4-mBs>),=
 we will be experimenting at IETF 99 with a side meeting room available =
with first-come first-served advance online sign-up, rather than using =
area director approval for allocation of rooms for side meetings. If you =
were already thinking about asking for AD approval for a side meeting =
room, please get in touch with an area director to discuss the FCFS =
room, a non-WG-forming BOF proposal, or other options.

Alissa Cooper
IETF Chair=

--Apple-Mail=_7A6A1ABE-0D62-46AA-AE57-61A1310B67DE
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"">I wanted to remind everyone that the deadline for submitting =
proposals for&nbsp;"Birds of a Feather=E2=80=9D (BOF) sessions at IETF =
99 is in one week: June 2 at 23:59 . Instructions for submitting your =
proposal are available at&nbsp;<a =
href=3D"https://ietf.org/iesg/bof-procedures.html" =
class=3D"">https://ietf.org/iesg/bof-procedures.html</a>. Please also =
read&nbsp;<a href=3D"https://tools.ietf.org/html/rfc5434" =
class=3D"">https://tools.ietf.org/html/rfc5434</a>,&nbsp;Considerations =
for Having a Successful Birds-of-a-Feather Session, if you are not =
familiar with it.<div class=3D""><br class=3D""></div><div class=3D""><div=
 class=3D"">We have a number of ways of bringing new work into the IETF =
and BOFs are just one of them, so please talk to an area director (<a =
href=3D"https://ietf.org/iesg/members.html" =
class=3D"">https://ietf.org/iesg/members.html</a>) about your idea if =
you=E2=80=99re thinking about proposing a BOF.</div><div class=3D""><br =
class=3D""></div><div class=3D"">As the IESG recently noted (<a =
href=3D"https://mailarchive.ietf.org/arch/msg/ietf/pf3iqgJIHsC0f984mBC1VE4=
-mBs" =
class=3D"">https://mailarchive.ietf.org/arch/msg/ietf/pf3iqgJIHsC0f984mBC1=
VE4-mBs</a>), we will be experimenting at IETF 99 with a side meeting =
room available with first-come first-served advance online sign-up, =
rather than using area director approval for allocation of rooms for =
side meetings. If you were already thinking about asking for AD approval =
for a side meeting room, please get in touch with an area director to =
discuss the FCFS room, a non-WG-forming BOF proposal, or other =
options.</div><div class=3D""><br class=3D"">Alissa =
Cooper</div></div><div class=3D"">IETF Chair</div></body></html>=

--Apple-Mail=_7A6A1ABE-0D62-46AA-AE57-61A1310B67DE--


From nobody Fri May 26 14:31:26 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 4C64012773A; Fri, 26 May 2017 14:31:19 -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 N5NpvMH9OABd; Fri, 26 May 2017 14:31:18 -0700 (PDT)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::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 CED13128B4E; Fri, 26 May 2017 14:31:17 -0700 (PDT)
Received: by mail-wm0-x236.google.com with SMTP id e127so4521641wmg.1; Fri, 26 May 2017 14:31: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=pxGAWLCs94q9HUkYkGUqMnRAEYpFYxmkDJwxN2UPZ9A=; b=fiH6NPOY7WS5An8UPhL2wJI1EoR+iPVBM72+05Uu+GeNqP7c9IVip5TaI5DB9iWYlN RqjOpLdQsuL04iXezpsuq2as7fqbSIGo9ejJMRIWzAEtx8IfI4Uz0BlbHQ8K5Pwci/or dr1gNV23g7wVpXAmACOBLedONrGw+qKJAyICAJO858XJeMBt3UEoso82H7t4+WwvK6Bz nltt1wpz0FQJ0jkm50NmmRUL3+/4NTp/nsp2UPrlwICl38fXcxh8jTPn5MxQplLiXW/P 5IEISLcqxPqPlv4+FZlJbvEcTiIxLmZesX3RkmfgIuiFCaHVaMS0s6iemmA3D2Sn9Gpv NOxg==
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=pxGAWLCs94q9HUkYkGUqMnRAEYpFYxmkDJwxN2UPZ9A=; b=JzPBYnbH64Ns/YeUrALaKP1xN7T6ltlzze9PZMG+r1zgeX3hY0yv0EcYw6iy3zM57W tscYfIHX+aLs7DxA9Ape0ZzyP3JpgibLthLIE7kgUxCQIkDV7nlt1eLak5YdwBP1twPW h+MOqleZ60o+3hD/XVfA4k3JGmox7q2YAhjmFu+ssy0Ptuf39aq4NnWzqnod0c9AhcfP MT67Je++o72iqMMnWBf0PgzusSDC/A7E9xiulwFYWTv+dLpt2vnZfAyVp2f21BBZ7CvC QKh38/XIq2evL98dnJSgg5onL7eZ0buYMCT3zj1emJqeAsgGFBPE/VmFYS0zVFt90RgV Jj6w==
X-Gm-Message-State: AODbwcAunmRSZK5V+TyCGW/OuVz8NJVhKcLgIggzKJqR2mFfMxqbhKXN 8TgmmDVHWw4MiuI8srUxwpz+TUmiHQea
X-Received: by 10.28.209.141 with SMTP id i135mr13898213wmg.123.1495834276089;  Fri, 26 May 2017 14:31:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.135.86 with HTTP; Fri, 26 May 2017 14:31:15 -0700 (PDT)
In-Reply-To: <571A5927-B330-4A0F-82D4-843AAF46FD3E@gmail.com>
References: <F93ADBDA-0304-4545-8319-6600898D379E@gmail.com> <571A5927-B330-4A0F-82D4-843AAF46FD3E@gmail.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Fri, 26 May 2017 17:31:15 -0400
Message-ID: <CAG4d1re7T96WnQKyn0eyXJLnejnKfE3GtyjMdeYA0OKxrZ=pRg@mail.gmail.com>
Subject: Re: Side meetings experiment at IETF 99
To: Yoav Nir <ynir.ietf@gmail.com>
Cc: Suresh Krishnan <suresh.krishnan@gmail.com>, IETF Discussion <ietf@ietf.org>, IESG <iesg@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c13055aab75a20550740e2f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xp65PfWAlCqLL6dnKHt-W49kRo4>
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, 26 May 2017 21:31:19 -0000

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

Yoav,

As indicated in Suresh's email, the existing on-site FCFS room that holds
around 16 people will continue to be
available.  There will also be a room that holds about 30 people, in a
U-shape, that will be available for sign-ups
a couple weeks before IETF (when the IETF agenda comes out).

Does that help clarify?

Regards,
Alia

On Fri, May 26, 2017 at 4:34 PM, Yoav Nir <ynir.ietf@gmail.com> wrote:

> Hi, Suresh.
>
> How is this experiment different from the sign-up room that has been
> available for the last several meetings with a sign-up sheet by the door?
>
> I mean, other than making the sign-up online.
>
> Will a sign-up room still be available, or is this experiment replacing
> that?
>
> Thanks
>
> Yoav
>
> > On 26 May 2017, at 23:24, Suresh Krishnan <suresh.krishnan@gmail.com>
> wrote:
> >
> > Hi all,
> >  The IESG has discussed how to improve the path for potential new topics
> to be discussed transparently in the IETF community.  For some cross-area
> topics, it is quite useful to have active conversation among a group of
> people to work on defining the potential work and how it interacts with
> existing efforts.  As the IETF week is quite busy, it can be a challenge to
> arrange these side-meetings to avoid conflicts.  To facilitate the
> scheduling of these conversational side-meetings, the IESG has decided to
> provide a meeting room at IETF 99 in Prague for around 30 people, with a
> U-shaped table, that will be available for first-come first-served (FCFS)
> signup online as soon as the final IETF meeting agenda is published.  This
> experiment will be conducted for IETF 99 in Prague and will replace AD
> approval for rooms for side-meetings for potential new topics. Proponents
> of potential new topics are reminded that the BoF deadline is June 2; this
> includes non-WG forming BoFs.  The on-site signup FCFS room (seats about
> 16) will continue to be available at IETF 99.
> >
> > Thanks
> > Suresh
> > (on behalf of the IESG)
> >
>
>

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

<div dir=3D"ltr">Yoav,<div><br></div><div>As indicated in Suresh&#39;s emai=
l, the existing on-site FCFS room that holds around 16 people will continue=
 to be</div><div>available.=C2=A0 There will also be a room that holds abou=
t 30 people, in a U-shape, that will be available for sign-ups</div><div>a =
couple weeks before IETF (when the IETF agenda comes out).</div><div><br></=
div><div>Does that help clarify?</div><div><br></div><div>Regards,</div><di=
v>Alia</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"=
>On Fri, May 26, 2017 at 4:34 PM, Yoav Nir <span dir=3D"ltr">&lt;<a href=3D=
"mailto:ynir.ietf@gmail.com" target=3D"_blank">ynir.ietf@gmail.com</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">Hi, Suresh.<br>
<br>
How is this experiment different from the sign-up room that has been availa=
ble for the last several meetings with a sign-up sheet by the door?<br>
<br>
I mean, other than making the sign-up online.<br>
<br>
Will a sign-up room still be available, or is this experiment replacing tha=
t?<br>
<br>
Thanks<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Yoav<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; On 26 May 2017, at 23:24, Suresh Krishnan &lt;<a href=3D"mailto:suresh=
.krishnan@gmail.com">suresh.krishnan@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi all,<br>
&gt;=C2=A0 The IESG has discussed how to improve the path for potential new=
 topics to be discussed transparently in the IETF community.=C2=A0 For some=
 cross-area topics, it is quite useful to have active conversation among a =
group of people to work on defining the potential work and how it interacts=
 with existing efforts.=C2=A0 As the IETF week is quite busy, it can be a c=
hallenge to arrange these side-meetings to avoid conflicts.=C2=A0 To facili=
tate the scheduling of these conversational side-meetings, the IESG has dec=
ided to provide a meeting room at IETF 99 in Prague for around 30 people, w=
ith a U-shaped table, that will be available for first-come first-served (F=
CFS) signup online as soon as the final IETF meeting agenda is published.=
=C2=A0 This experiment will be conducted for IETF 99 in Prague and will rep=
lace AD approval for rooms for side-meetings for potential new topics. Prop=
onents of potential new topics are reminded that the BoF deadline is June 2=
; this includes non-WG forming BoFs.=C2=A0 The on-site signup FCFS room (se=
ats about 16) will continue to be available at IETF 99.<br>
&gt;<br>
&gt; Thanks<br>
&gt; Suresh<br>
&gt; (on behalf of the IESG)<br>
&gt;<br>
<br>
</div></div></blockquote></div><br></div>

--94eb2c13055aab75a20550740e2f--


From nobody Fri May 26 18:34:03 2017
Return-Path: <mglt.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 D48C9129B74; Fri, 26 May 2017 18:33:47 -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 W19sB5B902U8; Fri, 26 May 2017 18:33:46 -0700 (PDT)
Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::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 DE94312940F; Fri, 26 May 2017 18:33:42 -0700 (PDT)
Received: by mail-lf0-x233.google.com with SMTP id a5so13490855lfh.2; Fri, 26 May 2017 18:33:42 -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=i1nmYy1+l1o03GPXGopcgyBKuHr8MADo1MiSwXgLlFw=; b=hfjAu/iFj2wr2IK6m1b1qZmZn1mesZnCYU+Zk5SyH8MuYUT0+ac1LAldzXlw+u6rn6 qo3P+NprxlfbjyAdyDxcK9ij4lNVej36nfWVTfycZA5wUeAz8q/6wjsHA5eTc/R0hDme 0w+jE3YkBV0ShFHfQ7JJ5Nf7i+d3RQrmvt9f1lzCpuEN4hjQYYOylwP2N4HMBOt3Jc95 CEg2OUO2Df+o6EdueEPe4s9TmHHT6waoGyZCRSwh9I5r1EpDc8WUPlfmX7berZFCOC87 3DPjlOW4i2AUwb+12hDOoh0OrYjuDc+t94nKxyGEE/On9vBtjX4J/2l0iC/0OGz/YZXB nDCQ==
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=i1nmYy1+l1o03GPXGopcgyBKuHr8MADo1MiSwXgLlFw=; b=SKx1XCuS1qbINKDNGhoVjvGEmhhWgvufRRzV1nrMXVsiwZc4YK/zFHL2V8if0Avd17 6rrfyNcwz9zP1oz53VDeNChjWJTZF71kVa2aPQ2kJddfX+mdTzvCuUbyu/T6wVTsF9LO xxiedopmDyf3E4g6UuajCXIKlfSq5tlmq99aj/gdUk3XA4Rj0N8ErzGl0LvH6P8DxwBc ugCb08LUmqKYM0qdh63BgYY0GpbQtFlNjrJ2Kni5S9zdnKCDLulX0vPemBx/lBLJqQnl FYv3BQnj326rm0IymW7rhUb3usja4nnMsEtDdxSd7SLKU/cO4MDEGdAqU7cJkIYLwCky nEHA==
X-Gm-Message-State: AODbwcCXspQo5dxcF1RFcQMB/0OXF7gOpbs1+JidhP60OSeUrl+Q09P5 GvPA4TzlSN5YiN2Iwo/eidt6o76s9g==
X-Received: by 10.25.104.5 with SMTP id d5mr1484330lfc.147.1495848821228; Fri, 26 May 2017 18:33:41 -0700 (PDT)
MIME-Version: 1.0
Sender: mglt.ietf@gmail.com
Received: by 10.46.0.14 with HTTP; Fri, 26 May 2017 18:33:40 -0700 (PDT)
In-Reply-To: <149570983670.8681.5001417855088402577@ietfa.amsl.com>
References: <149570983670.8681.5001417855088402577@ietfa.amsl.com>
From: Daniel Migault <daniel.migault@ericsson.com>
Date: Fri, 26 May 2017 21:33:40 -0400
X-Google-Sender-Auth: BsW1gIuTArfSwfSzWZ7rcgrTqZc
Message-ID: <CADZyTkkjsWSJtBQAH8XnKDWLLdd219U4aq+TqLaSMW=Ay=fLmw@mail.gmail.com>
Subject: Re: [Curdle] Genart last call review of draft-ietf-curdle-cms-ecdh-new-curves-07
To: Roni Even <ron.even.tlv@gmail.com>
Cc: "gen-art >> General area reviewing team" <gen-art@ietf.org>, draft-ietf-curdle-cms-ecdh-new-curves.all@ietf.org,  curdle <curdle@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f403045e589ca08b9f05507771bf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/COztYRoKdW-vZCcx32Go-FFB2GU>
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, 27 May 2017 01:33:48 -0000

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

Thank you Roni for the review.
Yours,
Daniel

On Thu, May 25, 2017 at 6:57 AM, Roni Even <ron.even.tlv@gmail.com> wrote:

> 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-curdle-cms-ecdh-new-curves-??
> Reviewer: Roni Even
> Review Date: 2017-05-25
> IETF LC End Date: 2017-05-28
> IESG Telechat date: Not scheduled for a telechat
>
> Summary:
> The document is ready for publication as a standard track RFC
>
> Major issues:
>
> Minor issues:
>
> Nits/editorial comments:
>
> In general it was easy to read and follow.  Maybe it will be good to
> repeat in section 3.2 the definition of KeyAgreeRecipientInfo . This
> is done is section 2 for ECC-CMS-SharedInfo but it is not crucial.
>
> 1. There is no ToC
> 2. In section 2.2 fourth paragraph "is used two places" - "in two .."
>
>
>
>
>
> _______________________________________________
> Curdle mailing list
> Curdle@ietf.org
> https://www.ietf.org/mailman/listinfo/curdle
>

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

<div dir=3D"ltr"><div><div>Thank you Roni for the review.<br></div>Yours, <=
br></div>Daniel<br></div><div class=3D"gmail_extra"><br><div class=3D"gmail=
_quote">On Thu, May 25, 2017 at 6:57 AM, Roni Even <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:ron.even.tlv@gmail.com" target=3D"_blank">ron.even.tlv@gmai=
l.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Reviewer: Ron=
i Even<br>
Review result: Ready with Nits<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-curdle-cms-ecdh-<wbr>new-curves-??<br>
Reviewer: Roni Even<br>
Review Date: 2017-05-25<br>
IETF LC End Date: 2017-05-28<br>
IESG Telechat date: Not scheduled for a telechat<br>
<br>
Summary:<br>
The document is ready for publication as a standard track RFC<br>
<br>
Major issues:<br>
<br>
Minor issues:<br>
<br>
Nits/editorial comments:<br>
<br>
In general it was easy to read and follow.=C2=A0 Maybe it will be good to<b=
r>
repeat in section 3.2 the definition of KeyAgreeRecipientInfo . This<br>
is done is section 2 for ECC-CMS-SharedInfo but it is not crucial.<br>
<br>
1. There is no ToC<br>
2. In section 2.2 fourth paragraph &quot;is used two places&quot; - &quot;i=
n two ..&quot;<br>
<br>
<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
Curdle mailing list<br>
<a href=3D"mailto:Curdle@ietf.org">Curdle@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/curdle" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/curdle</a><br=
>
</blockquote></div><br></div>

--f403045e589ca08b9f05507771bf--


From nobody Fri May 26 19:44:08 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 5792912E03F; Fri, 26 May 2017 19:44:01 -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, RP_MATCHES_RCVD=-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 r6jBjdlVZqhO; Fri, 26 May 2017 19:43:59 -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 DFDBB120727; Fri, 26 May 2017 19:43:58 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dERht-00070x-6E; Fri, 26 May 2017 22:43:57 -0400
Date: Fri, 26 May 2017 22:43:52 -0400
From: John C Klensin <john-ietf@jck.com>
To: Alia Atlas <akatlas@gmail.com>, Yoav Nir <ynir.ietf@gmail.com>
cc: IETF Discussion <ietf@ietf.org>, IESG <iesg@ietf.org>
Subject: Re: Side meetings experiment at IETF 99
Message-ID: <0CA30B5E7BF2617910B438AE@PSB>
In-Reply-To: <CAG4d1re7T96WnQKyn0eyXJLnejnKfE3GtyjMdeYA0OKxrZ=pRg@mail.gmail.com>
References: <F93ADBDA-0304-4545-8319-6600898D379E@gmail.com> <571A5927-B330-4A0F-82D4-843AAF46FD3E@gmail.com> <CAG4d1re7T96WnQKyn0eyXJLnejnKfE3GtyjMdeYA0OKxrZ=pRg@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YGYLsCWA147dZVTxscMJYMOtH8M>
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, 27 May 2017 02:44:01 -0000

--On Friday, May 26, 2017 17:31 -0400 Alia Atlas
<akatlas@gmail.com> wrote:

> Yoav,
> 
> As indicated in Suresh's email, the existing on-site FCFS room
> that holds around 16 people will continue to be
> available.  There will also be a room that holds about 30
> people, in a U-shape, that will be available for sign-ups
> a couple weeks before IETF (when the IETF agenda comes out).
> 
> Does that help clarify?

It does, but let me note three things for whatever they might be
worth:

(1) <rant> Suresh's description of these informal meetings match
reasonably closely something we did in the distant past.  It was
calls a "BOF".  Over the years, that concept of a BOF as a
relatively informal session for discussion of new ideas and
other things that were not ready for WG charters, morphed into
very formal arrangements requiring formal proposals more than
six weeks in advance of IETF meetings and approval by the IESG
and advice from the IAB.   People dealt with that problem with
formally organized Bar BOFs, a combination that would have been
considered an oxymoron when BOFs were more informal gatherings,
which led to requests for meeting rooms for side meetings and
now sign-up arrangements for those meeting rooms.</rant>  

(2) I believe there was at least one "informal side meeting" in
Chicago that wanted video remote participation arrangements, so
let me ask the question in advance: will this room be set up for
Meetecho and, if not, why not?   Is it time for the IESG to
rethink how we do this and why we seem to need to move in
directions of more and more Procedures, rather than just walking
across (or down) slippery slopes? 

(3) For those who are concerned about where we meet and what the
constraints are on locations, it may be worth noting that, for
at least some facilities, the number of small to medium-sized
meeting rooms we now require for one or two official
side-meeting spaces, plus rooms for IESG, IAB, Nomcom, IAD,
IOAC, ISOC, Secretariat work space, etc., may be as much of a
constraint as spaces for parallel WG sessions.

Grumpily,
   john


From nobody Fri May 26 20:16:27 2017
Return-Path: <melinda.shore@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 F336F12EA95 for <ietf@ietfa.amsl.com>; Fri, 26 May 2017 20:16:26 -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 gWda3f-nPPWq for <ietf@ietfa.amsl.com>; Fri, 26 May 2017 20:16:25 -0700 (PDT)
Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::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 4887312EA81 for <ietf@ietf.org>; Fri, 26 May 2017 20:16:25 -0700 (PDT)
Received: by mail-pf0-x22f.google.com with SMTP id e193so25073346pfh.0 for <ietf@ietf.org>; Fri, 26 May 2017 20:16:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=j8GlaM/6ZmzAStheoxhqP1lwYCteqOFKjRYAMxOg98U=; b=kzCMQ2kaM1L/m+WVtUWQB3ptUGTv9f3ecHqeaAzRnyaunpoD/CzWkUe41HJmRA1KNz LQpFHO+lVOMlmM7hUA/231GP7Or41lbLTRXU6sZ/Y8kheZw09+zgOywxSy7gk3DnRKic T6GzkroQE/Ej88Tpn0K52mEjSdvzYci6MkO4R1dlKhZgz3xFkkO6XY5rcp7Cee8rTrp5 G8uOHw+vWbCoaFug9tAemMR+gzrP7ZJf3iwiNcqVNZTnH7BLqv/zuyPUToDz4krky/Ww luAdRXIOdefPQT2c9+qeYr0lyg9SKCYML1FaFqpr+XRoY/3Nl/KCAEUUcDR8hiGgfwuv n8Ww==
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; bh=j8GlaM/6ZmzAStheoxhqP1lwYCteqOFKjRYAMxOg98U=; b=AxmqY9g+ccX7oeOoRSM8Yf6dqUUNrPL0WdRlPQi9lpWZTj0CBsVEOzXFmZ9eRZ5z39 UNa5shp1poDVMme5xSAKfYK3OgdufbK5vfnrjCyYYwtA13HeGChxWfF468mnf1ifY0oZ 47vZVfMZvw+llu9whpmsXAyj47dSpL0O65Ob3lc1JKRjDMRtd8A7V7IqY/tRhQ1lQNbw SRccOZEZEITFcsHuIHIhmdmAEXJnDQDG5IxIyOq1sdO+3MlmkjMjt2Tf0AWKtj1vdu0A a+nKcnu57BeDZvGrjxSRbUfNiKgb+6QFzJHfnzgj/Av5VqZDqU93XCmCvFdgyxsCxJeA EIFg==
X-Gm-Message-State: AODbwcDjQ6coP1OK6wHdGx3VtcSuKqIy7p1Hhyvf8SfkxjMTQSGGoftW DyL9xWWIgN+m7Jq6
X-Received: by 10.84.202.163 with SMTP id x32mr62188816pld.51.1495854984682; Fri, 26 May 2017 20:16:24 -0700 (PDT)
Received: from Melindas-Mac-mini.local (216-67-78-84-radius.dynamic.acsalaska.net. [216.67.78.84]) by smtp.gmail.com with ESMTPSA id m5sm4474915pgd.28.2017.05.26.20.16.22 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 26 May 2017 20:16:23 -0700 (PDT)
Subject: Re: Side meetings experiment at IETF 99
To: ietf@ietf.org
References: <F93ADBDA-0304-4545-8319-6600898D379E@gmail.com> <571A5927-B330-4A0F-82D4-843AAF46FD3E@gmail.com> <CAG4d1re7T96WnQKyn0eyXJLnejnKfE3GtyjMdeYA0OKxrZ=pRg@mail.gmail.com> <0CA30B5E7BF2617910B438AE@PSB>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <58583b21-6552-53c1-08cc-da7a9714ad93@gmail.com>
Date: Fri, 26 May 2017 19:16:20 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <0CA30B5E7BF2617910B438AE@PSB>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="F5kHS9j8QIM1KeK27M44pARuuhvECJDhE"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/m4i_yAH44pELNB_CGi3coxsF1XA>
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, 27 May 2017 03:16:27 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--F5kHS9j8QIM1KeK27M44pARuuhvECJDhE
Content-Type: multipart/mixed; boundary="5MhsKtu50KDxPvvb1a0wGhrTAj4Q1vRuj";
 protected-headers="v1"
From: Melinda Shore <melinda.shore@gmail.com>
To: ietf@ietf.org
Message-ID: <58583b21-6552-53c1-08cc-da7a9714ad93@gmail.com>
Subject: Re: Side meetings experiment at IETF 99
References: <F93ADBDA-0304-4545-8319-6600898D379E@gmail.com>
 <571A5927-B330-4A0F-82D4-843AAF46FD3E@gmail.com>
 <CAG4d1re7T96WnQKyn0eyXJLnejnKfE3GtyjMdeYA0OKxrZ=pRg@mail.gmail.com>
 <0CA30B5E7BF2617910B438AE@PSB>
In-Reply-To: <0CA30B5E7BF2617910B438AE@PSB>

--5MhsKtu50KDxPvvb1a0wGhrTAj4Q1vRuj
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 5/26/17 6:43 PM, John C Klensin wrote:
> (1) <rant> Suresh's description of these informal meetings match
> reasonably closely something we did in the distant past.  It was
> calls a "BOF".  Over the years, that concept of a BOF as a
> relatively informal session for discussion of new ideas and
> other things that were not ready for WG charters, morphed into
> very formal arrangements requiring formal proposals more than
> six weeks in advance of IETF meetings and approval by the IESG
> and advice from the IAB.   People dealt with that problem with
> formally organized Bar BOFs, a combination that would have been
> considered an oxymoron when BOFs were more informal gatherings,
> which led to requests for meeting rooms for side meetings and
> now sign-up arrangements for those meeting rooms.</rant> =20

I agree with all of this, although I think it's very easy to
move from less structure to more structure and extremely difficult
to move from more structure to less structure.  This weighty
process stuff was put in place to solve some problem, and I
think (but am not completely sure) that that problem is related
to resource contention and shortages, where "resource" is probably
some combination of time/attention of the I*, meeting rooms,
etc.  But, of course, the problem of how to have relatively
unstructured but productive interactions hasn't gone away, so
we keep adding more, er, "stuff" to the process of finding ways
to talk with each other.  And then the culture has changed as
well, with increasing participation from people whose job it
is to go to standards meetings bringing in process expectations
from organizations with more formal structures.

I'll add that it's kind of weird, at least to me, to say
that people will get supported resources to brainstorm together
informally but only if they grab that resource first.

It would be nice to find some way to strip away some of the
weight in our processes.  I'm still intrigued by the IRSG
experiment with letting groups meet for a year and seeing what
they come up with, then axing them if the work isn't up to
snuff, although that may not translate well to the broader
IETF organization.  In the meantime, over the past few years
I've increasingly found that the best place to grab some
informal chat and whiteboarding time to work through some ideas
at meetings is the hackathon (which is, of course, not its
intent, but there we are anyway).

Melinda



--5MhsKtu50KDxPvvb1a0wGhrTAj4Q1vRuj--

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

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

iQIcBAEBCgAGBQJZKO+FAAoJELiGRpM6HoEuEAcP/jK+EzfGYUue0p8p71d6cKzY
bLTJ5h3KtpT27VTfleD4rodSSrVfDWuI0YePrRArnc/Ql+zFynpHh37v+akTCtMZ
y2MSX/Bol7J91ELZbYTdXqQA4Okf0ouKExAF+MBZkZ3gydBTgZnSBiOOveMsbLGQ
2gsEfAOC72z64e0VmLGD4MTg7YK8CAGF/T3xbTD1ojlrJu5zyMJMNqEXd8NN0t+M
oDdxtlBPDPrry5XDn7Rqux6HYD7ptSLS5rmUseYWYF1FD+VCoYB6YN+c2xRBvyq/
6sb3Uwgud2OMBp84W0uKKj0/PxeBY8zLQU8Pvmo7cXkYqKsV5CPnMhIOVlB2Ff+8
SW8f+kynd2icMBOGG9iY3DivFBYfRUEoxE4bpjiCUlPxjxDtiauRffuhvbbyCfBI
fhorO2RxijCjixSI+JPbCPZOI0mgMd4VtQXYZT45+7fX6zdTmZdYtGGH/PJ+mkVX
vwrRx8xBY32dJdqHDXcgxK798ndppnBSijb1+r6n17j2WORWZy2WUFgcaULEw1W5
/2T/t/ymKHK+nJXx04syJl8Uc6TmUhbES5vQDwDROMMmARfhhQWxPBKjlvjBk/Kc
tYS1FuuicFQzFqncCba1muqeAak+OgNu3m9IhI3DL9BOY06so8ikApET+MYtcufu
L1nbD1GMFHH139Zo4r9m
=KnnL
-----END PGP SIGNATURE-----

--F5kHS9j8QIM1KeK27M44pARuuhvECJDhE--


From nobody Fri May 26 20:24:41 2017
Return-Path: <lorenzo@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 9EC2E12944F for <ietf@ietfa.amsl.com>; Fri, 26 May 2017 20:24:33 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, 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 7rZF_Z80Io9Y for <ietf@ietfa.amsl.com>; Fri, 26 May 2017 20:24:32 -0700 (PDT)
Received: from mail-ua0-x230.google.com (mail-ua0-x230.google.com [IPv6:2607:f8b0:400c:c08::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 3FD0C12EAAE for <ietf@ietf.org>; Fri, 26 May 2017 20:24:31 -0700 (PDT)
Received: by mail-ua0-x230.google.com with SMTP id e28so14653882uah.0 for <ietf@ietf.org>; Fri, 26 May 2017 20:24:31 -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=MOx32uabCYy0kIEko1W5PXt4p0qzsn7/gae0ivVXTl0=; b=ItwypI3RdBwRxlGmVm4CrVq60L0NAqu/SssdnAqwd/5HaJeD4DQ5UrEMSxQzkibH8e v6OlsmQzbKyUUKT/AZjB0BtWlwiu9IJpZ2eR0fY9cxc10IBkP24P+6NfQuvBPOQwV9TJ 4P99anePCSbOGwZsZ03gX4aodncVd3rCMfDZxGO/vxuX0IAKAw9bQOswjV68SsFUIpYk eDnM72SdXvZNwKx9Iv2ySsdvs4QzViXriWYtdRlhugysc/tATdYEw5OB6VSzs2qGJm0K VxNV4Jxo1UvcMUEXJKtMlkpjW8KRUD+kdNBkSAssPHExMjgXqT/5fGm3DYuFmC1uiKeE ZpYA==
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=MOx32uabCYy0kIEko1W5PXt4p0qzsn7/gae0ivVXTl0=; b=V3cR8hdLCJFST1hcnpn36CDDMTSMiOoNfH5z5srUEEq8BJAnMt2XcUw/7ygnS4HGky 2ot/r1umduH4EJOrXuDzGoALVFSqLnpY6DSWw0s/RcL31Jh4on9H2zIU8zNmUFLTNrdC YEBHW4aOQ5koCB8J7V5jw7o6KpgVJdN5vRZa3Sm9YbKMiNjMov3DfFxmXxIquDlWNqrq F5cRSr0WWS97MHljAW3K7nH4ljbjBgDGZJM1DMe0hdOBK9v+JAMnRZogEq6QtXbr/o2f cBiQ6deDll5eI1fmeRx+4ipkIF53AVrNAk2Zs1AdQSZnT+WxUlPfN9PyQHjG8I7bT4DB izeA==
X-Gm-Message-State: AODbwcCQC44BBdgCeIRpbfkCvre6etDuzJZ757eBUwbEQas+E9Gl5LpX qHyDvHUKI1s4ct+PC/WdrOuw8YaaNTBo
X-Received: by 10.159.35.232 with SMTP id 95mr2882552uao.48.1495855470202; Fri, 26 May 2017 20:24:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.168.138 with HTTP; Fri, 26 May 2017 20:24:28 -0700 (PDT)
Received: by 10.31.168.138 with HTTP; Fri, 26 May 2017 20:24:28 -0700 (PDT)
In-Reply-To: <fa82ceef-7cd6-ab37-aee6-f386266b5c56@gmail.com>
References: <149556850339.28443.2716896366216678645.idtracker@ietfa.amsl.com> <fa82ceef-7cd6-ab37-aee6-f386266b5c56@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 26 May 2017 20:24:28 -0700
Message-ID: <CAKD1Yr1kG2zCJ+qrap=Th9TP-uPi-eHmP8y=p-MWjsTYfuCrHw@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-unique-ipv6-prefix-per-host-03.txt> (Unique IPv6 Prefix Per Host) to Best Current Practice
To: "Brian E. Carpenter" <brian.e.carpenter@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>, "v6ops@ietf.org WG" <v6ops@ietf.org>,  draft-ietf-v6ops-unique-ipv6-prefix-per-host.all@ietf.org,  v6ops-chairs@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c03c790f03850055078fdbf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HR5bwr2z5lgiJRQ8PCY2uajW7u4>
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, 27 May 2017 03:24:34 -0000

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

On 26 May 2017 13:24, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:

So the draft
shouldn't assume a particular prefix length either. We all know that
it's usually 64 today, but that doesn't affect the argument made by
the draft.


It's always /64 for all addresses starting with binary 000, which cannot be
assigned to hosts in a real network because they are unallocated space.

We need consistency with RFC 7608 (BCP 198).


No, we don't. RFC 7608 is about forwarding, not address assignment.

--94eb2c03c790f03850055078fdbf
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 26 May 2017 13:24, &quot;Brian E Carpenter&quot; &lt;<a href=3D"mailto=
:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpenter@gmail.com=
</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"m_-27469499967=
7984619quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">So the draft<br>
shouldn&#39;t assume a particular prefix length either. We all know that<br=
>
it&#39;s usually 64 today, but that doesn&#39;t affect the argument made by=
<br>
the draft.</blockquote></div></div></div><div dir=3D"auto"><br></div><div d=
ir=3D"auto">It&#39;s always /64 for all addresses starting with binary 000,=
 which cannot be assigned to hosts in a real network because they are unall=
ocated space.</div><div dir=3D"auto"><br></div><div dir=3D"auto"><div class=
=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote class=3D"m_-2746949=
99677984619quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex"> We need consistency with RFC 7608 (BCP 198).</blockquote></=
div></div></div><div dir=3D"auto"><br></div><div dir=3D"auto"></div><div di=
r=3D"auto">No, we don&#39;t. RFC 7608 is about forwarding, not address assi=
gnment.</div></div>

--94eb2c03c790f03850055078fdbf--


From nobody Sat May 27 07:06:18 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 40FB912944E for <ietf@ietfa.amsl.com>; Sat, 27 May 2017 07:06:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.491
X-Spam-Level: 
X-Spam-Status: No, score=-2.491 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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] 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 xZHqZhH9Gk5n for <ietf@ietfa.amsl.com>; Sat, 27 May 2017 07:06:15 -0700 (PDT)
Received: from sonic312-29.consmr.mail.ir2.yahoo.com (sonic312-29.consmr.mail.ir2.yahoo.com [77.238.178.100]) (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 B172A1200C5 for <ietf@ietf.org>; Sat, 27 May 2017 07:06:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048;  t=1495893972; bh=Ke/X1Mv2deYFg23h/YgGuMhRkpPyqmCUrgUoAbBEhro=;  h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject;  b=NP81lK0KcYbzwa8p1kp3cT9iw166r6GRR3esuCwUpWZdX5Hzx7J3nvMu3N2BIZ0k6Jp0h6uXqRKi+9JUHC2G43YMOeFnBeBe6pwMOcH4iIXalRRQf/NBt0SZNqOpGuzzJw43GbXn76QoKTHnOcfNLOvnQf/VrhJ+TD0z0iaJvtAxH1hmOOyXU1Tg0kFJZYJikM3yPwP6yhYEOx9f3sacJ1j0E/tdu1UWwo2Ub34CQ57WpOtUrDxV13SsshP04xG4bJI/svD4sl9u65xOdM6znU/42y9OjefqBo66EfVyKl5rebkyMnP0SrdAoKJXHZzvXGs7d4m8SzNN9fW6ge4iBg==
X-YMail-OSG: hU38w6UVM1ljITDWJg5B_3B3wbRb1hviAkDByHC2jRoYKGbrgXFbERojbjVmQRj OdxunPOQ03cigIUjZvK56enjGEcdeEqSb091DPim.V8uDpTjM9qTfoaGY3uADPA5RWDkj.V4vThJ oKNGncAMqmnw3AHtZiB8wQC3OC7uCtB5NOYzsAaYlIGooO44rAGdX57c.bdCHQ0gjYKBKYiw1hAD ygOIcvrHrBmt6niQLXFfXwKFuWiJdmr_7N8sDagW2BtSSISSfLHs0mU9q_nJWSP8gM2JtDypIjOE MXKBwQ0ouBz3oMG3KdT_Vkqk_04RmSgcVgOV4kVKgiXL.OJKE5JiGiwejlJkb9zFSyYABqadLxhP zNGgBtbQ3NFzP_Wo6PltdTR7cj5AqxliwzisnT1JLN7F5kHwydxkGzDGv1AQDtg1afxkhscfW33r wKaGmEStbf2HLVpyBNTDeL39d.55oE9Gu7Os8QQMCgsqd0zRpwzu9PtwPGHhPIH7Hu1Eyx.kdX7T 0c.juCSibzq2.rLindj4hSK1iruhCuRy0nVc1SriVPoLLostBKG3P
Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.ir2.yahoo.com with HTTP; Sat, 27 May 2017 14:06:12 +0000
Date: Sat, 27 May 2017 14:06:11 +0000 (UTC)
From: Lloyd Wood <lloyd.wood@yahoo.co.uk>
Reply-To: Lloyd Wood <lloyd.wood@yahoo.co.uk>
To: IETF Discussion <ietf@ietf.org>
Message-ID: <1847083762.1690966.1495893971671@mail.yahoo.com>
In-Reply-To: <F93ADBDA-0304-4545-8319-6600898D379E@gmail.com>
References: <F93ADBDA-0304-4545-8319-6600898D379E@gmail.com>
Subject: Re: Side meetings experiment at IETF 99
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailer: WebService/1.1.9726 YahooMailNeo Mozilla/5.0 (Windows NT 6.1; Win64;  x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Zh0MyGmC2IFpL9kIy7pB-p1_pLg>
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, 27 May 2017 14:06:16 -0000

It's interesting watching the ongoing ossification of the
IETF and its workflow process.

RFCs were originally actual requests for comments.
(What was the first internet-draft requesting comments?)

Workgroups begat BOFs to possibly lead to workgroups.
BOFs became formalised to beget Bar BOFs once the BOF
process was formalised.

I was half-expecting bar seating reservations and waitlists,
with applications for bar discussions to be accepted by

a new ad-hoc committee, leading to Bar Queue Grouping
Formaulation discussions for Bar BOF applications...
And now we have side meetings? Bar, humbug.

Lloyd Wood lloyd.wood@yahoo.co.uk http://about.me/lloydwood=20



________________________________
From: Suresh Krishnan <suresh.krishnan@gmail.com>
To: IETF Discussion <ietf@ietf.org>=20
Cc: IESG <iesg@ietf.org>
Sent: Saturday, 27 May 2017, 6:25
Subject: Side meetings experiment at IETF 99



Hi all,

  The IESG has discussed how to improve the path for potential new topics t=
o be discussed transparently in the IETF community.  For some cross-area to=
pics, it is quite useful to have active conversation among a group of peopl=
e to work on defining the potential work and how it interacts with existing=
 efforts.  As the IETF week is quite busy, it can be a challenge to arrange=
 these side-meetings to avoid conflicts.  To facilitate the scheduling of t=
hese conversational side-meetings, the IESG has decided to provide a meetin=
g room at IETF 99 in Prague for around 30 people, with a U-shaped table, th=
at will be available for first-come first-served (FCFS) signup online as so=
on as the final IETF meeting agenda is published.  This experiment will be =
conducted for IETF 99 in Prague and will replace AD approval for rooms for =
side-meetings for potential new topics. Proponents of potential new topics =
are reminded that the BoF deadline is June 2; this includes non-WG forming =
BoFs.  The on-site signup FCFS room (seats about 16) will continue to be av=
ailable at IETF 99.


Thanks

Suresh

(on behalf of the IESG)


From nobody Sat May 27 23:50:16 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 F1BAD1293D6; Sat, 27 May 2017 23:49:58 -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: v6ops@ietf.org, ietf@ietf.org, draft-ietf-v6ops-v4v6-xlat-prefix.all@ietf.org
Subject: Genart last call review of draft-ietf-v6ops-v4v6-xlat-prefix-01
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149595419894.24426.7074020393438812680@ietfa.amsl.com>
Date: Sat, 27 May 2017 23:49:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KOrnoIfPnjQT3PeY9UEwuySbGxg>
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, 28 May 2017 06:49:59 -0000

Reviewer: Roni Even
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 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-v6ops-v4v6-xlat-prefix-??
Reviewer: Roni Even
Review Date: 2017-05-27
IETF LC End Date: 2017-06-05
IESG Telechat date: Not scheduled for a telechat

Summary:
The document is ready with issues for publication as standard track
RFC
Major issues:

Minor issues:
I was wondering why this document does not update RFC6052. My
reasoning is that RFC7915 section 6 says "The translator MUST support
the stateless address mapping algorithm defined in [RFC6052], which is
the default behavior."  This document suggests that the mapping in
this document can be used.

Nits/editorial comments: 



From nobody Sun May 28 04:27:35 2017
Return-Path: <tore@fud.no>
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 3112712422F; Sun, 28 May 2017 04:27:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.502
X-Spam-Level: 
X-Spam-Status: No, score=-0.502 tagged_above=-999 required=5 tests=[BAYES_05=-0.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 qyxs5eOm5HQ8; Sun, 28 May 2017 04:27:31 -0700 (PDT)
Received: from mail.fud.no (mail.fud.no [IPv6:2a02:c0:4f0:bb02:f816:3eff:fed3:8342]) (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 866241205F0; Sun, 28 May 2017 04:27:31 -0700 (PDT)
Received: from [2a02:fe0:c420:330a::bc8] (port=55670 helo=envy.e1.y.home) by mail.fud.no with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from <tore@fud.no>) id 1dEwM5-000501-Ce; Sun, 28 May 2017 11:27:29 +0000
Date: Sun, 28 May 2017 13:27:28 +0200
From: Tore Anderson <tore@fud.no>
To: Roni Even <ron.even.tlv@gmail.com>
Cc: <gen-art@ietf.org>, v6ops@ietf.org, ietf@ietf.org, draft-ietf-v6ops-v4v6-xlat-prefix.all@ietf.org
Subject: Re: [v6ops] Genart last call review of draft-ietf-v6ops-v4v6-xlat-prefix-01
Message-ID: <20170528132728.1b418349@envy.e1.y.home>
In-Reply-To: <149595419894.24426.7074020393438812680@ietfa.amsl.com>
References: <149595419894.24426.7074020393438812680@ietfa.amsl.com>
X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/a1SCFqE3j2U7SyQ8Eg1spvEJEDE>
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, 28 May 2017 11:27:33 -0000

Hi Roni, and thank you for your review.

> I was wondering why this document does not update RFC6052. My
> reasoning is that RFC7915 section 6 says "The translator MUST support
> the stateless address mapping algorithm defined in [RFC6052], which is
> the default behavior."  This document suggests that the mapping in
> this document can be used.

There's nothing in RFC6052 that needs updating, as RFC6052 already
caters for the use of its stateless address mapping algorithm with
arbitrary IPv6 prefixes outside of the WKP 64:ff9b::/96.

Tore


From nobody Sun May 28 10:00:19 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 56C721200F3 for <ietf@ietfa.amsl.com>; Sun, 28 May 2017 10:00:17 -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 MrItOXsHFW_Z for <ietf@ietfa.amsl.com>; Sun, 28 May 2017 10:00:15 -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 3518D1200FC for <ietf@ietf.org>; Sun, 28 May 2017 10:00:15 -0700 (PDT)
Received: by mail-yw0-x22a.google.com with SMTP id l14so20935429ywk.1 for <ietf@ietf.org>; Sun, 28 May 2017 10:00:15 -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=R3zH+WhU1vr849XBAWnY52eQ9ew7+OkUIuoM+imZ7lI=; b=YdHN2bXZExBBDKJsUf4JBgl39Tsr6ZDU9Dv9HIEfejO0nl2woeKllyb+wbpQF4BSg4 yHX9AZOvsNbo97S1QlaDU9z0oA698o9BLMKGZK+8Rbihmh/Cn9VDSvXZoaD/Iptoj31n 1/7C5pdwzW/d4vyC3Juusnoz9/1drjfrGSM7iRL3XKuBe+A9GWm6pPuT0WhpRAbBIhyl ULMYKZq8++PtES3vWFmpaVkok8gH2s0YG1XLVlht0zb4IIKDyPIlmn5nzn3Jmi5DKm5q 8DqHNb2H+HuSADu9txnr9Ymxs8lWFEb97TFOTpwT6r92eetp8dsQXwhMARU66C1ELFAw CwiA==
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=R3zH+WhU1vr849XBAWnY52eQ9ew7+OkUIuoM+imZ7lI=; b=rZyLC41Fi6QluQjNk1vN5GfTyH6gmOua78Q0Hp69k3J3KemR1u3tUcW0YL5GvWqLhv 9F4MW1XnlhLjPBfbI19azNL/o1L9D/tfPcPePq7tFnKRdl08gwgJrbLiJCGn4CNJMtmB ByOaUhEbisVTx4BhwPNldmWlSkRZ6kGk2p83uwvBuFA83aaCnyVWuTU37uBZCT9W/f2e AQg/7Qtl/esdWH7eN+GxgndQ37vyJAaTp2KdbBQ0Lt6xeKJ/SSbJq6mZSGYliugevIGk A93GnyKW3zVFxvrFra+SRQeUSXd5koGpEemQjq5WdDqcD44/5Nj44128aJailswICWKP MtSw==
X-Gm-Message-State: AODbwcA336snHzdtNPCBanYfaJF/N/pMYrepXzN0XJqAuK1xepFHrpQp tZMfBN0akpY2tS4V/Ig79uQCelrOng==
X-Received: by 10.129.76.17 with SMTP id z17mr9440630ywa.42.1495990814393; Sun, 28 May 2017 10:00:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.195.194 with HTTP; Sun, 28 May 2017 10:00:13 -0700 (PDT)
Received: by 10.37.195.194 with HTTP; Sun, 28 May 2017 10:00:13 -0700 (PDT)
In-Reply-To: <1847083762.1690966.1495893971671@mail.yahoo.com>
References: <F93ADBDA-0304-4545-8319-6600898D379E@gmail.com> <1847083762.1690966.1495893971671@mail.yahoo.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sun, 28 May 2017 13:00:13 -0400
Message-ID: <CAKKJt-fbSLyBbMFXiZ26=ufZdQf+-tFaEZV4EnUOa-WXJZHp5Q@mail.gmail.com>
Subject: Re: Side meetings experiment at IETF 99
To: Lloyd Wood <lloyd.wood@yahoo.co.uk>
Cc: IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113f2bdc1452930550988140"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ksw8p8Az0yPqlkBJAUyesm4N750>
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, 28 May 2017 17:00:17 -0000

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

Hi, Lloyd,

On May 27, 2017 09:06, "Lloyd Wood" <lloyd.wood@yahoo.co.uk> wrote:

It's interesting watching the ongoing ossification of the
IETF and its workflow process.

RFCs were originally actual requests for comments.
(What was the first internet-draft requesting comments?)

Workgroups begat BOFs to possibly lead to workgroups.
BOFs became formalised to beget Bar BOFs once the BOF
process was formalised.

I was half-expecting bar seating reservations and waitlists,
with applications for bar discussions to be accepted by

a new ad-hoc committee, leading to Bar Queue Grouping
Formaulation discussions for Bar BOF applications...
And now we have side meetings? Bar, humbug.


If by "now", you mean "since 2012", yes.

https://datatracker.ietf.org/doc/rfc6771/ (first draft in 2010) was written
in response to a series of barless bar bofs. One of the side effects of
having them called "bar bofs" was that they were easily confused with
actual BoFs, especially when they were held in the same meeting rooms as
actual BoFs, and looked indistingushable from actual BoFs. So, the
half-decade-ago guidance was to call them something else, hence "side
meetings".

I can't speak to why other IESG members thought this was a reasonable
experiment, but the reason I supported this experiment was to give the
community more tools to have the kind of organizational side meetings I
hope BoF proponents have - with Occam's Razor being whether the desired
outcome is

- the proponents agree on what to ask the community for (so, side meeting),
or

- the community agrees that a working group should be chartered (so, BoF).

And it's always appropriate to point out that if this all sounds like
organizational claptrap, there is no requirement to have a side meeting
before requesting a BoF, AND there's no requirement to have a BoF before
requesting approval for a working group charter, so you can safely ignore
ALL of it ;-)

Please, enjoy your day.

Spencer, speaking as only 1/15th of the currently serving ADs, but one who
has chartered working groups without a BoF ...

Lloyd Wood lloyd.wood@yahoo.co.uk http://about.me/lloydwood



________________________________
From: Suresh Krishnan <suresh.krishnan@gmail.com>
To: IETF Discussion <ietf@ietf.org>
Cc: IESG <iesg@ietf.org>
Sent: Saturday, 27 May 2017, 6:25
Subject: Side meetings experiment at IETF 99



Hi all,

  The IESG has discussed how to improve the path for potential new topics
to be discussed transparently in the IETF community.  For some cross-area
topics, it is quite useful to have active conversation among a group of
people to work on defining the potential work and how it interacts with
existing efforts.  As the IETF week is quite busy, it can be a challenge to
arrange these side-meetings to avoid conflicts.  To facilitate the
scheduling of these conversational side-meetings, the IESG has decided to
provide a meeting room at IETF 99 in Prague for around 30 people, with a
U-shaped table, that will be available for first-come first-served (FCFS)
signup online as soon as the final IETF meeting agenda is published.  This
experiment will be conducted for IETF 99 in Prague and will replace AD
approval for rooms for side-meetings for potential new topics. Proponents
of potential new topics are reminded that the BoF deadline is June 2; this
includes non-WG forming BoFs.  The on-site signup FCFS room (seats about
16) will continue to be available at IETF 99.


Thanks

Suresh

(on behalf of the IESG)

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

<div dir=3D"auto"><div>Hi, Lloyd,<br><div class=3D"gmail_extra"><br><div cl=
ass=3D"gmail_quote">On May 27, 2017 09:06, &quot;Lloyd Wood&quot; &lt;<a hr=
ef=3D"mailto:lloyd.wood@yahoo.co.uk">lloyd.wood@yahoo.co.uk</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">It&#39;s interesting watch=
ing the ongoing ossification of the<br>
IETF and its workflow process.<br>
<br>
RFCs were originally actual requests for comments.<br>
(What was the first internet-draft requesting comments?)<br>
<br>
Workgroups begat BOFs to possibly lead to workgroups.<br>
BOFs became formalised to beget Bar BOFs once the BOF<br>
process was formalised.<br>
<br>
I was half-expecting bar seating reservations and waitlists,<br>
with applications for bar discussions to be accepted by<br>
<br>
a new ad-hoc committee, leading to Bar Queue Grouping<br>
Formaulation discussions for Bar BOF applications...<br>
And now we have side meetings? Bar, humbug.<br></blockquote></div></div></d=
iv><div dir=3D"auto"><br></div><div dir=3D"auto">If by &quot;now&quot;, you=
 mean &quot;since 2012&quot;, yes.</div><div dir=3D"auto"><br></div><div di=
r=3D"auto"><a href=3D"https://datatracker.ietf.org/doc/rfc6771/">https://da=
tatracker.ietf.org/doc/rfc6771/</a> (first draft in 2010) was written in re=
sponse to a series of barless bar bofs. One of the side effects of having t=
hem called &quot;bar bofs&quot; was that they were easily confused with act=
ual BoFs, especially when they were held in the same meeting rooms as actua=
l BoFs, and looked indistingushable from actual BoFs. So, the half-decade-a=
go guidance was to call them something else, hence &quot;side meetings&quot=
;.</div><div dir=3D"auto"><br></div><div dir=3D"auto">I can&#39;t speak to =
why other IESG members thought this was a reasonable experiment, but the re=
ason I supported this experiment was to give the community more tools to ha=
ve the kind of organizational side meetings I hope BoF proponents have - wi=
th Occam&#39;s Razor being whether the desired outcome is</div><div dir=3D"=
auto"><br></div><div dir=3D"auto">- the proponents agree on what to ask the=
 community for (so, side meeting), or</div><div dir=3D"auto"><br></div><div=
 dir=3D"auto">- the community agrees that a working group should be charter=
ed (so, BoF).</div><div dir=3D"auto"><br></div><div dir=3D"auto">And it&#39=
;s always appropriate to point out that if this all sounds like organizatio=
nal claptrap, there is no requirement to have a side meeting before request=
ing a BoF, AND there&#39;s no requirement to have a BoF before requesting a=
pproval for a working group charter, so you can safely ignore ALL of it ;-)=
</div><div dir=3D"auto"><br></div><div dir=3D"auto">Please, enjoy your day.=
</div><div dir=3D"auto"><br></div><div dir=3D"auto">Spencer, speaking as on=
ly 1/15th of the currently serving ADs, but one who has chartered working g=
roups without a BoF ...</div><div dir=3D"auto"><br></div><div dir=3D"auto">=
<div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote class=3D"=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">Lloyd Wood <a href=3D"mailto:lloyd.wood@yahoo.co.uk">lloyd.wood@yahoo.c=
o.uk</a> <a href=3D"http://about.me/lloydwood" rel=3D"noreferrer" target=3D=
"_blank">http://about.me/lloydwood</a><br>
<br>
<br>
<br>
______________________________<wbr>__<br>
From: Suresh Krishnan &lt;<a href=3D"mailto:suresh.krishnan@gmail.com">sure=
sh.krishnan@gmail.com</a>&gt;<br>
To: IETF Discussion &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&=
gt;<br>
Cc: IESG &lt;<a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>&gt;<br>
Sent: Saturday, 27 May 2017, 6:25<br>
Subject: Side meetings experiment at IETF 99<br>
<div class=3D"elided-text"><br>
<br>
<br>
Hi all,<br>
<br>
=C2=A0 The IESG has discussed how to improve the path for potential new top=
ics to be discussed transparently in the IETF community.=C2=A0 For some cro=
ss-area topics, it is quite useful to have active conversation among a grou=
p of people to work on defining the potential work and how it interacts wit=
h existing efforts.=C2=A0 As the IETF week is quite busy, it can be a chall=
enge to arrange these side-meetings to avoid conflicts.=C2=A0 To facilitate=
 the scheduling of these conversational side-meetings, the IESG has decided=
 to provide a meeting room at IETF 99 in Prague for around 30 people, with =
a U-shaped table, that will be available for first-come first-served (FCFS)=
 signup online as soon as the final IETF meeting agenda is published.=C2=A0=
 This experiment will be conducted for IETF 99 in Prague and will replace A=
D approval for rooms for side-meetings for potential new topics. Proponents=
 of potential new topics are reminded that the BoF deadline is June 2; this=
 includes non-WG forming BoFs.=C2=A0 The on-site signup FCFS room (seats ab=
out 16) will continue to be available at IETF 99.<br>
<br>
<br>
Thanks<br>
<br>
Suresh<br>
<br>
(on behalf of the IESG)<br>
<br>
</div></blockquote></div><br></div></div></div>

--001a113f2bdc1452930550988140--


From nobody Mon May 29 05:21:13 2017
Return-Path: <bwietf@bwijnen.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 A856712954C; Mon, 29 May 2017 05:21:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Bert Wijnen <bwietf@bwijnen.net>
To: <ops-dir@ietf.org>
Cc: draft-ietf-sipcore-name-addr-guidance.all@ietf.org, sipcore@ietf.org, ietf@ietf.org
Subject: Opsdir last call review of draft-ietf-sipcore-name-addr-guidance-01
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149606047056.22794.2528878714319182056@ietfa.amsl.com>
Date: Mon, 29 May 2017 05:21:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FJjEeGOs1c4P0YByEp39GaaMFNE>
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, 29 May 2017 12:21:11 -0000

Reviewer: Bert Wijnen
Review result: Ready

This document makes a clarification to a set of RFCs. I think the
clarifications are clear and understandable.

Bert Wijnen


From nobody Mon May 29 18:55:01 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 B201C124D85; Mon, 29 May 2017 18:54:58 -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-nottingham-rfc5988bis.all@ietf.org, ietf@ietf.org
Subject: Opsdir last call review of draft-nottingham-rfc5988bis-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149610929864.16507.9397481139030287156@ietfa.amsl.com>
Date: Mon, 29 May 2017 18:54:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nLNgCp0VxJU1rr_Nh4OGoZfj3rM>
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, 30 May 2017 01:54:58 -0000

Reviewer: Carlos Martinez
Review result: Ready

With the caveat that I'm not an expert in the subject matter, I have
found this document well-written and easy to read. I believe it is
ready to move forward.

A minor nit, in the IANA considerations section:

| In addition to the actions below, IANA should terminate the Link
|   Relation Application Data Registry, as it has not been used, and
|   future use is not anticipated.

I believe this rather important requirement for IANA is somewhat lost
in the different sections. It should probably have it's own 4.x
section.

Thanks

Carlos


From nobody Mon May 29 21:31:44 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 F3B95128961; Mon, 29 May 2017 21:31:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=kLb2oC37; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=dZFa0bxq
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SSLWknXrC07Q; Mon, 29 May 2017 21:31:33 -0700 (PDT)
Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A81261200FC; Mon, 29 May 2017 21:31:33 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.nyi.internal (Postfix) with ESMTP id 4C51CC47; Tue, 30 May 2017 00:31:31 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Tue, 30 May 2017 00:31:31 -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=ZoAeLZDT6UmRv81NQM orse+WHs/CVcQ978zfs2GMntg=; b=kLb2oC37oVeXB/dFEU0N6wuXMQ5RouMLp8 DGz209kVymPfVV472Ne7f8HViuwfv3DuIlbPLPEbMDMWtbeqevAQkw1BQFKlST6Q M0w9v+1XblVIFnqQLQp2Xk1t131oE0dj9b/IakDj3DNa5uE5W0SAbl8bD0vBoZlM uLEXjWl8rWfpdnJ4I238OZWJqczn1zT+XJk4hSR/c+DRCfwajaNSt6t2sgbsf2It tn1nj6C+6uRCjjb8XbOSk2liWj+4jx0rqgAyrAowLQ2xlXYiAtCvTcXRl1gIdwlB Y1iZk3Po9gcnxzo95sJTIncyy5ZoWS70TriM5QgDjWBdWJPm9fLQ==
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=ZoAeLZDT6UmRv81NQMorse+WHs/CVcQ978zfs2GMntg=; b=dZFa0bxq Oo95gGGNpgyV+Q0Kp0BeuMa2lvJM+xy989gWeuLN/ZOq9J+PJ4V+QPMWEXfB3vz7 rtIUul1ptyU4X45y3PtlcjbjSXvk//PjfNfT1XOnFBlAm49AlQ4htSgXxqqXGbbO ALDAVdDJk04ER7qyKraF8dD3J8X2k7MoejFp0IbPfJQQGyJEJOMqGzar9yHCSe9F 1KETgzcbqwf1ODz/pYaSrE3rFgyD4pcPYWbOLfZA9WXR3jc/vqRu5QljG0pxEE4Q KI3suwFjEkHTST3X34ggYvgVVCK1V1+9oZauRmvuhMNT/L1YC9oPwq3aytS6ILDz asexJugyaswIyA==
X-ME-Sender: <xms:ovUsWZCxaCDGFcNqziuOuXEPUvGQV7eNfgi3o_eeZoNodEOL77HsJw>
X-Sasl-enc: jxuOK3ba5owmp57bSXzNLWWbBOBqCia2cqme/Zhd5S50 1496118689
Received: from [192.168.1.18] (cpe-124-188-19-231.hdbq1.win.bigpond.net.au [124.188.19.231]) by mail.messagingengine.com (Postfix) with ESMTPA id E3E6B240F6; Tue, 30 May 2017 00:31:28 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Opsdir last call review of draft-nottingham-rfc5988bis-05
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <149610929864.16507.9397481139030287156@ietfa.amsl.com>
Date: Tue, 30 May 2017 14:31:25 +1000
Cc: ops-dir@ietf.org, draft-nottingham-rfc5988bis.all@ietf.org, ietf@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <18AFCBD1-691D-4B76-9488-17EEA69B9397@mnot.net>
References: <149610929864.16507.9397481139030287156@ietfa.amsl.com>
To: Carlos Martinez <carlosm3011@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jC25w6pr5G3lh73xoVSWJEaycw0>
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, 30 May 2017 04:31:36 -0000

Done in:
  https://github.com/mnot/I-D/commit/b4db782a75e8

Thanks!


> On 30 May 2017, at 11:54 am, Carlos Martinez <carlosm3011@gmail.com> wrote:
> 
> Reviewer: Carlos Martinez
> Review result: Ready
> 
> With the caveat that I'm not an expert in the subject matter, I have
> found this document well-written and easy to read. I believe it is
> ready to move forward.
> 
> A minor nit, in the IANA considerations section:
> 
> | In addition to the actions below, IANA should terminate the Link
> |   Relation Application Data Registry, as it has not been used, and
> |   future use is not anticipated.
> 
> I believe this rather important requirement for IANA is somewhat lost
> in the different sections. It should probably have it's own 4.x
> section.
> 
> Thanks
> 
> Carlos
> 

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


From nobody Tue May 30 01:14:52 2017
Return-Path: <alexandru.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 7AAAD129B8B; Tue, 30 May 2017 01:14:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.401
X-Spam-Level: 
X-Spam-Status: No, score=0.401 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BiCo7l6P6Dgv; Tue, 30 May 2017 01:14:43 -0700 (PDT)
Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::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 0B236129511; Tue, 30 May 2017 01:14:42 -0700 (PDT)
Received: by mail-wm0-x243.google.com with SMTP id g15so23267516wmc.2; Tue, 30 May 2017 01:14:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:subject:to:references:cc:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=r3mb58DuLqJIEqRF9OdFBKBKRp+u1p/d+iDHIXFFqcM=; b=r3PSG2V339+v9il9eHcga62dVUwBfMje8JyxL28VzQ/VHWp+q9t0tXmw/PtjpD9xNF z5rnB9mm44uIPn3IWegiJiNWIZrtDhD7GUuK6PPwbyAt0/3pzrM1fL3Yw+AwHkoaCY73 2IG79LEmotUBUBb6rewjTJgRr9QKfWIMAjOHwNBFiREIZac+mo+q8YfeTLYkCYULs02o 5VwkulyRQP4xH/0xep6TiUbHOOL0SVedoVGjmHeH+tOskKQqHjGxNr44DrzA5au5ZqLL N300jUMz0PuVlXqpGWEIQ99K5jeIWZEGOMWFZl8n/Xf7H0Ja5ST0/MeSz40I/hnJ2Gay nzwQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:cc:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=r3mb58DuLqJIEqRF9OdFBKBKRp+u1p/d+iDHIXFFqcM=; b=S3Eu1TGrtFZhsvrIH0YhsXMHrLCPUwXO9G9PTMXYRXDBrJD9E7f20uMtVJSlTS9Ay8 ofHfpK7ppKqthU0WRZL7VW6D64EYMekCv40vVNmWFAxhJwxEnFRf1qmCojlB3T8ap2dA 3JIYf49UaUrhf6v2CgcZjm0r7k3iamuqchb8JVPRp1FuDgiDCczHWo2wtlvDUJ12UHqA GuupdswKSLiILJnw6ScPWIokuW8vpwDBCCwoeG9yj1/UVsUkUWz8EmS8faYJC+kA3ns4 f3vj1olE7+FMlQZdEgFzgHLM0GeIUYfHw7bQ04YMBCibNcbXCkB5v5KcOdUJ/oLSJmRg mCvA==
X-Gm-Message-State: AODbwcB16t9337PwUnhK8ZOhich8feXVHhU0SKxHImQUyOg38jYrqGdd POKPkI6wKClCwc7jREI=
X-Received: by 10.223.165.14 with SMTP id i14mr16078232wrb.127.1496132080322;  Tue, 30 May 2017 01:14:40 -0700 (PDT)
Received: from ?IPv6:2001:648:22b0:0:a5fc:c650:d3a3:a232? ([2001:648:22b0:0:a5fc:c650:d3a3:a232]) by smtp.googlemail.com with ESMTPSA id n92sm9539711wrb.62.2017.05.30.01.14.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 May 2017 01:14:39 -0700 (PDT)
From: Alexandre Petrescu <alexandru.petrescu@gmail.com>
X-Google-Original-From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-unique-ipv6-prefix-per-host-03.txt> (Unique IPv6 Prefix Per Host) to Best Current Practice
To: Lorenzo Colitti <lorenzo@google.com>, "Brian E. Carpenter" <brian.e.carpenter@gmail.com>
References: <149556850339.28443.2716896366216678645.idtracker@ietfa.amsl.com> <fa82ceef-7cd6-ab37-aee6-f386266b5c56@gmail.com> <CAKD1Yr1kG2zCJ+qrap=Th9TP-uPi-eHmP8y=p-MWjsTYfuCrHw@mail.gmail.com>
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, draft-ietf-v6ops-unique-ipv6-prefix-per-host.all@ietf.org, v6ops-chairs@ietf.org, IETF Discussion <ietf@ietf.org>
Message-ID: <c555b6d3-1a2b-0f61-2a8f-207cc0a49a68@gmail.com>
Date: Tue, 30 May 2017 11:14:36 +0300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr1kG2zCJ+qrap=Th9TP-uPi-eHmP8y=p-MWjsTYfuCrHw@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1n_XYTJytevGeWxO7oXJ84d4gio>
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, 30 May 2017 08:14:45 -0000

Le 27/05/2017 à 06:24, Lorenzo Colitti a écrit :
> On 26 May 2017 13:24, "Brian E Carpenter"
> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>>
> wrote:
>
>> So the draft shouldn't assume a particular prefix length either. We
>> all know that it's usually 64 today, but that doesn't affect the
>> argument made by the draft.
>
>
> It's always /64 for all addresses starting with binary 000, which
> cannot be assigned to hosts in a real network because they are
> unallocated space.
>
>> We need consistency with RFC 7608 (BCP 198).
>
>
> No, we don't. RFC 7608 is about forwarding, not address assignment.

But forwarded packets reach assigned addresses.

Some situations can be unfortunate, such as forwarding a /65 to an 
address containing a 64bit IID.

Consistency is desirable.

Alex

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


From nobody Tue May 30 07:51:58 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 385EB129564; Tue, 30 May 2017 07:51:44 -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-bmwg-ipv6-tran-tech-benchmarking.all@ietf.org, ietf@ietf.org, bmwg@ietf.org
Subject: Genart telechat review of draft-ietf-bmwg-ipv6-tran-tech-benchmarking-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.52.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149615590409.14768.3879167079373046273@ietfa.amsl.com>
Date: Tue, 30 May 2017 07:51:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9RhSR6OaeXITtwhBOIadD8Fx_8w>
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, 30 May 2017 14:51:44 -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 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-bmwg-ipv6-tran-tech-benchmarking-08
Reviewer: Robert Sparks
Review Date: 2017-05-30
IETF LC End Date: 2017-05-02
IESG Telechat date: 2017-06-08

Summary: Ready for publication as an Informational RFC

Thanks for addressing my comments on -06


From nobody Tue May 30 09:20:01 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 830441200E5; Tue, 30 May 2017 09:19:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: 99all@ietf.org, ietf@ietf.org
Subject: IETF 99 Meeting Information
X-Test-IDTracker: no
X-IETF-IDTracker: 6.52.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: IETF Agenda <agenda@ietf.org>
Message-ID: <149616119144.14899.16376329161675659474.idtracker@ietfa.amsl.com>
Date: Tue, 30 May 2017 09:19:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uO4P7LOlr2Sm_KulEOGPzzC8fYg>
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, 30 May 2017 16:19:52 -0000

IETF 99
Prague, Czech Republic
July 16-21, 2017
Host: Comcast/NBCUniversal and CZ.NIC

IETF 99 Information: https://ietf.org/meeting/99/index.html
Register online at: https://ietf.org/meeting/register.html

1.  Registration
2.  Value Added Tax (VAT)
3.  Visas & Letters of Invitation
4.  Accommodations
5.  Social Event!
6.  Hackathon

1. Registration:

Registration fees do not include the VAT of 21%. The VAT will be added to the fee and paid over to the tax authorities.

	A. Early-Bird Registration: USD 700.00, if paid in full prior to 23:59 UTC 2017-07-07
	B. After Early-Bird cutoff: USD 875.00
	C. Full-time Student Registrations: USD 150.00 (with proper ID)
	D. One Day Pass Registration: USD 375.00
	E. Registration Cancellation   
	Cutoff for registration cancellation is Monday, 10 July 2017 at UTC 23:59. 
	Cancellations are subject to a 10% (ten percent) cancellation fee if requested by 
	that date and time.
	F. Online Registration and Payment ends Friday, 14 July, 2017, 17:00 local Prague time
	G. On-site Registration begins on Sunday, 16 July 2017 at 10:00 local Prague time.

2. Value Added Tax (VAT)

	You may be entitled to recoup some or all of the VAT.
	In addition to a receipt from the IETF, all IETF 99
	attendees will receive a VAT compliant invoice from BC&A
	(VMC), our tax agent. For this meeting the Czech VAT of
	21% has been added to the Registration Fee. More
	information is available at:
	https://www.ietf.org/meeting/99/vat.html

3. Visas & Letters of Invitation:

	Letters of invitation are available through the registration
	system. Once you register for IETF 99 you may request a local
	letter of invitation through a link in your confirmation email or
	the self-service portal. 

4.  Accommodations:
	
	1. Hilton Prague (Headquarters Hotel, block of 600 rooms)
	Room Rate:  $148 (single) $164 (double) USD. Includes in-room high-speed
	Internet and breakfast.
	VAT of 15% (taxes subject to change) is excluded from
	the above prices.
	Reservation Cutoff Date: 19 June 2017
	Cancel with No Penalty: 7 Days prior to arrival
	Distance to Meeting Venue: N/A
	More detail at: http://www.ietf.org/meeting/99/hotel.html
	Reservations: http://eventsathilton.com/show/58ca77f5e6f1441222ee7b5e
	
	2. Hilton Prague Old Town (Overflow hotel, block of 140)
	Room Rate: $148 (single) $163 (double) USD. Includes in-room high-speed
	Internet and breakfast.
	VAT of 15% (taxes subject to change) is excluded from
	the above prices.
	Reservations Cutoff Date: 27 June 2017
	Cancel with No Penalty: Up to 72 hours prior to check-in/arrival
	Distance to Meeting Venue: 11 minute walk
	Reservations: http://eventsathilton.com/show/58ca6c33e6f1441222ee7b58

5. Social Event
	Date: Tuesday, 18 July 2017
	Time: 18:30 - 22:00
	Cost: $20 USD per ticket, limit two per attendee. Children 10 and under are free. 
	Hosted by: CZ.NIC, Comcast, and NBC Universal
	Location: Kafka museum at Hergetova Cihelna
	
	Join us on Tuesday, July 18 from 18:30 to 22:00 for a
	tour of the Kafka museum at Hergetova Cihelna. A boat
	ride to the event will start the evening off before you
	experience an interactive tour of different eras of
	Prague's history and meet iconic Czech personas that
	changed the country. The event will have Czech and other
	cuisines, beer, wine and non-alcoholic beverages.

	More information here: https://www.ietf99.cz/#socialevent
	Link to purchase Social Tickets: https://www.ietf.org/registration/ietf99/eventticket.py

6. Hackathon
	The IETF is holding a Hackathon at IETF 99 to encourage
  	developers to discuss, collaborate and develop utilities, ideas,
  	sample code and solutions that show practical implementations of
  	IETF standards.

	When: Saturday July 15 and Sunday July 16
	Where: Hilton Prague, Room TBD
	Signup for the Hackathon: https://www.ietf.org/registration/ietf99/hackathonregistration.py
	More information can be found here: http://ietf.org/hackathon/99-hackathon.html 
	Keep up to date by subscribing to: https://www.ietf.org/mailman/listinfo/hackathon

	The IETF is still seeking a Hackathon sponsor for 2017! For more information please see: 
	https://iaoc.ietf.org/host-and-sponsorship.html
	Contact Howard Baggott if interested, baggott@isoc.org.

	The Hackathon is free to attend and open to all. Extend
	the invitation to colleagues outside the IETF!

	Descriptions and information regarding the technologies
	for the hackathon are located on the IETF 99 Meeting Wiki:
	https://www.ietf.org/registration/MeetingWiki/wiki/99hackathon

	Don’t see anything that interests you? Feel free to add
	your preferred technology to the list, sign up as its
	Champion and show up to work on it. Note: you must login to
	the wiki to add content. If you do add a new technology, we
	strongly suggest that you send an email to hackathon@ietf.org
	to let others know. You may generate interest in your
	technology, and find other people who want to contribute to
	it.

	To request a wiki account, please click on the “login”
	button on the bottom right corner of the page, and choose
	“register.” If you need a new password please click on the
	“login” button on the bottom right corner of the page and
	choose “Send new password.”


From nobody Tue May 30 10:42:51 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 6A20F129C31; Tue, 30 May 2017 10:42:36 -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: draft-ietf-sacm-requirements.all@ietf.org, ietf@ietf.org, sacm@ietf.org
Subject: Secdir last call review of draft-ietf-sacm-requirements-15
X-Test-IDTracker: no
X-IETF-IDTracker: 6.52.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149616615640.19877.7389294095180042080@ietfa.amsl.com>
Date: Tue, 30 May 2017 10:42:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lxBCag1pXJ4ZTgbhx0QF8EDV0Xs>
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, 30 May 2017 17:42:36 -0000

Reviewer: Barry Leiba
Review result: Has Nits

While I'm calling this document "ready", I really don't see why it
should be published in the RFC series at all.  It's well written, and
it seems to be important material for the working group to use as it
develops the SACM  architecture, data model and transport protocols,
but does not seem to be of lasting interest after those are done.  I'd
rather see it in the working group wiki, and used that way.

That said, I know the working group wants it published and that my
comment here is likely not to go far, so I'll say that if it's to be
published as an RFC, it's ready.  The one nit I note is that in the
XML "title" element you appear to have abbrev="Abbreviated Title",
rather than the more likely abbrev="SACM Requirements".


From nobody Tue May 30 11:51:24 2017
Return-Path: <jinmei.tatuya@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 79F19129440; Tue, 30 May 2017 11:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 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, 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 x-w0MmMXzvHX; Tue, 30 May 2017 11:51:19 -0700 (PDT)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::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 E890B129420; Tue, 30 May 2017 11:51:18 -0700 (PDT)
Received: by mail-qk0-x236.google.com with SMTP id u75so76024345qka.3; Tue, 30 May 2017 11:51: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=l+siWs4Zxd8827PTbYgaDszkKJi+QRaL/JSUSnlwXlw=; b=rexeH9Xx3zQGdZnCKTnugG3512pXBNSKKOYrauzIAkNstIRWRzCBzCw0KKfon7pylH +lmlgbJC5x8dy/+HWMwpM0huHXXl22NJK0epKHcyoBW4CjfB7+N2L5bPXphMe8wug+2h nFzfczxWmkhGILm7o+YgXamLbBL/22gy5UN052Q9Cx+ujMBrABjXV8NhjirowugFl/Un fEvrmzMmwkIPyw64BE9sN5FCtHDfz3/TDfYy8PRyVMaWEFwmbNCLjE2y9EMpw2FsdYUe 1bUtkoyj06o0qEF9bvcm5k0GjCSP5Nqjze+n0RVTTQFJQMb0dQSlUU5Z9NqBYLveMu8D q01w==
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=l+siWs4Zxd8827PTbYgaDszkKJi+QRaL/JSUSnlwXlw=; b=jaC1MUh6Nb5SqkR8RJiUZ/Kp8DGUwanLtMNN7Qzsn8zUdZAYz/mmHnMbYI2zIUB/NH r0jggzE4RIyW49pevbuuto4pDWtGjhSbKzilfz/EVisJcYrlkbBUgrqXquwxZYK0kT6T tWWJn1i9/N68u5iP+1UHP+WyhK8MRHTEBagK6gxTmkbQ7MTHFxZhuRCtmoLOx+UNf82D kpJBESFu2GGMU4+KH53dm0CrP54iv+77hRCXgT0QewsLqGPyow5A8/gLF9g+0+Mh4UB4 lUftLySSrGu/NndDFmm3WAWiOqHhtoJ66fiuMHjxojEBaDIRfay7a717wLHBa9prB27D CpQw==
X-Gm-Message-State: AODbwcDoFnPS/0XPW83WDcl1P8YwypplM4c46WJPpW/SgxWNqsz/DlqB mjrlVpp2XK273o9xDyxYfvyMuvVtnQ==
X-Received: by 10.55.104.129 with SMTP id d123mr26987944qkc.126.1496170278051;  Tue, 30 May 2017 11:51:18 -0700 (PDT)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.200.48.141 with HTTP; Tue, 30 May 2017 11:51:17 -0700 (PDT)
In-Reply-To: <fa82ceef-7cd6-ab37-aee6-f386266b5c56@gmail.com>
References: <149556850339.28443.2716896366216678645.idtracker@ietfa.amsl.com> <fa82ceef-7cd6-ab37-aee6-f386266b5c56@gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Date: Tue, 30 May 2017 11:51:17 -0700
X-Google-Sender-Auth: 0gfMttB0zGD93h3h_yqDAWPhgTs
Message-ID: <CAJE_bqfN2u0YN1Ufd+-BN+z0byab0o97kWQoAJPn9a0xOt-vUg@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-unique-ipv6-prefix-per-host-03.txt> (Unique IPv6 Prefix Per Host) to Best Current Practice
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>,  draft-ietf-v6ops-unique-ipv6-prefix-per-host.all@ietf.org,  v6ops-chairs@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Mu9Yn5n3-JeJLxS9cKDs0ePU4mk>
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, 30 May 2017 18:51:22 -0000

At Sat, 27 May 2017 08:24:39 +1200,
Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> This draft cites RFC4862 (SLAAC) and mentions Router Advertisements
> (without also citing RFC4861, which is possibly a mistake). Those
> documents do not specify the subnet prefix length. So the draft
> shouldn't assume a particular prefix length either. We all know that
> it's usually 64 today, but that doesn't affect the argument made by
> the draft. We need consistency with RFC 7608 (BCP 198).

It looks like this draft has the commonly seen confusion I tried to
clarify in my own draft: draft-jinmei-6man-prefix-clarify-00

Specifically, in Section 4 v6ops-unique-ipv6-prefix-per-host-03
states:

   This
   RA contains two important parameters for the EU/subscriber to
   consume: (1) a /64 prefix and (2) flags.
[...]
   o  A-flag = 1 (The UE/subscriber can configure itself using SLAAC)
[...]
   o  L-flag = 0 (The UE/subscriber is off-link, which means that the
      UE/subscriber will ALWAYS send packets to its default gateway,
      even if the destination is within the range of the /64 prefix)

Since A-flag=1 and L-flag=0, this /64 prefix is an "SLAAC subnet
prefix" but not an "on-link prefix" (using the terminology introduced
in draft-jinmei-6man-prefix-clarify-00).  And, in that sense, the
"which means..." part could even be misleading in that it might read
as if this (SLAAC subnet) prefix were somehow related to an on-link
prefix.

I'd also note that "The UE/subscriber is off-link" is not accurate.
When L=0 "the advertisement makes no statement about on-link or
off-link properties of the prefix" (RFC4861 Section 4.6.2).  See below
for a specific suggestion to fix it.

As for the reference to the specific number of 64, I think it's okay
with this clarification, the fact that that's the only possible SLAAC
subnet prefix length today in practice, and the intended status of
this document (BCP).

But I also tend to agree with Brian in that this document could be
more clarified to avoid confusing and/or misleading readers.  My high
level suggestion is:

- clearly state that the prefix in this document is a kind of "SLAAC
  subnet prefix" but not an "on-link prefix".  I understand "SLAAC
  subnet prefix" may not be the best choice since this document
  doesn't limit the address configuration method to SLAAC - hence "a
  kind of".  But the main point is that it's better to explicitly
  clarify the prefix is one and the only one of the two kinds of
  prefixes advertised via RA PIO.  With this clarification, and fixing
  the error I pointed out above, the description for the L-flag would
  look something like this:

   o  L-flag = 0 (the prefix is not an on-link prefix, which means
      that the UE/subscriber will NEVER assume destination addresses
      that match the prefix are on-link and will ALWAYS send packets
      to those addresses to its default gateway.)

- if it refers to a specific (SLAAC subnet) prefix length of 64,
  explain that it's the SLAAC subnet prefix length derived from the
  current addressing architecture for unicast IPv6 addresses starting
  with the binary value 000 (and those are only addresses used in
  production today).  It might also note that future specification may
  or may not introduce a different prefix length for different ranges
  of addresses, but that's out of scope of the document as a BCP.

--
JINMEI, Tatuya


From nobody Wed May 31 09:01:58 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 9050F12EAE4; Wed, 31 May 2017 09:01:49 -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: ietf@ietf.org, draft-ietf-pals-p2mp-pw-lsp-ping.all@ietf.org, pals@ietf.org
Subject: Genart last call review of draft-ietf-pals-p2mp-pw-lsp-ping-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.52.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149624650955.19868.7577458644448516887@ietfa.amsl.com>
Date: Wed, 31 May 2017 09:01:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/25OOJ1wz3nGh-1fQbhbXpxgHw9w>
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, 31 May 2017 16:01:50 -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-pals-p2mp-pw-lsp-ping-??
Reviewer: Joel Halpern
Review Date: 2017-05-31
IETF LC End Date: 2017-06-09
IESG Telechat date: 2017-06-22

Summary: This document is ready for publication as a proposed
standard

Major issues: N/A

Minor issues: N/A

Nits/editorial comments:  N/A



From nobody Wed May 31 11:35:43 2017
Return-Path: <stewart@g3ysx.org.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 91613129AC1; Wed, 31 May 2017 11:35:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart@g3ysx.org.uk>
To: <rtg-dir@ietf.org>
Cc: draft-bashandy-rtgwg-segment-routing-ti-lfa.all@ietf.org, ietf@ietf.org
Subject: Rtgdir early review of draft-bashandy-rtgwg-segment-routing-ti-lfa-00
X-Test-IDTracker: no
X-IETF-IDTracker: 6.52.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149625574151.19908.2374594318145684422@ietfa.amsl.com>
Date: Wed, 31 May 2017 11:35:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/x_B-10AKOb_oalRS1-iLQaLqC7E>
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, 31 May 2017 18:35:42 -0000

Reviewer: Stewart Bryant
Review result: Has Issues

These review comments were incorrectly posted against the uloop draft,
apologies for any confustion.

I have been asked to perform an early review of this document on
behalf of the Routing Directorate.

Summary:

A document on this subject is something that the WG should publish,
but I think that there are number of issues that the WG need to
discuss and reach consensus on before deciding whether or not they
should adopt this draft as a starting point for that work.


Major Issues:

Before I get into the substance I am surprised that there are no IPR
disclosures. In an earlier and related work
(draft-francois-segment-routing-ti-lfa-00) there were three IPR
disclosures. 

The work has four basic components, the concept of resolving the
problem of P and Q being non-adjacent, the use of SR to solve the
non-adjacency, the use of the post convergence path following failure
and the applicability of these techniques to an SR network. The first
and second points seem of utility in non-SR networks, and so I am
surprised that they are not called out as such, in the first case
perhaps with consideration to strategically places RSVP tunnels, or
binding segments.

The issue of mapping repair path to the post convergence path to the
something that has always concerned me in this concept. It is true
that traffic that always passes through the PLR will experience the
properties the authors describe, but not all traffic will pass through
the PLR post convergence. The post failure path will be topology
dependent, and may take a different path from the point of ingress.

I am also concerned that the authors do not discuss the need for loop
free convergence, since although traffic going through the repair path
will be loop-free, traffic arriving at the PLR might not be. Consider
for example a topology fragment that looks like a clock with a router
at each minute. Traffic enters at 9 o'clock, leave at 3 o'clock and
goes via 12 o'clock and 12 o'clock fails.  The routers 9..12 will
re-converge at different times and this may give rise to the
micro-looping of traffic trying to get to the PLR. A summary of the
problem and a pointer to the companion draft may be sufficient.

Finally on the basic concept it would be good to state up from whether
the proposal is constrained solely to SR networks, or whether the
authors believe that the concept is of wider applicability. It see no
reason why it would be constrained to only work on SR networks.

There is no discussion of multiple failures, nor as far as I can see
of failures that are worse than anticipated. This is an important
point that needs to be established early. Some methods, (MRT)
intrinsically address multiple failures, others (NV) intrinsically
exclude them. Simple LFA needs a supervisor to quickly abandon all
hope when they occur.

In an SR network the paths used are not the shortest paths, they are a
collection of shortest paths, so there needs to be some discussion on
the interaction between the SR paths and repair paths to consider
whether it is unconditionally safe against forwarding loops. It would
presumably be so if the authors borrowed the concept of repair
addresses rather than normal forwarding addresses from not-via, but I
don't think they have done this.

There should also be some discussion on the original path constraints
that are applicable to the repair. Presumably the ingress node
constrained the traffic to go though failed node F for a reason. If
the repair is unconstrained that reason could be violated, but this is
not discussed in the text.


In the Security section you say:

   The behavior described in this document is internal functionality
   to a router that result in the ability to guarantee an upper bound
   on the time taken to restore traffic flow upon the failure of a
   directly connected link or node. As such no additional security
   risk is introduced by using the mechanisms proposed in this
   document.


SB> I am not sure that the above is correct. There may be a security
reason
SB> why a packet was steered along a path which breaks when you use
this
SB> technique.

In the conclusion you say:

   The
   mechanism is able to calculate the backup path irrespective of the
   topology as long as the topology is sufficiently redundant.


SB> That is certainly true in classic. I am not sure this is
universally 
SB> true under SR which includes the use of non-shortest path and 
SB> binding segments.



Minor issues:

   For each destination in the network, TI-LFA prepares a data-plane
   switch-over to be activated upon detection of the failure of a
   link used to reach the destination.  

SB> To make the scaling clearer to the reader, I think you need
SB> to make it clear that for each protected link, you determine
SB> the repair needed to reach every destination reachable over that
SB> link. You sort of say that, but it's a bit hidden.

   We provide the TI-LFA approach that achieves guaranteed coverage
   against link, node, and local SRLG failure, in any IGP network,
   relying on the flexibility of SR.

SB> Should that be any SINGLE link.... failure?

In the text (and the text that follows)

   To do so, S applies a "NEXT" operation on Adj(S-F) and then two
   consecutive "PUSH" operations: first it pushes a node segment for
F,
   and then it pushes a protection list allowing to reach F while
   bypassing S-F.

You need to reference the SR operations.

Also you are considering Adj segments, and presumably they were there
for a reason, but you do not discuss that.

In 5.3.1 and 5.3.2 you have a list of conditions, but do not make it
clear whether any or all must be true.

Nits

1. Introduction

   Segment Routing aims at supporting services with tight SLA
   guarantees [1]. This document provides a local repair mechanism
   relying on SR-capable of restoring end-to-end connectivity in the
   case of a sudden failure of a network component.

SB> Grammar needs a little work in the last sentence.

In Fig 1, I assume that the blobs are network fragments.

In the conclusion you say:
   This document proposes a mechanism that is able to pre-calculate a
   backup path for every primary path so as to be able to protect
   against the failure of a directly connected link or node. 
SB> you need to add SRLG


From nobody Wed May 31 13:11:03 2017
Return-Path: <housley@vigilsec.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 B5CBA129AD3; Wed, 31 May 2017 13:10:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Russ Housley <housley@vigilsec.com>
To: <gen-art@ietf.org>
Cc: precis@ietf.org, ietf@ietf.org, draft-ietf-precis-7700bis.all@ietf.org
Subject: Genart last call review of draft-ietf-precis-7700bis-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.52.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149626145570.19916.16628797750334932421@ietfa.amsl.com>
Date: Wed, 31 May 2017 13:10:55 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Zs6bCal2TnaTH60ITRQpspFYPB0>
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, 31 May 2017 20:10:56 -0000

Reviewer: Russ Housley
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
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-precis-7700bis-07
Reviewer: Russ Housley
Review Date: 2017-05-31
IETF LC End Date: 2017-06-13
IESG Telechat date: 2017-07-06

Summary: Ready

Major Concerns: None

Minor Concerns: None

Nits:

Section 2.3 includes this note:

   Note: An entity SHOULD NOT apply the Case Mapping Rule during
   enforcement, because typically it is appropriate only during
   comparison.

I question the inclusion of "typically" in this note.  Can you simply
say that the Case Mapping Rule SHOULD only be used during comparison?



From nobody Wed May 31 23:53:20 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 B3C34126D46; Wed, 31 May 2017 23:53:03 -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: avtext@ietf.org, draft-ietf-avtext-lrr.all@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-ietf-avtext-lrr-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.52.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149629998360.19813.14889515687249184753@ietfa.amsl.com>
Date: Wed, 31 May 2017 23:53:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZcjqzKnwJdVJyykfRCJpkkIeEXk>
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, 01 Jun 2017 06:53:04 -0000

Reviewer: Roni Even
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 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-avtext-lrr-??
Reviewer: Roni Even
Review Date: 2017-05-31
IETF LC End Date: 2017-06-08
IESG Telechat date: Not scheduled for a telechat

Summary:
The document is ready with issues for a standard track RFC
Major issues:

Minor issues:

1. Can you specify both TTID and TLID in the same FCI.
2. What is the meaning of value 0 for TTID and TLID - TID or LID =0 in
frame marking draft means base layer if there is scalability.
     This relates to the previous question. 
3.  What would an FCI with both TTID and TLID equal 0 mean.

Nits/editorial comments: 

1. Section 3 "an Real-Time Transport Control Protocol" should be "a
Real...".
2. In section 3 " [RFC5104](Section 3.5.1)" there is a link to section
3.5.1 but it does not work.
3. In section 3.2 "(see section Section 2.1)" section appears twice.



